1. Rationale of the change

In ITM based environment users defined KEPLER_DIR variable to point to the place where all user based Kepler installations were stored.

IMAS based Kepler also use this variable, but in different way. The layout of KEPLER_DIR is slightly different.

As we don't foresee any further modifications of the layout in ITM based approach of installing and selecting Kepler we suggest following

1.1. New variable for installation directory - ITM_KEPLER_DIR

We suggest to introduce new variable - ITM_KEPLER_DIR - for ITM based environment.

This variable will be set by users inside shell's startup script.

Users will have to remove KEPLER_DIR or change it such way it points to location where IMAS based Kepler will be installed.

1.2. Updating $SWITMDIR scripts

In order to make all the scripts (related to Kepler) work again, we will update them such way they use ITM_KEPLER_DIR instead of KEPLER_DIR. This change will affect

install_kepler.sh
install_personal_kepler.sh
list_my_keplers.sh
remove_kepler.sh
switch_to_kepler.sh

1.3. Checking locations of login files with KEPLER_DIR

It might have happened that users have set up KEPLER_DIR long time ago and don't even bother about its existence.

#!/bin/bash
for file in .bashrc .bash_profile .tcshrc .cshrc .login
do
  grep KEPLER_DIR $HOME/$file
done

1.4. Finding ITM based Kepler installations inside KEPLER_DIR

For some users it may be the case, they already have a mixed installation of IMAS and ITM based Keplers.

The best approach here would be to:

• create new place for ITM based Kepler (e.g. $ITMWORK/itm-kepler-dir)
• locate all the Keplers that belong to ITM based installation (see the script below)
• move these directories to new location

find $KEPLER_DIR -name "version" | sed "s|$KEPLER_DIR||" | sed 's/^\///' | cut -f1 -d'/'

1.5. Setting new location for Kepler installation

Once user is done with choosing new location for ITM based Kepler, this information should be set inside