1.1. Separate module for FC2K generated actors
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
itm/src/
??? cpp // native code - could be moved outside itm module
? ??? itm
? ??? nocpo
? ? ??? bin
? ? ??? build
? ? ??? lib
? ? ? ??? def
? ? ? ??? opt
? ? ??? lib_ext
? ? ? ??? def
? ? ? ??? opt
? ? ??? src
? ??? nocpoparam
? ??? bin
? ??? build
? ??? lib
? ? ??? def
? ? ??? opt
? ??? lib_ext
? ? ??? def
? ? ??? opt
? ??? src
??? eu
? ??? euforia
? ? ??? visit
? ??? itm // Java code - partially autogenerated, partially taken from ualactors repository
? ??? cpocontent
? ??? cpodiscard
? ??? cpoflush
? ??? cpooccurrence
? ??? cpotime
? ??? itmmatlab
? ??? nocpo // this actor
? ??? nocpoparam // and this actor could have been moved to a different place (new module)
? ??? python
? ??? recordget
? ??? recordoperation
? ??? recordset
? ??? setbreakpoint
? ??? syncsetvariable
? ??? tools
? ? ??? attributes
? ??? ualclose
? ??? ualcollector
? ??? ualdemux
? ??? ualinit
? ??? ualmux
? ??? ualmuxparam
? ??? ualpythonjni
? ??? ualpythonws
? ??? ualslicecollector
??? org
??? kepler
??? module
??? itm
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
