4 namelist files
4 namelist files
I'm a little confused about the namelist files. There are 4 of them in the "static" directory (of my arw run) - where do I set start and stop times for runs? These seem to have been created from some other master file - I don't think I have to edit all 4 of these... I checked the data/domains/arw/static but that holds a different time than my simulation. There wasn't a time of run setting in dwiz...
-
- Posts: 1540
- Joined: Wed Aug 19, 2009 10:05 am
Re: 4 namelist files
Don't touch those namelists if you want to use EMS features. If you want to work with namelists directly, then you have to forget about EMS and do your scripting yourself.
WRF EMS scripts create dynamically namelists and you don't need to worry about how. Only if something doesn't work as you like, then you can hack the scripts, but again, not namelists directly.
If you want to use EMS system as it is, then you should go through users manual first. There you will find all information about how to start and configure your runs. Look also at directory wrfems/runs/<domainname>/conf - everything that you need to set about your run is there
WRF EMS scripts create dynamically namelists and you don't need to worry about how. Only if something doesn't work as you like, then you can hack the scripts, but again, not namelists directly.
If you want to use EMS system as it is, then you should go through users manual first. There you will find all information about how to start and configure your runs. Look also at directory wrfems/runs/<domainname>/conf - everything that you need to set about your run is there

Re: 4 namelist files
Thank you for the reply! I didn't want to hack EMS but I thought I saw a post on here requesting a namelis, which made me think that occasionally these were to be modified. Of course, I went through the users manual ~1.5 times so far - finished it last night - obviously forgot most of it. My mind is swimming - lots of stuff I didn't understand very well, but it helps my understanding quite a lot to exercise the software - I understand things that didn't make sense by just reading words.meteoadriatic wrote:Don't touch those namelists if you want to use EMS features. If you want to work with namelists directly, then you have to forget about EMS and do your scripting yourself.
WRF EMS scripts create dynamically namelists and you don't need to worry about how. Only if something doesn't work as you like, then you can hack the scripts, but again, not namelists directly.
If you want to use EMS system as it is, then you should go through users manual first. There you will find all information about how to start and configure your runs. Look also at directory wrfems/runs/<domainname>/conf - everything that you need to set about your run is there
I should have mentioned I'm trying to reproduce this event:
http://www.youtube.com/watch?v=wk70fAQG6c8
(or else the 8 July 2002 storm)
...just as an exercise in actually using the software and getting decent outputs. I'm looking for suggestions on which --dset's would be needed.
Thanks Again
-
- Posts: 1540
- Joined: Wed Aug 19, 2009 10:05 am
Re: 4 namelist files
That is 11. september, 2010, so if you want FNL dataset, go here:pattim wrote:I should have mentioned I'm trying to reproduce this event:
http://www.youtube.com/watch?v=wk70fAQG6c8
...just as an exercise in actually using the software and getting decent outputs.
.
http://nomads.ncdc.noaa.gov/data/gfsanl ... /20100911/
Then download these files:
http://nomads.ncdc.noaa.gov/data/gfsanl ... 0_000.grb2
http://nomads.ncdc.noaa.gov/data/gfsanl ... 0_000.grb2
http://nomads.ncdc.noaa.gov/data/gfsanl ... 0_000.grb2
http://nomads.ncdc.noaa.gov/data/gfsanl ... 0_000.grb2
http://nomads.ncdc.noaa.gov/data/gfsanl ... 0_000.grb2
With those 5 files you will be able to run 24h simulation starting at 2012-09-11, 00 UTC and ending at 2012-09-12, 00 UTC.
When you download these at your computer, create domain with dwiz around area where you want the simulation. I recommend that you first try without nesting, use ARW core at around 12km resolution.... also go into wrfems/runs/<domainname>/conf and configure your run as you like. Conf files there are pretty much commented so you won't have much trouble doing that.
When you create domain, put downloaded files into wrfems/runs/<domainname>/grib directory.
Then you have to ensure that gribs file names and naming convention for FNL dataset matches. So you need to check wrfems/conf/grib_info/fnl_gribinfo.conf file. There you will find sumething like:
Code: Select all
LOCFIL = YYMMDDCC.fnl_YYYY-MM-DD_CC
Now, either change this line to match grib names that you downloaded, or rename gribs to match this line... whatever you like more.
When you do that, you can simply issue ems_autorun procedure...
Code: Select all
ems_autorun --dset fnl --local --date 20100911 --cycle 00 --analysis

Re: 4 namelist files
You ARE the best! Thank you for your help. I'm going to start that run and hit the manual again. I still have to get a couple more softwares installed. My colleague is trying to install CESM, but I like WRF/GEOS5/ModelE. But we do need CESM because it can actually reach the thermosphere and my colleague does satellite/debris orbits and orbit decay (I do cloud remote sensing from orbit). - Patricia
EDIT: I meant to ask - the EMS scripts aren't "smart" enough to automatically download the files needed from that repo?
EDIT: I meant to ask - the EMS scripts aren't "smart" enough to automatically download the files needed from that repo?
-
- Posts: 1540
- Joined: Wed Aug 19, 2009 10:05 am
Re: 4 namelist files
I don't know about 0.5 deg yet. They are smart enough for FNL 1 deg, but only with wrfems 3.2 beta. In 3.1 everything should be downloaded manually (it's not very hardpattim wrote:You ARE the best! Thank you for your help. I'm going to start that run and hit the manual again. I still have to get a couple more softwares installed. My colleague is trying to install CESM, but I like WRF/GEOS5/ModelE. But we do need CESM because it can actually reach the thermosphere and my colleague does satellite/debris orbits and orbit decay (I do cloud remote sensing from orbit). - Patricia
EDIT: I meant to ask - the EMS scripts aren't "smart" enough to automatically download the files needed from that repo?

