I was able to get WRFEMS to run successful if I only run a single non-nested domain, but when I add the a nested domain there seems to be a time issue. Have you seen this before, and if so what is the solution?
! Possible problem as system return code was 9
! Your WRF simulation (PID 26027) returned a exit status of 9, which i s never good.
System Signal Code (SN) : 9 (Kill signal)
! While perusing the log/run_wrfm.log file I determined the following:
It appears that your run failed because it exceeded either a CPU or wall
clock time limit. Time is such a precious resource. Use it wisely and
! Here are the last few lines from the run_wrfm.log file:
starting wrf task 4 of 23
starting wrf task 8 of 23
starting wrf task 15 of 23
starting wrf task 18 of 23
starting wrf task 19 of 23
starting wrf task 21 of 23
starting wrf task 2 of 23
starting wrf task 3 of 23
= BAD TERMINATION OF ONE OF YOUR APPLICATION PROCESSES
= EXIT CODE: 9
= CLEANING UP REMAINING PROCESSES
= YOU CAN IGNORE THE BELOW CLEANUP MESSAGES
YOUR APPLICATION TERMINATED WITH THE EXIT STRING: Killed (signal 9)
This typically refers to a problem with your application.
Please see the FAQ page for debugging suggestions
* System information is available in static/ems_system.info
! Here's a little help from your friend at EMS world headquarters:
The log files from your premature termination have been neatly bundl ed in log/2014052917.wrfm_crash_logs.tgz
Feel free to send them to a person who cares should you need some
assistance in troubleshooting this problem.
* All available wrfout files have been moved to the wrfprd directory
Your EMS party was busted at Thu May 29 17:36:33 2014 UTC - Ya know, 'cause stuff just happens
As the alchemists at Cambridge are fond of stating: "Think Globally, Model Loc
All issues/questions about EMS v3.4 package, please ask here.
1 post • Page 1 of 1
Who is online
Users browsing this forum: No registered users and 1 guest