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
Remove max_hlevel from DFS #608
Conversation
This was not exposed in the dfs method so it always used the default value of 2, it was undocumented, and it was unclear if it provided any value.
This is no longer used.
Codecov Report
@@ Coverage Diff @@
## multipath-dfs-no-cycles #608 +/- ##
===========================================================
+ Coverage 96.35% 96.38% +0.03%
===========================================================
Files 119 119
Lines 9713 9605 -108
===========================================================
- Hits 9359 9258 -101
+ Misses 354 347 -7
Continue to review full report at Codecov.
|
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.
onces this is good. let's just merge it into multipath-dfs-no-cycles branch
if ((max_depth is None or self._get_depth(f) <= max_depth) and | ||
(self.max_hlevel is None or | ||
self._max_hlevel(f) <= self.max_hlevel)): | ||
if max_depth is None or self._get_depth(f) <= max_depth: |
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.
I think we can replace self._get_depth(f)
with f.get_depth(stop_at=self.seed_features)
and remove self._get_depth
For entitysets with multiple paths between two entities DFS will now create features through all paths. Entitysets with cycles in the directed graph are not supported. - Use feature.unique_name instead of hash in dicts - Change EntitySet.get_backward_entities and get_forward_entities to yield paths. - Add RelationshipPath which represents a directed path through relationships. - Add RelationshipPath.entities - Warn if dfs produces a feature multiple times - Remove max_hlevel from DFS (#608). - Remove EntitySet.find_path
For entitysets with multiple paths between two entities DFS will now create features through all paths. Entitysets with cycles in the directed graph are not supported. - Use feature.unique_name instead of hash in dicts - Change EntitySet.get_backward_entities and get_forward_entities to yield paths. - Add RelationshipPath which represents a directed path through relationships. - Add RelationshipPath.entities - Warn if dfs produces a feature multiple times - Remove max_hlevel from DFS (alteryx#608). - Remove EntitySet.find_path
This was not exposed in the
dfs
method so it always used the defaultvalue of 2, it was undocumented, and it was unclear if it provided any
value.
Also remove
EntitySet.find_path
as it is no longer used.The base branch should be changed to
master
after #600 is merged.