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
Handle no child data when calculating aggregation features with multiple arguments #264
Conversation
Codecov Report
@@ Coverage Diff @@
## master #264 +/- ##
==========================================
+ Coverage 94.14% 94.15% +<.01%
==========================================
Files 71 71
Lines 7638 7649 +11
==========================================
+ Hits 7191 7202 +11
Misses 447 447
Continue to review full report at Codecov.
|
|
||
# cutoff time after all rows, but where clause filters all rows | ||
ft.calculate_feature_matrix(entityset=es, features=[count], cutoff_time=pd.Timestamp("1/4/2018")) | ||
ft.calculate_feature_matrix(entityset=es, features=[count, count_where, trend], cutoff_time=pd.Timestamp("1/4/2018")) |
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.
Could we add assertions here to confirm we get expected feature values from these matrices?
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.
done
This pull requests updates how we handle calculating aggregation features when there is no child data. We fixed this for aggregations with where features in #258, but this fixes it for when there are multiple arguments to the agg feature.
This PR fixes the second issue reported in #252