Re: 4 namelist files
LOL!!...meteoadriatic wrote: Now, either change this line to match grib names that you downloaded, or rename gribs to match this line... whatever you like more.
When you do that, you can simply issue ems_autorun procedure...It should be pretty much everything you need to do. Try itCode: Select all
ems_autorun --dset fnl --local --date 20100911 --cycle 00 --analysis
EMS ERROR : OOPS - I smell option trouble
Hey, did you know that "--local --analysis" are not options
to ems_autorun. Try again or run "ems_autorun --help" for
assistance.
Remember, there are no bad options, just those that will
result in this message again.
patti@OS121->
Just on a whim, I tried
patti@OS121-> ems_prep --dset fnl --date 20100911 --cycle 00 --analysis
...but the script doesn't try to connect to the online fnl dataset - it tries to FTP to "local" - maybe because of the first time when I used the --local flag with autorun? I'm looking for how to remove the "local" from the FTP command because I *know* the software scripts know about the fnl database.
* Locating fnl files for model initial and boundary conditions
Initiating FTP connection to LOCAL
! CONNECTION ERROR - Net::FTP: Bad hostname 'local'
! There were problems acquiring the fnl data files for model initialization
EDIT: Ap - found the trouble - in the gribinfo for fnl:
SERVER-FTP = LOCAL:/data/grib/fnl/fnl_YYYY-MM-DD_CC
...do I change the file name format here also (in addition to LOCFIL=)?
Hmmm... Looks OK except for a zero length simulation... I guess I need --length 24
Code: Select all
patti@OS121-> ems_prep --dset fnl --date 20100911 --cycle 00 --analysis
WRF EMS Program ems_prep (V3.2.1.5.45.beta) started on OS121 at Wed Jul 4 23:17:50 2012 UTC
The WRF EMS Says: "Who's Awesome? You're Awesome!"
I. WRF EMS ems_prep Model Initialization Summary
Initialization Start Time : Sat Sep 11 00:00:00 2010 UTC
Initialization End Time : Sat Sep 11 00:00:00 2010 UTC
Boundary Condition Frequency : 360 Minutes
Initialization Data Set : fnl
Boundary Condition Data Set : fnl
Static Surface Data Sets : None
Land Surface Data Sets : None
II. Search out requested files for WRF model initialization
* Locating fnl files for model initial and boundary conditions
* All requested fnl files are available for model initialization
Excellent! - Your master plan is working!
III. Create the WPS ARW intermediate format files
* Processing fnl files for use as model initial and boundary conditions - Bingo!!
ARW core intermediate file processing completed in 11.64 seconds
IV. Horizontal interpolation of the intermediate files to the computational domain
* Metgrid processed files are located in
/home/patti/00_GCMs/EMS_WRF/wrfems/runs/nested_mediteranean_Storm09112012Athens/wpsprd
Horizontal interpolation to computational domain completed in 2.73 seconds
WRF EMS Program ems_prep completed at Wed Jul 4 23:18:05 2012 UTC
patti@OS121-> ems_run --domain 1
Use of qw(...) as parentheses is deprecated at /home/patti/00_GCMs/EMS_WRF/wrfems/strc/ems_run/Run_cfgarw.pm line 431.
Use of qw(...) as parentheses is deprecated at /home/patti/00_GCMs/EMS_WRF/wrfems/strc/ems_run/Run_cfgnmm.pm line 350.
WRF EMS Program ems_run (V3.2.1.5.45.beta) started on OS121 at Wed Jul 4 23:18:28 2012 UTC
The WRF EMS Says: "Who's Awesome? You're Awesome!"
I. Preforming configuration in preparation for your EMS experience
* You are running the WRF ARW core. Hey Ho! Let's go! - model'n!
* Simulation start and end times:
Domain Start End
1 2010-09-11_00:00:00 2010-09-11_00:00:00
* Simulation length will be 0.00 seconds
* Large timestep to be used for this simulation is 160 seconds
II. Creating the initial and boundary condition files for the user domain(s)
* The WRF REAL program shall be run on the following systems and processors:
6 processors on OS121 (1 tiles per processor)
* Creating the WRF initial and boundary condition files
EMS ERROR : UGH! Creation of model initial and boundary conditions failed!
I hate when this #%^!#!!% happens.
Hopefully nobody was hurt during this attempt!
! Here are the last few lines of the the log/real.0000.err file:
*************************************
Parent domain
ids,ide,jds,jde 1 100 1 104
ims,ime,jms,jme -4 105 -4 25
ips,ipe,jps,jpe 1 100 1 18
*************************************
DYNAMICS OPTION: Eulerian Mass Coordinate
alloc_space_field: domain 1 , 94837944 bytes allocated
metgrid input_wrf.F first_date_nml = 2010-09-11_00:00:00
d01 2010-09-11_00:00:00 Timing for input 0 s.
d01 2010-09-11_00:00:00 flag_soil_layers read from met_em file is 1
Max map factor in domain 1 = 1.04. Scale the dt in the model accordingly.
d01 2010-09-11_00:00:00 Old data, no inland lake information
Assume Noah LSM input
d01 2010-09-11_00:00:00 Timing for processing 0 s.
d01 2010-09-11_00:00:00 Timing for output 1 s.
d01 2010-09-11_00:00:00 Timing for loop # 1 = 1 s.
d01 2010-09-11_00:00:00 real_em: SUCCESS COMPLETE REAL_EM INIT
* Gathering information for localhost OS121
! System information is also available from static/wrfems_system.info
! A little help from your friend at EMS world headquarters
The log files from your failed run have been written to:
/home/patti/00_GCMs/EMS_WRF/wrfems/runs/nested_mediteranean_Storm09112012Athens/log/2012070423.real_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_run failure (3) at Wed Jul 4 23:18:36 2012 UTC
patti@OS121->
Code: Select all
patti@OS121-> ems_prep --dset fnl --date 20100911 --cycle 00 --analysis --length 24
WRF EMS Program ems_prep (V3.2.1.5.45.beta) started on OS121 at Wed Jul 4 23:20:42 2012 UTC
The WRF EMS Says: "Who's Awesome? You're Awesome!"
I. WRF EMS ems_prep Model Initialization Summary
Initialization Start Time : Sat Sep 11 00:00:00 2010 UTC
Initialization End Time : Sun Sep 12 00:00:00 2010 UTC
Boundary Condition Frequency : 360 Minutes
Initialization Data Set : fnl
Boundary Condition Data Set : fnl
Static Surface Data Sets : None
Land Surface Data Sets : None
II. Search out requested files for WRF model initialization
* Locating fnl files for model initial and boundary conditions
* All requested fnl files are available for model initialization
Excellent! - Your master plan is working!
III. Create the WPS ARW intermediate format files
* Processing fnl files for use as model initial and boundary conditions - That's Hot!!
ARW core intermediate file processing completed in 53.33 seconds
IV. Horizontal interpolation of the intermediate files to the computational domain
* Metgrid processed files are located in
/home/patti/00_GCMs/EMS_WRF/wrfems/runs/nested_mediteranean_Storm09112012Athens/wpsprd
Horizontal interpolation to computational domain completed in 9.07 seconds
WRF EMS Program ems_prep completed at Wed Jul 4 23:21:45 2012 UTC
patti@OS121-> ems_run --domain 1
Use of qw(...) as parentheses is deprecated at /home/patti/00_GCMs/EMS_WRF/wrfems/strc/ems_run/Run_cfgarw.pm line 431.
Use of qw(...) as parentheses is deprecated at /home/patti/00_GCMs/EMS_WRF/wrfems/strc/ems_run/Run_cfgnmm.pm line 350.
WRF EMS Program ems_run (V3.2.1.5.45.beta) started on OS121 at Wed Jul 4 23:21:51 2012 UTC
The WRF EMS Says: "Who's Awesome? You're Awesome!"
I. Preforming configuration in preparation for your EMS experience
* You are running the WRF ARW core. Hey Ho! Let's go! - model'n!
* Simulation start and end times:
Domain Start End
1 2010-09-11_00:00:00 2010-09-12_00:00:00
* Simulation length will be 24 hours
* Large timestep to be used for this simulation is 160 seconds
II. Creating the initial and boundary condition files for the user domain(s)
* The WRF REAL program shall be run on the following systems and processors:
6 processors on OS121 (1 tiles per processor)
* Creating the WRF initial and boundary condition files
* WRF initial and boundary conditions successfully created in 3 seconds
Moving on to bigger and better delusions of grandeur
III. Running ARW WRF while thinking happy thoughts
* The WRF ARW core shall be run on the following systems and processors:
6 processors on OS121 (1 tiles per processor)
* Run Output Frequency Primary wrfout Aux File 1
---------------------------------------------------
Domain 01 : 1 hour Off
* Runnning your simulation with enthusiasm!
You can sing along to the progress of the simulation while watching:
% tail -f /home/patti/00_GCMs/EMS_WRF/wrfems/runs/nested_mediteranean_Storm09112012Athens/rsl.out.0000
Unless you have something better to do with your time
Re: 4 namelist files
On EMS 3.4:
ems_prep --dset fnl --local --date YYYYMMDD --cycle 00 --analysis --lenght 24
gives an error:
Passing --lenght will not get your EMSgruven on because that's not an option.
Any idea??
ems_prep --dset fnl --local --date YYYYMMDD --cycle 00 --analysis --lenght 24
gives an error:
Passing --lenght will not get your EMSgruven on because that's not an option.
Any idea??
Re: 4 namelist files
The same problem on 3.2....
-
- Posts: 1
- Joined: Thu Sep 26, 2013 4:49 pm
Re: 4 namelist files
nebojsa,
You misspelled "length" as "lenght".
That would be why ems_prep is not working for you.
You misspelled "length" as "lenght".
That would be why ems_prep is not working for you.
Who is online
Users browsing this forum: No registered users and 9 guests