Changes needed for GFS Update 2017?

Questions and other topics related to UEMS 15.
meteo60
Posts: 104
Joined: Tue Apr 17, 2012 4:50 pm

Re: Changes needed for GFS Update 2017?

Post by meteo60 » Thu Jul 20, 2017 9:52 pm

I updated to 15.99.2 because with previous version I had some problems on coastline for temperature and RH due to new GFS. Now every runs are crashing; this is the log's content.
Same problem than "Delinend"
Unless you have something better to do with your time


! Possible problem as system return code was 11

! Your WRF simulation (PID 110458) returned a exit status of 11, which is never good.

System Signal Code (SN) : 11 (Invalid Memory Reference - Seg Fault)

! While perusing the log/run_wrfm.log file I determined the following:

It appears that your run failed due to a Segmentation Fault on your
system. This failure is typically caused when the EMS attempt to access a
region of memory that has not been allocated. Most often, segmentation
faults are due to an array bounds error or accessing memory though a NULL
pointer. Either way, this is an issue that needs to be corrected by the
developer.

So, if you want this problem fixed send your log files along with the
namelist.wrfm and namelist.wps files to xxxxx@noaa.gov, just
because he cares.


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

starting wrf task 1 of 2
starting wrf task 0 of 2

===================================================================================
= BAD TERMINATION OF ONE OF YOUR APPLICATION PROCESSES
= PID 110462 RUNNING AT sd-123831
= EXIT CODE: 11
= CLEANING UP REMAINING PROCESSES
= YOU CAN IGNORE THE BELOW CLEANUP MESSAGES
===================================================================================
YOUR APPLICATION TERMINATED WITH THE EXIT STRING: Segmentation fault (signal 11)
This typically refers to a problem with your application.
Please see the FAQ page for debugging suggestions
Last edited by meteo60 on Fri Jul 21, 2017 10:36 am, edited 1 time in total.

meteoadriatic
Posts: 1567
Joined: Wed Aug 19, 2009 10:05 am

Re: Changes needed for GFS Update 2017?

Post by meteoadriatic » Fri Jul 21, 2017 2:39 am

This must be something directly related to EMS because outside of EMS I do not have any problems. My ARW and NMM runs work fine (http://meteoadriatic.net/racunalna-vremenska-prognoza).

delinend
Posts: 65
Joined: Wed Oct 28, 2009 7:07 pm

Re: Changes needed for GFS Update 2017?

Post by delinend » Fri Jul 21, 2017 3:54 am

Here by me, there is a 50/50 chance of fine-run or crash.
Here a temp Fix from Robert:

All,
There appears to be a problem with the tropopause and/or max wind level data in the new
GFS GRIB files causing a segmentation fault while running in a simulation.
For now, set in conf/ems_run/run_real.conf

USE_MAXW_LEVEL = F
and
USE_TROP_LEVEL = F


I'll look into the problem more tomorrow.
Robert

meteoadriatic
Posts: 1567
Joined: Wed Aug 19, 2009 10:05 am

Re: Changes needed for GFS Update 2017?

Post by meteoadriatic » Fri Jul 21, 2017 5:00 am

Oh, I see. I didn't used those namelist variables in my runs and defaults are =0. Maybe it is WRF thing then...

meteo60
Posts: 104
Joined: Tue Apr 17, 2012 4:50 pm

Re: Changes needed for GFS Update 2017?

Post by meteo60 » Fri Jul 21, 2017 11:09 am

This temp fix seems to be OK. Wait for definitely patch...
delinend wrote:
Fri Jul 21, 2017 3:54 am
Here by me, there is a 50/50 chance of fine-run or crash.
Here a temp Fix from Robert:

All,
There appears to be a problem with the tropopause and/or max wind level data in the new
GFS GRIB files causing a segmentation fault while running in a simulation.
For now, set in conf/ems_run/run_real.conf

USE_MAXW_LEVEL = F
and
USE_TROP_LEVEL = F


I'll look into the problem more tomorrow.
Robert

meteo60
Posts: 104
Joined: Tue Apr 17, 2012 4:50 pm

Re: Changes needed for GFS Update 2017?

Post by meteo60 » Fri Jul 21, 2017 6:27 pm

There is a new update on uems server: 15.99.5 http://ems3.comet.ucar.edu/uems/releases/
Has anyone tested it?

apextreme
Posts: 30
Joined: Mon Apr 05, 2010 7:29 pm

Re: Changes needed for GFS Update 2017?

Post by apextreme » Sat Jul 22, 2017 2:18 am

Hello everyone.
Robert send me a ems_install.pl utility (15.99.5) and he say me:

uems_install.pl --update

but that utility give me error:

Global symbol "$dh" requires explicit package name (did you forget to declare "my $dh"?) at ./uems_install.pl line 2610.
Global symbol "$dh" requires explicit package name (did you forget to declare "my $dh"?) at ./uems_install.pl line 2610.
Global symbol "$dh" requires explicit package name (did you forget to declare "my $dh"?) at ./uems_install.pl line 2610.
BEGIN not safe after errors--compilation aborted at ./uems_install.pl line 2705.

What is the error?
Help Please!

norulz
Posts: 92
Joined: Thu Mar 12, 2015 1:43 pm

Re: Changes needed for GFS Update 2017?

Post by norulz » Sat Jul 22, 2017 8:28 am

There is a new update on uems server: 15.99.5 http://ems3.comet.ucar.edu/uems/releases/
Has anyone tested it?
I have tried it and it finally appears to be working OK.
I performed both updates (15.99.2 & 15.99.5) at the same time using the install utility dated 18 July 2017.

There were problems with the run_conf files that all had a .notused extension added. After I removed this extension, the ems_domain --refresh updated the files while keeping the original configuration. If the .notused extension is not removed the domain --refresh or --localize creates a new set of run_conf files without previous configuration.

After update I did experience a number of unexplained run failures but with no log files kept - only the usual email message. Each of these failures started up OK on a retrial. I have no idea what happened.

meteo60
Posts: 104
Joined: Tue Apr 17, 2012 4:50 pm

Re: Changes needed for GFS Update 2017?

Post by meteo60 » Sat Jul 22, 2017 8:51 am

I confirm that you said norulz.
But after an update I have not failures, only the first run which is longer

meteoadriatic
Posts: 1567
Joined: Wed Aug 19, 2009 10:05 am

Re: Changes needed for GFS Update 2017?

Post by meteoadriatic » Sat Jul 22, 2017 11:12 am

Does this update fixes SE_MAXW_LEVEL and USE_TROP_LEVEL problem?

Post Reply