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

init_atmopshere stops

This post was from a previous version of the WRF&MPAS-A Support Forum. New replies have been disabled and if you have follow up questions related to this post, then please start a new thread from the forum home page.


While running the inital_atmosphere model executable, the program runs fine for nearly 18mintues and then simply stops and no error messages are made. My submission script allows for it to run up to 10hours so time should not be an issue. I have retried several times and it stops at the same spot each time. Do you have any recommendations for how/where to start troubleshooting?


  • Screen Shot 2020-03-10 at 9.45.39 AM.png
    Screen Shot 2020-03-10 at 9.45.39 AM.png
    525.2 KB · Views: 1,356
It looks like your screenshot is from an execution of the atmosphere_model program (i.e., the model itself) rather than the init_atmosphere_model program. The log output indicates that NaNs were present in the model velocity fields, which is likely the reason why the model eventually failed. Can you attach your namelist.atmosphere file? On which mesh are you running your simulation?
Since the last post, I have been attempting to troubleshoot this problem. I have finally even gone to the extreme of rebuilding the entire model and rerunning the same steps. Unfortunately, I am getting the same issue, but without the wind error you mentioned in the previous comment. It simply stops a few moments into running the init step and does not produce and error file. Knowing that this may be an issue, I capture each step via screenshots and TextEdit files and have attached them to this message. There were no errors present after creating the file. If you have any suggestions, I would be very grateful.


  • pwd.png
    482.5 KB · Views: 1,342


  • 0.build_atmo.png
    675.3 KB · Views: 1,340
  • 0.build_init.png
    556.8 KB · Views: 1,340
  • 1.ENSO.mesh.png
    369.8 KB · Views: 1,341
  • 2.static_log.png
    481.5 KB · Views: 1,341
  • 2.static_test.png
    741.4 KB · Views: 1,340
  • 2.static_test2.png
    837.1 KB · Views: 1,341
  • 2.static_name.rtf
    1.5 KB · Views: 59
  • 2.static_streams.rtf
    1.3 KB · Views: 59
  • 3.init_log.rtf
    7.4 KB · Views: 62
  • 3.init_name.rtf
    1.5 KB · Views: 60
The email for the failed batch script:

PBS Job Id:
Job Name: init_1
Execution terminated
This could be an issue of memory usage. Could you try running the job to create the initial conditions on four nodes of Cheyenne?
For a bit more information on memory usage, we've generally found that providing about 0.175 MB of memory per grid column (with 55 vertical layers) is adequate when running the model itself (i.e., the atmosphere_model program). The initialization program requires less memory because it allocates fewer fields; I don't have a good figure, but just guessing wildly, it may be that the init_atmosphere_model program requires only half the memory of the model. For a mesh with 535554 columns, then, you might want to ensure that you have at least 535554 * 0.175 MB = 93.7 GB of aggregate memory when running a model simulation, and the initialization of the model might require around 46 GB. Although most of the Cheyenne batch nodes have 64 GB of memory, not all of this is available to user processes. So, using at least a couple of nodes when creating the initial conditions, and using more nodes still when running the model is probably good.