Analysis tool support

tool support

While there are some special cases to be aware of, Modelica-based models work like Simcenter Amesim C-based libraries for the existing Simcenter Amesim analysis tools shown in the figure below. Modelica developers can leverage visualization tools, perform linear analysis, run design explorations and invoke scripts just like C-based Simcenter Amesim developers.

Analysis Tool	Feature
	Performance Analyzer		Run Statistics
	State Contributions
	Frequencies
	Linear Analysis		Eigen Values
	Modal Shapes
	Frequency Response
	Root Locus
	Design Exploration		DOE
	Optimization
	Monte Carlo
	Visualization		Plots
	Animations
	Dashboards
	Scripting		App Designer
	Python Scripts

Note that users should sometimes pay attention to certain special cases. For example, the method for calculating a models frequency response (e.g., Bode plots) requires that Simcenter Amesim have direct authority over the control signal. If the forcing function is buried inside a Modelica submodel, then Simcenter Amesim cannot manipulate it directly and therefore cannot produce the information needed for the frequency response plot. In such a case, the user can simply use one of the adapter models described in the Coupling Modelica and native Simcenter Amesim submodels section to "externalize" the control signal, allowing Simcenter Amesim to control it directly. Observer variables on the other hand, may remain inside the Modelica submodel and do not need to be exported.

Another note of interest is the subject of variable paths. When a user makes a plot and stores it in the model, the plot is referencing a variable path that tells the plot where to find the signal in the model. With the Modelica Editor, the user has the freedom to edit a Modelica model, and then use the Update Modelica model context menu from submodel mode. This freedom also gives developers the possibility of removing or modifying variable names. Any Simcenter Amesim plots referencing that variable path would no longer be able to find the variable of interest and would return empty results. Variable paths are used in many visualization tools (plots, animations, etc.) or scripts and therefore the user should make sure they reference the current submodels variable names.