I’m currently working on launching a calculation that requires the coupling of code_saturne & Persalys(in Linux). I want to use the ‘Design of experiments’ feature so that I can launch a series of CFD calculations with different mesh parameters. Since I need to change some parameters of the mesh, I use a python scripts to generate a mesh automatically by SALOME for each run.
The issue is that when the shell commands include the SALOME command, e.g. (./salome -t generate_mesh.py), when i click ‘check model’, Persalys is unable to read the output, resulting in the software becoming unresponsive. Strangely, when I comment out this line, everything runs smoothly.
I believe that the environment parameters or something else using by Persalys may be altered due to my using SALOME, but I’m not sure how to fix that since I know very little about the software. Please let me know if you need any further information or if there are any suggestions you can provide.
PS: The version of Persalys is 12.0 and the version of SALOME is 9.6.0, the ‘code_saturne’ shell command is posted
Thanks for your reply. I’ve also thought about it, and then I attempted to isolate this command ( i.e. ’ /media/freddy/c5df8610-7837-463e-a21e-f276a63b0639/freddy/code_saturne/SALOME-9.6.0-UB20.04-SRC/salome -t wt_mesh.py ') by adding ‘bash (…) exit’ or by running it by calling another shell file. But unfortunately, it didn’t work.
I’m not sure if my solution is correct or if it’s the key to this issue. I would appreciate it if you have any more ideas about it.
it could probably be the PYTHONPATH/PYTHONHOME or PATH environment variables
that are inherited from the persalys environment that are overriding the ones in your script
you may want to overload them in your script
Thanks for your advice, in fact I’ve also renewed the env variables after calling SALOME but it doesn’t work. This issue’s eventually caused by not closing SALOME after calling it through tui and can be easily solved by simply adding ‘-w1’ after this command.