When a reporting range is set, min_or_max_peaks_mode (1) allows the user to find the minimum or maximum time step value within it and for the set schedule. Note that this is not currently possible for frequency mapping (e.g. finding the day with the highest thermal discomfort frequency), but might be added in future releases.
For example, selecting the whole year from daily inputs in average mode (1 – 365) with the variable Zone Air Temperature will return as display values either the minimum or maximum air temperature that occurred per zone. The reporting_frequency (2) switch here determines the time resolution, meaning that in the daily mode example, the hottest or coldest daily average per zone is returned from within the set range; hourly would give the hottest/coldest hour, monthly th hottest/coldest month.
Additionally, time stamps are reported to the “Zone Peak Reports” panel (3) and also mapped at surface centroids through GH components. Looking at them closely, one can see that peaks may not always occur at the same time even in spatially close zones; the peak value display is temporally asynchronous and can hence be used to generate spatial “sensitivity maps”.
Triggering peak mode in the annual reporting frequency outputs time stamps for all lower frequencies down to hourly, but as display values still returns sums or averages, not peaks. This is to facilitate the at-a-glance comparison of annual sum/average and all-timestep average or sum peaks per zone.