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
Update last_datapoint_time even if we don't update bounds
When we see a failure or success and it doesn't result in a bounds
update, we previously were'nt updating the `last_datapoint_time`
field as we were updating it in the bounds-update logic.
This is wrong for the purpose of the `probing_diversity_penalty`
because the whole point is to avoid repeatedly probing the same
channel, but because of this we'll probe the same channel again and
again as long as we don't learn any new information from the probes
which causes a bounds update.
0 commit comments