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

--skip_fastqc is not usable #330

Closed
d4straub opened this issue Sep 23, 2021 · 1 comment
Closed

--skip_fastqc is not usable #330

d4straub opened this issue Sep 23, 2021 · 1 comment
Labels
bug Something isn't working
Milestone

Comments

@d4straub
Copy link
Collaborator

d4straub commented Sep 23, 2021

Description of the bug

Usage of --skip_fastqc crashes the pipeline.

Steps to reproduce

Steps to reproduce the behaviour:

nextflow run nf-core/ampliseq -r 2.1.0 -profile test,singularity --skip_fastqc

Error:

No such variable: info

 -- Check script 'ampliseq/./workflows/../subworkflows/local/parse_input.nf' at line: 61 or see '.nextflow.log' file for more details
Access to 'FASTQC.out' is undefined since process doesn't declare any output

 -- Check script 'ampliseq/./workflows/ampliseq.nf' at line: 584 or see '.nextflow.log' file for more details

Expected behaviour

No error.

Additional context

That line needs to read:

if (!params.skip_fastqc) {
    ch_multiqc_files = ch_multiqc_files.mix(FASTQC.out.zip.collect{it[1]}.ifEmpty([]))
}

Also, the test profiles should probably use various skipping options to make sure those work!

@d4straub d4straub added the bug Something isn't working label Sep 23, 2021
@d4straub d4straub added this to the 2.1.1 milestone Sep 23, 2021
@d4straub
Copy link
Collaborator Author

That's fixed in the dev branch.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant