You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Exclusive feature bundling has a notion of "joining features that rarely take on non-zero values simultaneously". What does "nonzero" mean in the context of joining 2 continuous variables? I'd imagine continuous variables are actually nonzero most of the time in most dataset. Is "zero" set to some mean value or would continuous features just not be bundled?
How do we expect EFB to behave when the features are dense and there are few exclusive sets? Will bundling still occur?
The algorithm seems to allow a small fraction of conflicts in feature bundling, how are conflicts handled? Are they set to 0 by default or the value of one feature is ignored or something else?
The text was updated successfully, but these errors were encountered:
EFB is used in the sparse data, which contains many zero/nan values. And in our implementation, we use most_freq_bin (the bucketed int value with most data) as "zero" to perform bundling. Therefore, EFB may work for dense data with many repeated values.
The EFB is always used. It may cannot find the bundle for dense data.
The feature value in the conflicting row will be treated is zero/most_freq_bin.
Exclusive feature bundling has a notion of "joining features that rarely take on non-zero values simultaneously". What does "nonzero" mean in the context of joining 2 continuous variables? I'd imagine continuous variables are actually nonzero most of the time in most dataset. Is "zero" set to some mean value or would continuous features just not be bundled?
How do we expect EFB to behave when the features are dense and there are few exclusive sets? Will bundling still occur?
The algorithm seems to allow a small fraction of conflicts in feature bundling, how are conflicts handled? Are they set to 0 by default or the value of one feature is ignored or something else?
The text was updated successfully, but these errors were encountered: