These are chat archives for nightscout/intend-to-bolus

14th
Jan 2015
Scott Leibrand
@scottleibrand
Jan 14 2015 04:16
@jasoncalabrese agreed. The hard part will be deduplicating manual and automatic bolus entries, when the auto uploads are unreliable, and the manual timestamps never exactly match the automatic ones.
Jason Calabrese
@jasoncalabrese
Jan 14 2015 04:17
yeah
maybe we can treat device data as immutable, but allow some other data to be modified
so device data can be stored in a way that's easy to display, merge, etc
Dana Lewis
@danamlewis
Jan 14 2015 04:20
Challenge is the walk-away, come back problem when you're off and on the uploader and so device and manual data compete. Currently creating all kinds of bugs for various scenarios.
Jason Calabrese
@jasoncalabrese
Jan 14 2015 04:20
thought of a quick hack for you to clean up the display, for temp basal, just set a high bg, then they'll be drawn at the top
Scott Leibrand
@scottleibrand
Jan 14 2015 04:26
Well, right now we don't even have the concept of a temp basal treatment event, do we?
i want to get away from the "0.1U every x minutes" hack as soon as we we can.
Jason Calabrese
@jasoncalabrese
Jan 14 2015 04:30
I'd like a simple model for manual entry, will be a while before I can use a mdt pump for real
need to make a remote first
Ben West
@bewest
Jan 14 2015 05:22
I had a git-phr plan for that
stubbed out a few things
basically idea was to check device data into special device-data repo
use software to automatically transform it in series of commits/merges into master format, all aggregated, but stuffed away in the git log
then re-import the records from master
or simply get just the new records that were added :-)
put that in the db
but only works for the immutable stuff like device data
for comments/conversations it's not good really
Scott Leibrand
@scottleibrand
Jan 14 2015 05:26
I am always amused at how many nails @bewest wants to hit with a git hammer. :-)
Ben West
@bewest
Jan 14 2015 05:27
hehe, only handful of problems
starting to take shape a bit more
needs some community buy-in though with people suggesting better stories... like maybe image plus little story of FB post -> github issue -> release