       Upgrade instruction for Mark-5 VLBI Analysis Software Calc/Solve 
       ################################################################


It is assumed that 
~~~~~~~~~~~~~~~~~~

1) You have already installed Solve version released in 2003.07.25 or later.

2) You have all local customization files in appropriate directories. 
 

Installation:
~~~~~~~~~~~~~


-1) Check whether your environment for sh-shell and c-shell is tuned properly. 
    Your path environment should be correct and you should be able to call 
    system programs and program unzip. Directory ./ should be specified 
    at the end of path environment variable.

0) Stop all Solve processes. You should be aware that after upgrade in general
   you CANNOT continue your Solve process and contents of your Solve scratch 
   (or work) files will be or may be lost. Therefore you have to update the 
   database if you were running interactive solution and you need to save it, 
   and you have to either to wait for completion of batch Solve process or 
   cancel it.

1) Select a scratch directory where you put the distribution kit.
   That directory should have space enough for both tar-ed and untar-ed 
   distribution kit (at least 25Mb).

   Browse distribution kit from Solve web-site http://gemini.gsfc.nasa.gov/solve
   Distribution kit is a file with name SOLVE_xxxxxx.tar where xxxxxx is a date
   of creation of this file. This tar-file contains a set of zip-files and
   several C-shell programs.

   Untar distribution kit by using a commands:

   cd <scratch_directory_with_kit>
   tar -xvf <SOLVE_distribution_tarfile>

2) Read section of release notes: "Installation". This section describes
   which operations you should do (if any) before installation, for example 
   editing your local files and your files with definitions of environment 
   variables. Files in $MK5_ROOT/local directory are not updated. If more than 
   one release occurred from the time you upgraded your Solve, you should   
   *first* apply all changes in these files in chronological order of solve 
   releases.

3) Launch csh-shell or tcsh-shell. Keep in mind that results are unpredictable 
   if you choose another shell.

   Set environment variables:

   a) MK5_ROOT  -- root directory for CALC/SOLVE directory tree.
   b) SAVE_DIR  -- directory for SOLVE-related files with data.

   by using  C-shell command "setenv {name} {value}", for example

   setenv MK5_ROOT   /diskB5/mk5
   setenv SAVE_DIR   /diskB5/mk5/solve/save_files

4) Run solve_install from the directory where untar-ed distribution kit is 
   located:

      cd <scratch_directory_with_kit>
      solve_install upgrade

   It takes from 30 minutes to 2 hours to compile and link all mk5-programs.

   solve_install makes
   a) checks whether necessary executables and libraries installed in your
      system;
   b) whether all parameters are defined in your local files. This may occur
      because some new parameters were added to the new release. In this case
      look at the file $SAVE_DIR/template_local.lcl, find definitions of
      the new parameters, edit your local solve.lcl file and add
      appropriate definitions.

   If at least one check fails, solve_install refuses to install the package.
   You have to fix the problems. 

   If your local customization file is not up to date you may need to update
   it. solve_install checks whether it has all definitions. If there are new
   definitions which Solve requires, but you don't have, you should update your
   local definitions file and then restart solve install again. You are able
   to do it by two ways: by launching "solve_install by 
   "${MK5_ROOT}/make_all_mk5 . In the latter case Solve will 
   not unpack source code since it has been already unziped, and outright will
   start compilation and linking/

6) Check files $MK5_ROOT/temp/make_libs_errs, 
               $MK5_ROOT/temp/make_progs_errs, 
               $MK5_ROOT/temp/make_solve_errs, 
               $MK5_ROOT/temp/make_testware_errs, 
               $MK5_ROOT/temp/make_utils_errs

   It should not contain error messages: only informational messages
   and compiler warnings. Search for patterns "**" and "Don't":

     grep "\*\*"   $MK5_ROOT/temp/*_err*
     grep "Don\'t" $MK5_ROOT/temp/*_err*


7) You may need to re-create your scratch files by running 
   solve_reset program. 


That's all.
~~~~~~~~~~~

If it does not work, write a verbose message with a detailed report of what
you have done to Leonid Petrov ( pet@leo.gsfc.nasa.gov )

2003.07.25_18:43:19
