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

20040719: 20040719: sending EXP data to another LDM server

Ying,

Sorry, my typo. Don't use pqing (which is meant to read WMO format bulletins).
Instead, use pqinsert which will insert a file into the queue.


Steve Chiswell
Unidata User Support






>From: address@hidden
>Organization: UCAR/Unidata
>Keywords: 200407192318.i6JNIDaW001884

>Hi Steve,
>
>Thanks a lot !
>I store the files38077g35.hdr, 38077g35.sdw, 38077g35.sid  at ~/data/doqq/, an
> d use the pqing as below
>for file 38077g35.sid
>[ldm@unidata doqq]$ ~/bin/pqing -v -l - -f EXP ~/data/doqq/38077g35.sid
>It returns:
>Jul 19 22:32:32 pqing[31751]: Starting Up
>Jul 19 22:32:32 pqing[31751]: FILE "/usr/local/ldm/data/doqq/38077g35.sid"
>Jul 19 22:32:32 pqing[31751]: Lone SOH error                          3
>Jul 19 22:32:32 pqing[31751]: scan_wmo: length 5 too short
>Jul 19 22:32:32 pqing[31751]: Lone ETX error                        108       
>   -01   X Q00      192232
>Jul 19 22:32:32 pqing[31751]: Lone SOH error                         33       
>   -01      00      192232
>Jul 19 22:32:32 pqing[31751]: Lone SOH error                         25       
>   -01      00      192232
>Jul 19 22:32:32 pqing[31751]: Lone SOH error                          5       
>   -01      00      192232
>Jul 19 22:32:32 pqing[31751]: Lone SOH error                          5       
>   -01      00      192232
>Jul 19 22:32:32 pqing[31751]: Lone SOH error                          2
>Jul 19 22:32:32 pqing[31751]: Lone SOH error                          3
>Jul 19 22:32:32 pqing[31751]: scan_wmo: length 3 too short
>Jul 19 22:32:32 pqing[31751]: Lone SOH error                          2
>Jul 19 22:32:32 pqing[31751]: Lone SOH error                          7       
>   -01      00      192232
>Jul 19 22:32:32 pqing[31751]: Lone SOH error                          5       
>   -01      00      192232
>Jul 19 22:32:32 pqing[31751]: Lone SOH error                          6       
>   -01      00      192232
>Jul 19 22:32:32 pqing[31751]: scan_wmo: length 16 too short
>Jul 19 22:32:32 pqing[31751]: Lone SOH error                          3
>Jul 19 22:32:32 pqing[31751]: scan_wmo: length 14 too short
>...
>...
>
>for file 38077g35.hdr, it returns
>[ldm@unidata doqq]$ ~/bin/pqing -v -l - -f EXP ~/data/doqq/38077g35.hdr
>Jul 19 22:47:42 pqing[31754]: Starting Up
>Jul 19 22:47:42 pqing[31754]: FILE "/usr/local/ldm/data/doqq/38077g35.hdr"
>Jul 19 22:47:42 pqing[31754]: Expanding input buffer size to 32768
>Jul 19 22:47:42 pqing[31754]: Exiting
>Jul 19 22:47:42 pqing[31754]:   Queue usage (bytes):1048576000
>Jul 19 22:47:42 pqing[31754]:            (nregions):  182025
>Jul 19 22:47:42 pqing[31754]:   Duplicates rejected:       0
>Jul 19 22:47:42 pqing[31754]:   WMO Messages seen:         0
>Jul 19 22:47:42 pqing[31754]:   SOH/ETX missing  :         0
>Jul 19 22:47:42 pqing[31754]:   parity/chksum err:         0
>Jul 19 22:47:42 pqing[31754]:   WMO format errors:         0
>Jul 19 22:47:42 pqing[31754]:   FILE Bytes read:       18696
>
>for file 38077g35.swd, similar to the previous result.
>
>when I type notifyme, it is:
>[ldm@unidata doqq]$ ~/bin/notifyme -vxl- -f EXP -h unidata.scs.gmu.edu
>Jul 19 22:48:42 notifyme[31755]: Starting Up: unidata.scs.gmu.edu: 20040719224
> 842.487 TS_ENDT {{EXP,  ".*"}}
>Jul 19 22:48:42 notifyme[31755]: Connected to upstream LDM-5
>        NOTIFYME(unidata.scs.gmu.edu) returns OK
>Jul 19 22:48:42 notifyme[31755]: NOTIFYME(unidata.scs.gmu.edu): OK
>
>Did I successfully pqing the files?  Anything wrong?
>
>Another question is,  does it mean everytime I get a new file from i.e. antenn
> a, I need to pqing it to product queue manually? Is  there any way to insert 
> it automatically once I put it under a certain folder?
>
>Sorry for so many questions and thank you very much for you help!
>
>Ying
>
>
>
>
>----- Original Message -----
>From: Unidata Support <address@hidden>
>Date: Monday, July 19, 2004 2:37 pm
>Subject: 20040719: sending EXP data to another LDM server
>
>> 
>> Ying,
>> 
>> You can use a single "pqinsert" command to insetyour 3 files in your 
>> list.
>> The LDM product name of these files will be file name (uless you
>> specify anothr name). If you specify a full path to the files,
>> then that would be part of the name as well. You can use the
>> notifyme command to seee that the files are in your local queue.
>> 
>> To receive the files at another LDM, you should:
>> 
>> 1) Makefile sure your ~ldm/etc/ldmd.conf file has an allow line
>> for the other LDM host. Ensure that EXP is part of the feedtype
>> lit that you are allowing that host to receive.
>> 
>> 2) On the other LDM, make sure the ~ldm/etc/ldmd.conf
>> has a "request" line for the EXP feedtype from your ldm.
>> You can either use the ".*" pattern to match all EXP products,
>> or a pattern of file names to request. 
>> 
>> 3) On this LDM, you can have pqact.conf actions to automatically
>> process the files as they arrive.
>> 
>> Thats it.....
>> 
>> 
>> Steve Chiswell
>> Unidata User Support
>> 
>> 
>> >From: address@hidden
>> >Organization: UCAR/Unidata
>> >Keywords: 200407191635.i6JGZ3aW023824
>> 
>> >Hello,
>> >
>> >I've got LDM running well and am trying to send our own data 
>> (DOQQ) to another
>> >  LDM server as EXP data. But I'm not sure about the whole 
>> process. 
>> >For example, the data is in three related files:  
>> >38077g35.hdr, 
>> >38077g35.sdw, 
>> >38077g35.sid
>> >Do I need to write three "pqinsert" commands to insert them to 
>> product queue?
>> >
>> >How can I make the data automatically arrive at another LDM 
>> server once I put 
>> > new data into corresponding directory on my server? Anything I 
>> need to add in
>> >  pqact.conf, etc?
>> >
>> >Thank you in advance for your help!
>> >
>> >Ying 
>> >
>> >
>> >
>> >
>> --
>> ****************************************************************************
>> Unidata User Support                                    UCAR 
>> (303)497-8643                                                  
>> address@hidden                                   
>> -------------------------------------------------------------------
>> Unidata WWW Service              
>> -------------------------------------------------------------------
>> NOTE: All email exchanges with Unidata User Support are recorded 
>> in the
>> Unidata inquiry tracking system and then made publically 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 publically 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.