Can't tell which inputs are intermediate results.

[philngo]

Running the get_inputs function on a meter will expose all necessary inputs; however, some inputs are automatically generated during the course of running the meter (quite a few of them, actually) and that makes it particularly difficult to tell which ones need to be supplied on the outermost evaluate call.

[philngo]

Dealing with this sort of thing might justify some sort of results or outputs object which stores a bit more metadata than a dictionary should. Up until this point, we haven't needed anything more than a dict of outputs.

[philngo]

DataCollection objects help address this issue by putting more structure on meter outputs. For instance, outputs can be tagged to indicate that they are intermediate.