Accepted, thank you.

1. Please move Python mains into sub-folder, e.g. ModelRun or py-main or any other name of your choice. I assume it would be more than one Python utility here.

2. It may be better to shutdown oms by curl -v -X PUT http://localhost:4040/shutdown on Linux / MacOS or use kill.

Please see example of shutdown at https://github.com/openmpp/openmpp.github.io/wiki/Oms-API-PUT-shutdown-service or even better at models/stop-model-ui-linux.sh. Also there is a kill example at https://github.com/openmpp/other/blob/master/azure_cloud/oms/omsd-start.sh and omsd-stop.sh

It is also possible to start oms on available port instead of hard coded 4040. Scripts in models directory doing exactly that. Oms can save it own URL into file where stop-model-ui-linux.sh can find it later.

I am thinking to add another option into oms to save pid into file, similar to current option which save url into file. Feel free to do it, if you have a time to play with Go.

3. I understand model run function is at very early stage now, you will probably going to add more options into that. Model run API call documented at: https://github.com/openmpp/openmpp.github.io/wiki/Oms-API-POST-run-the-model

I am keeping Opts OpenM.Threads for backward compatibility only, it should work, however, it would be nice to use Threads integer in the new development, example from wiki:

{
  "ModelName": "RiskPaths",
  "Opts": {
    "OpenM.SubValues": "16"
  },
  "Threads": 4,
  "Mpi": {
    "Np": 2
  },
  "Template": "mpiSmallCluster.template.txt"
}