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
{{ message }}
Repository navigation
Cannot combine OneVersusAll with FieldAwareFactorizationMachine #590
Before changing OVA to take IPredictionTransformer instead of ISingleFeaturePredictionTransformer, FAF needs further work to implement one of the interfaces above. @sfilipi / @Ivanidzo4ka do you know how to do it? FAF interface looks different than other BinaryClassifiers (say Sdca):
After spending some time on this, I realized that FAF is the only binary trainer with multiple feature columns (string[] featureColumns), whereas other trainers have only one feature column. This is making FAF an odd trainer that doesn't fit the existing interfaces. We'd need to adjust all the trainer interfaces to accommodate this case. This won't be a trivial fix.
Given that @rauhs thinks this is not an important scenario, I'm putting this item in the backlog to be visited later.
Activity
sfilipi commentedon Jul 30, 2018
Thanks for reporting, @rauhs.
We should update The FieldAwareFactorizationMachineBinaryClassifier to implement the IValueMapper interface.
rauhs commentedon Oct 9, 2018
Any update on this?
Zruty0 commentedon Nov 5, 2018
No. This is still an outstanding issue. How important is it for you @rauhs ?
rauhs commentedon Nov 8, 2018
I guess not all that important after all. I just wanted to try it out.
shmoradims commentedon Nov 29, 2018
FieldAwareFactorizationMachine doesn't implement the correct interface. Neither of the casts below work, which means OVA cannot use FAF.
Before changing OVA to take IPredictionTransformer instead of ISingleFeaturePredictionTransformer, FAF needs further work to implement one of the interfaces above. @sfilipi / @Ivanidzo4ka do you know how to do it? FAF interface looks different than other BinaryClassifiers (say Sdca):

shmoradims commentedon Nov 30, 2018
After spending some time on this, I realized that FAF is the only binary trainer with multiple feature columns (string[] featureColumns), whereas other trainers have only one feature column. This is making FAF an odd trainer that doesn't fit the existing interfaces. We'd need to adjust all the trainer interfaces to accommodate this case. This won't be a trivial fix.
Given that @rauhs thinks this is not an important scenario, I'm putting this item in the backlog to be visited later.
justinormont commentedon Dec 4, 2018
Notable: FieldAwareFactorizationMachine is the only of our binary learners which doesn't work with OVA.
codemzs commentedon Jun 30, 2019
@wschin What is the status on this?
justinormont commentedon May 10, 2021
Unassigning @wschin as he is on other topics.