Tutorial 1 – Structure of the project file<\/h3>\nMASTERSIM<\/em> uses a simple project file that describes the simulation scenario. This project file has the extension msim<\/code> and contains all the data required to carry out a simulation.<\/p>\n\n\n\nA second file with the same name and the extension bm<\/code>is saved in the same directory as the project file. This contains the graphical representation of the simulation scenario. As the graphical network display is purely optional<\/em>, the bm<\/code>file can be omitted\/ignored\/deleted at will.<\/p>\n\n\n\n# Created:\tDi. Aug. 14 17:02:20 2022\n# LastModified:\tDi. Aug. 14 17:02:20 2022\n\n# Project file example for iterating GaussSeidel with time step adjustment\n#\n# No error test included, time step adjustment based on convergence failures.\ntStart 0 s\ntEnd 12 s\nhMax 30 min\nhMin 1e-06 s\nhFallBackLimit 0.001 s\nhStart 1e-07 s\nhOutputMin 0.12 s\nadjustStepSize no\npreventOversteppingOfEndTime yes\nabsTol 1e-06\nrelTol 0.01\nMasterMode GAUSS_JACOBI\nErrorControlMode NONE\nmaxIterations 1\nwriteInternalVariables yes\n\nsimulator 0 0 Part1 #ff447cb4 \"fmus\/simx\/Part1.fmu\"\nsimulator 1 1 Part2 #ffc38200 \"fmus\/simx\/Part2.fmu\"\nsimulator 2 1 Part3 #ffff0000 \"fmus\/simx\/Part3.fmu\"\n\ngraph Part1.x2 Part2.x2\ngraph Part1.x1 Part2.x1\ngraph Part2.x3 Part3.x3\ngraph Part3.x4 Part2.x4\n\nparameters Part1.para1 14.3<\/code><\/pre>\n<\/div><\/div>\n\nTutorial 2 – Introduction and basic concepts<\/h3>\nMASTERSIM<\/em> is a co-simulation master program that supports FMI co-simulation. If co-simulation is something completely new to you or you are not yet familiar with the functional mock-up interface (FMI), I recommend that you first read a little about the basics, e.g. on the fmi-standard.org<\/a> website.<\/p>\n\n\n\nMASTERSIM<\/em> basically connects different simulation models and exchanges data between simulation slaves at runtime<\/em>. The following diagram illustrates the individual components of the program and the data exchange between them.<\/p>\n\n\n\n![\"FMI](\"http:\/\/bauklimatik-dresden.de\/wp-content\/uploads\/2023\/02\/DataFlowDiagram.png\")
Diagram of the data flow (files) and programs involved<\/em><\/figcaption><\/figure>\n\n\n\nMASTERSIM<\/em> consists of two parts:<\/p>\n\n\n\n\n- a graphical user interface (GUI<\/em>) and<\/li>\n\n\n\n
- the MasterSimulator<\/em> simulation program for the command line<\/li>\n<\/ol>\n\n\n\n
The interface makes it very easy to create, adapt and modify simulation projects. A simulation project is saved in two files, the MASTERSIM<\/em> project and the graphical representation (linking scheme). The latter is optional and not necessary for the simulation.<\/p>\n\n\n\nThe simulation is executed by the command line program MasterSimulator<\/em>, which reads project files, imports referenced FMUs and executes the simulation. The results generated, both by MasterSimulator<\/em> itself and those of the slaves, are then used by further processing tools to visualize and analyse the results (the free analysis tool with PostProc2<\/a> is very well suited for this and my recommendation for MASTERSIM<\/em> result evaluation).<\/p>\n\n\n\nThe separation between the user interface and the actual simulator makes it very easy to use MASTERSIM<\/em> in a scripted environment or for a systematic variant study as described below in the Workflows<\/a> section.<\/p>\n<\/div><\/div>\n\nSpecial topics, tips and tricks<\/h3>\nWith various methods, MASTERSIM<\/em> can be used much more efficiently and extensively than seems possible using the user interface alone. Script-based editing or creation of the MASTERSIM<\/em> project file is just one way of increasing efficiency. Further ideas can be found in the tutorials listed and in the manual<\/a>.<\/p>\n\n\n\n<\/p>\n<\/div><\/div>\n\n
\n\n\n\n
MASTERSIM<\/em> uses a simple project file that describes the simulation scenario. This project file has the extension A second file with the same name and the extension MASTERSIM<\/em> is a co-simulation master program that supports FMI co-simulation. If co-simulation is something completely new to you or you are not yet familiar with the functional mock-up interface (FMI), I recommend that you first read a little about the basics, e.g. on the fmi-standard.org<\/a> website.<\/p>\n\n\n\n MASTERSIM<\/em> basically connects different simulation models and exchanges data between simulation slaves at runtime<\/em>. The following diagram illustrates the individual components of the program and the data exchange between them.<\/p>\n\n\n\n MASTERSIM<\/em> consists of two parts:<\/p>\n\n\n\n The interface makes it very easy to create, adapt and modify simulation projects. A simulation project is saved in two files, the MASTERSIM<\/em> project and the graphical representation (linking scheme). The latter is optional and not necessary for the simulation.<\/p>\n\n\n\n The simulation is executed by the command line program MasterSimulator<\/em>, which reads project files, imports referenced FMUs and executes the simulation. The results generated, both by MasterSimulator<\/em> itself and those of the slaves, are then used by further processing tools to visualize and analyse the results (the free analysis tool with PostProc2<\/a> is very well suited for this and my recommendation for MASTERSIM<\/em> result evaluation).<\/p>\n\n\n\n The separation between the user interface and the actual simulator makes it very easy to use MASTERSIM<\/em> in a scripted environment or for a systematic variant study as described below in the Workflows<\/a> section.<\/p>\n<\/div><\/div>\n\n With various methods, MASTERSIM<\/em> can be used much more efficiently and extensively than seems possible using the user interface alone. Script-based editing or creation of the MASTERSIM<\/em> project file is just one way of increasing efficiency. Further ideas can be found in the tutorials listed and in the manual<\/a>.<\/p>\n\n\n\n <\/p>\n<\/div><\/div>\n\nmsim<\/code> and contains all the data required to carry out a simulation.<\/p>\n\n\n\nbm<\/code>is saved in the same directory as the project file. This contains the graphical representation of the simulation scenario. As the graphical network display is purely optional<\/em>, the bm<\/code>file can be omitted\/ignored\/deleted at will.<\/p>\n\n\n\n# Created:\tDi. Aug. 14 17:02:20 2022\n# LastModified:\tDi. Aug. 14 17:02:20 2022\n\n# Project file example for iterating GaussSeidel with time step adjustment\n#\n# No error test included, time step adjustment based on convergence failures.\ntStart 0 s\ntEnd 12 s\nhMax 30 min\nhMin 1e-06 s\nhFallBackLimit 0.001 s\nhStart 1e-07 s\nhOutputMin 0.12 s\nadjustStepSize no\npreventOversteppingOfEndTime yes\nabsTol 1e-06\nrelTol 0.01\nMasterMode GAUSS_JACOBI\nErrorControlMode NONE\nmaxIterations 1\nwriteInternalVariables yes\n\nsimulator 0 0 Part1 #ff447cb4 \"fmus\/simx\/Part1.fmu\"\nsimulator 1 1 Part2 #ffc38200 \"fmus\/simx\/Part2.fmu\"\nsimulator 2 1 Part3 #ffff0000 \"fmus\/simx\/Part3.fmu\"\n\ngraph Part1.x2 Part2.x2\ngraph Part1.x1 Part2.x1\ngraph Part2.x3 Part3.x3\ngraph Part3.x4 Part2.x4\n\nparameters Part1.para1 14.3<\/code><\/pre>\n<\/div><\/div>\n\nTutorial 2 – Introduction and basic concepts<\/h3>
\n
Special topics, tips and tricks<\/h3>
\n\n