Schedule:Compact
For flexibility, a schedule can be entered in “one fell swoop”. Using the Schedule:Compact object, all the features of the schedule components are accessed in a single command. Like the “regular” schedule object, each schedule:compact entry must cover all the days for a year. Additionally, the validations for DaySchedule (i.e. must have values for all 24 hours) and WeekSchedule (i.e. must have values for all day types) will apply. Schedule values are “given” to the simulation at the zone time step, so there is also a possibility of “interpolation” from the entries used in this object to the value used in the simulation.
This object is an unusual object for description. For the data the number of fields and position are not set, they cannot really be described in the usual Field # manner. Thus, the following description will list the fields and order in which they must be used in the object.
Information from the EnergyPlus Input Output Reference:
Field: Name
This field should contain a unique (within all Schedules) designation for this schedule. It is referenced by various “scheduled” items (e.g. Lights, People, Infiltration) to define the appropriate schedule values.
Field: ScheduleType
This field contains a reference to the ScheduleType. If found in a list of ScheduleTypes (see above), then the restrictions on the ScheduleType could be used to validate the referenced WeekSchedule (which reference DaySchedule) hourly field values. Field-Set (Through, For, Interpolate, Until, Value) Each compact schedule must contain the elements Through (date), For (days), Interpolate (optional), Until (time of day) and Value. In general, each of the “titled” fields must include the “title”.
Field: Through
This field starts with “Through:” and contains the ending date for the schedule period (may be more than one). Refer to Table 4. Date Field Interpretation for information on date entry – note that only Month-Day combinations are allowed for this field. Each “through” field generates a new WeekSchedule named “Schedule Name”_wk_# where # is the sequential number for this compact schedule.
Field: For
This field starts with “For:” and contains the applicable days (reference the compact week schedule object above for complete description) for the 24 hour period that must be described. Each “for” field generates a new DaySchedule named “Schedule Name”_dy_# where # is the sequential number for this compact schedule.
Field: Interpolate (optional)
This field, if used, starts with “Interpolate:” and contains the word “Yes” or “No”. If this field is not used, it should not be blank – rather just have the following field appear in this slot. The definition of “Interpolate” in this context is shown in the interval day schedule above.
Field: Until
This field contains the ending time (again, reference the interval day schedule discussion above) for the current days and day schedule being defined.
Field: Value
Finally, the value field is the schedule value for the specified time interval.