Originally Posted by microe
First, specify the resolution of the mouse by either typing in a value or by clicking the Measure
button and following the instructions in the text box at the bottom. Helpful hint, the program does not intercept clicks or movements from the system so I usually just click in the text box area when starting the data collection.
Second, collect some mouse data by clicking the Collect
button and following the instructions in the text box at the bottom.
After that you can Plot
the data you have collected using the specified cpi for calculations.
You can also save and load your data to .csv for future reference or importing into other programs like excel or [R] etc...
As far as the plots are concerned, first thing I do is window the data (to hide the garbage at the beginning and end of the collection) using the Data Point Start and Data Point End. From there it depends on the movement that was recorded. Here are some examples:
Count vs. Time: This is for looking at the raw counts from the mouse. The line is a moving average of the data and is provided as a general reference to gauge the consistency of the reporting from the mouse. For a mouse that does not loose tracking you will see the counts generally bouncing above and below the line without much deviation. If the counts deviate too much from the line then the mouse tracking may not appear smooth. If the mouse looses tracking then you will see the counts go erratic. You can also sometimes see angle snapping / prediction here (the counts will go to zero and hold there even though you moved the mouse with a slight arc). You can also see data path clipping here if the data plateaus at a fixed value (e.g. 127 for 8-bit mice). If the mouse is performing some form of multiplication for cpi boosting then you may be able to see that here as skipped counting steps.
Velocity vs. Time: This uses the time interval between updates, the cpi, and the counts to calculate the velocity of the mouse movement. Using fast swipes you can try to get the malfunction rate of the mouse here. Just like Counts vs. Time going erratic, when the tracking is lost the velocity goes erratic as well.
Interval vs. Time: This is for checking the consistency of the update rate from the mouse (i.e. 1000 Hz mouse updates every 1 ms).
X vs. Y: This is just plotting the data that you collected as a path. Like paint testing you can draw arbitrary shapes and see the exact raw mouse reports (e.g. jitter, angle snapping, stair stepping, etc...). Arbitrary movements can be used for acceleration and accuracy testing using this kind of plot as well. For example accuracy can be tested by starting from some point "A", moving the mouse (e.g. varying speed / angles) and then returning to point A. You should see the path that you moved the mouse along with the start and end points being roughly the same. You can do fast swipe / slow swipe back to the same point movements for acceleration testing. You can also do things like move the mouse in a bunch of circles and seeing if the path drifts away.
I hope this helps.