Reanalysis based on ECMWF

Forum dedicated to older versions of EMS package (WRFEMS v3.2, v3.1 or older). Support is user-to-user based, so please help others if you can.
lcana
Posts: 58
Joined: Wed Nov 30, 2011 4:34 pm

Reanalysis based on ECMWF

Post by lcana » Tue Nov 20, 2012 3:47 pm

Dear all,

I've read some old post about doing reanalysis with ECMWF data. I've taken a look into my computer and ECMWF points towards local files:

SERVER-NFS = LOCAL:/home/ems/wrfems/data/ECMWF/YYYYMMDDHH.ecmwf.grb.bz2

Which should be the path to the full repository? I guess there is a server with the whole grib dataset from 1989 to 2008.

Thanks in advance,

Luis

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

Re: Reanalysis based on ECMWF

Post by meteoadriatic » Tue Nov 20, 2012 7:21 pm


lcana
Posts: 58
Joined: Wed Nov 30, 2011 4:34 pm

Re: Reanalysis based on ECMWF

Post by lcana » Wed Nov 21, 2012 4:55 pm

meteoadriatic wrote:Hello!

Try this:
http://soostrc.comet.ucar.edu/data/grib/ecmwf/
Thanks, Meteoadriatic! Yes, I've finally downloaded the data. Now I'm experiencing another problem: after downloaded, ems_prep fails when processing the data.

Dates are correct. Perhaps is related with the domain: using dwiz, I've designed one rectangular domain: Mercator, 9 km, centered on 24.0 N, -8.0 W and 250 x 150 x 45. However, ems_prep claims that some of the data are out of this domain -or there is a lack of data somewhere-

I'm trying to simulate a heavy saharian dust episode. Does anybody know the area covered by the ECMWF data?

Cheers, Luis

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

Re: Reanalysis based on ECMWF

Post by meteoadriatic » Wed Nov 21, 2012 7:31 pm

Can we see log files? Look into domain log directory and find a file (metgrid log) that states exact error...

lcana
Posts: 58
Joined: Wed Nov 30, 2011 4:34 pm

Re: Reanalysis based on ECMWF

Post by lcana » Thu Nov 22, 2012 10:31 am

meteoadriatic wrote:Can we see log files? Look into domain log directory and find a file (metgrid log) that states exact error...
Sure!

This is the output of the ems_prep command:
==================================
ems_prep --dset ecmwf --analysis --date 20040301 --cycle 00 --domain 1 --length 96

WRF EMS Program ems_prep (V3.1.1.5.1) started on f213 at Thu Nov 22 10:24:11 2012 UTC


The WRF EMS Says: "Who's Awesome? You're Awesome!"

I. WRF EMS ems_prep Model Initialization Summary

Initialization Start Time : Mon Mar 1 00:00:00 2004 UTC
Initialization End Time : Fri Mar 5 00:00:00 2004 UTC
Boundary Condition Frequency : 360 Minutes
Initialization Data Set : ecmwf
Boundary Condition Data Set : ecmwf
Static Surface Data Sets : None
Land Surface Data Sets : None
Included Sub-Domains:

Domain Parent Start Date

1 1


II. Search out requested files for WRF model initialization


* Locating ecmwf files for model initial and boundary conditions

* All requested ecmwf files are available for model initialization


Excellent! - Your master plan is working!


III. Create the WPS ARW intermediate format files

* Processing ecmwf files for use as model initial and boundary conditions - Schwing!!

ARW core intermediate file processing completed in 1 minute 45 seconds


IV. Horizontal interpolation of the intermediate files to the computational domain


EMS ERROR : In metgrid - This is not looking good!

* Missing values encountered in interpolated fields.

Check to make sure the areal coverage of your domain lies entirely
within the initialization data set.

See:

/home/ems/wrfems/runs/Dust/log/prep_metgrid.log

For more information.

! A little help from your friend

The log files from your failed run have been written to:

/home/ems/wrfems/runs/Dust/log/2012112210.metgrid_crash_logs.tgz

Feel free to send them to a person that cares if you need some assistance
troubleshooting this problem.


WRF EMS Program ems_prep failure (5) at Thu Nov 22 10:26:13 2012 UTC
====================================

And this is prep_metgrid.log

====================================

