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

[Datastream #SYG-389000]: Changing requests based on time

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: [Datastream #SYG-389000]: Changing requests based on time
  • Date: Mon, 25 Feb 2013 17:46:53 -0700
Hi Joe,

re:
> I have a small question
> 
> I have a line in my LDM conf to pull data down
> request FSL2 "(.*000Hour)" idd.unidata.ucar.edu

OK.  Just so you know, the '.*' preceeding '000Hour' is not
necessary, and the only reason to enclose the regular expression
in parentheses is if there is a second request with the same
pattern and you want to force both feeds to operate in PRIMARY
mode.

The following REQUEST will likely be just want you want/need:

request FSL2 "000Hour" idd.unidata.ucar.edu

By the way, I assume from this pattern that you are interested
in the HRRR data; correct?

re:
> Is there a way I can modify it to request
> 
> request FSL2 
> "(.*000Hour|.*001Hour|.*002Hour|.*003Hour|.*004Hour|.*005Hour|.*006Hour)" 
> idd.unidata.ucar.edu
> every 6 hours
>
> request FSL2 "(.*000Hour)" idd.unidata.ucar.edu
> the rest of the time

There is ** IF ** there is a part of the Product IDs that will match only
every 6 hours.

Also, your REQUEST could be written more compactly as:

request FSL2 "00[0123456]Hour" idd.unidata.ucar.edu

Assuming that you are trying to get the HRRR data, then one of the last fields
looks to be the date/time in the form CCYYMMDDYHHMM. Here is a portion of a 
'notifyme'
output that shows some of the Product IDs:

Feb 26 00:19:12 notifyme[29468] INFO:   687326 20130225232621.583    FSL2 000  
GRIB2.FSL.HRRR.1905141_Lambert.006Hour.REFC.EA.201302252100.*
Feb 26 00:19:12 notifyme[29468] INFO:   430611 20130225232621.596    FSL2 000  
GRIB2.FSL.HRRR.1905141_Lambert.006Hour.BMIXL.CloudTop.201302252100.*
Feb 26 00:19:12 notifyme[29468] INFO:   429679 20130225232621.602    FSL2 000  
GRIB2.FSL.HRRR.1905141_Lambert.006Hour.5WGH.CloudTop.201302252100.*
Feb 26 00:19:12 notifyme[29468] INFO:  1285428 20130225232621.614    FSL2 000  
GRIB2.FSL.HRRR.1905141_Lambert.006Hour.UGWD.EA.201302252100.*
Feb 26 00:19:12 notifyme[29468] INFO:   792242 20130225232621.629    FSL2 000  
GRIB2.FSL.HRRR.1905141_Lambert.006Hour.VGWD.EA.201302252100.*
Feb 26 00:19:12 notifyme[29468] INFO:  1151492 20130225232621.640    FSL2 000  
GRIB2.FSL.HRRR.1905141_Lambert.006Hour.Vis.Surface.201302252100.*
Feb 26 00:19:12 notifyme[29468] INFO:   407617 20130225232621.651    FSL2 000  
GRIB2.FSL.HRRR.1905141_Lambert.006Hour.REFD.1000m_FHAG.201302252100.*
Feb 26 00:19:12 notifyme[29468] INFO:  1006365 20130225232621.666    FSL2 000  
GRIB2.FSL.HRRR.1905141_Lambert.006Hour.MAXUD_1Hour_Missing.40000Pa_to_100000Pa_Isobaric.201302252100.*
Feb 26 00:19:13 notifyme[29468] INFO:   964431 20130225232621.678    FSL2 000  
GRIB2.FSL.HRRR.1905141_Lambert.006Hour.CNWAT_1Hour_Missing.40000Pa_to_100000Pa_Isobaric.201302252100.*
Feb 26 00:19:13 notifyme[29468] INFO:   516072 20130225232621.687    FSL2 000  
GRIB2.FSL.HRRR.1905141_Lambert.006Hour.GVV_1Hour_Missing.50_to_80_Sigma.201302252100.*
Feb 26 00:19:13 notifyme[29468] INFO:   625413 20130225232621.694    FSL2 000  
GRIB2.FSL.HRRR.1905141_Lambert.006Hour.PMSL.MSL.201302252100.*
 ...

I believe that you could fashion two ~ldm/etc/ldmd.conf REQUEST lines that would
do what you want (two are needed, not one):

# Get the 0 hour forecasts whenever they are available
request FSL2 "000Hour\." idd.unidata.ucar.edu

# Get the 1-6 hour forecasts every 6 hours
request FSL2 "00[123456]Hour\..*2013....(00|06|12|18)" idd.unidata.ucar.edu

I think that this will work, but, of course, the patterns need testing.

re:
> this dataset is roughly every hour, and say every 6 we want to pull the
> forecast ones in addition to the actual, but not all the time....

I understand.  Try the example above, and please let us know if it works
the way you want/need.

re;
> Thanks for your help

No worries.

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: SYG-389000
Department: Support IDD
Priority: Normal
Status: Closed