Why does Cyclic Measurements' maximum calculation use values from the next peak?

By default Cyclic Measurements detects and places event markers at the maximum of each peak. When calculating the maximum from each cycle, either in a Cyclic Measurements channel calculation or in the Data Pad, this default setting can lead to unexpected results. This is because Cyclic Measurements defines the cycle as the region between two detected events, and then uses the maximum value in that region as the cyclic maximum. 
servlet.ImageServer?id=01520000001fC9p&oid=00D20000000HncM

Example: If you have three peaks selected with highest values of 5V, 3V and 5V respectively, the maximum calculation will return close to 5V for the middle cycle, because at the end of that cycle the signal value approaches 5V (the next peak).

To resolve this, Cyclic Measurements can be set to detect on the minimum rather than the maximum. In the Customize dialog, the Trigger setting in the Detection parameters needs to be changed to Minimum. This will ensure only one peak is included in each cycle and the maximum values are reported as expected.