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 Samuel, re: > We're still weren't filing anything as of this afternoon, so I decided to just > simply file the data(instead of decoding) using the following lines in > pqact.gempak: > > CMC > CMC_reg_.*_.*_.*_(.*)_([12][0-9][0-9][0-9])([0-1][0-9])([0-3][0-9])([0-2][0-9])_(P.*).grib > FILE data/cmc/\2\3\4\5_\6.\1 > > This produced no files, and didn't even report an error in ldmd.log. > > Now I'm REALLY lost. When I saw your message this morning I checked to see if you were receiving GEM data. I did this by looking at the statistics being reported back to us by shu.cup.edu: GEM volume: http://www.unidata.ucar.edu/cgi-bin/rtstats/iddstats_vol_nc?GEM+shu.cup.edu When I checked, you had not received any GEM data since about 17 UTC on March 29. The current volume plot shows that you did receive data today at approx. 17 and 23 UTC. Question: Does your report of not being able to FILE the GEM (CMC) products fall in the period when you were not receiving any GEM data, or does it relate to the period(s) today when you were receiving the data? Also, I just logged onto shu.cup.edu and do not see a pqact instance running on etc/pqact.gempak: [ldm@shu logs]$ ps -eaf | grep pqact ldm 28562 27182 0 18:06 pts/2 00:00:00 vim pqact.gempak ldm 15637 15634 2 19:06 ? 00:00:14 pqact -f IDS|DDPLUS etc/pqact.conf_mcidasA ldm 15638 15634 2 19:06 ? 00:00:13 pqact -f NIMAGE etc/pqact.conf_nimage ldm 15639 15634 2 19:06 ? 00:00:13 pqact -f FSL2|NLDN|UNIWISC etc/pqact.conf_mcidasB ldm 15640 15634 2 19:06 ? 00:00:12 pqact -f CONDUIT|HRS|NGRID etc/pqact.conf_mcidasC ldm 15641 15634 2 19:06 ? 00:00:13 pqact -f NNEXRAD etc/pqact.conf_nnexrad ldm 15642 15634 2 19:06 ? 00:00:13 pqact -f NEXRAD2 etc/pqact.conf_nexrad2 ldm 16253 15184 0 19:15 pts/4 00:00:00 grep pqact A quick check in the LDM log file, ~ldm/logs/ldmd.log, shows that the pqact instance that was supposed to use pqact.gempak exited: Mar 31 23:06:06 shu pqact[15643] NOTE: Starting Up ... Mar 31 23:06:06 shu pqact[15643] ERROR: Unknown action "FILE data/cmc/\2\3\4\5_\6.\1" at line 35 ... Mar 31 23:06:07 shu pqact[15643] ERROR: Error in configuration-file "etc/pqact.gempak" ... Mar 31 23:06:08 shu pqact[15643] NOTE: Exiting ... Mar 31 23:06:08 shu rpc.ldmd[15634] NOTE: child 15643 exited with status 1: pqact -f GEM|CMC etc/pqact.gempak When I went to edit pqact.gempak, I noticed that it was already being edited: [ldm@shu ldm]$ ps -eaf | grep vi ldm 28562 27182 0 18:06 pts/2 00:00:00 vim pqact.gempak I killed this vi invocation: [ldm@shu ldm]$ kill 28562 and then edited the file to look for weirdness. I found that the whitespace after FILE was spaces and not a tab. I corrected the error and then restarted the LDM. The GEM (aka CMC) data products should now be FILEd. As far as why the GEMPAK decoding action using dcgrib2 wasn't working, I ran into something that I don't yet understand: [ldm@shu ldm]$ ldd decoders/dcgrib2 not a dynamic executable [ldm@shu ldm]$ ls -alt decoders/dcgrib2 -rwxr-xr-x 1 ldm ldm 551932 Mar 21 16:43 decoders/dcgrib2 [ldm@shu ldm]$ file decoders/dcgrib2 decoders/dcgrib2: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), for GNU/Linux 2.6.9, dynamically linked (uses shared libs), stripped The output from ldd that says that ~ldm/decoders/dcgrib2 is not a dynamic executable is indirect contradiction to the 'file decoders/dcgrib2' output. I am scratching my head on this one at the moment. I will write back when I figure it out. Cheers, Tom **************************************************************************** Unidata User Support UCAR Unidata Program (303) 497-8642 P.O. Box 3000 address@hidden Boulder, CO 80307 ---------------------------------------------------------------------------- Unidata HomePage http://www.unidata.ucar.edu **************************************************************************** Ticket Details =================== Ticket ID: QYV-528693 Department: Support GEMPAK Priority: Normal Status: Closed