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

When running metgrid.exe, all but one met_em.d* files are good. Why does the first one (d01, t=0) return an HDF error.

B

bashaman

New member
Hi,

In running WPS, metgrid.exe runs start to finish. However, a single met_em.d* file, met_em.d01.2006-12-12_00:00:00.nc (starting time step), returns an HDF error on ncdump.
The met_em files for d02 and d03 of the same time step are fine, as well as later time steps of d01. I'm wondering what is singling out this one file to give it errors? Namelist attached below.


Thanks for any insights you might have on this.
 

Attachments

  • namelist.wps
    1.2 KB · Views: 2
Which version of WPS did you run? Can you rerun metgrid to process only the first time data for D01 and see whether it works normally?
 
I'm running version 4.1 of WPS (I have colleagues that are more familiar with 4.1, so when I get more familiar with WPS and WRF, I plan to switch to a newer version). I ran WPS for only the first time data and D01, but it still yielded the same issue.
Ming Chen said:
Which version of WPS did you run? Can you rerun metgrid to process only the first time data for D01 and see whether it works normally?
Click to expand...
 
When I run real.exe, I get the following error in the rsl files:
Ming Chen said:
What error message did you get in your rsl files?
Click to expand...


FATAL CALLED FROM FILE: <stdin> LINE: 401
error opening met_em.d01.2006-12-12_00:00:00.nc for input; bad date in namelist or file not in directory
 
bashaman said:
When I run real.exe, I get the following error in the rsl files:



FATAL CALLED FROM FILE: <stdin> LINE: 401
error opening met_em.d01.2006-12-12_00:00:00.nc for input; bad date in namelist or file not in directory
Click to expand...
An interesting development: in the namelist, I switched the start time from 2006-12-12_00:00:00 to 2006-12-12_03:00:00 and the same error occurred for met_em.d01.2006-12-12_03:00:00.nc
 
Do you have met_em.d01.2006-12-12_00:00:00.nc in your working directory?

I ask this because I couldn't repeat your issue. The only reason I can guess is that you don't have met-em file at the time specified in your namelist.wps.

Anyway, please keep me updated if you eventually figure out what is wrong. Thanks in advance.
 
Ming Chen said:
Do you have met_em.d01.2006-12-12_00:00:00.nc in your working directory?

I ask this because I couldn't repeat your issue. The only reason I can guess is that you don't have met-em file at the time specified in your namelist.wps.

Anyway, please keep me updated if you eventually figure out what is wrong. Thanks in advance.
Click to expand...
The files in question are in the working directory. I'll keep working on this.
 
I am perplexed by the model behavior in your case. We never see such problems before and I cannot repeat the problem. Probably it is related to environmental setttings and/or libraries, however, this cannot explain why the model works for data of different times.

Anyway, Please keep me updated about this issue. Thanks in advance.
 
You must log in or register to reply here.
Top