"In all these simulations," continued Roscoe, "you need to devise a sort of random number generator." "Well," I said, "what devices did you have at your disposal?" "Not much," responded Roscoe. "All we had were three identical dice of the usual variety, with one to six spots on each. Still, I figured it would be easy to simulate probabilities with them, because that was really what we needed to do. We decided that the simplest thing to do was roll the three dice simultaneously, add up the number of spots, and use that total to determine success or failure." "Probabilities? I'm not sure I understand," I said. "Sure, probabilities! That's how the fantasy baseball concept works. For example, assume you have a hitter at the plate with a batting average of .250. At the lowest level of sophistication (forget, for a minute, about walks) we need a way of randomly deciding if he gets a hit for this at-bat, so we need to create a random event that has a probability of occurring 250 times out of 1,000." I had never known Roscoe to be that interested in probability and statistics, but I was about to be impressed. "Now in reality, it's more complicated. In our game, for example, we ignored the quality of the pitcher, and complicated situations like sacrifice flies and so on." "Well, assuming you have made these simplifications, how do you actually simulate a batter's appearance at the plate?" I asked. "We have only two things to think about," Roscoe replied. "Plate appearances and official at-bats. When a player gets a walk, it counts as a plate appearance, but not as an official at-bat. So basically, you need two numbers: the percentage of plate appearances that yield official at-bats for that player, and then his batting average. Suppose, for example, that a player walks in one out of every 10 plate appearances.
"On the other hand, if you don't roll that total, then the player does not walk; instead, he has an official at-bat. Now you take his batting average, say .250, and you roll for that probability. If you're successful, he makes a hit; if not, he is out. Then, of course, you can roll for what kind of hit (single, double, triple, home run) by using those statistics per at-bat. And so on. I used batting average as the generic example, but basically you can refine the simulation to your heart's content, depending on how many of the 'corner cases' you want to include.
"Fair enough. I get the gist of it. So what's the problem?" I replied in turn. "The problem," said Roscoe, "is this: Can we figure out how to simulate probabilities using a device as simple as three dice, and still have enough granularity to make the simulation reasonable? For example, if we can only simulate .250, .500, and .750, we don't have enough values to do a good simulation." "Well, if you throw all three dice simultaneously, you get totals that range from 3 to 18; that's 16 different outcomes, so that's a start," I responded. "Indeed," said Roscoe, "that is exactly how we proceeded." |

The Software Development Edge(c) Essays on Managing Successful Projects

ISBN: N/A

EAN: N/A

EAN: N/A

Year: 2006

Pages: 269

Pages: 269

flylib.com © 2008-2017.

If you may any questions please contact us: flylib@qtcs.net

If you may any questions please contact us: flylib@qtcs.net