How do I "want" to make a schedule? Well, I do want to satisfy whatever requests/requirements are specified. But I have more experience and comfort when that means something in a form like MLB has. My tools have been developed to work more easily for such a form. That is due in part to various factors that all can relate - I am familiar with and thus like the form, I believe other people tend the same way overall, and OOTP is probably geared toward that form.
What are the characteristics of that form to which I pay particular attention when building a schedule?
Showing posts with label parameters. Show all posts
Showing posts with label parameters. Show all posts
Sunday, March 31, 2019
Tuesday, October 13, 2009
The Modern MLB schedule
When I make a schedule I tend to gravitate in the absence of contrary specifications (and maybe sometimes in spite of them!) to a form very similar to that of modern Major League Baseball (MLB) schedules for parameters not specific to league structure. What I mean by modern is basically the last several years when I have been making schedules, though not much has changed across the wild card/interleague era going back to the mid-1990s. Maybe "current" is a better term, but I am using "modern".
This is probably the sort of schedule with which more people, at least in the US and Canada, are more familiar than any other. I suspect that even if the specifics are not consciously known, many people have a good "feel" for many of the parameters. Unless something is specified otherwise I will generally make the assumption that someone requesting a schedule is figuring on parameters similar to current MLB. From that mindset initially when I first got into this some of my creation techniques became geared more toward making schedules with resemblance to modern MLB. That in turn leaves me more inclined in that direction, which over time leads to a preferred style.
Now I will describe and discuss some of the parameters of the modern MLB schedule. Feel free to comment on any you may like or not like.
This is probably the sort of schedule with which more people, at least in the US and Canada, are more familiar than any other. I suspect that even if the specifics are not consciously known, many people have a good "feel" for many of the parameters. Unless something is specified otherwise I will generally make the assumption that someone requesting a schedule is figuring on parameters similar to current MLB. From that mindset initially when I first got into this some of my creation techniques became geared more toward making schedules with resemblance to modern MLB. That in turn leaves me more inclined in that direction, which over time leads to a preferred style.
Now I will describe and discuss some of the parameters of the modern MLB schedule. Feel free to comment on any you may like or not like.
Wednesday, September 30, 2009
Schedule parameters introduction
I know this may be like telling people who wonder how to build a house, 'this is a board, and this is a nail.' But I think talking about some nuts and bolts (and mixing metaphors) is a good start. I do want to get the basics out there and have people think about the factors that come into play when mapping out a schedule. Plus I am still figuring out how I want to approach describing aspects of the creation process.
Everything that defines how to make a schedule can be considered parameters. All the details in a request for a schedule, plus a variety of other details typically not specified are parameters. Total number of games, numbers of games against division/league/interleague opponents, start/end dates, All-Star Break, and offday frequency are among the key parameters.
A well-defined schedule request includes specification of enough parameters to establish a good blueprint for constructing the schedule. Most of the above-mentioned are critical. Obviously without the number of games there is no way to know how to make a schedule. Perhaps less obviously though the timeframe for the schedule is important. There is a major difference between a 100 game schedule spanning 16 weeks versus spanning 26 weeks. You can say build a house that looks like this, but you better also tell the size to make it.
Every possible detail need not be explicitly spelled out in a request. Some parameters can be defined by other parameters. For example, offday frequency is generally established by the number of games plus the start and end dates rather than being stated directly.
Some parameters I will take the liberty of defining myself if the request did not and there is an apparently obvious choice. For a 162 game schedule, unless told otherwise I will assume it can be like modern MLB and span 26 weeks (including, if applicable, a half-week All-Star Break).
The better defined the parameters are, the clearer the blueprint is, and thus the more certain the instructions on how to build the schedule will be. That is usually good, however it can also cause problems. Parameters might be contradictary. That can usually be fixed though. A more difficult problem is when parameters are such that I do not see the schedule as being feasible to produce. A complicated league structure with a very specific breakdown of games per opponent simply may not be possible to make, or at least in any reasonable amount of time.
In the future I plan to discuss how various parameters fit into my schedule creation process.
Everything that defines how to make a schedule can be considered parameters. All the details in a request for a schedule, plus a variety of other details typically not specified are parameters. Total number of games, numbers of games against division/league/interleague opponents, start/end dates, All-Star Break, and offday frequency are among the key parameters.
A well-defined schedule request includes specification of enough parameters to establish a good blueprint for constructing the schedule. Most of the above-mentioned are critical. Obviously without the number of games there is no way to know how to make a schedule. Perhaps less obviously though the timeframe for the schedule is important. There is a major difference between a 100 game schedule spanning 16 weeks versus spanning 26 weeks. You can say build a house that looks like this, but you better also tell the size to make it.
Every possible detail need not be explicitly spelled out in a request. Some parameters can be defined by other parameters. For example, offday frequency is generally established by the number of games plus the start and end dates rather than being stated directly.
Some parameters I will take the liberty of defining myself if the request did not and there is an apparently obvious choice. For a 162 game schedule, unless told otherwise I will assume it can be like modern MLB and span 26 weeks (including, if applicable, a half-week All-Star Break).
The better defined the parameters are, the clearer the blueprint is, and thus the more certain the instructions on how to build the schedule will be. That is usually good, however it can also cause problems. Parameters might be contradictary. That can usually be fixed though. A more difficult problem is when parameters are such that I do not see the schedule as being feasible to produce. A complicated league structure with a very specific breakdown of games per opponent simply may not be possible to make, or at least in any reasonable amount of time.
In the future I plan to discuss how various parameters fit into my schedule creation process.
Subscribe to:
Posts (Atom)