About Behavior Experience

A behavior experience (simulation object) is a reference which links a logical or functional system model with its simulation data.

This section deals with information you should know before working with behavior experiences.

This page discusses:

Behavior Experience

The behavior experience consists of three components:

  • Model: The model to be simulated and its associated representation.
  • Scenario: The parameters that define the simulation, including scenarios, excitations, and probes.
  • Result: The postprocessing data, including watchlists and plots.

The model is edited within the Functional & Logical Design app, or the Dymola Behavior Modeling app.

The simulation specifications and results are edited within the Behavior Experience app.

When creating a behavior experience, an empty scenario is automatically created.

Important:
  • To be able to simulate, a valid compiler must be installed. The existence of such a compiler can be verified. See Native Apps Preferences Guide: Compiler for more information.
  • To be able to simulate logical-physical models (models containing both physical products and logical components) you must have the Mechanical Systems Experience app.

Model

Different models can be simulated in the Behavior Experience app:

  • Functional models with Dymola behavior.

    Such models are created from the Functional & Logical Design app.

  • Logical models with Dymola behavior.

    Such models are created from the Functional & Logical Design app.

  • Logical-physical models (models containing both physical products and logical components).

    Such models are created from the Functional & Logical Design app. See Functional & Logical Design UserĀ“s Guide: Mapping of Logical and Physical Models. They are computed like logical models, and the same type of results are available.

  • Stand-alone Dymola behavior models.

    Such models are created from the Dymola Behavior Modeling app.

Scenario

A scenario aggregates all the specifications needed for a simulation.

Those specifications include:

You can create as many scenarios as needed, by Adding or Editing a Scenario.

Results

This is the output of a scenario. When a simulation is computed, the variable values can be displayed in (refer also to previous section):

  • Watchlists (in the Scenario window)
  • Plot windows
  • Modelica complete results
  • Steady state results
  • Camera viewers (Viewer windows)

You can visualize and manage results in the Variable Browser, see Working with the Variable Browser.

These results are also stored into the behavior experience representation.

Information about the computation of the simulation is displayed in the Incident Diagnosis window. See Viewing Computation Incidents.

Clash computation and handling is available for logical-physical models, see Detecting and Handling Physical Clashes.