#181 Richmond (2-9)

avg: 174.71  •  sd: 68.99  •  top 16/20: 0%

Click on a column to sort  • 
# Opponent Result Game Rating Status Date Event
113 Cedarville Loss 6-11 251.3 Feb 18th Commonwealth Cup Weekend1 2023
144 Virginia-B Loss 2-8 -49.92 Feb 18th Commonwealth Cup Weekend1 2023
195 Wake Forest Loss 8-9 -125.1 Feb 18th Commonwealth Cup Weekend1 2023
165 George Washington Loss 6-7 205.73 Feb 19th Commonwealth Cup Weekend1 2023
213 Elon Win 8-4 252.46 Feb 19th Commonwealth Cup Weekend1 2023
166 Michigan-B Loss 6-11 -216.66 Feb 19th Commonwealth Cup Weekend1 2023
79 St. Olaf** Loss 1-13 407.47 Ignored Mar 25th Needle in a Ho Stack2
86 Boston College** Loss 3-11 355.65 Ignored Mar 25th Needle in a Ho Stack2
115 Union (Tennessee) Loss 1-13 155.42 Mar 25th Needle in a Ho Stack2
195 Wake Forest Win 6-4 365.51 Mar 25th Needle in a Ho Stack2
61 Tennessee Loss 6-13 556.5 Mar 26th Needle in a Ho Stack2
**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)