Formatting netCDF files correctly for MET to correctly get forecast hour lead information #1400
-
Hello, As a part of the Global Deterministic Atmospheric verification we are verifying daily averaged Geopotential Height Anomalies. After some discussions about what stats we are looking for it is just some continuous statistics like Bias and RMSE. Geopotential Height Anomalies are not an output in the GFS grib2 files so I have to calculate these myself. Here is the process I am doing:
When I go to run GridStat to output the CNT line type on this file, the STAT file out has the suffix "000000L_20220201_000000V.stat" when I would have expected "240000L_20220201_000000V.stat". If needed I can hand over the example I am talking about! |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 4 replies
-
Hi Mallory: Are you using MET version netcdf files or CF-compliant? Could I see a sample of one of them? Thanks, |
Beta Was this translation helpful? Give feedback.
-
@malloryprow and @CPKalb, yes, Grid-Stat does name its output files based on the timing information of the forecast data: On this line of grid_stat.cc, the first forecast data plane object read is passed as an argument to setup_first_pass(). And this line of setup_first_pass() sends the valid and lead time of that forecast data to setup_txt_files(), which uses it to create the output file names. So all of that logic is working the way we expect. What is NOT working the way we expect is MET's parsing the timing information from that forecast field. This can be demonstrated by running plot_data_plane at verbosity level 4:
And the log messages contain:
But that doesn't match the timestamps in the file:
So I'd say there's a bug in the library code's parsing of these times. I'll write up a bugfix issue and we'll get this fixed in MET-10.1.0. In the meantime, you could use the set_attr_init and set_attr_lead options as a temporary workaround until this bug is fixed:
|
Beta Was this translation helpful? Give feedback.
@malloryprow and @CPKalb, yes, Grid-Stat does name its output files based on the timing information of the forecast data:
On this line of grid_stat.cc, the first forecast data plane object read is passed as an argument to setup_first_pass(). And this line of setup_first_pass() sends the valid and lead time of that forecast data to setup_txt_files(), which uses it to create the output file names. So all of that logic is working the way we expect.
What is NOT working the way we expect is MET's parsing the timing information from that forecast field. This can be demonstrated by running plot_data_plane at verbosity level 4: