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

20041229: 20041228: HDS products

Tom,

All the CONDUIT patterns were changes back in November.
This is now "MT.nam" in the pattern below. Also, you
would need to check your ldmd.conf. This change was made 
due to the NWS changing the names on theiur file servers.

Steve Chiswell
Unidata User Support


>From: "Thomas L. Mote" <address@hidden>
>Organization: UCAR/Unidata
>Keywords: 200412291602.iBTG2jlI009341

>This is a multi-part message in MIME format.
>--------------030406040308010101060002
>Content-Type: text/plain; charset=us-ascii; format=flowed
>Content-Transfer-Encoding: 7bit
>
>
>Steve,
>
>How will the header changes affect CONDUIT. You gave me
>a pqact entry for CONDUIT that looks like:
>
>CONDUIT MT.eta_CY.(..)/RD.(........)/.*/fh.(....)_(.*) !(.*)!
>        FILE    data/conduit/\2\1F\3_\4
>
>
>Will this need to change as well?
>
>
>
>Steve Chiswell wrote:
>
>>Mike,
>>
>>Our DVB-S test noaaport ingest system was restarted yesterday which
>>allowed some products from the current nwstg channel with new 
>>/m metatags in the HDS data stream.
>>
>>I have restored the system and the tags should be as previous.
>>
>>Now, since the subject has been brought up...
>>
>>At present, the ETA products in the HDS data stream have
>>a /mETA string appended to the LDM product header. This will be
>>changing to /mNAM. The former AVN products (now called GFS)
>>have been tagged /mAVN and /mSSIAVN. These will change to
>>/mGFS and /mSSIGFS. We will announce a time when these headers
>>will change, which will be implemented at all the ingest locations for
>>HDS within the IDD.
>>
>>In the mean time, if you currently have patterns with /mETA, you can
>>update these to /m(ETA|NAM) to work under either convention.
>>Similarly, /m(AVN|SSIAVN) can be updated to /m(AVN|SSIAVN|GFS|SSIGFS).
>>
>>
>>Steve Chiswell
>>Unidata User Support
>>
>>
>>
>>
>>
>>On Tue, 2004-12-28 at 11:32, Mike Voss wrote:
>>  
>>
>>>Has the HDS data feed has changed recently. I'm not decoding 
>>>any of the ETA or AVN grids since 12/28 at 00Z. I have done limited 
>>>trouble shooting because I'm on vacation, but at least I know the HDS 
>>>feed is flowing, my disks aren't full, all my other data is being filed 
>>>and decoded properly.
>>>
>>>So, before I waste time, I thought I would check to see if anything has 
>>>changed. I know the Conduit feed changed the ETA to NAM and AVN to GFS, 
>>>but the HDS names stayed the same, yes?
>>>
>>>thanks,
>>>-Mike
>>>
>>>--------------------------
>>>Mike Voss 
>>>Department of Meteorology 
>>>San Jose State University 
>>>One Washington Square 
>>>San Jose, CA 95192-0104
>>>
>>>408.924.5204 voice
>>>408.924.5191 fax
>>>    
>>>
>>
>>  
>>
>
>-- 
>
>Thomas L. Mote, Associate Professor
>Graduate Coordinator
>Department of Geography 
>University of Georgia
>Athens, GA 30602-2502 USA
>
>e-mail: address@hidden
>voice:   706-542-2906
>lab:     706-542-6060
>fax:     706-542-2388
>
>
>--------------030406040308010101060002
>Content-Type: text/html; charset=us-ascii
>Content-Transfer-Encoding: 7bit
>
><!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
><html>
><head>
>  <meta http-equiv="Content-Type" content="text/html;charset=ISO-8859-1">
>  <title></title>
></head>
><body text="#000000" bgcolor="#ffffff">
><br>
>Steve,<br>
><br>
>How will the header changes affect CONDUIT. You gave me<br>
>a pqact entry for CONDUIT that looks like:<br>
><br>
>CONDUIT MT.eta_CY.(..)/RD.(........)/.*/fh.(....)_(.*) !(.*)!<br>
>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; FILE&nbsp;&nbsp;&nbsp; data/conduit
> /\2\1F\3_\4<br>
><br>
><br>
>Will this need to change as well?<br>
><br>
><br>
><br>
>Steve Chiswell wrote:<br>
><blockquote type="cite"
> cite="address@hidden">
>  <pre wrap="">Mike,
>
>Our DVB-S test noaaport ingest system was restarted yesterday which
>allowed some products from the current nwstg channel with new 
>/m metatags in the HDS data stream.
>
>I have restored the system and the tags should be as previous.
>
>Now, since the subject has been brought up...
>
>At present, the ETA products in the HDS data stream have
>a /mETA string appended to the LDM product header. This will be
>changing to /mNAM. The former AVN products (now called GFS)
>have been tagged /mAVN and /mSSIAVN. These will change to
>/mGFS and /mSSIGFS. We will announce a time when these headers
>will change, which will be implemented at all the ingest locations for
>HDS within the IDD.
>
>In the mean time, if you currently have patterns with /mETA, you can
>update these to /m(ETA|NAM) to work under either convention.
>Similarly, /m(AVN|SSIAVN) can be updated to /m(AVN|SSIAVN|GFS|SSIGFS).
>
>
>Steve Chiswell
>Unidata User Support
>
>
>
>
>
>On Tue, 2004-12-28 at 11:32, Mike Voss wrote:
>  </pre>
>  <blockquote type="cite">
>    <pre wrap="">Has the HDS data feed has changed recently. I'm not decoding 
>any of the ETA or AVN grids since 12/28 at 00Z. I have done limited 
>trouble shooting because I'm on vacation, but at least I know the HDS 
>feed is flowing, my disks aren't full, all my other data is being filed 
>and decoded properly.
>
>So, before I waste time, I thought I would check to see if anything has 
>changed. I know the Conduit feed changed the ETA to NAM and AVN to GFS, 
>but the HDS names stayed the same, yes?
>
>thanks,
>-Mike
>
>--------------------------
>Mike Voss 
>Department of Meteorology 
>San Jose State University 
>One Washington Square 
>San Jose, CA 95192-0104
>
>408.924.5204 voice
>408.924.5191 fax
>    </pre>
>  </blockquote>
>  <pre wrap=""><!---->
>  </pre>
></blockquote>
><br>
><pre class="moz-signature" cols="72">-- 
>
>Thomas L. Mote, Associate Professor
>Graduate Coordinator
>Department of Geography 
>University of Georgia
>Athens, GA 30602-2502 USA
>
>e-mail: <a class="moz-txt-link-abbreviated" href="mailto:address@hidden";>tmote@
> uga.edu</a>
>voice:   706-542-2906
>lab:     706-542-6060
>fax:     706-542-2388</pre>
></body>
></html>
>
>--------------030406040308010101060002--
>
--
NOTE: All email exchanges with Unidata User Support are recorded in the
Unidata inquiry tracking system and then made publicly available
through the web.  If you do not want to have your interactions made
available in this way, you must let us know in each email you send to us.