Open brandonarbiter opened 10 years ago
cheddar
commented
10 years ago This is based on an older version of the medtronic parser. Let's make sure that we deploy the newer version and get brandon to upload again and verify the behavior at that point before spending too much time debugging this.
cheddar
commented
10 years ago @brandonarbiter ping to have you try again
brandonarbiter
commented
10 years ago @cheddar I'm still seeing a static basal rate. It reads "0.4U over 3421 1/2 hours" :)
brandonarbiter
commented
10 years ago @cheddar This behavior is consistent on Staging and Prod.
cheddar
commented
10 years ago Ok, so you reuploaded and still see it @brandonarbiter? Let me look at the data then and try to figure out what is happening.
brandonarbiter
commented
10 years ago Correct
Brandon Arbiter VP, Product + Biz Dev Tidepool http://www.tidepool.org | brandon@tidepool.org 917.536.0505 (m)
On Tue, Apr 29, 2014 at 2:24 PM, cheddar notifications@github.com wrote:
Ok, so you reuploaded and still see it @brandonarbiterhttps://github.com/brandonarbiter? Let me look at the data then and try to figure out what is happening.
— Reply to this email directly or view it on GitHubhttps://github.com/tidepool-org/hub/issues/23#issuecomment-41734152 .
cmakler
commented
10 years ago
Howard and I futzed with my medtronic pump on Feb 19, forcing a rewind and cannula fill in an attempt to debug a Carelink issue. Then I removed the battery from the pump and stopped using it until Feb 26.
blip recognizes the basal rate from Feb 19 at 0.4u/hour. Then, despite the pump being off, it maintains that rate until Feb 26 (the date I turned the pump back on), when at ~10:30pm it changes to .525u/hour.
This is an interesting edge case. I don't think it needs to be addressed before pilot, but since it's happening, I wanted to document and provide. What if I had data from another pump for this time period? Would it show two basal rates? How would the conflict resolve?