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

"Could not find level above ground" error in real.exe

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.

SuperiorDrax

New member
Hi everyone
I am using WRFV4.0 and have met a problem after running real.exe. It reported "Could not find level above ground". It seems that there is something wrong in calculating psfc, but I have already provided this variable in my met_em file.
I have searched some related problems in this forum and there is one post saying that this is a machine issue. Does that mean I have to run WRF in another computer?
I have attached my namelist and one of the met_em files.
Thanks in advance.

The following part is the the end of my rsl.out.0000 file:

Domain 1: Current date being processed: 2018-07-07_00:00:00.0000, which is loop # 1 out of 96
configflags%julyr, %julday, %gmt: 2018 188 0.00000000
d01 2018-07-07_00:00:00 Yes, this special data is acceptable to use: OUTPUT FROM METGRID V4.0
d01 2018-07-07_00:00:00 Input data is acceptable to use: met_em.d01.2018-07-07_00:00:00.nc
metgrid input_wrf.F first_date_input = 2018-07-07_00:00:00
metgrid input_wrf.F first_date_nml = 2018-07-07_00:00:00
d01 2018-07-07_00:00:00 Timing for input 0 s.
d01 2018-07-07_00:00:00 flag_soil_layers read from met_em file is 1
Max map factor in domain 1 = 1.05. Scale the dt in the model accordingly.
Using sfcprs3 to compute psfc
i,j = 3 17
p = -851.808350 100000.000 97500.0000 95000.0000 92500.0000 90000.0000 87500.0000 85000.0000 82500.0000 80000.0000 77500.0000 75000.0000 70000.0000 65000.0000 60000.0000 55000.0000 50000.0000 45000.0000 40000.0000 35000.0000 30000.0000 25000.0000 22500.0000 20000.0000 17500.0000 15000.0000 12500.0000 10000.0000 7000.00000 5000.00000 3000.00000 2000.00000 1000.00000 700.000000 500.000000 300.000000 200.000000 100.000000
p sfc = -851.808350
-------------- FATAL CALLED ---------------
FATAL CALLED FROM FILE: <stdin> LINE: 6459
Could not find level above ground
-------------------------------------------
 

Attachments

  • namelist.input
    3.3 KB · Views: 24
The rsl.out files are also provided here.
 

Attachments

  • rsl.error.0000.txt
    1.3 KB · Views: 22
  • rsl.out.0000.txt
    7.1 KB · Views: 22
Hi,
I believe this is an issue with the PSFC variable in your met_em* files. When looking at that variable in the file you sent, I see the value ranges from -22602.6 to 28564.5 Pa. So you have quite a negative value in there, in several locations in that file. I would recommend plotting that variable from the raw input data file to see if the value for surface pressure looks correct, to determine whether this is an issue with metgrid, or with the input file, itself.
 
kwerner said:
Hi,
I believe this is an issue with the PSFC variable in your met_em* files. When looking at that variable in the file you sent, I see the value ranges from -22602.6 to 28564.5 Pa. So you have quite a negative value in there, in several locations in that file. I would recommend plotting that variable from the raw input data file to see if the value for surface pressure looks correct, to determine whether this is an issue with metgrid, or with the input file, itself.
Hi
Thank your very much for your suggestion. I have found out that this error was due to the incorrect process of my input data.
I am trying to run WRF with ERA5 data and after downloading the data in netcdf4 format, I read the file like this at first:
fname="PS.2018.07.nc"
in_sp = addfile(dat_dir+fname,"r")
PS = in_sp->sp
but now I know what I should do is adding
PS := PS*PS@scale_factor+PS@add_offset
It seems that the data is normalized in the file I downloaded and I did not notice it. This explained the negative value in PSFC.
Anyway, this error has nothing to do with WRF or my computer.
 
Hi,
I'm so glad to hear you've figured out the issue, and that it was neither the fault of WRF, nor your computer! Thank you for updating the issue.
 
Top