Changes needed for GFS Update 2017?
-
- Posts: 1539
- Joined: Wed Aug 19, 2009 10:05 am
Re: Changes needed for GFS Update 2017?
Maybe but not very probably. I would guess that your setup is too "risky". Did you take a detailed look into error logs? CFL violations or something like that?
Re: Changes needed for GFS Update 2017?
No I didn't see anything like that in log files.
Sometimes I've already seen runs that apparently crash because of GFS data but it's rare and even rarer two following
Sometimes I've already seen runs that apparently crash because of GFS data but it's rare and even rarer two following
Re: Changes needed for GFS Update 2017?
Hello
I found on this topic the following link http://gamma.meteoadriatic.net/test/uems_install.pl.gz
to download the installer for new version of UEMS but gives this error:
I confirm that wget and curl are installed .
I'm using DEBIAN 9.
Have you suggestions?
Thanks in advance
I found on this topic the following link http://gamma.meteoadriatic.net/test/uems_install.pl.gz
to download the installer for new version of UEMS but gives this error:
Code: Select all
rox-desktop:~/uems_install.pl> uems_install.pl --install 15.99.5
Can't exec "lscpu": File o directory non esistente at uems_install.pl line 3140.
Can't exec "whereis": File o directory non esistente at uems_install.pl line 5164.
Use of uninitialized value $util in scalar chomp at uems_install.pl line 5164.
Use of uninitialized value $util in -s at uems_install.pl line 5165.
Can't exec "whereis": File o directory non esistente at uems_install.pl line 5164.
Use of uninitialized value $util in scalar chomp at uems_install.pl line 5164.
Use of uninitialized value $util in -s at uems_install.pl line 5165.
Greetings irrefutably intelligent and devastatingly good-looking UEMS user!
Welcome to the NWS SOO Science and Training Resource Center (SOO/STRC) Unified
Environmental Modeling System (UEMS) installation and update routine.
Phew! That's more than a mouthful.
* Checking http connection to ems2.comet.ucar.edu - It's Alive!
* Connecting to ems2.comet.ucar.edu -sh: wget: comando non trovato
Failed
sh: wget: comando non trovato
! There was a problem retrieving information from ems2.comet.ucar.edu
Our relationship is off to a rocky start. I need some jewelry!
I'm using DEBIAN 9.
Have you suggestions?
Thanks in advance
Re: Changes needed for GFS Update 2017?
Hi
the previous problem is solved after log out and re-log on terminal but when I try to run domain wizard appears the following error:
and this is the dwiz.log
Probably the error is caused by mpich2 but I've installed UEMS using the command : ./uems_install.pl --install and the program has downloaded the correct binaries.
For more info this my sysinfo log
I tested uems 5 month ago on the same machine under Linux-Mint 17 and it worked correctly and now under Debian 9 gives these problems.
Thanks in advance for any suggestion.
Rodi
the previous problem is solved after log out and re-log on terminal but when I try to run domain wizard appears the following error:
Code: Select all
/usr1/uems/runs/arw1/static/geogrid.log is Not Found;
***CANNOT continue request***
Attempt number 1 to find and read geogrid.log
/usr1/uems/runs/arw1/static/geogrid.log is Not Found;
***CANNOT continue request***
Attempt number 2 to find and read geogrid.log
/usr1/uems/runs/arw1/static/geogrid.log is Not Found;
***CANNOT continue request***
Attempt number 3 to find and read geogrid.log
After three attempts to find geogrid.log ...now giving up.
- - - - - - - List of Output - - - - - - -
List of geogrid.exe files found
No geo_* files were found.
Code: Select all
INFO: Mac or Linux computer detected. Setting Mac/Linux fonts
INFO: JVM memory=630128640
INFO: WRF Domain Wizard version 2.82
Attempting to run ems_domain.pl...
path to ems_domain.pl: /usr1/uems/strc/ems_domain.pl
--dwiz --rundir /usr1/uems/runs --update arw1 --core arw
Running ems_domain.pl....
Starting UEMS Program ems_domain.pl (V15.99.5) on rox-desktop at Tue Aug 1 13:30:51 2017 UTC
! EMS Inspirational Message #601 - Help Me, Help You
What, exactly, do you expect to achieve by passing such jibberish ("update")?
"It is better to keep your mouth closed and let people think you are a fool than
to open it and remove all doubt."
- Mark Twain
ems_domain.pl exit code is: 1
Local
INFO: ( $EMS_UTIL/mpich2/bin/mpiexec.gf -n $OMP_NUM_THREADS /usr1/uems/bin/geogrid >& /usr1/uems/runs/arw1/static/geogrid.log ; echo $? > /usr1/uems/runs/arw1/static/geogrid.log.exitCode) &
Local
Local
For more info this my sysinfo log
Code: Select all
rox-desktop:/usr1/uems/strc/EMSbin> ./sysinfo
! Processors hath gone missing!
It appears that either NCPUS (0) or CORES (0) is undefined in the
EMS.profile file. Rather than stopping this train and pestering you do
actually do somthing about it, I am continuing with the following values:
1 PHYSICAL CPUs - Those that you would see if you opened up the computer
case
4 CORES per CPU - Just that and not the total number of available
processors
If you don't like it then edit the EMS.conf file.
It's your job. Don't make me print this message again.
Starting UEMS Program sysinfo (V15.99.5) on rox-desktop at Tue Aug 1 13:40:37 2017 UTC
* Gathering information for localhost rox-desktop
------------------------------------------------------------------
System Information for rox-desktop
System Date : Tue Aug 1 13:40:38 2017 UTC
System Hostname : rox-desktop
System Address : 127.0.1.1
System OS : Linux
OS Kernel : 4.9.0-3-amd64
Kernel Type : x86_64
Linux Distribution : Debian GNU/Linux 9.1 (stretch)
Network Interface Information for rox-desktop
Network Interface : sh
Interface Address : None Assigned
Address Resolves to : Nothing
Interface State : Inactive
Processor and Memory Information for rox-desktop
CPU Name : Intel(R) Core(TM) i7-4770 CPU @ 3.40GHz
CPU Instructions : haswell
CPU Type : 64-bit
CPU Speed : 3699.24 MHz
EMS Determined Processor Count
Physical CPUs : 1
Cores per CPU : 4
Total Processors : 4
EMS.cshrc Specified Processor Count
Physical CPUs : 1
Cores per CPU : 4
Total Processors : 4
Hyper-Threading : Off
System Memory : 15.5 Gbytes
EMS User Information for rox on rox-desktop
User ID : 1000
Group ID : 1000
Home Directory : /home/rox
Home Directory Mount : Local
User Shell : /bin/bash
Shell Installed : Yes
Shell Login Files :
EMS.cshrc Sourced :
EMS.cshrc Port Range : None Defined
EMS Installation Information for rox-desktop
EMS Release : 15.99.5,WRF3.7.1
EMS Home Directory : /usr1/uems
EMS Home Mount : Local
EMS User ID : 1000
EMS Group ID : 1000
EMS Binaries : x64
EMS Run Directory : /usr1/uems/runs
EMS Run Dir Mount : Local
EMS Run Dir User ID : 1000
EMS Run Dir Group ID : 1000
Run Dir Avail Space : 690.54 Gb
Run Dir Space Used : 16%
EMS Util Directory : /usr1/uems/util
Your awesome EMS sysinfo party is complete - Tue Aug 1 13:40:38 2017 UTC
As Shields and Yarnell loved to gesticulate: "Think Globally, Model Locally!"
Thanks in advance for any suggestion.
Rodi
Re: Changes needed for GFS Update 2017?
I have the same error but it's not a problem for me to create domain after in command line, put namelist.wps and localize it
Re: Changes needed for GFS Update 2017?
Hi meteo60
I've the same error under wrfems 3.4, I tried your suggestion and the problem is solved but under UEMS the problem persist.
When I lanch ems_domain.pl appears this error:

