Unidata McIDAS-X - Upgrading from a Previous Version


Users upgrading from a previous version of McIDAS-X will at a minimum need to do the following.

  1. Review McIDAS-X v2016 Release Notes.

  2. Download the McIDAS-X v2016 distribution files:

    to the HOME directory of the user mcidas

  3. Define needed Unix environment variables:

    • Define the Unix environment variable McINST_ROOT to be the fully qualified directory name under which McIDAS is to be installed. This is typically the HOME directory of the user mcidas. Define McINST_ROOT in the definition file for the Unix shell you are using (e.g., .cshrc for C and TC shells, .profile for the Bourne shell, .bash_profile for bash, or .kshrc for the Korn shell).

    • Define the Unix environment variable VENDOR to select which of the two supported set of compilers you want to use to build Unidata McIDAS-X/-XCD (-vendor for vendor-supplied compilers, -g77 for GNU gcc/g77, or -gfortran for GNU gcc/gfortran (NB: tested on Linux only!)). The VENDOR definition should also be put in your shell definition file.

    • Define the Unix environment variable MySQL_ROOT to build McIDAS-X/-XCD with support/use of the MySQL database for the ADDE GRIB server (hightly recommended!). The site administrator must install the MySQL client, server, AND development environments before building McIDAS if the ADDE GRIB server is to be used.

    Assuming that the McIDAS-X/-XCD is to be installed in the standard location, and the user wants to use the GNU gcc/g77 compiler combination, The entries for McINST_ROOT and VENDOR will look like:

    non-Conforming shells (e.g., .cshrc) Conforming shells (e.g., .profile, .bash_profile, or .kshrc)
    # McINST_ROOT and VENDOR non-conforming shell defines
    # needed to build McIDAS
    setenv McINST_ROOT $HOME
    setenv VENDOR -g77
    
    # NOTE: uncomment the line that sets MySQL_ROOT if you want to
    #       build with MySQL support:
    #       - leave the value blank if MySQL is installed in a standard
    #         location
    #       - specify the value as the root directory of the MySQL
    #         installation if MySQL is not installed in a standard
    #         location
    # setenv MySQL_ROOT TRUE
    
    if ( -e $HOME/admin/mcidas_env.csh ) then
      source $HOME/admin/mcidas_env.csh
    endif
    
    # McINST_ROOT and VENDOR conforming shell defines
    # needed to bulid McIDAS
    McINST_ROOT=$HOME
    VENDOR=-g77
    export McINST_ROOT VENDOR
    
    # NOTE: uncomment the next two lines that set MySQL_ROOT if you
    #       want to build with MySQL support:
    #       - leave the value blank if MySQL is installed in a standard
    #         location
    #       - specify the value as the root directory of the MySQL
    #         installation if MySQL is not installed in a standard
    #         location
    # MySQL_ROOT=TRUE
    # export MySQL_ROOT
    
    if [ -e $HOME/admin/mcidas_env.sh ]; then
      . $HOME/admin/mcidas_env.sh
    fi
    

    After adding entries to your shell definition file, make those additions active in your session (e.g. source .cshrc, . .profile, . .bash_profile, etc.).

  4. Unpack the distribution:

    cd ~mcidas
    chmod +x mcunpack
    ./mcunpack
    

  5. Build the distribution (if you are upgrading, the assumption is that the needed Unix environment variable definitions for the user mcidas are active):

    cd ~/mcidas2016/src
    make mcx          <- to build McIDAS-X only
      -- OR --
    make all          <- to build both McIDAS-X and McIDAS-XCD
    

  6. Optional: Test the distribution before installing it (NOTE: not needed this is a new installation or if if you are committed to upgrading to the new distribution).

  7. If you made any changes to the MCGUI image load definition file ADDEIMAGE.CORE, copied the file to your McIDAS working directory, created a site image load file ADDEIMAGE.SITE, or created a user image load defaults file ADDEIMAGE.USER, you MUST move them out of the directories defined in your MCPATH. The 2016 format and content of these files was significantly changed.

    If this step applies to you, please review the contents of v2016's ADDEIMAGE.CORE to learn what you must do to convert your previous files to the correct content and format.

  8. stop the LDM if you are installing -XCD:

    <login as 'ldm'>
    cd ~ldm
    ldmadmin stop
    <exit>
    

  9. Uninstall the previous distribution (NOTE: example is for v2009):

    cd ~/mcidas2009/src
    make uninstall.all
    

  10. Install v2016:

    cd ~/mcidas2016/src          <- to install McIDAS-X only
    make install
      -- OR --
    make install.all             <- to install both McIDAS-X and McIDAS-XCD
    

  11. Run the McIDAS-X/-XCD configuration script, mcxconfig, to configure McIDAS:

    cd $MCDATA
    mcxconfig
    

    Recommendation: use defaults presented by mcxconfig for most actions.

    If you are upgrading an existing McIDAS installation, you may need to do the following before running mcxconfig:

    • Save v2009 locally created file REDIRECTions (should be located in $McINST_ROOT/data/LOCAL.NAM before you run mcxconfig).

      cd $McINST_ROOT/data
      cp LOCAL.NAM LOCAL.NAM.2007
      

      When mcxconfig advises you to review file REDIRECTions in $McINST_ROOT/data/LOCAL.NAM, merge any/all locally added definitions from $McINST_ROOT/data/LOCAL.NAM.2009 into $McINST_ROOT/data/LOCAL.NAM.

    • Save v2009 locally created ADDE server mapping table definitions (should be located in $McINST_ROOT/data/LSSERVE.BAT before you run mcxconfig).

      cd $McINST_ROOT/data
      cp LSSERVE.BAT LSSERVE.BAT.2009
      

      When mcxconfig advises you to review server mapping table actions in $McINST_ROOT/data/LSSERVE.BAT, merge any/all locally added definitions from $McINST_ROOT/data/LSSERVE.BAT.2009 into $McINST_ROOT/data/LSSERVE.BAT.

    • If you are upgrading an existing -XCD installation, do the following:

      cd $MCDATA
      rm DECINFO.DAT
      

  12. If you stopped the LDM in a previous step, restart it now:

    <login as 'ldm'>
    ldmadmin start
    <exit>
    

At this point, your McIDAS v2016 distribution should be ready to use. If you have problems, please send email to Unidata McIDAS Support <support-mcidas@unidata.ucar.edu> for assistance. Please make sure to describe the problem you are having in enough detail so we can help you troubleshoot.