Neil, > Thanks Steve. > > Check with Chiz or Michael James : the GEMPAK package scripts that generate > pqact entries for gempak decoders will create output filename strings like: > > data/gempak/model/gfs/YYYYMMDDHH_gfs212.gem > data/gempak/mos/YYYYMMDDHH_gmos.gem > data/gempak/syn/YYYYMMDD_syn.gem > > Likewise to be found in the gempak package config file âdatatype.tblâ > referenced by the decoder for output file paths and filenames. Well... the names of the output files might have that pattern, but I can guarantee that pqact(1) doesn't understand those patterns. If you search the relevant pqact(1) configuration-file(s), you'll likely see that the string "YYYYMMDDHH" doesn't appear as the name of a file in a FILE action. It's possible, however, that such strings are used as input to various GEMPAK decoders -- to tell them how to name their output files. > I guess they work because Iâve been using them for years in our pqact files. > > And a clarification please: > The (\x: ..) in the documentation will always be the number referencing the > day-of-month parenthetical? And the yyyy and mm will be derived from it? That's correct. A WMO header doesn't have a year field -- so a heuristic is needed to determine the year when near the end of one year and the beginning of the next. Regards, Steve Emmerson Ticket Details =================== Ticket ID: PRT-382252 Department: Support LDM Priority: Normal Status: Closed
NOTE: All email exchanges with Unidata User Support are recorded in the Unidata inquiry tracking system and then made publicly available through the web. If you do not want to have your interactions made available in this way, you must let us know in each email you send to us.