-
Notifications
You must be signed in to change notification settings - Fork 3
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
Properly instruct BALSAMIC to run QC workflow for MH cases #825
Comments
So what is the proposed solution? |
There will be many cases in future where we would like to run only QC part of Balsamic. |
Temporary solutions:
This exists to some extent. Probably @annagellerbring or @elevu know how it is defined in orders. Maybe even @patrikgrenfeldt can help on order portal side. |
As I understand, now in the order portal for Balsamic there is no way to specify the delivery type. But it definitely can be added. |
How about analysis type? Are all analysis only |
@Mropat What is the status of this? Order portal parts seems to be done, but what is left to do in cg? |
This is ancient. Balsamic doesn't have qc only anymore. This can be closed. |
Nice! |
BALSAMIC is capable running in
qc
only mode since release3.X.X
. Andcg
is supporting it since couple of month ago: #687Related prio 3 project: https://github.com/Clinical-Genomics/cgp-mh-fastq-delivery
MH samples can be problematic and break variant calling runs for various reasons (it is outside of scope of this issue), so we preferably want to run only QC for these samples so we can deliver trimmed fastq files.
This is related to AMDoc 1046 (fastq delivery MH).
I'm fully aware of Trailblazer can mark cases as finished, but BALSAMIC won't prepare a delivery file unless it is properly finished (the feature to deliver without finishing workflow will be deprecated, i.e. if there is any file missing, it won't prepare the file. This is due to refactoring I'll be doing to prepare unique tags for sake of housekeeper store smoothness).
The text was updated successfully, but these errors were encountered: