Slivka's service definition allows different parameters to be passed to runners according to input parameters (data and other arguments) for a job, but does not allow the constructed commandline executed by the runner to be reconfigured.
e.g. for the ClustalO service, the binary has an argument which specifies the number of threads to use. In v0.80 of slivka's slivka-bio, this parameter is hardcoded regardless of the number of cores allocated to it on the executable platform.
At the very least, different runner configurations should allow values of the thread parameter to be adjusted. Ideally there could also be a way that a runner is informed that a particular parameter should map to information such as the number of cores, allowing each runner to map this data to the runtime platform as needed.
Slivka's service definition allows different parameters to be passed to runners according to input parameters (data and other arguments) for a job, but does not allow the constructed commandline executed by the runner to be reconfigured.
e.g. for the ClustalO service, the binary has an argument which specifies the number of threads to use. In v0.80 of slivka's slivka-bio, this parameter is hardcoded regardless of the number of cores allocated to it on the executable platform.
At the very least, different runner configurations should allow values of the thread parameter to be adjusted. Ideally there could also be a way that a runner is informed that a particular parameter should map to information such as the number of cores, allowing each runner to map this data to the runtime platform as needed.