Conversation
Contributor
|
Warning Newer version of the nf-core template is available. Your pipeline is using an old version of the nf-core template: 3.5.2. For more documentation on how to update your pipeline, please see the nf-core documentation and Synchronisation documentation. |
|
sainsachiko
approved these changes
Jun 5, 2026
sainsachiko
left a comment
Contributor
There was a problem hiding this comment.
This looks good to me. It will be beneficial in case we don't have run accession (with the old code, user will need to put a dummy run accession anyway). We might need to adjust pubish path in case we want to export individual alignment, but that is not allowed in the pipeline.
Just a minor comment on release date of the pipeline in citation.cffs
Co-authored-by: Hanh Hoang <134130358+sainsachiko@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
I know we had agreed in our discussion and in the code review on requiring
meta.sampleto be unique, but as I was running the pipeline on Psyche data and got a lot of failures, I realised it's because I hadn't mademeta.sampleunique when there was multiple BAMs for the same tolid.Before updating the samplesheets, I thought: is the unicity really necessary ?
As far as I could see, the code doesn't require it to be unique. It's not used as a key for like
join.The main thing I had to add is a fallback for
meta.runbeing empty.What do you think ? Did I miss anything ?
PR checklist
nf-core pipelines lint).nextflow run . -profile test,docker --outdir <OUTDIR>).nextflow run . -profile debug,test,docker --outdir <OUTDIR>).docs/usage.mdis updated.docs/output.mdis updated.CHANGELOG.mdis updated.README.mdis updated (including new tool citations and authors/contributors).