It looks like (from user's perspective) we miss simplified way of choosing "dressed" Kepler and workflow that will be used to launch ETS. In fact, the same sort of issues will affect Python based workflows.
...
In order to use it, user will.
Use-case 1 - running existing installation of
...
ETS
| Code Block |
|---|
# 1. log in to machine
# 2. initialise environment
> module load itmenv
> module load ets_workflow
# 3. run the autoGui
> launch_kepler.sh |
autoGui is started, user can use his version of Kepler ETS with the default workflow loaded by environment.
Use-case 2 - running existing installation of
...
ETS after new
...
version was released - using already installed version
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 itmenv > module load ets_workflow # 3. run the autoGui > launch_kepler.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 - running existing installation of
...
ETS after new
...
version was released - using upgraded release
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 itmenv
> module load ets_workflow
# 3. run the autoGui
> launch_kepler.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
...