-
Notifications
You must be signed in to change notification settings - Fork 16
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
1.0.0 - Ratzupaltuff #135
1.0.0 - Ratzupaltuff #135
Conversation
Community
Community update
Update from Upstream
Update README.md
If you go in the |
Important! Template update for nf-core/tools v2.9
$query_list \\ | ||
--threads $task.cpus \\ | ||
$paf_mappings \\ | ||
$args > ${prefix}.paf |
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.
On start, wfmash options do not seem to have defaults
Wfmash Options
wfmash_block_length : null
wfmash_sparse_map : null
shows up as
Wfmash Options
wfmash_block_length N/A
wfmash_sparse_map N/A
in the MultiQC report, under nf-core/pangenome Workflow Summary
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 was also seeing this and was annoyed.
These parameters can be set, but if they are not set, they will be calculated based on other parameters later. So I am not sure what to do here.
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.
Because one should never set params.<PARAM>
later.
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 see, haven't run into this before. Maybe drop a question on nf-core slack to see if anyone else might have a suggestion.
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.
https://nfcore.slack.com/archives/CE6SDBX2A/p1689605084916579
I tried, but no answer, yet.
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 I don't get an answer by the end of the week, I would resolve this conversation and continue the first release protocol.
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.
@maxulysse @mirpedrol Do you know more here maybe?
Ran |
I see no blockers, only small doc changes 🎉 Would you like me to suggest changes or pull request against this branch? |
@heuermh Suggest changes here would be cool! |
Thanks for the review @heuermh ! |
Co-authored-by: Michael L Heuer <[email protected]>
I think |
Per Slack, we're ready to go! |
🎉 |
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).Towards a first release of the nf-core/pangenome pipeline. Fingers crossed :)