start
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| start [2025/05/07 11:06] – [Acknowledgements] bp | start [2025/09/27 00:11] (current) – [Documentation & Resources] bp | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| {{ : | {{ : | ||
| {{keywords> | {{keywords> | ||
| - | ====== MuPIF ====== | + | ====== MuPIF.org - Empowering Complex Multiphysics Simulations with Open-Source, |
| - | MuPIF is an open-source, | + | |
| + | MuPIF is an open-source, | ||
| **Key features of MuPIF include:** | **Key features of MuPIF include:** | ||
| * Distributed Design: Allows execution of simulation scenarios involving remote applications and data. | * Distributed Design: Allows execution of simulation scenarios involving remote applications and data. | ||
| - | * Data Management System (DMS): Builds digital twin representations of physical systems, enhancing predictive simulations. | + | * Data Management System (DMS): Builds digital twin representations of physical systems, enhancing predictive simulations. Provides full traceability. |
| * Interoperability: | * Interoperability: | ||
| * Graphical Workflow Editor: Facilitates low-code workflow development and makes implementation more accessible. | * Graphical Workflow Editor: Facilitates low-code workflow development and makes implementation more accessible. | ||
| Line 14: | Line 15: | ||
| * Performance: | * Performance: | ||
| * Open Source: Available under LGPL Open source license | * Open Source: Available under LGPL Open source license | ||
| + | |||
| + | {{ : | ||
| MuPIF utilizes an object-oriented approach, with abstract classes defining standardized interfaces introduced to represent simulation models and data types. | MuPIF utilizes an object-oriented approach, with abstract classes defining standardized interfaces introduced to represent simulation models and data types. | ||
| Line 20: | Line 23: | ||
| MuPIF achieves interoperability with standardization of application and data component interfaces and it is not reliant on standardized data structures or protocols. Any existing data representation or simulation model can be plugged in and used transparently, | MuPIF achieves interoperability with standardization of application and data component interfaces and it is not reliant on standardized data structures or protocols. Any existing data representation or simulation model can be plugged in and used transparently, | ||
| - | |||
| - | {{ : | ||
| Even though the platform can be used locally on a single computer orchestrating installed applications, | Even though the platform can be used locally on a single computer orchestrating installed applications, | ||
| Line 30: | Line 31: | ||
| ====== Documentation & Resources ====== | ====== Documentation & Resources ====== | ||
| + | * [[tutorials|MuPIF platform video tutorials]] | ||
| * The Musicode project MuPIF training video recording is available on YouTube: [[https:// | * The Musicode project MuPIF training video recording is available on YouTube: [[https:// | ||
| * The mupif/ | * The mupif/ | ||
| Line 126: | Line 128: | ||
| * [[http:// | * [[http:// | ||
| * DeeMa project (Deep-Learning and Optimisation Enabled Material Microstructure Design), funded by Technology Agency of the Czech Republic, grant agreement no. TH75020002. | * DeeMa project (Deep-Learning and Optimisation Enabled Material Microstructure Design), funded by Technology Agency of the Czech Republic, grant agreement no. TH75020002. | ||
| + | * INODIN project (Innovative methods for materials diagnostics and monitoring of engineering infrastructure to improve its durability and service life), funded by MŠMT, grant agreement CZ.02.01.01/ | ||
| | | ||
start.1746608781.txt.gz · Last modified: by bp
