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.
addressing stats issue #199
the issue stems mostly from the fact that
dist_freq
became a dictionary by distance-bin instead of being anndarray
(before v1.0) - then there 2 different interpretation of that dict happen:dist_bin
themselves in__init__
,add_pair
,add_pairs_fromdataframe_chunk
...bin_id
of a givendistance
(i.e.bin_id = np.searchsorted(self._dist_bins, some_distance)
) in places likefrom_file
and__gfetitem__
This is minimal fix PR - where we switch to
dist_freq
- as a dict withdist
-keys - i.e. changingfrom_file
and__getitem__
Then there is just a simple bug/typo in
flatten
, wheredist
is incorrectly defined for the very last open-ended distance interval - it is fixed here as well