#76 Cal Poly-SLO-B (3-7)

avg: 518.91  •  sd: 69.09  •  top 16/20: 0%

Click on a column to sort  • 
# Opponent Result Game Rating Status Date Event
46 British Columbia-B Loss 1-13 446.09 Feb 1st Stanford Open Womens
42 Oregon State Loss 7-13 512.19 Feb 1st Stanford Open Womens
29 Carleton College-Eclipse** Loss 4-13 672.76 Ignored Feb 1st Stanford Open Womens
88 Nevada-Reno Win 11-7 758.98 Feb 2nd Stanford Open Womens
45 California-Irvine Loss 2-13 448.33 Feb 15th Santa Clara University WLT Tournament
75 Occidental Loss 7-8 412.05 Feb 15th Santa Clara University WLT Tournament
89 California-Davis-B Win 8-7 407.77 Feb 15th Santa Clara University WLT Tournament
82 California-B Win 8-3 1069.87 Feb 16th Santa Clara University WLT Tournament
45 California-Irvine Loss 2-13 448.33 Feb 16th Santa Clara University WLT Tournament
75 Occidental Loss 9-11 287.84 Feb 16th Santa Clara University WLT Tournament
**Blowout Eligible

FAQ

What is the uncertainty of the mean?
The uncertainty of the mean is equal to the standard deviation of the set of game ratings, divided by the square root of the number of games. We treated a team’s ranking as a normally distributed random variable, with the USAU ranking as the mean and the uncertainty of the ranking as the standard deviation
What's the algorithm again?
  1. Calculate uncertainy for USAU ranking averge
  2. Model ranking as a normal distribution around USAU averge with standard deviation equal to uncertainty
  3. Simulate seasons by drawing a rank for each team from their distribution. Note the teams in the top 16 (club) or top 20 (college)
  4. Sum the fractions for each region for how often each of it's teams appeared in the top 16 (club) or top 20 (college)
  5. Subtract one from each fraction for "autobids"
  6. Award remainings bids to the regions with the highest remaining fraction, subtracting one from the fraction each time a bid is awarded
Is there a longer explanation of all this?
There is an article on Ulitworld written by Scott Dunham and I that gives a little more context (though it probably was the thing that linked you here)