As our config file grows we should start to think about how to limit the amount of parameters that land in a a final config file. As of right now, the config file recieves the default for all the vaules possible in config after the user is done with it.
@scotthavens has started to add some more options and suggested using "Hidden sections" in the core config to manage this.
E.G.
Input parameters
[air_temp]
distribution: idw
CoreConfig Recipes
[_distribution_idw]
slope: = -1
The would be seen by smrf the same as
[air_temp]
distribution: idw
slope: -1
The trick here will be managing the options associate with an option that is set in the recipe and can be set by the module.
Questions to answer:
How much repetition are we trying to avoid? (i.e. do we somehow standardize slope on its own?)
How do we handle options for an item thats in a recipe? Do use the section the recipe is being called from? Or do we have the options available be set in the recipe?
As our config file grows we should start to think about how to limit the amount of parameters that land in a a final config file. As of right now, the config file recieves the default for all the vaules possible in config after the user is done with it. @scotthavens has started to add some more options and suggested using "Hidden sections" in the core config to manage this.
E.G.
Input parameters
[air_temp] distribution: idw
CoreConfig Recipes
[_distribution_idw] slope: = -1
The would be seen by smrf the same as [air_temp] distribution: idw slope: -1
The trick here will be managing the options associate with an option that is set in the recipe and can be set by the module.
Questions to answer: