Fixed an interpolation issue where scipy now requires unique x-axis values. #842
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Kenneth-T-Moore
approved these changes
Oct 23, 2022
… > 1.9.3 until a solution is made.
…ntil we find a different solution.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
Scipy 1.9.3 introduced an exception raised during
load_casebecause time values used to interpolate states and controls contained duplicate values at segment bounds.This fix runs time values from the solution being interpolated through
np.uniqueto extract the indices of the unique time values, and then applies those to states and controls when performing the interpolation.Related Issues
load_case#841Backwards incompatibilities
None
New Dependencies
None