Allow set_velocities to accept ids as scalar or 0d array#41
Open
pooleya19 wants to merge 1 commit into
Open
Conversation
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Fixes #39.
Calling
set_velocities(ids, velocities)whenidsis a scalar or a 0-dimensional NDArray raises aValueError. This is caused by numpy failing to broadcastvelocitieswith shape(2,1)toself._velocities[:,ids]with shape(2,).Making
idsbe at least 1d allowsself._velocities[:,ids]to maintain a shape of(2,1), and should have no effect to function calls whenidsis 1d or 2d.