Open guoqing-noaa opened 2 months ago
Did you used the ioda converter to convert the prepbufr file containing upper air data, which indicates that the prepbufr file is valid either at 12Z or 00Z?
Good point. The failed ioda_bufr task is at 03z. Does your upper air data mean "sounding" only?
Good point. The failed ioda_bufr task is at 03z. Does your upper air data mean "sounding" only?
the upper air yaml file is only used to convert ADPUPA.
ok, thanks for the clarification! In this sense, we would like to rename it to ADPUPA instead of upper air which is a little bit of confusing.
you can also rename surface to adpsfc.
Yes, that reduces confusion. Do we need to make any other name changes?
Yes, that reduces confusion. Do we need to make any other name changes?
Probably no cause others are using their subsets name, except profiler contains both PROFLR and VADWND.
Just hold on for a moment to rename those files, because I'm about to submit a new pull request to includ time offset into the YAML files.
ok.
When ADPUPA data is not available, the bufr2ioda.x should only print out INFO that no valid BUFR subset was found and should not exit with an error. Because there is some sounding data available at cycles other than 00z, and 12z.
The
ioda_bufr
task is to convert all conventional observations (aircraft, ascatw, gpsipw, mesonet, profiler, rassda, satwnd, all surface types, upperair) in prepbufr to ioda files.The executable is under rrfs-workflow/exec, which is linked from sorc/RDASApp/build/bin/bufr2ioda.x bufr2ioda.x needs a few libraries to work as described in issue #55
bufr2ioda.x can only run in serial but needs 4G memory when converting mesonet obs (per @spanNOAA ). If only one core is requested for the
ioda_bufr
task, one needs to add this to the slurm job card:#SBATCH --mem=4GB
Currently, ioda converter failed for the upper air obs: