...
- Base Kepler installation
- Patches applied by us
- Actors that can access ITM/IMAS database (ual actors)
- Actors generated by FC2K
| Code Block |
|---|
itm/src/ ??? cpp // native code - could be moved outside itm module ? ??? itm ? ??? nocpo ?eu |-- euforia | `-- visit `-- itm |-- cpocontent ?// all ual ??? bin ? ? ??? build ?based actors could be a part of Kepler release |-- cpodiscard ? ??? lib ? // this release ?would be shared ?by all the ??? defusers ? ? ? ??? opt ?|-- cpoflush ? ??? lib_ext ?|-- cpooccurrence ? ? ??? def ?|-- cpotime ? ? ??? opt ?|-- itmmatlab ? ??? src ? ??? nocpoparam ? ??? bin ? ??? build ? ??? lib ? ? ??? def ? ? ??? opt ? ??? lib_ext ?|-- nocpo ? ??? def ? ? ??? opt ? ??? src ??? eu ? ??? euforia ? ? ??? visit ? ??? itm // Javathese codetwo -actors partiallycan autogenerated,be partiallymoved takento fromseparate ualactors repositorymodule ? ??? cpocontent ? ??? cpodiscard ? ??? cpoflush ? ??? cpooccurrence ? ??? cpotime ? ??? itmmatlab ?|-- nocpoparam ??? nocpo // thisthese actor ?two actors can ??? nocpoparam // and this actor could have been be moved to a different place (new module) ?separate module ???|-- python ? ??? |-- recordget ? ??? |-- recordoperation ? ???|-- recordset ? ??? |-- setbreakpoint ? ??? |-- syncsetvariable ? ???|-- tools ? | ? ??? `-- attributes ? ??? |-- ualclose ? ???|-- ualcollector ? ??? |-- ualdemux ? ???|-- ualinit ? ??? |-- ualmux ? ???|-- ualmuxparam ? ??? |-- ualpythonjni ? ??? |-- ualpythonws ? ??? ualslicecollector ??? org ??? kepler ??? module ??? itm`-- 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
...