[ldmMcidas #JLP-943200]: ldm-mcidas-2012: Compiling pnga2area [Mac Pro w/Mac OS X v10.8.4]

Hi Dave,

I just got a chance to look into the ldm-mcidas 'pnga2area' problem that
you reported below; sorry for the long wait.

re: waiting for the smoke to clear wrt LDM installation
> Go for it.
> 
> One thing that I didn't report (and that helped motivate my attempt to
> upgrade pnga2area to the 2012 version) were systematically recurring
> messages in the ~ldm/logs/ldm-mcidas.log file of this sort:
> 
> Jun 18 18:41:39 pnga2area[34296] INFO: output file pathname: 
> data/mcidas/gwir/1306181800_sir.mca
> Jun 18 18:41:39 pnga2area[34296] NOTE: unPNG::  1017319   2439056  2.3975
> Jun 18 18:41:39 pnga2area[34296] NOTE: Exiting
> Jun 18 18:41:39 pnga2area[34344] NOTE: Starting Up
> Jun 18 18:41:39 pnga2area[34344] ERROR: GetSatBandInfo: Sat or Band info not 
> found in SATBAND
> 
> (There were similar messages for all of the other types of satellite images 
> that I'm getting.)
> 
> I copied SATBAND and SATANNOT  from ldm-mcidas-2012 to ~ldm/etc, and the
> "Sat or Band info not found" messages went away.

Good, that shows that the SATBAND and SATANNOT files that were being used were
out of date wrt satellites providing imagery in the Unidata-Wisconsin 
datastream.

re:
> However, the other messages (reported below) have continued. (I'm still using 
> the
> version of pnga2area that I think that you helped me to compile in 2007.)

Two things:

- it appears that the version compiled in 2007 is working correctly for you

  At least, I do not see any error messages in ~ldm/logs/ldm-mcidas.log

- 'ldm' can not write in the directory where the ldm-mcidas-2012 source is
  located:

  % ls -alt /usr/local/unidata/ldm-mcidas-2012/src
  total 560
  drwxr-xr-x  132 admin  staff    4488 Jun 18 16:18 decode/
  drwxr-xr-x   62 admin  staff    2108 Jun 18 16:18 libpng/
  drwxr-xr-x   44 admin  staff    1496 Jun 18 16:18 zlib/
  drwxr-xr-x   23 admin  staff     782 Jun 18 16:18 ./
  -rw-r--r--    1 admin  staff   11533 Jun 18 16:18 config.log
  drwxr-xr-x   10 admin  staff     340 Jun 18 16:18 port/
  -rw-r--r--    1 admin  staff   23257 Jun 18 16:18 Makefile
  -rw-r--r--    1 admin  staff    1714 Jun 18 16:18 config.cache
  -rwxr-xr-x    1 admin  staff   12690 Jun 18 16:18 config.status*
  -rw-r--r--    1 admin  staff    1874 Jun 18 16:18 CUSTOMIZE
  drwxr-xr-x    3 admin  staff     102 Jun 18 14:47 ../
  -rw-r--r--    1 admin  staff   14221 Aug  7  2012 INSTALL
  -rwxr-xr-x    1 admin  staff  139787 Jan 19  2012 configure*
  -rw-r--r--    1 admin  staff     957 Jan 19  2012 configure.in
  -rw-r--r--    1 admin  staff     133 Jan 18  2012 ORIGIN
  -rw-r--r--    1 admin  staff     788 Jan 18  2012 COPYRIGHT
  -rw-r--r--    1 admin  staff   27237 Jan 18  2012 RELEASE_NOTES
  -rw-r--r--    1 admin  staff       5 Jan 18  2012 VERSION
  -rw-r--r--    1 admin  staff    2147 Apr 30  2009 Makefile.in
  -rw-r--r--    1 admin  staff      31 Apr 30  2009 cull.sed
  -rw-r--r--    1 admin  staff      75 Apr 29  2009 ldmd.conf
  -rw-r--r--    1 admin  staff    3372 Sep 16  2004 README
  -rw-r--r--    1 admin  staff    1643 Jun 19  2000 aclocal.m4

  As you can see, these directories are owned by user 'admin' in group
  'staff', but there are no group write permissions.  This means that
  user 'ldm' in group 'staff' can not write in the directories.

I noticed that 'ldm' has sudo, so I am using it to become 'admin'
so I can build the ldm-mcidas v2012 decoders...

OK, after quite a bit of experimentation, I successfully built
the 'pnga2area' and 'area2png' utilities in the ldm-mcidas v2012
distribution (located under /usr/local/unidata/ldm-mcidas-2012)
I then copied the newly built version of 'pnga2area' to the
/usr/local/bin directory, the location where I found the
version of 'pnga2area' that was being used by the LDM installation
(after renaming the old version to 'pnga2area.old').  I am
now waiting for some Unidata-Wisconsin images to be received
so I can verify that the newly built decoder works correctly.

Comment:

I had a lot of problems trying to build the ldm-mcidas decoders
on your machine.  This surprised me because I used the configuration
settings that I had put together after building the entire package
on another user's MacOS-X machine.  I am left scratching my head
as to why your system is so different than the other users...

Follow-up comment:

I just observed the receipt and processing of a Unidata-Wisconsin
(IDD datafeed type UNIWISC aka MCIDAS), so it looks like things are
working.  Please let me know if you run into anything that looks off.



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: JLP-943200
Department: Support ldm-mcidas
Priority: Normal
Status: Closed