New config handling functions #91
Draft
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Started making some headway with changing how the configuration in HBT-HERONS is handled. The idea is to streamline as much as possible the declaration and initialisation of parameter values, including those read from the parameter file. My motivation is based on the feeling that there is a lot of repeated keywords, e.g.
Parameter_tParameter_t::Parameter_tTrySetParinParameter_t::SetParameterValue, with the precise definition ofTrySetPardepending on the dtype of the new variable.Parameter_t::BroadCast.I envision this PR as a way to streamline all of the above, such that any new variable is added to a single file ONCE, and everything else is automatically handled.
For the time being, I have implemented a solution for steps 1 and 2. We can now define new parameters in
parameters.hin the form: