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

17th
Apr 2018
Tim Gunn
@Tornado-Tim
Apr 17 2018 07:10
What have people got set for a Pump Battery Warning? I am now getting a battery warming because it was set at 1.39V but the pump battery symbol on the pump main screen is still full.
I use Energizer Lithium AAA
johnaras98
@johnaras98
Apr 17 2018 09:03
I have set the warning at 1.3V. You can check the discharge profile here : http://data.energizer.com/pdfs/l92.pdf
Tim Gunn
@Tornado-Tim
Apr 17 2018 09:07
Brilliant @johnaras98 , wondered if 1.39 was a bit conservative......
johnaras98
@johnaras98
Apr 17 2018 09:24
@Tornado-Tim when battery gets really low, your pump will first shutdown wireless comms, which will result to failed loop cycles, but pump operation will go on. With the Energizer Lithium this will probably happen between 1.25 and 1.20V.
fidoman
@efidoman
Apr 17 2018 11:14
Been on Fiasp for 2 weeks so far and though it's still early, the results are almost too good to believe this is the new normal. Since starting Fiasp, I haven't manually bolused at all, just announce meal carb guess at the time I eat and sometimes set a low temp target. My BG has stayed below 180 for 100% of the time in the past 7 days. Most of the time the post-meal spikes do not go above 130. I am eating the same (or perhaps more carbs) as before Fiasp. I haven't measured, but it seems that I'm having less lows because I'm letting OpenAPS do all the work. The times I've gotten myself in trouble in the past is when I manually bolus too much or try correct at the wrong time. Using Fiasp with OpenAPS "allows" me to be hands off. :smile:
RedCyclist1
@RedCyclist1
Apr 17 2018 14:53
I am looking for input on phone service. I am on Verizon, but thinking of going to T Mobile. Anyone use T Mobile and do you get good service all the time to run your rig? I travel and am looking for feedback in Az, Boise, Idaho and traveling to San Diego.
live4sw
@live4sw
Apr 17 2018 14:58
@RedCyclist1 I use t-mobile without any problems (in metro areas, none you listed though). Have you ever done offline access with your rig? I view that as a good backup if I ever have bad connectivity when traveling (if can't find good wifi).
RedCyclist1
@RedCyclist1
Apr 17 2018 15:10
@live4sw
Good point Andrew. I have not had to do that w Verizon but one of my rigs can do it. The other is too old and cannot be used for offline.
@danamlewis I know you travel a lot, what service do you use and how does it perform?
Dana Lewis
@danamlewis
Apr 17 2018 15:53
@efidoman 👏🏼😊
@RedCyclist1 was on AT&T; now on Verizon. Switched mostly for international coverage purposes, I don't pay attention to the US coverage maps. +1 for having an offline rig ready to go if you plan to travel.
user1109
@user1109
Apr 17 2018 17:00
@scottleibrand
var/log/openaps is filling up
pump-loop.log grows to 800-900 MB, then the loop stops, because there is "no space left on device"
I suspect that logrotate does not work properly. I changed the logrotate.conf from daily to hourly.
The 5 log files in var/log/openaps should rotate every hour , or not?
Scott Leibrand
@scottleibrand
Apr 17 2018 17:18
what is filling up pump-loop.log?
user1109
@user1109
Apr 17 2018 17:29
Starting oref0-pump-loop at Mon Apr 9 06:21:01 CEST 2018 with 5 second wait_for_silence:
MDT CGM configured; not waiting
Radio ok. Listening: .No interfering pump comms detected from other rigs (this is a good thing!)
Preflight OK.
Attempting to retrieve MDT CGM data from pump
date: invalid date ‘+%s’
/usr/local/bin/oref0-pump-loop: line 332: [: 1523247540: unary operator expected
MDT CGM data retrieved
MDT New cgm data reformatted
Old pumphistory-24h, waiting for 5 seconds of silence: Radio ok. Listening: .No interfering pump comms detected from other rigs (this is a good thing!)
Old pumphistory-24h refreshed
Profile less than 60m old; Profile valid. RefreshedNo duration found for 0 U/hr basalundefined { _type: 'BGReceived',
_description: 'BGReceived 2018-04-08T16:59:35 head[2], body[3] op[0x3f]',
timestamp: '2018-04-08T16:59:35+02:00',
_body: 'c02c01',
_head: '3f13',
amount: 155,
link: 'c02c01',
_date: '633b706812' } { _type: 'TempBasal',
temp: 'absolute',
_description: 'TempBasal 2018-04-08T16:14:49 head[2], body[1] op[0x33]',
timestamp: '2018-04-08T16:14:49+02:00',
_body: '00',
_head: '3300',
rate: 0,
_date: '710e104812' } { _type: 'BasalProfileStart',
_description: 'BasalProfileStart 2018-04-08T16:14:49 head[2], body[3] op[0x7b]',
timestamp: '2018-04-08T16:14:49+02:00',
_body: '202000',
profile_index: 16,
_head: '7b10',
rate: 0.8,
offset: 57600000,
_date: '710e300812' }
No duration found for 0 U/hr basalundefined { _type: 'BGReceived',
_description: 'BGReceived 2018-04-08T16:59:35 head[2], body[3] op[0x3f]',
timestamp: '2018-04-08T16:59:35+02:00',
_body: 'c02c01',
_head: '3f13',
amount: 155,
link: 'c02c01',
_date: '633b706812' } { _type: 'TempBasal',
temp: 'absolute',
_description: 'TempBasal 2018-04-08T16:14:49 head[2], body[1] op[0x33]',
timestamp: '2018-04-08T16:14:49+02:00',
_body: '00',
_head: '3300',
rate: 0,
_date: '710e104812' } { _type: 'BasalProfileStart',
_description: 'BasalProfileStart 2018-04-08T16:14:49 head[2], body[3] op[0x7b]',
timestamp: '2018-04-08T16:14:49+02:00',
_body: '202000',
profile_index: 16,
_head: '7b10',
rate: 0.8,
offset: 57600000,
_date: '710e300812' }
Warning; adjusting DIA from 2 to minimum of 3 hours
Warning; adjusting DIA from 2 to minimum of 3 hours
Warning; adjusting DIA from 2 to minimum of 3 hours
Warning; adjusting DIA from 2 to minimum of 3 hours
Warning; adjusting DIA from 2 to minimum of 3 hours
Warning; adjusting DIA from 2 to minimum of 3 hours
Warning; adjusting DIA from 2 to minimum of 3 hours
Warning; adjusting DIA from 2 to minimum of 3 hours
Warning; adjusting DIA from 2 to minimum of 3 hours
Warning; adjusting DIA from 2 to minimum of 3 hours
Warning; adjusting DIA from 2 to minimum of 3 hours
Warning; adjusting DIA from 2 to minimum of 3 hours
Warning; adjusting DIA from 2 to minimum of 3 hours
Warning; adjusting DIA from 2 to minimum of 3 hours
Warning; adjusting DIA from 2 to minimum of 3 hours
Warning; adjusting DIA from 2 to minimum of 3 hours
Warning; adjusting DIA from 2 to minimum of 3 hours
Warning; adjusting DIA from 2 to minimum of 3 hours
Warning; adjusting DIA from 2 to minimum of 3 hours
Warning; adjusting DIA from 2 to minimum of 3 hours
Warning; adjusting DIA from 2 to minimum of 3 hours
Warning; adjusting DIA from 2 to minimum of 3 hours
Warning; adjusting DIA from 2 to minimum of 3 hours
Warning; adjusting DIA from 2 to minimum of 3 hours
Warning; adjusting DIA from 2 to minimum of 3 hours
Warning; adjusting DIA from 2 to minimum of 3 hours
Warning; adjusting DIA from 2 to minimum of 3 hours
Warning; adjusting DIA from 2 to minimum of 3 hours
Warning; adjusting DIA from 2 to minimum of 3 hours
Warning; adjusting DIA from 2 to minimum of 3 hours
Warning; adjusting DIA from 2 to minimum of 3 hours
Warning; adjusting DIA from 2 to minimum of 3 hours
Warning; adjusting DIA from 2 to minimum of 3 hours
Warning; adjusting DIA from 2 to minimum of 3 hours
Warning; adjusting DIA from 2 to minimum of 3 hours
Warning; adjusting DIA from 2 to minimum of 3 hours
Warnin
Dana Lewis
@danamlewis
Apr 17 2018 17:30
^ @user1109 have you switch the dia on your pump to 3 or higher? If not, I recommend doing that
(But also @scottleibrand ^ wondering if we can prevent that from being so verbose over time)
user1109
@user1109
Apr 17 2018 17:38
@danamlewis
I switched to 2, i use fiasp
my doctor told me so
James Babcock
@jimrandomh
Apr 17 2018 17:39
The DIA setting in OpenAPS's config is the one that matters, not the one in the pump
Martin Haeberli
@mhaeberli
Apr 17 2018 17:40
@Tornado-Tim @johnaras98 YDMV; YourPumpMayVary, etc. but after a few experiences (we also use the Energizer Lithium AAA) we switch batteries by about 1.41 - 1.39 V indicated.
Dana Lewis
@danamlewis
Apr 17 2018 17:40
It is physiologically impossible to have a DIA of 2. Also, OpenAPS is using 5 for the fiasp FYI.
James Babcock
@jimrandomh
Apr 17 2018 17:41
I don't think those numbers are the same thing
Dana Lewis
@danamlewis
Apr 17 2018 17:43
So - to immediately cut down on log buildup - change pump dia. Will not change what OpenAPS is doing since it's using the curve defaults instead of pump.
Also make sure that you're using the ultra rapid curve
statuur
@statuur
Apr 17 2018 17:45
hardware concept OpenAPS.ai
@danamlewis
James Babcock
@jimrandomh
Apr 17 2018 17:47
Diagram is accurate for users with Medtronic CGMs, leaves things out for people with Dexcom CGMs
Dana Lewis
@danamlewis
Apr 17 2018 17:48
@statuur won't let me look closely on phone - will take a look later 😊 when at my desk
Thx for starting to take a crack at this!
statuur
@statuur
Apr 17 2018 17:49
@jimrandomh deliberately, because this infographic should explain the basic concept, made an other one about compatibility
James Babcock
@jimrandomh
Apr 17 2018 17:50
Right, the way to do it is probably to have several similar-style diagrams for different setups
Jon Cluck
@cluckj
Apr 17 2018 17:51
Very nice 😁
statuur
@statuur
Apr 17 2018 17:53
You mean also an explorer hat version? Are there more?
Dana Lewis
@danamlewis
Apr 17 2018 17:55
We'll have to figure out if we can do one that is general enough to support all the hardware options.
James Babcock
@jimrandomh
Apr 17 2018 17:55
So for example, in my rig, the Explorer board is connected to a Dexcom G4 receiver using a USB OTG cable, and it gets glucose data from there rather than from the pump.
statuur
@statuur
Apr 17 2018 17:57
Ahhh good to know! then your right indeed
katie disimone
@Kdisimone
Apr 17 2018 17:58
@scottleibrand @danamlewis Narrowed down the source of the extra cob mysteriously showing up. The additional COB appears to be triggered by a carb ratio change. Can you help explain why this would be happening? Prior to 19:30 the carb ratio is 35. At 19:30, carb ratio shifts to 9. Dinner is being bolused and entered prior to 19:30. Once 19:30+ hits, OpenAPS is revising the cob up significantly and the unexpected high temping happens
James Babcock
@jimrandomh
Apr 17 2018 17:58
But I think it'd be too confusing to put all the possible setups in one diagram; better would be to first ask which CGM someone has, then show Medtronic users the diagram you just posted, G4 users a different one
Scott Leibrand
@scottleibrand
Apr 17 2018 18:00
@Kdisimone ah. so what is probably happening there is that the previous carb absorption from lunch is recalculated using the new carb ratio, and comes "back into play". that is much too large of a difference in carb ratios between meals, and is likely being used to compensate for something else. the two CRs should be made close enough that lunch isn't considered to be still unabsorbed by dinner time.
katie disimone
@Kdisimone
Apr 17 2018 18:00
But openaps shouldn’t be UPing an entered carb value
that’s dangerous
Scott Leibrand
@scottleibrand
Apr 17 2018 18:00
it's not
katie disimone
@Kdisimone
Apr 17 2018 18:01
it is
Scott Leibrand
@scottleibrand
Apr 17 2018 18:01
those are lunch carbs showing up in COB again once the CR changes
katie disimone
@Kdisimone
Apr 17 2018 18:01
she enters 20g of carbs. once 19:31 comes around, Openaps starts using cob of 26g yesterday, 37g today.
The lunch carbs had already decayed to zero prior to dinner
Scott Leibrand
@scottleibrand
Apr 17 2018 18:02
if she didn't enter any carbs, once 19:31 came around, she'd still get COB jumping up from 0g to 11g
katie disimone
@Kdisimone
Apr 17 2018 18:02
Its dangerous...
Scott Leibrand
@scottleibrand
Apr 17 2018 18:02
yes. it is dangerous to have CRs that divergent
katie disimone
@Kdisimone
Apr 17 2018 18:02
no carbs should be coming back that had already been decayed
Scott Leibrand
@scottleibrand
Apr 17 2018 18:02
we should probably disallow CR settings that far off of reality
katie disimone
@Kdisimone
Apr 17 2018 18:03
or disallow carbs from reappearing?
Scott Leibrand
@scottleibrand
Apr 17 2018 18:03
that would require tracking state. the COB calculation is performed at each loop independent of how it was performed previously
so for example, if you edit your 2h-ago carb entry to add 15g of carbs, COB will increase when it's recalculated
Martin Haeberli
@mhaeberli
Apr 17 2018 18:04
@Kdisimone - is this ‘jumping CR’ thing to do with the Madrid openaps user from yesterday’s discussion?
katie disimone
@Kdisimone
Apr 17 2018 18:04
yes
Scott Leibrand
@scottleibrand
Apr 17 2018 18:04
despite the fact that it was lower 5m ago, the inputs have changed
the underlying problem here is that we're not sufficiently bounding the allowed inputs
Martin Haeberli
@mhaeberli
Apr 17 2018 18:05
on a distantly related note - we recently began using hot-backup openaps instances (two edisons). It occurs to me that it is VERY important that both be set to the same preferences, for example, and ideally work to evolve to similar autotune states, or one can get unexpected and potentially dangerous outcomes...
Dana Lewis
@danamlewis
Apr 17 2018 18:13
So for safety, short term: I would have the person change their carb ratios. If they don't want to do that, I would turn maxIOB to be very low (say 1u) and plan to only use it for mostly low fixing, if they don't want the rig to help out after meals. (Confirmed yesterday this person is not using SMB, which is good).
katie disimone
@Kdisimone
Apr 17 2018 18:13
I’ll disagree…why are we “sufficiently bounding” other user inputs like this one? I agree it’s a big jump…but that would seem to be something that they should be allowed to determine without having an unexpected safety issue
Scott Leibrand
@scottleibrand
Apr 17 2018 18:13
@danamlewis @user1109 openaps/oref0#976
user1109
@user1109
Apr 17 2018 18:14
@danamlewis
Scott Leibrand
@scottleibrand
Apr 17 2018 18:14
@Kdisimone do you have another suggestion for how to fix this?
Dana Lewis
@danamlewis
Apr 17 2018 18:14
may be something we can add as a warning somehow, check and if > X % or X amount, warn about the impact of it. but I think safety bounding to a reasonable amount is also a good idea, for people who unexepectedly come in with really disparate settings throughout the day
user1109
@user1109
Apr 17 2018 18:17
@danamlewis ok thank you.
Dana Lewis
@danamlewis
Apr 17 2018 18:19
@user1109 :+1: and thanks for flagging that; merging to dev and those warnings will be truncated in 0.6.1
Related: anyone who wants to help us do the next release more quickly, please see openaps/oref0#816 and the related notes around testing 0.6.1.
^ we especially need x12 testers to verify the setup is improved (and works); someone to document the offline web page; test that suspends properly count toward IOB (which will enable you to not need to temp-and-suspend if you prefer), etc. Lots of goodies in there.
Jon Cluck
@cluckj
Apr 17 2018 18:25
(please ping me on x12 issues too :) )
Dana Lewis
@danamlewis
Apr 17 2018 18:26
@cluckj ^wanna test some fresh? :)
Jon Cluck
@cluckj
Apr 17 2018 18:26
lol
Scott Leibrand
@scottleibrand
Apr 17 2018 18:32
@Kdisimone it might be possible to figure out how to apply the CR at the time of the carb entry instead of the current CR when calculating COB. But the dynamic COB calculation is already fairly complicated, and I’m not sure how easy that would be to do. We probably need to revisit the whole thing and deal with all the other known COB calculation issues (such as due to missing CGM data) together. In the mean time, a patch to ignore carbs issued prior to a ~2x CR change would probably be a faster way to address this.
James Babcock
@jimrandomh
Apr 17 2018 18:33
How biologically plausible is it to have CRs varying 2x throughout the day?
Scott Leibrand
@scottleibrand
Apr 17 2018 18:38
not very likely. most likely settings that divergent are compensating for something else, perhaps different absorption speeds of different foods, or perhaps related to different macronutrient composition (instead of entering carb equivalents for fat/protein), differing basal insulin needs around mealtime, or something else.
James Babcock
@jimrandomh
Apr 17 2018 18:44
Maybe the OpenAPS-users email list should get a warning about large CR differences potentially causing a problem?
katie disimone
@Kdisimone
Apr 17 2018 18:56
These (it’s happening to two families that have contacted me) are small kids. Lots more variation in kids than adults I suspect. I’m not judging the settings (yes, it is a very big change…but also kids are prone to ridiculous insulin needs right after they fall asleep if they are in growth spurt. So, if carbs are given before sleep vs after…there could be a very very dramatic difference)…more concerned about unexpected consequences of the settings.
Jon Cluck
@cluckj
Apr 17 2018 18:56
hormone cycling, too
Dana Lewis
@danamlewis
Apr 17 2018 18:58
Been talking with a few parents of smaller kids, too, about this - but doesn't seem like the ratios that diverse for carb ratio matches physiology. Basal rates or ISF changing more - yes, carb ratio that diverse seems to indicate compensation for other settings. I agree there is more variance for small kids, and we need to think about how to communicate this given the existing behavior, and think about potentially adjusting that design in the future. I logged an issue to track discussions around it and brainstorm short and longer term solutions, and I also modified the docs so people coming into OpenAPS, where they're reminded about settings and getting set up on Medtronic pumps, also see notes about DIA and carb ratio.
@Kdisimone do you know how Loop deals with a carb ratio change if it occurs in the middle of a carb absorption period?
katie disimone
@Kdisimone
Apr 17 2018 19:00
Loop doesn’t separate cob from the carb entry. so it is seamless. The users with this issue said they were operating on Loop for a year with same settings and didn’t have this problem on Loop. Just since coming on OpenAPS.
Dana Lewis
@danamlewis
Apr 17 2018 19:01
so it locks CR at the time of the entry (locks it to the carb entry and uses that for subsequent calculations)?
statuur
@statuur
Apr 17 2018 20:04
Been thinking about a way to be able to save money for OpenAPS users. Especially the hosting costs that come with Azure. I host my own Nightscout instance. The code is approximately 25mb and the node_modules 125 mb (which probably can be used for all instances). Me own cloud hosting server costs are 8 euro a month. 25gb of disk space. I i could setup a server dedicated for OpenAPS users with some kind of easy install wizard. Wouldn't that simplify Nightscout's install process and reduce the costs to zero per user? Other benefits could be centered storage of data and therefore easier big data analysis and updating Nightscout for all users at once? What do you think?
James Babcock
@jimrandomh
Apr 17 2018 20:05
Heroku free tier seems to work fine?
Dana Lewis
@danamlewis
Apr 17 2018 20:05
yea - we recommend Heroku for that reason
statuur
@statuur
Apr 17 2018 20:05
So your saying no need for that kind of solutions
Dana Lewis
@danamlewis
Apr 17 2018 20:06
related to easy improvements - some of the things I would love for folks to help out on is helping resolve the remaining issues around getting Autotune into NS reports; that will have a huge impact of allowing many hundreds more people to utilize autotune.
nah, most people are just running on Heroku and doing fine with free tier. thanks for the thought on that, though :)
(here's that nightscout/cgm-remote-monitor#3191 if you want to check it out and help out on debugging so we can move that along)
or anyone else :)
James Babcock
@jimrandomh
Apr 17 2018 20:09
What if Autotune's nightly reports came as -2 priority Pushover notifications? That's easier than getting them into Nightscout
Dana Lewis
@danamlewis
Apr 17 2018 20:10
the goal is to make Autotune more accessible for non-loopers as well
the infrastructure is mostly done, thanks to all the people in that PR, but there's some tweaking that needs to be done since different results are appearing in different browsers, so probably a counting thing that needs fixing
James Babcock
@jimrandomh
Apr 17 2018 20:10
Ok, that wouldn't work for someone who wasn't running OpenAPS at all
Dana Lewis
@danamlewis
Apr 17 2018 20:11
nope
(and for anyone who wants to dive into details, we can move this over to the openaps/autotune channel for detailed discussions)
Jon Cluck
@cluckj
Apr 17 2018 20:16
web-based autotune would be a game changer (and save some cycles on rigs)
Dana Lewis
@danamlewis
Apr 17 2018 20:17
I think OpenAPS users likely will still want to run it on their rigs in order to utilize the results for looping. but agree game changer for Loop & non-DIY-loop users
Jon Cluck
@cluckj
Apr 17 2018 20:21
and a fabulous place to educate LOADS of endocrinologists about DIY diabetes :)