... | ... | @@ -11,11 +11,11 @@ We thought about 3 possible solutions : |
|
|
* It is really (really) quick at execution, Easiest to implement
|
|
|
* Modules have to be compile together. The IA shall not possibly modify this variable.
|
|
|
2. The Data Management discussion came with the following idea : We use a central module which has access to all the datas, gives the data required when asked by a module. Datas are actualized when a variable is modified. (there s a existing module to do that efficiently) This module could be merged with Core Simulation if it decreases a lot the quantity of data exchanged.
|
|
|
⋅⋅* It permits to have different programmation languages for each module. It is easier in the implementation for modularity.Fast enough if well implement see annexe.
|
|
|
⋅⋅* Harder to implement on the data module side.
|
|
|
* It permits to have different programmation languages for each module. It is easier in the implementation for modularity.Fast enough if well implement see annexe.
|
|
|
* Harder to implement on the data module side.
|
|
|
3. Use a class system to allow only a getter to the IAs and the whole class to the Core Simulation.
|
|
|
⋅⋅* It can't be quicker, it is the same as a physical access but with no possible modification.
|
|
|
⋅⋅* It can be harder to implement, it may affect the modularity because it may force both module to be implemented in the same programmation language.
|
|
|
* It can't be quicker, it is the same as a physical access but with no possible modification.
|
|
|
* It can be harder to implement, it may affect the modularity because it may force both module to be implemented in the same programmation language.
|
|
|
|
|
|
## Conclusion :
|
|
|
|
... | ... | |