Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

bug fix in velocity_marked_npairs functions #859

Merged
merged 4 commits into from
Dec 12, 2017

Conversation

duncandc
Copy link
Contributor

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 updating weight_func_id in a couple other locations with the pairwise_velocities module. These changes have been noted CHANGES.rst

Andrew Hearin and others added 4 commits November 28, 2017 09:22
…_xy_z functions. Up until now, these functions were not executed by any unit-test. The newly added doctest revealed a bug in both functions related to weight_func_id=0 not being recognized.

Additionally, the docstrings of both functions mention that further information about weight_func_id can be found in the Notes section, but there is no Notes section.

@duncandc - can you address this to resolve Issue astropy#836?
@aphearin aphearin added this to the v0.6 milestone Dec 12, 2017
@aphearin aphearin changed the title big fix in velocity_marked_npairs functions bug fix in velocity_marked_npairs functions Dec 12, 2017
@aphearin aphearin merged commit c7fc4a5 into astropy:master Dec 12, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants