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

29th
Mar 2019
tynbendad
@tynbendad
Mar 29 00:07 UTC

anyone?

has anyone tried autotune_isf_adjustmentFraction on 0.6.2 master? it doesn't seem to do anything for me (tried values of 0.5, 1.0, 0.0)... the description in docs says "keeps autotune ISF closer to pump ISF via a weighted average of fullNewISF and pumpISF. 1.0" but that isn't happening. pump isf is 19, autotune isf was around 12 for all tested values of autotune_isf_adjustmentFraction.

Scott Leibrand
@scottleibrand
Mar 29 00:09 UTC
I don't even remember what that preference value was supposed to do.
tynbendad
@tynbendad
Mar 29 00:14 UTC
lol, i just ran across it, looking for something that did what doc said.
maybe it doesn't affect the autotune output, but how the autotune output is used later?..
Scott Leibrand
@scottleibrand
Mar 29 00:18 UTC
or maybe it was deprecated and not removed from everywhere
one of them appears to be autotune
    // adjust the target ISF to be a weighted average of fullNewISF and pumpISF
    var adjustmentFraction;

    if (typeof(pumpProfile.autotune_isf_adjustmentFraction) !== 'undefined') {
        adjustmentFraction = pumpProfile.autotune_isf_adjustmentFraction;
    } else {
        adjustmentFraction = 1.0;
    }

    // low autosens ratio = high ISF
    var maxISF = pumpISF / autotuneMin;
    // high autosens ratio = low ISF
    var minISF = pumpISF / autotuneMax;
    if (typeof(pumpISF) !== 'undefined') {
        if ( fullNewISF < 0 ) {
            var adjustedISF = ISF;
        } else {
            var adjustedISF = adjustmentFraction*fullNewISF + (1-adjustmentFraction)*pumpISF;
        }
Scott Leibrand
@scottleibrand
Mar 29 00:29 UTC
pretty sure I put that in temporarily before we fixed something, and it's no longer needed.
tynbendad
@tynbendad
Mar 29 00:30 UTC
i think its good... it looks like my autosens ratios and pumpisf may be limiting it:
p50deviation: 3.37 p50BGI -3.77 p50ratios: 0.325 Old ISF: 12.661 fullNewISF: 4.115 adjustedISF: 11.875 newISF: 12.504
holy cow, it wants to put isf at 4
that's not gonna work... glad the limits are there
Scott Leibrand
@scottleibrand
Mar 29 00:31 UTC
even without the autosense_(min|max) limits, it only applies 20% of the "full" changes
individual days' data is expected to be noisy
tynbendad
@tynbendad
Mar 29 00:32 UTC
lately isf has been going down each day, i thought 12 was too low (he's going hypo too much after eating, no bolus/announcements...) was trying to keep it up a bit.
Scott Leibrand
@scottleibrand
Mar 29 00:33 UTC
eating = CR, not ISF
oh, sorry, fully unannounced?
tynbendad
@tynbendad
Mar 29 00:33 UTC
yes
scottleibrand @scottleibrand pays attention to who he's talking to :)
tynbendad
@tynbendad
Mar 29 00:33 UTC
lol
we're on the full aps
Scott Leibrand
@scottleibrand
Mar 29 00:34 UTC
yeah, he's anonymously famous. ;-)
tynbendad
@tynbendad
Mar 29 00:34 UTC
fiasp is still working for him, his insulin usage shot up and then back down recently
must have been hormonal
Scott Leibrand
@scottleibrand
Mar 29 00:35 UTC
anyway, I'm honestly not sure whether autotune has any biases that would affect convergence in the fully-UAM case
if you need to set the pump ISF higher to limit downward pressure on ISF, go for it
tynbendad
@tynbendad
Mar 29 00:36 UTC
yeah, that looks like the way to go - glad i looked though,, didn't realize it was so far off.
or i could adjust autosense ratios, but i'd prefer one thing not affecting the other (separate factors would be better).
Scott Leibrand
@scottleibrand
Mar 29 00:39 UTC
If you just set pump ISF 20% above the desired lower limit that should work.
tynbendad
@tynbendad
Mar 29 00:39 UTC
its at 19 now, so already 20% above
Scott Leibrand
@scottleibrand
Mar 29 00:40 UTC
Hmm, is it not being refreshed then?
Check your pumpprofile
I’m assuming you have the default 1.2 for autosens_max
tynbendad
@tynbendad
Mar 29 00:41 UTC
oh no... no defaults ;)
Parameter      | Pump     | Autotune
-------------------------------------
ISF [mg/dL/U]  | 19.000   | 12.109
        "autosens_max": 1.6,
        "autosens_min": 0.4,
Scott Leibrand
@scottleibrand
Mar 29 00:41 UTC
Well, ok, then 60% above
tynbendad
@tynbendad
Mar 29 00:41 UTC
ok, got it - 19 / 1.6 = 11.875
thanks!
Scott Leibrand
@scottleibrand
Mar 29 00:42 UTC
Ya
tynbendad
@tynbendad
Mar 29 00:44 UTC
hah, the log even has that:
Limiting adjusted ISF of 3.21 to 11.88 (which is pump ISF of 19 / 1.6 )
doh
i recently 'tightened' the autosens ratios so that must have helped stem the isf flow a bit. but did not realize this was an issue before now.
tynbendad
@tynbendad
Mar 29 00:50 UTC

it wasn't an issue in december, but his ratios have changed so much since then...

p50deviation: -2.35 p50BGI -2.35 p50ratios: 2.263 Old ISF: 46.5 fullNewISF: 105.23 adjustedISF: 105.23 newISF: 58.246

actually that is similar issue there, but other direction isn't it?
going to look thru more old logs to make sure i don't have to revisit this every day...
lol, ok i see what you mean by individual days' data being noisy...
root@benaps2:~/myopenaps/autotune# gunzip -c autotune.2019-01-01*.log.gz |grep p50deviation
p50deviation: -2.47 p50BGI -4.54 p50ratios: 1.757 Old ISF: 58.246 fullNewISF: 102.338 adjustedISF: 102.338 newISF: 67.064
root@benaps2:~/myopenaps/autotune# gunzip -c autotune.2019-01-02*.log.gz |grep p50deviation
p50deviation: 2.07 p50BGI -3.52 p50ratios: 1.076 Old ISF: 67.064 fullNewISF: 72.161 adjustedISF: 72.161 newISF: 68.083
root@benaps2:~/myopenaps/autotune# gunzip -c autotune.2019-01-03*.log.gz |grep p50deviation
p50deviation: 5.43 p50BGI -5.07 p50ratios: 0.071 Old ISF: 68.083 fullNewISF: 4.834 adjustedISF: 21.053 newISF: 58.677
root@benaps2:~/myopenaps/autotune# gunzip -c autotune.2019-01-04*.log.gz |grep p50deviation
p50deviation: -0.115 p50BGI -4.415 p50ratios: 1.053 Old ISF: 58.677 fullNewISF: 61.787 adjustedISF: 61.787 newISF: 59.299
root@benaps2:~/myopenaps/autotune# gunzip -c autotune.2019-01-05*.log.gz |grep p50deviation
p50deviation: 14.76 p50BGI -15.015 p50ratios: 0.061 Old ISF: 59.299 fullNewISF: 3.617 adjustedISF: 21.053 newISF: 51.65
tynbendad
@tynbendad
Mar 29 01:08 UTC
ugh... now i'm wondering if i shouldn't just lower pump isf to let autotune continue to lower it, its always been right in the past. looks like we started hitting the pumpisf/autosens limit a month ago.
i'll lower it slowly, bet its right again.
tynbendad
@tynbendad
Mar 29 01:15 UTC
one thing that might help is if we put the autosens-factored limits right into the table at the end of the autotune output (or the recommendations log) so that its obvious we're bumping into the limit.
think i've changed it at least 3 times since january
not sure how i figured it out the last times, my personal memory appears to have been deleted ;)
WeedsDIY
@WeedsDIY
Mar 29 02:00 UTC
image.png
Attempting to flash radio chip on explorer board and getting this error. Does anyone know what "CC1110" is and why this would return "unsupported chip"?
tynbendad
@tynbendad
Mar 29 02:49 UTC
@WeedsDIY try rebooting? are you sure you followed the right set of commands for the board type you have (hat vs edison)
also someone just helped me clean an explorer board to get it flashable again.
WeedsDIY
@WeedsDIY
Mar 29 03:13 UTC
@tynbendad Very certain I followed edison/explorer instructs. Board was freshly rebooted when I started this command string, but I can try again.
Martin Haeberli
@mhaeberli
Mar 29 04:03 UTC
trying to flash edison with jubilinux 0.3.0 but always getting Timed out while waiting for dfu device 8087:0a99
Martin Haeberli
@mhaeberli
Mar 29 04:32 UTC
problem was one of the USB cables
Martin Haeberli
@mhaeberli
Mar 29 05:30 UTC
ok - now I tried to do a fresh install on jubilinux-0.3.0 and I started to get errors like this during setup:
…
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 npm : Depends: nodejs (>= 6.11~) but 4.8.2~dfsg-1 is to be installed
       Depends: node-abbrev (>= 1.1.1~) but 1.0.9-1 is to be installed
       Depends: node-ansi-regex (>= 3.0~) but 2.0.0-1 is to be installed
       Depends: node-cacache (>= 10.0.4~) but it is not going to be installed
       Depends: node-config-chain (>= 1.1.11~) but it is not going to be installed
       Depends: node-glob (>= 7.1.2~) but 7.1.1-1 is to be installed
       Depends: node-hosted-git-info (>= 2.6~) but 2.1.5-1 is to be installed
       Depends: node-ini (>= 1.3.5~) but 1.1.0-1 is to be installed
       Depends: node-npm-package-arg but it is not going to be installed
       Depends: node-jsonstream (>= 1.3.2~) but 1.0.3-4 is to be installed
       Depends: node-libnpx (>= 10.0.1~) but it is not going to be installed
       Depends: node-lockfile (>= 1.0.3~) but 0.4.1-1 is to be installed
       Depends: node-lru-cache (>= 4.1.1~) but 4.0.2-1 is to be installed
       Depends: node-move-concurrently (>= 1.0.1~) but it is not going to be installed
       Depends: node-normalize-package-data (>= 2.4~) but 2.3.5-2 is to be installed
       Depends: node-gyp (>= 3.6.2~) but 3.4.0-1 is to be installed
       Depends: node-resolve-from (>= 4.0~) but 2.0.0-1 is to be installed
       Depends: node-npmlog (>= 4.1.2~) but 0.0.4-1 is to be installed
       Depends: node-osenv (>= 0.1.5~) but 0.1.0-1 is to be installed
       Depends: node-read-package-json (>= 2.0.13~) but 1.2.4-1 is to be installed
       Depends: node-request (>= 2.83~) but 2.26.1-1 is to be installed
       Depends: node-retry (>= 0.10.1~) but 0.6.0-1 is to be installed
       Depends: node-rimraf (>= 2.6.2~) but 2.5.4-2 is to be installed
       Depends: node-semver (>= 5.5~) but 5.3.0-1 is to be installed
       Depends: node-sha (>= 2.0.1~) but 1.2.3-1 is to be installed
       Depends: node-slide (>= 1.1.6~) but 1.1.4-1 is to be installed
       Depends: node-strip-ansi (>= 4.0~) but 3.0.1-1 is to be installed
       Depends: node-tar (>= 4.4~) but 2.2.1-1 is to be installed
       Depends: node-boxen (>= 1.2.1~) but it is not going to be installed
       Depends: node-latest-version (>= 3.0~) but it is not going to be installed
       Depends: node-which (>= 1.3~) but 1.2.11-1 is to be installed
