Hi Danus,
Managing data dictionaries in Simulink can indeed be challenging for large models. But you could try out the following tips in order to improve the management of your "Desgin Data" for Simulink.
1) Flat Structure with Naming Conventions:
- Since Simulink does not support accessing nested structures directly in blocks, consider using a flat structure in your data dictionary.
- Use naming conventions to simulate hierarchy. For example, use names like Subsystem1_LUT, Subsystem2_Parameter, etc. This approach maintains clarity and organization without nesting.
- But for very large models, this may not be very relevant.
2) Custom Data Types and Buses:
- For grouping related parameters, consider using Simulink.Bus objects. Buses allow you to group signals logically without nesting them in a struct.
- Define a Bus object for each subsystem and use it to bundle relevant signals.
- The following MATLAB answers post suggests a good way of managing the Simulink.Bus objects as well: https://www.mathworks.com/matlabcentral/answers/229389-bus-objects-using-multiple-data-dictionaries-in-large-models
3) Separate Dictionaries:
- If your model is large and consists of multiple subsystems, consider using separate data dictionaries for each subsystem. This can help in managing the data more effectively and maintaining a clear structure.
- The following MathWorks documentation is a very good read if you are using a lot of Model References in your model: https://www.mathworks.com/help/simulink/ug/compose-dictionary-hierarchy.html
- For information on "reference dictionaries" you can refer to: https://www.mathworks.com/help/simulink/ug/partition-dictionary-into-reference-dictionaries.html
The above tips should resolve the issues with Stateflow as well, since you can directly access the data from SLDD if it is defined as "Data"
To summarize, I think your next steps would be to explore how you can manage your "Design Data" using multiple dictionaries instead of making your design data itself a complex one.
I hope this helps.
