You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/version/development.md
+6-2Lines changed: 6 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -22,9 +22,9 @@ There are no differences between `dev` and `main` at this time. However, there a
22
22
|:--|:--|:--|
23
23
| main | 3.8.2 | release |
24
24
| dev | 3.9.2 | identical to main except version number |
25
-
| feat/pod-keep-alive | 3.9.3 | - identical to 3.8.2 & 3.9.2 except uses the OmniBLE pod-keep-alive branch to support users of iPhone 16 phones with InPlay BLE (-Atlas) DASH pods<br>- should have maintained the 3.9.2 version number<br>- SHA for OmniBLE is `8c47404`|
25
+
|[feat/pod-keep-alive](#feature-branch-pod-keep-alive-feature)| 3.9.3 | - identical to 3.8.2 & 3.9.2 except uses the OmniBLE pod-keep-alive branch to support users of iPhone 16 phones with InPlay BLE (-Atlas) DASH pods<br>- should have maintained the 3.9.2 version number<br>- SHA for OmniBLE is `8c47404`|
26
26
| release/3.8.1 | 3.8.1 | - copy of the main release at version 3.8.1 that included Dana support<br>- this branch is meant to support people already using Dana with v3.8.1 who understand how to manage the issues with that version<br>- SHA for DanaKit is `3e606b8`|
27
-
| feat/dev-dana-medtrum | 3.9.1 | - identical to dev when it was at 3.9.1, with addition of experimental support for Dana and Medtrum pumps<br>- this branch will be updated as updates are available for DanaKit and MedtrumKit<br>- this branch has newer version of the Dana pump manager than release/3.8.1 but new bolus recording issues were observed with this update<br>- when an updated version of dev is merged into this branch, the version number will be similarly incremented<br>- SHA for DanaKit is `0875c1e`<br>- SHA for MedtrumKit is `a85496e`|
27
+
|[feat/dev-dana-medtrum](#feature-branch-medtrum-and-dana-support)| 3.9.1 | - identical to dev when it was at 3.9.1, with addition of experimental support for Dana and Medtrum pumps<br>- this branch will be updated as updates are available for DanaKit and MedtrumKit<br>- this branch has newer version of the Dana pump manager than release/3.8.1 but new bolus recording issues were observed with this update<br>- when an updated version of dev is merged into this branch, the version number will be similarly incremented<br>- SHA for DanaKit is `0875c1e`<br>- SHA for MedtrumKit is `a85496e`|
28
28
29
29
!!! question "What is SHA?"
30
30
SHA-1 means Secure Hash Algorithm 1. This is used to generate an alphanumeric code to identify which version of a repository is used.
@@ -58,6 +58,9 @@ For more information about using the `feat/pod-keep-alive` branch with an iPhone
58
58
59
59
### Feature Branch: Medtrum and Dana Support
60
60
61
+
!!! danger "Do Not Use in Closed Loop"
62
+
Users report that after a bolus finishes in Loop, the record of the bolus is removed from the event history.
63
+
61
64
!!! important "Experts Only"
62
65
Please only use the feat/dev-dana-medtrum branch if you are prepared to follow along in zulipchat and are willing to test an experimental branch that has known issues.
63
66
@@ -71,6 +74,7 @@ There are differences in the way Loop and Trio manage insulin delivery. An event
71
74
* an example of a mutable delivery is a bolus in progress or a temporary basal rate with a fixed duration that ends in the future
72
75
* Trio has its own method for dealing with doses that are initiated but might later change
73
76
* Both systems respond to reported reservoir values for pumps that allow a user to manually initiate insulin delivery on the pump, but the methods differ
77
+
* The interaction between reservoir level versus event history and the isMutable logic is probably what is causing the current Loop event history problem
0 commit comments