fix #551: up
and gain_scale_factor
are set by StressModel
#573
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.
Short Description
As discussed:
up
orgain_scale_factor
in response function init, added trap to raise TypeError if they are passed to init.rfunc.update_rfunc_settings()
rfunc.update_rfunc_settings()
Once again a question in relation to deprecation warnings. I can modify the trap to generate a warning instead of raising an error if up is passed to the response function, do we want that, or since we never intended this behavior is it okay to just make the change? I vote for the latter option.
Commits
Checklist before PR can be merged: