Consider using atomic subcharts when one or more of these scenarios apply:
|Scenario||Reason for Using Atomic Subcharts||Reference||Tutorial|
You want to reuse the same state or subchart many times across different charts or models to facilitate large-scale modeling.
You can store an atomic subchart in a library to enable reuse across different charts and models. When you change an atomic subchart in a library, the change propagates to all links.
You want to use simulation to test your changes, one by one, without recompiling the entire chart.
When you modify an atomic subchart, recompilation occurs for only that object and not the entire chart.
You want to break a chart into standalone parts because multiple people are working on different parts of the chart.
Because atomic subcharts behave as standalone objects, people can work on different parts of a chart without affecting any work that someone else is doing.
You want to inspect Simulink® Coder™ or Embedded Coder® generated code manually for a specific part of a chart.
You can specify that code for an atomic subchart appears in a separate file for unit testing.