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

20050721: 20050720: LDM feed CMC



John,

The request line looks fine. You do not need the accept line, since the
connection is initiated at your end, and not the other.

Did you restart your ldm after modifying the ldmd.conf file?
After that, you should see some log messages in ldmd.log about
the connection to the CMC LDM which will tell you if it was
sucessful or not. 

You can use notifyme to test your connection and see the data,
such as:
% notifyme -v -l - -o 999999 -f CMC -h ldm.meteo.ec.gc.ca

The GEM model data should appear twice per day, around 16:01Z for
the 12Z run and around 4:21Z for the 00Z run.

For your pqact.conf action, you will have problems though, since
the files are named:
/home/wxofeed/data/dd/ldmfeed/CMC_GEM_reg_ww_L150_2005071800_P12.grib

The request line will match the CMC_GEM_reg_, but your pqact.conf pattern
is matching the entire (.*) name which is a directory path that
starts with /home/wxofeed/data/dd/ldmfeed/, which you probably dont want.
You probably want a pattern such as:
CMC     (CMC_GEM_reg_.*)

If you do that, you are going to get separate files for every parameter/level,
whereas if you use the pattern I suggested yesterday, your have one file
for each forecast time.

Steve Chiswell
Unidata User Support




>From: "John Cangialosi" <address@hidden>
>Organization: UCAR/Unidata
>Keywords: 200507211518.j6LFICjo008568

>Hi,
>
>
>This is John from the University of Miami.  I recently got access to CMC
>GEM data.
>
>Here is what I have set up for the CMC data, but its not working.
>
>ldmd.conf:
>
>REQUEST CMC    "CMC_GEM_reg_" ldm.meteo.ec.gc.ca
>
>ACCEPT  CMC     (.*) ^ldm\.meteo\.ec\.gc\.ca\.?$
>
>pqact.conf
>
># Canadian GEM data
>CMC        (.*)
>        FILE        /home/dusky/ldm/data/raw/cmc/\1
>
>
>Do you see anything wrong with this?
>
>Thanks,
>John Cangialosi
>
>
>
>
>
>>
>> John,
>>
>> We request the data using the following ldmd.conf entry:
>> #
>> # CMC/GEM
>> request CMC "CMC_GEM_reg_" ldm.meteo.ec.gc.ca
>>
>> You can file the data to hourly forecast files using a pqact.conf entry
>> such as:
>> # Canadian GEM data
>> CMC  CMC_GEM_reg_.*_.*_([12][0-9][0-9][0-9])([0-1][0-9])([0-3][0-9])([0-2][0
> -9])_(.*).grib
>>      FILE    data/gem/\1\2\3\4_\5.cmcgem
>>
>> Steve Chiswell
>> Unidata User Support
>>
>>
>>
>>
>>
>>>From: "John Cangialosi" <address@hidden>
>>>Organization: UCAR/Unidata
>>>Keywords: 200507201734.j6KHYbjo001017
>>
>>>Hi,
>>>
>>>This is John Cangialosi from the University of Miami.  Jeff Weber help me
>>>set obtain access to NOGAPS and CMC data
>>>
>>>
>>>I have the NOGAPS feed set up, but need a little help with CMC.
>>>
>>>Do you have any advice on how to set up the feed on our system,i.e.
>>>REQUEST info.
>>>
>>>This is grib data from the CMC model.
>>>
>>>Thanks,
>>>
>>>John Cangialosi
>>>
>>>
>>>
>>>
>>>--
>>>
>>>
>> --
>> ****************************************************************************
>> Unidata User Support                                    UCAR Unidata
>> (303)497-8643                                                  P.O. Box
>> address@hidden                                   Boulder, CO
>> ----------------------------------------------------------------------------
>> Unidata WWW Service
>> ----------------------------------------------------------------------------
>> 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.
>>
>
>
>-- 
>
>
--
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.


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.