| Warning | ||
|---|---|---|
| ||
This page is important if you are or had been using Kepler through commands If you are using Kepler for CPOs but never used these commands, please do care about this page, but check Environment configuration (section 2.2) instead" |
| Info | ||
|---|---|---|
| ||
If you want to fix your Kepler installation (CPO based), follow step-by-step instructions below
|
Rationale of the change
In ITM CPO based environment users defined KEPLER_DIR variable to point to the place where all user based Kepler installations were stored.
...
As we don't foresee any further modifications of the layout in ITM CPO based approach of installing and selecting Kepler we suggest following
...
We suggest to introduce new variable - ITM_KEPLER_DIR - for ITM based CPO based environment. This variable will replace already existing one: KEPLER_DIR
This variable will be set by users inside shell's startup script (take a look below - section Setting new location for Kepler installation).
Users will have to remove remove existing settings for KEPLER_DIR (take a look further in the page) or change it such way it points to location where IMAS based Kepler will be installed.
Updating $SWITMDIR scripts
...
| Code Block |
|---|
grep -H -n -s KEPLER_DIR $HOME/.bashrc $HOME/.bash_profile $HOME/.tcshrc $HOME/.cshrc $HOME/.login |
Finding
...
CPO 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 CPO based Keplers.
The best approach here would be to:
- create new place for
ITMbasedCPObased Kepler (e.g.$ITMWORK/itm-kepler-dir) - locate all the Keplers that belong to
ITMbased CPO based installation (see the script below) - move these directories to new location
...
Once user is done with choosing new location for ITM based CPO based Kepler, this information should be set
...
| Info | |||
|---|---|---|---|
| |||
|
...
| Info | |||
|---|---|---|---|
| |||
|