Non-virtual subsystems in ADM_Integrated_Logic

1. Code Mapping [hide]

The following table:

  • provides a mapping from the non-virtual subsystems in the model to functions or reusable functions in the generated code and
  • notes exceptions that caused some non-virtual subsystems to not reuse code even though they were assigned a function packaging setting ('Function packaging' entry on the Subsystem Block Dialog) of 'Auto' or 'Reusable function'.

Subsystem Reuse Setting Reuse Outcome Outcome Diagnostic
<S52> Auto Reusable Function(S52) normal
<S53> Auto Reusable Function(S52) normal
<S10> Auto Reusable Function(S10) normal
<S12> Auto Reusable Function(S10) normal
<S11> Auto Reusable Function(S11) normal
<S13> Auto Reusable Function(S11) normal
<S2> Auto Inline normal
<S20> Auto Inline normal
<S22> Auto Inline normal
<S23> Auto Inline normal
<S25> Auto Inline normal
<S5> Auto Inline normal
<S6> Auto Inline normal
<S40> Auto Inline normal
<S41> Auto Inline normal
<S42> Auto Inline normal
<S51> Auto Inline normal
<S48> Auto Inline normal
<S9> Auto Inline normal
<S14> Auto Inline normal
<S15> Auto Inline normal
<S59> Auto Inline normal

2. Code Reuse Exceptions [hide]

The following section provides details on each exception that caused a non-virtual subsystem with a function packaging setting of

  • 'Auto' to become an inlined code segment,
  • 'Auto' to become a non-reusable function without arguments, or
  • 'Reusable function' to become a non-reusable function without arguments.
Note:This section does not report graphically identical non-virtual subsystems marked as 'Auto' that were not reused due to differences in their functional properties (such as dimensions, datatypes, work vectors, parameters, etc.). You may identify reasons for non-reuse in such cases by inspecting the differences in the functional attributes of the subsystems in the model or in the inlined generated code.


No reuse exception in model