Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Multiple cgm data sources #539

Open
LongboatAline opened this issue Feb 23, 2019 · 2 comments
Open

Multiple cgm data sources #539

LongboatAline opened this issue Feb 23, 2019 · 2 comments

Comments

@LongboatAline
Copy link

LongboatAline commented Feb 23, 2019

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:

  • Depending on the uploader, multiple traces could be assigned different colour schemes.
  • if more than one uploader is detected, there could be the option to select the one(s) to display. (This would also address Option to hide the same sugar levels from different sources #508, I'd think)
  • Uploaders could be classified in
    • 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.)
201812 27_28enlite - unknown

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...
noise2sensors - tidepool

@clintonium-119
Copy link
Member

@clintonium-119
Copy link
Member

Hi Tatjana. Glad to hear you're enjoying experimenting with our platform :)

We have had some internal discussions about how we want to handle this, but we haven't come to a definite solution as of yet.

I've forwarded your suggestions to the design and engineering team. In the meantime, you can track progress of this on the Trello card referenced above.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants