Has no one noticed the last "anomaly" I mentioned? Perhaps no one cares.
Well, looks like I found another "anomaly". Have a look at the capture attached. Notice the counts on the statistics. For some really odd reason, the count on the fall time is twice the others even though they were all started at teh same time.
Not an anomaly.
Some measurements are performed once per screen, some will be done as many times as possible.
For instance, RMS is once per screen (one triggered acquisition), period or frequency can be 100 or 1000 times if there are 1000 pulses on screen.
Combine this with track on measurements for seeing how it changes with time.
In measurements Statistics menu you can setup how it works.
There are Count Limit and AIM limit params.
AIM limit controls how much maximum measurements will be performed per screen (for measurements that support it).
IF you set it to 1 you will get only one measurement per screen for every measurement
Count limit is max number of running length of data used for statistics.. If you set it to anything else than unlimited, than that number will be max of measurements used for stats, and there will be no multi measurements either.
Play with that a bit to get an idea..