Open cassimons opened 1 year ago
This is annoying, sorry @cassimons! Is it blocking you? If so, I'll remove these keys quickly now while I think about the best way to handle this.
Thanks @vivbak, that fix has got the pipeline running again for the moment.
In the recent update to analysis_keys, the CramQC stage now hard codes
picard_wgs_metrics
as an expected analysis_key. However, when running on exome data this stage will producepicard_hs_metrics
notpicard_wgs_metrics
.In the current state, if the pipeline is run on exome data you get the following error (edited for clarity):
I am not sure where this target dependent behaviour should be handled?