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.
Alan, I see you sent the message to Robb, so I'll let him answer more competely, but here is a quick impression: The easiest thing to do is probably let the 15 minute precip mode file just overwrite the 10 minute file. In other words, you are matching both 10 and 15 with the (1[0-9]) pattern at the end, but you can write them to the same file name instead of using the \6 pattern. This would be OK, unless you absolutely want the filename to be the exact time of the data. For example: WSI ^NEX/(...)/BREF1/..([0-9][0-9])([0-1][0-9])([0-3][0-9])([0-2][0-9])(1[0-9]) FILE -overwrite data/nexrad/\2/\1r0/\3\4\510.nid This way, any image from 10-19 minutes would be written to a file name using 10 as the minutes. A subsequent image would overwrite the previous using the -overwrite tage to FILE. Without -overwrite, the data would be appended. Steve Chiswell Unidata User Support >From: Alan F Cunningham <address@hidden> >Organization: . >Keywords: 200003012049.NAA28905 >I have a problem which I might be able to fix with the pqact.conf, >I'm trying to get NIDS files once an hour with a line like this.. > >WSI >^NEX/(...)/BREF1/..([0-9][0-9])([0-1][0-9])([0-3][0-9])([0-2][0-9])(1[0-9]) > FILE /usr/local/ldm/data/nexrad/\2/\1r0/\3\4\5\6.nid > >This works fine for stations in clear air mode, where I would get one file >per hour (ending either in ......10.nid or ......15.nid) because the >update rate is 10-11 minutes for the mode. However, >in precip mode (updates 5-6 minutes), I get two files every hour, ending >in ......10.nid and ......15.nid. This is a problem of storage and >scheduling. > >Would _ELSE_ be able to help me with a line like this appended to the one >above? > >WSI ^_ELSE_$ NOOP > >I feel like I would need the abilty to define a regular pattern for >_ELSE_ to >really do the job. > >Alan Cunningham >Clemson University Radar Ornithology Lab >310 Jordan Hall >864-656-3584 >hubcap.clemson.edu/~acunnin >