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 all choices for loglikehood task are exactly one token, one can only run single pass to compute their logprobs. This is the case of MCF formulation (A/B/C) of tasks, which is the most used. However currently if one wants to leverage this fast evaluation, he needs to use special metric variant (metric_single_token). This is not only annoying to maintain, but many users don't know about this and don't benefit from potential speed-up.
Solution/Feature
We could detect the single token case automatically during loglikehood requests computation.
Group loglikehood requests by context
From each group select those that have exactly one token
Run the single_token requests from each group using the single-token workflow.
Benefits
Huge speed-up all mcq tasks. Easier to maintain models and metrics (no need to create and handle single token variants of metrics)
The text was updated successfully, but these errors were encountered:
Issue encountered
Solution/Feature
We could detect the single token case automatically during loglikehood requests computation.
Benefits
Huge speed-up all mcq tasks. Easier to maintain models and metrics (no need to create and handle single token variants of metrics)
The text was updated successfully, but these errors were encountered: