First visualization: understanding average or sum mode, scheduling & time ranges

Mr.Comfy calculates averages or sums (or finds peaks of those, see next section) of the hourly input data based on the provided schedule (schedule_hour_start, schedule_hour_end) (1) and related display modes. Scheduling means that sum/average results are calculated from the specified hours, making it possible to, e.g., map zone temperatures only during the afternoon. The hour input convention follows human standards; “8 – 12″ would instruct the tool to include the hour beginning from 8 up to 12 but not to consider any data for the last input hour (hour 11 is the last data source in this example).

Average_sum_or_freq_mode (2) needs to be chosen by the user depending on the report variable; it would be strange to sum zone temperatures, but would e.g. make sense for cumulative energy use. Note that when e.g. summing report variables with the unit Watt, Watt hours result. As the *.csv time step required by Mr.Comfy is hourly, keep in mind that the individual hour data may already contain averages or sums of whatever report variable is requested. Frequency mode counts the hours within a given schedule and mapping range combination that either meet a single condition or fall within a custom range. See the frequency / conditional percentage mapping page for details.

The schedule and sum/average/frequency combination alone, however, does not yet define which date range or time step is actually mapped. Range or point in time selection is made through the input range_or_point_in_time_mode (3). When in point in time mode, the position of the hour/day/month_report_time_start slider selects the current time step. Range mode takes its start/end bounds from both frequency slider input positions (hour/day/month_report_time_start to end) (4). Which slider pair or point in time input is currently active is governed by the selector reporting_frequency (5). In annual mode, all but the schedule inputs have no effect. Hourly time inputs follow the schedule hour declaration convention; daily and monthly inputs (1 – 365 / 1 – 12) always include values for both minimum and indicated maximum, meaning to e.g. set day 22 – 48 would include data of day 48, and not only go up to it as would be the case in the hourly input.

In essence, selecting a reporting frequency and range vs. point in time mode allows the user to either generate static maps of season & schedule combinations, or to walk through individual time steps filtered through a schedule. Beware that no scheduling is in effect when in hourly time step mode! The currently active time step or range is reported in the “Report Time Range & Schedule” output panel (6).

Note that when walking through time steps in this simple scenario, the mapping color extremes are always fit to the minimum and maximum values of all set zones (unless null zone suppression is turned on, see section of same name). Hence, the color change between zones and individual time steps denotes relative differences between values only (see sections Color & data output customization & Visualization bounds for details).