Prep for eventual 0.6.0 dev to master release #694
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Number one error for beginners that blocks looping is when people don't have the pump set to absolute u/hr (in % basal type instead), which prevents the rig from being able to set temp basals.
* echo status * try preflight twice * check radio 10x, and mmtune if all checks fail * echo Preflight when starting it * mmtune 30% of the time * it's ok if refresh_profile or refresh_pumphistory_24h fail * Revert "check radio 10x, and mmtune if all checks fail" This reverts commit 6ea8637. * remove extra any_pump_comms debugging * removing duplicate 30s wait_for_silence before mmtune * show just last line of any_pump_comms 1 output when Radio check fails * check radio thrice * echo "Done waiting for rigs with better signal." * case-insensitive grep to match 'Comms with pump detected' too * print when preflight fails * retry radio check one more time * exponential backoff on Radio check * echo -n . when retrying Radio check * print any_pump_comms output when it doesn't succeed * ignore mmeowlink-any-pump-comms.py exit code and just check output * reduce debugging
…r zombie-carb safety
…ir-own' into 0.6.0-dev
* properly calculate minguardBG if COB==0 and UAM is off * properly calculate minguardBG if COB==0 and UAM is off * typo
Project remaining carb absorption time based on % carbs absorbed
* recalculate IOB and predBGs after refreshing everything * don't print determine-basal output * no need to refresh temp again or display suggested.json output * print new IOB from refreshed smb-suggested.json * no newline after Settings line
* remove extra minPredBG in rT object * remove extra minPredBG in rT object
* ignore last CR period if COB > 0 at midnight * allow slightly positive avgDeltas to contribute to ISF to remove upward bias * capture 12h more for UTC-dated treatments * downgrade API_SECRET check to a warning, as readable sites work w/o it * cap ISF and CR before adjusting, not just after * debugging * don't recategorize ISF as basal if BGI > 0 and ISF < 0 * use avgDeltas up to -2*BGI for ISF * allow full autotune ISF adjustment now that safety caps fully apply * apply 20% of ISF adjustment now * remove CSF now that it's not used for anything * comment out unused code * only use CSF data if UAM data is insufficient * ignore negative ISFs * only use CSF data for ISF if ISFLength < 10
* randomize wait_for_silence before smb_verify_reservoir * typo
* use lastCarbAge instead of fractionCOBAbsorbed to calculate remainingCATime * set lastCarbTime based on the max treatmentTime * remainingCATimeMax is now unused
* add an enableSMB_always option * disable SMB on really big jumps for safety * add SMB disabled to reason field if delta > 10% of bg
* look ahead an additional 15m to get insulin started faster * ramp up remainingCATime 1.5x as fast as lastCarbAge
5 tasks
* use curl instead of wget --no-check-certificate * use the version of openaps-install.sh in oref0 master
* don't run pump-loop if rig is too hot * print error messages for overtemp * temp threshold 80C * fix comment * truncate ns-loop if rig is too hot * use 85°C
Attempting to --nogit by default for existing user installs
* blend minCOBGuardBG and minUAMGuardBG according to fractionCarbsLeft * round(minGuardBG) * only use minUAMPredBG not avgMinPredBG * debugging output
* rm smb-suggested.json after pushover to avoid dupes * require enact/smb-suggested.json be <5m old instead
|
Just updated to #694. I see "exercise mode" in preferences, but I didn't see that mentioned in the notes above. Also, I didn't see a SMB always on mode in preferences. For that do you add a new line to preferences.json? Also I haven't been using pushover alerts from the rig bc I want to be able to set a minimum amount for carbs needed. Is that still an option? Thanks! I LOVE eSMB and the insulin curves! |
Contributor
Author
|
@kcrcgm (and all) please see the currently open PR to dev which is now #707. Sorry for the moving cheese. There's notes in that one about the changes in activity mode. And yes, you'll need to manually add SMB always on if you want it. Ditto for customizing carbsReq amounts, you'll manually add that as well. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Note: this next release will be a big release (from 0.5.5 to 0.6.0 to match the significant changes).
WARNING: This code is highly experimental and has many changes compared to 0.5.5. Do not implement this branch for testing unless you review the diff and plan to watch it closely. Also, do not change behaviors until you test the defaults of this branch. There may be some things not yet documented here that need to be documented; please comment on this thread or in channel to help note what needs documenting. Make sure you follow this PR so you will get notifications about changes to this branch. It is still changing feature-wise, so you will want to update as new features and bug fixes are added in.
See the bottom-most comment for how to install and run 0.6.0.
CHANGED: Default behavior change for carb absorption
In 0.6.0, carb absorption now uses a
/\shaped bilinear carb absorption model (replacing the previous---shaped constant model for predicting the future absorption of newly entered carbs that haven't shown any effect on BG yet. As a result, the COB predBG purple prediction line immediately after entering carbs shows an S-curve shaped rise that starts out flat (in line with current BG trends), and then rises sharply after about an hour before flattening out.Exponential Curves
The code now supports three new configuration variables in preferences.json to allow exponential curves that better reflect the effects of insulin:
if left blank or set to "bilinear", OpenAPS uses the old insulin activity model
If set to "ultra-rapid", the new curve model analyzed from publicly available data for Fiasp from Novo Nordisk is used, set to reach activity peak at 55 minutes
If set to "rapid-acting", the new curve model analyzed from publicly available data for Novorapid (Novolog) from Novo Nordisk is used. This curve should match well to Novorapid, Novolog, Humalog and Apidra and is set to peak at 75 minutes
In order to use the rapid-acting or ultra-rapid curves, your pump must be set to 5 hour DIA, or longer. 6 hours is recommended as the starting point.
The details of the curve calculations and discussions can be found PR #568
Enhanced SMB (eSMB)
Note: for folks with tiny basals (in this case, say <0.5u/hr), exercise even more caution, as additional tweaks may need to be made to SMB-related portions of the code.
The default behaviour for SMB is that the max bolus that can be delivered is no greater than 30 mins of basal insulin. An additional preferences value, "maxSMBBasalMinutes", has been added to allow SMB to deliver a different amount of insulin as an SMB. This gives the ability to make SMB more aggressive if you choose. As with standard SMB, it is triggered by temp targets, carb entries and a pump bolus.
Increasing "maxSMBBasalMinutes" will allow the SMB functionality to deliver more insulin, earlier in the SMB process.
"maxSMBBasalMinutes" can be added into
myopenaps/preferences.json. It is recommended that the value is set to start at 30, in line with the default, and if you choose to increase this value, do so in no more than 15 minute increments, keeping a close eye on the effects of the changes.It is not recommended to set this value higher than 90 mins, as this may affect the ability for the algorithm to safely zero temp. It is also recommended that pushover is used when setting the value to be greater than default, so that alerts are generated for any predicted lows or highs.
Other SMB adjustments include: The preference of enabling SMB to always be on. (Leaving this as false (off) means the existing SMB toggles for carbs, temp targets, etc. will be what drives SMB behaviors.)
Autotune adjustments
Autotune now tunes carb ratio directly, eliminating the previously known upward bias on ISF and carb ratio. This also smooths out mealtime basals based on surrounding hours when there's no data for tuning a particular hour due to meals.
Behavior change recommended as a result: You should be logging rescue carbs (carbs eaten for lows or predicted lows) so that Autotune knows about them. (Rescue carbs can be entered into Nightscout directly (i.e. NS website care portal, IFTTT buttons, etc.) or via the pump as long as they are accompanied by a 0.1 bolus. Any carb entry on the pump without a bolus is ignored by OpenAPS).
Troubleshooting
preferences.json- if you get "Could not parse input data: {SyntaxError: Unexpected end of input]" or similar input error, double checkpreferences.jsonHow to install 0.6.0
0.6.0 also has support for no-git-based-flow, to reduce git-related errors for most users. This is now the default path.
Follow the dev instructions in the docs: http://openaps.readthedocs.io/en/latest/docs/Customize-Iterate/update-your-rig.html
As always, after an update/runagain, you'll also want to go in and edit your preferences as well. Check the code diff here to see what the optional preferences are for 0.6.0 - they are not in the main docs yet.
Testing list before release
Release checklist