-
Notifications
You must be signed in to change notification settings - Fork 2
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
Samplesheet multilevel nesting ick4 #24
Conversation
… is this param is empty
Please remove option in either scenario, ignore any other fastq files present in the directory tree passed to |
I have removed the |
This needs some param validation because running with NOTE: Process |
I've enforced the valid values for |
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.
Looks good.
This branch adds an option to choose which files to create the samplesheet (and thus, run the pipeline) on. It defaults to only running the pipeline on fastq files nested in subdirectories, the default CDC Core format. But you can instead choose to run the pipeline on all the files (top-nested and one-dir-under nested) or only the top-level files.
Test cmd:
nextflow run main.nf --indir /scicomp/groups-pure/Projects/scbs_mpob/JRowell_ick4/mpox_testing/paired/ --file_levels <nested, all, top> --outdir /scicomp/groups-pure/Projects/scbs_mpob/JRowell_ick4/mpox_testing/results/ --project_name test -config /scicomp/reference/nextflow/configs/cdc-dev.config -profile singularity,rosalind
PR checklist
nf-core lint
).nextflow run . -profile 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).