-
Notifications
You must be signed in to change notification settings - Fork 36
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
Improve validation of run_accessions IDs within sample IDs #484
Conversation
|
@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.
Tested and it detects if a run_accession
and a sample Id
are not unique.
I'm just wondering, are there good cases for when a run accession should not be globally unique, but only within a sample? |
Do you approve then @sofstam ? |
Depends on naming schemes basically... My definition of a run was based on ENA run accessions where they were were unique. But @sofstam had an issue where they were not unique, as they were interpreted as a sequencing run accession (so in the table, the same sequencing run was shared across all the samples). |
I approve, shall but shall we merge the template first? |
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.
The linting should be fixed before merging!
Should hopefully close #483
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).