[Ncep.list.pmb-dataflow] Re: [Fwd: Re: [Fwd: Administrative, EUMETSAT Swap of Meteosat-9 and Meteosat-8 12/1/08 to 12/9/08 - Issued 12/1/08]]

Paula Freeman paula.freeman at noaa.gov
Fri Dec 5 11:42:00 EST 2008


So, do we still put it in for next time, just not as a crisis?

-p


Bill Lapenta said:
> Greetings--
>
> Word from Russ Treadon is that the operational global system (and the
> NCO parallel) does not assimilate Meteosat-9 satellite derived winds.
> We only monitor those data. Therefore, the absence of this data has no
> operational impact on the GDAS/GFS.
>
> A Crisis RFC will NOT be required.
>
> Regards,
> Bill


Jeff Ator wrote:
> Paula,
>
> Thanks for forwarding this along.  We've still been receiving the 
> (^I[UX]C[NS](0[1-9]|[12][0-9]) EUMS) products since the 2nd, which 
> explains the lesser amount of data that I mentioned I was seeing in 
> the tanks (as opposed to no data at all) during the 9am meeting.  I 
> believe these may be lower-resolution products, whereas the 
> ^I[UW]V[ADEHIL]..EUMG products are high-resolution and may be the only 
> ones that EMC is looking for(?)  Either way, once decoded they all go 
> into the same b005/xx06[4-6] tanks in /dcom.  If the decision is to 
> make a change to begin routing the "W" bulletins via DBNet and pqact, 
> the decoder should work just fine without any adjustment.
>
> -Jeff
>
> Paula Freeman wrote:
>> Sorry Jeff, I thought you were on this thread.
>> -p
>>
>>
>> -------- Original Message --------
>> Subject:     Re: [Fwd: Administrative, EUMETSAT Swap of Meteosat-9 
>> and Meteosat-8 12/1/08 to 12/9/08 - Issued 12/1/08]
>> Date:     Fri, 05 Dec 2008 07:40:07 -0500
>> From:     Brent A Gordon <Brent.Gordon at noaa.gov>
>> To:     Paula Freeman <Paula.Freeman at noaa.gov>
>> CC:     Justin Cooke <justin.cooke at noaa.gov>, Dennis Keyser 
>> <Dennis.Keyser at noaa.gov>, Michelle Mainelli 
>> <Michelle.M.Mainelli at noaa.gov>, Joey Carr <Joe.Carr at noaa.gov>
>> References:     <4935B4F8.7050200 at noaa.gov> 
>> <3BDEFF52-BE34-4F94-9A65-51ED167F4BF0 at noaa.gov> 
>> <493678F1.1020501 at noaa.gov> <49367D0F.6000407 at noaa.gov> 
>> <49391E81.3010806 at noaa.gov>
>>
>>
>>
>> Dennis,
>>
>> Basically we need you to confirm that the models will be ok using 
>> this data.
>>
>> Brent
>>
>> Paula Freeman wrote:
>>> Dennis, et al,
>>>
>>> Should we proceed with sending the W products to the decod_dcelrw 
>>> decoder?  It's swapped back on the 9th, but if we did it Monday at 
>>> least we'd be able to see if the replacement products look good. And 
>>> MAYBE we'll be prepared for next time!
>>>
>>> -paula
>>>
>>>
>>>
>>> Paula Freeman wrote:
>>>> Ah, we are getting the W products but they are not getting to ldm.
>>>> If we route them to ldm, they won't go to the decod_dcelrw decoder 
>>>> as the U products do.  Is that what we need to do?
>>>>
>>>> In parsing.tbl, replace:
>>>> WMOMSG  ^IUV[ADEHIL]..EUMG    .*    WC76_WMOMSG
>>>> with:
>>>> WMOMSG  ^I[UW]V[ADEHIL]..EUMG    .*    WC76_WMOMSG
>>>>
>>>> And in pqact.conf, replace:
>>>>
>>>> #
>>>> HDS     (^I[UX]C[NS](0[1-9]|[12][0-9]) 
>>>> EUMS)|(^IUC[NS](4[1-6]|[57][1-9]|[69][0-5]|8[0-9]) 
>>>> RJTD)|(^IUV[ADEHIL].. EUMG)
>>>>        PIPE    /nwprod/exec/decod_dcelrw  -v 2  -t 300  -d 
>>>> /dcom/us007003/decoder_logs/decod_dcelrw.log
>>>>                /nwprod/fix/bufrtab.EUMS_SATWIND
>>>>                /nwprod/fix/bufrtab.JAPAN_SATWIND
>>>>                /nwprod/fix/bufrtab.005
>>>>
>>>> With this:
>>>> HDS     (^I[UX]C[NS](0[1-9]|[12][0-9]) 
>>>> EUMS)|(^IUC[NS](4[1-6]|[57][1-9]|[69][0-5]|8[0-9]) 
>>>> RJTD)|(^I[UW]V[ADEHIL].. EUMG)
>>>>        PIPE    /nwprod/exec/decod_dcelrw  -v 2  -t 300  -d 
>>>> /dcom/us007003/decoder_logs/decod_dcelrw.log
>>>>                /nwprod/fix/bufrtab.EUMS_SATWIND
>>>>                /nwprod/fix/bufrtab.JAPAN_SATWIND
>>>>                /nwprod/fix/bufrtab.005
>>>>
>>>> ?
>>>>
>>>> -Paula
>>>>
>>>>
>>>> Paula Freeman wrote:
>>>>> We are getting the replacement product IWVH15 EUMG.
>>>>>
>>>>> -Paula
>>>>>
>>>>> Justin Cooke wrote:
>>>>>> Dennis,
>>>>>>
>>>>>> The last successful receipt of the product IUVH15 EUMG by us was 
>>>>>> at 1127Z on 12/01/2008.
>>>>>>
>>>>>> Paula, can you check FADD to see if this product is updating and 
>>>>>> just not being routed to us?
>>>>>>
>>>>>> Thanks,
>>>>>> Justin
>>>>>>
>>>>>> On Dec 2, 2008, at 5:21 PM, Dennis Keyser wrote:
>>>>>>
>>>>>>> Hi all,
>>>>>>>
>>>>>>> EUMETSAT did another one of their METEOSAT-9/METEOSAT-8 swaps 
>>>>>>> yesterday (see attached).  Once again, we are not picking up 
>>>>>>> METEOSAT-8.  Recall this also happened on two previous 
>>>>>>> occasions, but we had thought that everything was corrected 
>>>>>>> after the last case (almost exactly 1 year ago) such that we 
>>>>>>> would get the METEOSAT-8 headers and decode them.   That doesn't 
>>>>>>> appear to be the case.
>>>>>>>
>>>>>>> Thanks,
>>>>>>> Dennis
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> On 12/13/2007 8:19 PM, Brent A. Gordon wrote:
>>>>>>>> Simon,
>>>>>>>>
>>>>>>>> Thanks for the information.  This is a bit humbling for us as 
>>>>>>>> we are usually in the position where we are "apologizing" for 
>>>>>>>> our users not paying attention to our notices!
>>>>>>>>
>>>>>>>> At least we should be ready if this happens again.
>>>>>>>>
>>>>>>>> Cheers,
>>>>>>>>
>>>>>>>> Brent
>>>>>>>>
>>>>>>>> Walter Mussante wrote:
>>>>>>>>> Justin,
>>>>>>>>> So the mystery is solved. The headings were changed and we are 
>>>>>>>>> not routing those headings to NCEP.
>>>>>>>>> Walt M
>>>>>>>>>
>>>>>>>>> Simon Elliott wrote:
>>>>>>>>>> Dear all,
>>>>>>>>>>
>>>>>>>>>> during the period in question MET8 products indeed replaced 
>>>>>>>>>> those from MET9.
>>>>>>>>>>
>>>>>>>>>> In order to make the necessary routing changes as simple as 
>>>>>>>>>> possible we used distinct abbreviated headers for the MET8 
>>>>>>>>>> data during this period, where T2 was set to "W".  That means 
>>>>>>>>>> that the MET8 wind data were in headers named like this:
>>>>>>>>>> IWV[ADEHIL]..EUMG
>>>>>>>>>>
>>>>>>>>>> This was explained in various announcements, via our web site 
>>>>>>>>>> (see 
>>>>>>>>>> http://www.eumetsat.int/Home/Main/Access_to_Data/index.htm 
>>>>>>>>>> under 3/12/07 and 12/12/07), and was the subject of a GTS 
>>>>>>>>>> service message which you should have received via RTH 
>>>>>>>>>> Washington.
>>>>>>>>>>
>>>>>>>>>> I can only apologise that we didn't get the message across 
>>>>>>>>>> clearly enough.
>>>>>>>>>>
>>>>>>>>>> Regards,
>>>>>>>>>>
>>>>>>>>>> Simon
>>>>>>>>>>
>>>>>>>>>> Dr Simon Elliott
>>>>>>>>>> Product Implementation Manager
>>>>>>>>>> Operations Department
>>>>>>>>>> EUMETSAT
>>>>>>>>>> tel: (+49) 6151 807385
>>>>>>>>>> fax: (+49) 6151 807304
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>  
>>>>>>>>>>>>> Dennis Keyser <Dennis.Keyser at noaa.gov> 13/12/2007 15:26 >>>
>>>>>>>>>>>>>         
>>>>>>>>>> Perhaps also Simon Elliott - he is the only contact I have at 
>>>>>>>>>> EUMETSAT.
>>>>>>>>>>
>>>>>>>>>> Dennis
>>>>>>>>>>
>>>>>>>>>> On 12/13/2007 8:52 AM, Brent A Gordon wrote:
>>>>>>>>>>  
>>>>>>>>>>> The only person I know there is Kenneth Holmlund 
>>>>>>>>>>> (Kenneth.Holmlund at eumetsat.int).  He is very active in the 
>>>>>>>>>>> North America - European data exchange group, so he should 
>>>>>>>>>>> be able to either answer your question or direct you to 
>>>>>>>>>>> someone who can.
>>>>>>>>>>>
>>>>>>>>>>> Brent
>>>>>>>>>>>
>>>>>>>>>>> Justin Cooke wrote:
>>>>>>>>>>>  
>>>>>>>>>>>> Brent, Dennis, or Chris,
>>>>>>>>>>>>
>>>>>>>>>>>> Do we have any contacts at EUMETSAT that we can give the 
>>>>>>>>>>>> TOC to try and get to the bottom of the MET-8/MET-9 switch 
>>>>>>>>>>>> problem?
>>>>>>>>>>>>
>>>>>>>>>>>> Thanks,
>>>>>>>>>>>> Justin
>>>>>>>>>>>>
>>>>>>>>>>>> Walter Mussante wrote:
>>>>>>>>>>>>  
>>>>>>>>>>>>> Justin,
>>>>>>>>>>>>>
>>>>>>>>>>>>> I've checked our logs and there is no evidence that we 
>>>>>>>>>>>>> received these products, correctly or incorrectly. Does 
>>>>>>>>>>>>> the UKMET believe they sent them to us? I don't think 
>>>>>>>>>>>>> we're going to know what happened. But, for the future, 
>>>>>>>>>>>>> can this be tested or can we at least be notified when 
>>>>>>>>>>>>> MET-8 will be in use again so we troubleshoot it 
>>>>>>>>>>>>> immediately  instead of trying to do it after the fact.
>>>>>>>>>>>>>
>>>>>>>>>>>>> Thanks,
>>>>>>>>>>>>> Walt
>>>>>>>>>>>>>
>>>>>>>>>>>>> Justin Cooke wrote:
>>>>>>>>>>>>>    
>>>>>>>>>>>>>> Hi Richard,
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Sending these products only over line 292 is fine. But it 
>>>>>>>>>>>>>> still doesn't explain why we had the two week outage... 
>>>>>>>>>>>>>> Are there any logs you can check to see if TOC was 
>>>>>>>>>>>>>> receiving the IUV[ADEHIL].. headers from 12/03/07 to 
>>>>>>>>>>>>>> 12/12/07?
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Thanks,
>>>>>>>>>>>>>> Justin
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Richard Robinson wrote:
>>>>>>>>>>>>>>      
>>>>>>>>>>>>>>> Hello Justin,
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>    I had check the routing of the products which are all 
>>>>>>>>>>>>>>> on line 292 only, should have the products been listed 
>>>>>>>>>>>>>>> on both 291 and 292 for distribution.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Justin Cooke wrote:
>>>>>>>>>>>>>>>        
>>>>>>>>>>>>>>>> Sue, Richard, and Walter,
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> >From 12/03/2007 to 12/12/2007 EUMETSAT replaced 
>>>>>>>>>>>>>>>> satellite output from MET-9 with MET-8. But during that 
>>>>>>>>>>>>>>>> entire time we didn't receive any of the expected 
>>>>>>>>>>>>>>>> headers,  here is the regular expression we used:
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> ^IUV[ADEHIL]..EUMG
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> All products have the EUMG originator. Late yesterday I 
>>>>>>>>>>>>>>>> did a search for IUVH15 EUMG in FADD but this product, 
>>>>>>>>>>>>>>>> like all other MET-9 products only started being 
>>>>>>>>>>>>>>>> received yesterday after MET-9 came back into service. 
>>>>>>>>>>>>>>>> Are you able to receive these datasets when MET-8 is 
>>>>>>>>>>>>>>>> acting for MET-9.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Here is a description of the work EUMETSAT performed:
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> http://oiswww.eumetsat.org/UNS/webapps/showData.do?type=4
>>>>>>>>>>>>>>>> Thanks,
>>>>>>>>>>>>>>>> Justin
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>               
>>>>>>>>>>   
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> *From: *Brian Hughes <Brian.Hughes at noaa.gov 
>>>>>>> <mailto:Brian.Hughes at noaa.gov>>
>>>>>>> *Date: *December 1, 2008 8:56:22 AM EST
>>>>>>> *To: *Brian Hughes <Brian.Hughes at noaa.gov 
>>>>>>> <mailto:Brian.Hughes at noaa.gov>>
>>>>>>> *Subject: **Administrative, EUMETSAT Swap of Meteosat-9 and 
>>>>>>> Meteosat-8 12/1/08 to 12/9/08 - Issued 12/1/08*
>>>>>>>
>>>>>>>
>>>>>>>  Topic: EUMETSAT Swap of Meteosat-9 and Meteosat-8: December 
>>>>>>> 1-9, 2008
>>>>>>> Message Issued: December 1, 2008, 1400 UTC
>>>>>>> Satellites Impacted: Meteosat-9 and Meteosat-8
>>>>>>> Products Impacted: All Meteosat-9 data and products from NOAA, 
>>>>>>> including
>>>>>>> the Meteosat-9 DOMSAT Service
>>>>>>> Date/Time of Initial Impact: December 1, 2008  1200 UTC
>>>>>>> --------------------------
>>>>>>> Details:
>>>>>>>
>>>>>>> NOAA has received the following bulletin from EUMETSAT:
>>>>>>>
>>>>>>> ------
>>>>>>> Meteosat Prime Service During Meteosat-9 Spacecraft Decontamination
>>>>>>>
>>>>>>> As part of routine spacecraft operations, a Meteosat-9 spacecraft
>>>>>>> decontamination will be performed between 1 - 9 December 2008. 
>>>>>>> During
>>>>>>> this period the Meteosat-9 SEVIRI Image and Meteorological Product
>>>>>>> services will be unavailable and will be replaced by the equivalent
>>>>>>> services from Meteosat-8. Meteosat-8 data will be rectified to 0 
>>>>>>> degrees
>>>>>>> during the decontamination period.
>>>>>>>
>>>>>>> ------
>>>>>>>
>>>>>>> The period of Meteosat-8 data to take the place of Meteosat-9 is
>>>>>>> scheduled from December 1, 2008 at 1200 UTC to December 9, 2008 
>>>>>>> at 1200 UTC.
>>>>>>>
>>>>>>> NOAA retransmission of encrypted Meteosat data, uplinked from the
>>>>>>> Wallops Command and Data Acquisition Station, should not be 
>>>>>>> affected.
>>>>>>> For users accessing Meteosat data via DOMSAT, NOAA will forward the
>>>>>>> Meteosat-8 encryption keys prior to the start of the planned 
>>>>>>> Meteosat-8
>>>>>>> swap (December 1, 2008 at 1200 UTC)
>>>>>>>
>>>>>>> Meteosat-8 data will be rectified to 0 degrees during the
>>>>>>> decontamination period.
>>>>>>>
>>>>>>> More information can be found at:
>>>>>>> http://www.eumetsat.int/Home/Main/Media/News/707918?l=en
>>>>>>>
>>>>>>> Assignment of GTS Bulletin headers for Meteosat-8 products can 
>>>>>>> be found
>>>>>>> at:
>>>>>>> http://www.eumetsat.int/groups/ops/documents/document/pdf_gts_bulletinheaders_decont.pdf 
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> ---------------------------
>>>>>>> Contact Information:
>>>>>>> Brian Hughes
>>>>>>> Satellite Services Division
>>>>>>> NOAA/NESDIS/OSDPD
>>>>>>> 301-763-8051 x106
>>>>>>> Brian.Hughes at noaa.gov <mailto:Brian.Hughes at noaa.gov>
>>>>>>>
>>>>>>> See http://www.ssd.noaa.gov/PS/SATS/messages.html  for this and 
>>>>>>> other
>>>>>>> satellite related messages.
>>>>>>> See http://www.ssd.noaa.gov for full GOES scanning schedules.
>>>>>>>
>>>>>>>
>>>>>>> <Dennis_Keyser.vcf>
>>>>>>
>>>>>
>>>>
>>


More information about the Ncep.list.pmb-dataflow mailing list