Currently, all simulations and user data share the same 4 repertories, according to what classes are (action, factory, watcher or genome).
This is simple and modulable, but all simulation are mixed, so sharing them can be difficult, and its almost impossible to have an overview of which simulations are presents or not.
Improvement: in userdata, create a python module (init.py + files) for each simulation.
For run a simulation, get its name is enough, and the init.py file defined which classes need to be used by EvolAcc, that used the mother class information for determine what is the class.
Need deep modifications of command lines options, and modify classes importation.
Currently, all simulations and user data share the same 4 repertories, according to what classes are (action, factory, watcher or genome). This is simple and modulable, but all simulation are mixed, so sharing them can be difficult, and its almost impossible to have an overview of which simulations are presents or not.
Improvement: in userdata, create a python module (init.py + files) for each simulation. For run a simulation, get its name is enough, and the init.py file defined which classes need to be used by EvolAcc, that used the mother class information for determine what is the class.
Need deep modifications of command lines options, and modify classes importation.