bug fix in velocity_marked_npairs functions #859
Merged
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.
This pull request addresses issue #836.
There is no weight_func_id=0 for these velocity weighted functions. In addition, each function was being called incorrectly within the doc string example section.
I have corrected these bugs and modified the
weight_func_id
numbers of each weighting function to be more reasonable, e.g. 1,2,3,4. This change required updatingweight_func_id
in a couple other locations with thepairwise_velocities module
. These changes have been noted CHANGES.rst