Coverage decreased (-1.1%) to 76.808% when pulling 331c1a4 on don4get:feature/state-space-plot into 0d94329 on python-control:master.

Coverage decreased (-1.1%) to 77.075% when pulling 398828d on don4get:feature/state-space-plot into bcf5382 on python-control:master.

@don4get It would be useful if you could split this into two PRs, as you suggest. I have some questions about the use of heat maps; will post those once these have been split.

Hello, I splitted the PR in two, feel free to ask questions about the feature presented here.
Happy coding!

I'm not sure I understand the reasoning for having this function in the control systems toolbox. Is there a reason that looking at the heat map for state space matrices is useful? Since the matrices are not uniquely defined, seems like the heat map is kind of arbitrary.

I suggested this PR beacause I find it useful to look a system: is it sparse? in which form is it written? It also helps in one wants to check if his system looks well written at a glance. Let say someone wants to solve a problem on a python notebook. First thing is to right the system. To check for typo, he might want a state space pretty printing function, which is in fact this feature.

It s not about precise result, just to give insight.

Spyder has this kind of behavior in the variable brower:

My inclination at this point is to drop this PR. It seems to add functionality that is not specific to control systems (could be used for any matrix). Marking as wontfix but leaving in place for a while in case others want to chime in.