DOE-2 Reference Manual Version 2.1 - DOE2.com

c. If parametric study is planned, to evaluate the effect of varyingspecific system parameters, use the PARAMETER instruction tosimplify preparation of input data for the multiple runs required(see discussion in Chap. II).d. If, at this point, the user is able to identify the SYSTEM-TYPE(see SYSTEM co~~and), he should refer to the proper ApplicabilityTable in Sec. B. of this chapter. This table will identify, forthe user's chosen system, which commands and keywords areapplicable, required, and optional. This table is the user'sguide and checklist because not all commands and keywords areappropriate to all systems. This-Ghapter addresses 21 differenttypes of systemS:- The user will notice that after identifyinghis SYSTEM-TYPE, the magnitude of this manual will appear todiminish. He can then turn his attention to "what is necessary",not "what all is available". The alternative, of course, toidentifying SYSTEM-TYPE now is to review, the entire chapter andthen select a SYSTEM-TYP~ Entering data without having chosena SYSTEM-TYPE is next to impossible (see the keyword SYSTEM-TYPEin the SYSTEM instruction for more information on this subject).If, of course, the user chooses the wrong SYSTEM-TYPE, he canalways return to this point and choose a different one.e. Prepare and enter as many schedule instructions (DAY-SCHEDULE,WEEK-SCHEDULE, SCHEDULE, and/or DAY-RESET-SCH, RESET-SCHEDULE)as are required for the system(s) being specified. (Thefollowing SOL keywords are schedule-dependent; HEATING-SCHEDULE,COOLING-SCHEDULE, FAN-SCHEDULE, HEAT-TEMP-SCH, COOL-TEMP-SCH,MIN-AIR-SCH, COOL-SET-SCH, HEAT-SET-SCH, HEAT-RESET-SCH,COOL-RESET-SCH, NATURAL-VENT-SCH, BASEBOARD-SCH, VENT-TEMP-SCH,INDUC-MODE-SCH, and REPORT-SCHEDULE). Note that the sameSCHEDULE instruction (or RESET-SCHEDULE instruction) can bereferenced by more than one keyword.In actual practice, the user will probably generate the schedulesif and when needed. The input tends to be more orderly ifschedules are grouped at this point, but that is not necessary.f. One or both of the ZONE subcommands, ZONE-AIR and ZONE-CONTROL,may be used to enter zone data (in lieu of entering this datadirectly with the ZONE instruction). The user may prepare andenter as many of each type as there are zone-to-zone variationsin the specified data, up to the limit specified for thatcommand. Once a ZONE subcommand is labeled and data are enteredfor the applicable keywords, it can be referenced by any numberof different ZONE instructions, thus reducing data input effort.A ZONE SUbcommand, when used, must always be entered before theZONE instruction in which it is referenced.Note: All subcommands must be defined before being referenced.However~AY-SCHEDULEs, WEEK-SCHEDULEs, SCHEDULEs, ZONEs, andSYSTEMs may be referenced and defined later (except for use inthe REPORT-BLOCK instruction).IV.6 (Revised 5/81)