User Tools

Site Tools


start

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revisionBoth sides next revision
start [2023/01/30 13:47] – [Documentation & Resources] bpstart [2023/01/30 13:52] – [MuPIF] bp
Line 17: Line 17:
 The simulation workflows are implemented as Python scripts built on top of MuPIF. The graphical workflow editor is available to make the workflow implementation more accessible and convenient. The simulation workflows are implemented as Python scripts built on top of MuPIF. The graphical workflow editor is available to make the workflow implementation more accessible and convenient.
  
-MuPIF comes with a Data Management System (DMS) called MuPIFDB. The DMS is used to track integrated simulation workflows, their executions including execution inputs and outputs. It also provides a generic Digital Twin model, which is based on the user-defined Entity Data Model (EDM). The EDM identifies the individual entities, their attributes and relations between them. The EDM is defined using JSON schema, and the DMS structure is generated from this schema. When designing the EDM, one should introduce Entities and their States, following the EMMO Reductionistic perspective. The EDM allows to map State attributes to simulation workflow inputs (determining the initial conditions) and simulation workflow outputs can be mapped to new State representing updated configuration(s). The EDM can thus be regarded as hypergraph, where nodes represent entity states and edges representing processes.+MuPIF comes with a Data Management System (DMS) called MuPIFDB. The DMS is used to track integrated simulation workflows, their executions including execution inputs and outputs. It also provides a generic Digital Twin model, which is based on Entity Data Model (EDM). The EDM identifies the individual entities, their attributes and relations between them. The EDM is defined using JSON schema, and the DMS structure is generated from this schema. The EDM allows to map entity attributes to simulation workflow inputs (determining the initial conditions) and simulation workflow outputs can be mapped to newly cloned entities representing updated configuration(s). The EDM can be regarded as hypergraph, where nodes represent entity states and edges representing processes.
  
  
start.txt · Last modified: 2023/04/27 23:10 by bp