It's currently really messy passing this into the built-in summary (very-long-named-parameters-and-there-are-two-of-them-:-)

If I had my druthers, I'd add a computeSat =T option to mxRun()

The saturated/ind models can be cached, and would be computed only once, when the user changes the data.

Maybe run a checksum on model@data@observed, (and model@manifestVars), then mark the sat/ind models dirty when this is not equal to a cached value.

Also, need to decide whether to
1a. Calc both ind and sat models: if only the sat is done, it will not meet the needs of our actual users.
1b. Whether to calc ind model analytically
2. Whether to handle submodels
3. How to check the model is valid for the sat/ind solutions being proposed (definition variables etc.)
4. Support non-RAM models.
5. Function and parameter names that encompass saturated and independence models.