Currently an error gets thrown when the user tries to run a model where the flexmodel definition (handled through functions like add_rate(), etc.) utilizes symbols that have not been passed through the params or state vectors. It would be great if a warning for the converse case existed, i.e., when a user provides a symbol via the params or state vectors that isn't actually used in the model definition.
I can imagine a case where a user puts a parameter symbol in the params list intending to build a mechanism using it, but then forgets to add it to the model definition, and runs the model thinking that mechanism has actually been implemented. The warning I suggest would help prevent this issue.
Currently an error gets thrown when the user tries to run a model where the
flexmodeldefinition (handled through functions likeadd_rate(), etc.) utilizes symbols that have not been passed through theparamsorstatevectors. It would be great if a warning for the converse case existed, i.e., when a user provides a symbol via theparamsorstatevectors that isn't actually used in the model definition.I can imagine a case where a user puts a parameter symbol in the
paramslist intending to build a mechanism using it, but then forgets to add it to the model definition, and runs the model thinking that mechanism has actually been implemented. The warning I suggest would help prevent this issue.