Reconcile Config class #63
Description
This class encodes species information, can be used for generating impacts for things such as "harvest" or "pruning" or "fertilizer", and use it to inform another multiplier.
I think something like... a config can span an event, one we know will be relevant, so we dont need a second lookup perhaps (for configs and events). Have to think through where the inefficiencies are.
Maybe config isnt even required? How is it used right now?
We have a step where we find the relevant configs.
For example... Config stores info about a species, then can be used to generate harvest functions like the ones in simulate.py. Should events be able to take configs as arguments? So, rather than span four guate-functions, encode info in config, and span on the fly? Seems like itd be an inefficiency for runtime but efficiency for storage. Easier to store a config and a template callable than a bunch of generated functions from that template.