Main Content


Visualize task scheduling

Since R2021a



schedule(executionProfile), using the Simulation Data Inspector, helps you to visualize how code was executed on the target hardware in the last software-in-the-loop (SIL), processor-in-the-loop (PIL), or XCP-based external mode simulation.

schedule(executionProfile,Name,Value) uses name-value arguments to control the display of function execution and simulation time.


collapse all

This example uses a SIL simulation to show how you can visualize task scheduling. For an example that uses an XCP external mode simulation, see Visualize Task Scheduling in XCP External Mode Simulation.

Run a SIL simulation with a model that is configured to generate a workspace variable with execution-time measurements.

openExample('ecoder/SILPILVerificationExample', ...

% Disable Simulink Code Coverage and third-party code coverage analysis
          'CovEnable', 'off');
covSettings = get_param('SILTopModel', 'CodeCoverageSettings');
covSettings.CoverageTool = 'None';
set_param('SILTopModel', 'CodeCoverageSettings', covSettings);

% Configure code execution time profiling
          'CodeExecutionProfiling', 'on');
          'CodeProfilingInstrumentation', 'Detailed');
          'CodeProfilingSaveOptions', 'AllData');
simOut = sim('SILTopModel');

The simulation generates the variable executionProfile (default) in the object simOut.

At the end of the SIL simulation, open the Code Profile Analyzer:

  1. Click the SIL/PIL tab.

  2. In the Results gallery, under Execution Profiling Results, click Code Profile Analyser.

In the Analysis section, click Function Execution. You see execution-time metrics for six code sections, for example, the step [0.1 0] task and the CounterTypeA and CounterTypeB functions.

To visualize how the tasks are scheduled and generated code is executed, in the Results section, click Generate Schedule. Or, in the Command Window, enter:


The Simulation Data Inspector displays task and simulation time plots.

In each task plot, the Y-axis lists tasks and functions executed. From the plots, you can infer the following information:

  • The order in which tasks run.

    If the model is multi-rate, you can see how Simulink® schedules the different rates (a task for each rate).

  • The time that is required to execute a task or a function, computed as the difference between the stop and start times. For example, observe that CounterTypeB takes less time to run than CounterTypeA. When a task is not running, the Y-axis value of the plot is NotRunning.

  • The order in which functions run within a task. For example, in the initialize task, counterTypeA_Init function runs before counterTypeB_Init function. If function calls are nested, you can see the execution order of the functions.

The last plot shows the simulation time when the tasks and functions are executed.

Input Arguments

collapse all

Variable specified by the Workspace variable configuration parameter, which contains the code execution profiling data. The SIL or PIL simulation generates the variable.

Name-Value Arguments

Specify optional pairs of arguments as Name1=Value1,...,NameN=ValueN, where Name is the argument name and Value is the corresponding value. Name-value arguments must appear after other arguments, but the order of the pairs does not matter.

Before R2021a, use commas to separate each name and value, and enclose Name in quotes.

Example: schedule(simOut.executionProfile, 'ShowTasksOnly', false, 'StartSimTime', 0.1, 'StopSimTime', 5.7)

Control display of function execution plots:

  • true –– Display task execution only. Do not display function execution.

  • false –– Display task and function execution.

Specify maximum number of points to display.

Specify simulation time at the start of the display.

Specify simulation time at the end of the display.

Version History

Introduced in R2021a