...
| Code Block |
|---|
# 1. log in to machine # 2. initialise environment > module load ets_workflow # 3. run the autoGui > launch_keplerets.sh |
autoGui is started, user can use his version of ETS with the default workflow loaded by environment.
Use-case 2 -
...
Using already installed version of ETS after new version was released
...
In this scenario, system was upgraded and new release of tools was installed
...
| Code Block |
|---|
# 1. log in to machine # 2. initialise environment > module load ets_workflow # 3. run the autoGui > launch_keplerets.sh There is a new release of Kepler. Do you want to upgrade [Y/N]?: N |
User presses N and currently installed version of autoGui and current version of Kepler are used. No changes inside user's settings are done.
Use-case 3 -
...
Automatic update of ETS
...
installation
In this scenario, system was upgraded and new release of tools was installed
...
| Info |
|---|
With current layout of |
| Code Block |
|---|
# 1. log in to machine # 2. initialise environment > module load itmenv > module load ets_workflow # 3. run the autoGui > launch_keplerets.sh There is a new release of Kepler. Do you want to upgrade [Y/N]?: Y |
User presses Y. Script performs upgrade of all tools installed for the user and starts most recent version of autoGui and most recent version of Kepler. Previous version of user's installation are preserved and it will be possible to go back to this version later.
Use-case 4 - running previous installation of Kepler
In this scenario, user decides it's required to run previous simulation with old set of actors. User runs dedicated script
| Code Block |
|---|
> list_keplers.sh
[ ] R5.0.16_v5.2.2
[ ] R5.0.16_v5.2.3
[X] R5.0.17_v5.2.3
> select_kepler.sh R5.0.16_v5.2.3
> list_keplers.sh
[ ] R5.0.16_v5.2.2
[X] R5.0.16_v5.2.3
[ ] R5.0.17_v5.2.3
> launch_kepler.sh --nocheck |
In this scenario, user decides to use previously installed Kepler and skips checking for newer version. Selected version of Kepler is started.