-
Notifications
You must be signed in to change notification settings - Fork 57
Don't force same KMCP mode for all database #493
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
Conversation
|
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.
🚀
Shall the kmcp mode be documented in docs? I realised it was not there.
} | ||
|
||
KMCP_SEARCH ( ch_input_for_kmcp.db, ch_input_for_kmcp.reads ) | ||
KMCP_SEARCH ( ch_input_for_kmcp.reads, ch_input_for_kmcp.db ) |
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.
Good catch!
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 flipped it in the module update 😬
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.
Yes, I saw it.
@sofstam what do you mean exactly? I would assume people would have to look up the settings of the particualar tool they are interested in anyway to know what to put in the db_params of the database sheet? |
PR checklist
nf-core lint
).nf-test test main.nf.test -profile test,docker
).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).