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

RE: [Support #FIR-658958]: RE: 20060221: 20060216: problems with CONDUIT feed from idd.unidata.ucar.edu



Title: RE: [Support #FIR-658958]: RE: 20060221: 20060216: problems with CONDUIT feed from idd.unidata.ucar.edu

I am trying to request every 3 hours out to 27 hours, then every 6 after that.   I am using this, but it isn't working I still get data every 3 hours:

MT.gfs_CY.(00|12).*DF.gr1/fh.(00[0-2][0-9]|[0-9][0-9][02468]).*[02468]$
MT.gfs_CY.(00|12).*DF.gr1/fh.(00[0-2][0-9]|[0-9][0-9][02468]).*[13579]$

Where did I mess up here?

Thanks,
Robert Mullenax





-----Original Message-----
From: Unidata CONDUIT Support [mailto:address@hidden]
Sent: Wed 2/22/2006 11:10 AM
To: Robert Mullenax
Subject: [Support #FIR-658958]: RE: 20060221: 20060216: problems with CONDUIT feed from idd.unidata.ucar.edu

Robert,

To just request the 0Z and 12Z one degree CONDUIT grids, you can use a request line pattern:
MT.gfs_CY.(00|12).*onedeg

To split the feeds 2 ways, you can do odd/even on the sequence number at the end of the name:
MT.gfs_CY.(00|12).*onedeg.*[02468]$
MT.gfs_CY.(00|12).*onedeg.*[13579]$

Your request below matching on all DF.gr1 will include the 2.5 degree grids from
192 through 384 hours. If you want those (separated out from the onedeg, then add the pattern:
MT.gfs_CY.(00|12).*2p5deg

Also, just to throw in 2 cents here, your LDM version of 6.0.14 is quite old. Is there a reason you are not
updating (I know you are just returning, so it might be on your todo list)? The current distribution is much
more efficient according to Steve.

Steve Chiswell
Unidata User Support

Ticket Details
===================
Ticket ID: FIR-658958
Department: Support CONDUIT
Priority: Normal
Status: Closed