-
Notifications
You must be signed in to change notification settings - Fork 57
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
Use StackedSparseArray for MetadataMatch sparse equal_match
#642
Conversation
equal_match
equal_match
sparse array_type
equal_match
sparse array_type
equal_match
sparse array_type
equal_match
sparse array_type
sparse equal_match
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me @zargham-ahmad thanks!
Not completely related to this PR, but I did not look at the MetadataMatch class before, the difference between "equal_match" and "difference" was not fully clear to me at first glance. Can you maybe add a bit of extra docstring here @zargham-ahmad? And maybe we should also give a warning if a tolerance is given, but matching_type is set to "equal_match". |
if array_type not in ["numpy", "sparse"]: | ||
raise ValueError("array_type must be 'numpy' or 'sparse'.") | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good addition - this should be covered by a unit test though to make sure this specification is tracked.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
test added in 24a8ecb
done in 24a8ecb |
@zargham-ahmad Thanks for the additions. Is it ready to be merged? If so feel free to merge, or if you don't have the rights, let me know :) |
Yes, it is ready. Please merge it. |
This PR includes the following:
equal_match
matching_type when array_type issparse
closes #544