Isolating Dependencies of an Actuator Subsystem

This example demonstrates highlighting model items that a subsystem depends on. It also demonstrates generating a standalone model slice from the model highlight.

Choose Starting Points and Direction

  1. Open the f14 example model.

    openExample('simulink/AddBlockFromAnotherModelExample,'f14')

  2. On the Apps tab, under Model Verification, Validation, and Test gallery, click Model Slicer.

    Model Slice for the f14 model

  3. In the Model Slicer, click the arrow to expand the Slice configuration list list. Set the slice properties:

    • Name: Actuator_slice

    • To the right of Name, click the colored square to set the highlight color. Choose magenta from the palette.

    • Signal Propagation: upstream.

  4. Add the Actuator Model subsystem as a starting point. In the model, right-click the Actuator Model subsystem and select Model Slicer > Add as Starting Point.

    Actuator Model shown as Starting Point for Model Slicer

View Precedents and Generate Model Slice

  1. The model highlights the upstream dependencies of the Actuator Model subsystem.

    Simulink canvas for f14 model with dependencies highlighted

    Trace the following dependency path. Aircraft Dynamics Model is highlighted via the Pitch Rate q signal, which is an input to Controller, the output of which feeds Actuator Model.

  2. Generate a standalone model containing the highlighted model items:

    1. In the Model Slicer, click Generate slice.

    2. In the Select File to Write dialog box, select the save location and enter actuator_slice_model.

    3. Click Save.

  3. The sliced model contains the highlighted model items.

    Simulink canvas for sliced model that contains the upstream dependencies

  4. To remove highlighting from the model, close the Model Slicer.