This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.
Art, The "end time" specified in the data (PDT 4.11) is being set to the initial time in the data for those products after 252 hours, so you are seeing the data being stored as F000 grids, and then the accumulation time which should be 6 hours before the end time becomes negative numbers, eg P-378M at F000 rather than P06M at F384. I've looked at the GRIB2 documentaton as well as the code, and the code seems to match the documentation. The change in the data at 252 hours is that the encoded forecast time changes from unit hours to 6 hours at that point. Eg, the 378 hour start time is encoded as 63 with a code table indicator meaning 6 hour units. All that code matches the documentation. I have sent a note to NCEP to try to see what's up. Steve Chiswell Unidata User Support > Hi... > > We're looking at the new GRIB2 ensemble data and notice that the P06M > fields are available from 0-252 hours, but are not available after that. > In addition, we notice some odd-looking fields named P-252 -> P-384 in the > zero-hour forecast files. Is there some sort of bug/error in the data or > decoding process, or some new "feature" we're unaware of? > > Thanks. > > Art > > Arthur A. Person > Research Assistant, System Administrator > Penn State Department of Meteorology > email: address@hidden, phone: 814-863-1563 > > Ticket Details =================== Ticket ID: ALF-313013 Department: Support GEMPAK Priority: Normal Status: Closed