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
If you call vw with --cb_explore_adf and an example that does not have a label then predict will be called twice, this seems sub-optimal and un-intuitive for reductions above cb_explore_adf and can cause bugs
e.g. when called with LAS, learn paths would not get full predictions if there is a label missing and -p <file> is specified (see #4273)
If a label is missing during learn what should the reduction contract be? Should learn be called anyway? Should prediction be called? Should we warn? Should we throw?
Describe the bug
If you call vw with
--cb_explore_adf
and an example that does not have a label then predict will be called twice, this seems sub-optimal and un-intuitive for reductions above cb_explore_adf and can cause bugse.g. when called with LAS, learn paths would not get full predictions if there is a label missing and
-p <file>
is specified (see #4273)If a label is missing during learn what should the reduction contract be? Should learn be called anyway? Should prediction be called? Should we warn? Should we throw?
How to reproduce
input modified from
cb_test.ldf
file:run with
--cb_explore_adf
and printing/breakpoint to see that predict gets called twice fromcb_explore_adf_common.h
code line
Version
9.5.0
OS
Linux
Language
CLI
Additional context
No response
The text was updated successfully, but these errors were encountered: