Implications of not using @tools.carpexample(parser, jobID)

Question

I have found that being forced to pass the run() function to the tools.carpexample decorator is limiting my code functionality. What will happen if I don't use the decorator?

As far as I can tell, the biggest things are that I will have to define my own parser, and the job directory isn't automatically made. Is there something else that might be important?

Edit: It also looks like I can't call job.bench(). How can I circumvent this?

Thanks,

Chang

Answer 1

Hi Chang,

run() takes care of multiple things including submitting the job. This is straightforward on a local machine but more tricky on HPC systems that use different schedulers and require additional parameters. To support these mechanisms, I would advise to use these functions. If you have suggestions for improvements, you can of course open a merge request. The bench issue would require more specific information.

You can find the code here: https://git.opencarp.org/openCARP/carputils/-/blob/master/carputils/job/job.py

These are the currently supported machines: https://git.opencarp.org/openCARP/carputils/-/tree/master/carputils/machines