-
Notifications
You must be signed in to change notification settings - Fork 99
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
add cancer splicing lib to starfusion ref #610
base: dev
Are you sure you want to change the base?
Conversation
Warning Newer version of the nf-core template is available. Your pipeline is using an old version of the nf-core template: 3.1.1. For more documentation on how to update your pipeline, please see the nf-core documentation and Synchronisation documentation. |
|
@rannick something seems wrong with the |
I would like to understand what is going on before merging, hope that is ok with you. Just easier to debug if there are not multiple layers |
Yeah I fully understand! This is not urgent for us I updated our local reference manually. Let me know if I can help |
I think the error comes from the starfusion references being different |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could you add the module's test ? :)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Right! I forgot thanks for the reminder :)
@@ -142,7 +143,15 @@ workflow BUILD_REFERENCES { | |||
!file(params.starfusion_ref_stub_check).exists() || file(params.starfusion_ref_stub_check).isEmpty() )) { | |||
STARFUSION_BUILD(ch_fasta, ch_gtf, params.fusion_annot_lib, params.species) | |||
ch_versions = ch_versions.mix(STARFUSION_BUILD.out.versions) | |||
ch_starfusion_ref = STARFUSION_BUILD.out.reference | |||
if (params.ctatsplicing || params.all) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
if (params.ctatsplicing || params.all) { | |
if (params.ctatsplicing) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The params.all is in the outer if clause:
if ((params.starfusion || params.all) &&
(!file(params.starfusion_ref).exists() || file(params.starfusion_ref).isEmpty() ||
!file(params.starfusion_ref_stub_check).exists() || file(params.starfusion_ref_stub_check).isEmpty() )) {
STARFUSION_BUILD(ch_fasta, ch_gtf, params.fusion_annot_lib, params.species)
I think that is why the test_build
is failing. It is not populating the ch_starfusion_ref
with CTATSPLICING_PREPGENOMELIB.out.reference
or STARFUSION_BUILD.out.reference
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hmm but the ctatsplicing reference creation will not run if --all
is supplied this way?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it is difficult to differentiate which is the default here. If --all
is supplied, should ch_starfusion_ref
produce STARFUSION_BUILD.out.reference
or CTATSPLICING_PREPGENOMELIB.out.reference
?
Before adding your new module CTATSPLICING_PREPGENOMELIB
, the default for --all
was to use the STARFUSION_BUILD.out.reference
but now it will always default to CTATSPLICING_PREPGENOMELIB.out.reference
.
PR checklist
nf-core lint
).nextflow run . -profile debug,test,docker --outdir <OUTDIR>
).docs/usage.md
is updated.docs/output.md
is updated.CHANGELOG.md
is updated.README.md
is updated (including new tool citations and authors/contributors).