-
Notifications
You must be signed in to change notification settings - Fork 6
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
Duplicate sequencing #62
Comments
Example
In this project, the first tumor sample of donor
|
Changes in Command:
Directory structure:
|
How to work with duplicate sequencing?
Duplicate sequencing
In the DKTK Master programme, patients are sometimes sequenced several times, apparently from the same tumor sample (according to DKFZ sample ids), several weeks or months apart.
When the second sequencing of the same sample comes in, I would increase the extract or library number, depending on the value of the DKFZ sample id. I would then have a library with an id which looks as one of the two below:
Current situation
SODAR
allows any sample, extract & library id, in particular<donor_id>-<sample_id>-DNA2-WES1
in its ISATAB description & in the directory structure.cubi-tk sodar pull-raw-data
downloads only one library per sample and per assay. It means that if both<donor_id>-<sample_id>-DNA1-WES1
and<donor_id>-<sample_id>-DNA2-WES1
are present in SODAR, only one of them will be downloaded (I am not sure which one).snappy
silently assigns the sample id to<donor_id>-<sample_id>-DNA1-WES1
, regardless of the input folder name.<donor_id>-<sample_id>-DNA2-WES1
could be uploaded to<donor_id>-<sample_id>-DNA1-WES1
bycubi-tk
.Points for discussion
snappy
orcubi-tk
, that would address the issue.The text was updated successfully, but these errors were encountered: