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

eta level error

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.

mitchellkcm

New member
Hi there,
I'm getting this error when running real.exe

-----------------------------------------------------------------------------

Domain 1: Current date being processed: 2017-04-10_00:00:00.0000, which is loop # 1 out of 44
configflags%julyr, %julday, %gmt: 2017 100 0.0000000E+00
d01 2017-04-10_00:00:00 Yes, this special data is acceptable to use: OUTPUT FROM METGRID V4.0.2
d01 2017-04-10_00:00:00 Input data is acceptable to use: met_em.d01.2017-04-10_00:00:00.nc
metgrid input_wrf.F first_date_input = 2017-04-10_00:00:00
metgrid input_wrf.F first_date_nml = 2017-04-10_00:00:00
d01 2017-04-10_00:00:00 Timing for input 0 s.
d01 2017-04-10_00:00:00 flag_soil_layers read from met_em file is 1
Max map factor in domain 1 = 0.97. Scale the dt in the model accordingly.
Using sfcprs3 to compute psfc
-------------- FATAL CALLED ---------------
FATAL CALLED FROM FILE: <stdin> LINE: 7197
First eta level should be 1.0 and the last 0.0 in namelist
-------------------------------------------

My first eta level is 1.0 and the last is 0.0. What could be causing this error?
 

Attachments

  • namelist.input.txt
    7.8 KB · Views: 125
Hi Kimberly...

You list 32 "eta_levels", however, you told WRF to only use 20 levels. Change "e_vert"
from 20 to 32 to fix things.
 
Top