-
Notifications
You must be signed in to change notification settings - Fork 717
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
Activate multiqc ai summaries #1495
Conversation
Add support for MultiQC's AI-powered summaries feature via new parameter: - Add enable_multiqc_ai boolean parameter to schema - Add --ai flag to MultiQC args when enabled - Use nf-core standard array syntax for MultiQC args
Warning Newer version of the nf-core template is available. Your pipeline is using an old version of the nf-core template: 3.0.2. For more documentation on how to update your pipeline, please see the nf-core documentation and Synchronisation documentation. |
|
Needs nf-core/modules#7364 |
@nf-core-bot fix linting |
@nf-core-bot fix linting |
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.
<3
Report from test profile: multiqc_report rnaseq_test.html.zip |
This reverts commit 81f6bb4.
// Propagate API keys to MultiQC | ||
System.getenv('SEQERA_ACCESS_TOKEN')?.with { SEQERA_ACCESS_TOKEN = it } | ||
System.getenv('TOWER_ACCESS_TOKEN')?.with { TOWER_ACCESS_TOKEN = it } | ||
System.getenv('OPENAI_API_KEY')?.with { OPENAI_API_KEY = it } | ||
System.getenv('ANTHROPIC_API_KEY')?.with { ANTHROPIC_API_KEY = it } |
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 know nf-core wants to be 'batteries included', but this does feel like a lot of stuff when it's user configurable.
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 quite like the approach, but I'm not sure that it'll be allowed with the new config parser :/
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.
But I don't want to be the user that configures it ;-)
Converted to draft pending conclusion of community discussions as to how good an idea this is |
Closing for now after discussion, we'll wait and see how people end up using this. Once we update the multiqc module you will already be able to use this functionality by following the MultiQC docs. If you come across this wanting to use the functionality, you'll need custom configuration like:
... and then run the workflow like this:
|
PR checklist
nf-core pipelines lint
).nextflow run . -profile test,docker --outdir <OUTDIR>
).nextflow run . -profile debug,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).