more prep_metgrid.log
WARNING: In METGRID.TBL, FLAG_SST is given as a flag more than once.
WARNING: In METGRID.TBL, FLAG_SM000010 is given as a flag more than once.
WARNING: In METGRID.TBL, FLAG_SM010040 is given as a flag more than once.
WARNING: In METGRID.TBL, FLAG_SM040100 is given as a flag more than once.
WARNING: In METGRID.TBL, FLAG_SM100200 is given as a flag more than once.
WARNING: In METGRID.TBL, FLAG_ST000010 is given as a flag more than once.
WARNING: In METGRID.TBL, FLAG_ST010040 is given as a flag more than once.
WARNING: In METGRID.TBL, FLAG_ST040100 is given as a flag more than once.
WARNING: In METGRID.TBL, FLAG_ST100200 is given as a flag more than once.
WARNING: In METGRID.TBL, FLAG_SOILM000 is given as a flag more than once.
WARNING: In METGRID.TBL, FLAG_SOILM005 is given as a flag more than once.
WARNING: In METGRID.TBL, FLAG_SOILM020 is given as a flag more than once.
WARNING: In METGRID.TBL, FLAG_SOILM040 is given as a flag more than once.
WARNING: In METGRID.TBL, FLAG_SOILM160 is given as a flag more than once.
WARNING: In METGRID.TBL, FLAG_SOILM300 is given as a flag more than once.
WARNING: In METGRID.TBL, FLAG_SOILT000 is given as a flag more than once.
WARNING: In METGRID.TBL, FLAG_SOILT005 is given as a flag more than once.
WARNING: In METGRID.TBL, FLAG_SOILT020 is given as a flag more than once.
WARNING: In METGRID.TBL, FLAG_SOILT040 is given as a flag more than once.
WARNING: In METGRID.TBL, FLAG_SOILT160 is given as a flag more than once.
WARNING: In METGRID.TBL, FLAG_SOILT300 is given as a flag more than once.
Processing domain 1 of 1
Processing 2004-03-01_00:00
/home/ems/wrfems/runs/Dust/wpsprd/ECMWF
INFORM: GHT at level 200100.000000 already exists; leaving it alone.
INFORM: PSFC at level 200100.000000 already exists; leaving it alone.
INFORM: LANDSEA at level 200100.000000 already exists; leaving it alone.
INFORM: RH at level 200100.000000 already exists; leaving it alone.
INFORM: Going to create the field ST
INFORM: Couldn't find ST000010 at level 200100.000000 to fill level 10.000000 of ST.
INFORM: Couldn't find ST010040 at level 200100.000000 to fill level 40.000000 of ST.
INFORM: Couldn't find ST040100 at level 200100.000000 to fill level 100.000000 of ST.
INFORM: Couldn't find ST100200 at level 200100.000000 to fill level 200.000000 of ST.
INFORM: Couldn't find ST000010 at level 200100.000000 to fill level 10.000000 of ST.
INFORM: Couldn't find ST010200 at level 200100.000000 to fill level 200.000000 of ST.
INFORM: Going to create the field SM
INFORM: Couldn't find SM000010 at level 200100.000000 to fill level 10.000000 of SM.
INFORM: Couldn't find SM010040 at level 200100.000000 to fill level 40.000000 of SM.
INFORM: Couldn't find SM040100 at level 200100.000000 to fill level 100.000000 of SM.
INFORM: Couldn't find SM100200 at level 200100.000000 to fill level 200.000000 of SM.
INFORM: Couldn't find SM000010 at level 200100.000000 to fill level 10.000000 of SM.
INFORM: Couldn't find SM010200 at level 200100.000000 to fill level 200.000000 of SM.
INFORM: Going to create the field SW
INFORM: Couldn't find SW000010 at level 200100.000000 to fill level 1.000000 of SW.
INFORM: Couldn't find SW010040 at level 200100.000000 to fill level 2.000000 of SW.
INFORM: Couldn't find SW040100 at level 200100.000000 to fill level 3.000000 of SW.
INFORM: Couldn't find SW100200 at level 200100.000000 to fill level 4.000000 of SW.
INFORM: Couldn't find SW000010 at level 200100.000000 to fill level 1.000000 of SW.
INFORM: Couldn't find SW010200 at level 200100.000000 to fill level 2.000000 of SW.
INFORM: Going to create the field SOIL_LAYERS
INFORM: Going to create the field SOILM
INFORM: Couldn't find SOILM000 at level 200100.000000 to fill level 0.000000 of SOILM.
INFORM: Couldn't find SOILM005 at level 200100.000000 to fill level 5.000000 of SOILM.
INFORM: Couldn't find SOILM020 at level 200100.000000 to fill level 20.000000 of SOILM.
INFORM: Couldn't find SOILM040 at level 200100.000000 to fill level 40.000000 of SOILM.
INFORM: Couldn't find SOILM160 at level 200100.000000 to fill level 160.000000 of SOILM.
INFORM: Couldn't find SOILM300 at level 200100.000000 to fill level 300.000000 of SOILM.
INFORM: Going to create the field SOILT
INFORM: Couldn't find SOILT000 at level 200100.000000 to fill level 0.000000 of SOILT.
INFORM: Couldn't find SOILT005 at level 200100.000000 to fill level 5.000000 of SOILT.
INFORM: Couldn't find SOILT020 at level 200100.000000 to fill level 20.000000 of SOILT.
INFORM: Couldn't find SOILT040 at level 200100.000000 to fill level 40.000000 of SOILT.
INFORM: Couldn't find SOILT160 at level 200100.000000 to fill level 160.000000 of SOILT.
INFORM: Couldn't find SOILT300 at level 200100.000000 to fill level 300.000000 of SOILT.
INFORM: Going to create the field SOIL_LEVELS
INFORM: Going to create the field PRES
INFORM: PRES at level 200100.000000 already exists; leaving it alone.
WARNING: Field PRES has missing values at level 200100 at (i,j)=(211,1)
WARNING: Field GHT has missing values at level 200100 at (i,j)=(211,1)
WARNING: Field PMSL has missing values at level 200100 at (i,j)=(211,1)
WARNING: Field PSFC has missing values at level 200100 at (i,j)=(211,1)
WARNING: Field SOILHGT has missing values at level 200100 at (i,j)=(211,1)
INFORM: Field SST.mask does not have a valid mask and will not be checked for missing values
INFORM: Field LANDSEA.mask does not have a valid mask and will not be checked for missing values
ERROR: Missing values encountered in interpolated fields. Stopping.

