SimLab Environment
The user can work in one of the three following environments:
-Fortran
-C/C++
-Matlab
and has to interact with SimLab from the selected working environment.
The following figure shows a typical configuration. In this case the user is using SimLab through the Matlab environment. All UA/SA commands are executed in the SimLab environment through the Matlab prompt. The SimLab environment contains all the DLLs for UA/SA that the user may need.
The code representing the model to be analyzed is usually a Matlab code present in the Matlab environment.
-Fortran
-C/C++
-Matlab
and has to interact with SimLab from the selected working environment.
The following figure shows a typical configuration. In this case the user is using SimLab through the Matlab environment. All UA/SA commands are executed in the SimLab environment through the Matlab prompt. The SimLab environment contains all the DLLs for UA/SA that the user may need.
The code representing the model to be analyzed is usually a Matlab code present in the Matlab environment.
Arrow 1 -
If the model
execution results are stored in an external file and we want to run an
SA on them it is necessary to previously load them into the SimLab
environment
(e.g. LoadModelOutputFile). This step allows to work inside SimLab with
the data obtained by a model execution outside the work environment.
Arrow 2 - If the model the user wants to analyze is implemented directly as Matlab code the user may load the model execution results in the SimLab environment by calling an appropriate command (e.g. LoadModelOutput)
Arrow 3 - In order to perform the SA or UA it will be necessary to call the specific SimLab commands (e.g. GetFastTotalValues). Once the analysis has been executed the results (indices) are passed to the MatLab environment.
Therefore SimLab is not an independent environment, since it needs another hosting environment (in this case Matlab) which allows it to work. In other words, SimLab can be considered as a black box which is able to prepare useful products (SA). In order to use it, we first have to open it and fill it with the ingredients that are necessary (inputs, models or model outputs). Once the results are produced (SA indices), we have to open the box again and extract those results.
Depending on which hosting environment we are using, commands to access and leave SimLab may be different; this tool results to be extremely flexible as it adapts to different programming languages depending on the complexity of the model or on the user particular needs.
Arrow 2 - If the model the user wants to analyze is implemented directly as Matlab code the user may load the model execution results in the SimLab environment by calling an appropriate command (e.g. LoadModelOutput)
Arrow 3 - In order to perform the SA or UA it will be necessary to call the specific SimLab commands (e.g. GetFastTotalValues). Once the analysis has been executed the results (indices) are passed to the MatLab environment.
Therefore SimLab is not an independent environment, since it needs another hosting environment (in this case Matlab) which allows it to work. In other words, SimLab can be considered as a black box which is able to prepare useful products (SA). In order to use it, we first have to open it and fill it with the ingredients that are necessary (inputs, models or model outputs). Once the results are produced (SA indices), we have to open the box again and extract those results.
Depending on which hosting environment we are using, commands to access and leave SimLab may be different; this tool results to be extremely flexible as it adapts to different programming languages depending on the complexity of the model or on the user particular needs.