1. But what is your formula? You’re still not getting the numbers I would expect based on the formulas I’ve seen. Is this something you’ve created yourself, or with the0nlyis? It’s important, because you’re coming up with a much wider difference than I would expect based on the accepted formulas I’ve seen.
2. It’s interesting (and telling) that you dive into the stat analysis behind the curtain of the part of the algorithm you’ve clearly worked very hard on, but in response to an issue lying outside the scope of that algorithm, you ignore statistical discrepancy. If you’re going to do scientific stat analytics, it’s very important that you go in without the sort of biases you’re showing here (“12 BH in a big is roughly meaningless). So *points* matter to you, but *possessions* don’t? Brooks *should* have rebounded as well, and *shouldn’t have* turned the ball over more, because you don’t know how to account for them, so they’re just not part of efficiency I guess. Hard pass. :l
3. This is where your GI/GO takes you completely off the rails. Brooks will score more points, for sure, given a higher distribution. That’s not in doubt, although the claim that 2.5x is optimal is a severe stretch. But again, it’s not about two players in a vacuum, it’s about whole team. More on that below.
4. See #2 I guess. Just a bad take.
5. See #1. I question the validity of that 3% difference in the first place.
*From basketball-reference: “Effective Field Goal Percentage; the formula is (
FG + 0.5 *
3P) /
FGA. This statistic adjusts for the fact that a 3-point field goal is worth one more point than a 2-point field goal. For example, suppose Player A goes 4 for 10 with 2 threes, while Player B goes 5 for 10 with 0 threes. Each player would have 10 points from field goals, and thus would have the same effective field goal percentage (50%).”
This is clearly not what you’re doing, because if it was, the difference you’d get would just be the difference in FG% (neither player shoots 3s). I understand you are trying to add FT into equation, but that tells me you’re trying to make this tell us something entirely different from what efg% is designed to do. So again, let’s see what that formula is, show your work.
6. Respectfully, I am pretty sure I am thinking just fine. No team needs 5 starters scoring 15 points to be optimal. To say Wisconsin was ever “desperate” for scoring was an overstatement, but certainly by tournament time, with the freshmen on the bench, they were scoring plenty of points. In that situation, having some scorers on the bench with them is actually preferable. In summary, players bring more to the +/- than scoring.
6 part 2. Stamina doesn’t make the player better. It’s not a modifier (like amphetamine) that spikes performance. It just tells us how long the player will be able to sustain the level of established goodness. It’s feeling like you’re trying to treat it like another athleticism, and it’s not that. Deficiencies can get amplified in some settings when teams try to do things without having enough of it, but once you have enough in the right spots, more isn’t better. So to use Wisconsin, if they were set on running uptempo, having Brooks start might be a slightly better option; but only for a couple minutes per game. Pacquet would have no problems getting 20-22 minutes per game, even uptempo, if settings were right (I suspect Rowle may have been using minutes, or had him set to getting tired, not sure though). IOW, 71-75 stamina does not prohibit getting 20+ minutes of elite rebounding and defense, if that’s what a coach decides they want from their post player.
Look, I’m not going to tell you to stop using your algorithm. You’ve spent a lot of time on it, and if it works for you, use it. Lots of ways to build a team.
But calling Pacquet “unstartable” on an elite team is just incorrect. You are *vastly* overstating your case, and overestimating the scope of your tool. Elite teams can win with pitching and defense.
ETA—thanks for clarifying on the ts%
1/21/2022 10:10 AM (edited)