Steps to reproduce:
Create a datafield and trace out the current, average, and max.
Expected results:
Simulator should provide valid values.
Actual results:
For example, this:
System.println(info.currentCadence+" "+info.averageCadence+" "+info.maxCadence);
Gave this where average value is a multiple of maximum - a logical and mathematical impossibility:
200 1064 234 200 1062 234 200 1059 234 200 1056 234 200 1054 234 200 1051 234 200 1049 234 200 1046 234 200 1043 234 200 1041 234 200 1038 234 200 1036 234 200 1033 234
This seems pretty consistent with cadence, but I have also noticed it sporadically with speed and power this morning.
Not sure whether it is relevant, but I have been toggling simulated data on and off also loading data from .FIT files.
Invalid data is particularly prevalent after swapping from simulated data to .FIT file data and back.
