-
Notifications
You must be signed in to change notification settings - Fork 34
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
Add the column db_type to database sheet #466
Add the column db_type to database sheet #466
Conversation
|
Update the mOTU database name in ci.yml
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 think this is veeery close now :D
I think once we have the optional column bit implemented I would start with testing :)
Otherwise this is looking very clean and concise :D!
Co-authored-by: James A. Fellows Yates <[email protected]>
correct the definition of db_type for both short and long reads
OK I made some changes to make the channel manipulation more 'nextflowy', namely using I then modify both database and read channels to have type as a 'meta-meta', to allow them to combine, and then move the type back into the meta after combining @LilyAnderssonLee please test when you have time to make sure I didn't get something compeltely wrong |
@jfy133 I have run the tests for the |
I forgot to check: did you check with an oldstyle samplesheet without the db_type column ? We wanted to make it optional and if so default to short;long right? |
Fix the issue #226
PR checklist
nf-core 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).