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

[LDM #WDO-168362]: Conduit ERE ldmd.conf: problems getting vertical motion and status

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: [LDM #WDO-168362]: Conduit ERE ldmd.conf: problems getting vertical motion and status
  • Date: Sun, 19 Aug 2012 11:15:24 -0600
Christian,

> With your help, I was able finally to fix it all.

Great!

> The only thing is that I
> add to had an arg to the notifyme to see something coming in from the
> CONDUIT feed:
> -T 86400
> e.g. notifyme -vl - -o 3600 -T 86400 -h idd.cise-nsf.gov -f CONDUIT -p
> "status|awip3d.*([UV]REL.*/..0|WX)|prod/gfs.*grbf.*(RELH/..0|WX|OMEG)"
> for example.

That ERE looks good.

notifyme(1) is your friend. :-)

> Now I have these *compact* CONDUIT ERE, esp. that the length of ERE is
> limited:
> 
> "prod/(gfs.*grbf.*(PMSL|HGHT|P..M|RELH/2.m|RELH.*hPa|WX|OMEG.*hPa|TMPK|TM[XN]K03|CLD|UREL.*/10m|UREL.*hPa|CLD|PRES/0.*NONE))"
> 
> "awip3d.*(PMSL|HGHT|P..M|RELH/2.m|TMPK|TM[XN]K03|CLD|HGT.*FRZH|UREL.*/10m|[UV]REL.*hPa|WX|OMEG.*hPa)"

That looks better.

> Really great that everything is working as I need! :-)

Glad I could help.

> Thanks for all again,
> 
> Christian

Regards,
Steve Emmerson

Ticket Details
===================
Ticket ID: WDO-168362
Department: Support LDM
Priority: Normal
Status: Closed