1.1. Separate module for FC2K generated actors
1.1.1. Already existing solution based on KeplerData directory
At the moment, Kepler installation consist of few elements
- Base Kepler installation
- Patches applied by us
- Actors that can access ITM/IMAS database (ual actors)
- Actors generated by FC2K
src/eu |-- euforia | `-- visit `-- itm |-- cpocontent // all ual based actors could be a part of Kepler release |-- cpodiscard // this release would be shared by all the users |-- cpoflush |-- cpooccurrence |-- cpotime |-- itmmatlab |-- nocpo // these two actors can be moved to separate module |-- nocpoparam // these two actors can be moved to separate module |-- python |-- recordget |-- recordoperation |-- recordset |-- setbreakpoint |-- syncsetvariable |-- tools | `-- attributes |-- ualclose |-- ualcollector |-- ualdemux |-- ualinit |-- ualmux |-- ualmuxparam |-- ualpythonjni |-- ualpythonws `-- ualslicecollector
We can think about new approach, where Kepler base system (plus ual actors) and FC2K based actors are completely separated. This way, we would be able to have centrally installed Kepler and different sets of user based actors. There are two solutions for this
- already existing approach where user based modules are stored inside $HOME/KeplerData directory
- solution based on modifications inside Kepler's core classes - we have to develop new feature that will allow Kepler to find modules in virtually any location
1.1.2. New solution based on custom module location