...
- The structure is layered so that functionalities are clearly separated
- It is generic and independent of e.g. the launching script/workflow engine
- The Physics solver part (dark green) is not changed, it is not linked to the ITER Data Model. It may use the ITER Data Model internally or not.
- The architecture is identical to the case of a component called within a workflow engine
- The Physics Subroutine can be directly reused to generate a workflow component – the IMAS Infrastructure provides a tool that generates the component (pink part) automatically
- Exception: for codes handling massive amounts of data, Data Access is usually parallelised and must be done inside the physics_solver (no processor has enough memory to gather all data)
...