Code organization issues after successful spike into creating transposed results array.

[rklancer]

1. This spike created a whole mess of new globals, model_md2d_results_RADIUS and friends, that need to be reconsidered and/or put into a namespace.
2. It also added a long stanza to the already-overloaded computeOutputState method of md2d. This method needs to be split up into separate helpers each of which is responsible for one thing.
3. That said, transposition is possibly a view concern and not the responsibility of the md2d engine at all, but rather of the overlying 'modeler'. (Following the rule that most things that don't need to be in the md2d closure to make the inner loop go, probably shouldn't be there.) I'll have to think about this more carefully, however.