Scheduled Downtime
On Friday 21 April 2023 @ 5pm MT, this website will be down for maintenance and expected to return online the morning of 24 April 2023 at the latest

ERROR not enough eta levels to reach p_top

This post was from a previous version of the WRF&MPAS-A Support Forum. New replies have been disabled and if you have follow up questions related to this post, then please start a new thread from the forum home page.

carinavb

New member
Hello, I finish the install of WPS and WRF v4.
WPS works OK, but when I perform

mpirun -np 8 ./real.exe

taskid: 0 hostname: WRF
module_io_quilt_old.F 2931 T
Ntasks in X 1 , ntasks in Y 1
*************************************
Configuring physics suite 'tropical'

mp_physics: 6
cu_physics: 16
ra_lw_physics: 4
ra_sw_physics: 4
bl_pbl_physics: 1
sf_sfclay_physics: 91
sf_surface_physics: 2
*************************************
REAL_EM V4.0 PREPROCESSOR
*************************************
Parent domain
ids,ide,jds,jde 1 33 1 41
ims,ime,jms,jme -4 38 -4 46
ips,ipe,jps,jpe 1 33 1 41
*************************************
DYNAMICS OPTION: Eulerian Mass Coordinate
alloc_space_field: domain 1 , 67968180 bytes allocated
d01 2019-07-19_00:00:00 Yes, this special data is acceptable to use: OUTPUT FROM METGRID V4.0
d01 2019-07-19_00:00:00 Input data is acceptable to use: met_em.d01.2019-07-19_00:00:00.nc
metgrid input_wrf.F first_date_input = 2019-07-19_00:00:00
metgrid input_wrf.F first_date_nml = 2019-07-19_00:00:00
d01 2019-07-19_00:00:00 Timing for input 0 s.
d01 2019-07-19_00:00:00 flag_soil_layers read from met_em file is 1
d01 2019-07-19_00:00:00 Turning off use of MAX WIND level data in vertical interpolation
d01 2019-07-19_00:00:00 Turning off use of TROPOPAUSE level data in vertical interpolation
Max map factor in domain 1 = 1.02. Scale the dt in the model accordingly.
Using sfcprs3 to compute psfc
d01 2019-07-19_00:00:00 You need one of four things:
d01 2019-07-19_00:00:00 1) More eta levels: e_vert
d01 2019-07-19_00:00:00 2) A lower p_top: p_top_requested
d01 2019-07-19_00:00:00 3) Increase the lowest eta thickness: dzbot
d01 2019-07-19_00:00:00 4) Increase the stretching factor: dzstretch_s or dzstretch_u
d01 2019-07-19_00:00:00 All are namelist options
-------------- FATAL CALLED ---------------
FATAL CALLED FROM FILE: <stdin> LINE: 7262
not enough eta levels to reach p_top
-------------------------------------------
application called MPI_Abort(MPI_COMM_WORLD, 1) - process 0


I attach namelist.wps and namelist.input
I download my gfs data from here:
curl -s --disable-epsv --connect-timeout 30 -m 60 -u anonymous:USER_ID@INSTITUTION -o GFS_00h ftp://ftpprd.ncep.noaa.gov/pub/data/nccf/com/gfs/prod/gfs.20190718/00/gfs.t00z.pgrb2.0p50.f000.

Someone can tell me what I'm doing wrong please!!
Best Regards

Carina
 

Attachments

  • namelist.input
    3.8 KB · Views: 202
  • namelist.wps
    1.3 KB · Views: 97
Your p_top is very high and the vertical levels you have indicated are not enough to cover the entire vertical. You have several options, all you see in your output. You can increase the number of vertical levels or decrease your p_top. If you do not want to do one thing or the other, you should modify the dzstretch_s and dzstretch_u factors, which is what I usually do, but that depends on your needs.
 
Top