-
Notifications
You must be signed in to change notification settings - Fork 0
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
Run controls through cttso pipeline #506
Comments
Ok. I reckon, we still need not being data-portal-apis/data_processors/pipeline/domain/workflow.py Lines 323 to 327 in f790a68
|
Think, data-portal-apis/data_processors/pipeline/domain/workflow.py Lines 349 to 354 in f790a68
data-portal-apis/data_processors/pipeline/domain/workflow.py Lines 30 to 37 in f790a68
|
Historically, data-portal-apis/data_processors/pipeline/domain/workflow.py Lines 329 to 334 in f790a68
|
I guess; without changing to current
That should work? |
Descope from 2.0 release for now further discussion |
Under
dragen_tso_ctdna_step.py
snippet below; we currently remove samples that have qc selected and only include samples that must be tumor.data-portal-apis/data_processors/pipeline/orchestration/dragen_tso_ctdna_step.py
Lines 91 to 97 in f790a68
If we wish to also run the control samples, should this rule be reduced to the following criteria?
The text was updated successfully, but these errors were encountered: