Louis Le Nézet
06/24/2025, 8:34 PMtask.ext.my_args but this does not fit with the task.ext.args that we use in all the other modules.
Also this way this argument is not referenced in the meta.yaml.
I see three possibility:
1. Continue using task.ext.my_args
2. Use tast.ext.args with flag (more complicated to parse) or use a python argument parser
3. Set all the argument as value channel even the optional one (+ description in meta.yml)
What do you think ?Mahesh Binzer-Panchal
06/25/2025, 8:07 AMscript:
args = task.ext.args ?: ""
prefix = task.ext.prefix ?: meta.id
template 'some_script.py'
and then args is used as a string in the script, as an input: would.
You can then do stuff with shlex.split(), or however you want to deal with it since the other input variables are also embedded in the template.Louis Le Nézet
06/25/2025, 9:42 AMCELLBENDER_MERGE :
script:
prefix = task.ext.prefix ?: "${meta.id}"
output_layer = task.ext.output_layer ?: "cellbender"
template 'merge.py'Mahesh Binzer-Panchal
06/25/2025, 9:44 AMoutput_layer? I would treat that as a input: because looks like a required value where you provide a default.Louis Le Nézet
06/25/2025, 9:46 AM