Hi again, thank you for your response.
Apologies I haven't checked back, but I wanted to be sure of the problem. I ran it again on three systems: ubuntu 16.04, macOS and windows10. To my surprise, only the macOS converged with the same files.
To look more closely at the outputs, I ran the openCARP docker container with the -ti option in both windows and macOS, adding the folder with my data as in per the following command:
docker run --rm --volume=/path/to/data:/shared:z --workdir=/shared -ti docker.opencarp.org/opencarp/opencarp:latest
Then on both I ran the same command:
openCARP +F parameter_file.par -simID in_docker_OUTPUT
The outputs differ in some obvious places (like the "done in XX.YY seconds" messages) and in some not so obvious places! Only in macOS, I get a message:
elliptic PDE (PETSc) solver: switching to default settings "-ksp_type cg -pc_type hypre -pc_hypre_type boomeramg -pc_hypre_boomeramg_max_iter 1 -pc_hypre_boomeramg_strong_threshold 0.0 -options_left"
You can see in the link below a screenshot of a diff I did of both outputs. It seems this might be the problem, do you know a way I could set the solver to default settings? Is this available as options when calling the openCARP command or parameter_file?
Link to diff screenshot
Given the previous information, I thought of trying a workaround that meant setting specifically the solver's parameters, this is setting a few other parameters, it looks long, but it's really simple. The command changes to:
docker run --rm --volume=/path/to/files:/shared:z --workdir=/shared docker.opencarp.org/opencarp/opencarp:latest openCARP -ellip_use_pt 0 -parab_use_pt 0 -parab_options_file /usr/local/lib/python3.6/dist-packages/carputils-0.0.0-py3.6-linux-x86_64.egg/carputils/resources/petsc_options/ilu_cg_opts -ellip_options_file /usr/local/lib/python3.6/dist-packages/carputils-0.0.0-py3.6-linux-x86_64.egg/carputils/resources/petsc_options/amg_cg_opts +F carpf_laplace_PA.par -simID output_directory
I'll carry on running tests and come back to this thread if necessary. I still do not understand why would the docker container decide to run different on those systems! But anyway, hope this helps someone.