-
Notifications
You must be signed in to change notification settings - Fork 616
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fds 6.7.8 crashes with fds_local on windows 64 for an immersed boundary case #10668
Comments
Thank you Bjarne we'll have a look. |
I'll test it on my computer. |
This appears to be a problem with the
For the moment, use this command instead of |
using the -c option, the command if I run the above line after removing -env I_MPI_FABRICS=shm , it works. kevin, do we need the I_MPI_FABRICS entry? |
also, if I run using the following (which is what fds_local generates) Job ID string : Example_5 forrtl: severe (157): Program Exception - access violation |
Noted the same, yet the problem only shows up when invoking the mkl cluster solver. I'll test this in an isolated piece of code. Might need help with the windows compiling.On Jun 13, 2022 9:44 PM, gforney ***@***.***> wrote:
also, if I run using the following (which is what fds_local generates)
mpiexec -localonly -n 1 -env I_MPI_FABRICS=shm fds Example_5.fds
I get the same error
Job ID string : Example_5
forrtl: severe (157): Program Exception - access violation
Image PC Routine Line Source
impi.dll 00007FF8EF7E1711 Unknown Unknown Unknown
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were assigned.Message ID: ***@***.***>
|
Also I was concerned I did not include the correct Intel files in the bundle but I see the same problem when using fds I built (rather than fds from bunde) and mpiexec from the oneapi I installed. |
I don't think we need the I_MPI_FABRICS setting. The -localonly option indicates that the job is to run on one computer and I assume that the fabric is set appropriately. |
I will take it out when -localonly is used |
try you case with nightly bundle |
I tried the nightly build. FDS no longer crashes, but there seems to be a problem with the parameter -o C:\Users\bphu\Documents\summer_school_2022\Examples_Marcos>fds_local -o 2 Example_5.fds Starting FDS ... MPI Process 0 started on BYG-A201-BPHU Reading FDS input file ... Fire Dynamics Simulator Current Date : June 14, 2022 19:58:05 MPI Enabled; Number of MPI Processes: 1 MPI version: 3.1 Job TITLE : Test specified mass flux bc on sphere and mass conservation. Time Step: 1, Simulation Time: 0.002 s |
I'll take a look |
I have the same problem. The -o option does not give me the right number of OpenMP threads. |
The -o option is ignored, and whatever OMP_NUM_THREADS has been set is used. |
I had typo in the variable used to specify the number of openmp threads , bundle at link below should work now. let me know if you still see a problem. thanks for pointing out the problems |
Thanks. I have tested it, - also with different combinations with -p and -o and I did not find any problems, so the case can be closed |
When using fds_local -o 1 example_5.fds FDS crashes. Just using fds example_5.fds works.
The error message is given below and an example file is attached.
The problem only appears on a windows pc. The mac os or a linux system do not show the same problem.
Starting FDS ...
MPI Process 0 started on BYG-A201-BPHU
Reading FDS input file ...
Fire Dynamics Simulator
Current Date : June 10, 2022 11:06:08
Revision : FDS6.7.8-0-gfbf3e11ee-release
Revision Date : Tue May 24 18:07:45 2022 -0400
Compiler : Intel ifort 2021.5.0
Compilation Date : Wed 05/25/2022 11:40 AM
MPI Enabled; Number of MPI Processes: 1
OpenMP Disabled
MPI version: 3.1
MPI library version: Intel(R) MPI Library 2021.4 for Windows* OS
Job TITLE : Test specified mass flux bc on sphere and mass conservation.
Job ID string : Example_5
forrtl: severe (157): Program Exception - access violation
Image PC Routine Line Source
impi.dll 00007FFF178ACB65 Unknown Unknown Unknown
impi.dll 00007FFF178B3A43 Unknown Unknown Unknown
impi.dll 00007FFF17B06506 Unknown Unknown Unknown
Example_5.txt
The text was updated successfully, but these errors were encountered: