@dougboss I usually have to delete entries in Nightscout mongo database. I go to menu in nightscout then admin tools and use the button to delete all documents in the mongo section. It clears the corrupt data causing the graph not to display correctly. Give it a minute and things show up as expected.

Hi, for breakfast I tried the first time to use OpenAPS for meal. It happens that the eventual BG was 183 and target 130, but nevertheless insulin req was negative and the rig made low temping all the time after the meal. I also adjusted the preferences with bolussnooze dia divisor but still low temps.

For some reason the new setup script which i installed interactively did not ask if i want to use autosens, though i think it runs automatically cose i have autosens_min and autosens_max as variables [0,7;1,2] in my preferences.

@scottleibrand okay UAM is then better even when I enter carbs? Yes, in the very beginning after the meal bolus the purple prediction lines predicted to drop very low, but then settled at a normal level. For info: I entered carbs in NS.

Yes, UAM provides an alternate prediction independent of carb entry. When you do enter carbs, it uses both to make a better prediction of what’s going to happen than it can do with the COB based prediction alone.

It’s fairly common to see zero temping right after a full meal bolus: until it sees carb absorption, the algorithm assumes it might be slow to ramp up, which can result in a low before all the carbs absorb. So it’d rather zero temp initially and then give extra insulin as soon as it’s clear it’ll be needed.