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
Well the 55% / 400 game gating is our own imposed secondary test, not a true SPRT result. We could remove the gating checks and add all of this into the SPRT test perhaps but I think it's safer to keep the SPRT function clean and apply the gating over top of it? null result isn't "wrong". we just ignore it if our other gating decision is met.
What we do want eventually though is a stick pass on matches table to get people to stop complaining about it. :) Perhaps just a simple global Map set when we make the Networks table, setting very network with a selfplay game to true, then when making the matches table if the network1 in the Map is true, set SPRT to PASS for that match table row. (This will only be true for networks with selfplay games, meaning they did PASS at some point for sure.)
For 400 games with 55% gating, I would expect the SPRT result to be
Here are test cases found to be faulty
Script to generate test cases
@roy7
Have I misinterpret how SPRT should work? or maybe we need to hard code the boundaries to fix this.
The text was updated successfully, but these errors were encountered: