IODA files not working with MET 11 #2134
-
files are at DAVIS_DATA MET version 11.0.1
MET version 10.1.2 WORKS!MET version 10.1.2
MET version 11.0.1
ncdump -h raob_20210806T1200Z.nc4
ncdump -h raob_all_v1_20201215T0600Z.nc4
|
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 1 reply
-
Hi Davis, And thank you for your question. I just ran both of the files you provided us (raob_all_v1_20201216T0000Z.nc4 and raob_20210806T1200Z.nc4) through ioda2nc and was unable to duplicate the behavior you're seeing. The first file I tested, raob_all_v1_20201216T0000Z.nc4, had no issues with the default ioda2nc configuration file for the 4 MET releases I tested (10.0.0, 10.1.1, 11.0.0, and 11.0.1). Here's the readout from one of the version 11 runs:
When I ran ioda2nc with the second file, raob_20210806T1200Z.nc4, for the same 4 MET releases I did run into errors, but only in the MET version 10 releases. This is exactly opposite of what you experienced. Those errors looked like the following:
Because the MET 10 versions are an older version, it's not surprising to see that they are not able to process files in the same way as newer versions of MET do. However, the flipped behavior I'm seeing to what you're describing is something we can look more into. Would you be able to try a few things and report back how they go? The first is to try to rerun the file(s) using only the default configuration file for each release. That can be accomplished by simply omitting the configuration file from the ioda2nc prompt, i.e. |
Beta Was this translation helpful? Give feedback.
-
The ioda file with the NetCDF group (IODA version 2) is supported from MET 11.
|
Beta Was this translation helpful? Give feedback.
-
I upped the debug verbosity and got this:
DEBUG 2: Rejected: message type = 389 This stuck out so I checked what was in the post ioda2nc file under message type and got this:
So I looked in my point_stat config file and added NA to my message_type_group_map
And success! |
Beta Was this translation helpful? Give feedback.
I upped the debug verbosity and got this: