| Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision |
| wiki:welcome [2016/05/06 09:56] – Initial version bp | wiki:welcome [2016/05/06 10:14] – [Authors & Credits] bp |
|---|
| ====== MuPIF ====== | ====== MuPIF ====== |
| {{ :mupif:mupif_logo.png?250|}} | {{ :wiki:images:mupif_logo.png?250|}} |
| A reliable multiscale/multiphysics numerical modeling requires including all relevant physical phenomena along the process chain, typically involving multiple scales, and the combination of knowledge from multiple fields. A pragmatic approach lies in combining existing tools, to build a customized multiphysics simulation chains. In order to achieve such a modular approach a multiphysics integration framework, called MuPIF has been designed, which provides an underlying infrastructure enabling high-level data exchange and steering of individual applications. | A reliable multiscale/multiphysics numerical modeling requires including all relevant physical phenomena along the process chain, typically involving multiple scales, and the combination of knowledge from multiple fields. A pragmatic approach lies in combining existing tools, to build a customized multiphysics simulation chains. In order to achieve such a modular approach a multiphysics integration framework, called MuPIF has been designed, which provides an underlying infrastructure enabling high-level data exchange and steering of individual applications. |
| |
| ===== Framework Design ===== | ===== Framework Design ===== |
| One of the main objectives is to develop an integrated modelling platform targeted to multiscale and multi-physics engineering problems. The approach followed in MuPIF is based on an system of distributed, interacting objects designed to solve given problem. The individual objects represent entities in the problem domain, including individual simulation packages, but also the data, such as fields and properties. The abstract classes are introduced for all entities in the model space. They define a common interface that needs to be implemented by any derived class, representing particular implementation of specific component. Such interface concept allows using any derived class on a very abstract level, using common services defined by abstract class, without being concerned with the implementation details of an individual software component. This essentially allows to manipulate all simulation tools using the same interface. Moreover, as the simulation data are represented by objects as well, the platform is independent on particular data format(s), as the exchanged data (such as fields and properties) can be manipulated using the same abstract interface. Therefore, the focus on services is provided by objects (object interfaces) and not on underlying data itself. | One of the main objectives is to develop an integrated modelling platform targeted to multiscale and multi-physics engineering problems. The approach followed in MuPIF is based on an system of distributed, interacting objects designed to solve given problem. The individual objects represent entities in the problem domain, including individual simulation packages, but also the data, such as fields and properties. The abstract classes are introduced for all entities in the model space. They define a common interface that needs to be implemented by any derived class, representing particular implementation of specific component. Such interface concept allows using any derived class on a very abstract level, using common services defined by abstract class, without being concerned with the implementation details of an individual software component. This essentially allows to manipulate all simulation tools using the same interface. Moreover, as the simulation data are represented by objects as well, the platform is independent on particular data format(s), as the exchanged data (such as fields and properties) can be manipulated using the same abstract interface. Therefore, the focus on services is provided by objects (object interfaces) and not on underlying data itself. |
| {{ :mupif:mupif-map.png?direct&400|MuPIF Features}} | {{ :wiki:images:mupif-map.png?direct&400|MuPIF Features}} |
| |
| The complex simulation pipeline developed in MuPIF consists of top-level script in Python language (called scenario) enriched by newly introduced classes. Even though the platform can be used locally on a single computer orchestrating installed applications, the real strength of the MMP platform is its distributed design, allowing to execute simulation scenarios involving remote applications. MuPIF provides a transparent distributed object system, which takes care of the network communication between the objects when they are distributed over different machines on the network. One can just call a method on a remote object as if it were a local object – the use of remote objects is (almost) transparent. This is achieved by using the concept of proxies representing remote objects, which forward the calls to the remote objects and pass the results back to the calling code. In this way, there is no difference between simulation script for local or distributed case, except for the initialization, where, instead of creating local object, one has to connect to the remote object. | The complex simulation pipeline developed in MuPIF consists of top-level script in Python language (called scenario) enriched by newly introduced classes. Even though the platform can be used locally on a single computer orchestrating installed applications, the real strength of the MMP platform is its distributed design, allowing to execute simulation scenarios involving remote applications. MuPIF provides a transparent distributed object system, which takes care of the network communication between the objects when they are distributed over different machines on the network. One can just call a method on a remote object as if it were a local object – the use of remote objects is (almost) transparent. This is achieved by using the concept of proxies representing remote objects, which forward the calls to the remote objects and pass the results back to the calling code. In this way, there is no difference between simulation script for local or distributed case, except for the initialization, where, instead of creating local object, one has to connect to the remote object. |
| ===== Authors & Credits ===== | ===== Authors & Credits ===== |
| Mupif developpers: | Mupif developpers: |
| * Bořek Patzák (Lead Developper) | * [[http://mech.fsv.cvut.cz/~bp|Bořek Patzák]] (Lead Developper) |
| * Vit Šmilauer | * [[http://mech.fsv.cvut.cz/~smilauer/|Vit Šmilauer]] |
| * Guillaume Pacquaut | * Guillaume Pacquaut |
| * Václav Šmilauer | * Václav Šmilauer |
| * Former developpers: Daniel Rypl, Jaroslav Kruis | * Former developpers: Daniel Rypl, Jaroslav Kruis |
| | Contact: info@oofem.org |
| ===== Acknowledgements===== | ===== Acknowledgements===== |
| * The development of MuPIF has been funded by Grant Agency of the Czech Republic - Projects No. P105/10/1402. | * The development of MuPIF has been funded by Grant Agency of the Czech Republic - Projects No. P105/10/1402. |
| * The development is at present supported by the EU project [[http://mmp-project.eu/|Multiscale Modelling Platform: Smart design of nano-enabled products in green technologies]], project number 604279. | * The development is at present supported by the EU project [[http://mmp-project.eu/|Multiscale Modelling Platform: Smart design of nano-enabled products in green technologies]], project number 604279. |
| |
| {{gallery>:wiki}} | |
