In the 2/3 days i've been looping, i've been using 29% less basal insulin. Which is great because too much plasma insulin is just almost as bad for health as high glucose levels. Anyone else using less insulin?

I'm stepping through the walkthrough in the docs, and trying to be diligent about following each step and understanding what it does. But I'm wrestling with the mixed use of what seems to be newer and older ways of doing things, which sometimes clash. In particular, there's a note at the start of 'phase-2/Using-oref0-tools.html' that says "Here are some of the newer reports copied from the newer style walkthrough" which then gives some oref0 commands to create reports and devices (but then also says that they are inconsistent with the rest of the walkthrough). Is this "newer style walkthrough" available somewhere? If not, any suggestions about what path to follow through the docs?

if you’re looking on github, there’s a link at the top of the nav of the outline in the readme that links to it, but the readme needs a PR to reflect the flow as outlined in the RTD version (auto generated)

@danamlewis Thanks, but I don't quite follow. I see the "guide to understanding openaps" link (and I am indeed in readthedocs). It looks like that set of links explains a bunch of things nicely. But is one not supposed to go on to the Walkthrough section after that? Since there is no 'next' link at the bottom of any of the doc pages I've been using the left-hand Navigation bar to try to figure out where to go next.

yes. the context is, there used to not be that “understanding” guide to help you get introduced to the toolset (openaps). Ben added that guide, and moved it to the top because it seemed to help people get their brain wrapped around the toolkit before they started applying it to building an implementation (which is what the walkthrough docs are).

Whether using RTD or using github, I usually keep a tab open with the highest level outline/TOC (in github, it’s the readme page) and use that to help me navigate in another tab as I move through, so I can see which section I’m in and how it relates to the overall flow.

Cool. I feel like I totally get openaps. But mixed in with the openaps stuff (pretty early on in the walkthrough) is some oref0 stuff that is much more cryptic. For example, in the middle of the pretty gentle walkthrough of adding devices, in Phase 1, are these two lines that kind of come out of nowhere:

(Yea. We’re getting to the point where there’s been a bunch of adds to the docs, but no one has taken the time to do a start to finish run through recently with a new rig setup and flag where there’s any jarring points from new adds that need smoothing. So if you could PR clarifications, or file an issue to make note of them so someone else could tackle, that would be great!)

So that's the kind of things that's hanging me up. Not sure whether I should be skipping the oref0 stuff that comes early on (well before oref0 is even mentioned) - but once I start skipping things, it gets a little tricky to figure out what to keep in and leave out...

OK, perfect. Not trying to be hypercritical here at all - just wanting to figure out if I'm missing something particular. I've done a few PRs to fix trivial things in the docs, but there are some higher-level organizational issues that I'm not sure what to do about.

you can also click in the bottom right corner of RTD and see there’s different date versions, and see if an earlier version of the docs is more helpful to you.. some people have preferred that. but generally, if you find it jarring, others will too, and it’s worth flagging in a place where it can get tracked & followed up on. Here is good for asking a Q, but it’s super helpful to the community to submit a PR to fix or log an issue

no worries. and not just saying this to you - saying this to everyone who’s got fresh eyes looking at the docs.

danamlewis @danamlewis encourages everyone to submit PRs or flag issues at any time, don’t wait until you’re done with your setup, otherwise you won’t remember what was confusing at various points in the docs.

@daveewall k. Sounds like you might want to look at whether your carb ratio is too high to start with. If you could adjust the carb ratio on the pump, but continue to give the same size meal bolus, AMA will be less inclined to low temp, and should even high temp somewhat to help out. Or, if you rarely see lows after meals, you could also do the higher boluses as well: then low-temping would be just as likely, but the extra bolus insulin would help prevent meal spikes.

You should also be able to look at net BG rise after meals, and whether additional insulin is usually required to correct, to get an estimate of whether your carb ratio is too high.

If it turns out your carb ratio is accurate and it's just a timing thing, you could also look at slowing the bolus snooze time back down to what it was in master (DIA/2 instead of DIA/4 IIRC). @jasoncalabrese was exploring that for similar symptoms, and found it helped. You'll want to make sure your carb ratio is well tuned first though, as otherwise bolus snooze is just a bandaid.

@bewest@scottleibrand Those report changes we made yesterday got our IOB numbers back into the believable range. Success! Are the nightscout reports for IOB a valuable way to test those values? The data looks a bit erratic.