Random Ballpark Generator Download

84CubsFan · 07-10-2003, 11:54 AM

Wanting to make my fictional league really interesting, I sat down for an hour or two last night and developed a random ballpark generator for Excel. It's not just random numbers -- there is a logic to the depth flow of the outfield wall, and to the wall heights.

If you're interested, it's very simple to use. The program generates depths and wall heights for 30 random stadiums. I added darkhorse's stadium calculator to the program(*), so the program also calculates all of the stadium factors for you. All you have to do is type the numbers into OOTP, and then of course find weather data for the home city.

Hope you find it useful, and enjoy.

* darkhorse: I hope you don't mind that I did this. If you do, please post and I'll remove it right away. Your calculator is awesome, by the way.

Cooleyvol · 07-10-2003, 01:02 PM

We'd love to have this on OOTPLinks.com in the Downloads section.

There's a FAQ on the site on how to upload the zip file to our site.

Once you do that, go to the Downloads area and add a link to it.

then go post news on the front page announcing it..........the world will see it on OOTPLinks.com!!

ctorg · 07-10-2003, 01:14 PM

Cool util.

PineTar · 07-10-2003, 06:17 PM

In just kicking the tires a bit in the spreadsheet... the way you've built your factors and relationships leads to league average HR factors of less than 100 a vast majority of the time. I would think that you would want an even distribution of the random generations based around 100. Any thoughts?

Regardless, great work with this utility!!

84CubsFan · 07-10-2003, 09:12 PM

Quote:

Originally posted by PineTar
In just kicking the tires a bit in the spreadsheet... the way you've built your factors and relationships leads to league average HR factors of less than 100 a vast majority of the time. I would think that you would want an even distribution of the random generations based around 100. Any thoughts?

Yeah, the program was kind of slapped together, so it certainly has some flaws. The HR factors indeed seem to average out consistently around 95 or so, which I thought was close enough to work with, especially since the average, 2B, and 3B factors seem about right. As I have time, I'll undoubtedly tweak the numbers a bit more (the answer to the HR factor lies in the wall heights, I think). There should also be random generation of the occasional symmetrical park (boring though they may be), which will be easy enough to add in. Until then, though, if you press F9 enough (5-10 times), you can get an average distribution that is about 100 for each stat. And of course, remember that it is a 100 average for 30 parks. For 10 or 40 or any other number, the averages will be skewed anyway.

Hope you find it useful!

84CubsFan · 07-10-2003, 09:25 PM

Pine Tar,

Forgot to mention: you've probably already considered this, but if you're worried about having all 100 averages (for fictional leagues using historical players, e.g.) you can always do number tweaks yourself. That is, if the league average for LHR is 93, you can add 7 to every park's LHR factor. It's not elegant, but it will work numerically.

84CubsFan · 07-11-2003, 11:56 AM

Cooleyvol,

I don't have FTP software on my computer, but you're welcome to put the program up on OOTPlinks.

Dark Horse · 07-11-2003, 02:09 PM

CubsFan nice work on the util. i have no problem with it at all.

And the low home run ratings is something from the calculator i did. That's why i put the cheat factors in the last calculator.

It was originally made just take into consideration individual stadiums. i may take a second look at it; and see if i can come up with a way to "normalize" the ratings for a league setting.

It's not perfect but if the community keeps working with it, it will get better.

[WWBL]Batboy · 07-12-2003, 07:46 PM

This is awesome!

I'm editing my ballparks right now.

Thanks man!

seth70liz76 · 07-13-2003, 05:54 PM

I don't know if anyone else has tried this (God knows I have, but Math isn't my strong suit) has anyone factored altitude into their ballpark utilities? Coors, according to one utility I downloaded, is an extreme pitchers park-because, I assume it is working with sea level as it's base. Part of the problem, I believe, is most altitude studies are focused on the extreme of Denver, without alot of work on the many points in between Colorado and the ocean coast. Any thoughts on how to make theses "corrections" with the ballpark generators?

84CubsFan · 07-17-2003, 03:16 PM

Sorry, seth, didn't see your question. If you want to make altitude a factor, assume a standard and then set bonuses or penalties accordingly. I don't know the research about baseball performance at different altitudes, but assume that at 500 feet, the standard ratings apply. Then do + or - 1 bonuses or penalties based on 500 foot increments.

Fictional stadium at an altitude of 500ft:

(Ratings) 2B 100, 3B 109, RBA 91, RHR 93, LBA 107, LHR 105

Same stadium at 5500 ft:

(Ratings) 2B 110, 3B 119, RBA 101, RHR 103, LBA 117, LHR 115

Same stadium at -500 ft (if you want to build it there):

(Ratings) 2B 98, 3B 107, RBA 89, RHR 91, LBA 105, LHR 103

It's kind of simplistic, but it will give you the effect you're looking for, I think.

seth70liz76 · 07-19-2003, 02:42 AM

Maybe this is something that those of you who understand the math could make use of. I guess the question I have is mainly about doubles and triples. I think a 10% increase (or decrease) from sea level to 1 mile in home runs is safe to assume. And possibly 10% is safe to assume for Batting average. But a good number of these Home Runs would have been doubles or triples. Now, the utility I ran showing Coors as a pitchers park also showed it as a great park for doubles and triples (which, given the large outfield, makes sense--few outfielders can really cover that ground). I had thought about this as my adjustment:

For HR add 10% of the 2B rating and 15% of the 3B rating. Reduce the 2B and 3B by that amount.

I don't know if that has any "mathmatical" or "statistical" reality, but it just seems, on the surface, a needed adjustment.

The item listed as #7 below (I don't recall where I pulled this off of) seems to suggest, every 500 feet is abt a 1% increase in distance traveled. Knowing this, and having the math skills and Excel skills to go with it, I think it is possible to put altitude into a ballpark creator. I just don't know how.

Colorado Rockies Online- the homepage of the Colorado Rockies- provides the chart shown in Fig. 2.R.1, which shows the effect of altitude on the distance a ball travels. (Go to www.coloradorockies.com/rockies and look under Baseball 101 at the Physics of Baseball link.) The graph in the chart curves upward, suggesting that a quadratic function might be a good model.

Figure 2.R.1 Distance a batted baseball travels, as a function of altitude above sea level. Source: Colorado Rockies Online.

7. Find the quadratic function of best fit for the data that is summarized in the following table.

Stadium Altitude in Feet (x) Distance in Feet (y)
Yankee Stadium 0 400
Turner Field 1050 408
Coors Field 5280 440

8. Use your quadratic model to predict the distance a ball would travel in Wrigley
Field, where the altitude is approximately 600 feet.

9. Find the linear function of best fit for the altitude-distance data, and use it to
predict the distance the ball would travel in Wrigley Field.

10. Look at the models from items (7) and (9) to explain why the estimates were
virtually the same. Does distance traveled appear to be a quadratic function of
altitude?

84CubsFan · 07-19-2003, 01:11 PM

Yeah, it could definitely be added to the generator with ease, but I hadn't even considered it because I just needed a park to use for already created teams in a known cities. A randomly generated park with adjustments for 6700ft of altitude (though cool!) wouldn't be of much use in Chicago, unless of course they added on to the Sears Tower.

As for the decrease in 2B and 3B ratings that you suggested, you may indeed be right, but I'm not sure that the physics would work like that. Yes, a ball that would hit the wall and carem around the field allowing a triple at sea level would probably be a homer at 5280 ft. But a ball lined to the left fielder for an out at sea level would perhaps go over his head, hit the wall and carem, etc., allowing a triple at 5280 ft. It seems to me the numbers would all increase, no?

seth70liz76 · 07-19-2003, 03:34 PM

From what I've been able to gather from a discussion in the main forum abt the park ratings, is that the increase in the Ave factor would boost the 2B and 3B totals, by the simple increase in Ave rating. I take the 2B/3B/HR ratings do not, by themselves, determine the amount of 2B/3B/HR hit, but what percentage of hits are 2B/3B/HR (did that make sense?). So, it's like layers: increase Ave increases the extra base hits, just because there are more hits, and an increase in HR increases the HR even more.

But you do raise a point, line drive outs, would now carry over an outfielders head, but would that be part of the Ave or 2B/3B ratings?

Dark Horse · 07-21-2003, 02:00 PM

i think it got lost in the wash on the other threads. But there are columns in the ballpark conversion tool that you can use for altitude.

i put in columns to take into consideration how well the ball carries to LF, CF and RF. They are called carL, carC and carR. That takes into consideration wind and altitude. If the wind blows out to LF, then you put a positive number in carL. If the wind blows in from RF, then you put a negative number in carR. And if you're playing in Denver you can put a positive number in all three columns.

The number in these columns only effect average and home run ratings. But the formula can always be adjusted to fit your taste.

Dark Horse · 07-21-2003, 02:03 PM

Here's the ballpark converter. i meant to attach it to the post above but i ran into technical difficulties.

Sagitta · 12-28-2003, 03:13 AM

Sorry to dredge up an old link, but I made a rudimentary altitude spreadsheet in Works a long, loooong time back. I used the OOTP4 stadium data as a base model, and worked out a rough set of equations for determining HR effects based on the altitude of the park. I didn't work the data in for triples, doubles or hits, as IMHO those would largely remain uneffected.

I'm trying to locate my ZIP file now with the spreadsheet in it. I just remember that you can get some scary figures if you try placing a stadium in -for instance- Aspen, Colorado (altitude 8000 feet!).

