Open jamesturner246 opened 11 months ago
I've just been having a look at this and while it might be possible, I think it'll be a fair amount of work (there are >50 uses of context.population()
).
Whether this is worth the effort or not kind of depends on what your longer-term refactoring plans are. Does pulling the population part out of context make sense?
I'm wondering whether it would make sense to split up RuntimeContext
into two different data structures: one for the immutable data (model parameters) and the other for mutable data (e.g. the population, maybe even the RNG).
I'm about to change a whole lot of the context structure shortly, so happy to put this in the backlog for now.
Right now it is not, and we don't need to write to the
RuntimeContext
object, only thePopulation
object contained therein.Requires changing the RF model interface
HierarchicalLinearModel
(a bad and misleading name -- should think about changing this soon) and derived classes.