A: There are several ways to speed up your model.
1) Observe discontinuities:
CPU time problems in LMS Imagine.Lab Amesim models come very often from a lot of discontinuities.
Discontinuities are always taken into account in LMS Amesim. To see them, it is necessary to check the option “discontinuities printout” in the run parameters.
Processing a lot of discontinuities might slow down the solver. Indeed for each of them the solver has to interpolate backwards, to localilize the discontinuity precisely and to restart from the discontinuity point.
Most of the time discontinuities come from tables which are read from ASCII files and interpolated linearly. The linear interpolation process consists in using a linear polynomial to compute a value in a given interval.
Basically, the value y(x) is computed as y(x) = Yi + (Yi+1 - Yi) * (x – Xi) / (Xi+1 - Xi) with x inside the interval [Xi, Xi+1].
It is important to remark that the slope of each interval differs a lot. Thus, when x passes from one interval to another, it is important to catch this event by handling a discontinuity.
Submodels of the signal control library can optionally disable this discontinuity handling mechanism.
However, disabling the discontinuity handling is only recommended if the data in the table has small variations of their slopes between each interval.
When deactivating the unnecessary discontinuities you can have huge speed-ups on the CPU time (e.g. a model running in 27s. instead of 227 s.)
2) The Performance Analyzer tool:
This tool will automatically highlight the component which consumes the most energy in your system. A double-click on the row will label the corresponding component on the sketch, so that it can give you an indication where you should start first with the simplification or speed up modifications.
The Performance Analyzer allows you to check the solver run statistics, the number of discontinuities, the state contributions, all the frequencies and associated damping of the model. This tool can identify inadequate parameters of your model.
3) Generic cosimulation technique:
Using the hydraulic library:
For any library: (information about the libraries here)
This technique is only applicable to a system which can be divided. The two subsystems should have a limited (or slow) interaction. A demo model ClutchFading illustrates a situation where a split is easily achieved. Thermal effects are coupled to a mechanical model with higher dynamics. Using cosimulation in that context is very efficient.
4) Reduce complexity:
When multiple small volumes are located at different places in the hydraulic circuit, we usually recommend to create an equivalent larger volume to reduce the number of state equations that the solver generates.
It is also possible to choose simpler submodels if the fidelity and accuracy are still acceptable.
5) Some general tips: