Introduction to the blog

Hi everyone,

This blog is a place for my thoughts and writings on sabermetrics and baseball analysis. I'll mainly be exploring predictions from my machine learning based pitch evaluation model, PitchingBot, but there will be a sprinkling of analysis on other baseball topics which happen to pique my interest.

I intend to occasionally make apps to go along with these blog posts, allowing people to explore the data for themselves.

Hopefully this sounds interesting to those reading. If you have any feedback or questions that you think could be answered using PitchingBot then put them in the comments or find me on twitter here.

Thanks!
Cameron

Comments

Custom Pitch Stuff Grades

I've made an app allowing anyone to see what my models think of any hypothetical pitch.

Don't Let Opposing Hitters See the Same Reliever Too Many Times, Especially in the Postseason.

Here I show how relief pitchers get significantly worse results when hitters see them on multiple occasions in a short time period.

PitchingBot: Now With Seam-Shifted Wake

Introduction This is the final update that I'll be making to my pitch quality model. The main update is the inclusion of spin/movement axis differences which was a clear weakness of my previous work. In addition, I've reworked the format of the underlying models. These approach changes have limited me to data from 2020 onwards, but greater accuracy has been achieved in almost every model prediction. This model update will only be used on my main website , other apps will continue to use the old version. Pitching grades from before 2020 will be grandfathered in using the old model. For more information on older versions of the model, see these blog posts: [1] , [2] Spin Axis and Efficiency On a pitch-by-pitch basis, the observed spin and movement axis from Statcast data can be compared to produce the axis difference metric, commonly attributed to Seam-Shifted Wake (SSW). Increased SSW is generally correlated with improved performance as seen in the graph below, which used the o...

Ahead in the count

Search This Blog