|
||||||||||
|
Note: Be careful here, and be clever in naming your variables. For instance, somebody might be using 'oxygen-quantity' to mean the amount of oxygen used in a detailed industrial process. That's a bad move, because someone else might use 'oxygen-quantity' to mean the amount of oxygen needed for people to breathe per day. It's better to use a variable name like 'oxygen-ls-rate-lb-pppd'.
Nomenclature: "ls" is life support. "lb-pppd" is short-hand for "pounds per person per day". We use "rate" because this is a flow rate through the system, not a static quantity (use "quan").
For dollars, use "d" rather than "$" since the dollar sign will make most compilers choke. Calculate all money transactions in constant-year 1994 U.S. dollars.
We'll agree on other standard nomenclature and variable-naming conventions as we build up the model. Keep an eye on the 'Standard Variable Names Dictionary', which the APTC chairmen will maintain on the ASI web.
Use a standard time interval of one day where you can. We could write a simulation control executive which can handle slower or faster iteration intervals, but it will increase the complexity of the task. If the model depends upon an event, such as arrival of a commercial space liner, make sure that's obvious.
If it's really complex, consider developing a simplified model in parallel with the detailed one to speed up processing time. For example, to figure out the economic viability of the tourist transportation industry, we'll need a detailed model of the ship's operation. However, for a whole-moon economic model, we only need a summary model telling us where the money goes and what resources are required from the moon. You might find it easier to estimate the summary model first, and then refine it by working the details.
|
|