Remove unused levels from categorical unique_id
#473
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.
Summary
Check if
unique_id
is categorical and drop unused levels.Why?
If
unique_id
is categorical, and some levels were removed, thenvalue_counts()
in_grouped_array_from_df()
still returns these levels, but with counts of 0._grouped_array_from_df()
, however, does not expect that some counts could be zero, therefore, it makes sense to drop unused levels from a categorical index.This situation arises, for example, when we
unique_id
, e.g., to save memory when a dataset is large.unique_id
, e.g., for faster development, because the data set is large.Feel free to use your judgment on whether this edge case is common enough to justify an additional validation.
Test
Example code, which fails before the fix:
Throws the following error, which does not help identifying the cause of the problem: