SIMULATION ERROR MPI

[carlop...@gmail.com]

Good morning,

I have a problem with a new PC purchased for simulations.
I have a workstation, in which I installed FDS and on which two computers have access it gives me this error when I try to do simulations with more than 7 meshes. I don't understand if it is an error from FDS or from pyrosim (which I have already requested assistance from).

Do you kindly know how I could solve it?
I thank you in advance as always for the availability

Regards
Carlo

MESSAGE ERROR

ENV:  {PATH=C:\Program Files\PyroSim 2023\fds;C:\Program Files\PyroSim 2023\fds\mpi;C:\Windows;C:\Windows\system32, OMP_STACKSIZE=16M, OMP_NUM_THREADS=1, I_MPI_WAIT_MODE=1}

CMD:  "C:\Program Files\PyroSim 2023\fds\runfds.exe" mpiexec.exe -localonly -n 8 fds.exe untitled.fds

WDIR: C:\Users\xxxx\Desktop\Nuova cartella\untitled

[mpiexec @ NamePC] wmain (mpiexec.c:2165): assert (pg->intel.exitcodes != NULL) failed

[runfds.exe] subprocess exit: -1

[ mpiexec @ NamePC  ] HYD_sock_write (..\windows\src\hydra_sock.c:387): write error (errno = 34)

[dr_jfloyd]

Not sure why Google deleted my response but one thing to try is running your 8 mesh case on just one process. If it doesn't start timestepping on one process, then there may be some input file error when you went to 8 meshes.

[carlop...@gmail.com]

Thank you Dr. Floyd,
google also deletes my posts...today is an error day :)

The problem occurs on any file, even in an "empty" simulation where only meshes are present.

Files with a single process start correctly and I see the time step. FDS correctly simulates up to 7 meshes both with a single process and with MPI.
When I simulate with a single process more than 8 meshes it works.

When I simulate with a multiple process more than 8 mesh it does not work.

I do not understand what the problem could be...

[dr_jfloyd]

Can you open an issue and attach the empty simulation that fails?

[carlop...@gmail.com]

yeah sure, maybe in the next few days if I can't solve it myself I'll open an issue on gifthub (that's where I should open the issue right?).

In any case I think even attaching the "empty" file doesn't change the situation much. Simulating on other PCs everything works, I think it's a SETUP problem of the workstation I'm using. I thought this was a problem that has happened before and maybe someone could give me some guidance on this.