You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
primary uploaders (dumping unmodified data as read from the source),
secondary uploaders (repeating data from primary uploaders), and
tertiary uploaders (modifying the data they received, be it by adding their own calibration or smoothing, for example Kalman filters)
depending on noise, noisier traces could be given a lighter/transparent shade.
Example screenshots
Thanks for providing a bunch of servers to experiment with! :)
New sensor: Enlite2
Production server, patient 726922b6fb uploaded via Tidepool Uploader.
(That Sensor is displaying "typical Enlite behaviour" going deeper and deeper between calibrations.
I don't think BGs ever dropped below 160 during the initial 10 hours.)
Dying G5 and Enlite simultaneously
Integration Server, patient 98c5f0daa7, uploaded via xDrip.
I had kept the noisy G5 around for about a day, since I was curious "how bad it would get", and if it would resume operation at some point in time. Obviously, it didn't...
In the case that the traces of more than one sensor get uploaded simultaneously, it would be nice if they could be distinguishable in the view.
Some random ideas:
Example screenshots
Thanks for providing a bunch of servers to experiment with! :)
New sensor: Enlite2
Production server, patient

726922b6fbuploaded via Tidepool Uploader.(That Sensor is displaying "typical Enlite behaviour" going deeper and deeper between calibrations.
I don't think BGs ever dropped below 160 during the initial 10 hours.)
Dying G5 and Enlite simultaneously
Integration Server, patient

98c5f0daa7, uploaded via xDrip.I had kept the noisy G5 around for about a day, since I was curious "how bad it would get", and if it would resume operation at some point in time. Obviously, it didn't...