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 Mar, re: pnga2area output area was the same in both log file snippits > agreed re: possible output directory write permission issue > > - /data <- if pnga2area needs to create /data/ldm > > - /data/ldm <- if pnga2area needs to create /data/ldm/gempak > > - /data/ldm/gempak <- if pnga2area needs to create /data/ldm/gempak/images > > - /data/ldm/gempak/images <- etc. > > Yeah, I forgot to include that ldm and the pqact.gempak processors were > able to successfully create other files in the /data/ldm/gempak/images > directory. OK. > I have included a consolidated directory listing: > [ldm@foehn ~]$ ls -l data > lrwxrwxrwx 1 ldm met-apps 10 Jun 29 15:21 data -> /data2/ldm So, ~ldm/data points to /data2/ldm, not /data/ldm. This is likely the entire problem as your pqact.gempak entries for the MCIDAS feed have /data/ldm/... as the output directories. > [ldm@foehn ~]$ ls -l /data2/ldm > total 402432 > drwxr-xr-x 24 ldm met-apps 4096 Jul 15 16:05 gempak > > [ldm@foehn ~]$ ls -l /data2/ldm/gempak > total 88 > drwxr-xr-x 3 ldm met-apps 4096 Jul 15 16:05 images > > [ldm@foehn ~]$ ls -l /data2/ldm/gempak/images > total 4 > drwxr-xr-x 3 ldm met-apps 4096 Jul 15 16:05 sat > > [ldm@foehn ~]$ ls -l /data2/ldm/gempak/images/sat > total 4 > drwxr-xr-x 5 ldm met-apps 4096 Jul 15 16:05 NEXRCOMP Looks good... > At the same time that I instituted the UNIWISC feed it, which is > resulting in these errors, it successfully created the NEXRCOMP > directory and products. OK. The pqact.conf entry must have been pointing to /data2/ldm/... or you were using the connection through the ~ldm/data <-> /data2/ldm soft link. > If you want in to poke around, I have temporarily changed the magic word > to: ... Thanks. I logged on and changed the specified output data directories from/data/ldm/gempak/... to data/gempak. Now the images are being decoded and written as shown in this ~ldm/data/gempak/logs/ldm-mcidas.log output: Jul 16 14:42:09 pnga2area[13551]: Starting Up Jul 16 14:42:09 pnga2area[13551]: output file pathname: data/gempak/images/sat/GOES-11/4km/12.0/12.0_20060716_1430 Jul 16 14:42:09 pnga2area[13551]: unPNG:: 908797 2439056 2.6838 Jul 16 14:42:09 pnga2area[13551]: Exiting Jul 16 14:45:05 pnga2area[13906]: Starting Up Jul 16 14:45:05 pnga2area[13906]: output file pathname: data/gempak/images/sat/SOUNDER/1km/CTP/CTP_20060716_1400 Jul 16 14:45:05 pnga2area[13906]: unPNG:: 71830 309200 4.3046 Jul 16 14:45:05 pnga2area[13906]: Exiting > Thank you for your help. No worries... 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: VMF-784186 Department: Support ldm-mcidas Priority: Normal Status: Closed