Simulator Values - Manual Override

It would be nice to be able to adjust the metrics manually that the simulator injects randomly when you start the simulator. To emulate conditions your code is handling.

One example is when you set GPS to Not Available, in a real device Speed is NULL, the simulator continues to send a random value. But in general a table of all simulated values would be nice to be able to allow random values between X and Y. And if X=Y, then of course it is a stable value.

  • I fully agree.
    For developing and testing of algorithms it's often necessary to get defined sensor values, e.g. constant or ramped elapsedDistance rate.

    Also, currently the simulator values at start of an activity change randomly between running speed (e.g. 7 min/mi) and bike speed (e.g. 3 min/mi). This make it hard to verify and compare the results of algorithms.