Scheduled Downtime
On Friday 21 April 2023 @ 5pm MT, this website will be down for maintenance and expected to return online the morning of 24 April 2023 at the latest

Atmosphere model simply stops, without error message

Hello.

I am running test simulations using distinct microphysics and convection schemes, to see which configuration works best for my region. I am literally using every possible combination for the microphysics and convection schemes (while maintaining the mesoscale suite option) and for most of the configurations tested, the simulations were successful, except for three specific cases: 1) microp. off and ntiedtke for cu. scheme, 2) microp. off and kain fritsch for cu. scheme, 3) mp kessler for microp. and kain fritsch for cu. scheme. The simulations are using the same namelist and streams files, the only modification was, obviously, in the parameter for choosing the microp. and cu. schemes and I am running the simulations using 50 cores.

For each oe of those simulations I had a different issue:

For the first one (microp. off and ntiedtke for cu. scheme), I was receiving the following screen error:

Code:
===================================================================================
=   BAD TERMINATION OF ONE OF YOUR APPLICATION PROCESSES
=   PID 47552 RUNNING AT nemo
=   EXIT CODE: 136
=   CLEANING UP REMAINING PROCESSES
=   YOU CAN IGNORE THE BELOW CLEANUP MESSAGES
===================================================================================
YOUR APPLICATION TERMINATED WITH THE EXIT STRING: Floating point exception (signal 8)
This typically refers to a problem with your application.
Please see the FAQ page for debugging suggestions
application called MPI_Abort(MPI_COMM_WORLD, 1416939706) - process 0


Then, when I attempted using 52 cores instead of 50, the simulation worked.

For the other two simulations, I did not receive any error message and the model actually was able to start the simulation, but after going through the first time step it simply stopped, without any error being displayed on the screen. I did try to run the simulations with 52 and 54 cores, but got the same result.

I hope that I was able to clearly state my problem. If anyone have any ideas of what is happening here and/or any possible solution that would be very handy.

Thank you!
 
Top