diff --git a/docs/CROWDIN/cs/Getting-Started/Introduction.md b/docs/CROWDIN/cs/Getting-Started/Introduction.md index 363ed729cd4e..16ccd87c3319 100644 --- a/docs/CROWDIN/cs/Getting-Started/Introduction.md +++ b/docs/CROWDIN/cs/Getting-Started/Introduction.md @@ -192,7 +192,7 @@ Pokud by došlo k útoku hackera na vaši inzulínovou pumpu, tato strategie mů #### Bezpečnostní hlediska týkající se příliš rychlého zlepšení kontroly glykémie -Rychlé snížení HbA1c a zlepšení kontroly glukózy v krvi zní přitažlivě. Nicméně _příliš rychlé_ snížení průměrné úrovně glykémie nastartiváním uzavřené smyčky může způsobit trvalá poškození, včetně poškození očí nebo bolestivé neuropatie, které se nikdy nezbavíte. Těmto rizikům je možné snadno předejít pomalejším snižováním úrovní. Pokud v současné době máte zvýšenou hodnotu HbA1c a začínáte se systémem AAPS (nebo jiným systémem uzavřené smyčky), prodiskutujte prosím toto riziko s Vaším lékařem před zahájením, a dohodněte se na časovém horizontu s postupným bezpečným snižováním cílů glykémie. More general information on how to reduce your glucose levels safely, including links to medical literature is given in the [safety section [here](#preparing-safety-first). +Rychlé snížení HbA1c a zlepšení kontroly glukózy v krvi zní přitažlivě. Nicméně _příliš rychlé_ snížení průměrné úrovně glykémie nastartiváním uzavřené smyčky může způsobit trvalá poškození, včetně poškození očí nebo bolestivé neuropatie, které se nikdy nezbavíte. Těmto rizikům je možné snadno předejít pomalejším snižováním úrovní. If you currently have an elevated HbA1c and are moving to AAPS (or any other closed loop system), please discuss this potential risk with your clinical team before starting, and agree a time plan with them. More general information on how to reduce your glucose levels safely, including links to medical literature is given in the safety section [here](#preparing-safety-first). #### Zdravotní bezpečnost zařízení, spotřebního materiálu a jiných léků diff --git a/docs/CROWDIN/cs/GettingHelp/ProfileTuning.md b/docs/CROWDIN/cs/GettingHelp/ProfileTuning.md new file mode 100644 index 000000000000..566fc5f5c43b --- /dev/null +++ b/docs/CROWDIN/cs/GettingHelp/ProfileTuning.md @@ -0,0 +1,136 @@ +# **Tweaking the AAPS' Profile** + +```{admonition} This is NOT a medical advice +:class: warning +Please work with your care team for support and advice on your diabetes management.
+Use this guide only once you have [set up your **Profile** correctly](https://androidaps.readthedocs.io/en/latest/SettingUpAaps/YourAapsProfile.md), following all **AAPS** objectives. +``` + +This guide explains the logic of the OpenAPS algorithm results with a given __Profile__, and provides information about which values to adjust when certain situations are observed. The suggestions about basal testing below may diverge from what your care team advises + +Using **closed loop** may make basal testing easier and may significantly reduce the hypo risk if your __Profile__ basal is too strong. + +## **Changing profile's settings, how to proceed** + +1. Ensure you have read and understand __AAPS’__ recommended settings and advice below. Not following this advice will make the whole process problematic and less likely to get a well tuned __Profile__ +2. Carefully observe and compare, **over several days**, what is happening with your __BG__ and __IOB__. +3. Keep an eye out for patterns that happen around the same time (almost) everyday. +4. It's important to do this over several days. Poor results tend to be yielded from using data observed on a single day to make __Profile’s__ adjustment decisions. +5. After you have observed a repeatable pattern of behavior, e.g. at 1PM you see a spike in __BG__ or a negative __IOB__ value, only then start to make small changes to your __Profile__. +6. It's important to limit the changes you make to one thing at a time. E.g. increase your basal by 10% around 1PM. +7. After every change, it's important to monitor the impact on your __BG__ and __IOB__ for the next few days. +8. Repeat this pattern, observe, decide, tweak again if needed + +Don't rush, go slow! + +## **Recommended settings and advice while tweaking basal** + +- Do all testing with [closed loop enabled](#AapsScreens-loop-status). +- **Turn OFF all [automations](../DailyLifeWithAAPS/Automations.md)** +- **Turn OFF [DynISF](#Open-APS-features-DynamicISF), [AutoISF](../AdvancedOptions/DevBranch.md), [AutoSens](#Open-APS-features-autosens)** so that they will not try to adapt your profile. +- Do not make manual user actions (manual bolus, temp targets etc…) while testing: let the system use the **Profile** settings only. +- For the [additional graphs](#AapsScreens-section-g-additional-graphs): on graph 1, use Insulin On Board, Carbs On Board (and Sensitivity change). On graph 2, use Deviations and Blood Glucose Impact. When asking for advice, always include those on your screenshots. +- COB=0[*](#profiletuning-cob-zero) +- No physical activities. +- No stress. +- No illness. +- No extreme weather like high or low temperatures. +- If your [basal rate profile](#your-aaps-profile-basal-rates) is correct, when you are on target with COB=0[*](#profiletuning-cob-zero) and IOB=0, you will remain constantly on target whatever your ISF (ISF is only used when you are higher than your target). +- You need to check the actual IOB but also, the IOB chart to see how the IOB was during the past few hours. + +(profiletuning-cob-zero)= + +***COB = 0** + +Meaning that the meal is digested, and there are no more carbs in your body. + +AAPS might indicate [COB=0 while you still have carbs on board](../DailyLifeWithAAPS/CobCalculation.md). + +## **[Profile](../SettingUpAaps/YourAapsProfile.md) definitions** + +A too **strong Profile** indicates some combination of the following: + +- [ISF](#insulin-sensitivity-factor-isf) number is too small +- The [basal](#basal-rates) number is too big +- [I:C](#insulin-to-carb-ratio-icr) number is too small + +## **IOB Observations** + +*Note: you can also use Loopalyzer IOB graph in Nightscout reports to view IOB on several days.* + +If you observe the following patterns after a few days, consider the following changes + +### **IOB positive** + +- **Profile** basal might not be strong enough (this could also be because of things like unannounced food, illness, bad site absorption, etc.) + +![Positive IOB](../images/troubleshooting/profiletuning/PositiveInsulin.png) + +### **IOB negative** + +- Default basal too strong +- May be the effect from past exercise/physical activity + +![Negative IOB](../images/troubleshooting/profiletuning/NegativeInsulin.png) + +- Previous meal: too much bolus (which resulted in a very long zero temp basal) + +![Negative IOB](../images/troubleshooting/profiletuning/NegativeInsulin2.png) + +## **BG Target Observations** + +### **Stuck High** + +- __ISF__ ‘s number is high and not strong enough (calculated insulin is too weak) + +![Stuck High](../images/troubleshooting/profiletuning/StuckHigh.png) + +- __Profile__ basal might not be strong enough (SMBs do not have enough "basal stock" to use) +- A security ([MaxIOB](#Open-APS-features-maximum-total-iob-openaps-cant-go-over)?) might have kicked in and is limiting insulin injection. Verify in the [SMB](#Open-APS-features-super-micro-bolus-smb) tab. +- Technical issue: site absorption, infusion set, ... + +### **Stuck Low** + +- __ISF__ too strong and the number needs to be raised higher +- __Profile__ basal too strong (if also negative IOB) + +### **Rollercoaster (ups and downs)** + +- **ISF** too strong? See your [AAPS Profile](#your-aaps-profile-insulin-sensitivity-factor) + +![Rollercoaster](../images/troubleshooting/profiletuning/StrongISF.png) + +## **BG After Meals Observations** + +### **Fast rise and BG going high** + +- Food contains fast carbs +- Consider doing a pre-bolus +- Bolus (IC or injected %) not strong enough + +![Rise High](../images/troubleshooting/profiletuning/FastRise.png) + +### **Fast rise and then BG going low** + +- Consider doing a pre-bolus, profile might be too aggressive (over correction of the raise) +- Bolus too strong + + + +## **[How to calculate your I:C](#your-aaps-profile-insulin-to-carbs-ratio)** + +1. First, you need the correct default basal settings in your **Profile**. +2. Start on target, better without negative IOB. +3. Record the total insulin given in the pump tab (or pump history) and call it Start insulin C4. Very accurately measure a known portion of carbs, and record the start time and Start IOB. Then enter carbs and bolus information into AAPS using the wizard (with the current configured CI). Don't forget to eat the carbs ;) +4. After some hours, when COB=0[*](#profiletuning-cob-zero) and you're back on target, record end time, and note down the End IOB, check the total insulin given as before and call it End insulin. *NOTE: The time frame is NOT important, as long as it is longer than your digestion* +5. From the difference between Start and End insulin amount, subtract/add the difference end IOB - start IOB. Then subtract the basal insulin calculated from your profile settings. +6. If __BG__ is in target, you'll have the total insulin used to “digest” your carbs. Calculate your **I:C**. + +### **Explanations for the I:C calculations** + +- With a **Profile** that has the correct default basal rate, during any time frame, you should stay on target and have an IOB near 0. You get your **Profile** basal only. +- You add carbs and bolus to this mix. Wait till your body digests all the carbs and be back on **BG** target. Your insulin usage will be the sum of your basal + the insulin needed for the carbs. You calculate the insulin used for your basal (by using your **Profile**) and the surplus will be the insulin used to digest the carbs. +- If the time frame is too short, there will be carbs undigested, thus your "insulin needed for the carbs" will be wrong. +- If the time frame is too long, nothing bad will happen. You'll use all your carbs and you'll get more basal. At the end, you'll subtract the basal from the total insulin used, the extended time frame (with more basal use) will not affect the result. + +Originally written up by @Robby (Discord) on tips and tricks to help tune your AAPS Profile, reviewed and edited by the community (thank you!). diff --git a/docs/CROWDIN/cs/SettingUpAaps/ComputerBuild.md b/docs/CROWDIN/cs/SettingUpAaps/ComputerBuild.md index 6212751c0845..cf092f280940 100644 --- a/docs/CROWDIN/cs/SettingUpAaps/ComputerBuild.md +++ b/docs/CROWDIN/cs/SettingUpAaps/ComputerBuild.md @@ -70,7 +70,7 @@ The Gradle version is linked to the source code, you will always get the correct ## Pomoc a podpora během procesu sestavení -If you run into difficulties in the process of building the **AAPS** app, there is a dedicated [**troubleshooting Android Studio**](../GettingHelp/TroubleshootingAndroidStudio) section, please consult that first. +If you run into difficulties in the process of building the **AAPS** app, there is a dedicated [**troubleshooting Android Studio**](../GettingHelp/TroubleshootingAndroidStudio.md) section, please consult that first. If you think something in the building instructions is wrong, missing or confusing, or you are still struggling, please reach out to other **AAPS** users group on [Facebook](https://www.facebook.com/groups/AndroidAPSUsers) or [Discord](https://discord.gg/4fQUWHZ4Mw). If you want to change something yourself (updating screenshots _etc_), please submit a [pull request (PR)](../SupportingAaps/HowToEditTheDocs.md). @@ -409,7 +409,7 @@ Po dokončení sestavení aplikace zobrazí Android Studio informaci "BUILD SUCC ![Build finished](../images/Building-the-App/049_ReopenNotification.png) -**_If the build was not successful, refer to the [Android Studio Troubleshooting section](../GettingHelp/TroubleshootingAndroidStudio)._** +**_If the build was not successful, refer to the [Android Studio Troubleshooting section](../GettingHelp/TroubleshootingAndroidStudio.md)._** V oznámení klikněte na modrý odkaz "locate": diff --git a/docs/CROWDIN/cs/SettingUpAaps/Preferences.md b/docs/CROWDIN/cs/SettingUpAaps/Preferences.md index 116e9d506265..d308cd8dd9bf 100644 --- a/docs/CROWDIN/cs/SettingUpAaps/Preferences.md +++ b/docs/CROWDIN/cs/SettingUpAaps/Preferences.md @@ -300,7 +300,7 @@ Switch between Open Loop, Closed Loop and Low Glucose Suspend (LGS). ![Config builder - loop mode](../images/ConfigBuilder_LoopLGS.png) -(Preferences-pen-loop)= +(Preferences-open-loop)= #### Open Loop **AAPS** continuously evaluates all available data (IOB, COB, BG...) and makes treatment suggestions (temporary basal rates) on how to adjust your therapy if necessary. diff --git a/docs/CROWDIN/cs/SettingUpAaps/YourAapsProfile.md b/docs/CROWDIN/cs/SettingUpAaps/YourAapsProfile.md index de1a5f705244..81084ab98a93 100644 --- a/docs/CROWDIN/cs/SettingUpAaps/YourAapsProfile.md +++ b/docs/CROWDIN/cs/SettingUpAaps/YourAapsProfile.md @@ -123,11 +123,13 @@ The **figure below** shows an example of how the basal rates can be set in an ** Setting your basal rates right is done by trial and error, and should be done in consultation with your diabetic team. -There are basal testing methods which usually entails observing your basal rates and insulin needs during an intermittent fasting over a 24-hour period. Although you need to test your basal rates for the whole day, it is not recommended to fast during 24h straight. This is because the body triggers mechanisms such as hormones to compensate. A recommended way is to fast 3 times for 8 hours. +There are basal testing methods which usually entails observing your basal rates and insulin needs during an intermittent fasting over a 24-hour period. Although you need to test your basal rates for the whole day, it is not recommended to fast during 24h straight. This is because the body triggers mechanisms such as hormones to compensate. A recommended way is to fast 3 times for 8 hours. -The recommended method is to suspend the loop, which will revert to your default background basal rate. Observe how your **BG** changes: if it is dropping, basal rate is too high. And vice versa.
An alternative method (may be more tricky) is to keep the loop running, and seeing how **IOB** changes. If **IOB** is negative, your basal rate is too high. And vice versa. Beware that this method relies on **ISF** to correct **BG**, and thus depends on other variables to be set reasonably well for it to be successful.
Another way of adjusting your basal rates is to watch the loop action during the night, when all COB have decayed. This method is particularly useful for children, when fasting is difficult or insulin needs change often. [Dr Saleh Adi from Tidepool](https://www.youtube.com/watch?v=-fpWnGRhLSo) provides useful ways on how to analyse overnight BG lines in order to optimise your basal rates. +The recommended method is to suspend the loop (for safety you can set AAPS to [**LGS**](#Preferences-aps-mode) to avoid lows, as done for achieving [objective 6](#objectives-objective6)), which will revert to your default background basal rate. Observe how your **BG** changes: if it is dropping, basal rate is too high. And vice versa.
An alternative method (may be more tricky) is to keep the loop running, and seeing how **IOB** changes. If **IOB** is negative, your basal rate is too high. And vice versa. Beware that this method relies on **ISF** to correct **BG**, and thus depends on other variables to be set reasonably well for it to be successful.
Another way of adjusting your basal rates is to watch the loop action during the night, when all COB have decayed. This method is particularly useful for children, when fasting is difficult or insulin needs change often. [Dr Saleh Adi from Tidepool](https://www.youtube.com/watch?v=-fpWnGRhLSo) provides useful ways on how to analyze overnight BG lines in order to optimize your basal rates. -When taking action on the result of your basal testing, changes in the **Profile** should be done 1 hour before the rise/drop. Repeat the test as necessary until you are comfortable with your **basal rates** settings. +See [here](../GettingHelp/ProfileTuning.md) how to tweak your basal profile, analyzing patterns in closed loop. + +When taking action on the result of your basal testing, changes in the **Profile** should be done 1 to 2 hours (depends on your insulin type) before the rise/drop. Repeat the test as necessary until you are comfortable with your **basal rates** settings. (your-aaps-profile-insulin-sensitivity-factor)= diff --git a/docs/CROWDIN/cs/SupportingAaps/HowCanIHelp.md b/docs/CROWDIN/cs/SupportingAaps/HowCanIHelp.md index 8ec630000b9c..744202ce8311 100644 --- a/docs/CROWDIN/cs/SupportingAaps/HowCanIHelp.md +++ b/docs/CROWDIN/cs/SupportingAaps/HowCanIHelp.md @@ -15,7 +15,7 @@ Jéje! Podívejte se na seznam problémů, zeptejte se na discord fóru, tam je Skvělé, toto je velmi ceněná věc a dobrý způsob, jak své znalosti zúročit! * Kanál na discordu týkající se wiki lze nalézt zde: [AndroidAPS](https://discord.gg/4fQUWHZ4Mw). -* A guide how to do commits on English wiki can be found here: [How to make a PR](../SupportingAaps/HowToEditTheDocs.md). Jiné jazyky jsou pouze překladem z angličtiny a nelze je upravovat z důvodů konzistence. +* A guide how to do commits on English wiki can be found here: [How to make a PR](../SupportingAaps/HowToEditTheDocs.md). Other languages are only translated from English and can't be edited for consistency reasons. ## Umím víc jazyků a chci překládat aplikaci nebo dokumentaci @@ -23,7 +23,7 @@ If you are translating something for the first time, please start with translati You are welcome to start as a translator for the documentation in parallel or later. -You can check the state of translations for the languages app and documentation [here](StateOfTranslations). +You can check the state of translations for the languages app and documentation [here](#StateOfTranslations). * Pokud chcete přeložit **aplikaci** do jiných jazyků (děkuji), použijte prosím [crowdin](https://crowdin.com/project/androidaps). * Pokud chcete přeložit **wiki** do jiných jazyků (děkuji), použijte prosím [crowdin](https://crowdin.com/project/androidapsdocs). diff --git a/docs/CROWDIN/cs/UsefulLinks/FAQ.md b/docs/CROWDIN/cs/UsefulLinks/FAQ.md index 9e4347b90fb2..a89e7c2762b3 100644 --- a/docs/CROWDIN/cs/UsefulLinks/FAQ.md +++ b/docs/CROWDIN/cs/UsefulLinks/FAQ.md @@ -247,7 +247,7 @@ Nahrajte si na cloudové úložiště (Dropbox, Google etc) všechny apk soubory Prosím -- check [Troubleshooting Android Studio](../GettingHelp/TroubleshootingAndroidStudio) for typical errors and +- check [Troubleshooting Android Studio](../GettingHelp/TroubleshootingAndroidStudio.md) for typical errors and - tipy na [krok za krokem](https://docs.google.com/document/d/1oc7aG0qrIMvK57unMqPEOoLt-J8UT1mxTKdTAxm8-po). ### I'm stuck on an objective and need help. diff --git a/docs/CROWDIN/cs/images/troubleshooting/profiletuning/FastRise.png b/docs/CROWDIN/cs/images/troubleshooting/profiletuning/FastRise.png new file mode 100644 index 000000000000..ba35b5bb6bf0 Binary files /dev/null and b/docs/CROWDIN/cs/images/troubleshooting/profiletuning/FastRise.png differ diff --git a/docs/CROWDIN/cs/images/troubleshooting/profiletuning/NegativeInsulin.png b/docs/CROWDIN/cs/images/troubleshooting/profiletuning/NegativeInsulin.png new file mode 100644 index 000000000000..7c39c50d00df Binary files /dev/null and b/docs/CROWDIN/cs/images/troubleshooting/profiletuning/NegativeInsulin.png differ diff --git a/docs/CROWDIN/cs/images/troubleshooting/profiletuning/NegativeInsulin2.png b/docs/CROWDIN/cs/images/troubleshooting/profiletuning/NegativeInsulin2.png new file mode 100644 index 000000000000..4bd840d597ad Binary files /dev/null and b/docs/CROWDIN/cs/images/troubleshooting/profiletuning/NegativeInsulin2.png differ diff --git a/docs/CROWDIN/cs/images/troubleshooting/profiletuning/PositiveInsulin.png b/docs/CROWDIN/cs/images/troubleshooting/profiletuning/PositiveInsulin.png new file mode 100644 index 000000000000..e50e806ebf01 Binary files /dev/null and b/docs/CROWDIN/cs/images/troubleshooting/profiletuning/PositiveInsulin.png differ diff --git a/docs/CROWDIN/cs/images/troubleshooting/profiletuning/StrongISF.png b/docs/CROWDIN/cs/images/troubleshooting/profiletuning/StrongISF.png new file mode 100644 index 000000000000..ca16a1ad1b9d Binary files /dev/null and b/docs/CROWDIN/cs/images/troubleshooting/profiletuning/StrongISF.png differ diff --git a/docs/CROWDIN/cs/images/troubleshooting/profiletuning/StuckHigh.png b/docs/CROWDIN/cs/images/troubleshooting/profiletuning/StuckHigh.png new file mode 100644 index 000000000000..1fbeefc01c50 Binary files /dev/null and b/docs/CROWDIN/cs/images/troubleshooting/profiletuning/StuckHigh.png differ diff --git a/docs/CROWDIN/cs/index.md b/docs/CROWDIN/cs/index.md index 27dd29c76f33..12a5c3282e66 100644 --- a/docs/CROWDIN/cs/index.md +++ b/docs/CROWDIN/cs/index.md @@ -159,6 +159,7 @@ Updating to a new version of AAPS <./Maintenance/UpdateToNewVersion.md> Where can I get help with AAPS <./GettingHelp/WhereCanIGetHelp.md> General troubleshooting <./GettingHelp/GeneralTroubleshooting.md> - Bluetooth troubleshooting <./GettingHelp/BluetoothTroubleshooting.md> +Profile Tuning Guide <./GettingHelp/ProfileTuning.md> Troubleshooting Android Studio <./GettingHelp/TroubleshootingAndroidStudio.md> Accessing logfiles <./GettingHelp/AccessingLogFiles.md> ``` diff --git a/docs/CROWDIN/de/Getting-Started/Introduction.md b/docs/CROWDIN/de/Getting-Started/Introduction.md index 34377592e8d5..3d154a5fe680 100644 --- a/docs/CROWDIN/de/Getting-Started/Introduction.md +++ b/docs/CROWDIN/de/Getting-Started/Introduction.md @@ -192,7 +192,7 @@ Diese Strategie reduziert das Risiko erheblich, wenn ein bösartiger Angriff auf #### Sicherheitsaspekte bezüglich einer allzu schnellen Absenkung der Blutzuckerwerte -Eine schnelle Reduktion des HbA1c und eine verbesserte Blutzuckerkontrolle klingt verlockend. Allerdings kann das _zu schnelle_Senken des durchschnittlichen Blutzuckerspiegels, durch Start eines Closed-Loop-Systems zu permanenten Schäden führen, auch an den Augen, und schmerzhafter Neuropathie, die nie mehr verschwindet. Solche Schäden lassen sich einfach vermeiden, indem man die Werte langsamer reduziert. Wenn Du derzeit einen erhöhten HbA1c hast und zu **AAPS** (oder einem anderen Closed-Loop-System) wechselst, besprich dieses potentielle Risiko _bitte_ mit Deinem Klinik-Team, bevor Du startest, und lege gemeinsam einen Zeitraum fest, in dem Du den Glukosespiegel sicher schrittweise senkst. Allgemeine Informationen darüber, wie Du Deine BZ-Werte sicher reduzieren kannst, mit Links zur medizinischen Literatur, findest Du im Abschnitt über Sicherheit [hier](#preparing-safety-first). +Eine schnelle Reduktion des HbA1c und eine verbesserte Blutzuckerkontrolle klingt verlockend. Allerdings kann das _zu schnelle_Senken des durchschnittlichen Blutzuckerspiegels, durch Start eines Closed-Loop-Systems zu permanenten Schäden führen, auch an den Augen, und schmerzhafter Neuropathie, die nie mehr verschwindet. Solche Schäden lassen sich einfach vermeiden, indem man die Werte langsamer reduziert. If you currently have an elevated HbA1c and are moving to AAPS (or any other closed loop system), please discuss this potential risk with your clinical team before starting, and agree a time plan with them. More general information on how to reduce your glucose levels safely, including links to medical literature is given in the safety section [here](#preparing-safety-first). #### Medizinische Sicherheit bezüglich Geräte, Verbrauchsmaterialien und anderer Medikamente diff --git a/docs/CROWDIN/de/GettingHelp/ProfileTuning.md b/docs/CROWDIN/de/GettingHelp/ProfileTuning.md new file mode 100644 index 000000000000..df5f85badd60 --- /dev/null +++ b/docs/CROWDIN/de/GettingHelp/ProfileTuning.md @@ -0,0 +1,136 @@ +# **Tweaking the AAPS' Profile** + +```{admonition} This is NOT a medical advice +:class: warning +Please work with your care team for support and advice on your diabetes management.
+Use this guide only once you have [set up your **Profile** correctly](https://androidaps.readthedocs.io/en/latest/SettingUpAaps/YourAapsProfile.md), following all **AAPS** objectives. +``` + +This guide explains the logic of the OpenAPS algorithm results with a given __Profile__, and provides information about which values to adjust when certain situations are observed. The suggestions about basal testing below may diverge from what your care team advises + +Using **closed loop** may make basal testing easier and may significantly reduce the hypo risk if your __Profile__ basal is too strong. + +## **Changing profile's settings, how to proceed** + +1. Ensure you have read and understand __AAPS’__ recommended settings and advice below. Not following this advice will make the whole process problematic and less likely to get a well tuned __Profile__ +2. Carefully observe and compare, **over several days**, what is happening with your __BG__ and __IOB__. +3. Keep an eye out for patterns that happen around the same time (almost) everyday. +4. It's important to do this over several days. Poor results tend to be yielded from using data observed on a single day to make __Profile’s__ adjustment decisions. +5. After you have observed a repeatable pattern of behavior, e.g. at 1PM you see a spike in __BG__ or a negative __IOB__ value, only then start to make small changes to your __Profile__. +6. It's important to limit the changes you make to one thing at a time. z.B. increase your basal by 10% around 1PM. +7. After every change, it's important to monitor the impact on your __BG__ and __IOB__ for the next few days. +8. Repeat this pattern, observe, decide, tweak again if needed + +Don't rush, go slow! + +## **Recommended settings and advice while tweaking basal** + +- Do all testing with [closed loop enabled](#AapsScreens-loop-status). +- **Turn OFF all [automations](../DailyLifeWithAAPS/Automations.md)** +- **Turn OFF [DynISF](#Open-APS-features-DynamicISF), [AutoISF](../AdvancedOptions/DevBranch.md), [AutoSens](#Open-APS-features-autosens)** so that they will not try to adapt your profile. +- Do not make manual user actions (manual bolus, temp targets etc…) while testing: let the system use the **Profile** settings only. +- For the [additional graphs](#AapsScreens-section-g-additional-graphs): on graph 1, use Insulin On Board, Carbs On Board (and Sensitivity change). On graph 2, use Deviations and Blood Glucose Impact. When asking for advice, always include those on your screenshots. +- COB=0[*](#profiletuning-cob-zero) +- No physical activities. +- No stress. +- No illness. +- No extreme weather like high or low temperatures. +- If your [basal rate profile](#your-aaps-profile-basal-rates) is correct, when you are on target with COB=0[*](#profiletuning-cob-zero) and IOB=0, you will remain constantly on target whatever your ISF (ISF is only used when you are higher than your target). +- You need to check the actual IOB but also, the IOB chart to see how the IOB was during the past few hours. + +(profiletuning-cob-zero)= + +***COB = 0** + +Meaning that the meal is digested, and there are no more carbs in your body. + +AAPS might indicate [COB=0 while you still have carbs on board](../DailyLifeWithAAPS/CobCalculation.md). + +## **[Profile](../SettingUpAaps/YourAapsProfile.md) definitions** + +A too **strong Profile** indicates some combination of the following: + +- [ISF](#insulin-sensitivity-factor-isf) number is too small +- The [basal](#basal-rates) number is too big +- [I:C](#insulin-to-carb-ratio-icr) number is too small + +## **IOB Observations** + +*Note: you can also use Loopalyzer IOB graph in Nightscout reports to view IOB on several days.* + +If you observe the following patterns after a few days, consider the following changes + +### **IOB positive** + +- **Profile** basal might not be strong enough (this could also be because of things like unannounced food, illness, bad site absorption, etc.) + +![Positive IOB](../images/troubleshooting/profiletuning/PositiveInsulin.png) + +### **IOB negative** + +- Default basal too strong +- May be the effect from past exercise/physical activity + +![Negative IOB](../images/troubleshooting/profiletuning/NegativeInsulin.png) + +- Previous meal: too much bolus (which resulted in a very long zero temp basal) + +![Negative IOB](../images/troubleshooting/profiletuning/NegativeInsulin2.png) + +## **BG Target Observations** + +### **Stuck High** + +- __ISF__ ‘s number is high and not strong enough (calculated insulin is too weak) + +![Stuck High](../images/troubleshooting/profiletuning/StuckHigh.png) + +- __Profile__ basal might not be strong enough (SMBs do not have enough "basal stock" to use) +- A security ([MaxIOB](#Open-APS-features-maximum-total-iob-openaps-cant-go-over)?) might have kicked in and is limiting insulin injection. Verify in the [SMB](#Open-APS-features-super-micro-bolus-smb) tab. +- Technical issue: site absorption, infusion set, ... + +### **Stuck Low** + +- __ISF__ too strong and the number needs to be raised higher +- __Profile__ basal too strong (if also negative IOB) + +### **Rollercoaster (ups and downs)** + +- **ISF** too strong? See your [AAPS Profile](#your-aaps-profile-insulin-sensitivity-factor) + +![Rollercoaster](../images/troubleshooting/profiletuning/StrongISF.png) + +## **BG After Meals Observations** + +### **Fast rise and BG going high** + +- Food contains fast carbs +- Consider doing a pre-bolus +- Bolus (IC or injected %) not strong enough + +![Rise High](../images/troubleshooting/profiletuning/FastRise.png) + +### **Fast rise and then BG going low** + +- Consider doing a pre-bolus, profile might be too aggressive (over correction of the raise) +- Bolus too strong + + + +## **[How to calculate your I:C](#your-aaps-profile-insulin-to-carbs-ratio)** + +1. First, you need the correct default basal settings in your **Profile**. +2. Start on target, better without negative IOB. +3. Record the total insulin given in the pump tab (or pump history) and call it Start insulin C4. Very accurately measure a known portion of carbs, and record the start time and Start IOB. Then enter carbs and bolus information into AAPS using the wizard (with the current configured CI). Don't forget to eat the carbs ;) +4. After some hours, when COB=0[*](#profiletuning-cob-zero) and you're back on target, record end time, and note down the End IOB, check the total insulin given as before and call it End insulin. *NOTE: The time frame is NOT important, as long as it is longer than your digestion* +5. From the difference between Start and End insulin amount, subtract/add the difference end IOB - start IOB. Then subtract the basal insulin calculated from your profile settings. +6. If __BG__ is in target, you'll have the total insulin used to “digest” your carbs. Calculate your **I:C**. + +### **Explanations for the I:C calculations** + +- With a **Profile** that has the correct default basal rate, during any time frame, you should stay on target and have an IOB near 0. You get your **Profile** basal only. +- You add carbs and bolus to this mix. Wait till your body digests all the carbs and be back on **BG** target. Your insulin usage will be the sum of your basal + the insulin needed for the carbs. You calculate the insulin used for your basal (by using your **Profile**) and the surplus will be the insulin used to digest the carbs. +- If the time frame is too short, there will be carbs undigested, thus your "insulin needed for the carbs" will be wrong. +- If the time frame is too long, nothing bad will happen. You'll use all your carbs and you'll get more basal. At the end, you'll subtract the basal from the total insulin used, the extended time frame (with more basal use) will not affect the result. + +Originally written up by @Robby (Discord) on tips and tricks to help tune your AAPS Profile, reviewed and edited by the community (thank you!). diff --git a/docs/CROWDIN/de/SettingUpAaps/ComputerBuild.md b/docs/CROWDIN/de/SettingUpAaps/ComputerBuild.md index 03044cde6d56..ba32a6f094d9 100644 --- a/docs/CROWDIN/de/SettingUpAaps/ComputerBuild.md +++ b/docs/CROWDIN/de/SettingUpAaps/ComputerBuild.md @@ -70,7 +70,7 @@ Die Gradle-Version ist mit dem Quellcode verknüpft. Wenn Du den Quellcode herun ## Hilfe und Unterstützung während des Erstellungsprozesses -Solltest Du Probleme beim Erstellen der **AAPS**-App haben, kannst Du im Abschnitt [**Fehlerbehebung für Android Studio**](../GettingHelp/TroubleshootingAndroidStudio) einiges an Hilfestellung finden. +If you run into difficulties in the process of building the **AAPS** app, there is a dedicated [**troubleshooting Android Studio**](../GettingHelp/TroubleshootingAndroidStudio.md) section, please consult that first. Wenn Du den Eindruck hast, dass in der Anleitung Schritte falsch, fehlend oder missverständlich sind, oder Du trotzdem noch Probleme hast, wende Dich über [Facebook](https://www.facebook.com/groups/AndroidAPSUsers) oder [Discord](https://discord.gg/4fQUWHZ4Mw) an andere **AAPS**-Nutzende. Wenn Du selbst etwas ändern möchtest (z.B. Screenshots aktualisieren _etc_), erstelle einen entsprechenden [Pull-Request (PR)](../SupportingAaps/HowToEditTheDocs.md). @@ -409,7 +409,7 @@ Sobald der Build abgeschlossen ist, wird Android Studio "BUILD SUCCESSFUL" anzei ![Build abgeschlossen](../images/Building-the-App/049_ReopenNotification.png) -**_Wenn der „Build“ fehlgeschlagen ist, lies bitte den Abschnitt [Fehlerbehebung für Android Studio](../GettingHelp/TroubleshootingAndroidStudio)._** +**_If the build was not successful, refer to the [Android Studio Troubleshooting section](../GettingHelp/TroubleshootingAndroidStudio.md)._** Klicke im Benachrichtigungsfeld auf den blauen Link "locate": diff --git a/docs/CROWDIN/de/SettingUpAaps/Preferences.md b/docs/CROWDIN/de/SettingUpAaps/Preferences.md index 74a8af21328e..57024907bbce 100644 --- a/docs/CROWDIN/de/SettingUpAaps/Preferences.md +++ b/docs/CROWDIN/de/SettingUpAaps/Preferences.md @@ -300,7 +300,7 @@ Wechsel zwischen Open Loop, Closed Loop und Unterbrechung bei niedrigen BZ (LGS) ![Konfigurations-Generator - Loop Modus](../images/ConfigBuilder_LoopLGS.png) -(Preferences-pen-loop)= +(Preferences-open-loop)= #### Open Loop **AAPS** wertet kontinuierlich alle verfügbaren Daten (IOB, COB, BZ...) aus und erstellt, sofern notwendig, daraus Behandlungsvorschläge (temporäre Basalraten) zur Anpassung Deiner Therapie. diff --git a/docs/CROWDIN/de/SettingUpAaps/YourAapsProfile.md b/docs/CROWDIN/de/SettingUpAaps/YourAapsProfile.md index 8f2d900b7a0f..4c2208536fe0 100644 --- a/docs/CROWDIN/de/SettingUpAaps/YourAapsProfile.md +++ b/docs/CROWDIN/de/SettingUpAaps/YourAapsProfile.md @@ -123,11 +123,13 @@ Die **Abbildung unten** zeigt ein Beispiel, wie im **AAPS**-Profil die Basalrate Die richtige Basalrate zu finden ist ein „Trial and Error“-Prozess, und sollte in Abstimmung mit Deinem Diabetes-Team erfolgen. -Basalraten-Tests bringen es normalerweise mit sich, während einer 24-stündigen Fastenperiode die Basalrate und den Insulinbedarf zu beobachten. Auch wenn die Basalrate für einen ganzen Tag getestet werden muss, ist es nicht empfehlenswert 24 Stunden am Stück zu fasten. Das liegt daran, dass der Körper über spezielle Mechanismen versuchen wird das Fasten (z. B. durch Hormonausschüttung) auszugleichen. Eine empfohlene Methode ist 3 Mal für einen Zeitraum von 8 Stunden zu fasten. +There are basal testing methods which usually entails observing your basal rates and insulin needs during an intermittent fasting over a 24-hour period. Auch wenn die Basalrate für einen ganzen Tag getestet werden muss, ist es nicht empfehlenswert 24 Stunden am Stück zu fasten. Das liegt daran, dass der Körper über spezielle Mechanismen versuchen wird das Fasten (z. B. durch Hormonausschüttung) auszugleichen. Eine empfohlene Methode ist 3 Mal für einen Zeitraum von 8 Stunden zu fasten. -Die empfohlene Vorgehensweise ist, den Loop zu pausieren, sodass auf die Standard-Basalrate „zurückgefallen“ wird. Beobachte wie sich Dein **Glukosewert** entwickelt: Sinkt er, ist die Basalrate zu hoch. Und umgekehrt.
Eine andere (möglicherweise schwierigere) Methode ist, den Loop aktiv zu lassen und zu beobachten, wie sich das **IOB** verändert. Wenn das **IOB** negativ ist, ist Deine Basalrate zu hoch. Und umgekehrt. Beachte, dass diese Methode den **ISF** nutzt, um damit den **Glukosewert** zu korrigieren. Damit hängt der Erfolg von mehreren Variablen (und nicht nur von der Basalrate) ab.
Eine weitere Möglichkeit die Basalrate anzuzupassen ist, die Loop-Aktionen während der Nacht, wenn keine Kohlenhydrate mehr aktiv sind, zu beobachten. Diese Methode ist besonders für Kinder, für die Fasten oft schwierig ist oder deren Insulinbedarf sich oft ändert, geeignet. [Dr. Saleh Adi von Tidepool](https://www.youtube.com/watch?v=-fpWnGRhLSo) bietet hilfreiche Wege, wie Du nächtliche Glukoseverläufe analysieren kannst und daraus Optimierungen der Basalrate ableiten kannst, an. +The recommended method is to suspend the loop (for safety you can set AAPS to [**LGS**](#Preferences-aps-mode) to avoid lows, as done for achieving [objective 6](#objectives-objective6)), which will revert to your default background basal rate. Beobachte wie sich Dein **Glukosewert** entwickelt: Sinkt er, ist die Basalrate zu hoch. Und umgekehrt.
Eine andere (möglicherweise schwierigere) Methode ist, den Loop aktiv zu lassen und zu beobachten, wie sich das **IOB** verändert. Wenn das **IOB** negativ ist, ist Deine Basalrate zu hoch. Und umgekehrt. Beachte, dass diese Methode den **ISF** nutzt, um damit den **Glukosewert** zu korrigieren. Damit hängt der Erfolg von mehreren Variablen (und nicht nur von der Basalrate) ab.
Eine weitere Möglichkeit die Basalrate anzuzupassen ist, die Loop-Aktionen während der Nacht, wenn keine Kohlenhydrate mehr aktiv sind, zu beobachten. Diese Methode ist besonders für Kinder, für die Fasten oft schwierig ist oder deren Insulinbedarf sich oft ändert, geeignet. [Dr Saleh Adi from Tidepool](https://www.youtube.com/watch?v=-fpWnGRhLSo) provides useful ways on how to analyze overnight BG lines in order to optimize your basal rates. -Wenn Du Veränderungen aus dem Basalratentest umsetzen möchtest, sollten die Änderungen im **Profil** eine Stunde vor dem Zeitpunkt des beobachteten Steigens oder Fallens vorgenommen werden. Wiederhole den Test so lange, bis Du mit Deiner **Basalraten**-Einstellungen zufrieden bist. +See [here](../GettingHelp/ProfileTuning.md) how to tweak your basal profile, analyzing patterns in closed loop. + +When taking action on the result of your basal testing, changes in the **Profile** should be done 1 to 2 hours (depends on your insulin type) before the rise/drop. Wiederhole den Test so lange, bis Du mit Deiner **Basalraten**-Einstellungen zufrieden bist. (your-aaps-profile-insulin-sensitivity-factor)= diff --git a/docs/CROWDIN/de/SupportingAaps/HowCanIHelp.md b/docs/CROWDIN/de/SupportingAaps/HowCanIHelp.md index 7c015a11bcdb..6b6380f67bb4 100644 --- a/docs/CROWDIN/de/SupportingAaps/HowCanIHelp.md +++ b/docs/CROWDIN/de/SupportingAaps/HowCanIHelp.md @@ -15,7 +15,7 @@ Juhuu! Schau dir die Issues an, frag im discord Channel. Es gibt immer viel zu t Großartig, das ist sehr willkommen und eine gute Möglichkeit, etwas beizutragen! * Den discord Channel über das Wiki findest du hier: [AndroidAPSwiki/Lobby](https://discord.gg/4fQUWHZ4Mw). -* Eine Anleitung, wie man Beiträge auf Englisch hinzufügt und bearbeitet, ist hier zu finden: [Wie man die Dokumentation bearbeitet](../SupportingAaps/HowToEditTheDocs.md). Andere Sprachen können nur übersetzt, aber nicht bearbeitet werden. Dadurch wird die Einheitlichkeit des Wikis in allen Sprachen gewährleistet. +* Eine Anleitung, wie man Beiträge auf Englisch hinzufügt und bearbeitet, ist hier zu finden: [Wie man die Dokumentation bearbeitet](../SupportingAaps/HowToEditTheDocs.md). Other languages are only translated from English and can't be edited for consistency reasons. ## Ich spreche mehrere Sprachen und würde gerne bei der Übersetzung der App bzw. des Wikis helfen @@ -23,7 +23,7 @@ Wenn Du zum ersten Mal übersetzen solltest, beginne mit der Übersetzung der Te Als Übersetzer für die Dokumentation kannst Du parallel zur App-Übersetzung oder auch später anfangen. -Den aktuellen Fortschritt bei der Übersetzung der App und der Dokumentation kannst Du[hier](StateOfTranslations) einsehen. +You can check the state of translations for the languages app and documentation [here](#StateOfTranslations). * Falls du die **die App** in andere Sprachen übersetzen willst (danke), nutze bitte [crowdin](https://crowdin.com/project/androidaps). * Falls du die **die Docs** in andere Sprachen übersetzen willst (danke), nutze bitte [crowdin](https://crowdin.com/project/androidapsdocs). diff --git a/docs/CROWDIN/de/UsefulLinks/FAQ.md b/docs/CROWDIN/de/UsefulLinks/FAQ.md index 61bedcabc042..4b14d796e136 100644 --- a/docs/CROWDIN/de/UsefulLinks/FAQ.md +++ b/docs/CROWDIN/de/UsefulLinks/FAQ.md @@ -247,7 +247,7 @@ Kopiere auf ein Cloud-Drive (Dropbox, Google etc.): Alle APK's die Du benutzt ha Bitte -- schau im Abschnitt [Fehlerbehebung für Android Studio](../GettingHelp/TroubleshootingAndroidStudio) nach typischen Fehlern und +- check [Troubleshooting Android Studio](../GettingHelp/TroubleshootingAndroidStudio.md) for typical errors and - die Tipps in dieser [Schritt für Schritt Anleitung](https://docs.google.com/document/d/1oc7aG0qrIMvK57unMqPEOoLt-J8UT1mxTKdTAxm8-po). ### Ich stecke bei einem Ziel fest und brauche Hilfe. diff --git a/docs/CROWDIN/de/images/troubleshooting/profiletuning/FastRise.png b/docs/CROWDIN/de/images/troubleshooting/profiletuning/FastRise.png new file mode 100644 index 000000000000..ba35b5bb6bf0 Binary files /dev/null and b/docs/CROWDIN/de/images/troubleshooting/profiletuning/FastRise.png differ diff --git a/docs/CROWDIN/de/images/troubleshooting/profiletuning/NegativeInsulin.png b/docs/CROWDIN/de/images/troubleshooting/profiletuning/NegativeInsulin.png new file mode 100644 index 000000000000..7c39c50d00df Binary files /dev/null and b/docs/CROWDIN/de/images/troubleshooting/profiletuning/NegativeInsulin.png differ diff --git a/docs/CROWDIN/de/images/troubleshooting/profiletuning/NegativeInsulin2.png b/docs/CROWDIN/de/images/troubleshooting/profiletuning/NegativeInsulin2.png new file mode 100644 index 000000000000..4bd840d597ad Binary files /dev/null and b/docs/CROWDIN/de/images/troubleshooting/profiletuning/NegativeInsulin2.png differ diff --git a/docs/CROWDIN/de/images/troubleshooting/profiletuning/PositiveInsulin.png b/docs/CROWDIN/de/images/troubleshooting/profiletuning/PositiveInsulin.png new file mode 100644 index 000000000000..e50e806ebf01 Binary files /dev/null and b/docs/CROWDIN/de/images/troubleshooting/profiletuning/PositiveInsulin.png differ diff --git a/docs/CROWDIN/de/images/troubleshooting/profiletuning/StrongISF.png b/docs/CROWDIN/de/images/troubleshooting/profiletuning/StrongISF.png new file mode 100644 index 000000000000..ca16a1ad1b9d Binary files /dev/null and b/docs/CROWDIN/de/images/troubleshooting/profiletuning/StrongISF.png differ diff --git a/docs/CROWDIN/de/images/troubleshooting/profiletuning/StuckHigh.png b/docs/CROWDIN/de/images/troubleshooting/profiletuning/StuckHigh.png new file mode 100644 index 000000000000..1fbeefc01c50 Binary files /dev/null and b/docs/CROWDIN/de/images/troubleshooting/profiletuning/StuckHigh.png differ diff --git a/docs/CROWDIN/de/index.md b/docs/CROWDIN/de/index.md index 0164e835c6a5..d26c1df997d6 100644 --- a/docs/CROWDIN/de/index.md +++ b/docs/CROWDIN/de/index.md @@ -159,6 +159,7 @@ Updating to a new version of AAPS <./Maintenance/UpdateToNewVersion.md> Where can I get help with AAPS <./GettingHelp/WhereCanIGetHelp.md> General troubleshooting <./GettingHelp/GeneralTroubleshooting.md> - Bluetooth troubleshooting <./GettingHelp/BluetoothTroubleshooting.md> +Profile Tuning Guide <./GettingHelp/ProfileTuning.md> Troubleshooting Android Studio <./GettingHelp/TroubleshootingAndroidStudio.md> Accessing logfiles <./GettingHelp/AccessingLogFiles.md> ``` diff --git a/docs/CROWDIN/el/Getting-Started/Introduction.md b/docs/CROWDIN/el/Getting-Started/Introduction.md index 973fe67cee43..5f8df8b634f0 100644 --- a/docs/CROWDIN/el/Getting-Started/Introduction.md +++ b/docs/CROWDIN/el/Getting-Started/Introduction.md @@ -192,7 +192,7 @@ If a malicious attack was made on your insulin pump, these strategies would sign #### Safety considerations around improving blood glucose control too fast -A rapid reduction in HbA1c and improved blood glucose control sounds appealing. However, reducing average blood glucose levels _too fast_ by starting any closed loop system can cause permanent damage, including to the eyes, and painful neuropathy that never goes away. This damage can be avoided simply by reducing levels more slowly. If you currently have an elevated HbA1c and are moving to AAPS (or any other closed loop system), please discuss this potential risk with your clinical team before starting, and agree a timeplan with them. More general information on how to reduce your glucose levels safely, including links to medical literature is given in the [safety section [here](#preparing-safety-first). +A rapid reduction in HbA1c and improved blood glucose control sounds appealing. However, reducing average blood glucose levels _too fast_ by starting any closed loop system can cause permanent damage, including to the eyes, and painful neuropathy that never goes away. This damage can be avoided simply by reducing levels more slowly. If you currently have an elevated HbA1c and are moving to AAPS (or any other closed loop system), please discuss this potential risk with your clinical team before starting, and agree a time plan with them. More general information on how to reduce your glucose levels safely, including links to medical literature is given in the safety section [here](#preparing-safety-first). #### Medical safety around devices, consumable supplies and other medications diff --git a/docs/CROWDIN/el/GettingHelp/ProfileTuning.md b/docs/CROWDIN/el/GettingHelp/ProfileTuning.md new file mode 100644 index 000000000000..566fc5f5c43b --- /dev/null +++ b/docs/CROWDIN/el/GettingHelp/ProfileTuning.md @@ -0,0 +1,136 @@ +# **Tweaking the AAPS' Profile** + +```{admonition} This is NOT a medical advice +:class: warning +Please work with your care team for support and advice on your diabetes management.
+Use this guide only once you have [set up your **Profile** correctly](https://androidaps.readthedocs.io/en/latest/SettingUpAaps/YourAapsProfile.md), following all **AAPS** objectives. +``` + +This guide explains the logic of the OpenAPS algorithm results with a given __Profile__, and provides information about which values to adjust when certain situations are observed. The suggestions about basal testing below may diverge from what your care team advises + +Using **closed loop** may make basal testing easier and may significantly reduce the hypo risk if your __Profile__ basal is too strong. + +## **Changing profile's settings, how to proceed** + +1. Ensure you have read and understand __AAPS’__ recommended settings and advice below. Not following this advice will make the whole process problematic and less likely to get a well tuned __Profile__ +2. Carefully observe and compare, **over several days**, what is happening with your __BG__ and __IOB__. +3. Keep an eye out for patterns that happen around the same time (almost) everyday. +4. It's important to do this over several days. Poor results tend to be yielded from using data observed on a single day to make __Profile’s__ adjustment decisions. +5. After you have observed a repeatable pattern of behavior, e.g. at 1PM you see a spike in __BG__ or a negative __IOB__ value, only then start to make small changes to your __Profile__. +6. It's important to limit the changes you make to one thing at a time. E.g. increase your basal by 10% around 1PM. +7. After every change, it's important to monitor the impact on your __BG__ and __IOB__ for the next few days. +8. Repeat this pattern, observe, decide, tweak again if needed + +Don't rush, go slow! + +## **Recommended settings and advice while tweaking basal** + +- Do all testing with [closed loop enabled](#AapsScreens-loop-status). +- **Turn OFF all [automations](../DailyLifeWithAAPS/Automations.md)** +- **Turn OFF [DynISF](#Open-APS-features-DynamicISF), [AutoISF](../AdvancedOptions/DevBranch.md), [AutoSens](#Open-APS-features-autosens)** so that they will not try to adapt your profile. +- Do not make manual user actions (manual bolus, temp targets etc…) while testing: let the system use the **Profile** settings only. +- For the [additional graphs](#AapsScreens-section-g-additional-graphs): on graph 1, use Insulin On Board, Carbs On Board (and Sensitivity change). On graph 2, use Deviations and Blood Glucose Impact. When asking for advice, always include those on your screenshots. +- COB=0[*](#profiletuning-cob-zero) +- No physical activities. +- No stress. +- No illness. +- No extreme weather like high or low temperatures. +- If your [basal rate profile](#your-aaps-profile-basal-rates) is correct, when you are on target with COB=0[*](#profiletuning-cob-zero) and IOB=0, you will remain constantly on target whatever your ISF (ISF is only used when you are higher than your target). +- You need to check the actual IOB but also, the IOB chart to see how the IOB was during the past few hours. + +(profiletuning-cob-zero)= + +***COB = 0** + +Meaning that the meal is digested, and there are no more carbs in your body. + +AAPS might indicate [COB=0 while you still have carbs on board](../DailyLifeWithAAPS/CobCalculation.md). + +## **[Profile](../SettingUpAaps/YourAapsProfile.md) definitions** + +A too **strong Profile** indicates some combination of the following: + +- [ISF](#insulin-sensitivity-factor-isf) number is too small +- The [basal](#basal-rates) number is too big +- [I:C](#insulin-to-carb-ratio-icr) number is too small + +## **IOB Observations** + +*Note: you can also use Loopalyzer IOB graph in Nightscout reports to view IOB on several days.* + +If you observe the following patterns after a few days, consider the following changes + +### **IOB positive** + +- **Profile** basal might not be strong enough (this could also be because of things like unannounced food, illness, bad site absorption, etc.) + +![Positive IOB](../images/troubleshooting/profiletuning/PositiveInsulin.png) + +### **IOB negative** + +- Default basal too strong +- May be the effect from past exercise/physical activity + +![Negative IOB](../images/troubleshooting/profiletuning/NegativeInsulin.png) + +- Previous meal: too much bolus (which resulted in a very long zero temp basal) + +![Negative IOB](../images/troubleshooting/profiletuning/NegativeInsulin2.png) + +## **BG Target Observations** + +### **Stuck High** + +- __ISF__ ‘s number is high and not strong enough (calculated insulin is too weak) + +![Stuck High](../images/troubleshooting/profiletuning/StuckHigh.png) + +- __Profile__ basal might not be strong enough (SMBs do not have enough "basal stock" to use) +- A security ([MaxIOB](#Open-APS-features-maximum-total-iob-openaps-cant-go-over)?) might have kicked in and is limiting insulin injection. Verify in the [SMB](#Open-APS-features-super-micro-bolus-smb) tab. +- Technical issue: site absorption, infusion set, ... + +### **Stuck Low** + +- __ISF__ too strong and the number needs to be raised higher +- __Profile__ basal too strong (if also negative IOB) + +### **Rollercoaster (ups and downs)** + +- **ISF** too strong? See your [AAPS Profile](#your-aaps-profile-insulin-sensitivity-factor) + +![Rollercoaster](../images/troubleshooting/profiletuning/StrongISF.png) + +## **BG After Meals Observations** + +### **Fast rise and BG going high** + +- Food contains fast carbs +- Consider doing a pre-bolus +- Bolus (IC or injected %) not strong enough + +![Rise High](../images/troubleshooting/profiletuning/FastRise.png) + +### **Fast rise and then BG going low** + +- Consider doing a pre-bolus, profile might be too aggressive (over correction of the raise) +- Bolus too strong + + + +## **[How to calculate your I:C](#your-aaps-profile-insulin-to-carbs-ratio)** + +1. First, you need the correct default basal settings in your **Profile**. +2. Start on target, better without negative IOB. +3. Record the total insulin given in the pump tab (or pump history) and call it Start insulin C4. Very accurately measure a known portion of carbs, and record the start time and Start IOB. Then enter carbs and bolus information into AAPS using the wizard (with the current configured CI). Don't forget to eat the carbs ;) +4. After some hours, when COB=0[*](#profiletuning-cob-zero) and you're back on target, record end time, and note down the End IOB, check the total insulin given as before and call it End insulin. *NOTE: The time frame is NOT important, as long as it is longer than your digestion* +5. From the difference between Start and End insulin amount, subtract/add the difference end IOB - start IOB. Then subtract the basal insulin calculated from your profile settings. +6. If __BG__ is in target, you'll have the total insulin used to “digest” your carbs. Calculate your **I:C**. + +### **Explanations for the I:C calculations** + +- With a **Profile** that has the correct default basal rate, during any time frame, you should stay on target and have an IOB near 0. You get your **Profile** basal only. +- You add carbs and bolus to this mix. Wait till your body digests all the carbs and be back on **BG** target. Your insulin usage will be the sum of your basal + the insulin needed for the carbs. You calculate the insulin used for your basal (by using your **Profile**) and the surplus will be the insulin used to digest the carbs. +- If the time frame is too short, there will be carbs undigested, thus your "insulin needed for the carbs" will be wrong. +- If the time frame is too long, nothing bad will happen. You'll use all your carbs and you'll get more basal. At the end, you'll subtract the basal from the total insulin used, the extended time frame (with more basal use) will not affect the result. + +Originally written up by @Robby (Discord) on tips and tricks to help tune your AAPS Profile, reviewed and edited by the community (thank you!). diff --git a/docs/CROWDIN/el/SettingUpAaps/ComputerBuild.md b/docs/CROWDIN/el/SettingUpAaps/ComputerBuild.md index b2a73a90edde..2fc642a54006 100644 --- a/docs/CROWDIN/el/SettingUpAaps/ComputerBuild.md +++ b/docs/CROWDIN/el/SettingUpAaps/ComputerBuild.md @@ -70,7 +70,7 @@ The Gradle version is linked to the source code, you will always get the correct ## Help and support during the building process -If you run into difficulties in the process of building the **AAPS** app, there is a dedicated [**troubleshooting Android Studio**](../GettingHelp/TroubleshootingAndroidStudio) section, please consult that first. +If you run into difficulties in the process of building the **AAPS** app, there is a dedicated [**troubleshooting Android Studio**](../GettingHelp/TroubleshootingAndroidStudio.md) section, please consult that first. If you think something in the building instructions is wrong, missing or confusing, or you are still struggling, please reach out to other **AAPS** users group on [Facebook](https://www.facebook.com/groups/AndroidAPSUsers) or [Discord](https://discord.gg/4fQUWHZ4Mw). If you want to change something yourself (updating screenshots _etc_), please submit a [pull request (PR)](../SupportingAaps/HowToEditTheDocs.md). @@ -409,7 +409,7 @@ Android Studio will display the information "BUILD SUCCESSFUL" after build is fi ![Build finished](../images/Building-the-App/049_ReopenNotification.png) -**_If the build was not successful, refer to the [Android Studio Troubleshooting section](../GettingHelp/TroubleshootingAndroidStudio)._** +**_If the build was not successful, refer to the [Android Studio Troubleshooting section](../GettingHelp/TroubleshootingAndroidStudio.md)._** In the Notifications box, click on the blue link "locate": diff --git a/docs/CROWDIN/el/SettingUpAaps/Preferences.md b/docs/CROWDIN/el/SettingUpAaps/Preferences.md index 1018bdb03d51..d1dcc3e3d60a 100644 --- a/docs/CROWDIN/el/SettingUpAaps/Preferences.md +++ b/docs/CROWDIN/el/SettingUpAaps/Preferences.md @@ -300,7 +300,7 @@ Switch between Open Loop, Closed Loop and Low Glucose Suspend (LGS). ![Config builder - loop mode](../images/ConfigBuilder_LoopLGS.png) -(Preferences-pen-loop)= +(Preferences-open-loop)= #### Open Loop **AAPS** continuously evaluates all available data (IOB, COB, BG...) and makes treatment suggestions (temporary basal rates) on how to adjust your therapy if necessary. diff --git a/docs/CROWDIN/el/SettingUpAaps/YourAapsProfile.md b/docs/CROWDIN/el/SettingUpAaps/YourAapsProfile.md index 398007b682fe..48752f29b1b6 100644 --- a/docs/CROWDIN/el/SettingUpAaps/YourAapsProfile.md +++ b/docs/CROWDIN/el/SettingUpAaps/YourAapsProfile.md @@ -123,11 +123,13 @@ The **figure below** shows an example of how the basal rates can be set in an ** Setting your basal rates right is done by trial and error, and should be done in consultation with your diabetic team. -There are basal testing methods which usually entails observing your basal rates and insulin needs during an intermittent fasting over a 24-hour period. Although you need to test your basal rates for the whole day, it is not recommended to fast during 24h straight. This is because the body triggers mechanisms such as hormones to compensate. A recommended way is to fast 3 times for 8 hours. +There are basal testing methods which usually entails observing your basal rates and insulin needs during an intermittent fasting over a 24-hour period. Although you need to test your basal rates for the whole day, it is not recommended to fast during 24h straight. This is because the body triggers mechanisms such as hormones to compensate. A recommended way is to fast 3 times for 8 hours. -The recommended method is to suspend the loop, which will revert to your default background basal rate. Observe how your **BG** changes: if it is dropping, basal rate is too high. And vice versa.
An alternative method (may be more tricky) is to keep the loop running, and seeing how **IOB** changes. If **IOB** is negative, your basal rate is too high. And vice versa. Beware that this method relies on **ISF** to correct **BG**, and thus depends on other variables to be set reasonably well for it to be successful.
Another way of adjusting your basal rates is to watch the loop action during the night, when all COB have decayed. This method is particularly useful for children, when fasting is difficult or insulin needs change often. [Dr Saleh Adi from Tidepool](https://www.youtube.com/watch?v=-fpWnGRhLSo) provides useful ways on how to analyse overnight BG lines in order to optimise your basal rates. +The recommended method is to suspend the loop (for safety you can set AAPS to [**LGS**](#Preferences-aps-mode) to avoid lows, as done for achieving [objective 6](#objectives-objective6)), which will revert to your default background basal rate. Observe how your **BG** changes: if it is dropping, basal rate is too high. And vice versa.
An alternative method (may be more tricky) is to keep the loop running, and seeing how **IOB** changes. If **IOB** is negative, your basal rate is too high. And vice versa. Beware that this method relies on **ISF** to correct **BG**, and thus depends on other variables to be set reasonably well for it to be successful.
Another way of adjusting your basal rates is to watch the loop action during the night, when all COB have decayed. This method is particularly useful for children, when fasting is difficult or insulin needs change often. [Dr Saleh Adi from Tidepool](https://www.youtube.com/watch?v=-fpWnGRhLSo) provides useful ways on how to analyze overnight BG lines in order to optimize your basal rates. -When taking action on the result of your basal testing, changes in the **Profile** should be done 1 hour before the rise/drop. Repeat the test as necessary until you are comfortable with your **basal rates** settings. +See [here](../GettingHelp/ProfileTuning.md) how to tweak your basal profile, analyzing patterns in closed loop. + +When taking action on the result of your basal testing, changes in the **Profile** should be done 1 to 2 hours (depends on your insulin type) before the rise/drop. Repeat the test as necessary until you are comfortable with your **basal rates** settings. (your-aaps-profile-insulin-sensitivity-factor)= diff --git a/docs/CROWDIN/el/SupportingAaps/HowCanIHelp.md b/docs/CROWDIN/el/SupportingAaps/HowCanIHelp.md index 23ea6c79f5b9..d9bf2a1c6c81 100644 --- a/docs/CROWDIN/el/SupportingAaps/HowCanIHelp.md +++ b/docs/CROWDIN/el/SupportingAaps/HowCanIHelp.md @@ -15,7 +15,7 @@ Developers are parents, caregivers, loved ones and people with diabetes working Great, this is a highly appreciated thing and a good way to pay it forward! * The discord channel regarding the wiki can be found here: [AndroidAPS](https://discord.gg/4fQUWHZ4Mw). -* A guide how to do commits on English wiki can be found here: [How to make a PR](../SupportingAaps/HowToEditTheDocs.md). Άλλες γλώσσες μεταφράζονται μόνο από τα αγγλικά και δεν μπορούν να επεξεργαστούν για λόγους συνέπειας. +* A guide how to do commits on English wiki can be found here: [How to make a PR](../SupportingAaps/HowToEditTheDocs.md). Other languages are only translated from English and can't be edited for consistency reasons. ## I do speak multiple languages and want to translate the app or the documentation @@ -23,7 +23,7 @@ If you are translating something for the first time, please start with translati You are welcome to start as a translator for the documentation in parallel or later. -You can check the state of translations for the languages app and documentation [here](StateOfTranslations). +You can check the state of translations for the languages app and documentation [here](#StateOfTranslations). * Εάν θέλετε να μεταφράσετε **the app ** σε άλλες γλώσσες (ευχαριστούμε), χρησιμοποιήστε [ crowdin ](https://crowdin.com/project/androidaps). * If you want to translate **the docs** to other languages (thank you), please use [crowdin](https://crowdin.com/project/androidapsdocs). diff --git a/docs/CROWDIN/el/UsefulLinks/FAQ.md b/docs/CROWDIN/el/UsefulLinks/FAQ.md index 0beaa7f059d0..3b9b645b7c79 100644 --- a/docs/CROWDIN/el/UsefulLinks/FAQ.md +++ b/docs/CROWDIN/el/UsefulLinks/FAQ.md @@ -247,7 +247,7 @@ Copy on an internet drive (Dropbox, Google etc) : all the apks you used to insta Please -- check [Troubleshooting Android Studio](../GettingHelp/TroubleshootingAndroidStudio) for typical errors and +- check [Troubleshooting Android Studio](../GettingHelp/TroubleshootingAndroidStudio.md) for typical errors and - the tipps for with a [step by step walktrough](https://docs.google.com/document/d/1oc7aG0qrIMvK57unMqPEOoLt-J8UT1mxTKdTAxm8-po). ### I'm stuck on an objective and need help. diff --git a/docs/CROWDIN/el/images/troubleshooting/profiletuning/FastRise.png b/docs/CROWDIN/el/images/troubleshooting/profiletuning/FastRise.png new file mode 100644 index 000000000000..ba35b5bb6bf0 Binary files /dev/null and b/docs/CROWDIN/el/images/troubleshooting/profiletuning/FastRise.png differ diff --git a/docs/CROWDIN/el/images/troubleshooting/profiletuning/NegativeInsulin.png b/docs/CROWDIN/el/images/troubleshooting/profiletuning/NegativeInsulin.png new file mode 100644 index 000000000000..7c39c50d00df Binary files /dev/null and b/docs/CROWDIN/el/images/troubleshooting/profiletuning/NegativeInsulin.png differ diff --git a/docs/CROWDIN/el/images/troubleshooting/profiletuning/NegativeInsulin2.png b/docs/CROWDIN/el/images/troubleshooting/profiletuning/NegativeInsulin2.png new file mode 100644 index 000000000000..4bd840d597ad Binary files /dev/null and b/docs/CROWDIN/el/images/troubleshooting/profiletuning/NegativeInsulin2.png differ diff --git a/docs/CROWDIN/el/images/troubleshooting/profiletuning/PositiveInsulin.png b/docs/CROWDIN/el/images/troubleshooting/profiletuning/PositiveInsulin.png new file mode 100644 index 000000000000..e50e806ebf01 Binary files /dev/null and b/docs/CROWDIN/el/images/troubleshooting/profiletuning/PositiveInsulin.png differ diff --git a/docs/CROWDIN/el/images/troubleshooting/profiletuning/StrongISF.png b/docs/CROWDIN/el/images/troubleshooting/profiletuning/StrongISF.png new file mode 100644 index 000000000000..ca16a1ad1b9d Binary files /dev/null and b/docs/CROWDIN/el/images/troubleshooting/profiletuning/StrongISF.png differ diff --git a/docs/CROWDIN/el/images/troubleshooting/profiletuning/StuckHigh.png b/docs/CROWDIN/el/images/troubleshooting/profiletuning/StuckHigh.png new file mode 100644 index 000000000000..1fbeefc01c50 Binary files /dev/null and b/docs/CROWDIN/el/images/troubleshooting/profiletuning/StuckHigh.png differ diff --git a/docs/CROWDIN/el/index.md b/docs/CROWDIN/el/index.md index 5ee779ed9b13..00cae18e1388 100644 --- a/docs/CROWDIN/el/index.md +++ b/docs/CROWDIN/el/index.md @@ -159,6 +159,7 @@ Updating to a new version of AAPS <./Maintenance/UpdateToNewVersion.md> Where can I get help with AAPS <./GettingHelp/WhereCanIGetHelp.md> General troubleshooting <./GettingHelp/GeneralTroubleshooting.md> - Bluetooth troubleshooting <./GettingHelp/BluetoothTroubleshooting.md> +Profile Tuning Guide <./GettingHelp/ProfileTuning.md> Troubleshooting Android Studio <./GettingHelp/TroubleshootingAndroidStudio.md> Accessing logfiles <./GettingHelp/AccessingLogFiles.md> ``` diff --git a/docs/CROWDIN/es/Getting-Started/Introduction.md b/docs/CROWDIN/es/Getting-Started/Introduction.md index 9b6db88d304e..0793503d9301 100644 --- a/docs/CROWDIN/es/Getting-Started/Introduction.md +++ b/docs/CROWDIN/es/Getting-Started/Introduction.md @@ -192,7 +192,7 @@ Si se realizara un ataque malicioso a tu bomba de insulina, estas estrategias re #### Safety considerations around improving blood glucose control too fast -A rapid reduction in HbA1c and improved blood glucose control sounds appealing. However, reducing average blood glucose levels _too fast_ by starting any closed loop system can cause permanent damage, including to the eyes, and painful neuropathy that never goes away. This damage can be avoided simply by reducing levels more slowly. If you currently have an elevated HbA1c and are moving to AAPS (or any other closed loop system), please discuss this potential risk with your clinical team before starting, and agree a timeplan with them. More general information on how to reduce your glucose levels safely, including links to medical literature is given in the [safety section [here](#preparing-safety-first). +A rapid reduction in HbA1c and improved blood glucose control sounds appealing. However, reducing average blood glucose levels _too fast_ by starting any closed loop system can cause permanent damage, including to the eyes, and painful neuropathy that never goes away. This damage can be avoided simply by reducing levels more slowly. If you currently have an elevated HbA1c and are moving to AAPS (or any other closed loop system), please discuss this potential risk with your clinical team before starting, and agree a time plan with them. More general information on how to reduce your glucose levels safely, including links to medical literature is given in the safety section [here](#preparing-safety-first). #### Medical safety around devices, consumable supplies and other medications diff --git a/docs/CROWDIN/es/GettingHelp/ProfileTuning.md b/docs/CROWDIN/es/GettingHelp/ProfileTuning.md new file mode 100644 index 000000000000..566fc5f5c43b --- /dev/null +++ b/docs/CROWDIN/es/GettingHelp/ProfileTuning.md @@ -0,0 +1,136 @@ +# **Tweaking the AAPS' Profile** + +```{admonition} This is NOT a medical advice +:class: warning +Please work with your care team for support and advice on your diabetes management.
+Use this guide only once you have [set up your **Profile** correctly](https://androidaps.readthedocs.io/en/latest/SettingUpAaps/YourAapsProfile.md), following all **AAPS** objectives. +``` + +This guide explains the logic of the OpenAPS algorithm results with a given __Profile__, and provides information about which values to adjust when certain situations are observed. The suggestions about basal testing below may diverge from what your care team advises + +Using **closed loop** may make basal testing easier and may significantly reduce the hypo risk if your __Profile__ basal is too strong. + +## **Changing profile's settings, how to proceed** + +1. Ensure you have read and understand __AAPS’__ recommended settings and advice below. Not following this advice will make the whole process problematic and less likely to get a well tuned __Profile__ +2. Carefully observe and compare, **over several days**, what is happening with your __BG__ and __IOB__. +3. Keep an eye out for patterns that happen around the same time (almost) everyday. +4. It's important to do this over several days. Poor results tend to be yielded from using data observed on a single day to make __Profile’s__ adjustment decisions. +5. After you have observed a repeatable pattern of behavior, e.g. at 1PM you see a spike in __BG__ or a negative __IOB__ value, only then start to make small changes to your __Profile__. +6. It's important to limit the changes you make to one thing at a time. E.g. increase your basal by 10% around 1PM. +7. After every change, it's important to monitor the impact on your __BG__ and __IOB__ for the next few days. +8. Repeat this pattern, observe, decide, tweak again if needed + +Don't rush, go slow! + +## **Recommended settings and advice while tweaking basal** + +- Do all testing with [closed loop enabled](#AapsScreens-loop-status). +- **Turn OFF all [automations](../DailyLifeWithAAPS/Automations.md)** +- **Turn OFF [DynISF](#Open-APS-features-DynamicISF), [AutoISF](../AdvancedOptions/DevBranch.md), [AutoSens](#Open-APS-features-autosens)** so that they will not try to adapt your profile. +- Do not make manual user actions (manual bolus, temp targets etc…) while testing: let the system use the **Profile** settings only. +- For the [additional graphs](#AapsScreens-section-g-additional-graphs): on graph 1, use Insulin On Board, Carbs On Board (and Sensitivity change). On graph 2, use Deviations and Blood Glucose Impact. When asking for advice, always include those on your screenshots. +- COB=0[*](#profiletuning-cob-zero) +- No physical activities. +- No stress. +- No illness. +- No extreme weather like high or low temperatures. +- If your [basal rate profile](#your-aaps-profile-basal-rates) is correct, when you are on target with COB=0[*](#profiletuning-cob-zero) and IOB=0, you will remain constantly on target whatever your ISF (ISF is only used when you are higher than your target). +- You need to check the actual IOB but also, the IOB chart to see how the IOB was during the past few hours. + +(profiletuning-cob-zero)= + +***COB = 0** + +Meaning that the meal is digested, and there are no more carbs in your body. + +AAPS might indicate [COB=0 while you still have carbs on board](../DailyLifeWithAAPS/CobCalculation.md). + +## **[Profile](../SettingUpAaps/YourAapsProfile.md) definitions** + +A too **strong Profile** indicates some combination of the following: + +- [ISF](#insulin-sensitivity-factor-isf) number is too small +- The [basal](#basal-rates) number is too big +- [I:C](#insulin-to-carb-ratio-icr) number is too small + +## **IOB Observations** + +*Note: you can also use Loopalyzer IOB graph in Nightscout reports to view IOB on several days.* + +If you observe the following patterns after a few days, consider the following changes + +### **IOB positive** + +- **Profile** basal might not be strong enough (this could also be because of things like unannounced food, illness, bad site absorption, etc.) + +![Positive IOB](../images/troubleshooting/profiletuning/PositiveInsulin.png) + +### **IOB negative** + +- Default basal too strong +- May be the effect from past exercise/physical activity + +![Negative IOB](../images/troubleshooting/profiletuning/NegativeInsulin.png) + +- Previous meal: too much bolus (which resulted in a very long zero temp basal) + +![Negative IOB](../images/troubleshooting/profiletuning/NegativeInsulin2.png) + +## **BG Target Observations** + +### **Stuck High** + +- __ISF__ ‘s number is high and not strong enough (calculated insulin is too weak) + +![Stuck High](../images/troubleshooting/profiletuning/StuckHigh.png) + +- __Profile__ basal might not be strong enough (SMBs do not have enough "basal stock" to use) +- A security ([MaxIOB](#Open-APS-features-maximum-total-iob-openaps-cant-go-over)?) might have kicked in and is limiting insulin injection. Verify in the [SMB](#Open-APS-features-super-micro-bolus-smb) tab. +- Technical issue: site absorption, infusion set, ... + +### **Stuck Low** + +- __ISF__ too strong and the number needs to be raised higher +- __Profile__ basal too strong (if also negative IOB) + +### **Rollercoaster (ups and downs)** + +- **ISF** too strong? See your [AAPS Profile](#your-aaps-profile-insulin-sensitivity-factor) + +![Rollercoaster](../images/troubleshooting/profiletuning/StrongISF.png) + +## **BG After Meals Observations** + +### **Fast rise and BG going high** + +- Food contains fast carbs +- Consider doing a pre-bolus +- Bolus (IC or injected %) not strong enough + +![Rise High](../images/troubleshooting/profiletuning/FastRise.png) + +### **Fast rise and then BG going low** + +- Consider doing a pre-bolus, profile might be too aggressive (over correction of the raise) +- Bolus too strong + + + +## **[How to calculate your I:C](#your-aaps-profile-insulin-to-carbs-ratio)** + +1. First, you need the correct default basal settings in your **Profile**. +2. Start on target, better without negative IOB. +3. Record the total insulin given in the pump tab (or pump history) and call it Start insulin C4. Very accurately measure a known portion of carbs, and record the start time and Start IOB. Then enter carbs and bolus information into AAPS using the wizard (with the current configured CI). Don't forget to eat the carbs ;) +4. After some hours, when COB=0[*](#profiletuning-cob-zero) and you're back on target, record end time, and note down the End IOB, check the total insulin given as before and call it End insulin. *NOTE: The time frame is NOT important, as long as it is longer than your digestion* +5. From the difference between Start and End insulin amount, subtract/add the difference end IOB - start IOB. Then subtract the basal insulin calculated from your profile settings. +6. If __BG__ is in target, you'll have the total insulin used to “digest” your carbs. Calculate your **I:C**. + +### **Explanations for the I:C calculations** + +- With a **Profile** that has the correct default basal rate, during any time frame, you should stay on target and have an IOB near 0. You get your **Profile** basal only. +- You add carbs and bolus to this mix. Wait till your body digests all the carbs and be back on **BG** target. Your insulin usage will be the sum of your basal + the insulin needed for the carbs. You calculate the insulin used for your basal (by using your **Profile**) and the surplus will be the insulin used to digest the carbs. +- If the time frame is too short, there will be carbs undigested, thus your "insulin needed for the carbs" will be wrong. +- If the time frame is too long, nothing bad will happen. You'll use all your carbs and you'll get more basal. At the end, you'll subtract the basal from the total insulin used, the extended time frame (with more basal use) will not affect the result. + +Originally written up by @Robby (Discord) on tips and tricks to help tune your AAPS Profile, reviewed and edited by the community (thank you!). diff --git a/docs/CROWDIN/es/SettingUpAaps/ComputerBuild.md b/docs/CROWDIN/es/SettingUpAaps/ComputerBuild.md index 92b8708bfe69..5a62c27b15f2 100644 --- a/docs/CROWDIN/es/SettingUpAaps/ComputerBuild.md +++ b/docs/CROWDIN/es/SettingUpAaps/ComputerBuild.md @@ -70,7 +70,7 @@ The Gradle version is linked to the source code, you will always get the correct ## Help and support during the building process -If you run into difficulties in the process of building the **AAPS** app, there is a dedicated [**troubleshooting Android Studio**](../GettingHelp/TroubleshootingAndroidStudio) section, please consult that first. +If you run into difficulties in the process of building the **AAPS** app, there is a dedicated [**troubleshooting Android Studio**](../GettingHelp/TroubleshootingAndroidStudio.md) section, please consult that first. If you think something in the building instructions is wrong, missing or confusing, or you are still struggling, please reach out to other **AAPS** users group on [Facebook](https://www.facebook.com/groups/AndroidAPSUsers) or [Discord](https://discord.gg/4fQUWHZ4Mw). If you want to change something yourself (updating screenshots _etc_), please submit a [pull request (PR)](../SupportingAaps/HowToEditTheDocs.md). @@ -409,7 +409,7 @@ Android Studio will display the information "BUILD SUCCESSFUL" after build is fi ![Build finished](../images/Building-the-App/049_ReopenNotification.png) -**_If the build was not successful, refer to the [Android Studio Troubleshooting section](../GettingHelp/TroubleshootingAndroidStudio)._** +**_If the build was not successful, refer to the [Android Studio Troubleshooting section](../GettingHelp/TroubleshootingAndroidStudio.md)._** In the Notifications box, click on the blue link "locate": diff --git a/docs/CROWDIN/es/SettingUpAaps/Preferences.md b/docs/CROWDIN/es/SettingUpAaps/Preferences.md index 5209d038622e..975eee33dc36 100644 --- a/docs/CROWDIN/es/SettingUpAaps/Preferences.md +++ b/docs/CROWDIN/es/SettingUpAaps/Preferences.md @@ -300,7 +300,7 @@ Switch between Open Loop, Closed Loop and Low Glucose Suspend (LGS). ![Config builder - loop mode](../images/ConfigBuilder_LoopLGS.png) -(Preferences-pen-loop)= +(Preferences-open-loop)= #### Open Loop **AAPS** continuously evaluates all available data (IOB, COB, BG...) and makes treatment suggestions (temporary basal rates) on how to adjust your therapy if necessary. diff --git a/docs/CROWDIN/es/SettingUpAaps/YourAapsProfile.md b/docs/CROWDIN/es/SettingUpAaps/YourAapsProfile.md index 4b32c9c12726..a226ae21816b 100644 --- a/docs/CROWDIN/es/SettingUpAaps/YourAapsProfile.md +++ b/docs/CROWDIN/es/SettingUpAaps/YourAapsProfile.md @@ -123,11 +123,13 @@ The **figure below** shows an example of how the basal rates can be set in an ** Setting your basal rates right is done by trial and error, and should be done in consultation with your diabetic team. -There are basal testing methods which usually entails observing your basal rates and insulin needs during an intermittent fasting over a 24-hour period. Although you need to test your basal rates for the whole day, it is not recommended to fast during 24h straight. This is because the body triggers mechanisms such as hormones to compensate. A recommended way is to fast 3 times for 8 hours. +There are basal testing methods which usually entails observing your basal rates and insulin needs during an intermittent fasting over a 24-hour period. Although you need to test your basal rates for the whole day, it is not recommended to fast during 24h straight. This is because the body triggers mechanisms such as hormones to compensate. A recommended way is to fast 3 times for 8 hours. -The recommended method is to suspend the loop, which will revert to your default background basal rate. Observe how your **BG** changes: if it is dropping, basal rate is too high. And vice versa.
An alternative method (may be more tricky) is to keep the loop running, and seeing how **IOB** changes. If **IOB** is negative, your basal rate is too high. And vice versa. Beware that this method relies on **ISF** to correct **BG**, and thus depends on other variables to be set reasonably well for it to be successful.
Another way of adjusting your basal rates is to watch the loop action during the night, when all COB have decayed. This method is particularly useful for children, when fasting is difficult or insulin needs change often. [Dr Saleh Adi from Tidepool](https://www.youtube.com/watch?v=-fpWnGRhLSo) provides useful ways on how to analyse overnight BG lines in order to optimise your basal rates. +The recommended method is to suspend the loop (for safety you can set AAPS to [**LGS**](#Preferences-aps-mode) to avoid lows, as done for achieving [objective 6](#objectives-objective6)), which will revert to your default background basal rate. Observe how your **BG** changes: if it is dropping, basal rate is too high. And vice versa.
An alternative method (may be more tricky) is to keep the loop running, and seeing how **IOB** changes. If **IOB** is negative, your basal rate is too high. And vice versa. Beware that this method relies on **ISF** to correct **BG**, and thus depends on other variables to be set reasonably well for it to be successful.
Another way of adjusting your basal rates is to watch the loop action during the night, when all COB have decayed. This method is particularly useful for children, when fasting is difficult or insulin needs change often. [Dr Saleh Adi from Tidepool](https://www.youtube.com/watch?v=-fpWnGRhLSo) provides useful ways on how to analyze overnight BG lines in order to optimize your basal rates. -When taking action on the result of your basal testing, changes in the **Profile** should be done 1 hour before the rise/drop. Repeat the test as necessary until you are comfortable with your **basal rates** settings. +See [here](../GettingHelp/ProfileTuning.md) how to tweak your basal profile, analyzing patterns in closed loop. + +When taking action on the result of your basal testing, changes in the **Profile** should be done 1 to 2 hours (depends on your insulin type) before the rise/drop. Repeat the test as necessary until you are comfortable with your **basal rates** settings. (your-aaps-profile-insulin-sensitivity-factor)= diff --git a/docs/CROWDIN/es/SupportingAaps/HowCanIHelp.md b/docs/CROWDIN/es/SupportingAaps/HowCanIHelp.md index 6aeca540f5b9..7b90cca588fd 100644 --- a/docs/CROWDIN/es/SupportingAaps/HowCanIHelp.md +++ b/docs/CROWDIN/es/SupportingAaps/HowCanIHelp.md @@ -15,7 +15,7 @@ Yay! Look at the issues, ask in the discord channel, there is always a lot to do Great, this is a highly appreciated thing and a good way to pay it forward! * The discord channel regarding the wiki can be found here: [AndroidAPS](https://discord.gg/4fQUWHZ4Mw). -* A guide how to do commits on English wiki can be found here: [How to make a PR](../SupportingAaps/HowToEditTheDocs.md). Other languages are only translated from english and can't be edited for consistency reasons. +* A guide how to do commits on English wiki can be found here: [How to make a PR](../SupportingAaps/HowToEditTheDocs.md). Other languages are only translated from English and can't be edited for consistency reasons. ## I do speak multiple languages and want to translate the app or the documentation @@ -23,7 +23,7 @@ If you are translating something for the first time, please start with translati You are welcome to start as a translator for the documentation in parallel or later. -You can check the state of translations for the languages app and documentation [here](StateOfTranslations). +You can check the state of translations for the languages app and documentation [here](#StateOfTranslations). * If you want to translate **the app** to other languages (thank you), please use [crowdin](https://crowdin.com/project/androidaps). * If you want to translate **the docs** to other languages (thank you), please use [crowdin](https://crowdin.com/project/androidapsdocs). diff --git a/docs/CROWDIN/es/UsefulLinks/FAQ.md b/docs/CROWDIN/es/UsefulLinks/FAQ.md index 03f237eb9353..26a734613713 100644 --- a/docs/CROWDIN/es/UsefulLinks/FAQ.md +++ b/docs/CROWDIN/es/UsefulLinks/FAQ.md @@ -247,7 +247,7 @@ Copy on an internet drive (Dropbox, Google etc) : all the apks you used to insta Please -- check [Troubleshooting Android Studio](../GettingHelp/TroubleshootingAndroidStudio) for typical errors and +- check [Troubleshooting Android Studio](../GettingHelp/TroubleshootingAndroidStudio.md) for typical errors and - the tipps for with a [step by step walktrough](https://docs.google.com/document/d/1oc7aG0qrIMvK57unMqPEOoLt-J8UT1mxTKdTAxm8-po). ### I'm stuck on an objective and need help. diff --git a/docs/CROWDIN/es/images/troubleshooting/profiletuning/FastRise.png b/docs/CROWDIN/es/images/troubleshooting/profiletuning/FastRise.png new file mode 100644 index 000000000000..ba35b5bb6bf0 Binary files /dev/null and b/docs/CROWDIN/es/images/troubleshooting/profiletuning/FastRise.png differ diff --git a/docs/CROWDIN/es/images/troubleshooting/profiletuning/NegativeInsulin.png b/docs/CROWDIN/es/images/troubleshooting/profiletuning/NegativeInsulin.png new file mode 100644 index 000000000000..7c39c50d00df Binary files /dev/null and b/docs/CROWDIN/es/images/troubleshooting/profiletuning/NegativeInsulin.png differ diff --git a/docs/CROWDIN/es/images/troubleshooting/profiletuning/NegativeInsulin2.png b/docs/CROWDIN/es/images/troubleshooting/profiletuning/NegativeInsulin2.png new file mode 100644 index 000000000000..4bd840d597ad Binary files /dev/null and b/docs/CROWDIN/es/images/troubleshooting/profiletuning/NegativeInsulin2.png differ diff --git a/docs/CROWDIN/es/images/troubleshooting/profiletuning/PositiveInsulin.png b/docs/CROWDIN/es/images/troubleshooting/profiletuning/PositiveInsulin.png new file mode 100644 index 000000000000..e50e806ebf01 Binary files /dev/null and b/docs/CROWDIN/es/images/troubleshooting/profiletuning/PositiveInsulin.png differ diff --git a/docs/CROWDIN/es/images/troubleshooting/profiletuning/StrongISF.png b/docs/CROWDIN/es/images/troubleshooting/profiletuning/StrongISF.png new file mode 100644 index 000000000000..ca16a1ad1b9d Binary files /dev/null and b/docs/CROWDIN/es/images/troubleshooting/profiletuning/StrongISF.png differ diff --git a/docs/CROWDIN/es/images/troubleshooting/profiletuning/StuckHigh.png b/docs/CROWDIN/es/images/troubleshooting/profiletuning/StuckHigh.png new file mode 100644 index 000000000000..1fbeefc01c50 Binary files /dev/null and b/docs/CROWDIN/es/images/troubleshooting/profiletuning/StuckHigh.png differ diff --git a/docs/CROWDIN/es/index.md b/docs/CROWDIN/es/index.md index 9c3c7a8e54d7..f850b4bfb8f0 100644 --- a/docs/CROWDIN/es/index.md +++ b/docs/CROWDIN/es/index.md @@ -159,6 +159,7 @@ Updating to a new version of AAPS <./Maintenance/UpdateToNewVersion.md> Where can I get help with AAPS <./GettingHelp/WhereCanIGetHelp.md> General troubleshooting <./GettingHelp/GeneralTroubleshooting.md> - Bluetooth troubleshooting <./GettingHelp/BluetoothTroubleshooting.md> +Profile Tuning Guide <./GettingHelp/ProfileTuning.md> Troubleshooting Android Studio <./GettingHelp/TroubleshootingAndroidStudio.md> Accessing logfiles <./GettingHelp/AccessingLogFiles.md> ``` diff --git a/docs/CROWDIN/fr/Getting-Started/Introduction.md b/docs/CROWDIN/fr/Getting-Started/Introduction.md index 099837250616..0fe727ffe165 100644 --- a/docs/CROWDIN/fr/Getting-Started/Introduction.md +++ b/docs/CROWDIN/fr/Getting-Started/Introduction.md @@ -192,7 +192,7 @@ Si une attaque malveillante était effectuée contre votre pompe à insuline, ce #### Considérations de sécurité en lien avec l'amélioration trop rapide du contrôle de la glycémie -Une baisse rapide de l'HbA1c et un meilleur contrôle de la glycémie paraissent attirants. Cependant, faire baisser les niveaux moyens de glucose sanguin _trop rapidement_ en démarrant un système de boucle fermée quel qu'il soit, peut causer des dommages permanents, y compris aux yeux, et une neuropathie douloureuse qui ne disparaîtra jamais. Ces atteintes peuvent être évitées simplement en baissant plus lentement les niveaux. Si vous avez actuellement un taux d'HbA1c élevé et que vous passez à AAPS (ou à tout autre système en boucle fermée), veuillez discuter de ce risque potentiel avec votre équipe médicale avant de commencer, et convenez d'un plan de mise en place avec elle. More general information on how to reduce your glucose levels safely, including links to medical literature is given in the [safety section [here](#preparing-safety-first). +Une baisse rapide de l'HbA1c et un meilleur contrôle de la glycémie paraissent attirants. Cependant, faire baisser les niveaux moyens de glucose sanguin _trop rapidement_ en démarrant un système de boucle fermée quel qu'il soit, peut causer des dommages permanents, y compris aux yeux, et une neuropathie douloureuse qui ne disparaîtra jamais. Ces atteintes peuvent être évitées simplement en baissant plus lentement les niveaux. If you currently have an elevated HbA1c and are moving to AAPS (or any other closed loop system), please discuss this potential risk with your clinical team before starting, and agree a time plan with them. More general information on how to reduce your glucose levels safely, including links to medical literature is given in the safety section [here](#preparing-safety-first). #### Sûreté médicale autour des dispositifs, consommables et autres médicaments diff --git a/docs/CROWDIN/fr/GettingHelp/ProfileTuning.md b/docs/CROWDIN/fr/GettingHelp/ProfileTuning.md new file mode 100644 index 000000000000..2fc8714128f3 --- /dev/null +++ b/docs/CROWDIN/fr/GettingHelp/ProfileTuning.md @@ -0,0 +1,136 @@ +# **Tweaking the AAPS' Profile** + +```{admonition} This is NOT a medical advice +:class: warning +Please work with your care team for support and advice on your diabetes management.
+Use this guide only once you have [set up your **Profile** correctly](https://androidaps.readthedocs.io/en/latest/SettingUpAaps/YourAapsProfile.md), following all **AAPS** objectives. +``` + +This guide explains the logic of the OpenAPS algorithm results with a given __Profile__, and provides information about which values to adjust when certain situations are observed. The suggestions about basal testing below may diverge from what your care team advises + +Using **closed loop** may make basal testing easier and may significantly reduce the hypo risk if your __Profile__ basal is too strong. + +## **Changing profile's settings, how to proceed** + +1. Ensure you have read and understand __AAPS’__ recommended settings and advice below. Not following this advice will make the whole process problematic and less likely to get a well tuned __Profile__ +2. Carefully observe and compare, **over several days**, what is happening with your __BG__ and __IOB__. +3. Keep an eye out for patterns that happen around the same time (almost) everyday. +4. It's important to do this over several days. Poor results tend to be yielded from using data observed on a single day to make __Profile’s__ adjustment decisions. +5. After you have observed a repeatable pattern of behavior, e.g. at 1PM you see a spike in __BG__ or a negative __IOB__ value, only then start to make small changes to your __Profile__. +6. It's important to limit the changes you make to one thing at a time. Par ex. increase your basal by 10% around 1PM. +7. After every change, it's important to monitor the impact on your __BG__ and __IOB__ for the next few days. +8. Repeat this pattern, observe, decide, tweak again if needed + +Don't rush, go slow! + +## **Recommended settings and advice while tweaking basal** + +- Do all testing with [closed loop enabled](#AapsScreens-loop-status). +- **Turn OFF all [automations](../DailyLifeWithAAPS/Automations.md)** +- **Turn OFF [DynISF](#Open-APS-features-DynamicISF), [AutoISF](../AdvancedOptions/DevBranch.md), [AutoSens](#Open-APS-features-autosens)** so that they will not try to adapt your profile. +- Do not make manual user actions (manual bolus, temp targets etc…) while testing: let the system use the **Profile** settings only. +- For the [additional graphs](#AapsScreens-section-g-additional-graphs): on graph 1, use Insulin On Board, Carbs On Board (and Sensitivity change). On graph 2, use Deviations and Blood Glucose Impact. When asking for advice, always include those on your screenshots. +- COB=0[*](#profiletuning-cob-zero) +- No physical activities. +- No stress. +- No illness. +- No extreme weather like high or low temperatures. +- If your [basal rate profile](#your-aaps-profile-basal-rates) is correct, when you are on target with COB=0[*](#profiletuning-cob-zero) and IOB=0, you will remain constantly on target whatever your ISF (ISF is only used when you are higher than your target). +- You need to check the actual IOB but also, the IOB chart to see how the IOB was during the past few hours. + +(profiletuning-cob-zero)= + +***COB = 0** + +Meaning that the meal is digested, and there are no more carbs in your body. + +AAPS might indicate [COB=0 while you still have carbs on board](../DailyLifeWithAAPS/CobCalculation.md). + +## **[Profile](../SettingUpAaps/YourAapsProfile.md) definitions** + +A too **strong Profile** indicates some combination of the following: + +- [ISF](#insulin-sensitivity-factor-isf) number is too small +- The [basal](#basal-rates) number is too big +- [I:C](#insulin-to-carb-ratio-icr) number is too small + +## **IOB Observations** + +*Note: you can also use Loopalyzer IOB graph in Nightscout reports to view IOB on several days.* + +If you observe the following patterns after a few days, consider the following changes + +### **IOB positive** + +- **Profile** basal might not be strong enough (this could also be because of things like unannounced food, illness, bad site absorption, etc.) + +![Positive IOB](../images/troubleshooting/profiletuning/PositiveInsulin.png) + +### **IOB negative** + +- Default basal too strong +- May be the effect from past exercise/physical activity + +![Negative IOB](../images/troubleshooting/profiletuning/NegativeInsulin.png) + +- Previous meal: too much bolus (which resulted in a very long zero temp basal) + +![Negative IOB](../images/troubleshooting/profiletuning/NegativeInsulin2.png) + +## **BG Target Observations** + +### **Stuck High** + +- __ISF__ ‘s number is high and not strong enough (calculated insulin is too weak) + +![Stuck High](../images/troubleshooting/profiletuning/StuckHigh.png) + +- __Profile__ basal might not be strong enough (SMBs do not have enough "basal stock" to use) +- A security ([MaxIOB](#Open-APS-features-maximum-total-iob-openaps-cant-go-over)?) might have kicked in and is limiting insulin injection. Verify in the [SMB](#Open-APS-features-super-micro-bolus-smb) tab. +- Technical issue: site absorption, infusion set, ... + +### **Stuck Low** + +- __ISF__ too strong and the number needs to be raised higher +- __Profile__ basal too strong (if also negative IOB) + +### **Rollercoaster (ups and downs)** + +- **ISF** too strong? See your [AAPS Profile](#your-aaps-profile-insulin-sensitivity-factor) + +![Rollercoaster](../images/troubleshooting/profiletuning/StrongISF.png) + +## **BG After Meals Observations** + +### **Fast rise and BG going high** + +- Food contains fast carbs +- Consider doing a pre-bolus +- Bolus (IC or injected %) not strong enough + +![Rise High](../images/troubleshooting/profiletuning/FastRise.png) + +### **Fast rise and then BG going low** + +- Consider doing a pre-bolus, profile might be too aggressive (over correction of the raise) +- Bolus too strong + + + +## **[How to calculate your I:C](#your-aaps-profile-insulin-to-carbs-ratio)** + +1. First, you need the correct default basal settings in your **Profile**. +2. Start on target, better without negative IOB. +3. Record the total insulin given in the pump tab (or pump history) and call it Start insulin C4. Very accurately measure a known portion of carbs, and record the start time and Start IOB. Then enter carbs and bolus information into AAPS using the wizard (with the current configured CI). Don't forget to eat the carbs ;) +4. After some hours, when COB=0[*](#profiletuning-cob-zero) and you're back on target, record end time, and note down the End IOB, check the total insulin given as before and call it End insulin. *NOTE: The time frame is NOT important, as long as it is longer than your digestion* +5. From the difference between Start and End insulin amount, subtract/add the difference end IOB - start IOB. Then subtract the basal insulin calculated from your profile settings. +6. If __BG__ is in target, you'll have the total insulin used to “digest” your carbs. Calculate your **I:C**. + +### **Explanations for the I:C calculations** + +- With a **Profile** that has the correct default basal rate, during any time frame, you should stay on target and have an IOB near 0. You get your **Profile** basal only. +- You add carbs and bolus to this mix. Wait till your body digests all the carbs and be back on **BG** target. Your insulin usage will be the sum of your basal + the insulin needed for the carbs. You calculate the insulin used for your basal (by using your **Profile**) and the surplus will be the insulin used to digest the carbs. +- If the time frame is too short, there will be carbs undigested, thus your "insulin needed for the carbs" will be wrong. +- If the time frame is too long, nothing bad will happen. You'll use all your carbs and you'll get more basal. At the end, you'll subtract the basal from the total insulin used, the extended time frame (with more basal use) will not affect the result. + +Originally written up by @Robby (Discord) on tips and tricks to help tune your AAPS Profile, reviewed and edited by the community (thank you!). diff --git a/docs/CROWDIN/fr/SettingUpAaps/ComputerBuild.md b/docs/CROWDIN/fr/SettingUpAaps/ComputerBuild.md index add30ad71bff..450331d9e67d 100644 --- a/docs/CROWDIN/fr/SettingUpAaps/ComputerBuild.md +++ b/docs/CROWDIN/fr/SettingUpAaps/ComputerBuild.md @@ -70,7 +70,7 @@ The Gradle version is linked to the source code, you will always get the correct ## Aide et support pour le processus de compilation -If you run into difficulties in the process of building the **AAPS** app, there is a dedicated [**troubleshooting Android Studio**](../GettingHelp/TroubleshootingAndroidStudio) section, please consult that first. +If you run into difficulties in the process of building the **AAPS** app, there is a dedicated [**troubleshooting Android Studio**](../GettingHelp/TroubleshootingAndroidStudio.md) section, please consult that first. If you think something in the building instructions is wrong, missing or confusing, or you are still struggling, please reach out to other **AAPS** users group on [Facebook](https://www.facebook.com/groups/AndroidAPSUsers) or [Discord](https://discord.gg/4fQUWHZ4Mw). If you want to change something yourself (updating screenshots _etc_), please submit a [pull request (PR)](../SupportingAaps/HowToEditTheDocs.md). @@ -409,7 +409,7 @@ Le message "BUILD SUCCESSFUL / COMPILATION RÉUSSIE" s'affiche quand la généra ![Build finished](../images/Building-the-App/049_ReopenNotification.png) -**_If the build was not successful, refer to the [Android Studio Troubleshooting section](../GettingHelp/TroubleshootingAndroidStudio)._** +**_If the build was not successful, refer to the [Android Studio Troubleshooting section](../GettingHelp/TroubleshootingAndroidStudio.md)._** Dans la fenêtre des notifications, cliquez sur le lien bleu "locate/trouver" : diff --git a/docs/CROWDIN/fr/SettingUpAaps/Preferences.md b/docs/CROWDIN/fr/SettingUpAaps/Preferences.md index d8c981923dbe..ad754b17d127 100644 --- a/docs/CROWDIN/fr/SettingUpAaps/Preferences.md +++ b/docs/CROWDIN/fr/SettingUpAaps/Preferences.md @@ -300,7 +300,7 @@ Switch between Open Loop, Closed Loop and Low Glucose Suspend (LGS). ![Config builder - loop mode](../images/ConfigBuilder_LoopLGS.png) -(Preferences-pen-loop)= +(Preferences-open-loop)= #### Open Loop **AAPS** continuously evaluates all available data (IOB, COB, BG...) and makes treatment suggestions (temporary basal rates) on how to adjust your therapy if necessary. diff --git a/docs/CROWDIN/fr/SettingUpAaps/YourAapsProfile.md b/docs/CROWDIN/fr/SettingUpAaps/YourAapsProfile.md index 5790a031a468..bb2c67ffe345 100644 --- a/docs/CROWDIN/fr/SettingUpAaps/YourAapsProfile.md +++ b/docs/CROWDIN/fr/SettingUpAaps/YourAapsProfile.md @@ -123,11 +123,13 @@ The **figure below** shows an example of how the basal rates can be set in an ** Setting your basal rates right is done by trial and error, and should be done in consultation with your diabetic team. -There are basal testing methods which usually entails observing your basal rates and insulin needs during an intermittent fasting over a 24-hour period. Although you need to test your basal rates for the whole day, it is not recommended to fast during 24h straight. This is because the body triggers mechanisms such as hormones to compensate. A recommended way is to fast 3 times for 8 hours. +There are basal testing methods which usually entails observing your basal rates and insulin needs during an intermittent fasting over a 24-hour period. Although you need to test your basal rates for the whole day, it is not recommended to fast during 24h straight. This is because the body triggers mechanisms such as hormones to compensate. A recommended way is to fast 3 times for 8 hours. -The recommended method is to suspend the loop, which will revert to your default background basal rate. Observe how your **BG** changes: if it is dropping, basal rate is too high. And vice versa.
An alternative method (may be more tricky) is to keep the loop running, and seeing how **IOB** changes. If **IOB** is negative, your basal rate is too high. And vice versa. Beware that this method relies on **ISF** to correct **BG**, and thus depends on other variables to be set reasonably well for it to be successful.
Another way of adjusting your basal rates is to watch the loop action during the night, when all COB have decayed. This method is particularly useful for children, when fasting is difficult or insulin needs change often. [Dr Saleh Adi from Tidepool](https://www.youtube.com/watch?v=-fpWnGRhLSo) provides useful ways on how to analyse overnight BG lines in order to optimise your basal rates. +The recommended method is to suspend the loop (for safety you can set AAPS to [**LGS**](#Preferences-aps-mode) to avoid lows, as done for achieving [objective 6](#objectives-objective6)), which will revert to your default background basal rate. Observe how your **BG** changes: if it is dropping, basal rate is too high. And vice versa.
An alternative method (may be more tricky) is to keep the loop running, and seeing how **IOB** changes. If **IOB** is negative, your basal rate is too high. And vice versa. Beware that this method relies on **ISF** to correct **BG**, and thus depends on other variables to be set reasonably well for it to be successful.
Another way of adjusting your basal rates is to watch the loop action during the night, when all COB have decayed. This method is particularly useful for children, when fasting is difficult or insulin needs change often. [Dr Saleh Adi from Tidepool](https://www.youtube.com/watch?v=-fpWnGRhLSo) provides useful ways on how to analyze overnight BG lines in order to optimize your basal rates. -When taking action on the result of your basal testing, changes in the **Profile** should be done 1 hour before the rise/drop. Repeat the test as necessary until you are comfortable with your **basal rates** settings. +See [here](../GettingHelp/ProfileTuning.md) how to tweak your basal profile, analyzing patterns in closed loop. + +When taking action on the result of your basal testing, changes in the **Profile** should be done 1 to 2 hours (depends on your insulin type) before the rise/drop. Repeat the test as necessary until you are comfortable with your **basal rates** settings. (your-aaps-profile-insulin-sensitivity-factor)= diff --git a/docs/CROWDIN/fr/SupportingAaps/HowCanIHelp.md b/docs/CROWDIN/fr/SupportingAaps/HowCanIHelp.md index d7032b78be4e..26be1b65d4cf 100644 --- a/docs/CROWDIN/fr/SupportingAaps/HowCanIHelp.md +++ b/docs/CROWDIN/fr/SupportingAaps/HowCanIHelp.md @@ -15,7 +15,7 @@ Yeh ! Regardez les problèmes ("Issues"), demandez dans "discord", il y a toujou Excellent, c'est une chose très appréciée et une bonne façon de contribuer ! * Le canal de discord concernant la doc se trouve ici : [AndroidAPS](https://discord.gg/4fQUWHZ4Mw). -* A guide how to do commits on English wiki can be found here: [How to make a PR](../SupportingAaps/HowToEditTheDocs.md). Les autres langues ne sont que traduites de l'anglais et ne peuvent pas être éditées indépendamment pour des raisons de cohérence. +* A guide how to do commits on English wiki can be found here: [How to make a PR](../SupportingAaps/HowToEditTheDocs.md). Other languages are only translated from English and can't be edited for consistency reasons. ## Je parle plusieurs langues et je veux traduire l'application ou la documentation @@ -23,7 +23,7 @@ Si vous traduisez pour la première fois, veuillez commencer par traduire les ch Vous pouvez commencer en tant que traducteur pour la documentation en parallèle ou plus tard. -You can check the state of translations for the languages app and documentation [here](StateOfTranslations). +You can check the state of translations for the languages app and documentation [here](#StateOfTranslations). * Si vous voulez traduire **l'application** dans d'autres langues (merci), utilisez [crowdin](https://crowdin.com/project/androidaps). * Si vous voulez traduire la **documentation** dans d'autres langues (merci), utilisez [crowdin](https://crowdin.com/project/androidapsdocs). diff --git a/docs/CROWDIN/fr/UsefulLinks/FAQ.md b/docs/CROWDIN/fr/UsefulLinks/FAQ.md index 277b99b82ed0..510840f0a0f2 100644 --- a/docs/CROWDIN/fr/UsefulLinks/FAQ.md +++ b/docs/CROWDIN/fr/UsefulLinks/FAQ.md @@ -247,7 +247,7 @@ Copiez sur un lecteur internet (Dropbox, Google etc) : toutes les apks que vous Veuillez -- check [Troubleshooting Android Studio](../GettingHelp/TroubleshootingAndroidStudio) for typical errors and +- check [Troubleshooting Android Studio](../GettingHelp/TroubleshootingAndroidStudio.md) for typical errors and - suivre les conseils pour un accompagnement [pas à pas](https://docs.google.com/document/d/1oc7aG0qrIMvK57unMqPEOoLt-J8UT1mxTKdTAxm8-po). ### I'm stuck on an objective and need help. diff --git a/docs/CROWDIN/fr/images/troubleshooting/profiletuning/FastRise.png b/docs/CROWDIN/fr/images/troubleshooting/profiletuning/FastRise.png new file mode 100644 index 000000000000..ba35b5bb6bf0 Binary files /dev/null and b/docs/CROWDIN/fr/images/troubleshooting/profiletuning/FastRise.png differ diff --git a/docs/CROWDIN/fr/images/troubleshooting/profiletuning/NegativeInsulin.png b/docs/CROWDIN/fr/images/troubleshooting/profiletuning/NegativeInsulin.png new file mode 100644 index 000000000000..7c39c50d00df Binary files /dev/null and b/docs/CROWDIN/fr/images/troubleshooting/profiletuning/NegativeInsulin.png differ diff --git a/docs/CROWDIN/fr/images/troubleshooting/profiletuning/NegativeInsulin2.png b/docs/CROWDIN/fr/images/troubleshooting/profiletuning/NegativeInsulin2.png new file mode 100644 index 000000000000..4bd840d597ad Binary files /dev/null and b/docs/CROWDIN/fr/images/troubleshooting/profiletuning/NegativeInsulin2.png differ diff --git a/docs/CROWDIN/fr/images/troubleshooting/profiletuning/PositiveInsulin.png b/docs/CROWDIN/fr/images/troubleshooting/profiletuning/PositiveInsulin.png new file mode 100644 index 000000000000..e50e806ebf01 Binary files /dev/null and b/docs/CROWDIN/fr/images/troubleshooting/profiletuning/PositiveInsulin.png differ diff --git a/docs/CROWDIN/fr/images/troubleshooting/profiletuning/StrongISF.png b/docs/CROWDIN/fr/images/troubleshooting/profiletuning/StrongISF.png new file mode 100644 index 000000000000..ca16a1ad1b9d Binary files /dev/null and b/docs/CROWDIN/fr/images/troubleshooting/profiletuning/StrongISF.png differ diff --git a/docs/CROWDIN/fr/images/troubleshooting/profiletuning/StuckHigh.png b/docs/CROWDIN/fr/images/troubleshooting/profiletuning/StuckHigh.png new file mode 100644 index 000000000000..1fbeefc01c50 Binary files /dev/null and b/docs/CROWDIN/fr/images/troubleshooting/profiletuning/StuckHigh.png differ diff --git a/docs/CROWDIN/fr/index.md b/docs/CROWDIN/fr/index.md index 7b7ac138b0f2..9a0cf6299506 100644 --- a/docs/CROWDIN/fr/index.md +++ b/docs/CROWDIN/fr/index.md @@ -159,6 +159,7 @@ Updating to a new version of AAPS <./Maintenance/UpdateToNewVersion.md> Where can I get help with AAPS <./GettingHelp/WhereCanIGetHelp.md> General troubleshooting <./GettingHelp/GeneralTroubleshooting.md> - Bluetooth troubleshooting <./GettingHelp/BluetoothTroubleshooting.md> +Profile Tuning Guide <./GettingHelp/ProfileTuning.md> Troubleshooting Android Studio <./GettingHelp/TroubleshootingAndroidStudio.md> Accessing logfiles <./GettingHelp/AccessingLogFiles.md> ``` diff --git a/docs/CROWDIN/he/Getting-Started/Introduction.md b/docs/CROWDIN/he/Getting-Started/Introduction.md index 052f440d6da9..4fbd82ac3cef 100644 --- a/docs/CROWDIN/he/Getting-Started/Introduction.md +++ b/docs/CROWDIN/he/Getting-Started/Introduction.md @@ -192,7 +192,7 @@ If a malicious attack was made on your insulin pump, these strategies would sign #### Safety considerations around improving blood glucose control too fast -A rapid reduction in HbA1c and improved blood glucose control sounds appealing. However, reducing average blood glucose levels _too fast_ by starting any closed loop system can cause permanent damage, including to the eyes, and painful neuropathy that never goes away. This damage can be avoided simply by reducing levels more slowly. If you currently have an elevated HbA1c and are moving to AAPS (or any other closed loop system), please discuss this potential risk with your clinical team before starting, and agree a timeplan with them. More general information on how to reduce your glucose levels safely, including links to medical literature is given in the [safety section [here](#preparing-safety-first). +A rapid reduction in HbA1c and improved blood glucose control sounds appealing. However, reducing average blood glucose levels _too fast_ by starting any closed loop system can cause permanent damage, including to the eyes, and painful neuropathy that never goes away. This damage can be avoided simply by reducing levels more slowly. If you currently have an elevated HbA1c and are moving to AAPS (or any other closed loop system), please discuss this potential risk with your clinical team before starting, and agree a time plan with them. More general information on how to reduce your glucose levels safely, including links to medical literature is given in the safety section [here](#preparing-safety-first). #### Medical safety around devices, consumable supplies and other medications diff --git a/docs/CROWDIN/he/GettingHelp/ProfileTuning.md b/docs/CROWDIN/he/GettingHelp/ProfileTuning.md new file mode 100644 index 000000000000..566fc5f5c43b --- /dev/null +++ b/docs/CROWDIN/he/GettingHelp/ProfileTuning.md @@ -0,0 +1,136 @@ +# **Tweaking the AAPS' Profile** + +```{admonition} This is NOT a medical advice +:class: warning +Please work with your care team for support and advice on your diabetes management.
+Use this guide only once you have [set up your **Profile** correctly](https://androidaps.readthedocs.io/en/latest/SettingUpAaps/YourAapsProfile.md), following all **AAPS** objectives. +``` + +This guide explains the logic of the OpenAPS algorithm results with a given __Profile__, and provides information about which values to adjust when certain situations are observed. The suggestions about basal testing below may diverge from what your care team advises + +Using **closed loop** may make basal testing easier and may significantly reduce the hypo risk if your __Profile__ basal is too strong. + +## **Changing profile's settings, how to proceed** + +1. Ensure you have read and understand __AAPS’__ recommended settings and advice below. Not following this advice will make the whole process problematic and less likely to get a well tuned __Profile__ +2. Carefully observe and compare, **over several days**, what is happening with your __BG__ and __IOB__. +3. Keep an eye out for patterns that happen around the same time (almost) everyday. +4. It's important to do this over several days. Poor results tend to be yielded from using data observed on a single day to make __Profile’s__ adjustment decisions. +5. After you have observed a repeatable pattern of behavior, e.g. at 1PM you see a spike in __BG__ or a negative __IOB__ value, only then start to make small changes to your __Profile__. +6. It's important to limit the changes you make to one thing at a time. E.g. increase your basal by 10% around 1PM. +7. After every change, it's important to monitor the impact on your __BG__ and __IOB__ for the next few days. +8. Repeat this pattern, observe, decide, tweak again if needed + +Don't rush, go slow! + +## **Recommended settings and advice while tweaking basal** + +- Do all testing with [closed loop enabled](#AapsScreens-loop-status). +- **Turn OFF all [automations](../DailyLifeWithAAPS/Automations.md)** +- **Turn OFF [DynISF](#Open-APS-features-DynamicISF), [AutoISF](../AdvancedOptions/DevBranch.md), [AutoSens](#Open-APS-features-autosens)** so that they will not try to adapt your profile. +- Do not make manual user actions (manual bolus, temp targets etc…) while testing: let the system use the **Profile** settings only. +- For the [additional graphs](#AapsScreens-section-g-additional-graphs): on graph 1, use Insulin On Board, Carbs On Board (and Sensitivity change). On graph 2, use Deviations and Blood Glucose Impact. When asking for advice, always include those on your screenshots. +- COB=0[*](#profiletuning-cob-zero) +- No physical activities. +- No stress. +- No illness. +- No extreme weather like high or low temperatures. +- If your [basal rate profile](#your-aaps-profile-basal-rates) is correct, when you are on target with COB=0[*](#profiletuning-cob-zero) and IOB=0, you will remain constantly on target whatever your ISF (ISF is only used when you are higher than your target). +- You need to check the actual IOB but also, the IOB chart to see how the IOB was during the past few hours. + +(profiletuning-cob-zero)= + +***COB = 0** + +Meaning that the meal is digested, and there are no more carbs in your body. + +AAPS might indicate [COB=0 while you still have carbs on board](../DailyLifeWithAAPS/CobCalculation.md). + +## **[Profile](../SettingUpAaps/YourAapsProfile.md) definitions** + +A too **strong Profile** indicates some combination of the following: + +- [ISF](#insulin-sensitivity-factor-isf) number is too small +- The [basal](#basal-rates) number is too big +- [I:C](#insulin-to-carb-ratio-icr) number is too small + +## **IOB Observations** + +*Note: you can also use Loopalyzer IOB graph in Nightscout reports to view IOB on several days.* + +If you observe the following patterns after a few days, consider the following changes + +### **IOB positive** + +- **Profile** basal might not be strong enough (this could also be because of things like unannounced food, illness, bad site absorption, etc.) + +![Positive IOB](../images/troubleshooting/profiletuning/PositiveInsulin.png) + +### **IOB negative** + +- Default basal too strong +- May be the effect from past exercise/physical activity + +![Negative IOB](../images/troubleshooting/profiletuning/NegativeInsulin.png) + +- Previous meal: too much bolus (which resulted in a very long zero temp basal) + +![Negative IOB](../images/troubleshooting/profiletuning/NegativeInsulin2.png) + +## **BG Target Observations** + +### **Stuck High** + +- __ISF__ ‘s number is high and not strong enough (calculated insulin is too weak) + +![Stuck High](../images/troubleshooting/profiletuning/StuckHigh.png) + +- __Profile__ basal might not be strong enough (SMBs do not have enough "basal stock" to use) +- A security ([MaxIOB](#Open-APS-features-maximum-total-iob-openaps-cant-go-over)?) might have kicked in and is limiting insulin injection. Verify in the [SMB](#Open-APS-features-super-micro-bolus-smb) tab. +- Technical issue: site absorption, infusion set, ... + +### **Stuck Low** + +- __ISF__ too strong and the number needs to be raised higher +- __Profile__ basal too strong (if also negative IOB) + +### **Rollercoaster (ups and downs)** + +- **ISF** too strong? See your [AAPS Profile](#your-aaps-profile-insulin-sensitivity-factor) + +![Rollercoaster](../images/troubleshooting/profiletuning/StrongISF.png) + +## **BG After Meals Observations** + +### **Fast rise and BG going high** + +- Food contains fast carbs +- Consider doing a pre-bolus +- Bolus (IC or injected %) not strong enough + +![Rise High](../images/troubleshooting/profiletuning/FastRise.png) + +### **Fast rise and then BG going low** + +- Consider doing a pre-bolus, profile might be too aggressive (over correction of the raise) +- Bolus too strong + + + +## **[How to calculate your I:C](#your-aaps-profile-insulin-to-carbs-ratio)** + +1. First, you need the correct default basal settings in your **Profile**. +2. Start on target, better without negative IOB. +3. Record the total insulin given in the pump tab (or pump history) and call it Start insulin C4. Very accurately measure a known portion of carbs, and record the start time and Start IOB. Then enter carbs and bolus information into AAPS using the wizard (with the current configured CI). Don't forget to eat the carbs ;) +4. After some hours, when COB=0[*](#profiletuning-cob-zero) and you're back on target, record end time, and note down the End IOB, check the total insulin given as before and call it End insulin. *NOTE: The time frame is NOT important, as long as it is longer than your digestion* +5. From the difference between Start and End insulin amount, subtract/add the difference end IOB - start IOB. Then subtract the basal insulin calculated from your profile settings. +6. If __BG__ is in target, you'll have the total insulin used to “digest” your carbs. Calculate your **I:C**. + +### **Explanations for the I:C calculations** + +- With a **Profile** that has the correct default basal rate, during any time frame, you should stay on target and have an IOB near 0. You get your **Profile** basal only. +- You add carbs and bolus to this mix. Wait till your body digests all the carbs and be back on **BG** target. Your insulin usage will be the sum of your basal + the insulin needed for the carbs. You calculate the insulin used for your basal (by using your **Profile**) and the surplus will be the insulin used to digest the carbs. +- If the time frame is too short, there will be carbs undigested, thus your "insulin needed for the carbs" will be wrong. +- If the time frame is too long, nothing bad will happen. You'll use all your carbs and you'll get more basal. At the end, you'll subtract the basal from the total insulin used, the extended time frame (with more basal use) will not affect the result. + +Originally written up by @Robby (Discord) on tips and tricks to help tune your AAPS Profile, reviewed and edited by the community (thank you!). diff --git a/docs/CROWDIN/he/SettingUpAaps/ComputerBuild.md b/docs/CROWDIN/he/SettingUpAaps/ComputerBuild.md index 627d5ac754fd..3fa5c30f9739 100644 --- a/docs/CROWDIN/he/SettingUpAaps/ComputerBuild.md +++ b/docs/CROWDIN/he/SettingUpAaps/ComputerBuild.md @@ -70,7 +70,7 @@ The Gradle version is linked to the source code, you will always get the correct ## Help and support during the building process -If you run into difficulties in the process of building the **AAPS** app, there is a dedicated [**troubleshooting Android Studio**](../GettingHelp/TroubleshootingAndroidStudio) section, please consult that first. +If you run into difficulties in the process of building the **AAPS** app, there is a dedicated [**troubleshooting Android Studio**](../GettingHelp/TroubleshootingAndroidStudio.md) section, please consult that first. If you think something in the building instructions is wrong, missing or confusing, or you are still struggling, please reach out to other **AAPS** users group on [Facebook](https://www.facebook.com/groups/AndroidAPSUsers) or [Discord](https://discord.gg/4fQUWHZ4Mw). If you want to change something yourself (updating screenshots _etc_), please submit a [pull request (PR)](../SupportingAaps/HowToEditTheDocs.md). @@ -409,7 +409,7 @@ Android Studio will display the information "BUILD SUCCESSFUL" after build is fi ![Build finished](../images/Building-the-App/049_ReopenNotification.png) -**_If the build was not successful, refer to the [Android Studio Troubleshooting section](../GettingHelp/TroubleshootingAndroidStudio)._** +**_If the build was not successful, refer to the [Android Studio Troubleshooting section](../GettingHelp/TroubleshootingAndroidStudio.md)._** In the Notifications box, click on the blue link "locate": diff --git a/docs/CROWDIN/he/SettingUpAaps/Preferences.md b/docs/CROWDIN/he/SettingUpAaps/Preferences.md index 28147ce782cf..62923730fd58 100644 --- a/docs/CROWDIN/he/SettingUpAaps/Preferences.md +++ b/docs/CROWDIN/he/SettingUpAaps/Preferences.md @@ -300,7 +300,7 @@ Switch between Open Loop, Closed Loop and Low Glucose Suspend (LGS). ![Config builder - loop mode](../images/ConfigBuilder_LoopLGS.png) -(Preferences-pen-loop)= +(Preferences-open-loop)= #### Open Loop **AAPS** continuously evaluates all available data (IOB, COB, BG...) and makes treatment suggestions (temporary basal rates) on how to adjust your therapy if necessary. diff --git a/docs/CROWDIN/he/SettingUpAaps/YourAapsProfile.md b/docs/CROWDIN/he/SettingUpAaps/YourAapsProfile.md index b85c7e377366..c8b80569d9f6 100644 --- a/docs/CROWDIN/he/SettingUpAaps/YourAapsProfile.md +++ b/docs/CROWDIN/he/SettingUpAaps/YourAapsProfile.md @@ -123,11 +123,13 @@ The **figure below** shows an example of how the basal rates can be set in an ** Setting your basal rates right is done by trial and error, and should be done in consultation with your diabetic team. -There are basal testing methods which usually entails observing your basal rates and insulin needs during an intermittent fasting over a 24-hour period. Although you need to test your basal rates for the whole day, it is not recommended to fast during 24h straight. This is because the body triggers mechanisms such as hormones to compensate. A recommended way is to fast 3 times for 8 hours. +There are basal testing methods which usually entails observing your basal rates and insulin needs during an intermittent fasting over a 24-hour period. Although you need to test your basal rates for the whole day, it is not recommended to fast during 24h straight. This is because the body triggers mechanisms such as hormones to compensate. A recommended way is to fast 3 times for 8 hours. -The recommended method is to suspend the loop, which will revert to your default background basal rate. Observe how your **BG** changes: if it is dropping, basal rate is too high. And vice versa.
An alternative method (may be more tricky) is to keep the loop running, and seeing how **IOB** changes. If **IOB** is negative, your basal rate is too high. And vice versa. Beware that this method relies on **ISF** to correct **BG**, and thus depends on other variables to be set reasonably well for it to be successful.
Another way of adjusting your basal rates is to watch the loop action during the night, when all COB have decayed. This method is particularly useful for children, when fasting is difficult or insulin needs change often. [Dr Saleh Adi from Tidepool](https://www.youtube.com/watch?v=-fpWnGRhLSo) provides useful ways on how to analyse overnight BG lines in order to optimise your basal rates. +The recommended method is to suspend the loop (for safety you can set AAPS to [**LGS**](#Preferences-aps-mode) to avoid lows, as done for achieving [objective 6](#objectives-objective6)), which will revert to your default background basal rate. Observe how your **BG** changes: if it is dropping, basal rate is too high. And vice versa.
An alternative method (may be more tricky) is to keep the loop running, and seeing how **IOB** changes. If **IOB** is negative, your basal rate is too high. And vice versa. Beware that this method relies on **ISF** to correct **BG**, and thus depends on other variables to be set reasonably well for it to be successful.
Another way of adjusting your basal rates is to watch the loop action during the night, when all COB have decayed. This method is particularly useful for children, when fasting is difficult or insulin needs change often. [Dr Saleh Adi from Tidepool](https://www.youtube.com/watch?v=-fpWnGRhLSo) provides useful ways on how to analyze overnight BG lines in order to optimize your basal rates. -When taking action on the result of your basal testing, changes in the **Profile** should be done 1 hour before the rise/drop. Repeat the test as necessary until you are comfortable with your **basal rates** settings. +See [here](../GettingHelp/ProfileTuning.md) how to tweak your basal profile, analyzing patterns in closed loop. + +When taking action on the result of your basal testing, changes in the **Profile** should be done 1 to 2 hours (depends on your insulin type) before the rise/drop. Repeat the test as necessary until you are comfortable with your **basal rates** settings. (your-aaps-profile-insulin-sensitivity-factor)= diff --git a/docs/CROWDIN/he/SupportingAaps/HowCanIHelp.md b/docs/CROWDIN/he/SupportingAaps/HowCanIHelp.md index 6aeca540f5b9..7b90cca588fd 100644 --- a/docs/CROWDIN/he/SupportingAaps/HowCanIHelp.md +++ b/docs/CROWDIN/he/SupportingAaps/HowCanIHelp.md @@ -15,7 +15,7 @@ Yay! Look at the issues, ask in the discord channel, there is always a lot to do Great, this is a highly appreciated thing and a good way to pay it forward! * The discord channel regarding the wiki can be found here: [AndroidAPS](https://discord.gg/4fQUWHZ4Mw). -* A guide how to do commits on English wiki can be found here: [How to make a PR](../SupportingAaps/HowToEditTheDocs.md). Other languages are only translated from english and can't be edited for consistency reasons. +* A guide how to do commits on English wiki can be found here: [How to make a PR](../SupportingAaps/HowToEditTheDocs.md). Other languages are only translated from English and can't be edited for consistency reasons. ## I do speak multiple languages and want to translate the app or the documentation @@ -23,7 +23,7 @@ If you are translating something for the first time, please start with translati You are welcome to start as a translator for the documentation in parallel or later. -You can check the state of translations for the languages app and documentation [here](StateOfTranslations). +You can check the state of translations for the languages app and documentation [here](#StateOfTranslations). * If you want to translate **the app** to other languages (thank you), please use [crowdin](https://crowdin.com/project/androidaps). * If you want to translate **the docs** to other languages (thank you), please use [crowdin](https://crowdin.com/project/androidapsdocs). diff --git a/docs/CROWDIN/he/UsefulLinks/FAQ.md b/docs/CROWDIN/he/UsefulLinks/FAQ.md index ff7b2593d92c..9310cf43ceca 100644 --- a/docs/CROWDIN/he/UsefulLinks/FAQ.md +++ b/docs/CROWDIN/he/UsefulLinks/FAQ.md @@ -247,7 +247,7 @@ If you want to share some information about AAPS and DIY looping with your clini Please -- check [Troubleshooting Android Studio](../GettingHelp/TroubleshootingAndroidStudio) for typical errors and +- check [Troubleshooting Android Studio](../GettingHelp/TroubleshootingAndroidStudio.md) for typical errors and - הטיפים שב[מדריך הבניה, שלב אחר שלב](https://docs.google.com/document/d/1oc7aG0qrIMvK57unMqPEOoLt-J8UT1mxTKdTAxm8-po). ### I'm stuck on an objective and need help. diff --git a/docs/CROWDIN/he/images/troubleshooting/profiletuning/FastRise.png b/docs/CROWDIN/he/images/troubleshooting/profiletuning/FastRise.png new file mode 100644 index 000000000000..ba35b5bb6bf0 Binary files /dev/null and b/docs/CROWDIN/he/images/troubleshooting/profiletuning/FastRise.png differ diff --git a/docs/CROWDIN/he/images/troubleshooting/profiletuning/NegativeInsulin.png b/docs/CROWDIN/he/images/troubleshooting/profiletuning/NegativeInsulin.png new file mode 100644 index 000000000000..7c39c50d00df Binary files /dev/null and b/docs/CROWDIN/he/images/troubleshooting/profiletuning/NegativeInsulin.png differ diff --git a/docs/CROWDIN/he/images/troubleshooting/profiletuning/NegativeInsulin2.png b/docs/CROWDIN/he/images/troubleshooting/profiletuning/NegativeInsulin2.png new file mode 100644 index 000000000000..4bd840d597ad Binary files /dev/null and b/docs/CROWDIN/he/images/troubleshooting/profiletuning/NegativeInsulin2.png differ diff --git a/docs/CROWDIN/he/images/troubleshooting/profiletuning/PositiveInsulin.png b/docs/CROWDIN/he/images/troubleshooting/profiletuning/PositiveInsulin.png new file mode 100644 index 000000000000..e50e806ebf01 Binary files /dev/null and b/docs/CROWDIN/he/images/troubleshooting/profiletuning/PositiveInsulin.png differ diff --git a/docs/CROWDIN/he/images/troubleshooting/profiletuning/StrongISF.png b/docs/CROWDIN/he/images/troubleshooting/profiletuning/StrongISF.png new file mode 100644 index 000000000000..ca16a1ad1b9d Binary files /dev/null and b/docs/CROWDIN/he/images/troubleshooting/profiletuning/StrongISF.png differ diff --git a/docs/CROWDIN/he/images/troubleshooting/profiletuning/StuckHigh.png b/docs/CROWDIN/he/images/troubleshooting/profiletuning/StuckHigh.png new file mode 100644 index 000000000000..1fbeefc01c50 Binary files /dev/null and b/docs/CROWDIN/he/images/troubleshooting/profiletuning/StuckHigh.png differ diff --git a/docs/CROWDIN/he/index.md b/docs/CROWDIN/he/index.md index 4a68c3da4a06..45f0cb8f2227 100644 --- a/docs/CROWDIN/he/index.md +++ b/docs/CROWDIN/he/index.md @@ -162,6 +162,7 @@ Updating to a new version of AAPS <./Maintenance/UpdateToNewVersion.md> Where can I get help with AAPS <./GettingHelp/WhereCanIGetHelp.md> General troubleshooting <./GettingHelp/GeneralTroubleshooting.md> - Bluetooth troubleshooting <./GettingHelp/BluetoothTroubleshooting.md> +Profile Tuning Guide <./GettingHelp/ProfileTuning.md> Troubleshooting Android Studio <./GettingHelp/TroubleshootingAndroidStudio.md> Accessing logfiles <./GettingHelp/AccessingLogFiles.md> ``` diff --git a/docs/CROWDIN/ko/Getting-Started/Introduction.md b/docs/CROWDIN/ko/Getting-Started/Introduction.md index 5a025cb2a97a..1d89a35238c6 100644 --- a/docs/CROWDIN/ko/Getting-Started/Introduction.md +++ b/docs/CROWDIN/ko/Getting-Started/Introduction.md @@ -192,7 +192,7 @@ If a malicious attack was made on your insulin pump, these strategies would sign #### Safety considerations around improving blood glucose control too fast -A rapid reduction in HbA1c and improved blood glucose control sounds appealing. However, reducing average blood glucose levels _too fast_ by starting any closed loop system can cause permanent damage, including to the eyes, and painful neuropathy that never goes away. This damage can be avoided simply by reducing levels more slowly. If you currently have an elevated HbA1c and are moving to AAPS (or any other closed loop system), please discuss this potential risk with your clinical team before starting, and agree a timeplan with them. More general information on how to reduce your glucose levels safely, including links to medical literature is given in the [safety section [here](#preparing-safety-first). +A rapid reduction in HbA1c and improved blood glucose control sounds appealing. However, reducing average blood glucose levels _too fast_ by starting any closed loop system can cause permanent damage, including to the eyes, and painful neuropathy that never goes away. This damage can be avoided simply by reducing levels more slowly. If you currently have an elevated HbA1c and are moving to AAPS (or any other closed loop system), please discuss this potential risk with your clinical team before starting, and agree a time plan with them. More general information on how to reduce your glucose levels safely, including links to medical literature is given in the safety section [here](#preparing-safety-first). #### Medical safety around devices, consumable supplies and other medications diff --git a/docs/CROWDIN/ko/GettingHelp/ProfileTuning.md b/docs/CROWDIN/ko/GettingHelp/ProfileTuning.md new file mode 100644 index 000000000000..566fc5f5c43b --- /dev/null +++ b/docs/CROWDIN/ko/GettingHelp/ProfileTuning.md @@ -0,0 +1,136 @@ +# **Tweaking the AAPS' Profile** + +```{admonition} This is NOT a medical advice +:class: warning +Please work with your care team for support and advice on your diabetes management.
+Use this guide only once you have [set up your **Profile** correctly](https://androidaps.readthedocs.io/en/latest/SettingUpAaps/YourAapsProfile.md), following all **AAPS** objectives. +``` + +This guide explains the logic of the OpenAPS algorithm results with a given __Profile__, and provides information about which values to adjust when certain situations are observed. The suggestions about basal testing below may diverge from what your care team advises + +Using **closed loop** may make basal testing easier and may significantly reduce the hypo risk if your __Profile__ basal is too strong. + +## **Changing profile's settings, how to proceed** + +1. Ensure you have read and understand __AAPS’__ recommended settings and advice below. Not following this advice will make the whole process problematic and less likely to get a well tuned __Profile__ +2. Carefully observe and compare, **over several days**, what is happening with your __BG__ and __IOB__. +3. Keep an eye out for patterns that happen around the same time (almost) everyday. +4. It's important to do this over several days. Poor results tend to be yielded from using data observed on a single day to make __Profile’s__ adjustment decisions. +5. After you have observed a repeatable pattern of behavior, e.g. at 1PM you see a spike in __BG__ or a negative __IOB__ value, only then start to make small changes to your __Profile__. +6. It's important to limit the changes you make to one thing at a time. E.g. increase your basal by 10% around 1PM. +7. After every change, it's important to monitor the impact on your __BG__ and __IOB__ for the next few days. +8. Repeat this pattern, observe, decide, tweak again if needed + +Don't rush, go slow! + +## **Recommended settings and advice while tweaking basal** + +- Do all testing with [closed loop enabled](#AapsScreens-loop-status). +- **Turn OFF all [automations](../DailyLifeWithAAPS/Automations.md)** +- **Turn OFF [DynISF](#Open-APS-features-DynamicISF), [AutoISF](../AdvancedOptions/DevBranch.md), [AutoSens](#Open-APS-features-autosens)** so that they will not try to adapt your profile. +- Do not make manual user actions (manual bolus, temp targets etc…) while testing: let the system use the **Profile** settings only. +- For the [additional graphs](#AapsScreens-section-g-additional-graphs): on graph 1, use Insulin On Board, Carbs On Board (and Sensitivity change). On graph 2, use Deviations and Blood Glucose Impact. When asking for advice, always include those on your screenshots. +- COB=0[*](#profiletuning-cob-zero) +- No physical activities. +- No stress. +- No illness. +- No extreme weather like high or low temperatures. +- If your [basal rate profile](#your-aaps-profile-basal-rates) is correct, when you are on target with COB=0[*](#profiletuning-cob-zero) and IOB=0, you will remain constantly on target whatever your ISF (ISF is only used when you are higher than your target). +- You need to check the actual IOB but also, the IOB chart to see how the IOB was during the past few hours. + +(profiletuning-cob-zero)= + +***COB = 0** + +Meaning that the meal is digested, and there are no more carbs in your body. + +AAPS might indicate [COB=0 while you still have carbs on board](../DailyLifeWithAAPS/CobCalculation.md). + +## **[Profile](../SettingUpAaps/YourAapsProfile.md) definitions** + +A too **strong Profile** indicates some combination of the following: + +- [ISF](#insulin-sensitivity-factor-isf) number is too small +- The [basal](#basal-rates) number is too big +- [I:C](#insulin-to-carb-ratio-icr) number is too small + +## **IOB Observations** + +*Note: you can also use Loopalyzer IOB graph in Nightscout reports to view IOB on several days.* + +If you observe the following patterns after a few days, consider the following changes + +### **IOB positive** + +- **Profile** basal might not be strong enough (this could also be because of things like unannounced food, illness, bad site absorption, etc.) + +![Positive IOB](../images/troubleshooting/profiletuning/PositiveInsulin.png) + +### **IOB negative** + +- Default basal too strong +- May be the effect from past exercise/physical activity + +![Negative IOB](../images/troubleshooting/profiletuning/NegativeInsulin.png) + +- Previous meal: too much bolus (which resulted in a very long zero temp basal) + +![Negative IOB](../images/troubleshooting/profiletuning/NegativeInsulin2.png) + +## **BG Target Observations** + +### **Stuck High** + +- __ISF__ ‘s number is high and not strong enough (calculated insulin is too weak) + +![Stuck High](../images/troubleshooting/profiletuning/StuckHigh.png) + +- __Profile__ basal might not be strong enough (SMBs do not have enough "basal stock" to use) +- A security ([MaxIOB](#Open-APS-features-maximum-total-iob-openaps-cant-go-over)?) might have kicked in and is limiting insulin injection. Verify in the [SMB](#Open-APS-features-super-micro-bolus-smb) tab. +- Technical issue: site absorption, infusion set, ... + +### **Stuck Low** + +- __ISF__ too strong and the number needs to be raised higher +- __Profile__ basal too strong (if also negative IOB) + +### **Rollercoaster (ups and downs)** + +- **ISF** too strong? See your [AAPS Profile](#your-aaps-profile-insulin-sensitivity-factor) + +![Rollercoaster](../images/troubleshooting/profiletuning/StrongISF.png) + +## **BG After Meals Observations** + +### **Fast rise and BG going high** + +- Food contains fast carbs +- Consider doing a pre-bolus +- Bolus (IC or injected %) not strong enough + +![Rise High](../images/troubleshooting/profiletuning/FastRise.png) + +### **Fast rise and then BG going low** + +- Consider doing a pre-bolus, profile might be too aggressive (over correction of the raise) +- Bolus too strong + + + +## **[How to calculate your I:C](#your-aaps-profile-insulin-to-carbs-ratio)** + +1. First, you need the correct default basal settings in your **Profile**. +2. Start on target, better without negative IOB. +3. Record the total insulin given in the pump tab (or pump history) and call it Start insulin C4. Very accurately measure a known portion of carbs, and record the start time and Start IOB. Then enter carbs and bolus information into AAPS using the wizard (with the current configured CI). Don't forget to eat the carbs ;) +4. After some hours, when COB=0[*](#profiletuning-cob-zero) and you're back on target, record end time, and note down the End IOB, check the total insulin given as before and call it End insulin. *NOTE: The time frame is NOT important, as long as it is longer than your digestion* +5. From the difference between Start and End insulin amount, subtract/add the difference end IOB - start IOB. Then subtract the basal insulin calculated from your profile settings. +6. If __BG__ is in target, you'll have the total insulin used to “digest” your carbs. Calculate your **I:C**. + +### **Explanations for the I:C calculations** + +- With a **Profile** that has the correct default basal rate, during any time frame, you should stay on target and have an IOB near 0. You get your **Profile** basal only. +- You add carbs and bolus to this mix. Wait till your body digests all the carbs and be back on **BG** target. Your insulin usage will be the sum of your basal + the insulin needed for the carbs. You calculate the insulin used for your basal (by using your **Profile**) and the surplus will be the insulin used to digest the carbs. +- If the time frame is too short, there will be carbs undigested, thus your "insulin needed for the carbs" will be wrong. +- If the time frame is too long, nothing bad will happen. You'll use all your carbs and you'll get more basal. At the end, you'll subtract the basal from the total insulin used, the extended time frame (with more basal use) will not affect the result. + +Originally written up by @Robby (Discord) on tips and tricks to help tune your AAPS Profile, reviewed and edited by the community (thank you!). diff --git a/docs/CROWDIN/ko/SettingUpAaps/ComputerBuild.md b/docs/CROWDIN/ko/SettingUpAaps/ComputerBuild.md index bc8e63e577ea..d030e412fa78 100644 --- a/docs/CROWDIN/ko/SettingUpAaps/ComputerBuild.md +++ b/docs/CROWDIN/ko/SettingUpAaps/ComputerBuild.md @@ -70,7 +70,7 @@ The Gradle version is linked to the source code, you will always get the correct ## Help and support during the building process -If you run into difficulties in the process of building the **AAPS** app, there is a dedicated [**troubleshooting Android Studio**](../GettingHelp/TroubleshootingAndroidStudio) section, please consult that first. +If you run into difficulties in the process of building the **AAPS** app, there is a dedicated [**troubleshooting Android Studio**](../GettingHelp/TroubleshootingAndroidStudio.md) section, please consult that first. If you think something in the building instructions is wrong, missing or confusing, or you are still struggling, please reach out to other **AAPS** users group on [Facebook](https://www.facebook.com/groups/AndroidAPSUsers) or [Discord](https://discord.gg/4fQUWHZ4Mw). If you want to change something yourself (updating screenshots _etc_), please submit a [pull request (PR)](../SupportingAaps/HowToEditTheDocs.md). @@ -409,7 +409,7 @@ Android Studio will display the information "BUILD SUCCESSFUL" after build is fi ![Build finished](../images/Building-the-App/049_ReopenNotification.png) -**_If the build was not successful, refer to the [Android Studio Troubleshooting section](../GettingHelp/TroubleshootingAndroidStudio)._** +**_If the build was not successful, refer to the [Android Studio Troubleshooting section](../GettingHelp/TroubleshootingAndroidStudio.md)._** In the Notifications box, click on the blue link "locate": diff --git a/docs/CROWDIN/ko/SettingUpAaps/Preferences.md b/docs/CROWDIN/ko/SettingUpAaps/Preferences.md index f864818d466f..61cb92c3f0cd 100644 --- a/docs/CROWDIN/ko/SettingUpAaps/Preferences.md +++ b/docs/CROWDIN/ko/SettingUpAaps/Preferences.md @@ -300,7 +300,7 @@ Switch between Open Loop, Closed Loop and Low Glucose Suspend (LGS). ![Config builder - loop mode](../images/ConfigBuilder_LoopLGS.png) -(Preferences-pen-loop)= +(Preferences-open-loop)= #### Open Loop **AAPS** continuously evaluates all available data (IOB, COB, BG...) and makes treatment suggestions (temporary basal rates) on how to adjust your therapy if necessary. diff --git a/docs/CROWDIN/ko/SettingUpAaps/YourAapsProfile.md b/docs/CROWDIN/ko/SettingUpAaps/YourAapsProfile.md index 0af8692d2b1b..630076685991 100644 --- a/docs/CROWDIN/ko/SettingUpAaps/YourAapsProfile.md +++ b/docs/CROWDIN/ko/SettingUpAaps/YourAapsProfile.md @@ -123,11 +123,13 @@ The **figure below** shows an example of how the basal rates can be set in an ** Setting your basal rates right is done by trial and error, and should be done in consultation with your diabetic team. -There are basal testing methods which usually entails observing your basal rates and insulin needs during an intermittent fasting over a 24-hour period. Although you need to test your basal rates for the whole day, it is not recommended to fast during 24h straight. This is because the body triggers mechanisms such as hormones to compensate. A recommended way is to fast 3 times for 8 hours. +There are basal testing methods which usually entails observing your basal rates and insulin needs during an intermittent fasting over a 24-hour period. Although you need to test your basal rates for the whole day, it is not recommended to fast during 24h straight. This is because the body triggers mechanisms such as hormones to compensate. A recommended way is to fast 3 times for 8 hours. -The recommended method is to suspend the loop, which will revert to your default background basal rate. Observe how your **BG** changes: if it is dropping, basal rate is too high. And vice versa.
An alternative method (may be more tricky) is to keep the loop running, and seeing how **IOB** changes. If **IOB** is negative, your basal rate is too high. And vice versa. Beware that this method relies on **ISF** to correct **BG**, and thus depends on other variables to be set reasonably well for it to be successful.
Another way of adjusting your basal rates is to watch the loop action during the night, when all COB have decayed. This method is particularly useful for children, when fasting is difficult or insulin needs change often. [Dr Saleh Adi from Tidepool](https://www.youtube.com/watch?v=-fpWnGRhLSo) provides useful ways on how to analyse overnight BG lines in order to optimise your basal rates. +The recommended method is to suspend the loop (for safety you can set AAPS to [**LGS**](#Preferences-aps-mode) to avoid lows, as done for achieving [objective 6](#objectives-objective6)), which will revert to your default background basal rate. Observe how your **BG** changes: if it is dropping, basal rate is too high. And vice versa.
An alternative method (may be more tricky) is to keep the loop running, and seeing how **IOB** changes. If **IOB** is negative, your basal rate is too high. And vice versa. Beware that this method relies on **ISF** to correct **BG**, and thus depends on other variables to be set reasonably well for it to be successful.
Another way of adjusting your basal rates is to watch the loop action during the night, when all COB have decayed. This method is particularly useful for children, when fasting is difficult or insulin needs change often. [Dr Saleh Adi from Tidepool](https://www.youtube.com/watch?v=-fpWnGRhLSo) provides useful ways on how to analyze overnight BG lines in order to optimize your basal rates. -When taking action on the result of your basal testing, changes in the **Profile** should be done 1 hour before the rise/drop. Repeat the test as necessary until you are comfortable with your **basal rates** settings. +See [here](../GettingHelp/ProfileTuning.md) how to tweak your basal profile, analyzing patterns in closed loop. + +When taking action on the result of your basal testing, changes in the **Profile** should be done 1 to 2 hours (depends on your insulin type) before the rise/drop. Repeat the test as necessary until you are comfortable with your **basal rates** settings. (your-aaps-profile-insulin-sensitivity-factor)= diff --git a/docs/CROWDIN/ko/SupportingAaps/HowCanIHelp.md b/docs/CROWDIN/ko/SupportingAaps/HowCanIHelp.md index 6aeca540f5b9..7b90cca588fd 100644 --- a/docs/CROWDIN/ko/SupportingAaps/HowCanIHelp.md +++ b/docs/CROWDIN/ko/SupportingAaps/HowCanIHelp.md @@ -15,7 +15,7 @@ Yay! Look at the issues, ask in the discord channel, there is always a lot to do Great, this is a highly appreciated thing and a good way to pay it forward! * The discord channel regarding the wiki can be found here: [AndroidAPS](https://discord.gg/4fQUWHZ4Mw). -* A guide how to do commits on English wiki can be found here: [How to make a PR](../SupportingAaps/HowToEditTheDocs.md). Other languages are only translated from english and can't be edited for consistency reasons. +* A guide how to do commits on English wiki can be found here: [How to make a PR](../SupportingAaps/HowToEditTheDocs.md). Other languages are only translated from English and can't be edited for consistency reasons. ## I do speak multiple languages and want to translate the app or the documentation @@ -23,7 +23,7 @@ If you are translating something for the first time, please start with translati You are welcome to start as a translator for the documentation in parallel or later. -You can check the state of translations for the languages app and documentation [here](StateOfTranslations). +You can check the state of translations for the languages app and documentation [here](#StateOfTranslations). * If you want to translate **the app** to other languages (thank you), please use [crowdin](https://crowdin.com/project/androidaps). * If you want to translate **the docs** to other languages (thank you), please use [crowdin](https://crowdin.com/project/androidapsdocs). diff --git a/docs/CROWDIN/ko/UsefulLinks/FAQ.md b/docs/CROWDIN/ko/UsefulLinks/FAQ.md index 731e604cdc01..ee606fe6f1f3 100644 --- a/docs/CROWDIN/ko/UsefulLinks/FAQ.md +++ b/docs/CROWDIN/ko/UsefulLinks/FAQ.md @@ -247,7 +247,7 @@ Copy on an internet drive (Dropbox, Google etc) : all the apks you used to insta Please -- check [Troubleshooting Android Studio](../GettingHelp/TroubleshootingAndroidStudio) for typical errors and +- check [Troubleshooting Android Studio](../GettingHelp/TroubleshootingAndroidStudio.md) for typical errors and - the tipps for with a [step by step walktrough](https://docs.google.com/document/d/1oc7aG0qrIMvK57unMqPEOoLt-J8UT1mxTKdTAxm8-po). ### I'm stuck on an objective and need help. diff --git a/docs/CROWDIN/ko/images/troubleshooting/profiletuning/FastRise.png b/docs/CROWDIN/ko/images/troubleshooting/profiletuning/FastRise.png new file mode 100644 index 000000000000..ba35b5bb6bf0 Binary files /dev/null and b/docs/CROWDIN/ko/images/troubleshooting/profiletuning/FastRise.png differ diff --git a/docs/CROWDIN/ko/images/troubleshooting/profiletuning/NegativeInsulin.png b/docs/CROWDIN/ko/images/troubleshooting/profiletuning/NegativeInsulin.png new file mode 100644 index 000000000000..7c39c50d00df Binary files /dev/null and b/docs/CROWDIN/ko/images/troubleshooting/profiletuning/NegativeInsulin.png differ diff --git a/docs/CROWDIN/ko/images/troubleshooting/profiletuning/NegativeInsulin2.png b/docs/CROWDIN/ko/images/troubleshooting/profiletuning/NegativeInsulin2.png new file mode 100644 index 000000000000..4bd840d597ad Binary files /dev/null and b/docs/CROWDIN/ko/images/troubleshooting/profiletuning/NegativeInsulin2.png differ diff --git a/docs/CROWDIN/ko/images/troubleshooting/profiletuning/PositiveInsulin.png b/docs/CROWDIN/ko/images/troubleshooting/profiletuning/PositiveInsulin.png new file mode 100644 index 000000000000..e50e806ebf01 Binary files /dev/null and b/docs/CROWDIN/ko/images/troubleshooting/profiletuning/PositiveInsulin.png differ diff --git a/docs/CROWDIN/ko/images/troubleshooting/profiletuning/StrongISF.png b/docs/CROWDIN/ko/images/troubleshooting/profiletuning/StrongISF.png new file mode 100644 index 000000000000..ca16a1ad1b9d Binary files /dev/null and b/docs/CROWDIN/ko/images/troubleshooting/profiletuning/StrongISF.png differ diff --git a/docs/CROWDIN/ko/images/troubleshooting/profiletuning/StuckHigh.png b/docs/CROWDIN/ko/images/troubleshooting/profiletuning/StuckHigh.png new file mode 100644 index 000000000000..1fbeefc01c50 Binary files /dev/null and b/docs/CROWDIN/ko/images/troubleshooting/profiletuning/StuckHigh.png differ diff --git a/docs/CROWDIN/ko/index.md b/docs/CROWDIN/ko/index.md index ac09b560fa39..2472bd744b7a 100644 --- a/docs/CROWDIN/ko/index.md +++ b/docs/CROWDIN/ko/index.md @@ -159,6 +159,7 @@ Updating to a new version of AAPS <./Maintenance/UpdateToNewVersion.md> Where can I get help with AAPS <./GettingHelp/WhereCanIGetHelp.md> General troubleshooting <./GettingHelp/GeneralTroubleshooting.md> - Bluetooth troubleshooting <./GettingHelp/BluetoothTroubleshooting.md> +Profile Tuning Guide <./GettingHelp/ProfileTuning.md> Troubleshooting Android Studio <./GettingHelp/TroubleshootingAndroidStudio.md> Accessing logfiles <./GettingHelp/AccessingLogFiles.md> ``` diff --git a/docs/CROWDIN/lt/Getting-Started/Introduction.md b/docs/CROWDIN/lt/Getting-Started/Introduction.md index de515d3603c1..cb0423996bd9 100644 --- a/docs/CROWDIN/lt/Getting-Started/Introduction.md +++ b/docs/CROWDIN/lt/Getting-Started/Introduction.md @@ -192,7 +192,7 @@ If a malicious attack was made on your insulin pump, these strategies would sign #### Safety considerations around improving blood glucose control too fast -A rapid reduction in HbA1c and improved blood glucose control sounds appealing. However, reducing average blood glucose levels _too fast_ by starting any closed loop system can cause permanent damage, including to the eyes, and painful neuropathy that never goes away. This damage can be avoided simply by reducing levels more slowly. If you currently have an elevated HbA1c and are moving to AAPS (or any other closed loop system), please discuss this potential risk with your clinical team before starting, and agree a timeplan with them. More general information on how to reduce your glucose levels safely, including links to medical literature is given in the [safety section [here](#preparing-safety-first). +A rapid reduction in HbA1c and improved blood glucose control sounds appealing. However, reducing average blood glucose levels _too fast_ by starting any closed loop system can cause permanent damage, including to the eyes, and painful neuropathy that never goes away. This damage can be avoided simply by reducing levels more slowly. If you currently have an elevated HbA1c and are moving to AAPS (or any other closed loop system), please discuss this potential risk with your clinical team before starting, and agree a time plan with them. More general information on how to reduce your glucose levels safely, including links to medical literature is given in the safety section [here](#preparing-safety-first). #### Medical safety around devices, consumable supplies and other medications diff --git a/docs/CROWDIN/lt/GettingHelp/ProfileTuning.md b/docs/CROWDIN/lt/GettingHelp/ProfileTuning.md new file mode 100644 index 000000000000..566fc5f5c43b --- /dev/null +++ b/docs/CROWDIN/lt/GettingHelp/ProfileTuning.md @@ -0,0 +1,136 @@ +# **Tweaking the AAPS' Profile** + +```{admonition} This is NOT a medical advice +:class: warning +Please work with your care team for support and advice on your diabetes management.
+Use this guide only once you have [set up your **Profile** correctly](https://androidaps.readthedocs.io/en/latest/SettingUpAaps/YourAapsProfile.md), following all **AAPS** objectives. +``` + +This guide explains the logic of the OpenAPS algorithm results with a given __Profile__, and provides information about which values to adjust when certain situations are observed. The suggestions about basal testing below may diverge from what your care team advises + +Using **closed loop** may make basal testing easier and may significantly reduce the hypo risk if your __Profile__ basal is too strong. + +## **Changing profile's settings, how to proceed** + +1. Ensure you have read and understand __AAPS’__ recommended settings and advice below. Not following this advice will make the whole process problematic and less likely to get a well tuned __Profile__ +2. Carefully observe and compare, **over several days**, what is happening with your __BG__ and __IOB__. +3. Keep an eye out for patterns that happen around the same time (almost) everyday. +4. It's important to do this over several days. Poor results tend to be yielded from using data observed on a single day to make __Profile’s__ adjustment decisions. +5. After you have observed a repeatable pattern of behavior, e.g. at 1PM you see a spike in __BG__ or a negative __IOB__ value, only then start to make small changes to your __Profile__. +6. It's important to limit the changes you make to one thing at a time. E.g. increase your basal by 10% around 1PM. +7. After every change, it's important to monitor the impact on your __BG__ and __IOB__ for the next few days. +8. Repeat this pattern, observe, decide, tweak again if needed + +Don't rush, go slow! + +## **Recommended settings and advice while tweaking basal** + +- Do all testing with [closed loop enabled](#AapsScreens-loop-status). +- **Turn OFF all [automations](../DailyLifeWithAAPS/Automations.md)** +- **Turn OFF [DynISF](#Open-APS-features-DynamicISF), [AutoISF](../AdvancedOptions/DevBranch.md), [AutoSens](#Open-APS-features-autosens)** so that they will not try to adapt your profile. +- Do not make manual user actions (manual bolus, temp targets etc…) while testing: let the system use the **Profile** settings only. +- For the [additional graphs](#AapsScreens-section-g-additional-graphs): on graph 1, use Insulin On Board, Carbs On Board (and Sensitivity change). On graph 2, use Deviations and Blood Glucose Impact. When asking for advice, always include those on your screenshots. +- COB=0[*](#profiletuning-cob-zero) +- No physical activities. +- No stress. +- No illness. +- No extreme weather like high or low temperatures. +- If your [basal rate profile](#your-aaps-profile-basal-rates) is correct, when you are on target with COB=0[*](#profiletuning-cob-zero) and IOB=0, you will remain constantly on target whatever your ISF (ISF is only used when you are higher than your target). +- You need to check the actual IOB but also, the IOB chart to see how the IOB was during the past few hours. + +(profiletuning-cob-zero)= + +***COB = 0** + +Meaning that the meal is digested, and there are no more carbs in your body. + +AAPS might indicate [COB=0 while you still have carbs on board](../DailyLifeWithAAPS/CobCalculation.md). + +## **[Profile](../SettingUpAaps/YourAapsProfile.md) definitions** + +A too **strong Profile** indicates some combination of the following: + +- [ISF](#insulin-sensitivity-factor-isf) number is too small +- The [basal](#basal-rates) number is too big +- [I:C](#insulin-to-carb-ratio-icr) number is too small + +## **IOB Observations** + +*Note: you can also use Loopalyzer IOB graph in Nightscout reports to view IOB on several days.* + +If you observe the following patterns after a few days, consider the following changes + +### **IOB positive** + +- **Profile** basal might not be strong enough (this could also be because of things like unannounced food, illness, bad site absorption, etc.) + +![Positive IOB](../images/troubleshooting/profiletuning/PositiveInsulin.png) + +### **IOB negative** + +- Default basal too strong +- May be the effect from past exercise/physical activity + +![Negative IOB](../images/troubleshooting/profiletuning/NegativeInsulin.png) + +- Previous meal: too much bolus (which resulted in a very long zero temp basal) + +![Negative IOB](../images/troubleshooting/profiletuning/NegativeInsulin2.png) + +## **BG Target Observations** + +### **Stuck High** + +- __ISF__ ‘s number is high and not strong enough (calculated insulin is too weak) + +![Stuck High](../images/troubleshooting/profiletuning/StuckHigh.png) + +- __Profile__ basal might not be strong enough (SMBs do not have enough "basal stock" to use) +- A security ([MaxIOB](#Open-APS-features-maximum-total-iob-openaps-cant-go-over)?) might have kicked in and is limiting insulin injection. Verify in the [SMB](#Open-APS-features-super-micro-bolus-smb) tab. +- Technical issue: site absorption, infusion set, ... + +### **Stuck Low** + +- __ISF__ too strong and the number needs to be raised higher +- __Profile__ basal too strong (if also negative IOB) + +### **Rollercoaster (ups and downs)** + +- **ISF** too strong? See your [AAPS Profile](#your-aaps-profile-insulin-sensitivity-factor) + +![Rollercoaster](../images/troubleshooting/profiletuning/StrongISF.png) + +## **BG After Meals Observations** + +### **Fast rise and BG going high** + +- Food contains fast carbs +- Consider doing a pre-bolus +- Bolus (IC or injected %) not strong enough + +![Rise High](../images/troubleshooting/profiletuning/FastRise.png) + +### **Fast rise and then BG going low** + +- Consider doing a pre-bolus, profile might be too aggressive (over correction of the raise) +- Bolus too strong + + + +## **[How to calculate your I:C](#your-aaps-profile-insulin-to-carbs-ratio)** + +1. First, you need the correct default basal settings in your **Profile**. +2. Start on target, better without negative IOB. +3. Record the total insulin given in the pump tab (or pump history) and call it Start insulin C4. Very accurately measure a known portion of carbs, and record the start time and Start IOB. Then enter carbs and bolus information into AAPS using the wizard (with the current configured CI). Don't forget to eat the carbs ;) +4. After some hours, when COB=0[*](#profiletuning-cob-zero) and you're back on target, record end time, and note down the End IOB, check the total insulin given as before and call it End insulin. *NOTE: The time frame is NOT important, as long as it is longer than your digestion* +5. From the difference between Start and End insulin amount, subtract/add the difference end IOB - start IOB. Then subtract the basal insulin calculated from your profile settings. +6. If __BG__ is in target, you'll have the total insulin used to “digest” your carbs. Calculate your **I:C**. + +### **Explanations for the I:C calculations** + +- With a **Profile** that has the correct default basal rate, during any time frame, you should stay on target and have an IOB near 0. You get your **Profile** basal only. +- You add carbs and bolus to this mix. Wait till your body digests all the carbs and be back on **BG** target. Your insulin usage will be the sum of your basal + the insulin needed for the carbs. You calculate the insulin used for your basal (by using your **Profile**) and the surplus will be the insulin used to digest the carbs. +- If the time frame is too short, there will be carbs undigested, thus your "insulin needed for the carbs" will be wrong. +- If the time frame is too long, nothing bad will happen. You'll use all your carbs and you'll get more basal. At the end, you'll subtract the basal from the total insulin used, the extended time frame (with more basal use) will not affect the result. + +Originally written up by @Robby (Discord) on tips and tricks to help tune your AAPS Profile, reviewed and edited by the community (thank you!). diff --git a/docs/CROWDIN/lt/SettingUpAaps/ComputerBuild.md b/docs/CROWDIN/lt/SettingUpAaps/ComputerBuild.md index 2c3b52d9130c..d80eff97167b 100644 --- a/docs/CROWDIN/lt/SettingUpAaps/ComputerBuild.md +++ b/docs/CROWDIN/lt/SettingUpAaps/ComputerBuild.md @@ -70,7 +70,7 @@ The Gradle version is linked to the source code, you will always get the correct ## Help and support during the building process -If you run into difficulties in the process of building the **AAPS** app, there is a dedicated [**troubleshooting Android Studio**](../GettingHelp/TroubleshootingAndroidStudio) section, please consult that first. +If you run into difficulties in the process of building the **AAPS** app, there is a dedicated [**troubleshooting Android Studio**](../GettingHelp/TroubleshootingAndroidStudio.md) section, please consult that first. If you think something in the building instructions is wrong, missing or confusing, or you are still struggling, please reach out to other **AAPS** users group on [Facebook](https://www.facebook.com/groups/AndroidAPSUsers) or [Discord](https://discord.gg/4fQUWHZ4Mw). If you want to change something yourself (updating screenshots _etc_), please submit a [pull request (PR)](../SupportingAaps/HowToEditTheDocs.md). @@ -409,7 +409,7 @@ Android Studio will display the information "BUILD SUCCESSFUL" after build is fi ![Build finished](../images/Building-the-App/049_ReopenNotification.png) -**_If the build was not successful, refer to the [Android Studio Troubleshooting section](../GettingHelp/TroubleshootingAndroidStudio)._** +**_If the build was not successful, refer to the [Android Studio Troubleshooting section](../GettingHelp/TroubleshootingAndroidStudio.md)._** In the Notifications box, click on the blue link "locate": diff --git a/docs/CROWDIN/lt/SettingUpAaps/Preferences.md b/docs/CROWDIN/lt/SettingUpAaps/Preferences.md index a6faf26dda27..1ad7ca3f147b 100644 --- a/docs/CROWDIN/lt/SettingUpAaps/Preferences.md +++ b/docs/CROWDIN/lt/SettingUpAaps/Preferences.md @@ -300,7 +300,7 @@ Switch between Open Loop, Closed Loop and Low Glucose Suspend (LGS). ![Config builder - loop mode](../images/ConfigBuilder_LoopLGS.png) -(Preferences-pen-loop)= +(Preferences-open-loop)= #### Open Loop **AAPS** continuously evaluates all available data (IOB, COB, BG...) and makes treatment suggestions (temporary basal rates) on how to adjust your therapy if necessary. diff --git a/docs/CROWDIN/lt/SettingUpAaps/YourAapsProfile.md b/docs/CROWDIN/lt/SettingUpAaps/YourAapsProfile.md index 4ab64358c802..c26b308c145f 100644 --- a/docs/CROWDIN/lt/SettingUpAaps/YourAapsProfile.md +++ b/docs/CROWDIN/lt/SettingUpAaps/YourAapsProfile.md @@ -123,11 +123,13 @@ The **figure below** shows an example of how the basal rates can be set in an ** Setting your basal rates right is done by trial and error, and should be done in consultation with your diabetic team. -There are basal testing methods which usually entails observing your basal rates and insulin needs during an intermittent fasting over a 24-hour period. Although you need to test your basal rates for the whole day, it is not recommended to fast during 24h straight. This is because the body triggers mechanisms such as hormones to compensate. A recommended way is to fast 3 times for 8 hours. +There are basal testing methods which usually entails observing your basal rates and insulin needs during an intermittent fasting over a 24-hour period. Although you need to test your basal rates for the whole day, it is not recommended to fast during 24h straight. This is because the body triggers mechanisms such as hormones to compensate. A recommended way is to fast 3 times for 8 hours. -The recommended method is to suspend the loop, which will revert to your default background basal rate. Observe how your **BG** changes: if it is dropping, basal rate is too high. And vice versa.
An alternative method (may be more tricky) is to keep the loop running, and seeing how **IOB** changes. If **IOB** is negative, your basal rate is too high. And vice versa. Beware that this method relies on **ISF** to correct **BG**, and thus depends on other variables to be set reasonably well for it to be successful.
Another way of adjusting your basal rates is to watch the loop action during the night, when all COB have decayed. This method is particularly useful for children, when fasting is difficult or insulin needs change often. [Dr Saleh Adi from Tidepool](https://www.youtube.com/watch?v=-fpWnGRhLSo) provides useful ways on how to analyse overnight BG lines in order to optimise your basal rates. +The recommended method is to suspend the loop (for safety you can set AAPS to [**LGS**](#Preferences-aps-mode) to avoid lows, as done for achieving [objective 6](#objectives-objective6)), which will revert to your default background basal rate. Observe how your **BG** changes: if it is dropping, basal rate is too high. And vice versa.
An alternative method (may be more tricky) is to keep the loop running, and seeing how **IOB** changes. If **IOB** is negative, your basal rate is too high. And vice versa. Beware that this method relies on **ISF** to correct **BG**, and thus depends on other variables to be set reasonably well for it to be successful.
Another way of adjusting your basal rates is to watch the loop action during the night, when all COB have decayed. This method is particularly useful for children, when fasting is difficult or insulin needs change often. [Dr Saleh Adi from Tidepool](https://www.youtube.com/watch?v=-fpWnGRhLSo) provides useful ways on how to analyze overnight BG lines in order to optimize your basal rates. -When taking action on the result of your basal testing, changes in the **Profile** should be done 1 hour before the rise/drop. Repeat the test as necessary until you are comfortable with your **basal rates** settings. +See [here](../GettingHelp/ProfileTuning.md) how to tweak your basal profile, analyzing patterns in closed loop. + +When taking action on the result of your basal testing, changes in the **Profile** should be done 1 to 2 hours (depends on your insulin type) before the rise/drop. Repeat the test as necessary until you are comfortable with your **basal rates** settings. (your-aaps-profile-insulin-sensitivity-factor)= diff --git a/docs/CROWDIN/lt/SupportingAaps/HowCanIHelp.md b/docs/CROWDIN/lt/SupportingAaps/HowCanIHelp.md index 6aeca540f5b9..7b90cca588fd 100644 --- a/docs/CROWDIN/lt/SupportingAaps/HowCanIHelp.md +++ b/docs/CROWDIN/lt/SupportingAaps/HowCanIHelp.md @@ -15,7 +15,7 @@ Yay! Look at the issues, ask in the discord channel, there is always a lot to do Great, this is a highly appreciated thing and a good way to pay it forward! * The discord channel regarding the wiki can be found here: [AndroidAPS](https://discord.gg/4fQUWHZ4Mw). -* A guide how to do commits on English wiki can be found here: [How to make a PR](../SupportingAaps/HowToEditTheDocs.md). Other languages are only translated from english and can't be edited for consistency reasons. +* A guide how to do commits on English wiki can be found here: [How to make a PR](../SupportingAaps/HowToEditTheDocs.md). Other languages are only translated from English and can't be edited for consistency reasons. ## I do speak multiple languages and want to translate the app or the documentation @@ -23,7 +23,7 @@ If you are translating something for the first time, please start with translati You are welcome to start as a translator for the documentation in parallel or later. -You can check the state of translations for the languages app and documentation [here](StateOfTranslations). +You can check the state of translations for the languages app and documentation [here](#StateOfTranslations). * If you want to translate **the app** to other languages (thank you), please use [crowdin](https://crowdin.com/project/androidaps). * If you want to translate **the docs** to other languages (thank you), please use [crowdin](https://crowdin.com/project/androidapsdocs). diff --git a/docs/CROWDIN/lt/UsefulLinks/FAQ.md b/docs/CROWDIN/lt/UsefulLinks/FAQ.md index 4a41104d926e..0fbb510d9dec 100644 --- a/docs/CROWDIN/lt/UsefulLinks/FAQ.md +++ b/docs/CROWDIN/lt/UsefulLinks/FAQ.md @@ -247,7 +247,7 @@ Copy on an internet drive (Dropbox, Google etc) : all the apks you used to insta Please -- check [Troubleshooting Android Studio](../GettingHelp/TroubleshootingAndroidStudio) for typical errors and +- check [Troubleshooting Android Studio](../GettingHelp/TroubleshootingAndroidStudio.md) for typical errors and - the tipps for with a [step by step walktrough](https://docs.google.com/document/d/1oc7aG0qrIMvK57unMqPEOoLt-J8UT1mxTKdTAxm8-po). ### I'm stuck on an objective and need help. diff --git a/docs/CROWDIN/lt/images/troubleshooting/profiletuning/FastRise.png b/docs/CROWDIN/lt/images/troubleshooting/profiletuning/FastRise.png new file mode 100644 index 000000000000..ba35b5bb6bf0 Binary files /dev/null and b/docs/CROWDIN/lt/images/troubleshooting/profiletuning/FastRise.png differ diff --git a/docs/CROWDIN/lt/images/troubleshooting/profiletuning/NegativeInsulin.png b/docs/CROWDIN/lt/images/troubleshooting/profiletuning/NegativeInsulin.png new file mode 100644 index 000000000000..7c39c50d00df Binary files /dev/null and b/docs/CROWDIN/lt/images/troubleshooting/profiletuning/NegativeInsulin.png differ diff --git a/docs/CROWDIN/lt/images/troubleshooting/profiletuning/NegativeInsulin2.png b/docs/CROWDIN/lt/images/troubleshooting/profiletuning/NegativeInsulin2.png new file mode 100644 index 000000000000..4bd840d597ad Binary files /dev/null and b/docs/CROWDIN/lt/images/troubleshooting/profiletuning/NegativeInsulin2.png differ diff --git a/docs/CROWDIN/lt/images/troubleshooting/profiletuning/PositiveInsulin.png b/docs/CROWDIN/lt/images/troubleshooting/profiletuning/PositiveInsulin.png new file mode 100644 index 000000000000..e50e806ebf01 Binary files /dev/null and b/docs/CROWDIN/lt/images/troubleshooting/profiletuning/PositiveInsulin.png differ diff --git a/docs/CROWDIN/lt/images/troubleshooting/profiletuning/StrongISF.png b/docs/CROWDIN/lt/images/troubleshooting/profiletuning/StrongISF.png new file mode 100644 index 000000000000..ca16a1ad1b9d Binary files /dev/null and b/docs/CROWDIN/lt/images/troubleshooting/profiletuning/StrongISF.png differ diff --git a/docs/CROWDIN/lt/images/troubleshooting/profiletuning/StuckHigh.png b/docs/CROWDIN/lt/images/troubleshooting/profiletuning/StuckHigh.png new file mode 100644 index 000000000000..1fbeefc01c50 Binary files /dev/null and b/docs/CROWDIN/lt/images/troubleshooting/profiletuning/StuckHigh.png differ diff --git a/docs/CROWDIN/lt/index.md b/docs/CROWDIN/lt/index.md index ed30b1c870e0..e9f4289c83ac 100644 --- a/docs/CROWDIN/lt/index.md +++ b/docs/CROWDIN/lt/index.md @@ -159,6 +159,7 @@ Updating to a new version of AAPS <./Maintenance/UpdateToNewVersion.md> Where can I get help with AAPS <./GettingHelp/WhereCanIGetHelp.md> General troubleshooting <./GettingHelp/GeneralTroubleshooting.md> - Bluetooth troubleshooting <./GettingHelp/BluetoothTroubleshooting.md> +Profile Tuning Guide <./GettingHelp/ProfileTuning.md> Troubleshooting Android Studio <./GettingHelp/TroubleshootingAndroidStudio.md> Accessing logfiles <./GettingHelp/AccessingLogFiles.md> ``` diff --git a/docs/CROWDIN/nl/Getting-Started/Introduction.md b/docs/CROWDIN/nl/Getting-Started/Introduction.md index 33170843274b..bd8f728b8fc8 100644 --- a/docs/CROWDIN/nl/Getting-Started/Introduction.md +++ b/docs/CROWDIN/nl/Getting-Started/Introduction.md @@ -192,7 +192,7 @@ If a malicious attack was made on your insulin pump, these strategies would sign #### Safety considerations around improving blood glucose control too fast -A rapid reduction in HbA1c and improved blood glucose control sounds appealing. However, reducing average blood glucose levels _too fast_ by starting any closed loop system can cause permanent damage, including to the eyes, and painful neuropathy that never goes away. This damage can be avoided simply by reducing levels more slowly. If you currently have an elevated HbA1c and are moving to AAPS (or any other closed loop system), please discuss this potential risk with your clinical team before starting, and agree a timeplan with them. More general information on how to reduce your glucose levels safely, including links to medical literature is given in the [safety section [here](#preparing-safety-first). +A rapid reduction in HbA1c and improved blood glucose control sounds appealing. However, reducing average blood glucose levels _too fast_ by starting any closed loop system can cause permanent damage, including to the eyes, and painful neuropathy that never goes away. This damage can be avoided simply by reducing levels more slowly. If you currently have an elevated HbA1c and are moving to AAPS (or any other closed loop system), please discuss this potential risk with your clinical team before starting, and agree a time plan with them. More general information on how to reduce your glucose levels safely, including links to medical literature is given in the safety section [here](#preparing-safety-first). #### Medical safety around devices, consumable supplies and other medications diff --git a/docs/CROWDIN/nl/GettingHelp/ProfileTuning.md b/docs/CROWDIN/nl/GettingHelp/ProfileTuning.md new file mode 100644 index 000000000000..566fc5f5c43b --- /dev/null +++ b/docs/CROWDIN/nl/GettingHelp/ProfileTuning.md @@ -0,0 +1,136 @@ +# **Tweaking the AAPS' Profile** + +```{admonition} This is NOT a medical advice +:class: warning +Please work with your care team for support and advice on your diabetes management.
+Use this guide only once you have [set up your **Profile** correctly](https://androidaps.readthedocs.io/en/latest/SettingUpAaps/YourAapsProfile.md), following all **AAPS** objectives. +``` + +This guide explains the logic of the OpenAPS algorithm results with a given __Profile__, and provides information about which values to adjust when certain situations are observed. The suggestions about basal testing below may diverge from what your care team advises + +Using **closed loop** may make basal testing easier and may significantly reduce the hypo risk if your __Profile__ basal is too strong. + +## **Changing profile's settings, how to proceed** + +1. Ensure you have read and understand __AAPS’__ recommended settings and advice below. Not following this advice will make the whole process problematic and less likely to get a well tuned __Profile__ +2. Carefully observe and compare, **over several days**, what is happening with your __BG__ and __IOB__. +3. Keep an eye out for patterns that happen around the same time (almost) everyday. +4. It's important to do this over several days. Poor results tend to be yielded from using data observed on a single day to make __Profile’s__ adjustment decisions. +5. After you have observed a repeatable pattern of behavior, e.g. at 1PM you see a spike in __BG__ or a negative __IOB__ value, only then start to make small changes to your __Profile__. +6. It's important to limit the changes you make to one thing at a time. E.g. increase your basal by 10% around 1PM. +7. After every change, it's important to monitor the impact on your __BG__ and __IOB__ for the next few days. +8. Repeat this pattern, observe, decide, tweak again if needed + +Don't rush, go slow! + +## **Recommended settings and advice while tweaking basal** + +- Do all testing with [closed loop enabled](#AapsScreens-loop-status). +- **Turn OFF all [automations](../DailyLifeWithAAPS/Automations.md)** +- **Turn OFF [DynISF](#Open-APS-features-DynamicISF), [AutoISF](../AdvancedOptions/DevBranch.md), [AutoSens](#Open-APS-features-autosens)** so that they will not try to adapt your profile. +- Do not make manual user actions (manual bolus, temp targets etc…) while testing: let the system use the **Profile** settings only. +- For the [additional graphs](#AapsScreens-section-g-additional-graphs): on graph 1, use Insulin On Board, Carbs On Board (and Sensitivity change). On graph 2, use Deviations and Blood Glucose Impact. When asking for advice, always include those on your screenshots. +- COB=0[*](#profiletuning-cob-zero) +- No physical activities. +- No stress. +- No illness. +- No extreme weather like high or low temperatures. +- If your [basal rate profile](#your-aaps-profile-basal-rates) is correct, when you are on target with COB=0[*](#profiletuning-cob-zero) and IOB=0, you will remain constantly on target whatever your ISF (ISF is only used when you are higher than your target). +- You need to check the actual IOB but also, the IOB chart to see how the IOB was during the past few hours. + +(profiletuning-cob-zero)= + +***COB = 0** + +Meaning that the meal is digested, and there are no more carbs in your body. + +AAPS might indicate [COB=0 while you still have carbs on board](../DailyLifeWithAAPS/CobCalculation.md). + +## **[Profile](../SettingUpAaps/YourAapsProfile.md) definitions** + +A too **strong Profile** indicates some combination of the following: + +- [ISF](#insulin-sensitivity-factor-isf) number is too small +- The [basal](#basal-rates) number is too big +- [I:C](#insulin-to-carb-ratio-icr) number is too small + +## **IOB Observations** + +*Note: you can also use Loopalyzer IOB graph in Nightscout reports to view IOB on several days.* + +If you observe the following patterns after a few days, consider the following changes + +### **IOB positive** + +- **Profile** basal might not be strong enough (this could also be because of things like unannounced food, illness, bad site absorption, etc.) + +![Positive IOB](../images/troubleshooting/profiletuning/PositiveInsulin.png) + +### **IOB negative** + +- Default basal too strong +- May be the effect from past exercise/physical activity + +![Negative IOB](../images/troubleshooting/profiletuning/NegativeInsulin.png) + +- Previous meal: too much bolus (which resulted in a very long zero temp basal) + +![Negative IOB](../images/troubleshooting/profiletuning/NegativeInsulin2.png) + +## **BG Target Observations** + +### **Stuck High** + +- __ISF__ ‘s number is high and not strong enough (calculated insulin is too weak) + +![Stuck High](../images/troubleshooting/profiletuning/StuckHigh.png) + +- __Profile__ basal might not be strong enough (SMBs do not have enough "basal stock" to use) +- A security ([MaxIOB](#Open-APS-features-maximum-total-iob-openaps-cant-go-over)?) might have kicked in and is limiting insulin injection. Verify in the [SMB](#Open-APS-features-super-micro-bolus-smb) tab. +- Technical issue: site absorption, infusion set, ... + +### **Stuck Low** + +- __ISF__ too strong and the number needs to be raised higher +- __Profile__ basal too strong (if also negative IOB) + +### **Rollercoaster (ups and downs)** + +- **ISF** too strong? See your [AAPS Profile](#your-aaps-profile-insulin-sensitivity-factor) + +![Rollercoaster](../images/troubleshooting/profiletuning/StrongISF.png) + +## **BG After Meals Observations** + +### **Fast rise and BG going high** + +- Food contains fast carbs +- Consider doing a pre-bolus +- Bolus (IC or injected %) not strong enough + +![Rise High](../images/troubleshooting/profiletuning/FastRise.png) + +### **Fast rise and then BG going low** + +- Consider doing a pre-bolus, profile might be too aggressive (over correction of the raise) +- Bolus too strong + + + +## **[How to calculate your I:C](#your-aaps-profile-insulin-to-carbs-ratio)** + +1. First, you need the correct default basal settings in your **Profile**. +2. Start on target, better without negative IOB. +3. Record the total insulin given in the pump tab (or pump history) and call it Start insulin C4. Very accurately measure a known portion of carbs, and record the start time and Start IOB. Then enter carbs and bolus information into AAPS using the wizard (with the current configured CI). Don't forget to eat the carbs ;) +4. After some hours, when COB=0[*](#profiletuning-cob-zero) and you're back on target, record end time, and note down the End IOB, check the total insulin given as before and call it End insulin. *NOTE: The time frame is NOT important, as long as it is longer than your digestion* +5. From the difference between Start and End insulin amount, subtract/add the difference end IOB - start IOB. Then subtract the basal insulin calculated from your profile settings. +6. If __BG__ is in target, you'll have the total insulin used to “digest” your carbs. Calculate your **I:C**. + +### **Explanations for the I:C calculations** + +- With a **Profile** that has the correct default basal rate, during any time frame, you should stay on target and have an IOB near 0. You get your **Profile** basal only. +- You add carbs and bolus to this mix. Wait till your body digests all the carbs and be back on **BG** target. Your insulin usage will be the sum of your basal + the insulin needed for the carbs. You calculate the insulin used for your basal (by using your **Profile**) and the surplus will be the insulin used to digest the carbs. +- If the time frame is too short, there will be carbs undigested, thus your "insulin needed for the carbs" will be wrong. +- If the time frame is too long, nothing bad will happen. You'll use all your carbs and you'll get more basal. At the end, you'll subtract the basal from the total insulin used, the extended time frame (with more basal use) will not affect the result. + +Originally written up by @Robby (Discord) on tips and tricks to help tune your AAPS Profile, reviewed and edited by the community (thank you!). diff --git a/docs/CROWDIN/nl/SettingUpAaps/ComputerBuild.md b/docs/CROWDIN/nl/SettingUpAaps/ComputerBuild.md index e6f7b66ced6c..68a3e0536488 100644 --- a/docs/CROWDIN/nl/SettingUpAaps/ComputerBuild.md +++ b/docs/CROWDIN/nl/SettingUpAaps/ComputerBuild.md @@ -70,7 +70,7 @@ The Gradle version is linked to the source code, you will always get the correct ## Help and support during the building process -If you run into difficulties in the process of building the **AAPS** app, there is a dedicated [**troubleshooting Android Studio**](../GettingHelp/TroubleshootingAndroidStudio) section, please consult that first. +If you run into difficulties in the process of building the **AAPS** app, there is a dedicated [**troubleshooting Android Studio**](../GettingHelp/TroubleshootingAndroidStudio.md) section, please consult that first. If you think something in the building instructions is wrong, missing or confusing, or you are still struggling, please reach out to other **AAPS** users group on [Facebook](https://www.facebook.com/groups/AndroidAPSUsers) or [Discord](https://discord.gg/4fQUWHZ4Mw). If you want to change something yourself (updating screenshots _etc_), please submit a [pull request (PR)](../SupportingAaps/HowToEditTheDocs.md). @@ -409,7 +409,7 @@ Android Studio will display the information "BUILD SUCCESSFUL" after build is fi ![Build finished](../images/Building-the-App/049_ReopenNotification.png) -**_If the build was not successful, refer to the [Android Studio Troubleshooting section](../GettingHelp/TroubleshootingAndroidStudio)._** +**_If the build was not successful, refer to the [Android Studio Troubleshooting section](../GettingHelp/TroubleshootingAndroidStudio.md)._** In the Notifications box, click on the blue link "locate": diff --git a/docs/CROWDIN/nl/SettingUpAaps/Preferences.md b/docs/CROWDIN/nl/SettingUpAaps/Preferences.md index 3c2ebcfb0d02..76804096907c 100644 --- a/docs/CROWDIN/nl/SettingUpAaps/Preferences.md +++ b/docs/CROWDIN/nl/SettingUpAaps/Preferences.md @@ -300,7 +300,7 @@ Switch between Open Loop, Closed Loop and Low Glucose Suspend (LGS). ![Config builder - loop mode](../images/ConfigBuilder_LoopLGS.png) -(Preferences-pen-loop)= +(Preferences-open-loop)= #### Open Loop **AAPS** continuously evaluates all available data (IOB, COB, BG...) and makes treatment suggestions (temporary basal rates) on how to adjust your therapy if necessary. diff --git a/docs/CROWDIN/nl/SettingUpAaps/YourAapsProfile.md b/docs/CROWDIN/nl/SettingUpAaps/YourAapsProfile.md index 135f29373f47..0e628b53f468 100644 --- a/docs/CROWDIN/nl/SettingUpAaps/YourAapsProfile.md +++ b/docs/CROWDIN/nl/SettingUpAaps/YourAapsProfile.md @@ -123,11 +123,13 @@ The **figure below** shows an example of how the basal rates can be set in an ** Setting your basal rates right is done by trial and error, and should be done in consultation with your diabetic team. -There are basal testing methods which usually entails observing your basal rates and insulin needs during an intermittent fasting over a 24-hour period. Although you need to test your basal rates for the whole day, it is not recommended to fast during 24h straight. This is because the body triggers mechanisms such as hormones to compensate. A recommended way is to fast 3 times for 8 hours. +There are basal testing methods which usually entails observing your basal rates and insulin needs during an intermittent fasting over a 24-hour period. Although you need to test your basal rates for the whole day, it is not recommended to fast during 24h straight. This is because the body triggers mechanisms such as hormones to compensate. A recommended way is to fast 3 times for 8 hours. -The recommended method is to suspend the loop, which will revert to your default background basal rate. Observe how your **BG** changes: if it is dropping, basal rate is too high. And vice versa.
An alternative method (may be more tricky) is to keep the loop running, and seeing how **IOB** changes. If **IOB** is negative, your basal rate is too high. And vice versa. Beware that this method relies on **ISF** to correct **BG**, and thus depends on other variables to be set reasonably well for it to be successful.
Another way of adjusting your basal rates is to watch the loop action during the night, when all COB have decayed. This method is particularly useful for children, when fasting is difficult or insulin needs change often. [Dr Saleh Adi from Tidepool](https://www.youtube.com/watch?v=-fpWnGRhLSo) provides useful ways on how to analyse overnight BG lines in order to optimise your basal rates. +The recommended method is to suspend the loop (for safety you can set AAPS to [**LGS**](#Preferences-aps-mode) to avoid lows, as done for achieving [objective 6](#objectives-objective6)), which will revert to your default background basal rate. Observe how your **BG** changes: if it is dropping, basal rate is too high. And vice versa.
An alternative method (may be more tricky) is to keep the loop running, and seeing how **IOB** changes. If **IOB** is negative, your basal rate is too high. And vice versa. Beware that this method relies on **ISF** to correct **BG**, and thus depends on other variables to be set reasonably well for it to be successful.
Another way of adjusting your basal rates is to watch the loop action during the night, when all COB have decayed. This method is particularly useful for children, when fasting is difficult or insulin needs change often. [Dr Saleh Adi from Tidepool](https://www.youtube.com/watch?v=-fpWnGRhLSo) provides useful ways on how to analyze overnight BG lines in order to optimize your basal rates. -When taking action on the result of your basal testing, changes in the **Profile** should be done 1 hour before the rise/drop. Repeat the test as necessary until you are comfortable with your **basal rates** settings. +See [here](../GettingHelp/ProfileTuning.md) how to tweak your basal profile, analyzing patterns in closed loop. + +When taking action on the result of your basal testing, changes in the **Profile** should be done 1 to 2 hours (depends on your insulin type) before the rise/drop. Repeat the test as necessary until you are comfortable with your **basal rates** settings. (your-aaps-profile-insulin-sensitivity-factor)= diff --git a/docs/CROWDIN/nl/SupportingAaps/HowCanIHelp.md b/docs/CROWDIN/nl/SupportingAaps/HowCanIHelp.md index 6aeca540f5b9..7b90cca588fd 100644 --- a/docs/CROWDIN/nl/SupportingAaps/HowCanIHelp.md +++ b/docs/CROWDIN/nl/SupportingAaps/HowCanIHelp.md @@ -15,7 +15,7 @@ Yay! Look at the issues, ask in the discord channel, there is always a lot to do Great, this is a highly appreciated thing and a good way to pay it forward! * The discord channel regarding the wiki can be found here: [AndroidAPS](https://discord.gg/4fQUWHZ4Mw). -* A guide how to do commits on English wiki can be found here: [How to make a PR](../SupportingAaps/HowToEditTheDocs.md). Other languages are only translated from english and can't be edited for consistency reasons. +* A guide how to do commits on English wiki can be found here: [How to make a PR](../SupportingAaps/HowToEditTheDocs.md). Other languages are only translated from English and can't be edited for consistency reasons. ## I do speak multiple languages and want to translate the app or the documentation @@ -23,7 +23,7 @@ If you are translating something for the first time, please start with translati You are welcome to start as a translator for the documentation in parallel or later. -You can check the state of translations for the languages app and documentation [here](StateOfTranslations). +You can check the state of translations for the languages app and documentation [here](#StateOfTranslations). * If you want to translate **the app** to other languages (thank you), please use [crowdin](https://crowdin.com/project/androidaps). * If you want to translate **the docs** to other languages (thank you), please use [crowdin](https://crowdin.com/project/androidapsdocs). diff --git a/docs/CROWDIN/nl/UsefulLinks/FAQ.md b/docs/CROWDIN/nl/UsefulLinks/FAQ.md index 804624a1fa54..f6d1e71358e5 100644 --- a/docs/CROWDIN/nl/UsefulLinks/FAQ.md +++ b/docs/CROWDIN/nl/UsefulLinks/FAQ.md @@ -247,7 +247,7 @@ Copy on an internet drive (Dropbox, Google etc) : all the apks you used to insta Please -- check [Troubleshooting Android Studio](../GettingHelp/TroubleshootingAndroidStudio) for typical errors and +- check [Troubleshooting Android Studio](../GettingHelp/TroubleshootingAndroidStudio.md) for typical errors and - the tipps for with a [step by step walktrough](https://docs.google.com/document/d/1oc7aG0qrIMvK57unMqPEOoLt-J8UT1mxTKdTAxm8-po). ### I'm stuck on an objective and need help. diff --git a/docs/CROWDIN/nl/images/troubleshooting/profiletuning/FastRise.png b/docs/CROWDIN/nl/images/troubleshooting/profiletuning/FastRise.png new file mode 100644 index 000000000000..ba35b5bb6bf0 Binary files /dev/null and b/docs/CROWDIN/nl/images/troubleshooting/profiletuning/FastRise.png differ diff --git a/docs/CROWDIN/nl/images/troubleshooting/profiletuning/NegativeInsulin.png b/docs/CROWDIN/nl/images/troubleshooting/profiletuning/NegativeInsulin.png new file mode 100644 index 000000000000..7c39c50d00df Binary files /dev/null and b/docs/CROWDIN/nl/images/troubleshooting/profiletuning/NegativeInsulin.png differ diff --git a/docs/CROWDIN/nl/images/troubleshooting/profiletuning/NegativeInsulin2.png b/docs/CROWDIN/nl/images/troubleshooting/profiletuning/NegativeInsulin2.png new file mode 100644 index 000000000000..4bd840d597ad Binary files /dev/null and b/docs/CROWDIN/nl/images/troubleshooting/profiletuning/NegativeInsulin2.png differ diff --git a/docs/CROWDIN/nl/images/troubleshooting/profiletuning/PositiveInsulin.png b/docs/CROWDIN/nl/images/troubleshooting/profiletuning/PositiveInsulin.png new file mode 100644 index 000000000000..e50e806ebf01 Binary files /dev/null and b/docs/CROWDIN/nl/images/troubleshooting/profiletuning/PositiveInsulin.png differ diff --git a/docs/CROWDIN/nl/images/troubleshooting/profiletuning/StrongISF.png b/docs/CROWDIN/nl/images/troubleshooting/profiletuning/StrongISF.png new file mode 100644 index 000000000000..ca16a1ad1b9d Binary files /dev/null and b/docs/CROWDIN/nl/images/troubleshooting/profiletuning/StrongISF.png differ diff --git a/docs/CROWDIN/nl/images/troubleshooting/profiletuning/StuckHigh.png b/docs/CROWDIN/nl/images/troubleshooting/profiletuning/StuckHigh.png new file mode 100644 index 000000000000..1fbeefc01c50 Binary files /dev/null and b/docs/CROWDIN/nl/images/troubleshooting/profiletuning/StuckHigh.png differ diff --git a/docs/CROWDIN/nl/index.md b/docs/CROWDIN/nl/index.md index 8040ea21f09f..82d0c2e450c5 100644 --- a/docs/CROWDIN/nl/index.md +++ b/docs/CROWDIN/nl/index.md @@ -159,6 +159,7 @@ Updating to a new version of AAPS <./Maintenance/UpdateToNewVersion.md> Where can I get help with AAPS <./GettingHelp/WhereCanIGetHelp.md> General troubleshooting <./GettingHelp/GeneralTroubleshooting.md> - Bluetooth troubleshooting <./GettingHelp/BluetoothTroubleshooting.md> +Profile Tuning Guide <./GettingHelp/ProfileTuning.md> Troubleshooting Android Studio <./GettingHelp/TroubleshootingAndroidStudio.md> Accessing logfiles <./GettingHelp/AccessingLogFiles.md> ``` diff --git a/docs/CROWDIN/pb/Getting-Started/Introduction.md b/docs/CROWDIN/pb/Getting-Started/Introduction.md index 1ac5379b3690..62790c0604f4 100644 --- a/docs/CROWDIN/pb/Getting-Started/Introduction.md +++ b/docs/CROWDIN/pb/Getting-Started/Introduction.md @@ -192,7 +192,7 @@ If a malicious attack was made on your insulin pump, these strategies would sign #### Safety considerations around improving blood glucose control too fast -A rapid reduction in HbA1c and improved blood glucose control sounds appealing. However, reducing average blood glucose levels _too fast_ by starting any closed loop system can cause permanent damage, including to the eyes, and painful neuropathy that never goes away. This damage can be avoided simply by reducing levels more slowly. If you currently have an elevated HbA1c and are moving to AAPS (or any other closed loop system), please discuss this potential risk with your clinical team before starting, and agree a timeplan with them. More general information on how to reduce your glucose levels safely, including links to medical literature is given in the [safety section [here](#preparing-safety-first). +A rapid reduction in HbA1c and improved blood glucose control sounds appealing. However, reducing average blood glucose levels _too fast_ by starting any closed loop system can cause permanent damage, including to the eyes, and painful neuropathy that never goes away. This damage can be avoided simply by reducing levels more slowly. If you currently have an elevated HbA1c and are moving to AAPS (or any other closed loop system), please discuss this potential risk with your clinical team before starting, and agree a time plan with them. More general information on how to reduce your glucose levels safely, including links to medical literature is given in the safety section [here](#preparing-safety-first). #### Medical safety around devices, consumable supplies and other medications diff --git a/docs/CROWDIN/pb/GettingHelp/ProfileTuning.md b/docs/CROWDIN/pb/GettingHelp/ProfileTuning.md new file mode 100644 index 000000000000..566fc5f5c43b --- /dev/null +++ b/docs/CROWDIN/pb/GettingHelp/ProfileTuning.md @@ -0,0 +1,136 @@ +# **Tweaking the AAPS' Profile** + +```{admonition} This is NOT a medical advice +:class: warning +Please work with your care team for support and advice on your diabetes management.
+Use this guide only once you have [set up your **Profile** correctly](https://androidaps.readthedocs.io/en/latest/SettingUpAaps/YourAapsProfile.md), following all **AAPS** objectives. +``` + +This guide explains the logic of the OpenAPS algorithm results with a given __Profile__, and provides information about which values to adjust when certain situations are observed. The suggestions about basal testing below may diverge from what your care team advises + +Using **closed loop** may make basal testing easier and may significantly reduce the hypo risk if your __Profile__ basal is too strong. + +## **Changing profile's settings, how to proceed** + +1. Ensure you have read and understand __AAPS’__ recommended settings and advice below. Not following this advice will make the whole process problematic and less likely to get a well tuned __Profile__ +2. Carefully observe and compare, **over several days**, what is happening with your __BG__ and __IOB__. +3. Keep an eye out for patterns that happen around the same time (almost) everyday. +4. It's important to do this over several days. Poor results tend to be yielded from using data observed on a single day to make __Profile’s__ adjustment decisions. +5. After you have observed a repeatable pattern of behavior, e.g. at 1PM you see a spike in __BG__ or a negative __IOB__ value, only then start to make small changes to your __Profile__. +6. It's important to limit the changes you make to one thing at a time. E.g. increase your basal by 10% around 1PM. +7. After every change, it's important to monitor the impact on your __BG__ and __IOB__ for the next few days. +8. Repeat this pattern, observe, decide, tweak again if needed + +Don't rush, go slow! + +## **Recommended settings and advice while tweaking basal** + +- Do all testing with [closed loop enabled](#AapsScreens-loop-status). +- **Turn OFF all [automations](../DailyLifeWithAAPS/Automations.md)** +- **Turn OFF [DynISF](#Open-APS-features-DynamicISF), [AutoISF](../AdvancedOptions/DevBranch.md), [AutoSens](#Open-APS-features-autosens)** so that they will not try to adapt your profile. +- Do not make manual user actions (manual bolus, temp targets etc…) while testing: let the system use the **Profile** settings only. +- For the [additional graphs](#AapsScreens-section-g-additional-graphs): on graph 1, use Insulin On Board, Carbs On Board (and Sensitivity change). On graph 2, use Deviations and Blood Glucose Impact. When asking for advice, always include those on your screenshots. +- COB=0[*](#profiletuning-cob-zero) +- No physical activities. +- No stress. +- No illness. +- No extreme weather like high or low temperatures. +- If your [basal rate profile](#your-aaps-profile-basal-rates) is correct, when you are on target with COB=0[*](#profiletuning-cob-zero) and IOB=0, you will remain constantly on target whatever your ISF (ISF is only used when you are higher than your target). +- You need to check the actual IOB but also, the IOB chart to see how the IOB was during the past few hours. + +(profiletuning-cob-zero)= + +***COB = 0** + +Meaning that the meal is digested, and there are no more carbs in your body. + +AAPS might indicate [COB=0 while you still have carbs on board](../DailyLifeWithAAPS/CobCalculation.md). + +## **[Profile](../SettingUpAaps/YourAapsProfile.md) definitions** + +A too **strong Profile** indicates some combination of the following: + +- [ISF](#insulin-sensitivity-factor-isf) number is too small +- The [basal](#basal-rates) number is too big +- [I:C](#insulin-to-carb-ratio-icr) number is too small + +## **IOB Observations** + +*Note: you can also use Loopalyzer IOB graph in Nightscout reports to view IOB on several days.* + +If you observe the following patterns after a few days, consider the following changes + +### **IOB positive** + +- **Profile** basal might not be strong enough (this could also be because of things like unannounced food, illness, bad site absorption, etc.) + +![Positive IOB](../images/troubleshooting/profiletuning/PositiveInsulin.png) + +### **IOB negative** + +- Default basal too strong +- May be the effect from past exercise/physical activity + +![Negative IOB](../images/troubleshooting/profiletuning/NegativeInsulin.png) + +- Previous meal: too much bolus (which resulted in a very long zero temp basal) + +![Negative IOB](../images/troubleshooting/profiletuning/NegativeInsulin2.png) + +## **BG Target Observations** + +### **Stuck High** + +- __ISF__ ‘s number is high and not strong enough (calculated insulin is too weak) + +![Stuck High](../images/troubleshooting/profiletuning/StuckHigh.png) + +- __Profile__ basal might not be strong enough (SMBs do not have enough "basal stock" to use) +- A security ([MaxIOB](#Open-APS-features-maximum-total-iob-openaps-cant-go-over)?) might have kicked in and is limiting insulin injection. Verify in the [SMB](#Open-APS-features-super-micro-bolus-smb) tab. +- Technical issue: site absorption, infusion set, ... + +### **Stuck Low** + +- __ISF__ too strong and the number needs to be raised higher +- __Profile__ basal too strong (if also negative IOB) + +### **Rollercoaster (ups and downs)** + +- **ISF** too strong? See your [AAPS Profile](#your-aaps-profile-insulin-sensitivity-factor) + +![Rollercoaster](../images/troubleshooting/profiletuning/StrongISF.png) + +## **BG After Meals Observations** + +### **Fast rise and BG going high** + +- Food contains fast carbs +- Consider doing a pre-bolus +- Bolus (IC or injected %) not strong enough + +![Rise High](../images/troubleshooting/profiletuning/FastRise.png) + +### **Fast rise and then BG going low** + +- Consider doing a pre-bolus, profile might be too aggressive (over correction of the raise) +- Bolus too strong + + + +## **[How to calculate your I:C](#your-aaps-profile-insulin-to-carbs-ratio)** + +1. First, you need the correct default basal settings in your **Profile**. +2. Start on target, better without negative IOB. +3. Record the total insulin given in the pump tab (or pump history) and call it Start insulin C4. Very accurately measure a known portion of carbs, and record the start time and Start IOB. Then enter carbs and bolus information into AAPS using the wizard (with the current configured CI). Don't forget to eat the carbs ;) +4. After some hours, when COB=0[*](#profiletuning-cob-zero) and you're back on target, record end time, and note down the End IOB, check the total insulin given as before and call it End insulin. *NOTE: The time frame is NOT important, as long as it is longer than your digestion* +5. From the difference between Start and End insulin amount, subtract/add the difference end IOB - start IOB. Then subtract the basal insulin calculated from your profile settings. +6. If __BG__ is in target, you'll have the total insulin used to “digest” your carbs. Calculate your **I:C**. + +### **Explanations for the I:C calculations** + +- With a **Profile** that has the correct default basal rate, during any time frame, you should stay on target and have an IOB near 0. You get your **Profile** basal only. +- You add carbs and bolus to this mix. Wait till your body digests all the carbs and be back on **BG** target. Your insulin usage will be the sum of your basal + the insulin needed for the carbs. You calculate the insulin used for your basal (by using your **Profile**) and the surplus will be the insulin used to digest the carbs. +- If the time frame is too short, there will be carbs undigested, thus your "insulin needed for the carbs" will be wrong. +- If the time frame is too long, nothing bad will happen. You'll use all your carbs and you'll get more basal. At the end, you'll subtract the basal from the total insulin used, the extended time frame (with more basal use) will not affect the result. + +Originally written up by @Robby (Discord) on tips and tricks to help tune your AAPS Profile, reviewed and edited by the community (thank you!). diff --git a/docs/CROWDIN/pb/SettingUpAaps/ComputerBuild.md b/docs/CROWDIN/pb/SettingUpAaps/ComputerBuild.md index 1908571be457..a914bc316879 100644 --- a/docs/CROWDIN/pb/SettingUpAaps/ComputerBuild.md +++ b/docs/CROWDIN/pb/SettingUpAaps/ComputerBuild.md @@ -70,7 +70,7 @@ The Gradle version is linked to the source code, you will always get the correct ## Help and support during the building process -If you run into difficulties in the process of building the **AAPS** app, there is a dedicated [**troubleshooting Android Studio**](../GettingHelp/TroubleshootingAndroidStudio) section, please consult that first. +If you run into difficulties in the process of building the **AAPS** app, there is a dedicated [**troubleshooting Android Studio**](../GettingHelp/TroubleshootingAndroidStudio.md) section, please consult that first. If you think something in the building instructions is wrong, missing or confusing, or you are still struggling, please reach out to other **AAPS** users group on [Facebook](https://www.facebook.com/groups/AndroidAPSUsers) or [Discord](https://discord.gg/4fQUWHZ4Mw). If you want to change something yourself (updating screenshots _etc_), please submit a [pull request (PR)](../SupportingAaps/HowToEditTheDocs.md). @@ -409,7 +409,7 @@ Android Studio will display the information "BUILD SUCCESSFUL" after build is fi ![Build finished](../images/Building-the-App/049_ReopenNotification.png) -**_If the build was not successful, refer to the [Android Studio Troubleshooting section](../GettingHelp/TroubleshootingAndroidStudio)._** +**_If the build was not successful, refer to the [Android Studio Troubleshooting section](../GettingHelp/TroubleshootingAndroidStudio.md)._** In the Notifications box, click on the blue link "locate": diff --git a/docs/CROWDIN/pb/SettingUpAaps/Preferences.md b/docs/CROWDIN/pb/SettingUpAaps/Preferences.md index d3840f615d9c..ac05db6c7586 100644 --- a/docs/CROWDIN/pb/SettingUpAaps/Preferences.md +++ b/docs/CROWDIN/pb/SettingUpAaps/Preferences.md @@ -300,7 +300,7 @@ Switch between Open Loop, Closed Loop and Low Glucose Suspend (LGS). ![Config builder - loop mode](../images/ConfigBuilder_LoopLGS.png) -(Preferences-pen-loop)= +(Preferences-open-loop)= #### Open Loop **AAPS** continuously evaluates all available data (IOB, COB, BG...) and makes treatment suggestions (temporary basal rates) on how to adjust your therapy if necessary. diff --git a/docs/CROWDIN/pb/SettingUpAaps/YourAapsProfile.md b/docs/CROWDIN/pb/SettingUpAaps/YourAapsProfile.md index e80d7962c766..d85a9d60170d 100644 --- a/docs/CROWDIN/pb/SettingUpAaps/YourAapsProfile.md +++ b/docs/CROWDIN/pb/SettingUpAaps/YourAapsProfile.md @@ -123,11 +123,13 @@ The **figure below** shows an example of how the basal rates can be set in an ** Setting your basal rates right is done by trial and error, and should be done in consultation with your diabetic team. -There are basal testing methods which usually entails observing your basal rates and insulin needs during an intermittent fasting over a 24-hour period. Although you need to test your basal rates for the whole day, it is not recommended to fast during 24h straight. This is because the body triggers mechanisms such as hormones to compensate. A recommended way is to fast 3 times for 8 hours. +There are basal testing methods which usually entails observing your basal rates and insulin needs during an intermittent fasting over a 24-hour period. Although you need to test your basal rates for the whole day, it is not recommended to fast during 24h straight. This is because the body triggers mechanisms such as hormones to compensate. A recommended way is to fast 3 times for 8 hours. -The recommended method is to suspend the loop, which will revert to your default background basal rate. Observe how your **BG** changes: if it is dropping, basal rate is too high. And vice versa.
An alternative method (may be more tricky) is to keep the loop running, and seeing how **IOB** changes. If **IOB** is negative, your basal rate is too high. And vice versa. Beware that this method relies on **ISF** to correct **BG**, and thus depends on other variables to be set reasonably well for it to be successful.
Another way of adjusting your basal rates is to watch the loop action during the night, when all COB have decayed. This method is particularly useful for children, when fasting is difficult or insulin needs change often. [Dr Saleh Adi from Tidepool](https://www.youtube.com/watch?v=-fpWnGRhLSo) provides useful ways on how to analyse overnight BG lines in order to optimise your basal rates. +The recommended method is to suspend the loop (for safety you can set AAPS to [**LGS**](#Preferences-aps-mode) to avoid lows, as done for achieving [objective 6](#objectives-objective6)), which will revert to your default background basal rate. Observe how your **BG** changes: if it is dropping, basal rate is too high. And vice versa.
An alternative method (may be more tricky) is to keep the loop running, and seeing how **IOB** changes. If **IOB** is negative, your basal rate is too high. And vice versa. Beware that this method relies on **ISF** to correct **BG**, and thus depends on other variables to be set reasonably well for it to be successful.
Another way of adjusting your basal rates is to watch the loop action during the night, when all COB have decayed. This method is particularly useful for children, when fasting is difficult or insulin needs change often. [Dr Saleh Adi from Tidepool](https://www.youtube.com/watch?v=-fpWnGRhLSo) provides useful ways on how to analyze overnight BG lines in order to optimize your basal rates. -When taking action on the result of your basal testing, changes in the **Profile** should be done 1 hour before the rise/drop. Repeat the test as necessary until you are comfortable with your **basal rates** settings. +See [here](../GettingHelp/ProfileTuning.md) how to tweak your basal profile, analyzing patterns in closed loop. + +When taking action on the result of your basal testing, changes in the **Profile** should be done 1 to 2 hours (depends on your insulin type) before the rise/drop. Repeat the test as necessary until you are comfortable with your **basal rates** settings. (your-aaps-profile-insulin-sensitivity-factor)= diff --git a/docs/CROWDIN/pb/SupportingAaps/HowCanIHelp.md b/docs/CROWDIN/pb/SupportingAaps/HowCanIHelp.md index 6aeca540f5b9..7b90cca588fd 100644 --- a/docs/CROWDIN/pb/SupportingAaps/HowCanIHelp.md +++ b/docs/CROWDIN/pb/SupportingAaps/HowCanIHelp.md @@ -15,7 +15,7 @@ Yay! Look at the issues, ask in the discord channel, there is always a lot to do Great, this is a highly appreciated thing and a good way to pay it forward! * The discord channel regarding the wiki can be found here: [AndroidAPS](https://discord.gg/4fQUWHZ4Mw). -* A guide how to do commits on English wiki can be found here: [How to make a PR](../SupportingAaps/HowToEditTheDocs.md). Other languages are only translated from english and can't be edited for consistency reasons. +* A guide how to do commits on English wiki can be found here: [How to make a PR](../SupportingAaps/HowToEditTheDocs.md). Other languages are only translated from English and can't be edited for consistency reasons. ## I do speak multiple languages and want to translate the app or the documentation @@ -23,7 +23,7 @@ If you are translating something for the first time, please start with translati You are welcome to start as a translator for the documentation in parallel or later. -You can check the state of translations for the languages app and documentation [here](StateOfTranslations). +You can check the state of translations for the languages app and documentation [here](#StateOfTranslations). * If you want to translate **the app** to other languages (thank you), please use [crowdin](https://crowdin.com/project/androidaps). * If you want to translate **the docs** to other languages (thank you), please use [crowdin](https://crowdin.com/project/androidapsdocs). diff --git a/docs/CROWDIN/pb/UsefulLinks/FAQ.md b/docs/CROWDIN/pb/UsefulLinks/FAQ.md index c8002cf52e15..caf03caea9f7 100644 --- a/docs/CROWDIN/pb/UsefulLinks/FAQ.md +++ b/docs/CROWDIN/pb/UsefulLinks/FAQ.md @@ -247,7 +247,7 @@ Copy on an internet drive (Dropbox, Google etc) : all the apks you used to insta Please -- check [Troubleshooting Android Studio](../GettingHelp/TroubleshootingAndroidStudio) for typical errors and +- check [Troubleshooting Android Studio](../GettingHelp/TroubleshootingAndroidStudio.md) for typical errors and - the tipps for with a [step by step walktrough](https://docs.google.com/document/d/1oc7aG0qrIMvK57unMqPEOoLt-J8UT1mxTKdTAxm8-po). ### I'm stuck on an objective and need help. diff --git a/docs/CROWDIN/pb/images/troubleshooting/profiletuning/FastRise.png b/docs/CROWDIN/pb/images/troubleshooting/profiletuning/FastRise.png new file mode 100644 index 000000000000..ba35b5bb6bf0 Binary files /dev/null and b/docs/CROWDIN/pb/images/troubleshooting/profiletuning/FastRise.png differ diff --git a/docs/CROWDIN/pb/images/troubleshooting/profiletuning/NegativeInsulin.png b/docs/CROWDIN/pb/images/troubleshooting/profiletuning/NegativeInsulin.png new file mode 100644 index 000000000000..7c39c50d00df Binary files /dev/null and b/docs/CROWDIN/pb/images/troubleshooting/profiletuning/NegativeInsulin.png differ diff --git a/docs/CROWDIN/pb/images/troubleshooting/profiletuning/NegativeInsulin2.png b/docs/CROWDIN/pb/images/troubleshooting/profiletuning/NegativeInsulin2.png new file mode 100644 index 000000000000..4bd840d597ad Binary files /dev/null and b/docs/CROWDIN/pb/images/troubleshooting/profiletuning/NegativeInsulin2.png differ diff --git a/docs/CROWDIN/pb/images/troubleshooting/profiletuning/PositiveInsulin.png b/docs/CROWDIN/pb/images/troubleshooting/profiletuning/PositiveInsulin.png new file mode 100644 index 000000000000..e50e806ebf01 Binary files /dev/null and b/docs/CROWDIN/pb/images/troubleshooting/profiletuning/PositiveInsulin.png differ diff --git a/docs/CROWDIN/pb/images/troubleshooting/profiletuning/StrongISF.png b/docs/CROWDIN/pb/images/troubleshooting/profiletuning/StrongISF.png new file mode 100644 index 000000000000..ca16a1ad1b9d Binary files /dev/null and b/docs/CROWDIN/pb/images/troubleshooting/profiletuning/StrongISF.png differ diff --git a/docs/CROWDIN/pb/images/troubleshooting/profiletuning/StuckHigh.png b/docs/CROWDIN/pb/images/troubleshooting/profiletuning/StuckHigh.png new file mode 100644 index 000000000000..1fbeefc01c50 Binary files /dev/null and b/docs/CROWDIN/pb/images/troubleshooting/profiletuning/StuckHigh.png differ diff --git a/docs/CROWDIN/pb/index.md b/docs/CROWDIN/pb/index.md index 2fb75a4a2686..a5a9d8e7d39c 100644 --- a/docs/CROWDIN/pb/index.md +++ b/docs/CROWDIN/pb/index.md @@ -159,6 +159,7 @@ Updating to a new version of AAPS <./Maintenance/UpdateToNewVersion.md> Where can I get help with AAPS <./GettingHelp/WhereCanIGetHelp.md> General troubleshooting <./GettingHelp/GeneralTroubleshooting.md> - Bluetooth troubleshooting <./GettingHelp/BluetoothTroubleshooting.md> +Profile Tuning Guide <./GettingHelp/ProfileTuning.md> Troubleshooting Android Studio <./GettingHelp/TroubleshootingAndroidStudio.md> Accessing logfiles <./GettingHelp/AccessingLogFiles.md> ``` diff --git a/docs/CROWDIN/pl/Getting-Started/Introduction.md b/docs/CROWDIN/pl/Getting-Started/Introduction.md index 1ac5379b3690..62790c0604f4 100644 --- a/docs/CROWDIN/pl/Getting-Started/Introduction.md +++ b/docs/CROWDIN/pl/Getting-Started/Introduction.md @@ -192,7 +192,7 @@ If a malicious attack was made on your insulin pump, these strategies would sign #### Safety considerations around improving blood glucose control too fast -A rapid reduction in HbA1c and improved blood glucose control sounds appealing. However, reducing average blood glucose levels _too fast_ by starting any closed loop system can cause permanent damage, including to the eyes, and painful neuropathy that never goes away. This damage can be avoided simply by reducing levels more slowly. If you currently have an elevated HbA1c and are moving to AAPS (or any other closed loop system), please discuss this potential risk with your clinical team before starting, and agree a timeplan with them. More general information on how to reduce your glucose levels safely, including links to medical literature is given in the [safety section [here](#preparing-safety-first). +A rapid reduction in HbA1c and improved blood glucose control sounds appealing. However, reducing average blood glucose levels _too fast_ by starting any closed loop system can cause permanent damage, including to the eyes, and painful neuropathy that never goes away. This damage can be avoided simply by reducing levels more slowly. If you currently have an elevated HbA1c and are moving to AAPS (or any other closed loop system), please discuss this potential risk with your clinical team before starting, and agree a time plan with them. More general information on how to reduce your glucose levels safely, including links to medical literature is given in the safety section [here](#preparing-safety-first). #### Medical safety around devices, consumable supplies and other medications diff --git a/docs/CROWDIN/pl/GettingHelp/ProfileTuning.md b/docs/CROWDIN/pl/GettingHelp/ProfileTuning.md new file mode 100644 index 000000000000..566fc5f5c43b --- /dev/null +++ b/docs/CROWDIN/pl/GettingHelp/ProfileTuning.md @@ -0,0 +1,136 @@ +# **Tweaking the AAPS' Profile** + +```{admonition} This is NOT a medical advice +:class: warning +Please work with your care team for support and advice on your diabetes management.
+Use this guide only once you have [set up your **Profile** correctly](https://androidaps.readthedocs.io/en/latest/SettingUpAaps/YourAapsProfile.md), following all **AAPS** objectives. +``` + +This guide explains the logic of the OpenAPS algorithm results with a given __Profile__, and provides information about which values to adjust when certain situations are observed. The suggestions about basal testing below may diverge from what your care team advises + +Using **closed loop** may make basal testing easier and may significantly reduce the hypo risk if your __Profile__ basal is too strong. + +## **Changing profile's settings, how to proceed** + +1. Ensure you have read and understand __AAPS’__ recommended settings and advice below. Not following this advice will make the whole process problematic and less likely to get a well tuned __Profile__ +2. Carefully observe and compare, **over several days**, what is happening with your __BG__ and __IOB__. +3. Keep an eye out for patterns that happen around the same time (almost) everyday. +4. It's important to do this over several days. Poor results tend to be yielded from using data observed on a single day to make __Profile’s__ adjustment decisions. +5. After you have observed a repeatable pattern of behavior, e.g. at 1PM you see a spike in __BG__ or a negative __IOB__ value, only then start to make small changes to your __Profile__. +6. It's important to limit the changes you make to one thing at a time. E.g. increase your basal by 10% around 1PM. +7. After every change, it's important to monitor the impact on your __BG__ and __IOB__ for the next few days. +8. Repeat this pattern, observe, decide, tweak again if needed + +Don't rush, go slow! + +## **Recommended settings and advice while tweaking basal** + +- Do all testing with [closed loop enabled](#AapsScreens-loop-status). +- **Turn OFF all [automations](../DailyLifeWithAAPS/Automations.md)** +- **Turn OFF [DynISF](#Open-APS-features-DynamicISF), [AutoISF](../AdvancedOptions/DevBranch.md), [AutoSens](#Open-APS-features-autosens)** so that they will not try to adapt your profile. +- Do not make manual user actions (manual bolus, temp targets etc…) while testing: let the system use the **Profile** settings only. +- For the [additional graphs](#AapsScreens-section-g-additional-graphs): on graph 1, use Insulin On Board, Carbs On Board (and Sensitivity change). On graph 2, use Deviations and Blood Glucose Impact. When asking for advice, always include those on your screenshots. +- COB=0[*](#profiletuning-cob-zero) +- No physical activities. +- No stress. +- No illness. +- No extreme weather like high or low temperatures. +- If your [basal rate profile](#your-aaps-profile-basal-rates) is correct, when you are on target with COB=0[*](#profiletuning-cob-zero) and IOB=0, you will remain constantly on target whatever your ISF (ISF is only used when you are higher than your target). +- You need to check the actual IOB but also, the IOB chart to see how the IOB was during the past few hours. + +(profiletuning-cob-zero)= + +***COB = 0** + +Meaning that the meal is digested, and there are no more carbs in your body. + +AAPS might indicate [COB=0 while you still have carbs on board](../DailyLifeWithAAPS/CobCalculation.md). + +## **[Profile](../SettingUpAaps/YourAapsProfile.md) definitions** + +A too **strong Profile** indicates some combination of the following: + +- [ISF](#insulin-sensitivity-factor-isf) number is too small +- The [basal](#basal-rates) number is too big +- [I:C](#insulin-to-carb-ratio-icr) number is too small + +## **IOB Observations** + +*Note: you can also use Loopalyzer IOB graph in Nightscout reports to view IOB on several days.* + +If you observe the following patterns after a few days, consider the following changes + +### **IOB positive** + +- **Profile** basal might not be strong enough (this could also be because of things like unannounced food, illness, bad site absorption, etc.) + +![Positive IOB](../images/troubleshooting/profiletuning/PositiveInsulin.png) + +### **IOB negative** + +- Default basal too strong +- May be the effect from past exercise/physical activity + +![Negative IOB](../images/troubleshooting/profiletuning/NegativeInsulin.png) + +- Previous meal: too much bolus (which resulted in a very long zero temp basal) + +![Negative IOB](../images/troubleshooting/profiletuning/NegativeInsulin2.png) + +## **BG Target Observations** + +### **Stuck High** + +- __ISF__ ‘s number is high and not strong enough (calculated insulin is too weak) + +![Stuck High](../images/troubleshooting/profiletuning/StuckHigh.png) + +- __Profile__ basal might not be strong enough (SMBs do not have enough "basal stock" to use) +- A security ([MaxIOB](#Open-APS-features-maximum-total-iob-openaps-cant-go-over)?) might have kicked in and is limiting insulin injection. Verify in the [SMB](#Open-APS-features-super-micro-bolus-smb) tab. +- Technical issue: site absorption, infusion set, ... + +### **Stuck Low** + +- __ISF__ too strong and the number needs to be raised higher +- __Profile__ basal too strong (if also negative IOB) + +### **Rollercoaster (ups and downs)** + +- **ISF** too strong? See your [AAPS Profile](#your-aaps-profile-insulin-sensitivity-factor) + +![Rollercoaster](../images/troubleshooting/profiletuning/StrongISF.png) + +## **BG After Meals Observations** + +### **Fast rise and BG going high** + +- Food contains fast carbs +- Consider doing a pre-bolus +- Bolus (IC or injected %) not strong enough + +![Rise High](../images/troubleshooting/profiletuning/FastRise.png) + +### **Fast rise and then BG going low** + +- Consider doing a pre-bolus, profile might be too aggressive (over correction of the raise) +- Bolus too strong + + + +## **[How to calculate your I:C](#your-aaps-profile-insulin-to-carbs-ratio)** + +1. First, you need the correct default basal settings in your **Profile**. +2. Start on target, better without negative IOB. +3. Record the total insulin given in the pump tab (or pump history) and call it Start insulin C4. Very accurately measure a known portion of carbs, and record the start time and Start IOB. Then enter carbs and bolus information into AAPS using the wizard (with the current configured CI). Don't forget to eat the carbs ;) +4. After some hours, when COB=0[*](#profiletuning-cob-zero) and you're back on target, record end time, and note down the End IOB, check the total insulin given as before and call it End insulin. *NOTE: The time frame is NOT important, as long as it is longer than your digestion* +5. From the difference between Start and End insulin amount, subtract/add the difference end IOB - start IOB. Then subtract the basal insulin calculated from your profile settings. +6. If __BG__ is in target, you'll have the total insulin used to “digest” your carbs. Calculate your **I:C**. + +### **Explanations for the I:C calculations** + +- With a **Profile** that has the correct default basal rate, during any time frame, you should stay on target and have an IOB near 0. You get your **Profile** basal only. +- You add carbs and bolus to this mix. Wait till your body digests all the carbs and be back on **BG** target. Your insulin usage will be the sum of your basal + the insulin needed for the carbs. You calculate the insulin used for your basal (by using your **Profile**) and the surplus will be the insulin used to digest the carbs. +- If the time frame is too short, there will be carbs undigested, thus your "insulin needed for the carbs" will be wrong. +- If the time frame is too long, nothing bad will happen. You'll use all your carbs and you'll get more basal. At the end, you'll subtract the basal from the total insulin used, the extended time frame (with more basal use) will not affect the result. + +Originally written up by @Robby (Discord) on tips and tricks to help tune your AAPS Profile, reviewed and edited by the community (thank you!). diff --git a/docs/CROWDIN/pl/SettingUpAaps/ComputerBuild.md b/docs/CROWDIN/pl/SettingUpAaps/ComputerBuild.md index 1908571be457..a914bc316879 100644 --- a/docs/CROWDIN/pl/SettingUpAaps/ComputerBuild.md +++ b/docs/CROWDIN/pl/SettingUpAaps/ComputerBuild.md @@ -70,7 +70,7 @@ The Gradle version is linked to the source code, you will always get the correct ## Help and support during the building process -If you run into difficulties in the process of building the **AAPS** app, there is a dedicated [**troubleshooting Android Studio**](../GettingHelp/TroubleshootingAndroidStudio) section, please consult that first. +If you run into difficulties in the process of building the **AAPS** app, there is a dedicated [**troubleshooting Android Studio**](../GettingHelp/TroubleshootingAndroidStudio.md) section, please consult that first. If you think something in the building instructions is wrong, missing or confusing, or you are still struggling, please reach out to other **AAPS** users group on [Facebook](https://www.facebook.com/groups/AndroidAPSUsers) or [Discord](https://discord.gg/4fQUWHZ4Mw). If you want to change something yourself (updating screenshots _etc_), please submit a [pull request (PR)](../SupportingAaps/HowToEditTheDocs.md). @@ -409,7 +409,7 @@ Android Studio will display the information "BUILD SUCCESSFUL" after build is fi ![Build finished](../images/Building-the-App/049_ReopenNotification.png) -**_If the build was not successful, refer to the [Android Studio Troubleshooting section](../GettingHelp/TroubleshootingAndroidStudio)._** +**_If the build was not successful, refer to the [Android Studio Troubleshooting section](../GettingHelp/TroubleshootingAndroidStudio.md)._** In the Notifications box, click on the blue link "locate": diff --git a/docs/CROWDIN/pl/SettingUpAaps/Preferences.md b/docs/CROWDIN/pl/SettingUpAaps/Preferences.md index 400bbf12b5c7..40856479484d 100644 --- a/docs/CROWDIN/pl/SettingUpAaps/Preferences.md +++ b/docs/CROWDIN/pl/SettingUpAaps/Preferences.md @@ -300,7 +300,7 @@ Switch between Open Loop, Closed Loop and Low Glucose Suspend (LGS). ![Config builder - loop mode](../images/ConfigBuilder_LoopLGS.png) -(Preferences-pen-loop)= +(Preferences-open-loop)= #### Open Loop **AAPS** continuously evaluates all available data (IOB, COB, BG...) and makes treatment suggestions (temporary basal rates) on how to adjust your therapy if necessary. diff --git a/docs/CROWDIN/pl/SettingUpAaps/YourAapsProfile.md b/docs/CROWDIN/pl/SettingUpAaps/YourAapsProfile.md index 82b3f6234cba..93322ebb8e02 100644 --- a/docs/CROWDIN/pl/SettingUpAaps/YourAapsProfile.md +++ b/docs/CROWDIN/pl/SettingUpAaps/YourAapsProfile.md @@ -123,11 +123,13 @@ The **figure below** shows an example of how the basal rates can be set in an ** Setting your basal rates right is done by trial and error, and should be done in consultation with your diabetic team. -There are basal testing methods which usually entails observing your basal rates and insulin needs during an intermittent fasting over a 24-hour period. Although you need to test your basal rates for the whole day, it is not recommended to fast during 24h straight. This is because the body triggers mechanisms such as hormones to compensate. A recommended way is to fast 3 times for 8 hours. +There are basal testing methods which usually entails observing your basal rates and insulin needs during an intermittent fasting over a 24-hour period. Although you need to test your basal rates for the whole day, it is not recommended to fast during 24h straight. This is because the body triggers mechanisms such as hormones to compensate. A recommended way is to fast 3 times for 8 hours. -The recommended method is to suspend the loop, which will revert to your default background basal rate. Observe how your **BG** changes: if it is dropping, basal rate is too high. And vice versa.
An alternative method (may be more tricky) is to keep the loop running, and seeing how **IOB** changes. If **IOB** is negative, your basal rate is too high. And vice versa. Beware that this method relies on **ISF** to correct **BG**, and thus depends on other variables to be set reasonably well for it to be successful.
Another way of adjusting your basal rates is to watch the loop action during the night, when all COB have decayed. This method is particularly useful for children, when fasting is difficult or insulin needs change often. [Dr Saleh Adi from Tidepool](https://www.youtube.com/watch?v=-fpWnGRhLSo) provides useful ways on how to analyse overnight BG lines in order to optimise your basal rates. +The recommended method is to suspend the loop (for safety you can set AAPS to [**LGS**](#Preferences-aps-mode) to avoid lows, as done for achieving [objective 6](#objectives-objective6)), which will revert to your default background basal rate. Observe how your **BG** changes: if it is dropping, basal rate is too high. And vice versa.
An alternative method (may be more tricky) is to keep the loop running, and seeing how **IOB** changes. If **IOB** is negative, your basal rate is too high. And vice versa. Beware that this method relies on **ISF** to correct **BG**, and thus depends on other variables to be set reasonably well for it to be successful.
Another way of adjusting your basal rates is to watch the loop action during the night, when all COB have decayed. This method is particularly useful for children, when fasting is difficult or insulin needs change often. [Dr Saleh Adi from Tidepool](https://www.youtube.com/watch?v=-fpWnGRhLSo) provides useful ways on how to analyze overnight BG lines in order to optimize your basal rates. -When taking action on the result of your basal testing, changes in the **Profile** should be done 1 hour before the rise/drop. Repeat the test as necessary until you are comfortable with your **basal rates** settings. +See [here](../GettingHelp/ProfileTuning.md) how to tweak your basal profile, analyzing patterns in closed loop. + +When taking action on the result of your basal testing, changes in the **Profile** should be done 1 to 2 hours (depends on your insulin type) before the rise/drop. Repeat the test as necessary until you are comfortable with your **basal rates** settings. (your-aaps-profile-insulin-sensitivity-factor)= diff --git a/docs/CROWDIN/pl/SupportingAaps/HowCanIHelp.md b/docs/CROWDIN/pl/SupportingAaps/HowCanIHelp.md index 6aeca540f5b9..7b90cca588fd 100644 --- a/docs/CROWDIN/pl/SupportingAaps/HowCanIHelp.md +++ b/docs/CROWDIN/pl/SupportingAaps/HowCanIHelp.md @@ -15,7 +15,7 @@ Yay! Look at the issues, ask in the discord channel, there is always a lot to do Great, this is a highly appreciated thing and a good way to pay it forward! * The discord channel regarding the wiki can be found here: [AndroidAPS](https://discord.gg/4fQUWHZ4Mw). -* A guide how to do commits on English wiki can be found here: [How to make a PR](../SupportingAaps/HowToEditTheDocs.md). Other languages are only translated from english and can't be edited for consistency reasons. +* A guide how to do commits on English wiki can be found here: [How to make a PR](../SupportingAaps/HowToEditTheDocs.md). Other languages are only translated from English and can't be edited for consistency reasons. ## I do speak multiple languages and want to translate the app or the documentation @@ -23,7 +23,7 @@ If you are translating something for the first time, please start with translati You are welcome to start as a translator for the documentation in parallel or later. -You can check the state of translations for the languages app and documentation [here](StateOfTranslations). +You can check the state of translations for the languages app and documentation [here](#StateOfTranslations). * If you want to translate **the app** to other languages (thank you), please use [crowdin](https://crowdin.com/project/androidaps). * If you want to translate **the docs** to other languages (thank you), please use [crowdin](https://crowdin.com/project/androidapsdocs). diff --git a/docs/CROWDIN/pl/UsefulLinks/FAQ.md b/docs/CROWDIN/pl/UsefulLinks/FAQ.md index 02271e05710d..c4a71a49a36c 100644 --- a/docs/CROWDIN/pl/UsefulLinks/FAQ.md +++ b/docs/CROWDIN/pl/UsefulLinks/FAQ.md @@ -247,7 +247,7 @@ Copy on an internet drive (Dropbox, Google etc) : all the apks you used to insta Please -- check [Troubleshooting Android Studio](../GettingHelp/TroubleshootingAndroidStudio) for typical errors and +- check [Troubleshooting Android Studio](../GettingHelp/TroubleshootingAndroidStudio.md) for typical errors and - the tipps for with a [step by step walktrough](https://docs.google.com/document/d/1oc7aG0qrIMvK57unMqPEOoLt-J8UT1mxTKdTAxm8-po). ### I'm stuck on an objective and need help. diff --git a/docs/CROWDIN/pl/images/troubleshooting/profiletuning/FastRise.png b/docs/CROWDIN/pl/images/troubleshooting/profiletuning/FastRise.png new file mode 100644 index 000000000000..ba35b5bb6bf0 Binary files /dev/null and b/docs/CROWDIN/pl/images/troubleshooting/profiletuning/FastRise.png differ diff --git a/docs/CROWDIN/pl/images/troubleshooting/profiletuning/NegativeInsulin.png b/docs/CROWDIN/pl/images/troubleshooting/profiletuning/NegativeInsulin.png new file mode 100644 index 000000000000..7c39c50d00df Binary files /dev/null and b/docs/CROWDIN/pl/images/troubleshooting/profiletuning/NegativeInsulin.png differ diff --git a/docs/CROWDIN/pl/images/troubleshooting/profiletuning/NegativeInsulin2.png b/docs/CROWDIN/pl/images/troubleshooting/profiletuning/NegativeInsulin2.png new file mode 100644 index 000000000000..4bd840d597ad Binary files /dev/null and b/docs/CROWDIN/pl/images/troubleshooting/profiletuning/NegativeInsulin2.png differ diff --git a/docs/CROWDIN/pl/images/troubleshooting/profiletuning/PositiveInsulin.png b/docs/CROWDIN/pl/images/troubleshooting/profiletuning/PositiveInsulin.png new file mode 100644 index 000000000000..e50e806ebf01 Binary files /dev/null and b/docs/CROWDIN/pl/images/troubleshooting/profiletuning/PositiveInsulin.png differ diff --git a/docs/CROWDIN/pl/images/troubleshooting/profiletuning/StrongISF.png b/docs/CROWDIN/pl/images/troubleshooting/profiletuning/StrongISF.png new file mode 100644 index 000000000000..ca16a1ad1b9d Binary files /dev/null and b/docs/CROWDIN/pl/images/troubleshooting/profiletuning/StrongISF.png differ diff --git a/docs/CROWDIN/pl/images/troubleshooting/profiletuning/StuckHigh.png b/docs/CROWDIN/pl/images/troubleshooting/profiletuning/StuckHigh.png new file mode 100644 index 000000000000..1fbeefc01c50 Binary files /dev/null and b/docs/CROWDIN/pl/images/troubleshooting/profiletuning/StuckHigh.png differ diff --git a/docs/CROWDIN/pl/index.md b/docs/CROWDIN/pl/index.md index 110162820f8d..1a3fadb01216 100644 --- a/docs/CROWDIN/pl/index.md +++ b/docs/CROWDIN/pl/index.md @@ -159,6 +159,7 @@ Updating to a new version of AAPS <./Maintenance/UpdateToNewVersion.md> Where can I get help with AAPS <./GettingHelp/WhereCanIGetHelp.md> General troubleshooting <./GettingHelp/GeneralTroubleshooting.md> - Bluetooth troubleshooting <./GettingHelp/BluetoothTroubleshooting.md> +Profile Tuning Guide <./GettingHelp/ProfileTuning.md> Troubleshooting Android Studio <./GettingHelp/TroubleshootingAndroidStudio.md> Accessing logfiles <./GettingHelp/AccessingLogFiles.md> ``` diff --git a/docs/CROWDIN/pt/Getting-Started/Introduction.md b/docs/CROWDIN/pt/Getting-Started/Introduction.md index 1ac5379b3690..62790c0604f4 100644 --- a/docs/CROWDIN/pt/Getting-Started/Introduction.md +++ b/docs/CROWDIN/pt/Getting-Started/Introduction.md @@ -192,7 +192,7 @@ If a malicious attack was made on your insulin pump, these strategies would sign #### Safety considerations around improving blood glucose control too fast -A rapid reduction in HbA1c and improved blood glucose control sounds appealing. However, reducing average blood glucose levels _too fast_ by starting any closed loop system can cause permanent damage, including to the eyes, and painful neuropathy that never goes away. This damage can be avoided simply by reducing levels more slowly. If you currently have an elevated HbA1c and are moving to AAPS (or any other closed loop system), please discuss this potential risk with your clinical team before starting, and agree a timeplan with them. More general information on how to reduce your glucose levels safely, including links to medical literature is given in the [safety section [here](#preparing-safety-first). +A rapid reduction in HbA1c and improved blood glucose control sounds appealing. However, reducing average blood glucose levels _too fast_ by starting any closed loop system can cause permanent damage, including to the eyes, and painful neuropathy that never goes away. This damage can be avoided simply by reducing levels more slowly. If you currently have an elevated HbA1c and are moving to AAPS (or any other closed loop system), please discuss this potential risk with your clinical team before starting, and agree a time plan with them. More general information on how to reduce your glucose levels safely, including links to medical literature is given in the safety section [here](#preparing-safety-first). #### Medical safety around devices, consumable supplies and other medications diff --git a/docs/CROWDIN/pt/GettingHelp/ProfileTuning.md b/docs/CROWDIN/pt/GettingHelp/ProfileTuning.md new file mode 100644 index 000000000000..566fc5f5c43b --- /dev/null +++ b/docs/CROWDIN/pt/GettingHelp/ProfileTuning.md @@ -0,0 +1,136 @@ +# **Tweaking the AAPS' Profile** + +```{admonition} This is NOT a medical advice +:class: warning +Please work with your care team for support and advice on your diabetes management.
+Use this guide only once you have [set up your **Profile** correctly](https://androidaps.readthedocs.io/en/latest/SettingUpAaps/YourAapsProfile.md), following all **AAPS** objectives. +``` + +This guide explains the logic of the OpenAPS algorithm results with a given __Profile__, and provides information about which values to adjust when certain situations are observed. The suggestions about basal testing below may diverge from what your care team advises + +Using **closed loop** may make basal testing easier and may significantly reduce the hypo risk if your __Profile__ basal is too strong. + +## **Changing profile's settings, how to proceed** + +1. Ensure you have read and understand __AAPS’__ recommended settings and advice below. Not following this advice will make the whole process problematic and less likely to get a well tuned __Profile__ +2. Carefully observe and compare, **over several days**, what is happening with your __BG__ and __IOB__. +3. Keep an eye out for patterns that happen around the same time (almost) everyday. +4. It's important to do this over several days. Poor results tend to be yielded from using data observed on a single day to make __Profile’s__ adjustment decisions. +5. After you have observed a repeatable pattern of behavior, e.g. at 1PM you see a spike in __BG__ or a negative __IOB__ value, only then start to make small changes to your __Profile__. +6. It's important to limit the changes you make to one thing at a time. E.g. increase your basal by 10% around 1PM. +7. After every change, it's important to monitor the impact on your __BG__ and __IOB__ for the next few days. +8. Repeat this pattern, observe, decide, tweak again if needed + +Don't rush, go slow! + +## **Recommended settings and advice while tweaking basal** + +- Do all testing with [closed loop enabled](#AapsScreens-loop-status). +- **Turn OFF all [automations](../DailyLifeWithAAPS/Automations.md)** +- **Turn OFF [DynISF](#Open-APS-features-DynamicISF), [AutoISF](../AdvancedOptions/DevBranch.md), [AutoSens](#Open-APS-features-autosens)** so that they will not try to adapt your profile. +- Do not make manual user actions (manual bolus, temp targets etc…) while testing: let the system use the **Profile** settings only. +- For the [additional graphs](#AapsScreens-section-g-additional-graphs): on graph 1, use Insulin On Board, Carbs On Board (and Sensitivity change). On graph 2, use Deviations and Blood Glucose Impact. When asking for advice, always include those on your screenshots. +- COB=0[*](#profiletuning-cob-zero) +- No physical activities. +- No stress. +- No illness. +- No extreme weather like high or low temperatures. +- If your [basal rate profile](#your-aaps-profile-basal-rates) is correct, when you are on target with COB=0[*](#profiletuning-cob-zero) and IOB=0, you will remain constantly on target whatever your ISF (ISF is only used when you are higher than your target). +- You need to check the actual IOB but also, the IOB chart to see how the IOB was during the past few hours. + +(profiletuning-cob-zero)= + +***COB = 0** + +Meaning that the meal is digested, and there are no more carbs in your body. + +AAPS might indicate [COB=0 while you still have carbs on board](../DailyLifeWithAAPS/CobCalculation.md). + +## **[Profile](../SettingUpAaps/YourAapsProfile.md) definitions** + +A too **strong Profile** indicates some combination of the following: + +- [ISF](#insulin-sensitivity-factor-isf) number is too small +- The [basal](#basal-rates) number is too big +- [I:C](#insulin-to-carb-ratio-icr) number is too small + +## **IOB Observations** + +*Note: you can also use Loopalyzer IOB graph in Nightscout reports to view IOB on several days.* + +If you observe the following patterns after a few days, consider the following changes + +### **IOB positive** + +- **Profile** basal might not be strong enough (this could also be because of things like unannounced food, illness, bad site absorption, etc.) + +![Positive IOB](../images/troubleshooting/profiletuning/PositiveInsulin.png) + +### **IOB negative** + +- Default basal too strong +- May be the effect from past exercise/physical activity + +![Negative IOB](../images/troubleshooting/profiletuning/NegativeInsulin.png) + +- Previous meal: too much bolus (which resulted in a very long zero temp basal) + +![Negative IOB](../images/troubleshooting/profiletuning/NegativeInsulin2.png) + +## **BG Target Observations** + +### **Stuck High** + +- __ISF__ ‘s number is high and not strong enough (calculated insulin is too weak) + +![Stuck High](../images/troubleshooting/profiletuning/StuckHigh.png) + +- __Profile__ basal might not be strong enough (SMBs do not have enough "basal stock" to use) +- A security ([MaxIOB](#Open-APS-features-maximum-total-iob-openaps-cant-go-over)?) might have kicked in and is limiting insulin injection. Verify in the [SMB](#Open-APS-features-super-micro-bolus-smb) tab. +- Technical issue: site absorption, infusion set, ... + +### **Stuck Low** + +- __ISF__ too strong and the number needs to be raised higher +- __Profile__ basal too strong (if also negative IOB) + +### **Rollercoaster (ups and downs)** + +- **ISF** too strong? See your [AAPS Profile](#your-aaps-profile-insulin-sensitivity-factor) + +![Rollercoaster](../images/troubleshooting/profiletuning/StrongISF.png) + +## **BG After Meals Observations** + +### **Fast rise and BG going high** + +- Food contains fast carbs +- Consider doing a pre-bolus +- Bolus (IC or injected %) not strong enough + +![Rise High](../images/troubleshooting/profiletuning/FastRise.png) + +### **Fast rise and then BG going low** + +- Consider doing a pre-bolus, profile might be too aggressive (over correction of the raise) +- Bolus too strong + + + +## **[How to calculate your I:C](#your-aaps-profile-insulin-to-carbs-ratio)** + +1. First, you need the correct default basal settings in your **Profile**. +2. Start on target, better without negative IOB. +3. Record the total insulin given in the pump tab (or pump history) and call it Start insulin C4. Very accurately measure a known portion of carbs, and record the start time and Start IOB. Then enter carbs and bolus information into AAPS using the wizard (with the current configured CI). Don't forget to eat the carbs ;) +4. After some hours, when COB=0[*](#profiletuning-cob-zero) and you're back on target, record end time, and note down the End IOB, check the total insulin given as before and call it End insulin. *NOTE: The time frame is NOT important, as long as it is longer than your digestion* +5. From the difference between Start and End insulin amount, subtract/add the difference end IOB - start IOB. Then subtract the basal insulin calculated from your profile settings. +6. If __BG__ is in target, you'll have the total insulin used to “digest” your carbs. Calculate your **I:C**. + +### **Explanations for the I:C calculations** + +- With a **Profile** that has the correct default basal rate, during any time frame, you should stay on target and have an IOB near 0. You get your **Profile** basal only. +- You add carbs and bolus to this mix. Wait till your body digests all the carbs and be back on **BG** target. Your insulin usage will be the sum of your basal + the insulin needed for the carbs. You calculate the insulin used for your basal (by using your **Profile**) and the surplus will be the insulin used to digest the carbs. +- If the time frame is too short, there will be carbs undigested, thus your "insulin needed for the carbs" will be wrong. +- If the time frame is too long, nothing bad will happen. You'll use all your carbs and you'll get more basal. At the end, you'll subtract the basal from the total insulin used, the extended time frame (with more basal use) will not affect the result. + +Originally written up by @Robby (Discord) on tips and tricks to help tune your AAPS Profile, reviewed and edited by the community (thank you!). diff --git a/docs/CROWDIN/pt/SettingUpAaps/ComputerBuild.md b/docs/CROWDIN/pt/SettingUpAaps/ComputerBuild.md index cdf11df2303d..228a3b11d793 100644 --- a/docs/CROWDIN/pt/SettingUpAaps/ComputerBuild.md +++ b/docs/CROWDIN/pt/SettingUpAaps/ComputerBuild.md @@ -70,7 +70,7 @@ The Gradle version is linked to the source code, you will always get the correct ## Help and support during the building process -If you run into difficulties in the process of building the **AAPS** app, there is a dedicated [**troubleshooting Android Studio**](../GettingHelp/TroubleshootingAndroidStudio) section, please consult that first. +If you run into difficulties in the process of building the **AAPS** app, there is a dedicated [**troubleshooting Android Studio**](../GettingHelp/TroubleshootingAndroidStudio.md) section, please consult that first. If you think something in the building instructions is wrong, missing or confusing, or you are still struggling, please reach out to other **AAPS** users group on [Facebook](https://www.facebook.com/groups/AndroidAPSUsers) or [Discord](https://discord.gg/4fQUWHZ4Mw). If you want to change something yourself (updating screenshots _etc_), please submit a [pull request (PR)](../SupportingAaps/HowToEditTheDocs.md). @@ -409,7 +409,7 @@ Android Studio will display the information "BUILD SUCCESSFUL" after build is fi ![Build finished](../images/Building-the-App/049_ReopenNotification.png) -**_If the build was not successful, refer to the [Android Studio Troubleshooting section](../GettingHelp/TroubleshootingAndroidStudio)._** +**_If the build was not successful, refer to the [Android Studio Troubleshooting section](../GettingHelp/TroubleshootingAndroidStudio.md)._** In the Notifications box, click on the blue link "locate": diff --git a/docs/CROWDIN/pt/SettingUpAaps/Preferences.md b/docs/CROWDIN/pt/SettingUpAaps/Preferences.md index 2183eabad71c..f894ea51f903 100644 --- a/docs/CROWDIN/pt/SettingUpAaps/Preferences.md +++ b/docs/CROWDIN/pt/SettingUpAaps/Preferences.md @@ -300,7 +300,7 @@ Switch between Open Loop, Closed Loop and Low Glucose Suspend (LGS). ![Config builder - loop mode](../images/ConfigBuilder_LoopLGS.png) -(Preferences-pen-loop)= +(Preferences-open-loop)= #### Open Loop **AAPS** continuously evaluates all available data (IOB, COB, BG...) and makes treatment suggestions (temporary basal rates) on how to adjust your therapy if necessary. diff --git a/docs/CROWDIN/pt/SettingUpAaps/YourAapsProfile.md b/docs/CROWDIN/pt/SettingUpAaps/YourAapsProfile.md index 82b3f6234cba..93322ebb8e02 100644 --- a/docs/CROWDIN/pt/SettingUpAaps/YourAapsProfile.md +++ b/docs/CROWDIN/pt/SettingUpAaps/YourAapsProfile.md @@ -123,11 +123,13 @@ The **figure below** shows an example of how the basal rates can be set in an ** Setting your basal rates right is done by trial and error, and should be done in consultation with your diabetic team. -There are basal testing methods which usually entails observing your basal rates and insulin needs during an intermittent fasting over a 24-hour period. Although you need to test your basal rates for the whole day, it is not recommended to fast during 24h straight. This is because the body triggers mechanisms such as hormones to compensate. A recommended way is to fast 3 times for 8 hours. +There are basal testing methods which usually entails observing your basal rates and insulin needs during an intermittent fasting over a 24-hour period. Although you need to test your basal rates for the whole day, it is not recommended to fast during 24h straight. This is because the body triggers mechanisms such as hormones to compensate. A recommended way is to fast 3 times for 8 hours. -The recommended method is to suspend the loop, which will revert to your default background basal rate. Observe how your **BG** changes: if it is dropping, basal rate is too high. And vice versa.
An alternative method (may be more tricky) is to keep the loop running, and seeing how **IOB** changes. If **IOB** is negative, your basal rate is too high. And vice versa. Beware that this method relies on **ISF** to correct **BG**, and thus depends on other variables to be set reasonably well for it to be successful.
Another way of adjusting your basal rates is to watch the loop action during the night, when all COB have decayed. This method is particularly useful for children, when fasting is difficult or insulin needs change often. [Dr Saleh Adi from Tidepool](https://www.youtube.com/watch?v=-fpWnGRhLSo) provides useful ways on how to analyse overnight BG lines in order to optimise your basal rates. +The recommended method is to suspend the loop (for safety you can set AAPS to [**LGS**](#Preferences-aps-mode) to avoid lows, as done for achieving [objective 6](#objectives-objective6)), which will revert to your default background basal rate. Observe how your **BG** changes: if it is dropping, basal rate is too high. And vice versa.
An alternative method (may be more tricky) is to keep the loop running, and seeing how **IOB** changes. If **IOB** is negative, your basal rate is too high. And vice versa. Beware that this method relies on **ISF** to correct **BG**, and thus depends on other variables to be set reasonably well for it to be successful.
Another way of adjusting your basal rates is to watch the loop action during the night, when all COB have decayed. This method is particularly useful for children, when fasting is difficult or insulin needs change often. [Dr Saleh Adi from Tidepool](https://www.youtube.com/watch?v=-fpWnGRhLSo) provides useful ways on how to analyze overnight BG lines in order to optimize your basal rates. -When taking action on the result of your basal testing, changes in the **Profile** should be done 1 hour before the rise/drop. Repeat the test as necessary until you are comfortable with your **basal rates** settings. +See [here](../GettingHelp/ProfileTuning.md) how to tweak your basal profile, analyzing patterns in closed loop. + +When taking action on the result of your basal testing, changes in the **Profile** should be done 1 to 2 hours (depends on your insulin type) before the rise/drop. Repeat the test as necessary until you are comfortable with your **basal rates** settings. (your-aaps-profile-insulin-sensitivity-factor)= diff --git a/docs/CROWDIN/pt/SupportingAaps/HowCanIHelp.md b/docs/CROWDIN/pt/SupportingAaps/HowCanIHelp.md index 6aeca540f5b9..7b90cca588fd 100644 --- a/docs/CROWDIN/pt/SupportingAaps/HowCanIHelp.md +++ b/docs/CROWDIN/pt/SupportingAaps/HowCanIHelp.md @@ -15,7 +15,7 @@ Yay! Look at the issues, ask in the discord channel, there is always a lot to do Great, this is a highly appreciated thing and a good way to pay it forward! * The discord channel regarding the wiki can be found here: [AndroidAPS](https://discord.gg/4fQUWHZ4Mw). -* A guide how to do commits on English wiki can be found here: [How to make a PR](../SupportingAaps/HowToEditTheDocs.md). Other languages are only translated from english and can't be edited for consistency reasons. +* A guide how to do commits on English wiki can be found here: [How to make a PR](../SupportingAaps/HowToEditTheDocs.md). Other languages are only translated from English and can't be edited for consistency reasons. ## I do speak multiple languages and want to translate the app or the documentation @@ -23,7 +23,7 @@ If you are translating something for the first time, please start with translati You are welcome to start as a translator for the documentation in parallel or later. -You can check the state of translations for the languages app and documentation [here](StateOfTranslations). +You can check the state of translations for the languages app and documentation [here](#StateOfTranslations). * If you want to translate **the app** to other languages (thank you), please use [crowdin](https://crowdin.com/project/androidaps). * If you want to translate **the docs** to other languages (thank you), please use [crowdin](https://crowdin.com/project/androidapsdocs). diff --git a/docs/CROWDIN/pt/UsefulLinks/FAQ.md b/docs/CROWDIN/pt/UsefulLinks/FAQ.md index af0d8bc20305..ad39718cbfb1 100644 --- a/docs/CROWDIN/pt/UsefulLinks/FAQ.md +++ b/docs/CROWDIN/pt/UsefulLinks/FAQ.md @@ -247,7 +247,7 @@ Copy on an internet drive (Dropbox, Google etc) : all the apks you used to insta Please -- check [Troubleshooting Android Studio](../GettingHelp/TroubleshootingAndroidStudio) for typical errors and +- check [Troubleshooting Android Studio](../GettingHelp/TroubleshootingAndroidStudio.md) for typical errors and - the tipps for with a [step by step walktrough](https://docs.google.com/document/d/1oc7aG0qrIMvK57unMqPEOoLt-J8UT1mxTKdTAxm8-po). ### I'm stuck on an objective and need help. diff --git a/docs/CROWDIN/pt/images/troubleshooting/profiletuning/FastRise.png b/docs/CROWDIN/pt/images/troubleshooting/profiletuning/FastRise.png new file mode 100644 index 000000000000..ba35b5bb6bf0 Binary files /dev/null and b/docs/CROWDIN/pt/images/troubleshooting/profiletuning/FastRise.png differ diff --git a/docs/CROWDIN/pt/images/troubleshooting/profiletuning/NegativeInsulin.png b/docs/CROWDIN/pt/images/troubleshooting/profiletuning/NegativeInsulin.png new file mode 100644 index 000000000000..7c39c50d00df Binary files /dev/null and b/docs/CROWDIN/pt/images/troubleshooting/profiletuning/NegativeInsulin.png differ diff --git a/docs/CROWDIN/pt/images/troubleshooting/profiletuning/NegativeInsulin2.png b/docs/CROWDIN/pt/images/troubleshooting/profiletuning/NegativeInsulin2.png new file mode 100644 index 000000000000..4bd840d597ad Binary files /dev/null and b/docs/CROWDIN/pt/images/troubleshooting/profiletuning/NegativeInsulin2.png differ diff --git a/docs/CROWDIN/pt/images/troubleshooting/profiletuning/PositiveInsulin.png b/docs/CROWDIN/pt/images/troubleshooting/profiletuning/PositiveInsulin.png new file mode 100644 index 000000000000..e50e806ebf01 Binary files /dev/null and b/docs/CROWDIN/pt/images/troubleshooting/profiletuning/PositiveInsulin.png differ diff --git a/docs/CROWDIN/pt/images/troubleshooting/profiletuning/StrongISF.png b/docs/CROWDIN/pt/images/troubleshooting/profiletuning/StrongISF.png new file mode 100644 index 000000000000..ca16a1ad1b9d Binary files /dev/null and b/docs/CROWDIN/pt/images/troubleshooting/profiletuning/StrongISF.png differ diff --git a/docs/CROWDIN/pt/images/troubleshooting/profiletuning/StuckHigh.png b/docs/CROWDIN/pt/images/troubleshooting/profiletuning/StuckHigh.png new file mode 100644 index 000000000000..1fbeefc01c50 Binary files /dev/null and b/docs/CROWDIN/pt/images/troubleshooting/profiletuning/StuckHigh.png differ diff --git a/docs/CROWDIN/pt/index.md b/docs/CROWDIN/pt/index.md index fb0410e17222..c24c3cd8d033 100644 --- a/docs/CROWDIN/pt/index.md +++ b/docs/CROWDIN/pt/index.md @@ -159,6 +159,7 @@ Updating to a new version of AAPS <./Maintenance/UpdateToNewVersion.md> Where can I get help with AAPS <./GettingHelp/WhereCanIGetHelp.md> General troubleshooting <./GettingHelp/GeneralTroubleshooting.md> - Bluetooth troubleshooting <./GettingHelp/BluetoothTroubleshooting.md> +Profile Tuning Guide <./GettingHelp/ProfileTuning.md> Troubleshooting Android Studio <./GettingHelp/TroubleshootingAndroidStudio.md> Accessing logfiles <./GettingHelp/AccessingLogFiles.md> ``` diff --git a/docs/CROWDIN/ro/Getting-Started/Introduction.md b/docs/CROWDIN/ro/Getting-Started/Introduction.md index b35093c790a2..d6387ddd6562 100644 --- a/docs/CROWDIN/ro/Getting-Started/Introduction.md +++ b/docs/CROWDIN/ro/Getting-Started/Introduction.md @@ -192,7 +192,7 @@ If a malicious attack was made on your insulin pump, these strategies would sign #### Safety considerations around improving blood glucose control too fast -A rapid reduction in HbA1c and improved blood glucose control sounds appealing. However, reducing average blood glucose levels _too fast_ by starting any closed loop system can cause permanent damage, including to the eyes, and painful neuropathy that never goes away. This damage can be avoided simply by reducing levels more slowly. If you currently have an elevated HbA1c and are moving to AAPS (or any other closed loop system), please discuss this potential risk with your clinical team before starting, and agree a timeplan with them. More general information on how to reduce your glucose levels safely, including links to medical literature is given in the [safety section [here](#preparing-safety-first). +A rapid reduction in HbA1c and improved blood glucose control sounds appealing. However, reducing average blood glucose levels _too fast_ by starting any closed loop system can cause permanent damage, including to the eyes, and painful neuropathy that never goes away. This damage can be avoided simply by reducing levels more slowly. If you currently have an elevated HbA1c and are moving to AAPS (or any other closed loop system), please discuss this potential risk with your clinical team before starting, and agree a time plan with them. More general information on how to reduce your glucose levels safely, including links to medical literature is given in the safety section [here](#preparing-safety-first). #### Medical safety around devices, consumable supplies and other medications diff --git a/docs/CROWDIN/ro/GettingHelp/ProfileTuning.md b/docs/CROWDIN/ro/GettingHelp/ProfileTuning.md new file mode 100644 index 000000000000..566fc5f5c43b --- /dev/null +++ b/docs/CROWDIN/ro/GettingHelp/ProfileTuning.md @@ -0,0 +1,136 @@ +# **Tweaking the AAPS' Profile** + +```{admonition} This is NOT a medical advice +:class: warning +Please work with your care team for support and advice on your diabetes management.
+Use this guide only once you have [set up your **Profile** correctly](https://androidaps.readthedocs.io/en/latest/SettingUpAaps/YourAapsProfile.md), following all **AAPS** objectives. +``` + +This guide explains the logic of the OpenAPS algorithm results with a given __Profile__, and provides information about which values to adjust when certain situations are observed. The suggestions about basal testing below may diverge from what your care team advises + +Using **closed loop** may make basal testing easier and may significantly reduce the hypo risk if your __Profile__ basal is too strong. + +## **Changing profile's settings, how to proceed** + +1. Ensure you have read and understand __AAPS’__ recommended settings and advice below. Not following this advice will make the whole process problematic and less likely to get a well tuned __Profile__ +2. Carefully observe and compare, **over several days**, what is happening with your __BG__ and __IOB__. +3. Keep an eye out for patterns that happen around the same time (almost) everyday. +4. It's important to do this over several days. Poor results tend to be yielded from using data observed on a single day to make __Profile’s__ adjustment decisions. +5. After you have observed a repeatable pattern of behavior, e.g. at 1PM you see a spike in __BG__ or a negative __IOB__ value, only then start to make small changes to your __Profile__. +6. It's important to limit the changes you make to one thing at a time. E.g. increase your basal by 10% around 1PM. +7. After every change, it's important to monitor the impact on your __BG__ and __IOB__ for the next few days. +8. Repeat this pattern, observe, decide, tweak again if needed + +Don't rush, go slow! + +## **Recommended settings and advice while tweaking basal** + +- Do all testing with [closed loop enabled](#AapsScreens-loop-status). +- **Turn OFF all [automations](../DailyLifeWithAAPS/Automations.md)** +- **Turn OFF [DynISF](#Open-APS-features-DynamicISF), [AutoISF](../AdvancedOptions/DevBranch.md), [AutoSens](#Open-APS-features-autosens)** so that they will not try to adapt your profile. +- Do not make manual user actions (manual bolus, temp targets etc…) while testing: let the system use the **Profile** settings only. +- For the [additional graphs](#AapsScreens-section-g-additional-graphs): on graph 1, use Insulin On Board, Carbs On Board (and Sensitivity change). On graph 2, use Deviations and Blood Glucose Impact. When asking for advice, always include those on your screenshots. +- COB=0[*](#profiletuning-cob-zero) +- No physical activities. +- No stress. +- No illness. +- No extreme weather like high or low temperatures. +- If your [basal rate profile](#your-aaps-profile-basal-rates) is correct, when you are on target with COB=0[*](#profiletuning-cob-zero) and IOB=0, you will remain constantly on target whatever your ISF (ISF is only used when you are higher than your target). +- You need to check the actual IOB but also, the IOB chart to see how the IOB was during the past few hours. + +(profiletuning-cob-zero)= + +***COB = 0** + +Meaning that the meal is digested, and there are no more carbs in your body. + +AAPS might indicate [COB=0 while you still have carbs on board](../DailyLifeWithAAPS/CobCalculation.md). + +## **[Profile](../SettingUpAaps/YourAapsProfile.md) definitions** + +A too **strong Profile** indicates some combination of the following: + +- [ISF](#insulin-sensitivity-factor-isf) number is too small +- The [basal](#basal-rates) number is too big +- [I:C](#insulin-to-carb-ratio-icr) number is too small + +## **IOB Observations** + +*Note: you can also use Loopalyzer IOB graph in Nightscout reports to view IOB on several days.* + +If you observe the following patterns after a few days, consider the following changes + +### **IOB positive** + +- **Profile** basal might not be strong enough (this could also be because of things like unannounced food, illness, bad site absorption, etc.) + +![Positive IOB](../images/troubleshooting/profiletuning/PositiveInsulin.png) + +### **IOB negative** + +- Default basal too strong +- May be the effect from past exercise/physical activity + +![Negative IOB](../images/troubleshooting/profiletuning/NegativeInsulin.png) + +- Previous meal: too much bolus (which resulted in a very long zero temp basal) + +![Negative IOB](../images/troubleshooting/profiletuning/NegativeInsulin2.png) + +## **BG Target Observations** + +### **Stuck High** + +- __ISF__ ‘s number is high and not strong enough (calculated insulin is too weak) + +![Stuck High](../images/troubleshooting/profiletuning/StuckHigh.png) + +- __Profile__ basal might not be strong enough (SMBs do not have enough "basal stock" to use) +- A security ([MaxIOB](#Open-APS-features-maximum-total-iob-openaps-cant-go-over)?) might have kicked in and is limiting insulin injection. Verify in the [SMB](#Open-APS-features-super-micro-bolus-smb) tab. +- Technical issue: site absorption, infusion set, ... + +### **Stuck Low** + +- __ISF__ too strong and the number needs to be raised higher +- __Profile__ basal too strong (if also negative IOB) + +### **Rollercoaster (ups and downs)** + +- **ISF** too strong? See your [AAPS Profile](#your-aaps-profile-insulin-sensitivity-factor) + +![Rollercoaster](../images/troubleshooting/profiletuning/StrongISF.png) + +## **BG After Meals Observations** + +### **Fast rise and BG going high** + +- Food contains fast carbs +- Consider doing a pre-bolus +- Bolus (IC or injected %) not strong enough + +![Rise High](../images/troubleshooting/profiletuning/FastRise.png) + +### **Fast rise and then BG going low** + +- Consider doing a pre-bolus, profile might be too aggressive (over correction of the raise) +- Bolus too strong + + + +## **[How to calculate your I:C](#your-aaps-profile-insulin-to-carbs-ratio)** + +1. First, you need the correct default basal settings in your **Profile**. +2. Start on target, better without negative IOB. +3. Record the total insulin given in the pump tab (or pump history) and call it Start insulin C4. Very accurately measure a known portion of carbs, and record the start time and Start IOB. Then enter carbs and bolus information into AAPS using the wizard (with the current configured CI). Don't forget to eat the carbs ;) +4. After some hours, when COB=0[*](#profiletuning-cob-zero) and you're back on target, record end time, and note down the End IOB, check the total insulin given as before and call it End insulin. *NOTE: The time frame is NOT important, as long as it is longer than your digestion* +5. From the difference between Start and End insulin amount, subtract/add the difference end IOB - start IOB. Then subtract the basal insulin calculated from your profile settings. +6. If __BG__ is in target, you'll have the total insulin used to “digest” your carbs. Calculate your **I:C**. + +### **Explanations for the I:C calculations** + +- With a **Profile** that has the correct default basal rate, during any time frame, you should stay on target and have an IOB near 0. You get your **Profile** basal only. +- You add carbs and bolus to this mix. Wait till your body digests all the carbs and be back on **BG** target. Your insulin usage will be the sum of your basal + the insulin needed for the carbs. You calculate the insulin used for your basal (by using your **Profile**) and the surplus will be the insulin used to digest the carbs. +- If the time frame is too short, there will be carbs undigested, thus your "insulin needed for the carbs" will be wrong. +- If the time frame is too long, nothing bad will happen. You'll use all your carbs and you'll get more basal. At the end, you'll subtract the basal from the total insulin used, the extended time frame (with more basal use) will not affect the result. + +Originally written up by @Robby (Discord) on tips and tricks to help tune your AAPS Profile, reviewed and edited by the community (thank you!). diff --git a/docs/CROWDIN/ro/SettingUpAaps/ComputerBuild.md b/docs/CROWDIN/ro/SettingUpAaps/ComputerBuild.md index 1908571be457..a914bc316879 100644 --- a/docs/CROWDIN/ro/SettingUpAaps/ComputerBuild.md +++ b/docs/CROWDIN/ro/SettingUpAaps/ComputerBuild.md @@ -70,7 +70,7 @@ The Gradle version is linked to the source code, you will always get the correct ## Help and support during the building process -If you run into difficulties in the process of building the **AAPS** app, there is a dedicated [**troubleshooting Android Studio**](../GettingHelp/TroubleshootingAndroidStudio) section, please consult that first. +If you run into difficulties in the process of building the **AAPS** app, there is a dedicated [**troubleshooting Android Studio**](../GettingHelp/TroubleshootingAndroidStudio.md) section, please consult that first. If you think something in the building instructions is wrong, missing or confusing, or you are still struggling, please reach out to other **AAPS** users group on [Facebook](https://www.facebook.com/groups/AndroidAPSUsers) or [Discord](https://discord.gg/4fQUWHZ4Mw). If you want to change something yourself (updating screenshots _etc_), please submit a [pull request (PR)](../SupportingAaps/HowToEditTheDocs.md). @@ -409,7 +409,7 @@ Android Studio will display the information "BUILD SUCCESSFUL" after build is fi ![Build finished](../images/Building-the-App/049_ReopenNotification.png) -**_If the build was not successful, refer to the [Android Studio Troubleshooting section](../GettingHelp/TroubleshootingAndroidStudio)._** +**_If the build was not successful, refer to the [Android Studio Troubleshooting section](../GettingHelp/TroubleshootingAndroidStudio.md)._** In the Notifications box, click on the blue link "locate": diff --git a/docs/CROWDIN/ro/SettingUpAaps/Preferences.md b/docs/CROWDIN/ro/SettingUpAaps/Preferences.md index 43bc827248c7..e09d8bfc3961 100644 --- a/docs/CROWDIN/ro/SettingUpAaps/Preferences.md +++ b/docs/CROWDIN/ro/SettingUpAaps/Preferences.md @@ -300,7 +300,7 @@ Switch between Open Loop, Closed Loop and Low Glucose Suspend (LGS). ![Config builder - loop mode](../images/ConfigBuilder_LoopLGS.png) -(Preferences-pen-loop)= +(Preferences-open-loop)= #### Open Loop **AAPS** continuously evaluates all available data (IOB, COB, BG...) and makes treatment suggestions (temporary basal rates) on how to adjust your therapy if necessary. diff --git a/docs/CROWDIN/ro/SettingUpAaps/YourAapsProfile.md b/docs/CROWDIN/ro/SettingUpAaps/YourAapsProfile.md index 9217ba030254..bbdb40e04056 100644 --- a/docs/CROWDIN/ro/SettingUpAaps/YourAapsProfile.md +++ b/docs/CROWDIN/ro/SettingUpAaps/YourAapsProfile.md @@ -123,11 +123,13 @@ The **figure below** shows an example of how the basal rates can be set in an ** Setting your basal rates right is done by trial and error, and should be done in consultation with your diabetic team. -There are basal testing methods which usually entails observing your basal rates and insulin needs during an intermittent fasting over a 24-hour period. Although you need to test your basal rates for the whole day, it is not recommended to fast during 24h straight. This is because the body triggers mechanisms such as hormones to compensate. A recommended way is to fast 3 times for 8 hours. +There are basal testing methods which usually entails observing your basal rates and insulin needs during an intermittent fasting over a 24-hour period. Although you need to test your basal rates for the whole day, it is not recommended to fast during 24h straight. This is because the body triggers mechanisms such as hormones to compensate. A recommended way is to fast 3 times for 8 hours. -The recommended method is to suspend the loop, which will revert to your default background basal rate. Observe how your **BG** changes: if it is dropping, basal rate is too high. And vice versa.
An alternative method (may be more tricky) is to keep the loop running, and seeing how **IOB** changes. If **IOB** is negative, your basal rate is too high. And vice versa. Beware that this method relies on **ISF** to correct **BG**, and thus depends on other variables to be set reasonably well for it to be successful.
Another way of adjusting your basal rates is to watch the loop action during the night, when all COB have decayed. This method is particularly useful for children, when fasting is difficult or insulin needs change often. [Dr Saleh Adi from Tidepool](https://www.youtube.com/watch?v=-fpWnGRhLSo) provides useful ways on how to analyse overnight BG lines in order to optimise your basal rates. +The recommended method is to suspend the loop (for safety you can set AAPS to [**LGS**](#Preferences-aps-mode) to avoid lows, as done for achieving [objective 6](#objectives-objective6)), which will revert to your default background basal rate. Observe how your **BG** changes: if it is dropping, basal rate is too high. And vice versa.
An alternative method (may be more tricky) is to keep the loop running, and seeing how **IOB** changes. If **IOB** is negative, your basal rate is too high. And vice versa. Beware that this method relies on **ISF** to correct **BG**, and thus depends on other variables to be set reasonably well for it to be successful.
Another way of adjusting your basal rates is to watch the loop action during the night, when all COB have decayed. This method is particularly useful for children, when fasting is difficult or insulin needs change often. [Dr Saleh Adi from Tidepool](https://www.youtube.com/watch?v=-fpWnGRhLSo) provides useful ways on how to analyze overnight BG lines in order to optimize your basal rates. -When taking action on the result of your basal testing, changes in the **Profile** should be done 1 hour before the rise/drop. Repeat the test as necessary until you are comfortable with your **basal rates** settings. +See [here](../GettingHelp/ProfileTuning.md) how to tweak your basal profile, analyzing patterns in closed loop. + +When taking action on the result of your basal testing, changes in the **Profile** should be done 1 to 2 hours (depends on your insulin type) before the rise/drop. Repeat the test as necessary until you are comfortable with your **basal rates** settings. (your-aaps-profile-insulin-sensitivity-factor)= diff --git a/docs/CROWDIN/ro/SupportingAaps/HowCanIHelp.md b/docs/CROWDIN/ro/SupportingAaps/HowCanIHelp.md index 6aeca540f5b9..7b90cca588fd 100644 --- a/docs/CROWDIN/ro/SupportingAaps/HowCanIHelp.md +++ b/docs/CROWDIN/ro/SupportingAaps/HowCanIHelp.md @@ -15,7 +15,7 @@ Yay! Look at the issues, ask in the discord channel, there is always a lot to do Great, this is a highly appreciated thing and a good way to pay it forward! * The discord channel regarding the wiki can be found here: [AndroidAPS](https://discord.gg/4fQUWHZ4Mw). -* A guide how to do commits on English wiki can be found here: [How to make a PR](../SupportingAaps/HowToEditTheDocs.md). Other languages are only translated from english and can't be edited for consistency reasons. +* A guide how to do commits on English wiki can be found here: [How to make a PR](../SupportingAaps/HowToEditTheDocs.md). Other languages are only translated from English and can't be edited for consistency reasons. ## I do speak multiple languages and want to translate the app or the documentation @@ -23,7 +23,7 @@ If you are translating something for the first time, please start with translati You are welcome to start as a translator for the documentation in parallel or later. -You can check the state of translations for the languages app and documentation [here](StateOfTranslations). +You can check the state of translations for the languages app and documentation [here](#StateOfTranslations). * If you want to translate **the app** to other languages (thank you), please use [crowdin](https://crowdin.com/project/androidaps). * If you want to translate **the docs** to other languages (thank you), please use [crowdin](https://crowdin.com/project/androidapsdocs). diff --git a/docs/CROWDIN/ro/UsefulLinks/FAQ.md b/docs/CROWDIN/ro/UsefulLinks/FAQ.md index 1ae07410b9cb..574ee4a37389 100644 --- a/docs/CROWDIN/ro/UsefulLinks/FAQ.md +++ b/docs/CROWDIN/ro/UsefulLinks/FAQ.md @@ -247,7 +247,7 @@ Copy on an internet drive (Dropbox, Google etc) : all the apks you used to insta Please -- check [Troubleshooting Android Studio](../GettingHelp/TroubleshootingAndroidStudio) for typical errors and +- check [Troubleshooting Android Studio](../GettingHelp/TroubleshootingAndroidStudio.md) for typical errors and - the tipps for with a [step by step walktrough](https://docs.google.com/document/d/1oc7aG0qrIMvK57unMqPEOoLt-J8UT1mxTKdTAxm8-po). ### I'm stuck on an objective and need help. diff --git a/docs/CROWDIN/ro/images/troubleshooting/profiletuning/FastRise.png b/docs/CROWDIN/ro/images/troubleshooting/profiletuning/FastRise.png new file mode 100644 index 000000000000..ba35b5bb6bf0 Binary files /dev/null and b/docs/CROWDIN/ro/images/troubleshooting/profiletuning/FastRise.png differ diff --git a/docs/CROWDIN/ro/images/troubleshooting/profiletuning/NegativeInsulin.png b/docs/CROWDIN/ro/images/troubleshooting/profiletuning/NegativeInsulin.png new file mode 100644 index 000000000000..7c39c50d00df Binary files /dev/null and b/docs/CROWDIN/ro/images/troubleshooting/profiletuning/NegativeInsulin.png differ diff --git a/docs/CROWDIN/ro/images/troubleshooting/profiletuning/NegativeInsulin2.png b/docs/CROWDIN/ro/images/troubleshooting/profiletuning/NegativeInsulin2.png new file mode 100644 index 000000000000..4bd840d597ad Binary files /dev/null and b/docs/CROWDIN/ro/images/troubleshooting/profiletuning/NegativeInsulin2.png differ diff --git a/docs/CROWDIN/ro/images/troubleshooting/profiletuning/PositiveInsulin.png b/docs/CROWDIN/ro/images/troubleshooting/profiletuning/PositiveInsulin.png new file mode 100644 index 000000000000..e50e806ebf01 Binary files /dev/null and b/docs/CROWDIN/ro/images/troubleshooting/profiletuning/PositiveInsulin.png differ diff --git a/docs/CROWDIN/ro/images/troubleshooting/profiletuning/StrongISF.png b/docs/CROWDIN/ro/images/troubleshooting/profiletuning/StrongISF.png new file mode 100644 index 000000000000..ca16a1ad1b9d Binary files /dev/null and b/docs/CROWDIN/ro/images/troubleshooting/profiletuning/StrongISF.png differ diff --git a/docs/CROWDIN/ro/images/troubleshooting/profiletuning/StuckHigh.png b/docs/CROWDIN/ro/images/troubleshooting/profiletuning/StuckHigh.png new file mode 100644 index 000000000000..1fbeefc01c50 Binary files /dev/null and b/docs/CROWDIN/ro/images/troubleshooting/profiletuning/StuckHigh.png differ diff --git a/docs/CROWDIN/ro/index.md b/docs/CROWDIN/ro/index.md index 2fb75a4a2686..a5a9d8e7d39c 100644 --- a/docs/CROWDIN/ro/index.md +++ b/docs/CROWDIN/ro/index.md @@ -159,6 +159,7 @@ Updating to a new version of AAPS <./Maintenance/UpdateToNewVersion.md> Where can I get help with AAPS <./GettingHelp/WhereCanIGetHelp.md> General troubleshooting <./GettingHelp/GeneralTroubleshooting.md> - Bluetooth troubleshooting <./GettingHelp/BluetoothTroubleshooting.md> +Profile Tuning Guide <./GettingHelp/ProfileTuning.md> Troubleshooting Android Studio <./GettingHelp/TroubleshootingAndroidStudio.md> Accessing logfiles <./GettingHelp/AccessingLogFiles.md> ``` diff --git a/docs/CROWDIN/ru/Getting-Started/Introduction.md b/docs/CROWDIN/ru/Getting-Started/Introduction.md index c43578f07d05..2bbb0aeeaeaa 100644 --- a/docs/CROWDIN/ru/Getting-Started/Introduction.md +++ b/docs/CROWDIN/ru/Getting-Started/Introduction.md @@ -205,7 +205,7 @@ The current master version of **AAPS** (3.3.1.3) does not have any machine learn #### Соображения о безопасности слишком быстрого улучшения контроля гликемии крови -Быстрое снижение HbA1c и улучшение контроля глюкозы в крови кажется привлекательным. Однако _слишком быстрое_ снижение среднего уровня глюкозы в крови путем запуска любой системы с замкнутым контуром может привести к необратимым нарушениям, включая повреждение глаз, и болезненную непроходящую нейропатию. Этого можно избежать просто путем более медленного снижения уровней ГК. Если в настоящее время у вас повышенный уровень HbA1c и вы переходите на AAPS (или любую другую замкнутую систему), обсудите потенциальные риски с эндокринологом и согласуйте с ним график безопасного снижения целевых показателей гликемии. Более общая информация о том, как безопасно сократить уровни глюкозы, включая ссылки на медицинскую литературу приведены в разделе [безопасности [здесь](#preparing-safety-first). +Быстрое снижение HbA1c и улучшение контроля глюкозы в крови кажется привлекательным. Однако _слишком быстрое_ снижение среднего уровня глюкозы в крови путем запуска любой системы с замкнутым контуром может привести к необратимым нарушениям, включая повреждение глаз, и болезненную непроходящую нейропатию. Этого можно избежать просто путем более медленного снижения уровней ГК. If you currently have an elevated HbA1c and are moving to AAPS (or any other closed loop system), please discuss this potential risk with your clinical team before starting, and agree a time plan with them. More general information on how to reduce your glucose levels safely, including links to medical literature is given in the safety section [here](#preparing-safety-first). diff --git a/docs/CROWDIN/ru/GettingHelp/ProfileTuning.md b/docs/CROWDIN/ru/GettingHelp/ProfileTuning.md new file mode 100644 index 000000000000..eb5eaca8d494 --- /dev/null +++ b/docs/CROWDIN/ru/GettingHelp/ProfileTuning.md @@ -0,0 +1,136 @@ +# **Tweaking the AAPS' Profile** + +```{admonition} This is NOT a medical advice +:class: warning +Please work with your care team for support and advice on your diabetes management.
+Use this guide only once you have [set up your **Profile** correctly](https://androidaps.readthedocs.io/en/latest/SettingUpAaps/YourAapsProfile.md), following all **AAPS** objectives. +``` + +This guide explains the logic of the OpenAPS algorithm results with a given __Profile__, and provides information about which values to adjust when certain situations are observed. The suggestions about basal testing below may diverge from what your care team advises + +Using **closed loop** may make basal testing easier and may significantly reduce the hypo risk if your __Profile__ basal is too strong. + +## **Changing profile's settings, how to proceed** + +1. Ensure you have read and understand __AAPS’__ recommended settings and advice below. Not following this advice will make the whole process problematic and less likely to get a well tuned __Profile__ +2. Carefully observe and compare, **over several days**, what is happening with your __BG__ and __IOB__. +3. Keep an eye out for patterns that happen around the same time (almost) everyday. +4. It's important to do this over several days. Poor results tend to be yielded from using data observed on a single day to make __Profile’s__ adjustment decisions. +5. After you have observed a repeatable pattern of behavior, e.g. at 1PM you see a spike in __BG__ or a negative __IOB__ value, only then start to make small changes to your __Profile__. +6. It's important to limit the changes you make to one thing at a time. Например, increase your basal by 10% around 1PM. +7. After every change, it's important to monitor the impact on your __BG__ and __IOB__ for the next few days. +8. Repeat this pattern, observe, decide, tweak again if needed + +Don't rush, go slow! + +## **Recommended settings and advice while tweaking basal** + +- Do all testing with [closed loop enabled](#AapsScreens-loop-status). +- **Turn OFF all [automations](../DailyLifeWithAAPS/Automations.md)** +- **Turn OFF [DynISF](#Open-APS-features-DynamicISF), [AutoISF](../AdvancedOptions/DevBranch.md), [AutoSens](#Open-APS-features-autosens)** so that they will not try to adapt your profile. +- Do not make manual user actions (manual bolus, temp targets etc…) while testing: let the system use the **Profile** settings only. +- For the [additional graphs](#AapsScreens-section-g-additional-graphs): on graph 1, use Insulin On Board, Carbs On Board (and Sensitivity change). On graph 2, use Deviations and Blood Glucose Impact. When asking for advice, always include those on your screenshots. +- COB=0[*](#profiletuning-cob-zero) +- No physical activities. +- No stress. +- No illness. +- No extreme weather like high or low temperatures. +- If your [basal rate profile](#your-aaps-profile-basal-rates) is correct, when you are on target with COB=0[*](#profiletuning-cob-zero) and IOB=0, you will remain constantly on target whatever your ISF (ISF is only used when you are higher than your target). +- You need to check the actual IOB but also, the IOB chart to see how the IOB was during the past few hours. + +(profiletuning-cob-zero)= + +***COB = 0** + +Meaning that the meal is digested, and there are no more carbs in your body. + +AAPS might indicate [COB=0 while you still have carbs on board](../DailyLifeWithAAPS/CobCalculation.md). + +## **[Profile](../SettingUpAaps/YourAapsProfile.md) definitions** + +A too **strong Profile** indicates some combination of the following: + +- [ISF](#insulin-sensitivity-factor-isf) number is too small +- The [basal](#basal-rates) number is too big +- [I:C](#insulin-to-carb-ratio-icr) number is too small + +## **IOB Observations** + +*Note: you can also use Loopalyzer IOB graph in Nightscout reports to view IOB on several days.* + +If you observe the following patterns after a few days, consider the following changes + +### **IOB positive** + +- **Profile** basal might not be strong enough (this could also be because of things like unannounced food, illness, bad site absorption, etc.) + +![Positive IOB](../images/troubleshooting/profiletuning/PositiveInsulin.png) + +### **IOB negative** + +- Default basal too strong +- May be the effect from past exercise/physical activity + +![Negative IOB](../images/troubleshooting/profiletuning/NegativeInsulin.png) + +- Previous meal: too much bolus (which resulted in a very long zero temp basal) + +![Negative IOB](../images/troubleshooting/profiletuning/NegativeInsulin2.png) + +## **BG Target Observations** + +### **Stuck High** + +- __ISF__ ‘s number is high and not strong enough (calculated insulin is too weak) + +![Stuck High](../images/troubleshooting/profiletuning/StuckHigh.png) + +- __Profile__ basal might not be strong enough (SMBs do not have enough "basal stock" to use) +- A security ([MaxIOB](#Open-APS-features-maximum-total-iob-openaps-cant-go-over)?) might have kicked in and is limiting insulin injection. Verify in the [SMB](#Open-APS-features-super-micro-bolus-smb) tab. +- Technical issue: site absorption, infusion set, ... + +### **Stuck Low** + +- __ISF__ too strong and the number needs to be raised higher +- __Profile__ basal too strong (if also negative IOB) + +### **Rollercoaster (ups and downs)** + +- **ISF** too strong? See your [AAPS Profile](#your-aaps-profile-insulin-sensitivity-factor) + +![Rollercoaster](../images/troubleshooting/profiletuning/StrongISF.png) + +## **BG After Meals Observations** + +### **Fast rise and BG going high** + +- Food contains fast carbs +- Consider doing a pre-bolus +- Bolus (IC or injected %) not strong enough + +![Rise High](../images/troubleshooting/profiletuning/FastRise.png) + +### **Fast rise and then BG going low** + +- Consider doing a pre-bolus, profile might be too aggressive (over correction of the raise) +- Bolus too strong + + + +## **[How to calculate your I:C](#your-aaps-profile-insulin-to-carbs-ratio)** + +1. First, you need the correct default basal settings in your **Profile**. +2. Start on target, better without negative IOB. +3. Record the total insulin given in the pump tab (or pump history) and call it Start insulin C4. Very accurately measure a known portion of carbs, and record the start time and Start IOB. Then enter carbs and bolus information into AAPS using the wizard (with the current configured CI). Don't forget to eat the carbs ;) +4. After some hours, when COB=0[*](#profiletuning-cob-zero) and you're back on target, record end time, and note down the End IOB, check the total insulin given as before and call it End insulin. *NOTE: The time frame is NOT important, as long as it is longer than your digestion* +5. From the difference between Start and End insulin amount, subtract/add the difference end IOB - start IOB. Then subtract the basal insulin calculated from your profile settings. +6. If __BG__ is in target, you'll have the total insulin used to “digest” your carbs. Calculate your **I:C**. + +### **Explanations for the I:C calculations** + +- With a **Profile** that has the correct default basal rate, during any time frame, you should stay on target and have an IOB near 0. You get your **Profile** basal only. +- You add carbs and bolus to this mix. Wait till your body digests all the carbs and be back on **BG** target. Your insulin usage will be the sum of your basal + the insulin needed for the carbs. You calculate the insulin used for your basal (by using your **Profile**) and the surplus will be the insulin used to digest the carbs. +- If the time frame is too short, there will be carbs undigested, thus your "insulin needed for the carbs" will be wrong. +- If the time frame is too long, nothing bad will happen. You'll use all your carbs and you'll get more basal. At the end, you'll subtract the basal from the total insulin used, the extended time frame (with more basal use) will not affect the result. + +Originally written up by @Robby (Discord) on tips and tricks to help tune your AAPS Profile, reviewed and edited by the community (thank you!). diff --git a/docs/CROWDIN/ru/SettingUpAaps/ComputerBuild.md b/docs/CROWDIN/ru/SettingUpAaps/ComputerBuild.md index 287d599ae7dd..3c7355dc74e9 100644 --- a/docs/CROWDIN/ru/SettingUpAaps/ComputerBuild.md +++ b/docs/CROWDIN/ru/SettingUpAaps/ComputerBuild.md @@ -70,7 +70,7 @@ The Gradle version is linked to the source code, you will always get the correct ## Помощь и поддержка в процессе сборки -If you run into difficulties in the process of building the **AAPS** app, there is a dedicated [**troubleshooting Android Studio**](../GettingHelp/TroubleshootingAndroidStudio) section, please consult that first. +If you run into difficulties in the process of building the **AAPS** app, there is a dedicated [**troubleshooting Android Studio**](../GettingHelp/TroubleshootingAndroidStudio.md) section, please consult that first. If you think something in the building instructions is wrong, missing or confusing, or you are still struggling, please reach out to other **AAPS** users group on [Facebook](https://www.facebook.com/groups/AndroidAPSUsers) or [Discord](https://discord.gg/4fQUWHZ4Mw). If you want to change something yourself (updating screenshots _etc_), please submit a [pull request (PR)](../SupportingAaps/HowToEditTheDocs.md). @@ -411,7 +411,7 @@ Android Studio will now build the **AAPS** apk. It will show "Gradle Build runni ![Build finished](../images/Building-the-App/049_ReopenNotification.png) -**_If the build was not successful, refer to the [Android Studio Troubleshooting section](../GettingHelp/TroubleshootingAndroidStudio)._** +**_If the build was not successful, refer to the [Android Studio Troubleshooting section](../GettingHelp/TroubleshootingAndroidStudio.md)._** В окне Уведомления нажмите на синюю ссылку "locate": diff --git a/docs/CROWDIN/ru/SettingUpAaps/Preferences.md b/docs/CROWDIN/ru/SettingUpAaps/Preferences.md index 271ac4e5a1d1..6d5944e11057 100644 --- a/docs/CROWDIN/ru/SettingUpAaps/Preferences.md +++ b/docs/CROWDIN/ru/SettingUpAaps/Preferences.md @@ -300,7 +300,7 @@ Switch between Open Loop, Closed Loop and Low Glucose Suspend (LGS). ![Config builder - loop mode](../images/ConfigBuilder_LoopLGS.png) -(Preferences-pen-loop)= +(Preferences-open-loop)= #### Open Loop **AAPS** continuously evaluates all available data (IOB, COB, BG...) and makes treatment suggestions (temporary basal rates) on how to adjust your therapy if necessary. diff --git a/docs/CROWDIN/ru/SettingUpAaps/YourAapsProfile.md b/docs/CROWDIN/ru/SettingUpAaps/YourAapsProfile.md index 1a2601b6ea08..6866f72c2c7d 100644 --- a/docs/CROWDIN/ru/SettingUpAaps/YourAapsProfile.md +++ b/docs/CROWDIN/ru/SettingUpAaps/YourAapsProfile.md @@ -123,11 +123,13 @@ The **figure below** shows an example of how the basal rates can be set in an ** Setting your basal rates right is done by trial and error, and should be done in consultation with your diabetic team. -There are basal testing methods which usually entails observing your basal rates and insulin needs during an intermittent fasting over a 24-hour period. Although you need to test your basal rates for the whole day, it is not recommended to fast during 24h straight. This is because the body triggers mechanisms such as hormones to compensate. A recommended way is to fast 3 times for 8 hours. +There are basal testing methods which usually entails observing your basal rates and insulin needs during an intermittent fasting over a 24-hour period. Although you need to test your basal rates for the whole day, it is not recommended to fast during 24h straight. This is because the body triggers mechanisms such as hormones to compensate. A recommended way is to fast 3 times for 8 hours. -The recommended method is to suspend the loop, which will revert to your default background basal rate. Observe how your **BG** changes: if it is dropping, basal rate is too high. And vice versa.
An alternative method (may be more tricky) is to keep the loop running, and seeing how **IOB** changes. If **IOB** is negative, your basal rate is too high. And vice versa. Beware that this method relies on **ISF** to correct **BG**, and thus depends on other variables to be set reasonably well for it to be successful.
Another way of adjusting your basal rates is to watch the loop action during the night, when all COB have decayed. This method is particularly useful for children, when fasting is difficult or insulin needs change often. [Dr Saleh Adi from Tidepool](https://www.youtube.com/watch?v=-fpWnGRhLSo) provides useful ways on how to analyse overnight BG lines in order to optimise your basal rates. +The recommended method is to suspend the loop (for safety you can set AAPS to [**LGS**](#Preferences-aps-mode) to avoid lows, as done for achieving [objective 6](#objectives-objective6)), which will revert to your default background basal rate. Observe how your **BG** changes: if it is dropping, basal rate is too high. And vice versa.
An alternative method (may be more tricky) is to keep the loop running, and seeing how **IOB** changes. If **IOB** is negative, your basal rate is too high. And vice versa. Beware that this method relies on **ISF** to correct **BG**, and thus depends on other variables to be set reasonably well for it to be successful.
Another way of adjusting your basal rates is to watch the loop action during the night, when all COB have decayed. This method is particularly useful for children, when fasting is difficult or insulin needs change often. [Dr Saleh Adi from Tidepool](https://www.youtube.com/watch?v=-fpWnGRhLSo) provides useful ways on how to analyze overnight BG lines in order to optimize your basal rates. -When taking action on the result of your basal testing, changes in the **Profile** should be done 1 hour before the rise/drop. Repeat the test as necessary until you are comfortable with your **basal rates** settings. +See [here](../GettingHelp/ProfileTuning.md) how to tweak your basal profile, analyzing patterns in closed loop. + +When taking action on the result of your basal testing, changes in the **Profile** should be done 1 to 2 hours (depends on your insulin type) before the rise/drop. Repeat the test as necessary until you are comfortable with your **basal rates** settings. (your-aaps-profile-insulin-sensitivity-factor)= diff --git a/docs/CROWDIN/ru/SupportingAaps/HowCanIHelp.md b/docs/CROWDIN/ru/SupportingAaps/HowCanIHelp.md index 01fbff165d8d..0cea3b0e6dd3 100644 --- a/docs/CROWDIN/ru/SupportingAaps/HowCanIHelp.md +++ b/docs/CROWDIN/ru/SupportingAaps/HowCanIHelp.md @@ -15,7 +15,7 @@ Отлично, это очень ценится и это хороший способ внести свой вклад в общее дело! * Канал для обсуждения AAPS находится здесь: [AndroidAPS](https://discord.gg/4fQUWHZ4Mw). -* A guide how to do commits on English wiki can be found here: [How to make a PR](../SupportingAaps/HowToEditTheDocs.md). Другие языки переводятся только с английского языка и не могут редактироваться по соображениям целостности и последовательности. +* A guide how to do commits on English wiki can be found here: [How to make a PR](../SupportingAaps/HowToEditTheDocs.md). Other languages are only translated from English and can't be edited for consistency reasons. ## Я говорю на нескольких языках и хочу перевести приложение или документацию @@ -23,7 +23,7 @@ Вы можете приступить к переводу документации параллельно или позднее. -You can check the state of translations for the languages app and documentation [here](StateOfTranslations). +You can check the state of translations for the languages app and documentation [here](#StateOfTranslations). * Если вы хотите перевести **приложение** на другие языки (спасибо), воспользуйтесь [crowdin](https://crowdin.com/project/androidaps). * Если вы хотите перевести **документацию** на другие языки (спасибо), воспользуйтесь [crowdin](https://crowdin.com/project/androidapsdocs). diff --git a/docs/CROWDIN/ru/UsefulLinks/FAQ.md b/docs/CROWDIN/ru/UsefulLinks/FAQ.md index efd04bee7f5b..797b6a6591f1 100644 --- a/docs/CROWDIN/ru/UsefulLinks/FAQ.md +++ b/docs/CROWDIN/ru/UsefulLinks/FAQ.md @@ -247,7 +247,7 @@ If you want to share some information about AAPS and DIY looping with your clini Пожалуйста, -- check [Troubleshooting Android Studio](../GettingHelp/TroubleshootingAndroidStudio) for typical errors and +- check [Troubleshooting Android Studio](../GettingHelp/TroubleshootingAndroidStudio.md) for typical errors and - [пошаговые инструкции](https://docs.google.com/document/d/1oc7aG0qrIMvK57unMqPEOoLt-J8UT1mxTKdTAxm8-po). ### I'm stuck on an objective and need help. diff --git a/docs/CROWDIN/ru/images/troubleshooting/profiletuning/FastRise.png b/docs/CROWDIN/ru/images/troubleshooting/profiletuning/FastRise.png new file mode 100644 index 000000000000..ba35b5bb6bf0 Binary files /dev/null and b/docs/CROWDIN/ru/images/troubleshooting/profiletuning/FastRise.png differ diff --git a/docs/CROWDIN/ru/images/troubleshooting/profiletuning/NegativeInsulin.png b/docs/CROWDIN/ru/images/troubleshooting/profiletuning/NegativeInsulin.png new file mode 100644 index 000000000000..7c39c50d00df Binary files /dev/null and b/docs/CROWDIN/ru/images/troubleshooting/profiletuning/NegativeInsulin.png differ diff --git a/docs/CROWDIN/ru/images/troubleshooting/profiletuning/NegativeInsulin2.png b/docs/CROWDIN/ru/images/troubleshooting/profiletuning/NegativeInsulin2.png new file mode 100644 index 000000000000..4bd840d597ad Binary files /dev/null and b/docs/CROWDIN/ru/images/troubleshooting/profiletuning/NegativeInsulin2.png differ diff --git a/docs/CROWDIN/ru/images/troubleshooting/profiletuning/PositiveInsulin.png b/docs/CROWDIN/ru/images/troubleshooting/profiletuning/PositiveInsulin.png new file mode 100644 index 000000000000..e50e806ebf01 Binary files /dev/null and b/docs/CROWDIN/ru/images/troubleshooting/profiletuning/PositiveInsulin.png differ diff --git a/docs/CROWDIN/ru/images/troubleshooting/profiletuning/StrongISF.png b/docs/CROWDIN/ru/images/troubleshooting/profiletuning/StrongISF.png new file mode 100644 index 000000000000..ca16a1ad1b9d Binary files /dev/null and b/docs/CROWDIN/ru/images/troubleshooting/profiletuning/StrongISF.png differ diff --git a/docs/CROWDIN/ru/images/troubleshooting/profiletuning/StuckHigh.png b/docs/CROWDIN/ru/images/troubleshooting/profiletuning/StuckHigh.png new file mode 100644 index 000000000000..1fbeefc01c50 Binary files /dev/null and b/docs/CROWDIN/ru/images/troubleshooting/profiletuning/StuckHigh.png differ diff --git a/docs/CROWDIN/ru/index.md b/docs/CROWDIN/ru/index.md index 46ec0b2ce973..ae2f77d02390 100644 --- a/docs/CROWDIN/ru/index.md +++ b/docs/CROWDIN/ru/index.md @@ -159,6 +159,7 @@ Updating to a new version of AAPS <./Maintenance/UpdateToNewVersion.md> Where can I get help with AAPS <./GettingHelp/WhereCanIGetHelp.md> General troubleshooting <./GettingHelp/GeneralTroubleshooting.md> - Bluetooth troubleshooting <./GettingHelp/BluetoothTroubleshooting.md> +Profile Tuning Guide <./GettingHelp/ProfileTuning.md> Troubleshooting Android Studio <./GettingHelp/TroubleshootingAndroidStudio.md> Accessing logfiles <./GettingHelp/AccessingLogFiles.md> ``` diff --git a/docs/CROWDIN/sk/Getting-Started/Introduction.md b/docs/CROWDIN/sk/Getting-Started/Introduction.md index 482b48b9c915..26397b134c2c 100644 --- a/docs/CROWDIN/sk/Getting-Started/Introduction.md +++ b/docs/CROWDIN/sk/Getting-Started/Introduction.md @@ -192,7 +192,7 @@ Ak by došlo k škodlivému útoku na vašu inzulínovú pumpu, takéto riešeni #### Bezpečnostné aspekty týkajúce sa príliš rýchleho zlepšenia kontroly hladiny glukózy v krvi -Rýchle zníženie HbA1c a zlepšená kontrola hladiny glukózy v krvi znie lákavo. Príliš rýchle zníženie priemernej hladiny glukózy v krvi spustením akéhokoľvek systému s uzavretou slučkou však môže spôsobiť trvalé poškodenie, vrátane poškodenia očí, a bolestivú neuropatiu, ktorá nikdy nezmizne. Tomuto poškodeniu sa dá vyhnúť jednoducho pomalším znižovaním hladín. Ak máte v súčasnosti zvýšený HbA1c a prechádzate na AAPS (alebo akýkoľvek iný systém s uzavretou slučkou), pred začatím preberte toto potenciálne riziko so svojím lekárom a dohodnite si s ním časový harmonogram. Všeobecnejšie informácie o tom, ako bezpečne znížiť hladinu glukózy, vrátane odkazov na lekársku literatúru, sú uvedené v [sekcii o bezpečnosti [tu](#preparing-safety-first)]. +Rýchle zníženie HbA1c a zlepšená kontrola hladiny glukózy v krvi znie lákavo. Príliš rýchle zníženie priemernej hladiny glukózy v krvi spustením akéhokoľvek systému s uzavretou slučkou však môže spôsobiť trvalé poškodenie, vrátane poškodenia očí, a bolestivú neuropatiu, ktorá nikdy nezmizne. Tomuto poškodeniu sa dá vyhnúť jednoducho pomalším znižovaním hladín. If you currently have an elevated HbA1c and are moving to AAPS (or any other closed loop system), please discuss this potential risk with your clinical team before starting, and agree a time plan with them. More general information on how to reduce your glucose levels safely, including links to medical literature is given in the safety section [here](#preparing-safety-first). #### Bezpečnosť v oblasti zdravotníckych zariadení, spotrebného materiálu a iných liekov diff --git a/docs/CROWDIN/sk/GettingHelp/ProfileTuning.md b/docs/CROWDIN/sk/GettingHelp/ProfileTuning.md new file mode 100644 index 000000000000..566fc5f5c43b --- /dev/null +++ b/docs/CROWDIN/sk/GettingHelp/ProfileTuning.md @@ -0,0 +1,136 @@ +# **Tweaking the AAPS' Profile** + +```{admonition} This is NOT a medical advice +:class: warning +Please work with your care team for support and advice on your diabetes management.
+Use this guide only once you have [set up your **Profile** correctly](https://androidaps.readthedocs.io/en/latest/SettingUpAaps/YourAapsProfile.md), following all **AAPS** objectives. +``` + +This guide explains the logic of the OpenAPS algorithm results with a given __Profile__, and provides information about which values to adjust when certain situations are observed. The suggestions about basal testing below may diverge from what your care team advises + +Using **closed loop** may make basal testing easier and may significantly reduce the hypo risk if your __Profile__ basal is too strong. + +## **Changing profile's settings, how to proceed** + +1. Ensure you have read and understand __AAPS’__ recommended settings and advice below. Not following this advice will make the whole process problematic and less likely to get a well tuned __Profile__ +2. Carefully observe and compare, **over several days**, what is happening with your __BG__ and __IOB__. +3. Keep an eye out for patterns that happen around the same time (almost) everyday. +4. It's important to do this over several days. Poor results tend to be yielded from using data observed on a single day to make __Profile’s__ adjustment decisions. +5. After you have observed a repeatable pattern of behavior, e.g. at 1PM you see a spike in __BG__ or a negative __IOB__ value, only then start to make small changes to your __Profile__. +6. It's important to limit the changes you make to one thing at a time. E.g. increase your basal by 10% around 1PM. +7. After every change, it's important to monitor the impact on your __BG__ and __IOB__ for the next few days. +8. Repeat this pattern, observe, decide, tweak again if needed + +Don't rush, go slow! + +## **Recommended settings and advice while tweaking basal** + +- Do all testing with [closed loop enabled](#AapsScreens-loop-status). +- **Turn OFF all [automations](../DailyLifeWithAAPS/Automations.md)** +- **Turn OFF [DynISF](#Open-APS-features-DynamicISF), [AutoISF](../AdvancedOptions/DevBranch.md), [AutoSens](#Open-APS-features-autosens)** so that they will not try to adapt your profile. +- Do not make manual user actions (manual bolus, temp targets etc…) while testing: let the system use the **Profile** settings only. +- For the [additional graphs](#AapsScreens-section-g-additional-graphs): on graph 1, use Insulin On Board, Carbs On Board (and Sensitivity change). On graph 2, use Deviations and Blood Glucose Impact. When asking for advice, always include those on your screenshots. +- COB=0[*](#profiletuning-cob-zero) +- No physical activities. +- No stress. +- No illness. +- No extreme weather like high or low temperatures. +- If your [basal rate profile](#your-aaps-profile-basal-rates) is correct, when you are on target with COB=0[*](#profiletuning-cob-zero) and IOB=0, you will remain constantly on target whatever your ISF (ISF is only used when you are higher than your target). +- You need to check the actual IOB but also, the IOB chart to see how the IOB was during the past few hours. + +(profiletuning-cob-zero)= + +***COB = 0** + +Meaning that the meal is digested, and there are no more carbs in your body. + +AAPS might indicate [COB=0 while you still have carbs on board](../DailyLifeWithAAPS/CobCalculation.md). + +## **[Profile](../SettingUpAaps/YourAapsProfile.md) definitions** + +A too **strong Profile** indicates some combination of the following: + +- [ISF](#insulin-sensitivity-factor-isf) number is too small +- The [basal](#basal-rates) number is too big +- [I:C](#insulin-to-carb-ratio-icr) number is too small + +## **IOB Observations** + +*Note: you can also use Loopalyzer IOB graph in Nightscout reports to view IOB on several days.* + +If you observe the following patterns after a few days, consider the following changes + +### **IOB positive** + +- **Profile** basal might not be strong enough (this could also be because of things like unannounced food, illness, bad site absorption, etc.) + +![Positive IOB](../images/troubleshooting/profiletuning/PositiveInsulin.png) + +### **IOB negative** + +- Default basal too strong +- May be the effect from past exercise/physical activity + +![Negative IOB](../images/troubleshooting/profiletuning/NegativeInsulin.png) + +- Previous meal: too much bolus (which resulted in a very long zero temp basal) + +![Negative IOB](../images/troubleshooting/profiletuning/NegativeInsulin2.png) + +## **BG Target Observations** + +### **Stuck High** + +- __ISF__ ‘s number is high and not strong enough (calculated insulin is too weak) + +![Stuck High](../images/troubleshooting/profiletuning/StuckHigh.png) + +- __Profile__ basal might not be strong enough (SMBs do not have enough "basal stock" to use) +- A security ([MaxIOB](#Open-APS-features-maximum-total-iob-openaps-cant-go-over)?) might have kicked in and is limiting insulin injection. Verify in the [SMB](#Open-APS-features-super-micro-bolus-smb) tab. +- Technical issue: site absorption, infusion set, ... + +### **Stuck Low** + +- __ISF__ too strong and the number needs to be raised higher +- __Profile__ basal too strong (if also negative IOB) + +### **Rollercoaster (ups and downs)** + +- **ISF** too strong? See your [AAPS Profile](#your-aaps-profile-insulin-sensitivity-factor) + +![Rollercoaster](../images/troubleshooting/profiletuning/StrongISF.png) + +## **BG After Meals Observations** + +### **Fast rise and BG going high** + +- Food contains fast carbs +- Consider doing a pre-bolus +- Bolus (IC or injected %) not strong enough + +![Rise High](../images/troubleshooting/profiletuning/FastRise.png) + +### **Fast rise and then BG going low** + +- Consider doing a pre-bolus, profile might be too aggressive (over correction of the raise) +- Bolus too strong + + + +## **[How to calculate your I:C](#your-aaps-profile-insulin-to-carbs-ratio)** + +1. First, you need the correct default basal settings in your **Profile**. +2. Start on target, better without negative IOB. +3. Record the total insulin given in the pump tab (or pump history) and call it Start insulin C4. Very accurately measure a known portion of carbs, and record the start time and Start IOB. Then enter carbs and bolus information into AAPS using the wizard (with the current configured CI). Don't forget to eat the carbs ;) +4. After some hours, when COB=0[*](#profiletuning-cob-zero) and you're back on target, record end time, and note down the End IOB, check the total insulin given as before and call it End insulin. *NOTE: The time frame is NOT important, as long as it is longer than your digestion* +5. From the difference between Start and End insulin amount, subtract/add the difference end IOB - start IOB. Then subtract the basal insulin calculated from your profile settings. +6. If __BG__ is in target, you'll have the total insulin used to “digest” your carbs. Calculate your **I:C**. + +### **Explanations for the I:C calculations** + +- With a **Profile** that has the correct default basal rate, during any time frame, you should stay on target and have an IOB near 0. You get your **Profile** basal only. +- You add carbs and bolus to this mix. Wait till your body digests all the carbs and be back on **BG** target. Your insulin usage will be the sum of your basal + the insulin needed for the carbs. You calculate the insulin used for your basal (by using your **Profile**) and the surplus will be the insulin used to digest the carbs. +- If the time frame is too short, there will be carbs undigested, thus your "insulin needed for the carbs" will be wrong. +- If the time frame is too long, nothing bad will happen. You'll use all your carbs and you'll get more basal. At the end, you'll subtract the basal from the total insulin used, the extended time frame (with more basal use) will not affect the result. + +Originally written up by @Robby (Discord) on tips and tricks to help tune your AAPS Profile, reviewed and edited by the community (thank you!). diff --git a/docs/CROWDIN/sk/SettingUpAaps/ComputerBuild.md b/docs/CROWDIN/sk/SettingUpAaps/ComputerBuild.md index 1908571be457..a914bc316879 100644 --- a/docs/CROWDIN/sk/SettingUpAaps/ComputerBuild.md +++ b/docs/CROWDIN/sk/SettingUpAaps/ComputerBuild.md @@ -70,7 +70,7 @@ The Gradle version is linked to the source code, you will always get the correct ## Help and support during the building process -If you run into difficulties in the process of building the **AAPS** app, there is a dedicated [**troubleshooting Android Studio**](../GettingHelp/TroubleshootingAndroidStudio) section, please consult that first. +If you run into difficulties in the process of building the **AAPS** app, there is a dedicated [**troubleshooting Android Studio**](../GettingHelp/TroubleshootingAndroidStudio.md) section, please consult that first. If you think something in the building instructions is wrong, missing or confusing, or you are still struggling, please reach out to other **AAPS** users group on [Facebook](https://www.facebook.com/groups/AndroidAPSUsers) or [Discord](https://discord.gg/4fQUWHZ4Mw). If you want to change something yourself (updating screenshots _etc_), please submit a [pull request (PR)](../SupportingAaps/HowToEditTheDocs.md). @@ -409,7 +409,7 @@ Android Studio will display the information "BUILD SUCCESSFUL" after build is fi ![Build finished](../images/Building-the-App/049_ReopenNotification.png) -**_If the build was not successful, refer to the [Android Studio Troubleshooting section](../GettingHelp/TroubleshootingAndroidStudio)._** +**_If the build was not successful, refer to the [Android Studio Troubleshooting section](../GettingHelp/TroubleshootingAndroidStudio.md)._** In the Notifications box, click on the blue link "locate": diff --git a/docs/CROWDIN/sk/SettingUpAaps/Preferences.md b/docs/CROWDIN/sk/SettingUpAaps/Preferences.md index 36fcf4578d2f..a7290a02d01b 100644 --- a/docs/CROWDIN/sk/SettingUpAaps/Preferences.md +++ b/docs/CROWDIN/sk/SettingUpAaps/Preferences.md @@ -300,7 +300,7 @@ Prepínanie medzi otvorenou slučkou, uzavretou slučkou a pozastavením pri ní ![Konfigurátor – režim slučky](../images/ConfigBuilder_LoopLGS.png) -(Preferences-pen-loop)= +(Preferences-open-loop)= #### Otvorený okruh **AAPS** priebežne vyhodnocuje všetky dostupné údaje (IOB, COB, BG...) a v prípade potreby podáva návrhy ošetrení (dočasné bazálne dávky), ako upraviť vašu liečbu. diff --git a/docs/CROWDIN/sk/SettingUpAaps/YourAapsProfile.md b/docs/CROWDIN/sk/SettingUpAaps/YourAapsProfile.md index a128a5b29bdc..7b1adc4cfe4b 100644 --- a/docs/CROWDIN/sk/SettingUpAaps/YourAapsProfile.md +++ b/docs/CROWDIN/sk/SettingUpAaps/YourAapsProfile.md @@ -123,11 +123,13 @@ The **figure below** shows an example of how the basal rates can be set in an ** Setting your basal rates right is done by trial and error, and should be done in consultation with your diabetic team. -There are basal testing methods which usually entails observing your basal rates and insulin needs during an intermittent fasting over a 24-hour period. Although you need to test your basal rates for the whole day, it is not recommended to fast during 24h straight. This is because the body triggers mechanisms such as hormones to compensate. A recommended way is to fast 3 times for 8 hours. +There are basal testing methods which usually entails observing your basal rates and insulin needs during an intermittent fasting over a 24-hour period. Although you need to test your basal rates for the whole day, it is not recommended to fast during 24h straight. This is because the body triggers mechanisms such as hormones to compensate. A recommended way is to fast 3 times for 8 hours. -The recommended method is to suspend the loop, which will revert to your default background basal rate. Observe how your **BG** changes: if it is dropping, basal rate is too high. And vice versa.
An alternative method (may be more tricky) is to keep the loop running, and seeing how **IOB** changes. If **IOB** is negative, your basal rate is too high. And vice versa. Beware that this method relies on **ISF** to correct **BG**, and thus depends on other variables to be set reasonably well for it to be successful.
Another way of adjusting your basal rates is to watch the loop action during the night, when all COB have decayed. This method is particularly useful for children, when fasting is difficult or insulin needs change often. [Dr Saleh Adi from Tidepool](https://www.youtube.com/watch?v=-fpWnGRhLSo) provides useful ways on how to analyse overnight BG lines in order to optimise your basal rates. +The recommended method is to suspend the loop (for safety you can set AAPS to [**LGS**](#Preferences-aps-mode) to avoid lows, as done for achieving [objective 6](#objectives-objective6)), which will revert to your default background basal rate. Observe how your **BG** changes: if it is dropping, basal rate is too high. And vice versa.
An alternative method (may be more tricky) is to keep the loop running, and seeing how **IOB** changes. If **IOB** is negative, your basal rate is too high. And vice versa. Beware that this method relies on **ISF** to correct **BG**, and thus depends on other variables to be set reasonably well for it to be successful.
Another way of adjusting your basal rates is to watch the loop action during the night, when all COB have decayed. This method is particularly useful for children, when fasting is difficult or insulin needs change often. [Dr Saleh Adi from Tidepool](https://www.youtube.com/watch?v=-fpWnGRhLSo) provides useful ways on how to analyze overnight BG lines in order to optimize your basal rates. -When taking action on the result of your basal testing, changes in the **Profile** should be done 1 hour before the rise/drop. Repeat the test as necessary until you are comfortable with your **basal rates** settings. +See [here](../GettingHelp/ProfileTuning.md) how to tweak your basal profile, analyzing patterns in closed loop. + +When taking action on the result of your basal testing, changes in the **Profile** should be done 1 to 2 hours (depends on your insulin type) before the rise/drop. Repeat the test as necessary until you are comfortable with your **basal rates** settings. (your-aaps-profile-insulin-sensitivity-factor)= diff --git a/docs/CROWDIN/sk/SupportingAaps/HowCanIHelp.md b/docs/CROWDIN/sk/SupportingAaps/HowCanIHelp.md index 6aeca540f5b9..7b90cca588fd 100644 --- a/docs/CROWDIN/sk/SupportingAaps/HowCanIHelp.md +++ b/docs/CROWDIN/sk/SupportingAaps/HowCanIHelp.md @@ -15,7 +15,7 @@ Yay! Look at the issues, ask in the discord channel, there is always a lot to do Great, this is a highly appreciated thing and a good way to pay it forward! * The discord channel regarding the wiki can be found here: [AndroidAPS](https://discord.gg/4fQUWHZ4Mw). -* A guide how to do commits on English wiki can be found here: [How to make a PR](../SupportingAaps/HowToEditTheDocs.md). Other languages are only translated from english and can't be edited for consistency reasons. +* A guide how to do commits on English wiki can be found here: [How to make a PR](../SupportingAaps/HowToEditTheDocs.md). Other languages are only translated from English and can't be edited for consistency reasons. ## I do speak multiple languages and want to translate the app or the documentation @@ -23,7 +23,7 @@ If you are translating something for the first time, please start with translati You are welcome to start as a translator for the documentation in parallel or later. -You can check the state of translations for the languages app and documentation [here](StateOfTranslations). +You can check the state of translations for the languages app and documentation [here](#StateOfTranslations). * If you want to translate **the app** to other languages (thank you), please use [crowdin](https://crowdin.com/project/androidaps). * If you want to translate **the docs** to other languages (thank you), please use [crowdin](https://crowdin.com/project/androidapsdocs). diff --git a/docs/CROWDIN/sk/UsefulLinks/FAQ.md b/docs/CROWDIN/sk/UsefulLinks/FAQ.md index 0fa932a88705..0cc83a62f7f7 100644 --- a/docs/CROWDIN/sk/UsefulLinks/FAQ.md +++ b/docs/CROWDIN/sk/UsefulLinks/FAQ.md @@ -247,7 +247,7 @@ Copy on an internet drive (Dropbox, Google etc) : all the apks you used to insta Please -- check [Troubleshooting Android Studio](../GettingHelp/TroubleshootingAndroidStudio) for typical errors and +- check [Troubleshooting Android Studio](../GettingHelp/TroubleshootingAndroidStudio.md) for typical errors and - the tipps for with a [step by step walktrough](https://docs.google.com/document/d/1oc7aG0qrIMvK57unMqPEOoLt-J8UT1mxTKdTAxm8-po). ### I'm stuck on an objective and need help. diff --git a/docs/CROWDIN/sk/images/troubleshooting/profiletuning/FastRise.png b/docs/CROWDIN/sk/images/troubleshooting/profiletuning/FastRise.png new file mode 100644 index 000000000000..ba35b5bb6bf0 Binary files /dev/null and b/docs/CROWDIN/sk/images/troubleshooting/profiletuning/FastRise.png differ diff --git a/docs/CROWDIN/sk/images/troubleshooting/profiletuning/NegativeInsulin.png b/docs/CROWDIN/sk/images/troubleshooting/profiletuning/NegativeInsulin.png new file mode 100644 index 000000000000..7c39c50d00df Binary files /dev/null and b/docs/CROWDIN/sk/images/troubleshooting/profiletuning/NegativeInsulin.png differ diff --git a/docs/CROWDIN/sk/images/troubleshooting/profiletuning/NegativeInsulin2.png b/docs/CROWDIN/sk/images/troubleshooting/profiletuning/NegativeInsulin2.png new file mode 100644 index 000000000000..4bd840d597ad Binary files /dev/null and b/docs/CROWDIN/sk/images/troubleshooting/profiletuning/NegativeInsulin2.png differ diff --git a/docs/CROWDIN/sk/images/troubleshooting/profiletuning/PositiveInsulin.png b/docs/CROWDIN/sk/images/troubleshooting/profiletuning/PositiveInsulin.png new file mode 100644 index 000000000000..e50e806ebf01 Binary files /dev/null and b/docs/CROWDIN/sk/images/troubleshooting/profiletuning/PositiveInsulin.png differ diff --git a/docs/CROWDIN/sk/images/troubleshooting/profiletuning/StrongISF.png b/docs/CROWDIN/sk/images/troubleshooting/profiletuning/StrongISF.png new file mode 100644 index 000000000000..ca16a1ad1b9d Binary files /dev/null and b/docs/CROWDIN/sk/images/troubleshooting/profiletuning/StrongISF.png differ diff --git a/docs/CROWDIN/sk/images/troubleshooting/profiletuning/StuckHigh.png b/docs/CROWDIN/sk/images/troubleshooting/profiletuning/StuckHigh.png new file mode 100644 index 000000000000..1fbeefc01c50 Binary files /dev/null and b/docs/CROWDIN/sk/images/troubleshooting/profiletuning/StuckHigh.png differ diff --git a/docs/CROWDIN/sk/index.md b/docs/CROWDIN/sk/index.md index 2fb75a4a2686..a5a9d8e7d39c 100644 --- a/docs/CROWDIN/sk/index.md +++ b/docs/CROWDIN/sk/index.md @@ -159,6 +159,7 @@ Updating to a new version of AAPS <./Maintenance/UpdateToNewVersion.md> Where can I get help with AAPS <./GettingHelp/WhereCanIGetHelp.md> General troubleshooting <./GettingHelp/GeneralTroubleshooting.md> - Bluetooth troubleshooting <./GettingHelp/BluetoothTroubleshooting.md> +Profile Tuning Guide <./GettingHelp/ProfileTuning.md> Troubleshooting Android Studio <./GettingHelp/TroubleshootingAndroidStudio.md> Accessing logfiles <./GettingHelp/AccessingLogFiles.md> ``` diff --git a/docs/CROWDIN/tr/Getting-Started/Introduction.md b/docs/CROWDIN/tr/Getting-Started/Introduction.md index 165e868409da..7d5813ad81c3 100644 --- a/docs/CROWDIN/tr/Getting-Started/Introduction.md +++ b/docs/CROWDIN/tr/Getting-Started/Introduction.md @@ -192,7 +192,7 @@ If a malicious attack was made on your insulin pump, these strategies would sign #### Safety considerations around improving blood glucose control too fast -A rapid reduction in HbA1c and improved blood glucose control sounds appealing. However, reducing average blood glucose levels _too fast_ by starting any closed loop system can cause permanent damage, including to the eyes, and painful neuropathy that never goes away. This damage can be avoided simply by reducing levels more slowly. If you currently have an elevated HbA1c and are moving to AAPS (or any other closed loop system), please discuss this potential risk with your clinical team before starting, and agree a timeplan with them. More general information on how to reduce your glucose levels safely, including links to medical literature is given in the [safety section [here](#preparing-safety-first). +A rapid reduction in HbA1c and improved blood glucose control sounds appealing. However, reducing average blood glucose levels _too fast_ by starting any closed loop system can cause permanent damage, including to the eyes, and painful neuropathy that never goes away. This damage can be avoided simply by reducing levels more slowly. If you currently have an elevated HbA1c and are moving to AAPS (or any other closed loop system), please discuss this potential risk with your clinical team before starting, and agree a time plan with them. More general information on how to reduce your glucose levels safely, including links to medical literature is given in the safety section [here](#preparing-safety-first). #### Medical safety around devices, consumable supplies and other medications diff --git a/docs/CROWDIN/tr/GettingHelp/ProfileTuning.md b/docs/CROWDIN/tr/GettingHelp/ProfileTuning.md new file mode 100644 index 000000000000..aec6c2439237 --- /dev/null +++ b/docs/CROWDIN/tr/GettingHelp/ProfileTuning.md @@ -0,0 +1,136 @@ +# **Tweaking the AAPS' Profile** + +```{admonition} This is NOT a medical advice +:class: warning +Please work with your care team for support and advice on your diabetes management.
+Use this guide only once you have [set up your **Profile** correctly](https://androidaps.readthedocs.io/en/latest/SettingUpAaps/YourAapsProfile.md), following all **AAPS** objectives. +``` + +This guide explains the logic of the OpenAPS algorithm results with a given __Profile__, and provides information about which values to adjust when certain situations are observed. The suggestions about basal testing below may diverge from what your care team advises + +Using **closed loop** may make basal testing easier and may significantly reduce the hypo risk if your __Profile__ basal is too strong. + +## **Changing profile's settings, how to proceed** + +1. Ensure you have read and understand __AAPS’__ recommended settings and advice below. Not following this advice will make the whole process problematic and less likely to get a well tuned __Profile__ +2. Carefully observe and compare, **over several days**, what is happening with your __BG__ and __IOB__. +3. Keep an eye out for patterns that happen around the same time (almost) everyday. +4. It's important to do this over several days. Poor results tend to be yielded from using data observed on a single day to make __Profile’s__ adjustment decisions. +5. After you have observed a repeatable pattern of behavior, e.g. at 1PM you see a spike in __BG__ or a negative __IOB__ value, only then start to make small changes to your __Profile__. +6. It's important to limit the changes you make to one thing at a time. Ör. increase your basal by 10% around 1PM. +7. After every change, it's important to monitor the impact on your __BG__ and __IOB__ for the next few days. +8. Repeat this pattern, observe, decide, tweak again if needed + +Don't rush, go slow! + +## **Recommended settings and advice while tweaking basal** + +- Do all testing with [closed loop enabled](#AapsScreens-loop-status). +- **Turn OFF all [automations](../DailyLifeWithAAPS/Automations.md)** +- **Turn OFF [DynISF](#Open-APS-features-DynamicISF), [AutoISF](../AdvancedOptions/DevBranch.md), [AutoSens](#Open-APS-features-autosens)** so that they will not try to adapt your profile. +- Do not make manual user actions (manual bolus, temp targets etc…) while testing: let the system use the **Profile** settings only. +- For the [additional graphs](#AapsScreens-section-g-additional-graphs): on graph 1, use Insulin On Board, Carbs On Board (and Sensitivity change). On graph 2, use Deviations and Blood Glucose Impact. When asking for advice, always include those on your screenshots. +- COB=0[*](#profiletuning-cob-zero) +- No physical activities. +- No stress. +- No illness. +- No extreme weather like high or low temperatures. +- If your [basal rate profile](#your-aaps-profile-basal-rates) is correct, when you are on target with COB=0[*](#profiletuning-cob-zero) and IOB=0, you will remain constantly on target whatever your ISF (ISF is only used when you are higher than your target). +- You need to check the actual IOB but also, the IOB chart to see how the IOB was during the past few hours. + +(profiletuning-cob-zero)= + +***COB = 0** + +Meaning that the meal is digested, and there are no more carbs in your body. + +AAPS might indicate [COB=0 while you still have carbs on board](../DailyLifeWithAAPS/CobCalculation.md). + +## **[Profile](../SettingUpAaps/YourAapsProfile.md) definitions** + +A too **strong Profile** indicates some combination of the following: + +- [ISF](#insulin-sensitivity-factor-isf) number is too small +- The [basal](#basal-rates) number is too big +- [I:C](#insulin-to-carb-ratio-icr) number is too small + +## **IOB Observations** + +*Note: you can also use Loopalyzer IOB graph in Nightscout reports to view IOB on several days.* + +If you observe the following patterns after a few days, consider the following changes + +### **IOB positive** + +- **Profile** basal might not be strong enough (this could also be because of things like unannounced food, illness, bad site absorption, etc.) + +![Positive IOB](../images/troubleshooting/profiletuning/PositiveInsulin.png) + +### **IOB negative** + +- Default basal too strong +- May be the effect from past exercise/physical activity + +![Negative IOB](../images/troubleshooting/profiletuning/NegativeInsulin.png) + +- Previous meal: too much bolus (which resulted in a very long zero temp basal) + +![Negative IOB](../images/troubleshooting/profiletuning/NegativeInsulin2.png) + +## **BG Target Observations** + +### **Stuck High** + +- __ISF__ ‘s number is high and not strong enough (calculated insulin is too weak) + +![Stuck High](../images/troubleshooting/profiletuning/StuckHigh.png) + +- __Profile__ basal might not be strong enough (SMBs do not have enough "basal stock" to use) +- A security ([MaxIOB](#Open-APS-features-maximum-total-iob-openaps-cant-go-over)?) might have kicked in and is limiting insulin injection. Verify in the [SMB](#Open-APS-features-super-micro-bolus-smb) tab. +- Technical issue: site absorption, infusion set, ... + +### **Stuck Low** + +- __ISF__ too strong and the number needs to be raised higher +- __Profile__ basal too strong (if also negative IOB) + +### **Rollercoaster (ups and downs)** + +- **ISF** too strong? See your [AAPS Profile](#your-aaps-profile-insulin-sensitivity-factor) + +![Rollercoaster](../images/troubleshooting/profiletuning/StrongISF.png) + +## **BG After Meals Observations** + +### **Fast rise and BG going high** + +- Food contains fast carbs +- Consider doing a pre-bolus +- Bolus (IC or injected %) not strong enough + +![Rise High](../images/troubleshooting/profiletuning/FastRise.png) + +### **Fast rise and then BG going low** + +- Consider doing a pre-bolus, profile might be too aggressive (over correction of the raise) +- Bolus too strong + + + +## **[How to calculate your I:C](#your-aaps-profile-insulin-to-carbs-ratio)** + +1. First, you need the correct default basal settings in your **Profile**. +2. Start on target, better without negative IOB. +3. Record the total insulin given in the pump tab (or pump history) and call it Start insulin C4. Very accurately measure a known portion of carbs, and record the start time and Start IOB. Then enter carbs and bolus information into AAPS using the wizard (with the current configured CI). Don't forget to eat the carbs ;) +4. After some hours, when COB=0[*](#profiletuning-cob-zero) and you're back on target, record end time, and note down the End IOB, check the total insulin given as before and call it End insulin. *NOTE: The time frame is NOT important, as long as it is longer than your digestion* +5. From the difference between Start and End insulin amount, subtract/add the difference end IOB - start IOB. Then subtract the basal insulin calculated from your profile settings. +6. If __BG__ is in target, you'll have the total insulin used to “digest” your carbs. Calculate your **I:C**. + +### **Explanations for the I:C calculations** + +- With a **Profile** that has the correct default basal rate, during any time frame, you should stay on target and have an IOB near 0. You get your **Profile** basal only. +- You add carbs and bolus to this mix. Wait till your body digests all the carbs and be back on **BG** target. Your insulin usage will be the sum of your basal + the insulin needed for the carbs. You calculate the insulin used for your basal (by using your **Profile**) and the surplus will be the insulin used to digest the carbs. +- If the time frame is too short, there will be carbs undigested, thus your "insulin needed for the carbs" will be wrong. +- If the time frame is too long, nothing bad will happen. You'll use all your carbs and you'll get more basal. At the end, you'll subtract the basal from the total insulin used, the extended time frame (with more basal use) will not affect the result. + +Originally written up by @Robby (Discord) on tips and tricks to help tune your AAPS Profile, reviewed and edited by the community (thank you!). diff --git a/docs/CROWDIN/tr/SettingUpAaps/ComputerBuild.md b/docs/CROWDIN/tr/SettingUpAaps/ComputerBuild.md index 37a5c521e22d..a75d4a5b2271 100644 --- a/docs/CROWDIN/tr/SettingUpAaps/ComputerBuild.md +++ b/docs/CROWDIN/tr/SettingUpAaps/ComputerBuild.md @@ -70,7 +70,7 @@ The Gradle version is linked to the source code, you will always get the correct ## Help and support during the building process -If you run into difficulties in the process of building the **AAPS** app, there is a dedicated [**troubleshooting Android Studio**](../GettingHelp/TroubleshootingAndroidStudio) section, please consult that first. +If you run into difficulties in the process of building the **AAPS** app, there is a dedicated [**troubleshooting Android Studio**](../GettingHelp/TroubleshootingAndroidStudio.md) section, please consult that first. If you think something in the building instructions is wrong, missing or confusing, or you are still struggling, please reach out to other **AAPS** users group on [Facebook](https://www.facebook.com/groups/AndroidAPSUsers) or [Discord](https://discord.gg/4fQUWHZ4Mw). If you want to change something yourself (updating screenshots _etc_), please submit a [pull request (PR)](../SupportingAaps/HowToEditTheDocs.md). @@ -409,7 +409,7 @@ Android Studio will display the information "BUILD SUCCESSFUL" after build is fi ![Build finished](../images/Building-the-App/049_ReopenNotification.png) -**_If the build was not successful, refer to the [Android Studio Troubleshooting section](../GettingHelp/TroubleshootingAndroidStudio)._** +**_If the build was not successful, refer to the [Android Studio Troubleshooting section](../GettingHelp/TroubleshootingAndroidStudio.md)._** In the Notifications box, click on the blue link "locate": diff --git a/docs/CROWDIN/tr/SettingUpAaps/Preferences.md b/docs/CROWDIN/tr/SettingUpAaps/Preferences.md index aaff81ff0b4a..d38577d9dc04 100644 --- a/docs/CROWDIN/tr/SettingUpAaps/Preferences.md +++ b/docs/CROWDIN/tr/SettingUpAaps/Preferences.md @@ -300,7 +300,7 @@ Switch between Open Loop, Closed Loop and Low Glucose Suspend (LGS). ![Config builder - loop mode](../images/ConfigBuilder_LoopLGS.png) -(Preferences-pen-loop)= +(Preferences-open-loop)= #### Open Loop **AAPS** continuously evaluates all available data (IOB, COB, BG...) and makes treatment suggestions (temporary basal rates) on how to adjust your therapy if necessary. diff --git a/docs/CROWDIN/tr/SettingUpAaps/YourAapsProfile.md b/docs/CROWDIN/tr/SettingUpAaps/YourAapsProfile.md index c24a7df1f5e6..56abb4c9f579 100644 --- a/docs/CROWDIN/tr/SettingUpAaps/YourAapsProfile.md +++ b/docs/CROWDIN/tr/SettingUpAaps/YourAapsProfile.md @@ -123,11 +123,13 @@ The **figure below** shows an example of how the basal rates can be set in an ** Setting your basal rates right is done by trial and error, and should be done in consultation with your diabetic team. -There are basal testing methods which usually entails observing your basal rates and insulin needs during an intermittent fasting over a 24-hour period. Although you need to test your basal rates for the whole day, it is not recommended to fast during 24h straight. This is because the body triggers mechanisms such as hormones to compensate. A recommended way is to fast 3 times for 8 hours. +There are basal testing methods which usually entails observing your basal rates and insulin needs during an intermittent fasting over a 24-hour period. Although you need to test your basal rates for the whole day, it is not recommended to fast during 24h straight. This is because the body triggers mechanisms such as hormones to compensate. A recommended way is to fast 3 times for 8 hours. -The recommended method is to suspend the loop, which will revert to your default background basal rate. Observe how your **BG** changes: if it is dropping, basal rate is too high. And vice versa.
An alternative method (may be more tricky) is to keep the loop running, and seeing how **IOB** changes. If **IOB** is negative, your basal rate is too high. And vice versa. Beware that this method relies on **ISF** to correct **BG**, and thus depends on other variables to be set reasonably well for it to be successful.
Another way of adjusting your basal rates is to watch the loop action during the night, when all COB have decayed. This method is particularly useful for children, when fasting is difficult or insulin needs change often. [Dr Saleh Adi from Tidepool](https://www.youtube.com/watch?v=-fpWnGRhLSo) provides useful ways on how to analyse overnight BG lines in order to optimise your basal rates. +The recommended method is to suspend the loop (for safety you can set AAPS to [**LGS**](#Preferences-aps-mode) to avoid lows, as done for achieving [objective 6](#objectives-objective6)), which will revert to your default background basal rate. Observe how your **BG** changes: if it is dropping, basal rate is too high. And vice versa.
An alternative method (may be more tricky) is to keep the loop running, and seeing how **IOB** changes. If **IOB** is negative, your basal rate is too high. And vice versa. Beware that this method relies on **ISF** to correct **BG**, and thus depends on other variables to be set reasonably well for it to be successful.
Another way of adjusting your basal rates is to watch the loop action during the night, when all COB have decayed. This method is particularly useful for children, when fasting is difficult or insulin needs change often. [Dr Saleh Adi from Tidepool](https://www.youtube.com/watch?v=-fpWnGRhLSo) provides useful ways on how to analyze overnight BG lines in order to optimize your basal rates. -When taking action on the result of your basal testing, changes in the **Profile** should be done 1 hour before the rise/drop. Repeat the test as necessary until you are comfortable with your **basal rates** settings. +See [here](../GettingHelp/ProfileTuning.md) how to tweak your basal profile, analyzing patterns in closed loop. + +When taking action on the result of your basal testing, changes in the **Profile** should be done 1 to 2 hours (depends on your insulin type) before the rise/drop. Repeat the test as necessary until you are comfortable with your **basal rates** settings. (your-aaps-profile-insulin-sensitivity-factor)= diff --git a/docs/CROWDIN/tr/SupportingAaps/HowCanIHelp.md b/docs/CROWDIN/tr/SupportingAaps/HowCanIHelp.md index c7cbe88d9533..1a5c1ee046c9 100644 --- a/docs/CROWDIN/tr/SupportingAaps/HowCanIHelp.md +++ b/docs/CROWDIN/tr/SupportingAaps/HowCanIHelp.md @@ -15,7 +15,7 @@ Hey! Konulara bak, discord kanalında sor, her zaman yapılacak çok iş var! İ Harika, bu çok takdir edilen bir şey ve ona katkıda bulunmanın iyi bir yolu! * Wiki ile ilgili discord kanalını burada bulabilirsiniz: [AndroidAPS](https://discord.gg/4fQUWHZ4Mw). -* A guide how to do commits on English wiki can be found here: [How to make a PR](../SupportingAaps/HowToEditTheDocs.md). Diğer diller yalnızca İngilizce'den çevrilmiştir ve tutarlılık nedeniyle düzenlenemez. +* A guide how to do commits on English wiki can be found here: [How to make a PR](../SupportingAaps/HowToEditTheDocs.md). Other languages are only translated from English and can't be edited for consistency reasons. ## Birden çok dil konuşuyorum ve uygulamayı veya belgeleri çevirmek istiyorum @@ -23,7 +23,7 @@ Bir şeyi ilk kez çeviriyorsanız, lütfen uygulamayı çevirerek başlayın, Paralelinde veya daha sonra dokümantasyon çevirisine başlayabilirsiniz. -You can check the state of translations for the languages app and documentation [here](StateOfTranslations). +You can check the state of translations for the languages app and documentation [here](#StateOfTranslations). * **Uygulamayı** başka dillere çevirmek istiyorsanız (teşekkür ederim), lütfen [crowdin](https://crowdin.com/project/androidaps) kullanın. * **Dokümantasyonu** başka dillere çevirmek istiyorsanız (teşekkürler), lütfen [crowdin](https://crowdin.com/project/androidapsdocs) kullanın. diff --git a/docs/CROWDIN/tr/UsefulLinks/FAQ.md b/docs/CROWDIN/tr/UsefulLinks/FAQ.md index bcd93b09357d..0b246703dada 100644 --- a/docs/CROWDIN/tr/UsefulLinks/FAQ.md +++ b/docs/CROWDIN/tr/UsefulLinks/FAQ.md @@ -247,7 +247,7 @@ Bir internet sürücüsüne kopyalayın (Dropbox, Google vb.): Telefonunuza uygu Lütfen -- check [Troubleshooting Android Studio](../GettingHelp/TroubleshootingAndroidStudio) for typical errors and +- check [Troubleshooting Android Studio](../GettingHelp/TroubleshootingAndroidStudio.md) for typical errors and - [adım adım izlenecek yol](https://docs.google.com/document/d/1oc7aG0qrIMvK57unMqPEOoLt-J8UT1mxTKdTAxm8-po) ile ilgili ipuçları. ### I'm stuck on an objective and need help. diff --git a/docs/CROWDIN/tr/images/troubleshooting/profiletuning/FastRise.png b/docs/CROWDIN/tr/images/troubleshooting/profiletuning/FastRise.png new file mode 100644 index 000000000000..ba35b5bb6bf0 Binary files /dev/null and b/docs/CROWDIN/tr/images/troubleshooting/profiletuning/FastRise.png differ diff --git a/docs/CROWDIN/tr/images/troubleshooting/profiletuning/NegativeInsulin.png b/docs/CROWDIN/tr/images/troubleshooting/profiletuning/NegativeInsulin.png new file mode 100644 index 000000000000..7c39c50d00df Binary files /dev/null and b/docs/CROWDIN/tr/images/troubleshooting/profiletuning/NegativeInsulin.png differ diff --git a/docs/CROWDIN/tr/images/troubleshooting/profiletuning/NegativeInsulin2.png b/docs/CROWDIN/tr/images/troubleshooting/profiletuning/NegativeInsulin2.png new file mode 100644 index 000000000000..4bd840d597ad Binary files /dev/null and b/docs/CROWDIN/tr/images/troubleshooting/profiletuning/NegativeInsulin2.png differ diff --git a/docs/CROWDIN/tr/images/troubleshooting/profiletuning/PositiveInsulin.png b/docs/CROWDIN/tr/images/troubleshooting/profiletuning/PositiveInsulin.png new file mode 100644 index 000000000000..e50e806ebf01 Binary files /dev/null and b/docs/CROWDIN/tr/images/troubleshooting/profiletuning/PositiveInsulin.png differ diff --git a/docs/CROWDIN/tr/images/troubleshooting/profiletuning/StrongISF.png b/docs/CROWDIN/tr/images/troubleshooting/profiletuning/StrongISF.png new file mode 100644 index 000000000000..ca16a1ad1b9d Binary files /dev/null and b/docs/CROWDIN/tr/images/troubleshooting/profiletuning/StrongISF.png differ diff --git a/docs/CROWDIN/tr/images/troubleshooting/profiletuning/StuckHigh.png b/docs/CROWDIN/tr/images/troubleshooting/profiletuning/StuckHigh.png new file mode 100644 index 000000000000..1fbeefc01c50 Binary files /dev/null and b/docs/CROWDIN/tr/images/troubleshooting/profiletuning/StuckHigh.png differ diff --git a/docs/CROWDIN/tr/index.md b/docs/CROWDIN/tr/index.md index e5607a931d3c..8ae4d30690be 100644 --- a/docs/CROWDIN/tr/index.md +++ b/docs/CROWDIN/tr/index.md @@ -159,6 +159,7 @@ Updating to a new version of AAPS <./Maintenance/UpdateToNewVersion.md> Where can I get help with AAPS <./GettingHelp/WhereCanIGetHelp.md> General troubleshooting <./GettingHelp/GeneralTroubleshooting.md> - Bluetooth troubleshooting <./GettingHelp/BluetoothTroubleshooting.md> +Profile Tuning Guide <./GettingHelp/ProfileTuning.md> Troubleshooting Android Studio <./GettingHelp/TroubleshootingAndroidStudio.md> Accessing logfiles <./GettingHelp/AccessingLogFiles.md> ``` diff --git a/docs/CROWDIN/zh_CN/Getting-Started/Introduction.md b/docs/CROWDIN/zh_CN/Getting-Started/Introduction.md index d4bd467d5d77..7279fddd9236 100644 --- a/docs/CROWDIN/zh_CN/Getting-Started/Introduction.md +++ b/docs/CROWDIN/zh_CN/Getting-Started/Introduction.md @@ -192,7 +192,7 @@ _表格说明：_ #### 关于过快改善血糖控制的安全注意事项 -快速降低 HbA1c 和改善血糖控制听起来很有吸引力。 但是，不管用哪种闭环系统，_过快_降低平均血糖水平都可能造成永久性损伤，包括对眼睛的损伤，以及永远无法消除的疼痛性神经病变。 这种损害可以通过缓慢降低血糖水平来避免。 如果您目前的 HbA1c 偏高，并准备改用 AAPS（或任何其他闭环系统），请在开始之前与您的临床团队讨论这一潜在风险，并与他们商定一个时间计划。 有关如何安全降低血糖水平的更多一般信息，包括医学文献链接，请参阅[此处](#preparing-safety-first)的安全部分。 +快速降低 HbA1c 和改善血糖控制听起来很有吸引力。 但是，不管用哪种闭环系统，_过快_降低平均血糖水平都可能造成永久性损伤，包括对眼睛的损伤，以及永远无法消除的疼痛性神经病变。 这种损害可以通过缓慢降低血糖水平来避免。 If you currently have an elevated HbA1c and are moving to AAPS (or any other closed loop system), please discuss this potential risk with your clinical team before starting, and agree a time plan with them. More general information on how to reduce your glucose levels safely, including links to medical literature is given in the safety section [here](#preparing-safety-first). #### 关于设备、耗材和其他药物的医疗安全 diff --git a/docs/CROWDIN/zh_CN/GettingHelp/ProfileTuning.md b/docs/CROWDIN/zh_CN/GettingHelp/ProfileTuning.md new file mode 100644 index 000000000000..8b95d095d10d --- /dev/null +++ b/docs/CROWDIN/zh_CN/GettingHelp/ProfileTuning.md @@ -0,0 +1,136 @@ +# **Tweaking the AAPS' Profile** + +```{admonition} This is NOT a medical advice +:class: warning +Please work with your care team for support and advice on your diabetes management.
+Use this guide only once you have [set up your **Profile** correctly](https://androidaps.readthedocs.io/en/latest/SettingUpAaps/YourAapsProfile.md), following all **AAPS** objectives. +``` + +This guide explains the logic of the OpenAPS algorithm results with a given __Profile__, and provides information about which values to adjust when certain situations are observed. The suggestions about basal testing below may diverge from what your care team advises + +Using **closed loop** may make basal testing easier and may significantly reduce the hypo risk if your __Profile__ basal is too strong. + +## **Changing profile's settings, how to proceed** + +1. Ensure you have read and understand __AAPS’__ recommended settings and advice below. Not following this advice will make the whole process problematic and less likely to get a well tuned __Profile__ +2. Carefully observe and compare, **over several days**, what is happening with your __BG__ and __IOB__. +3. Keep an eye out for patterns that happen around the same time (almost) everyday. +4. It's important to do this over several days. Poor results tend to be yielded from using data observed on a single day to make __Profile’s__ adjustment decisions. +5. After you have observed a repeatable pattern of behavior, e.g. at 1PM you see a spike in __BG__ or a negative __IOB__ value, only then start to make small changes to your __Profile__. +6. It's important to limit the changes you make to one thing at a time. 例如 increase your basal by 10% around 1PM. +7. After every change, it's important to monitor the impact on your __BG__ and __IOB__ for the next few days. +8. Repeat this pattern, observe, decide, tweak again if needed + +Don't rush, go slow! + +## **Recommended settings and advice while tweaking basal** + +- Do all testing with [closed loop enabled](#AapsScreens-loop-status). +- **Turn OFF all [automations](../DailyLifeWithAAPS/Automations.md)** +- **Turn OFF [DynISF](#Open-APS-features-DynamicISF), [AutoISF](../AdvancedOptions/DevBranch.md), [AutoSens](#Open-APS-features-autosens)** so that they will not try to adapt your profile. +- Do not make manual user actions (manual bolus, temp targets etc…) while testing: let the system use the **Profile** settings only. +- For the [additional graphs](#AapsScreens-section-g-additional-graphs): on graph 1, use Insulin On Board, Carbs On Board (and Sensitivity change). On graph 2, use Deviations and Blood Glucose Impact. When asking for advice, always include those on your screenshots. +- COB=0[*](#profiletuning-cob-zero) +- No physical activities. +- No stress. +- No illness. +- No extreme weather like high or low temperatures. +- If your [basal rate profile](#your-aaps-profile-basal-rates) is correct, when you are on target with COB=0[*](#profiletuning-cob-zero) and IOB=0, you will remain constantly on target whatever your ISF (ISF is only used when you are higher than your target). +- You need to check the actual IOB but also, the IOB chart to see how the IOB was during the past few hours. + +(profiletuning-cob-zero)= + +***COB = 0** + +Meaning that the meal is digested, and there are no more carbs in your body. + +AAPS might indicate [COB=0 while you still have carbs on board](../DailyLifeWithAAPS/CobCalculation.md). + +## **[Profile](../SettingUpAaps/YourAapsProfile.md) definitions** + +A too **strong Profile** indicates some combination of the following: + +- [ISF](#insulin-sensitivity-factor-isf) number is too small +- The [basal](#basal-rates) number is too big +- [I:C](#insulin-to-carb-ratio-icr) number is too small + +## **IOB Observations** + +*Note: you can also use Loopalyzer IOB graph in Nightscout reports to view IOB on several days.* + +If you observe the following patterns after a few days, consider the following changes + +### **IOB positive** + +- **Profile** basal might not be strong enough (this could also be because of things like unannounced food, illness, bad site absorption, etc.) + +![Positive IOB](../images/troubleshooting/profiletuning/PositiveInsulin.png) + +### **IOB negative** + +- Default basal too strong +- May be the effect from past exercise/physical activity + +![Negative IOB](../images/troubleshooting/profiletuning/NegativeInsulin.png) + +- Previous meal: too much bolus (which resulted in a very long zero temp basal) + +![Negative IOB](../images/troubleshooting/profiletuning/NegativeInsulin2.png) + +## **BG Target Observations** + +### **Stuck High** + +- __ISF__ ‘s number is high and not strong enough (calculated insulin is too weak) + +![Stuck High](../images/troubleshooting/profiletuning/StuckHigh.png) + +- __Profile__ basal might not be strong enough (SMBs do not have enough "basal stock" to use) +- A security ([MaxIOB](#Open-APS-features-maximum-total-iob-openaps-cant-go-over)?) might have kicked in and is limiting insulin injection. Verify in the [SMB](#Open-APS-features-super-micro-bolus-smb) tab. +- Technical issue: site absorption, infusion set, ... + +### **Stuck Low** + +- __ISF__ too strong and the number needs to be raised higher +- __Profile__ basal too strong (if also negative IOB) + +### **Rollercoaster (ups and downs)** + +- **ISF** too strong? See your [AAPS Profile](#your-aaps-profile-insulin-sensitivity-factor) + +![Rollercoaster](../images/troubleshooting/profiletuning/StrongISF.png) + +## **BG After Meals Observations** + +### **Fast rise and BG going high** + +- Food contains fast carbs +- Consider doing a pre-bolus +- Bolus (IC or injected %) not strong enough + +![Rise High](../images/troubleshooting/profiletuning/FastRise.png) + +### **Fast rise and then BG going low** + +- Consider doing a pre-bolus, profile might be too aggressive (over correction of the raise) +- Bolus too strong + + + +## **[How to calculate your I:C](#your-aaps-profile-insulin-to-carbs-ratio)** + +1. First, you need the correct default basal settings in your **Profile**. +2. Start on target, better without negative IOB. +3. Record the total insulin given in the pump tab (or pump history) and call it Start insulin C4. Very accurately measure a known portion of carbs, and record the start time and Start IOB. Then enter carbs and bolus information into AAPS using the wizard (with the current configured CI). Don't forget to eat the carbs ;) +4. After some hours, when COB=0[*](#profiletuning-cob-zero) and you're back on target, record end time, and note down the End IOB, check the total insulin given as before and call it End insulin. *NOTE: The time frame is NOT important, as long as it is longer than your digestion* +5. From the difference between Start and End insulin amount, subtract/add the difference end IOB - start IOB. Then subtract the basal insulin calculated from your profile settings. +6. If __BG__ is in target, you'll have the total insulin used to “digest” your carbs. Calculate your **I:C**. + +### **Explanations for the I:C calculations** + +- With a **Profile** that has the correct default basal rate, during any time frame, you should stay on target and have an IOB near 0. You get your **Profile** basal only. +- You add carbs and bolus to this mix. Wait till your body digests all the carbs and be back on **BG** target. Your insulin usage will be the sum of your basal + the insulin needed for the carbs. You calculate the insulin used for your basal (by using your **Profile**) and the surplus will be the insulin used to digest the carbs. +- If the time frame is too short, there will be carbs undigested, thus your "insulin needed for the carbs" will be wrong. +- If the time frame is too long, nothing bad will happen. You'll use all your carbs and you'll get more basal. At the end, you'll subtract the basal from the total insulin used, the extended time frame (with more basal use) will not affect the result. + +Originally written up by @Robby (Discord) on tips and tricks to help tune your AAPS Profile, reviewed and edited by the community (thank you!). diff --git a/docs/CROWDIN/zh_CN/SettingUpAaps/ComputerBuild.md b/docs/CROWDIN/zh_CN/SettingUpAaps/ComputerBuild.md index 247925c66c00..bebc9c92e149 100644 --- a/docs/CROWDIN/zh_CN/SettingUpAaps/ComputerBuild.md +++ b/docs/CROWDIN/zh_CN/SettingUpAaps/ComputerBuild.md @@ -70,7 +70,7 @@ Gradle版本由源代码仓库锁定，在拉取/更新代码时将自动获取 ## 构建过程中的帮助和支持 -如果在构建**AAPS**应用的过程中遇到困难，有一个专门的[**Android Studio故障排除**](../GettingHelp/TroubleshootingAndroidStudio)部分，请先参考该部分。 +If you run into difficulties in the process of building the **AAPS** app, there is a dedicated [**troubleshooting Android Studio**](../GettingHelp/TroubleshootingAndroidStudio.md) section, please consult that first. 如果你认为构建说明中有错误、遗漏或令人困惑的地方，或者你仍然在努力解决问题，请联系[Facebook](https://www.facebook.com/groups/AndroidAPSUsers)或[Discord](https://discord.gg/4fQUWHZ4Mw)上的其他**AAPS**用户组。 如果你想自己更改某些内容（如更新截图_等_），请提交一个[拉取请求（PR）](../SupportingAaps/HowToEditTheDocs.md)。 @@ -406,7 +406,7 @@ Android Studio现在将构建AAPS apk。 在右下角会显示“Gradle 构建 ![Build finished](../images/Building-the-App/049_ReopenNotification.png) -**_如果构建不成功，请参阅[Android Studio故障排除部分](../GettingHelp/TroubleshootingAndroidStudio)。_** +**_If the build was not successful, refer to the [Android Studio Troubleshooting section](../GettingHelp/TroubleshootingAndroidStudio.md)._** 在通知框中，点击蓝色链接“定位”： diff --git a/docs/CROWDIN/zh_CN/SettingUpAaps/Preferences.md b/docs/CROWDIN/zh_CN/SettingUpAaps/Preferences.md index ba7108ba5249..7f368dbce458 100644 --- a/docs/CROWDIN/zh_CN/SettingUpAaps/Preferences.md +++ b/docs/CROWDIN/zh_CN/SettingUpAaps/Preferences.md @@ -300,7 +300,7 @@ ![配置构建器 - 循环模式](../images/ConfigBuilder_LoopLGS.png) -(Preferences-pen-loop)= +(Preferences-open-loop)= #### 开环 **AAPS**连续评估所有可用数据（IOB、COB、BG...），如有必要，会就如何调整治疗（如临时基础率）提出建议。 diff --git a/docs/CROWDIN/zh_CN/SettingUpAaps/YourAapsProfile.md b/docs/CROWDIN/zh_CN/SettingUpAaps/YourAapsProfile.md index 1eb56ed1a263..97139a9a10e5 100644 --- a/docs/CROWDIN/zh_CN/SettingUpAaps/YourAapsProfile.md +++ b/docs/CROWDIN/zh_CN/SettingUpAaps/YourAapsProfile.md @@ -123,11 +123,13 @@ AAPS以默认基础率为“基线”。 如果基础率设置得太高，那么 正确设置基础率需要通过反复试验来确定，并且应该与您的糖尿病治疗团队协商进行。 -有一些基础率测试方法，通常需要在24小时内的间歇性禁食期间观察您的基础率和胰岛素需求。 虽然你需要测试一整天的基础率，但不建议连续24小时禁食。 这是因为身体会触发激素等机制进行补偿。 一个推荐的方法是在一天中进行三次8小时的禁食。 +There are basal testing methods which usually entails observing your basal rates and insulin needs during an intermittent fasting over a 24-hour period. 虽然你需要测试一整天的基础率，但不建议连续24小时禁食。 这是因为身体会触发激素等机制进行补偿。 一个推荐的方法是在一天中进行三次8小时的禁食。 -推荐的方法是暂停循环，这将恢复到你的默认基础率。 观察你的**BG**如何变化：如果它在下降，基础率就过高。 反之亦然。
另一种方法（可能更棘手）是让闭环系统持续运行，并观察**活性胰岛素（IOB）**的变化情况。 如果IOB为负，你的基础率就过高。 反之亦然。 请注意，这种方法依赖于**ISF**来纠正**BG**，因此取决于其他变量设置得是否合理才能成功。
另一种调整基础率的方法是观察夜间循环操作，当所有碳水化合物都已消耗时。 这种方法对儿童特别有用，当禁食困难或胰岛素需求经常变化时。 [Tidepool的Dr Saleh Adi](https://www.youtube.com/watch?v=-fpWnGRhLSo)提供了有用的方法来分析夜间BG曲线，以优化你的基础率。 +The recommended method is to suspend the loop (for safety you can set AAPS to [**LGS**](#Preferences-aps-mode) to avoid lows, as done for achieving [objective 6](#objectives-objective6)), which will revert to your default background basal rate. 观察你的**BG**如何变化：如果它在下降，基础率就过高。 反之亦然。
另一种方法（可能更棘手）是让闭环系统持续运行，并观察**活性胰岛素（IOB）**的变化情况。 如果IOB为负，你的基础率就过高。 反之亦然。 请注意，这种方法依赖于**ISF**来纠正**BG**，因此取决于其他变量设置得是否合理才能成功。
另一种调整基础率的方法是观察夜间循环操作，当所有碳水化合物都已消耗时。 这种方法对儿童特别有用，当禁食困难或胰岛素需求经常变化时。 [Dr Saleh Adi from Tidepool](https://www.youtube.com/watch?v=-fpWnGRhLSo) provides useful ways on how to analyze overnight BG lines in order to optimize your basal rates. -根据基础测试的结果更改配置文件时，应更改上升/下降情况的前1小时的设置。 根据需要重复测试，直到你对基础率设置感到满意。 +See [here](../GettingHelp/ProfileTuning.md) how to tweak your basal profile, analyzing patterns in closed loop. + +When taking action on the result of your basal testing, changes in the **Profile** should be done 1 to 2 hours (depends on your insulin type) before the rise/drop. 根据需要重复测试，直到你对基础率设置感到满意。 (your-aaps-profile-insulin-sensitivity-factor)= diff --git a/docs/CROWDIN/zh_CN/SupportingAaps/HowCanIHelp.md b/docs/CROWDIN/zh_CN/SupportingAaps/HowCanIHelp.md index 79df45afe995..849477249e28 100644 --- a/docs/CROWDIN/zh_CN/SupportingAaps/HowCanIHelp.md +++ b/docs/CROWDIN/zh_CN/SupportingAaps/HowCanIHelp.md @@ -15,7 +15,7 @@ 太棒了！文档贡献是极受社区推崇的回馈方式，您的付出将推动项目持续发展！​ * 有关Wiki的Discord频道请访问：[AndroidAPS](https://discord.gg/4fQUWHZ4Mw)​ -* 英文Wiki的提交操作指南详见：[如何创建PR](../SupportingAaps/HowToEditTheDocs.md)​ 其他语言版本仅从英文原文翻译而来，出于一致性考虑禁止直接编辑。​ +* 英文Wiki的提交操作指南详见：[如何创建PR](../SupportingAaps/HowToEditTheDocs.md)​ Other languages are only translated from English and can't be edited for consistency reasons. ## 我掌握多门语言，愿参与应用程序或文档的翻译工作。​ @@ -23,7 +23,7 @@ 您也可以同时或后续参与文档翻译工作，我们非常欢迎！​ -您可在此查看应用程序及文档的各语言翻译进度：[链接](StateOfTranslations)​ +You can check the state of translations for the languages app and documentation [here](#StateOfTranslations). * 如需将**应用程序**翻译为其他语言（感谢您的贡献），请使用[Crowdin](https://crowdin.com/project/androidaps)平台。​ * 如需将**文档**翻译为其他语言（感谢您的贡献），请使用[Crowdin](https://crowdin.com/project/androidapsdocs)平台。​ diff --git a/docs/CROWDIN/zh_CN/UsefulLinks/FAQ.md b/docs/CROWDIN/zh_CN/UsefulLinks/FAQ.md index 6e0c10fe4765..535c40426f53 100644 --- a/docs/CROWDIN/zh_CN/UsefulLinks/FAQ.md +++ b/docs/CROWDIN/zh_CN/UsefulLinks/FAQ.md @@ -247,7 +247,7 @@ AAPS用于控制您的泵并输注胰岛素。 根据欧洲现行的规定，所 请 -- 请查看[Android Studio故障排除](../GettingHelp/TroubleshootingAndroidStudio)以了解典型错误及其解决方案。 +- check [Troubleshooting Android Studio](../GettingHelp/TroubleshootingAndroidStudio.md) for typical errors and - 以及[逐步操作指南](https://docs.google.com/document/d/1oc7aG0qrIMvK57unMqPEOoLt-J8UT1mxTKdTAxm8-po)中的提示。 ### 我被卡在一个目标上，需要帮助。 diff --git a/docs/CROWDIN/zh_CN/images/troubleshooting/profiletuning/FastRise.png b/docs/CROWDIN/zh_CN/images/troubleshooting/profiletuning/FastRise.png new file mode 100644 index 000000000000..ba35b5bb6bf0 Binary files /dev/null and b/docs/CROWDIN/zh_CN/images/troubleshooting/profiletuning/FastRise.png differ diff --git a/docs/CROWDIN/zh_CN/images/troubleshooting/profiletuning/NegativeInsulin.png b/docs/CROWDIN/zh_CN/images/troubleshooting/profiletuning/NegativeInsulin.png new file mode 100644 index 000000000000..7c39c50d00df Binary files /dev/null and b/docs/CROWDIN/zh_CN/images/troubleshooting/profiletuning/NegativeInsulin.png differ diff --git a/docs/CROWDIN/zh_CN/images/troubleshooting/profiletuning/NegativeInsulin2.png b/docs/CROWDIN/zh_CN/images/troubleshooting/profiletuning/NegativeInsulin2.png new file mode 100644 index 000000000000..4bd840d597ad Binary files /dev/null and b/docs/CROWDIN/zh_CN/images/troubleshooting/profiletuning/NegativeInsulin2.png differ diff --git a/docs/CROWDIN/zh_CN/images/troubleshooting/profiletuning/PositiveInsulin.png b/docs/CROWDIN/zh_CN/images/troubleshooting/profiletuning/PositiveInsulin.png new file mode 100644 index 000000000000..e50e806ebf01 Binary files /dev/null and b/docs/CROWDIN/zh_CN/images/troubleshooting/profiletuning/PositiveInsulin.png differ diff --git a/docs/CROWDIN/zh_CN/images/troubleshooting/profiletuning/StrongISF.png b/docs/CROWDIN/zh_CN/images/troubleshooting/profiletuning/StrongISF.png new file mode 100644 index 000000000000..ca16a1ad1b9d Binary files /dev/null and b/docs/CROWDIN/zh_CN/images/troubleshooting/profiletuning/StrongISF.png differ diff --git a/docs/CROWDIN/zh_CN/images/troubleshooting/profiletuning/StuckHigh.png b/docs/CROWDIN/zh_CN/images/troubleshooting/profiletuning/StuckHigh.png new file mode 100644 index 000000000000..1fbeefc01c50 Binary files /dev/null and b/docs/CROWDIN/zh_CN/images/troubleshooting/profiletuning/StuckHigh.png differ diff --git a/docs/CROWDIN/zh_CN/index.md b/docs/CROWDIN/zh_CN/index.md index e62a88db5db2..64c79474105a 100644 --- a/docs/CROWDIN/zh_CN/index.md +++ b/docs/CROWDIN/zh_CN/index.md @@ -158,6 +158,7 @@ Updating to a new version of AAPS <./Maintenance/UpdateToNewVersion.md> Where can I get help with AAPS <./GettingHelp/WhereCanIGetHelp.md> General troubleshooting <./GettingHelp/GeneralTroubleshooting.md> - Bluetooth troubleshooting <./GettingHelp/BluetoothTroubleshooting.md> +Profile Tuning Guide <./GettingHelp/ProfileTuning.md> Troubleshooting Android Studio <./GettingHelp/TroubleshootingAndroidStudio.md> Accessing logfiles <./GettingHelp/AccessingLogFiles.md> ``` diff --git a/docs/CROWDIN/zh_TW/Getting-Started/Introduction.md b/docs/CROWDIN/zh_TW/Getting-Started/Introduction.md index f8887631ea15..b8df8c3d2928 100644 --- a/docs/CROWDIN/zh_TW/Getting-Started/Introduction.md +++ b/docs/CROWDIN/zh_TW/Getting-Started/Introduction.md @@ -192,7 +192,7 @@ _表格說明：_ #### 關於過快改善血糖控制的安全考量 -迅速降低HbA1c並改善血糖控制聽起來很吸引人。 然而，透過開始任何閉環系統過快降低平均血糖數值可能會導致永久損害，包括眼睛損傷，以及不可逆的疼痛性神經病變。 只要緩慢降低血糖數值，就可以避免這些損害。 如果你目前的HbA1c偏高，並且正在轉向使用AAPS（或其他閉環系統），請在開始之前與你的臨床團隊討論這個潛在風險，並與他們協商一個時間表。 關於如何安全降低血糖數值的更多資訊，包括與醫學文獻的連結，可以在安全部分[這裡](#preparing-safety-first)中找到。 +迅速降低HbA1c並改善血糖控制聽起來很吸引人。 然而，透過開始任何閉環系統過快降低平均血糖數值可能會導致永久損害，包括眼睛損傷，以及不可逆的疼痛性神經病變。 只要緩慢降低血糖數值，就可以避免這些損害。 If you currently have an elevated HbA1c and are moving to AAPS (or any other closed loop system), please discuss this potential risk with your clinical team before starting, and agree a time plan with them. More general information on how to reduce your glucose levels safely, including links to medical literature is given in the safety section [here](#preparing-safety-first). #### 關於設備、耗材和其他藥物的醫療安全 diff --git a/docs/CROWDIN/zh_TW/GettingHelp/ProfileTuning.md b/docs/CROWDIN/zh_TW/GettingHelp/ProfileTuning.md new file mode 100644 index 000000000000..56908f82f380 --- /dev/null +++ b/docs/CROWDIN/zh_TW/GettingHelp/ProfileTuning.md @@ -0,0 +1,136 @@ +# **Tweaking the AAPS' Profile** + +```{admonition} This is NOT a medical advice +:class: warning +Please work with your care team for support and advice on your diabetes management.
+Use this guide only once you have [set up your **Profile** correctly](https://androidaps.readthedocs.io/en/latest/SettingUpAaps/YourAapsProfile.md), following all **AAPS** objectives. +``` + +This guide explains the logic of the OpenAPS algorithm results with a given __Profile__, and provides information about which values to adjust when certain situations are observed. The suggestions about basal testing below may diverge from what your care team advises + +Using **closed loop** may make basal testing easier and may significantly reduce the hypo risk if your __Profile__ basal is too strong. + +## **Changing profile's settings, how to proceed** + +1. Ensure you have read and understand __AAPS’__ recommended settings and advice below. Not following this advice will make the whole process problematic and less likely to get a well tuned __Profile__ +2. Carefully observe and compare, **over several days**, what is happening with your __BG__ and __IOB__. +3. Keep an eye out for patterns that happen around the same time (almost) everyday. +4. It's important to do this over several days. Poor results tend to be yielded from using data observed on a single day to make __Profile’s__ adjustment decisions. +5. After you have observed a repeatable pattern of behavior, e.g. at 1PM you see a spike in __BG__ or a negative __IOB__ value, only then start to make small changes to your __Profile__. +6. It's important to limit the changes you make to one thing at a time. 例如： increase your basal by 10% around 1PM. +7. After every change, it's important to monitor the impact on your __BG__ and __IOB__ for the next few days. +8. Repeat this pattern, observe, decide, tweak again if needed + +Don't rush, go slow! + +## **Recommended settings and advice while tweaking basal** + +- Do all testing with [closed loop enabled](#AapsScreens-loop-status). +- **Turn OFF all [automations](../DailyLifeWithAAPS/Automations.md)** +- **Turn OFF [DynISF](#Open-APS-features-DynamicISF), [AutoISF](../AdvancedOptions/DevBranch.md), [AutoSens](#Open-APS-features-autosens)** so that they will not try to adapt your profile. +- Do not make manual user actions (manual bolus, temp targets etc…) while testing: let the system use the **Profile** settings only. +- For the [additional graphs](#AapsScreens-section-g-additional-graphs): on graph 1, use Insulin On Board, Carbs On Board (and Sensitivity change). On graph 2, use Deviations and Blood Glucose Impact. When asking for advice, always include those on your screenshots. +- COB=0[*](#profiletuning-cob-zero) +- No physical activities. +- No stress. +- No illness. +- No extreme weather like high or low temperatures. +- If your [basal rate profile](#your-aaps-profile-basal-rates) is correct, when you are on target with COB=0[*](#profiletuning-cob-zero) and IOB=0, you will remain constantly on target whatever your ISF (ISF is only used when you are higher than your target). +- You need to check the actual IOB but also, the IOB chart to see how the IOB was during the past few hours. + +(profiletuning-cob-zero)= + +***COB = 0** + +Meaning that the meal is digested, and there are no more carbs in your body. + +AAPS might indicate [COB=0 while you still have carbs on board](../DailyLifeWithAAPS/CobCalculation.md). + +## **[Profile](../SettingUpAaps/YourAapsProfile.md) definitions** + +A too **strong Profile** indicates some combination of the following: + +- [ISF](#insulin-sensitivity-factor-isf) number is too small +- The [basal](#basal-rates) number is too big +- [I:C](#insulin-to-carb-ratio-icr) number is too small + +## **IOB Observations** + +*Note: you can also use Loopalyzer IOB graph in Nightscout reports to view IOB on several days.* + +If you observe the following patterns after a few days, consider the following changes + +### **IOB positive** + +- **Profile** basal might not be strong enough (this could also be because of things like unannounced food, illness, bad site absorption, etc.) + +![Positive IOB](../images/troubleshooting/profiletuning/PositiveInsulin.png) + +### **IOB negative** + +- Default basal too strong +- May be the effect from past exercise/physical activity + +![Negative IOB](../images/troubleshooting/profiletuning/NegativeInsulin.png) + +- Previous meal: too much bolus (which resulted in a very long zero temp basal) + +![Negative IOB](../images/troubleshooting/profiletuning/NegativeInsulin2.png) + +## **BG Target Observations** + +### **Stuck High** + +- __ISF__ ‘s number is high and not strong enough (calculated insulin is too weak) + +![Stuck High](../images/troubleshooting/profiletuning/StuckHigh.png) + +- __Profile__ basal might not be strong enough (SMBs do not have enough "basal stock" to use) +- A security ([MaxIOB](#Open-APS-features-maximum-total-iob-openaps-cant-go-over)?) might have kicked in and is limiting insulin injection. Verify in the [SMB](#Open-APS-features-super-micro-bolus-smb) tab. +- Technical issue: site absorption, infusion set, ... + +### **Stuck Low** + +- __ISF__ too strong and the number needs to be raised higher +- __Profile__ basal too strong (if also negative IOB) + +### **Rollercoaster (ups and downs)** + +- **ISF** too strong? See your [AAPS Profile](#your-aaps-profile-insulin-sensitivity-factor) + +![Rollercoaster](../images/troubleshooting/profiletuning/StrongISF.png) + +## **BG After Meals Observations** + +### **Fast rise and BG going high** + +- Food contains fast carbs +- Consider doing a pre-bolus +- Bolus (IC or injected %) not strong enough + +![Rise High](../images/troubleshooting/profiletuning/FastRise.png) + +### **Fast rise and then BG going low** + +- Consider doing a pre-bolus, profile might be too aggressive (over correction of the raise) +- Bolus too strong + + + +## **[How to calculate your I:C](#your-aaps-profile-insulin-to-carbs-ratio)** + +1. First, you need the correct default basal settings in your **Profile**. +2. Start on target, better without negative IOB. +3. Record the total insulin given in the pump tab (or pump history) and call it Start insulin C4. Very accurately measure a known portion of carbs, and record the start time and Start IOB. Then enter carbs and bolus information into AAPS using the wizard (with the current configured CI). Don't forget to eat the carbs ;) +4. After some hours, when COB=0[*](#profiletuning-cob-zero) and you're back on target, record end time, and note down the End IOB, check the total insulin given as before and call it End insulin. *NOTE: The time frame is NOT important, as long as it is longer than your digestion* +5. From the difference between Start and End insulin amount, subtract/add the difference end IOB - start IOB. Then subtract the basal insulin calculated from your profile settings. +6. If __BG__ is in target, you'll have the total insulin used to “digest” your carbs. Calculate your **I:C**. + +### **Explanations for the I:C calculations** + +- With a **Profile** that has the correct default basal rate, during any time frame, you should stay on target and have an IOB near 0. You get your **Profile** basal only. +- You add carbs and bolus to this mix. Wait till your body digests all the carbs and be back on **BG** target. Your insulin usage will be the sum of your basal + the insulin needed for the carbs. You calculate the insulin used for your basal (by using your **Profile**) and the surplus will be the insulin used to digest the carbs. +- If the time frame is too short, there will be carbs undigested, thus your "insulin needed for the carbs" will be wrong. +- If the time frame is too long, nothing bad will happen. You'll use all your carbs and you'll get more basal. At the end, you'll subtract the basal from the total insulin used, the extended time frame (with more basal use) will not affect the result. + +Originally written up by @Robby (Discord) on tips and tricks to help tune your AAPS Profile, reviewed and edited by the community (thank you!). diff --git a/docs/CROWDIN/zh_TW/SettingUpAaps/ComputerBuild.md b/docs/CROWDIN/zh_TW/SettingUpAaps/ComputerBuild.md index 2c74d27a4b12..93ee3d93bb87 100644 --- a/docs/CROWDIN/zh_TW/SettingUpAaps/ComputerBuild.md +++ b/docs/CROWDIN/zh_TW/SettingUpAaps/ComputerBuild.md @@ -70,7 +70,7 @@ Gradle版本與源代碼相連結，下載/更新源代碼時，你將始終獲 ## 建置過程中的幫助與支援 -如果在建置**AAPS**應用的過程中遇到困難，請參考專門的[**Android Studio問題排除**](../GettingHelp/TroubleshootingAndroidStudio)部分。 +If you run into difficulties in the process of building the **AAPS** app, there is a dedicated [**troubleshooting Android Studio**](../GettingHelp/TroubleshootingAndroidStudio.md) section, please consult that first. 如果你認為建置說明中的內容有錯誤、缺失或令人困惑，或仍然感到困難，請與其他**AAPS**用戶群聯繫，群組可在[Facebook](https://www.facebook.com/groups/AndroidAPSUsers)或[Discord](https://discord.gg/4fQUWHZ4Mw)上找到。 如果你想自行更改某些內容（更新螢幕截圖_等_），請提交[拉取請求（PR）](../SupportingAaps/HowToEditTheDocs.md)。 @@ -409,7 +409,7 @@ Android Studio在建置完成後將顯示“BUILD SUCCESSFUL”的訊息。 你 ![建置完成](../images/Building-the-App/049_ReopenNotification.png) -**_如果建置不成功，請參考[Android Studio 問題排除部分](../GettingHelp/TroubleshootingAndroidStudio)。_** +**_If the build was not successful, refer to the [Android Studio Troubleshooting section](../GettingHelp/TroubleshootingAndroidStudio.md)._** 在通知欄中，點擊藍色連結“定位”： diff --git a/docs/CROWDIN/zh_TW/SettingUpAaps/Preferences.md b/docs/CROWDIN/zh_TW/SettingUpAaps/Preferences.md index 483378b0bea0..038ff60f34f1 100644 --- a/docs/CROWDIN/zh_TW/SettingUpAaps/Preferences.md +++ b/docs/CROWDIN/zh_TW/SettingUpAaps/Preferences.md @@ -300,7 +300,7 @@ ![組態建置工具 - 循環模式](../images/ConfigBuilder_LoopLGS.png) -(Preferences-pen-loop)= +(Preferences-open-loop)= #### 開放循環 **AAPS**持續評估所有可用資料（IOB、COB、BG...）並在必要時提供治療建議（臨時基礎率），告訴你如何調整治療。 diff --git a/docs/CROWDIN/zh_TW/SettingUpAaps/YourAapsProfile.md b/docs/CROWDIN/zh_TW/SettingUpAaps/YourAapsProfile.md index 53e4d5fe3b31..14d134ca6d61 100644 --- a/docs/CROWDIN/zh_TW/SettingUpAaps/YourAapsProfile.md +++ b/docs/CROWDIN/zh_TW/SettingUpAaps/YourAapsProfile.md @@ -123,11 +123,13 @@ 正確設定你的基礎率需要透過反覆試驗，並且應在與你的糖尿病團隊的諮詢下進行。 -有一些基礎測試方法，通常涉及在24小時內觀察你的基礎率和胰島素需求。 雖然你需要測試全天的基礎率，但不建議連續禁食24小時。 因為身體會啟動機制如激素來進行補償。 推薦的方式是禁食3次，每次8小時。 +There are basal testing methods which usually entails observing your basal rates and insulin needs during an intermittent fasting over a 24-hour period. 雖然你需要測試全天的基礎率，但不建議連續禁食24小時。 因為身體會啟動機制如激素來進行補償。 推薦的方式是禁食3次，每次8小時。 -推薦的方法是暫停循環，這樣會恢復到你的預設背景基礎率。 觀察你的**血糖**如何變化：如果它下降，則基礎率過高。 反之亦然。
另一種替代方法（ might be more tricky）是在循環運行的情況下，查看**IOB**如何變化。 如果**IOB**是負的，則你的基礎率過高。 反之亦然。 請注意，這種方法依賴於**ISF**來修正**血糖**，因此需要其他變數合理設置，這樣才能成功。
調整基礎率的另一種方法是觀察在夜間的循環行為，當所有 COB 已經降到為止。 這種方法對於兒童特別有用，因為禁食較困難或胰島素需求經常變化。 [Tidepool 的 Saleh Adi 醫生](https://www.youtube.com/watch?v=-fpWnGRhLSo)提供了如何分析夜間 血糖數據線以優化你的基礎率的有用建議。 +The recommended method is to suspend the loop (for safety you can set AAPS to [**LGS**](#Preferences-aps-mode) to avoid lows, as done for achieving [objective 6](#objectives-objective6)), which will revert to your default background basal rate. 觀察你的**血糖**如何變化：如果它下降，則基礎率過高。 反之亦然。
另一種替代方法（ might be more tricky）是在循環運行的情況下，查看**IOB**如何變化。 如果**IOB**是負的，則你的基礎率過高。 反之亦然。 請注意，這種方法依賴於**ISF**來修正**血糖**，因此需要其他變數合理設置，這樣才能成功。
調整基礎率的另一種方法是觀察在夜間的循環行為，當所有 COB 已經降到為止。 這種方法對於兒童特別有用，因為禁食較困難或胰島素需求經常變化。 [Dr Saleh Adi from Tidepool](https://www.youtube.com/watch?v=-fpWnGRhLSo) provides useful ways on how to analyze overnight BG lines in order to optimize your basal rates. -當你對基礎測試的結果採取行動時，對**設定檔**的變更應在升高/下降前1小時進行。 根據需要重複測試，直到你對**基礎率**設定感到滿意。 +See [here](../GettingHelp/ProfileTuning.md) how to tweak your basal profile, analyzing patterns in closed loop. + +When taking action on the result of your basal testing, changes in the **Profile** should be done 1 to 2 hours (depends on your insulin type) before the rise/drop. 根據需要重複測試，直到你對**基礎率**設定感到滿意。 (your-aaps-profile-insulin-sensitivity-factor)= diff --git a/docs/CROWDIN/zh_TW/SupportingAaps/HowCanIHelp.md b/docs/CROWDIN/zh_TW/SupportingAaps/HowCanIHelp.md index c12f0349992d..cb8a0c5d9d67 100644 --- a/docs/CROWDIN/zh_TW/SupportingAaps/HowCanIHelp.md +++ b/docs/CROWDIN/zh_TW/SupportingAaps/HowCanIHelp.md @@ -15,7 +15,7 @@ 太好了，這是非常受到歡迎的事，也是報答社群的好方式！ * 關於 Wiki 的 Discord 頻道可以在這裡找到：[AndroidAPS](https://discord.gg/4fQUWHZ4Mw)。 -* 有關如何在英文 wiki 中進行提交的指南可以在這裡找到：[如何製作 PR](../SupportingAaps/HowToEditTheDocs.md)。 其他語系僅從英文翻譯，出於一致性原因，無法進行編輯。 +* 有關如何在英文 wiki 中進行提交的指南可以在這裡找到：[如何製作 PR](../SupportingAaps/HowToEditTheDocs.md)。 Other languages are only translated from English and can't be edited for consistency reasons. ## 我會多種語系，想翻譯應用程式或文件 @@ -23,7 +23,7 @@ 你也可以同時或稍後開始翻譯文件。 -你可以在[這裡](StateOfTranslations)檢查應用程式和文件的翻譯狀態。 +You can check the state of translations for the languages app and documentation [here](#StateOfTranslations). * 如果你想將**應用程式**翻譯成其他語系（感謝你的幫助），請使用 [Crowdin](https://crowdin.com/project/androidaps)。 * 如果你想將**文件**翻譯成其他語系（感謝你的幫助），請使用 [Crowdin](https://crowdin.com/project/androidapsdocs)。 diff --git a/docs/CROWDIN/zh_TW/UsefulLinks/FAQ.md b/docs/CROWDIN/zh_TW/UsefulLinks/FAQ.md index 41975de690bd..63d335bc6c27 100644 --- a/docs/CROWDIN/zh_TW/UsefulLinks/FAQ.md +++ b/docs/CROWDIN/zh_TW/UsefulLinks/FAQ.md @@ -247,7 +247,7 @@ AAPS 用來控制你的幫浦並提供胰島素。 根據歐洲現行法規， 請 -- 請檢查[問題排除 Android Studio](../GettingHelp/TroubleshootingAndroidStudio)以獲取典型錯誤和 +- check [Troubleshooting Android Studio](../GettingHelp/TroubleshootingAndroidStudio.md) for typical errors and - 查看有關[逐步指南](https://docs.google.com/document/d/1oc7aG0qrIMvK57unMqPEOoLt-J8UT1mxTKdTAxm8-po)的提示。 ### 我在目標上卡住了，需要幫助。 diff --git a/docs/CROWDIN/zh_TW/images/troubleshooting/profiletuning/FastRise.png b/docs/CROWDIN/zh_TW/images/troubleshooting/profiletuning/FastRise.png new file mode 100644 index 000000000000..ba35b5bb6bf0 Binary files /dev/null and b/docs/CROWDIN/zh_TW/images/troubleshooting/profiletuning/FastRise.png differ diff --git a/docs/CROWDIN/zh_TW/images/troubleshooting/profiletuning/NegativeInsulin.png b/docs/CROWDIN/zh_TW/images/troubleshooting/profiletuning/NegativeInsulin.png new file mode 100644 index 000000000000..7c39c50d00df Binary files /dev/null and b/docs/CROWDIN/zh_TW/images/troubleshooting/profiletuning/NegativeInsulin.png differ diff --git a/docs/CROWDIN/zh_TW/images/troubleshooting/profiletuning/NegativeInsulin2.png b/docs/CROWDIN/zh_TW/images/troubleshooting/profiletuning/NegativeInsulin2.png new file mode 100644 index 000000000000..4bd840d597ad Binary files /dev/null and b/docs/CROWDIN/zh_TW/images/troubleshooting/profiletuning/NegativeInsulin2.png differ diff --git a/docs/CROWDIN/zh_TW/images/troubleshooting/profiletuning/PositiveInsulin.png b/docs/CROWDIN/zh_TW/images/troubleshooting/profiletuning/PositiveInsulin.png new file mode 100644 index 000000000000..e50e806ebf01 Binary files /dev/null and b/docs/CROWDIN/zh_TW/images/troubleshooting/profiletuning/PositiveInsulin.png differ diff --git a/docs/CROWDIN/zh_TW/images/troubleshooting/profiletuning/StrongISF.png b/docs/CROWDIN/zh_TW/images/troubleshooting/profiletuning/StrongISF.png new file mode 100644 index 000000000000..ca16a1ad1b9d Binary files /dev/null and b/docs/CROWDIN/zh_TW/images/troubleshooting/profiletuning/StrongISF.png differ diff --git a/docs/CROWDIN/zh_TW/images/troubleshooting/profiletuning/StuckHigh.png b/docs/CROWDIN/zh_TW/images/troubleshooting/profiletuning/StuckHigh.png new file mode 100644 index 000000000000..1fbeefc01c50 Binary files /dev/null and b/docs/CROWDIN/zh_TW/images/troubleshooting/profiletuning/StuckHigh.png differ diff --git a/docs/CROWDIN/zh_TW/index.md b/docs/CROWDIN/zh_TW/index.md index bfcabcf46193..dffaf3ac72fa 100644 --- a/docs/CROWDIN/zh_TW/index.md +++ b/docs/CROWDIN/zh_TW/index.md @@ -154,13 +154,14 @@ AAPS 版本更新說明 <./Maintenance/ReleaseNotes.md> ``` ```{toctree} -:caption: 8) 取得協助 - -在哪裡可以取得 AAPS 協助 <./GettingHelp/WhereCanIGetHelp.md> -一般疑難排解 <./GettingHelp/GeneralTroubleshooting.md> -- 藍牙疑難排解 <./GettingHelp/BluetoothTroubleshooting.md> -Android Studio 疑難排解 <./GettingHelp/TroubleshootingAndroidStudio.md> -存取記錄檔 <./GettingHelp/AccessingLogFiles.md> +:caption: 8) Getting Help + +Where can I get help with AAPS <./GettingHelp/WhereCanIGetHelp.md> +General troubleshooting <./GettingHelp/GeneralTroubleshooting.md> +- Bluetooth troubleshooting <./GettingHelp/BluetoothTroubleshooting.md> +Profile Tuning Guide <./GettingHelp/ProfileTuning.md> +Troubleshooting Android Studio <./GettingHelp/TroubleshootingAndroidStudio.md> +Accessing logfiles <./GettingHelp/AccessingLogFiles.md> ``` ```{toctree}