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

24th
Jan 2019
Scott Leibrand
@scottleibrand
Jan 24 10:24
@acember yes, you’re correct. Preference values have to be explicitly added to the profile processing code.
Jens Heuschkel
@juehv
Jan 24 16:29
Today Medtronic wrote me they discontinue old guardian technology and only provide Enlite v3 in future. Does anybody know if it is still compatible with the old v1 transmitters for the VEO pumps ?
Juan Mejías
@juanjuanmejias_twitter
Jan 24 19:29
Hello all, I have a question re maxSafeBasal. I thought this was = the Max Basal Rate setting from the pump, but in a decision from my rig I see a value that doesn't match that (4.971 u/h versus 11.00 u/h on my pump). Is there something I'm not accounting for?
image.png
Juan Mejías
@juanjuanmejias_twitter
Jan 24 19:35
I just checked my loop and I see that it's a changing value. What does it represent then?
image.png
Zach Gohr
@zgohr
Jan 24 19:37
it’s a safety multiplier in your preferences
well, it’s the lesser of a couple things
max_daily_safety_multiplier and current_basal_safety_multiplier
Juan Mejías
@juanjuanmejias_twitter
Jan 24 19:40
Yes, that's where I got it from. It says it's the max basal rate in the pump settings, but it seems like that's not the case. Or am I reading it wrong?
image.png
Zach Gohr
@zgohr
Jan 24 19:42
right, but it uses the “lesser” of the other safety multipliers
see example 2
the pump’s max setting is 2, and yet APS maxes out at 1.6
becuase 0.4 (current basal rate) * 4 (current basal multiplier) = 1.6 - in this scenario, the pump’s max setting isn’t even used
Juan Mejías
@juanjuanmejias_twitter
Jan 24 19:46
If I read it right, maxSafeBasal isn't the smallest of the three, it's just one of them, and it's always equal to the max basal rate from the pump. So in your description, the system would choose the smallest of max_daily_safety_multiplier, current_basal_safety_multiplier or maxSafeBasal. At least that's what I understand
Zach Gohr
@zgohr
Jan 24 19:47
the smallest of pump’s max safe basal OR daily_mult * maximum daily basal rate OR current_mult * current basal rate
Juan Mejías
@juanjuanmejias_twitter
Jan 24 19:49
Yes, correct. So maxSafeBasal should be a constant and = the pump's max basal rate
And in my case it's not equal to that value (4.971 vs 11 on the pump)
Zach Gohr
@zgohr
Jan 24 19:50
maxSafeBasal isn’t your pump’s value
it’s the computed value
Juan Mejías
@juanjuanmejias_twitter
Jan 24 19:50
Computed how?
Zach Gohr
@zgohr
Jan 24 19:50
maxSafeBasal != max basal safety setting (in pump)
Juan Mejías
@juanjuanmejias_twitter
Jan 24 19:51
What's the calculation?
Zach Gohr
@zgohr
Jan 24 19:51
computed by running the calculations i said above, and choosing the least
in the example table in the link i sent, the last row is the computed value in 4 different scenarios
“Actual temp basal rate allowed” == maxSafeBasal
Juan Mejías
@juanjuanmejias_twitter
Jan 24 19:52

I don't understand. You just said it's one of the three you compare

the smallest of pump’s max safe basal OR daily_mult * maximum daily basal rate OR current_mult * current basal rate

