Automatically select reusable components
Option to enable automatic selection of reusable components for scalable and incremental compilation
Since R2026a
Model Configuration Pane: Simscape
Description
This parameter enables automatic selection of reusable components for scalable and incremental compilation, which helps you simplify the process of configuring a model to improve model compilation time.
If this parameter is on, the software automatically identifies appropriate reusable
components and subsystems during compilation and marks them as reusable. This automatic
selection process respects the explicit designations made by setting the
simscape.reuse.setConfig parameter or the CompileReuse
attribute. If you explicitly designate components as reusable, they continue to be treated as
reusable, in addition to the automatically selected ones.
Dependencies
To enable this parameter, select the Reuse components during compilation parameter.
Settings
- On
The software automatically identifies appropriate reusable components and subsystems during compilation and marks them as reusable.
- Off
There is no automatic selection of reusable components. You must explicitly designate which components are reusable. For more information, see How to Designate Reusable Components.
Note
To avoid backward compatibility issues, for models existing prior to R2026a, if Reuse components during compilation is on, the default value of the Automatically select reusable components parameter is off. For new models, as well as for existing models created prior to R2026a but not using scalable and incremental compilation, once you select Reuse components during compilation, the Automatically select reusable components is on by default.
Recommended Settings
| Application | Setting |
|---|---|
| Debugging | No Impact |
| Traceability | No Impact |
| Efficiency | On |
| Safety precaution | No Impact |
Programmatic Use
Parameter:
SimscapeAutoSelectReusableComponents |
| Type: character vector | string scalar |
Value:
"on" | "off" |
Default:
"on" |
Version History
Introduced in R2026a
