This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.
Hi Steve, Can you please send me your current pqact.conf file.. Thank you, -Jeff ____________________________ _____________________ Jeff Weber address@hidden Unidata Support PH:303-497-8676 COMET Case Study Library FX:303-497-8690 University Corp for Atmospheric Research 3300 Mitchell Ln http://www.unidata.ucar.edu/staff/jweber Boulder,Co 80307-3000 ________________________________________ ______________________ On Fri, 25 Oct 2002, Steve Cousins wrote: > Hi Jeff, > > I did what you suggest with the notifyme command and it produces: > > Oct 25 14:44:20 notifyme[2322]: Starting Up: usgodae3.fnmoc.navy.mil: > 20021025103420.508 TS_ENDT {{NOGAPS, ".*"}} > Oct 25 14:44:20 notifyme[2322]: NOTIFYME(usgodae3.fnmoc.navy.mil): OK > Oct 25 14:44:20 notifyme[2322]: 44469 20021025142700.293 NOGAPS 000 > US058GMET-GR1mdl.0082_0020_02400F0PL2002102512_0102_000000-000000pres > Oct 25 14:44:20 notifyme[2322]: 44469 20021025142700.610 NOGAPS 000 > US058GMET-GR1mdl.0082_0020_00600F0PL2002102512_0102_000000-000000pres > . > . > . > > The clock is correct. It is using a time server at Colby College here in > Maine. I have just checked it against tycho.usno.navy.mil and it matches to > the second at least. > > However, the time that is used in the ldmd.log file seems to be GMT. I'm > assuming this is correct. > > I've changed the ldmadmin script to be able to use the -x switch for rpc.ldmd > in order to get the debugging level of logging. Here is what the ldmd.log > looks like for NOGAPS: > > Oct 25 15:20:00 rocky usgodae3[2876]: run_requester: Starting Up: > usgodae3.fnmoc.navy.mil > Oct 25 15:20:00 rocky usgodae3[2876]: run_requester: 20021025142000.909 > TS_ENDT {{NOGAPS, ".*"}} > Oct 25 15:20:01 rocky usgodae3[2876]: FEEDME(usgodae3.fnmoc.navy.mil) returns > OK > Oct 25 15:20:01 rocky usgodae3[2876]: FEEDME(usgodae3.fnmoc.navy.mil): OK > Oct 25 15:20:01 rocky usgodae3[2876]: comings: > 7bc436f5dd80ceb23b77a4872e35cfdc 44469 20021025142700.293 NOGAPS 000 > US058GMET-GR1mdl.0082_0020_02400F0PL2002102512_0102_000000-000000pres (pktsz > 8120) > Oct 25 15:20:01 rocky usgodae3[2876]: blkdata: > 7bc436f5dd80ceb23b77a4872e35cfdc 8120 0 > Oct 25 15:20:01 rocky usgodae3[2876]: blkdata: > 7bc436f5dd80ceb23b77a4872e35cfdc 8120 1 > Oct 25 15:20:01 rocky usgodae3[2876]: blkdata: > 7bc436f5dd80ceb23b77a4872e35cfdc 8120 2 > Oct 25 15:20:01 rocky usgodae3[2876]: blkdata: > 7bc436f5dd80ceb23b77a4872e35cfdc 8120 3 > Oct 25 15:20:01 rocky usgodae3[2876]: blkdata: > 7bc436f5dd80ceb23b77a4872e35cfdc 8120 4 > Oct 25 15:20:02 rocky usgodae3[2876]: blkdata: > 7bc436f5dd80ceb23b77a4872e35cfdc 3869 5 > Oct 25 15:20:02 rocky usgodae3[2876]: comings: > 4348efa3903ebadb98e484eb6842dca8 44469 20021025142700.610 NOGAPS 000 > US058GMET-GR1mdl.0082_0020_00600F0PL2002102512_0102_000000-000000pres (pktsz > 8120) > Oct 25 15:20:02 rocky usgodae3[2876]: blkdata: > 4348efa3903ebadb98e484eb6842dca8 8120 0 > Oct 25 15:20:02 rocky usgodae3[2876]: blkdata: > 4348efa3903ebadb98e484eb6842dca8 8120 1 > Oct 25 15:20:02 rocky usgodae3[2876]: blkdata: > 4348efa3903ebadb98e484eb6842dca8 8120 2 > Oct 25 15:20:02 rocky usgodae3[2876]: blkdata: > 4348efa3903ebadb98e484eb6842dca8 8120 3 > Oct 25 15:20:02 rocky usgodae3[2876]: blkdata: > 4348efa3903ebadb98e484eb6842dca8 8120 4 > Oct 25 15:20:02 rocky usgodae3[2876]: blkdata: > 4348efa3903ebadb98e484eb6842dca8 3869 5 > > Here is what it looks like for WMO: > > Oct 25 15:20:00 rocky snow[2875]: run_requester: Starting Up: > snow.nrcc.cornell.edu > Oct 25 15:20:00 rocky snow[2875]: run_requester: 20021025142000.887 TS_ENDT > {{WMO, ".*"}} > Oct 25 15:20:00 rocky snow[2875]: FEEDME(snow.nrcc.cornell.edu) returns OK > Oct 25 15:20:00 rocky snow[2875]: FEEDME(snow.nrcc.cornell.edu): OK > Oct 25 15:20:00 rocky snow[2875]: comings: af888feb7f9e1e860dac80562d0955f6 > 83108 20021025142417.084 HDS 756 YCUB99 KWBE 251200 /mETA_84 (pktsz > 16312) > Oct 25 15:20:01 rocky snow[2875]: blkdata: af888feb7f9e1e860dac80562d0955f6 > 16312 0 > Oct 25 15:20:01 rocky snow[2875]: blkdata: af888feb7f9e1e860dac80562d0955f6 > 16312 1 > Oct 25 15:20:01 rocky snow[2875]: blkdata: af888feb7f9e1e860dac80562d0955f6 > 16312 2 > Oct 25 15:20:01 rocky snow[2875]: blkdata: af888feb7f9e1e860dac80562d0955f6 > 16312 3 > Oct 25 15:20:01 rocky snow[2875]: blkdata: af888feb7f9e1e860dac80562d0955f6 > 16312 4 > Oct 25 15:20:01 rocky snow[2875]: blkdata: af888feb7f9e1e860dac80562d0955f6 > 1548 5 > Oct 25 15:20:01 rocky snow[2875]: comings: 5e77b52b4f8e93cf3ae26d40f2f8899d > 71254 20021025142417.463 HDS 767 YCUB85 KWBE 251200 /mETA_84 (pktsz > 16312) > Oct 25 15:20:01 rocky snow[2875]: blkdata: 5e77b52b4f8e93cf3ae26d40f2f8899d > 16312 0 > Oct 25 15:20:01 rocky snow[2875]: blkdata: 5e77b52b4f8e93cf3ae26d40f2f8899d > 16312 1 > Oct 25 15:20:01 rocky snow[2875]: blkdata: 5e77b52b4f8e93cf3ae26d40f2f8899d > 16312 2 > Oct 25 15:20:01 rocky snow[2875]: blkdata: 5e77b52b4f8e93cf3ae26d40f2f8899d > 16312 3 > Oct 25 15:20:01 rocky snow[2875]: blkdata: 5e77b52b4f8e93cf3ae26d40f2f8899d > 6006 4 > > > Does this look ok? The only differece that I see is that the packet size is > smaller for NOGAPS but it looks like the data is arriving. Is there any way > of finding out what is happening to the data once it gets here? > > Is there a switch to rpc.ldmd which can turn on a more verbose logging for > file access? The volume that ldm is on has 26 GB available to it and the > file permissions for the ldm01 directory are the same as for ldm02. I see no > reason why the data > shouldn't be written. > > Thanks, > > Steve > > > > address@hidden writes: > >HI Steve, > > > >Yes, the examples on the page should work.. > > > >I have eyeballed them again, and they match what my notifyme puts out: > >Oct 24 22:49:41 notifyme[10230]: 65269 20021024214800.533 FNMOC 000 > >US058GMET-GR1mdl.0058_0240_00000F0OF2002102418_0001_000000-000000snw_dpth > > > > > >What do you see when you do a: > > > >notifyme -vl - -h usgodae3.fnmoc.navy.mil -f NOGAPS -o 15000 > > > > > >This may not be pertinent since you did indicate other data was coming in, > >but is your clock right? > > > >In regards to the pqact we have: > > > >HDS|NMC2|NOGAPS|CMC ^(/afs|[HOYZ]|US058)|.*CMC_GEM_reg_).* > > PIPE decoders/dcgrib2 -d data/pub/decoded/gempak/logs/dcgrib.log > > -v 1 > > -e GEMTBL=/home/gempak/NAWIPS/gempak/tables > > > >Could be modified to: > > > >NOGAPS ^(US058*) > > PIPE decoders/dcgrib2 -d data/pub/decoded/gempak/logs/dcgrib.log -v 1 > > -e GEMTBL=/home/gempak/NAWIPS/gempak/tables > > > >But if you are not getting these other models, or even if you are, you can > >use the original..I now it works.. > > > >Keep me posted! > > > >-Jeff > >____________________________ _____________________ > >Jeff Weber address@hidden > >Unidata Support PH:303-497-8676 > >COMET Case Study Library FX:303-497-8690 > >University Corp for Atmospheric Research 3300 Mitchell Ln > >http://www.unidata.ucar.edu/staff/jweber Boulder,Co 80307-3000 > >________________________________________ ______________________ > > > >On Thu, 24 Oct 2002, Unidata Support wrote: > > > >> > >> ------- Forwarded Message > >> > >> >To: address@hidden > >> >cc: address@hidden, > >> >cc: address@hidden, > >> >cc: address@hidden > >> >From: "Steve Cousins" <address@hidden> > >> >Subject: Re: Fwd: Re: 20021004:Maine FNMOC NOGAPS Feed > >> >Organization: UCAR/Unidata > >> >Keywords: 200210241752.g9OHqsq22280 > >> > >> Hi Jeff, > >> > >> I tried putting the following in the pqact.conf file: > >> > >> NOGAPS ^US058....-.......(0058)_...._.........(....)(..)(..)(..)_(.*) > >> FILE -overwrite -close ldm02/nogaps/\2/\3/\4/\5/\1/\6 > >> # COAMPS > >> NOGAPS > >> ^US058....-.......([^0]...|0[^0]..|00[^5].|005[^8])_...._.........(....)(..)(..)(..)_(.*) > >> FILE -overwrite -close ldm02/coamps/\2/\3/\4/\5/\1/\6 > >> > >> I got this from the Unidata web site. I restarted ldm and let it run all > >> night. Still nothing in the ldm02 directory. The ldmd.log file still > >> shows multiple pairs of: > >> > >> Oct 24 17:22:20 rocky usgodae3[1678]: RECLASS: 20021024162220.607 > >> TS_ENDT {{NOGAPS, ".*"}} > >> Oct 24 17:22:20 rocky usgodae3[1678]: skipped: 20021024162119.486 > >> (61.120 seconds) > >> > >> I'd give the one that you supplied a try except I'm not sure what parts > >> are relevant for our needs. Should the ones that I put in (above) work? > >> > >> Thanks for any help you can give (anyone). > >> > >> Steve > >> > >> address@hidden writes: > >> >Hi Steve, > >> > > >> >If you do not "act" on the data..i.e. via pqact, then the LDM does not > >> >know what to do with it, it will sit in your queue and then go away.. > >> > > >> >Something like this: > >> > > >> ># GEMPAK GRIB decoding > >> ># > >> >HDS|NMC2|NOGAPS|CMC ^(/afs|[HOYZ]|US058)|.*CMC_GEM_reg_).* > >> > PIPE decoders/dcgrib2 -d > >> > data/pub/decoded/gempak/logs/dcgrib.log -v 1 > >> > -e GEMTBL=/home/gempak/NAWIPS/gempak/tables > >> > > >> >Is how we have it...but this is acting on ALL the models(NCEP, NCEP > >> >Conduit, FNMOC, and GEM) > >> > > >> > > >> >-Jeff > >> ________________________________________________ > >> Steve Cousins Email: address@hidden > >> Research Associate Phone: (207) 581-4302 > >> Ocean Modeling Group > >> School of Marine Sciences 208 Libby Hall, > >> University of Maine Orono ME 04469 > >> > >> > >> > >> ------- End of Forwarded Message > >> > >> > > ________________________________________________ > Steve Cousins Email: address@hidden > Research Associate Phone: (207) 581-4302 > Ocean Modeling Group > School of Marine Sciences 208 Libby Hall, > University of Maine Orono ME 04469 > > >