Skip to content
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

Open
wants to merge 6 commits into
base: dev
Choose a base branch
from

Conversation

alanmmobbs93
Copy link

PR checklist

  • This comment contains a description of changes (with reason).
  • If you've fixed a bug or added code that should be tested, add tests!
  • If you've added a new tool - have you followed the pipeline conventions in the contribution docs
  • If necessary, also make a PR on the nf-core/rnafusion branch on the nf-core/test-datasets repository.
  • Make sure your code lints (nf-core lint).
  • Check for unexpected warnings in debug mode (nextflow run . -profile debug,test,docker --outdir <OUTDIR>).
  • Usage Documentation in docs/usage.md is updated.
  • Output Documentation in 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

  • nf-test for local subworkflow 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

  • Refactored subworkflow inputs.
  • Improve fusioncatcher detect module's input, adding meta components.

Perspectives

  • It's necessary to improve how modules are skipped and the use of the dummy file.

@nf-core-bot
Copy link
Member

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.
Please update your pipeline to the latest version.

For more documentation on how to update your pipeline, please see the nf-core documentation and Synchronisation documentation.

Copy link

github-actions bot commented Dec 18, 2024

nf-core pipelines lint overall result: Passed ✅

Posted for pipeline commit 970fded

+| ✅ 222 tests passed       |+
#| ❔   2 tests were ignored |#

❔ Tests ignored:

  • files_unchanged - File ignored due to lint config: .github/CONTRIBUTING.md
  • files_unchanged - File ignored due to lint config: .github/PULL_REQUEST_TEMPLATE.md

✅ Tests passed:

Run details

  • nf-core/tools version 3.0.2
  • Run at 2024-12-19 17:23:41

@@ -3,6 +3,6 @@ process {
resourceLimits = [
cpus: 4,
memory: '15.GB',
time: '1.h'
time: '4.h'
Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I know this is not optimal, maybe skip this change until using fusioncatcher_download properly

Comment on lines -12 to -25
"references",
"references/ensembl",
"references/ensembl/Homo_sapiens.GRCh38.102.chr.gtf",
"references/ensembl/Homo_sapiens.GRCh38.102.dna.primary_assembly.fa",
"references/ensembl/Homo_sapiens.GRCh38.102.dna.primary_assembly.fa.fai",
"references/ensembl/Homo_sapiens.GRCh38.102.genepred",
"references/ensembl/Homo_sapiens.GRCh38.102.gtf",
"references/ensembl/Homo_sapiens.GRCh38.102.refflat",
"references/ensembl/Homo_sapiens.GRCh38.102_rrna_intervals.gtf.interval_list",
"references/hgnc",
"references/hgnc/HGNC-DB-timestamp.txt",
"references/hgnc/hgnc_complete_set.txt",
"rrnatranscripts",
"rrnatranscripts/Homo_sapiens.GRCh38.102_rrna_intervals.gtf"

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why are all of these references being removed?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@atrigila Sorry for this but I'm having many issues when running the pipeline's test. I wanted to talk to you and @nschcolnicov about that because I don't know which ones are known to fail or succeed

@@ -6,8 +6,8 @@ process FUSIONCATCHER_DOWNLOAD {
container "community.wave.seqera.io/library/fusioncatcher:1.33--4733482b637ef92f"

output:
path "*" , emit: reference
path "versions.yml" , emit: versions
tuple env(meta), path("*"), emit: reference

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Interesting. Did you find a change in behaviour with or without env()?


if (( run_fusioncatcher || all) && !fusioninspector_only ) {
if (fusioncatcher_fusions){

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change

ch_fusioncatcher_fusions = reads.combine(Channel.value(file(fusioncatcher_fusions, checkIfExists:true)))
.map { meta, reads, fusions -> [ meta, fusions ] }
} else {

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants