Differences

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

--- start [2023/01/30 13:52] – [MuPIF] bp
+++ start [2023/04/27 23:10] (current) – bp
@@ Line 1: / Line 1: @@
 {{ :wiki:images:mupif-logo.png?100|}}
+{{keywords> Open Simulation Platform, Digital twin, Interoperability, Modelling, Simulations, Workflows}}
 ====== MuPIF ======
-MuPIF is open-source, modular, object-oriented integration platform allowing to create complex, distributed, multiphysics simulation workflows across the scales and processing chains by combining existing simulation tools. MuPIF is written in Python 3.5 and is independent on operating system.
+MuPIF is open-source, modular, object-oriented integration platform allowing to create complex, distributed, multiphysics simulation workflows across the scales and processing chains by combining existing simulation tools. Platform comes with data management system allowing to build digital twin representations of physical systems.
 MuPIF utilizes an object-oriented approach, with abstract classes defining standardized interfaces introduced to represent simulation models and data types.
@@ Line 19: / Line 19: @@
 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.
+MuPIF is written in Python 3.5 and is independent on operating system.
 ==== MuPIF highlights ====