Define paradigm (and provide example) of defining template variables and overriding with instance variables about cyclus HOT 3 CLOSED

The most proper solution for this I can think of is to simply use public setters for parameters that will need run-time adjustment. Public methods also allow more proper testing. We really should try to stay away from testing via protected member vars - test code should not lock us down into specific implementations. I actually did a little bit of param exposing in RecipeReactor in 76c3246

from cyclus.

I feel like this issue is a little vague, and that, insofar as I understand the issue, your comment and the example of using setters and getters should be a sufficient solution for now. Real solutions and examples will likely arise from these notions when an immediate need for this functionality is apparent. I propose we call this issue closed unless there are complicating details that I haven't understood.

from cyclus.

I agree. Not only do I think getters/setters are a solution, I think they are 'the' solution. No need to complicate the core.

from cyclus.