E: Unable to correct problems, you have held broken packages.
…
pepecb
@pepecb
Mar 29 10:19 UTC
About to buy a new battery for the explorer/edison combo. According to the website "The output ranges from 4.2V when completely charged to 3.7V. This battery has a capacity of 2400mAh for a total of about 9 Wh" See link: https://www.m.nu/batterier/lithium-ion-polymer-battery-37v-2400mah. OK to use this battery?
They also have a bigger battery Lithium Ion Battery Pack - 3.7V 6600mAh (https://www.m.nu/batterier/lithium-ion-battery-pack-37v-6600mah) Would this one work as well?
Riko L
@Ricco555
Mar 29 10:39 UTC

@WeedsDIY

Attempting to flash radio chip on explorer board and getting this error. Does anyone know what "CC1110" is and why this would return "unsupported chip"?

I have Explorer Board that gives above error. And unfortunately I had no success in making it alive again. The standard ccprog would not allow programing the chip if it does not recognize it. What you can try is the ccprog from https://github.com/eupakhomov/ccprog where this control has been disabled so it would allow to program anyway. For me it didn't help but some had success.

what did make you do the reflash? errors in communication with the radio?
Jon Cluck
@cluckj
Mar 29 12:03 UTC
@mhaeberli you need to use the dev bootstrap/install scripts
WeedsDIY
@WeedsDIY
Mar 29 12:11 UTC
@Riko L Thanks for the link. I'll give that a try. Yes, radio chip issues. At first, deteriorating intermittent looping. Then a persistent "Can't find subg_rfspy" error after checking edison connection, etc in docs. Sadly, this is occurring on a brand new board only used 2 weeks.
Jon Cluck
@cluckj
Mar 29 12:12 UTC
@WeedsDIY did you try some of the hardware troubleshooting like reseating the edison board, etc.?
Ebgineer
@Ebgineer
Mar 29 12:41 UTC
@pepecb Those batteries look fine. The larger one will power the rig longer, with the tradeoff of larger size.
Riko L
@Ricco555
Mar 29 13:03 UTC
@WeedsDIY mine was working for 1,5 months before the same issues. Still I am trying to resurrect it, not sure if it is the comm chip issue or the SPI problem. programming solves only Comm chip issue. AFAIK no solution exists if it is SPI problem. Currently Edison works on a new Board (so at least it is no Edison issue).
Riko L
@Ricco555
Mar 29 13:12 UTC

Can someone explain in practical terms what these parameters effects are:

  "high_temptarget_raises_sensitivity": false,
  "low_temptarget_lowers_sensitivity": false,
  "sensitivity_raises_target": true,
  "resistance_lowers_target": false,
  "adv_target_adjustments": false,

We are experiencing some strange behavior in the last few days. Could be multiple issues but I think it revolves around ISF so I am trying to figure out what a heck is going on. I'll upload few consecutive images to visualize. Basically, openaps rapidly issued SMBs and the result was rapid drop of BG to all times low.

2019-03-29_Microbolus_spam-0847.jpg
2019-03-29_Microbolus_spam-0920.jpg
2019-03-29_Microbolus_spam.jpg
Riko L
@Ricco555
Mar 29 13:19 UTC
There is not much that we changed lately only parameters revolving around autotune. Namely, basal rates, ISF and CR. parameters in preferences.json did not touch.
ISF we want to push around 20, but it keeps droping to 8ish in the morning. I am right now checking through all outputs and trying to analyze the behavior in this period. But it takes time.
philipgo
@philipgo
Mar 29 13:36 UTC
@Ricco555 Which CGMsource do you use? You have massive jumps in your CGM values.
Riko L
@Ricco555
Mar 29 13:51 UTC
bluecon on top of libre sensor . recently we are having issues in that field as well.
but, we also have incredible rise and drops of sugar levels whatsoever.
philipgo
@philipgo
Mar 29 13:55 UTC
@Ricco555 Well at least the severe hypos may not have occured if Libre had been correct. Any chance you could get a Dexcom?
I suggest raising the target while figuring out all settings, 5 is pretty low. You could e.g. use 6,5 at day and 5.5 at night.
For Libre users using SMB after carbs/always is strongly discouraged, looks like you may have SMB after carbs activated
Riko L
@Ricco555
Mar 29 13:58 UTC

Will try that. in the mean time I've shut down the SMB feature and will gradually turn it back on.

For Libre users using SMB after carbs/always is strongly discouraged, looks like you may have SMB after carbs activated

this was turned on:

  "enableSMB_with_COB": true,
  "enableSMB_with_temptarget": true,
  "enableSMB_always": false,
  "enableSMB_after_carbs": true,
  "allowSMB_with_high_temptarget": false,
philipgo
@philipgo
Mar 29 14:02 UTC
@Ricco555 I would set"enableSMB_after_carbs": false,and leave "enableSMB_with_COB": true, and raise targets at the same time. Then gradually reduce your meal time insulin bolus (start with full bolus as usual, then ca. 80% and so on).
Riko L
@Ricco555
Mar 29 14:11 UTC
thanks @philipgo will definitely use that. the second part we will also try but first have to prove that everything works as expected in certain scenarios and that there are no great highs and lows as a result of openaps involvement. Definitely need to fine tune things more.
Martin Haeberli
@mhaeberli
Mar 29 14:45 UTC
@cluckj thx
WeedsDIY
@WeedsDIY
Mar 29 15:09 UTC
@cluckj Yes, that list was the first fixes I tried. This is the 5th or 6th board I've had this recurrent issue with over the past year and a half, but I've been able to reflash them in the past. This one is behaving differently.
Martin Haeberli
@mhaeberli
Mar 29 20:51 UTC
@cluckj - so i’m trying to use the dev script vs the master, but I did not re - re- flash jubilinux - stretch onto the edison. so I’m still getting errors like
       Depends: node-tar (>= 4.4~) but 2.2.1-1 is to be installed
       Depends: node-boxen (>= 1.2.1~) but it is not going to be installed
       Depends: node-latest-version (>= 3.0~) but it is not going to be installed
       Depends: node-which (>= 1.3~) but 1.2.11-1 is to be installed
E: Unable to correct problems, you have held broken packages.
fresh install of nodejs now yields:
apt-get install nodejs
Reading package lists... Done
Building dependency tree       
Reading state information... Done
The following NEW packages will be installed:
  nodejs
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/3422 kB of archives.
After this operation, 13.5 MB of additional disk space will be used.
Selecting previously unselected package nodejs.
(Reading database ... 33495 files and directories currently installed.)
Preparing to unpack .../nodejs_4.8.2~dfsg-1_i386.deb ...
Unpacking nodejs (4.8.2~dfsg-1) ...
Setting up nodejs (4.8.2~dfsg-1) ...
update-alternatives: using /usr/bin/nodejs to provide /usr/bin/js (js) in auto mode
which I gather is the wrong version...
suggestions? or just flash Edison again
tynbendad
@tynbendad
Mar 29 20:54 UTC
@mhaeberli are you using jubilinux 0.3 for a reason? i'm still using jubilinux 0.1 ;)
Martin Haeberli
@mhaeberli
Mar 29 21:00 UTC
because 0.3 is under lts; apt-get update / upgrade on 0.2 now fails - thus following @cluckj s advice
on dev branch in any case
Jon Cluck
@cluckj
Mar 29 21:02 UTC
ah, you need to tell the install script to use dev or it defaults to master
Martin Haeberli
@mhaeberli
Mar 29 21:03 UTC
how?
this time, I pulled ‘dev’ install script blob. obviously, not enough
Jon Cluck
@cluckj
Mar 29 21:04 UTC
it's a command line option; run it like openaps-install.sh dev
Martin Haeberli
@mhaeberli
Mar 29 21:04 UTC
thx; does it matter if I use the ‘master’ or the ‘dev’ openaps-install.sh blob?
Jon Cluck
@cluckj
Mar 29 21:04 UTC
yes, only dev has the option to install dev
Martin Haeberli
@mhaeberli
Mar 29 21:05 UTC
ok thx
Jon Cluck
@cluckj
Mar 29 21:05 UTC
tynbendad
@tynbendad
Mar 29 21:54 UTC
oh yuck, does that mean if i try to install today it would fail?
Jon Cluck
@cluckj
Mar 29 22:04 UTC
yeah, master would need some magic to get working, but dev is okay
tynbendad
@tynbendad
Mar 29 22:05 UTC
oh that sucks, i love 0.6.2
and jubi 0.1
Jon Cluck
@cluckj
Mar 29 22:07 UTC
you can still use it :P
Jon Cluck
@cluckj
Mar 29 22:13 UTC
it's a little more DIY now that the package manager is a bit useless
Martin Haeberli
@mhaeberli
Mar 29 22:14 UTC
ok looks like 0.3.0 and dev are working thx to @cluckj advice
tynbendad
@tynbendad
Mar 29 22:14 UTC
how do you work around using package manager? install scripts will fail?
glad we still have a way to use edison at least
Jon Cluck
@cluckj
Mar 29 22:16 UTC
@mhaeberli great! :D
you can manually install things, or use backports if they're still available
tynbendad
@tynbendad
Mar 29 22:17 UTC
not sure i would know how to do that
guess i'll try to be really careful with the rigs i have ;)
Jon Cluck
@cluckj
Mar 29 22:17 UTC
yes :)