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.
David, > One of our users wanted to convert this pqact.conf entry to work with > the new CONDUIT naming conventions. > > CONDUIT > ^/afs/\.nwstg\.nws\.noaa\.gov/ftp/SL\.us008001/ST\.opnl/MT\.(gfs|avn)_CY.([0-9][0-9])/RD\.([0-9][0-9][0-9][0-9][0-9][0-9][0-9][0-9])/PT\.grid_DF\.gr1/fh\.0([0-9][0-9][0-9])_tl\.press_gr\.onedeg.*$ > FILE data/avn/\3\2/avngrib.\3\2.f0\4 > > And I told him: > > This is tricky because the new name can have 2 digits in the file > name (hours < 100) or three (hours >= 100): > gfs.t12z.pgrbf150 gfs.t12z.pgrbf42 > > So, this almost does it: > > CONDUIT > ^data/nccf/com/gfs/prod/gfs.([0-9][0-9][0-9][0-9][0-9][0-9][0-9][0-9][0-9][0-9])/gfs.t([0-9][0-9])z.pgrbf([^\ > ]*) > FILE data/avn/\1/avngrib.\1.f0\3 > > I am not sure if there is a way in the LDM to force the number > found in the 3rd match, \3, to write out in specified number of > digits -- that is add a zero at the beginning for numbers under > 100. > > I suppose we could do this: > > CONDUIT > ^data/nccf/com/gfs/prod/gfs.([0-9][0-9][0-9][0-9][0-9][0-9][0-9][0-9][0-9][0-9])/gfs.t([0-9][0-9])z.pgrbf([0-9][0-9])$ > FILE data/avn/\1/avngrib.\1.f00\3 > CONDUIT > ^data/nccf/com/gfs/prod/gfs.([0-9][0-9][0-9][0-9][0-9][0-9][0-9][0-9][0-9][0-9])/gfs.t([0-9][0-9])z.pgrbf([0-9][0-9][0-9])$ > FILE data/avn/\1/avngrib.\1.f0\3 > > Is that the only way to handle this 2-digit vs 3-digit issue? That's what I would do. I'd also request the creator of the product-identifiers to fix the format. Regards, Steve Emmerson Ticket Details =================== Ticket ID: KEO-270357 Department: Support LDM Priority: Normal Status: Closed