===================================

I'm going to try to build the files with a standard WRF-3.3.1. Let's see what happens.

Thanks again,
Luis

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

Re: Reanalysis based on ECMWF

Post by meteoadriatic » Thu Nov 22, 2012 10:54 pm

Hi,

try first to look at this topic from wrfforum:

http://forum.wrfforum.com/viewtopic.php?f=22&t=389

In short: I'm not sure but maybe some tables in wrfems v3.1 distribution are outdated. You can try to replace them with those from v3.2 version if they differ, or even from original WPS tarball.

I think those files you should check:
wrfems/data/tables/vtables/Vtable.ECMWF
wrfems/data/tables/vtables/Vtable.ECMWF_sigma
wrfems/data/tables/vtables/Vtable.ERA-interim.ml
wrfems/data/tables/vtables/Vtable.ERA-interim.pl
wrfems/data/tables/wps/METGRID.TBL.ARW (or NMM)

Not sure though if this will solve a problem.

lcana
Posts: 58
Joined: Wed Nov 30, 2011 4:34 pm

Re: Reanalysis based on ECMWF

Post by lcana » Fri Nov 23, 2012 6:05 pm

meteoadriatic wrote:Hi,

try first to look at this topic from wrfforum:

http://forum.wrfforum.com/viewtopic.php?f=22&t=389

In short: I'm not sure but maybe some tables in wrfems v3.1 distribution are outdated. You can try to replace them with those from v3.2 version if they differ, or even from original WPS tarball.

I think those files you should check:
wrfems/data/tables/vtables/Vtable.ECMWF
wrfems/data/tables/vtables/Vtable.ECMWF_sigma
wrfems/data/tables/vtables/Vtable.ERA-interim.ml
wrfems/data/tables/vtables/Vtable.ERA-interim.pl
wrfems/data/tables/wps/METGRID.TBL.ARW (or NMM)

Not sure though if this will solve a problem.
Well, I finally built the met_em* files using a standard WRF-3.3.1. I'll take a look to those files, comparing them with the ones shipped with the standard version to check the differences.

BTW, my current version is 3.1.1.5.1. Is it too old?

Thanks again!

Luis

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

Re: Reanalysis based on ECMWF

Post by meteoadriatic » Fri Nov 23, 2012 8:24 pm

lcana wrote:BTW, my current version is 3.1.1.5.1. Is it too old?
It depends on your needs. Few of us upgraded binaries and support files to latest WRF versions (current 3.4.1) and with ems v3.1 scripts works great. In fact I like v3.1 scripts much more than v3.2 (easier to adapt to my needs).

lcana
Posts: 58
Joined: Wed Nov 30, 2011 4:34 pm

Re: Reanalysis based on ECMWF

Post by lcana » Sat Nov 24, 2012 9:32 am

meteoadriatic wrote:
lcana wrote:BTW, my current version is 3.1.1.5.1. Is it too old?
It depends on your needs. Few of us upgraded binaries and support files to latest WRF versions (current 3.4.1) and with ems v3.1 scripts works great. In fact I like v3.1 scripts much more than v3.2 (easier to adapt to my needs).
Ok.

I'll ask you in the Hacking forum about how to do it. I'd like to upgrade WRF EMS to the 3.3.1 standard version. Thanks a lot for your help!

Luis

Giancarlo Modugno
Posts: 59
Joined: Tue Jun 05, 2012 5:25 pm

Re: Reanalysis based on ECMWF

Post by Giancarlo Modugno » Mon Jan 07, 2013 4:45 pm

it could be a common problem related to the original grid data: what kind of resolution do you use? I had a similar problem and with a different dx it worked

Post Reply

Who is online

Users browsing this forum: No registered users and 1 guest