Open Nicolai-vKuegelgen opened 5 months ago
The wrapper should not determine anything but remain oblivious of its context. I'd rather factor the config access out and make the par_intervals a parameter, i.e. an entry in params.args. I.e. the steps calling this wrapper should be in charge of producing the correct par_intervals value to hand off to the wrapper.
Sounds like a better solution, I have so far only 'hotfixed' this by adding a "helper_gcnv_model_targeted" config section to my WGS projects.
Describe the bug The wrapper for gcnv contig_ploidy contains hard-coded config sections (see below) but is uactually sed by different steps (helper_gcnv_model_targeted and helper_gcnv_model_wgs)
From snappy_wrappers/wrappers/gcnv/contig_ploidy/wrapper.py
To Reproduce Steps to reproduce the behavior:
Expected behavior The wrapper script should automatically determine whether the targeted or wgs step is being run.