alteryx / alteryx/featuretools

DFS does not build some features when there are multiple paths to an entity

オープン
#652 コメント 1 件 リアクション 0 件 担当者 0 名 GitHub で見る
needs design
主要言語
Python
スター
7.7k
フォーク
915
PR マージ指標
30日以内にマージされた PR はありません

説明

DFS currently builds features for each entity only once. This is problematic because depending on which path is taken to an entity different features may be built. For example, the following test currently fails:
```py
def test_makes_direct_of_agg_on_all_paths(diamond_es):
dfs_obj = DeepFeatureSynthesis(target_entity_id='transactions',
entityset=diamond_es,
max_depth=3,
agg_primitives=[Count],
trans_primitives=[])

features = dfs_obj.build_features()
# These two pass
assert feature_with_name(features, 'stores.regions.COUNT(stores)')
assert feature_with_name(features, 'stores.regions.COUNT(customers)')
# These two fail
assert feature_with_name(features, 'customers.regions.COUNT(stores)')
assert feature_with_name(features, 'customers.regions.COUNT(customers)')
```
This is because the `customers` features are built before the aggregations on `regions`. The execution looks something like this
```
_run_dfs(transactions)
_run_dfs(stores)
build_agg_features
_run_dfs(regions)
_run_dfs(customers)
build_agg_features
build_direct_features
build_agg_features
build_direct_features
build_direct_features
```
When there are not multiple paths this is fine because you don't want features like `regions.MEAN(customers.regions.COUNT(stores))`. But when there are multiple paths the features on `customers` may be used by entities other than `regions`.

コントリビューションガイド

コントリビューションガイドを開く

評価

この issue はまだ評価されていません。

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。