-
Notifications
You must be signed in to change notification settings - Fork 7
[Do not merge!] Pseudo PR for first release #159
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
base: TEMPLATE
Are you sure you want to change the base?
Conversation
Merging template updates
Co-authored-by: Mahesh Binzer-Panchal <mahesh.binzer-panchal@nbis.se>
Warning Newer version of the nf-core template is available. Your pipeline is using an old version of the nf-core template: 3.2.0. For more documentation on how to update your pipeline, please see the nf-core documentation and Synchronisation documentation. |
Important! Template update for nf-core/tools v3.2.1
This pull request sets up GitHub code scanning for this repository. Once the scans have completed and the checks have passed, the analysis results for this pull request branch will appear on this overview. Once you merge this pull request, the 'Security' tab will show more code scanning analysis results (for example, for the default branch). Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results. For more information about GitHub code scanning, check out the documentation. |
@mashehu and @mahesh-panchal, Thanks for all the detailed feedback! I believe I have addressed all of your comments so far. |
saveAs: { filename -> filename.equals('versions.yml') ? null : filename } | ||
] | ||
cpus = { 4 } | ||
memory = { 8.GB * Math.pow(3, task.attempt - 1) } |
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 you have a rough idea of what usually causes process failure with regard to resources, not that there is also https://www.nextflow.io/docs/latest/process.html#dynamic-task-resources-with-previous-execution-trace
ext.args = { secrets.NCBI_API_KEY ? "--api-key ${secrets.NCBI_API_KEY}" : "" } | ||
|
||
// Settings to avoid API rate limits and not put too much stress on servers | ||
maxForks = 1 // NCBI seems to be not allowing concurrent downloads with this command, althogh I cannot find any documentation about this |
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.
maxForks = 1 // NCBI seems to be not allowing concurrent downloads with this command, althogh I cannot find any documentation about this | |
maxForks = 1 // NCBI seems to be not allowing concurrent downloads with this command, although I cannot find any documentation about this |
memory = { 1.GB * task.attempt } | ||
time = { 12.h * task.attempt } | ||
storeDir = { params.data_dir == "false" ? null : "${params.data_dir}/assembly_metadata" } | ||
ext.args = { secrets.NCBI_API_KEY ? "--as-json-lines --api-key ${secrets.NCBI_API_KEY}" : "--as-json-lines" } |
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.
An alternate way to write this is:
ext.args = { secrets.NCBI_API_KEY ? "--as-json-lines --api-key ${secrets.NCBI_API_KEY}" : "--as-json-lines" } | |
ext.args = { [ | |
secrets.NCBI_API_KEY ? "--api-key ${secrets.NCBI_API_KEY}": "", | |
"--as-json-lines" | |
].minus("").join(" ") } |
This avoids repetition and makes it easier to add to later, particularly if extra conditions are introduced.
The typical command for running the pipeline is as follows: | ||
|
||
```bash | ||
nextflow run nf-core/pathogensurveillance --input ./samplesheet.csv --outdir ./results --genome GRCh37 -profile docker | ||
nextflow run nf-core/pathogensurveillance -profile <REPLACE WITH RUN TOOL> -resume --input <REPLACE WITH TSV/CSV> --outdir <REPLACE WITH OUTPUT PATH> |
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 find the term RUN TOOL
confusing here. Perhaps use package manager
.
@@ -0,0 +1,23 @@ | |||
# Dockerfile to create container with Cell Ranger v8.0.0 and bcl2fastq v2.20.0 |
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 don't see these tools in this file.
This looks like something that could be created with Seqera Containers instead. https://seqera.io/containers/
versions = versions.mix(BAKTA_BAKTA.out.versions) | ||
|
||
// For references that have a gff already, combine the assembly with the gff the same way bakta outputs | ||
MAKE_GFF_WITH_FASTA ( |
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.
Versions also missing here. Please check the other processes below too.
} | ||
messages = messages.mix(spades_warnings) | ||
|
||
FLYE_NANOPORE ( |
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.
Please add versions for both FLYE
s
messages = Channel.empty() | ||
|
||
// Parse input tables | ||
SAMPLESHEET_CHECK ( sample_data_tsv, reference_data_tsv, params.max_samples ) |
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.
Please add versions
versions = versions.mix(FIND_ASSEMBLIES.out.versions) | ||
|
||
// Parse assembly metadata to TSVs to save time when multiple samples use the same data | ||
PARSE_ASSEMBLIES ( |
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.
Please add versions, and for other processes below too.
.map {[[id: it.getSimpleName()], it]} | ||
|
||
// For each group, assign references for variant calling if not user-defined | ||
ASSIGN_MAPPING_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.
missing versions
Do not merge! This is a PR of
dev
compared to theTEMPLATE
branch for whole-pipeline reviewing purposes. Changes should be made todev
and this PR should not be merged! The actual release PR is at #136