Warning for user when non-constant functions are modified by 'params'

[JamesPHoughton]

Say the user wants to set the initial conditions for the simulation, but they accidentally use the 'params' keyword. This will overwrite the stock calling functions with the values they meant to use as initial conditions, and they will get very unusual behavior.

We could check for this, and give a warning.

[JamesPHoughton]

And by 'hypothetical user' I really mean: I just did this, and couldn't figure out what was happening.

[enekomartinmartinez]

Hi @JamesPHoughton
I am thinking about including some small improvements in 3.8.0 to close some old issues. I could probably include different warnings in params let me know if they suit you (I will probably include also information about the var names and an option to don't show the warning messages):

• When setting a Data o Lookup object to a constant "Warning: Replacing interpolation data with constant values."
• When setting a cache constant value with a type different than a constant (i.e. a constant that is computed with other constant values): "Warning: Replacing a constant value that is not primitive by another constant value."
• When replacing a constant with a pandas.Series "Warning: replacing a constant value with a time-dependent value. The value will be interpolated over time."
• When replacing a time-dependent variable with a constant or a pandas.Series "Warning: replacing the value of a variable by a constant/time dependent value"
• When replacing a stateful object with a constant or a pandas.Series "Warning: replacing the value of Stateful variable by a constant/time-dependent value. To set initial conditions use xxxxxx"