After running a lot of simple FSI test cases on my pc, I have to run a very large simulation on a server.
I’ve already installed the two solvers (SU2 and MBDyn) along with preCICE, the adapters and the necessary dependencies. I tested SU2 and MBDyn separately and both work properly, but when I couple them I got a very cryptic error. In order to understand if the error is on MBDyn part or on SU2, I run a MBDyn-dummy test case and here the error is the same.
I’m attaching the error here:
I’m not very comfortable at reading segmentation fault errors, so I do not understand what error comes first.
In order to run the case on the server, I have to use slurm, so I use 2 separate run.sh file: I run one in the Fluid folder and one in the structure folder.
Have anyone of you any experience with servers? Could it be an error related to the way in which I have to send the jobs? Do I need to run both commands from one single run.sh?
I’ve got zero experience with servers, so any help would be greatly appreciated.
Yes I tested preCICE with make test and I also run the quickstart using SU2 instead of OpenFOAM as fluid. Everything works perfectly.
So I think it’s safe to conclude that the problem is either in the python-bindings or in MBDyn…
I would try reinstalling the Python bindings. If the dummy solvers still show the same error, it could be worth to install preCICE and the Python bindings with debugging flags to get better error messages and additional checks.
Yes I managed to solve this issue. At the end, I re-installed Python with OpenSSL and then I used pip to install all the required packages. In this manner, I installed pyprecice directly with pip install.