FredJacket
Helluva Engineer
- Messages
- 6,292
- Location
- Fredericksburg, Virginia
Decided I'd like a thread dedicated to this. Hope that is ok with some of you who've chimed in on our approach to sacrificing runners.
These tables (thank you @Lagrangejacket) provide very good data. I do sort of believe CDH (and other coaches too) seems to overuse the SAC bunt...ultimately costing us runs in the long term. I won't rehash all the back and forth on other threads. The consensus seems to be (particularly this year)... Tech should NEVER use the top of the order (guys with high OBPs) to sac bunt runners over. Some do concede the only exception would be the late inning situation (i.e. 9th inning) where 1 run is needed to tie or get the lead.
The data in the tables does include all plays in all games (it says roughly 93% of D1 games). If we are using the data to do analysis on the value of a sac bunt... I'd like to see it with the data for lopsided games removed. Set some score differential limit at like 2 or 3 runs. Nearly all the time in lopsided games... there will be no decision to sac bunt. So.. you would make a more apples to apples comparison. I'd bet this would deflate the tables some too.. making it appear more reasonable to attempt sac bunts in tight games at any point during the game. However, that data would likely still make the same case, just less dramatically... you should not bunt early and often.
Anecdotally, as I fan who considers "small ball" exciting... I see value in a well-executed sac bunt or squeeze play to fire up a team or crowd and/or establish some momentum early by scoring first. I cannot say those things necessarily translate to a "good coaching decision" if you too often fail to execute (opposite effect) or you need 14 runs to win a baseball game.
Anyway... I value the input of others on this and thoroughly enjoy the discussion. Baseball is a beautiful thing... always some small nuance to learn; and if you're alert to it, you'll nearly always see something you've never seen before at a baseball game.
These tables (thank you @Lagrangejacket) provide very good data. I do sort of believe CDH (and other coaches too) seems to overuse the SAC bunt...ultimately costing us runs in the long term. I won't rehash all the back and forth on other threads. The consensus seems to be (particularly this year)... Tech should NEVER use the top of the order (guys with high OBPs) to sac bunt runners over. Some do concede the only exception would be the late inning situation (i.e. 9th inning) where 1 run is needed to tie or get the lead.
The data in the tables does include all plays in all games (it says roughly 93% of D1 games). If we are using the data to do analysis on the value of a sac bunt... I'd like to see it with the data for lopsided games removed. Set some score differential limit at like 2 or 3 runs. Nearly all the time in lopsided games... there will be no decision to sac bunt. So.. you would make a more apples to apples comparison. I'd bet this would deflate the tables some too.. making it appear more reasonable to attempt sac bunts in tight games at any point during the game. However, that data would likely still make the same case, just less dramatically... you should not bunt early and often.
Anecdotally, as I fan who considers "small ball" exciting... I see value in a well-executed sac bunt or squeeze play to fire up a team or crowd and/or establish some momentum early by scoring first. I cannot say those things necessarily translate to a "good coaching decision" if you too often fail to execute (opposite effect) or you need 14 runs to win a baseball game.
Anyway... I value the input of others on this and thoroughly enjoy the discussion. Baseball is a beautiful thing... always some small nuance to learn; and if you're alert to it, you'll nearly always see something you've never seen before at a baseball game.