Timeout running uems

Questions and other topics related to UEMS 15.
Post Reply
lpajurek
Posts: 1
Joined: Tue Dec 01, 2015 8:30 am

Timeout running uems

Post by lpajurek » Tue Dec 01, 2015 8:39 am

Hello!

I have some issue with running uems, looks like I have timeout while trying to create WRF initial and boundary condition files.
Does anyone remember, where I could find .conf file, to change the maxtime variable?
In the wrfems it was located somewhere in $EMS_STRC/ems_prep/Prep_metgrid.pm, but now, there is nothing like that.

I'm posting error display:


lpajurek@storm:/home/uems/runs/polska_0.5$ ems_run --nodes local:22 --length 12h

Starting UEMS Program ems_run (V15.47.3) on storm at Mon Nov 30 14:18:14 2015 UTC


I. Preparing your EMS Run experience


* You are running the WRF ARW core. Hey Ho! Let's go! -

* Simulation start and end times:

Domain Start End

1 2015-11-30_06:00:00 2015-11-30_18:00:00

* Simulation length will be 12 hours

* A large timestep of 2.5 seconds will be used for this


II. Creating the initial and boundary condition files for th


* The WRF REAL program shall be run on the following sy

22 processors on storm (1 tile per processor)

* Creating WRF initial and boundary condition files - Failed (9)

System Signal Code (SN) : 9 (Kill signal)


! UGH! Creation of model initial and boundary conditions failed!

I hate when this #%^!#!!% happens. Hopefully nobody lost an eye!

! While perusing the log/run_real.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
often.



! Here are the last few lines from the run_real.log file:

starting wrf task 13 of 22
starting wrf task 14 of 22
starting wrf task 15 of 22
starting wrf task 16 of 22
starting wrf task 17 of 22
starting wrf task 18 of 22
starting wrf task 0 of 22

===================================================== ==============================
= BAD TERMINATION OF ONE OF YOUR APPLICATION PROCESSES
= PID 19426 RUNNING AT storm
= EXIT CODE: 9
= CLEANING UP REMAINING PROCESSES
= YOU CAN IGNORE THE BELOW CLEANUP MESSAGES
===================================================== ==============================
YOUR APPLICATION TERMINATED WITH THE EXIT STRING: Kill led (signal 9)
This typically refers to a problem with your application.
Please see the FAQ page for debugging suggestions


Argument "użyte" isn't numeric in multiplication (*) at /home/uems/strc/EMSbin/emsinfo line 152.

* 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 bundled in log/2015113014.real_crash_logs.tgz

Feel free to send them to a person who cares should you need some
assistance in troubleshooting this problem.



Your EMS party was busted at Mon Nov 30 14:22:06 2015 UTC - Ya know, 'cause stuff just happens

You can sometimes hear Tibetan Monks chant: "Think Globally, Model Locally!"

Post Reply

Who is online

Users browsing this forum: No registered users and 3 guests