The file may still be on the boards buried somewhere, I vaguely remember posting it here over a year ago.

07-10-2003, 01:14 PM	#3
ctorg Global Moderator Join Date: Nov 2002 Location: Queens, NY Posts: 9,848	Cool util. __________________ My music "When the trees blow back and forth, that's what makes the wind." - Steven Wright Fjord emena pancreas thorax fornicate marmalade morpheme proteolysis smaxa cabana offal srue vitriol grope hallelujah lentils

07-10-2003, 06:17 PM	#4
PineTar Minors (Double A) Join Date: Dec 2001 Posts: 154	In just kicking the tires a bit in the spreadsheet... the way you've built your factors and relationships leads to league average HR factors of less than 100 a vast majority of the time. I would think that you would want an even distribution of the random generations based around 100. Any thoughts? Regardless, great work with this utility!! __________________

07-11-2003, 02:09 PM	#8
Dark Horse Hall Of Famer Join Date: May 2002 Location: Texas! Posts: 2,633	CubsFan nice work on the util. i have no problem with it at all. And the low home run ratings is something from the calculator i did. That's why i put the cheat factors in the last calculator. It was originally made just take into consideration individual stadiums. i may take a second look at it; and see if i can come up with a way to "normalize" the ratings for a league setting. It's not perfect but if the community keeps working with it, it will get better. __________________ A Justafan Fan LBA Geo Bahn Rock Hounds fan of the ISLANDIAN PRO ALLIANCE

07-13-2003, 05:54 PM	#10
seth70liz76 All Star Starter Join Date: Feb 2003 Posts: 1,634	I don't know if anyone else has tried this (God knows I have, but Math isn't my strong suit) has anyone factored altitude into their ballpark utilities? Coors, according to one utility I downloaded, is an extreme pitchers park-because, I assume it is working with sea level as it's base. Part of the problem, I believe, is most altitude studies are focused on the extreme of Denver, without alot of work on the many points in between Colorado and the ocean coast. Any thoughts on how to make theses "corrections" with the ballpark generators? __________________ It was a mistake to come back.

07-19-2003, 02:42 AM	#12
seth70liz76 All Star Starter Join Date: Feb 2003 Posts: 1,634	Maybe this is something that those of you who understand the math could make use of. I guess the question I have is mainly about doubles and triples. I think a 10% increase (or decrease) from sea level to 1 mile in home runs is safe to assume. And possibly 10% is safe to assume for Batting average. But a good number of these Home Runs would have been doubles or triples. Now, the utility I ran showing Coors as a pitchers park also showed it as a great park for doubles and triples (which, given the large outfield, makes sense--few outfielders can really cover that ground). I had thought about this as my adjustment: For HR add 10% of the 2B rating and 15% of the 3B rating. Reduce the 2B and 3B by that amount. I don't know if that has any "mathmatical" or "statistical" reality, but it just seems, on the surface, a needed adjustment. The item listed as #7 below (I don't recall where I pulled this off of) seems to suggest, every 500 feet is abt a 1% increase in distance traveled. Knowing this, and having the math skills and Excel skills to go with it, I think it is possible to put altitude into a ballpark creator. I just don't know how. Colorado Rockies Online- the homepage of the Colorado Rockies- provides the chart shown in Fig. 2.R.1, which shows the effect of altitude on the distance a ball travels. (Go to www.coloradorockies.com/rockies and look under Baseball 101 at the Physics of Baseball link.) The graph in the chart curves upward, suggesting that a quadratic function might be a good model. Figure 2.R.1 Distance a batted baseball travels, as a function of altitude above sea level. Source: Colorado Rockies Online. 7. Find the quadratic function of best fit for the data that is summarized in the following table. Stadium Altitude in Feet (x) Distance in Feet (y) Yankee Stadium 0 400 Turner Field 1050 408 Coors Field 5280 440 8. Use your quadratic model to predict the distance a ball would travel in Wrigley Field, where the altitude is approximately 600 feet. 9. Find the linear function of best fit for the altitude-distance data, and use it to predict the distance the ball would travel in Wrigley Field. 10. Look at the models from items (7) and (9) to explain why the estimates were virtually the same. Does distance traveled appear to be a quadratic function of altitude? __________________ It was a mistake to come back.

07-10-2003, 01:02 PM	#2
Cooleyvol Hall Of Famer Join Date: Dec 2001 Location: Union City, TN Posts: 6,383	We'd love to have this on OOTPLinks.com in the Downloads section. There's a FAQ on the site on how to upload the zip file to our site. Once you do that, go to the Downloads area and add a link to it. then go post news on the front page announcing it..........the world will see it on OOTPLinks.com!!

