Home | Webstore
Latest News: OOTP 26 Available - FHM 12 Available - OOTP Go! Available

Out of the Park Baseball 26 Buy Now!

  

Go Back   OOTP Developments Forums > Out of the Park Baseball 25 > OOTP 25 - General Discussions

OOTP 25 - General Discussions Everything about the brand new 25th Anniversary Edition of Out of the Park Baseball - officially licensed by MLB, the MLBPA, KBO and the Baseball Hall of Fame.

Reply
 
Thread Tools
Old 01-29-2025, 10:24 AM   #21
Matt Arnold
OOTP Developer
 
Matt Arnold's Avatar
 
Join Date: Jun 2009
Location: Here and there
Posts: 15,833
Quote:
Originally Posted by turtle4499 View Post
Can you please provide clarity on exactly what is being multiplied out for dynamic runs per win and split starter/rp. Can you also provide clarity of just the forumla being used to turn park factors into run adjustments. I am not really sure why FIPs run adjustment takes into account the parks doubles factor.



I don't think anyone is actually asking you to calculate park factors based on seasonal data. I am really just asking for the park factors to be applied to the actual games correctly. Applying them broadly cannot possibly work out the correct numbers.



Simple example from my reddit post. I had a starting pitcher in coors with 50 innings at home and 100 on the road (because he was shelled at home) the adjustment is being applied like he played half his innings at home. There is no reason to assume starting pitchers do this at all. Especially in any hitter friendly park in an era where pitchers aren't just pitching 9 innings.






I am really struggling to understand what amount of data do you think is needed that isn't currently being stored right now? If we are able to look up home/away splits and vs team splits there is clearly enough data being stored to apply the park adjustments to the actual parks the games occurred in.
A lot of that data could be available in the current season, but we may not necessarily store it for past seasons. So you can't look up a player's home splits from 3 seasons back, we'd have to store a lot more information to be able to adjust those calculations to factor that in. So I mean, yeah, arguably we could give you a more granular breakdown of the current season, but it would look weird to see a guy as 1.8 WAR on October 30th, but then on November 1st when the data rolls over, we're have to recalculate to the generic formula and he might be 1.6. Even on the batters side, when you look at the splits WAR values, we don't include defense in, because we don't actually store the game by game defensive values for players. Never mind accounting for it in previous seasons.
Now, could we adjust a few of the data points more? Maybe, sure. I guess it's always a balancing act. Especially once you get into like double-splits, we won't always track exactly what split we're looking at. Even if we special-cased some of the home/road splits, it would look weird if you saw different WAR values when looking at a split one way vs another, just because it can be complex to track in. So yeah, that's one of those assumptions where we basically treat every stat as a 50/50 home/road mix when applying park factors.

In terms of a FIP specific park factor, to be honest, I didn't even know that Fangraphs split them out. That's probably something we could split out, and give a different park factor adjustment to FIP and fWAR, but use the "traditional" park factor calculation for stuff like wRC+ or rWAR.

For the actual park factors, we tend to take the modifiers you have and see what that does to a typical stats line's wOBA, more or less. i don't recall if that's how they actually do real park factors, but I know it seemed to do reasonably. On the sortable team stats page, you can see the calculated park factor there. It may break down in some extreme cases, if it does look off, feel free to report that and we can see about fixing or updating that. It's always possible that something in a calculation somewhere is off as well. Again, sometimes we do make some assumptions or adjustments (ie. in some cases maybe we apply a basic modifier on league stats to remove pitcher batting lines, but in other cases we might actually have that data and can calculate exactly)

The rest is basically us trying to follow the BB-Ref or Fangraphs calculations as close as we can, with the data and stats that we have. We always aim to be as accurate and faithful about things as we can, but certainly there can always be some room for improvement. Especially with complex calculations like these - even those who understand them have trouble following along.
Matt Arnold is offline   Reply With Quote
Old 01-29-2025, 11:22 AM   #22
turtle4499
Minors (Single A)
 
Join Date: Apr 2022
Posts: 52
Quote:
Originally Posted by Matt Arnold View Post
A lot of that data could be available in the current season, but we may not necessarily store it for past seasons. So you can't look up a player's home splits from 3 seasons back, we'd have to store a lot more information to be able to adjust those calculations to factor that in. So I mean, yeah, arguably we could give you a more granular breakdown of the current season, but it would look weird to see a guy as 1.8 WAR on October 30th, but then on November 1st when the data rolls over, we're have to recalculate to the generic formula and he might be 1.6.
Modifying a park doesn't change previous seasons anymore for WAR. What is being used to control that? Not really sure I understand why it would need to change and cannot just be stored outright. Historic data shouldn't be changing. I can understand and live with splits being off or war even being suppressed in splits.



Quote:
Originally Posted by Matt Arnold View Post
In terms of a FIP specific park factor, to be honest, I didn't even know that Fangraphs split them out. That's probably something we could split out, and give a different park factor adjustment to FIP and fWAR, but use the "traditional" park factor calculation for stuff like wRC+ or rWAR.
Also for clarity here there is specific park factors for OBP and SLG used in the calculation of OPS+.



Quote:
  1. Using these adjusted values compute what the league average player would have hit lgOBP*, lgSLG* in a park.
  2. Take OPS+ = 100 * (OBP/lgOBP* + SLG/lgSLG* - 1)
turtle4499 is offline   Reply With Quote
Old 01-29-2025, 11:41 AM   #23
Matt Arnold
OOTP Developer
 
Matt Arnold's Avatar
 
Join Date: Jun 2009
Location: Here and there
Posts: 15,833
Quote:
Originally Posted by turtle4499 View Post
Modifying a park doesn't change previous seasons anymore for WAR. What is being used to control that? Not really sure I understand why it would need to change and cannot just be stored outright. Historic data shouldn't be changing. I can understand and live with splits being off or war even being suppressed in splits.




Also for clarity here there is specific park factors for OBP and SLG used in the calculation of OPS+.
The way we handle it, WAR is a calculated value. So we don't actually store a WAR value, we always calculate it on the fly based on the stats that are given. Even if a player sits out for a day, their WAR can change, just because the current season league stats might shift the average a little.

We do store past season park factors to be able to calculate. That's so we can actually calculate past WAR based on the actual park that season, if you change a team from Colorado to SD this year it shouldn't impact previous calculations.
Matt Arnold is offline   Reply With Quote
Reply

Bookmarks


Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT -4. The time now is 05:54 PM.

 

Major League and Minor League Baseball trademarks and copyrights are used with permission of Major League Baseball. Visit MLB.com and MiLB.com.

Officially Licensed Product – MLB Players, Inc.

Out of the Park Baseball is a registered trademark of Out of the Park Developments GmbH & Co. KG

Google Play is a trademark of Google Inc.

Apple, iPhone, iPod touch and iPad are trademarks of Apple Inc., registered in the U.S. and other countries.

COPYRIGHT © 2023 OUT OF THE PARK DEVELOPMENTS. ALL RIGHTS RESERVED.

 

Powered by vBulletin® Version 3.8.10
Copyright ©2000 - 2025, vBulletin Solutions, Inc.
Copyright © 2024 Out of the Park Developments