#59 Davenport (10-1)

avg: 1659.67  •  sd: 75.07  •  top 16/20: 0%

Click on a column to sort  • 
# Opponent Result Game Rating Status Date Event
134 Catholic** Win 9-1 1658.71 Ignored Feb 15th 2025 Commonwealth Cup Weekend 1
48 Liberty Loss 3-10 1219.58 Feb 15th 2025 Commonwealth Cup Weekend 1
92 Richmond Win 10-5 1930 Feb 15th 2025 Commonwealth Cup Weekend 1
79 Tennessee Win 9-6 1897.49 Feb 16th 2025 Commonwealth Cup Weekend 1
107 Virginia Tech Win 6-2 1853.9 Feb 16th 2025 Commonwealth Cup Weekend 1
132 Grand Valley Win 10-2 1664.88 Mar 15th Davenport Spring Skirmish
87 Michigan State Win 6-3 1954.87 Mar 15th Davenport Spring Skirmish
165 Oberlin Win 5-4 962.33 Mar 15th Davenport Spring Skirmish
96 Michigan Tech Win 8-6 1636.79 Mar 16th Davenport Spring Skirmish
132 Grand Valley Win 9-1 1664.88 Mar 16th Davenport Spring Skirmish
96 Michigan Tech Win 7-4 1832.45 Mar 16th Davenport Spring Skirmish
**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)