Rodi
I've the same error under wrfems 3.4, I tried your suggestion and the problem is solved but under UEMS the problem persist.
When I lanch ems_domain.pl appears this error:
Code: Select all
rox-desktop:/usr1/uems/strc> ems_domain.pl --localize arw1
Starting UEMS Program ems_domain.pl (V15.99.5) on rox-desktop at Wed Aug 2 08:23:40 2017 UTC
* Localizing "arw1" domain - /usr1/uems/runs/arw1
Here is some information about your domain:
Primary Domain
Projection : lambert
Standard Longitude : 9.714 Degrees
True Latitude 1 : 45.249 Degrees
True Latitude 2 : 45.249 Degrees
Reference Latitude : 45.249 Degrees
Reference Longitude : 9.714 Degrees
Grid NX x NY : 100 x 87
Grid Spacing : 6.00 Kilometers
Geog Dset Res : 2m
* Burn'n up 2 processors to localize your domain. Please ignore the smoke - Success
Localization Complete - Model Strong!
* Domain "arw1" appears to be in need of some refreshment (My work is never done!):
Refreshing files in arw1/conf/ems_auto (configuration retained):
MISSING : Configuration file - ems_autopost.conf
MISSING : Configuration file - ems_autorun.conf
Refreshing files in arw1/conf/ems_run (configuration retained):
MISSING : Configuration file - run_afwaout.conf
MISSING : Configuration file - run_auxhist1.conf
MISSING : Configuration file - run_dfi.conf
MISSING : Configuration file - run_dynamics.conf
MISSING : Configuration file - run_levels.conf
MISSING : Configuration file - run_lightning.conf
MISSING : Configuration file - run_namelist.conf
MISSING : Configuration file - run_ncpus.conf
MISSING : Configuration file - run_nests.conf
MISSING : Configuration file - run_noahmp.conf
MISSING : Configuration file - run_nudging.conf
MISSING : Configuration file - run_physics.conf
MISSING : Configuration file - run_real.conf
MISSING : Configuration file - run_restart.conf
MISSING : Configuration file - run_sealakes.conf
MISSING : Configuration file - run_timestep.conf
MISSING : Configuration file - run_wrfout.conf
Refreshing files in arw1/conf/ems_post (configuration retained):
MISSING : Configuration file - post_bufr.conf
MISSING : Configuration file - post_export.conf
MISSING : Configuration file - post_gempak.conf
MISSING : Configuration file - post_grads.conf
MISSING : Configuration file - post_grib.conf
MISSING : Configuration file - post_uems.conf
Refreshing EMSUPP control files in arw1/static (configuration saved):
Checking paths in arw1/static/namelist.wps
EMS Program ems_domain completed at Wed Aug 2 08:23:50 2017 UTC
Toista perässäni: "Think Globally, Model Locally!"

Rodi
Re: Changes needed for GFS Update 2017?
meteoadriatic wrote: ↑Wed Jul 26, 2017 7:01 amThis works for my NMM just fine. I wrote paths for tables and ungrib should go instead that one you have in bin directory.dominic wrote: ↑Tue Jul 25, 2017 10:23 pmHi ivan, this is needed to activate nmm? If so, where should these files be placed?meteoadriatic wrote: ↑Thu Jul 20, 2017 4:54 pmOK, here are the changes for NMM
http://gamma.meteoadriatic.net/tmp/NMM/
This ungrib is from WPS 3.9 with patch for new GFS, compiled statically so it should work with any system. Also, that one from Robert's update should work also in NMM but didn't tested it myself. Vtable.GFS should be placed in data/tables/vtable and METGRID.TBL.NMM in data/tables/wps
That should be all you need to change. Let me know if it works.
Ivan
Hi ivan
I've put the files on your ftp. The problem arises when I go to localize the domain, and I get the following error:
ERROR: Could not open GEOGRID.TBL
ERROR: Could not open GEOGRID.TBL
ERROR: ERROR: Could not open GEOGRID.TBL
ERROR: Could not open GEOGRID.TBL
ERROR: Could not open GEOGRID.TBL
Could not open GEOGRID.TBL
application called MPI_Abort(MPI_COMM_WORLD, 127) - process 0
application called MPI_Abort(MPI_COMM_WORLD, 127) - process 4
application called MPI_Abort(MPI_COMM_WORLD, 127) - process 1
application called MPI_Abort(MPI_COMM_WORLD, 127) - process 2
application called MPI_Abort(MPI_COMM_WORLD, 127) - process 3
application called MPI_Abort(MPI_COMM_WORLD, 127) - process 5
Re: Changes needed for GFS Update 2017?
Delete uems folder
recreate domain: ems_domain.pl --newdom xxxx
Send namelist.wps in static folder
Localize: ems_domain.pl --localize xxxx
It should be ok
recreate domain: ems_domain.pl --newdom xxxx
Send namelist.wps in static folder
Localize: ems_domain.pl --localize xxxx
It should be ok
Re: Changes needed for GFS Update 2017?
The problem of segfault occurred on the run of 2017080206Z and I have nothing in the logs however I have this in syslog:
any idea?
Code: Select all
segfault at fffffffe0708c084 ip 0000000003759488 sp 00007ffed269d750 error 5 in wrfm_arw.exe[400000+3f78000]
segfault at fffffffe0708c084 ip 0000000003759488 sp 00007fff736935e0 error 5 in wrfm_arw.exe[400000+3f78000]
segfault at fffffffe0708c084 ip 0000000003759488 sp 00007ffc20722a10 error 5 in wrfm_arw.exe[400000+3f78000]
Re: Changes needed for GFS Update 2017?
Ok so I am bad, the segfault error was caused by the conf/ems_run/run_real.conf file because I had returned an old version in which USE_MAXW_LEVEL and USE_TROP_LEVEL were at T whereas in the latest version 15.99.5 they must Be to F ... F as f*%$*
Be careful
But what can be the effect of this parameter on F on model performance??
Be careful

But what can be the effect of this parameter on F on model performance??
Who is online
Users browsing this forum: No registered users and 1 guest