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 v2022 Release Notes.

  2. Download the McIDAS-X v2022 distribution files:

    to the HOME directory of the user mcidas

  3. Define needed Unix environment variables:

    1. Define the Unix environment variable MCVER to match the version of the McIDAS distribtion to be installed. For example, define MCVER to 2022 for the Unidata McIDAS v2022 distribution.

    2. Define the Unix environment variable MCHOME to be the fully qualified directory name under which McIDAS is to be installed. This is typically the HOME directory of the user mcidas.

    3. Define McINST_ROOT to be the fully qualified directory name under which McIDAS is to be installed. This is typically the same as MCHOME. Include this setting 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).

    4. 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 (NOT recommended) or -gfortran (recommended) for GNU gcc/gfortran (NB: tested on CentOS 6.10 and Ubuntu 14.04 LTS Linux only!)). The VENDOR definition should also be put in your shell definition file.

    5. Define the Unix environment variable MySQL_ROOT to build McIDAS-X/-XCD with support/use of the MySQL database for the ADDE GRIB server (highly 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.

    6. Define the Unix environment variable MCADMIN to be fully qualified directory name under which this McIDAS distribution's admin files are to be installed. This is typically the $McINST_ROOT/admin directory of the user mcidas. The MCADMIN definition should also be put in your shell definition file.

    Assuming that the McIDAS-X/-XCD is to be installed in the standard location, and the user wants to use the GNU gcc/gfortran 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 MCVER 2022
    setenv MCHOME $HOME
    setenv McINST_ROOT $MCHOME
    setrenv MCADMIN $McINST_ROOT/admin
    setenv VENDOR -gfortran
    
    # 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 $MCADMIN/mcidas_env.csh ) then
      source $MCADMIN/mcidas_env.csh
    endif
    
    # McINST_ROOT and VENDOR conforming shell defines
    # needed to bulid McIDAS
    MCVER=2022
    MCHOME=$HOME
    McINST_ROOT=$MCHOME
    MCADMIN=$McINST_ROOT/admin
    VENDOR=-gfortran
    export MCVER MCHOME McINST_ROOT MCADMIN VENDOR
    
    # NOTE: uncomment the 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 $MCADMIN/mcidas_env.sh ]; then
      . $MCADMIN/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 2022
    

  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 ~/mcidas2022/src
    make mcx          <- to build McIDAS-X only
      -- OR --
    make all          <- to build both McIDAS-X and McIDAS-XCD
      -- OR --
    make all xrd      <- to build McIDAS-X, McIDAS-XCD and McIDAS-XRD
    

  6. Optional: Test the distribution before installing it (NOTE: testing is 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, copy the file to your McIDAS working directory, created a site image load file ADDEIMAGE.SITE, in the data subdirectory of user 'mcidas' HOME, or create an individualized user image load defaults file ADDEIMAGE.USER and put it in the user's McIDAS working directory defined by the environment variable MCDATA.

    If this step applies to you, please review the contents of v2022'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 v2019):

    cd ~/mcidas2019/src
    make uninstall.all uninstall.xrd
    

  10. Install v2022:

    cd ~/mcidas2022/src          <- to install McIDAS-X only
    make install
      -- OR --
    make install.all             <- to install both McIDAS-X and McIDAS-XCD
      -- OR --
    make install.all install.xrd <- to install McIDAS-X, McIDAS-XCD and McIDAS-XRD
    

  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:

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

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

At this point, your McIDAS v2019 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.