07-10-2003, 09:25 PM	#6
84CubsFan Major Leagues Join Date: Mar 2003 Posts: 376	Pine Tar, Forgot to mention: you've probably already considered this, but if you're worried about having all 100 averages (for fictional leagues using historical players, e.g.) you can always do number tweaks yourself. That is, if the league average for LHR is 93, you can add 7 to every park's LHR factor. It's not elegant, but it will work numerically.

07-11-2003, 11:56 AM	#7
84CubsFan Major Leagues Join Date: Mar 2003 Posts: 376	Cooleyvol, I don't have FTP software on my computer, but you're welcome to put the program up on OOTPlinks.

07-12-2003, 07:46 PM	#9
[WWBL]Batboy Major Leagues Join Date: Jan 2002 Location: Atlanta, Ga Posts: 485	This is awesome! I'm editing my ballparks right now. Thanks man!

07-17-2003, 03:16 PM	#11
84CubsFan Major Leagues Join Date: Mar 2003 Posts: 376	Sorry, seth, didn't see your question. If you want to make altitude a factor, assume a standard and then set bonuses or penalties accordingly. I don't know the research about baseball performance at different altitudes, but assume that at 500 feet, the standard ratings apply. Then do + or - 1 bonuses or penalties based on 500 foot increments. Fictional stadium at an altitude of 500ft: (Ratings) 2B 100, 3B 109, RBA 91, RHR 93, LBA 107, LHR 105 Same stadium at 5500 ft: (Ratings) 2B 110, 3B 119, RBA 101, RHR 103, LBA 117, LHR 115 Same stadium at -500 ft (if you want to build it there): (Ratings) 2B 98, 3B 107, RBA 89, RHR 91, LBA 105, LHR 103 It's kind of simplistic, but it will give you the effect you're looking for, I think.

07-19-2003, 01:11 PM	#13
84CubsFan Major Leagues Join Date: Mar 2003 Posts: 376	Yeah, it could definitely be added to the generator with ease, but I hadn't even considered it because I just needed a park to use for already created teams in a known cities. A randomly generated park with adjustments for 6700ft of altitude (though cool!) wouldn't be of much use in Chicago, unless of course they added on to the Sears Tower. As for the decrease in 2B and 3B ratings that you suggested, you may indeed be right, but I'm not sure that the physics would work like that. Yes, a ball that would hit the wall and carem around the field allowing a triple at sea level would probably be a homer at 5280 ft. But a ball lined to the left fielder for an out at sea level would perhaps go over his head, hit the wall and carem, etc., allowing a triple at 5280 ft. It seems to me the numbers would all increase, no?

07-19-2003, 03:34 PM	#14
seth70liz76 All Star Starter Join Date: Feb 2003 Posts: 1,634	From what I've been able to gather from a discussion in the main forum abt the park ratings, is that the increase in the Ave factor would boost the 2B and 3B totals, by the simple increase in Ave rating. I take the 2B/3B/HR ratings do not, by themselves, determine the amount of 2B/3B/HR hit, but what percentage of hits are 2B/3B/HR (did that make sense?). So, it's like layers: increase Ave increases the extra base hits, just because there are more hits, and an increase in HR increases the HR even more. But you do raise a point, line drive outs, would now carry over an outfielders head, but would that be part of the Ave or 2B/3B ratings? __________________ It was a mistake to come back.

07-21-2003, 02:00 PM	#15
Dark Horse Hall Of Famer Join Date: May 2002 Location: Texas! Posts: 2,633	i think it got lost in the wash on the other threads. But there are columns in the ballpark conversion tool that you can use for altitude. i put in columns to take into consideration how well the ball carries to LF, CF and RF. They are called carL, carC and carR. That takes into consideration wind and altitude. If the wind blows out to LF, then you put a positive number in carL. If the wind blows in from RF, then you put a negative number in carR. And if you're playing in Denver you can put a positive number in all three columns. The number in these columns only effect average and home run ratings. But the formula can always be adjusted to fit your taste. __________________ A Justafan Fan LBA Geo Bahn Rock Hounds fan of the ISLANDIAN PRO ALLIANCE

12-28-2003, 03:13 AM	#17
Sagitta Major Leagues Join Date: Aug 2002 Location: Bouncing between Phillies and Red Sox territory Posts: 357	Sorry to dredge up an old link, but I made a rudimentary altitude spreadsheet in Works a long, loooong time back. I used the OOTP4 stadium data as a base model, and worked out a rough set of equations for determining HR effects based on the altitude of the park. I didn't work the data in for triples, doubles or hits, as IMHO those would largely remain uneffected. I'm trying to locate my ZIP file now with the spreadsheet in it. I just remember that you can get some scary figures if you try placing a stadium in -for instance- Aspen, Colorado (altitude 8000 feet!). The file may still be on the boards buried somewhere, I vaguely remember posting it here over a year ago. __________________ I'm a lifelong Phillies fan - "Hey, at least we beat the Braves in '93."