...
Default location of Kepler based cache files
It looks like we need a common place for various cache files: .kepler, .ptolemyII, KeplerData
...
We have agreed to make current working directory a place where all the local data used by Kepler will be stored.
Use-case - running two different sessions of Kepler
Let's say we want to run two, completely separate sessions of Kepler. In that case, user will do following
| Code Block |
|---|
> mkdir experiments
> cd experiments
> mkdir my_firs_experiment
> cd my_firs_experiment
> kepler.sh
... some things are happening ... workflow is started ... done ...
... at the end, user saves his own version of ETS workflow as "workflow.xml"
> cd ..
> mkdir my_second_experiment
> cd my_second_experiment
> kepler.sh
... some things are happening ... workflow is started ... done ...
... at the end, user saves his own version of ETS workflow as "workflow.xml"
> cd ../..
> tree experiments
experiments
|-- my_first_experiment
| |-- KeplerData
| | `-- workflow.xml
| |-- kepler.log
| |-- keplerLog4J.log
| |-- .local
| |-- .ptolemyII
| `-- SOME_FILE_CREATED_BY_PHYSICS_CODE
`-- my_second_experiment
|-- KeplerData
| `-- workflow.xml
|-- kepler.log
|-- keplerLog4J.log
|-- .local
|-- .ptolemyII
`-- SOME_FILE_CREATED_BY_PHYSICS_CODE |
At the very end, all the local data end up in a location where Kepler was started. There are no references to $HOME or $KEPLER or some other locations. Everything is stored in the directory where Kepler was started.
...
Kplots and other scripts
...