-
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 nf-test for FUSIONCATCHER
subworkflow
#591
Add nf-test for FUSIONCATCHER
subworkflow
#591
Conversation
Warning Newer version of the nf-core template is available. Your pipeline is using an old version of the nf-core template: 3.0.2. For more documentation on how to update your pipeline, please see the nf-core documentation and Synchronisation documentation. |
|
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.
Excellent job! Let's wait for @rannick's feedback before merging just to make sure this does not disrupt anything.
conda "${projectDir}/environment.yml" | ||
container "${ workflow.containerEngine == 'singularity' && !task.ext.singularity_pull_docker_container ? | ||
'https://community-cr-prod.seqera.io/docker/registry/v2/blobs/sha256/d5/d53f36e9e01d14a0ae8e15f8046f52b2883c970c27fe43fdfbd9440a55f5403f/data' : | ||
'community.wave.seqera.io/library/fusioncatcher:1.33--4733482b637ef92f' }" |
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.
It works with 1.33 now because ensembl 113 directory does not contain 37 and 38 which was confusing the build. It is not compatible with ensembl 112 and we can't force to use a certain version. Conclusion: use 113/gencode 47 as default
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.
And keep 1.33. Add in documentation where to find the references for ensembl 112
|
||
input: | ||
tuple val(meta), path(fasta) | ||
path reference | ||
tuple val(meta), path(fastqs, stageAs: "input/*") |
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.
Nice!
|
||
// TODO: Remove fusioncatcher_fusions as parameter. | ||
// TODO: remove dummy file. Work with Channel.empty() | ||
// TODO: if the files were already produced and the user want to skip the module because of this, they should be taken them from the sample sheet |
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.
Open issues?
Using fusioncatcher_fusions is practical if you want to run the last part of rnafusion: fusionreport and fusioninspector
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.
@rannick thanks for looking into this! Let me understand this correctly, the fusioncatcher_fusions
parameter can be used to feed one single file and hence skip the FUSIONCATCHER_DETECT
process, am I right? I was wondering whether this single file should contain the data for all the samples that the user want to analyze with fusionreport and fusioninspector, or if the user has to supply one file per sample.
If the second scenario is the correct one, then I got it wrong and this approach is almost ok, just a little bit of fine tunning. But if the first scenario is the correct, then we should change more things
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.
Yes fusioncatcher_fusions
allows to skip FUSIONCATCHER_DETECT
.
That is a good point about the samples, the files probably have to be fed per sample
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.
LGTM, just have a look at my comments
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).It's important to know that it takes almost and hour to download the references.
Added
FUSIONCATCHER
. Note: fusioncatcher reference files are large for testing purposes. After this it would be ideal to dedicate some time to create or obtain a reduced reference, as explained in Create small reference for fusioncatcher (chr4) #580.Changed
fusioncatcher
detect module's input, adding meta components.Perspectives