-
Notifications
You must be signed in to change notification settings - Fork 16
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
Fix issues with auto_entityset #21
base: main
Are you sure you want to change the base?
Conversation
Codecov Report
@@ Coverage Diff @@
## master #21 +/- ##
=========================================
Coverage ? 94.74%
=========================================
Files ? 10
Lines ? 970
Branches ? 0
=========================================
Hits ? 919
Misses ? 51
Partials ? 0
Continue to review full report at Codecov.
|
autonormalize/dfd.py
Outdated
masks.add_mask(attr, row[attr], m) | ||
if mask is None: | ||
mask = m | ||
else: | ||
mask = mask & m | ||
options = df[mask] | ||
_, unique_counts = numpy.unique(options[rhs].to_numpy(), return_counts=True) | ||
|
||
# _, unique_counts = np.unique(options[rhs].to_numpy(), return_counts=True) |
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.
should this line be removed?
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.
Yep, removed this and another temporary test that I added trying to replicate the problem that was present in #19.
This PR fixes two issues that were identified when trying to replicate the error described in Issue #19
The first change addresses a problem that resulted by trying to do an
==
comparison betweennan
values.The second change fixes an issue that can happen causing a column that is needed in other relationships to be dropped from an entity when
make_indexes
is executed.Two additional tests were added to cover these scenarios.
Also, note, while these issues were discovered when testing for Issue #19, that specific error was not reproduced and it is unknown whether these changes will resolve that issue or not.