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 NetCDF: Attribute not found while running wrf.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.

darwinblue

New member
Hi
While running real.exe, I am getting an error though it is successfully completed. I tried with WRF v4.0.3 also but same error is there. I am attaching the error report and namelist.

The error is,
metgrid input_wrf.F first_date_nml = 2015-01-01_00:00:00
d01 2015-01-01_06:00:00 NetCDF error: NetCDF: Attribute not found
d01 2015-01-01_06:00:00 NetCDF error in ext_ncd_get_dom_ti.code REAL, line 83 Element P_TOP
d01 2015-01-01_06:00:00 NetCDF error: NetCDF: Attribute not found
d01 2015-01-01_06:00:00 NetCDF error in ext_ncd_get_dom_ti.code REAL, line 83 Element GMT
d01 2015-01-01_06:00:00 NetCDF error: NetCDF: Attribute not found
d01 2015-01-01_06:00:00 NetCDF error in ext_ncd_get_dom_ti.code INTEGER, line 83 Element JULYR
d01 2015-01-01_06:00:00 NetCDF error: NetCDF: Attribute not found
d01 2015-01-01_06:00:00 NetCDF error in ext_ncd_get_dom_ti.code INTEGER, line 83 Element JULDAY
d01 2015-01-01_06:00:00 mminlu = 'MODIFIED_IGBP_MODIS_NOAH'
d01 2015-01-01_06:00:00 NetCDF error: NetCDF: Variable not found
d01 2015-01-01_06:00:00 NetCDF error in wrf_io.F90, line 2883 Varname UST_T
d01 2015-01-01_06:00:00 NetCDF error: NetCDF: Variable not found
...
 

Attachments

  • rsl.error.txt
    1.1 MB · Views: 68
  • namelist.input
    8.3 KB · Views: 66
Hi,
I have moved this post to the wrf.exe section of the forum, as this is specific to wrf (and not real.exe, where it was originally posted). The messages you are seeing are simply print-outs from various routines during the wrf.exe process. They shouldn't be anything to worry about, especially since your simulation is running successfully. As long as your results look reasonable, you can ignore these print-outs. We recommend setting debug_level = 0 in your namelist to avoid these "scary" messages that are deceiving. We actually removed the debug_level namelist option from the current default namelists because this variable does not typically provide any useful information and actually can make things more difficult. Turning it on also causes the error logs to be much larger and difficult to look through.
 
Thank you for the reply. Yes you are right it is really difficult to look through the error logs with debug switched on. I will turn off the debug option.
 
Top