20000426: McIDAS addenda

>From: weather <address@hidden>
>Organization: NMSU/NSBF
>Keywords: 200004261648.e3QGmjG16871 McIDAS-X 7.611 addendum

Robert,

>On the latest addenda the last step shown is to rebuild the entire
>McIDAS distribution.  Is that in addition to the previous steps,
>or is it an either/or.

I try to list out the procedure that can be used to build portions of
each addendum so that sites not wanting to install everything don't
have to.  The absolute easiest thing to do, however, is to rebuild
the entire distribution each time an addendum is issued.  In practice,
this typically results in a couple/few routines being recompiled and
linked.  If there are library routines in the addendum, however, all
applications will be relinked as their executables explicitly depend
on the McIDAS-X library, libmcidas.a

>Thanks,
>Robert Mullenax
>NSBF Meteorology

Tom

To: weather <address@hidden>

>So would building the whole thing negate having to do the other
>configuration changes associated with DCGRIB, etc..

Is this a question about GEMPAK or McIDAS.  I assume you mean DMGRID
since dcgrib is a GEMPAK decoder.

>I should know this, but am a little confused.

Doing the whole thing makes doing the pieces unnecessary EXCEPT in the
area of increasing the spool file size for DMGRID.  In order to change
this file, one has to:

o stop the LDM
o delete the old HRS.SPL file
o delete the HRS spool pointer file, GRIBDEC.PRO
o install the new tables
o restart the LDM

The new spool file will be created as data comes in, and the new spool
pointer file will be created as soon as data is decoded.

I will change my online addendum installation instructions to be more
clear on installing pieces or the whole thing.

Tom