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
Update primitive matching to consider all inputs #2019
Conversation
Codecov Report
@@ Coverage Diff @@
## main #2019 +/- ##
==========================================
+ Coverage 99.09% 99.10% +0.01%
==========================================
Files 143 143
Lines 16511 16586 +75
==========================================
+ Hits 16361 16438 +77
+ Misses 150 148 -2
Continue to review full report at Codecov.
|
When testing this change, two new issues were discovered that can cause feature value calculation to fail in some cases. These two issues were not caused by this change and are documented in #2020 and #2021. Previous to this PR, users would have had to manually define the features in order for these bugs to show up, but with this PR, DFS could potentially generate features that could not be calculated without error. |
Do you think we should have an alert of some kind in the release notes about the number of features created by DFS potentially changing? |
Sounds like a good idea. I'll add that. |
@rwedge Added a note in the release notes about number of features increasing in some cases with this change. |
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.
lgtm
I ran the |
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.
LGTM
Update primitive matching to consider all inputs
Closes #1828