You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Today for any paired assay we run all possible pairs, which for most projects is no issue as there are not multiple assays on the constitutional or tumor samples but some things like ULP-WGS then get paired with high-coverage WGS wasting compute time, we could set a pairing requirement so assays could be filtered by a metric like total reads which is known at runtime, alternatively the pipeline could be split into alignment and calling parts so coverage could be known at the calling runtime but this might create more havoc than it is worth.
The text was updated successfully, but these errors were encountered:
Today for any paired assay we run all possible pairs, which for most projects is no issue as there are not multiple assays on the constitutional or tumor samples but some things like ULP-WGS then get paired with high-coverage WGS wasting compute time, we could set a pairing requirement so assays could be filtered by a metric like total reads which is known at runtime, alternatively the pipeline could be split into alignment and calling parts so coverage could be known at the calling runtime but this might create more havoc than it is worth.
The text was updated successfully, but these errors were encountered: