Skip to content

Commit a812735

Browse files
committed
added batting order post
1 parent ee4dc25 commit a812735

File tree

1 file changed

+6
-4
lines changed

1 file changed

+6
-4
lines changed

_posts/2025-04-01-batting-order.md

Lines changed: 6 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -21,7 +21,7 @@ I used a _Monte Carlo_ approach to generate distributions of runs scored given d
2121
This is a fancy way of saying that I simulated a lot of baseball games with different lineups, and used the outcomes of those simluations as distributions of expected run production.
2222
By comparing these distributions across different batting orders, I could evaluate which lineups are more effective.
2323

24-
To implement the simulation, I built a simple model.
24+
To implement the simulation, I modeled the game in the simplest way I could.
2525
As you'll see, I think it does a decent job of capturing reality.
2626
I defined hitters as a set of static per-plate-appearance probabilities.
2727
The plate appearance outcomes I modeled are walk, single, double, triple, and home run.
@@ -50,16 +50,17 @@ The pitcher is of course an important factor, but my model essentially always as
5050
Similarly, factors like the defense, runners, lefty/righty splits, extra innings, and emotion, are not modeled.
5151

5252
With that caveat, here is the simulated distribution of the runs scored in each game by the 2024 Yankees.
53+
I'll focus on the Ya
5354

5455
![](/assets/img/2025/run_dist_comp.png){: .center}
5556

56-
I used 2024 data from Baseball Reference to define the plate appearance outcome probabilities for a linup of Gleyber Torres, Juan Soto, Aaron Judge, Austin Wells, Giancarlo Stanton, Jazz Chisolm Jr., Anthony Rizzo, Anthony Volpe, and Alex Verdugo.
57+
I used 2024 data from Baseball Reference to define the plate appearance outcome probabilities for a lineup of Gleyber Torres, Juan Soto, Aaron Judge, Austin Wells, Giancarlo Stanton, Jazz Chisolm Jr., Anthony Rizzo, Anthony Volpe, and Alex Verdugo.
5758

5859
Alongside the simulation results, I plotted the actual per-game run distribution from the same year.
5960
The model lines well with the real data.
6061

6162
Before messing with batting orders, a sanity check.
62-
What happens if we remove Aaron Judge from this lineup.
63+
What happens if we remove Aaron Judge from this lineup?
6364
He's the best hitter here by a decent margin, so it should have a big effect.
6465
Here's what the run distribution looks like if you replace Judge with a second copy of leadoff hitter Gleyber Torres.
6566

@@ -68,12 +69,13 @@ Here's what the run distribution looks like if you replace Judge with a second c
6869
Pretty big effect.
6970
Replacing Judge with another Gleyber brings the 2024 Yankees from 5.4 to 4.7 runs per game.
7071
Incidentally, if you multiply this per-game difference by the number of games Judge played, subtract the total difference from the Yankees' 2024 total runs scored, and plug into a [Pythagorean win-loss](https://en.wikipedia.org/wiki/Pythagorean_expectation) formula, you get a value of about 10 Wins Above Gleyber or 11.7 Wins Above Replacement.
72+
This is pretty close to his 2024 fWAR of 11.2.
7173
Nice to see different methods agree.
7274

7375
# The results
7476

7577
Now let's get to batting order.
76-
Here's what happens if we do something pretty extreme and slide Judge from 3rd in the linup, where he typically hit in 2024, all the way down to 9th.
78+
Here's what happens if we do something pretty extreme and slide Judge from 3rd in the lineup, where he typically hit in 2024, all the way down to 9th.
7779

7880
![](/assets/img/2025/run_dist_judge_9.png){: .center}
7981

0 commit comments

Comments
 (0)