slist (Simulink Reference)

Display the sorted list of a model's root system and of each of its nonvirtual subsystems

Syntax

```
slist
```

Description

The slist command displays the sorted list of a model's root system and each of its nonvirtual subsystems. For example, the sorted list for the vdp model's root system is

---- Sorted list for 'vdp' [9 nonvirtual blocks, directFeed=0]
  0:0    'vdp/x1' (Integrator)
  0:1    'vdp/Out1' (Outport)
  0:2    'vdp/x2' (Integrator)
  0:3    'vdp/Out2' (Outport)
  0:4    'vdp/Scope' (Scope)
  0:5    'vdp/Fcn' (Fcn)
  0:6    'vdp/Product' (Product)
  0:7    'vdp/Mu' (Gain)
  0:8    'vdp/Sum' (Sum)

For each system (root or nonvirtual), the slist command displays a title line followed by an entry for each block in the order in which the blocks appear in the sorted list. The title line specifies the name of the system, the number of nonvirtual blocks that the system contains, and the number of blocks in the system that have direct feedthrough ports. Each block entry lists the block's id and the name and type of the block. The block id consists of a system index and a block index separated by a colon (s:b). The block index is the position of the block in the sorted list. The system index is the order in which Simulink generated the system's sorted list. The system index has no special significance. It simply allows blocks that appear in the same position in different sorted lists to have unique identifiers.

A sorted list is a list of a root system or nonvirtual subsystem's blocks sorted according to data dependencies and other criteria. Simulink uses sorted lists to create block method execution lists (see elist) for root system and nonvirtual subsystem methods that invoke the corresponding methods of the blocks that the root system or subsystem contains. In general, root system and nonvirtual subsystem methods invoke the block methods in the same order as the blocks appear in the sorted list. However, significant exceptions occur. For example, execution lists for multitask models group all blocks operating at the same rate (i.e., in the same task) together with slower groups appearing later than faster groups. The grouping of methods by task can result in an order of block method execution that differs from the order in which blocks appear in the sorted list. However, within groups, methods execute in the same order as the corresponding blocks appear in the sorted list.

See Also

systems, elist

run states