You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* using same bottom margin as text sections
* renaming title
* changing the logo
* typos
* Updated logo and page icon
* updates based on review comments #61
Co-authored-by: Ćésar Carvalho <[email protected]>
Copy file name to clipboardExpand all lines: index.md
+34-19Lines changed: 34 additions & 19 deletions
Original file line number
Diff line number
Diff line change
@@ -6,29 +6,44 @@ has_toc: false
6
6
youtubeId: E5KumnkeKO8
7
7
---
8
8
9
-
# Core Simulation Environment
10
-
The Core Simulation Environment (CSE) is an open source software for co-simulation, built on a combination of technical solutions from the Open Simulation Platform (OSP) initiators and other established industrial solutions. The key working principle has been to use the best available technology and knowledge to meet the requirements for the OSP to efficiently serve its purpose. The CSE source code will be made available on GitHub, free of charge, through the MPL 2.0 open source licence.
11
-
The open-source software coined the CSE produced in the OSP JIP consists of the following elements:
9
+
<divstyle="text-align: right">
10
+
<b>
11
+
<a href="https://github.com/open-simulation-platform">OSP</a> on GitHub
12
+
</b>
13
+
</div>
14
+
15
+
# Open Simulation Platform Software
16
+
The open source software for co-simulation is built on a combination of technical solutions from the
17
+
Open Simulation Platform (OSP) initiators and other established industrial solutions.
18
+
The key working principle has been to use the best available technology and knowledge to meet the requirements for
19
+
the OSP to efficiently serve its purpose. The source code for all software except `kopl` is made available on
20
+
[GitHub](https://github.com/open-simulation-platform), free of charge, through the MPL 2.0 open source licence.
12
21
13
22
{% include youtubePlayer.html id=page.youtubeId %}
With OSP, simulation models are interconnected using the Functional Mock-up Interface ([FMI](https://fmi-standard.org/))
36
+
co-simulation interface. Based on input-output variable mapping, the OSP master algorithm routes the data between the
37
+
models.
22
38
23
-
The conceptual architecture of the co-simulation is illustrated as in figure below. The models are connected using the standardized Functional Mock-up Interface (FMI) co-simulation interface. Based on the input-output variable mapping included in the configuration file, the OSP master algorithm routes the data between the models.
39
+
There is currently support for FMI 2.0 (including FMI 2.0.1) and FMI 1.0. FMI 3.0 will be supported when this standard
40
+
becomes operational. The structure of the co-simulated system can be defined using the System Structure & Parameterization
41
+
standard ([SSP](https://ssp-standard.org/)) or the new model interface standard OSP Interface Specification
42
+
([OSP-IS]()) developed in the OSP project.
24
43
25
-
<figure>
26
-
<imgsrc="/assets/img/cseFig1.png"width="500">
27
-
</figure>
44
+
The main benefit introduced with OSP-IS is the possibility to define FMU interconnections at a higher level, i.e. variable
45
+
group connections rather than scalar connections. Additionally, it enables automatic unit conversions and provides the a
46
+
priori validation of the system configuration utilizing an ontology that models the connection types.
28
47
29
-
Currently, the OSP is supporting [FMI 2.0 and FMI 1.0](https://fmi-standard.org/) and will be updated to support FMI 3.0 when this standard becomes operational.
30
-
The structure of the co-simulated system can be defined using the System Structure & Parameterization (SSP) standard or the new model interface standard MSMI (Marine System Model Interface) developed in the OSP project.
31
-
Both standards can be used to include Functional Mock-up Unit (FMUs), defining their interconnections, initial values for simulation variables and individual model step sizes.
32
-
The benefit introduced with MSMI is the possibility to defining FMU interconnections at a higher level, i.e. variable group connections rather than scalar connections.
33
-
Additionally, it enables automatic unit conversions and provides the a priori validation of the system configuration utilizing an ontology that models the connection types.
34
-
CSE comes with example configurations containing FMUs and co-simulation configuration exemplified in both MSMI and SSP.
48
+
OSP comes with [example configurations](/demo-cases) containing FMUs and co-simulation configuration exemplified using both OSP-IS and
0 commit comments