forrtl: severe (157): Program Exception - access violation question #14345
Replies: 4 comments 8 replies
-
|
Your case is 8 million grid cells. Do you have enough RAM available to run this? This will need probably at least 16 Gb of available RAM if not more. |
Beta Was this translation helpful? Give feedback.
-
|
I have enough capacity, and even when I reduce the grid size to 1 million, the same message still appears. How can I solve this issue? |
Beta Was this translation helpful? Give feedback.
-
|
Simplify. Step 1. Can you run any fds case? Try running one of the examples. Once you can do these two things, then let's see about the more complicated case. |
Beta Was this translation helpful? Give feedback.
-
|
I can run simple models, but complex ones fail to run. |
Beta Was this translation helpful? Give feedback.
-
|
Find the boundary. You are jumping from simple to something that is too complex. I'm asking you to do what we would have to do, strip your model down to something that works. Then start adding back complexity until you find what fails. |
Beta Was this translation helpful? Give feedback.
-
|
I run your case with a 100^3 grid and latest source, and this is what I see: Starting FDS ... MPI Process 0 started on spark001 Reading FDS input file ... WARNING: SPEC REAC_FUEL is not in the table of pre-defined species. See the Users Guide chapter on species for the treatment of any undefined properties. ERROR(818): VENT Burner requires an orientation index, IOR. (MPI Process: 0, CHID: nktv) ERROR: FDS was improperly set-up - FDS stopped (CHID: nktv) |
Beta Was this translation helpful? Give feedback.
-
|
ERROR(818): VENT Burner requires an orientation index, IOR. (MPI Process: 0, CHID: nktv) |
Beta Was this translation helpful? Give feedback.
-
|
Even after modifying another version, the same issue still occurs. I've tried many solutions, but they all failed—it's quite frustrating. &HEAD CHID='ktv15'/ &MESH ID='Mesh08', IJK=200,200,56, XB=0.0,40.0,0.0,40.0,0.0,11.2/ &PART ID='ignitor particle', &REAC ID='Reaction', &DEVC ID='4F-T', QUANTITY='TEMPERATURE', XYZ=33.4,30.0,13.0/ &MATL ID='CONCRETE', &SURF ID='ignitor', &INIT ID='inginitor particle', PART_ID='ignitor particle', N_PARTICLES=1, XYZ=34.5,30.8,11.4/ &OBST ID='Obstruction', XB=0.0,39.0,0.0,33.6,0.0,0.2, SURF_ID='con'/ &VENT ID='Vent02', SURF_ID='Supply', XB=0.0,0.0,0.0,40.0,0.0,36.6, IOR=1/ &SLCF QUANTITY='TEMPERATURE', VECTOR=.TRUE., CELL_CENTERED=.TRUE., PBX=34.8/ &TAIL / |
Beta Was this translation helpful? Give feedback.
-
|
Could it be because my computer is running other files at the same time? Would that affect it? |
Beta Was this translation helpful? Give feedback.
-
|
It could be a lot of things. That is why I have repeated asked you to simplify things until it works (you claim you have cases that work). And then slowly start adding things back. Also, with long input files, please just append ".txt" to the end of the filename and attach the file. It get's very hard to follow the thread when you have thousands of lines of input to scroll through. |
Beta Was this translation helpful? Give feedback.
-
|
I suggest you start with very simple input files where you test your varoius inputs to make sure they are correct and that you understand how they work. You are making multiple errors. When I try to run your case with FDS 6.9.1 I get this error: ERROR(887): DEVC 4F-H1 must have an ORIENTATION. (CHID: ktv15) I simply made all the devices of that type have the same orientation. Then I get this error: ERROR(607): OBST Obstruction needs a BULK_DENSITY if it is to BURN_AWAY. (MPI Process: 1, CHID: ktv15) If set BULK_DENSITY everywhere to a value, then there is this error: ERROR(819): VENT null is OPEN, MIRROR OR PERIODIC and must be on an exterior boundary. (MPI Process: 4, CHID: ktv15) Looking at your inputs: &SURF ID='con', &SURF ID='calcium silicate', Why do you have BURN_AWAY=T for concrete and calcium silicate? You can attach an fds input file to a discussion by changing the file extension to .txt. This makes it much easier for others to be able to run your input as the file can be simply downloaded. Also it makes the discussion easier to follow as you can easily see the conversation without having to scroll through 100s of lines of input trying to find the next reply. Iif you do you do not have enough available RAM for everything your computer is trying to do then that will be a problem. BURN_AWAY can take a lot of resources as every OBST with BURN_AWAY has to be decomposed into single grid cell OBST so that wall cells can be available for the interiot of the OBST. Your MESH lines are very inefficient. The first mesh has 2.24 million grid cells and the next to last has 360,000. The time a process spends doing a timestep is proportionate to the number of grid cells. So your 360,000 cell mesh is going to spend 80+% of its time waiting for the 2.25 million cell mesh to finish. You could divide this domain into 8 equal meshes of 100x100x92 giving 920,000 cells in all meshes which is 40 % of 2.24 million cells. 920,000 cells in a single mesh is going to take a long time to initialize and run. |
Beta Was this translation helpful? Give feedback.
-
|
Thank you all for your replies! I will do my best to make the necessary modifications. |
Beta Was this translation helpful? Give feedback.
-
My simulation file fails to run successfully and always shows this message. I've tried modifying it many times, but nothing works. Can anyone help me? Please!
forrtl: severe (157): Program Exception - access violation
Image PC Routine Line Source
fds.exe 00007FF7E72C51D1 Unknown Unknown Unknown
fds.exe 00007FF7E72C63E7 Unknown Unknown Unknown
fds.exe 00007FF7E72C6FAA Unknown Unknown Unknown
fds.exe 00007FF7E72C7053 Unknown Unknown Unknown
fds.exe 00007FF7EE5A95BB Unknown Unknown Unknown
fds.exe 00007FF7EE5A0FDE Unknown Unknown Unknown
fds.exe 00007FF7EE6CECC9 Unknown Unknown Unknown
fds.exe 00007FF7EE6CC0F0 Unknown Unknown Unknown
fds.exe 00007FF7EDDFA0D4 Unknown Unknown Unknown
fds.exe 00007FF7EDDC77DB Unknown Unknown Unknown
fds.exe 00007FF7EE782250 Unknown Unknown Unknown
KERNEL32.DLL 00007FF9F812E8D7 Unknown Unknown Unknown
ntdll.dll 00007FF9F90BBF2C Unknown Unknown Unknown
Beta Was this translation helpful? Give feedback.
All reactions