[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[CONDUIT #ZRX-794011]: 20150728: help with regex patterns help

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.

  • Subject: [CONDUIT #ZRX-794011]: 20150728: help with regex patterns help
  • Date: Wed, 29 Jul 2015 01:35:29 -0600
Hi Donna,

Sorry for the slow reply, things have been quite hectic around
Unidata given the number of things going on at the same time
(workshop, me writing a GOES-R proposal, the addition of 0.25 degree
GFS to CONDUIT, and a number of other things).

re:
> With the announcement that the gfs 0p25 data will be added to the
> CONDUIT feed tomorrow, I would like to know how to change our CONDUIT
> request to not allow .*pgrb2.0p25.* files while still allowing all other
> CONDUIT products. This is to be a temporary measure (until next week).

We included the URL for a page that has some REQUEST examples in 
the CONDUIT announcement blog post.  Here it is again:

http://www.unidata.ucar.edu/blogs/news/entry/gfs-0-25-176-model

re:
> My initial reaction was to change:
> 
> request                CONDUIT "([09]$)" idd.unidata.ucar.edu
> request                CONDUIT "([18]$)" idd.unidata.ucar.edu
> request                CONDUIT "([27]$)" idd.unidata.ucar.edu
> request                CONDUIT "([36]$)" idd.unidata.ucar.edu
> request                CONDUIT "([45]$)" idd.unidata.ucar.edu
> 
> to
> 
> request         CONDUIT "([^pgrb2.0p25].*[09]$)" idd.unidata.ucar.edu
> request         CONDUIT "([^pgrb2.0p25].*[18]$)" idd.unidata.ucar.edu
> request         CONDUIT "([^pgrb2.0p25].*[27]$)" idd.unidata.ucar.edu
> request         CONDUIT "([^pgrb2.0p25].*[36]$)" idd.unidata.ucar.edu
> request         CONDUIT "([^pgrb2.0p25].*[45]$)" idd.unidata.ucar.edu

The bracket syntax ('[]') in a regular expression means a list
of characters.  [^pgrb2.0p25] is interpreted as "not p or g or r or b, etc."

re:
> But when I test different product names with the new regex, sometimes it
> fails when I want it to succeed and succeed when I want it to fail. If
> this regex isn't going to do what I want it to do, I suppose I will give
> up on the idea.
> 
> Am I doing this wrong?
> 
> [ldm@ldm-relay0 ~]$ regex -s 'data2/TIGGE/gep14.t12z.pgrb2cf12
> !grib2/ncep/GEFS/#000/201507271200F012/PVOR/320 K THTA! 000018'
> "[^pgrb2.0p25].*[28]$"
> 
> match
> 
> [ldm@ldm-relay0 ~]$ regex -s 'data/nccf/com/gfs/prod/gfs.2015072712
> <tel:2015072712>/gfs.t12z.pgrb2.0p50.f348
> !grib2/ncep/GFS/#000/201507271200F348/VREL/400 hPa PRES! 000098'
> "[^pgrb2.0p25].*[28]$"
> 
> match
> 
> [ldm@ldm-relay0 ~]$ regex -s 'data/nccf/com/gfs/prod/gfs.2015072712
> <tel:2015072712>/gfs.t12z.pgrb2.0p25.f348
> !grib2/ncep/GFS/#000/201507271200F348/VREL/400 hPa PRES! 000098'
> "[^pgrb2.0p25].*[28]$"
> 
> match

Please check the example for sites that do not want to receive
the 0.25 degree GFS in:

http://www.unidata.ucar.edu/blogs/news/entry/gfs-0-25-176-model

If you still have problems, we can login to your machines and
take a look.

Cheers,

Tom
--
****************************************************************************
Unidata User Support                                    UCAR Unidata Program
(303) 497-8642                                                 P.O. Box 3000
address@hidden                                   Boulder, CO 80307
----------------------------------------------------------------------------
Unidata HomePage                       http://www.unidata.ucar.edu
****************************************************************************


Ticket Details
===================
Ticket ID: ZRX-794011
Department: Support CONDUIT
Priority: Normal
Status: Closed