#10 Space Heater (6-8)

avg: 1897.63  •  sd: 65.53  •  top 16/20: 93.6%

Click on a column to sort  • 
# Opponent Result Game Rating Status Date Event
25 Alloy Win 12-7 2230.27 Jun 9th AMP Invite 2019
2 AMP Loss 8-10 1844.7 Jun 9th AMP Invite 2019
37 Jughandle Loss 10-11 1437.97 Jun 9th AMP Invite 2019
23 Rally Win 13-8 2207.5 Jun 9th AMP Invite 2019
6 BFG Loss 12-15 1666.62 Aug 2nd 2019 US Open Club Championship
12 Blackbird Win 15-11 2260.89 Aug 2nd 2019 US Open Club Championship
1 Drag'n Thrust Loss 11-15 1815.2 Aug 3rd 2019 US Open Club Championship
2 AMP Loss 10-13 1779.23 Aug 4th 2019 US Open Club Championship
14 Love Tractor Win 12-10 2064.42 Aug 31st TCT Pro Championships 2019
1 Drag'n Thrust Loss 9-13 1777.8 Aug 31st TCT Pro Championships 2019
31 XIST Loss 13-14 1500.92 Aug 31st TCT Pro Championships 2019
37 Jughandle Win 15-7 2162.97 Sep 1st TCT Pro Championships 2019
4 Slow White Loss 10-14 1616.69 Sep 1st TCT Pro Championships 2019
13 Toro Win 14-10 2249.18 Sep 1st TCT Pro Championships 2019
**Blowout Eligible

FAQ

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
  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
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)