-
Notifications
You must be signed in to change notification settings - Fork 35
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 a new sample field to meta #425
Add a new sample field to meta #425
Conversation
|
Damn! "no space left on device."!
|
Yeah, I guess I have to start thinking about turning off some of the process for the github ci, so that we can avoid this error 😅 |
…raredisease into addsampletometa
mt_analysis uses a few large containers so I have turned it off to save space in the runner. But I haven't turned it off for the Hopefully, we can switch to nf-test soon, and all these issues will go away 😅 |
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.
Looks good to me! Nice to not rely on string splitting to get the sample id.
PR checklist
We used to add "_T[linenumber]" to sample id to differentiate between data from different lanes. Then before merging bam files from multiple lanes into one file, we split based on "_T" to get the sample id back. This could potentially cause issues when the sample name has an _T. To avoid that, I have created a new field
sample
in the meta which also contains the user given sample id. Before the merging step the value from the sample field will be copied into id.nf-core lint
).nextflow run . -profile test,docker --outdir <OUTDIR>
).nextflow run . -profile test_one_sample,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).