Zach Gohr
@zgohr
Jan 24 19:52
yes
John Sjolund
@sjolundjohn
Jan 24 19:52
Are there any differences from the documentation when setting up Papertrail for the HAT rig (with a PI). I have followed step and get this error:
root@hat:~/myopenaps# tar xzf ./remote_syslog*.tar.gz
root@hat:~/myopenaps# cd remote_syslog
root@hat:~/myopenaps/remote_syslog# sudo cp ./remote_syslog /usr/local/bin
root@hat:~/myopenaps/remote_syslog# 
root@hat:~/myopenaps/remote_syslog# vi /etc/log_files.yml
root@hat:~/myopenaps/remote_syslog# sudo remote_syslog
2019-01-24 19:45:14 ERROR  config_manager.go:208 Could not parse the config file: YAML error: line 10: mapping values are not allowed in this context
2019-01-24 19:45:14 CRITICAL  config_manager.go:145 Failed to configure the application: Could not parse the config file: YAML error: line 10: mapping values are not allowed in this context
Zach Gohr
@zgohr
Jan 24 19:52
that’s the equation it uses
Ha, i apologize. I don’t understand what you’re not understanding. Obviously we’re on different pages here.
Juan Mejías
@juanjuanmejias_twitter
Jan 24 19:54
So maxSafeBasal is the smallest of maxSafeBasal, OR daily_mult * maximum daily basal rate OR current_mult * current basal rate. Is that what you're saying?
John Sjolund
@sjolundjohn
Jan 24 19:54
@Teamhrach seems you had the same issue - could you fix?
Scott Leibrand
@scottleibrand
Jan 24 19:56
@juanjuanmejias_twitter maxSafeBasal = min(pump max basal, daily_mult * maximum daily basal rate, current_mult * current basal rate)
maxSafeBasal is the smallest of the three
Zach Gohr
@zgohr
Jan 24 19:57
@juanjuanmejias_twitter yes what scott said - you’re conflating maxSafeBasal with the pump’s max safety setting. they’re not the same thing
Juan Mejías
@juanjuanmejias_twitter
Jan 24 19:57
Thanks @scottleibrand, I see. Then this bit in the docs can be a bit misleading
image.png
Zach Gohr
@zgohr
Jan 24 19:58
oh wow, i didn’t even notice that in the docs. yes that is incorrect
Juan Mejías
@juanjuanmejias_twitter
Jan 24 19:58
If you read back that's what I was trying to say :D
Scott Leibrand
@scottleibrand
Jan 24 19:58
yes, that sentence is incorrect. Can you PR a fix?
Juan Mejías
@juanjuanmejias_twitter
Jan 24 19:59
Yes, for sure
Scott Leibrand
@scottleibrand
Jan 24 19:59
thx
Juan Mejías
@juanjuanmejias_twitter
Jan 24 20:14
@scottleibrand It's submitted
@zgohr Thanks for helping by the way. I could have explained much better
Zach Gohr
@zgohr
Jan 24 20:19
no problem!
Juan Mejías
@juanjuanmejias_twitter
Jan 24 21:51
@scottleibrand maximum daily basal rate, current basal rate: These two are taken straight from the pump's basal settings, or they're affected by autosens/autotune?
Scott Leibrand
@scottleibrand
Jan 24 21:55
Those are the autotuned values. That could use some clarification in the docs as well if you’d like.
Juan Mejías
@juanjuanmejias_twitter
Jan 24 21:57
OK, I'll edit it. How can I know my current autotuned values? If I run cat-autotune I get what I'm currently getting dosed?
Juan Mejías
@juanjuanmejias_twitter
Jan 24 22:19
@scottleibrand It's ready
Juan Mejías
@juanjuanmejias_twitter
Jan 24 23:31
Hi, maybe someone can give me hand. My rig is connected to Wi Fi, and radio seems to be working, but the OpenAPS pill hasn't refreshed for 33 mins now
It's coincided with switching on SMB for the first time. Don't know if it could be related somehow
I've checked the clocks and they seem to be in sync
image.png
I've also tried rebooting the rig, but it hasn't helped
Juan Mejías
@juanjuanmejias_twitter
Jan 24 23:36
The loop itself seems to be happening. This is from two minutes ago:
image.png
OK, I fixed it. When I edited preferences.json I introduced a typo and it was messing things up apparently
karlruhl
@karlruhl
Jan 24 23:42
Hi guys, am re-running oref setup and am getting the following error:
Using /home/.rootfs/usr/local/lib/python2.7/dist-packages
Finished processing dependencies for decocare==0.1.0-dev
/root/src/oref0/ already exists; pulling latest
error: object file .git/objects/85/bc323e35e84d28587f496253750d4139430f32 is empty
error: object file .git/objects/85/bc323e35e84d28587f496253750d4139430f32 is empty
fatal: loose object 85bc323e35e84d28587f496253750d4139430f32 (stored in .git/objects/85/bc323e35e84d28587f496253750d4139430f32) is corrupt
Couldn't pull latest oref0
aside from re-flashing the edison and trying again, not sure where to go from here!