When building models, I start simple and get simple models. Because of various reasons, I add more and more controls for visualization or substantively extend my models. Later, I try to group controls into things relevant at setup, things relevant at runtime, just visualization-relevant controls, and model extensions. It becomes super large. Still good for me, but it loses its simplicity for educational purposes and can overwhelm new users with too many options. I think in the end it is a fundamental design problem with no standard solution. Still, the option to hide a certain part of controls and outputs would give an option to design a better learning path by focusing the user first on the essential things before “opening” advanced visualizations and model extensions.
Thanks for the suggestion, I’ve wanted something like this as well!