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.
Leon, >Date: Thu, 08 Sep 2005 13:51:44 -0500 >From: Leon Minton <address@hidden> >Organization: NOAA >To: Steve Emmerson <address@hidden> >Subject: Re: 20050908: Avoiding certain products via pqact.conf The above message contained the following: > I actually didn't quite ask the question correctly. I had already > figured out how to eliminate products in the \3 category that come from > WOH by doing something like this: > > ([^W]..|W[^O].|WO[^H]) > > which would take care of all the RRS stuff but to eliminate all the > other products I need to not process such as the DPA, RCM, etc. that > actually fall into the \5 category which can be either 4, 5, or 6 > characters in length, I need to pipe to a script. I'm sure a slight > modification of your script below using with the PIPE command will do > the trick. I do a lot of mysql database and php stuff but am not up on > the scripting so if you know how to modify the script below to allow for > 1, 2, or 3 characters after the RRS, DPS, or RCM values, I would be most > thankful. Because the substring corresponding to the \5 backreference can be 4, 5, or 6 characters in length, I'm not sure what you're talking about when you say "1, 2, or 3 characters after the RRS, DPS, or RCM values". Would, for example, an "RRS" substring be part of the \3 or the \5 backreference in ^(....[0-9][0-9]|....[0-9]) (K|T|P|N)(...)(.*)/p(....|.....|......)$ Incidentally, because the "(.*)" substring is never referenced via a backreference, the above can be simplified to ^....[0-9][0-9]|....[0-9] (K|T|P|N)(...).*/p(....|.....|......)$ changing the \3 and \5 backreference to \2 and \3, respectively. Regards, Steve Emmerson