cyclus/core — Issue #48: StateID handling and comp recording should be managed by Material class
Author: rwcarlsen
Created: 2012-02-28 17:02:11+00:00
State: open
Labels: Output Side

Note that this applies to matt's db work that is not all fully pushed to blessed yet.

We don't want to record every state that an IsoVector is in - every time somebody is manipulating recipes or doing stuff within their concrete agents, we would have no choice but to record every little change. If someone were to create an intermediate/temp IsoVector object, it would be recorded. We only want to record compositions of IsoVector's that are "participating" in the simulation - and the defining characteristic of "participating" IsoVector is their inclusion in a Material object. The addToTable method can stay in the IsoVector class, but the functionality that exists in trackComposition needs to somehow be migrated into the material class.

If you wanted to keep stateID_ tracking in the cyclus core, it too should be shifted into the material class.

@gidden