You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, the user can put any kind of parameters in the instruction file even if they are not used. For example, if “Lifespan” is not a mortality factor, one can still set hft.life_history.lifespan.
I think the user should get a notification if there are parameters in the instruction file that are not used.
This can be important in case the user assumes that a parameter has an effect, but actually the underlying module is inadvertently disabled.
Implementing this could be easily done in Hft::is_valid() and Parameters::is_valid(): Just write into the message stream, but still return true (“is valid”).
The text was updated successfully, but these errors were encountered:
Currently, the user can put any kind of parameters in the instruction file even if they are not used. For example, if “Lifespan” is not a mortality factor, one can still set
hft.life_history.lifespan
.I think the user should get a notification if there are parameters in the instruction file that are not used.
This can be important in case the user assumes that a parameter has an effect, but actually the underlying module is inadvertently disabled.
Implementing this could be easily done in
Hft::is_valid()
andParameters::is_valid()
: Just write into the message stream, but still returntrue
(“is valid”).The text was updated successfully, but these errors were encountered: