diff --git a/docs/CROWDIN/ar/Hardware/Smartwatch.md b/docs/CROWDIN/ar/Hardware/Smartwatch.md deleted file mode 100644 index 12281d6d256a..000000000000 --- a/docs/CROWDIN/ar/Hardware/Smartwatch.md +++ /dev/null @@ -1,10 +0,0 @@ -# Smartwatches - -Smartwatches are optional, but very useful for some users. More details are here: - -- [List of tested phones and smartwatches](../Getting-Started/Phones.md) -- [Watchfaces Wear OS](../Configuration/Watchfaces.md) -- [Troubleshooting Sony Smartwatch SW 3](../Usage/SonySW3.md) - -## Instructions for Building the AAPS Wear APK for Wear OS -https://androidaps.readthedocs.io/en/latest/remote-control.html#building-the-aaps-wear-apk diff --git a/docs/CROWDIN/ar/Sandbox/sandbox2.md b/docs/CROWDIN/ar/Sandbox/sandbox2.md deleted file mode 100644 index b44d905fe338..000000000000 --- a/docs/CROWDIN/ar/Sandbox/sandbox2.md +++ /dev/null @@ -1,32 +0,0 @@ -# internal sandbox file 2 for testing - -```{admonition} no need to translate this -:class: note - -No need to translate this. -``` - -This is an internal sandbox file for the documentation team to test - -1. markdown syntax and - -1. background process for - 1. CROWDIN translation and - 2. Read The Docs deployment. - -You can dirctly jump from here to the first label in the sandbox1.md file - ["Jump"](sandbox1-this-is-a-test). - -You can dirctly jump from here to the second label in this file - ["Jump"](sandbox1-this-is-another-test). - -Here you can jump to the first sandbox file - ["Jump"](./sandbox1.md). - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -(sandbox2-this-is-a-test)= -## This is a test - -This is a test if labels must be unique. diff --git a/docs/CROWDIN/ar/Usage/Objectives.md b/docs/CROWDIN/ar/Usage/Objectives.md deleted file mode 100644 index 11e81d6e955a..000000000000 --- a/docs/CROWDIN/ar/Usage/Objectives.md +++ /dev/null @@ -1,168 +0,0 @@ -# Objectives - -AAPS has a series of Objectives that need to be completed to walk you through the features and settings of safe looping. They ensure you have configured everything detailed in the sections above correctly, and that you understand what your system is doing and why so you can trust it. - -If you are **upgrading phones** then you can [export your settings](../Usage/ExportImportSettings.md) to keep your progress through the objectives. Not only will your progress through the objectives be saved, but also your safety settings such as max bolus etc. If you do not export and import your settings then you will need to start the objectives from the beginning again. It is a good idea to [backup your settings](../Usage/ExportImportSettings.html) frequently just in case. - -If you want to go back in objectives see [explanation below](Objectives-go-back-in-objectives). - -## Objective 1: Setting up visualization and monitoring, analysing basals and ratios - -- Select the right blood glucose source for your setup. See [BG Source](../Configuration/BG-Source.md) for more information. -- Select the right Pump in ConfigBuilder (select Virtual Pump if you are using a pump model with no AAPS driver for looping) to ensure your pump status can communicate with AAPS. -- If using DanaR pump then ensure you have followed [DanaR Insulin Pump](../Configuration/DanaR-Insulin-Pump.md) instructions to ensure the link between pump and AAPS. -- You need to establish a data repository/reporting platform to complete this objective. That can be accomplished with either Nightscout or Tidepool (or both). Follow instructions at the [Nightscout](../Installing-AndroidAPS/Nightscout.md) or [Tidepool](../Installing-AndroidAPS/Tidepool.md) page for instructions. -- Note that URL in NSClient must be **WITHOUT /api/v1/** at the end - see [NSClient settings in Preferences](Preferences-nsclient). - -*You may need to wait for the next blood glucose reading to arrive before AAPS will recognise it.* - -## Objective 2: Learn how to control AAPS - -- Perform several actions in AAPS as described in this objective. - -- Click on the orange text "Not completed yet" to access the to-dos. - -- Links will be provided to guide you in case you are not familiar with a specific action yet. - - ![Screenshot objective 2](../images/Objective2_V2_5.png) - -(Objectives-objective-3-prove-your-knowledge)= - -## Objective 3: Prove your knowledge - -Objective 3 is a multiple choice test based on questions designed to test your theoretical knowledge of **AAPS**. - -Some users find Objective 3 to be the most difficult objective to complete. Please do read the AAPS documents in conjunction with the questions. If you are genuinely stuck after researching the **AAPS** documents, please search or ask for help on the Facebook or Discord group. These groups can provide friendly hints or redirect you to the relevant part of the **AAPS** documents. - -To proceed with Objective 3, click on the orange text “Not completed yet” to access the relevant question. Please read each question and select your answer(s). - - - -Within each question, a hyperlink to the **AAPS** documents will guide you to the relevant section of the document which you should read in order to locate the correct answer. - - -[Obj3_Screenshot 2023-12-05 223422](https://github.com/openaps/AndroidAPSdocs/assets/137224335/77347516-e24e-459d-98ab-acbb49a3d4e8)![image](https://github.com/openaps/AndroidAPSdocs/assets/137224335/ca756b8e-efbc-4427-b281-ac953ce16718) - - - -For each question, there may be more than one answer that is correct! If an incorrect answer is selected, the question will be time locked for a certain amount of time (60 minutes) before you can go back and answer the question. - - -After updating to a new version of **AAPS**, new questions may be added to cover a prevalent issue picked up by **AAPS** or alternatively to test your knowledge of a new feature of **AAPS** as released. - - -When **AAPS** is installed for the first time, you will have to complete Objective 3 entirely in order to move onto Objective 4. Each objective is required to be completed in sequential order. New features will gradually be unlocked as progress is made through the objectives. - -__What happens if new questions are added later to Objective 3?__ From time to time, new features are added to **AAPS** which may require a new question to be added to Objective 3. As a result, any new question added to Objective 3 will be marked as “incomplete” because **AAPS** will require you to action this. As each Objective is independent, you will not lose the existing functionality of **AAPS** providing the other objectives remain completed. - - -## Objective 4: Starting on an open loop - -- Select Open Loop either from Preferences, or by pressing and holding the Loop button in top left of the home screen. -- Work through the [Preferences](../Configuration/Preferences.md) to set up for you. -- Manually enact at least 20 of the temporary basal rate suggestions over a period of 7 days; input them to your pump and confirm in AAPS that you have accepted them. Ensure this data shows in AAPS and Nightscout. -- Enable [temp targets](../Usage/temptarget.md) if necessary. Use hypo temp targets to prevent that the system will correct too strong because of a raising blood glucose after a hypo. - -### Reduce number of notifications - -- To reduce the Number of decisions to be made while in Open Loop set wide target range like 90 - 150 mg/dl or 5,0 - 8,5 mmol/l. - -- You might even want to wider upper limit (or disable Open Loop) at night. - -- In Preferences you can set a minimum percentage for suggestion of basal rate change. - - ![Open Loop minimal request change](../images/OpenLoop_MinimalRequestChange2.png) - -- Also, you do not need to act every 5 minutes on all suggestions... - -## Objective 5: Understanding your open loop, including its temp basal recommendations - -- Start to understand the thinking behind the temp basal recommendations by looking at the [determine basal logic](https://openaps.readthedocs.io/en/latest/docs/While%20You%20Wait%20For%20Gear/Understand-determine-basal.html) and both the [forecast line in AAPS homescreen](Screenshots-prediction-lines)/Nightscout and the summary of outputs from the calculations in your OpenAPS tab. - -You will want to set your target higher than usual until you are confident in the calculations and settings. System allows - -- a low target to be a minimum of 4 mmol (72 mg/dl) or maximum of 10 mmol (180 mg/dl) -- a high target to be a minimum of 5 mmol (90 mg/dl) and maximum of 15 mmol (225 mg/dl) -- a temporary target as a single value can be anywhere in the range of 4 mmol to 15 mmol (72 mg/dl to 225 mg/dl) - -The target is the value that calculations are based on, and not the same as where you aim to keep your blood glucose values within. If your target is very wide (say, 3 or more mmol \[50 mg/dl or more\] wide), you will often find little AAPS action. This is because blood glucose is eventually predicted to be somewhere in that wide range and therefore not many fluctuating temporary basal rates are suggested. - -You may want to experiment with adjusting your targets to be a closer together range (say, 1 or less mmol \[20 mg/dl or less\] wide) and observe how the behavior of your system changes as a result. - -You can view a wider range (green lines) on the graph for the values you aim to keep your blood glucose within by entering different values in [Preferences](../Configuration/Preferences.md) > Range for Visualisation. - -![Stop sign](../images/sign_stop.png) - -### Stop here if you are open looping with a virtual pump - do not click Verify at the end of this objective. - -![blank](../images/blank.png) - -(Objectives-objective-6-starting-to-close-the-loop-with-low-glucose-suspend)= -## Objective 6: Starting to close the loop with Low Glucose Suspend - -![Warning sign](../images/sign_warning.png) - -### Closed loop will not correct high BG values in objective 6 as it is limited to low glucose suspend. High BG values have to be corrected manually by you! - -- Prerequisite: You need a good profile (basal, ISF, IC) already working in AAPS to start with Loop in Low Glucose Suspend mode. Otherwise you can run in a hypo which you have to manually correct. This will help you a lot to avoid having to treat a low glucose over a period of 5 days. **If you are still having frequent or severe low glucose episodes then consider refining your DIA, basal, ISF and carb ratios and do NOT start objective 6 at this time.** -- You don't have to change your settings now. During objective 6, the maxIOB setting is internally set to zero automatically. **This override will be reversed when moving to objective 7.** -- The system will override your maxIOB settings to zero, which means if blood glucose is dropping it can reduce basal for you. If blood glucose is rising then it will only increase basal if the basal IOB is negative from a previous Low Glucose Suspend. Otherwise basal rates will remain the same as your selected profile. **That means that you have to manually handle high values with insulin corrections.** -- If your basal IOB is negative (see screenshot below) a TBR > 100% can be issued also in objective 6. - -![Example negative IOB](../images/Objective6_negIOB.png) - -- Set your target range slightly higher than you usually aim for, just to be safe and have a bit more scurity buffer. -- Enable 'Low Glucose Suspend' mode either by by pressing and holding the Loop icon at the top right corner of the home screen and selecting the Loop - LGS mode icon. -- Watch how temporary basals are active by viewing the blue basal text on the homescreen or the blue basal render on the homescreen graph. -- You may temporarily experience spikes following treated hypos without the ability to increase basal on the rebound. - -(Objectives-objective-7-tuning-the-closed-loop-raising-max-iob-above-0-and-gradually-lowering-bg-targets)= -## Objective 7: Tuning the closed loop, raising maxIOB above 0 and gradually lowering BG targets - -- Select 'Closed Loop' either from [Preferences](../Configuration/Preferences.md) or by pressing and holding the Loop icon at the top right corner of the home screen, over a period of 1 day. - -- Raise your 'Maximum total IOB OpenAPS can’t go over' (in OpenAPS called 'max-iob') above 0. The default recommendation is "average mealbolus + 3x max daily basal" (for the SMB algorithm) or "3x max daily basal" (for the older AMA algorithm) but you should slowly work up to this until you know your settings work for you (max daily basal = the maximum hourly value in any time segment of the day). - - This recommendation should be seen as a starting point. If you set to the 3x and you are seeing moves that push you too hard and fast then lower that number. If you are very resistant, raise it very little at a time. - - ![max daily basal](../images/MaxDailyBasal2.png) - -- Once confident on how much IOB suits your looping patterns, then reduce your targets to your desired level. - -(Objectives-objective-8-adjust-basals-and-ratios-if-needed-and-then-enable-autosens)= -## Objective 8: Adjust basals and ratios if needed, and then enable autosens - -- You can use [autotune](https://openaps.readthedocs.io/en/latest/docs/Customize-Iterate/autotune.html) as a one off to check your basals remain accurate or do a traditional basal test. -- Enable [autosens](../Usage/Open-APS-features.md) over a period of 7 days and watch the white line on the homescreen graph show how your sensitivity to insulin may be rising or falling as a result of exercise or hormones etc. and keep an eye in the OpenAPS report tab how AAPS is adjusting the basals and/or targets accordingly. - -*Don’t forget to record your looping in* [this form](https://bit.ly/nowlooping) *logging AAPS as your type of DIY loop software, if you have not already done so.* - -(Objectives-objective-9-enabling-additional-oref1-features-for-daytime-use-such-as-super-micro-bolus-smb)= -## Objective 9: Enabling additional oref1 features for daytime use, such as super micro bolus (SMB) - -- You must read the [SMB chapter in this wiki](Open-APS-features-super-micro-bolus-smb) and [chapter oref1 in openAPSdocs](https://openaps.readthedocs.io/en/latest/docs/Customize-Iterate/oref1.html) to understand how SMB works, especially what's the idea behind zero-temping. -- Then you ought to [rise maxIOB](Open-APS-features-maximum-total-iob-openaps-cant-go-over-openaps-max-iob) to get SMBs working fine. maxIOB now includes all IOB, not just added basal. That is, if given a bolus of 8 U for a meal and maxIOB is 7 U, no SMBs will be delivered until IOB drops below 7 U. A good start is maxIOB = average mealbolus + 3x max daily basal (max daily basal = the maximum hourly value in any time segment of the day - see [objective 7](Objectives-objective-7-tuning-the-closed-loop-raising-max-iob-above-0-and-gradually-lowering-bg-targets) for an illustration) -- min_5m_carbimpact default in absorption settings has changed from 3 to 8 going from AMA to SMB. If you are upgrading from AMA to SMB, you have to change it manually. - -(Objectives-objective-10-automation)= -## Objective 10: Automation - -- You have to start objective 10 to be able to use [Automation](../Usage/Automation.md). -- Make sure you have completed all objectives including exam [Objectives-objective-3-prove-your-knowledge](Objectives#objective-3-prove-your-knowledge). -- Completing previous objectives will not effect other objectives you have already finished. You will keep all finished objectives! - -(Objectives-objective-11-DynamicISF)= -## Objective 11: Additional Features such as DynamicISF - -- You have to start objective 11 to be able to use [DynamicISF](../Usage/Open-APS-features.md) - -(Objectives-go-back-in-objectives)= -## Go back in objectives - -If you want to go back in objectives for whatever reason you can do so by clicking at "clear finished". - -![Go back in objectives](../images/Objective_ClearFinished.png) - -## Objectives in Android APS before version 3.0 - -One objective was removed when Android APS 3.0 was released. Users of Android APS version 2.8.2.1 who are on older Android software (i.e. earlier than version 9) will be using an older set of objectives which can be found [here](../Usage/Objectives_old.md). diff --git a/docs/CROWDIN/cs/Configuration/Dexcom.md b/docs/CROWDIN/cs/Configuration/Dexcom.md deleted file mode 100644 index 313b7fcaf010..000000000000 --- a/docs/CROWDIN/cs/Configuration/Dexcom.md +++ /dev/null @@ -1,32 +0,0 @@ -# Dexcom G6 - -## Základní nastavení - -* Postupujte podle [obecných doporučení pro používání CGM](../Configuration/BG-Source#cgm-hygiene) -* [Zvláštní doporučení pro Dexcom G6 a DIY systémy](../Configuration/BG-Source#dexcom-g6-diy-systems) *V případě vysílačů G6 vyrobených po podzimu / ke konci roku 2018 se prosím ujistěte, že používáte jednu z [nejnovějších verzí aplikace xDrip+ (tzv. nightly built)](https://github.com/NightscoutFoundation/xDrip/releases). Tyto vysílače mají nový firmware, a poslední stabilní verze xDrip+ (2019/01/10) si s ním neporadí. - -## Nastavení senzoru - -Při nastřelování senzoru je doporučeno nepřikládat aplikátor příliš velkou silou, aby se zabránilo krvácení. Senzor by se neměl dostat do kontaktu s krví. - -Po nastřelení senzoru je možno nakliknout vysílač do pouzdra senzoru. Pozor! Vysílač nejprve nasaďte na hranaté straně senzoru, a až poté na kulaté. - -## Poradce při potížích - -### Problém s připojením - -Bluetooth spojení může být rušeno nedalekými Bluetooth zařízeními, jako například glukomentry, bluetooth sluchátka, tablety nebo kuchyňská zařízení, jako jsou mikrovlnné trouby nebo varné desky. V tomto případě xDrip neukazuje žádné hodnoty glykémií. Jakmile se bluetooth spojení obnoví, jsou data zpětně doplněna. - -### Chyby senzorů - -V případě vyskytnutí opakovaných problémů se senzorem zkuste senzor nastřelit na jinou část těla. Senzor by se neměl dostat do kontaktu s krví. - -Často je možné vyřešit problémy senzoru okamžitým podáním tekutin a masáží kolem senzoru! - -### Skákající hodnoty - -Můžete zkusit změnit nastavení blokování šumu v aplikaci xdrip (Nastavení - Komunikace mezi aplikacemi - Noise Blocking), např.: „Block Very High noise and worse“ (Blokovat velmi vysoký šum a horší). Viz také [Vyhlazování dat glykémií](../Usage/Smoothing-Blood-Glucose-Data-in-xDrip.md). - -### Nový vysílač se spuštěným senzorem - -Pokud se stane, že budete měnit vysílač na spuštěném senzoru, pokuste se odejmout vysílač, aniž byste poškodili samotný senzor. Video najdete na . \ No newline at end of file diff --git a/docs/CROWDIN/cs/Configuration/EOFLOW.md b/docs/CROWDIN/cs/Configuration/EOFLOW.md deleted file mode 100644 index aca5a67ec4cc..000000000000 --- a/docs/CROWDIN/cs/Configuration/EOFLOW.md +++ /dev/null @@ -1,155 +0,0 @@ -# EOPatch2 Instruction Manual - -The patch requires the use of rapid-acting U-100 type insulin, such as NovoRapid or Humalog. Use a rapid-acting insulin that is suitable for you according to your doctor’s prescription and inject the prescribed dosage. - -The smallest injectable dose of insulin when using the patch is 0.05 U. The Profile BAS should therefore be set at a minimum value of 0.05 U/hr or more and an interval of 0.05 U/hr, as otherwise there may be an error between the estimated total infusion amount in the Profile and the actual infusion amount in the patch. Likewise, the bolus must also be set and infused with a minimum infusion volume of 0.05 U. - -## Pump Setup -1. On the AndroidAPS home screen, click the hamburger menu in the upper left corner and go to Config Builder. -1. Select 'EOPatch2' in the Pump section. -1. Press the Back key to return to the home screen. - -![Bild1](../../images/EOPatch/Bild1.png) ![Bild2](../../images/EOPatch/Bild2.png) - -## Nastavení -Select EOPATCH2 at the top of the home screen to go to the EOPATCH2 tab. - -Select the EOPatch2 Preferences menu by clicking the three dots in the upper right corner. - -The EOPatch2 Preferences menu offers a menu to set 3 types of notifications. - -### Low reservoir Alerts -A warning appears when the amount of insulin remaining in the reservoir reaches the set value or less while using the patch. It can be set from 10 to 50U in 5U increments. - -### Patch expiration Reminder -This is a reminder to notify you of the time remaining before the current patch expires. It can be set from 1 to 24 hours in 1 hour increments. The initial setting value is 4 hours. - -### Patch buzzer Reminder -This is a reminder function for injections other than basal injection. If you are using an (extended) bolus injection or a temporary basal injection, the patch will make a buzzer sound when the injection starts and when the injection is complete. The initial setting value is Off. - -![Bild3](../../images/EOPatch/Bild3.png) - -## Connecting the Patch - -### Move to patch connection screen - -Select EOPATCH2 at the top of the home screen and click the ACTIVATE PATCH button at the bottom left. - -![Bild4](../../images/EOPatch/Bild4.png) - -### Connecting the patch -Insert the syringe needle into the insulin inlet on the patch and then slowly push the piston to inject the insulin. When insulin is filled with more than 80U, the patch makes a booting sound (1 buzzer) and boots. After confirming the buzzer sound, click the START PAIRING button on the screen. - -[Warning] - -- Do not turn the needle action lever until instructed. It can cause serious problems during injection or safety checks otherwise. -- The amount of insulin that can be injected into the patch is 80~200U. If you inject less than 80U into the patch initially, the patch will not work. -- Take the insulin to be put into the patch from the refrigerator and leave it at room temperature for 15 to 30 minutes beforehand. The temperature of the insulin to be injected must be at least 10°C. - -![Bild5](../../images/EOPatch/Bild5.png) - -### patch pairing -The Patch pairing screen will be displayed, and pairing will be attempted automatically. If communication is successful, the Bluetooth pairing request notification appears. Click OK and when the Bluetooth pairing request notification appears a second time with the authentication code, select OK again. - -[Warning] - -- For pairing, the patch and the smartphone must be located within 30 cm of each other. -- After the patch booting is completed, the patch will beep every 3 minutes until the pairing is complete. -- After booting the patch, the patch application must be completed via the app within 60 minutes. If the application cannot be completed within 60 minutes, the patch should be discarded. - -![Bild6](../../images/EOPatch/Bild6.png) ![Bild7](../../images/EOPatch/Bild7.png) ![Bild8](../../images/EOPatch/Bild8.png) - - -### patch preparation -After removing the adhesive tape of the patch, check if the needle is sticking out. If there are no problems with the patch, click NEXT. - -![Bild9](../../images/EOPatch/Bild9.png) - -### Patch attachment -Insulin should be injected in a spot with subcutaneous fat but few nerves or blood vessels, so it is recommended to use the abdomen, arm, or thigh for the patch attachment site. Choose a patch attachment site and apply the patch after disinfecting the location. - -[Warning] - -- Make sure to straighten the side of the patch tape attached to the body evenly, so that the patch adheres completely to the skin. -- If the patch does not stick completely, air may enter between the patch and the skin, which can weaken the adhesive strength and waterproof effect of the patch. - -![Bild10](../../images/EOPatch/Bild10.png) - -### Safety Check -When patching is complete, touch Start Safety Check. When the safety check is completed, the patch will beep once. - -[Warning] - -- For safe use, do not turn the needle action lever until the safety check has been completed. - -![Bild11](../../images/EOPatch/Bild11.png) ![Bild12](../../images/EOPatch/Bild12.png) - - -### Inserting the needle -The needle is inserted by holding around the patch and turning the needle action lever more than 100° in the upward direction of the lever. There is a buzzer sound when the needle is inserted correctly. Turn the needle action lever further clockwise to release the lever. Click NEXT. - -[Caution] - -- If you go to the next step without the buzzer sounding, a needle insertion error warning will appear. - -## Discarding the patch -Patches must be replaced in the case of low insulin levels, usage expiration, and defects. The recommended usage period for each patch is 84 hours after booting the patch. - -### Discarding the patch -Select EOPATCH2 at the top of the home screen and click the DISCARD/CHANGE PATCH button at the bottom. On the next screen, click the DISCARD PATCH button. A dialog box appears to confirm once more and if you select the DISCARD PATCH button, the disposal is completed. - -![Bild13](../../images/EOPatch/Bild13.png) ![Bild14](../../images/EOPatch/Bild14.png) ![Bild15](../../images/EOPatch/Bild15.png) ![Bild16](../../images/EOPatch/Bild16.png) - -## Suspending and Resuming Insulin Delivery -Suspending insulin delivery also cancels both extended bolus and temporary basal. When resuming insulin delivery, the canceled extended bolus and temporary basal will not be resumed. And when insulin delivery is suspended, the patch will give a sound every 15 minutes. - -### Suspending insulin delivery -Select EOPATCH2 at the top of the home screen and click the SUSPEND button at the bottom right. When you select CONFIRM in the confirmation box, a time selection box appears. If you select the CONFIRM button after selecting the time, the insulin delivery will be suspended for the set amount of time. - -![Bild17](../../images/EOPatch/Bild17.png) ![Bild18](../../images/EOPatch/Bild18.png) ![Bild19](../../images/EOPatch/Bild19.png) - - -### Resuming insulin delivery -Select EOPATCH2 at the top of the home screen and click the RESUME button at the bottom right. Insulin delivery will resume by selecting CONFIRM in the confirmation dialog box. - -![Bild20](../../images/EOPatch/Bild20.png) ![Bild21](../../images/EOPatch/Bild21.png) - -## Alarms/Warnings - -### Alarm - -Alarms are issued for emergency situations of the highest priority and require immediate action. The alarm signal does not disappear or time out until it is acknowledged. An alarm occurs when there is a problem with the patch being used, so there may be cases where the patch in use needs to be discarded and replaced with a new patch. The warning is displayed as a dialog box and switching to another screen is not possible until processing is completed. - -![Bild22](../../images/EOPatch/Bild22.png) ![Bild23](../../images/EOPatch/Bild23.png) - -The different types of alarms are explained below. - -| Alarms | Explanation | -| -------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| Empty reservoir | Occurs when the patch’s reservoir runs out of insulin. | -| Patch expired | Occurs when the patch usage time has expired, and no further insulin injections are possible. | -| Occlusion | Occurs when it appears that the patch's insulin inlet is clogged. | -| Power on self-test failure | Occurs when the patch finds an unexpected error during the post-boot self-test process. | -| Inappropriate temperature | Occurs when the patch is outside the normal operating temperature range during patch application and use. To deal with this alarm, move the patch to an appropriate operating temperature (4.4 to 37°C) condition. | -| Needle insertion Error | Occurs when needle insertion is not normal during the patch application process. Check that the needle insertion edge of the patch and the needle activation button are in a straight line. | -| Patch battery Error | Occurs just before the patch’s internal battery runs out and powers off. | -| Patch activation Error | Occurs when the app fails to complete the patching process within 60 minutes after the patch is booted. | -| Patch Error | Occurs when the patch encounters an unexpected error while applying and using the patch. | - -### Warning - -A warning occurs in a medium or low-priority situation. When a warning occurs, it is displayed as a notification in the Overview screen. - -![Bild24](../../images/EOPatch/Bild24.png) - -The different types of warnings are explained below. - -| Warnings | Explanation | -| ---------------------------- | ------------------------------------------------------------------------------------------------------------------------------------- | -| End of insulin suspend | Occurs when the time set by the user has elapsed after the insulin infusion suspension has been completed. | -| Low reservoir | Occurs when the remaining amount of insulin in the patch is below the set amount. | -| Patch operating life expired | Occurs when the patch usage period is over. | -| Patch will expire soon | Occurs 1 hour before the patch must be discarded. | -| Incomplete Patch activation | Occurs when more than 3 minutes have elapsed due to an interruption during patch application in the stage after pairing is completed. | -| Patch battery low | Occurs when the patch's battery is low. | - diff --git a/docs/CROWDIN/cs/Configuration/Hardware/index.md b/docs/CROWDIN/cs/Configuration/Hardware/index.md deleted file mode 100644 index 1f64573e2356..000000000000 --- a/docs/CROWDIN/cs/Configuration/Hardware/index.md +++ /dev/null @@ -1,27 +0,0 @@ -# Hardware-Configuration - -## Konfigurace - -## Zdroj glykémií - -- [BG Source](../BG-Source.md) -- [xDrip+ Settings](../xDrip.md) -- [Dexcom G6 hints](../Dexcom.md) -- [Smoothing blood glucose data](../../Usage/Smoothing-Blood-Glucose-Data-in-xDrip.md) - -## Pumps - -- [Dana-R pump](../DanaR-Insulin-Pump.md) -- [Dana-RS pump](../DanaRS-Insulin-Pump.md) -- [Accu-Chek Combo pump](../Accu-Chek-Combo-Pump.md) -- [Accu-Chek Insight pump](../Accu-Chek-Insight-Pump.md) -- [Medtronic pump](../MedtronicPump.md) - -## Telefony - -- [Jelly Pro Settings](../../Usage/jelly.md) -- [Huawei Settings](../../Usage/huawei.md) - -## Chytré hodinky - -- [Watchfaces](../Watchfaces.md) diff --git a/docs/CROWDIN/cs/Getting-Started/ClosedLoop.md b/docs/CROWDIN/cs/Getting-Started/ClosedLoop.md deleted file mode 100644 index f0be9c1cf453..000000000000 --- a/docs/CROWDIN/cs/Getting-Started/ClosedLoop.md +++ /dev/null @@ -1,55 +0,0 @@ -# Co je systém uzavřené smyčky? - -![AAPS je jako autopilot](../images/autopilot.png) - -Systém uzavřené smyčky APS využívá kombinaci různých komponent, aby vám usnadnil management diabetu. In her great book [Automated Insulin Delivery](https://www.artificialpancreasbook.com/) Dana M. Lewis, one of the founders of the open source closed loop movement, calls it an ["autopilot for your diabetes"](https://www.artificialpancreasbook.com/3.-getting-started-with-your-aps). Co to však znamená? - -**Autopilot in an aircraft** - -Autopilot nedělá úplně všechno a neumožňuje skutečnému pilotovi, abys celý let prospal. Pouze mu pomáhá při jeho práci. Ulevuje mu od zátěže způsobené nutností neustále monitorovat funkce letadla a sledovat letovou hladinu. Pilot se tak může soustředit na sledování letového prostoru a kontrolu funkcí autopilota. - -Autopilot dostává signály od mnoha různých senzorů, počítač je následně vyhodnocuje společně se zadanými specifikacemi od pilota a nakonec provede potřebné korekce. Pilot se tak již nemusí zabývat neustálými drobnými úpravami. - -**Closed Loop System** - -Totéž platí pro systém uzavřené smyčky APS. Nedělá úplně všechno, stále se musíte o svůj diabetes starat vy sami. Systém uzavřené smyčky využívá data ze senzorů CGM/FGM v kombinaci s vašimi specifikacemi, jako jsou bazální dávky, citlivost na inzulin a inzulino-sacharidový poměr. Na základě toho pak vypočítává návrhy, jak upravit léčbu, a provádí tyto neustále drobné změny tak, aby udržel vaší glykémii v cílovém rozmezí a vy jste s nimi neměli tolik práce. Získáte tak více času na život „mimo diabetes“. - -Stejně jako byste nenastoupili do letadla, které by řídil pouze autopilot bez dohledu živého pilota, tak i systém uzavřené smyčky vám sice usnadní management vašeho diabetu, ale stále vyžaduje vaši pozornost a podporu! **Even with a closed loop you can't just forget your diabetes!** - -Stejně jako autopilot závisí na hodnotách ze senzorů i specifikacích pilota, tak i systém uzavřené smyčky potřebuje správné údaje jako bazály, ISF a sacharidový poměr, aby vám mohl dobře pomáhat. - -## Open source systémy uzavřené smyčky APS - -V současnosti jsou k dispozici tři hlavní oper source systémy uzavřené smyčky: - -### AndroidAPS (AAPS) - -AAPS is described in detail in [this documentation](./WhatisAndroidAPS.html). Pro výpočty a ovládání inzulinové pumpy využívá smartphone se systémem Android. It is in strong collaboration with OpenAPS (i.e. they share algorithms). - -Compatible [pumps](../Hardware/pumps.md) are: - -- [DanaR](../Configuration/DanaR-Insulin-Pump.md) / [DanaRS & Dana-i](../Configuration/DanaRS-Insulin-Pump.html) -- [Accu-Chek Combo](../Configuration/Accu-Chek-Combo-Pump.md) -- [Accu-Chek Insight](../Configuration/Accu-Chek-Insight-Pump.md) -- [Diaconn G8](../Configuration/DiaconnG8.md) -- [Omnipod DASH](../Configuration/OmnipodDASH.md) -- [Omnipod Eros](../Configuration/OmnipodEros.md) -- some old [Medtronic pumps](../Configuration/MedtronicPump.md) - -### OpenAPS - -[OpenAPS](https://openaps.readthedocs.io) was the first Open Source Closed Loop System. Používá malý počítač, jako je Raspberry Pi nebo Intel Edison. - -Kompatibilní pumpy jsou: - -- some old Medtronic pumps - -### Loop pro iOS - -[Loop for iOS](https://loopkit.github.io/loopdocs/) is the Open Source Closed Loop System to be used with Apple iPhones. - -Kompatibilní pumpy jsou: - -- Omnipod DASH -- Omnipod Eros -- some old Medtronic pumps diff --git a/docs/CROWDIN/cs/Getting-Started/GlossaryTest.md b/docs/CROWDIN/cs/Getting-Started/GlossaryTest.md deleted file mode 100644 index 9324a1bdc871..000000000000 --- a/docs/CROWDIN/cs/Getting-Started/GlossaryTest.md +++ /dev/null @@ -1,391 +0,0 @@ -# Slovníček - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
TermínPopisviz takédalší podrobnosti @
AAPSAndroidAPS - systém umělé slinivky  
AMAAdvanced Meal Assist - pokročilý algoritmus pro práci se sacharidyMA / SMBWiki - AMA
Android autoZobrazuje notifikace z AAPS na palubním počítači a centrálním displeji kompatibilního vozu Wiki - android auto
APKSoftwarový instalační soubor (balíček aplikace pro Android) Wiki - Sestavení APK
AutosensVýpočet změn citlivosti na inzulin v důsledku cvičení, hormonů atd. DIABETTECH - Autosens
AzurePlatforma pro cloud computing umožňující hostování dat z NightscoutuHeroku / NightscoutAzure
BATStavový indikátor nízké baterie na domovské obrazovceCAN / RES / SENNastavení
Snímky obrazovky
BGGlykémie (blood glucose)  
BGIBlood Glucose Impact - do jaké míry „by měla“ glykémie stoupat nebo klesat pouze na základě aktivity inzulinu  
Zdroj glykémie (BG source)Odkud pocházejí hodnoty vaší glykémie?CGM / FGMWiki - Zdroj glykémie
Blukon NightreaderVysílač s technologií bluetooth určený k tomu, aby senzor Freestyle Libre fungoval jako CGMBlueReader / MiaoMiaoAmbrosia Blukon Nightreader
BRbazál (basal rate)  
CAGEcanula age - displayed in Nightscout if information was entered in actions tab / menu tab or through AAPS actions tab 'prime'Nightscout 
CANstatus light overdue canula change on homescreenBAT / RES / SENNastavení
Snímky obrazovky
CGMcontinuous glucose monitor  
Uzavřená smyčka (Closed Loop)closed-loop systems make automatic adjustments to basal delivery, without needing user-approval, based on an algorithmOpen loopWiki closed loop
COBcarbs on board  
DIAduration of insulin action Wiki insulin types
DIABETTECH - DIA
DSTdaylight savings time Wiki DST
eCarbs"extended carbs" - carbs split up over serveral hours (i.e. lot of fat/protein)
extended boluses you might know from regular pump therapy do not make much sense when looping		SMBWiki - eCarbs
eCarbs use case
FGMflash glucose monitor (Freestyle Libre) Wiki - Zdroj glykémie
gitversion-control system for tracking changes in computer files and coordinating work on those files
-> neccessary for APK updates		 Wiki - update APK
Githubweb-based hosting service for version control using Git
-> storage of source code		 Github AndroidAPS
Glimpapp to collect values from Freestyle Libre Nightscout with Glimp
HerokuPlatforma pro cloud computing umožňující hostování dat z NightscoutuAzure / NightscoutHeroku
IC (or I:C)insulin to carb ratio (How many carbs are covered by one unit of insulin?)  
IOBinsulin on board - insulin active in your body  
ISFinsulin sensitivity factor - the expected decrease in BG as a result of one unit of insulin  
LGSLow Glucose Suspend
AAPS will reduce basal if blood glucose is dropping. But if blood glucose is rising then it will only increase basal if the IOB is negative (from a previous LGS), otherwise basal rates will remain the same as your selected profile. You may temporarily experience spikes following treated hypos without the ability to increase basal on the rebound.		objective 6 
LineageOSfree and open-source operating system for smartphones etc.
alternative OS for smartphones not running Android 8.1 (Oreo)
(when using Accu-Chek Combo)		 Wiki - Combo pump
Log filesrecord of all AAPS actions (useful for trubbleshooting and debugging) Wiki - log files
maxIOBsafety feature - maximum total IOB AAPS can't go over Wiki - maxIOB
Wiki - SMB
MiaoMiaoVysílač s technologií bluetooth určený k tomu, aby senzor Freestyle Libre fungoval jako CGMBlueReader / Blukon NightreaderMiaoMiao
min_5m_carbimpactsaftey feature - default carb decay at times when carb absorption can’t be dynamically worked out based on your bloods reactions Wiki - config builder
Nightscoutopen source project to access and report CGM dataNightscout ReporterNightscout
NS Clientpart of AAPS to connect to your Nightscout site Wiki - NS Client
Nightscout ReporterTool from fellow looper to generate PDFs reports from Nightscout dataNightscoutNightscout Reporter
NS Reporter @ Facebook
Cílelearning program within AAPS guiding you step by step from open to closed loop Wiki - objectives
OpenAPSopen artificial pancreas system
APS run on small computers (i.e. Raspberry Pie)
AAPS uses some of the OpenAPS features		 OpenAPS docs
Otevřená smyčkasystem will suggest recommended adjustments which have to be performed manually on the pumpUzavřená smyčka (Closed Loop)Wiki - config builder
Oref0 / Oref1sensitivity detection
"reference design implementation version 0/1" - the key algorithm behind OpenAPS		 Wiki - sensitivity detection
Peak timetime of maximum effect of insulin given Wiki - config builder
PHpump history (entry in treatments tab) Screenshots
Predikcepreditions for BG in the future based on different calculations Wiki - predition lines
Profilbasic treatment settings (basal rate, DIA, IC, ISF, BG target)
can be defined locally or through Nightscout		NightscoutWiki - profile
Přepínání profilu(temporary) change of profile used or percentual increase/decrease Wiki - profile switch
RESstatus light overdue reservoir change on homescreenBAT / CAN / SENNastavení
Snímky obrazovky
RileyLinkopen source hardware device to bridge Bluetooth Low Energy (BLE) to 916MHz wireless communication (used for old Medtronic pumps)OpenAPS 
SAGEsensor age - displayed in Nightscout if information was entered in the actions tab / menuNightscout 
SENstatus light sensor change on homescreenBAT / CAN / RESNastavení
Snímky obrazovky
Sensivity detectionVýpočet změn citlivosti na inzulin v důsledku cvičení, hormonů atd. DIABETTECH - Autosens
Sensor noiseunstable CGM readings leading to "jumping" values Wiki - sensor noise
SMBsuper micro bolus
advanced feature for faster BG adjustment		UAMWiki - SMB
Super bolusshift of basal to bolus insulin for faster BG adjustment John Walsh - The Super Bolus
TBBtotal base basal (sum of basal rate within 24 hours)  
TBRtemporary basal rate  
TDDtotal daily dose (bolus + basal per day)  
TTtemporary target
temporary increase/decrease of BG target (range)		 Wiki - temp targets
UAMunannounced meals - detection of significant increase in glucose levels due to meals, adrenaline or other influences and attempt to adjust this with SMBSMBWiki - SMB
Virtual pumpoption to try AAPS functions or for PWD using a pump model with no AndroidAPS driver for loopingOtevřená smyčka 
PozadíAndroidAPS background imagesee phones page
xDrip / xDrip+open source software to read CGM systems xDrip+
xDrip
Zero-temptemporary basal rate with 0% (no basal insulin delivery)  
See also https://openaps.readthedocs.io/en/latest/docs/Resources/glossary.html
diff --git a/docs/CROWDIN/cs/Getting-Started/Safety-first.md b/docs/CROWDIN/cs/Getting-Started/Safety-first.md deleted file mode 100644 index 083472132e49..000000000000 --- a/docs/CROWDIN/cs/Getting-Started/Safety-first.md +++ /dev/null @@ -1,41 +0,0 @@ -# Bezpečnost především - -**When you decide to build your own artificial pancreas, it's always important to think about security and safety, and to understand the impact of all your actions** - -## Obecné - -- AAPS is a just a tool to help you manage diabetes, it is not a fully automated system you can install and forget! -- Do not assume that AAPS will never make mistakes. Toto zařízení přebírá kontrolu nad vaším podáváním inzulinu: Vždy jej kontrolujte, snažte se porozumět tomu, jak funguje a naučte se interpretovat jeho akce. -- Remember that, once paired, the phone can instruct the pump to do anything. Only use this phone for AAPS and, if being used by a child, essential communications. Neinstalujte nepotřebné aplikace nebo hry (!!!), které by mohly do vašeho telefonu zavléci malware, jako jsou trojské koně, viry nebo boty, které by mohly zasahovat do vašeho systému. -- Install all security updates provided by your phone manufacturer and Google. -- You might also need to change your diabetes habits as you change your therapy by using a closed loop system. Např. some people report, they need less hypo treatments as AAPS has already reduced insulin. - -## SMS komunikátor - -- AAPS umožňuje vládat telefon vašeho dítěte na dálku prostřednictvím textových zpráv. Pokud povolíte SMS komunikátor, vždy pamatujte na to, že telefon nastavený k vydávání vzdálených příkazů, může být ukraden. Proto vždy chraňte telefon alespoň pomocí kódu PIN. -- AAPS vás bude textovou zprávou informovat, že byl poslaný příkaz (bolus, změna profilu apod.) úspěšně vykonán. Je proto vhodné nastavit, aby byly potvrzovací zprávy odesílány alespoň na dvě různá telefonní čísla pro případ, že by došlo ke zcizení jednoho z rodičovských telefonů. - -(Safety-first-aaps-can-also-be-used-by-blind-people)= -## AAPS can also be used by blind people - -On Android devices TalkBack is part of the operating system. It is a program for screen orientation via voice output. With TalkBack you can operate your smartphone as well as AAPS blind. - -We users create the AAPS app ourselves with Android Studio. Many use Microsoft Windows for this purpose, where there is the Screenreader analogous to TalkBack. Since Android Studio is a Java application, the "Java Access Bridge" component must be enabled in the Control Panel. Otherwise, the screen reader of the PC will not speak in Android Studio. - -To do this, please proceed as follows: - -- Press WINDOWSTASTE and enter "Control Panel" in the search field, open with Enter. It opens: "All Control Panel Items". -- Press the letter C to get to "Center for Ease of Use", open with Enter. -- Then open "Use computer without a screen" with Enter. -- There, at the bottom, you will find the checkbox "Enable Java Access Bridge", select it. -- Done, just close the window! The screen reader should work now. - -```{note} -**IMPORTANT SAFETY NOTICE** - -The foundation of AAPS safety features discussed in this documentation is built on the safety features of the hardware used to build your system. Je zásadně důležité, abyste používali pouze testované, plně funkční a pro uzavřenou smyčku schválené inzulinové pumpy a CGM. Hardwarové nebo softwarové úpravy těchto komponent mohou způsobit neočekávané dávkování inzulínu, což může znamenat pro uživatele významné riziko. If you find or get offered broken, modified or self-made insulin pumps or CGM receivers, *do not use* these for creating an AAPS system. - -Kromě toho je stejně důležité používat pouze originální spotřební materiál, jako jsou sety a zásobníky, schválené výrobcem pro použití s vaší pumpou nebo CGM. Použití nevyzkoušeného nebo upraveného spotřebního materiálu může způsobit nepřesnosti a chyby při dodávce inzulínu. Inzulín je velmi nebezpečný, když není dávkovaný správně – prosím, nehazardujte se svým životem tím, že budete upravovat spotřební materiál. - -V neposlední řadě nesmíte užívat SGLT-2 inhibitory (glifloziny), které snižují hadinu cukru v krvi. Kombinace se systémem, která snižuje bazální hodnoty ke zvýšení glykémie je zvláště nebezpečná, protože v důsledku gliflozinu tento nárůst glykémie nemusí nastat a může dojít k nebezpečnému stavu nedostatku inzulínu. -``` diff --git a/docs/CROWDIN/cs/Getting-Started/Sample-Setup.md b/docs/CROWDIN/cs/Getting-Started/Sample-Setup.md deleted file mode 100644 index 085cbdd366bd..000000000000 --- a/docs/CROWDIN/cs/Getting-Started/Sample-Setup.md +++ /dev/null @@ -1,151 +0,0 @@ -# Ukázková instalace: Samsung S7, DanaRS, Dexcom G6 a Sony Smartwatch - -![Ukázková instalace](../images/SampleSetup.png) - -## Popis - -V tomto případě je k ovládání smyčky použit telefon Samsung Galaxy S7. Upravená aplikace Dexcom přijímá data ze senzoru Dexcom G6. AndroidAPS slouží k ovládání inzulínové pumpy Dana R od korejského výrobce SOOIL přes bluetooth. Další zařízení nejsou vyžadována. - -Protože Dexcom aplikace nabízí pouze omezené možnosti alarmů, použijeme open source aplikaci xDrip+, která umí nastavit kromě alarmů vysoké a nízké glykémie také další alarmy přizpůsobené individuálním požadavkům. - -Hodinky s WearOS lze použít (v tomto příkladu Sony Smartwatch 3 (SWR50)), volitelně k zobrazení glykémie a hodnot AndroidAPS na vašem zápěstí. Hodinky lze dokonce použít k ovládání AndroidAPS (např. diskrétní poslání bolusu k jídlu). - -Systém pracuje offline. To znamená, že pro ovládání není třeba datové připojení telefonu k internetu. - -Nicméně, data se automaticky nahrají do Nightscoutu, jakmile je navázáno datové připojení. Nahráním dat do Nightscoutu získáte kompletní výkazy, které využijete například při návštěvě lékaře nebo můžete sdílet aktuální hodnoty s členy rodiny. Data do Nightscoutu (abyste mohli využívat různé Výkazy) lze také pouze prostřednictvím (předdefinovaného) Wi-Fi připojení. - -## Požadované součásti - -1. Samsung Galaxy S7 - - * Alternativy: viz [seznam testovaných telefonů a hodinek](https://docs.google.com/spreadsheets/d/1gZAsN6f0gv6tkgy9EBsYl0BQNhna0RDqA9QGycAqCQc/edit) pro AndroidAPS - -2. [DanaRS](http://www.sooil.com/eng/product/) - - * Alternativy: - * [Accu-Chek Combo](../Configuration/Accu-Chek-Combo-Pump.md) - * [Accu-Chek Insight](../Configuration/Accu-Chek-Insight-Pump.md) - * [DanaR](../Configuration/DanaR-Insulin-Pump.md) - * [Některé starší pumpy od Medtronic (je potřeba RileyLink/Gnarl hardware, mobilní telefon s Androidem a bluetooth s nízkou spotřebou / BLE-chipset)](../Configuration/MedtronicPump.md) - * Další pumpy mohou být k dispozici v budoucnu, podrobnosti viz [budoucí možné ovladače pumpy ](Future-possible-Pump-Drivers.md). - -3. [Dexcom G6](https://dexcom.com) - - * Alternatives: see list of possible [BG sources](../Configuration/BG-Source.md) - -4. Volitelné: Sony Smartwatch 3 (SWR50) - - * Alternativy: Pro AndroidAPS (OS musí být Android Wear) by měly všechny [ hodinky s Google Wear OS](https://wearos.google.com/intl/de_de/#find-your-watch) fungovat bez problémů. Další info najdete v [seznam testovaných telefonů a hodinek](https://docs.google.com/spreadsheets/d/1gZAsN6f0gv6tkgy9EBsYl0BQNhna0RDqA9QGycAqCQc/edit) - -## Příprava Nightscoutu - -Podrobné [Nastavení Nightscoutu](../Installing-AndroidAPS/Nightscout.md) - -## Nastavení počítače - -Abyste byli schopni vytvořit aplikaci pro Android z volně dostupných otevřených zdrojových kódu AAPS, potřebujete Android Studio nainstalované na svém počítači nebo notebooku (Windows, Mac, Linux). Podrobné instrukce naleznete v části [Vytvoření APK](../Installing-AndroidAPS/Building-APK.md). - -Při instalaci Android Studia buďte trpěliví, software potřebuje stáhnout spoustu dodatečných dat (balíčků) po nainstalovaní do počítače. - -## Nastavení telefonu - -![Chytrý telefon](../images/SampleSetupSmartphone.png) - -### Zkontrolujte firmware telefonu - -* Nabídka > Nastavení> Info o telefonu > Info o softwaru: Je potřeba alespoň „Android-verze 8.0“ (úspěšně testované do Android verze 8.0.0 Oreo - Samsung Experience verze 9.0) -* Chcete-li aktualizovat firmware: Nabídka > Nastavení > Aktualizace softwaru - -### Povolit instalaci aplikací z neznámých zdrojů - -Nabídka > Nastavení> Zabezpečení > Neznámé zdroje > přepněte doprava (= aktivní) - -Z bezpečnostních důvodů by toto nastavení mělo být nastaveno zpět na neaktivní po dokončení instalace všech aplikací, které jsou popsané zde. - -### Zapněte Bluetooth - -1. Nabídka > Nastavení > Připojení > Bluetooth > přepnout doprava (= aktivní) -2. Nabídka > Nastavení > Připojení > Umístění > přepnout doprava (= aktivní) - -Služby určování polohy (dále jen „GPS“) musí být aktivovány, aby Bluetooth správně fungovalo. - -### Nainstalujte aplikaci Dexcom (upravená verze) - -![Upravená aplikace Dexcom](../images/SampleSetupDexApp.png) - -Původní aplikace Dexcom z obchodu Google Play nebude fungovat, protože nevysílá hodnoty do jiné aplikace. Proto je vyžadována verze mírně upravená komunitou. Pouze tato upravená Dexcom aplikace může komunikovat s AAPS. Navíc lze použít upravenou Dexcom aplikaci se všemi Android telefony a ne jen s těmi v [seznamu kompatibilních zařízení s Dexcom](https://www.dexcom.com/dexcom-international-compatibility). - -To do this perform the following steps on your smartphone: - -1. Je-li původní Dexcom aplikace již nainstalována: - * Zastavte senzor - * Odinstalujte aplikaci přes Nabídka > Nastavení > Aplikace > Dexcom G6 Mobile > odinstalovat -2. Download and install the [BYODA Dexcom ap](../Hardware/DexcomG6.md#if-using-g6-with-build-your-own-dexcom-app) -3. Start modified Dexcom G6 app, activate/calibrate the sensor according to the given instructions and wait until the warm-up phase is finished. -4. Once the modified Dexcom app shows actual glucose value, setup the warnings (hamburger menu on top left side of the screen) as follows: - * Urgent low `55mg/dl` / `3.1mmol/l` (cannot be disabled) - * Low `OFF` - * High `OFF` - * Rise rate `OFF` - * Fall rate `OFF` - * Signal loss `OFF` - -## Nainstalujte AndroidAPS - -1. Follow the instructions to [build the APK](../Installing-AndroidAPS/Building-APK.md#generate-signed-apk) -2. [Transfer](../Installing-AndroidAPS/Building-APK.md#transfer-apk-to-smartphone) the generated APK to your phone -3. [Nakonfigurujte AndroidAPS ](../Configuration/Config-Builder.md) podle svých potřeb pomocí průvodce nastavením nebo ručně -4. V tomto vzorovém nastavení jsme (mimo jiné) použili - -* BG source: `Dexcom G6 App (patched)` -- click cock-wheel and activate `Upload BG data to NS` and `Send BG data to xDrip+` (see [BG source](../Configuration/BG-Source.md)) - -![G5 Settings](../images/SampleSetupG5Settings.png) - -* NS Client activated (see [Nightscout setup](../Installing-AndroidAPS/Nightscout.md)) - -## Nainstalujte xDrip+ - -xDrip+ is another mature open source app that offers countless possibilities. In this setup, contrary to what the developers first wrote the app for, xDrip+ is not used to collect glucose data from the Dexcom G6, but only to output alarms and to display the current glucose value including the curve on the Android home screen in the widget. With xDrip+ the alarms can be set much more individually than with the Dexcom software, AAPS or Nightscout (no limitation in the selection of sounds, different alarms depending on day/night time etc.). - -1. Stáhněte si nejnovější stabilní verzi aplikace xDrip+ (APK) do svého telefonu - ne verze z Google Play! -2. Nainstalujte xDrip+ ze staženého souboru APK. -3. Spusťte xDrip + a proveďte následující nastavení (hamburger menu vlevo nahoře) - * Nastavení > Výstrahy a Upozornění > Seznam výstrah glykémií > Vytvořte výstrahy (vysoké a nízké) podle svých potřeb. - * Vytvořenou výstrahu lze změnit tak, že ji stisknete a dlouze přidržíte. - * Nastavení > Výstrahy a Upozornění > Výstrahy kalibrace: vypnout (Připomínáno prostřednictvím upravené Dexcom aplikace) - * Nastavení > Zdroj dat > 640G/EverSense - * Nastavení > Komunikace mezi aplikacemi > Přijímat kalibrace > `ZAP` - * Menu > Spustit senzor (je pouze „pro forma“ a nemá nic společného s běžícím senzorem G6. (To je nezbytné, jinak se bude pravidelně objevovat chybová zpráva.) - -For more information about xDrip+, see here [BG source page](../Configuration/BG-Source.md). - -### Příklad nastavení výstrahy - -The "Urgent low alarm" (below 55 mg/dl resp. 3,1 mmol) is a standard alarm from the modified Dexcom app that cannot be disabled. - -![xDrip alarms](../images/SampleSetupxDripWarning.png) - -Tip for meetings / church visits / cinema etc..: - -If "Do not disturb" mode is activated in the Samsung Galaxy S7 (Menu > Settings > Sounds and vibration > Do not disturb: slider to right side (= active)), the phone only vibrates during urgent low alarm and does not issue an acoustic warning. For the other alarms set up via xDrip+ you can select whether the silent mode should be ignored (acoustic sound played) or not. - -## Zakažte možnost pro úsporu energie - -On your Samsung Galaxy S7 go to Menu > Settings > Device Maintenance > Battery > Unmonitored Apps > + Add apps: Select the apps AndroidAPS, Dexcom G6 Mobile, xDrip+ and Android Wear (if smartwatch is used) one after the other - -## Volitelné: Sony Smartwatch 3 (SWR50) - -With an Android Wear smartwatch life with diabetes can be made even more inconspicuous. The watch can be used to display the current glucose level, the status of the loop etc. on the wrist. Hodinky lze dokonce použít k ovládání AndroidAPS (např. diskrétní poslání bolusu k jídlu). To do this, double tap the CGM value of the AAPSv2 watchface. The SWR50 usually runs for a full day until the battery needs to be recharged (same charger as the Samsung Galaxy S7: microUSB). - -![Chytré hodinky](../images/SampleSetupSmartwatch.png) - -Details about the information displayed on the watchface can be found [here](../Configuration/Watchfaces.md). - -* Nainstalujte si aplikaci „Wear OS" do svého smartphonu přes Google Play a připojte hodinky podle uvedených pokynů. -* V AAPS zvolte hamburger menu (levý horní roh) > Konfigurace > Obecné (v dolní části seznamu) > Wear > Aktivovat na levé straně, klepněte na ozubené kolečko > Nastavení hodinek a aktivujte možnost `Řízení z hodinek Wear` -* Na hodinkách: chcete-li změnit ciferník, dlouze podržte displej hodinek a vyberte `AAPSv2` -* V případě potřeby restartujte obě zařízení. - -## Nastavení pumpy - -see [Dana RS pump](../Configuration/DanaRS-Insulin-Pump.md) \ No newline at end of file diff --git a/docs/CROWDIN/cs/Getting-Started/WhatisAndroidAPS.md b/docs/CROWDIN/cs/Getting-Started/WhatisAndroidAPS.md deleted file mode 100644 index b8873ab8f29a..000000000000 --- a/docs/CROWDIN/cs/Getting-Started/WhatisAndroidAPS.md +++ /dev/null @@ -1,39 +0,0 @@ -# What is a closed loop system with AAPS? - -AAPS is an app that acts as an artificial pancreas system (APS) on an Android smartphone. Co je systém umělé slinivky? Jedná se o softwarový program, jehož účelem je simulovat chování zdravé slinivky: automaticky udržovat hladinu krevního cukru v optimálním rozmezí. - -APS to sice nedokáže dělat tak dobře, jako skutečná slinivka, avšak dokáže lidem s diabetem 1 typu usnadnit zvládání nemoci, a to za použití zařízení, která jsou běžně dostupná a softwaru, který je jednoduchý a bezpečný. Those devices include a continuous glucose monitor (CGM) to tell AAPS about your blood sugar levels and an insulin pump which AAPS controls to deliver appropriate doses of insulin. Aplikace komunikuje s těmito zařízeními prostřednictvím technologie bluetooth. K výpočtu správného množství inzulínu využívá speciální algoritmus, neboli sadu pravidel, vyvinutý pro jiný systém umělé slinivky zvaný OpenAPS, který na celém světě používají tisíce lidí a eviduje miliony hodin používání. - -A note of caution: AAPS is not regulated by any medical authority in any country. Using AAPS is essentially carrying out a medical experiment on yourself. Vytvoření tohoto systému vyžaduje odhodlání a technické znalosti. Pokud na začátku nemáte technické znalosti, na konci je mít budete. Veškeré potřebné informace naleznete v této dokumentaci, jinde na internetu nebo je získáte od ostatních uživatelů -- můžete se jich zeptat prostřednictvím skupin na Facebooku nebo v jiných diskuzních fórech. Many people have successfully built AAPS and are now using it entirely safely, but it is essential that every user: - -- Builds the system themselves so that they thoroughly understand how it works -- Adjusts its individual dosage algorithm with his or her diabetes team to work nearly perfect -- Maintains and monitors the system to ensure it is working properly - -```{note} -**Disclaimer and Warning** - -- All information, thought, and code described here is intended for informational and educational purposes only. Nightscout se nesnaží v současné době dodržovat zákon HIPAA. Use Nightscout and AAPS at your own risk, and do not use the information or code to make medical decisions. -- Use of code from github.com is without warranty or formal support of any kind. Přečtěte licenci z této repozitoře pro další podrobnosti. -- All product and company names, trademarks, servicemarks, registered trademarks, and registered servicemarks are the property of their respective holders. Jejich použití je pro informační účely a neznamená žádné spojení. - -Please note - this project has no association with and is not endorsed by: [SOOIL](http://www.sooil.com/eng/), [Dexcom](https://www.dexcom.com/), [Accu-Chek, Roche Diabetes Care](https://www.accu-chek.com/), [Insulet](https://www.insulet.com/) or [Medtronic](https://www.medtronic.com/). -``` - -Jste-li připraveni přijmout tuto výzvu, čtěte dál. - -## Primary goals behind AAPS - -- An app with safety built in. To read about the safety features of the algorithms, known as oref0 and oref1, click here () -- An all-in-one app for managing type 1 diabetes with an artificial pancreas and Nightscout -- An app to which users can easily add or remove modules as needed -- An app with different versions for specific locations and languages. -- An app which can be used in open- and closed-loop mode -- An app that is totally transparent: users can input parameters, see results, and make the final decision -- An app which is independent of particular pump drivers and contains a "virtual pump" so users can safely experiment before using it on themselves -- An app closely integrated with Nightscout -- An app in which the user is in control of safety constraints - -## Jak začít - -Veškerý tento obsah je samozřejmě velmi důležitý, ale může být na začátku docela matoucí. A good orientation is given by the [Module Overview](../Module/module.md) and the [Objectives](../Usage/Objectives.html). diff --git a/docs/CROWDIN/cs/Hardware/DexcomG4.md b/docs/CROWDIN/cs/Hardware/DexcomG4.md deleted file mode 100644 index e090363e23dd..000000000000 --- a/docs/CROWDIN/cs/Hardware/DexcomG4.md +++ /dev/null @@ -1,6 +0,0 @@ -# Dexcom G4 - -## Pokud používáte G4 s OTG kabelem („tradiční“ Nightscout) -- Pokud jste tak ještě neučinili, stáhněte si z obchodu Play aplikaci Nightscout Uploader a postupujte podle pokynů na stránce [Nightscout](https://nightscout.github.io/). -- In AAPS Preferences enter your Nightscout website and API secret. -- Select NSClient in ConfigBuilder (setting in AAPS). diff --git a/docs/CROWDIN/cs/Hardware/Smartwatch.md b/docs/CROWDIN/cs/Hardware/Smartwatch.md deleted file mode 100644 index 4aff98d3c784..000000000000 --- a/docs/CROWDIN/cs/Hardware/Smartwatch.md +++ /dev/null @@ -1,10 +0,0 @@ -# Chytré hodinky - -Chytré hodinky jsou volitelné, ale pro některé uživatele velmi užitečné. More details are here: - -- [List of tested phones and smartwatches](../Getting-Started/Phones.md) -- [Watchfaces Wear OS](../Configuration/Watchfaces.md) -- [Troubleshooting Sony Smartwatch SW 3](../Usage/SonySW3.md) - -## Instructions for Building the AAPS Wear APK for Wear OS -https://androidaps.readthedocs.io/en/latest/remote-control.html#building-the-aaps-wear-apk diff --git a/docs/CROWDIN/cs/Installing-AndroidAPS/Building-APK.md b/docs/CROWDIN/cs/Installing-AndroidAPS/Building-APK.md deleted file mode 100644 index 37dad334729f..000000000000 --- a/docs/CROWDIN/cs/Installing-AndroidAPS/Building-APK.md +++ /dev/null @@ -1,369 +0,0 @@ -# Sestavení APK - -## Vyrobte si místo stažení - -**AAPS is not available as download due to regulation for medical devices. It is legal to build the app for your own use, but you must not give a copy to others! Další informace naleznete v části [Časté dotazy](../Getting-Started/FAQ.md).** - -## Důležité poznámky - -* Please use **[Android Studio Giraffe" (2022.3.1)](https://developer.android.com/studio/)** or newer to build the apk. -* [Windows 32-bit systems](troubleshooting_androidstudio-unable-to-start-daemon-process) are not supported by Android Studio - -(Building-APK-recommended-specification-of-computer-for-building-apk-file)= - -## Doporučená specifikace počítače pro vytváření souboru apk - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
OS (Only 64 bit)Windows 8 nebo novějšíMac OS 10.14 nebo novějšíJakýkoli Linux, který podporuje Gnome, KDE nebo Unity DE;  GNU C knihovnu 2.31 nebo novější

CPU (Only 64 bit)

CPU s architekturou x86_64; 2. generace Intel Core nebo novější, nebo AMD CPU s podporou
Windows Hypervisor		Procesory založené na ARM nebo Intel Core 2. generace nebo novější s podporou
Hypervisor.Framework		CPU s architekturou x86_64; Intel Core 2. generace nebo novější nebo processor AMD s podporou AMD Virtualization (AMD-V) a SSSE3

RAM

min. 8 GB

Pevný disk

Alespoň 30 GB volného místa. Je doporučeno SSD.

Rozlišení

Minimálně 1280 × 800

Internet

Širokopásmové připojení

- -Please keep in mind that both **64 bit CPU and 64 bit OS are mandatory condition.** If your system DOES NOT meet this condition, you have to change affected hardware or software or the whole system. **It is strongly recommended to use SSD (Solid State Disk) instead of HDD (Hard Disk Drive) because it will take less time when you are building the APS installation apk file.** Recommended is just recommended and it is not a mandatory. However, you may still use a HDD when you are building apk file but note that the building process can take a long time to complete, although once started, you can leave it running unattended. - -* * * - -### Tento článek je rozdělený do dvou částí. - -* In the overview part there is an explanation on what steps are necessary to build the APK file. -* In the step by step walkthrough part you will find the screenshots of a concrete installation. Because the versions of Android Studio - the software development environment which we will use to build the APK - will change very quickly this will be not identical to your installation but it should give you a good starting point. Android Studio also runs on Windows, Mac OS X and Linux and there might be small differences in some aspects between each platform. If you find that something important is wrong or missing, please inform the facebook group "AAPS users" or in the Discord chat [Android APS](https://discord.gg/4fQUWHZ4Mw) so that we can have a look at this. - -## Přehled - -In general, the steps necessary to build the APK file: - -1. [Nainstalujte git](../Installing-AndroidAPS/git-install.md) -2. [Instalace Android Studio](Building-APK-install-android-studio) -3. [Nastavte v předvolbách Android Studio cestu ke gitu](Building-APK-set-git-path-in-preferences) -4. [Download AAPS code](Building-APK-download-AAPS-code) -5. [Stáhněte Android SDK](Building-APK-download-android-sdk) -6. [Build the app](Building-APK-generate-signed-apk) (generate signed apk) -7. [Nahrajte aplikaci do mobilu](Building-APK-transfer-apk-to-smartphone) -8. [Možnost „Identify receiver“ při používání xDripu+](xdrip-identify-receiver) - -## Průvodce krok za krokem - -Detailed description of the steps necessary to build the APK file. - -## Nainstalujte git (pokud ho ještě nemáte) - -Follow the manual on the [git installation page](../Installing-AndroidAPS/git-install.md). - -(Building-APK-install-android-studio)= - -## Instalace Android Studio - -The following screenshots have been taken from Android Studio Version Arctic Fox | 2020.3.1. Screens can change in future versions of Android Studio. But you should be able to find your way through. [Help from the community](../Where-To-Go-For-Help/Connect-with-other-users.md) is provided. - -One of the most important things when installing Android Studio: **Be patient!** During installation and setup Android Studio is downloading a lot of stuff which will take its time. - -Download [Android Studio from here](https://developer.android.com/studio/install.html) and install it on your computer. - -On first start you will find the setup wizard: - -Select "Do not import settings" as you have not used it before. - -![Do not import settings](../images/studioSetup/01_ImportSettings.png) - -Decide whether you want to share data with Google or not. - -![Share data with Google](../images/studioSetup/02_DataSharing.png) - -On the following screen click "Next". - -![Welcome screen](../images/studioSetup/03_Welcome.png) - -Select "Standard" installation and click "Next". - -![Standard installation](../images/studioSetup/04_InstallType.png) - -Select the theme for the user interface you like. (In this manual we used "Light".) Then click "Next". - -> ***Note:*** This is just the color scheme. You can select whatever you like (i.e. "Darcula" for dark mode). This selection has no influence on building the APK but the following screenshots might look different. - -![UI color scheme](../images/studioSetup/05_UITheme.png) - -Click "Next" on the "Verify Settings" dialog. - -![Verify settings](../images/studioSetup/06_Overview.png) - -Click on all three license agreement parts and select "Agree". When you have agreed to all, the "Finish" button will be enabled and you can "Finish". - - ![Agree license agreements](../images/studioSetup/07_LicenseAgreement.png) - - -Wait while Android Studio downloads additional components and be patient. Once everything is downloaded button "Finish" turns blue. Click the button now. - -![Downloading components](../images/studioSetup/08_Downloading.png) - -(Building-APK-download-AAPS-code)= - -## Download AAPS code - -* On the Android Studio welcome screen select "Projects" (1) on the left and then "Get from VCS" (2). - - ![Android Studio wizard](../images/studioSetup/20_ProjectVCS.png) - - * If you already opened Android Studio and do not see the welcome screen anymore select File (1) > New (2) > Project from Version Control... (3) - - ![Check out project from version control within Android Studio](../images/AndroidStudio_FileNew.PNG) - - * We will now tell Android Studio were to get the code from: - - * Make sure you have selected "Repository URL" on the left (1). - - * Check if "Git" is selected as version control (2). - * Copy and paste the URL ```https://github.com/nightscout/AndroidAPS``` to the main AAPS repository into the URL textbox (3). - * Choose the directory where you want to save the cloned code (4). - - ![Clone Git](../images/studioSetup/21_CloneURL.png) - -* Click button "Clone" (5). - - ![Clone repository](../images/studioSetup/22_Cloning.png) - -* Do not click "Background" while repository is cloned! - -* After the repository is cloned successfully, Android Studio will open the cloned project. - -* You will be asked whether you want to trust the project. Click on "Trust project"! - - ![Trust project](../images/studioSetup/23_TrustProject.png) - -* In the status bar at the bottom you will see the information that Android Studio is running background tasks. - - ![Background tasks](../images/studioSetup/24_GradleSyncRunning.png) - -* Windows only: Grant access if your firewall is asking for permission. - - ![Firewall permission java](../images/AndroidStudio361_18.png) - -* Once the background tasks are finished you will probably see an error saying that errors occurred (1) or (2) or (3). - - ![SDK licence](../images/studioSetup/25_SyncFailed.png) - - Don't worry, this will be solved soon! - -(Building-APK-set-git-path-in-preferences)= - -## Set git path in preferences - -Make sure [git is installed](../Installing-AndroidAPS/git-install.md) on your computer and you have restarted your computer since installing. - -On the Android Studio welcome screen click "Customize" (1) on the left and then select the link "All settings..." (2): - -![Android Studio settings from welcome screen](../images/studioSetup/10_WizardSettings.png) - -### Windows - -* As windows user, make sure you have restarted your computer after [installing Git](../Installing-AndroidAPS/git-install.md). - -* In the menu, go to File (1) > Settings (2) (or Android Studio > Preferences on Mac). - - ![Open settings](../images/studioSetup/30_Settings.png) - -* Double-click "Version Control" (1) to open the sub-menu. - -* Click Git (2). -* Make sure update method "Merge" (3) is selected. -* Check if Android Studio can locate path to git.exe automatically by clicking the button "Test" (4). - - ![Android Studio settings](../images/studioSetup/11_GitPath.png) - -* If automatic setting is successful git version will be displayed next to the path. - - ![Git version displayed](../images/studioSetup/12_GitVersion.png) - -* Eventually git.exe cannot be found automatically or the Test will result in an error (1): - - ![Git not found](../images/studioSetup/13_GitVersionError.png) - - In this case click on the folder icon (2). - -* Use [search function](https://www.tenforums.com/tutorials/94452-search-file-explorer-windows-10-a.html) in windows explorer to find "git.exe" if you are unsure where git has been installed. You are looking for a file named "git.exe", located in **\bin** folder. - -* Select path to git.exe and make sure you selected the one in ** \bin\ ** folder (3) and click "OK" (4). - - ![Select git manually](../images/studioSetup/14_GitManualSelection.png) - -* Check your selected git path again with the "Test" button as described above. - -* When the git version is displayed next to the path (see screenshot above), close settings window by clicking "OK" button (5). - -### Mac - -* Any git version should work. For example . -* Use homebrew to install git: ```$ brew install git```. -* For details on installing git see the [official git documentation](https://git-scm.com/book/en/v2/Getting-Started-Installing-Git). -* If you install git via homebrew there is no need to change any preferences. Just in case: They can be found here: Android Studio - Preferences. - -(Building-APK-download-android-sdk)= - -## Stáhněte Android SDK - -* In the menu, go to File (1) > Settings (2) (or Android Studio > Preferences on Mac). - - ![Open settings](../images/studioSetup/30_Settings.png) - -* Double-click on Languages & Frameworks to open its submenu (1). - -* Select Android SDK (2). -* Tick the box left of "Android 9.0 (Pie)" (3) (API Level 28). - - ![SDK settings](../images/studioSetup/31_AndroidSDK.png) - -* Confirm changes by clicking OK. - - ![Confirm SDK changes](../images/studioSetup/32_ConfirmSDK.png) - -* Wait until the SDK download and installation is finished. - - ![Wait during SDK installation](../images/studioSetup/34_DownloadSDK.png) - -* When SDK installation is completed the "Finish" button will turn blue. Click this button. - - ![Finish SDK installation](../images/studioSetup/35_DownloadSDKfinished.png) - -* Android Studio might recommend to update the gradle system. **Never update gradle!** This will lead to difficulties! - -* If you see an information on the lower right side of your Android Studio window that Android Gradle Plugin is ready to update click on the text "upgrade" (1). - - ![No gradle update](../images/studioSetup/36_GradleUpdateRequest.png) - -* In the dialog box the select "Don't remind me again for this project" (2). - - ![No gradle update](../images/studioSetup/37_GradleUpdateDeny.png) - -* Restart Android Studio before you continue. - -(Building-APK-generate-signed-apk)= - -## Vytvořte podepsaný soubor APK - -Signing means that you indicate your app to be your own creation but in a digital way as a kind of digital fingerprint within the app itself. That is necessary because Android has a rule that it only accepts signed code to run for security reasons. For more information on this topic, follow [this link](https://developer.android.com/studio/publish/app-signing.html#generate-key). - -* After Android Studio is started, wait until all background tasks are finished. - - ![Wait for background tasks](../images/studioSetup/40_BackgroundTasks.png) - - * ***Warning:*** If errors occur, do not continue with the following steps. \ Consult the [troubleshooting section](../Installing-AndroidAPS/troubleshooting_androidstudio) for known problems! - - ![Gradle Sync Error](../images/studioSetup/41_GradleSyncError.png) - -* Click "Build" (1) in the menu bar and select "Generate Signed Bundle / APK..." (2). - - ![Sestavení apk](../images/studioSetup/42_MenuBuild.png) - -* Select "APK" (1) instead of "Android App Bundle" and click "Next" (2). - - ![APK namísto možnosti bundle](../images/studioSetup/43_Apk.png) - -* Make sure that module is set to "AndroidAPS.app" (1). - -* Click "Create new..." (2) to start creating your key store. - - ***Note:*** A key store in this case is nothing more than a file in which the information for signing is stored. It is encrypted and the information is secured with passwords. - - ![Create key store](../images/studioSetup/44_KeystoreNew.png) - -* Click the folder symbol to select a path on your computer for your key store. - - ![Create key store](../images/studioSetup/45_KeystoreDialog.png) - -* Select the path where your key store shall be saved (1). - - ![Create key store](../images/studioSetup/46_KeystorePath.png) - - ***Warning: Do not save in same folder as project. You must use a different directory!*** A good location would be your home folder. - -* Type a file name for your key store (2) and confirm with "OK" (3). - -* Enter (2) and confirm (3) the password for your key store. ![Select key store path](../images/studioSetup/47_KeystoreDialog.png) - - ***Note:*** Passwords for key store and key do not have to be very sophisticated. Make sure to remember those or make a note in a safe place. In case you will not remember your passwords in the future, see [troubleshooting for lost key store](troubleshooting_androidstudio-lost-keystore). - -* Enter an alias (4) for your key. Choose whatever you like. - -* Enter (5) and confirm (6) the password for your key - -* Validity (7) is 25 years by default. You do not have to change the default value. - -* First and last name must be entered (8). All other information is optional. - -* Click "OK" (9) when you are done. - -* Make sure the box to remember passwords is checked (1). So you don't have to enter them again next time you build the apk (i.e. when updating to a new AAPS version). - -* Click "Next" (2). - - ![Remember passwords](../images/studioSetup/48_KeystoreSave.png) - -* Select build variant "fullRelease" (1) and press "Finish". - - ![Select build variant](../images/studioSetup/49_BuildVariant.png) - -* Android Studio will show "Gradle Build running" at the bottom. This takes some time, depending on your computer and internet connection. **Be patient!** - - ![Gradle Running](../images/studioSetup/50_GradleRunning.png) - -* Android Studio will display the information "Generate Signed APK" after build is finished. - - ![Build finished](../images/studioSetup/51_BuildFinished.png) - -* In case build was not successful refer to the [troubleshooting section](../Installing-AndroidAPS/troubleshooting_androidstudio). - -* Click on the notification to expand it. - -* Click on the link "locate". - - ![Locate build](../images/studioSetup/52_BuildLocate.png) - - * If the notification is gone, you can always open the "Event log" and select the same link there. ![Úspěšné sestavení - event log](../images/studioSetup/53_EventLog.png) - -* Your file manager/explorer will open. Navigate to the directory "full" (1) > "release" (2). - - ![Umístění souboru apk](../images/studioSetup/54_APKlocation.png) - -* "app-full-release.apk" (3) is the file you are looking for! - -(Building-APK-transfer-apk-to-smartphone)= - -## Přeneste soubor APK do telefonu - -Easiest way to transfer app-full-release.apk to your phone is via [USB cable or Google Drive](https://support.google.com/android/answer/9064445?hl=en). Please note that transfer by mail might cause difficulties and is not the preferred way. - -On your phone you have to allow installation from unknown sources. Manuals how to do this can be found on the internet (i.e. [here](https://www.expressvpn.com/de/support/vpn-setup/enable-apk-installs-android/) or [here](https://www.androidcentral.com/unknown-sources)). - -## Řešení problémů - -See separate page [troubleshooting Android Studio](../Installing-AndroidAPS/troubleshooting_androidstudio). \ No newline at end of file diff --git a/docs/CROWDIN/cs/Resources/index.md b/docs/CROWDIN/cs/Resources/index.md deleted file mode 100644 index 1e2fef122a9c..000000000000 --- a/docs/CROWDIN/cs/Resources/index.md +++ /dev/null @@ -1,8 +0,0 @@ -# Zdroje - -```{toctree} -:glob: true -:maxdepth: 4 - -Klinický průvodce k AndroidAPS -``` diff --git a/docs/CROWDIN/cs/Sandbox/sandbox2.md b/docs/CROWDIN/cs/Sandbox/sandbox2.md deleted file mode 100644 index 33c547956c89..000000000000 --- a/docs/CROWDIN/cs/Sandbox/sandbox2.md +++ /dev/null @@ -1,43 +0,0 @@ -# internal sandbox file 2 for testing - -```{admonition} no need to translate this -:class: note - -No need to translate this. -``` - -This is an internal sandbox file for the documentation team to test - -1. markdown syntax and - -1. background process for - 1. CROWDIN translation and - 2. Read The Docs deployment. - -You can dirctly jump from here to the first label in the sandbox1.md file - ["Jump"](sandbox1-this-is-a-test). - -You can dirctly jump from here to the second label in this file - ["Jump"](sandbox1-this-is-another-test). - -Here you can jump to the first sandbox file - ["Jump"](./sandbox1.md). - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -(sandbox2-this-is-a-test)= -## This is a test - -This is a test if labels must be unique. - -### This is spare information from the docs - -cut from index: - -There are "limits" set in place when you are first beginning your AAPS journey. These safety limits have been developed over many years by observations of the inadvertent mistakes that new users are most likely to make when first learning to set up, build, and then successfully loop with AAPS - as most often those mistakes occur simply because the user was so excited to get started using the system that they may have forgotten to sit down and dedicate the time needed to understand the information within this documentation thoroughly. - - -### spare info from the overview to put into "preparing" - -Since the requirements are very different from anything you might have set up in the past, we recommend that you really follow the instructions, step-by-step the first few times you build the app, so that you have a stronger sense of how the app building process is supposed to behave when all directions are followed exactly. Please remember to take your time. Later this will go very quickly when you build the app again for a new version. That way you will have a greater chance of noticing when something doesn't going as planned before too many steps are out of line. It is important to save the your keystore file (.jks file used to sign your app) in a safe place, so that you can always use that exact same keystore file and password each and every time you are asked to create a new updated version of AAPS, as this file is what makes sure that each new version of the app "remembers" all the information that you have provided to it in previous versions of the app and thus ensure that the updates will go as smoothly as possible. On average, you can assume that there will be one new version and 2-3 required updates per year. This number is based on experience and may change in the future. But we do want to at least give you a general guideline on what to expect. When you are more experienced at building updated AAPS app versions all the steps that are required in building an updated app will only take 15-30 minutes, on average. However, in the beginning there can be a rather steep learning curve as these steps are not always considered intuitive by new users! So do not get frustrated if you find that it takes half a day or a whole day with some help from the community before you are finally finished with the update process. If you find that you are getting very frustrated just take a short break, and oftentimes; after a stroll around the block or two...you'll find that you are better able to approach the problem again. diff --git a/docs/CROWDIN/cs/Usage/Objectives.md b/docs/CROWDIN/cs/Usage/Objectives.md deleted file mode 100644 index eb7be2778c6f..000000000000 --- a/docs/CROWDIN/cs/Usage/Objectives.md +++ /dev/null @@ -1,184 +0,0 @@ -# Cíle - -AAPS has a series of Objectives that need to be completed to walk you through the features and settings of safe looping. Zajistí vám, že jste nastavili všechny detaily z dříve uvedených sekcí správně, že rozumíte tomu, co váš systém dělá a proč, a že mu můžete důvěřovat. - -If you are **upgrading phones** then you can [export your settings](../Usage/ExportImportSettings.md) to keep your progress through the objectives. Not only will your progress through the objectives be saved, but also your safety settings such as max bolus etc. If you do not export and import your settings then you will need to start the objectives from the beginning again. It is a good idea to [backup your settings](../Usage/ExportImportSettings.html) frequently just in case. - -If you want to go back in objectives see [explanation below](Objectives-go-back-in-objectives). - -## Cíl 1: Nastavit vizualizaci a monitoring, analyzovat bazály a poměry - -- Select the right blood glucose source for your setup. See [BG Source](../Configuration/BG-Source.md) for more information. -- Select the right Pump in ConfigBuilder (select Virtual Pump if you are using a pump model with no AAPS driver for looping) to ensure your pump status can communicate with AAPS. -- If using DanaR pump then ensure you have followed [DanaR Insulin Pump](../Configuration/DanaR-Insulin-Pump.md) instructions to ensure the link between pump and AAPS. -- You need to establish a data repository/reporting platform to complete this objective. That can be accomplished with either Nightscout or Tidepool (or both). Follow instructions at the [Nightscout](../Installing-AndroidAPS/Nightscout.md) or [Tidepool](../Installing-AndroidAPS/Tidepool.md) page for instructions. -- Note that URL in NSClient must be **WITHOUT /api/v1/** at the end - see [NSClient settings in Preferences](Preferences-nsclient). - -*You may need to wait for the next blood glucose reading to arrive before AAPS will recognise it.* - -## Objective 2: Learn how to control AAPS - -- Perform several actions in AAPS as described in this objective. - -- Click on the orange text "Not completed yet" to access the to-dos. - -- Links will be provided to guide you in case you are not familiar with a specific action yet. - - ```{image} ../images/Objective2_V2_5.png - :alt: Screenshot cíl 2 - ``` - -(Objectives-objective-3-prove-your-knowledge)= - -## Cíl 3: Prokázat své znalosti - -Objective 3 is a multiple choice test based on questions designed to test your theoretical knowledge of **AAPS**. - -Some users find Objective 3 to be the most difficult objective to complete. Please do read the AAPS documents in conjunction with the questions. If you are genuinely stuck after researching the **AAPS** documents, please search or ask for help on the Facebook or Discord group. These groups can provide friendly hints or redirect you to the relevant part of the **AAPS** documents. - -To proceed with Objective 3, click on the orange text “Not completed yet” to access the relevant question. Please read each question and select your answer(s). - - - -Within each question, a hyperlink to the **AAPS** documents will guide you to the relevant section of the document which you should read in order to locate the correct answer. - - -[Obj3_Screenshot 2023-12-05 223422](https://github.com/openaps/AndroidAPSdocs/assets/137224335/77347516-e24e-459d-98ab-acbb49a3d4e8)![image](https://github.com/openaps/AndroidAPSdocs/assets/137224335/ca756b8e-efbc-4427-b281-ac953ce16718) - - - -For each question, there may be more than one answer that is correct! If an incorrect answer is selected, the question will be time locked for a certain amount of time (60 minutes) before you can go back and answer the question. - - -After updating to a new version of **AAPS**, new questions may be added to cover a prevalent issue picked up by **AAPS** or alternatively to test your knowledge of a new feature of **AAPS** as released. - - -When **AAPS** is installed for the first time, you will have to complete Objective 3 entirely in order to move onto Objective 4. Each objective is required to be completed in sequential order. New features will gradually be unlocked as progress is made through the objectives. - -__What happens if new questions are added later to Objective 3?__ From time to time, new features are added to **AAPS** which may require a new question to be added to Objective 3. As a result, any new question added to Objective 3 will be marked as “incomplete” because **AAPS** will require you to action this. As each Objective is independent, you will not lose the existing functionality of **AAPS** providing the other objectives remain completed. - - -## Cíl 4: Začít s otevřenou smyčkou - -- Select Open Loop either from Preferences, or by pressing and holding the Loop button in top left of the home screen. -- Work through the [Preferences](../Configuration/Preferences.md) to set up for you. -- Manually enact at least 20 of the temporary basal rate suggestions over a period of 7 days; input them to your pump and confirm in AAPS that you have accepted them. Ensure this data shows in AAPS and Nightscout. -- Enable [temp targets](../Usage/temptarget.md) if necessary. Použijte dočasný cíl Hypoglykémie, abyste systému zabránili v příliš agresivních korekcích, pokud by glykémie po vyřešení hypoglykémie stoupala. - -### Snížení počtu oznámení - -- To reduce the Number of decisions to be made while in Open Loop set wide target range like 90 - 150 mg/dl or 5,0 - 8,5 mmol/l. - -- You might even want to wider upper limit (or disable Open Loop) at night. - -- In Preferences you can set a minimum percentage for suggestion of basal rate change. - - ```{image} ../images/OpenLoop_MinimalRequestChange2.png - :alt: Minimální změna pro požadavek Open Loop - ``` - -- Also, you do not need to act every 5 minutes on all suggestions... - -## Cíl 5: Porozumění otevřené smyčce, včetně doporučení pro dočasné bazály - -- Start to understand the thinking behind the temp basal recommendations by looking at the [determine basal logic](https://openaps.readthedocs.io/en/latest/docs/While%20You%20Wait%20For%20Gear/Understand-determine-basal.html) and both the [forecast line in AAPS homescreen](Screenshots-prediction-lines)/Nightscout and the summary of outputs from the calculations in your OpenAPS tab. - -Cíl nastavte o něco výše než obvykle, dokud si nebudete jisti správností výpočtů a nastavení. Systém umožňuje - -- a low target to be a minimum of 4 mmol (72 mg/dl) or maximum of 10 mmol (180 mg/dl) -- a high target to be a minimum of 5 mmol (90 mg/dl) and maximum of 15 mmol (225 mg/dl) -- a temporary target as a single value can be anywhere in the range of 4 mmol to 15 mmol (72 mg/dl to 225 mg/dl) - -Cíl je hodnota, o kterou se opírá kalkulace, nikoliv hodnota, na které byste chtěli svou glykémii držet. If your target is very wide (say, 3 or more mmol \[50 mg/dl or more\] wide), you will often find little AAPS action. To je proto, že predikovaná glykémie bude někde v tomto širokém rozmezí a proto není doporučováno mnoho dočasných bazálů. - -You may want to experiment with adjusting your targets to be a closer together range (say, 1 or less mmol \[20 mg/dl or less\] wide) and observe how the behavior of your system changes as a result. - -You can view a wider range (green lines) on the graph for the values you aim to keep your blood glucose within by entering different values in [Preferences](../Configuration/Preferences.md) > Range for Visualisation. - -```{image} ../images/sign_stop.png -:alt: Znaménko Stop -``` - -### Zastavte se zde, pokud používáte otevřenou smyčku s virtuální pumpou – neklikejte na tlačítko Zkontrolovat na konci tohoto cíle. - -```{image} ../images/blank.png -:alt: prázdný -``` - -(Objectives-objective-6-starting-to-close-the-loop-with-low-glucose-suspend)= -## Cíl 6: Začátek uzavřené smyčky - s pozastavením pumpy při nízké glykémii - -```{image} ../images/sign_warning.png -:alt: Varování -``` - -### Closed loop will not correct high BG values in objective 6 as it is limited to low glucose suspend. High BG values have to be corrected manually by you! - -- Prerequisite: You need a good profile (basal, ISF, IC) already working in AAPS to start with Loop in Low Glucose Suspend mode. Otherwise you can run in a hypo which you have to manually correct. This will help you a lot to avoid having to treat a low glucose over a period of 5 days. **If you are still having frequent or severe low glucose episodes then consider refining your DIA, basal, ISF and carb ratios and do NOT start objective 6 at this time.** -- You don't have to change your settings now. During objective 6, the maxIOB setting is internally set to zero automatically. **This override will be reversed when moving to objective 7.** -- The system will override your maxIOB settings to zero, which means if blood glucose is dropping it can reduce basal for you. If blood glucose is rising then it will only increase basal if the basal IOB is negative from a previous Low Glucose Suspend. Otherwise basal rates will remain the same as your selected profile. **That means that you have to manually handle high values with insulin corrections.** -- If your basal IOB is negative (see screenshot below) a TBR > 100% can be issued also in objective 6. - -```{image} ../images/Objective6_negIOB.png -:alt: Příklad negativního IOB -``` - -- Set your target range slightly higher than you usually aim for, just to be safe and have a bit more scurity buffer. -- Enable 'Low Glucose Suspend' mode either by by pressing and holding the Loop icon at the top right corner of the home screen and selecting the Loop - LGS mode icon. -- Watch how temporary basals are active by viewing the blue basal text on the homescreen or the blue basal render on the homescreen graph. -- Bez možnosti zvýšit bazál při srovnání křivky glykémie se vám dočasně může stávat, že po vyřešení hypoglykémie, bude následovat přílišný vzestup glykémie. - -(Objectives-objective-7-tuning-the-closed-loop-raising-max-iob-above-0-and-gradually-lowering-bg-targets)= -## Objective 7: Tuning the closed loop, raising maxIOB above 0 and gradually lowering BG targets - -- Select 'Closed Loop' either from [Preferences](../Configuration/Preferences.md) or by pressing and holding the Loop icon at the top right corner of the home screen, over a period of 1 day. - -- Raise your 'Maximum total IOB OpenAPS can’t go over' (in OpenAPS called 'max-iob') above 0. The default recommendation is "average mealbolus + 3x max daily basal" (for the SMB algorithm) or "3x max daily basal" (for the older AMA algorithm) but you should slowly work up to this until you know your settings work for you (max daily basal = the maximum hourly value in any time segment of the day). - - Toto doporučení by mělo být považováno za výchozí bod. If you set to the 3x and you are seeing moves that push you too hard and fast then lower that number. If you are very resistant, raise it very little at a time. - - ```{image} ../images/MaxDailyBasal2.png - :alt: max denní bazál - ``` - -- Once confident on how much IOB suits your looping patterns, then reduce your targets to your desired level. - -(Objectives-objective-8-adjust-basals-and-ratios-if-needed-and-then-enable-autosens)= -## Cíl 8: Upravit bazály a poměry, když bude potřeba, a povolit automatickou detekci citlivosti na inzulín - -- You can use [autotune](https://openaps.readthedocs.io/en/latest/docs/Customize-Iterate/autotune.html) as a one off to check your basals remain accurate or do a traditional basal test. -- Enable [autosens](../Usage/Open-APS-features.md) over a period of 7 days and watch the white line on the homescreen graph show how your sensitivity to insulin may be rising or falling as a result of exercise or hormones etc. and keep an eye in the OpenAPS report tab how AAPS is adjusting the basals and/or targets accordingly. - -*Don’t forget to record your looping in* [this form](https://bit.ly/nowlooping) *logging AAPS as your type of DIY loop software, if you have not already done so.* - -(Objectives-objective-9-enabling-additional-oref1-features-for-daytime-use-such-as-super-micro-bolus-smb)= -## Objective 9: Enabling additional oref1 features for daytime use, such as super micro bolus (SMB) - -- You must read the [SMB chapter in this wiki](Open-APS-features-super-micro-bolus-smb) and [chapter oref1 in openAPSdocs](https://openaps.readthedocs.io/en/latest/docs/Customize-Iterate/oref1.html) to understand how SMB works, especially what's the idea behind zero-temping. -- Then you ought to [rise maxIOB](Open-APS-features-maximum-total-iob-openaps-cant-go-over-openaps-max-iob) to get SMBs working fine. maxIOB nyní zahrnuje veškerý IOB, nejen ten z bazálů. That is, if given a bolus of 8 U for a meal and maxIOB is 7 U, no SMBs will be delivered until IOB drops below 7 U. A good start is maxIOB = average mealbolus + 3x max daily basal (max daily basal = the maximum hourly value in any time segment of the day - see [objective 7](Objectives-objective-7-tuning-the-closed-loop-raising-max-iob-above-0-and-gradually-lowering-bg-targets) for an illustration) -- min_5m_carbimpact default in absorption settings has changed from 3 to 8 going from AMA to SMB. Přecházíte-li z AMA na SMB, musíte to změnit ručně. - -(Objectives-objective-10-automation)= -## Objective 10: Automation - -- You have to start objective 10 to be able to use [Automation](../Usage/Automation.md). -- Make sure you have completed all objectives including exam [Objectives-objective-3-prove-your-knowledge](Objectives#objective-3-prove-your-knowledge). -- Completing previous objectives will not effect other objectives you have already finished. Splněné cíle zůstanou zachovány! - -(Objectives-objective-11-DynamicISF)= -## Objective 11: Additional Features such as DynamicISF - -- You have to start objective 11 to be able to use [DynamicISF](../Usage/Open-APS-features.md) - -(Objectives-go-back-in-objectives)= -## Návrat k předchozímu cíli - -Chcete-li se z jakéhokoliv důvodu vrátit k předchozímu cíli, stačí tak učinit kliknutím na „vymazat dokončené“. - -```{image} ../images/Objective_ClearFinished.png -:alt: Návrat zpět -``` - -## Objectives in Android APS before version 3.0 - -One objective was removed when Android APS 3.0 was released. Users of Android APS version 2.8.2.1 who are on older Android software (i.e. earlier than version 9) will be using an older set of objectives which can be found [here](../Usage/Objectives_old.md). diff --git a/docs/CROWDIN/cs/Usage/Objectives_old.md b/docs/CROWDIN/cs/Usage/Objectives_old.md deleted file mode 100644 index a2f76e1683bd..000000000000 --- a/docs/CROWDIN/cs/Usage/Objectives_old.md +++ /dev/null @@ -1,152 +0,0 @@ -# Objectives as of Android APS 2.8.2.1 - -This is not the latest version of the Android APS Objectives. This page details the Objectives that were in place prior to version 3.0. Anyone using an older version of Android (i.e. prior to Android 9) and Android APS version 2.8.2.1 should refer to this page. - -Please see [this page](../Usage/Objectives.md) for the current set of Objectives. - -AndroidAPS má sadu Cílů, které musíte dokončit a které vás provedou jeho funkcemi a nastaveními tak, aby pro vás smyčka nebyla nebezpečná. Zajistí vám, že jste nastavili všechny detaily z dříve uvedených sekcí správně, že rozumíte tomu, co váš systém dělá a proč, a že mu můžete důvěřovat. - -If you are **upgrading phones** then you can [export your settings](../Usage/ExportImportSettings.md) to keep your progress through the objectives. Not only will your progress through the objectives be saved, but also your safety settings such as max bolus etc. If you do not export and import your settings then you will need to start the objectives from the beginning again. It is a good idea to [backup your settings](../Usage/ExportImportSettings.html) frequently just in case. - -If you want to go back in objectives see [explanation below](../Usage/Objectives.md#go-back-in-objectives). - -## Cíl 1: Nastavit vizualizaci a monitoring, analyzovat bazály a poměry - -- Select the right blood glucose source for your setup. See [BG Source](../Configuration/BG-Source.md) for more information. -- Select the right Pump in ConfigBuilder (select Virtual Pump if you are using a pump model with no AndroidAPS driver for looping) to ensure your pump status can communicate with AndroidAPS. -- If using DanaR pump then ensure you have followed [DanaR Insulin Pump](../Configuration/DanaR-Insulin-Pump.md) instructions to ensure the link between pump and AndroidAPS. -- Follow instructions in [Nightscout](../Installing-AndroidAPS/Nightscout.md) page to ensure Nightscout can receive and display this data. -- Note that URL in NSClient must be **WITHOUT /api/v1/** at the end - see [NSClient settings in Preferences](../Configuration/Preferences.md#nsclient). - -*You may need to wait for the next blood glucose reading to arrive before AndroidAPS will recognise it.* - -## Cíl 2: Naučte se ovládat AndroidAPS - -- Perform several actions in AndroidAPS as described in this objective. - -- Click on the orange text "Not completed yet" to access the to-dos. - -- Links will be provided to guide you in case you are not familiar with a specific action yet. - - ![Screenshot cíl 2](../images/Objective2_V2_5.png) - -## Cíl 3: Prokázat své znalosti - -- Pass a multiple-choice exam testing your AndroidAPS knowledge. - -- Click on the orange text "Not completed yet" to access the page with the question and answering options. - - ![Screenshot cíl 3](../images/Objective3_V2_5.png) - -- Links will be provided to guide you in case you are unsure about the correct answers yet. - -- The questions for objective 3 have been completely rewritten by native speakers as of AAPS 2.8. Nové otázky pokrývají stejná témata a několik nových. - -- These new questions will lead to some not answered questions even though you have successfully completed objective 3 in previous versions. - -- Unanswered questions will affect you only if you start a new objective. Jinými slovy: Pokud jste již dokončili všechny cíle, můžete počkat a odpovědět na nové otázky později bez ztráty funkcí AAPS. - -## Cíl 4: Začít s otevřenou smyčkou - -- Select Open Loop either from Preferences, or by pressing and holding the Loop button in top left of the home screen. -- Work through the [Preferences](../Configuration/Preferences.md) to set up for you. -- Manually enact at least 20 of the temporary basal rate suggestions over a period of 7 days; input them to your pump and confirm in AndroidAPS that you have accepted them. Ujistěte se, že se tyto údaje zobrazí v AndroidAPS a Nightscoutu. -- Enable [temp targets](../Usage/temptarget.md) if necessary. Použijte dočasný cíl Hypoglykémie, abyste systému zabránili v příliš agresivních korekcích, pokud by glykémie po vyřešení hypoglykémie stoupala. - -### Snížení počtu oznámení - -- To reduce the Number of decisions to be made while in Open Loop set wide target range like 90 - 150 mg/dl or 5,0 - 8,5 mmol/l. - -- You might even want to wider upper limit (or disable Open Loop) at night. - -- In Preferences you can set a minimum percentage for suggestion of basal rate change. - - ![Minimální změna pro požadavek Open Loop](../images/OpenLoop_MinimalRequestChange2.png) - -- Also, you do not need to act every 5 minutes on all suggestions... - -## Cíl 5: Porozumění otevřené smyčce, včetně doporučení pro dočasné bazály - -- Start to understand the thinking behind the temp basal recommendations by looking at the [determine basal logic](https://openaps.readthedocs.io/en/latest/docs/While%20You%20Wait%20For%20Gear/Understand-determine-basal.html) and both the [forecast line in AndroidAPS homescreen](../Getting-Started/Screenshots.md#prediction-lines)/Nightscout and the summary of outputs from the calculations in your OpenAPS tab. - -Cíl nastavte o něco výše než obvykle, dokud si nebudete jisti správností výpočtů a nastavení. Systém umožňuje - -- a low target to be a minimum of 4 mmol (72 mg/dl) or maximum of 10 mmol (180 mg/dl) -- a high target to be a minimum of 5 mmol (90 mg/dl) and maximum of 15 mmol (225 mg/dl) -- a temporary target as a single value can be anywhere in the range of 4 mmol to 15 mmol (72 mg/dl to 225 mg/dl) - -Cíl je hodnota, o kterou se opírá kalkulace, nikoliv hodnota, na které byste chtěli svou glykémii držet. If your target is very wide (say, 3 or more mmol \[50 mg/dl or more\] wide), you will often find little AAPS action. To je proto, že predikovaná glykémie bude někde v tomto širokém rozmezí a proto není doporučováno mnoho dočasných bazálů. - -You may want to experiment with adjusting your targets to be a closer together range (say, 1 or less mmol \[20 mg/dl or less\] wide) and observe how the behavior of your system changes as a result. - -You can view a wider range (green lines) on the graph for the values you aim to keep your blood glucose within by entering different values in [Preferences](../Configuration/Preferences.md) > Range for Visualisation. - -![Znaménko Stop](../images/sign_stop.png) - -### Zastavte se zde, pokud používáte otevřenou smyčku s virtuální pumpou – neklikejte na tlačítko Zkontrolovat na konci tohoto cíle. - -![prázdný](../images/blank.png) - -## Cíl 6: Začátek uzavřené smyčky - s pozastavením pumpy při nízké glykémii - -![Varování](../images/sign_warning.png) - -### U 6. cíle nebude uzavřená smyčka korigovat vysokou glykémii, bude pouze zastavovat před nízkou. Na vysoké glykémie musíte ručně dopíchnout vy sami! - -- Select Closed Loop either from [Preferences](../Configuration/Preferences.md) or by pressing and holding the Open Loop button in the top left of the home screen. - -- Set your target range slightly higher than you usually aim for, just to be safe. - -- Watch how temporary basals are active by viewing the blue basal text on the homescreen or the blue basal render on the homescreen graph. - -- Ensure your settings have supported AndroidAPS to avoid having to treat a low glucose over a period of 5 days. Pokud stále řešíte časté nebo vážné výskyty nízkých glykémií, zvažte úpravu svého DIA, bazálů, citlivosti a sacharidových poměrů. - -- You don't have to change your settings. Při plnění cíle 6 je maxIOB nastaveno automaticky na nulu. Toto nastavení bude při přechodu na cíl 7 odstraněno. - -- The system will override your maxIOB settings to zero, which means if blood glucose is dropping it can reduce basal for you, but if blood glucose is rising then it will only increase basal if the basal IOB is negative (from a previous Low Glucose Suspend), otherwise basal rates will remain the same as your selected profile. - - ![Příklad negativního IOB](../images/Objective6_negIOB.png) - -- If your basal IOB is negative (see screenshot above) a TBR > 100% can be issued also in objective 6. - -- Bez možnosti zvýšit bazál při srovnání křivky glykémie se vám dočasně může stávat, že po vyřešení hypoglykémie, bude následovat přílišný vzestup glykémie. - -## Cíl 7: Vyladit uzavřenou smyčku, zvyšovat max IOB nad 0 a postupně snižovat cílovou glykémii - -- Raise your 'Maximum total IOB OpenAPS can’t go over' (in OpenAPS called 'max-iob') above 0 over a period of 1 day, the default recommendation is "average mealbolus + 3x max daily basal"(for SMB algorithm) or "3x max daily basal" (for older AMA algorithm) but you should slowly work up to this until you know your settings work for you (max daily basal = the maximum hourly value in any time segment of the day). - - Toto doporučení by mělo být považováno za výchozí bod. Pokud ho nastavíte na 3x a uvidíte kroky, které vás rychle stahují dolů, pak snižte toto číslo. Pokud jste velmi rezistentní na inzulín, pomalu ho zvyšujte. - - ![max denní bazál](../images/MaxDailyBasal2.png) - -- Once confident on how much IOB suits your looping patterns then reduce your targets to your desired level. - -## Cíl 8: Upravit bazály a poměry, když bude potřeba, a povolit automatickou detekci citlivosti na inzulín - -- You can use [autotune](https://openaps.readthedocs.io/en/latest/docs/Customize-Iterate/autotune.html) as a one off to check your basals remain accurate or do a traditional basal test. -- Enable [autosens](../Usage/Open-APS-features.md) over a period of 7 days and watch the white line on the homescreen graph show how your sensitivity to insulin may be rising or falling as a result of exercise or hormones etc. and keep an eye in the OpenAPS report tab how AndroidAPS is adjusting the basals and/or targets accordingly. - -*Don’t forget to record your looping in* [this form](https://bit.ly/nowlooping) *logging AndroidAPS as your type of DIY loop software, if you have not already done so.* - -## Objective 9: Try additional features for daytime use and gain confidence in your closed loop system - -- Before AAPS version 2.7 meal assist (MA) was the basic algorithm for AAPS and completing objective 8 was necessary to activate [advanced meal assist (AMA)](../Usage/Open-APS-features.md#advanced-meal-assist-ama). -- As [advanced meal assist (AMA)](../Usage/Open-APS-features.md#advanced-meal-assist-ama) is the standard algorithm from AAPS version 2.7 onwards use the following 28 days to try features you haven't used yet and get more confident with you closed loop system. - -## Objective 10: Enabling additional oref1 features for daytime use, such as super micro bolus (SMB) - -- You must read the [SMB chapter in this wiki](../Usage/Open-APS-features.md#super-micro-bolus-smb) and [chapter oref1 in openAPSdocs](https://openaps.readthedocs.io/en/latest/docs/Customize-Iterate/oref1.html) to understand how SMB works, especially what's the idea behind zero-temping. -- Then you ought to [rise maxIOB](../Usage/Open-APS-features.md#maximum-total-iob-openaps-cant-go-over-openaps-max-iob) to get SMBs working fine. maxIOB nyní zahrnuje veškerý IOB, nejen ten z bazálů. That is, if given a bolus of 8 U for a meal and maxIOB is 7 U, no SMBs will be delivered until IOB drops below 7 U. A good start is maxIOB = average mealbolus + 3x max daily basal (max daily basal = the maximum hourly value in any time segment of the day - see [objective 7](../Usage/Objectives#objective-7-tuning-the-closed-loop-raising-max-iob-above-0-and-gradually-lowering-bg-targets) for an illustration) -- min_5m_carbimpact default in absorption settings has changed from 3 to 8 going from AMA to SMB. Přecházíte-li z AMA na SMB, musíte to změnit ručně. - -## Objective 11: Automation - -- You have to start objective 11 to be able to use [Automation](../Usage/Automation.md). -- Make sure you have completed all objectives including exam [../Usage/Objectives.md#objective-3-prove-your-knowledge](../Usage/Objectives#objective-3-prove-your-knowledge). -- Completing previous objectives will not effect other objectives you have already finished. Splněné cíle zůstanou zachovány! - -## Návrat k předchozímu cíli - -Chcete-li se z jakéhokoliv důvodu vrátit k předchozímu cíli, stačí tak učinit kliknutím na „vymazat dokončené“. - -![Návrat zpět](../images/Objective_ClearFinished.png) diff --git a/docs/CROWDIN/cs/Usage/Smoothing-Blood-Glucose-Data-in-xDrip.md b/docs/CROWDIN/cs/Usage/Smoothing-Blood-Glucose-Data-in-xDrip.md deleted file mode 100644 index 09005ade000d..000000000000 --- a/docs/CROWDIN/cs/Usage/Smoothing-Blood-Glucose-Data-in-xDrip.md +++ /dev/null @@ -1,33 +0,0 @@ -(Smoothing-Blood-Glucose-Data-in-xDrip-smoothing-blood-glucose-data)= - -# Vyhlazování zarušených dat glykémií - -If BG data is jumpy/noisy, AAPS may dose insulin incorrectly resulting in high or low BG. For this reason it’s important to disable the loop until the problem is resolved. Depending on your CGM such issues may be due to the CGM’s configuration or sensor problems/site issues. You may need to replace your CGM sensor to resolve this. - -Some CGM systems have internal algorithms to detect the noise level in the readings and AAPS can use this information to avoid giving SMBs if the BG data is too unreliable. However, some CGMs do not transmit this data and for these BG sources 'Enable SMB always' and 'Enable SMB after carbs' are disabled for safety reasons. - -## Dexcom sensors - -### Build Your Own Dexcom App - -When using [BYODA](DexcomG6-if-using-g6-with-build-your-own-dexcom-app) your BG data is smooth and consistent. Furthermore you can take advantage of Dexcom back-smoothing. There are no restrictions in using SMBs, because the noise-level data is shared with AAPS. - -### xDrip+ with Dexcom G6 or Dexcom ONE - -Noise-level data and smooth BG readings are only shared with AAPS if you use xDrip+ [native mode](https://navid200.github.io/xDrip/docs/Native-Algorithm). Using native mode, there are no restrictions in using SMBs. - -### Dexcom G6 or Dexcom ONE with xDrip+ Companion Mode - -The noise-level data is not shared with AAPS using this method. Therefore 'Enable SMB always' and 'Enable SMB after carbs' are disabled. - -## Freestyle Libre sensors - -### xDrip+ with FreeStyle Libre - -None of the FreeStyle Libre systems (FSL1, FSL2, or FSL3) broadcast any information about the level of noise detected in the readings, and therefore 'Enable SMB always' and 'Enable SMB after carbs' are disabled for all setups using the FreeStyle Libre. - -In addition, many people have reported the FreeStyle Libre often produces noisy data. In xDrip+ there are a few options to help with this: - -**Smooth Sensor Noise.** In xDrip+ Settings > xDrip+ Display Settings ensure that Smooth Sensor Noise is turned on. This attempts to apply smoothing to noisy data. - -**Smooth Sensor Noise (Ultrasensitive).** If you are still seeing noisy data in xDrip+ you can apply more aggressive smoothing using the Smooth Sensor Noise (Ultrasensitive) setting. This will attempt to apply smoothing even on very low levels of detected noise. To do this, first enable [engineering mode](Enabling-Engineering-Mode-in-xDrip.md) in xDrip+. Then navigate to Settings > xDrip+ Display Settings and turn on Smooth Sensor Noise (Ultrasensitive). \ No newline at end of file diff --git a/docs/CROWDIN/cs/Usage/autotune_b.md b/docs/CROWDIN/cs/Usage/autotune_b.md deleted file mode 100644 index ab2adab4a505..000000000000 --- a/docs/CROWDIN/cs/Usage/autotune_b.md +++ /dev/null @@ -1,186 +0,0 @@ -# How to use Autotune plugin - -Documentation about Autotune algorythm can be found in [OpenAPS documentation](https://openaps.readthedocs.io/en/latest/docs/Customize-Iterate/autotune.html). - -Autotune plugin is an implementation of OpenAPS autotune algorythm within AAPS. - -**Currently Autotune Plugin is only available in dev branch with Engineering mode.** - -## Autotune user interface - -![Autotune default screen](../images/Autotune/Autotune_1b.png) - -- You can select in the Profile dropdown menu the input profile you want to tune (by default your current active profile is selected) - - Note: each time you select a new profile, previous results will be removed and Tune days parameter will be set to default value -- Then Tune days is to select the number of days used in calculation to tune your profile. The minimum value is 1 day and the maximum value 30 days. This number should not be too small to get correct iterative and smooth results (above 7 days for each calculation) - - Note: each time you change Tune days parameter, previous results will be removed -- Last Run il a link that recover your latest valid calculation. If you didn't launch Autotune on current day, or if previous results was removed with a modification of calculation parameter above, then you can recover parameters and results of the latest successfull run. -- Warning show you for example some information about selected profile (if you have several IC values or several ISF values) - - Note: Autotune calculation works with only a single IC and a single ISF value. There is currently no existing Autotune algorythm to tune a circadian IC or circadian ISF. If your input profile has several values, you can see in warning section the average value taken into account to tune your profile. -- Check Input Profile button open the Profile Viewer to allow you a quick verification of your profile (Units, DAI, IC, ISF, basal and target) - - Note: Autotune will only tune your IC (single value), ISF (single value) and basal (with circadian variation). Units, DAI and target will remain unchanged in output profile. - -- "Run Autotune" will launch Autotune calculation with selected profile and the number of Tune days - - Note: Autotune calculation can take a long time. Once launched, you can switch to another view (home, ...) and come back later in Autotune plugin to see results - -![Autotune Run start](../images/Autotune/Autotune_2b.png) - -- Then during the run you will see intermediate results below - - - Note: During run, settings are locked, so you cannot change anymore selected input profile or the number of day. You will have to wait the end of current calculation if you want to launch another run with other parameters. - - ![Autotune during run](../images/Autotune/Autotune_3b.png) - -- When Autotune calculation is finished, you will see the result (Tuned profile) and four buttons below. - -![Autotune Result](../images/Autotune/Autotune_4b.png) - -- It's important to always compare input profile (column "Profile"), output profile (column "Tuned") and the percentage of variation for each value (Column "%"). - -- For basal rates, you also have the number of "missing days". You have missing days when Autotune don't have enough data categorized as "Basal" to tune basal rate for this period (for example after each meal when you have carbs absorption). This number should be as low as possible especially when basal is important (for example during the night or at the end of the afternoon) - -- The "Compare profiles" button open the profile comparator view. Input profile is in blue, and output profile (named "Tuned") is in red. - - - Note: in the example below input profile has circadian variation for IC and ISF, but output calculated profile has a single value. If it's important for you to get a circadian output profile see [Circadian IC or ISF profile](#circadian-ic-or-isf-profile) below. - - ![Autotune Compare profiles](../images/Autotune/Autotune_5.png) - -- If you trust results (low percentage of variation between input profile and output profile), you can click on "Activate profile" button and then click on OK to validated. - - - Activate Tuned profile will automatically create a new profile "Tuned" in your Local profile plugin. - - If you already have a profile named "Tuned" in your local profile plugin, then this profile will be updated with calculated Autotune profile before the activation - - ![Autotune Activate profile](../images/Autotune/Autotune_6.png) - -- If you think Tuned profile must be adjusted (for example if you think some variation are too important), then you can click on "Copy to local profile" button - - - A new profile with the prefix "Tuned" and the date and time of the run will be created in local profile plugin - -![Autotune Copy to local profile](../images/Autotune/Autotune_7.png) - -- You can then select local profile to edit the Tuned profile (it will be selected by default when you open Local profile plugin) - - - the values in local profile will but rounded in the user interface to your pump capabilities - - ![Autotune local profile update](../images/Autotune/Autotune_8.png) - -- If you want to replace your input profile with Autotune result, click on "Update input profile" button and validate the Popup with OK - - - Note: if you click on "Activate profile" after "Update input profile", then you will activate your updated profile and not the default "Tuned" profile? - - ![Autotune Update input profile](../images/Autotune/Autotune_9.png) - -- If you have updated your input profile, then the "Update input profile" button is replaced by "Revert input profile" button (see screenshot below). You can that way immediatly see if your current input profile in Local profile plugin already include the result of last run or not. You also have the possibility to recover you input profile without autotune result with this button - - ![Autotune Update input profile](../images/Autotune/Autotune_10.png) - - - -## Autotune settings - -### Autotune plugin settings - -![Autotune default screen](../images/Autotune/Autotune_11.png) - -- Automation Switch Profile (default Off): see [Run Autotune with an automation rule](#run-autotune-with-an-automation-rule) below. If you change this setting to On, the input profile will automatically be updated by the Tuned profile, and it will be activated. - - **Be Carefull, you must trust and verified during several following days that after an update and activation of Tuned profile without modification, it improves your loop** - -- Categorize UAM as basal (default On): This setting is for the users using AndroidAPS without any carbs entered (Full UAM). It will prevent (when Off) to categorize UAM as basal. - - Note: if you have at least one hour of Carbs absorption detected during one day, then all data categorized as "UAM" will be categorized as basal, whatever this setting (On or Off) -- Number of days of data (default 5): You can define default value with this setting. Each time your select a new profile in Autotune plugin, Tune days parameter will be replaced by this default value -- Apply average result in circadian IC/ISF (default Off): see [Circadian IC or ISF profile](#circadian-ic-or-isf-profile) below. - -### Další nastavení - -- Autotune also uses Max autosens ratio and Min autotsens ratio to limit variation. You can see and adjust these values in Config Builder > Sensitivity detection plugin > Settings > Advanced Settings - - ![Autotune default screen](../images/Autotune/Autotune_12.png) - - - -## Advanced feature - -### Circadian IC or ISF profile - -- If you have important variation of IC and/or you ISF in your profile, and you fully trust in your circadian time and variation, then you can set "Apply average result in circadiant IC/ISF" - - - Note that Autotune calculation will always be done with a single value, and circadian variation will not be tuned by Autotune. This setting only apply average variation calculated for IC and/or ISF on your circadian values - -- See on screenshot below Tuned profile with Apply average variation Off (on the left) and On (on the right) - - ![Autotune default screen](../images/Autotune/Autotune_13.png) - - - -### Tune specific days of the week - -- If you click on the checkbox with the eye on the right of "Rune days" parameter, you will see the day selection. You can specify which day of the week should be included in Autotune calculation (in screenshot below you can see an example for "working days" with Saturday and Sunday removed from autotune calculation) - - If the number of day included in Autotune calculation is lower than the number of Tune days, then you will see how many days will be included on the right of Tune days selector (10 days in the example below) - - This setting gives good results only if the number of remaining days is not to small (for example if you Tune a specific profile for week end days with only Sunday and Saturday selected, you should select a minimum of 21 or 28 Tune days to have 6 or 8 days included in Autotune calculation) - -![Autotune default screen](../images/Autotune/Autotune_14b.png) - -- During Autotune calculation, you can see the progress of the calculations ("Partial result day 3 / 10 tuned" on example below) - - ![Autotune default screen](../images/Autotune/Autotune_15b.png) - -## Run Autotune with an automation rule - -First step is to define correct trigger for an automation rule with Autotune: - -Note: for more information on how to set an automation rule, see [here](./Automation.rst). - -- You should select Recurring time trigger: only run Autotune once per day, and autotune is designed to be runned daily (each new run you shift one day later and quickly profile modification should be tiny) - - ![Autotune default screen](../images/Autotune/Autotune_16.png) - -- It's better at the beginning to run Autotune during the day to be able to check results. If you want to run Autotune during the night, you have to select in the trigger 4AM or later to include current day in next Autotune Calculation. - - ![Autotune default screen](../images/Autotune/Autotune_17.png) - -- Then you can select "Run Autotune" Action in the list - - ![Autotune default screen](../images/Autotune/Autotune_18.png) - -- You can then select Autotune Action to adjust parameters for your run. Default parameters are "Active Profile", default Tune days value defined in Autotune Plugin preferences, and All days are selected. - - ![Autotune default screen](../images/Autotune/Autotune_19b.png) - -- After a few days, if you fully trust Autotune results and percentage of modification is low, you can modify [Autotune settings](#autotune-plugin-settings) "Automation Switch Profile" to enabled to automatically update and activate profile tuned after calculation. - -Note: if you want to automatically tune profiles for specific days of the week (for example a profile for "Weekend days" and another one for "Working days"), then create one rule for each profile, select the same days in Trigger and in Autotune Action, Tune days must be high enough to be sure tuning will be done with at least 6 or 8 days, and don't forget to select time after 4AM in trigger... - -- See below an example of rule to tune "my profile" on all "Working days" with 14 Tune days selected (so only 10 days included in autotune calculation). - -![Autotune default screen](../images/Autotune/Autotune_20b.png) - - - -## Tips and trick's - -Autotune works with information existing in your database, so if you just installed AAPS on a new phone, you will have to wait several days before being able to launch Autotune with enough days to get relevant results; - -Autotune is just an help, it's important to regularly check if you agree with calculated profile. If you have any doubt, change Autotune settings (for example the number of days) or copy results in local profile and adjust profile before using it. - -Always use Autotune several days manually to check results before applyling them. And it's only when you fully trust Autotune results, and when variation becomes tiny between previous profile and calculated profile than you start to use Automation (Never before) - -- Autotune can work very well for some users and not for others, so **If you don't trust Autotune result, don't use it** - -It's also important to analyse Autotune results to understand (or try to understand) why Autotune propose these modifications - -- you can have a whole increase or decrease of the strength of your profile (for example increase of total basal associated to decrease of ISF and IC values). it could be associated to several following days with autosens correction above 100% (more agressivity required) or below 100% (you are more sensitive) -- Sometimes Autotune propose a different balance between basal rates and IC/ISF (for ex lower basal and more aggressive IC/ISF) - -We advise to not use Autotune in the following cases: - -- You don't enter all your carbs - - If you don't enter carbs correction for an hypoglycemia, Autotune will see an unexcepted increase of your BG value and will increase your basal rates the ' hours earlier, it could be the opposite of what you need to avoid hypo, especially if it's in the middle of the night. That's why it's important to enter all carabs especially correction for hypo. -- You have a lot of period with UAM detected during the day. - - Do you have entered all your carbs and correctly estimated your Carbs ? - - All UAM periods (except if you enter no carbs during a day and categorized UAM as basal is disabled), all your UAM periods will be categorized as basal, this can increase a lot your basal (much more than necessary) - -- Your carbs absorption is very slow: if most of your carbs absorption are calculated with min_5m_carbimpact parameter (you can see these periods with a little orange dot in the top of COB curve), the calculation of COB could be wrong and leads to wrong results. - - We you practice sport, you are generally more sensitive and your BG doesn't rise a lot, so during or after an exercice, it's usual to see some periods with slow carbs. But if you have too often unexpected slow carb absorption, then you may need a profile adjustment (higher value of IC) or a min_5m_carbimpact a bit to high. -- You have a "very bad days", for example stuck several hours in hyperglycemia with a huge amount of insulin to be able to go down within the range, or after a sensor change you got long periods of wrong BG values. -- If the percentage of modification is too important - - You can try to increase the number of days to get smoother results \ No newline at end of file diff --git a/docs/CROWDIN/cs/Usage/making-sport-with-AAPS.md b/docs/CROWDIN/cs/Usage/making-sport-with-AAPS.md deleted file mode 100644 index 79d2f1c38223..000000000000 --- a/docs/CROWDIN/cs/Usage/making-sport-with-AAPS.md +++ /dev/null @@ -1,185 +0,0 @@ -# making sport with AAPS - -In this section we want to address the topic of sport with AAPS. - -The aim is to show you how AAPS can help you to continue doing your favorite sport more easily or even to start doing it. It is relatively common for new type 1 diabetics to ask whether exercise is still possible for them, even if the answer in the training courses is actually a clear yes. Exercise is not only good for healthy people, but also for type 1 diabetics and even moderate exercise can even help to stabilize the blood sugar curve overall. - -:::{admonition} consult with your diabetes team after reading - -::: - -The difficulty here is that the prerequisites that someone brings with them and the expectations of what sport means to them are very different. - -Since we can assume that experienced top athletes with T1D who use AAPS are unlikely to look it up here, we deliberately set the bar low for ourselves when writing and for you when reading and using it, so that as many people as possible can benefit from it. - -Since even sport as a category is far too imprecise, as the effects of endurance sports differ greatly from strength training, for example, we are trying to break it down by type of sport. - -To be concrete and give you something you can test yourself we arrange the explanaiton around a concrete example and explain to you they action, reactions and effects. - -:::{admonition} more examples wanted - -The focus should always be on how others can do sport and not on the top performance someone has achieved. - -It's really about the basics. Your experience, which you share here, can help others to pursue their beloved sport more quickly and successfully and is therefore important. -::: - -## Cycling - -:::{admonition} take a friend with you - at least on your first trials -:class: information -A gerneral very good idea can be to take a good friend with you on the first rides. -This is especially important if you are not experienced in T1D. -Always keep in mind please: arrival comes before speed! Safety for you and the others in road traffic is very, very important. -::: - -### Example - -Let's take about 60 minutes of cycling on a flat route with a moderate heart rate as an example. - -1. we take a flat route in order to have an even load for the first exercise. This is not about performance, but purely about learning how you should react to changes in blood glucose. -2. we take the heart rate as an indicator of the load, as it is easy to see whether you are under load or not. -3. we set ourselves the goal of doing a relaxed lap around the neighborhood and focus on staying within our target range during the lap. In my case, this would be 70 <= x <= 180 mg/dl. - -We **don't** take the speed, as this is heavily dependent on personal physical conditions as well as the bike and surface used. It is therefore not very meaningful. - -You should know from the diabetes training courses you have attended that during endurance sports cycling, the insulin active in the body works significantly better than during times without physical exertion. The insulin active in the body is referred to as insulin on board (IoB). It is our most important parameter when cycling with T1D. - -We try to keep the IoB as low as possible at the start and during exercise. IoB should be around 0 or even slightly negative. You can get it there by not eating 3-4 hours before exercise. In the beginning it can also be helpful to exercise in the morning before breakfast, as with the right profile you should always have around 0 for IoB in the morning. - -AAPS shows us the IoB value on the home screen on the left under the blood glucose value. - -![IoB](../images/cycling_20240104-174035.png) - -:::{admonition} ignoring the IoB rule increases the risk for roller coaster BG dramatically -:class: danger -If you ignore this rule, you can still go cycling, but it will be much more difficult to keep your blood sugar levels in balance, so it is better to save this for later tests after several successful simple tests. -::: - -As you should know from the diabetes training courses, you should reduce the basal rate during exercise. The factor is individual. I have found a value of 50% in tests to be suitable for me. - -In AAPS, you should therefore change your profile to 50% before exercise and keep it active until the end of exercise. Some people even do it a certain amount of time before, e.g. 1 hour. Unfortunately, the pre-run is also individual. We will come to the post-run later. - -You should use two carbohydrates during exercise. - -1. medium-fast carbohydrates for the insulin still in the body and -2. very fast carbohydrates to prevent slipping into a hypo. - -For medium-fast carbohydrates, I treat myself to cookies or a banana before exercise, for example. You can also use something else that is more suitable for you. -For very fast carbohydrates, I take 3 teaspoons of dissolved glucose per 100 ml of still water in a 500 ml water bottle on my bike. If I'm cycling longer distances, I take a larger bottle with me and, if necessary, packaged glucose to refill the bottle. I add a little lemon juice for flavor. You can also use something other than lemon juice for the taste. You shouldn't change anything about the dextrose, as dissolved dextrose raises blood sugar levels super quickly. If you only take it in sips, your blood sugar won't go super high either! You can also do this tip at home beforehand as a dry run and see how quickly the change shows up on the CGMS. - -Why do I place so much emphasis on fast carbohydrates? - -1. once you are in a slight hypo, you may get back into the normal range by drinking the dextrose solution. As a rule, however, the oscillation of the curve then begins, which leads to a rollercoaster ride of the blood sugar. You may even be able to keep this within your target range, but you must be constantly vigilant. Without a hypo it is simply the most stable. -2. if you even slip into a somewhat severe hypo (without the need for outside help, of course), you may even have to pause briefly to avoid getting stuck in the hypo. - With both hypos, there is a risk that you will be tempted to switch from drinking 2-3 sips at a time to larger quantities. Not too bad at first, until the oscillation sets in and pushes you into a hyper. You can correct this, but your blood sugar will most likely go on a rollercoaster ride. - -What else is helpful, but not absolutely necessary? -It is important to keep an eye on your blood sugar, as your blood sugar can change enormously (e.g. 30 - 50 mg/dl) within 15 minutes of riding and a little more IoB or a basal rate that is still too high. The best way to keep an eye on it is if it is visible on the handlebars or if it is also displayed on your watch. It is even possible to install an additional app on some Garmin GPS bike computers that displays the blood glucose from XDrip or Nightscout as a data field on the bike computer. The additional app was developed by Andreas May from the T1D community. It is available free of charge in the official connect IQ Store. Certainly an interesting option for riders interested in sports. - -[Link to Andreas May Data Field App on connect IQ store](https://apps.garmin.com/de-DE/apps/5a3e2cda-12f0-4afd-88ed-000e67a68d84) - -Here is a picture of my Garmin Edge 530 bike computer with map, blood sugar and heart rate. - -![Garmin Edge 530 with BG data field](../images/cycling_IMG_1087.jpeg) - -After you have eaten the medium fast carbohydrates (24 - 36 g I take) and the blood sugar is above 100 mg/dl but also below 160 mg/dl, I carry out the profile change to 50% and set the activity temp target. - -:::{admonition} disable SMBs during high temp targets if necessary -:class: danger -Attention: If you prefer not to receive SMBs during the sport, please disable the option "Enable SMB with hight temp targets" in the settings of SMB or DynIFS Plugin. -::: - -The following picture shows the start and end of the sport. The end was specified as the duration when the profile was changed at the start. - -The temporary profile change has the following effects - -1. for a period of 60 minutes -2. a reduction to 50% of the profile and -3. the target is raised by clicking on the Activity Target option, which may have the side effect of disabling the SMBs - see above. - -![profile switch with temp target](../images/cycling_20240104-174056.png) - -The second image shows that the start at IoB was started towards 0. - -![IoB around 0](../images/cycling_20240104-174111.png) - -If the blood sugar drops faster than 15 mg/dl in 5 minutes or if it is at 120 mg/dl and tends to fall, I drink 1-2 sips of dissolved glucose. Then I wait for the next value and proceed as described above. - -You can hardly see it here, but at the beginning I took 2 sips from the bottle several times when my blood sugar started to fall. When it stabilized, I didn't need any more glucose. - -Here is the picture that illustrates this. The chart is saved on the Garmin as a result of the activity. - -![BG chart Garmin](../images/cycling_20240104-174431.png) - -If you should suddenly break out upwards, i.e. above 180 mg/dl, you should consider whether you should make a correction bolus. Caution: Remember the factor and apply it to the correction, otherwise the correction will be too strong. - -If your blood sugar drops below 80 mg/dl, take a break and drink two sips until your blood sugar is back above 100 mg/dl. - -At the end of the ride, the profile change should be finished as the time is up. - -Since we only rode easy for 60 minutes, there shouldn't be a big muscle bulking effect continuing to pull carbohydrates from your blood sugar. However, if it felt strenuous to you, keep an eye on it. This is especially true if you then go straight to bed. It may be better to change your profile to e.g. 80% for sleep. You may come out of sleep slightly too high, but it's better than having a hypo at night. Over time, you will surely find out what happens to you. - -The following pictures show the low intensity of the sport. - -The elevation profile -![](../images/cycling_20240104-174314.png) - -Speed with average and maximum speed - -![](../images/cycling_20240104-174326.png) - -Note the pause at the level crossing, which is also reflected in the heart rate. - -The heart rate. -![](../images/cycling_20240104-174337.png) - -The training effect. -![](../images/cycling_20240104-174358.png) - -The time in the different heart rate training zones. -![](../images/cycling_20240104-174423.png) - -After succesfully mastering this simple example you could go for further targets by stretching - -1. the distance and time -2. the load during the ride -3. the elevation during the right which should make a big impact on the more necessary carbs or further reduction of IoB and percentage of profile switch. - -Based on my experiences I would not expect to come back 100% with time in range over the whole and every ride. - -### Tipps - -I already gave some tipps for during the ride above. - -Here are some further tipps what can go wrong and how you can act to prevent it or react to compensate it. - -#### sky rocket high after ride - -During the ride everything was fine but after siting down and relax the blood sugar go sky rocket high. - -**Possible reason:** This happens when you have drunk too much dissolved glucose. - -**Reaction:** Drink 500 ml water, go to the shower and then control again. Latest after 30 minutes think about giving a correction bolus but be careful when it is short for bed time. Therefore it can be very good to make the first try runs on weekend mornings. - -**Action:** Next time be a bit more cautious in drinking from the dissolved glucose. - -#### hypo during ride - -During the ride you are going into hypo and can't recover your blood sugar during cycling. - -**Possible reason:** Your body cannot absorb enough carbohydrates quickly enough during exercise. - -**Reaction:** Take a rest and corrrect your blood sugar with drinking dissolved glucose. Stay calm: arrival comes before speed. - -**Action:** Did you started with IoB near 0? Have you eaten a small amount of middle fast carbs? Can you increase this or are the not fast enough for your body? Is it possible to prevent going into hypo by reducing the factor for the profile switch? Have you disbaled SMBs during ride as explained above? - -#### sky rocket high during ride - -During the ride your blood sugar goes sky rocket high. - -**Possible reason:** You have got taken too much carbs for your IoB at that time. Beneath for sure the typical technical problems with your -insulin pump like leakage or blockage of the catheder! - -**Reaction:** If it is too high for you take a rest and correct with a bolus. Keep in mind that you must ride home and therefore make it carefully. Drink 500 ml pure water without carbs. Stay calm: arrival comes before speed. - -**Action:** Have you eaten too much? Especially have you drunk too much from the dissolved glucose during the ride? Is your percentage of reduction the profile during profile switch too low and you can increase this? diff --git a/docs/CROWDIN/cs/Where-To-Go-For-Help/How-to-get-support.md b/docs/CROWDIN/cs/Where-To-Go-For-Help/How-to-get-support.md deleted file mode 100644 index e43a93c44161..000000000000 --- a/docs/CROWDIN/cs/Where-To-Go-For-Help/How-to-get-support.md +++ /dev/null @@ -1,11 +0,0 @@ -# Jak získat podporu - -**Úroveň 1:** Wiki - nyní máme i vyhledávání! - -**Úroveň 2:** [Facebook](https://www.facebook.com/groups/AndroidAPSUsers/) nebo [gitter](https://gitter.im/MilosKozak/AndroidAPS) - -**Úroveň 3:** Gitter (pokud nezískáte odpověď na FB. Vyčkejte alespoň pár hodin !!! Vícenásobné příspěvky budou ignorovány nebo vymazány v obou kanálech) - -**Úroveň 4:** Vytvořte Issue (nahlášení problému), přiložte log a čas problému - -**Úroveň 5:** Osobní zpráva (pouze pokud je třeba sdílet osobní data, která by neměla být zveřejněna) \ No newline at end of file diff --git a/docs/CROWDIN/cs/buildingAAPS.md b/docs/CROWDIN/cs/buildingAAPS.md deleted file mode 100644 index 98164a09e49b..000000000000 --- a/docs/CROWDIN/cs/buildingAAPS.md +++ /dev/null @@ -1,28 +0,0 @@ -# Dummy - -## This is a dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - - -## This is another dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - - -## This is another another dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - diff --git a/docs/CROWDIN/cs/completingObjetives.md b/docs/CROWDIN/cs/completingObjetives.md deleted file mode 100644 index 98164a09e49b..000000000000 --- a/docs/CROWDIN/cs/completingObjetives.md +++ /dev/null @@ -1,28 +0,0 @@ -# Dummy - -## This is a dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - - -## This is another dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - - -## This is another another dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - diff --git a/docs/CROWDIN/cs/dummy.md b/docs/CROWDIN/cs/dummy.md deleted file mode 100644 index 98164a09e49b..000000000000 --- a/docs/CROWDIN/cs/dummy.md +++ /dev/null @@ -1,28 +0,0 @@ -# Dummy - -## This is a dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - - -## This is another dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - - -## This is another another dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - diff --git a/docs/CROWDIN/cs/intro.md b/docs/CROWDIN/cs/intro.md deleted file mode 100644 index 814a2bb834f3..000000000000 --- a/docs/CROWDIN/cs/intro.md +++ /dev/null @@ -1,291 +0,0 @@ -![20-06-23v2 AAPS simple overview-cropped](https://github.com/openaps/AndroidAPSdocs/assets/94044064/e505b73b-09a0-42a4-a1ab-b830a0741234) - -# Introduction to APS and AAPS - -## What is an “Artificial Pancreas System”? - -A human pancreas does a lot of things besides regulating blood sugar. However, the term **“Artificial Pancreas System” (APS)** usually refers to a system which works to automatically keep blood sugar levels within healthy limits. - -The most basic way to do this is by detecting **glucose levels**, using these values to do **calculations**, and then delivering the (predicted) right amount of **insulin** to the body. It repeats the calculation, every few minutes, 24/7. It uses **alarms** and **alerts** to inform the user if intervention or attention is needed. This system is typically made up of a **glucose sensor**, an **insulin pump** and an **app** on a phone. - -You can read more about the different artificial pancreas systems currently in use and in development in this 2022 review article: - -![Frontiers](./images/FRONTIERS_Logo_Grey_RGB.png) [Future Directions in Closed-Loop Technology](https://www.frontiersin.org/articles/10.3389/fendo.2022.919942/full#:~:text=Fully%20closed%2Dloop%20systems%2C%20unlike,user%20input%20for%20mealtime%20boluses). - -In the near future, some so-called "dual-hormone" systems will also have the ability to infuse glucagon alongside insulin, with the aim of preventing severe hypos and allowing even tighter blood glucose control. - -An artificial pancreas can be thought of as an [“autopilot for your diabetes”]. (https://www.artificialpancreasbook.com/) What does that mean? In an aircraft, an autopilot does not do the complete job of the human pilot, the pilot cannot sleep through the entire flight. The autopilot aids the work of the pilot. It relieves them of the burden of permanently monitoring the aircraft, allowing the pilot to concentrate on wider monitoring from time to time. The autopilot receives signals from various sensors, a computer evaluates them together with the pilot’s specifications and then makes the necessary adjustments, alerting the pilot to any concerns. The pilot no longer has to worry about constantly making decisions. - -## What does hybrid closed loop mean? - -The best solution for type 1 diabetes would be a “functional cure” (probably an implant of pancreatic cells which are protected from the immune system). While we are waiting for that, a “full closed loop” artificial pancreas is probably the next best thing. This is a tech system that doesn’t need any user input (like bolusing insulin for meals, or announcing exercise), with good regulation of blood glucose levels. At the moment, there are no widely available systems which are “full” closed loop, they all need some user input. The currently available systems are called “hybrid” closed loop, because they use a combination of automated technology and user input. - -## How and why did looping start? - -The development of commercial technology for people with type 1 diabetes (T1D) is very slow. In 2013 the T1D community founded the #WeAreNotWaiting movement. They developed systems themselves using existing approved technology (insulin pumps and sensors) to improve blood glucose control, safety, and quality of life. These are known as DIY (do-it-yourself) systems, because they are not formally approved by health bodies (FDA, NHS etc). There are four main DIY systems available: OpenAPS, **AAPS**, Loop and iAPS. - -A great way to understand the fundamentals of DIY looping is to read Dana Lewis’s book “Automated Insulin Delivery”. You can access it \[here\] (https://www.artificialpancreasbook.com/) for free (or buy a hardcopy of the book). If you want to understand more about OpenAPS, which** AAPS** has developed from, the \[OpenAPS website\] (https://openaps.org/what-is-openaps/) is also a great resource. - -Several commercial hybrid closed loop systems have been launched, the most recent of which are \[CamAPS FX\] (https://camdiab.com/) (UK and EU) and \[Omnipod 5\] (https://www.omnipod.com/en-gb/what-is-omnipod/omnipod-5) (USA and EU). These are very different to DIY systems, mainly because they both include a “learning algorithm” which adjusts how much insulin is delivered according to your insulin needs from previous days. Many people in the DIY community have already tried out these commercial systems and compared them with their DIY system. You can find out more about how the different systems compare by asking on the dedicated Facebook groups for these systems, on the \[AAPS Facebook group\] (https://www.facebook.com/groups/AndroidAPSUsers/) or on \[Discord\] (https://discord.com/invite/4fQUWHZ4Mw). - -## What is Android APS (AAPS)? - -![image](https://github.com/openaps/AndroidAPSdocs/assets/94044064/0f089d96-b7ee-452a-aa9d-aae10ab58971) - -**Figure 1**. Basic outline of the Android APS (Artificial Pancreas System), AAPS. - -Android APS (AAPS) is a hybrid closed loop system, or Artificial Pancreas System (APS). It makes its insulin dosing calculations using established \[OpenAPS\] (https://openaps.org/) algorithms (a set of rules) developed by the #WeAreNotWaiting type 1 diabetes community. - -Since OpenAPS is only compatible with certain older insulin pumps, AAPS (which can be used with a wider range of insulin pumps) was developed in 2016 by Milos Kozak, for a family member with type 1 diabetes. Since those early days, **AAPS** has been continually developed and refined by a team of volunteer computer developers and other enthusiasts who have a connection to the type 1 diabetes world. Today, **AAPS** is used by approximately 10,000 people. It is a highly customisable and versatile system, and because it is open-source, it is also readily compatible with many other open-source diabetes softwares and platforms. The fundamental components of the current **AAPS** system are outlined in Figure 1 above. - -## What are the basic components of AAPS? - -The “brain” of AAPS is an **app** which you build yourself. There are detailed step-by-step instructions for this. You then install the **AAPS app** on a compatible **Android smartphone** (1). A number of users prefer their loop on a separate phone to their main phone. So, you don’t necessarily have to be using an Android phone for everything else in your life, just for running your AAPS loop. - -The **Android smartphone** will also need to have another app installed on it as well as **AAPS**, either a modified Dexcom app called build-your-own dexcom app (**BYODA**) or Xdrip+. This receives glucose data from a sensor (2) by bluetooth, and then sends the data internally on the phone to the **AAPS app**. - -The **AAPS app** uses a decision making process (**algorithm**) from OpenAPS. Beginners start out using the basic **oref0** algorithm, but it is possible to switch to using the newer **oref1** algorithm as you progress with AAPS. Which algorithm you use (oref0 or oref1), depends on which suits your specific situation best. In both cases, the algorithm takes into account multiple factors, and performs rapid calculations every time a new reading comes in from the sensor. The algorithm then sends instructions to the insulin pump (3) on how much insulin to deliver by bluetooth. All the information can be sent by mobile data or wifi to the internet. This data can also be shared with followers if desired, and/or collected for analysis. - -## What are the advantages of the AAPS system? - -The OpenAPS algorithm used by **AAPS** controls blood sugar levels in the absence of user input, according to the users’ defined parameters (important ones being basal rates, insulin sensitivity factors, insulin-to-carb ratios, duration of insulin activity etc.), reacting every 5 minutes to the new sensor data. Some of the reported advantages of using AAPS are extensive fine-tunable options, automations and increased transparency of the system for the patient/caregiver. This can result in better control over your (or your dependent’s) diabetes, which in turn may give improved quality of life and increased peace of mind. - -Practical advantages include: - -- **Hardware flexibility**: **AAPS** works with a wide range of insulin pumps and sensors. So for example, if you develop an allergy to Dexcom sensor patch glue, you could switch to using a Libre sensor instead. That offers flexibility as life changes. You don't have to rebuild, just tick a different box in the AAPS app to change your hardware. - -- **Highly customisable with wide parameters**: here are some examples of the possibilities with AAPS: a) The ability to set a lower glucose target 30 min before eating; you can set the target as low as 72 mg/dL (4.0 mmol/L). b) If you are insulin-resistant resulting in high blood sugars, **AAPS** allows you to set an **automation** rule to activate when BG rises above 8 mmol/L (144 mg/dL), switching to a 120% profile (resulting in an 20% increase in basal and strengthening of other factors too, compared to your normal **profile** setting). The automation will last according to the scheduled time you set. Such an automation could be set to only be active on certain days of the week, at certain times of day, and even at certain locations. c) If your child is on a trampoline with no advance notice, **AAPS** allows insulin suspension for a set time period, directly via the phone. d) After reconnecting a tubed pump which has been disconnected for swimming, AAPS will calculate the basal insulin you have missed while disconnected and deliver it carefully, according to your current BG. Any insulin not required can be overridden by just “cancelling” the missed basal. f) **AAPS** has the ability to set different profiles for different situations and easily switch between them. Features which make the algorithm quicker to bring down elevated BG (like supermicro boluses (“SMB”), unannounced meals, (“**UAM**”) can be set to only work during the daytime, if you are worried about night-time hypos. - - -These are all examples, the full range of features gives huge flexibility for daily life including sport, illness, hormone cycles etc. Ultimately, it is for the user to decide how to use this flexibility, and there is no one-size-fits-all automation for this. - -- **Remote monitoring**: there are multiple possible monitoring channels (Sugarmate, Dexcom Follow, Xdrip+, Android Auto etc.) which are useful for parents/carers and adults in certain scenarios (sleeping/driving) who need customisable alerts. In some apps (Xdrip+) you can also turn alarms off totally, which is great if you have a new sensor “soaking” or settling down that you don’t want to loop with yet. - -- **Remote control**: a significant advantage of **AAPS **over commercial systems is that it is possible for followers, using authenticated text (SMS) commands or via an app (Nightscout or NSClient) to send a wide range of commands back to the ****AAPS** **system. This is used extensively by parents of kids with type 1 diabetes who use AAPS. It is very useful in the playground, for example, if you want to pre-bolus for a snack from your own phone, and your child is busy playing. It is possible to monitor the system (e.g. Fitbit), send basic commands (e.g. Samsung Galaxy watch 4), or even run the entire AAPS system from a high-spec smartwatch (5) (e.g. LEMFO LEM14). In this last scenario, you don’t need to use a phone to run AAPS. As battery life on watches improves, this last option is likely to become increasingly attractive. - -- **No commercial constraints due to open application interfaces**: beyond the use of an open source approach, which allows the source code of **AAPS** to be viewed at any time, the general principle of providing open programming interfaces gives other developers the opportunity to contribute new ideas that allow users to live more easily with their diabetes. This is complementary to commercial systems which adopt the innovations from DIY, where interfaces are only made possible in return for licensing, thus preventing innovations in particular that are not-for-profit. Good examples for such integrations are NightScout, Nightscout Reporter, Xdrip+ M5 stack etc. - -- **Detailed app interface**: It is easy to keep track of things like: insulin levels, cannula age, sensor age, pump battery age, and many actions can be done through the **AAPS** app (priming the pump, disconnecting the pump etc.), instead of on the pump itself. - -- **Accessibility and affordability**: **AAPS** gives people who currently can’t afford to self-fund, or don’t have funding/insurance, access to a world-class hybrid closed looping system which is conceptually years ahead, in terms of development, of the commercial systems being offered by clinics. You currently need to have a Nightscout account to set up **AAPS**. Although the Nightscout account it not necessarily required after setup, many people continue to use Nightscout for collecting their data, and for remote control. So, although **AAPS **itself is free, setting up Nightscout through one of the various platforms may incur a fee (E0 - E12), depending on what level of support you want (see comparison table). **AAPS** works with a wide range of affordable (starting from approx E150) Android phones. In comparison, Loop currently costs around $80 a year for the Apple development licence and CamAPS FX costs around E80/month (as at 2023). - -- ****Support**: No automated insulin delivery system is perfect. Commercial and open-source systems share many common glitches in both communications and temporary hardware failure. There is a community of AAPS users on both Facebook and Discord and Github who designed, developed and are currently using **AAPS** all over the world. There are Facebook support groups and help from clinic/commercial companies for the commercial APS systems - it is worth speaking to the users, or former users of these systems to get feedback on the common glitches, the quality of the education programme and the level of ongoing support provided. - -- **Predictability, transparency and safety**: with no learning algorithm, **AAPS** is logical and in some respect, more predictable, which may make it easier to know when a setting is wrong, and to adjust it accordingly. You can see exactly what the system is doing, why it is doing it, and set its operational limits, which puts the control (and responsibility) in your hands. This can provide the user with confidence, and a sounder sleep. - -- **Access to advanced features through dev modes including full closed loop**: **AAPS **documentation focuses on the mainstream **“master”** branch of **AAPS**, however, research and development is going on all the time. More experienced users may wish to explore the experimental features in the **development** branch such as integration of Dexcom G7, and automatically adjusting insulin delivery according to short-term sensitivity changes (DYNISF), not having to bolus for meals, and generally trying to make life with type 1 diabetes as convenient as possible. - -- **Ability to contribute yourself to further improvements**: type 1 diabetes can be highly frustrating and isolating. Having control over your own diabetes tech, with the possibility to “pay it forward” as soon as you are making progress by helping others on their journey can be really rewarding. You can educate yourself, discover the roadblocks and look for and even contribute to new developments and the documentation. There will be others with the same quest to bounce ideas off and work with. This is the essence of #WeAreNotWaiting. - - -## How does AAPS compare to MDI and open looping? - -Multiple daily injections (MDI, a) usually involve giving an injection of a long-lasting insulin (e.g. Tresiba) once a day, with injections of faster-acting insulin (e.g. Novorapid, Fiasp) at mealtimes, or for corrections. Open pumping (b) involves using a pump to deliver basal at pre-programmed rates of rapid-acting insulin, and then boluses through the pump at mealtimes or for corrections. The basics of a looping system is that the App uses the glucose data to instruct the pump to stop insulin delivery when it predicts you are heading for a low, and to give you extra insulin if your glucose levels are rising and predicted to go too high (c). Although this is oversimplified, (mostly because hybrid closed looping has a lot of additional useful features) the key features of each system are shown in **Figure 2**. - -![image](https://github.com/openaps/AndroidAPSdocs/assets/94044064/4e7d8608-684d-4c69-9c61-88c9539f5d6f) - -**Figure 2**. Overview of (a) MDI, (b) open-loop pumping and (c) hybrid closed loop pumping - -## How does AAPS compare to other looping systems? - -At present there are four major open source closed loop systems available: OpenAPS, **AAPS**, \[Loop\] (https://loopkit.github.io/loopdocs/#what-is-loop) and iAPS, (formerly FreeAPS X). The features of the different systems are shown in the table below: - -| Devicestyp | Name | [Open APS](https://openaps.readthedocs.io/en/latest/) | [AAPS](https://wiki.aaps.app) | [Smyčka](https://loopkit.github.io/loopdocs/) | [iAPS](https://iaps.readthedocs.io/en/latest/) | -| ---------- | -------------------------------------------------------------------------------------------------------- | ----------------------------------------------------- | ------------------------------------------- | --------------------------------------------- | ---------------------------------------------- | -| PUMP | Older Medtronic | ![available](./images/available.png) | ![available](./images/available.png) | ![available](./images/available.png) | ![available](./images/available.png) | -| PUMP | Older Omnipod (Eros) | ![unavailable](./images/unavailable.png) | ![available](./images/available.png) | ![available](./images/available.png) | ![available](./images/available.png) | -| PUMP | Newer Omnipod (Dash) | ![unavailable](./images/unavailable.png) | ![available](./images/available.png) | ![available](./images/available.png) | ![available](./images/available.png) | -| PUMP | DANA R, DANA RS, DANA I | ![unavailable](./images/unavailable.png) | ![available](./images/available.png) | ![unavailable](./images/unavailable.png) | ![unavailable](./images/unavailable.png) | -| PUMP | Roche Combo, Insight | ![unavailable](./images/unavailable.png) | ![available](./images/available.png) | ![unavailable](./images/unavailable.png) | ![unavailable](./images/unavailable.png) | -| CGM | Dexcom G4, G5, G6 | ![available](./images/available.png) | ![available](./images/available.png) | ![available](./images/available.png) | ![available](./images/available.png) | -| CGM | Libre 1 (requires Miao Miao) | ![available](./images/available.png) | ![available](./images/available.png) | ![available](./images/available.png) | ![available](./images/available.png) | -| CGM | Libre 2 | ![available](./images/available.png) | ![available](./images/available.png) | ![available](./images/available.png) | ![available](./images/available.png) | -| CGM | Libre 3 | | ![unavailable](./images/unavailable.png) | --- | ![unavailable](./images/unavailable.png) | -| CGM | Medtronic Enlite | | --- | ![unavailable](./images/unavailable.png) | --- | -| CGM | [Dexcom G7](https://androidaps.readthedocs.io/en/latest/Hardware/DexcomG7.html) | | ![available](./images/available.png) (beta) | ![available](./images/available.png) | ![available](./images/available.png) | -| CGM | [Eversense](https://androidaps.readthedocs.io/en/latest/Hardware/Eversense.html) | | ![available](./images/available.png) | | ![available](./images/available.png) | -| CGM | [MM640g/MM630g](https://androidaps.readthedocs.io/en/latest/Hardware/MM640g.html) | | ![available](./images/available.png) | | ![available](./images/available.png) | -| CGM | [PocTech](https://androidaps.readthedocs.io/en/latest/Hardware/PocTech.html) | | ![available](./images/available.png) | | ![available](./images/available.png) | -| CGM | [Nightscout as BG Source](https://androidaps.readthedocs.io/en/latest/Hardware/CgmNightscoutUpload.html) | | ![available](./images/available.png) | | ![available](./images/available.png) | -| Phone | Android | ![available](./images/available.png) | ![available](./images/available.png) | ![unavailable](./images/unavailable.png) | ![unavailable](./images/unavailable.png) | -| Phone | iPhone | ![available](./images/available.png) | ![unavailable](./images/unavailable.png) | ![available](./images/available.png) | ![available](./images/available.png) | - -[OpenAPS](https://openaps.readthedocs.io/) was the first Open Source Closed Loop System. Používá malý počítač, jako je Raspberry Pi nebo Intel Edison. Both AndroidAPS (AAPS) and iAPS use the OpenAPS algorithms, whereas Loop uses a separate algorithm. You can read a comparison of iAPS and **AAPS** here. - -An international peer-reviewed consensus statement containing practical guidance on open source looping was written by and for health-care professionals, and published in a leading medical journal in 2022. It is well worth a read (including for your diabetes clinic) and summarises the main technical differences between the different open-source hybrid closed loop systems: - - Lancet Diabetes Endocrinol, 2022; 10: 58–74 - -[https://www.ncbi.nlm.nih.gov/pmc/articles/PMC8720075/](https://www.ncbi.nlm.nih.gov/pmc/articles/PMC8720075/) - -It is hard to get a “feel” for any system without using it, or talking to others who are using it, so do reach out to others on Facebook/Discord and ask. Most people find that AAPS is incredibly sophisticated in comparison to other hybrid closed loop systems (particularly the commercial systems), with a huge number of potentially customisable settings and features, discussed above. Some people can find this a little overwhelming in the beginning, but there is no rush to investigate all the possibilities at once, you can progress as slowly or as fast as you would like, and there is help available at every step of the way. - -## Does AAPS use artificial intelligence or any learning algorithm? - -Ne. **AAPS** does not have any complicated machine learning algorithms, multiple-parameter insulin response models, or differential equations. As such, the system is open and transparent in how it works, and has the ability to be understood not just by experts, but also by clinicians and patients. It also means that if you have a sharply varying schedule (maybe switching from a stressful week at work to a relaxing holiday) and are likely to need a significantly different amount of insulin, you can immediately switch **AAPS** to run a weaker/stronger profile. A ‘learning system’ will do this adjustment for you automatically, but is likely to take longer to adjust the insulin delivery. - -## Which system is right for me or my dependent? - -Practically, your choice of system is often restricted by which pump you already have, or can obtain from your medical provider, and your choice of phone (Apple or Android). If you don’t yet have a pump you have the biggest choice of systems. Technology is continually evolving, pumps are being discontinued and new pumps and sensors are being released. Most open-source systems work with the main sensors (Libre and Dexcom) or are quickly adapted to work with new sensors a year or so after they are released (with a bit of time delay for safety and stability testing). - -Most **AAPS **users report more time in range, HbA1c reductions, as well as quality of life improvements from having a system that can auto-adjust basal rates overnight during sleep, and this is true for most hybrid closed loop APS. Some people have a preference for a very simple system which is not very customisable (which means you may prefer a commercial system), and others find this lack of control very frustrating (you may prefer an open-source system). If you (or your dependent) are newly diagnosed, a common route is to get the hang of MDI plus sensor first, then progress to a pump which has the potential for looping, then to **AAPS**, but some people (especially small kids) may go straight to a pump. - -It is important to note that the **AAPS** user needs to be proactive to troubleshoot and fix problems themselves, with help from the community. This is a very different mindset to that when using a commercial system. With **AAPS** a user has more control, but also the responsibility, and needs to be comfortable with that. - -## Is it safe to use open-source systems like AAPS? - -A more accurate question is probably “is it safe compared to my current type 1 diabetes insulin delivery system?” since no method of insulin delivery is without risk. There are many checks and balances in place with **AAPS**. A recent paper looked at the use of**** AAPS ****in a computer simulated set-up, [https://www.liebertpub.com/doi/epub/10.1089/dia.2019.0375](https://www.liebertpub.com/doi/epub/10.1089/dia.2019.0375) which was an effective way to unobjectively trial how safe and effective the system is. More generally, it is estimated that over 10,000 individuals worldwide are using open-source automated-insulin delivery systems, and uptake continues to increase globally. - -Any device that uses radio communications could be hacked, and this is true for a non-looping insulin pump as well. Currently, we are not aware of anyone attempting to harm individuals by hacking their diabetes-related medical equipment. However, there are multiple ways to protect against such risks: - -1. In the pump settings, limit both the max bolus allowed and max temporary basal settings to amounts that you believe are safest. These are hard limits that we do not believe any malicious hacker could circumvent. - -2. Set your CGM alarms enabled for both highs and lows. - -3. Monitor your insulin delivery online. Nightscout users can set additional alarms to alert for a wide variety of conditions, including conditions that are much more likely to occur than a malicious attack. In addition to highs and lows, Nightscout can display diagnostic data useful for verifying that the pump is operating as desired, including current IOB, pump temporary basal history, pump bolus history. It can also be configured to proactively alert users to undesirable conditions, such as predicted highs and lows, low insulin reservoir, and low pump battery. - - -If a malicious attack was made on your insulin pump, these strategies would significantly mitigate the risk. Every potential **AAPS** user needs to weigh the risks associated with using **AAPS**, versus the risks of using a different system. - -## How can I approach discussing AAPS with my clinical team? - -Depending on the country - link to doctors section of docs - - Lancet Diabetes Endocrinol, 2022; 10: 58–74 - -[https://www.ncbi.nlm.nih.gov/pmc/articles/PMC8720075/](https://www.ncbi.nlm.nih.gov/pmc/articles/PMC8720075/) - -## Q: Why can’t I just download AAPS and use it straight away? - -The **AAPS** app is not provided in Google Play - you have to build it from source code by yourself for legal reasons. **AAPS** is unlicensed, meaning that it does not have approval by any regulatory body authority in any country. **AAPS**is deemed to be carrying out a medical experiment on yourself, and is carried out at the user’s own risk. - -Setting up the system requires patience, determination and the gradual development of technical knowledge. All the information and support can be found in these documents, elsewhere online, or from others who have already done it. It is estimated that over 2000 people have successfully built and are currently using **AAPS** worldwide. - -The developers of **AAPS**t ake safety incredibly seriously, and want others to have a good experience of using **AAPS**. That is why it is essential that every user (or carer, if the user is a child): - -- builds the AAPS system themself and works through the **objectives** so that they have reasonably good personalised settings and understand the basics of how AAPS ****works by the time they “close the loop”; - -- backs up their system by exporting and saving important files (like keystore and settings .json file) somewhere safe, so you can setup again quickly if needed; - -- updates to newer master versions as and when they become available; and - -- maintains and monitors the system to ensure it is working properly. - - -## Q: What is the connectivity of the AAPS system? - -**Figure 3 (below)** shows one example of the **AAPS** system for a user who do not require any followers interacting with the system: - -![potential AAPS connectivity setup with no followers](./images/intro03.png) - -**Figure 4 (below)** shows the full potential of the **AAPS** system for a user who has followers and requires a monitor and send adjust the system remotely (like a child with T1D): - -![potential AAPS connectivity setup with followers](./images/intro04.png) - -## Q: How does AAPS get continually developed and improved? - -Most **AAPS** users use the fully tested **master** version of AAPS, which has been tested for bugs and problems, before being released to the community. Behind the scenes, the developers try out new improvements, and test these out in “developer” (**dev**) versions of **AAPS** with a user community who are happy to do bug updates at short notice. If the improvements work well, they are then released as a new “master” version of **AAPS**. Any new master release is announced on the Facebook group, so that the mainstream **AAPS** users can read about and update to the new master version. - -Some experienced and confident **AAPS ** users conduct experiments with emerging technologies and with dev versions of the **AAPS** app, which can be interesting for the less adventurous users to read about, without having to do it themselves! People tend to share these experiments on the Facebook group too. - -You can read more about some of these experiments and discussion on emerging tech here: - -[https://www.diabettech.com/](https://www.diabettech.com/) - -[https://bionicwookie.com/](https://bionicwookie.com/) - -## Q: Who can benefit? - -| User Type | -| ------------------------------------------- | -| ✔️ type 1 diabetic | -| ✔️ caregiver or parent of a type 1 diabetic | -| ✔️ blind users type 1 diabetic | -| ✔️ *clincians and healthcare professionals | - -The above table assumes that the user has access to both continuous gluocse monitor and insulin pump. - -*All data from **AAPS** can be made available to healthcare professionals via data sharing platforms, including NightScout that provides logging and real time monitoring of CGM data, insulin delivery, carbohydrate entries, predictions and settings. Nightscout records include daily and weekly reports which can aid healthcare professionals' discussions with type 1 patients with more accurate data on glycemic control and any behavioural considerations. - -## Q: What benefits can I get? - -With investment of your time, **AAPS** can potentially lead to: - -- alleviating the stress and burden of managing type 1 diabetes; - -- reducing the multitude of mundane decisions that arise from type 1 diabetes; - -- the provision of personalised and dynamic insulin dosing based on real-time data which can cut down the need for hypo treatments and reduce hyperglycemia episodes; - -- an increased knowledge of insulin management and confidence to better fine tune your settings; - -- the ability to create automatic settings (**automations**) that are tailored to fit in with your lifestyle; - -- improved sleep quality and overall reduction in the frequency of nighttime interventions; - -- remote monitoring and administration of insulin delivery for caregivers of type 1 diabetics; and - -- streamlining of all your portable diabetic equipment (continuous glucose monitor and insulin portable devices) by replacing them with an android phone controlled by **AAPS**. - - -Ultimately,**AAPS** can empower individuals to better manage their diabetes resulting in stable blood sugars and improved long term health outcomes. - ---- - -## AAPS First Steps - -Welcome. This is an introduction to aid beginners getting started with **AAPS** (or commonly referred to as "looping"). - -## Safety - -“_With great powers comes great responsibilities…_” - -**AAPS** is designed with an extensive set of safety features with limits imposed and gradually removed with completion of the **objectives **(predominately made up of multiple choice questions). An **AAPS** feature will be unlocked as the Objectives are successfully completed. This process will gradually allow the user to migrate from Open Loop to Closed Loop. - -This has been done to achieve the best possible experience with **AAPS** in order to prevent common mistakes that new users tend to make when starting to loop. The safety parameters have been built upon typical errors and general trends **AAPS** developers have observed with new users. Mistakes can happen because the beginner is inexperienced and too eager to get started with AAPS or has overlooked the required materials. Do not worry, we have all been there! - -## Key Principles - -The key principles and concepts of looping must be understood by the user before using **AAPS**. This is achieved by investing your personal time into reading the **AAPS** documentation, and completing the Objectives which is aimed to provide you with a solid platform for safe and effective use of **AAPS**. The volume of **AAPS** documentation may seem overwhelming at first but be patient and trust the process - with the proper approach, you'll get there! The overall process will depend upon the beginner’s progress and completion of objectives can typically take between 6 to 9 weeks . - -## Plan for hiccups - -At the preliminary stages of **AAPS**, you should expect to experience some hiccups whilst trying to fine tune your settings. **AAPS**’ glitches cannot be flushed out until the system is used in everyday life. Please plan accordingly and allow a sensible amount of time to troubleshoot and resolve such issues. - -## Flexibility/Adaptability - -Success with **AAPS** requires a proactive approach, a willingness to reflect on the BG data and flexibility to make the necessary adjustments to **AAPS** in order to improve your outcomes. Just as it is nearly impossible to learn to play a sport by reading about the rules alone, the same can be said of **AAPS**. - -## Technology compatibility - -There are limitations with **AAPS** as it is accessible for only certain types of insulin pumps or CGMs, and some technology may not be available for use in various countries. In order to avoid any disappointment or frustrations, please read please read Component Set Up (Section INSERT). - -## App Build Time - -The time to build the **AAPS**(under Section INSERT) depends on your level of expertise and technical ability. Typically for inexperienced users, it can take up to half a day or a full day (with help from the community) in order to build the **AAPS**. The process will significantly speed up as you become more experienced at building the **AAPS**. To aid the build process there are sections dedicated for: -- list of questions and answers for frequent errors that are likely to occur under FAQs (Section K); -- “How to install AAPS? (Section INSERT) which includes Troubleshooting subsection. - -## Keystore & configurations settings a export file - -A “keystore” is a password encrypted file unique to your own copy of **AAPS**. Your android phone uses it to ensure that nobody else can upgrade your own copy without the keystore. In short, as part of the **AAPS** build, you should: - -- save the your keystore file (.jks file used to sign your app) in a safe place; -- keep a note of your password for your keystore file. - -By doing the above, this will ensure that you can use that exact same keystore file each time an updated version of **AAPS** is created. On average, there will be 2-3 AAPS updates required each year. - -In addition, **AAPS** provides the ability to export all your configuration settings. This ensures that you can safely recover your system while changing phones, upgrading/reinstalling the application with minimum disruption. - -## Troubleshootng - -Please feel free to reach out to the AAPS community if there is anything you feel unsure about - there is no such thing as a silly question! All users with various levels of experience are encouraged to ask questions as necessary. Response times to questions are usually quick, typically only a few hours due to the volume of **AAPS** users. - -a) check the documentation; b) ask AAPS facebook group (https://www.facebook.com/groups/AndroidAPSUsers); and c) ask our discord channel. - -## Section overview - -AAPS documentation is made up of the following Sections: - -[INSERT ONCE SECTIONS /SUB SECTIONS AGREED] ---- diff --git a/docs/CROWDIN/cs/maintaining.md b/docs/CROWDIN/cs/maintaining.md deleted file mode 100644 index 98164a09e49b..000000000000 --- a/docs/CROWDIN/cs/maintaining.md +++ /dev/null @@ -1,28 +0,0 @@ -# Dummy - -## This is a dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - - -## This is another dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - - -## This is another another dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - diff --git a/docs/CROWDIN/cs/optimizing.md b/docs/CROWDIN/cs/optimizing.md deleted file mode 100644 index 98164a09e49b..000000000000 --- a/docs/CROWDIN/cs/optimizing.md +++ /dev/null @@ -1,28 +0,0 @@ -# Dummy - -## This is a dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - - -## This is another dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - - -## This is another another dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - diff --git a/docs/CROWDIN/cs/prepairing.md b/docs/CROWDIN/cs/prepairing.md deleted file mode 100644 index d92fc002ce92..000000000000 --- a/docs/CROWDIN/cs/prepairing.md +++ /dev/null @@ -1,145 +0,0 @@ -# Prepairing - -## Guide to the Android APS doc - -### First Steps -Welcome. This is an introduction to aid beginners to the concept of Do-It-Yourself-APS (Android-Artificial-Pancreas-Systems “AAPS”) is commonly referred to as ‘looping’.. - -#### Safetys -“With great powers come great responsibilities…” - -AAPS is designed with an extensive set of safety features with limits imposed and gradually removed with completion of the [Objectives](https://androidaps.readthedocs.io/en/latest/Usage/Objectives.html) (predominately made up of multiple choice questions). An AAPS feature will be unlocked as the Objectives are successfully completed. This process will gradually allow the user to migrate from Open Loop to Closed Loop. - -This has been done to achieve the best possible experience with AAPS by preventing common mistakes new users tend to make when starting to loop. The safety parameters have been built upon typical errors and general trends AAPS developers have observed with new users. Mistakes can happen because the beginner is inexperienced and too eager to get started with AAPS or has overlooked the required materials. Do not worry, we have all been there! - -#### Key Principles - -The key principles and concepts of looping must be understood by the user before using AAPS. This is achieved by investing your personal time into reading the AAPS documentation, and completing the [Objectives](https://androidaps.readthedocs.io/en/latest/Usage/Objectives.html) which is aimed to provide you with a solid platform for safe and effective use of AAPS. The volume of AAPS documentation may seem overwhelming at first but be patient and trust the process - with the proper approach, you'll get there! The overall process will depend upon the beginner’s progress and completion of objectives which typically take between 6 to 9 weeks . - -#### Plan for hiccups - -At the preliminary stages of AAPS, you should expect to experience some hiccups whilst trying to fine tune your settings. AAPS’ glitches cannot be flushed out until the system is used in everyday life. Please plan accordingly and allow a sensible amount of time to troubleshoot and resolve such issues. - -#### Flexibility/Adaptability - -Success with AAPS requires a proactive approach, a willingness to reflect on the BG data and flexibility to make the necessary adjustments to AAPS in order to improve your outcomes. Just as it is nearly impossible to learn to play a sport by reading about the rules alone, the same can be said of AAPS. - -#### Technology compatibility -There are limitations with AAPS as it is accessible for only certain types of insulin pumps or CGMs, and some technology may not be available for use in various countries. In order to avoid any disappointment or frustrations, please read [Component Set Up (Section E).](https://androidaps.readthedocs.io/en/latest/Configuration/BG-Source.html) - -#### App Build time -The time to build the AAPS (under Section D) depends on your level of expertise and technical ability. Typically for inexperienced users, it can take up to half a day or a full day (with help from the community) in order to build the AAPS. The process will significantly speed up as you become more experienced at building the AAPS.  - -To aid the build process there are sections dedicated for: - -- list of questions and answers for frequent errors that are likely to occur under [FAQs (Section](https://androidaps.readthedocs.io/en/latest/Getting-Started/FAQ.html) K); - -- “[How to install AAPS](https://androidaps.readthedocs.io/en/latest/Installing-AndroidAPS/Building-APK.html)? (Section D) which includes [Troubleshooting](https://androidaps.readthedocs.io/en/latest/Usage/troubleshooting.html) subsection. - - -#### Keystore & configuration settings export  file - -A “keystore” is a password encrypted file unique to your own copy of AAPS. Your android phone uses it to ensure that nobody else can upgrade your own copy without the keystore.In short, as part of the AAPS build, you should: - -1. save the your keystore file (.jks file used to sign your app) in a safe place; - -2. keep a note of your password for your keystore file. - - -By doing the above, this will ensure that you can use that exact same keystore file each time an updated version of AAPS is created. On average, there will be 2-3 updates to the AAPS required each year. In addition, AAPS provides the ability to [export all your configuration settings](https://androidaps.readthedocs.io/en/latest/Usage/ExportImportSettings.html). This ensures that you can safely recover your system while changing phones, upgrading/reinstalling the application with minimum disruption.  - -#### Řešení problémů - -Please feel free to reach out to the AAPS community if there is anything you feel unsure about - there is no such thing as a silly question!  All users with various levels of experience are encouraged to ask questions as necessary. Response times to questions are usually quick, typically only a few hours due to the volume of AAPS users.  - -##### [check the documentation](https://androidaps.readthedocs.io/en/latest/index.html) - -##### [ask our facebook group](https://www.facebook.com/groups/AndroidAPSUsers/) - -##### [ask our discord channel](https://discord.com/channels/629952586895851530/629954570394533889) - -#### Section overview - -AAPS documentation is made up of the following Sections: - -##### [Getting started](https://androidaps.readthedocs.io/en/latest/Getting-Started/Safety-first.html) - -This is a must read to understand the general concept of what an artificial pancreas system is designed to do. - -##### [What do I need?](https://androidaps.readthedocs.io/en/latest/Module/module.html) - -This explains AAPS’ compatibility with CGMs (Continuous Glucose Monitors) and insulin pumps. It also provides a guide on the correct assembly of an AAPS system to ensure that it functions correctly in everyday life. - -##### How to install AAPS - -This section is the manual for building the AAPS. Strict adherence to the step-by-step instructions are required in order to successfully build the AAPS. Please take your time. - -##### [Component Setup](https://androidaps.readthedocs.io/en/latest/Configuration/BG-Source.html) - -This explains how to properly integrate each of the various different separate component parts into AAPS, as well as how to set them up to work as seamlessly as possible together. All components are listed under the separate sections: CGM/FGM, xDrip Settings, Pumps, Phones, Nightscout setup, and Smartwatches. The sensor (BG) values and control of the insulin pump are particularly important information to understand. - -##### Configuration - -This explains how to set and configure your ‘Profile’, ‘Insulin’, ‘BG Source’, ‘Pump’, ‘Sensitivity Detection’, ‘APS’, ‘Loop’, ‘Treatments’. - -##### AAPS Usage - -This section provides a breakdown of the features provided by AAPS. - -##### [General Hints](https://androidaps.readthedocs.io/en/latest/Usage/Timezone-traveling.html) - -Useful tricks on how to tackle looping issues such as time zones, and daylight saving (i.e. Spring Forward/ - Fall Back). - -##### [AAPS](https://androidaps.readthedocs.io/en/latest/Getting-Started/Screenshots.html) for Children - -This is designed for parents or caregivers who want to build an AAPS for their child. It also explains the extra features necessary in order to support and safely control your child’s AAPS remotely.

The concepts in this section should be fully understood in order to competently use this feature. - -##### Řešení problémů - -This section contains links to help solve issues when building or using AAPS. - -##### Nejčastější dotazy - -This section addresses specific questions which tend to come up when building or using AAPS. - -##### [Slovníček](https://androidaps.readthedocs.io/en/latest/Getting-Started/Glossary.html) - -This contains a list of the acronyms (or short-term names) or defined terms developed specifically for AAP (for instance, the terms ‘ISF’ or ‘TT’ have special meanings in AAPS). - -##### [Where to go for help](https://androidaps.readthedocs.io/en/latest/Where-To-Go-For-Help/Background-reading.html)? - -This section is aimed to provide new users with links on resources in order to get help including accessing community support made up of both new and experienced users who can clarify questions, and resolve the usual pitfalls that come with AAPS. - -##### For Clinicians - -This is a section for the clinicians who have expressed interest in open source artificial pancreas technology such as AAPS, or for patients who want to share such information with their clinicians. | - -## what are we going to build? - -### An Android Phone Application - -At the core, AAPS is an android application running from a phone. You are going to build it from scratch by installing tools to download the sourcecode and build the actual application. - -### A reporting server NightScout (or Tidepool) - -In order to fully use AAPS properly you will want to setup a nightscout server. It is used to collect data from AAPS over time and possibly communicate to the application. It is required for parents who want to oversee their children AAPS sessions. It is also key to share data between clinicians and patients to perform analysis over time. - -## How long will it take? - -## Who might AAPS not be suitable for? - -## Where can I get help? - -## Requirements - -### medical - -### technical - -### personal - -### CGMs - -### Insulin Pump - -### Reporting (NS, Tidepool) \ No newline at end of file diff --git a/docs/CROWDIN/de/Configuration/Dexcom.md b/docs/CROWDIN/de/Configuration/Dexcom.md deleted file mode 100644 index 5a5fe8fc9464..000000000000 --- a/docs/CROWDIN/de/Configuration/Dexcom.md +++ /dev/null @@ -1,32 +0,0 @@ -# Dexcom G6 - -## Grundsätzliches vorab - -* Folge den allgemeinen Empfehlungen zur ["CGM Hygiene"](../Configuration/BG-Source#cgm-hygiene). -* [Spzifische Hinweise zum Dexcom G6 und DIY Systemen](../Configuration/BG-Source#dexcom-g6-diy-systems) *Nutze für G6 Transmitter, die nach Mitte / Ende 2018 hergestellt wurden, eine der aktuellen [nightly build xDrip+ Versionen](https://github.com/NightscoutFoundation/xDrip/releases). Diese Transmitter haben eine neue Firmware und die letzte stabile Version von xDrip+ vom 10.01.2019 kann mit diesen noch nicht korrekt umgehen. - -## Sensor setzen - -Beim Setzen des Sensors darf die Setzhilfe nicht zu stark auf die Haut gedrückt werden, um Blutungen zu vermeiden. Der Sensorfaden sollte nicht mit Blut in Kontakt kommen. - -Nach dem Setzen des Sensors wird der Transmitter in den Halter auf dem Sensorpflaster eingeklickt. Achtung! Zuerst auf der rechteckigen Seite einführen und danach auf der runden Seite nach unten Drücken bis der Transmitter mit einem Klick einrastet. - -## Problembehandlung - -### Verbindungsprobleme - -Die Bluetooth-Verbindung kann durch andere Bluetooth-Geräte, die sich in der Nähe befinden, gestört werden, Solche Geräte können Blutzuckermessgeräte, Headsets, Tablets (iPad...) aber auch Küchengeräte wie Mikrowellen oder Cerankochfelder sein. In diesem Fall zeigt xdrip keine BZ-Werte an. Die Daten werden nachgetragen, so bald die Bluetooth-Verbindung wieder hergestellt wurde. - -### Sensorfehler - -Wenn Sensorfehler wiederholt auftreten, probiere den Sensor an einer anderen Körperstelle zu setzen. Der Sensorfaden sollte nicht mit Blut in Kontakt kommen. - -Oftmals kann ein Sensorfehler durch sofortiges Trinken und "Massage" an der Sensorsetzstelle beseitigt werden. - -### Springende Werte - -Versuche, die Einstellungen zum "noise blocking" in xDrip (Einstellungen -> Inter-App Einstellungen -> Verrauschungsunterdrückung) zu ändern, z.B. "Block Very High noise and worse". Siehe auch die Informationen zur [Glättung von BZ-Daten](../Usage/Smoothing-Blood-Glucose-Data-in-xDrip.md). - -### Neuer Transmitter bei laufendem Sensor - -Falls Du einen Transmitter bei einer laufenden Sensorsitzung wechseln musst, kannst Du versuchen, den Transmitter zu tauschen, ohne die Transmitterhalterung zu beschädigen. Eine Videoanleitung findest Du unter . \ No newline at end of file diff --git a/docs/CROWDIN/de/Configuration/EOFLOW.md b/docs/CROWDIN/de/Configuration/EOFLOW.md deleted file mode 100644 index e44ed26f61ce..000000000000 --- a/docs/CROWDIN/de/Configuration/EOFLOW.md +++ /dev/null @@ -1,155 +0,0 @@ -# EOPatch2 Instruction Manual - -The patch requires the use of rapid-acting U-100 type insulin, such as NovoRapid or Humalog. Use a rapid-acting insulin that is suitable for you according to your doctor’s prescription and inject the prescribed dosage. - -The smallest injectable dose of insulin when using the patch is 0.05 U. The Profile BAS should therefore be set at a minimum value of 0.05 U/hr or more and an interval of 0.05 U/hr, as otherwise there may be an error between the estimated total infusion amount in the Profile and the actual infusion amount in the patch. Likewise, the bolus must also be set and infused with a minimum infusion volume of 0.05 U. - -## Pump Setup -1. On the AndroidAPS home screen, click the hamburger menu in the upper left corner and go to Config Builder. -1. Select 'EOPatch2' in the Pump section. -1. Press the Back key to return to the home screen. - -![Bild1](../../images/EOPatch/Bild1.png) ![Bild2](../../images/EOPatch/Bild2.png) - -## Einstellungen -Select EOPATCH2 at the top of the home screen to go to the EOPATCH2 tab. - -Select the EOPatch2 Preferences menu by clicking the three dots in the upper right corner. - -The EOPatch2 Preferences menu offers a menu to set 3 types of notifications. - -### Low reservoir Alerts -A warning appears when the amount of insulin remaining in the reservoir reaches the set value or less while using the patch. It can be set from 10 to 50U in 5U increments. - -### Patch expiration Reminder -This is a reminder to notify you of the time remaining before the current patch expires. It can be set from 1 to 24 hours in 1 hour increments. The initial setting value is 4 hours. - -### Patch buzzer Reminder -This is a reminder function for injections other than basal injection. If you are using an (extended) bolus injection or a temporary basal injection, the patch will make a buzzer sound when the injection starts and when the injection is complete. The initial setting value is Off. - -![Bild3](../../images/EOPatch/Bild3.png) - -## Connecting the Patch - -### Move to patch connection screen - -Select EOPATCH2 at the top of the home screen and click the ACTIVATE PATCH button at the bottom left. - -![Bild4](../../images/EOPatch/Bild4.png) - -### Connecting the patch -Insert the syringe needle into the insulin inlet on the patch and then slowly push the piston to inject the insulin. When insulin is filled with more than 80U, the patch makes a booting sound (1 buzzer) and boots. After confirming the buzzer sound, click the START PAIRING button on the screen. - -[Warning] - -- Do not turn the needle action lever until instructed. It can cause serious problems during injection or safety checks otherwise. -- The amount of insulin that can be injected into the patch is 80~200U. If you inject less than 80U into the patch initially, the patch will not work. -- Take the insulin to be put into the patch from the refrigerator and leave it at room temperature for 15 to 30 minutes beforehand. The temperature of the insulin to be injected must be at least 10°C. - -![Bild5](../../images/EOPatch/Bild5.png) - -### patch pairing -The Patch pairing screen will be displayed, and pairing will be attempted automatically. If communication is successful, the Bluetooth pairing request notification appears. Click OK and when the Bluetooth pairing request notification appears a second time with the authentication code, select OK again. - -[Warning] - -- For pairing, the patch and the smartphone must be located within 30 cm of each other. -- After the patch booting is completed, the patch will beep every 3 minutes until the pairing is complete. -- After booting the patch, the patch application must be completed via the app within 60 minutes. If the application cannot be completed within 60 minutes, the patch should be discarded. - -![Bild6](../../images/EOPatch/Bild6.png) ![Bild7](../../images/EOPatch/Bild7.png) ![Bild8](../../images/EOPatch/Bild8.png) - - -### patch preparation -After removing the adhesive tape of the patch, check if the needle is sticking out. If there are no problems with the patch, click NEXT. - -![Bild9](../../images/EOPatch/Bild9.png) - -### Patch attachment -Insulin should be injected in a spot with subcutaneous fat but few nerves or blood vessels, so it is recommended to use the abdomen, arm, or thigh for the patch attachment site. Choose a patch attachment site and apply the patch after disinfecting the location. - -[Warning] - -- Make sure to straighten the side of the patch tape attached to the body evenly, so that the patch adheres completely to the skin. -- If the patch does not stick completely, air may enter between the patch and the skin, which can weaken the adhesive strength and waterproof effect of the patch. - -![Bild10](../../images/EOPatch/Bild10.png) - -### Safety Check -When patching is complete, touch Start Safety Check. When the safety check is completed, the patch will beep once. - -[Warning] - -- For safe use, do not turn the needle action lever until the safety check has been completed. - -![Bild11](../../images/EOPatch/Bild11.png) ![Bild12](../../images/EOPatch/Bild12.png) - - -### Inserting the needle -The needle is inserted by holding around the patch and turning the needle action lever more than 100° in the upward direction of the lever. There is a buzzer sound when the needle is inserted correctly. Turn the needle action lever further clockwise to release the lever. Click NEXT. - -[Caution] - -- If you go to the next step without the buzzer sounding, a needle insertion error warning will appear. - -## Discarding the patch -Patches must be replaced in the case of low insulin levels, usage expiration, and defects. The recommended usage period for each patch is 84 hours after booting the patch. - -### Discarding the patch -Select EOPATCH2 at the top of the home screen and click the DISCARD/CHANGE PATCH button at the bottom. On the next screen, click the DISCARD PATCH button. A dialog box appears to confirm once more and if you select the DISCARD PATCH button, the disposal is completed. - -![Bild13](../../images/EOPatch/Bild13.png) ![Bild14](../../images/EOPatch/Bild14.png) ![Bild15](../../images/EOPatch/Bild15.png) ![Bild16](../../images/EOPatch/Bild16.png) - -## Insulinlieferung stoppen und fortsetzen -Suspending insulin delivery also cancels both extended bolus and temporary basal. When resuming insulin delivery, the canceled extended bolus and temporary basal will not be resumed. And when insulin delivery is suspended, the patch will give a sound every 15 minutes. - -### Suspending insulin delivery -Select EOPATCH2 at the top of the home screen and click the SUSPEND button at the bottom right. When you select CONFIRM in the confirmation box, a time selection box appears. If you select the CONFIRM button after selecting the time, the insulin delivery will be suspended for the set amount of time. - -![Bild17](../../images/EOPatch/Bild17.png) ![Bild18](../../images/EOPatch/Bild18.png) ![Bild19](../../images/EOPatch/Bild19.png) - - -### Resuming insulin delivery -Select EOPATCH2 at the top of the home screen and click the RESUME button at the bottom right. Insulin delivery will resume by selecting CONFIRM in the confirmation dialog box. - -![Bild20](../../images/EOPatch/Bild20.png) ![Bild21](../../images/EOPatch/Bild21.png) - -## Alarms/Warnings - -### Alarm - -Alarms are issued for emergency situations of the highest priority and require immediate action. The alarm signal does not disappear or time out until it is acknowledged. An alarm occurs when there is a problem with the patch being used, so there may be cases where the patch in use needs to be discarded and replaced with a new patch. The warning is displayed as a dialog box and switching to another screen is not possible until processing is completed. - -![Bild22](../../images/EOPatch/Bild22.png) ![Bild23](../../images/EOPatch/Bild23.png) - -The different types of alarms are explained below. - -| Alarms | Explanation | -| -------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| Empty reservoir | Occurs when the patch’s reservoir runs out of insulin. | -| Patch expired | Occurs when the patch usage time has expired, and no further insulin injections are possible. | -| Occlusion | Occurs when it appears that the patch's insulin inlet is clogged. | -| Power on self-test failure | Occurs when the patch finds an unexpected error during the post-boot self-test process. | -| Inappropriate temperature | Occurs when the patch is outside the normal operating temperature range during patch application and use. To deal with this alarm, move the patch to an appropriate operating temperature (4.4 to 37°C) condition. | -| Needle insertion Error | Occurs when needle insertion is not normal during the patch application process. Check that the needle insertion edge of the patch and the needle activation button are in a straight line. | -| Patch battery Error | Occurs just before the patch’s internal battery runs out and powers off. | -| Patch activation Error | Occurs when the app fails to complete the patching process within 60 minutes after the patch is booted. | -| Patch Error | Occurs when the patch encounters an unexpected error while applying and using the patch. | - -### Warning - -A warning occurs in a medium or low-priority situation. When a warning occurs, it is displayed as a notification in the Overview screen. - -![Bild24](../../images/EOPatch/Bild24.png) - -The different types of warnings are explained below. - -| Warnings | Explanation | -| ---------------------------- | ------------------------------------------------------------------------------------------------------------------------------------- | -| End of insulin suspend | Occurs when the time set by the user has elapsed after the insulin infusion suspension has been completed. | -| Low reservoir | Occurs when the remaining amount of insulin in the patch is below the set amount. | -| Patch operating life expired | Occurs when the patch usage period is over. | -| Patch will expire soon | Occurs 1 hour before the patch must be discarded. | -| Incomplete Patch activation | Occurs when more than 3 minutes have elapsed due to an interruption during patch application in the stage after pairing is completed. | -| Patch battery low | Occurs when the patch's battery is low. | - diff --git a/docs/CROWDIN/de/Configuration/Hardware/index.md b/docs/CROWDIN/de/Configuration/Hardware/index.md deleted file mode 100644 index 95467d55c4b3..000000000000 --- a/docs/CROWDIN/de/Configuration/Hardware/index.md +++ /dev/null @@ -1,27 +0,0 @@ -# Hardwarekonfiguration - -## AndroidAPS einrichten - -## BZ-Quelle - -- [BZ Quelle](../BG-Source.md) -- [xDrip+ Einstellungen](../xDrip.md) -- [Dexcom G6 Hinweise](../Dexcom.md) -- [Glättung der Blut-Glukose-Daten](../../Usage/Smoothing-Blood-Glucose-Data-in-xDrip.md) - -## Pumpen - -- [Dana-R Pumpe](../DanaR-Insulin-Pump.md) -- [Dana-RS Pumpe](../DanaR-Insulin-Pump.md) -- [Accu-Chek Combo Pumpe](../Accu-Chek-Combo-Pump.md) -- [Accu-Chek Insight Pumpe](../Accu-Chek-Insight-Pump.md) -- [Medtronic Pumpe](../MedtronicPump.md) - -## Smartphones - -- [Jelly Pro Einstellungen](../../Usage/jelly.md) -- [Huawei Einstellungen](../../Usage/huawei.md) - -## Smartwatch - -- [Watchfaces](../Watchfaces.md) diff --git a/docs/CROWDIN/de/Getting-Started/ClosedLoop.md b/docs/CROWDIN/de/Getting-Started/ClosedLoop.md deleted file mode 100644 index a0ccbd67937e..000000000000 --- a/docs/CROWDIN/de/Getting-Started/ClosedLoop.md +++ /dev/null @@ -1,55 +0,0 @@ -# Was ist ein Closed Loop-System? - -![AAPS ist wie ein Autopilot](../images/autopilot.png) - -Ein Closed Loop System für eine künstliche Bauchspeicheldrüse kombiniert verschiedene Komponenten, um Dein Diabetes Management zu vereinfachen. In ihrem großartigen Buch [Automated Insulin Delivery](https://www.artificialpancreasbook.com/) bezeichnet Dana M. Lewis, eine der Gründerinnen der Open Source Closed Loop Bewegung, es als ["Autopilot für Deinen Diabetes"](https://www.artificialpancreasbook.com/3.-getting-started-with-your-aps). Aber was bedeutet das? - -**Autopilot in einem Flugzeug** - -Der Autopilot erledigt nicht den kompletten Job und gibt dem Piloten daher nicht die Möglichkeit, während des gesamten Fluges zu schlafen. Er erleichtert die Arbeit der Piloten. Er entlastet sie von der permanenten Überwachung des Flugzeugs und der Fluglage. Dadurch kann sich der Pilot auf die Überwachung des Luftraums und die Kontrolle der Funktionen des Autopiloten konzentrieren. - -Der Autopilot empfängt Signale von verschiedenen Sensoren, ein Computer wertet diese zusammen mit den Vorgaben der Piloten aus und nimmt dann die notwendigen Anpassungen vor. Der Pilot muss sich nicht mehr um die dauernden Justierungen kümmern. - -**Closed Loop System** - -Gleiches gilt für ein Closed Loop System für eine künstliche Bauchspeicheldrüse. Es macht nicht den kompletten Job für Dich, Du musst Dich weiter um Deinen Diabetes kümmern. Ein Closed Loop System kombiniert die Sensordaten aus einem CGM/FGM mit Deinen Vorgaben zum Diabetes Management wie Basalrate, Korrektur- und BE-Faktoren. Daraus errechnet es Behandlungsvorschläge und setzt diese permanenten kleinen Anpassungen um, um Deinen Diabetes im Zielbereich zu halten und Dich zu entlasten. So bleibt mehr Zeit für das Leben "neben" dem Diabetes. - -Genauso wenig wie Du in ein Flugzeug steigen willst, in dem nur noch der Autopilot ohne menschliche Überwachung fliegt, hilft Dir ein Closed Loop System bei Deinem Diabetes Management, benötigt aber immer Deine Unterstützung! **Auch mit einem Closed Loop kannst Du Deinen Diabetes nicht einfach vergessen!** - -So wie der Autopilot neben den Sensorwerten auf die Vorgaben der Piloten angewiesen ist, so braucht ein Closed Loop System passende Basalraten, Korrektur- und BE-Faktoren, um Dich erfolgreich unterstützen zu können. - -## Open Source Closed Loop System für eine künstliche Bauchspeicheldrüse - -Aktuell sind drei große Open Source Closed Loop Systeme verfügbar: - -### AndroidAPS (AAPS) - -AAPS is described in detail in [this documentation](./WhatisAndroidAPS.html). AAPS verwendet ein Android Smartphone für die Berechnungen und die Steuerung Deiner Insulinpumpe. AAPS steht in enger Verbindung mit OpenAPS, sie teilen z.B. die Oref Algorithmen. - -Kompatible [Insulinpumpen](../Hardware/pumps.md) sind: - -- [DanaR](../Configuration/DanaR-Insulin-Pump.md) / [DanaRS & Dana-i](../Configuration/DanaRS-Insulin-Pump.html) -- [Accu-Chek Combo](../Configuration/Accu-Chek-Combo-Pump.md) -- [Accu-Chek Insight](../Configuration/Accu-Chek-Insight-Pump.md) -- [Diaconn G8](../Configuration/DiaconnG8.md) -- [Omnipod DASH](../Configuration/OmnipodDASH.md) -- [Omnipod Eros](../Configuration/OmnipodEros.md) -- einige alte [Medtronic Pumpen](../Configuration/MedtronicPump.md) - -### OpenAPS - -[OpenAPS](https://openaps.readthedocs.io) war das erste Open Source Closed Loop System. OpenAPS verwendet einen kleinen Computer wie Raspberry Pi oder Intel Edison. - -Kompatible Insulinpumpen sind: - -- einige alte Medtronic Pumpen - -### Loop für iOS - -[Loop for iOS](https://loopkit.github.io/loopdocs/) ist ein Open Source Closed Loop System für iPhones von Apple. - -Kompatible Insulinpumpen sind: - -- Omnipod DASH -- Omnipod Eros -- einige alte Medtronic Pumpen diff --git a/docs/CROWDIN/de/Getting-Started/GlossaryTest.md b/docs/CROWDIN/de/Getting-Started/GlossaryTest.md deleted file mode 100644 index 8a93dd949496..000000000000 --- a/docs/CROWDIN/de/Getting-Started/GlossaryTest.md +++ /dev/null @@ -1,391 +0,0 @@ -# Glossar - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
BegriffBeschreibungsiehe auchweitere Informationen
AAPSAndroidAPS - System einer künstlichen Bauchspeicheldrüse (artifical pancreas system)  
AMAerweiterter Mahlzeiten-Assistent (advanced meal assist) - erweiterte Algorithmus zum Umgang mit KohlenhydratenMA / SMBWiki - AMA
Android autoAnzeige von AAPS Benachrichtigungen auf kompatiblen Kfz-Multimedia-Systemen Wiki - android auto
APKAndroid Installations-Datei (Android application package) Wiki - APK aus Quellcode erstellen
AutosensErmittlung der Änderung der Insulinempfindlichkeit durch Bewegung, Hormone etc. DIABETTECH - Autosens (englisch)
AzureCloud Computing-Plattform zum Hosten der Nightscout-DatenHeroko / NightscoutAzure
BATStatusanzeige niedriger Batteriestand auf dem StartbildschirmCAN / RES / SENEinstellungen
AAPS-Bildschirme
BZBlutzucker  
BGIblood glucose interaction - erwartete BZ-Änderung allein auf Basis des aktiven Insulins  
BZ-QuelleWoher kommen Deine Blutzucker-Werte?CGM / FGMWiki - BZ-Quelle
Blukon NightreaderBluetooth-Sender, um das Freestyle Libre als CGM zu verwendenBlueReader / MiaoMiaoAmbrosia Blukon Nightreader
BRBasalrate  
CAGEKanülenalter (canula age) - Wird in Nightscout angezeigt, wenn die Information in AAPS im Aktionen Tab/Menü oder durch AAPS Tab Aktionen -> Vorfüllen/Füllen eingetragen wurde.Nightscout 
CANStatusanzeige Kanülenwechsel auf dem StartbildschirmBAT / RES / SENEinstellungen
AAPS-Bildschirme
CGMkontinuierliche Glukosemessung (continuous glucose monitor)  
Closed LoopClosed-loop-Systeme passen die Basalrate basierend auf einem Algorithmus automatisch an ohne dass der Nutzer eingreifen muss.Open LoopWiki closed loop
COBcarbs on board (aktive Kohlenhydrate)  
DIAInsulinwirkdauer (duration of insulin action) Wiki Insulintypen
DIABETTECH - DIA (englisch)
DSTSommerzeit (daylight savings time) Wiki Zeitumstellung
eCarbsverzögerte Kohlenhydrate (extended carbs) - Kohlenhydrate, die über mehrere Stunden aufgeteilt werden (z.B. hoher Fett- oder Proteinanteil)
Der verlängerte Bolus, den du vielleicht aus der klassischen Pumpentherapie kennst, macht beim Loopen wenig Sinn.		SMBWiki - verzögerte Kohlenhydrate (eCarbs)
eCarbs Anwendungsfall (englisch)
FGMFlash-Glukose-Monitor (Freestyle Libre) Wiki - BZ-Quelle
gitVersionskontrollsystem für die Nachverfolgung von Änderungen in Computerdateien und Koordinierung der Arbeit an diese Dateien
-> für APK-Updates notwendig		 Wiki - Update auf neue Version...
Githubwebbasierter Hosting-Dienst für die Versionskontrolle mit Git
-> Speicherort des Quellcodes		 Github AndroidAPS
GlimpApp mit der Werte vom Freestyle Libre empfangen werden können Nightscout mit Glimp (englisch)
HerokuCloud Computing-Plattform zum Hosten der Nightscout-DatenAzure / NightscoutHeroku
IC (oder I:C)Kohlenhydrat-Faktor (insulin to carb ratio) - Wie viele Gramm Kohlenhydrate können mit einer Einheit Insulin abgedeckt werden?  
IOBim Körper aktives Insulin (insulin on board)  
ISFKorrekturfaktor (insulin sensifity factor) - Erwartete BZ-Senkung durch eine Einheit Insulin.  
LGSLow Glucose Suspend (Reduzierung der Baslarate bei niedrigen Glukosewerten)
AAPS wird die Basalrate reduzieren, wenn die BZ-Werte zu stark sinken. Wenn die BZ-Werte aber steigen, wird AAPS die Basalrate nur dann erhöhen, wenn negatives Insulin on board (von einer vorangegangenen Basalratenreduzierung) ist. Sonst bleibt die Basalrate wie in Deinem Profil eingestellt. Wenn du eine Hypo korrigierst, kann es vorkommen, dass danach Spitzen auftreten, die du nicht durch Erhöhung der Basalrate korrigieren kannst.		Ziel 6 
LineageOSfreies OpenSource Betriebssystem für Smartphones und andere Geräte
alternatives Betriebssystem für Smartphones, auf denen Android 8.1 (Oreo) nicht betrieben werden kann
(bei Benutzung der Accu-Chek Combo)		 Wiki - Akku-Chek Combo Pumpe
LogdateienAufzeichnung aller AAPS Aktionen (nützlich für Fehlersuche und -beseitigung) Wiki - Logfiles erhalten
maxIOBSicherheitsfunktion - Wert für maximales aktives Insulin im Körper, der von AAPS nicht überschritten werden kann Wiki - maxIOB
Wiki - SMB
MiaoMiaoBluetooth-Sender, um das Freestyle Libre als CGM zu verwendenBlueReader / Blukon NightreaderMiaoMiao
min_5m_carbimpactSicherheitsfunktion - Standardzeitangabe für den Abbau der Kohlenhydrate. Wird verwendet wenn dieser nicht durch die Veränderung der BZ-Werte dynamisch ermittelt werden kann. Wiki - Konfigurations-Generator
NightscoutOpen Source Projekt zur Anzeige der und für Berichte zu den CGM-DatenNightscout ReporterNightscout
NS Client Einstellungen für die Synchronisation deiner AndroidAPS Daten mit NightscoutTeil von AAPS zur Verbindung mit Deiner Nightscout-Seite Wiki - NS Client
Nightscout ReporterTool eines Mitloopers zur Erstellung von PDF-Berichten auf Basis der Nightscout-DatenNightscoutNightscout Reporter
NS Reporter bei Facebook
Objectives (Ziele)Ziele - Lenrprogramm innerhalb von AAPS um Dich Schritt für Schritt vom Open Loop zum Closed Loop zu führen. Wiki - Objectives (Ziele)
OpenAPSopen artificial pancreas system
APS run on small computers (i.e. Raspberry Pie)
AAPS uses some of the OpenAPS features		 OpenAPS docs (englisch)
Open LoopOpen-loop-Systeme machen Vorschläge zur Anpassung der Basalrate basierend auf einem Algorithmus. Diese müssen vom Nutzer händisch in der Pumpe umgesetzt werden.Closed LoopWiki - Konfigurations-Generator
Oref0 / Oref1Empfindlichkeitserkennung
"reference design implementation version 0/1" - der Schlüsselalgorithmus von OpenAPS		 Wiki - Empfindlichkeitserkennung...
Peak time (Wirkungshoch)Zeitpunkt des Wirkungshochs des gespritzen Insulins Wiki - Konfigurations-Generator
PHPumpenhistorie (Eintrag im Behandlungs-Tab) Screenshots
Predictions (Vorhersagen)Vorhersage der BZ-Werte basierend auf verschiedenen Berechnungsannahmen Wiki - Vorhersagelinien
Profilegrundlegende Behandlungseinstellungen (Basalrate, DIA, IC, ISF, BZ-Zielbereich)
kann lokal auf dem Gerät oder über Nightscout eingerichtet werden		NightscoutWiki - Profil
Profilwechsel(vorübergehende) Änderung des verwendeten Profils oder dessen prozentuale Absenkung/Anhebung Wiki - Profil Wechsel
RESStatusanzeige Reservoirwechsel auf dem StartbildschirmBAT / CAN / SENEinstellungen
AAPS-Bildschirme
RileyLinkOpen Source Hardware zur Umwandlung von Bluetooth Low Energy (BLE) in 916 MHz Funksignale (wird für ältere Medtronic-Pumpen verwendet)OpenAPS 
SAGESensoralter (sensor age) - Wird in Nightscout angezeigt, wenn die Information in AAPS im Aktionen Tab/Menü eingetragen wurde.Nightscout 
SENStatusanzeige Sensorwechsel auf dem StartbildschirmBAT / CAN / RESEinstellungen
AAPS-Bildschirme
SensitivitätserkennungErmittlung der Änderung der Insulinempfindlichkeit durch Bewegung, Hormone etc. DIABETTECH - Autosens (englisch)
Sensor noiseSensorrauschen - instabile CGM-Werte die zu "springenden" BZ-Werten führen Wiki - Sensorrauschen
SMBsuper micro bolus
erweiterte Bolusfunktion für schnellere Anpassung des BZ		UAMWiki - SMB
Super bolusVerschiebung von Basal- zu Bolusinsulin um BZ schneller senken zu können John Walsh - The Super Bolus (englisch)
TBBGesamtbasalmenge (total base basal) - Summe des über 24 Stunden über die Basalrate abgegebenen Insulins  
TBRTemporäre Basalrate (temporary basal rate)  
TDDTotal daily dose = Bolus + Basal pro Tag  
TTvorübergehendes Ziel (temporary target)
vorübergehende Absenkung/Anhebung des BZ-Ziels bzw. BZ-Zielbereichs		 Wiki - Temporäre Ziele
UAM"nicht angemeldete Mahlzeiten" (unannounced meals) - Erkennung von signifikanten Erhöhungen des Blutzuckerspiegels aufgrund von Mahlzeiten, Adrenalin oder anderen Einflüssen und Versuch, diese mit SMB anzupassenSMBWiki - SMB
Virtuelle PumpeMöglichkeit, AAPS Funktionen auszuprobieren oder für um mit Pumpen, für die noch kein Treiber zur Verfügung steht, manuell loopen zu könnenOpen Loop 
Smartphone-HintergrundbildAndroidAPS-Hintergrundbildsiehe Seite Smartphones
xDrip / xDrip+Open Source Software um CGM/FGM-Systeme auszulesen xDrip+
xDrip
Zero-temptemporäre Basalrate mit 0 % (keine Basalinsulin-Lieferung)  
siehe auch https://openaps.readthedocs.io/en/latest/docs/Resources/glossary.html (englisch)
diff --git a/docs/CROWDIN/de/Getting-Started/Safety-first.md b/docs/CROWDIN/de/Getting-Started/Safety-first.md deleted file mode 100644 index 8c54c04c7f20..000000000000 --- a/docs/CROWDIN/de/Getting-Started/Safety-first.md +++ /dev/null @@ -1,41 +0,0 @@ -# Sicherheitshinweise - -**Wenn Du Dich entscheidest, Deine eigene künstliche Bauchspeicheldrüse zu bauen, ist es immer wichtig, über Sicherheit und Schutz nachzudenken und die Auswirkungen all Deiner Handlungen zu verstehen.** - -## Allgemein - -- AAPS is a just a tool to help you manage diabetes, it is not a fully automated system you can install and forget! -- Do not assume that AAPS will never make mistakes. AndroidAPS übernimmt die Kontrolle Deiner Insulinabgabe: Habe es immer im Auge, verstehe wie es arbeitet und lerne, seine Handlungen zu interpretieren. -- Bedenke, dass ein Smartphone, welches einmal mit Deiner Pumpe gekoppelt ist, jegliche Anweisungen an die Pumpe geben kann. Only use this phone for AAPS and, if being used by a child, essential communications. Installiere keine unnötigen Anwendungen oder Spiele (!!!!!), die Malware wie Trojaner, Viren oder Bots einschleppen könnten, die Dein System stören könnten. -- Installiere alle Sicherheits-Updates, die der Smartphone-Hersteller und Google zur Verfügung stellen. -- Du musst auch Deine Diabetes-Gewohnheiten anpassen, da Du Deine Therapie durch den Closed Loop wesentlich veränderst. Zum Beispiel some people report, they need less hypo treatments as AAPS has already reduced insulin. - -## SMS Kommunikator - -- AAPS allows you to control a child's phone remotely via text message. Wenn Du diesen SMS-Kommunikator aktivierst, denke immer daran, dass das Telefon, das für Remote-Befehle eingerichtet ist, gestohlen werden kann. Schütze dieses mit einem zumindest mit einem sicheren PIN-Code. -- AAPS will also inform you by text message if your remote commands, such as a bolus or a profile change, have been carried out. Es ist ratsam, dies so einzustellen, dass Bestätigungstexte an mindestens zwei verschiedene Telefonnummern gesendet werden, falls eines der Empfangstelefone gestohlen wird. - -(Safety-first-aaps-can-also-be-used-by-blind-people)= -## AAPS can also be used by blind people - -Auf Android Geräten ist TalkBack Teil des Betriebssystems. Es handelt sich um ein Programm zur Bildschirmorientierung über die Sprachausgabe. With TalkBack you can operate your smartphone as well as AAPS blind. - -We users create the AAPS app ourselves with Android Studio. Viele verwenden Microsoft Windows zu diesem Zweck, wo es den Screenreader analog zu TalkBack gibt. Da Android Studio eine Java-Anwendung ist, muss die Komponente "Java Access Bridge" in der Systemsteuerung aktiviert sein. Andernfalls wird der Screenreader des PCs nicht in Android Studio sprechen. - -Bitte gehen Sie dazu wie folgt vor: - -- Drücken Sie WINDOWSTASTE und geben Sie in das Suchfeld "Systemsteuerung" ein, öffnen Sie mit Enter. Es öffnt: "Alle Systemsteuerungselemente". -- Drücken Sie den Buchstaben C, um zu "Center für erleichterte Bedienung" zu gelangen, öffnen Sie mit Enter. -- Dann öffnen Sie "Computer ohne Bildschirm verwenden" mit Enter. -- Dort unten finden Sie das Kontrollkästchen "Java Access Bridge aktivieren". -- Fertig, einfach das Fenster schließen! Der Screenreader sollte jetzt funktionieren. - -```{note} -**WICHTIGER SICHERHEITSHINWEIS** - -Die grundlegenden Sicherheitsfunktionen von AAPS, die in dieser Dokumentation beschrieben sind, bauen auf den Sicherheitsfunktionen der Hardware auf, mit der Du Dein System aufgesetzt hast. Es ist extrem wichtig, dass die Insulinpumpe und das CGM-System, die für ein Closed Loop System mit automatisierter Insulinabgabe verwendet werden, hinreichend getestet und voll funktionstüchtig sind sowie (in Europa) eine CE-Kennzeichnung haben und (in Deutschland) als Medizinprodukte zugelassen sind. Veränderungen an Hard- oder Software dieser Komponenten können zu unerwarteter Insulinabgabe und damit zu erheblichen Risiken für den Anwender führen. *Verwende keine* defekten, modifizierten oder selbsterstellten Insulinpumpen oder CGM-Empfänger, um ein AAPS-System zu erstellen oder zu betreiben. - -Außerdem ist es ebenso wichtig, nur Originalzubehör zu verwenden. Setzhilfen, Kanülen und Reservoire müssen vom Hersteller für den Einsatz mit deiner Pumpe bzw. deinem CGM zugelassen sein. Die Verwendung von nicht geprüftem oder modifiziertem Zubehör kann zu Ungenauigkeiten des CGM-Systems und Insulinabgabefehlern führen. Insulin ist sehr gefährlich, wenn es falsch dosiert wird. Spiele nicht mit deinem Leben, indem du ungeprüftes oder modifiziertes Zubehör verwendest. - -Nicht zuletzt darfst Du keine SGLT-2-Hemmer (Gliflozins) einnehmen, da sie den Blutzuckerspiegel unberechenbar senken. Die Kombination mit einem Closed Loop System, das die basalen Raten senkt, um den BZ zu erhöhen ist besonders gefährlich, da durch die Gliflozin dieser BZ-Anstieg verhindert wird und ein gefährlicher Zustand durch Insulinmangel auftreten kann. -``` diff --git a/docs/CROWDIN/de/Getting-Started/Sample-Setup.md b/docs/CROWDIN/de/Getting-Started/Sample-Setup.md deleted file mode 100644 index 4e8a3cce02fb..000000000000 --- a/docs/CROWDIN/de/Getting-Started/Sample-Setup.md +++ /dev/null @@ -1,151 +0,0 @@ -# Konfigurationsbeispiel: Samsung S7, Dana RS, Dexcom G6 und Sony Smartwatch - -![Konfigurationsbeispiel](../images/SampleSetup.png) - -## Beschreibung - -In dieser Variante ist das Smartphone Samsung Galaxy S7 die Schaltzentrale des Loop. Es liest mit der originalen, aber von der Community leicht modifizierten Dexcom-App das kontinuierliche Glukosemesssystem Dexcom G6 aus. AndroidAPS steuert auf Basis dieser Daten die Insulinpumpe Dana RS des koreanischen Herstellers SOOIL via Bluetooth. Weitere Geräte werden nicht benötigt. - -Da die Dexcom App nur begrenzte Alarmoptionen zur Verfügung stellt, wird xDrip+ verwendet, um nicht nur Hoch- und Niedrigalarme sondern auch weitere Alarme nach individuellen Bedürfnissen auszugeben. - -Falls gewünscht, können alle aktuellen Glukose- und Behandlungsdaten auf einer Android Wear Smartwatch (in diesem Beispiel die "Sony Smartwatch 3" (SWR50)) am Handgelenk angezeigt werden. Über die Smartwatch kann AndroidAPS auch bedient werden (z.B. Bolusgabe). - -Das System funktioniert offline, also ohne dass zum Betrieb eine Datenverbindung des Smartphones zum Internet erforderlich ist. - -Die Daten werden jedoch automatisch zu Nightscout (Open Source Cloud Service) hochgeladen, wenn eine Datenverbindung hergestellt wird. So können umfangreiche Auswertungen für den Arztbesuch erstellt oder jederzeit die aktuellen Werte mit Familienmitgliedern geteilt werden. Es ist auch möglich, die Daten nur über eine (ggf. zuvor definiertes) WLAN-Verbindung zu übertragen, um die Nightscout-Berichte nutzen zu können. - -## Benötigte Komponenten - -1. Samsung Galaxy S7 - - * Alternativen: siehe [Liste der getesteten Smartphones und Smartwatches](https://docs.google.com/spreadsheets/d/1gZAsN6f0gv6tkgy9EBsYl0BQNhna0RDqA9QGycAqCQc/edit) für AndroidAPS - -2. [Dana RS](http://www.sooil.com/eng/product/) - - * Alternativen: - * [Accu-Chek Combo](../Configuration/Accu-Chek-Combo-Pump.md) - * [Accu-Chek Insight](../Configuration/Accu-Chek-Insight-Pump.md) - * [Dana R](../Configuration/DanaR-Insulin-Pump.md) - * [Einige alte Medtronic Pumpen (zusätzlich erforderlich: RileyLink/Gnarl Hardware, Android Phone mit Bluetooth Low Energy/BLE-Chipsatz)](../Configuration/MedtronicPump.md) - * Künftig werden evtl. weitere Pumpen für den Loop nutzbar sein. Eine Liste der zukünftig ggf. loopbare Pumpen finden sich [hier](Future-possible-Pump-Drivers.md). - -3. [Dexcom G6](https://dexcom.com) - - * Alternatives: see list of possible [BG sources](../Configuration/BG-Source.md) - -4. Optional: Sony Smartwatch 3 (SWR50) - - * Alternativen: Alle [Uhren mit Google Wear OS](https://wearos.google.com/intl/de_de/#find-your-watch) sollten funktionieren. Details findest Du in der [Liste der getesteten Smartphones und Smartwatches](https://docs.google.com/spreadsheets/d/1gZAsN6f0gv6tkgy9EBsYl0BQNhna0RDqA9QGycAqCQc/edit) für AndroidAPS (OS muss Android Wear sein). - -## Nightscout Einrichtung - -Detaillierte Anleitung siehe [Nightscout Setup](../Installing-AndroidAPS/Nightscout.md). - -## Computer Einrichtung - -Um aus dem frei verfügbaren OpenSource-Quellcode von AAPS eine Android-App selbst erstellen zu können, wird Android Studio auf dem Computer oder Notebook (Windows, Mac, Linux) benötigt. Eine detaillierte, bebilderte Installationsanleitung findet sich unter [App aus Quellcode erstellen](../Installing-AndroidAPS/Building-APK.md). - -Bei der Erstinstallation von Android Studio ist einige Geduld erforderlich, da die Software nach der Installation auf dem Rechner einige weitere Komponenten nachlädt. - -## Smartphone Einrichtung - -![Smartphone](../images/SampleSetupSmartphone.png) - -### Firmware des Smartphones prüfen - -* Menü > Einstellungen > Telefoninfo > Softwareinfo: Hier sollte mindestens die Firmware-Version stehen: "Android-Version 8.0" (erfolgreich getestet bis Android-Version 8.0.0 Oreo - Samsung Experience Version 9.0) -* Falls nicht: Menü > Einstellungen > Software-Update durchführen - -### Installation von Apps aus unbekannten Quellen zulassen - -Menü > Einstellungen > Gerätesicherheit > Unbekannte Quellen > Schieber nach rechts (= aktiv) - -Diese Einstellung sollte aus Sicherheitsgründen wieder auf inaktiv gestellt werden, wenn die Installation aller hier beschriebenen Apps abgeschlossen ist. - -### Bluetooth aktivieren - -1. Menü > Einstellungen > Verbindungen > Bluetooth > Schieber nach rechts (= aktiv) -2. Menü > Einstellungen > Verbindungen > Standort > Schieber nach rechts (= aktiv) - -Standortdienste ("GPS") müssen aktiviert sein, damit Bluetooth ordnungsgemäß funktioniert. - -### Dexcom App (modifizierte Version) installieren - -![gepatchte Dexcom App](../images/SampleSetupDexApp.png) - -Die Original-App von Dexcom aus dem Google Play Store wird nicht funktionieren, weil sie die Werte nicht an andere Apps weitergibt. Darum ist eine von der Community leicht modifizierte Version erforderlich. Nur sie kann später mit AAPS kommunizieren. Außerdem kann die modifizierte Dexcom App mit allen Android Smartphones verwendet werden, nicht nur mit den in der [Dexcom Kompatibilitätsliste](https://www.dexcom.com/dexcom-international-compatibility) aufgeführten. - -Zur Einrichtung im Smartphone folgende Schritte ausführen: - -1. Falls die Original-Dexcom-App bereits installiert sein sollte: - * Sensor stoppen - * App deinstallieren über Menü > Einstellungen > Apps > Dexcom G6 Mobile > Deinstallieren -2. Download and install the [BYODA Dexcom ap](../Hardware/DexcomG6.md#if-using-g6-with-build-your-own-dexcom-app) -3. Modifizierte Dexcom G6-App starten, den Sensor nach Anweisung aktivieren / kalibrieren und die Aufwärmphase abwarten. -4. Wenn die modifizierte Dexcom-App den aktuellen Wert anzeigt, dann im Hamburger-Menü (= drei waagerechte Striche links oben in der App) auf “Warnungen” und folgende Konfiguration einstellen: - * Akut niedrig: `55mg/dl` / `3.1mmol/l` (kann nicht deaktiviert werden) - * Niedrig `OFF` - * Hoch `OFF` - * Anstiegsrate `OFF` - * Abfallrate `OFF` - * Signalverlust `OFF` - -## AndroidAPS installieren - -1. Follow the instructions to [build the APK](../Installing-AndroidAPS/Building-APK.md#generate-signed-apk) -2. [Transfer](../Installing-AndroidAPS/Building-APK.md#transfer-apk-to-smartphone) the generated APK to your phone -3. AndroidAPS entsprechend den eigenen Anforderungen mit Hilfe des Einrichtungsassistenten oder manuell [konfigurieren](../Configuration/Config-Builder.md). -4. In diesem Beispiel haben wir (unter anderem) folgende Einstellungen verwendet: - -* BG source: `Dexcom G6 App (patched)` -- click cock-wheel and activate `Upload BG data to NS` and `Send BG data to xDrip+` (see [BG source](../Configuration/BG-Source.md)) - -![G5 Einstellungen](../images/SampleSetupG5Settings.png) - -* NS Client activated (see [Nightscout setup](../Installing-AndroidAPS/Nightscout.md)) - -## xDrip+ installieren - -xDrip + ist eine weitere ausgereifte Open-Source-App, die unzählige Möglichkeiten bietet. Anders als von den Entwicklern eigentlich gedacht, wird xDrip+ aber bei dieser Methode nicht auch zum Sammeln der Glukosedaten vom Dexcom G6 verwendet, sondern nur, um Alarme auszugeben und auf dem Android-Homescreen im Widget den aktuellen Glukosewert samt Kurve anzuzeigen. Mit xDrip+ können die Alarme nämlich viel individueller eingestellt werden als mit der Dexcom-Software, AAPS oder Nightscout (keine Einschränkung bei der Auswahl der Sounds, verschiedene Alarme je nach Tages-/Nachtzeit etc.). - -1. Letzte stabile APK-Version von xDrip+ mit dem Smartphone herunterladen unter - nicht die Version aus dem GooglePlay-Store! -2. xDrip+ installieren, indem die heruntergeladene APK-Datei ausgewählt wird. -3. xDrip+ starten und im Hamburger-Menü (drei waagerechte Striche links oben) folgende Einstellungen vornehmen: - * Einstellungen > Warnungen > Glukose-Alarm-Liste > Warnungen (niedrig) und (hoch) je nach Bedarf erstellen. - * Die bestehenden Alarme können mit einem langen Fingerdruck geändert werden. - * Einstellungen > Kalibrierungs-Erinnerungen: deaktiviert (wird über die Dexcom-App erinnert) - * Einstellungen > Datenquelle > 640G/EverSense - * Einstellungen > Inter-App-Einstellungen > Accept Calibrations > `AN` - * Menü > Sensor starten (Ist nur "pro forma" und hat nichts mit dem laufenden G6-Sensor zu tun. Dies ist nötig, da sonst regelmäßig eine Fehlermeldung kommt.) - -For more information about xDrip+, see here [BG source page](../Configuration/BG-Source.md). - -### Beispiel für ein Alarm-Setup: - -Der "Akut niedrig Alarm" (unter 55 mg/dl bzw. 3,1 mmol/l) ist ein Standardalarm der modifizierten Dexcom App, der nicht abgeschaltet werden kann. - -![xDrip Alarme](../images/SampleSetupxDripWarning.png) - -Tipp für Tagungen, Kirchenbesuche, Kino etc...: - -Wenn im Samsung Galaxy S7 der "Nicht stören-Modus" aktiviert ist (Menü > Einstellungen > Töne und Vibration > Nicht stören: nach rechts schieben), dann vibriert das Smartphone bei dem nicht abschaltbaren Dexcom-Niedrigalarm nur und gibt keine akustische Warnung aus. Bei den übrigen, über xDrip+ eingerichteten Alarmen kann jeweils ausgewählt werden, ob der Lautlosmodus ignoriert werden soll oder nicht. - -## Energiesparoptionen deaktivieren - -Im Samsung Galaxy S7 auf Menü > Einstellungen > Gerätewartung > Akku > Nicht überwachte Apps > +Apps hinzufügen: Hier nacheinander die Apps AndroidAPS, Dexcom G6 Mobile, xDrip+ und ggf. AndroidWear auswählen (falls die Smartwatch verwendet wird). - -## Optional: Sony Smartwatch 3 (SWR50) einrichten - -Mit einer Android Wear Smartwatch lässt sich das Leben mit Diabetes noch viel unauffälliger gestalten. Über sie kann am Handgelenk jederzeit der aktuelle Glukosezucker, der Status der Loop etc. angezeigt Über die Smartwatch kann AndroidAPS auch bedient werden (z.B. Bolusgabe). Dazu den CGM-Wert im AAPSv2 Watchface doppelklicken. Die SWR50 läuft in der Regel einen ganzen Tag, bis der Akku wieder aufgeladen werden muss (selbes Ladegerät wie das Samsung Galaxy S7: microUSB). - -![Smartwatch](../images/SampleSetupSmartwatch.png) - -Details zu dem auf dem Watchface angezeigten Informationen finden sich [hier](../Configuration/Watchfaces.md). - -* Auf dem Smartphone über den Google-Play-Store die App "Android Wear" installieren und die SWR50 nach dortigen Anweisungen koppeln. -* In AAPS Hamburger Menü (oben links) > Konfiguration > Allgemein (ganz unten in der Liste) > Wear > links aktivieren, Zahnrad klicken > Wear-Einstellungen > `Steuerung durch die Uhr` -* Auf der Smartwatch: Lange auf das Display drücken, um das Watchface zu ändern, und dann `AAPSv2` auswählen. -* Ggf. beide Geräte einmal neu starten. - -## Pumpe einrichten - -siehe [Dana RS](../Configuration/DanaRS-Insulin-Pump.md) \ No newline at end of file diff --git a/docs/CROWDIN/de/Getting-Started/WhatisAndroidAPS.md b/docs/CROWDIN/de/Getting-Started/WhatisAndroidAPS.md deleted file mode 100644 index 290269565e7f..000000000000 --- a/docs/CROWDIN/de/Getting-Started/WhatisAndroidAPS.md +++ /dev/null @@ -1,39 +0,0 @@ -# What is a closed loop system with AAPS? - -AAPS is an app that acts as an artificial pancreas system (APS) on an Android smartphone. Was ist eine künstliche Bauchspeicheldrüse? Es ist eine App, die darauf abzielt, das zu tun, was eine funktionierende Bauchspeicheldrüse tut: den Blutzuckerspiegel automatisch in gesunden Grenzen zu halten. - -Ein APS kann die Aufgabe nicht so gut erfüllen wie eine biologische Bauchspeicheldrüse, aber es kann die Behandlung von Typ-1-Diabetes mit handelsüblichen Geräten und einer einfachen und sicheren Software erleichtern. Those devices include a continuous glucose monitor (CGM) to tell AAPS about your blood sugar levels and an insulin pump which AAPS controls to deliver appropriate doses of insulin. Die App kommuniziert mit diesen Geräten über Bluetooth. Es führt seine Dosisberechnungen unter Verwendung eines Algorithmus oder eines Regelsatzes durch, der für eine andere künstliches Bauchspeicheldrüse, OpenAPS genannt, entwickelt wurde. OpenAPS hat Tausende von Nutzern, die Millionen von Nutzungsstunden gesammelt haben. - -A note of caution: AAPS is not regulated by any medical authority in any country. Using AAPS is essentially carrying out a medical experiment on yourself. Die Einrichtung des Systems erfordert Entschlossenheit und technisches Wissen. Wenn Dir zu Beginn das technische Know-how noch fehlt, wirst Du es am Ende haben. Alle Informationen, die Du benötigst, findest Du auf dieser und anderen Seiten im Internet. Oder Du kannst Deine Fragen in Facebook-Gruppen oder anderen Foren an erfahrene Nutzer stellen. Many people have successfully built AAPS and are now using it entirely safely, but it is essential that every user: - -- das System selbst erstellt, damit Er/Sie vollständig versteht, wie es funktioniert. -- seine individuellen Diabetes-Einstellungen zusammen mit seinem Diabetes-Team anpasst, so dass diese bestmöglich funktionieren. -- das System pflegt, auf dem aktuellen Stand hält und es überwacht, um sicherzustellen, dass es ordnungsgemäß funktioniert. - -```{note} -**Haftungsausschluss und Warnung** - -- Alle Informationen, Gedanken und Code, die hier beschrieben werden, sind ausschließlich zu Informations- und Bildungszwecken bestimmt. Nightscout erfüllt keinerlei Anforderungen des Datenschutzes im Gesundheitswesen. Du verwendest Nightscout und AAPS auf eigenes Risiko. Setze es nicht ein, um Behandlungsentscheidungen zu treffen. -- Bei Nutzung des Quellcodes von github.com bestehen keinerlei Gewährleistungs- und Garantieansprüche. Es gibt keinen Support. Im Übrigen wird auf die Lizenz verwiesen, die im Repository abgerufen werden kann. -- Sämtliche Produkt- und Herstellernamen, Handelsmarken, Dienstleistungsmarken, Warenzeichen und eingetragene Dienstleistungsmarken sind Eigentum ihrer jeweiligen Inhaber und werden nur zu Informationszwecken genutzt und nicht für Werbung oder Marketing. Ihre Verwendung dient nur zur Information und bedeutet weder, dass AAPS zu ihnen gehört, noch dass sie unterstützt werden. - -Bitte beachten - Dieses Projekt steht in keinerlei Verbindung zu: [SOOIL](http://www.sooil.com/eng/), [Dexcom](https://www.dexcom.com/), [Accu-Chek, Roche Diabetes Care](https://www.accu-chek.com/), [Insulet](https://www.insulet.com/) oder [Medtronic](https://www.medtronic.com/). -``` - -Wenn Du bereit bist, diese Herausforderung anzunehmen, lies bitte weiter. - -## Primary goals behind AAPS - -- Eine App mit eingebauter Sicherheit. Um mehr über die Sicherheitsfunktionen der Algorithmen, die als oref0 und oref1 bekannt sind, zu lesen, klicke hier () -- Eine All-in-one-App für das Management Deines Typ1-Diabetes mit einer künstlichen Bauchspeicheldrüse und Nightscout. -- Eine App, zu der Benutzer bei Bedarf Module einfach hinzufügen oder entfernen können. -- Eine App mit Versionen für verschiedenen Standorte und Sprachen. -- Eine App, die im Open- und Closed-Loop-Modus verwendet werden kann. -- Eine App, die vollkommen transparent ist: Benutzer können Parameter eingeben, Ergebnisse sehen und die endgültige Entscheidung treffen. -- Eine App, die unabhängig von bestimmten Pumpen-Treibern ist und eine "virtuelle Pumpe" enthält, damit Benutzer sicher experimentieren können, bevor sie diese zusammen mit ihrer Insulinpumpe verwenden. -- Eine App, die eng mit Nightscout verbunden ist. -- Eine App, in der der Benutzer die Kontrolle über die Sicherheitseinschränkungen hat. - -## Wie lege ich los? - -Natürlich sind alle hier verfügbaren Informationen für Dein Closed Loop System sehr wichtig, es ist aber auch normal, dass die vielen neuen Dinge anfangs etwas verwirrend wirken. Gute Orientierung bieten die [Modul-Übersicht](../Module/module.md) und die [Objectives (Ziele)](../Usage/Objectives.html). diff --git a/docs/CROWDIN/de/Hardware/DexcomG4.md b/docs/CROWDIN/de/Hardware/DexcomG4.md deleted file mode 100644 index cd350436a14a..000000000000 --- a/docs/CROWDIN/de/Hardware/DexcomG4.md +++ /dev/null @@ -1,6 +0,0 @@ -# Dexcom G4 - dies ist der MD file - -## Dexcom G4 mit OTG Kabel ("traditionelles Nightscout") -- Falls nicht bereits konfiguriert, dann laden Sie die Nightscout Uploader-App aus dem Play Store herunter und folgen Sie den Anweisungen auf [Nightscout](https://nightscout.github.io/). -- In AAPS Preferences enter your Nightscout website and API secret. -- Select NSClient in ConfigBuilder (setting in AAPS). diff --git a/docs/CROWDIN/de/Hardware/Smartwatch.md b/docs/CROWDIN/de/Hardware/Smartwatch.md deleted file mode 100644 index 7c8fd1167404..000000000000 --- a/docs/CROWDIN/de/Hardware/Smartwatch.md +++ /dev/null @@ -1,10 +0,0 @@ -# Smartwatches - -Smartwatches sind nicht zwingend erforderlich, werden von einigen Anwendern aber als sehr hilfreich beschrieben. Mehr Infos hier: - -- [Liste der getesteten Telefone und Smartwatches](../Getting-Started/Phones.md) -- [Watchfaces Wear-OS](../Configuration/Watchfaces.md) -- [Fehlerbehebung für Sony Smartwach 3](../Usage/SonySW3.md) - -## Instructions for Building the AAPS Wear APK for Wear OS -https://androidaps.readthedocs.io/en/latest/remote-control.html#building-the-aaps-wear-apk diff --git a/docs/CROWDIN/de/Installing-AndroidAPS/Building-APK.md b/docs/CROWDIN/de/Installing-AndroidAPS/Building-APK.md deleted file mode 100644 index df8d8b13ec0a..000000000000 --- a/docs/CROWDIN/de/Installing-AndroidAPS/Building-APK.md +++ /dev/null @@ -1,369 +0,0 @@ -# AndroidAPS installieren - App erstellen - -## Kein Download möglich - APK muss selbst erstellt werden - -**Aufgrund der gesetzlichen Regelungen für Medizinprodukte ist AndroidAPS nicht als Download verfügbar. Es ist zulässig, die App für den eigenen Gebrauch zu erstellen, aber du darfst keine Kopie an andere weitergeben! Weitere Informationen findest Du auf der [FAQ Seite](../Getting-Started/FAQ.md).** - -## Wichtige Hinweise - -* Please use **[Android Studio Giraffe" (2022.3.1)](https://developer.android.com/studio/)** or newer to build the apk. -* [Windows 32-bit systems](troubleshooting_androidstudio-unable-to-start-daemon-process) are not supported by Android Studio - -(Building-APK-recommended-specification-of-computer-for-building-apk-file)= - -## Empfohlene Spezifikation des Computers zum Erstellen der Apk-Datei - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Betriebssystem (nur 64 Bit)Windows 8 oder höherMac OS 10.14 oder höherJedes Linux unterstützt Gnome, KDE oder Unity DE;  GNU C Library 2.31 oder höher

CPU (nur 64 Bit)

x86_64 CPU-Architektur; Intel Core oder neuere Generation oder AMD CPU mit Unterstützung für einen
Windows Hypervisor		ARM-based Chips oder Intel Core der zweiten Generation oder neuer mit Unterstützung für
Hypervisor.Framework		x86_64 CPU Architektur; Intel Core der zweiten Generation oder neuer, alternativ AMD Prozessor mit Unterstützung für AMD Virtualization (AMD-V) und SSSE3

RAM

8GB oder mehr

Festplatte

Mind. 30 GB freier Speicherplatz. SSD wird empfohlen.

Bildschirmauflösung

min. 1280 x 800

Internet

Breitband

- -Please keep in mind that both **64 bit CPU and 64 bit OS are mandatory condition.** If your system DOES NOT meet this condition, you have to change affected hardware or software or the whole system. **Es wird dringend empfohlen, SSD (Solid State Disk) anstelle von HDD (Hard Disk Drive) zu verwenden, da dies dies die Zeit zur Erstellung der APS-Installationsdatei reduziert.** Dies wird nur eine Empfohlung und ist nicht zwingend erforderlich. Du kannst auch eine normale Festplatte verwenden. Beachte aber, dass der Prozess zur Erstellung der APK-Datei dann länger dauert. Du kannst den Prozess aber unbeaufsichtigt laufen lassen, nachdem Du ihn gestartet hast. - -* * * - -### Dieser Artikel ist in zwei Teile geteilt. - -* Im Überblick werden die wichtigsten Schritte kurz zusammengefasst die allgemein nötig sind, um die APK Datei zu erstellen. -* In der “Schritt für Schritt Anleitung” wird detailliert auf die einzelnen Punkte mithilfe von Screenshots eingegangen. Da die Versionen von Android Studio - der Software, die wir zum Bau der APK verwenden werden - sich schnell weiterentwickeln werden diese nicht mit deiner Installation übereinstimmen, aber sie geben einen guten ersten Eindruck. Android Studio läuft sowohl auf Windows als auch auf Mac OS X und Linux. Es kann sein, dass es bei jedem Betriebssystem einige kleinere Unterschiede gibt. Falls Du feststellst, dass etwas wichtiges falsch ist oder fehlt, informiere bitte die Facebook Gruppe "AndroidAPS users" oder im Discord chat [Android APS](https://discord.gg/4fQUWHZ4Mw), damit wir uns das anschauen können. - -## Übersicht - -Kurzfassung der wichtigsten Schritte zum Erstellen der APK Datei: - -1. [Git installieren](../Installing-AndroidAPS/git-install.md) -2. [Android Studio installieren](Building-APK-install-android-studio) -3. [Pfad zu git.exe in den Einstellungen von Android Studio festlegen](Building-APK-set-git-path-in-preferences) -4. [Download AAPS-Code](Building-APK-download-AAPS-code) -5. [Download Android SDK](Building-APK-download-android-sdk) -6. [App erstellen](Building-APK-generate-signed-apk) (generate signed apk) -7. [APK-Datei auf das Smartphone übertragen](Building-APK-transfer-apk-to-smartphone) -8. [Identifiziere den Empfänger falls Du xDrip verwendest+](xdrip-identify-receiver) - -## Schritt für Schritt Anleitung - -Detaillierte Beschreibung der notwendigen Schritte. - -## Installiere git (falls du es noch nicht hast) - -Die Schritt-für-Schritt-Anleitung findest Du auf der Seite zur [git Installation](../Installing-AndroidAPS/git-install.md). - -(Building-APK-install-android-studio)= - -## Android Studio installieren - -Die folgenden Screenshots stammen von Android Studio Version Arctic Fox | 2020.3.1. Die Bildschirme können bei zukünftigen Versionen von Android Studio leicht anders aussehen. Aber Du solltest Dich dennoch zurechtfinden. Bei Fragen gibt es [Hilfe in der Community](../Where-To-Go-For-Help/Connect-with-other-users.md). - -Einer der wichtigsten Punkte bei der Installation von Android Studio ist: **Sei geduldig!** Während der Installation und Einrichtung lädt Android Studio sehr viele Daten nach und das braucht seine Zeit. - -Lade [Android Studio von dieser Seite](https://developer.android.com/studio/install.html) herunter und installiere es auf Deinem Computer. - -Beim ersten Start öffnet sich der Setup Wizard: - -Wähle “Do not import settings”, da bisher keine Einstellungen vorgenommen wurden. - -![Einstellungen nicht importieren](../images/studioSetup/01_ImportSettings.png) - -Entscheide, ob Du Daten mit Google teilen möchtest oder nicht. - -![Daten mit Google teilen](../images/studioSetup/02_DataSharing.png) - -Klicke auf dem nächsten Bildschirm den Button "Next". - -![Willkommensbildschirm](../images/studioSetup/03_Welcome.png) - -Wähle “Standard” Installation und klicke auf “Next”. - -![Standardinstallation](../images/studioSetup/04_InstallType.png) - -Wähle das Design für die Benutzeroberfläche, welches Dir am besten gefällt. (In dieser Anleitung verwenden wir "Light".) Dann klicke auf "Next". - -> ***Hinweis:*** Das ist nur das Farbschema. Du kannst auswählen, was Du möchtest (z.B. "Darcula" für den dunklen Modus). Diese Auswahl hat keinen Einfluss auf das Erstellen der APK, aber die folgenden Screenshots könnten anders aussehen. - -![Farbschema](../images/studioSetup/05_UITheme.png) - -Click "Next" on the "Verify Settings" dialog. - -![Einstellungen überprüfen](../images/studioSetup/06_Overview.png) - -Click on all three license agreement parts and select "Agree". When you have agreed to all, the "Finish" button will be enabled and you can "Finish". - - ![Agree license agreements](../images/studioSetup/07_LicenseAgreement.png) - - -Wait while Android Studio downloads additional components and be patient. Once everything is downloaded button "Finish" turns blue. Click the button now. - -![Downloading components](../images/studioSetup/08_Downloading.png) - -(Building-APK-download-AAPS-code)= - -## Download AAPS-Code - -* On the Android Studio welcome screen select "Projects" (1) on the left and then "Get from VCS" (2). - - ![Android Studio wizard](../images/studioSetup/20_ProjectVCS.png) - - * If you already opened Android Studio and do not see the welcome screen anymore select File (1) > New (2) > Project from Version Control... (3) - - ![Check out project from version control within Android Studio](../images/AndroidStudio_FileNew.PNG) - - * We will now tell Android Studio were to get the code from: - - * Make sure you have selected "Repository URL" on the left (1). - - * Check if "Git" is selected as version control (2). - * Copy and paste the URL ```https://github.com/nightscout/AndroidAPS``` to the main AAPS repository into the URL textbox (3). - * Choose the directory where you want to save the cloned code (4). - - ![Clone Git](../images/studioSetup/21_CloneURL.png) - -* Click button "Clone" (5). - - ![Clone repository](../images/studioSetup/22_Cloning.png) - -* Do not click "Background" while repository is cloned! - -* After the repository is cloned successfully, Android Studio will open the cloned project. - -* You will be asked whether you want to trust the project. Click on "Trust project"! - - ![Trust project](../images/studioSetup/23_TrustProject.png) - -* In the status bar at the bottom you will see the information that Android Studio is running background tasks. - - ![Background tasks](../images/studioSetup/24_GradleSyncRunning.png) - -* Windows only: Grant access if your firewall is asking for permission. - - ![Firewall permission java](../images/AndroidStudio361_18.png) - -* Once the background tasks are finished you will probably see an error saying that errors occurred (1) or (2) or (3). - - ![SDK licence](../images/studioSetup/25_SyncFailed.png) - - Don't worry, this will be solved soon! - -(Building-APK-set-git-path-in-preferences)= - -## Set git path in preferences - -Make sure [git is installed](../Installing-AndroidAPS/git-install.md) on your computer and you have restarted your computer since installing. - -On the Android Studio welcome screen click "Customize" (1) on the left and then select the link "All settings..." (2): - -![Android Studio settings from welcome screen](../images/studioSetup/10_WizardSettings.png) - -### Windows - -* As windows user, make sure you have restarted your computer after [installing Git](../Installing-AndroidAPS/git-install.md). - -* Gehe im Menü auf Datei (1) > Einstellungen (2) (oder Android Studio > Einstellungen auf dem Mac). - - ![Einstellungen öffnen](../images/studioSetup/30_Settings.png) - -* Double-click "Version Control" (1) to open the sub-menu. - -* Click Git (2). -* Make sure update method "Merge" (3) is selected. -* Check if Android Studio can locate path to git.exe automatically by clicking the button "Test" (4). - - ![Android Studio settings](../images/studioSetup/11_GitPath.png) - -* If automatic setting is successful git version will be displayed next to the path. - - ![Git version displayed](../images/studioSetup/12_GitVersion.png) - -* Eventually git.exe cannot be found automatically or the Test will result in an error (1): - - ![Git not found](../images/studioSetup/13_GitVersionError.png) - - In this case click on the folder icon (2). - -* Use [search function](https://www.tenforums.com/tutorials/94452-search-file-explorer-windows-10-a.html) in windows explorer to find "git.exe" if you are unsure where git has been installed. You are looking for a file named "git.exe", located in **\bin** folder. - -* Select path to git.exe and make sure you selected the one in ** \bin\ ** folder (3) and click "OK" (4). - - ![Select git manually](../images/studioSetup/14_GitManualSelection.png) - -* Check your selected git path again with the "Test" button as described above. - -* When the git version is displayed next to the path (see screenshot above), close settings window by clicking "OK" button (5). - -### Mac - -* Any git version should work. For example . -* Use homebrew to install git: ```$ brew install git```. -* For details on installing git see the [official git documentation](https://git-scm.com/book/en/v2/Getting-Started-Installing-Git). -* If you install git via homebrew there is no need to change any preferences. Just in case: They can be found here: Android Studio - Preferences. - -(Building-APK-download-android-sdk)= - -## Download Android SDK - -* Gehe im Menü auf Datei (1) > Einstellungen (2) (oder Android Studio > Einstellungen auf dem Mac). - - ![Einstellungen öffnen](../images/studioSetup/30_Settings.png) - -* Double-click on Languages & Frameworks to open its submenu (1). - -* Select Android SDK (2). -* Tick the box left of "Android 9.0 (Pie)" (3) (API Level 28). - - ![SDK-Einstellungen](../images/studioSetup/31_AndroidSDK.png) - -* Bestätige die Änderungen durch Klick auf OK. - - ![SDK-Änderungen bestätigen](../images/studioSetup/32_ConfirmSDK.png) - -* Wait until the SDK download and installation is finished. - - ![Wait during SDK installation](../images/studioSetup/34_DownloadSDK.png) - -* When SDK installation is completed the "Finish" button will turn blue. Click this button. - - ![Finish SDK installation](../images/studioSetup/35_DownloadSDKfinished.png) - -* Android Studio might recommend to update the gradle system. **Never update gradle!** This will lead to difficulties! - -* If you see an information on the lower right side of your Android Studio window that Android Gradle Plugin is ready to update click on the text "upgrade" (1). - - ![Kein Gradle Update](../images/studioSetup/36_GradleUpdateRequest.png) - -* In the dialog box the select "Don't remind me again for this project" (2). - - ![Kein Gradle Update](../images/studioSetup/37_GradleUpdateDeny.png) - -* Restart Android Studio before you continue. - -(Building-APK-generate-signed-apk)= - -## Signierte APK erstellen (Generate signed APK) - -Signing means that you indicate your app to be your own creation but in a digital way as a kind of digital fingerprint within the app itself. That is necessary because Android has a rule that it only accepts signed code to run for security reasons. For more information on this topic, follow [this link](https://developer.android.com/studio/publish/app-signing.html#generate-key). - -* Nachdem Android Studio gestartet wurde, musst Du warten, bis alle Hintergrundaufgaben abgeschlossen sind. - - ![Auf Hintergrundaufgaben warten](../images/studioSetup/40_BackgroundTasks.png) - - * ***Warnung:*** Fahre mit den folgenden Schritten nicht fort, wenn Fehler auftreten. \ Schaue auf der [Seite zur Problembehebung in Android Studio](../Installing-AndroidAPS/troubleshooting_androidstudio) nach bekannten Problemen! - - ![Gradle Sync Fehler](../images/studioSetup/41_GradleSyncError.png) - -* Klicke in der Menüzeile auf "Build" (1) und wähle "Generate Signed Bundle / APK..." (2). - - ![Apk erstellen](../images/studioSetup/42_MenuBuild.png) - -* Wähle "APK" (1) statt "Android App Bundle" aus und klicke auf "Next" (2). - - ![APK statt Bundle](../images/studioSetup/43_Apk.png) - -* Make sure that module is set to "AndroidAPS.app" (1). - -* Klicke auf “Create new...” (2), um Deinen key store zu erstellen. - - ***Hinweis:*** Ein key store ist in diesem Fall nichts anderes als eine Datei, in der die Signierdaten gespeichert werden. Sie ist verschlüsselt und passwortgeschützt. - - ![Key Store erstellen](../images/studioSetup/44_KeystoreNew.png) - -* Klicke das Ordner-Symbol, um den Pfad zu wählen, unter dem Dein key store auf Deinem PC gespeichert werden soll. - - ![Key Store erstellen](../images/studioSetup/45_KeystoreDialog.png) - -* Wähle den Pfad, in dem Dein key store gespeichert werden soll (1). - - ![Key Store erstellen](../images/studioSetup/46_KeystorePath.png) - - ***Speichere ihn nicht im gleichen Ordner wie Dein Projekt. Du musst ein anderes Verzeichnis verwenden!*** Dein Benutzerordner wäre ein guter Speicherort. - -* Gib einen Dateinamen für Deinen key store ein (2) und bestätige mit "OK" (3). - -* Gib das Passwort für Deinen key store ein (2) und bestätige es (3).![Key store Pfad wählen](../images/studioSetup/47_KeystoreDialog.png) - - ***Hinweis:*** Passwörter für key store und key müssen nicht sehr anspruchsvoll sein. Merke sie Dir gut oder notiere sie an einem sicheren Ort. Falls Du künftig einmal keinen Zugriff auf die Passwörter haben solltest, findest Du einen Lösungsvorschlag unter [Fehlerbehebung verlorener key store](troubleshooting_androidstudio-lost-keystore). - -* Gib einen Alias für Deinen key ein (4). Wähle eine beliebige Bezeichnung. - -* Gib das Passwort für Deinen key ein (5) und bestätige es (6). - -* Als Validity (Gültigkeit) (7) ist standardmäßig 25 Jahre voreingestellt. Das musst Du nicht verändern. - -* Ein Vor- und Nachname müssen eingegeben werden (8). Alle anderen Informationen sind optional. - -* Klicke auf "OK" (9), wenn Du fertig bist. - -* Achte darauf, dass die Checkbox "remember passwords" ausgewählt ist (1). Dann musst Du sie bei der nächsten App-Erstellung (z.B. beim Update auf eine neue AndroidAPS Version) nicht erneut eingeben. - -* Klicke auf "Next" (2). - - ![Passwörter speichern](../images/studioSetup/48_KeystoreSave.png) - -* Wähle die Build-Variante "fullRelease" (1) und drücke "Finish". - - ![Build-Variante auswählen](../images/studioSetup/49_BuildVariant.png) - -* Android Studio zeigt im unteren Teil des Fensters "Gradle Build running" an. Dies dauert eine Weile je nach Computer und Internetverbindung. **Sei geduldig!** - - ![Gradle läuft](../images/studioSetup/50_GradleRunning.png) - -* Android Studio zeigt "Generate Signed APK" an, so bald die Erstellung der APK-Datei abgeschlossen ist. - - ![Build abgeschlossen](../images/studioSetup/51_BuildFinished.png) - -* Falls beim Erstellen Fehler auftreten, findest Du Lösungsansätze auf den Seiten zur [Fehlerbehebung](../Installing-AndroidAPS/troubleshooting_androidstudio). - -* Klicke auf die Benachrichtigung, um sie zu vergrößern. - -* Klicke auf den link "locate". - - ![Build finden](../images/studioSetup/52_BuildLocate.png) - - * Falls die Benrachrichtigung automatisch geschlossen wurde, kannst Du immer den "Event log" öffen und dort den Link auswählen.![Build erfolgreich - Ereignisprotokoll](../images/studioSetup/53_EventLog.png) - -* Dein Dateimanager (z.B. Windows Explorer) wird geöffnet. Navigiere zum Verzeichnis "full" (1) > "release" (2). - - ![Datei-Speicherort apk](../images/studioSetup/54_APKlocation.png) - -* "app-full-release.apk" (3) ist die von Dir gesuchte Datei! - -(Building-APK-transfer-apk-to-smartphone)= - -## Übertrage die APK-Datei auf das Smartphone - -Easiest way to transfer app-full-release.apk to your phone is via [USB cable or Google Drive](https://support.google.com/android/answer/9064445?hl=en). Please note that transfer by mail might cause difficulties and is not the preferred way. - -On your phone you have to allow installation from unknown sources. Manuals how to do this can be found on the internet (i.e. [here](https://www.expressvpn.com/de/support/vpn-setup/enable-apk-installs-android/) or [here](https://www.androidcentral.com/unknown-sources)). - -## Problembehandlung - -See separate page [troubleshooting Android Studio](../Installing-AndroidAPS/troubleshooting_androidstudio). \ No newline at end of file diff --git a/docs/CROWDIN/de/Resources/index.md b/docs/CROWDIN/de/Resources/index.md deleted file mode 100644 index 2ed9a642e3be..000000000000 --- a/docs/CROWDIN/de/Resources/index.md +++ /dev/null @@ -1,7 +0,0 @@ -# Ressourcen - -```{toctree} -:maxdepth: 4 - -Für medizinische Fachkräfte -``` diff --git a/docs/CROWDIN/de/Sandbox/sandbox2.md b/docs/CROWDIN/de/Sandbox/sandbox2.md deleted file mode 100644 index 493e9febd383..000000000000 --- a/docs/CROWDIN/de/Sandbox/sandbox2.md +++ /dev/null @@ -1,43 +0,0 @@ -# interne Sandbox-Datei 2 zum Testen - -```{admonition} no need to translate this -:class: note - -No need to translate this. -``` - -Dies ist eine interne Sandbox-Datei für das Dokumentationsteam zum Testen - -1. Markdown-Syntax und - -1. Hintergrundprozesse für - 1. CROWDIN Übersetzung und - 2. Read The Docs Deployment. - -Du kannst direkt von hier zum ersten Label in der sandbox1.md-Datei springen - ["Jump"](sandbox1-this-is-a-test). - -Du kannst direkt von hier zum zweiten Label in der sandbox1.md-Datei springen - ["Jump"](sandbox1-this-is-another-test). - -Hier kannst Du zur ersten Sandbox-Datei springen - ["Springen"](./sandbox1.md). - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -(sandbox2-this-is-a-test)= -## Dies ist ein Test - -Dies ist ein Test, ob Label eindeutig sein müssen. - -### This is spare information from the docs - -cut from index: - -There are "limits" set in place when you are first beginning your AAPS journey. Diese Sicherheitsbeschränkungen wurden über viele Jahre hinweg durch Beobachtungen der unbeabsichtigten Fehler entwickelt, die neue Benutzer am ehesten beim Bauen und Einrichten machen, und dann erfolgreich Loopen mit AAPS - da diese Fehler meist auftreten, einfach weil der Benutzer so begeistert war, mit dem System loszulegen, dass er vergessen hat, sich die Zeit zu nehmen, die notwendig ist, um die Informationen innerhalb dieser Dokumentation gründlich zu verstehen. - - -### spare info from the overview to put into "preparing" - -Da die Anforderungen zur Installation sehr anders von den Anforderungen anderer Installationen, die Du vielleicht in der Vergangenheit gemacht hast, sind, empfehlen wir Dir, beim ersten Erstellen der App den Schritt-für-Schritt Anweisungen strikt zu folgen. Das wird Dir helfen ein Gefühl dafür zu bekommen, wie ein reibungsloser Bau der App aussehen soll. Bitte gehe langsam und genau durch die Schritte. Wenn Du später eine neue Version zusammenstellst, wird es in der Regel sehr schnell und einfach von der Hand gehen. Auf diese Weise verbesserst Du Deine Chance mögliche Fehler im Erstellungsprozess sehr früh zu bemerken. Es ist wichtig, dass Du die keystore-Datei (.jks Datei zum Signieren der App) an einem sicheren Ort speicherst und Dir das zugehörige Passwort gut merkst. Du wirst beim Zusammenstellen einer neuer Version der App danch gefragt werden. Diese Datei stellt sicher, dass alle wichtigen Informationen aus der bestehenden App in die neue Version übertragen werden und der 'Neubau' der App reibungsloser klappen wird. In der Regel gibt es 2-3 neue AAPS-Versionen im Jahr, die ein Update der App erforderlich machen. Die Anzahl der Updates basiert auf den Erfahrungen der letzten Jahre, kann sich in der Zukunft aber anpassen. Uns ist wichtig, dass Du trotzdem eine ungefähre Vorstellung vom zu erwartenden Update-Zyklus bekommst. Wenn Du später routinierter im Erstellen neuer AAPS-Version sein wirst, wird der Erstellprozess ca. 15-30 Minuten benötigen. Da die Erstellschritte von Vielen als nicht intuitiv wahrgenommen werden, solltest Du am Anfang davon ausgehen, dass Du durch eine steile Lernkurve gehen wirst. Es kann also ganz normal sein, wenn Du, trotz Hilfe der Community, einen halben oder ganzen Tag zum Erstellen einer neuen Version benötigst. Wenn Du merkst, dass Du zunehmend frustrierter wirst, mache eine Pause, drehe die eine oder andere Runde um den Block und häufig hilft das schon, das Problem noch einmal mit freiem Kopf anzugehen. diff --git a/docs/CROWDIN/de/Usage/Objectives.md b/docs/CROWDIN/de/Usage/Objectives.md deleted file mode 100644 index 0beed8713b5a..000000000000 --- a/docs/CROWDIN/de/Usage/Objectives.md +++ /dev/null @@ -1,185 +0,0 @@ -# Objectives (Ziele) - -AAPS has a series of Objectives that need to be completed to walk you through the features and settings of safe looping. Sie stellen sicher, dass du alles, was in den Abschnitten weiter oben beschrieben wurde, korrekt installiert hast und dass du verstehst, was das System tut und warum du ihm vertrauen kannst. - -Wenn Du Dein **Smartphone wechselst** kannst Du Deine [Einstellungen exportieren](../Usage/ExportImportSettings.md) , um Deinen Fortschritt bei der Bearbeitung der Objectives zu behalten. Neben dem Fortschritt bei den Zielen werden auch deine Sicherheitseinstellungen wie der maximale Bolus usw. gespeichert. Wenn Du die Einstellungen nicht exportierst und wieder importierst, musst Du die Ziele von Anfang an neu erreichen. Denke daran, regelmäßig ein [Backup Deiner Einstellungen](../Usage/ExportImportSettings.html) zu machen, um auf der sicheren Seite zu sein. - -Wenn Du eines der Objectives (Ziele) neu starten willst, folge der [Anleitung weiter unten](Objectives-go-back-in-objectives). - -## Ziel 1: Einrichten der Darstellung und Überwachung sowie analysieren der Basalraten und Faktoren - -- Wähle die zu deinen Geräten passende Quelle für den Blutzuckerwert. Weitere Informationen findest Du unter [BZ-Quelle](../Configuration/BG-Source.md). -- Select the right Pump in ConfigBuilder (select Virtual Pump if you are using a pump model with no AAPS driver for looping) to ensure your pump status can communicate with AAPS. -- If using DanaR pump then ensure you have followed [DanaR Insulin Pump](../Configuration/DanaR-Insulin-Pump.md) instructions to ensure the link between pump and AAPS. -- You need to establish a data repository/reporting platform to complete this objective. That can be accomplished with either Nightscout or Tidepool (or both). Follow instructions at the [Nightscout](../Installing-AndroidAPS/Nightscout.md) or [Tidepool](../Installing-AndroidAPS/Tidepool.md) page for instructions. -- Die URL im NSClient muss **OHNE /api/v1/** am Ende eingegeben werden - siehe [NSClient Einstellungen](Preferences-nsclient). - -*You may need to wait for the next blood glucose reading to arrive before AAPS will recognise it.* - -## Objective 2: Learn how to control AAPS - -- Perform several actions in AAPS as described in this objective. - -- Klicke auf den orangenen Text "Noch nicht abgeschlossen", um zu den einzelnen Aufgaben zu kommen. - -- Links zum Wiki helfen Dir weiter, falls Du an der einen oder anderen Stelle noch nicht so sicher sein solltest. - - ```{image} ../images/Objective2_V2_5.png - :alt: Screenshot Ziel 2 - ``` - -(Objectives-objective-3-prove-your-knowledge)= - -## Ziel 3: Belege Dein Wissen - -Objective 3 is a multiple choice test based on questions designed to test your theoretical knowledge of **AAPS**. - -Some users find Objective 3 to be the most difficult objective to complete. Please do read the AAPS documents in conjunction with the questions. If you are genuinely stuck after researching the **AAPS** documents, please search or ask for help on the Facebook or Discord group. These groups can provide friendly hints or redirect you to the relevant part of the **AAPS** documents. - -To proceed with Objective 3, click on the orange text “Not completed yet” to access the relevant question. Please read each question and select your answer(s). - - - -Within each question, a hyperlink to the **AAPS** documents will guide you to the relevant section of the document which you should read in order to locate the correct answer. - - -[Obj3_Screenshot 2023-12-05 223422](https://github.com/openaps/AndroidAPSdocs/assets/137224335/77347516-e24e-459d-98ab-acbb49a3d4e8)![image](https://github.com/openaps/AndroidAPSdocs/assets/137224335/ca756b8e-efbc-4427-b281-ac953ce16718) - - - -For each question, there may be more than one answer that is correct! If an incorrect answer is selected, the question will be time locked for a certain amount of time (60 minutes) before you can go back and answer the question. - - -After updating to a new version of **AAPS**, new questions may be added to cover a prevalent issue picked up by **AAPS** or alternatively to test your knowledge of a new feature of **AAPS** as released. - - -When **AAPS** is installed for the first time, you will have to complete Objective 3 entirely in order to move onto Objective 4. Each objective is required to be completed in sequential order. New features will gradually be unlocked as progress is made through the objectives. - -__What happens if new questions are added later to Objective 3?__ From time to time, new features are added to **AAPS** which may require a new question to be added to Objective 3. As a result, any new question added to Objective 3 will be marked as “incomplete” because **AAPS** will require you to action this. As each Objective is independent, you will not lose the existing functionality of **AAPS** providing the other objectives remain completed. - - -## Ziel 4: Starte den Open Loop - -- Wähle Open Loop entweder in den Einstellungen oder indem Du lange auf den Loop Button in der linken oberen Ecke des Hauptbildschirms drückst. -- Arbeite Dich durch die [Einstellungen](../Configuration/Preferences.md), um AndroidAPS an Deine Anforderungen anzupassen. -- Manually enact at least 20 of the temporary basal rate suggestions over a period of 7 days; input them to your pump and confirm in AAPS that you have accepted them. Ensure this data shows in AAPS and Nightscout. -- Aktiviere falls notwendig [temporäre Ziele](../Usage/temptarget.md). Nutze das Hypo Temp Target um zu verhindern, dass AAPS aufgrund des Blutzuckeranstiegs nach einer Hypo zu stark korrigiert. - -### Anzahl der Benachrichtigungen reduzieren - -- Um die Anzahl der zu bestätigenden Vorschläge im Open Loop zu reduzieren, setze einen weiteren Zielbereich (z.B. 90-150 mg/dl oder 5,0-8,5 mmol/l). - -- Ggf. kannst Du nachts auch das obere Limit höher setzen oder den Open Loop ganz pausieren. - -- In den Einstellungen kannst Du einen minimalen Prozentwert setzen, der erreicht werden muss, bevor eine Änderung der Basalrate vorgeschlagen wird. - - ```{image} ../images/OpenLoop_MinimalRequestChange2.png - :alt: Open Loop Mindeständerung - ``` - -- Auch musst Du nicht alle fünf Minuten auf jeden einzelnen Vorschlag reagieren... - -## Ziel 5: Open Loop inklusive der temporären Basalratenvorschläge verstehen - -- Start to understand the thinking behind the temp basal recommendations by looking at the [determine basal logic](https://openaps.readthedocs.io/en/latest/docs/While%20You%20Wait%20For%20Gear/Understand-determine-basal.html) and both the [forecast line in AAPS homescreen](Screenshots-prediction-lines)/Nightscout and the summary of outputs from the calculations in your OpenAPS tab. - -Es ist möglicherweise sinnvoll, wenn du das Ziel höher als üblich ansetzt, bis du den Berechnungen und Einstellungen vertraust. Das System erlaubt: - -- einen niedrigen Zielwert von mindestens 4 mmol (72 mg/dl) oder höchstens 10 mmol (180 mg/dl) -- einen hohen Zielwert von mindestens 5 mmol (90 mg/dl) und höchstens 15 mmol (225 mg/dl) -- ein temporäres Ziel als Einzelwert kann im Bereich von 4 mmol bis 15 mmol (72 mg/dl bis 225 mg/dl) liegen - -Der Zielwert ist der Wert, auf dem die Berechnungen basieren und nicht der gleiche wie der, den du als Zuckerwert anstrebst. Wenn Du einen sehr großen Zielbereich (z.B. 3 mmol / 50 mg/dl oder mehr) wirst Du kaum Aktivitäten von AndroidAPS feststellen. Der vorhergesagte Glukosewert wird mit hoher Wahrscheinlichkeit innerhalb Deines Zielbereichs liegen und daher nicht viele temporäre Änderungen an der Basalrate vorgeschlagen werden. - -Vielleicht möchtest Du mit der Anpassung der Werte für einen engeren Zielbereich experimentieren (z.B. 1 mmol/l bzw. 20 mg/dl oder weniger) und beobachten, wie sich das Verhalten des Systems daraufhin ändert. - -Du kannst die Anzeige Deines Zielbereichs (grüne Linien) durch die Änderung der Werte für die Niedrig-/ und Hoch-Markierungen in den [Einstellungen](../Configuration/Preferences.md) > Zielbereich für die Grafikanzeige anpassen. - -```{image} ../images/sign_stop.png -:alt: Stoppzeichen -``` - -### Falls Du eine virtuelle Pumpe verwendest darfst Du nicht zum 6. Ziel wechseln. Klicke nicht auf 'Bestätigen/Verify' am Ende des 5. Ziels. - -```{image} ../images/blank.png -:alt: leer -``` - -(Objectives-objective-6-starting-to-close-the-loop-with-low-glucose-suspend)= -## Ziel 6: Closed Loop mit Abschaltung bei niedrigen Glukose-Werten - -```{image} ../images/sign_warning.png -:alt: Warnzeichen -``` - -### Im Ziel 6 wird die Basalrate bei zu erwartenden niedrigen Glukose-Werten abgeschaltet werden. Der 'closed loop' wird im Ziel 6 keinen Korrekturbolus bei hohen Werten abgeben. Hohe Glukose-Werte müssen von Dir manuell korrigiert werden! - -- Prerequisite: You need a good profile (basal, ISF, IC) already working in AAPS to start with Loop in Low Glucose Suspend mode. Du kannst sonst in eine Hypo geraten, die Du manuell behandeln musst. Ein gut getestetes Profil wird Dir helfen, dass Du in den fünf Tagen seltener in eine Hypo kommst, die Du behandeln musst. **Starte das Ziel 6 NICHT, wenn Du immer noch häufig Situationen mit niedrigen oder sehr niedrigen Glukosewerten hast. Passe zuerst DIA, Basalrate, Korrekturfaktoren (ISF) und Essenfaktoren an und teste diese, bevor Du das Ziel 6 startest.** -- Du musst Deine Einstellungen noch nicht verändern. Während Du Dich im Ziel 6 befindest, wird maxIOB intern automatisch auf Null gesetzt. **Wenn Du zu Ziel 7 übergehst, wird es diesen 'override' nicht mehr geben.** -- Das System wird Deinen maxIOB Wert auf Null setzen (und Deinen Wert damit überschreiben). Wenn Deine Glukosewerte dann fallen, kann AAPS damit Deine Basalrate reduzieren oder aussetzen. Sollten die Glukosewerte steigen, wird das Basal nur dann erhöht, wenn Dein IOB negativ ist (z.B. nach dem Aussetzen der Basalrate wg. vorangegangener niedriger Werte). In allen anderen Fällen wird die Standard-Basalrate Deines aktuellen Profils verwendet. **Hohe Werte müssen deshalb von Dir manuell mit Insulin korrigiert werden.** -- Wenn Dein Basal-IOB negativ ist (siehe Bildschirmausschnitt unten), kann auch im Ziel 6 eine TBR > 100% gesetzt werden. - -```{image} ../images/Objective6_negIOB.png -:alt: Beispiel negatives IOB -``` - -- Nutze einen zusätzlichen Sicherheitspuffer, in dem Du Deinen Zielbereich etwas höher setzt, als Du es normalerweise tun würdest. -- Aktiviere den Modus 'Low Glucose Suspend' (Abschaltung bei niedrigen Glukosewerten), indem Du lange auf das Loop-Symbol in der oberen rechten Bildschirmecke drückst (und festhälst) und dann den LGS-Modus auswählst. -- Aktive temporäre Basalraten erkennst Du an der hellblauen Textfarbe auf dem Startbildschirm und an der hellblauen Basallinie in der Grafik. -- Wenn du eine Hypo korrigierst, kann es vorkommen, dass danach Spitzen auftreten, die du nicht durch Erhöhung der Basalrate korrigieren kannst. - -(Objectives-objective-7-tuning-the-closed-loop-raising-max-iob-above-0-and-gradually-lowering-bg-targets)= -## Ziel 7: Justiere den Closed Loop, erhöhe maxIOB über 0 und setze den Zielbereich langsam herunter - -- Wähle 'Closed Loop' entweder in den [Einstellungen](../Configuration/Preferences.md) oder indem Du lange auf das Loop-Symbol in der oberen rechten Bildschirmecke drückst und halte ihn für einen Tag aktiv. - -- Setze den Wert 'Maximales Gesamt-IOB, das nicht überschritten werden darf' (in OpenAPS: 'max-iob') auf über Null. Der empfohlene Standardwert ist bei Nutzung des SMB-Algorithmus: "ein durchschnittlicher Mahlzeitenbolus + das Dreifache Deiner größten täglichen Basalrate" (größte stündliche Basalrate = maximaler Basalwert pro Stunde innerhalb des 24-Stunden-Rasters eines Tages) und bei Nutzung des AMA-Algorithmus: das Dreifache Deiner höchsten täglichen Basalrate. Du solltestDich diesen Werten langsam annähern, bis Du weißt, dass die Einstellung für Dich funktionieren. - - Betrachte diese Empfehlung als Ausgangspunkt. Wenn Du den Faktor '3x' verwendest und feststellst, dass AAPS Deinen BZ zu stark senkt, reduziere diesen Faktor (z.B. auf '2x'). Wenn Du Insulinresistenzen feststellst, kannst Du diesen Faktor vorsichtig Schritt für Schritt erhöhen. - - ```{image} ../images/MaxDailyBasal2.png - :alt: max daily basal - ``` - -- Wenn Du zuverlässig weißt, welcher IOB Deinem Looping-Muster entspricht, dann senke Deinen Zielbereich auf den gewünschten Wert. - -(Objectives-objective-8-adjust-basals-and-ratios-if-needed-and-then-enable-autosens)= -## Ziel 8: Passe, falls notwendig, Basalraten und Faktoren an und aktiviere dann die Autosens-Funktion - -- Du kannst [Autotune](https://openaps.readthedocs.io/en/latest/docs/Customize-Iterate/autotune.html) verwenden, um dafür zu sorgen, dass Deine Basalraten korrekt bleiben oder einen traditionellen Basalratentest durchführen. -- Enable [autosens](../Usage/Open-APS-features.md) over a period of 7 days and watch the white line on the homescreen graph show how your sensitivity to insulin may be rising or falling as a result of exercise or hormones etc. and keep an eye in the OpenAPS report tab how AAPS is adjusting the basals and/or targets accordingly. - -*Don’t forget to record your looping in* [this form](https://bit.ly/nowlooping) *logging AAPS as your type of DIY loop software, if you have not already done so.* - -(Objectives-objective-9-enabling-additional-oref1-features-for-daytime-use-such-as-super-micro-bolus-smb)= -## Ziel 9: Aktiviere zusätzliche oref1 Funktionen zum täglichen Gebrauch, wie z. B. den super micro bolus (SMB) - -- Du musst das [SMB-Kapitel in diesem Wiki](Open-APS-features-super-micro-bolus-smb) und das [Kapitel oref1 in der openAPS Dokumentation](https://openaps.readthedocs.io/en/latest/docs/Customize-Iterate/oref1.html) lesen, um zu verstehen wie der SMB arbeitet, insbesondere was Sinn und Zweck des "zero-temping" ist. -- Danach solltest du [maxIOB erhöhen](Open-APS-features-maximum-total-iob-openaps-cant-go-over-openaps-max-iob), damit SMB korrekt funktioniert. maxIOB enthält nun das gesamte IOB, nicht nur das hinzugefügte Basalinsulin. Das bedeutet, wenn Du einen Mahlzeiten-Bolus von 8 IE abgegeben willst und in den Einstellungen ein maxIOB von 7 IE hinterlegt hast, wird solange kein SMB abgegeben, bis das IOB wieder unter 7 IE gefallen ist. Beginne mit maxIOB = durchschnittlicher Mahlzeiten-Bolus + 3x die größe stündliche Basalrate (größte stündliche Basalrate = maximaler Basalwert pro Stunde innerhalb des 24-Stunden-Rasters eines Tages - in [Ziel 7](Objectives-objective-7-tuning-the-closed-loop-raising-max-iob-above-0-and-gradually-lowering-bg-targets) findest Du eine Grafik zur Erklärung. -- Wenn Du von AMA zu SMB wechselst, muss der Standardwert von 'min_5m_carbimpact' in den Absorptions-Einstellungen von 3 auf 8 erhöht werden. Wenn du also von AMA auf SMB umstellst, dann musst du den Wert manuell auf 8 erhöhen. - -(Objectives-objective-10-automation)= -## Ziel 10: Automatisierung - -- Du musst Ziel 10 starten, um [Automatisierungen](../Usage/Automation.md) nutzen zu können. -- Stelle sicher, dass Du alle vorausgegangenen Ziele inkl. des [Wissenstest](Objectives#objective-3-prove-your-knowledge) abgeschlossen hast. -- Andere, von Dir bereits abgeschlossene Ziele, werden dadurch nicht verändert. Du behälst alle Objectives, die Du bereits abgeschlossen hast! - -(Objectives-objective-11-DynamicISF)= -## Objective 11: Additional Features such as DynamicISF - -- You have to start objective 11 to be able to use [DynamicISF](../Usage/Open-APS-features.md) - -(Objectives-go-back-in-objectives)= -## Objective (Ziel) neu starten - -Wenn Du aus welchem Grund auch immer ein Objective (Ziel) neu starten willst, klicke auf "Ziel neu starten". - -```{image} ../images/Objective_ClearFinished.png -:alt: Objective (Ziel) neu starten - -``` - -## Objectives (Ziele) in Android APS-Versionen vor 3.0 - -Mit dem AndroidAPS Release 3.0 wurde ein Objective (Ziel) entfernt. Diejenigen, die eine Android APS version 2.8.2.1 verwenden, weil sie eine Android-Version vor Version 9 nutzen, finden [hier](../Usage/Objectives_old.md) die dort verwendeten Ziele. diff --git a/docs/CROWDIN/de/Usage/Objectives_old.md b/docs/CROWDIN/de/Usage/Objectives_old.md deleted file mode 100644 index 818a8493a86c..000000000000 --- a/docs/CROWDIN/de/Usage/Objectives_old.md +++ /dev/null @@ -1,152 +0,0 @@ -# Objectives as of Android APS 2.8.2.1 - -This is not the latest version of the Android APS Objectives. This page details the Objectives that were in place prior to version 3.0. Anyone using an older version of Android (i.e. prior to Android 9) and Android APS version 2.8.2.1 should refer to this page. - -Please see [this page](../Usage/Objectives.md) for the current set of Objectives. - -AndroidAPS hat eine Reihe von Zielen (objectives), die erreicht werden müssen, damit du an die Funktionen und Einstellungen von sicherem Looping herangeführt wirst. Sie stellen sicher, dass du alles, was in den Abschnitten weiter oben beschrieben wurde, korrekt installiert hast und dass du verstehst, was das System tut und warum du ihm vertrauen kannst. - -If you are **upgrading phones** then you can [export your settings](../Usage/ExportImportSettings.md) to keep your progress through the objectives. Not only will your progress through the objectives be saved, but also your safety settings such as max bolus etc. If you do not export and import your settings then you will need to start the objectives from the beginning again. It is a good idea to [backup your settings](../Usage/ExportImportSettings.html) frequently just in case. - -If you want to go back in objectives see [explanation below](../Usage/Objectives.md#go-back-in-objectives). - -## Ziel 1: Einrichten der Darstellung und Überwachung sowie analysieren der Basalraten und Faktoren - -- Select the right blood glucose source for your setup. See [BG Source](../Configuration/BG-Source.md) for more information. -- Select the right Pump in ConfigBuilder (select Virtual Pump if you are using a pump model with no AndroidAPS driver for looping) to ensure your pump status can communicate with AndroidAPS. -- If using DanaR pump then ensure you have followed [DanaR Insulin Pump](../Configuration/DanaR-Insulin-Pump.md) instructions to ensure the link between pump and AndroidAPS. -- Follow instructions in [Nightscout](../Installing-AndroidAPS/Nightscout.md) page to ensure Nightscout can receive and display this data. -- Note that URL in NSClient must be **WITHOUT /api/v1/** at the end - see [NSClient settings in Preferences](../Configuration/Preferences.md#nsclient). - -*You may need to wait for the next blood glucose reading to arrive before AndroidAPS will recognise it.* - -## Ziel 2: Lerne, wie AndroidAPS bedient wird - -- Perform several actions in AndroidAPS as described in this objective. - -- Click on the orange text "Not completed yet" to access the to-dos. - -- Links will be provided to guide you in case you are not familiar with a specific action yet. - - ![Screenshot Ziel 2](../images/Objective2_V2_5.png) - -## Ziel 3: Belege Dein Wissen - -- Pass a multiple-choice exam testing your AndroidAPS knowledge. - -- Click on the orange text "Not completed yet" to access the page with the question and answering options. - - ![Screenshot Ziel 3](../images/Objective3_V2_5.png) - -- Links will be provided to guide you in case you are unsure about the correct answers yet. - -- The questions for objective 3 have been completely rewritten by native speakers as of AAPS 2.8. Die neuen Fragen decken die bisherigen ab und fügen ein paar neue hinzu. - -- These new questions will lead to some not answered questions even though you have successfully completed objective 3 in previous versions. - -- Unanswered questions will affect you only if you start a new objective. Anders gesagt: Wenn du alle Ziele (objectives) bereits erfolgreich abgeschlossen hast, verlierst du keine Funktionen in AAPS, wenn du die neuen Fragen nicht beantwortest. - -## Ziel 4: Starte den Open Loop - -- Select Open Loop either from Preferences, or by pressing and holding the Loop button in top left of the home screen. -- Work through the [Preferences](../Configuration/Preferences.md) to set up for you. -- Manually enact at least 20 of the temporary basal rate suggestions over a period of 7 days; input them to your pump and confirm in AndroidAPS that you have accepted them. Überprüfe, ob diese Daten in AndroidAPS und Nightscout angezeigt werden. -- Enable [temp targets](../Usage/temptarget.md) if necessary. Nutze das Hypo Temp Target um zu verhindern, dass AAPS aufgrund des Blutzuckeranstiegs nach einer Hypo zu stark korrigiert. - -### Anzahl der Benachrichtigungen reduzieren - -- To reduce the Number of decisions to be made while in Open Loop set wide target range like 90 - 150 mg/dl or 5,0 - 8,5 mmol/l. - -- You might even want to wider upper limit (or disable Open Loop) at night. - -- In Preferences you can set a minimum percentage for suggestion of basal rate change. - - ![Open Loop Mindeständerung](../images/OpenLoop_MinimalRequestChange2.png) - -- Also, you do not need to act every 5 minutes on all suggestions... - -## Ziel 5: Open Loop inklusive der temporären Basalratenvorschläge verstehen - -- Start to understand the thinking behind the temp basal recommendations by looking at the [determine basal logic](https://openaps.readthedocs.io/en/latest/docs/While%20You%20Wait%20For%20Gear/Understand-determine-basal.html) and both the [forecast line in AndroidAPS homescreen](../Getting-Started/Screenshots.md#prediction-lines)/Nightscout and the summary of outputs from the calculations in your OpenAPS tab. - -Es ist möglicherweise sinnvoll, wenn du das Ziel höher als üblich ansetzt, bis du den Berechnungen und Einstellungen vertraust. Das System erlaubt: - -- a low target to be a minimum of 4 mmol (72 mg/dl) or maximum of 10 mmol (180 mg/dl) -- a high target to be a minimum of 5 mmol (90 mg/dl) and maximum of 15 mmol (225 mg/dl) -- a temporary target as a single value can be anywhere in the range of 4 mmol to 15 mmol (72 mg/dl to 225 mg/dl) - -Der Zielwert ist der Wert, auf dem die Berechnungen basieren und nicht der gleiche wie der, den du als Zuckerwert anstrebst. If your target is very wide (say, 3 or more mmol \[50 mg/dl or more\] wide), you will often find little AAPS action. Der vorhergesagte Glukosewert wird mit hoher Wahrscheinlichkeit innerhalb Deines Zielbereichs liegen und daher nicht viele temporäre Änderungen an der Basalrate vorgeschlagen werden. - -You may want to experiment with adjusting your targets to be a closer together range (say, 1 or less mmol \[20 mg/dl or less\] wide) and observe how the behavior of your system changes as a result. - -You can view a wider range (green lines) on the graph for the values you aim to keep your blood glucose within by entering different values in [Preferences](../Configuration/Preferences.md) > Range for Visualisation. - -![Stoppzeichen](../images/sign_stop.png) - -### Falls Du eine virtuelle Pumpe verwendest darfst Du nicht zum 6. Ziel wechseln. Klicke nicht auf 'Bestätigen/Verify' am Ende des 5. Ziels. - -![leer](../images/blank.png) - -## Ziel 6: Closed Loop mit Abschaltung bei niedrigen Glukose-Werten - -![Warnzeichen](../images/sign_warning.png) - -### Der Closed Loop korrigiert im Objective 6 keine hohen BZ-Werte, da nur low glucose suspend zum Einsatz kommt. Hohe BZ-Werte müssen daher von Dir manuell korrigiert werden! - -- Select Closed Loop either from [Preferences](../Configuration/Preferences.md) or by pressing and holding the Open Loop button in the top left of the home screen. - -- Set your target range slightly higher than you usually aim for, just to be safe. - -- Watch how temporary basals are active by viewing the blue basal text on the homescreen or the blue basal render on the homescreen graph. - -- Ensure your settings have supported AndroidAPS to avoid having to treat a low glucose over a period of 5 days. Wenn du nach wie vor häufige oder schwere Unterzuckerungen hast, dann solltest du DIA, Basalraten, ISF oder Kohlenhydrat-Faktoren anpassen. - -- You don't have to change your settings. Während Du Dich im Ziel 6 befindest, wird maxIOB intern automatisch auf Null gesetzt. Wenn Du zum Ziel 7 weitergehst, wird dies automatisch wieder deaktiviert. - -- The system will override your maxIOB settings to zero, which means if blood glucose is dropping it can reduce basal for you, but if blood glucose is rising then it will only increase basal if the basal IOB is negative (from a previous Low Glucose Suspend), otherwise basal rates will remain the same as your selected profile. - - ![Beispiel negatives IOB](../images/Objective6_negIOB.png) - -- If your basal IOB is negative (see screenshot above) a TBR > 100% can be issued also in objective 6. - -- Wenn du eine Hypo korrigierst, kann es vorkommen, dass danach Spitzen auftreten, die du nicht durch Erhöhung der Basalrate korrigieren kannst. - -## Ziel 7: Stelle den Closed Loop fein ein, erhöhe maxIOB über 0 und setze den Zielbereich langsam herunter - -- Raise your 'Maximum total IOB OpenAPS can’t go over' (in OpenAPS called 'max-iob') above 0 over a period of 1 day, the default recommendation is "average mealbolus + 3x max daily basal"(for SMB algorithm) or "3x max daily basal" (for older AMA algorithm) but you should slowly work up to this until you know your settings work for you (max daily basal = the maximum hourly value in any time segment of the day). - - Betrachte diese Empfehlung als Ausgangspunkt. Wenn Du den Faktor 3x verwendest und feststellst, dass AAPS Deinen BZ zu stark senkt, reduziere diesen Faktor (z.B. 2,..). Wenn Du Resistenzen feststellst, kannst Du diesen Faktor vorsichtig Schritt für Schritt erhöhen. - - ![max daily basal](../images/MaxDailyBasal2.png) - -- Once confident on how much IOB suits your looping patterns then reduce your targets to your desired level. - -## Ziel 8: Passe, falls notwendig, Basalraten und Faktoren an und aktiviere dann die Autosens-Funktion - -- You can use [autotune](https://openaps.readthedocs.io/en/latest/docs/Customize-Iterate/autotune.html) as a one off to check your basals remain accurate or do a traditional basal test. -- Enable [autosens](../Usage/Open-APS-features.md) over a period of 7 days and watch the white line on the homescreen graph show how your sensitivity to insulin may be rising or falling as a result of exercise or hormones etc. and keep an eye in the OpenAPS report tab how AndroidAPS is adjusting the basals and/or targets accordingly. - -*Don’t forget to record your looping in* [this form](https://bit.ly/nowlooping) *logging AndroidAPS as your type of DIY loop software, if you have not already done so.* - -## Ziel 9: Teste zusätzliche Funktionen für den Alltagsgebrauch und gewinne Vertrauen in Dein Closed Loop System - -- Before AAPS version 2.7 meal assist (MA) was the basic algorithm for AAPS and completing objective 8 was necessary to activate [advanced meal assist (AMA)](../Usage/Open-APS-features.md#advanced-meal-assist-ama). -- As [advanced meal assist (AMA)](../Usage/Open-APS-features.md#advanced-meal-assist-ama) is the standard algorithm from AAPS version 2.7 onwards use the following 28 days to try features you haven't used yet and get more confident with you closed loop system. - -## Ziel 10: Aktiviere zusätzliche oref1 Funktionen zum täglichen Gebrauch, wie z. B. den super micro bolus (SMB) - -- You must read the [SMB chapter in this wiki](../Usage/Open-APS-features.md#super-micro-bolus-smb) and [chapter oref1 in openAPSdocs](https://openaps.readthedocs.io/en/latest/docs/Customize-Iterate/oref1.html) to understand how SMB works, especially what's the idea behind zero-temping. -- Then you ought to [rise maxIOB](../Usage/Open-APS-features.md#maximum-total-iob-openaps-cant-go-over-openaps-max-iob) to get SMBs working fine. maxIOB enthält nun das gesamte IOB, nicht nur das hinzugefügte Basalinsulin. That is, if given a bolus of 8 U for a meal and maxIOB is 7 U, no SMBs will be delivered until IOB drops below 7 U. A good start is maxIOB = average mealbolus + 3x max daily basal (max daily basal = the maximum hourly value in any time segment of the day - see [objective 7](../Usage/Objectives#objective-7-tuning-the-closed-loop-raising-max-iob-above-0-and-gradually-lowering-bg-targets) for an illustration) -- min_5m_carbimpact default in absorption settings has changed from 3 to 8 going from AMA to SMB. Wenn du also von AMA auf SMB umstellst, dann musst du den Wert manuell auf 8 erhöhen. - -## Ziel 11: Automatisierung - -- You have to start objective 11 to be able to use [Automation](../Usage/Automation.md). -- Make sure you have completed all objectives including exam [../Usage/Objectives.md#objective-3-prove-your-knowledge](../Usage/Objectives#objective-3-prove-your-knowledge). -- Completing previous objectives will not effect other objectives you have already finished. Du behälst alle Objectives, die Du bereits abgeschlossen hast! - -## Objective (Ziel) neu starten - -Wenn Du aus welchem Grund auch immer ein Objective (Ziel) neu starten willst, klicke auf "Ziel neu starten". - -![Objective (Ziel) neu starten](../images/Objective_ClearFinished.png) diff --git a/docs/CROWDIN/de/Usage/Smoothing-Blood-Glucose-Data-in-xDrip.md b/docs/CROWDIN/de/Usage/Smoothing-Blood-Glucose-Data-in-xDrip.md deleted file mode 100644 index fa19c06e02ae..000000000000 --- a/docs/CROWDIN/de/Usage/Smoothing-Blood-Glucose-Data-in-xDrip.md +++ /dev/null @@ -1,33 +0,0 @@ -(Smoothing-Blood-Glucose-Data-in-xDrip-smoothing-blood-glucose-data)= - -# Glättung der Blut-Glukose-Daten - -Wenn die BZ-Daten Sprünge haben oder verrauscht sind, kann es dazu kommen, dass AndroidAPS das Insulin falsch dosiert. Zu hohe oder zu niedrige BZ-Werte können die Folge sein. Daher ist es wichtig, den Loop zu pausieren, bis die Probleme beseitigt sind. Abhängig von Deinem CGM-System können solche Probleme durch die CGM-Konfiguration oder Probleme mit dem Sensor oder der Einsetzstelle entstehen. Ggf. musst Du einen neuen Sensor setzen, um den Fehler zu beheben. - -Some CGM systems have internal algorithms to detect the noise level in the readings and AAPS can use this information to avoid giving SMBs if the BG data is too unreliable. Für die CGMs, die diese Informationen nicht übermitteln, werden die Funktionen 'Aktiviere SMB immer' und 'Aktiviere SMB nach Mahlzeiten' aus Sicherheitsgründen deaktiviert. - -## Dexcom-Sensoren - -### Build your own Dexcom App - -Wird [BYODA](DexcomG6-if-using-g6-with-build-your-own-dexcom-app) genutzt, sind die Glukose-Daten stimmig und geglättet. Außerdem kannst Du die rückwirkende Glättung von Dexcom nutzen. Da die Qualität der Messwerte an AAPS übermittelt wird, können SMBs ohne Einschränkungen genutzt werden. - -### xDrip+ mit Dexcom G6 oder Dexcom ONE - -Die Qualität der Messwerte und geglättete Glukosewerte werden an AAPS nur im [nativen Modus](https://navid200.github.io/xDrip/docs/Native-Algorithm) übermittelt. Im nativen Modus können SMBs ohne Einschränkungen genutzt werden. - -### Dexcom G6 oder Dexcom ONE mit xDrip+ Companion App - -Die Qualität der Messwerte wird nicht an AAPS übermittelt. Die Funktionen 'Aktiviere SMB immer' und 'Aktiviere SMB nach Mahlzeiten' sind deaktiviert und können nicht genutzt werden. - -## Freestyle Libre Sensoren - -### xDrip+ mit FreeStyle Libre - -Keines der FreeStyle Libre Systeme (FSL1, FSL2 oder FSL3) sendet Informationen über die Qualität der Messwerte. Deswegen sind die Funktionen 'Aktiviere SMB immer' und 'Aktiviere SMB nach Mahlzeiten' bei der Nutzung mit allen FreeStyle Libre Systemen deaktiviert. - -Darüber hinaus haben viele Leute berichtet, dass der FreeStyle Libre oft verrauschte (springende) Werte erzeugt. In xDrip+ gibt es ein paar Optionen die Abhilfe schaffen können: - -**Smooth Sensor Noise.** In den xDrip+ Einstellungen > xDrip+ Anzeigeeinstellungen muss "Smooth Sensor Noise" aktiviert sein. Es wird dann versucht, übertragene verrauschte Werte zu glätten. - -**Smooth sensor noise (Ultrasensitive).** Wenn Du weiterhin verrauschte Werte in xDrip+ hast, dann kannst Du sie noch aggressiver glätten, indem Du die Einstellung Smooth Sensor Noise (Ultrasensitiv) verwendest. Das wird auch dann eine Rauschglättung auslösen, wenn nur geringes Rauschen erkannt wird. Dazu musst du zuerst den [engineering mode](Enabling-Engineering-Mode-in-xDrip.md) in xDrip+ aktivieren. Gehe dann zu Einstellungen > xDrip+ Anzeigeeinstellungen und aktivieren Smooth Sensor Noise (Ultrasensitiv). \ No newline at end of file diff --git a/docs/CROWDIN/de/Usage/autotune_b.md b/docs/CROWDIN/de/Usage/autotune_b.md deleted file mode 100644 index cbd4a34d4701..000000000000 --- a/docs/CROWDIN/de/Usage/autotune_b.md +++ /dev/null @@ -1,186 +0,0 @@ -# How to use Autotune plugin - -Documentation about Autotune algorythm can be found in [OpenAPS documentation](https://openaps.readthedocs.io/en/latest/docs/Customize-Iterate/autotune.html). - -Autotune plugin is an implementation of OpenAPS autotune algorythm within AAPS. - -**Currently Autotune Plugin is only available in dev branch with Engineering mode.** - -## Autotune user interface - -![Autotune default screen](../images/Autotune/Autotune_1b.png) - -- You can select in the Profile dropdown menu the input profile you want to tune (by default your current active profile is selected) - - Note: each time you select a new profile, previous results will be removed and Tune days parameter will be set to default value -- Then Tune days is to select the number of days used in calculation to tune your profile. The minimum value is 1 day and the maximum value 30 days. This number should not be too small to get correct iterative and smooth results (above 7 days for each calculation) - - Note: each time you change Tune days parameter, previous results will be removed -- Last Run il a link that recover your latest valid calculation. If you didn't launch Autotune on current day, or if previous results was removed with a modification of calculation parameter above, then you can recover parameters and results of the latest successfull run. -- Warning show you for example some information about selected profile (if you have several IC values or several ISF values) - - Note: Autotune calculation works with only a single IC and a single ISF value. There is currently no existing Autotune algorythm to tune a circadian IC or circadian ISF. If your input profile has several values, you can see in warning section the average value taken into account to tune your profile. -- Check Input Profile button open the Profile Viewer to allow you a quick verification of your profile (Units, DAI, IC, ISF, basal and target) - - Note: Autotune will only tune your IC (single value), ISF (single value) and basal (with circadian variation). Units, DAI and target will remain unchanged in output profile. - -- "Run Autotune" will launch Autotune calculation with selected profile and the number of Tune days - - Note: Autotune calculation can take a long time. Once launched, you can switch to another view (home, ...) and come back later in Autotune plugin to see results - -![Autotune Run start](../images/Autotune/Autotune_2b.png) - -- Then during the run you will see intermediate results below - - - Note: During run, settings are locked, so you cannot change anymore selected input profile or the number of day. You will have to wait the end of current calculation if you want to launch another run with other parameters. - - ![Autotune during run](../images/Autotune/Autotune_3b.png) - -- When Autotune calculation is finished, you will see the result (Tuned profile) and four buttons below. - -![Autotune Result](../images/Autotune/Autotune_4b.png) - -- It's important to always compare input profile (column "Profile"), output profile (column "Tuned") and the percentage of variation for each value (Column "%"). - -- For basal rates, you also have the number of "missing days". You have missing days when Autotune don't have enough data categorized as "Basal" to tune basal rate for this period (for example after each meal when you have carbs absorption). This number should be as low as possible especially when basal is important (for example during the night or at the end of the afternoon) - -- The "Compare profiles" button open the profile comparator view. Input profile is in blue, and output profile (named "Tuned") is in red. - - - Note: in the example below input profile has circadian variation for IC and ISF, but output calculated profile has a single value. If it's important for you to get a circadian output profile see [Circadian IC or ISF profile](#circadian-ic-or-isf-profile) below. - - ![Autotune Compare profiles](../images/Autotune/Autotune_5.png) - -- If you trust results (low percentage of variation between input profile and output profile), you can click on "Activate profile" button and then click on OK to validated. - - - Activate Tuned profile will automatically create a new profile "Tuned" in your Local profile plugin. - - If you already have a profile named "Tuned" in your local profile plugin, then this profile will be updated with calculated Autotune profile before the activation - - ![Autotune Activate profile](../images/Autotune/Autotune_6.png) - -- If you think Tuned profile must be adjusted (for example if you think some variation are too important), then you can click on "Copy to local profile" button - - - A new profile with the prefix "Tuned" and the date and time of the run will be created in local profile plugin - -![Autotune Copy to local profile](../images/Autotune/Autotune_7.png) - -- You can then select local profile to edit the Tuned profile (it will be selected by default when you open Local profile plugin) - - - the values in local profile will but rounded in the user interface to your pump capabilities - - ![Autotune local profile update](../images/Autotune/Autotune_8.png) - -- If you want to replace your input profile with Autotune result, click on "Update input profile" button and validate the Popup with OK - - - Note: if you click on "Activate profile" after "Update input profile", then you will activate your updated profile and not the default "Tuned" profile? - - ![Autotune Update input profile](../images/Autotune/Autotune_9.png) - -- If you have updated your input profile, then the "Update input profile" button is replaced by "Revert input profile" button (see screenshot below). You can that way immediatly see if your current input profile in Local profile plugin already include the result of last run or not. You also have the possibility to recover you input profile without autotune result with this button - - ![Autotune Update input profile](../images/Autotune/Autotune_10.png) - - - -## Autotune settings - -### Autotune plugin settings - -![Autotune default screen](../images/Autotune/Autotune_11.png) - -- Automation Switch Profile (default Off): see [Run Autotune with an automation rule](#run-autotune-with-an-automation-rule) below. If you change this setting to On, the input profile will automatically be updated by the Tuned profile, and it will be activated. - - **Be Carefull, you must trust and verified during several following days that after an update and activation of Tuned profile without modification, it improves your loop** - -- Categorize UAM as basal (default On): This setting is for the users using AndroidAPS without any carbs entered (Full UAM). It will prevent (when Off) to categorize UAM as basal. - - Note: if you have at least one hour of Carbs absorption detected during one day, then all data categorized as "UAM" will be categorized as basal, whatever this setting (On or Off) -- Number of days of data (default 5): You can define default value with this setting. Each time your select a new profile in Autotune plugin, Tune days parameter will be replaced by this default value -- Apply average result in circadian IC/ISF (default Off): see [Circadian IC or ISF profile](#circadian-ic-or-isf-profile) below. - -### Andere Einstellungen - -- Autotune also uses Max autosens ratio and Min autotsens ratio to limit variation. You can see and adjust these values in Config Builder > Sensitivity detection plugin > Settings > Advanced Settings - - ![Autotune default screen](../images/Autotune/Autotune_12.png) - - - -## Advanced feature - -### Circadian IC or ISF profile - -- If you have important variation of IC and/or you ISF in your profile, and you fully trust in your circadian time and variation, then you can set "Apply average result in circadiant IC/ISF" - - - Note that Autotune calculation will always be done with a single value, and circadian variation will not be tuned by Autotune. This setting only apply average variation calculated for IC and/or ISF on your circadian values - -- See on screenshot below Tuned profile with Apply average variation Off (on the left) and On (on the right) - - ![Autotune default screen](../images/Autotune/Autotune_13.png) - - - -### Tune specific days of the week - -- If you click on the checkbox with the eye on the right of "Rune days" parameter, you will see the day selection. You can specify which day of the week should be included in Autotune calculation (in screenshot below you can see an example for "working days" with Saturday and Sunday removed from autotune calculation) - - If the number of day included in Autotune calculation is lower than the number of Tune days, then you will see how many days will be included on the right of Tune days selector (10 days in the example below) - - This setting gives good results only if the number of remaining days is not to small (for example if you Tune a specific profile for week end days with only Sunday and Saturday selected, you should select a minimum of 21 or 28 Tune days to have 6 or 8 days included in Autotune calculation) - -![Autotune default screen](../images/Autotune/Autotune_14b.png) - -- During Autotune calculation, you can see the progress of the calculations ("Partial result day 3 / 10 tuned" on example below) - - ![Autotune default screen](../images/Autotune/Autotune_15b.png) - -## Run Autotune with an automation rule - -First step is to define correct trigger for an automation rule with Autotune: - -Note: for more information on how to set an automation rule, see [here](./Automation.rst). - -- You should select Recurring time trigger: only run Autotune once per day, and autotune is designed to be runned daily (each new run you shift one day later and quickly profile modification should be tiny) - - ![Autotune default screen](../images/Autotune/Autotune_16.png) - -- It's better at the beginning to run Autotune during the day to be able to check results. If you want to run Autotune during the night, you have to select in the trigger 4AM or later to include current day in next Autotune Calculation. - - ![Autotune default screen](../images/Autotune/Autotune_17.png) - -- Then you can select "Run Autotune" Action in the list - - ![Autotune default screen](../images/Autotune/Autotune_18.png) - -- You can then select Autotune Action to adjust parameters for your run. Default parameters are "Active Profile", default Tune days value defined in Autotune Plugin preferences, and All days are selected. - - ![Autotune default screen](../images/Autotune/Autotune_19b.png) - -- After a few days, if you fully trust Autotune results and percentage of modification is low, you can modify [Autotune settings](#autotune-plugin-settings) "Automation Switch Profile" to enabled to automatically update and activate profile tuned after calculation. - -Note: if you want to automatically tune profiles for specific days of the week (for example a profile for "Weekend days" and another one for "Working days"), then create one rule for each profile, select the same days in Trigger and in Autotune Action, Tune days must be high enough to be sure tuning will be done with at least 6 or 8 days, and don't forget to select time after 4AM in trigger... - -- See below an example of rule to tune "my profile" on all "Working days" with 14 Tune days selected (so only 10 days included in autotune calculation). - -![Autotune default screen](../images/Autotune/Autotune_20b.png) - - - -## Tips and trick's - -Autotune works with information existing in your database, so if you just installed AAPS on a new phone, you will have to wait several days before being able to launch Autotune with enough days to get relevant results; - -Autotune is just an help, it's important to regularly check if you agree with calculated profile. If you have any doubt, change Autotune settings (for example the number of days) or copy results in local profile and adjust profile before using it. - -Always use Autotune several days manually to check results before applyling them. And it's only when you fully trust Autotune results, and when variation becomes tiny between previous profile and calculated profile than you start to use Automation (Never before) - -- Autotune can work very well for some users and not for others, so **If you don't trust Autotune result, don't use it** - -It's also important to analyse Autotune results to understand (or try to understand) why Autotune propose these modifications - -- you can have a whole increase or decrease of the strength of your profile (for example increase of total basal associated to decrease of ISF and IC values). it could be associated to several following days with autosens correction above 100% (more agressivity required) or below 100% (you are more sensitive) -- Sometimes Autotune propose a different balance between basal rates and IC/ISF (for ex lower basal and more aggressive IC/ISF) - -We advise to not use Autotune in the following cases: - -- You don't enter all your carbs - - If you don't enter carbs correction for an hypoglycemia, Autotune will see an unexcepted increase of your BG value and will increase your basal rates the ' hours earlier, it could be the opposite of what you need to avoid hypo, especially if it's in the middle of the night. That's why it's important to enter all carabs especially correction for hypo. -- You have a lot of period with UAM detected during the day. - - Do you have entered all your carbs and correctly estimated your Carbs ? - - All UAM periods (except if you enter no carbs during a day and categorized UAM as basal is disabled), all your UAM periods will be categorized as basal, this can increase a lot your basal (much more than necessary) - -- Your carbs absorption is very slow: if most of your carbs absorption are calculated with min_5m_carbimpact parameter (you can see these periods with a little orange dot in the top of COB curve), the calculation of COB could be wrong and leads to wrong results. - - We you practice sport, you are generally more sensitive and your BG doesn't rise a lot, so during or after an exercice, it's usual to see some periods with slow carbs. But if you have too often unexpected slow carb absorption, then you may need a profile adjustment (higher value of IC) or a min_5m_carbimpact a bit to high. -- You have a "very bad days", for example stuck several hours in hyperglycemia with a huge amount of insulin to be able to go down within the range, or after a sensor change you got long periods of wrong BG values. -- If the percentage of modification is too important - - You can try to increase the number of days to get smoother results \ No newline at end of file diff --git a/docs/CROWDIN/de/Usage/making-sport-with-AAPS.md b/docs/CROWDIN/de/Usage/making-sport-with-AAPS.md deleted file mode 100644 index 79d2f1c38223..000000000000 --- a/docs/CROWDIN/de/Usage/making-sport-with-AAPS.md +++ /dev/null @@ -1,185 +0,0 @@ -# making sport with AAPS - -In this section we want to address the topic of sport with AAPS. - -The aim is to show you how AAPS can help you to continue doing your favorite sport more easily or even to start doing it. It is relatively common for new type 1 diabetics to ask whether exercise is still possible for them, even if the answer in the training courses is actually a clear yes. Exercise is not only good for healthy people, but also for type 1 diabetics and even moderate exercise can even help to stabilize the blood sugar curve overall. - -:::{admonition} consult with your diabetes team after reading - -::: - -The difficulty here is that the prerequisites that someone brings with them and the expectations of what sport means to them are very different. - -Since we can assume that experienced top athletes with T1D who use AAPS are unlikely to look it up here, we deliberately set the bar low for ourselves when writing and for you when reading and using it, so that as many people as possible can benefit from it. - -Since even sport as a category is far too imprecise, as the effects of endurance sports differ greatly from strength training, for example, we are trying to break it down by type of sport. - -To be concrete and give you something you can test yourself we arrange the explanaiton around a concrete example and explain to you they action, reactions and effects. - -:::{admonition} more examples wanted - -The focus should always be on how others can do sport and not on the top performance someone has achieved. - -It's really about the basics. Your experience, which you share here, can help others to pursue their beloved sport more quickly and successfully and is therefore important. -::: - -## Cycling - -:::{admonition} take a friend with you - at least on your first trials -:class: information -A gerneral very good idea can be to take a good friend with you on the first rides. -This is especially important if you are not experienced in T1D. -Always keep in mind please: arrival comes before speed! Safety for you and the others in road traffic is very, very important. -::: - -### Example - -Let's take about 60 minutes of cycling on a flat route with a moderate heart rate as an example. - -1. we take a flat route in order to have an even load for the first exercise. This is not about performance, but purely about learning how you should react to changes in blood glucose. -2. we take the heart rate as an indicator of the load, as it is easy to see whether you are under load or not. -3. we set ourselves the goal of doing a relaxed lap around the neighborhood and focus on staying within our target range during the lap. In my case, this would be 70 <= x <= 180 mg/dl. - -We **don't** take the speed, as this is heavily dependent on personal physical conditions as well as the bike and surface used. It is therefore not very meaningful. - -You should know from the diabetes training courses you have attended that during endurance sports cycling, the insulin active in the body works significantly better than during times without physical exertion. The insulin active in the body is referred to as insulin on board (IoB). It is our most important parameter when cycling with T1D. - -We try to keep the IoB as low as possible at the start and during exercise. IoB should be around 0 or even slightly negative. You can get it there by not eating 3-4 hours before exercise. In the beginning it can also be helpful to exercise in the morning before breakfast, as with the right profile you should always have around 0 for IoB in the morning. - -AAPS shows us the IoB value on the home screen on the left under the blood glucose value. - -![IoB](../images/cycling_20240104-174035.png) - -:::{admonition} ignoring the IoB rule increases the risk for roller coaster BG dramatically -:class: danger -If you ignore this rule, you can still go cycling, but it will be much more difficult to keep your blood sugar levels in balance, so it is better to save this for later tests after several successful simple tests. -::: - -As you should know from the diabetes training courses, you should reduce the basal rate during exercise. The factor is individual. I have found a value of 50% in tests to be suitable for me. - -In AAPS, you should therefore change your profile to 50% before exercise and keep it active until the end of exercise. Some people even do it a certain amount of time before, e.g. 1 hour. Unfortunately, the pre-run is also individual. We will come to the post-run later. - -You should use two carbohydrates during exercise. - -1. medium-fast carbohydrates for the insulin still in the body and -2. very fast carbohydrates to prevent slipping into a hypo. - -For medium-fast carbohydrates, I treat myself to cookies or a banana before exercise, for example. You can also use something else that is more suitable for you. -For very fast carbohydrates, I take 3 teaspoons of dissolved glucose per 100 ml of still water in a 500 ml water bottle on my bike. If I'm cycling longer distances, I take a larger bottle with me and, if necessary, packaged glucose to refill the bottle. I add a little lemon juice for flavor. You can also use something other than lemon juice for the taste. You shouldn't change anything about the dextrose, as dissolved dextrose raises blood sugar levels super quickly. If you only take it in sips, your blood sugar won't go super high either! You can also do this tip at home beforehand as a dry run and see how quickly the change shows up on the CGMS. - -Why do I place so much emphasis on fast carbohydrates? - -1. once you are in a slight hypo, you may get back into the normal range by drinking the dextrose solution. As a rule, however, the oscillation of the curve then begins, which leads to a rollercoaster ride of the blood sugar. You may even be able to keep this within your target range, but you must be constantly vigilant. Without a hypo it is simply the most stable. -2. if you even slip into a somewhat severe hypo (without the need for outside help, of course), you may even have to pause briefly to avoid getting stuck in the hypo. - With both hypos, there is a risk that you will be tempted to switch from drinking 2-3 sips at a time to larger quantities. Not too bad at first, until the oscillation sets in and pushes you into a hyper. You can correct this, but your blood sugar will most likely go on a rollercoaster ride. - -What else is helpful, but not absolutely necessary? -It is important to keep an eye on your blood sugar, as your blood sugar can change enormously (e.g. 30 - 50 mg/dl) within 15 minutes of riding and a little more IoB or a basal rate that is still too high. The best way to keep an eye on it is if it is visible on the handlebars or if it is also displayed on your watch. It is even possible to install an additional app on some Garmin GPS bike computers that displays the blood glucose from XDrip or Nightscout as a data field on the bike computer. The additional app was developed by Andreas May from the T1D community. It is available free of charge in the official connect IQ Store. Certainly an interesting option for riders interested in sports. - -[Link to Andreas May Data Field App on connect IQ store](https://apps.garmin.com/de-DE/apps/5a3e2cda-12f0-4afd-88ed-000e67a68d84) - -Here is a picture of my Garmin Edge 530 bike computer with map, blood sugar and heart rate. - -![Garmin Edge 530 with BG data field](../images/cycling_IMG_1087.jpeg) - -After you have eaten the medium fast carbohydrates (24 - 36 g I take) and the blood sugar is above 100 mg/dl but also below 160 mg/dl, I carry out the profile change to 50% and set the activity temp target. - -:::{admonition} disable SMBs during high temp targets if necessary -:class: danger -Attention: If you prefer not to receive SMBs during the sport, please disable the option "Enable SMB with hight temp targets" in the settings of SMB or DynIFS Plugin. -::: - -The following picture shows the start and end of the sport. The end was specified as the duration when the profile was changed at the start. - -The temporary profile change has the following effects - -1. for a period of 60 minutes -2. a reduction to 50% of the profile and -3. the target is raised by clicking on the Activity Target option, which may have the side effect of disabling the SMBs - see above. - -![profile switch with temp target](../images/cycling_20240104-174056.png) - -The second image shows that the start at IoB was started towards 0. - -![IoB around 0](../images/cycling_20240104-174111.png) - -If the blood sugar drops faster than 15 mg/dl in 5 minutes or if it is at 120 mg/dl and tends to fall, I drink 1-2 sips of dissolved glucose. Then I wait for the next value and proceed as described above. - -You can hardly see it here, but at the beginning I took 2 sips from the bottle several times when my blood sugar started to fall. When it stabilized, I didn't need any more glucose. - -Here is the picture that illustrates this. The chart is saved on the Garmin as a result of the activity. - -![BG chart Garmin](../images/cycling_20240104-174431.png) - -If you should suddenly break out upwards, i.e. above 180 mg/dl, you should consider whether you should make a correction bolus. Caution: Remember the factor and apply it to the correction, otherwise the correction will be too strong. - -If your blood sugar drops below 80 mg/dl, take a break and drink two sips until your blood sugar is back above 100 mg/dl. - -At the end of the ride, the profile change should be finished as the time is up. - -Since we only rode easy for 60 minutes, there shouldn't be a big muscle bulking effect continuing to pull carbohydrates from your blood sugar. However, if it felt strenuous to you, keep an eye on it. This is especially true if you then go straight to bed. It may be better to change your profile to e.g. 80% for sleep. You may come out of sleep slightly too high, but it's better than having a hypo at night. Over time, you will surely find out what happens to you. - -The following pictures show the low intensity of the sport. - -The elevation profile -![](../images/cycling_20240104-174314.png) - -Speed with average and maximum speed - -![](../images/cycling_20240104-174326.png) - -Note the pause at the level crossing, which is also reflected in the heart rate. - -The heart rate. -![](../images/cycling_20240104-174337.png) - -The training effect. -![](../images/cycling_20240104-174358.png) - -The time in the different heart rate training zones. -![](../images/cycling_20240104-174423.png) - -After succesfully mastering this simple example you could go for further targets by stretching - -1. the distance and time -2. the load during the ride -3. the elevation during the right which should make a big impact on the more necessary carbs or further reduction of IoB and percentage of profile switch. - -Based on my experiences I would not expect to come back 100% with time in range over the whole and every ride. - -### Tipps - -I already gave some tipps for during the ride above. - -Here are some further tipps what can go wrong and how you can act to prevent it or react to compensate it. - -#### sky rocket high after ride - -During the ride everything was fine but after siting down and relax the blood sugar go sky rocket high. - -**Possible reason:** This happens when you have drunk too much dissolved glucose. - -**Reaction:** Drink 500 ml water, go to the shower and then control again. Latest after 30 minutes think about giving a correction bolus but be careful when it is short for bed time. Therefore it can be very good to make the first try runs on weekend mornings. - -**Action:** Next time be a bit more cautious in drinking from the dissolved glucose. - -#### hypo during ride - -During the ride you are going into hypo and can't recover your blood sugar during cycling. - -**Possible reason:** Your body cannot absorb enough carbohydrates quickly enough during exercise. - -**Reaction:** Take a rest and corrrect your blood sugar with drinking dissolved glucose. Stay calm: arrival comes before speed. - -**Action:** Did you started with IoB near 0? Have you eaten a small amount of middle fast carbs? Can you increase this or are the not fast enough for your body? Is it possible to prevent going into hypo by reducing the factor for the profile switch? Have you disbaled SMBs during ride as explained above? - -#### sky rocket high during ride - -During the ride your blood sugar goes sky rocket high. - -**Possible reason:** You have got taken too much carbs for your IoB at that time. Beneath for sure the typical technical problems with your -insulin pump like leakage or blockage of the catheder! - -**Reaction:** If it is too high for you take a rest and correct with a bolus. Keep in mind that you must ride home and therefore make it carefully. Drink 500 ml pure water without carbs. Stay calm: arrival comes before speed. - -**Action:** Have you eaten too much? Especially have you drunk too much from the dissolved glucose during the ride? Is your percentage of reduction the profile during profile switch too low and you can increase this? diff --git a/docs/CROWDIN/de/Where-To-Go-For-Help/How-to-get-support.md b/docs/CROWDIN/de/Where-To-Go-For-Help/How-to-get-support.md deleted file mode 100644 index b8162cfd97dd..000000000000 --- a/docs/CROWDIN/de/Where-To-Go-For-Help/How-to-get-support.md +++ /dev/null @@ -1,11 +0,0 @@ -# Wie erhalte ich Support? - -** Stufe 1:** Wiki - jetzt mit Suchfunktion! - -** Stufe 2:** [Facebook](https://www.facebook.com/groups/AndroidAPSUsers/) ODER [gitter](https://gitter.im/MilosKozak/AndroidAPS) - -**Stufe 3:** Gitter (wenn Facebook keine Ergebnisse liefert, warte zumindest ein paar Stunden (Plural)!!! Identische Posts werden auf beiden Kanälen ignoriert/gelöscht!!!) - -**Stufe 4:** Erstelle ein Issue mit Logdateien und Uhrzeit, wann das Problem aufgetreten ist - -**Stufe 5:** Private Nachricht (nur wenn persönliche Daten betroffen sind, die nicht auf einem öffentlichen Kanal verbreitet werden sollen) \ No newline at end of file diff --git a/docs/CROWDIN/de/buildingAAPS.md b/docs/CROWDIN/de/buildingAAPS.md deleted file mode 100644 index 98164a09e49b..000000000000 --- a/docs/CROWDIN/de/buildingAAPS.md +++ /dev/null @@ -1,28 +0,0 @@ -# Dummy - -## This is a dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - - -## This is another dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - - -## This is another another dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - diff --git a/docs/CROWDIN/de/completingObjetives.md b/docs/CROWDIN/de/completingObjetives.md deleted file mode 100644 index 98164a09e49b..000000000000 --- a/docs/CROWDIN/de/completingObjetives.md +++ /dev/null @@ -1,28 +0,0 @@ -# Dummy - -## This is a dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - - -## This is another dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - - -## This is another another dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - diff --git a/docs/CROWDIN/de/dummy.md b/docs/CROWDIN/de/dummy.md deleted file mode 100644 index 98164a09e49b..000000000000 --- a/docs/CROWDIN/de/dummy.md +++ /dev/null @@ -1,28 +0,0 @@ -# Dummy - -## This is a dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - - -## This is another dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - - -## This is another another dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - diff --git a/docs/CROWDIN/de/intro.md b/docs/CROWDIN/de/intro.md deleted file mode 100644 index 78daf8f6b9ac..000000000000 --- a/docs/CROWDIN/de/intro.md +++ /dev/null @@ -1,291 +0,0 @@ -![20-06-23v2 AAPS simple overview-cropped](https://github.com/openaps/AndroidAPSdocs/assets/94044064/e505b73b-09a0-42a4-a1ab-b830a0741234) - -# Introduction to APS and AAPS - -## What is an “Artificial Pancreas System”? - -A human pancreas does a lot of things besides regulating blood sugar. However, the term **“Artificial Pancreas System” (APS)** usually refers to a system which works to automatically keep blood sugar levels within healthy limits. - -The most basic way to do this is by detecting **glucose levels**, using these values to do **calculations**, and then delivering the (predicted) right amount of **insulin** to the body. It repeats the calculation, every few minutes, 24/7. It uses **alarms** and **alerts** to inform the user if intervention or attention is needed. This system is typically made up of a **glucose sensor**, an **insulin pump** and an **app** on a phone. - -You can read more about the different artificial pancreas systems currently in use and in development in this 2022 review article: - -![Frontiers](./images/FRONTIERS_Logo_Grey_RGB.png) [Future Directions in Closed-Loop Technology](https://www.frontiersin.org/articles/10.3389/fendo.2022.919942/full#:~:text=Fully%20closed%2Dloop%20systems%2C%20unlike,user%20input%20for%20mealtime%20boluses). - -In the near future, some so-called "dual-hormone" systems will also have the ability to infuse glucagon alongside insulin, with the aim of preventing severe hypos and allowing even tighter blood glucose control. - -An artificial pancreas can be thought of as an [“autopilot for your diabetes”]. (https://www.artificialpancreasbook.com/) What does that mean? In an aircraft, an autopilot does not do the complete job of the human pilot, the pilot cannot sleep through the entire flight. The autopilot aids the work of the pilot. It relieves them of the burden of permanently monitoring the aircraft, allowing the pilot to concentrate on wider monitoring from time to time. The autopilot receives signals from various sensors, a computer evaluates them together with the pilot’s specifications and then makes the necessary adjustments, alerting the pilot to any concerns. The pilot no longer has to worry about constantly making decisions. - -## What does hybrid closed loop mean? - -The best solution for type 1 diabetes would be a “functional cure” (probably an implant of pancreatic cells which are protected from the immune system). While we are waiting for that, a “full closed loop” artificial pancreas is probably the next best thing. This is a tech system that doesn’t need any user input (like bolusing insulin for meals, or announcing exercise), with good regulation of blood glucose levels. At the moment, there are no widely available systems which are “full” closed loop, they all need some user input. The currently available systems are called “hybrid” closed loop, because they use a combination of automated technology and user input. - -## How and why did looping start? - -The development of commercial technology for people with type 1 diabetes (T1D) is very slow. In 2013 the T1D community founded the #WeAreNotWaiting movement. They developed systems themselves using existing approved technology (insulin pumps and sensors) to improve blood glucose control, safety, and quality of life. These are known as DIY (do-it-yourself) systems, because they are not formally approved by health bodies (FDA, NHS etc). There are four main DIY systems available: OpenAPS, **AAPS**, Loop and iAPS. - -A great way to understand the fundamentals of DIY looping is to read Dana Lewis’s book “Automated Insulin Delivery”. You can access it \[here\] (https://www.artificialpancreasbook.com/) for free (or buy a hardcopy of the book). If you want to understand more about OpenAPS, which** AAPS** has developed from, the \[OpenAPS website\] (https://openaps.org/what-is-openaps/) is also a great resource. - -Several commercial hybrid closed loop systems have been launched, the most recent of which are \[CamAPS FX\] (https://camdiab.com/) (UK and EU) and \[Omnipod 5\] (https://www.omnipod.com/en-gb/what-is-omnipod/omnipod-5) (USA and EU). These are very different to DIY systems, mainly because they both include a “learning algorithm” which adjusts how much insulin is delivered according to your insulin needs from previous days. Many people in the DIY community have already tried out these commercial systems and compared them with their DIY system. You can find out more about how the different systems compare by asking on the dedicated Facebook groups for these systems, on the \[AAPS Facebook group\] (https://www.facebook.com/groups/AndroidAPSUsers/) or on \[Discord\] (https://discord.com/invite/4fQUWHZ4Mw). - -## What is Android APS (AAPS)? - -![image](https://github.com/openaps/AndroidAPSdocs/assets/94044064/0f089d96-b7ee-452a-aa9d-aae10ab58971) - -**Figure 1**. Basic outline of the Android APS (Artificial Pancreas System), AAPS. - -Android APS (AAPS) is a hybrid closed loop system, or Artificial Pancreas System (APS). It makes its insulin dosing calculations using established \[OpenAPS\] (https://openaps.org/) algorithms (a set of rules) developed by the #WeAreNotWaiting type 1 diabetes community. - -Since OpenAPS is only compatible with certain older insulin pumps, AAPS (which can be used with a wider range of insulin pumps) was developed in 2016 by Milos Kozak, for a family member with type 1 diabetes. Since those early days, **AAPS** has been continually developed and refined by a team of volunteer computer developers and other enthusiasts who have a connection to the type 1 diabetes world. Today, **AAPS** is used by approximately 10,000 people. It is a highly customisable and versatile system, and because it is open-source, it is also readily compatible with many other open-source diabetes softwares and platforms. The fundamental components of the current **AAPS** system are outlined in Figure 1 above. - -## What are the basic components of AAPS? - -The “brain” of AAPS is an **app** which you build yourself. There are detailed step-by-step instructions for this. You then install the **AAPS app** on a compatible **Android smartphone** (1). A number of users prefer their loop on a separate phone to their main phone. So, you don’t necessarily have to be using an Android phone for everything else in your life, just for running your AAPS loop. - -The **Android smartphone** will also need to have another app installed on it as well as **AAPS**, either a modified Dexcom app called build-your-own dexcom app (**BYODA**) or Xdrip+. This receives glucose data from a sensor (2) by bluetooth, and then sends the data internally on the phone to the **AAPS app**. - -The **AAPS app** uses a decision making process (**algorithm**) from OpenAPS. Beginners start out using the basic **oref0** algorithm, but it is possible to switch to using the newer **oref1** algorithm as you progress with AAPS. Which algorithm you use (oref0 or oref1), depends on which suits your specific situation best. In both cases, the algorithm takes into account multiple factors, and performs rapid calculations every time a new reading comes in from the sensor. The algorithm then sends instructions to the insulin pump (3) on how much insulin to deliver by bluetooth. All the information can be sent by mobile data or wifi to the internet. This data can also be shared with followers if desired, and/or collected for analysis. - -## What are the advantages of the AAPS system? - -The OpenAPS algorithm used by **AAPS** controls blood sugar levels in the absence of user input, according to the users’ defined parameters (important ones being basal rates, insulin sensitivity factors, insulin-to-carb ratios, duration of insulin activity etc.), reacting every 5 minutes to the new sensor data. Some of the reported advantages of using AAPS are extensive fine-tunable options, automations and increased transparency of the system for the patient/caregiver. This can result in better control over your (or your dependent’s) diabetes, which in turn may give improved quality of life and increased peace of mind. - -Practical advantages include: - -- **Hardware flexibility**: **AAPS** works with a wide range of insulin pumps and sensors. So for example, if you develop an allergy to Dexcom sensor patch glue, you could switch to using a Libre sensor instead. That offers flexibility as life changes. You don't have to rebuild, just tick a different box in the AAPS app to change your hardware. - -- **Highly customisable with wide parameters**: here are some examples of the possibilities with AAPS: a) The ability to set a lower glucose target 30 min before eating; you can set the target as low as 72 mg/dL (4.0 mmol/L). b) If you are insulin-resistant resulting in high blood sugars, **AAPS** allows you to set an **automation** rule to activate when BG rises above 8 mmol/L (144 mg/dL), switching to a 120% profile (resulting in an 20% increase in basal and strengthening of other factors too, compared to your normal **profile** setting). The automation will last according to the scheduled time you set. Such an automation could be set to only be active on certain days of the week, at certain times of day, and even at certain locations. c) If your child is on a trampoline with no advance notice, **AAPS** allows insulin suspension for a set time period, directly via the phone. d) After reconnecting a tubed pump which has been disconnected for swimming, AAPS will calculate the basal insulin you have missed while disconnected and deliver it carefully, according to your current BG. Any insulin not required can be overridden by just “cancelling” the missed basal. f) **AAPS** has the ability to set different profiles for different situations and easily switch between them. Features which make the algorithm quicker to bring down elevated BG (like supermicro boluses (“SMB”), unannounced meals, (“**UAM**”) can be set to only work during the daytime, if you are worried about night-time hypos. - - -These are all examples, the full range of features gives huge flexibility for daily life including sport, illness, hormone cycles etc. Ultimately, it is for the user to decide how to use this flexibility, and there is no one-size-fits-all automation for this. - -- **Remote monitoring**: there are multiple possible monitoring channels (Sugarmate, Dexcom Follow, Xdrip+, Android Auto etc.) which are useful for parents/carers and adults in certain scenarios (sleeping/driving) who need customisable alerts. In some apps (Xdrip+) you can also turn alarms off totally, which is great if you have a new sensor “soaking” or settling down that you don’t want to loop with yet. - -- **Remote control**: a significant advantage of **AAPS **over commercial systems is that it is possible for followers, using authenticated text (SMS) commands or via an app (Nightscout or NSClient) to send a wide range of commands back to the ****AAPS** **system. This is used extensively by parents of kids with type 1 diabetes who use AAPS. It is very useful in the playground, for example, if you want to pre-bolus for a snack from your own phone, and your child is busy playing. It is possible to monitor the system (e.g. Fitbit), send basic commands (e.g. Samsung Galaxy watch 4), or even run the entire AAPS system from a high-spec smartwatch (5) (e.g. LEMFO LEM14). In this last scenario, you don’t need to use a phone to run AAPS. As battery life on watches improves, this last option is likely to become increasingly attractive. - -- **No commercial constraints due to open application interfaces**: beyond the use of an open source approach, which allows the source code of **AAPS** to be viewed at any time, the general principle of providing open programming interfaces gives other developers the opportunity to contribute new ideas that allow users to live more easily with their diabetes. This is complementary to commercial systems which adopt the innovations from DIY, where interfaces are only made possible in return for licensing, thus preventing innovations in particular that are not-for-profit. Good examples for such integrations are NightScout, Nightscout Reporter, Xdrip+ M5 stack etc. - -- **Detailed app interface**: It is easy to keep track of things like: insulin levels, cannula age, sensor age, pump battery age, and many actions can be done through the **AAPS** app (priming the pump, disconnecting the pump etc.), instead of on the pump itself. - -- **Accessibility and affordability**: **AAPS** gives people who currently can’t afford to self-fund, or don’t have funding/insurance, access to a world-class hybrid closed looping system which is conceptually years ahead, in terms of development, of the commercial systems being offered by clinics. You currently need to have a Nightscout account to set up **AAPS**. Although the Nightscout account it not necessarily required after setup, many people continue to use Nightscout for collecting their data, and for remote control. So, although **AAPS **itself is free, setting up Nightscout through one of the various platforms may incur a fee (E0 - E12), depending on what level of support you want (see comparison table). **AAPS** works with a wide range of affordable (starting from approx E150) Android phones. In comparison, Loop currently costs around $80 a year for the Apple development licence and CamAPS FX costs around E80/month (as at 2023). - -- ****Support**: No automated insulin delivery system is perfect. Commercial and open-source systems share many common glitches in both communications and temporary hardware failure. There is a community of AAPS users on both Facebook and Discord and Github who designed, developed and are currently using **AAPS** all over the world. There are Facebook support groups and help from clinic/commercial companies for the commercial APS systems - it is worth speaking to the users, or former users of these systems to get feedback on the common glitches, the quality of the education programme and the level of ongoing support provided. - -- **Predictability, transparency and safety**: with no learning algorithm, **AAPS** is logical and in some respect, more predictable, which may make it easier to know when a setting is wrong, and to adjust it accordingly. You can see exactly what the system is doing, why it is doing it, and set its operational limits, which puts the control (and responsibility) in your hands. This can provide the user with confidence, and a sounder sleep. - -- **Access to advanced features through dev modes including full closed loop**: **AAPS **documentation focuses on the mainstream **“master”** branch of **AAPS**, however, research and development is going on all the time. More experienced users may wish to explore the experimental features in the **development** branch such as integration of Dexcom G7, and automatically adjusting insulin delivery according to short-term sensitivity changes (DYNISF), not having to bolus for meals, and generally trying to make life with type 1 diabetes as convenient as possible. - -- **Ability to contribute yourself to further improvements**: type 1 diabetes can be highly frustrating and isolating. Having control over your own diabetes tech, with the possibility to “pay it forward” as soon as you are making progress by helping others on their journey can be really rewarding. You can educate yourself, discover the roadblocks and look for and even contribute to new developments and the documentation. There will be others with the same quest to bounce ideas off and work with. This is the essence of #WeAreNotWaiting. - - -## How does AAPS compare to MDI and open looping? - -Multiple daily injections (MDI, a) usually involve giving an injection of a long-lasting insulin (e.g. Tresiba) once a day, with injections of faster-acting insulin (e.g. Novorapid, Fiasp) at mealtimes, or for corrections. Open pumping (b) involves using a pump to deliver basal at pre-programmed rates of rapid-acting insulin, and then boluses through the pump at mealtimes or for corrections. The basics of a looping system is that the App uses the glucose data to instruct the pump to stop insulin delivery when it predicts you are heading for a low, and to give you extra insulin if your glucose levels are rising and predicted to go too high (c). Although this is oversimplified, (mostly because hybrid closed looping has a lot of additional useful features) the key features of each system are shown in **Figure 2**. - -![image](https://github.com/openaps/AndroidAPSdocs/assets/94044064/4e7d8608-684d-4c69-9c61-88c9539f5d6f) - -**Figure 2**. Overview of (a) MDI, (b) open-loop pumping and (c) hybrid closed loop pumping - -## How does AAPS compare to other looping systems? - -At present there are four major open source closed loop systems available: OpenAPS, **AAPS**, \[Loop\] (https://loopkit.github.io/loopdocs/#what-is-loop) and iAPS, (formerly FreeAPS X). The features of the different systems are shown in the table below: - -| Devicestyp | Name | [Open APS](https://openaps.readthedocs.io/en/latest/) | [AAPS](https://wiki.aaps.app) | [Loop](https://loopkit.github.io/loopdocs/) | [iAPS](https://iaps.readthedocs.io/en/latest/) | -| ---------- | --------------------------------------------------------------------------------------------------------- | ----------------------------------------------------- | ------------------------------------------- | ------------------------------------------- | ---------------------------------------------- | -| PUMP | Older Medtronic | ![available](./images/available.png) | ![available](./images/available.png) | ![available](./images/available.png) | ![available](./images/available.png) | -| PUMP | Older Omnipod (Eros) | ![unavailable](./images/unavailable.png) | ![available](./images/available.png) | ![available](./images/available.png) | ![available](./images/available.png) | -| PUMP | Newer Omnipod (Dash) | ![unavailable](./images/unavailable.png) | ![available](./images/available.png) | ![available](./images/available.png) | ![available](./images/available.png) | -| PUMP | DANA R, DANA RS, DANA I | ![unavailable](./images/unavailable.png) | ![available](./images/available.png) | ![unavailable](./images/unavailable.png) | ![unavailable](./images/unavailable.png) | -| PUMP | Roche Combo, Insight | ![unavailable](./images/unavailable.png) | ![available](./images/available.png) | ![unavailable](./images/unavailable.png) | ![unavailable](./images/unavailable.png) | -| CGM | Dexcom G4, G5, G6 | ![available](./images/available.png) | ![available](./images/available.png) | ![available](./images/available.png) | ![available](./images/available.png) | -| CGM | Libre 1 (requires Miao Miao) | ![available](./images/available.png) | ![available](./images/available.png) | ![available](./images/available.png) | ![available](./images/available.png) | -| CGM | Libre 2 | ![available](./images/available.png) | ![available](./images/available.png) | ![available](./images/available.png) | ![available](./images/available.png) | -| CGM | Libre 3 | | ![unavailable](./images/unavailable.png) | --- | ![unavailable](./images/unavailable.png) | -| CGM | Medtronic Enlite | | --- | ![unavailable](./images/unavailable.png) | --- | -| CGM | [Dexcom G7](https://androidaps.readthedocs.io/en/latest/Hardware/DexcomG7.html) | | ![available](./images/available.png) (beta) | ![available](./images/available.png) | ![available](./images/available.png) | -| CGM | [Eversense](https://androidaps.readthedocs.io/en/latest/Hardware/Eversense.html) | | ![available](./images/available.png) | | ![available](./images/available.png) | -| CGM | [MM640g/MM630g](https://androidaps.readthedocs.io/en/latest/Hardware/MM640g.html) | | ![available](./images/available.png) | | ![available](./images/available.png) | -| CGM | [PocTech](https://androidaps.readthedocs.io/en/latest/Hardware/PocTech.html) | | ![available](./images/available.png) | | ![available](./images/available.png) | -| CGM | [Nightscout als BZ-Quelle](https://androidaps.readthedocs.io/en/latest/Hardware/CgmNightscoutUpload.html) | | ![available](./images/available.png) | | ![available](./images/available.png) | -| Smartphone | Android | ![available](./images/available.png) | ![available](./images/available.png) | ![unavailable](./images/unavailable.png) | ![unavailable](./images/unavailable.png) | -| Smartphone | iPhone | ![available](./images/available.png) | ![unavailable](./images/unavailable.png) | ![available](./images/available.png) | ![available](./images/available.png) | - -[OpenAPS](https://openaps.readthedocs.io/) was the first Open Source Closed Loop System. OpenAPS verwendet einen kleinen Computer wie Raspberry Pi oder Intel Edison. Both AndroidAPS (AAPS) and iAPS use the OpenAPS algorithms, whereas Loop uses a separate algorithm. You can read a comparison of iAPS and **AAPS** here. - -An international peer-reviewed consensus statement containing practical guidance on open source looping was written by and for health-care professionals, and published in a leading medical journal in 2022. It is well worth a read (including for your diabetes clinic) and summarises the main technical differences between the different open-source hybrid closed loop systems: - - Lancet Diabetes Endocrinol, 2022; 10: 58–74 - -[https://www.ncbi.nlm.nih.gov/pmc/articles/PMC8720075/](https://www.ncbi.nlm.nih.gov/pmc/articles/PMC8720075/) - -It is hard to get a “feel” for any system without using it, or talking to others who are using it, so do reach out to others on Facebook/Discord and ask. Most people find that AAPS is incredibly sophisticated in comparison to other hybrid closed loop systems (particularly the commercial systems), with a huge number of potentially customisable settings and features, discussed above. Some people can find this a little overwhelming in the beginning, but there is no rush to investigate all the possibilities at once, you can progress as slowly or as fast as you would like, and there is help available at every step of the way. - -## Does AAPS use artificial intelligence or any learning algorithm? - -Leider nein. **AAPS** does not have any complicated machine learning algorithms, multiple-parameter insulin response models, or differential equations. As such, the system is open and transparent in how it works, and has the ability to be understood not just by experts, but also by clinicians and patients. It also means that if you have a sharply varying schedule (maybe switching from a stressful week at work to a relaxing holiday) and are likely to need a significantly different amount of insulin, you can immediately switch **AAPS** to run a weaker/stronger profile. A ‘learning system’ will do this adjustment for you automatically, but is likely to take longer to adjust the insulin delivery. - -## Which system is right for me or my dependent? - -Practically, your choice of system is often restricted by which pump you already have, or can obtain from your medical provider, and your choice of phone (Apple or Android). If you don’t yet have a pump you have the biggest choice of systems. Technology is continually evolving, pumps are being discontinued and new pumps and sensors are being released. Most open-source systems work with the main sensors (Libre and Dexcom) or are quickly adapted to work with new sensors a year or so after they are released (with a bit of time delay for safety and stability testing). - -Most **AAPS **users report more time in range, HbA1c reductions, as well as quality of life improvements from having a system that can auto-adjust basal rates overnight during sleep, and this is true for most hybrid closed loop APS. Some people have a preference for a very simple system which is not very customisable (which means you may prefer a commercial system), and others find this lack of control very frustrating (you may prefer an open-source system). If you (or your dependent) are newly diagnosed, a common route is to get the hang of MDI plus sensor first, then progress to a pump which has the potential for looping, then to **AAPS**, but some people (especially small kids) may go straight to a pump. - -It is important to note that the **AAPS** user needs to be proactive to troubleshoot and fix problems themselves, with help from the community. This is a very different mindset to that when using a commercial system. With **AAPS** a user has more control, but also the responsibility, and needs to be comfortable with that. - -## Is it safe to use open-source systems like AAPS? - -A more accurate question is probably “is it safe compared to my current type 1 diabetes insulin delivery system?” since no method of insulin delivery is without risk. There are many checks and balances in place with **AAPS**. A recent paper looked at the use of**** AAPS ****in a computer simulated set-up, [https://www.liebertpub.com/doi/epub/10.1089/dia.2019.0375](https://www.liebertpub.com/doi/epub/10.1089/dia.2019.0375) which was an effective way to unobjectively trial how safe and effective the system is. More generally, it is estimated that over 10,000 individuals worldwide are using open-source automated-insulin delivery systems, and uptake continues to increase globally. - -Any device that uses radio communications could be hacked, and this is true for a non-looping insulin pump as well. Currently, we are not aware of anyone attempting to harm individuals by hacking their diabetes-related medical equipment. However, there are multiple ways to protect against such risks: - -1. In the pump settings, limit both the max bolus allowed and max temporary basal settings to amounts that you believe are safest. These are hard limits that we do not believe any malicious hacker could circumvent. - -2. Set your CGM alarms enabled for both highs and lows. - -3. Monitor your insulin delivery online. Nightscout users can set additional alarms to alert for a wide variety of conditions, including conditions that are much more likely to occur than a malicious attack. In addition to highs and lows, Nightscout can display diagnostic data useful for verifying that the pump is operating as desired, including current IOB, pump temporary basal history, pump bolus history. It can also be configured to proactively alert users to undesirable conditions, such as predicted highs and lows, low insulin reservoir, and low pump battery. - - -If a malicious attack was made on your insulin pump, these strategies would significantly mitigate the risk. Every potential **AAPS** user needs to weigh the risks associated with using **AAPS**, versus the risks of using a different system. - -## How can I approach discussing AAPS with my clinical team? - -Depending on the country - link to doctors section of docs - - Lancet Diabetes Endocrinol, 2022; 10: 58–74 - -[https://www.ncbi.nlm.nih.gov/pmc/articles/PMC8720075/](https://www.ncbi.nlm.nih.gov/pmc/articles/PMC8720075/) - -## Q: Why can’t I just download AAPS and use it straight away? - -The **AAPS** app is not provided in Google Play - you have to build it from source code by yourself for legal reasons. **AAPS** is unlicensed, meaning that it does not have approval by any regulatory body authority in any country. **AAPS**is deemed to be carrying out a medical experiment on yourself, and is carried out at the user’s own risk. - -Setting up the system requires patience, determination and the gradual development of technical knowledge. All the information and support can be found in these documents, elsewhere online, or from others who have already done it. It is estimated that over 2000 people have successfully built and are currently using **AAPS** worldwide. - -The developers of **AAPS**t ake safety incredibly seriously, and want others to have a good experience of using **AAPS**. That is why it is essential that every user (or carer, if the user is a child): - -- builds the AAPS system themself and works through the **objectives** so that they have reasonably good personalised settings and understand the basics of how AAPS ****works by the time they “close the loop”; - -- backs up their system by exporting and saving important files (like keystore and settings .json file) somewhere safe, so you can setup again quickly if needed; - -- updates to newer master versions as and when they become available; and - -- maintains and monitors the system to ensure it is working properly. - - -## Q: What is the connectivity of the AAPS system? - -**Figure 3 (below)** shows one example of the **AAPS** system for a user who do not require any followers interacting with the system: - -![potential AAPS connectivity setup with no followers](./images/intro03.png) - -**Figure 4 (below)** shows the full potential of the **AAPS** system for a user who has followers and requires a monitor and send adjust the system remotely (like a child with T1D): - -![potential AAPS connectivity setup with followers](./images/intro04.png) - -## Q: How does AAPS get continually developed and improved? - -Most **AAPS** users use the fully tested **master** version of AAPS, which has been tested for bugs and problems, before being released to the community. Behind the scenes, the developers try out new improvements, and test these out in “developer” (**dev**) versions of **AAPS** with a user community who are happy to do bug updates at short notice. If the improvements work well, they are then released as a new “master” version of **AAPS**. Any new master release is announced on the Facebook group, so that the mainstream **AAPS** users can read about and update to the new master version. - -Some experienced and confident **AAPS ** users conduct experiments with emerging technologies and with dev versions of the **AAPS** app, which can be interesting for the less adventurous users to read about, without having to do it themselves! People tend to share these experiments on the Facebook group too. - -You can read more about some of these experiments and discussion on emerging tech here: - -[https://www.diabettech.com/](https://www.diabettech.com/) - -[https://bionicwookie.com/](https://bionicwookie.com/) - -## Q: Who can benefit? - -| User Type | -| ------------------------------------------- | -| ✔️ type 1 diabetic | -| ✔️ caregiver or parent of a type 1 diabetic | -| ✔️ blind users type 1 diabetic | -| ✔️ *clincians and healthcare professionals | - -The above table assumes that the user has access to both continuous gluocse monitor and insulin pump. - -*All data from **AAPS** can be made available to healthcare professionals via data sharing platforms, including NightScout that provides logging and real time monitoring of CGM data, insulin delivery, carbohydrate entries, predictions and settings. Nightscout records include daily and weekly reports which can aid healthcare professionals' discussions with type 1 patients with more accurate data on glycemic control and any behavioural considerations. - -## Q: What benefits can I get? - -With investment of your time, **AAPS** can potentially lead to: - -- alleviating the stress and burden of managing type 1 diabetes; - -- reducing the multitude of mundane decisions that arise from type 1 diabetes; - -- the provision of personalised and dynamic insulin dosing based on real-time data which can cut down the need for hypo treatments and reduce hyperglycemia episodes; - -- an increased knowledge of insulin management and confidence to better fine tune your settings; - -- the ability to create automatic settings (**automations**) that are tailored to fit in with your lifestyle; - -- improved sleep quality and overall reduction in the frequency of nighttime interventions; - -- remote monitoring and administration of insulin delivery for caregivers of type 1 diabetics; and - -- streamlining of all your portable diabetic equipment (continuous glucose monitor and insulin portable devices) by replacing them with an android phone controlled by **AAPS**. - - -Ultimately,**AAPS** can empower individuals to better manage their diabetes resulting in stable blood sugars and improved long term health outcomes. - ---- - -## AAPS First Steps - -Welcome. This is an introduction to aid beginners getting started with **AAPS** (or commonly referred to as "looping"). - -## Safety - -“_With great powers comes great responsibilities…_” - -**AAPS** is designed with an extensive set of safety features with limits imposed and gradually removed with completion of the **objectives **(predominately made up of multiple choice questions). An **AAPS** feature will be unlocked as the Objectives are successfully completed. This process will gradually allow the user to migrate from Open Loop to Closed Loop. - -This has been done to achieve the best possible experience with **AAPS** in order to prevent common mistakes that new users tend to make when starting to loop. The safety parameters have been built upon typical errors and general trends **AAPS** developers have observed with new users. Mistakes can happen because the beginner is inexperienced and too eager to get started with AAPS or has overlooked the required materials. Do not worry, we have all been there! - -## Key Principles - -The key principles and concepts of looping must be understood by the user before using **AAPS**. This is achieved by investing your personal time into reading the **AAPS** documentation, and completing the Objectives which is aimed to provide you with a solid platform for safe and effective use of **AAPS**. The volume of **AAPS** documentation may seem overwhelming at first but be patient and trust the process - with the proper approach, you'll get there! The overall process will depend upon the beginner’s progress and completion of objectives can typically take between 6 to 9 weeks . - -## Plan for hiccups - -At the preliminary stages of **AAPS**, you should expect to experience some hiccups whilst trying to fine tune your settings. **AAPS**’ glitches cannot be flushed out until the system is used in everyday life. Please plan accordingly and allow a sensible amount of time to troubleshoot and resolve such issues. - -## Flexibility/Adaptability - -Success with **AAPS** requires a proactive approach, a willingness to reflect on the BG data and flexibility to make the necessary adjustments to **AAPS** in order to improve your outcomes. Just as it is nearly impossible to learn to play a sport by reading about the rules alone, the same can be said of **AAPS**. - -## Technology compatibility - -There are limitations with **AAPS** as it is accessible for only certain types of insulin pumps or CGMs, and some technology may not be available for use in various countries. In order to avoid any disappointment or frustrations, please read please read Component Set Up (Section INSERT). - -## App Build Time - -The time to build the **AAPS**(under Section INSERT) depends on your level of expertise and technical ability. Typically for inexperienced users, it can take up to half a day or a full day (with help from the community) in order to build the **AAPS**. The process will significantly speed up as you become more experienced at building the **AAPS**. To aid the build process there are sections dedicated for: -- list of questions and answers for frequent errors that are likely to occur under FAQs (Section K); -- “How to install AAPS? (Section INSERT) which includes Troubleshooting subsection. - -## Keystore & configurations settings a export file - -A “keystore” is a password encrypted file unique to your own copy of **AAPS**. Your android phone uses it to ensure that nobody else can upgrade your own copy without the keystore. In short, as part of the **AAPS** build, you should: - -- save the your keystore file (.jks file used to sign your app) in a safe place; -- keep a note of your password for your keystore file. - -By doing the above, this will ensure that you can use that exact same keystore file each time an updated version of **AAPS** is created. On average, there will be 2-3 AAPS updates required each year. - -In addition, **AAPS** provides the ability to export all your configuration settings. This ensures that you can safely recover your system while changing phones, upgrading/reinstalling the application with minimum disruption. - -## Troubleshootng - -Please feel free to reach out to the AAPS community if there is anything you feel unsure about - there is no such thing as a silly question! All users with various levels of experience are encouraged to ask questions as necessary. Response times to questions are usually quick, typically only a few hours due to the volume of **AAPS** users. - -a) check the documentation; b) ask AAPS facebook group (https://www.facebook.com/groups/AndroidAPSUsers); and c) ask our discord channel. - -## Section overview - -AAPS documentation is made up of the following Sections: - -[INSERT ONCE SECTIONS /SUB SECTIONS AGREED] ---- diff --git a/docs/CROWDIN/de/maintaining.md b/docs/CROWDIN/de/maintaining.md deleted file mode 100644 index 98164a09e49b..000000000000 --- a/docs/CROWDIN/de/maintaining.md +++ /dev/null @@ -1,28 +0,0 @@ -# Dummy - -## This is a dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - - -## This is another dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - - -## This is another another dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - diff --git a/docs/CROWDIN/de/optimizing.md b/docs/CROWDIN/de/optimizing.md deleted file mode 100644 index 98164a09e49b..000000000000 --- a/docs/CROWDIN/de/optimizing.md +++ /dev/null @@ -1,28 +0,0 @@ -# Dummy - -## This is a dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - - -## This is another dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - - -## This is another another dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - diff --git a/docs/CROWDIN/de/prepairing.md b/docs/CROWDIN/de/prepairing.md deleted file mode 100644 index 1e422f275769..000000000000 --- a/docs/CROWDIN/de/prepairing.md +++ /dev/null @@ -1,145 +0,0 @@ -# Prepairing - -## Guide to the Android APS doc - -### First Steps -Welcome. This is an introduction to aid beginners to the concept of Do-It-Yourself-APS (Android-Artificial-Pancreas-Systems “AAPS”) is commonly referred to as ‘looping’.. - -#### Safetys -“With great powers come great responsibilities…” - -AAPS is designed with an extensive set of safety features with limits imposed and gradually removed with completion of the [Objectives](https://androidaps.readthedocs.io/en/latest/Usage/Objectives.html) (predominately made up of multiple choice questions). An AAPS feature will be unlocked as the Objectives are successfully completed. This process will gradually allow the user to migrate from Open Loop to Closed Loop. - -This has been done to achieve the best possible experience with AAPS by preventing common mistakes new users tend to make when starting to loop. The safety parameters have been built upon typical errors and general trends AAPS developers have observed with new users. Mistakes can happen because the beginner is inexperienced and too eager to get started with AAPS or has overlooked the required materials. Do not worry, we have all been there! - -#### Key Principles - -The key principles and concepts of looping must be understood by the user before using AAPS. This is achieved by investing your personal time into reading the AAPS documentation, and completing the [Objectives](https://androidaps.readthedocs.io/en/latest/Usage/Objectives.html) which is aimed to provide you with a solid platform for safe and effective use of AAPS. The volume of AAPS documentation may seem overwhelming at first but be patient and trust the process - with the proper approach, you'll get there! The overall process will depend upon the beginner’s progress and completion of objectives which typically take between 6 to 9 weeks . - -#### Plan for hiccups - -At the preliminary stages of AAPS, you should expect to experience some hiccups whilst trying to fine tune your settings. AAPS’ glitches cannot be flushed out until the system is used in everyday life. Please plan accordingly and allow a sensible amount of time to troubleshoot and resolve such issues. - -#### Flexibility/Adaptability - -Success with AAPS requires a proactive approach, a willingness to reflect on the BG data and flexibility to make the necessary adjustments to AAPS in order to improve your outcomes. Just as it is nearly impossible to learn to play a sport by reading about the rules alone, the same can be said of AAPS. - -#### Technology compatibility -There are limitations with AAPS as it is accessible for only certain types of insulin pumps or CGMs, and some technology may not be available for use in various countries. In order to avoid any disappointment or frustrations, please read [Component Set Up (Section E).](https://androidaps.readthedocs.io/en/latest/Configuration/BG-Source.html) - -#### App Build time -The time to build the AAPS (under Section D) depends on your level of expertise and technical ability. Typically for inexperienced users, it can take up to half a day or a full day (with help from the community) in order to build the AAPS. The process will significantly speed up as you become more experienced at building the AAPS.  - -To aid the build process there are sections dedicated for: - -- list of questions and answers for frequent errors that are likely to occur under [FAQs (Section](https://androidaps.readthedocs.io/en/latest/Getting-Started/FAQ.html) K); - -- “[How to install AAPS](https://androidaps.readthedocs.io/en/latest/Installing-AndroidAPS/Building-APK.html)? (Section D) which includes [Troubleshooting](https://androidaps.readthedocs.io/en/latest/Usage/troubleshooting.html) subsection. - - -#### Keystore & configuration settings export  file - -A “keystore” is a password encrypted file unique to your own copy of AAPS. Your android phone uses it to ensure that nobody else can upgrade your own copy without the keystore.In short, as part of the AAPS build, you should: - -1. save the your keystore file (.jks file used to sign your app) in a safe place; - -2. keep a note of your password for your keystore file. - - -By doing the above, this will ensure that you can use that exact same keystore file each time an updated version of AAPS is created. On average, there will be 2-3 updates to the AAPS required each year. In addition, AAPS provides the ability to [export all your configuration settings](https://androidaps.readthedocs.io/en/latest/Usage/ExportImportSettings.html). This ensures that you can safely recover your system while changing phones, upgrading/reinstalling the application with minimum disruption.  - -#### Problembehandlung - -Please feel free to reach out to the AAPS community if there is anything you feel unsure about - there is no such thing as a silly question!  All users with various levels of experience are encouraged to ask questions as necessary. Response times to questions are usually quick, typically only a few hours due to the volume of AAPS users.  - -##### [check the documentation](https://androidaps.readthedocs.io/en/latest/index.html) - -##### [ask our facebook group](https://www.facebook.com/groups/AndroidAPSUsers/) - -##### [ask our discord channel](https://discord.com/channels/629952586895851530/629954570394533889) - -#### Section overview - -AAPS documentation is made up of the following Sections: - -##### [Getting started](https://androidaps.readthedocs.io/en/latest/Getting-Started/Safety-first.html) - -This is a must read to understand the general concept of what an artificial pancreas system is designed to do. - -##### [What do I need?](https://androidaps.readthedocs.io/en/latest/Module/module.html) - -This explains AAPS’ compatibility with CGMs (Continuous Glucose Monitors) and insulin pumps. It also provides a guide on the correct assembly of an AAPS system to ensure that it functions correctly in everyday life. - -##### How to install AAPS - -This section is the manual for building the AAPS. Strict adherence to the step-by-step instructions are required in order to successfully build the AAPS. Lasse Dir Zeit. - -##### [Component Setup](https://androidaps.readthedocs.io/en/latest/Configuration/BG-Source.html) - -This explains how to properly integrate each of the various different separate component parts into AAPS, as well as how to set them up to work as seamlessly as possible together. All components are listed under the separate sections: CGM/FGM, xDrip Settings, Pumps, Phones, Nightscout setup, and Smartwatches. The sensor (BG) values and control of the insulin pump are particularly important information to understand. - -##### Configuration - -This explains how to set and configure your ‘Profile’, ‘Insulin’, ‘BG Source’, ‘Pump’, ‘Sensitivity Detection’, ‘APS’, ‘Loop’, ‘Treatments’. - -##### AAPS Usage - -This section provides a breakdown of the features provided by AAPS. - -##### [General Hints](https://androidaps.readthedocs.io/en/latest/Usage/Timezone-traveling.html) - -Useful tricks on how to tackle looping issues such as time zones, and daylight saving (i.e. Spring Forward/ - Fall Back). - -##### [AAPS](https://androidaps.readthedocs.io/en/latest/Getting-Started/Screenshots.html) for Children - -This is designed for parents or caregivers who want to build an AAPS for their child. It also explains the extra features necessary in order to support and safely control your child’s AAPS remotely.

The concepts in this section should be fully understood in order to competently use this feature. - -##### Problembehandlung - -This section contains links to help solve issues when building or using AAPS. - -##### FAQ - -This section addresses specific questions which tend to come up when building or using AAPS. - -##### [Glossar](https://androidaps.readthedocs.io/en/latest/Getting-Started/Glossary.html) - -This contains a list of the acronyms (or short-term names) or defined terms developed specifically for AAP (for instance, the terms ‘ISF’ or ‘TT’ have special meanings in AAPS). - -##### [Where to go for help](https://androidaps.readthedocs.io/en/latest/Where-To-Go-For-Help/Background-reading.html)? - -This section is aimed to provide new users with links on resources in order to get help including accessing community support made up of both new and experienced users who can clarify questions, and resolve the usual pitfalls that come with AAPS. - -##### For Clinicians - -This is a section for the clinicians who have expressed interest in open source artificial pancreas technology such as AAPS, or for patients who want to share such information with their clinicians. | - -## what are we going to build? - -### An Android Phone Application - -At the core, AAPS is an android application running from a phone. You are going to build it from scratch by installing tools to download the sourcecode and build the actual application. - -### A reporting server NightScout (or Tidepool) - -In order to fully use AAPS properly you will want to setup a nightscout server. It is used to collect data from AAPS over time and possibly communicate to the application. It is required for parents who want to oversee their children AAPS sessions. It is also key to share data between clinicians and patients to perform analysis over time. - -## How long will it take? - -## Who might AAPS not be suitable for? - -## Where can I get help? - -## Requirements - -### medical - -### technical - -### personal - -### CGMs - -### Insulin Pump - -### Reporting (NS, Tidepool) \ No newline at end of file diff --git a/docs/CROWDIN/el/Configuration/Dexcom.md b/docs/CROWDIN/el/Configuration/Dexcom.md deleted file mode 100644 index cb267e23c069..000000000000 --- a/docs/CROWDIN/el/Configuration/Dexcom.md +++ /dev/null @@ -1,32 +0,0 @@ -# Dexcom G6 - -## Basics first - -* Follow [general CGM hygiene recommendations](../Configuration/BG-Source#cgm-hygiene) -* [Special recommendations for Dexcom G6 and DIY systems](../Configuration/BG-Source#dexcom-g6-diy-systems) *For G6 transmitters manufactured after fall/end of 2018 please make sure to use one of the [latest nightly built xDrip+ versions](https://github.com/NightscoutFoundation/xDrip/releases). Those transmitters have a new firmware and latest stable version of xDrip+ (2019/01/10) cannot deal with it. - -## Setting sensor - -When setting sensor, it is recommended not to press the inserter too firmly in order to avoid bleeding. The sensor thread should not come into contact with blood. - -After setting the sensor, the transmitter can be clicked into the sensor holder. Caution! First click in the square side and then press down the round side. - -## Troubleshooting - -### Connection problems - -Bluetooth connection may be disturbed by other nearby Bluetooth devices such as blood glucose meters, headsets, tablets or kitchen devices such as microwave ovens or ceramic hobs. In this case xdrip does not display any BG values. When bluetooth connection is reestablished the data is backfilled. - -### Sensor Errors - -If recurring sensor errors occur try selecting a different body site to set your sensor. The sensor thread should not come into contact with blood. - -Often a "Sensor Error" can be corrected by immediate drinking and massage around the sensor! - -### Jumpy values - -You might try to change settings for noise blocking in xdrip (Settings - Inter-App Settings - Noise Blocking) i.e. "Block Very High noise and worse". See also [Smoothing BG data](../Usage/Smoothing-Blood-Glucose-Data-in-xDrip.md). - -### New transmitter with running sensor - -If you happen to change transmitter during a running sensor session you might try to remove the transmitter without damaging the sensor mount. A video can be found at . \ No newline at end of file diff --git a/docs/CROWDIN/el/Configuration/EOFLOW.md b/docs/CROWDIN/el/Configuration/EOFLOW.md deleted file mode 100644 index c5152fdfc91e..000000000000 --- a/docs/CROWDIN/el/Configuration/EOFLOW.md +++ /dev/null @@ -1,155 +0,0 @@ -# EOPatch2 Instruction Manual - -The patch requires the use of rapid-acting U-100 type insulin, such as NovoRapid or Humalog. Use a rapid-acting insulin that is suitable for you according to your doctor’s prescription and inject the prescribed dosage. - -The smallest injectable dose of insulin when using the patch is 0.05 U. The Profile BAS should therefore be set at a minimum value of 0.05 U/hr or more and an interval of 0.05 U/hr, as otherwise there may be an error between the estimated total infusion amount in the Profile and the actual infusion amount in the patch. Likewise, the bolus must also be set and infused with a minimum infusion volume of 0.05 U. - -## Pump Setup -1. On the AndroidAPS home screen, click the hamburger menu in the upper left corner and go to Config Builder. -1. Select 'EOPatch2' in the Pump section. -1. Press the Back key to return to the home screen. - -![Bild1](../../images/EOPatch/Bild1.png) ![Bild2](../../images/EOPatch/Bild2.png) - -## Ρυθμίσεις -Select EOPATCH2 at the top of the home screen to go to the EOPATCH2 tab. - -Select the EOPatch2 Preferences menu by clicking the three dots in the upper right corner. - -The EOPatch2 Preferences menu offers a menu to set 3 types of notifications. - -### Low reservoir Alerts -A warning appears when the amount of insulin remaining in the reservoir reaches the set value or less while using the patch. It can be set from 10 to 50U in 5U increments. - -### Patch expiration Reminder -This is a reminder to notify you of the time remaining before the current patch expires. It can be set from 1 to 24 hours in 1 hour increments. The initial setting value is 4 hours. - -### Patch buzzer Reminder -This is a reminder function for injections other than basal injection. If you are using an (extended) bolus injection or a temporary basal injection, the patch will make a buzzer sound when the injection starts and when the injection is complete. The initial setting value is Off. - -![Bild3](../../images/EOPatch/Bild3.png) - -## Connecting the Patch - -### Move to patch connection screen - -Select EOPATCH2 at the top of the home screen and click the ACTIVATE PATCH button at the bottom left. - -![Bild4](../../images/EOPatch/Bild4.png) - -### Connecting the patch -Insert the syringe needle into the insulin inlet on the patch and then slowly push the piston to inject the insulin. When insulin is filled with more than 80U, the patch makes a booting sound (1 buzzer) and boots. After confirming the buzzer sound, click the START PAIRING button on the screen. - -[Warning] - -- Do not turn the needle action lever until instructed. It can cause serious problems during injection or safety checks otherwise. -- The amount of insulin that can be injected into the patch is 80~200U. If you inject less than 80U into the patch initially, the patch will not work. -- Take the insulin to be put into the patch from the refrigerator and leave it at room temperature for 15 to 30 minutes beforehand. The temperature of the insulin to be injected must be at least 10°C. - -![Bild5](../../images/EOPatch/Bild5.png) - -### patch pairing -The Patch pairing screen will be displayed, and pairing will be attempted automatically. If communication is successful, the Bluetooth pairing request notification appears. Click OK and when the Bluetooth pairing request notification appears a second time with the authentication code, select OK again. - -[Warning] - -- For pairing, the patch and the smartphone must be located within 30 cm of each other. -- After the patch booting is completed, the patch will beep every 3 minutes until the pairing is complete. -- After booting the patch, the patch application must be completed via the app within 60 minutes. If the application cannot be completed within 60 minutes, the patch should be discarded. - -![Bild6](../../images/EOPatch/Bild6.png) ![Bild7](../../images/EOPatch/Bild7.png) ![Bild8](../../images/EOPatch/Bild8.png) - - -### patch preparation -After removing the adhesive tape of the patch, check if the needle is sticking out. If there are no problems with the patch, click NEXT. - -![Bild9](../../images/EOPatch/Bild9.png) - -### Patch attachment -Insulin should be injected in a spot with subcutaneous fat but few nerves or blood vessels, so it is recommended to use the abdomen, arm, or thigh for the patch attachment site. Choose a patch attachment site and apply the patch after disinfecting the location. - -[Warning] - -- Make sure to straighten the side of the patch tape attached to the body evenly, so that the patch adheres completely to the skin. -- If the patch does not stick completely, air may enter between the patch and the skin, which can weaken the adhesive strength and waterproof effect of the patch. - -![Bild10](../../images/EOPatch/Bild10.png) - -### Safety Check -When patching is complete, touch Start Safety Check. When the safety check is completed, the patch will beep once. - -[Warning] - -- For safe use, do not turn the needle action lever until the safety check has been completed. - -![Bild11](../../images/EOPatch/Bild11.png) ![Bild12](../../images/EOPatch/Bild12.png) - - -### Inserting the needle -The needle is inserted by holding around the patch and turning the needle action lever more than 100° in the upward direction of the lever. There is a buzzer sound when the needle is inserted correctly. Turn the needle action lever further clockwise to release the lever. Click NEXT. - -[Caution] - -- If you go to the next step without the buzzer sounding, a needle insertion error warning will appear. - -## Discarding the patch -Patches must be replaced in the case of low insulin levels, usage expiration, and defects. The recommended usage period for each patch is 84 hours after booting the patch. - -### Discarding the patch -Select EOPATCH2 at the top of the home screen and click the DISCARD/CHANGE PATCH button at the bottom. On the next screen, click the DISCARD PATCH button. A dialog box appears to confirm once more and if you select the DISCARD PATCH button, the disposal is completed. - -![Bild13](../../images/EOPatch/Bild13.png) ![Bild14](../../images/EOPatch/Bild14.png) ![Bild15](../../images/EOPatch/Bild15.png) ![Bild16](../../images/EOPatch/Bild16.png) - -## Suspending and Resuming Insulin Delivery -Suspending insulin delivery also cancels both extended bolus and temporary basal. When resuming insulin delivery, the canceled extended bolus and temporary basal will not be resumed. And when insulin delivery is suspended, the patch will give a sound every 15 minutes. - -### Suspending insulin delivery -Select EOPATCH2 at the top of the home screen and click the SUSPEND button at the bottom right. When you select CONFIRM in the confirmation box, a time selection box appears. If you select the CONFIRM button after selecting the time, the insulin delivery will be suspended for the set amount of time. - -![Bild17](../../images/EOPatch/Bild17.png) ![Bild18](../../images/EOPatch/Bild18.png) ![Bild19](../../images/EOPatch/Bild19.png) - - -### Resuming insulin delivery -Select EOPATCH2 at the top of the home screen and click the RESUME button at the bottom right. Insulin delivery will resume by selecting CONFIRM in the confirmation dialog box. - -![Bild20](../../images/EOPatch/Bild20.png) ![Bild21](../../images/EOPatch/Bild21.png) - -## Alarms/Warnings - -### Alarm - -Alarms are issued for emergency situations of the highest priority and require immediate action. The alarm signal does not disappear or time out until it is acknowledged. An alarm occurs when there is a problem with the patch being used, so there may be cases where the patch in use needs to be discarded and replaced with a new patch. The warning is displayed as a dialog box and switching to another screen is not possible until processing is completed. - -![Bild22](../../images/EOPatch/Bild22.png) ![Bild23](../../images/EOPatch/Bild23.png) - -The different types of alarms are explained below. - -| Alarms | Explanation | -| -------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| Empty reservoir | Occurs when the patch’s reservoir runs out of insulin. | -| Patch expired | Occurs when the patch usage time has expired, and no further insulin injections are possible. | -| Occlusion | Occurs when it appears that the patch's insulin inlet is clogged. | -| Power on self-test failure | Occurs when the patch finds an unexpected error during the post-boot self-test process. | -| Inappropriate temperature | Occurs when the patch is outside the normal operating temperature range during patch application and use. To deal with this alarm, move the patch to an appropriate operating temperature (4.4 to 37°C) condition. | -| Needle insertion Error | Occurs when needle insertion is not normal during the patch application process. Check that the needle insertion edge of the patch and the needle activation button are in a straight line. | -| Patch battery Error | Occurs just before the patch’s internal battery runs out and powers off. | -| Patch activation Error | Occurs when the app fails to complete the patching process within 60 minutes after the patch is booted. | -| Patch Error | Occurs when the patch encounters an unexpected error while applying and using the patch. | - -### Warning - -A warning occurs in a medium or low-priority situation. When a warning occurs, it is displayed as a notification in the Overview screen. - -![Bild24](../../images/EOPatch/Bild24.png) - -The different types of warnings are explained below. - -| Warnings | Explanation | -| ---------------------------- | ------------------------------------------------------------------------------------------------------------------------------------- | -| End of insulin suspend | Occurs when the time set by the user has elapsed after the insulin infusion suspension has been completed. | -| Low reservoir | Occurs when the remaining amount of insulin in the patch is below the set amount. | -| Patch operating life expired | Occurs when the patch usage period is over. | -| Patch will expire soon | Occurs 1 hour before the patch must be discarded. | -| Incomplete Patch activation | Occurs when more than 3 minutes have elapsed due to an interruption during patch application in the stage after pairing is completed. | -| Patch battery low | Occurs when the patch's battery is low. | - diff --git a/docs/CROWDIN/el/Configuration/Hardware/index.md b/docs/CROWDIN/el/Configuration/Hardware/index.md deleted file mode 100644 index 9215e2770d45..000000000000 --- a/docs/CROWDIN/el/Configuration/Hardware/index.md +++ /dev/null @@ -1,27 +0,0 @@ -# Hardware-Configuration - -## Configuration - -## BG Source - -- [BG Source](../BG-Source.md) -- [xDrip+ Settings](../xDrip.md) -- [Dexcom G6 hints](../Dexcom.md) -- [Smoothing blood glucose data](../../Usage/Smoothing-Blood-Glucose-Data-in-xDrip.md) - -## Pumps - -- [Dana-R pump](../DanaR-Insulin-Pump.md) -- [Dana-RS pump](../DanaRS-Insulin-Pump.md) -- [Accu-Chek Combo pump](../Accu-Chek-Combo-Pump.md) -- [Accu-Chek Insight pump](../Accu-Chek-Insight-Pump.md) -- [Medtronic pump](../MedtronicPump.md) - -## Phones - -- [Jelly Pro Settings](../../Usage/jelly.md) -- [Huawei Settings](../../Usage/huawei.md) - -## Smartwatch - -- [Watchfaces](../Watchfaces.md) diff --git a/docs/CROWDIN/el/Getting-Started/ClosedLoop.md b/docs/CROWDIN/el/Getting-Started/ClosedLoop.md deleted file mode 100644 index 203d22623f24..000000000000 --- a/docs/CROWDIN/el/Getting-Started/ClosedLoop.md +++ /dev/null @@ -1,55 +0,0 @@ -# What is a Closed Loop System? - -![AAPS is like an autopilot](../images/autopilot.png) - -An artificial pancreas closed loop system combines different components in order to make diabetes management easier for you. In her great book [Automated Insulin Delivery](https://www.artificialpancreasbook.com/) Dana M. Lewis, one of the founders of the open source closed loop movement, calls it an ["autopilot for your diabetes"](https://www.artificialpancreasbook.com/3.-getting-started-with-your-aps). But what does that mean? - -**Autopilot in an aircraft** - -The autopilot does not do the complete job and does not give the possibility to the pilot to sleep throughout the entire flight. It facilitates the work of the pilots. It relieves them of the burden of permanently monitoring the aircraft and the flight attitude. This allows the pilot to concentrate on monitoring the airspace and controlling the autopilot's functions. - -The autopilot receives signals from various sensors, a computer evaluates them together with the pilot's specifications and then makes the necessary adjustments. The pilot no longer has to worry about the constant adjustments. - -**Closed Loop System** - -The same applies to an artificial pancreas closed loop system. It does not do the whole job, you still have to take care of your diabetes. A closed loop system combines the sensor data from a CGM/FGM with your diabetes management specifications such as basal rate, insulin sensitivity factor and carb ratio. From this it calculates treatment suggestions and implements these permanent small adjustments in order to keep your diabetes within the target range and to relieve you. This leaves more time for your life "next to" diabetes. - -Just as you don't want to get on a plane where only the autopilot flies without human supervision, a closed loop system helps you with your diabetes management, but always needs your support! **Even with a closed loop you can't just forget your diabetes!** - -Just as the autopilot depends on the sensor values as well as the pilot's specifications, a closed loop system needs appropriate input such as basal rates, ISF and carb ratio to support you successfully. - -## Open Source Artificial Pancreas Closed Loop Systems - -At present there are three major open source closed loop systems available: - -### AndroidAPS (AAPS) - -AAPS is described in detail in [this documentation](./WhatisAndroidAPS.html). It uses an Android Smartphone for calculation and control of your insulin pump. It is in strong collaboration with OpenAPS (i.e. they share algorithms). - -Compatible [pumps](../Hardware/pumps.md) are: - -- [DanaR](../Configuration/DanaR-Insulin-Pump.md) / [DanaRS & Dana-i](../Configuration/DanaRS-Insulin-Pump.html) -- [Accu-Chek Combo](../Configuration/Accu-Chek-Combo-Pump.md) -- [Accu-Chek Insight](../Configuration/Accu-Chek-Insight-Pump.md) -- [Diaconn G8](../Configuration/DiaconnG8.md) -- [Omnipod DASH](../Configuration/OmnipodDASH.md) -- [Αντλία Omnipod Eros](../Configuration/OmnipodEros.md) -- some old [Medtronic pumps](../Configuration/MedtronicPump.md) - -### OpenAPS - -[OpenAPS](https://openaps.readthedocs.io) was the first Open Source Closed Loop System. It uses a small computer such as Raspberry Pi or Intel Edison. - -Compatible pumps are: - -- some old Medtronic pumps - -### Loop for iOS - -[Loop for iOS](https://loopkit.github.io/loopdocs/) is the Open Source Closed Loop System to be used with Apple iPhones. - -Compatible pumps are: - -- Omnipod DASH -- Αντλία Omnipod Eros -- some old Medtronic pumps diff --git a/docs/CROWDIN/el/Getting-Started/GlossaryTest.md b/docs/CROWDIN/el/Getting-Started/GlossaryTest.md deleted file mode 100644 index 30102aa9b541..000000000000 --- a/docs/CROWDIN/el/Getting-Started/GlossaryTest.md +++ /dev/null @@ -1,391 +0,0 @@ -# Γλωσσάριο - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ΌροςΠεριγραφήδείτε επίσηςπερισσότερες λεπτομέρειες στα
AAPSAndroidAPS - τεχνητό σύστημα παγκρέατος  
AMAπροηγμένο γεύμα βοηθός - προηγμένος αλγόριθμος για τη διαχείριση υδατανθρακώνMA / SMBWiki - AMA
Android autoπροβάλλετε τις ειδοποιήσεις AAPS στις συμβατές πληροφορίες για το αυτοκίνητο και στην κεφαλή ψυχαγωγίας Wiki - android auto
APKαρχείο εγκατάστασης λογισμικού (πακέτο εφαρμογών Android) Wiki - Building APK
Autosensυπολογισμός ευαισθησίας στην ινσουλίνη ως αποτέλεσμα άσκησης, ορμόνες κλπ. DIABETTECH - Autosens
Azurecloud computing platform για να φιλοξενήσει δεδομένα NightscoutHeroku / NightscoutAzure
BATχαμηλή στάθμη μπαταρίας στην αρχική οθόνηCAN / RES / SEN Προτιμήσεις
Στιγμιότυπα οθόνης
BGγλυκόζη αίματος  
BGIαλληλεπίδραση γλυκόζης στο αίμα - στο οποίο το BG πρέπει να αυξάνεται ή να πέφτει με βάση μόνο την ενεργότητα της ινσουλίνης  
Πηγή BGΑπό πού προέρχονται οι τιμές γλυκόζης;CGM / FGMWiki - Πηγή BG
Blukon Nightreaderbluetooth για να χρησιμοποιήσετε το Freestyle Libre ως CGMBlueReader / MiaoMiaoAmbrosia Blukon Nightreader
BRτου βασικού ρυθμού  
CAGEcanula age - displayed in Nightscout if information was entered in actions tab / menu tab or through AAPS actions tab 'prime'Nightscout 
CANstatus light overdue canula change on homescreenBAT / RES / SEN Προτιμήσεις
Στιγμιότυπα οθόνης
CGMcontinuous glucose monitor  
Κλειστό κύκλωμαclosed-loop systems make automatic adjustments to basal delivery, without needing user-approval, based on an algorithmOpen loopWiki closed loop
COBcarbs on board  
DIAduration of insulin action Wiki insulin types
DIABETTECH - DIA
DSTdaylight savings time Wiki DST
eCarbs"extended carbs" - carbs split up over serveral hours (i.e. lot of fat/protein)
extended boluses you might know from regular pump therapy do not make much sense when looping		SMBWiki - eCarbs
eCarbs use case
FGMflash glucose monitor (Freestyle Libre) Wiki - Πηγή BG
gitversion-control system for tracking changes in computer files and coordinating work on those files
-> neccessary for APK updates		 Wiki - update APK
Githubweb-based hosting service for version control using Git
-> storage of source code		 Github AndroidAPS
Glimpapp to collect values from Freestyle Libre Nightscout with Glimp
Herokucloud computing platform για να φιλοξενήσει δεδομένα NightscoutAzure / NightscoutHeroku
IC (or I:C)insulin to carb ratio (How many carbs are covered by one unit of insulin?)  
IOBinsulin on board - insulin active in your body  
ISFinsulin sensitivity factor - the expected decrease in BG as a result of one unit of insulin  
LGSLow Glucose Suspend
AAPS will reduce basal if blood glucose is dropping. But if blood glucose is rising then it will only increase basal if the IOB is negative (from a previous LGS), otherwise basal rates will remain the same as your selected profile. You may temporarily experience spikes following treated hypos without the ability to increase basal on the rebound.		objective 6 
LineageOSfree and open-source operating system for smartphones etc.
alternative OS for smartphones not running Android 8.1 (Oreo)
(when using Accu-Chek Combo)		 Wiki - Combo pump
Log filesrecord of all AAPS actions (useful for trubbleshooting and debugging) Wiki - log files
maxIOBsafety feature - maximum total IOB AAPS can't go over Wiki - maxIOB
Wiki - SMB
MiaoMiaobluetooth για να χρησιμοποιήσετε το Freestyle Libre ως CGMBlueReader / Blukon NightreaderMiaoMiao
5 λεπτά ελάχιστη δράση υδατανθράκωνsaftey feature - default carb decay at times when carb absorption can’t be dynamically worked out based on your bloods reactions Wiki - config builder
Nightscoutopen source project to access and report CGM dataNightscout ReporterNightscout
NS Clientpart of AAPS to connect to your Nightscout site Wiki - NS Client
Nightscout ReporterTool from fellow looper to generate PDFs reports from Nightscout dataNightscoutNightscout Reporter
NS Reporter @ Facebook
Στόχοιlearning program within AAPS guiding you step by step from open to closed loop Wiki - objectives
OpenAPSopen artificial pancreas system
APS run on small computers (i.e. Raspberry Pie)
AAPS uses some of the OpenAPS features		 OpenAPS docs
Ανοιχτό κύκλωμαsystem will suggest recommended adjustments which have to be performed manually on the pumpΚλειστό κύκλωμαWiki - config builder
Oref0 / Oref1sensitivity detection
"reference design implementation version 0/1" - the key algorithm behind OpenAPS		 Wiki - sensitivity detection
Peak timetime of maximum effect of insulin given Wiki - config builder
PHpump history (entry in treatments tab) Screenshots
Προβλέψειςpreditions for BG in the future based on different calculations Wiki - predition lines
Προφίλbasic treatment settings (basal rate, DIA, IC, ISF, BG target)
can be defined locally or through Nightscout		NightscoutWiki - profile
Αλλαγή Προφίλ(temporary) change of profile used or percentual increase/decrease Wiki - profile switch
RESstatus light overdue reservoir change on homescreenBAT / CAN / SEN Προτιμήσεις
Στιγμιότυπα οθόνης
RileyLinkopen source hardware device to bridge Bluetooth Low Energy (BLE) to 916MHz wireless communication (used for old Medtronic pumps)OpenAPS 
SAGEsensor age - displayed in Nightscout if information was entered in the actions tab / menuNightscout 
SENstatus light sensor change on homescreenBAT / CAN / RES Προτιμήσεις
Στιγμιότυπα οθόνης
Sensivity detectionυπολογισμός ευαισθησίας στην ινσουλίνη ως αποτέλεσμα άσκησης, ορμόνες κλπ. DIABETTECH - Autosens
Sensor noiseunstable CGM readings leading to "jumping" values Wiki - sensor noise
SMBsuper micro bolus
advanced feature for faster BG adjustment		UAMWiki - SMB
Super bolusshift of basal to bolus insulin for faster BG adjustment John Walsh - The Super Bolus
TBBtotal base basal (sum of basal rate within 24 hours)  
TBRtemporary basal rate  
TDDtotal daily dose (bolus + basal per day)  
TTtemporary target
temporary increase/decrease of BG target (range)		 Wiki - temp targets
UAMunannounced meals - detection of significant increase in glucose levels due to meals, adrenaline or other influences and attempt to adjust this with SMBSMBWiki - SMB
Virtual pumpoption to try AAPS functions or for PWD using a pump model with no AndroidAPS driver for loopingΑνοιχτό κύκλωμα 
ΤαπετσαρίαAndroidAPS background imagesee phones page
xDrip / xDrip+open source software to read CGM systems xDrip+
xDrip
Zero-temptemporary basal rate with 0% (no basal insulin delivery)  
See also https://openaps.readthedocs.io/en/latest/docs/Resources/glossary.html
diff --git a/docs/CROWDIN/el/Getting-Started/Safety-first.md b/docs/CROWDIN/el/Getting-Started/Safety-first.md deleted file mode 100644 index 0153dd034ad0..000000000000 --- a/docs/CROWDIN/el/Getting-Started/Safety-first.md +++ /dev/null @@ -1,41 +0,0 @@ -# Πρώτα η ασφάλεια - -**When you decide to build your own artificial pancreas, it's always important to think about security and safety, and to understand the impact of all your actions** - -## Γενικά - -- AAPS is a just a tool to help you manage diabetes, it is not a fully automated system you can install and forget! -- Do not assume that AAPS will never make mistakes. Αυτή η συσκευή αναλαμβάνει τον έλεγχο της χορήγησης ινσουλίνης: Παρακολουθήστε τη συνεχώς, κατανοήστε πώς λειτουργεί και μάθετε πώς να ερμηνεύετε τις ενέργειές της. -- Να θυμάστε ότι, μόλις συνδεθεί, το τηλέφωνο μπορεί να δώσει εντολή στην αντλία να κάνει οτιδήποτε. Only use this phone for AAPS and, if being used by a child, essential communications. Μην εγκαταστήσετε περιττές εφαρμογές ή παιχνίδια (!!!) που θα μπορούσαν να εισάγουν κακόβουλο λογισμικό, όπως trojans, ιούς ή bots που θα μπορούσαν να παρεμβληθούν στο σύστημά σας. -- Εγκαταστήστε όλες τις ενημερώσεις ασφαλείας που παρέχονται από τον κατασκευαστή του τηλεφώνου σας και το Google. -- Μπορεί επίσης να χρειαστεί να αλλάξετε τις συνήθειες του διαβήτη καθώς αλλάζετε τη θεραπεία σας χρησιμοποιώντας ένα σύστημα κλειστού κυκλώματος. Π.χ. some people report, they need less hypo treatments as AAPS has already reduced insulin. - -## Επικοινωνία με SMS - -- Το AAPS σας επιτρέπει να ελέγχετε εξ αποστάσεως το τηλέφωνο ενός παιδιού μέσω ενός μηνύματος SMS. Αν ενεργοποιήσετε αυτό την επικοινωνία με SMS, θυμηθείτε πάντα ότι το τηλέφωνο που έχει ρυθμιστεί για να δώσει απομακρυσμένες εντολές μπορεί να κλαπεί. Συνεπώς, πάντα να το προστατεύετε τουλάχιστον από ένα κωδικό PIN. -- Το AndroidAPS θα σας ενημερώσει επίσης με μήνυμα κειμένου , εάν έχουν πραγματοποιηθεί οι απομακρυσμένες εντολές σας, όπως μια γευματική δόση ή μια αλλαγή προφίλ. Συνιστάται να το ρυθμίσετε έτσι ώστε τα κείμενα επιβεβαίωσης να αποστέλλονται σε τουλάχιστον δύο διαφορετικούς αριθμούς τηλεφώνου σε περίπτωση κλοπής ενός από τα τηλέφωνα λήψης. - -(Safety-first-aaps-can-also-be-used-by-blind-people)= -## AAPS can also be used by blind people - -On Android devices TalkBack is part of the operating system. It is a program for screen orientation via voice output. With TalkBack you can operate your smartphone as well as AAPS blind. - -We users create the AAPS app ourselves with Android Studio. Many use Microsoft Windows for this purpose, where there is the Screenreader analogous to TalkBack. Since Android Studio is a Java application, the "Java Access Bridge" component must be enabled in the Control Panel. Otherwise, the screen reader of the PC will not speak in Android Studio. - -To do this, please proceed as follows: - -- Press WINDOWSTASTE and enter "Control Panel" in the search field, open with Enter. It opens: "All Control Panel Items". -- Press the letter C to get to "Center for Ease of Use", open with Enter. -- Then open "Use computer without a screen" with Enter. -- There, at the bottom, you will find the checkbox "Enable Java Access Bridge", select it. -- Done, just close the window! The screen reader should work now. - -```{note} -**IMPORTANT SAFETY NOTICE** - -The foundation of AAPS safety features discussed in this documentation is built on the safety features of the hardware used to build your system. Είναι πολύ σημαντικό να χρησιμοποιείτε μόνο μια δοκιμασμένη, πλήρως λειτουργική FDA ή CE εγκεκριμένη αντλία ινσουλίνης και CGM για το κλείσιμο ενός αυτοματοποιημένου κυκλώματος δοσολογίας ινσουλίνης. Οι τροποποιήσεις υλικού ή λογισμικού σε αυτά τα εξαρτήματα μπορεί να προκαλέσουν απροσδόκητη δόση ινσουλίνης, προκαλώντας σημαντικό κίνδυνο για τον χρήστη. If you find or get offered broken, modified or self-made insulin pumps or CGM receivers, *do not use* these for creating an AAPS system. - -Επιπλέον, είναι εξίσου σημαντικό να χρησιμοποιείτε μόνο αυθεντικά προϊόντα όπως εισαγωγείς, κάνουλα και δοχεία ινσουλίνης εγκεκριμένα από τον κατασκευαστή για χρήση με την αντλία ή το CGM. Η χρήση μη δοκιμασμένων ή τροποποιημένων αναλωσίμων μπορεί να προκαλέσει ανακρίβεια CGM και σφάλματα δοσολογίας ινσουλίνης. Η ινσουλίνη είναι εξαιρετικά επικίνδυνη όταν δίνετε σε λάθος δοσολογία - παρακαλώ μην παίζετε με τη ζωή σας με μη εγκεκριμένες προμήθειες. - -Last not least, you must not take SGLT-2 inhibitors (gliflozins) as they incalculably lower blood sugar levels. The combination with a system that lowers basal rates in order to increase BG is especially dangerous as due to the gliflozin this rise in BG might not happen and a dangerous state of lack of insulin can happen. -``` diff --git a/docs/CROWDIN/el/Getting-Started/Sample-Setup.md b/docs/CROWDIN/el/Getting-Started/Sample-Setup.md deleted file mode 100644 index 904ff94b1586..000000000000 --- a/docs/CROWDIN/el/Getting-Started/Sample-Setup.md +++ /dev/null @@ -1,151 +0,0 @@ -# Sample setup: Samsung S7, Dana RS, Dexcom G6 and Sony Smartwatch - -![Ρύθμιση δείγματος](../images/SampleSetup.png) - -## Περιγραφή - -Σε αυτή τη ρύθμιση, το smartphone Samsung Galaxy S7 χρησιμοποιείται ως κέντρο ελέγχου του κυκλώματος. The slightly modified Dexcom App reads glucose values from the Dexcom G6 CGM. AndroidAPS is used to control the Dana RS insulin pump from Korean manufacturer SOOIL via bluetooth. Δεν απαιτούνται άλλες συσκευές. - -Δεδομένου ότι η εφαρμογή Dexcom προσφέρει περιορισμένες επιλογές συναγερμού, η εφαρμογή open source xDrip + χρησιμοποιείται για τον ορισμό όχι μόνο υψηλών και χαμηλών συναγερμών αλλά και πρόσθετων συναγερμών σύμφωνα με τις επιμέρους απαιτήσεις. - -Προαιρετικά μπορεί να χρησιμοποιηθεί ένα smartwatch wear για Android (σε αυτή τη ρύθμιση δείγματος το Sony Smartwatch 3 (SWR50)) για την εμφάνιση των τιμών γλυκόζης και AndroidAPS στον καρπό σας. Το ρολόι μπορεί ακόμη να χρησιμοποιηθεί για τον έλεγχο του AndroidAPS (δηλ. Διακριτικά να ορίσει ένα bolus γεύματος). - -Το σύστημα λειτουργεί εκτός σύνδεσης. Αυτό σημαίνει ότι δεν υπάρχει ανάγκη για σύνδεση δεδομένων από το smartphone στο Internet για λειτουργία. - -Παρ 'όλα αυτά, τα δεδομένα μεταφορτώνονται αυτόματα στο Nightscout "στο cloud" όταν δημιουργείται μια σύνδεση δεδομένων. Με αυτόν τον τρόπο μπορείτε να παρέχετε ανά πάσα στιγμή αναλυτικές αναφορές για την επίσκεψη του γιατρού ή να μοιράζεστε τις τρέχουσες αξίες με τα μέλη της οικογένειάς σας. Είναι επίσης δυνατή η αποστολή δεδομένων στη Nightscout μόνο όταν χρησιμοποιείτε μια (προκαθορισμένη) σύνδεση Wi-Fi για να επωφεληθείτε από τις διάφορες αναφορές Nightscout. - -## Απαιτούμενος εξοπλισμός - -1. Samsung Galaxy S7 - - * Alternatives: see [list of tested phones and watches](https://docs.google.com/spreadsheets/d/1gZAsN6f0gv6tkgy9EBsYl0BQNhna0RDqA9QGycAqCQc/edit) for AndroidAPS - -2. [DanaRS](http://www.sooil.com/eng/product/) - - * Εναλλακτικά: - * [Accu-Chek Combo](../Configuration/Accu-Chek-Combo-Pump.md) - * [Accu-Check Insight](../Configuration/Accu-Chek-Insight-Pump.md) - * [DanaR](../Configuration/DanaR-Insulin-Pump.md) - * [Some old Medtronic pumps (additionally needed: RileyLink/Gnarl hardware, Android Phone with bluetooth low energy / BLE-chipset)](../Configuration/MedtronicPump.md) - * Other pumps might be available in the future, see [future possible pump drivers](Future-possible-Pump-Drivers.md) for details. - -3. [Dexcom G6](https://dexcom.com) - - * Alternatives: see list of possible [BG sources](../Configuration/BG-Source.md) - -4. Προαιρετικά: Sony Smartwatch 3 (SWR50) - - * Alternatives: All [watches with Google Wear OS](https://wearos.google.com/intl/de_de/#find-your-watch) should work fine, for details see [list of tested phones and watches](https://docs.google.com/spreadsheets/d/1gZAsN6f0gv6tkgy9EBsYl0BQNhna0RDqA9QGycAqCQc/edit) for AndroidAPS (OS must be Android Wear) - -## Ρύθμιση του Nightscout - -Δείτε λεπτομέρειες [ ρύθμιση Nightscout ](../Installing-AndroidAPS/Nightscout.md) - -## Ρύθμιση υπολογιστή - -Για να μπορέσετε να δημιουργήσετε μια εφαρμογή Android από τον ελεύθερα διαθέσιμο κώδικα ανοικτού πηγαίου κώδικα AAPS, χρειάζεστε το Android Studio στον υπολογιστή ή στο σημειωματάριό σας (Windows, Mac, Linux). Μια λεπτομερής οδηγία μπορεί να βρεθεί στο [ building the APK ](../Installing-AndroidAPS/Building-APK.md). - -Να είστε υπομονετικοί κατά την εγκατάσταση του Android Studio καθώς το λογισμικό κατεβάζει πολλά πρόσθετα δεδομένα μόλις εγκατασταθεί στον υπολογιστή σας. - -## Ρύθμιση Smartphone - -![Smartphone](../images/SampleSetupSmartphone.png) - -### Ελέγξτε το υλικολογισμικό του smartphone - -* Menu > Settings > Phone info > Software info: At least "Android-Version 8.0" (successfully tested up to Android version 8.0.0 Oreo - Samsung Experience Version 9.0) -* Για ενημέρωση υλικολογισμικού: μενού> Προτιμήσεις> ενημέρωση λογισμικού - -### Να επιτρέπεται η εγκατάσταση από άγνωστες πηγές - -Μενού> Ρυθμίσεις> Ασφάλεια συσκευής> Άγνωστες πηγές> ρυθμιστικό στη δεξιά πλευρά (= ενεργό) - -Για λόγους ασφαλείας, αυτή η ρύθμιση θα πρέπει να επαναφέρεται σε ανενεργό μόλις ολοκληρωθεί η εγκατάσταση όλων των εφαρμογών που περιγράφονται εδώ. - -### Ενεργοποιήστε το Bluetooth - -1. Μενού> Ρυθμίσεις> Συνδέσεις> Bluetooth> ρυθμιστικό στη δεξιά πλευρά (= ενεργό) -2. Μενού> Ρυθμίσεις> Συνδέσεις> Τοποθεσία> ρυθμιστικό στη δεξιά πλευρά (= ενεργό) - -Οι υπηρεσίες τοποθεσίας ("GPS") πρέπει να ενεργοποιηθούν για να λειτουργήσει σωστά το Bluetooth. - -### Εγκαταστήστε την εφαρμογή Dexcom (τροποποιημένη έκδοση) - -![Εφαρμογή Dexcom patched](../images/SampleSetupDexApp.png) - -Η αρχική εφαρμογή Dexcom από το Google Play Store δεν θα λειτουργήσει επειδή δεν μεταδίδει τις τιμές σε άλλες εφαρμογές. Επομένως, απαιτείται μια έκδοση ελαφρώς τροποποιημένη από την κοινότητα. Μόνο αυτή η τροποποιημένη εφαρμογή Dexcom μπορεί να επικοινωνήσει με το AAPS. Επιπλέον, η τροποποιημένη εφαρμογή Dexcom App μπορεί να χρησιμοποιηθεί με όλα τα Android smartphones όχι μόνο σε αυτά που περιλαμβάνονται στη λίστα συμβατότητας [ της Dexcom ](https://www.dexcom.com/dexcom-international-compatibility). - -To do this perform the following steps on your smartphone: - -1. Εάν η αρχική εφαρμογή Dexcom έχει ήδη εγκατασταθεί: - * Σταματήστε τον αισθητήρα - * Uninstall app via Menu > Settings > Apps > Dexcom G6 Mobile > Uninstall -2. Download and install the [BYODA Dexcom ap](../Hardware/DexcomG6.md#if-using-g6-with-build-your-own-dexcom-app) -3. Start modified Dexcom G6 app, activate/calibrate the sensor according to the given instructions and wait until the warm-up phase is finished. -4. Once the modified Dexcom app shows actual glucose value, setup the warnings (hamburger menu on top left side of the screen) as follows: - * Urgent low `55mg/dl` / `3.1mmol/l` (cannot be disabled) - * Low `OFF` - * High `OFF` - * Rise rate `OFF` - * Fall rate `OFF` - * Signal loss `OFF` - -## Εγκατάσταση AndroidAPS - -1. Follow the instructions to [build the APK](../Installing-AndroidAPS/Building-APK.md#generate-signed-apk) -2. [Transfer](../Installing-AndroidAPS/Building-APK.md#transfer-apk-to-smartphone) the generated APK to your phone -3. [ Διαμορφώστε το AndroidAPS ](../Configuration/Config-Builder.md) ανάλογα με τις ανάγκες σας χρησιμοποιώντας το βοηθό εγκατάστασης ή με μη αυτόματο τρόπο -4. Σε αυτό το δείγμα χρησιμοποιήσαμε (μεταξύ άλλων) - -* BG source: `Dexcom G6 App (patched)` -- click cock-wheel and activate `Upload BG data to NS` and `Send BG data to xDrip+` (see [BG source](../Configuration/BG-Source.md)) - -![G5 Settings](../images/SampleSetupG5Settings.png) - -* NS Client activated (see [Nightscout setup](../Installing-AndroidAPS/Nightscout.md)) - -## Εγκατάσταση xDrip+ - -xDrip+ is another mature open source app that offers countless possibilities. In this setup, contrary to what the developers first wrote the app for, xDrip+ is not used to collect glucose data from the Dexcom G6, but only to output alarms and to display the current glucose value including the curve on the Android home screen in the widget. With xDrip+ the alarms can be set much more individually than with the Dexcom software, AAPS or Nightscout (no limitation in the selection of sounds, different alarms depending on day/night time etc.). - -1. Κατεβάστε την τελευταία σταθερή έκδοση APK του xDrip + με το smartphone σας [ https://xdrip-plus-updates.appspot.com/stable/xdrip-plus-latest.apk ](https://xdrip-plus-updates.appspot.com/stable/xdrip-plus-latest.apk) - όχι την έκδοση από το Google Play Store! -2. Εγκαταστήστε το xDrip + επιλέγοντας το ληφθέν αρχείο APK. -3. Ξεκινήστε το xDrip + και πραγματοποιήστε τις ακόλουθες ρυθμίσεις (μενού χάμπουργκερ στο επάνω αριστερό μέρος) - * Ρυθμίσεις> Συναγερμοί και ειδοποιήσεις> Λίστα ειδοποιήσεων επιπέδου γλυκόζης> Δημιουργία ειδοποιήσεων (υψηλή και χαμηλή) ανάλογα με τις ανάγκες σας. - * Οι υπάρχοντες συναγερμοί μπορούν να αλλάξουν με μακρύ πάτημα του συναγερμού. - * Ρυθμίσεις> Συναγερμοί και ειδοποιήσεις> Ειδοποιήσεις βαθμονόμησης: απενεργοποιημένη (υπενθυμίζεται μέσω της τροποποιημένης εφαρμογής Dexcom) - * Ρυθμίσεις> Πηγή δεδομένων υλικού> 640G / EverSense - * Ρυθμίσεις> Ρυθμίσεις μεταξύ εφαρμογών> Αποδοχή βαθμονομήσεων> ` ON ` - * Menu > Start sensor (is only "pro forma" and has nothing to do with the running G6 sensor. Αυτό είναι απαραίτητο, διαφορετικά θα εμφανίζεται τακτικά ένα μήνυμα σφάλματος.) - -For more information about xDrip+, see here [BG source page](../Configuration/BG-Source.md). - -### Παράδειγμα ρύθμισης συναγερμού - -The "Urgent low alarm" (below 55 mg/dl resp. 3,1 mmol) is a standard alarm from the modified Dexcom app that cannot be disabled. - -![xDrip alarms](../images/SampleSetupxDripWarning.png) - -Tip for meetings / church visits / cinema etc..: - -If "Do not disturb" mode is activated in the Samsung Galaxy S7 (Menu > Settings > Sounds and vibration > Do not disturb: slider to right side (= active)), the phone only vibrates during urgent low alarm and does not issue an acoustic warning. For the other alarms set up via xDrip+ you can select whether the silent mode should be ignored (acoustic sound played) or not. - -## Απενεργοποιήστε την επιλογή εξοικονόμησης ενέργειας - -On your Samsung Galaxy S7 go to Menu > Settings > Device Maintenance > Battery > Unmonitored Apps > + Add apps: Select the apps AndroidAPS, Dexcom G6 Mobile, xDrip+ and Android Wear (if smartwatch is used) one after the other - -## Προαιρετικά: Ρύθμιση της συσκευής Sony Smartwatch 3 (SWR50) - -With an Android Wear smartwatch life with diabetes can be made even more inconspicuous. The watch can be used to display the current glucose level, the status of the loop etc. on the wrist. Το ρολόι μπορεί ακόμη να χρησιμοποιηθεί για τον έλεγχο του AndroidAPS (δηλ. Διακριτικά να ορίσει ένα bolus γεύματος). To do this, double tap the CGM value of the AAPSv2 watchface. The SWR50 usually runs for a full day until the battery needs to be recharged (same charger as the Samsung Galaxy S7: microUSB). - -![Smartwatch](../images/SampleSetupSmartwatch.png) - -Details about the information displayed on the watchface can be found [here](../Configuration/Watchfaces.md). - -* Εγκαταστήστε την εφαρμογή "Android Wear" στο smartphone σας μέσω του Google Play Store και συνδέστε το smartwatch σύμφωνα με τις οδηγίες εκεί. -* Στο AAPS επιλέξτε μενού χάμπουργκερ (άνω αριστερή γωνία)> Config Builder> Γενικά (στο κάτω μέρος της λίστας)> Φορέστε> ενεργοποιήστε την αριστερή πλευρά, κάντε κλικ στο τιμόνι> ρυθμίσεις Wear και να ενεργοποιείστε ` έλεγχος από ρολόι` -* Στο smartwatch σας: Πατήστε παρατεταμένα το πλήκτρο για να αλλάξετε το ρολόι και επιλέξτε ` AAPSv2 ` -* Αν χρειάζεται, κάντε επανεκκίνηση και των δύο συσκευών μία φορά. - -## Ρύθμιση αντλίας - -see [Dana RS pump](../Configuration/DanaRS-Insulin-Pump.md) \ No newline at end of file diff --git a/docs/CROWDIN/el/Getting-Started/WhatisAndroidAPS.md b/docs/CROWDIN/el/Getting-Started/WhatisAndroidAPS.md deleted file mode 100644 index b76138483f63..000000000000 --- a/docs/CROWDIN/el/Getting-Started/WhatisAndroidAPS.md +++ /dev/null @@ -1,39 +0,0 @@ -# What is a closed loop system with AAPS? - -AAPS is an app that acts as an artificial pancreas system (APS) on an Android smartphone. Τι είναι ένα τεχνητό σύστημα παγκρέατος; Είναι ένα πρόγραμμα λογισμικού που στοχεύει να κάνει ό, τι κάνει ένα ζωντανό πάγκρεας: διατηρεί τα επίπεδα σακχάρου στο αίμα μέσα σε υγιή όρια. - -Ένα APS δεν μπορεί να κάνει τη δουλειά όπως ένα βιολογικό πάγκρεας, αλλά μπορεί να κάνει τον διαβήτη τύπου 1 ευκολότερο να διαχειριστεί χρησιμοποιώντας συσκευές που είναι εμπορικά διαθέσιμες και λογισμικό που είναι απλό και ασφαλές. Those devices include a continuous glucose monitor (CGM) to tell AAPS about your blood sugar levels and an insulin pump which AAPS controls to deliver appropriate doses of insulin. Η εφαρμογή επικοινωνεί με αυτές τις συσκευές μέσω bluetooth. Κάνει τους υπολογισμούς δόσεων χρησιμοποιώντας έναν αλγόριθμο ή ένα σύνολο κανόνων που έχουν αναπτυχθεί για ένα άλλο τεχνητό σύστημα παγκρέατος, που ονομάζεται OpenAPS, το οποίο έχει χιλιάδες χρήστες και έχει συσσωρεύσει εκατομμύρια ώρες χρήσης. - -A note of caution: AAPS is not regulated by any medical authority in any country. Using AAPS is essentially carrying out a medical experiment on yourself. Η εγκατάσταση του συστήματος απαιτεί αποφασιστικότητα και τεχνικές γνώσεις. Εάν δεν έχετε την τεχνική τεχνογνωσία στην αρχή, θα την έχετε στο τέλος. Όλες οι πληροφορίες που χρειάζεστε μπορούν να βρεθούν σε αυτά τα έγγραφα, αλλού online ή από άλλους που το έχουν ήδη κάνει - μπορείτε να τα ρωτήσετε σε ομάδες του Facebook ή σε άλλα φόρουμ. Many people have successfully built AAPS and are now using it entirely safely, but it is essential that every user: - -- Να δημιουργεί το ίδιο το σύστημα έτσι ώστε να κατανοεί πλήρως το πώς λειτουργεί -- Ρυθμίζει τον ατομικό αλγόριθμο δοσολογίας με την ομάδα του διαβήτη για να δουλέψει σχεδόν τέλεια -- Να διατηρεί και παρακολουθεί το σύστημα για να διασφαλίσει ότι λειτουργεί σωστά - -```{note} -**Disclaimer and Warning** - -- All information, thought, and code described here is intended for informational and educational purposes only. Το Nightscout δεν πραγματοποιεί επί του παρόντος προσπάθεια συμμόρφωσης με το HIPAA. Use Nightscout and AAPS at your own risk, and do not use the information or code to make medical decisions. -- Η χρήση του κώδικα από το github.com είναι χωρίς εγγύηση ή επίσημη υποστήριξη οποιασδήποτε μορφής. Ανατρέξτε στην ΑΔΕΙΑ ΑΠΟΣΤΟΛΗΣ αυτού του αποθετηρίου για λεπτομέρειες. -- Όλα τα ονόματα των προϊόντων και των εταιρειών, τα εμπορικά σήματα, τα κατατεθέντα εμπορικά σήματα και τα καταχωρημένα λογότυπα υπηρεσίας αποτελούν ιδιοκτησία των αντίστοιχων κατόχων τους. Η χρήση τους είναι για ενημερωτικούς σκοπούς και δεν συνεπάγεται καμία προσχώρηση ή έγκριση από αυτούς. - -Please note - this project has no association with and is not endorsed by: [SOOIL](http://www.sooil.com/eng/), [Dexcom](https://www.dexcom.com/), [Accu-Chek, Roche Diabetes Care](https://www.accu-chek.com/), [Insulet](https://www.insulet.com/) or [Medtronic](https://www.medtronic.com/). -``` - -Εάν είστε έτοιμοι για την πρόκληση, παρακαλώ διαβάστε το. - -## Primary goals behind AAPS - -- Μια εφαρμογή με ενσωματωμένη ασφάλεια. To read about the safety features of the algorithms, known as oref0 and oref1, click here () -- Μια εφαρμογή all-in-one για τη διαχείριση του διαβήτη τύπου 1 με τεχνητό πάγκρεας και Nightscout -- An app to which users can easily add or remove modules as needed -- An app with different versions for specific locations and languages. -- An app which can be used in open- and closed-loop mode -- An app that is totally transparent: users can input parameters, see results, and make the final decision -- An app which is independent of particular pump drivers and contains a "virtual pump" so users can safely experiment before using it on themselves -- Μια εφαρμογή που είναι στενά συνδεδεμένη με το Nightscout -- Μια εφαρμογή στην οποία ο χρήστης ελέγχει τους περιορισμούς ασφαλείας - -## Πώς να ξεκινήσω - -Φυσικά, όλο αυτό το περιεχόμενο εδώ είναι πολύ σημαντικό, αλλά μπορεί να είναι στην αρχή αρκετά συγκεχυμένο. A good orientation is given by the [Module Overview](../Module/module.md) and the [Objectives](../Usage/Objectives.html). diff --git a/docs/CROWDIN/el/Hardware/DexcomG4.md b/docs/CROWDIN/el/Hardware/DexcomG4.md deleted file mode 100644 index 05f6dc1c32cb..000000000000 --- a/docs/CROWDIN/el/Hardware/DexcomG4.md +++ /dev/null @@ -1,6 +0,0 @@ -# Dexcom G4 - -## Εάν χρησιμοποιείτε το G4 με OTG καλώδιο (''παραδοσιακό'' Nightscout) -- If not already set up then download Nightscout Uploader app from the Play Store and follow instructions on [Nightscout](https://nightscout.github.io/). -- In AAPS Preferences enter your Nightscout website and API secret. -- Select NSClient in ConfigBuilder (setting in AAPS). diff --git a/docs/CROWDIN/el/Hardware/Smartwatch.md b/docs/CROWDIN/el/Hardware/Smartwatch.md deleted file mode 100644 index 12281d6d256a..000000000000 --- a/docs/CROWDIN/el/Hardware/Smartwatch.md +++ /dev/null @@ -1,10 +0,0 @@ -# Smartwatches - -Smartwatches are optional, but very useful for some users. More details are here: - -- [List of tested phones and smartwatches](../Getting-Started/Phones.md) -- [Watchfaces Wear OS](../Configuration/Watchfaces.md) -- [Troubleshooting Sony Smartwatch SW 3](../Usage/SonySW3.md) - -## Instructions for Building the AAPS Wear APK for Wear OS -https://androidaps.readthedocs.io/en/latest/remote-control.html#building-the-aaps-wear-apk diff --git a/docs/CROWDIN/el/Installing-AndroidAPS/Building-APK.md b/docs/CROWDIN/el/Installing-AndroidAPS/Building-APK.md deleted file mode 100644 index d983c1ad653f..000000000000 --- a/docs/CROWDIN/el/Installing-AndroidAPS/Building-APK.md +++ /dev/null @@ -1,369 +0,0 @@ -# Δημιουργώντας την εφαρμογή APK - -## Φτιάξτε το μόνοι σας, αντί να το κατεβάσετε - -**AAPS is not available as download due to regulation for medical devices. It is legal to build the app for your own use, but you must not give a copy to others! Δείτε το [σελίδα FAQ](../Getting-Started/FAQ.md) για λεπτομέρειες.** - -## Σημαντικές σημειώσεις - -* Please use **[Android Studio Giraffe" (2022.3.1)](https://developer.android.com/studio/)** or newer to build the apk. -* [Windows 32-bit systems](troubleshooting_androidstudio-unable-to-start-daemon-process) are not supported by Android Studio - -(Building-APK-recommended-specification-of-computer-for-building-apk-file)= - -## Recommended specification of computer for building apk file - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
OS (Only 64 bit)Windows 8 or higherMac OS 10.14 or higherAny Linux supports Gnome, KDE, or Unity DE;  GNU C Library 2.31 or later

CPU (Only 64 bit)

x86_64 CPU architecture; 2nd generation Intel Core or newer, or AMD CPU with support for a
Windows Hypervisor		ARM-based chips, or 2nd generation Intel Core or newer with support for
Hypervisor.Framework		x86_64 CPU architecture; 2nd generation Intel Core or newer, or AMD processor with support for AMD Virtualization (AMD-V) and SSSE3

RAM

8GB or more

Disk

At least 30GB free space. SSD is recommended.

Resolution

1280 x 800 Minimum

Internet

Broadband

- -Please keep in mind that both **64 bit CPU and 64 bit OS are mandatory condition.** If your system DOES NOT meet this condition, you have to change affected hardware or software or the whole system. **It is strongly recommended to use SSD (Solid State Disk) instead of HDD (Hard Disk Drive) because it will take less time when you are building the APS installation apk file.** Recommended is just recommended and it is not a mandatory. However, you may still use a HDD when you are building apk file but note that the building process can take a long time to complete, although once started, you can leave it running unattended. - -* * * - -### Αυτό το άρθρο χωρίζεται σε δύο μέρη. - -* Στο τμήμα επισκόπησης υπάρχει μια εξήγηση για τα βήματα που απαιτούνται για τη δημιουργία του αρχείου APK. -* Στο τμήμα βήμα προς βήμα θα βρείτε τα στιγμιότυπα οθόνης μιας πετυχημένης εγκατάστασης. Because the versions of Android Studio - the software development environment which we will use to build the APK - will change very quickly this will be not identical to your installation but it should give you a good starting point. Android Studio also runs on Windows, Mac OS X and Linux and there might be small differences in some aspects between each platform. If you find that something important is wrong or missing, please inform the facebook group "AAPS users" or in the Discord chat [Android APS](https://discord.gg/4fQUWHZ4Mw) so that we can have a look at this. - -## Σφαιρική Εικόνα - -Γενικά, τα απαραίτητα βήματα για τη δημιουργία του αρχείου APK: - -1. [Εγκαταστήστε το git](../Installing-AndroidAPS/git-install.md) -2. [Εγκατάσταση του Android Studio](Building-APK-install-android-studio) -3. [Set git path in Android Studio preferences](Building-APK-set-git-path-in-preferences) -4. [Download AAPS code](Building-APK-download-AAPS-code) -5. [Download Android SDK](Building-APK-download-android-sdk) -6. [Build the app](Building-APK-generate-signed-apk) (generate signed apk) -7. [Transfer apk file to your phone](Building-APK-transfer-apk-to-smartphone) -8. [Προσδιορίστε το δέκτη αν χρησιμοποιείτε το xDrip+](xdrip-identify-receiver) - -## Περιγραφή βήμα-βήμα - -Λεπτομερής περιγραφή των βημάτων που είναι απαραίτητα για τη δημιουργία του αρχείου APK. - -## Εγκαταστήστε το git (αν δεν το έχετε) - -Follow the manual on the [git installation page](../Installing-AndroidAPS/git-install.md). - -(Building-APK-install-android-studio)= - -## Εγκατάσταση του Android Studio - -The following screenshots have been taken from Android Studio Version Arctic Fox | 2020.3.1. Screens can change in future versions of Android Studio. Αλλά θα πρέπει να μπορείτε να βρείτε το δρόμο σας. [Help from the community](../Where-To-Go-For-Help/Connect-with-other-users.md) is provided. - -One of the most important things when installing Android Studio: **Be patient!** During installation and setup Android Studio is downloading a lot of stuff which will take its time. - -Download [Android Studio from here](https://developer.android.com/studio/install.html) and install it on your computer. - -On first start you will find the setup wizard: - -Επιλέξτε "Μην εισάγετε ρυθμίσεις", εάν δεν το έχετε χρησιμοποιήσει προηγουμένως. - -![Do not import settings](../images/studioSetup/01_ImportSettings.png) - -Decide whether you want to share data with Google or not. - -![Share data with Google](../images/studioSetup/02_DataSharing.png) - -On the following screen click "Next". - -![Welcome screen](../images/studioSetup/03_Welcome.png) - -Επιλέξτε την "βασική" εγκατάσταση και κάντε κλικ στο "Επόμενο". - -![Standard installation](../images/studioSetup/04_InstallType.png) - -Select the theme for the user interface you like. (In this manual we used "Light".) Then click "Next". - -> ***Note:*** This is just the color scheme. You can select whatever you like (i.e. "Darcula" for dark mode). This selection has no influence on building the APK but the following screenshots might look different. - -![UI color scheme](../images/studioSetup/05_UITheme.png) - -Click "Next" on the "Verify Settings" dialog. - -![Verify settings](../images/studioSetup/06_Overview.png) - -Click on all three license agreement parts and select "Agree". When you have agreed to all, the "Finish" button will be enabled and you can "Finish". - - ![Agree license agreements](../images/studioSetup/07_LicenseAgreement.png) - - -Wait while Android Studio downloads additional components and be patient. Once everything is downloaded button "Finish" turns blue. Click the button now. - -![Downloading components](../images/studioSetup/08_Downloading.png) - -(Building-APK-download-AAPS-code)= - -## Download AAPS code - -* On the Android Studio welcome screen select "Projects" (1) on the left and then "Get from VCS" (2). - - ![Android Studio wizard](../images/studioSetup/20_ProjectVCS.png) - - * If you already opened Android Studio and do not see the welcome screen anymore select File (1) > New (2) > Project from Version Control... (3) - - ![Check out project from version control within Android Studio](../images/AndroidStudio_FileNew.PNG) - - * We will now tell Android Studio were to get the code from: - - * Make sure you have selected "Repository URL" on the left (1). - - * Check if "Git" is selected as version control (2). - * Copy and paste the URL ```https://github.com/nightscout/AndroidAPS``` to the main AAPS repository into the URL textbox (3). - * Choose the directory where you want to save the cloned code (4). - - ![Clone Git](../images/studioSetup/21_CloneURL.png) - -* Click button "Clone" (5). - - ![Clone repository](../images/studioSetup/22_Cloning.png) - -* Do not click "Background" while repository is cloned! - -* After the repository is cloned successfully, Android Studio will open the cloned project. - -* You will be asked whether you want to trust the project. Click on "Trust project"! - - ![Trust project](../images/studioSetup/23_TrustProject.png) - -* In the status bar at the bottom you will see the information that Android Studio is running background tasks. - - ![Background tasks](../images/studioSetup/24_GradleSyncRunning.png) - -* Windows only: Grant access if your firewall is asking for permission. - - ![Firewall permission java](../images/AndroidStudio361_18.png) - -* Once the background tasks are finished you will probably see an error saying that errors occurred (1) or (2) or (3). - - ![SDK licence](../images/studioSetup/25_SyncFailed.png) - - Don't worry, this will be solved soon! - -(Building-APK-set-git-path-in-preferences)= - -## Set git path in preferences - -Make sure [git is installed](../Installing-AndroidAPS/git-install.md) on your computer and you have restarted your computer since installing. - -On the Android Studio welcome screen click "Customize" (1) on the left and then select the link "All settings..." (2): - -![Android Studio settings from welcome screen](../images/studioSetup/10_WizardSettings.png) - -### Windows - -* As windows user, make sure you have restarted your computer after [installing Git](../Installing-AndroidAPS/git-install.md). - -* In the menu, go to File (1) > Settings (2) (or Android Studio > Preferences on Mac). - - ![Open settings](../images/studioSetup/30_Settings.png) - -* Double-click "Version Control" (1) to open the sub-menu. - -* Click Git (2). -* Make sure update method "Merge" (3) is selected. -* Check if Android Studio can locate path to git.exe automatically by clicking the button "Test" (4). - - ![Android Studio settings](../images/studioSetup/11_GitPath.png) - -* If automatic setting is successful git version will be displayed next to the path. - - ![Git version displayed](../images/studioSetup/12_GitVersion.png) - -* Eventually git.exe cannot be found automatically or the Test will result in an error (1): - - ![Git not found](../images/studioSetup/13_GitVersionError.png) - - In this case click on the folder icon (2). - -* Use [search function](https://www.tenforums.com/tutorials/94452-search-file-explorer-windows-10-a.html) in windows explorer to find "git.exe" if you are unsure where git has been installed. You are looking for a file named "git.exe", located in **\bin** folder. - -* Select path to git.exe and make sure you selected the one in ** \bin\ ** folder (3) and click "OK" (4). - - ![Select git manually](../images/studioSetup/14_GitManualSelection.png) - -* Check your selected git path again with the "Test" button as described above. - -* When the git version is displayed next to the path (see screenshot above), close settings window by clicking "OK" button (5). - -### Mac - -* Any git version should work. For example . -* Use homebrew to install git: ```$ brew install git```. -* For details on installing git see the [official git documentation](https://git-scm.com/book/en/v2/Getting-Started-Installing-Git). -* If you install git via homebrew there is no need to change any preferences. Just in case: They can be found here: Android Studio - Preferences. - -(Building-APK-download-android-sdk)= - -## Download Android SDK - -* In the menu, go to File (1) > Settings (2) (or Android Studio > Preferences on Mac). - - ![Open settings](../images/studioSetup/30_Settings.png) - -* Double-click on Languages & Frameworks to open its submenu (1). - -* Select Android SDK (2). -* Tick the box left of "Android 9.0 (Pie)" (3) (API Level 28). - - ![SDK settings](../images/studioSetup/31_AndroidSDK.png) - -* Confirm changes by clicking OK. - - ![Confirm SDK changes](../images/studioSetup/32_ConfirmSDK.png) - -* Wait until the SDK download and installation is finished. - - ![Wait during SDK installation](../images/studioSetup/34_DownloadSDK.png) - -* When SDK installation is completed the "Finish" button will turn blue. Click this button. - - ![Finish SDK installation](../images/studioSetup/35_DownloadSDKfinished.png) - -* Android Studio might recommend to update the gradle system. **Never update gradle!** This will lead to difficulties! - -* If you see an information on the lower right side of your Android Studio window that Android Gradle Plugin is ready to update click on the text "upgrade" (1). - - ![No gradle update](../images/studioSetup/36_GradleUpdateRequest.png) - -* In the dialog box the select "Don't remind me again for this project" (2). - - ![No gradle update](../images/studioSetup/37_GradleUpdateDeny.png) - -* Restart Android Studio before you continue. - -(Building-APK-generate-signed-apk)= - -## Δημιουργία υπογεγραμμένου APK - -Signing means that you indicate your app to be your own creation but in a digital way as a kind of digital fingerprint within the app itself. That is necessary because Android has a rule that it only accepts signed code to run for security reasons. For more information on this topic, follow [this link](https://developer.android.com/studio/publish/app-signing.html#generate-key). - -* After Android Studio is started, wait until all background tasks are finished. - - ![Wait for background tasks](../images/studioSetup/40_BackgroundTasks.png) - - * ***Warning:*** If errors occur, do not continue with the following steps. \ Consult the [troubleshooting section](../Installing-AndroidAPS/troubleshooting_androidstudio) for known problems! - - ![Gradle Sync Error](../images/studioSetup/41_GradleSyncError.png) - -* Click "Build" (1) in the menu bar and select "Generate Signed Bundle / APK..." (2). - - ![Build apk](../images/studioSetup/42_MenuBuild.png) - -* Select "APK" (1) instead of "Android App Bundle" and click "Next" (2). - - ![APK instead of bundle](../images/studioSetup/43_Apk.png) - -* Make sure that module is set to "AndroidAPS.app" (1). - -* Click "Create new..." (2) to start creating your key store. - - ***Note:*** A key store in this case is nothing more than a file in which the information for signing is stored. Είναι κρυπτογραφημένο και οι πληροφορίες είναι ασφαλείς με κωδικούς πρόσβασης. - - ![Create key store](../images/studioSetup/44_KeystoreNew.png) - -* Click the folder symbol to select a path on your computer for your key store. - - ![Create key store](../images/studioSetup/45_KeystoreDialog.png) - -* Select the path where your key store shall be saved (1). - - ![Create key store](../images/studioSetup/46_KeystorePath.png) - - ***Warning: Do not save in same folder as project. You must use a different directory!*** A good location would be your home folder. - -* Type a file name for your key store (2) and confirm with "OK" (3). - -* Enter (2) and confirm (3) the password for your key store. ![Select key store path](../images/studioSetup/47_KeystoreDialog.png) - - ***Note:*** Passwords for key store and key do not have to be very sophisticated. Make sure to remember those or make a note in a safe place. In case you will not remember your passwords in the future, see [troubleshooting for lost key store](troubleshooting_androidstudio-lost-keystore). - -* Enter an alias (4) for your key. Choose whatever you like. - -* Enter (5) and confirm (6) the password for your key - -* Validity (7) is 25 years by default. You do not have to change the default value. - -* First and last name must be entered (8). All other information is optional. - -* Click "OK" (9) when you are done. - -* Make sure the box to remember passwords is checked (1). So you don't have to enter them again next time you build the apk (i.e. when updating to a new AAPS version). - -* Click "Next" (2). - - ![Remember passwords](../images/studioSetup/48_KeystoreSave.png) - -* Select build variant "fullRelease" (1) and press "Finish". - - ![Select build variant](../images/studioSetup/49_BuildVariant.png) - -* Android Studio will show "Gradle Build running" at the bottom. This takes some time, depending on your computer and internet connection. **Be patient!** - - ![Gradle Running](../images/studioSetup/50_GradleRunning.png) - -* Android Studio will display the information "Generate Signed APK" after build is finished. - - ![Build finished](../images/studioSetup/51_BuildFinished.png) - -* In case build was not successful refer to the [troubleshooting section](../Installing-AndroidAPS/troubleshooting_androidstudio). - -* Click on the notification to expand it. - -* Click on the link "locate". - - ![Locate build](../images/studioSetup/52_BuildLocate.png) - - * If the notification is gone, you can always open the "Event log" and select the same link there. ![Build successfully - event log](../images/studioSetup/53_EventLog.png) - -* Your file manager/explorer will open. Navigate to the directory "full" (1) > "release" (2). - - ![File location apk](../images/studioSetup/54_APKlocation.png) - -* "app-full-release.apk" (3) is the file you are looking for! - -(Building-APK-transfer-apk-to-smartphone)= - -## Μεταφορά APK σε smartphone - -Easiest way to transfer app-full-release.apk to your phone is via [USB cable or Google Drive](https://support.google.com/android/answer/9064445?hl=en). Please note that transfer by mail might cause difficulties and is not the preferred way. - -On your phone you have to allow installation from unknown sources. Manuals how to do this can be found on the internet (i.e. [here](https://www.expressvpn.com/de/support/vpn-setup/enable-apk-installs-android/) or [here](https://www.androidcentral.com/unknown-sources)). - -## Αντιμετώπιση προβλημάτων - -See separate page [troubleshooting Android Studio](../Installing-AndroidAPS/troubleshooting_androidstudio). \ No newline at end of file diff --git a/docs/CROWDIN/el/Resources/index.md b/docs/CROWDIN/el/Resources/index.md deleted file mode 100644 index 6e4a3d51e88b..000000000000 --- a/docs/CROWDIN/el/Resources/index.md +++ /dev/null @@ -1,8 +0,0 @@ -# Πηγές - -```{toctree} -:glob: true -:maxdepth: 4 - -κλινικός οδηγός για AndroidAPS -``` diff --git a/docs/CROWDIN/el/Sandbox/sandbox2.md b/docs/CROWDIN/el/Sandbox/sandbox2.md deleted file mode 100644 index 33c547956c89..000000000000 --- a/docs/CROWDIN/el/Sandbox/sandbox2.md +++ /dev/null @@ -1,43 +0,0 @@ -# internal sandbox file 2 for testing - -```{admonition} no need to translate this -:class: note - -No need to translate this. -``` - -This is an internal sandbox file for the documentation team to test - -1. markdown syntax and - -1. background process for - 1. CROWDIN translation and - 2. Read The Docs deployment. - -You can dirctly jump from here to the first label in the sandbox1.md file - ["Jump"](sandbox1-this-is-a-test). - -You can dirctly jump from here to the second label in this file - ["Jump"](sandbox1-this-is-another-test). - -Here you can jump to the first sandbox file - ["Jump"](./sandbox1.md). - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -(sandbox2-this-is-a-test)= -## This is a test - -This is a test if labels must be unique. - -### This is spare information from the docs - -cut from index: - -There are "limits" set in place when you are first beginning your AAPS journey. These safety limits have been developed over many years by observations of the inadvertent mistakes that new users are most likely to make when first learning to set up, build, and then successfully loop with AAPS - as most often those mistakes occur simply because the user was so excited to get started using the system that they may have forgotten to sit down and dedicate the time needed to understand the information within this documentation thoroughly. - - -### spare info from the overview to put into "preparing" - -Since the requirements are very different from anything you might have set up in the past, we recommend that you really follow the instructions, step-by-step the first few times you build the app, so that you have a stronger sense of how the app building process is supposed to behave when all directions are followed exactly. Please remember to take your time. Later this will go very quickly when you build the app again for a new version. That way you will have a greater chance of noticing when something doesn't going as planned before too many steps are out of line. It is important to save the your keystore file (.jks file used to sign your app) in a safe place, so that you can always use that exact same keystore file and password each and every time you are asked to create a new updated version of AAPS, as this file is what makes sure that each new version of the app "remembers" all the information that you have provided to it in previous versions of the app and thus ensure that the updates will go as smoothly as possible. On average, you can assume that there will be one new version and 2-3 required updates per year. This number is based on experience and may change in the future. But we do want to at least give you a general guideline on what to expect. When you are more experienced at building updated AAPS app versions all the steps that are required in building an updated app will only take 15-30 minutes, on average. However, in the beginning there can be a rather steep learning curve as these steps are not always considered intuitive by new users! So do not get frustrated if you find that it takes half a day or a whole day with some help from the community before you are finally finished with the update process. If you find that you are getting very frustrated just take a short break, and oftentimes; after a stroll around the block or two...you'll find that you are better able to approach the problem again. diff --git a/docs/CROWDIN/el/Usage/Objectives.md b/docs/CROWDIN/el/Usage/Objectives.md deleted file mode 100644 index 41fae3091d3f..000000000000 --- a/docs/CROWDIN/el/Usage/Objectives.md +++ /dev/null @@ -1,184 +0,0 @@ -# Στόχοι - -AAPS has a series of Objectives that need to be completed to walk you through the features and settings of safe looping. Εξασφαλίζουν ότι έχετε ρυθμίσει σωστά όλες τις λεπτομέριες στις παραπάνω ενότητες και ότι καταλαβαίνετε τι κάνει το σύστημά και γιατί μπορείτε να το εμπιστευτείτε. - -If you are **upgrading phones** then you can [export your settings](../Usage/ExportImportSettings.md) to keep your progress through the objectives. Not only will your progress through the objectives be saved, but also your safety settings such as max bolus etc. If you do not export and import your settings then you will need to start the objectives from the beginning again. It is a good idea to [backup your settings](../Usage/ExportImportSettings.html) frequently just in case. - -If you want to go back in objectives see [explanation below](Objectives-go-back-in-objectives). - -## Στόχος 1: Δημιουργία οπτικοποίησης και παρακολούθησης, ανάλυση βασικού δεδομένων και αναλογιών - -- Select the right blood glucose source for your setup. See [BG Source](../Configuration/BG-Source.md) for more information. -- Select the right Pump in ConfigBuilder (select Virtual Pump if you are using a pump model with no AAPS driver for looping) to ensure your pump status can communicate with AAPS. -- If using DanaR pump then ensure you have followed [DanaR Insulin Pump](../Configuration/DanaR-Insulin-Pump.md) instructions to ensure the link between pump and AAPS. -- You need to establish a data repository/reporting platform to complete this objective. That can be accomplished with either Nightscout or Tidepool (or both). Follow instructions at the [Nightscout](../Installing-AndroidAPS/Nightscout.md) or [Tidepool](../Installing-AndroidAPS/Tidepool.md) page for instructions. -- Note that URL in NSClient must be **WITHOUT /api/v1/** at the end - see [NSClient settings in Preferences](Preferences-nsclient). - -*You may need to wait for the next blood glucose reading to arrive before AAPS will recognise it.* - -## Objective 2: Learn how to control AAPS - -- Perform several actions in AAPS as described in this objective. - -- Click on the orange text "Not completed yet" to access the to-dos. - -- Links will be provided to guide you in case you are not familiar with a specific action yet. - - ```{image} ../images/Objective2_V2_5.png - :alt: Screenshot objective 2 - ``` - -(Objectives-objective-3-prove-your-knowledge)= - -## Objective 3: Prove your knowledge - -Objective 3 is a multiple choice test based on questions designed to test your theoretical knowledge of **AAPS**. - -Some users find Objective 3 to be the most difficult objective to complete. Please do read the AAPS documents in conjunction with the questions. If you are genuinely stuck after researching the **AAPS** documents, please search or ask for help on the Facebook or Discord group. These groups can provide friendly hints or redirect you to the relevant part of the **AAPS** documents. - -To proceed with Objective 3, click on the orange text “Not completed yet” to access the relevant question. Please read each question and select your answer(s). - - - -Within each question, a hyperlink to the **AAPS** documents will guide you to the relevant section of the document which you should read in order to locate the correct answer. - - -[Obj3_Screenshot 2023-12-05 223422](https://github.com/openaps/AndroidAPSdocs/assets/137224335/77347516-e24e-459d-98ab-acbb49a3d4e8)![image](https://github.com/openaps/AndroidAPSdocs/assets/137224335/ca756b8e-efbc-4427-b281-ac953ce16718) - - - -For each question, there may be more than one answer that is correct! If an incorrect answer is selected, the question will be time locked for a certain amount of time (60 minutes) before you can go back and answer the question. - - -After updating to a new version of **AAPS**, new questions may be added to cover a prevalent issue picked up by **AAPS** or alternatively to test your knowledge of a new feature of **AAPS** as released. - - -When **AAPS** is installed for the first time, you will have to complete Objective 3 entirely in order to move onto Objective 4. Each objective is required to be completed in sequential order. New features will gradually be unlocked as progress is made through the objectives. - -__What happens if new questions are added later to Objective 3?__ From time to time, new features are added to **AAPS** which may require a new question to be added to Objective 3. As a result, any new question added to Objective 3 will be marked as “incomplete” because **AAPS** will require you to action this. As each Objective is independent, you will not lose the existing functionality of **AAPS** providing the other objectives remain completed. - - -## Objective 4: Starting on an open loop - -- Select Open Loop either from Preferences, or by pressing and holding the Loop button in top left of the home screen. -- Work through the [Preferences](../Configuration/Preferences.md) to set up for you. -- Manually enact at least 20 of the temporary basal rate suggestions over a period of 7 days; input them to your pump and confirm in AAPS that you have accepted them. Ensure this data shows in AAPS and Nightscout. -- Enable [temp targets](../Usage/temptarget.md) if necessary. Χρησιμοποιήστε στόχους υπογλυκαιμίας για να αποφύγετε ότι το σύστημα θα διορθώσει πολύ έντονα λόγω αύξησης της γλυκόζης αίματος μετά από υπογλυκαιμία. - -### Reduce number of notifications - -- To reduce the Number of decisions to be made while in Open Loop set wide target range like 90 - 150 mg/dl or 5,0 - 8,5 mmol/l. - -- You might even want to wider upper limit (or disable Open Loop) at night. - -- In Preferences you can set a minimum percentage for suggestion of basal rate change. - - ```{image} ../images/OpenLoop_MinimalRequestChange2.png - :alt: Open Loop minimal request change - ``` - -- Also, you do not need to act every 5 minutes on all suggestions... - -## Objective 5: Understanding your open loop, including its temp basal recommendations - -- Start to understand the thinking behind the temp basal recommendations by looking at the [determine basal logic](https://openaps.readthedocs.io/en/latest/docs/While%20You%20Wait%20For%20Gear/Understand-determine-basal.html) and both the [forecast line in AAPS homescreen](Screenshots-prediction-lines)/Nightscout and the summary of outputs from the calculations in your OpenAPS tab. - -Θα θελήσετε να ορίσετε το στόχο σας υψηλότερο από το συνηθισμένο έως ότου είστε σίγουροι για τους υπολογισμούς και τις ρυθμίσεις. System allows - -- a low target to be a minimum of 4 mmol (72 mg/dl) or maximum of 10 mmol (180 mg/dl) -- a high target to be a minimum of 5 mmol (90 mg/dl) and maximum of 15 mmol (225 mg/dl) -- a temporary target as a single value can be anywhere in the range of 4 mmol to 15 mmol (72 mg/dl to 225 mg/dl) - -Ο στόχος είναι η τιμή στην οποία βασίζονται οι υπολογισμοί και όχι η ίδια με εκείνη που στοχεύετε να διατηρείτε τις τιμές γλυκόζης στο αίμα σας μέσα. If your target is very wide (say, 3 or more mmol \[50 mg/dl or more\] wide), you will often find little AAPS action. This is because blood glucose is eventually predicted to be somewhere in that wide range and therefore not many fluctuating temporary basal rates are suggested. - -You may want to experiment with adjusting your targets to be a closer together range (say, 1 or less mmol \[20 mg/dl or less\] wide) and observe how the behavior of your system changes as a result. - -You can view a wider range (green lines) on the graph for the values you aim to keep your blood glucose within by entering different values in [Preferences](../Configuration/Preferences.md) > Range for Visualisation. - -```{image} ../images/sign_stop.png -:alt: Stop sign -``` - -### Σταματήστε εδώ αν είστε σε ανοιχτό κύκλωμα με μια εικονική αντλία - μην κάνετε κλικ στην επιλογή Επαλήθευση στο τέλος αυτού του στόχου. - -```{image} ../images/blank.png -:alt: blank -``` - -(Objectives-objective-6-starting-to-close-the-loop-with-low-glucose-suspend)= -## Objective 6: Starting to close the loop with Low Glucose Suspend - -```{image} ../images/sign_warning.png -:alt: Warning sign -``` - -### Closed loop will not correct high BG values in objective 6 as it is limited to low glucose suspend. High BG values have to be corrected manually by you! - -- Prerequisite: You need a good profile (basal, ISF, IC) already working in AAPS to start with Loop in Low Glucose Suspend mode. Otherwise you can run in a hypo which you have to manually correct. This will help you a lot to avoid having to treat a low glucose over a period of 5 days. **If you are still having frequent or severe low glucose episodes then consider refining your DIA, basal, ISF and carb ratios and do NOT start objective 6 at this time.** -- You don't have to change your settings now. During objective 6, the maxIOB setting is internally set to zero automatically. **This override will be reversed when moving to objective 7.** -- The system will override your maxIOB settings to zero, which means if blood glucose is dropping it can reduce basal for you. If blood glucose is rising then it will only increase basal if the basal IOB is negative from a previous Low Glucose Suspend. Otherwise basal rates will remain the same as your selected profile. **That means that you have to manually handle high values with insulin corrections.** -- If your basal IOB is negative (see screenshot below) a TBR > 100% can be issued also in objective 6. - -```{image} ../images/Objective6_negIOB.png -:alt: Example negative IOB -``` - -- Set your target range slightly higher than you usually aim for, just to be safe and have a bit more scurity buffer. -- Enable 'Low Glucose Suspend' mode either by by pressing and holding the Loop icon at the top right corner of the home screen and selecting the Loop - LGS mode icon. -- Watch how temporary basals are active by viewing the blue basal text on the homescreen or the blue basal render on the homescreen graph. -- You may temporarily experience spikes following treated hypos without the ability to increase basal on the rebound. - -(Objectives-objective-7-tuning-the-closed-loop-raising-max-iob-above-0-and-gradually-lowering-bg-targets)= -## Objective 7: Tuning the closed loop, raising maxIOB above 0 and gradually lowering BG targets - -- Select 'Closed Loop' either from [Preferences](../Configuration/Preferences.md) or by pressing and holding the Loop icon at the top right corner of the home screen, over a period of 1 day. - -- Raise your 'Maximum total IOB OpenAPS can’t go over' (in OpenAPS called 'max-iob') above 0. The default recommendation is "average mealbolus + 3x max daily basal" (for the SMB algorithm) or "3x max daily basal" (for the older AMA algorithm) but you should slowly work up to this until you know your settings work for you (max daily basal = the maximum hourly value in any time segment of the day). - - Αυτή η σύσταση πρέπει να θεωρηθεί ως σημείο εκκίνησης. If you set to the 3x and you are seeing moves that push you too hard and fast then lower that number. If you are very resistant, raise it very little at a time. - - ```{image} ../images/MaxDailyBasal2.png - :alt: max daily basal - ``` - -- Once confident on how much IOB suits your looping patterns, then reduce your targets to your desired level. - -(Objectives-objective-8-adjust-basals-and-ratios-if-needed-and-then-enable-autosens)= -## Objective 8: Adjust basals and ratios if needed, and then enable autosens - -- You can use [autotune](https://openaps.readthedocs.io/en/latest/docs/Customize-Iterate/autotune.html) as a one off to check your basals remain accurate or do a traditional basal test. -- Enable [autosens](../Usage/Open-APS-features.md) over a period of 7 days and watch the white line on the homescreen graph show how your sensitivity to insulin may be rising or falling as a result of exercise or hormones etc. and keep an eye in the OpenAPS report tab how AAPS is adjusting the basals and/or targets accordingly. - -*Don’t forget to record your looping in* [this form](https://bit.ly/nowlooping) *logging AAPS as your type of DIY loop software, if you have not already done so.* - -(Objectives-objective-9-enabling-additional-oref1-features-for-daytime-use-such-as-super-micro-bolus-smb)= -## Objective 9: Enabling additional oref1 features for daytime use, such as super micro bolus (SMB) - -- You must read the [SMB chapter in this wiki](Open-APS-features-super-micro-bolus-smb) and [chapter oref1 in openAPSdocs](https://openaps.readthedocs.io/en/latest/docs/Customize-Iterate/oref1.html) to understand how SMB works, especially what's the idea behind zero-temping. -- Then you ought to [rise maxIOB](Open-APS-features-maximum-total-iob-openaps-cant-go-over-openaps-max-iob) to get SMBs working fine. η μέγιστη IOB περιλαμβάνει τώρα όλα τα IOB, όχι μόνο βασικά. That is, if given a bolus of 8 U for a meal and maxIOB is 7 U, no SMBs will be delivered until IOB drops below 7 U. A good start is maxIOB = average mealbolus + 3x max daily basal (max daily basal = the maximum hourly value in any time segment of the day - see [objective 7](Objectives-objective-7-tuning-the-closed-loop-raising-max-iob-above-0-and-gradually-lowering-bg-targets) for an illustration) -- min_5m_carbimpact default in absorption settings has changed from 3 to 8 going from AMA to SMB. If you are upgrading from AMA to SMB, you have to change it manually. - -(Objectives-objective-10-automation)= -## Objective 10: Automation - -- You have to start objective 10 to be able to use [Automation](../Usage/Automation.md). -- Make sure you have completed all objectives including exam [Objectives-objective-3-prove-your-knowledge](Objectives#objective-3-prove-your-knowledge). -- Completing previous objectives will not effect other objectives you have already finished. You will keep all finished objectives! - -(Objectives-objective-11-DynamicISF)= -## Objective 11: Additional Features such as DynamicISF - -- You have to start objective 11 to be able to use [DynamicISF](../Usage/Open-APS-features.md) - -(Objectives-go-back-in-objectives)= -## Go back in objectives - -If you want to go back in objectives for whatever reason you can do so by clicking at "clear finished". - -```{image} ../images/Objective_ClearFinished.png -:alt: Go back in objectives -``` - -## Objectives in Android APS before version 3.0 - -One objective was removed when Android APS 3.0 was released. Users of Android APS version 2.8.2.1 who are on older Android software (i.e. earlier than version 9) will be using an older set of objectives which can be found [here](../Usage/Objectives_old.md). diff --git a/docs/CROWDIN/el/Usage/Objectives_old.md b/docs/CROWDIN/el/Usage/Objectives_old.md deleted file mode 100644 index 901e0eb7f58b..000000000000 --- a/docs/CROWDIN/el/Usage/Objectives_old.md +++ /dev/null @@ -1,152 +0,0 @@ -# Objectives as of Android APS 2.8.2.1 - -This is not the latest version of the Android APS Objectives. This page details the Objectives that were in place prior to version 3.0. Anyone using an older version of Android (i.e. prior to Android 9) and Android APS version 2.8.2.1 should refer to this page. - -Please see [this page](../Usage/Objectives.md) for the current set of Objectives. - -Το AndroidAPS διαθέτει μια σειρά στόχων που πρέπει να ολοκληρωθούν για να σας καθοδηγήσουν στα χαρακτηριστικά και τις ρυθμίσεις του ασφαλούς κυκλώματος. Εξασφαλίζουν ότι έχετε ρυθμίσει σωστά όλες τις λεπτομέριες στις παραπάνω ενότητες και ότι καταλαβαίνετε τι κάνει το σύστημά και γιατί μπορείτε να το εμπιστευτείτε. - -If you are **upgrading phones** then you can [export your settings](../Usage/ExportImportSettings.md) to keep your progress through the objectives. Not only will your progress through the objectives be saved, but also your safety settings such as max bolus etc. If you do not export and import your settings then you will need to start the objectives from the beginning again. It is a good idea to [backup your settings](../Usage/ExportImportSettings.html) frequently just in case. - -If you want to go back in objectives see [explanation below](../Usage/Objectives.md#go-back-in-objectives). - -## Στόχος 1: Δημιουργία οπτικοποίησης και παρακολούθησης, ανάλυση βασικού δεδομένων και αναλογιών - -- Select the right blood glucose source for your setup. See [BG Source](../Configuration/BG-Source.md) for more information. -- Select the right Pump in ConfigBuilder (select Virtual Pump if you are using a pump model with no AndroidAPS driver for looping) to ensure your pump status can communicate with AndroidAPS. -- If using DanaR pump then ensure you have followed [DanaR Insulin Pump](../Configuration/DanaR-Insulin-Pump.md) instructions to ensure the link between pump and AndroidAPS. -- Follow instructions in [Nightscout](../Installing-AndroidAPS/Nightscout.md) page to ensure Nightscout can receive and display this data. -- Note that URL in NSClient must be **WITHOUT /api/v1/** at the end - see [NSClient settings in Preferences](../Configuration/Preferences.md#nsclient). - -*You may need to wait for the next blood glucose reading to arrive before AndroidAPS will recognise it.* - -## Objective 2: Learn how to control AndroidAPS - -- Perform several actions in AndroidAPS as described in this objective. - -- Click on the orange text "Not completed yet" to access the to-dos. - -- Links will be provided to guide you in case you are not familiar with a specific action yet. - - ![Screenshot objective 2](../images/Objective2_V2_5.png) - -## Objective 3: Prove your knowledge - -- Pass a multiple-choice exam testing your AndroidAPS knowledge. - -- Click on the orange text "Not completed yet" to access the page with the question and answering options. - - ![Screenshot objective 3](../images/Objective3_V2_5.png) - -- Links will be provided to guide you in case you are unsure about the correct answers yet. - -- The questions for objective 3 have been completely rewritten by native speakers as of AAPS 2.8. The new ones cover the same basic topics plus a few new ones. - -- These new questions will lead to some not answered questions even though you have successfully completed objective 3 in previous versions. - -- Unanswered questions will affect you only if you start a new objective. In other words: If you have already completed all objectives you can wait and answer the new questions later without loosing AAPS functions. - -## Objective 4: Starting on an open loop - -- Select Open Loop either from Preferences, or by pressing and holding the Loop button in top left of the home screen. -- Work through the [Preferences](../Configuration/Preferences.md) to set up for you. -- Manually enact at least 20 of the temporary basal rate suggestions over a period of 7 days; input them to your pump and confirm in AndroidAPS that you have accepted them. Βεβαιωθείτε ότι τα δεδομένα αυτά εμφανίζονται σε AndroidAPS και Nightscout. -- Enable [temp targets](../Usage/temptarget.md) if necessary. Χρησιμοποιήστε στόχους υπογλυκαιμίας για να αποφύγετε ότι το σύστημα θα διορθώσει πολύ έντονα λόγω αύξησης της γλυκόζης αίματος μετά από υπογλυκαιμία. - -### Reduce number of notifications - -- To reduce the Number of decisions to be made while in Open Loop set wide target range like 90 - 150 mg/dl or 5,0 - 8,5 mmol/l. - -- You might even want to wider upper limit (or disable Open Loop) at night. - -- In Preferences you can set a minimum percentage for suggestion of basal rate change. - - ![Open Loop minimal request change](../images/OpenLoop_MinimalRequestChange2.png) - -- Also, you do not need to act every 5 minutes on all suggestions... - -## Objective 5: Understanding your open loop, including its temp basal recommendations - -- Start to understand the thinking behind the temp basal recommendations by looking at the [determine basal logic](https://openaps.readthedocs.io/en/latest/docs/While%20You%20Wait%20For%20Gear/Understand-determine-basal.html) and both the [forecast line in AndroidAPS homescreen](../Getting-Started/Screenshots.md#prediction-lines)/Nightscout and the summary of outputs from the calculations in your OpenAPS tab. - -Θα θελήσετε να ορίσετε το στόχο σας υψηλότερο από το συνηθισμένο έως ότου είστε σίγουροι για τους υπολογισμούς και τις ρυθμίσεις. System allows - -- a low target to be a minimum of 4 mmol (72 mg/dl) or maximum of 10 mmol (180 mg/dl) -- a high target to be a minimum of 5 mmol (90 mg/dl) and maximum of 15 mmol (225 mg/dl) -- a temporary target as a single value can be anywhere in the range of 4 mmol to 15 mmol (72 mg/dl to 225 mg/dl) - -Ο στόχος είναι η τιμή στην οποία βασίζονται οι υπολογισμοί και όχι η ίδια με εκείνη που στοχεύετε να διατηρείτε τις τιμές γλυκόζης στο αίμα σας μέσα. If your target is very wide (say, 3 or more mmol \[50 mg/dl or more\] wide), you will often find little AAPS action. This is because blood glucose is eventually predicted to be somewhere in that wide range and therefore not many fluctuating temporary basal rates are suggested. - -You may want to experiment with adjusting your targets to be a closer together range (say, 1 or less mmol \[20 mg/dl or less\] wide) and observe how the behavior of your system changes as a result. - -You can view a wider range (green lines) on the graph for the values you aim to keep your blood glucose within by entering different values in [Preferences](../Configuration/Preferences.md) > Range for Visualisation. - -![Stop sign](../images/sign_stop.png) - -### Σταματήστε εδώ αν είστε σε ανοιχτό κύκλωμα με μια εικονική αντλία - μην κάνετε κλικ στην επιλογή Επαλήθευση στο τέλος αυτού του στόχου. - -![blank](../images/blank.png) - -## Objective 6: Starting to close the loop with Low Glucose Suspend - -![Warning sign](../images/sign_warning.png) - -### Closed loop will not correct high bg values in objective 6 as it is limited to low glucose suspend. Οι υψηλές τιμές BG πρέπει να διορθωθούν χειροκίνητα από εσάς! - -- Select Closed Loop either from [Preferences](../Configuration/Preferences.md) or by pressing and holding the Open Loop button in the top left of the home screen. - -- Set your target range slightly higher than you usually aim for, just to be safe. - -- Watch how temporary basals are active by viewing the blue basal text on the homescreen or the blue basal render on the homescreen graph. - -- Ensure your settings have supported AndroidAPS to avoid having to treat a low glucose over a period of 5 days. Εάν εξακολουθείτε να εμφανίζετε συχνά ή σοβαρά επεισόδια χαμηλής γλυκόζης, εξετάστε το ενδεχόμενο αλλαγής των αναλογιών DIA, βασικών, ISF και υδατανθράκων. - -- You don't have to change your settings. During objective 6 maxIOB setting is internally set to zero automatically. This override will be reversed when moving to objective 7. - -- The system will override your maxIOB settings to zero, which means if blood glucose is dropping it can reduce basal for you, but if blood glucose is rising then it will only increase basal if the basal IOB is negative (from a previous Low Glucose Suspend), otherwise basal rates will remain the same as your selected profile. - - ![Example negative IOB](../images/Objective6_negIOB.png) - -- If your basal IOB is negative (see screenshot above) a TBR > 100% can be issued also in objective 6. - -- You may temporarily experience spikes following treated hypos without the ability to increase basal on the rebound. - -## Objective 7: Tuning the closed loop, raising max IOB above 0 and gradually lowering BG targets - -- Raise your 'Maximum total IOB OpenAPS can’t go over' (in OpenAPS called 'max-iob') above 0 over a period of 1 day, the default recommendation is "average mealbolus + 3x max daily basal"(for SMB algorithm) or "3x max daily basal" (for older AMA algorithm) but you should slowly work up to this until you know your settings work for you (max daily basal = the maximum hourly value in any time segment of the day). - - Αυτή η σύσταση πρέπει να θεωρηθεί ως σημείο εκκίνησης. Εάν ρυθμίσετε στο 3x και βλέπετε κινήσεις που σας ωθούν έντονα και γρήγορα τότε μειώστε τον αριθμό. Εάν είστε πολύ ανθεκτικοί, αυξήστε το πολύ λίγο τη φορά. - - ![max daily basal](../images/MaxDailyBasal2.png) - -- Once confident on how much IOB suits your looping patterns then reduce your targets to your desired level. - -## Objective 8: Adjust basals and ratios if needed, and then enable autosens - -- You can use [autotune](https://openaps.readthedocs.io/en/latest/docs/Customize-Iterate/autotune.html) as a one off to check your basals remain accurate or do a traditional basal test. -- Enable [autosens](../Usage/Open-APS-features.md) over a period of 7 days and watch the white line on the homescreen graph show how your sensitivity to insulin may be rising or falling as a result of exercise or hormones etc. and keep an eye in the OpenAPS report tab how AndroidAPS is adjusting the basals and/or targets accordingly. - -*Don’t forget to record your looping in* [this form](https://bit.ly/nowlooping) *logging AndroidAPS as your type of DIY loop software, if you have not already done so.* - -## Objective 9: Try additional features for daytime use and gain confidence in your closed loop system - -- Before AAPS version 2.7 meal assist (MA) was the basic algorithm for AAPS and completing objective 8 was necessary to activate [advanced meal assist (AMA)](../Usage/Open-APS-features.md#advanced-meal-assist-ama). -- As [advanced meal assist (AMA)](../Usage/Open-APS-features.md#advanced-meal-assist-ama) is the standard algorithm from AAPS version 2.7 onwards use the following 28 days to try features you haven't used yet and get more confident with you closed loop system. - -## Objective 10: Enabling additional oref1 features for daytime use, such as super micro bolus (SMB) - -- You must read the [SMB chapter in this wiki](../Usage/Open-APS-features.md#super-micro-bolus-smb) and [chapter oref1 in openAPSdocs](https://openaps.readthedocs.io/en/latest/docs/Customize-Iterate/oref1.html) to understand how SMB works, especially what's the idea behind zero-temping. -- Then you ought to [rise maxIOB](../Usage/Open-APS-features.md#maximum-total-iob-openaps-cant-go-over-openaps-max-iob) to get SMBs working fine. η μέγιστη IOB περιλαμβάνει τώρα όλα τα IOB, όχι μόνο βασικά. That is, if given a bolus of 8 U for a meal and maxIOB is 7 U, no SMBs will be delivered until IOB drops below 7 U. A good start is maxIOB = average mealbolus + 3x max daily basal (max daily basal = the maximum hourly value in any time segment of the day - see [objective 7](../Usage/Objectives#objective-7-tuning-the-closed-loop-raising-max-iob-above-0-and-gradually-lowering-bg-targets) for an illustration) -- min_5m_carbimpact default in absorption settings has changed from 3 to 8 going from AMA to SMB. If you are upgrading from AMA to SMB, you have to change it manually. - -## Objective 11: Automation - -- You have to start objective 11 to be able to use [Automation](../Usage/Automation.md). -- Make sure you have completed all objectives including exam [../Usage/Objectives.md#objective-3-prove-your-knowledge](../Usage/Objectives#objective-3-prove-your-knowledge). -- Completing previous objectives will not effect other objectives you have already finished. You will keep all finished objectives! - -## Go back in objectives - -If you want to go back in objectives for whatever reason you can do so by clicking at "clear finished". - -![Go back in objectives](../images/Objective_ClearFinished.png) diff --git a/docs/CROWDIN/el/Usage/Smoothing-Blood-Glucose-Data-in-xDrip.md b/docs/CROWDIN/el/Usage/Smoothing-Blood-Glucose-Data-in-xDrip.md deleted file mode 100644 index 9c449859df53..000000000000 --- a/docs/CROWDIN/el/Usage/Smoothing-Blood-Glucose-Data-in-xDrip.md +++ /dev/null @@ -1,33 +0,0 @@ -(Smoothing-Blood-Glucose-Data-in-xDrip-smoothing-blood-glucose-data)= - -# Εξομάλυνση των δεδομένων γλυκόζης στο αίμα - -If BG data is jumpy/noisy, AAPS may dose insulin incorrectly resulting in high or low BG. For this reason it’s important to disable the loop until the problem is resolved. Depending on your CGM such issues may be due to the CGM’s configuration or sensor problems/site issues. You may need to replace your CGM sensor to resolve this. - -Some CGM systems have internal algorithms to detect the noise level in the readings and AAPS can use this information to avoid giving SMBs if the BG data is too unreliable. However, some CGMs do not transmit this data and for these BG sources 'Enable SMB always' and 'Enable SMB after carbs' are disabled for safety reasons. - -## Dexcom sensors - -### Build Your Own Dexcom App - -When using [BYODA](DexcomG6-if-using-g6-with-build-your-own-dexcom-app) your BG data is smooth and consistent. Furthermore you can take advantage of Dexcom back-smoothing. There are no restrictions in using SMBs, because the noise-level data is shared with AAPS. - -### xDrip+ with Dexcom G6 or Dexcom ONE - -Noise-level data and smooth BG readings are only shared with AAPS if you use xDrip+ [native mode](https://navid200.github.io/xDrip/docs/Native-Algorithm). Using native mode, there are no restrictions in using SMBs. - -### Dexcom G6 or Dexcom ONE with xDrip+ Companion Mode - -The noise-level data is not shared with AAPS using this method. Therefore 'Enable SMB always' and 'Enable SMB after carbs' are disabled. - -## Freestyle Libre sensors - -### xDrip+ with FreeStyle Libre - -None of the FreeStyle Libre systems (FSL1, FSL2, or FSL3) broadcast any information about the level of noise detected in the readings, and therefore 'Enable SMB always' and 'Enable SMB after carbs' are disabled for all setups using the FreeStyle Libre. - -In addition, many people have reported the FreeStyle Libre often produces noisy data. In xDrip+ there are a few options to help with this: - -**Smooth Sensor Noise.** In xDrip+ Settings > xDrip+ Display Settings ensure that Smooth Sensor Noise is turned on. This attempts to apply smoothing to noisy data. - -**Smooth Sensor Noise (Ultrasensitive).** If you are still seeing noisy data in xDrip+ you can apply more aggressive smoothing using the Smooth Sensor Noise (Ultrasensitive) setting. This will attempt to apply smoothing even on very low levels of detected noise. To do this, first enable [engineering mode](Enabling-Engineering-Mode-in-xDrip.md) in xDrip+. Then navigate to Settings > xDrip+ Display Settings and turn on Smooth Sensor Noise (Ultrasensitive). \ No newline at end of file diff --git a/docs/CROWDIN/el/Usage/autotune_b.md b/docs/CROWDIN/el/Usage/autotune_b.md deleted file mode 100644 index 411565b5dc8e..000000000000 --- a/docs/CROWDIN/el/Usage/autotune_b.md +++ /dev/null @@ -1,186 +0,0 @@ -# How to use Autotune plugin - -Documentation about Autotune algorythm can be found in [OpenAPS documentation](https://openaps.readthedocs.io/en/latest/docs/Customize-Iterate/autotune.html). - -Autotune plugin is an implementation of OpenAPS autotune algorythm within AAPS. - -**Currently Autotune Plugin is only available in dev branch with Engineering mode.** - -## Autotune user interface - -![Autotune default screen](../images/Autotune/Autotune_1b.png) - -- You can select in the Profile dropdown menu the input profile you want to tune (by default your current active profile is selected) - - Note: each time you select a new profile, previous results will be removed and Tune days parameter will be set to default value -- Then Tune days is to select the number of days used in calculation to tune your profile. The minimum value is 1 day and the maximum value 30 days. This number should not be too small to get correct iterative and smooth results (above 7 days for each calculation) - - Note: each time you change Tune days parameter, previous results will be removed -- Last Run il a link that recover your latest valid calculation. If you didn't launch Autotune on current day, or if previous results was removed with a modification of calculation parameter above, then you can recover parameters and results of the latest successfull run. -- Warning show you for example some information about selected profile (if you have several IC values or several ISF values) - - Note: Autotune calculation works with only a single IC and a single ISF value. There is currently no existing Autotune algorythm to tune a circadian IC or circadian ISF. If your input profile has several values, you can see in warning section the average value taken into account to tune your profile. -- Check Input Profile button open the Profile Viewer to allow you a quick verification of your profile (Units, DAI, IC, ISF, basal and target) - - Note: Autotune will only tune your IC (single value), ISF (single value) and basal (with circadian variation). Units, DAI and target will remain unchanged in output profile. - -- "Run Autotune" will launch Autotune calculation with selected profile and the number of Tune days - - Note: Autotune calculation can take a long time. Once launched, you can switch to another view (home, ...) and come back later in Autotune plugin to see results - -![Autotune Run start](../images/Autotune/Autotune_2b.png) - -- Then during the run you will see intermediate results below - - - Note: During run, settings are locked, so you cannot change anymore selected input profile or the number of day. You will have to wait the end of current calculation if you want to launch another run with other parameters. - - ![Autotune during run](../images/Autotune/Autotune_3b.png) - -- When Autotune calculation is finished, you will see the result (Tuned profile) and four buttons below. - -![Autotune Result](../images/Autotune/Autotune_4b.png) - -- It's important to always compare input profile (column "Profile"), output profile (column "Tuned") and the percentage of variation for each value (Column "%"). - -- For basal rates, you also have the number of "missing days". You have missing days when Autotune don't have enough data categorized as "Basal" to tune basal rate for this period (for example after each meal when you have carbs absorption). This number should be as low as possible especially when basal is important (for example during the night or at the end of the afternoon) - -- The "Compare profiles" button open the profile comparator view. Input profile is in blue, and output profile (named "Tuned") is in red. - - - Note: in the example below input profile has circadian variation for IC and ISF, but output calculated profile has a single value. If it's important for you to get a circadian output profile see [Circadian IC or ISF profile](#circadian-ic-or-isf-profile) below. - - ![Autotune Compare profiles](../images/Autotune/Autotune_5.png) - -- If you trust results (low percentage of variation between input profile and output profile), you can click on "Activate profile" button and then click on OK to validated. - - - Activate Tuned profile will automatically create a new profile "Tuned" in your Local profile plugin. - - If you already have a profile named "Tuned" in your local profile plugin, then this profile will be updated with calculated Autotune profile before the activation - - ![Autotune Activate profile](../images/Autotune/Autotune_6.png) - -- If you think Tuned profile must be adjusted (for example if you think some variation are too important), then you can click on "Copy to local profile" button - - - A new profile with the prefix "Tuned" and the date and time of the run will be created in local profile plugin - -![Autotune Copy to local profile](../images/Autotune/Autotune_7.png) - -- You can then select local profile to edit the Tuned profile (it will be selected by default when you open Local profile plugin) - - - the values in local profile will but rounded in the user interface to your pump capabilities - - ![Autotune local profile update](../images/Autotune/Autotune_8.png) - -- If you want to replace your input profile with Autotune result, click on "Update input profile" button and validate the Popup with OK - - - Note: if you click on "Activate profile" after "Update input profile", then you will activate your updated profile and not the default "Tuned" profile? - - ![Autotune Update input profile](../images/Autotune/Autotune_9.png) - -- If you have updated your input profile, then the "Update input profile" button is replaced by "Revert input profile" button (see screenshot below). You can that way immediatly see if your current input profile in Local profile plugin already include the result of last run or not. You also have the possibility to recover you input profile without autotune result with this button - - ![Autotune Update input profile](../images/Autotune/Autotune_10.png) - - - -## Autotune settings - -### Autotune plugin settings - -![Autotune default screen](../images/Autotune/Autotune_11.png) - -- Automation Switch Profile (default Off): see [Run Autotune with an automation rule](#run-autotune-with-an-automation-rule) below. If you change this setting to On, the input profile will automatically be updated by the Tuned profile, and it will be activated. - - **Be Carefull, you must trust and verified during several following days that after an update and activation of Tuned profile without modification, it improves your loop** - -- Categorize UAM as basal (default On): This setting is for the users using AndroidAPS without any carbs entered (Full UAM). It will prevent (when Off) to categorize UAM as basal. - - Note: if you have at least one hour of Carbs absorption detected during one day, then all data categorized as "UAM" will be categorized as basal, whatever this setting (On or Off) -- Number of days of data (default 5): You can define default value with this setting. Each time your select a new profile in Autotune plugin, Tune days parameter will be replaced by this default value -- Apply average result in circadian IC/ISF (default Off): see [Circadian IC or ISF profile](#circadian-ic-or-isf-profile) below. - -### Αλλες ρυθμισεις - -- Autotune also uses Max autosens ratio and Min autotsens ratio to limit variation. You can see and adjust these values in Config Builder > Sensitivity detection plugin > Settings > Advanced Settings - - ![Autotune default screen](../images/Autotune/Autotune_12.png) - - - -## Advanced feature - -### Circadian IC or ISF profile - -- If you have important variation of IC and/or you ISF in your profile, and you fully trust in your circadian time and variation, then you can set "Apply average result in circadiant IC/ISF" - - - Note that Autotune calculation will always be done with a single value, and circadian variation will not be tuned by Autotune. This setting only apply average variation calculated for IC and/or ISF on your circadian values - -- See on screenshot below Tuned profile with Apply average variation Off (on the left) and On (on the right) - - ![Autotune default screen](../images/Autotune/Autotune_13.png) - - - -### Tune specific days of the week - -- If you click on the checkbox with the eye on the right of "Rune days" parameter, you will see the day selection. You can specify which day of the week should be included in Autotune calculation (in screenshot below you can see an example for "working days" with Saturday and Sunday removed from autotune calculation) - - If the number of day included in Autotune calculation is lower than the number of Tune days, then you will see how many days will be included on the right of Tune days selector (10 days in the example below) - - This setting gives good results only if the number of remaining days is not to small (for example if you Tune a specific profile for week end days with only Sunday and Saturday selected, you should select a minimum of 21 or 28 Tune days to have 6 or 8 days included in Autotune calculation) - -![Autotune default screen](../images/Autotune/Autotune_14b.png) - -- During Autotune calculation, you can see the progress of the calculations ("Partial result day 3 / 10 tuned" on example below) - - ![Autotune default screen](../images/Autotune/Autotune_15b.png) - -## Run Autotune with an automation rule - -First step is to define correct trigger for an automation rule with Autotune: - -Note: for more information on how to set an automation rule, see [here](./Automation.rst). - -- You should select Recurring time trigger: only run Autotune once per day, and autotune is designed to be runned daily (each new run you shift one day later and quickly profile modification should be tiny) - - ![Autotune default screen](../images/Autotune/Autotune_16.png) - -- It's better at the beginning to run Autotune during the day to be able to check results. If you want to run Autotune during the night, you have to select in the trigger 4AM or later to include current day in next Autotune Calculation. - - ![Autotune default screen](../images/Autotune/Autotune_17.png) - -- Then you can select "Run Autotune" Action in the list - - ![Autotune default screen](../images/Autotune/Autotune_18.png) - -- You can then select Autotune Action to adjust parameters for your run. Default parameters are "Active Profile", default Tune days value defined in Autotune Plugin preferences, and All days are selected. - - ![Autotune default screen](../images/Autotune/Autotune_19b.png) - -- After a few days, if you fully trust Autotune results and percentage of modification is low, you can modify [Autotune settings](#autotune-plugin-settings) "Automation Switch Profile" to enabled to automatically update and activate profile tuned after calculation. - -Note: if you want to automatically tune profiles for specific days of the week (for example a profile for "Weekend days" and another one for "Working days"), then create one rule for each profile, select the same days in Trigger and in Autotune Action, Tune days must be high enough to be sure tuning will be done with at least 6 or 8 days, and don't forget to select time after 4AM in trigger... - -- See below an example of rule to tune "my profile" on all "Working days" with 14 Tune days selected (so only 10 days included in autotune calculation). - -![Autotune default screen](../images/Autotune/Autotune_20b.png) - - - -## Tips and trick's - -Autotune works with information existing in your database, so if you just installed AAPS on a new phone, you will have to wait several days before being able to launch Autotune with enough days to get relevant results; - -Autotune is just an help, it's important to regularly check if you agree with calculated profile. If you have any doubt, change Autotune settings (for example the number of days) or copy results in local profile and adjust profile before using it. - -Always use Autotune several days manually to check results before applyling them. And it's only when you fully trust Autotune results, and when variation becomes tiny between previous profile and calculated profile than you start to use Automation (Never before) - -- Autotune can work very well for some users and not for others, so **If you don't trust Autotune result, don't use it** - -It's also important to analyse Autotune results to understand (or try to understand) why Autotune propose these modifications - -- you can have a whole increase or decrease of the strength of your profile (for example increase of total basal associated to decrease of ISF and IC values). it could be associated to several following days with autosens correction above 100% (more agressivity required) or below 100% (you are more sensitive) -- Sometimes Autotune propose a different balance between basal rates and IC/ISF (for ex lower basal and more aggressive IC/ISF) - -We advise to not use Autotune in the following cases: - -- You don't enter all your carbs - - If you don't enter carbs correction for an hypoglycemia, Autotune will see an unexcepted increase of your BG value and will increase your basal rates the ' hours earlier, it could be the opposite of what you need to avoid hypo, especially if it's in the middle of the night. That's why it's important to enter all carabs especially correction for hypo. -- You have a lot of period with UAM detected during the day. - - Do you have entered all your carbs and correctly estimated your Carbs ? - - All UAM periods (except if you enter no carbs during a day and categorized UAM as basal is disabled), all your UAM periods will be categorized as basal, this can increase a lot your basal (much more than necessary) - -- Your carbs absorption is very slow: if most of your carbs absorption are calculated with min_5m_carbimpact parameter (you can see these periods with a little orange dot in the top of COB curve), the calculation of COB could be wrong and leads to wrong results. - - We you practice sport, you are generally more sensitive and your BG doesn't rise a lot, so during or after an exercice, it's usual to see some periods with slow carbs. But if you have too often unexpected slow carb absorption, then you may need a profile adjustment (higher value of IC) or a min_5m_carbimpact a bit to high. -- You have a "very bad days", for example stuck several hours in hyperglycemia with a huge amount of insulin to be able to go down within the range, or after a sensor change you got long periods of wrong BG values. -- If the percentage of modification is too important - - You can try to increase the number of days to get smoother results \ No newline at end of file diff --git a/docs/CROWDIN/el/Usage/making-sport-with-AAPS.md b/docs/CROWDIN/el/Usage/making-sport-with-AAPS.md deleted file mode 100644 index 79d2f1c38223..000000000000 --- a/docs/CROWDIN/el/Usage/making-sport-with-AAPS.md +++ /dev/null @@ -1,185 +0,0 @@ -# making sport with AAPS - -In this section we want to address the topic of sport with AAPS. - -The aim is to show you how AAPS can help you to continue doing your favorite sport more easily or even to start doing it. It is relatively common for new type 1 diabetics to ask whether exercise is still possible for them, even if the answer in the training courses is actually a clear yes. Exercise is not only good for healthy people, but also for type 1 diabetics and even moderate exercise can even help to stabilize the blood sugar curve overall. - -:::{admonition} consult with your diabetes team after reading - -::: - -The difficulty here is that the prerequisites that someone brings with them and the expectations of what sport means to them are very different. - -Since we can assume that experienced top athletes with T1D who use AAPS are unlikely to look it up here, we deliberately set the bar low for ourselves when writing and for you when reading and using it, so that as many people as possible can benefit from it. - -Since even sport as a category is far too imprecise, as the effects of endurance sports differ greatly from strength training, for example, we are trying to break it down by type of sport. - -To be concrete and give you something you can test yourself we arrange the explanaiton around a concrete example and explain to you they action, reactions and effects. - -:::{admonition} more examples wanted - -The focus should always be on how others can do sport and not on the top performance someone has achieved. - -It's really about the basics. Your experience, which you share here, can help others to pursue their beloved sport more quickly and successfully and is therefore important. -::: - -## Cycling - -:::{admonition} take a friend with you - at least on your first trials -:class: information -A gerneral very good idea can be to take a good friend with you on the first rides. -This is especially important if you are not experienced in T1D. -Always keep in mind please: arrival comes before speed! Safety for you and the others in road traffic is very, very important. -::: - -### Example - -Let's take about 60 minutes of cycling on a flat route with a moderate heart rate as an example. - -1. we take a flat route in order to have an even load for the first exercise. This is not about performance, but purely about learning how you should react to changes in blood glucose. -2. we take the heart rate as an indicator of the load, as it is easy to see whether you are under load or not. -3. we set ourselves the goal of doing a relaxed lap around the neighborhood and focus on staying within our target range during the lap. In my case, this would be 70 <= x <= 180 mg/dl. - -We **don't** take the speed, as this is heavily dependent on personal physical conditions as well as the bike and surface used. It is therefore not very meaningful. - -You should know from the diabetes training courses you have attended that during endurance sports cycling, the insulin active in the body works significantly better than during times without physical exertion. The insulin active in the body is referred to as insulin on board (IoB). It is our most important parameter when cycling with T1D. - -We try to keep the IoB as low as possible at the start and during exercise. IoB should be around 0 or even slightly negative. You can get it there by not eating 3-4 hours before exercise. In the beginning it can also be helpful to exercise in the morning before breakfast, as with the right profile you should always have around 0 for IoB in the morning. - -AAPS shows us the IoB value on the home screen on the left under the blood glucose value. - -![IoB](../images/cycling_20240104-174035.png) - -:::{admonition} ignoring the IoB rule increases the risk for roller coaster BG dramatically -:class: danger -If you ignore this rule, you can still go cycling, but it will be much more difficult to keep your blood sugar levels in balance, so it is better to save this for later tests after several successful simple tests. -::: - -As you should know from the diabetes training courses, you should reduce the basal rate during exercise. The factor is individual. I have found a value of 50% in tests to be suitable for me. - -In AAPS, you should therefore change your profile to 50% before exercise and keep it active until the end of exercise. Some people even do it a certain amount of time before, e.g. 1 hour. Unfortunately, the pre-run is also individual. We will come to the post-run later. - -You should use two carbohydrates during exercise. - -1. medium-fast carbohydrates for the insulin still in the body and -2. very fast carbohydrates to prevent slipping into a hypo. - -For medium-fast carbohydrates, I treat myself to cookies or a banana before exercise, for example. You can also use something else that is more suitable for you. -For very fast carbohydrates, I take 3 teaspoons of dissolved glucose per 100 ml of still water in a 500 ml water bottle on my bike. If I'm cycling longer distances, I take a larger bottle with me and, if necessary, packaged glucose to refill the bottle. I add a little lemon juice for flavor. You can also use something other than lemon juice for the taste. You shouldn't change anything about the dextrose, as dissolved dextrose raises blood sugar levels super quickly. If you only take it in sips, your blood sugar won't go super high either! You can also do this tip at home beforehand as a dry run and see how quickly the change shows up on the CGMS. - -Why do I place so much emphasis on fast carbohydrates? - -1. once you are in a slight hypo, you may get back into the normal range by drinking the dextrose solution. As a rule, however, the oscillation of the curve then begins, which leads to a rollercoaster ride of the blood sugar. You may even be able to keep this within your target range, but you must be constantly vigilant. Without a hypo it is simply the most stable. -2. if you even slip into a somewhat severe hypo (without the need for outside help, of course), you may even have to pause briefly to avoid getting stuck in the hypo. - With both hypos, there is a risk that you will be tempted to switch from drinking 2-3 sips at a time to larger quantities. Not too bad at first, until the oscillation sets in and pushes you into a hyper. You can correct this, but your blood sugar will most likely go on a rollercoaster ride. - -What else is helpful, but not absolutely necessary? -It is important to keep an eye on your blood sugar, as your blood sugar can change enormously (e.g. 30 - 50 mg/dl) within 15 minutes of riding and a little more IoB or a basal rate that is still too high. The best way to keep an eye on it is if it is visible on the handlebars or if it is also displayed on your watch. It is even possible to install an additional app on some Garmin GPS bike computers that displays the blood glucose from XDrip or Nightscout as a data field on the bike computer. The additional app was developed by Andreas May from the T1D community. It is available free of charge in the official connect IQ Store. Certainly an interesting option for riders interested in sports. - -[Link to Andreas May Data Field App on connect IQ store](https://apps.garmin.com/de-DE/apps/5a3e2cda-12f0-4afd-88ed-000e67a68d84) - -Here is a picture of my Garmin Edge 530 bike computer with map, blood sugar and heart rate. - -![Garmin Edge 530 with BG data field](../images/cycling_IMG_1087.jpeg) - -After you have eaten the medium fast carbohydrates (24 - 36 g I take) and the blood sugar is above 100 mg/dl but also below 160 mg/dl, I carry out the profile change to 50% and set the activity temp target. - -:::{admonition} disable SMBs during high temp targets if necessary -:class: danger -Attention: If you prefer not to receive SMBs during the sport, please disable the option "Enable SMB with hight temp targets" in the settings of SMB or DynIFS Plugin. -::: - -The following picture shows the start and end of the sport. The end was specified as the duration when the profile was changed at the start. - -The temporary profile change has the following effects - -1. for a period of 60 minutes -2. a reduction to 50% of the profile and -3. the target is raised by clicking on the Activity Target option, which may have the side effect of disabling the SMBs - see above. - -![profile switch with temp target](../images/cycling_20240104-174056.png) - -The second image shows that the start at IoB was started towards 0. - -![IoB around 0](../images/cycling_20240104-174111.png) - -If the blood sugar drops faster than 15 mg/dl in 5 minutes or if it is at 120 mg/dl and tends to fall, I drink 1-2 sips of dissolved glucose. Then I wait for the next value and proceed as described above. - -You can hardly see it here, but at the beginning I took 2 sips from the bottle several times when my blood sugar started to fall. When it stabilized, I didn't need any more glucose. - -Here is the picture that illustrates this. The chart is saved on the Garmin as a result of the activity. - -![BG chart Garmin](../images/cycling_20240104-174431.png) - -If you should suddenly break out upwards, i.e. above 180 mg/dl, you should consider whether you should make a correction bolus. Caution: Remember the factor and apply it to the correction, otherwise the correction will be too strong. - -If your blood sugar drops below 80 mg/dl, take a break and drink two sips until your blood sugar is back above 100 mg/dl. - -At the end of the ride, the profile change should be finished as the time is up. - -Since we only rode easy for 60 minutes, there shouldn't be a big muscle bulking effect continuing to pull carbohydrates from your blood sugar. However, if it felt strenuous to you, keep an eye on it. This is especially true if you then go straight to bed. It may be better to change your profile to e.g. 80% for sleep. You may come out of sleep slightly too high, but it's better than having a hypo at night. Over time, you will surely find out what happens to you. - -The following pictures show the low intensity of the sport. - -The elevation profile -![](../images/cycling_20240104-174314.png) - -Speed with average and maximum speed - -![](../images/cycling_20240104-174326.png) - -Note the pause at the level crossing, which is also reflected in the heart rate. - -The heart rate. -![](../images/cycling_20240104-174337.png) - -The training effect. -![](../images/cycling_20240104-174358.png) - -The time in the different heart rate training zones. -![](../images/cycling_20240104-174423.png) - -After succesfully mastering this simple example you could go for further targets by stretching - -1. the distance and time -2. the load during the ride -3. the elevation during the right which should make a big impact on the more necessary carbs or further reduction of IoB and percentage of profile switch. - -Based on my experiences I would not expect to come back 100% with time in range over the whole and every ride. - -### Tipps - -I already gave some tipps for during the ride above. - -Here are some further tipps what can go wrong and how you can act to prevent it or react to compensate it. - -#### sky rocket high after ride - -During the ride everything was fine but after siting down and relax the blood sugar go sky rocket high. - -**Possible reason:** This happens when you have drunk too much dissolved glucose. - -**Reaction:** Drink 500 ml water, go to the shower and then control again. Latest after 30 minutes think about giving a correction bolus but be careful when it is short for bed time. Therefore it can be very good to make the first try runs on weekend mornings. - -**Action:** Next time be a bit more cautious in drinking from the dissolved glucose. - -#### hypo during ride - -During the ride you are going into hypo and can't recover your blood sugar during cycling. - -**Possible reason:** Your body cannot absorb enough carbohydrates quickly enough during exercise. - -**Reaction:** Take a rest and corrrect your blood sugar with drinking dissolved glucose. Stay calm: arrival comes before speed. - -**Action:** Did you started with IoB near 0? Have you eaten a small amount of middle fast carbs? Can you increase this or are the not fast enough for your body? Is it possible to prevent going into hypo by reducing the factor for the profile switch? Have you disbaled SMBs during ride as explained above? - -#### sky rocket high during ride - -During the ride your blood sugar goes sky rocket high. - -**Possible reason:** You have got taken too much carbs for your IoB at that time. Beneath for sure the typical technical problems with your -insulin pump like leakage or blockage of the catheder! - -**Reaction:** If it is too high for you take a rest and correct with a bolus. Keep in mind that you must ride home and therefore make it carefully. Drink 500 ml pure water without carbs. Stay calm: arrival comes before speed. - -**Action:** Have you eaten too much? Especially have you drunk too much from the dissolved glucose during the ride? Is your percentage of reduction the profile during profile switch too low and you can increase this? diff --git a/docs/CROWDIN/el/buildingAAPS.md b/docs/CROWDIN/el/buildingAAPS.md deleted file mode 100644 index 98164a09e49b..000000000000 --- a/docs/CROWDIN/el/buildingAAPS.md +++ /dev/null @@ -1,28 +0,0 @@ -# Dummy - -## This is a dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - - -## This is another dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - - -## This is another another dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - diff --git a/docs/CROWDIN/el/completingObjetives.md b/docs/CROWDIN/el/completingObjetives.md deleted file mode 100644 index 98164a09e49b..000000000000 --- a/docs/CROWDIN/el/completingObjetives.md +++ /dev/null @@ -1,28 +0,0 @@ -# Dummy - -## This is a dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - - -## This is another dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - - -## This is another another dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - diff --git a/docs/CROWDIN/el/dummy.md b/docs/CROWDIN/el/dummy.md deleted file mode 100644 index 98164a09e49b..000000000000 --- a/docs/CROWDIN/el/dummy.md +++ /dev/null @@ -1,28 +0,0 @@ -# Dummy - -## This is a dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - - -## This is another dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - - -## This is another another dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - diff --git a/docs/CROWDIN/el/intro.md b/docs/CROWDIN/el/intro.md deleted file mode 100644 index e6f94357b81d..000000000000 --- a/docs/CROWDIN/el/intro.md +++ /dev/null @@ -1,291 +0,0 @@ -![20-06-23v2 AAPS simple overview-cropped](https://github.com/openaps/AndroidAPSdocs/assets/94044064/e505b73b-09a0-42a4-a1ab-b830a0741234) - -# Introduction to APS and AAPS - -## What is an “Artificial Pancreas System”? - -A human pancreas does a lot of things besides regulating blood sugar. However, the term **“Artificial Pancreas System” (APS)** usually refers to a system which works to automatically keep blood sugar levels within healthy limits. - -The most basic way to do this is by detecting **glucose levels**, using these values to do **calculations**, and then delivering the (predicted) right amount of **insulin** to the body. It repeats the calculation, every few minutes, 24/7. It uses **alarms** and **alerts** to inform the user if intervention or attention is needed. This system is typically made up of a **glucose sensor**, an **insulin pump** and an **app** on a phone. - -You can read more about the different artificial pancreas systems currently in use and in development in this 2022 review article: - -![Frontiers](./images/FRONTIERS_Logo_Grey_RGB.png) [Future Directions in Closed-Loop Technology](https://www.frontiersin.org/articles/10.3389/fendo.2022.919942/full#:~:text=Fully%20closed%2Dloop%20systems%2C%20unlike,user%20input%20for%20mealtime%20boluses). - -In the near future, some so-called "dual-hormone" systems will also have the ability to infuse glucagon alongside insulin, with the aim of preventing severe hypos and allowing even tighter blood glucose control. - -An artificial pancreas can be thought of as an [“autopilot for your diabetes”]. (https://www.artificialpancreasbook.com/) What does that mean? In an aircraft, an autopilot does not do the complete job of the human pilot, the pilot cannot sleep through the entire flight. The autopilot aids the work of the pilot. It relieves them of the burden of permanently monitoring the aircraft, allowing the pilot to concentrate on wider monitoring from time to time. The autopilot receives signals from various sensors, a computer evaluates them together with the pilot’s specifications and then makes the necessary adjustments, alerting the pilot to any concerns. The pilot no longer has to worry about constantly making decisions. - -## What does hybrid closed loop mean? - -The best solution for type 1 diabetes would be a “functional cure” (probably an implant of pancreatic cells which are protected from the immune system). While we are waiting for that, a “full closed loop” artificial pancreas is probably the next best thing. This is a tech system that doesn’t need any user input (like bolusing insulin for meals, or announcing exercise), with good regulation of blood glucose levels. At the moment, there are no widely available systems which are “full” closed loop, they all need some user input. The currently available systems are called “hybrid” closed loop, because they use a combination of automated technology and user input. - -## How and why did looping start? - -The development of commercial technology for people with type 1 diabetes (T1D) is very slow. In 2013 the T1D community founded the #WeAreNotWaiting movement. They developed systems themselves using existing approved technology (insulin pumps and sensors) to improve blood glucose control, safety, and quality of life. These are known as DIY (do-it-yourself) systems, because they are not formally approved by health bodies (FDA, NHS etc). There are four main DIY systems available: OpenAPS, **AAPS**, Loop and iAPS. - -A great way to understand the fundamentals of DIY looping is to read Dana Lewis’s book “Automated Insulin Delivery”. You can access it \[here\] (https://www.artificialpancreasbook.com/) for free (or buy a hardcopy of the book). If you want to understand more about OpenAPS, which** AAPS** has developed from, the \[OpenAPS website\] (https://openaps.org/what-is-openaps/) is also a great resource. - -Several commercial hybrid closed loop systems have been launched, the most recent of which are \[CamAPS FX\] (https://camdiab.com/) (UK and EU) and \[Omnipod 5\] (https://www.omnipod.com/en-gb/what-is-omnipod/omnipod-5) (USA and EU). These are very different to DIY systems, mainly because they both include a “learning algorithm” which adjusts how much insulin is delivered according to your insulin needs from previous days. Many people in the DIY community have already tried out these commercial systems and compared them with their DIY system. You can find out more about how the different systems compare by asking on the dedicated Facebook groups for these systems, on the \[AAPS Facebook group\] (https://www.facebook.com/groups/AndroidAPSUsers/) or on \[Discord\] (https://discord.com/invite/4fQUWHZ4Mw). - -## What is Android APS (AAPS)? - -![image](https://github.com/openaps/AndroidAPSdocs/assets/94044064/0f089d96-b7ee-452a-aa9d-aae10ab58971) - -**Figure 1**. Basic outline of the Android APS (Artificial Pancreas System), AAPS. - -Android APS (AAPS) is a hybrid closed loop system, or Artificial Pancreas System (APS). It makes its insulin dosing calculations using established \[OpenAPS\] (https://openaps.org/) algorithms (a set of rules) developed by the #WeAreNotWaiting type 1 diabetes community. - -Since OpenAPS is only compatible with certain older insulin pumps, AAPS (which can be used with a wider range of insulin pumps) was developed in 2016 by Milos Kozak, for a family member with type 1 diabetes. Since those early days, **AAPS** has been continually developed and refined by a team of volunteer computer developers and other enthusiasts who have a connection to the type 1 diabetes world. Today, **AAPS** is used by approximately 10,000 people. It is a highly customisable and versatile system, and because it is open-source, it is also readily compatible with many other open-source diabetes softwares and platforms. The fundamental components of the current **AAPS** system are outlined in Figure 1 above. - -## What are the basic components of AAPS? - -The “brain” of AAPS is an **app** which you build yourself. There are detailed step-by-step instructions for this. You then install the **AAPS app** on a compatible **Android smartphone** (1). A number of users prefer their loop on a separate phone to their main phone. So, you don’t necessarily have to be using an Android phone for everything else in your life, just for running your AAPS loop. - -The **Android smartphone** will also need to have another app installed on it as well as **AAPS**, either a modified Dexcom app called build-your-own dexcom app (**BYODA**) or Xdrip+. This receives glucose data from a sensor (2) by bluetooth, and then sends the data internally on the phone to the **AAPS app**. - -The **AAPS app** uses a decision making process (**algorithm**) from OpenAPS. Beginners start out using the basic **oref0** algorithm, but it is possible to switch to using the newer **oref1** algorithm as you progress with AAPS. Which algorithm you use (oref0 or oref1), depends on which suits your specific situation best. In both cases, the algorithm takes into account multiple factors, and performs rapid calculations every time a new reading comes in from the sensor. The algorithm then sends instructions to the insulin pump (3) on how much insulin to deliver by bluetooth. All the information can be sent by mobile data or wifi to the internet. This data can also be shared with followers if desired, and/or collected for analysis. - -## What are the advantages of the AAPS system? - -The OpenAPS algorithm used by **AAPS** controls blood sugar levels in the absence of user input, according to the users’ defined parameters (important ones being basal rates, insulin sensitivity factors, insulin-to-carb ratios, duration of insulin activity etc.), reacting every 5 minutes to the new sensor data. Some of the reported advantages of using AAPS are extensive fine-tunable options, automations and increased transparency of the system for the patient/caregiver. This can result in better control over your (or your dependent’s) diabetes, which in turn may give improved quality of life and increased peace of mind. - -Practical advantages include: - -- **Hardware flexibility**: **AAPS** works with a wide range of insulin pumps and sensors. So for example, if you develop an allergy to Dexcom sensor patch glue, you could switch to using a Libre sensor instead. That offers flexibility as life changes. You don't have to rebuild, just tick a different box in the AAPS app to change your hardware. - -- **Highly customisable with wide parameters**: here are some examples of the possibilities with AAPS: a) The ability to set a lower glucose target 30 min before eating; you can set the target as low as 72 mg/dL (4.0 mmol/L). b) If you are insulin-resistant resulting in high blood sugars, **AAPS** allows you to set an **automation** rule to activate when BG rises above 8 mmol/L (144 mg/dL), switching to a 120% profile (resulting in an 20% increase in basal and strengthening of other factors too, compared to your normal **profile** setting). The automation will last according to the scheduled time you set. Such an automation could be set to only be active on certain days of the week, at certain times of day, and even at certain locations. c) If your child is on a trampoline with no advance notice, **AAPS** allows insulin suspension for a set time period, directly via the phone. d) After reconnecting a tubed pump which has been disconnected for swimming, AAPS will calculate the basal insulin you have missed while disconnected and deliver it carefully, according to your current BG. Any insulin not required can be overridden by just “cancelling” the missed basal. f) **AAPS** has the ability to set different profiles for different situations and easily switch between them. Features which make the algorithm quicker to bring down elevated BG (like supermicro boluses (“SMB”), unannounced meals, (“**UAM**”) can be set to only work during the daytime, if you are worried about night-time hypos. - - -These are all examples, the full range of features gives huge flexibility for daily life including sport, illness, hormone cycles etc. Ultimately, it is for the user to decide how to use this flexibility, and there is no one-size-fits-all automation for this. - -- **Remote monitoring**: there are multiple possible monitoring channels (Sugarmate, Dexcom Follow, Xdrip+, Android Auto etc.) which are useful for parents/carers and adults in certain scenarios (sleeping/driving) who need customisable alerts. In some apps (Xdrip+) you can also turn alarms off totally, which is great if you have a new sensor “soaking” or settling down that you don’t want to loop with yet. - -- **Remote control**: a significant advantage of **AAPS **over commercial systems is that it is possible for followers, using authenticated text (SMS) commands or via an app (Nightscout or NSClient) to send a wide range of commands back to the ****AAPS** **system. This is used extensively by parents of kids with type 1 diabetes who use AAPS. It is very useful in the playground, for example, if you want to pre-bolus for a snack from your own phone, and your child is busy playing. It is possible to monitor the system (e.g. Fitbit), send basic commands (e.g. Samsung Galaxy watch 4), or even run the entire AAPS system from a high-spec smartwatch (5) (e.g. LEMFO LEM14). In this last scenario, you don’t need to use a phone to run AAPS. As battery life on watches improves, this last option is likely to become increasingly attractive. - -- **No commercial constraints due to open application interfaces**: beyond the use of an open source approach, which allows the source code of **AAPS** to be viewed at any time, the general principle of providing open programming interfaces gives other developers the opportunity to contribute new ideas that allow users to live more easily with their diabetes. This is complementary to commercial systems which adopt the innovations from DIY, where interfaces are only made possible in return for licensing, thus preventing innovations in particular that are not-for-profit. Good examples for such integrations are NightScout, Nightscout Reporter, Xdrip+ M5 stack etc. - -- **Detailed app interface**: It is easy to keep track of things like: insulin levels, cannula age, sensor age, pump battery age, and many actions can be done through the **AAPS** app (priming the pump, disconnecting the pump etc.), instead of on the pump itself. - -- **Accessibility and affordability**: **AAPS** gives people who currently can’t afford to self-fund, or don’t have funding/insurance, access to a world-class hybrid closed looping system which is conceptually years ahead, in terms of development, of the commercial systems being offered by clinics. You currently need to have a Nightscout account to set up **AAPS**. Although the Nightscout account it not necessarily required after setup, many people continue to use Nightscout for collecting their data, and for remote control. So, although **AAPS **itself is free, setting up Nightscout through one of the various platforms may incur a fee (E0 - E12), depending on what level of support you want (see comparison table). **AAPS** works with a wide range of affordable (starting from approx E150) Android phones. In comparison, Loop currently costs around $80 a year for the Apple development licence and CamAPS FX costs around E80/month (as at 2023). - -- ****Support**: No automated insulin delivery system is perfect. Commercial and open-source systems share many common glitches in both communications and temporary hardware failure. There is a community of AAPS users on both Facebook and Discord and Github who designed, developed and are currently using **AAPS** all over the world. There are Facebook support groups and help from clinic/commercial companies for the commercial APS systems - it is worth speaking to the users, or former users of these systems to get feedback on the common glitches, the quality of the education programme and the level of ongoing support provided. - -- **Predictability, transparency and safety**: with no learning algorithm, **AAPS** is logical and in some respect, more predictable, which may make it easier to know when a setting is wrong, and to adjust it accordingly. You can see exactly what the system is doing, why it is doing it, and set its operational limits, which puts the control (and responsibility) in your hands. This can provide the user with confidence, and a sounder sleep. - -- **Access to advanced features through dev modes including full closed loop**: **AAPS **documentation focuses on the mainstream **“master”** branch of **AAPS**, however, research and development is going on all the time. More experienced users may wish to explore the experimental features in the **development** branch such as integration of Dexcom G7, and automatically adjusting insulin delivery according to short-term sensitivity changes (DYNISF), not having to bolus for meals, and generally trying to make life with type 1 diabetes as convenient as possible. - -- **Ability to contribute yourself to further improvements**: type 1 diabetes can be highly frustrating and isolating. Having control over your own diabetes tech, with the possibility to “pay it forward” as soon as you are making progress by helping others on their journey can be really rewarding. You can educate yourself, discover the roadblocks and look for and even contribute to new developments and the documentation. There will be others with the same quest to bounce ideas off and work with. This is the essence of #WeAreNotWaiting. - - -## How does AAPS compare to MDI and open looping? - -Multiple daily injections (MDI, a) usually involve giving an injection of a long-lasting insulin (e.g. Tresiba) once a day, with injections of faster-acting insulin (e.g. Novorapid, Fiasp) at mealtimes, or for corrections. Open pumping (b) involves using a pump to deliver basal at pre-programmed rates of rapid-acting insulin, and then boluses through the pump at mealtimes or for corrections. The basics of a looping system is that the App uses the glucose data to instruct the pump to stop insulin delivery when it predicts you are heading for a low, and to give you extra insulin if your glucose levels are rising and predicted to go too high (c). Although this is oversimplified, (mostly because hybrid closed looping has a lot of additional useful features) the key features of each system are shown in **Figure 2**. - -![image](https://github.com/openaps/AndroidAPSdocs/assets/94044064/4e7d8608-684d-4c69-9c61-88c9539f5d6f) - -**Figure 2**. Overview of (a) MDI, (b) open-loop pumping and (c) hybrid closed loop pumping - -## How does AAPS compare to other looping systems? - -At present there are four major open source closed loop systems available: OpenAPS, **AAPS**, \[Loop\] (https://loopkit.github.io/loopdocs/#what-is-loop) and iAPS, (formerly FreeAPS X). The features of the different systems are shown in the table below: - -| Devicestyp | Name | [Open APS](https://openaps.readthedocs.io/en/latest/) | [AAPS](https://wiki.aaps.app) | [Κύκλωμα](https://loopkit.github.io/loopdocs/) | [iAPS](https://iaps.readthedocs.io/en/latest/) | -| ---------- | -------------------------------------------------------------------------------------------------------- | ----------------------------------------------------- | ------------------------------------------- | ---------------------------------------------- | ---------------------------------------------- | -| PUMP | Older Medtronic | ![available](./images/available.png) | ![available](./images/available.png) | ![available](./images/available.png) | ![available](./images/available.png) | -| PUMP | Older Omnipod (Eros) | ![unavailable](./images/unavailable.png) | ![available](./images/available.png) | ![available](./images/available.png) | ![available](./images/available.png) | -| PUMP | Newer Omnipod (Dash) | ![unavailable](./images/unavailable.png) | ![available](./images/available.png) | ![available](./images/available.png) | ![available](./images/available.png) | -| PUMP | DANA R, DANA RS, DANA I | ![unavailable](./images/unavailable.png) | ![available](./images/available.png) | ![unavailable](./images/unavailable.png) | ![unavailable](./images/unavailable.png) | -| PUMP | Roche Combo, Insight | ![unavailable](./images/unavailable.png) | ![available](./images/available.png) | ![unavailable](./images/unavailable.png) | ![unavailable](./images/unavailable.png) | -| CGM | Dexcom G4, G5, G6 | ![available](./images/available.png) | ![available](./images/available.png) | ![available](./images/available.png) | ![available](./images/available.png) | -| CGM | Libre 1 (requires Miao Miao) | ![available](./images/available.png) | ![available](./images/available.png) | ![available](./images/available.png) | ![available](./images/available.png) | -| CGM | Libre 2 | ![available](./images/available.png) | ![available](./images/available.png) | ![available](./images/available.png) | ![available](./images/available.png) | -| CGM | Libre 3 | | ![unavailable](./images/unavailable.png) | --- | ![unavailable](./images/unavailable.png) | -| CGM | Medtronic Enlite | | --- | ![unavailable](./images/unavailable.png) | --- | -| CGM | [Dexcom G7](https://androidaps.readthedocs.io/en/latest/Hardware/DexcomG7.html) | | ![available](./images/available.png) (beta) | ![available](./images/available.png) | ![available](./images/available.png) | -| CGM | [Eversense](https://androidaps.readthedocs.io/en/latest/Hardware/Eversense.html) | | ![available](./images/available.png) | | ![available](./images/available.png) | -| CGM | [MM640g/MM630g](https://androidaps.readthedocs.io/en/latest/Hardware/MM640g.html) | | ![available](./images/available.png) | | ![available](./images/available.png) | -| CGM | [PocTech](https://androidaps.readthedocs.io/en/latest/Hardware/PocTech.html) | | ![available](./images/available.png) | | ![available](./images/available.png) | -| CGM | [Nightscout as BG Source](https://androidaps.readthedocs.io/en/latest/Hardware/CgmNightscoutUpload.html) | | ![available](./images/available.png) | | ![available](./images/available.png) | -| Phone | Android | ![available](./images/available.png) | ![available](./images/available.png) | ![unavailable](./images/unavailable.png) | ![unavailable](./images/unavailable.png) | -| Phone | iPhone | ![available](./images/available.png) | ![unavailable](./images/unavailable.png) | ![available](./images/available.png) | ![available](./images/available.png) | - -[OpenAPS](https://openaps.readthedocs.io/) was the first Open Source Closed Loop System. It uses a small computer such as Raspberry Pi or Intel Edison. Both AndroidAPS (AAPS) and iAPS use the OpenAPS algorithms, whereas Loop uses a separate algorithm. You can read a comparison of iAPS and **AAPS** here. - -An international peer-reviewed consensus statement containing practical guidance on open source looping was written by and for health-care professionals, and published in a leading medical journal in 2022. It is well worth a read (including for your diabetes clinic) and summarises the main technical differences between the different open-source hybrid closed loop systems: - - Lancet Diabetes Endocrinol, 2022; 10: 58–74 - -[https://www.ncbi.nlm.nih.gov/pmc/articles/PMC8720075/](https://www.ncbi.nlm.nih.gov/pmc/articles/PMC8720075/) - -It is hard to get a “feel” for any system without using it, or talking to others who are using it, so do reach out to others on Facebook/Discord and ask. Most people find that AAPS is incredibly sophisticated in comparison to other hybrid closed loop systems (particularly the commercial systems), with a huge number of potentially customisable settings and features, discussed above. Some people can find this a little overwhelming in the beginning, but there is no rush to investigate all the possibilities at once, you can progress as slowly or as fast as you would like, and there is help available at every step of the way. - -## Does AAPS use artificial intelligence or any learning algorithm? - -Όχι. **AAPS** does not have any complicated machine learning algorithms, multiple-parameter insulin response models, or differential equations. As such, the system is open and transparent in how it works, and has the ability to be understood not just by experts, but also by clinicians and patients. It also means that if you have a sharply varying schedule (maybe switching from a stressful week at work to a relaxing holiday) and are likely to need a significantly different amount of insulin, you can immediately switch **AAPS** to run a weaker/stronger profile. A ‘learning system’ will do this adjustment for you automatically, but is likely to take longer to adjust the insulin delivery. - -## Which system is right for me or my dependent? - -Practically, your choice of system is often restricted by which pump you already have, or can obtain from your medical provider, and your choice of phone (Apple or Android). If you don’t yet have a pump you have the biggest choice of systems. Technology is continually evolving, pumps are being discontinued and new pumps and sensors are being released. Most open-source systems work with the main sensors (Libre and Dexcom) or are quickly adapted to work with new sensors a year or so after they are released (with a bit of time delay for safety and stability testing). - -Most **AAPS **users report more time in range, HbA1c reductions, as well as quality of life improvements from having a system that can auto-adjust basal rates overnight during sleep, and this is true for most hybrid closed loop APS. Some people have a preference for a very simple system which is not very customisable (which means you may prefer a commercial system), and others find this lack of control very frustrating (you may prefer an open-source system). If you (or your dependent) are newly diagnosed, a common route is to get the hang of MDI plus sensor first, then progress to a pump which has the potential for looping, then to **AAPS**, but some people (especially small kids) may go straight to a pump. - -It is important to note that the **AAPS** user needs to be proactive to troubleshoot and fix problems themselves, with help from the community. This is a very different mindset to that when using a commercial system. With **AAPS** a user has more control, but also the responsibility, and needs to be comfortable with that. - -## Is it safe to use open-source systems like AAPS? - -A more accurate question is probably “is it safe compared to my current type 1 diabetes insulin delivery system?” since no method of insulin delivery is without risk. There are many checks and balances in place with **AAPS**. A recent paper looked at the use of**** AAPS ****in a computer simulated set-up, [https://www.liebertpub.com/doi/epub/10.1089/dia.2019.0375](https://www.liebertpub.com/doi/epub/10.1089/dia.2019.0375) which was an effective way to unobjectively trial how safe and effective the system is. More generally, it is estimated that over 10,000 individuals worldwide are using open-source automated-insulin delivery systems, and uptake continues to increase globally. - -Any device that uses radio communications could be hacked, and this is true for a non-looping insulin pump as well. Currently, we are not aware of anyone attempting to harm individuals by hacking their diabetes-related medical equipment. However, there are multiple ways to protect against such risks: - -1. In the pump settings, limit both the max bolus allowed and max temporary basal settings to amounts that you believe are safest. These are hard limits that we do not believe any malicious hacker could circumvent. - -2. Set your CGM alarms enabled for both highs and lows. - -3. Monitor your insulin delivery online. Nightscout users can set additional alarms to alert for a wide variety of conditions, including conditions that are much more likely to occur than a malicious attack. In addition to highs and lows, Nightscout can display diagnostic data useful for verifying that the pump is operating as desired, including current IOB, pump temporary basal history, pump bolus history. It can also be configured to proactively alert users to undesirable conditions, such as predicted highs and lows, low insulin reservoir, and low pump battery. - - -If a malicious attack was made on your insulin pump, these strategies would significantly mitigate the risk. Every potential **AAPS** user needs to weigh the risks associated with using **AAPS**, versus the risks of using a different system. - -## How can I approach discussing AAPS with my clinical team? - -Depending on the country - link to doctors section of docs - - Lancet Diabetes Endocrinol, 2022; 10: 58–74 - -[https://www.ncbi.nlm.nih.gov/pmc/articles/PMC8720075/](https://www.ncbi.nlm.nih.gov/pmc/articles/PMC8720075/) - -## Q: Why can’t I just download AAPS and use it straight away? - -The **AAPS** app is not provided in Google Play - you have to build it from source code by yourself for legal reasons. **AAPS** is unlicensed, meaning that it does not have approval by any regulatory body authority in any country. **AAPS**is deemed to be carrying out a medical experiment on yourself, and is carried out at the user’s own risk. - -Setting up the system requires patience, determination and the gradual development of technical knowledge. All the information and support can be found in these documents, elsewhere online, or from others who have already done it. It is estimated that over 2000 people have successfully built and are currently using **AAPS** worldwide. - -The developers of **AAPS**t ake safety incredibly seriously, and want others to have a good experience of using **AAPS**. That is why it is essential that every user (or carer, if the user is a child): - -- builds the AAPS system themself and works through the **objectives** so that they have reasonably good personalised settings and understand the basics of how AAPS ****works by the time they “close the loop”; - -- backs up their system by exporting and saving important files (like keystore and settings .json file) somewhere safe, so you can setup again quickly if needed; - -- updates to newer master versions as and when they become available; and - -- maintains and monitors the system to ensure it is working properly. - - -## Q: What is the connectivity of the AAPS system? - -**Figure 3 (below)** shows one example of the **AAPS** system for a user who do not require any followers interacting with the system: - -![potential AAPS connectivity setup with no followers](./images/intro03.png) - -**Figure 4 (below)** shows the full potential of the **AAPS** system for a user who has followers and requires a monitor and send adjust the system remotely (like a child with T1D): - -![potential AAPS connectivity setup with followers](./images/intro04.png) - -## Q: How does AAPS get continually developed and improved? - -Most **AAPS** users use the fully tested **master** version of AAPS, which has been tested for bugs and problems, before being released to the community. Behind the scenes, the developers try out new improvements, and test these out in “developer” (**dev**) versions of **AAPS** with a user community who are happy to do bug updates at short notice. If the improvements work well, they are then released as a new “master” version of **AAPS**. Any new master release is announced on the Facebook group, so that the mainstream **AAPS** users can read about and update to the new master version. - -Some experienced and confident **AAPS ** users conduct experiments with emerging technologies and with dev versions of the **AAPS** app, which can be interesting for the less adventurous users to read about, without having to do it themselves! People tend to share these experiments on the Facebook group too. - -You can read more about some of these experiments and discussion on emerging tech here: - -[https://www.diabettech.com/](https://www.diabettech.com/) - -[https://bionicwookie.com/](https://bionicwookie.com/) - -## Q: Who can benefit? - -| User Type | -| ------------------------------------------- | -| ✔️ type 1 diabetic | -| ✔️ caregiver or parent of a type 1 diabetic | -| ✔️ blind users type 1 diabetic | -| ✔️ *clincians and healthcare professionals | - -The above table assumes that the user has access to both continuous gluocse monitor and insulin pump. - -*All data from **AAPS** can be made available to healthcare professionals via data sharing platforms, including NightScout that provides logging and real time monitoring of CGM data, insulin delivery, carbohydrate entries, predictions and settings. Nightscout records include daily and weekly reports which can aid healthcare professionals' discussions with type 1 patients with more accurate data on glycemic control and any behavioural considerations. - -## Q: What benefits can I get? - -With investment of your time, **AAPS** can potentially lead to: - -- alleviating the stress and burden of managing type 1 diabetes; - -- reducing the multitude of mundane decisions that arise from type 1 diabetes; - -- the provision of personalised and dynamic insulin dosing based on real-time data which can cut down the need for hypo treatments and reduce hyperglycemia episodes; - -- an increased knowledge of insulin management and confidence to better fine tune your settings; - -- the ability to create automatic settings (**automations**) that are tailored to fit in with your lifestyle; - -- improved sleep quality and overall reduction in the frequency of nighttime interventions; - -- remote monitoring and administration of insulin delivery for caregivers of type 1 diabetics; and - -- streamlining of all your portable diabetic equipment (continuous glucose monitor and insulin portable devices) by replacing them with an android phone controlled by **AAPS**. - - -Ultimately,**AAPS** can empower individuals to better manage their diabetes resulting in stable blood sugars and improved long term health outcomes. - ---- - -## AAPS First Steps - -Welcome. This is an introduction to aid beginners getting started with **AAPS** (or commonly referred to as "looping"). - -## Safety - -“_With great powers comes great responsibilities…_” - -**AAPS** is designed with an extensive set of safety features with limits imposed and gradually removed with completion of the **objectives **(predominately made up of multiple choice questions). An **AAPS** feature will be unlocked as the Objectives are successfully completed. This process will gradually allow the user to migrate from Open Loop to Closed Loop. - -This has been done to achieve the best possible experience with **AAPS** in order to prevent common mistakes that new users tend to make when starting to loop. The safety parameters have been built upon typical errors and general trends **AAPS** developers have observed with new users. Mistakes can happen because the beginner is inexperienced and too eager to get started with AAPS or has overlooked the required materials. Do not worry, we have all been there! - -## Key Principles - -The key principles and concepts of looping must be understood by the user before using **AAPS**. This is achieved by investing your personal time into reading the **AAPS** documentation, and completing the Objectives which is aimed to provide you with a solid platform for safe and effective use of **AAPS**. The volume of **AAPS** documentation may seem overwhelming at first but be patient and trust the process - with the proper approach, you'll get there! The overall process will depend upon the beginner’s progress and completion of objectives can typically take between 6 to 9 weeks . - -## Plan for hiccups - -At the preliminary stages of **AAPS**, you should expect to experience some hiccups whilst trying to fine tune your settings. **AAPS**’ glitches cannot be flushed out until the system is used in everyday life. Please plan accordingly and allow a sensible amount of time to troubleshoot and resolve such issues. - -## Flexibility/Adaptability - -Success with **AAPS** requires a proactive approach, a willingness to reflect on the BG data and flexibility to make the necessary adjustments to **AAPS** in order to improve your outcomes. Just as it is nearly impossible to learn to play a sport by reading about the rules alone, the same can be said of **AAPS**. - -## Technology compatibility - -There are limitations with **AAPS** as it is accessible for only certain types of insulin pumps or CGMs, and some technology may not be available for use in various countries. In order to avoid any disappointment or frustrations, please read please read Component Set Up (Section INSERT). - -## App Build Time - -The time to build the **AAPS**(under Section INSERT) depends on your level of expertise and technical ability. Typically for inexperienced users, it can take up to half a day or a full day (with help from the community) in order to build the **AAPS**. The process will significantly speed up as you become more experienced at building the **AAPS**. To aid the build process there are sections dedicated for: -- list of questions and answers for frequent errors that are likely to occur under FAQs (Section K); -- “How to install AAPS? (Section INSERT) which includes Troubleshooting subsection. - -## Keystore & configurations settings a export file - -A “keystore” is a password encrypted file unique to your own copy of **AAPS**. Your android phone uses it to ensure that nobody else can upgrade your own copy without the keystore. In short, as part of the **AAPS** build, you should: - -- save the your keystore file (.jks file used to sign your app) in a safe place; -- keep a note of your password for your keystore file. - -By doing the above, this will ensure that you can use that exact same keystore file each time an updated version of **AAPS** is created. On average, there will be 2-3 AAPS updates required each year. - -In addition, **AAPS** provides the ability to export all your configuration settings. This ensures that you can safely recover your system while changing phones, upgrading/reinstalling the application with minimum disruption. - -## Troubleshootng - -Please feel free to reach out to the AAPS community if there is anything you feel unsure about - there is no such thing as a silly question! All users with various levels of experience are encouraged to ask questions as necessary. Response times to questions are usually quick, typically only a few hours due to the volume of **AAPS** users. - -a) check the documentation; b) ask AAPS facebook group (https://www.facebook.com/groups/AndroidAPSUsers); and c) ask our discord channel. - -## Section overview - -AAPS documentation is made up of the following Sections: - -[INSERT ONCE SECTIONS /SUB SECTIONS AGREED] ---- diff --git a/docs/CROWDIN/el/maintaining.md b/docs/CROWDIN/el/maintaining.md deleted file mode 100644 index 98164a09e49b..000000000000 --- a/docs/CROWDIN/el/maintaining.md +++ /dev/null @@ -1,28 +0,0 @@ -# Dummy - -## This is a dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - - -## This is another dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - - -## This is another another dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - diff --git a/docs/CROWDIN/el/optimizing.md b/docs/CROWDIN/el/optimizing.md deleted file mode 100644 index 98164a09e49b..000000000000 --- a/docs/CROWDIN/el/optimizing.md +++ /dev/null @@ -1,28 +0,0 @@ -# Dummy - -## This is a dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - - -## This is another dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - - -## This is another another dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - diff --git a/docs/CROWDIN/el/prepairing.md b/docs/CROWDIN/el/prepairing.md deleted file mode 100644 index e9cb2d72ced8..000000000000 --- a/docs/CROWDIN/el/prepairing.md +++ /dev/null @@ -1,145 +0,0 @@ -# Prepairing - -## Guide to the Android APS doc - -### First Steps -Welcome. This is an introduction to aid beginners to the concept of Do-It-Yourself-APS (Android-Artificial-Pancreas-Systems “AAPS”) is commonly referred to as ‘looping’.. - -#### Safetys -“With great powers come great responsibilities…” - -AAPS is designed with an extensive set of safety features with limits imposed and gradually removed with completion of the [Objectives](https://androidaps.readthedocs.io/en/latest/Usage/Objectives.html) (predominately made up of multiple choice questions). An AAPS feature will be unlocked as the Objectives are successfully completed. This process will gradually allow the user to migrate from Open Loop to Closed Loop. - -This has been done to achieve the best possible experience with AAPS by preventing common mistakes new users tend to make when starting to loop. The safety parameters have been built upon typical errors and general trends AAPS developers have observed with new users. Mistakes can happen because the beginner is inexperienced and too eager to get started with AAPS or has overlooked the required materials. Do not worry, we have all been there! - -#### Key Principles - -The key principles and concepts of looping must be understood by the user before using AAPS. This is achieved by investing your personal time into reading the AAPS documentation, and completing the [Objectives](https://androidaps.readthedocs.io/en/latest/Usage/Objectives.html) which is aimed to provide you with a solid platform for safe and effective use of AAPS. The volume of AAPS documentation may seem overwhelming at first but be patient and trust the process - with the proper approach, you'll get there! The overall process will depend upon the beginner’s progress and completion of objectives which typically take between 6 to 9 weeks . - -#### Plan for hiccups - -At the preliminary stages of AAPS, you should expect to experience some hiccups whilst trying to fine tune your settings. AAPS’ glitches cannot be flushed out until the system is used in everyday life. Please plan accordingly and allow a sensible amount of time to troubleshoot and resolve such issues. - -#### Flexibility/Adaptability - -Success with AAPS requires a proactive approach, a willingness to reflect on the BG data and flexibility to make the necessary adjustments to AAPS in order to improve your outcomes. Just as it is nearly impossible to learn to play a sport by reading about the rules alone, the same can be said of AAPS. - -#### Technology compatibility -There are limitations with AAPS as it is accessible for only certain types of insulin pumps or CGMs, and some technology may not be available for use in various countries. In order to avoid any disappointment or frustrations, please read [Component Set Up (Section E).](https://androidaps.readthedocs.io/en/latest/Configuration/BG-Source.html) - -#### App Build time -The time to build the AAPS (under Section D) depends on your level of expertise and technical ability. Typically for inexperienced users, it can take up to half a day or a full day (with help from the community) in order to build the AAPS. The process will significantly speed up as you become more experienced at building the AAPS.  - -To aid the build process there are sections dedicated for: - -- list of questions and answers for frequent errors that are likely to occur under [FAQs (Section](https://androidaps.readthedocs.io/en/latest/Getting-Started/FAQ.html) K); - -- “[How to install AAPS](https://androidaps.readthedocs.io/en/latest/Installing-AndroidAPS/Building-APK.html)? (Section D) which includes [Troubleshooting](https://androidaps.readthedocs.io/en/latest/Usage/troubleshooting.html) subsection. - - -#### Keystore & configuration settings export  file - -A “keystore” is a password encrypted file unique to your own copy of AAPS. Your android phone uses it to ensure that nobody else can upgrade your own copy without the keystore.In short, as part of the AAPS build, you should: - -1. save the your keystore file (.jks file used to sign your app) in a safe place; - -2. keep a note of your password for your keystore file. - - -By doing the above, this will ensure that you can use that exact same keystore file each time an updated version of AAPS is created. On average, there will be 2-3 updates to the AAPS required each year. In addition, AAPS provides the ability to [export all your configuration settings](https://androidaps.readthedocs.io/en/latest/Usage/ExportImportSettings.html). This ensures that you can safely recover your system while changing phones, upgrading/reinstalling the application with minimum disruption.  - -#### Αντιμετώπιση προβλημάτων - -Please feel free to reach out to the AAPS community if there is anything you feel unsure about - there is no such thing as a silly question!  All users with various levels of experience are encouraged to ask questions as necessary. Response times to questions are usually quick, typically only a few hours due to the volume of AAPS users.  - -##### [check the documentation](https://androidaps.readthedocs.io/en/latest/index.html) - -##### [ask our facebook group](https://www.facebook.com/groups/AndroidAPSUsers/) - -##### [ask our discord channel](https://discord.com/channels/629952586895851530/629954570394533889) - -#### Section overview - -AAPS documentation is made up of the following Sections: - -##### [Getting started](https://androidaps.readthedocs.io/en/latest/Getting-Started/Safety-first.html) - -This is a must read to understand the general concept of what an artificial pancreas system is designed to do. - -##### [What do I need?](https://androidaps.readthedocs.io/en/latest/Module/module.html) - -This explains AAPS’ compatibility with CGMs (Continuous Glucose Monitors) and insulin pumps. It also provides a guide on the correct assembly of an AAPS system to ensure that it functions correctly in everyday life. - -##### How to install AAPS - -This section is the manual for building the AAPS. Strict adherence to the step-by-step instructions are required in order to successfully build the AAPS. Please take your time. - -##### [Component Setup](https://androidaps.readthedocs.io/en/latest/Configuration/BG-Source.html) - -This explains how to properly integrate each of the various different separate component parts into AAPS, as well as how to set them up to work as seamlessly as possible together. All components are listed under the separate sections: CGM/FGM, xDrip Settings, Pumps, Phones, Nightscout setup, and Smartwatches. The sensor (BG) values and control of the insulin pump are particularly important information to understand. - -##### Configuration - -This explains how to set and configure your ‘Profile’, ‘Insulin’, ‘BG Source’, ‘Pump’, ‘Sensitivity Detection’, ‘APS’, ‘Loop’, ‘Treatments’. - -##### AAPS Usage - -This section provides a breakdown of the features provided by AAPS. - -##### [General Hints](https://androidaps.readthedocs.io/en/latest/Usage/Timezone-traveling.html) - -Useful tricks on how to tackle looping issues such as time zones, and daylight saving (i.e. Spring Forward/ - Fall Back). - -##### [AAPS](https://androidaps.readthedocs.io/en/latest/Getting-Started/Screenshots.html) for Children - -This is designed for parents or caregivers who want to build an AAPS for their child. It also explains the extra features necessary in order to support and safely control your child’s AAPS remotely.

The concepts in this section should be fully understood in order to competently use this feature. - -##### Αντιμετώπιση προβλημάτων - -This section contains links to help solve issues when building or using AAPS. - -##### FAQ - -This section addresses specific questions which tend to come up when building or using AAPS. - -##### [Γλωσσάριο](https://androidaps.readthedocs.io/en/latest/Getting-Started/Glossary.html) - -This contains a list of the acronyms (or short-term names) or defined terms developed specifically for AAP (for instance, the terms ‘ISF’ or ‘TT’ have special meanings in AAPS). - -##### [Where to go for help](https://androidaps.readthedocs.io/en/latest/Where-To-Go-For-Help/Background-reading.html)? - -This section is aimed to provide new users with links on resources in order to get help including accessing community support made up of both new and experienced users who can clarify questions, and resolve the usual pitfalls that come with AAPS. - -##### For Clinicians - -This is a section for the clinicians who have expressed interest in open source artificial pancreas technology such as AAPS, or for patients who want to share such information with their clinicians. | - -## what are we going to build? - -### An Android Phone Application - -At the core, AAPS is an android application running from a phone. You are going to build it from scratch by installing tools to download the sourcecode and build the actual application. - -### A reporting server NightScout (or Tidepool) - -In order to fully use AAPS properly you will want to setup a nightscout server. It is used to collect data from AAPS over time and possibly communicate to the application. It is required for parents who want to oversee their children AAPS sessions. It is also key to share data between clinicians and patients to perform analysis over time. - -## How long will it take? - -## Who might AAPS not be suitable for? - -## Where can I get help? - -## Requirements - -### medical - -### technical - -### personal - -### CGMs - -### Insulin Pump - -### Reporting (NS, Tidepool) \ No newline at end of file diff --git a/docs/CROWDIN/es/Configuration/Dexcom.md b/docs/CROWDIN/es/Configuration/Dexcom.md deleted file mode 100644 index cb267e23c069..000000000000 --- a/docs/CROWDIN/es/Configuration/Dexcom.md +++ /dev/null @@ -1,32 +0,0 @@ -# Dexcom G6 - -## Basics first - -* Follow [general CGM hygiene recommendations](../Configuration/BG-Source#cgm-hygiene) -* [Special recommendations for Dexcom G6 and DIY systems](../Configuration/BG-Source#dexcom-g6-diy-systems) *For G6 transmitters manufactured after fall/end of 2018 please make sure to use one of the [latest nightly built xDrip+ versions](https://github.com/NightscoutFoundation/xDrip/releases). Those transmitters have a new firmware and latest stable version of xDrip+ (2019/01/10) cannot deal with it. - -## Setting sensor - -When setting sensor, it is recommended not to press the inserter too firmly in order to avoid bleeding. The sensor thread should not come into contact with blood. - -After setting the sensor, the transmitter can be clicked into the sensor holder. Caution! First click in the square side and then press down the round side. - -## Troubleshooting - -### Connection problems - -Bluetooth connection may be disturbed by other nearby Bluetooth devices such as blood glucose meters, headsets, tablets or kitchen devices such as microwave ovens or ceramic hobs. In this case xdrip does not display any BG values. When bluetooth connection is reestablished the data is backfilled. - -### Sensor Errors - -If recurring sensor errors occur try selecting a different body site to set your sensor. The sensor thread should not come into contact with blood. - -Often a "Sensor Error" can be corrected by immediate drinking and massage around the sensor! - -### Jumpy values - -You might try to change settings for noise blocking in xdrip (Settings - Inter-App Settings - Noise Blocking) i.e. "Block Very High noise and worse". See also [Smoothing BG data](../Usage/Smoothing-Blood-Glucose-Data-in-xDrip.md). - -### New transmitter with running sensor - -If you happen to change transmitter during a running sensor session you might try to remove the transmitter without damaging the sensor mount. A video can be found at . \ No newline at end of file diff --git a/docs/CROWDIN/es/Configuration/EOFLOW.md b/docs/CROWDIN/es/Configuration/EOFLOW.md deleted file mode 100644 index bc406460867a..000000000000 --- a/docs/CROWDIN/es/Configuration/EOFLOW.md +++ /dev/null @@ -1,155 +0,0 @@ -# EOPatch2 Instruction Manual - -The patch requires the use of rapid-acting U-100 type insulin, such as NovoRapid or Humalog. Use a rapid-acting insulin that is suitable for you according to your doctor’s prescription and inject the prescribed dosage. - -The smallest injectable dose of insulin when using the patch is 0.05 U. The Profile BAS should therefore be set at a minimum value of 0.05 U/hr or more and an interval of 0.05 U/hr, as otherwise there may be an error between the estimated total infusion amount in the Profile and the actual infusion amount in the patch. Likewise, the bolus must also be set and infused with a minimum infusion volume of 0.05 U. - -## Pump Setup -1. On the AndroidAPS home screen, click the hamburger menu in the upper left corner and go to Config Builder. -1. Select 'EOPatch2' in the Pump section. -1. Press the Back key to return to the home screen. - -![Bild1](../../images/EOPatch/Bild1.png) ![Bild2](../../images/EOPatch/Bild2.png) - -## Configuración -Select EOPATCH2 at the top of the home screen to go to the EOPATCH2 tab. - -Select the EOPatch2 Preferences menu by clicking the three dots in the upper right corner. - -The EOPatch2 Preferences menu offers a menu to set 3 types of notifications. - -### Low reservoir Alerts -A warning appears when the amount of insulin remaining in the reservoir reaches the set value or less while using the patch. It can be set from 10 to 50U in 5U increments. - -### Patch expiration Reminder -This is a reminder to notify you of the time remaining before the current patch expires. It can be set from 1 to 24 hours in 1 hour increments. The initial setting value is 4 hours. - -### Patch buzzer Reminder -This is a reminder function for injections other than basal injection. If you are using an (extended) bolus injection or a temporary basal injection, the patch will make a buzzer sound when the injection starts and when the injection is complete. The initial setting value is Off. - -![Bild3](../../images/EOPatch/Bild3.png) - -## Connecting the Patch - -### Move to patch connection screen - -Select EOPATCH2 at the top of the home screen and click the ACTIVATE PATCH button at the bottom left. - -![Bild4](../../images/EOPatch/Bild4.png) - -### Connecting the patch -Insert the syringe needle into the insulin inlet on the patch and then slowly push the piston to inject the insulin. When insulin is filled with more than 80U, the patch makes a booting sound (1 buzzer) and boots. After confirming the buzzer sound, click the START PAIRING button on the screen. - -[Warning] - -- Do not turn the needle action lever until instructed. It can cause serious problems during injection or safety checks otherwise. -- The amount of insulin that can be injected into the patch is 80~200U. If you inject less than 80U into the patch initially, the patch will not work. -- Take the insulin to be put into the patch from the refrigerator and leave it at room temperature for 15 to 30 minutes beforehand. The temperature of the insulin to be injected must be at least 10°C. - -![Bild5](../../images/EOPatch/Bild5.png) - -### patch pairing -The Patch pairing screen will be displayed, and pairing will be attempted automatically. If communication is successful, the Bluetooth pairing request notification appears. Click OK and when the Bluetooth pairing request notification appears a second time with the authentication code, select OK again. - -[Warning] - -- For pairing, the patch and the smartphone must be located within 30 cm of each other. -- After the patch booting is completed, the patch will beep every 3 minutes until the pairing is complete. -- After booting the patch, the patch application must be completed via the app within 60 minutes. If the application cannot be completed within 60 minutes, the patch should be discarded. - -![Bild6](../../images/EOPatch/Bild6.png) ![Bild7](../../images/EOPatch/Bild7.png) ![Bild8](../../images/EOPatch/Bild8.png) - - -### patch preparation -After removing the adhesive tape of the patch, check if the needle is sticking out. If there are no problems with the patch, click NEXT. - -![Bild9](../../images/EOPatch/Bild9.png) - -### Patch attachment -Insulin should be injected in a spot with subcutaneous fat but few nerves or blood vessels, so it is recommended to use the abdomen, arm, or thigh for the patch attachment site. Choose a patch attachment site and apply the patch after disinfecting the location. - -[Warning] - -- Make sure to straighten the side of the patch tape attached to the body evenly, so that the patch adheres completely to the skin. -- If the patch does not stick completely, air may enter between the patch and the skin, which can weaken the adhesive strength and waterproof effect of the patch. - -![Bild10](../../images/EOPatch/Bild10.png) - -### Safety Check -When patching is complete, touch Start Safety Check. When the safety check is completed, the patch will beep once. - -[Warning] - -- For safe use, do not turn the needle action lever until the safety check has been completed. - -![Bild11](../../images/EOPatch/Bild11.png) ![Bild12](../../images/EOPatch/Bild12.png) - - -### Inserting the needle -The needle is inserted by holding around the patch and turning the needle action lever more than 100° in the upward direction of the lever. There is a buzzer sound when the needle is inserted correctly. Turn the needle action lever further clockwise to release the lever. Click NEXT. - -[Caution] - -- If you go to the next step without the buzzer sounding, a needle insertion error warning will appear. - -## Discarding the patch -Patches must be replaced in the case of low insulin levels, usage expiration, and defects. The recommended usage period for each patch is 84 hours after booting the patch. - -### Discarding the patch -Select EOPATCH2 at the top of the home screen and click the DISCARD/CHANGE PATCH button at the bottom. On the next screen, click the DISCARD PATCH button. A dialog box appears to confirm once more and if you select the DISCARD PATCH button, the disposal is completed. - -![Bild13](../../images/EOPatch/Bild13.png) ![Bild14](../../images/EOPatch/Bild14.png) ![Bild15](../../images/EOPatch/Bild15.png) ![Bild16](../../images/EOPatch/Bild16.png) - -## Suspending and Resuming Insulin Delivery -Suspending insulin delivery also cancels both extended bolus and temporary basal. When resuming insulin delivery, the canceled extended bolus and temporary basal will not be resumed. And when insulin delivery is suspended, the patch will give a sound every 15 minutes. - -### Suspending insulin delivery -Select EOPATCH2 at the top of the home screen and click the SUSPEND button at the bottom right. When you select CONFIRM in the confirmation box, a time selection box appears. If you select the CONFIRM button after selecting the time, the insulin delivery will be suspended for the set amount of time. - -![Bild17](../../images/EOPatch/Bild17.png) ![Bild18](../../images/EOPatch/Bild18.png) ![Bild19](../../images/EOPatch/Bild19.png) - - -### Resuming insulin delivery -Select EOPATCH2 at the top of the home screen and click the RESUME button at the bottom right. Insulin delivery will resume by selecting CONFIRM in the confirmation dialog box. - -![Bild20](../../images/EOPatch/Bild20.png) ![Bild21](../../images/EOPatch/Bild21.png) - -## Alarms/Warnings - -### Alarm - -Alarms are issued for emergency situations of the highest priority and require immediate action. The alarm signal does not disappear or time out until it is acknowledged. An alarm occurs when there is a problem with the patch being used, so there may be cases where the patch in use needs to be discarded and replaced with a new patch. The warning is displayed as a dialog box and switching to another screen is not possible until processing is completed. - -![Bild22](../../images/EOPatch/Bild22.png) ![Bild23](../../images/EOPatch/Bild23.png) - -The different types of alarms are explained below. - -| Alarms | Explanation | -| -------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| Empty reservoir | Occurs when the patch’s reservoir runs out of insulin. | -| Patch expired | Occurs when the patch usage time has expired, and no further insulin injections are possible. | -| Occlusion | Occurs when it appears that the patch's insulin inlet is clogged. | -| Power on self-test failure | Occurs when the patch finds an unexpected error during the post-boot self-test process. | -| Inappropriate temperature | Occurs when the patch is outside the normal operating temperature range during patch application and use. To deal with this alarm, move the patch to an appropriate operating temperature (4.4 to 37°C) condition. | -| Needle insertion Error | Occurs when needle insertion is not normal during the patch application process. Check that the needle insertion edge of the patch and the needle activation button are in a straight line. | -| Patch battery Error | Occurs just before the patch’s internal battery runs out and powers off. | -| Patch activation Error | Occurs when the app fails to complete the patching process within 60 minutes after the patch is booted. | -| Patch Error | Occurs when the patch encounters an unexpected error while applying and using the patch. | - -### Warning - -A warning occurs in a medium or low-priority situation. When a warning occurs, it is displayed as a notification in the Overview screen. - -![Bild24](../../images/EOPatch/Bild24.png) - -The different types of warnings are explained below. - -| Warnings | Explanation | -| ---------------------------- | ------------------------------------------------------------------------------------------------------------------------------------- | -| End of insulin suspend | Occurs when the time set by the user has elapsed after the insulin infusion suspension has been completed. | -| Low reservoir | Occurs when the remaining amount of insulin in the patch is below the set amount. | -| Patch operating life expired | Occurs when the patch usage period is over. | -| Patch will expire soon | Occurs 1 hour before the patch must be discarded. | -| Incomplete Patch activation | Occurs when more than 3 minutes have elapsed due to an interruption during patch application in the stage after pairing is completed. | -| Patch battery low | Occurs when the patch's battery is low. | - diff --git a/docs/CROWDIN/es/Configuration/Hardware/index.md b/docs/CROWDIN/es/Configuration/Hardware/index.md deleted file mode 100644 index dac7a7bd8c63..000000000000 --- a/docs/CROWDIN/es/Configuration/Hardware/index.md +++ /dev/null @@ -1,27 +0,0 @@ -# Hardware-Configuration - -## Configuración - -## BG Source - -- [BG Source](../BG-Source.md) -- [xDrip+ Settings](../xDrip.md) -- [Dexcom G6 hints](../Dexcom.md) -- [Smoothing blood glucose data](../../Usage/Smoothing-Blood-Glucose-Data-in-xDrip.md) - -## Pumps - -- [Dana-R pump](../DanaR-Insulin-Pump.md) -- [Dana-RS pump](../DanaRS-Insulin-Pump.md) -- [Accu-Chek Combo pump](../Accu-Chek-Combo-Pump.md) -- [Accu-Chek Insight pump](../Accu-Chek-Insight-Pump.md) -- [Medtronic pump](../MedtronicPump.md) - -## Teléfonos - -- [Jelly Pro Settings](../../Usage/jelly.md) -- [Huawei Settings](../../Usage/huawei.md) - -## Smartwatch - -- [Watchfaces](../Watchfaces.md) diff --git a/docs/CROWDIN/es/Getting-Started/ClosedLoop.md b/docs/CROWDIN/es/Getting-Started/ClosedLoop.md deleted file mode 100644 index f57dddb53aba..000000000000 --- a/docs/CROWDIN/es/Getting-Started/ClosedLoop.md +++ /dev/null @@ -1,55 +0,0 @@ -# ¿Qué es un Sistema de Lazo Cerrado? - -![AAPS como un piloto automático](../images/autopilot.png) - -Un sistema de lazo cerrado de páncreas artificial combina diferentes componentes para facilitar la gestión de la diabetes para ti. En su excelente libro ["Automated Insulin Delivery"](https://www.artificialpancreasbook.com/), Dana M. Lewis, una de las fundadoras del movimiento de lazo cerrado de código abierto, lo denomina un ["piloto automático para tu diabetes"](https://www.artificialpancreasbook.com/3.-getting-started-with-your-aps). Pero, ¿Qué quiere decir esto? - -**Piloto automático de un avión** - -El piloto automático no realiza todo el trabajo y no brinda la posibilidad al piloto de dormir durante todo el vuelo. Facilita el trabajo de los pilotos. Los libera de la carga de monitorear permanentemente la aeronave y la actitud de vuelo. Esto permite al piloto concentrarse en monitorear el espacio aéreo y controlar las funciones del piloto automático. - -El piloto automático recibe señales de varios sensores, un ordenador los evalúa junto con las especificaciones del piloto y luego realiza los ajustes necesarios. El piloto ya no tiene que preocuparse por los ajustes constantes. - -**Sistema de lazo cerrado** - -Lo mismo se aplica a un sistema de lazo cerrado de páncreas artificial. No hace todo el trabajo, aún debes cuidar de tu diabetes. Un sistema de lazo cerrado combina los datos del sensor (MCG/MFG) con las especificaciones de tu manejo de la diabetes, como la tasa basal, el factor de sensibilidad a la insulina y la relación de carbohidratos. A partir de esto, calcula sugerencias de tratamiento e implementa estos pequeños ajustes permanentes con el fin de mantener tu diabetes dentro del rango objetivo y aliviarte. Esto te deja más tiempo para tu vida "junto a" la diabetes. - -Al igual que no querrías subirte a un avión donde solo el piloto automático vuele sin supervisión humana, un sistema de lazo cerrado te ayuda con el manejo de tu diabetes, ¡pero siempre necesita tu apoyo! **Incluso con un lazo cerrado, no puedes simplemente olvidarte de tu diabetes.** - -Al igual que el piloto automático depende de los valores de los sensores, así como de las especificaciones del piloto, un sistema de lazo cerrado necesita una entrada adecuada, como tasas basales, ISF y relación de carbohidratos, para apoyarte con éxito. - -## Sistemas de Lazo Cerrado de Páncreas Artificial de Código Abierto - -En la actualidad, existen tres principales sistemas de lazo cerrado de código abierto disponibles: - -### AndroidAPS (AAPS) - -AAPS se describe en detalle en [esta documentación](./WhatisAndroidAPS.html). Utiliza un smartphone Android para el cálculo y el control de tu bomba de insulina. Mantiene una estrecha colaboración con OpenAPS (es decir, comparten algoritmos). - -Las [bombas](../Hardware/pumps.md) compatibles son: - -- [DanaR](../Configuration/DanaR-Insulin-Pump.md) / [DanaRS & Dana-i](../Configuration/DanaRS-Insulin-Pump.html) -- [Accu-Check Combo](../Configuration/Accu-Chek-Combo-Pump.md) -- [Accu-Chek Insight](../Configuration/Accu-Chek-Insight-Pump.md) -- [Diaconn G8](../Configuration/DiaconnG8.md) -- [Omnipod DASH](../Configuration/OmnipodDASH.md) -- [Omnipod Eros](../Configuration/OmnipodEros.md) -- Antiguos modelos de [Medtronic](../Configuration/MedtronicPump.md) - -### OpenAPS - -[OpenAPS](https://openaps.readthedocs.io) fue el primer Sistema de Lazo Cerrado de Código Abierto. Utiliza un pequeño ordenador, como Raspberry Pi o Intel Edison. - -Las bombas compatibles son: - -- Algunas bombas antiguas de Medtronic - -### Loop para iOS - -[Loop for iOS](https://loopkit.github.io/loopdocs/) es el Sistema de Lazo Cerrado de Código Abierto que se utiliza con iPhones de Apple. - -Las bombas compatibles son: - -- Omnipod DASH -- Omnipod Eros -- Algunas bombas antiguas de Medtronic diff --git a/docs/CROWDIN/es/Getting-Started/GlossaryTest.md b/docs/CROWDIN/es/Getting-Started/GlossaryTest.md deleted file mode 100644 index 88bc97826608..000000000000 --- a/docs/CROWDIN/es/Getting-Started/GlossaryTest.md +++ /dev/null @@ -1,391 +0,0 @@ -# Glosario - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
TérminoDescripciónver tambiénmás detalles
AAPSAndroidAPS - sistema de páncreas artificial  
AMAayuda avanzada para comidas-algoritmo avanzado para manejar carbohidratosMA / SMBWiki - AMA
Android Automostrar las notificaciones de AAPS en la unidad de información y entretenimiento compatibles del coche Wiki - android auto
APKarchivo de instalación de software (paquete de aplicaciones Android) Wiki - Crear APK
Autosenscálculo de la sensibilidad a la insulina como resultado del ejercicio, las hormonas, etc. DIABETTECH-Autosens
Azureplataforma de computación en la nube para alojar los datos de NightscoutHeroku/NightscoutAzure
BATluz de estado de batería baja en la pantalla de inicioCAN/RES/SENPreferencias
Capturas de pantalla
BGglucosa en sangre  
BGIgrado en que BG 'debe' estar aumentando o cayendo sobre solamente en base a la actividad de la insulina  
(BG source) Fuentes de datos de glucemia¿De dónde vienen tus valores de glucosa?MCG/FGMWiki - Fuentes de BG
Blukon Nightreadertransmisor Bluetooth para utilizar Freestyle libre como CGMBlueReader / MiaoMiaoAmbrosia Blukon Nightreader
BRdosis basal  
CAGEcanula age - displayed in Nightscout if information was entered in actions tab / menu tab or through AAPS actions tab 'prime'Nightscout 
CANstatus light overdue canula change on homescreenBAT / RES / SENPreferencias
Capturas de pantalla
MCGcontinuous glucose monitor  
Lazo cerradoclosed-loop systems make automatic adjustments to basal delivery, without needing user-approval, based on an algorithmOpen loopWiki closed loop
COBcarbs on board  
DIAduration of insulin action Wiki insulin types
DIABETTECH - DIA
DSTdaylight savings time Wiki DST
eCarbs"extended carbs" - carbs split up over serveral hours (i.e. lot of fat/protein)
extended boluses you might know from regular pump therapy do not make much sense when looping		SMBWiki - eCarbs
eCarbs use case
FGMflash glucose monitor (Freestyle Libre) Wiki - Fuentes de BG
gitversion-control system for tracking changes in computer files and coordinating work on those files
-> neccessary for APK updates		 Wiki - update APK
Githubweb-based hosting service for version control using Git
-> storage of source code		 Github AndroidAPS
Glimpapp to collect values from Freestyle Libre Nightscout with Glimp
Herokuplataforma de computación en la nube para alojar los datos de NightscoutAzure / NightscoutHeroku
IC (or I:C)insulin to carb ratio (How many carbs are covered by one unit of insulin?)  
IOBinsulin on board - insulin active in your body  
ISFinsulin sensitivity factor - the expected decrease in BG as a result of one unit of insulin  
LGSLow Glucose Suspend
AAPS will reduce basal if blood glucose is dropping. But if blood glucose is rising then it will only increase basal if the IOB is negative (from a previous LGS), otherwise basal rates will remain the same as your selected profile. You may temporarily experience spikes following treated hypos without the ability to increase basal on the rebound.		objective 6 
LineageOSfree and open-source operating system for smartphones etc.
alternative OS for smartphones not running Android 8.1 (Oreo)
(when using Accu-Chek Combo)		 Wiki - Combo pump
Log filesrecord of all AAPS actions (useful for trubbleshooting and debugging) Wiki - log files
maxIOBsafety feature - maximum total IOB AAPS can't go over Wiki - maxIOB
Wiki - SMB
MiaoMiaotransmisor Bluetooth para utilizar Freestyle libre como CGMBlueReader / Blukon NightreaderMiaoMiao
min_5m_carbimpactsaftey feature - default carb decay at times when carb absorption can’t be dynamically worked out based on your bloods reactions Wiki - config builder
Nightscoutopen source project to access and report CGM dataNightscout ReporterNightscout
NS Clientpart of AAPS to connect to your Nightscout site Wiki - NS Client
Nightscout ReporterTool from fellow looper to generate PDFs reports from Nightscout dataNightscoutNightscout Reporter
NS Reporter @ Facebook
Objetivoslearning program within AAPS guiding you step by step from open to closed loop Wiki - objectives
OpenAPSopen artificial pancreas system
APS run on small computers (i.e. Raspberry Pie)
AAPS uses some of the OpenAPS features		 OpenAPS docs
Lazo abiertosystem will suggest recommended adjustments which have to be performed manually on the pumpLazo cerradoWiki - config builder
Oref0 / Oref1sensitivity detection
"reference design implementation version 0/1" - the key algorithm behind OpenAPS		 Wiki - sensitivity detection
Peak timetime of maximum effect of insulin given Wiki - config builder
PHpump history (entry in treatments tab) Screenshots
Prediccionespreditions for BG in the future based on different calculations Wiki - predition lines
Perfilbasic treatment settings (basal rate, DIA, IC, ISF, BG target)
can be defined locally or through Nightscout		NightscoutWiki - profile
Cambio de perfil(temporary) change of profile used or percentual increase/decrease Wiki - profile switch
RESstatus light overdue reservoir change on homescreenBAT / CAN / SENPreferencias
Capturas de pantalla
RileyLinkopen source hardware device to bridge Bluetooth Low Energy (BLE) to 916MHz wireless communication (used for old Medtronic pumps)OpenAPS 
SAGEsensor age - displayed in Nightscout if information was entered in the actions tab / menuNightscout 
SENstatus light sensor change on homescreenBAT / CAN / RESPreferencias
Capturas de pantalla
Sensivity detectioncálculo de la sensibilidad a la insulina como resultado del ejercicio, las hormonas, etc. DIABETTECH-Autosens
Sensor noiseunstable CGM readings leading to "jumping" values Wiki - sensor noise
SMBsuper micro bolus
advanced feature for faster BG adjustment		UAMWiki - SMB
Super bolusshift of basal to bolus insulin for faster BG adjustment John Walsh - The Super Bolus
TBBtotal base basal (sum of basal rate within 24 hours)  
TBRtemporary basal rate  
TDDtotal daily dose (bolus + basal per day)  
TTtemporary target
temporary increase/decrease of BG target (range)		 Wiki - temp targets
UAMunannounced meals - detection of significant increase in glucose levels due to meals, adrenaline or other influences and attempt to adjust this with SMBSMBWiki - SMB
Virtual pumpoption to try AAPS functions or for PWD using a pump model with no AndroidAPS driver for loopingLazo abierto 
Fondo de pantallaAndroidAPS background imagesee phones page
xDrip / xDrip+open source software to read CGM systems xDrip+
xDrip
Zero-temptemporary basal rate with 0% (no basal insulin delivery)  
See also https://openaps.readthedocs.io/en/latest/docs/Resources/glossary.html
diff --git a/docs/CROWDIN/es/Getting-Started/Safety-first.md b/docs/CROWDIN/es/Getting-Started/Safety-first.md deleted file mode 100644 index 0a9a23ebd182..000000000000 --- a/docs/CROWDIN/es/Getting-Started/Safety-first.md +++ /dev/null @@ -1,41 +0,0 @@ -# La seguridad es lo primero - -**When you decide to build your own artificial pancreas, it's always important to think about security and safety, and to understand the impact of all your actions** - -## General - -- AAPS is a just a tool to help you manage diabetes, it is not a fully automated system you can install and forget! -- Do not assume that AAPS will never make mistakes. Este dispositivo está tomando el control del suministro de tu insulina: supervísalo siempre, entiende cómo funciona y aprende a interpretar sus acciones. -- Remember that, once paired, the phone can instruct the pump to do anything. Only use this phone for AAPS and, if being used by a child, essential communications. No instales aplicaciones o juegos innecesarios (!!!!) que podrían introducir software malicioso como troyanos, virus o bots que podrían interferir con tu sistema. -- Install all security updates provided by your phone manufacturer and Google. -- You might also need to change your diabetes habits as you change your therapy by using a closed loop system. P.e. some people report, they need less hypo treatments as AAPS has already reduced insulin. - -## Comunicaciones SMS - -- AndroidAPS te permite controlar el teléfono de un niño de forma remota mediante mensajes de texto. Si activas esta función "SMS Communicator", recuerda siempre que el teléfono configurado para dar comandos remotos podría ser robado. Por lo que protege siempre el móvil con código PIN. -- AndroidAPS también te avisará por mensaje de texto si tus comandos remotos, tales como bolos o cambios de perfil, se han llevado a cabo. Es aconsejable, por seguridad, configurar esta función para que los textos de confirmación se envíen al menos a dos números de teléfono diferentes, así si falla (o ha sido robado) uno, quedará el otro. - -(Safety-first-aaps-can-also-be-used-by-blind-people)= -## AAPS can also be used by blind people - -On Android devices TalkBack is part of the operating system. It is a program for screen orientation via voice output. With TalkBack you can operate your smartphone as well as AAPS blind. - -We users create the AAPS app ourselves with Android Studio. Many use Microsoft Windows for this purpose, where there is the Screenreader analogous to TalkBack. Since Android Studio is a Java application, the "Java Access Bridge" component must be enabled in the Control Panel. Otherwise, the screen reader of the PC will not speak in Android Studio. - -To do this, please proceed as follows: - -- Press WINDOWSTASTE and enter "Control Panel" in the search field, open with Enter. It opens: "All Control Panel Items". -- Press the letter C to get to "Center for Ease of Use", open with Enter. -- Then open "Use computer without a screen" with Enter. -- There, at the bottom, you will find the checkbox "Enable Java Access Bridge", select it. -- Done, just close the window! The screen reader should work now. - -```{note} -**IMPORTANT SAFETY NOTICE** - -The foundation of AAPS safety features discussed in this documentation is built on the safety features of the hardware used to build your system. Es importante que sólo utilice una bomba de insulina y una bomba de insulina y MCG aprobados por la FDA o CE, para cerrar un lazo de dosificación de insulina automatizado. Las modificaciones de hardware o software a estos componentes pueden causar una dosificación inesperada de la insulina, causando un riesgo significativo para el usuario. If you find or get offered broken, modified or self-made insulin pumps or CGM receivers, *do not use* these for creating an AAPS system. - -Además, es igualmente importante utilizar los suministros originales, como los insertadores, las canulas y los recipientes de insulina aprobados por el fabricante para su uso con la bomba o MCG. El uso de suministros no probados o modificados puede provocar inexactitud del MCG y errores de dosificación de la insulina. Insulina es muy peligrosa cuando se malinterpreta-por favor, no juegas con tu vida hackeando con tus suministros. - -Por último pero no por ello menos importante, no hay que tomar inhibidores SGLT-2 (gliflozins) ya que reducen incalculablemente los niveles de azúcar en sangre. La combinación con un sistema que reduce las tasas basales para aumentar la BG es especialmente peligrosa, ya que debido al gliflozin este aumento en BG podría no suceder y podría derivar en un peligroso estado de falta de insulina. -``` diff --git a/docs/CROWDIN/es/Getting-Started/Sample-Setup.md b/docs/CROWDIN/es/Getting-Started/Sample-Setup.md deleted file mode 100644 index 15cce2f54ba8..000000000000 --- a/docs/CROWDIN/es/Getting-Started/Sample-Setup.md +++ /dev/null @@ -1,151 +0,0 @@ -# Ejemplo de instalación: Samsung S7, DanaR, Dexcom G5 y el Smartwatch de Sony - -![Configuración de ejemplo](../images/SampleSetup.png) - -## Descripción - -En esta configuración, se utiliza el Samsung Galaxy S7 como centro de control del lazo. La aplicación Dexcom, ligeramente modificada, lee los valores de glucosa del sensor MCG Dexcom G6. Se utiliza AndroidAPS para controlar la bomba de insulina Dana R del fabricante coreano SOOIL a través de bluetooth. No se requieren otros dispositivos. - -Como la aplicación Dexcom sólo ofrece opciones de alarma limitadas, la aplicación de código abierto xDrip+ se utiliza para definir no sólo alarmas altas y bajas, sino también alarmas adicionales según las necesidades individuales. - -Opcionalmente se puede usar un smartwatch Android (en este ejemplo de instalación: Sony Smartwatch 3 (SWR50)) para mostrar los valores de glucosa y AndroidAPS en la muñeca. El reloj también puede ser utilizado para controlar AndroidAPS (por ejemplo, poner discretamente un bolus de comida). - -El sistema funciona sin conexión. Esto significa que no hay necesidad de una conexión de datos desde el móvil a Internet para funcionar. - -Sin embargo, los datos se subirán automáticamente a Nightscout "en la nube" cuando se establece una conexión de datos. De esta manera, puedes disponer de informes completos para la visita al médico o compartir los valores actuales con los miembros de la familia en cualquier momento. También es posible enviar datos a Nightscout sólo cuando se utiliza una conexión Wi-Fi (predefinida) con el fin de beneficiarse de los diferentes informes de Nightscout. - -## Componentes necesarios - -1. Samsung Galaxy S7 - - * Alternatives: see [list of tested phones and watches](https://docs.google.com/spreadsheets/d/1gZAsN6f0gv6tkgy9EBsYl0BQNhna0RDqA9QGycAqCQc/edit) for AndroidAPS - -2. [DanaRS](http://www.sooil.com/eng/product/) - - * Alternativas: - * [Accu-Check Combo](../Configuration/Accu-Chek-Combo-Pump.md) - * [Accu-Chek Insight](../Configuration/Accu-Chek-Insight-Pump.md) - * [DanaR](../Configuration/DanaR-Insulin-Pump.md) - * [Algunas bombas Medtronic antiguas (además necesarias: hardware RileyLink/Gnarl, Android Phone con bluetooth low energy/BLE-chipset)](../Configuration/MedtronicPump.md) - * Puede que otras bombas estén disponibles en el futuro, vea [futuros drivers de bomba ](Future-possible-Pump-Drivers.md) para obtener detalles. - -3. [Dexcom G6](https://dexcom.com) - - * Alternatives: see list of possible [BG sources](../Configuration/BG-Source.md) - -4. Opcional: Sony Smartwatch 3 (SWR50) - - * Alternatives: All [watches with Google Wear OS](https://wearos.google.com/intl/de_de/#find-your-watch) should work fine, for details see [list of tested phones and watches](https://docs.google.com/spreadsheets/d/1gZAsN6f0gv6tkgy9EBsYl0BQNhna0RDqA9QGycAqCQc/edit) for AndroidAPS (OS must be Android Wear) - -## Nightscout - -Consulta el detallado apartado [Nightscout setup ](../Installing-AndroidAPS/Nightscout.md) - -## Configuración del ordenador - -Para poder crear una aplicación Android desde el código abierto AAPS, disponible libremente, necesitas Android Studio en tu ordenador o portátil (Windows, Mac, Linux). Se pueden encontrar instrucciones detalladas en [construyendo la APK ](../Installing-AndroidAPS/Building-APK.md). - -Por favor, ten paciencia al instalar Android Studio, ya que el software descarga muchos datos adicionales una vez instalado en tu ordenador. - -## Configuración del Smartphone - -![Teléfono inteligente](../images/SampleSetupSmartphone.png) - -### Comprobar firmware del smartphone - -* Menu > Settings > Phone info > Software info: At least "Android-Version 8.0" (successfully tested up to Android version 8.0.0 Oreo - Samsung Experience Version 9.0) -* Para actualizar el firmware: menú > Preferencias > actualización de software - -### Permitir la instalación de aplicaciones de fuentes desconocidas - -Menú > Ajustes > Ajustes de seguridad > fuentes Desconocidas > deslizar hacia la derecha (= activo) - -Por razones de seguridad, esta configuración debería estar inactiva una vez que la instalación de todas las aplicaciones descritas aquí se haya completado. - -### Habilitar Bluetooth - -1. Menú > Configuración > Conexiones > Bluetooth > control deslizante hacia la derecha (= activo) -2. Menú > Ajustes > Conexiones > Ubicación > control deslizante a la derecha (= activo) - -Servicios de ubicación ("GPS") se debe activar para que Bluetooth funcione correctamente. - -### Instalar la aplicación Dexcom (versión modificada) - -![Aplicación Dexcom parcheada](../images/SampleSetupDexApp.png) - -La aplicación de Dexcom original de Google Play Store no funcionará porque no difunde los valores a otras aplicaciones. Por lo tanto, se requiere una versión ligeramente modificada por la comunidad. Sólo esta aplicación de Dexcom modificada se puede comunicar con AAPS. Además, la aplicación Dexcom modificada se puede utilizar con todos los smartphones de Android y no sólo con los que están en la lista de compatibilidad de [Dexcom](https://www.dexcom.com/dexcom-international-compatibility). - -To do this perform the following steps on your smartphone: - -1. Si la aplicación Dexcom original ya está instalada: - * Detener Sensor - * Uninstall app via Menu > Settings > Apps > Dexcom G6 Mobile > Uninstall -2. Download and install the [BYODA Dexcom ap](../Hardware/DexcomG6.md#if-using-g6-with-build-your-own-dexcom-app) -3. Start modified Dexcom G6 app, activate/calibrate the sensor according to the given instructions and wait until the warm-up phase is finished. -4. Once the modified Dexcom app shows actual glucose value, setup the warnings (hamburger menu on top left side of the screen) as follows: - * Urgent low `55mg/dl` / `3.1mmol/l` (cannot be disabled) - * Low `OFF` - * High `OFF` - * Rise rate `OFF` - * Fall rate `OFF` - * Signal loss `OFF` - -## Instalar AndroidAPS - -1. Follow the instructions to [build the APK](../Installing-AndroidAPS/Building-APK.md#generate-signed-apk) -2. [Transfer](../Installing-AndroidAPS/Building-APK.md#transfer-apk-to-smartphone) the generated APK to your phone -3. [Configurar AndroidAPS](../Configuration/Config-Builder.md) de acuerdo a sus necesidades utilizando el asistente de configuración o de forma manual -4. En esta configuración de ejemplo hemos utilizado (entre otros) - -* BG source: `Dexcom G6 App (patched)` -- click cock-wheel and activate `Upload BG data to NS` and `Send BG data to xDrip+` (see [BG source](../Configuration/BG-Source.md)) - -![G5 Settings](../images/SampleSetupG5Settings.png) - -* NS Client activated (see [Nightscout setup](../Installing-AndroidAPS/Nightscout.md)) - -## Instalar xDrip+ - -xDrip+ is another mature open source app that offers countless possibilities. In this setup, contrary to what the developers first wrote the app for, xDrip+ is not used to collect glucose data from the Dexcom G6, but only to output alarms and to display the current glucose value including the curve on the Android home screen in the widget. With xDrip+ the alarms can be set much more individually than with the Dexcom software, AAPS or Nightscout (no limitation in the selection of sounds, different alarms depending on day/night time etc.). - -1. Descarga la última versión estable de xDrip+ con tu smartphone - ¡no la versión de Google Play Store! -2. Instala xDrip+ seleccionando el archivo APK descargado. -3. Inicia xDrip+ y haz los siguientes ajustes (menú hamburguesa en la parte superior izquierda) - * Configuración > Alarmas y Alertas > Lista de nivel de Glucosa de Alertas > Crear Alertas (alta y baja) de acuerdo a sus necesidades. - * Las alarmas existentes pueden ser cambiadas con una pulsación larga en la alarma. - * Configuración > Alarmas y Alertas > Calibración de Alertas: deshabilitado (recordado a través de la modificación de Dexcom app) - * Ajustes > Hardware de Origen de Datos > 640G/EverSense - * Ajustes > Configuración Inter-app > Aceptar Calibraciones> `ON` - * Menu > Start sensor (is only "pro forma" and has nothing to do with the running G6 sensor. Esto es necesario, de lo contrario, aparecerá un mensaje de error con regularidad.) - -For more information about xDrip+, see here [BG source page](../Configuration/BG-Source.md). - -### Ejemplo de una configuración de alarma - -The "Urgent low alarm" (below 55 mg/dl resp. 3,1 mmol) is a standard alarm from the modified Dexcom app that cannot be disabled. - -![xDrip alarms](../images/SampleSetupxDripWarning.png) - -Tip for meetings / church visits / cinema etc..: - -If "Do not disturb" mode is activated in the Samsung Galaxy S7 (Menu > Settings > Sounds and vibration > Do not disturb: slider to right side (= active)), the phone only vibrates during urgent low alarm and does not issue an acoustic warning. For the other alarms set up via xDrip+ you can select whether the silent mode should be ignored (acoustic sound played) or not. - -## Inhabilitar opción de ahorro de energía - -On your Samsung Galaxy S7 go to Menu > Settings > Device Maintenance > Battery > Unmonitored Apps > + Add apps: Select the apps AndroidAPS, Dexcom G6 Mobile, xDrip+ and Android Wear (if smartwatch is used) one after the other - -## Opcional: Configuración de Sony Smartwatch 3 (SWR50) - -With an Android Wear smartwatch life with diabetes can be made even more inconspicuous. The watch can be used to display the current glucose level, the status of the loop etc. on the wrist. El reloj también puede ser utilizado para controlar AndroidAPS (por ejemplo, poner discretamente un bolus de comida). To do this, double tap the CGM value of the AAPSv2 watchface. The SWR50 usually runs for a full day until the battery needs to be recharged (same charger as the Samsung Galaxy S7: microUSB). - -![Smartwatches (Relojes inteligentes)](../images/SampleSetupSmartwatch.png) - -Details about the information displayed on the watchface can be found [here](../Configuration/Watchfaces.md). - -* Install the app "Android Wear" on your smartphone via the Google Play Store and connect the smartwatch according to the instructions there. -* En AAPS elija el menú de hamburguesa (esquina superior izquierda) > Configurar Builder > General (al final de la lista) > Usar > activar en el lado izquierdo, haga clic en el engranaje > Usar ajustes y activar `Controles desde el reloj` -* En tu reloj inteligente: Pulsación larga para cambiar el watchface y selecciona `AAPSv2` -* Si es necesario reiniciar ambos dispositivos una vez. - -## Ajustes de la bomba - -see [Dana RS pump](../Configuration/DanaRS-Insulin-Pump.md) \ No newline at end of file diff --git a/docs/CROWDIN/es/Getting-Started/WhatisAndroidAPS.md b/docs/CROWDIN/es/Getting-Started/WhatisAndroidAPS.md deleted file mode 100644 index 0cc385562d56..000000000000 --- a/docs/CROWDIN/es/Getting-Started/WhatisAndroidAPS.md +++ /dev/null @@ -1,39 +0,0 @@ -# What is a closed loop system with AAPS? - -AAPS is an app that acts as an artificial pancreas system (APS) on an Android smartphone. ¿Qué es un sistema de páncreas artificial? Se trata de un programa de software que tiene como objetivo hacer lo que un páncreas vivo hace: mantener los niveles de azúcar en la sangre dentro de límites saludables automáticamente. - -Un APS no puede hacer el trabajo tan bien como lo hace un páncreas biológico, pero puede hacer que la diabetes de tipo 1 sea más fácil de manejar usando dispositivos que están comercialmente disponibles y un software que es simple y seguro. Those devices include a continuous glucose monitor (CGM) to tell AAPS about your blood sugar levels and an insulin pump which AAPS controls to deliver appropriate doses of insulin. La aplicación se comunica con esos dispositivos a través de Bluetooth. Hace sus cálculos de dosificación usando un algoritmo, o un conjunto de reglas, desarrollado para otro sistema de páncreas artificial, llamado OpenAPS, que tiene miles de usuarios y ha acumulado millones de horas de uso. - -A note of caution: AAPS is not regulated by any medical authority in any country. Using AAPS is essentially carrying out a medical experiment on yourself. La configuración del sistema requiere determinación y conocimientos técnicos. Si no tienes el know-how técnico al principio, al final lo tendrá. Toda la información que necesitas puede ser encontrada en estos documentos, en otros sitios en línea, o de otros que ya lo han hecho, puedes preguntarles en grupos de Facebook u otros foros. Many people have successfully built AAPS and are now using it entirely safely, but it is essential that every user: - -- Builds the system themselves so that they thoroughly understand how it works -- Adjusts its individual dosage algorithm with his or her diabetes team to work nearly perfect -- Maintains and monitors the system to ensure it is working properly - -```{note} -**Disclaimer and Warning** - -- All information, thought, and code described here is intended for informational and educational purposes only. Actualmente Nightscout no dispone de HIPAA privacy compliance. Utilice Nightscout y AAPS bajo su propio riesgo y no utilice la información o el código para tomar decisiones médicas. -- El uso del código de github.com se realiza sin garantía ni soporte formal de ningún tipo. Por favor revise el repositorio de Licencia para más detalles. -- Todos los nombres de productos y empresas, marcas comerciales, marcas de servicio, marcas registradas y marcas de servicio registradas, son propiedad de sus respectivos titulares. Su uso aquí es informativo y no implica afiliación o pago por ello. - -Please note - this project has no association with and is not endorsed by: [SOOIL](http://www.sooil.com/eng/), [Dexcom](https://www.dexcom.com/), [Accu-Chek, Roche Diabetes Care](https://www.accu-chek.com/), [Insulet](https://www.insulet.com/) or [Medtronic](https://www.medtronic.com/). -``` - -Si estás listo para el reto, por favor lee en. - -## Primary goals behind AAPS - -- An app with safety built in. To read about the safety features of the algorithms, known as oref0 and oref1, click here () -- An all-in-one app for managing type 1 diabetes with an artificial pancreas and Nightscout -- An app to which users can easily add or remove modules as needed -- An app with different versions for specific locations and languages. -- An app which can be used in open- and closed-loop mode -- An app that is totally transparent: users can input parameters, see results, and make the final decision -- An app which is independent of particular pump drivers and contains a "virtual pump" so users can safely experiment before using it on themselves -- An app closely integrated with Nightscout -- An app in which the user is in control of safety constraints - -## Como empezar - -Por supuesto, todo este contenido es muy importante, pero puede ser en el principio muy confuso. A good orientation is given by the [Module Overview](../Module/module.md) and the [Objectives](../Usage/Objectives.html). diff --git a/docs/CROWDIN/es/Hardware/DexcomG4.md b/docs/CROWDIN/es/Hardware/DexcomG4.md deleted file mode 100644 index b3a3671b63bb..000000000000 --- a/docs/CROWDIN/es/Hardware/DexcomG4.md +++ /dev/null @@ -1,6 +0,0 @@ -# Dexcom G4 - -## Si utiliza G4 con el cable OTG ('tradicional ' Nightscout) -- If not already set up then download Nightscout Uploader app from the Play Store and follow instructions on [Nightscout](https://nightscout.github.io/). -- En las preferencias de AAPS, ingresa tu sitio web de Nightscout y la API Secret. -- Selecciona NSClient en la Tabla de configuraciones (ajuste en AAPS). diff --git a/docs/CROWDIN/es/Hardware/Smartwatch.md b/docs/CROWDIN/es/Hardware/Smartwatch.md deleted file mode 100644 index 4a87f5109630..000000000000 --- a/docs/CROWDIN/es/Hardware/Smartwatch.md +++ /dev/null @@ -1,10 +0,0 @@ -# Smartwatches (Relojes inteligentes) - -Los Smartwatches son opcionales, pero son muy útiles para algunos usuarios. More details are here: - -- [List of tested phones and smartwatches](../Getting-Started/Phones.md) -- [Watchfaces Wear OS](../Configuration/Watchfaces.md) -- [Troubleshooting Sony Smartwatch SW 3](../Usage/SonySW3.md) - -## Instructions for Building the AAPS Wear APK for Wear OS -https://androidaps.readthedocs.io/en/latest/remote-control.html#building-the-aaps-wear-apk diff --git a/docs/CROWDIN/es/Installing-AndroidAPS/Building-APK.md b/docs/CROWDIN/es/Installing-AndroidAPS/Building-APK.md deleted file mode 100644 index c2a586dd6f4d..000000000000 --- a/docs/CROWDIN/es/Installing-AndroidAPS/Building-APK.md +++ /dev/null @@ -1,369 +0,0 @@ -# Construyendo la APK - -## Construyela tú mismo en lugar de descargarla - -**AAPS is not available as download due to regulation for medical devices. It is legal to build the app for your own use, but you must not give a copy to others! Consulte la página [FAQ](../Getting-Started/FAQ.md) para obtener detalles.** - -## Notas importantes - -* Please use **[Android Studio Giraffe" (2022.3.1)](https://developer.android.com/studio/)** or newer to build the apk. -* [Windows 32-bit systems](troubleshooting_androidstudio-unable-to-start-daemon-process) are not supported by Android Studio - -(Building-APK-recommended-specification-of-computer-for-building-apk-file)= - -## Configuraciones de equipos recomendadas para generar el archivo apk - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
OS (Only 64 bit)Windows 8 or higherMac OS 10.14 or higherAny Linux supports Gnome, KDE, or Unity DE;  GNU C Library 2.31 or later

CPU (Only 64 bit)

x86_64 CPU architecture; 2nd generation Intel Core or newer, or AMD CPU with support for a
Windows Hypervisor		ARM-based chips, or 2nd generation Intel Core or newer with support for
Hypervisor.Framework		x86_64 CPU architecture; 2nd generation Intel Core or newer, or AMD processor with support for AMD Virtualization (AMD-V) and SSSE3

RAM

8GB or more

Disk

At least 30GB free space. SSD is recommended.

Resolution

1280 x 800 Minimum

Internet

Broadband

- -Please keep in mind that both **64 bit CPU and 64 bit OS are mandatory condition.** If your system DOES NOT meet this condition, you have to change affected hardware or software or the whole system. **It is strongly recommended to use SSD (Solid State Disk) instead of HDD (Hard Disk Drive) because it will take less time when you are building the APS installation apk file.** Recommended is just recommended and it is not a mandatory. However, you may still use a HDD when you are building apk file but note that the building process can take a long time to complete, although once started, you can leave it running unattended. - -* * * - -### Este artículo se divide en dos partes. - -* In the overview part there is an explanation on what steps are necessary to build the APK file. -* In the step by step walkthrough part you will find the screenshots of a concrete installation. Because the versions of Android Studio - the software development environment which we will use to build the APK - will change very quickly this will be not identical to your installation but it should give you a good starting point. Android Studio also runs on Windows, Mac OS X and Linux and there might be small differences in some aspects between each platform. If you find that something important is wrong or missing, please inform the facebook group "AAPS users" or in the Discord chat [Android APS](https://discord.gg/4fQUWHZ4Mw) so that we can have a look at this. - -## Inicio - -In general, the steps necessary to build the APK file: - -1. [Instalar Git](../Installing-AndroidAPS/git-install.md) -2. [Instalar Android Studio](Building-APK-install-android-studio) -3. [Establecer la ruta git en las preferencias de Android Studio](Building-APK-set-git-path-in-preferences) -4. [Download AAPS code](Building-APK-download-AAPS-code) -5. [Descargar Android SDK](Building-APK-download-android-sdk) -6. [Build the app](Building-APK-generate-signed-apk) (generate signed apk) -7. [Transferir el archivo apk a su teléfono](Building-APK-transfer-apk-to-smartphone) -8. [Identificar receptor si se utiliza xDrip+](xdrip-identify-receiver) - -## Step by step walkthrough - -Detailed description of the steps necessary to build the APK file. - -## Instalar git (si no lo tienes ya) - -Follow the manual on the [git installation page](../Installing-AndroidAPS/git-install.md). - -(Building-APK-install-android-studio)= - -## Instalar Android Studio - -The following screenshots have been taken from Android Studio Version Arctic Fox | 2020.3.1. Screens can change in future versions of Android Studio. But you should be able to find your way through. [Help from the community](../Where-To-Go-For-Help/Connect-with-other-users.md) is provided. - -One of the most important things when installing Android Studio: **Be patient!** During installation and setup Android Studio is downloading a lot of stuff which will take its time. - -Download [Android Studio from here](https://developer.android.com/studio/install.html) and install it on your computer. - -On first start you will find the setup wizard: - -Select "Do not import settings" as you have not used it before. - -![Do not import settings](../images/studioSetup/01_ImportSettings.png) - -Decide whether you want to share data with Google or not. - -![Share data with Google](../images/studioSetup/02_DataSharing.png) - -On the following screen click "Next". - -![Welcome screen](../images/studioSetup/03_Welcome.png) - -Select "Standard" installation and click "Next". - -![Standard installation](../images/studioSetup/04_InstallType.png) - -Select the theme for the user interface you like. (In this manual we used "Light".) Then click "Next". - -> ***Note:*** This is just the color scheme. You can select whatever you like (i.e. "Darcula" for dark mode). This selection has no influence on building the APK but the following screenshots might look different. - -![UI color scheme](../images/studioSetup/05_UITheme.png) - -Click "Next" on the "Verify Settings" dialog. - -![Verify settings](../images/studioSetup/06_Overview.png) - -Click on all three license agreement parts and select "Agree". When you have agreed to all, the "Finish" button will be enabled and you can "Finish". - - ![Agree license agreements](../images/studioSetup/07_LicenseAgreement.png) - - -Wait while Android Studio downloads additional components and be patient. Once everything is downloaded button "Finish" turns blue. Click the button now. - -![Downloading components](../images/studioSetup/08_Downloading.png) - -(Building-APK-download-AAPS-code)= - -## Download AAPS code - -* On the Android Studio welcome screen select "Projects" (1) on the left and then "Get from VCS" (2). - - ![Android Studio wizard](../images/studioSetup/20_ProjectVCS.png) - - * If you already opened Android Studio and do not see the welcome screen anymore select File (1) > New (2) > Project from Version Control... (3) - - ![Check out project from version control within Android Studio](../images/AndroidStudio_FileNew.PNG) - - * We will now tell Android Studio were to get the code from: - - * Make sure you have selected "Repository URL" on the left (1). - - * Check if "Git" is selected as version control (2). - * Copy and paste the URL ```https://github.com/nightscout/AndroidAPS``` to the main AAPS repository into the URL textbox (3). - * Choose the directory where you want to save the cloned code (4). - - ![Clone Git](../images/studioSetup/21_CloneURL.png) - -* Click button "Clone" (5). - - ![Clone repository](../images/studioSetup/22_Cloning.png) - -* Do not click "Background" while repository is cloned! - -* After the repository is cloned successfully, Android Studio will open the cloned project. - -* You will be asked whether you want to trust the project. Click on "Trust project"! - - ![Trust project](../images/studioSetup/23_TrustProject.png) - -* In the status bar at the bottom you will see the information that Android Studio is running background tasks. - - ![Background tasks](../images/studioSetup/24_GradleSyncRunning.png) - -* Windows only: Grant access if your firewall is asking for permission. - - ![Firewall permission java](../images/AndroidStudio361_18.png) - -* Once the background tasks are finished you will probably see an error saying that errors occurred (1) or (2) or (3). - - ![SDK licence](../images/studioSetup/25_SyncFailed.png) - - Don't worry, this will be solved soon! - -(Building-APK-set-git-path-in-preferences)= - -## Set git path in preferences - -Make sure [git is installed](../Installing-AndroidAPS/git-install.md) on your computer and you have restarted your computer since installing. - -On the Android Studio welcome screen click "Customize" (1) on the left and then select the link "All settings..." (2): - -![Android Studio settings from welcome screen](../images/studioSetup/10_WizardSettings.png) - -### Windows - -* As windows user, make sure you have restarted your computer after [installing Git](../Installing-AndroidAPS/git-install.md). - -* In the menu, go to File (1) > Settings (2) (or Android Studio > Preferences on Mac). - - ![Open settings](../images/studioSetup/30_Settings.png) - -* Double-click "Version Control" (1) to open the sub-menu. - -* Click Git (2). -* Make sure update method "Merge" (3) is selected. -* Check if Android Studio can locate path to git.exe automatically by clicking the button "Test" (4). - - ![Android Studio settings](../images/studioSetup/11_GitPath.png) - -* If automatic setting is successful git version will be displayed next to the path. - - ![Git version displayed](../images/studioSetup/12_GitVersion.png) - -* Eventually git.exe cannot be found automatically or the Test will result in an error (1): - - ![Git not found](../images/studioSetup/13_GitVersionError.png) - - In this case click on the folder icon (2). - -* Use [search function](https://www.tenforums.com/tutorials/94452-search-file-explorer-windows-10-a.html) in windows explorer to find "git.exe" if you are unsure where git has been installed. You are looking for a file named "git.exe", located in **\bin** folder. - -* Select path to git.exe and make sure you selected the one in ** \bin\ ** folder (3) and click "OK" (4). - - ![Select git manually](../images/studioSetup/14_GitManualSelection.png) - -* Check your selected git path again with the "Test" button as described above. - -* When the git version is displayed next to the path (see screenshot above), close settings window by clicking "OK" button (5). - -### Mac - -* Any git version should work. For example . -* Use homebrew to install git: ```$ brew install git```. -* For details on installing git see the [official git documentation](https://git-scm.com/book/en/v2/Getting-Started-Installing-Git). -* If you install git via homebrew there is no need to change any preferences. Just in case: They can be found here: Android Studio - Preferences. - -(Building-APK-download-android-sdk)= - -## Descargar Android SDK - -* In the menu, go to File (1) > Settings (2) (or Android Studio > Preferences on Mac). - - ![Open settings](../images/studioSetup/30_Settings.png) - -* Double-click on Languages & Frameworks to open its submenu (1). - -* Select Android SDK (2). -* Tick the box left of "Android 9.0 (Pie)" (3) (API Level 28). - - ![SDK settings](../images/studioSetup/31_AndroidSDK.png) - -* Confirm changes by clicking OK. - - ![Confirm SDK changes](../images/studioSetup/32_ConfirmSDK.png) - -* Wait until the SDK download and installation is finished. - - ![Wait during SDK installation](../images/studioSetup/34_DownloadSDK.png) - -* When SDK installation is completed the "Finish" button will turn blue. Click this button. - - ![Finish SDK installation](../images/studioSetup/35_DownloadSDKfinished.png) - -* Android Studio might recommend to update the gradle system. **Never update gradle!** This will lead to difficulties! - -* If you see an information on the lower right side of your Android Studio window that Android Gradle Plugin is ready to update click on the text "upgrade" (1). - - ![No gradle update](../images/studioSetup/36_GradleUpdateRequest.png) - -* In the dialog box the select "Don't remind me again for this project" (2). - - ![No gradle update](../images/studioSetup/37_GradleUpdateDeny.png) - -* Restart Android Studio before you continue. - -(Building-APK-generate-signed-apk)= - -## Generar APK firmado - -Signing means that you indicate your app to be your own creation but in a digital way as a kind of digital fingerprint within the app itself. That is necessary because Android has a rule that it only accepts signed code to run for security reasons. For more information on this topic, follow [this link](https://developer.android.com/studio/publish/app-signing.html#generate-key). - -* After Android Studio is started, wait until all background tasks are finished. - - ![Wait for background tasks](../images/studioSetup/40_BackgroundTasks.png) - - * ***Warning:*** If errors occur, do not continue with the following steps. \ Consult the [troubleshooting section](../Installing-AndroidAPS/troubleshooting_androidstudio) for known problems! - - ![Gradle Sync Error](../images/studioSetup/41_GradleSyncError.png) - -* Click "Build" (1) in the menu bar and select "Generate Signed Bundle / APK..." (2). - - ![Crear apk](../images/studioSetup/42_MenuBuild.png) - -* Select "APK" (1) instead of "Android App Bundle" and click "Next" (2). - - ![APK instead of bundle](../images/studioSetup/43_Apk.png) - -* Make sure that module is set to "AndroidAPS.app" (1). - -* Click "Create new..." (2) to start creating your key store. - - ***Note:*** A key store in this case is nothing more than a file in which the information for signing is stored. It is encrypted and the information is secured with passwords. - - ![Create key store](../images/studioSetup/44_KeystoreNew.png) - -* Click the folder symbol to select a path on your computer for your key store. - - ![Create key store](../images/studioSetup/45_KeystoreDialog.png) - -* Select the path where your key store shall be saved (1). - - ![Create key store](../images/studioSetup/46_KeystorePath.png) - - ***Warning: Do not save in same folder as project. You must use a different directory!*** A good location would be your home folder. - -* Type a file name for your key store (2) and confirm with "OK" (3). - -* Enter (2) and confirm (3) the password for your key store. ![Select key store path](../images/studioSetup/47_KeystoreDialog.png) - - ***Note:*** Passwords for key store and key do not have to be very sophisticated. Make sure to remember those or make a note in a safe place. In case you will not remember your passwords in the future, see [troubleshooting for lost key store](troubleshooting_androidstudio-lost-keystore). - -* Enter an alias (4) for your key. Choose whatever you like. - -* Enter (5) and confirm (6) the password for your key - -* Validity (7) is 25 years by default. You do not have to change the default value. - -* First and last name must be entered (8). All other information is optional. - -* Click "OK" (9) when you are done. - -* Make sure the box to remember passwords is checked (1). So you don't have to enter them again next time you build the apk (i.e. when updating to a new AAPS version). - -* Click "Next" (2). - - ![Remember passwords](../images/studioSetup/48_KeystoreSave.png) - -* Select build variant "fullRelease" (1) and press "Finish". - - ![Select build variant](../images/studioSetup/49_BuildVariant.png) - -* Android Studio will show "Gradle Build running" at the bottom. This takes some time, depending on your computer and internet connection. **Be patient!** - - ![Gradle Running](../images/studioSetup/50_GradleRunning.png) - -* Android Studio will display the information "Generate Signed APK" after build is finished. - - ![Build finished](../images/studioSetup/51_BuildFinished.png) - -* In case build was not successful refer to the [troubleshooting section](../Installing-AndroidAPS/troubleshooting_androidstudio). - -* Click on the notification to expand it. - -* Click on the link "locate". - - ![Locate build](../images/studioSetup/52_BuildLocate.png) - - * If the notification is gone, you can always open the "Event log" and select the same link there. ![Build successfully - event log](../images/studioSetup/53_EventLog.png) - -* Your file manager/explorer will open. Navigate to the directory "full" (1) > "release" (2). - - ![File location apk](../images/studioSetup/54_APKlocation.png) - -* "app-full-release.apk" (3) is the file you are looking for! - -(Building-APK-transfer-apk-to-smartphone)= - -## Transferir APK a smartphone - -Easiest way to transfer app-full-release.apk to your phone is via [USB cable or Google Drive](https://support.google.com/android/answer/9064445?hl=en). Please note that transfer by mail might cause difficulties and is not the preferred way. - -On your phone you have to allow installation from unknown sources. Manuals how to do this can be found on the internet (i.e. [here](https://www.expressvpn.com/de/support/vpn-setup/enable-apk-installs-android/) or [here](https://www.androidcentral.com/unknown-sources)). - -## Solución de problemas - -See separate page [troubleshooting Android Studio](../Installing-AndroidAPS/troubleshooting_androidstudio). \ No newline at end of file diff --git a/docs/CROWDIN/es/Resources/index.md b/docs/CROWDIN/es/Resources/index.md deleted file mode 100644 index 00f743ea25cd..000000000000 --- a/docs/CROWDIN/es/Resources/index.md +++ /dev/null @@ -1,8 +0,0 @@ -# Recursos - -```{toctree} -:glob: true -:maxdepth: 4 - -clinician-guide-to-AndroidAPS -``` diff --git a/docs/CROWDIN/es/Sandbox/sandbox2.md b/docs/CROWDIN/es/Sandbox/sandbox2.md deleted file mode 100644 index 91b863d52262..000000000000 --- a/docs/CROWDIN/es/Sandbox/sandbox2.md +++ /dev/null @@ -1,43 +0,0 @@ -# internal sandbox file 2 for testing - -```{admonition} no need to translate this -:class: note - -No need to translate this. -``` - -This is an internal sandbox file for the documentation team to test - -1. markdown syntax and - -1. background process for - 1. CROWDIN translation and - 2. Read The Docs deployment. - -You can dirctly jump from here to the first label in the sandbox1.md file - ["Jump"](sandbox1-this-is-a-test). - -You can dirctly jump from here to the second label in this file - ["Jump"](sandbox1-this-is-another-test). - -Here you can jump to the first sandbox file - ["Jump"](./sandbox1.md). - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -(sandbox2-this-is-a-test)= -## This is a test - -This is a test if labels must be unique. - -### This is spare information from the docs - -cut from index: - -There are "limits" set in place when you are first beginning your AAPS journey. Estos límites de seguridad se han desarrollado a lo largo de muchos años mediante observaciones de los errores inadvertidos que los nuevos usuarios son más propensos a cometer cuando aprenden por primera vez a configurar, construir y luego loopear con éxito con AAPS. La mayoría de las veces, estos errores ocurren simplemente porque el usuario estaba tan emocionado por comenzar a usar el sistema que pueden haber olvidado sentarse y dedicar el tiempo necesario para comprender completamente la información dentro de esta documentación. - - -### spare info from the overview to put into "preparing" - -Dado que los requisitos son muy diferentes a cualquier cosa que hayas configurado en el pasado, recomendamos que sigas las instrucciones paso a paso las primeras veces que construyas la aplicación, para que tengas una mejor idea de cómo se supone que debe comportarse el proceso de construcción de la aplicación cuando se siguen todas las instrucciones exactamente. Por favor, recuerda tomarte tu tiempo. Más adelante, esto irá muy rápido cuando construyas la aplicación nuevamente para una nueva versión. De esta manera, tendrás una mayor probabilidad de darte cuenta cuando algo no vaya según lo planeado antes de que muchas etapas estén fuera de lugar. Es importante guardar tu archivo keystore (.jks, utilizado para firmar tu aplicación) en un lugar seguro, para que siempre puedas usar ese mismo archivo de almacén de claves y contraseña cada vez que se te pida crear una nueva versión actualizada de AAPS. Este archivo es lo que garantiza que cada nueva versión de la aplicación 'recuerde' toda la información que le has proporcionado en versiones anteriores de la aplicación y, por lo tanto, asegura que las actualizaciones se realicen de la manera más fluida posible. En promedio, puedes asumir que habrá una nueva versión y de 2 a 3 actualizaciones necesarias por año. Este número se basa en la experiencia y puede cambiar en el futuro. Pero al menos queremos brindarte una guía general sobre qué esperar. Cuando tengas más experiencia en la construcción de versiones actualizadas de la aplicación AAPS, todos los pasos que se requieren en la construcción de una aplicación actualizada solo tomarán de 15 a 30 minutos, de promedio. Sin embargo, al principio puede haber una curva de aprendizaje bastante pronunciada, ya que estos pasos no siempre son intuitivos para los nuevos usuarios. Así que no te frustres si descubres que te lleva medio día o un día completo, con algo de ayuda de la comunidad, antes de que finalmente termines con el proceso de actualización. Si descubres que te estás frustrando mucho, simplemente toma un breve descanso, y muchas veces, después de dar un paseo por la calle, te darás cuenta de que estás en mejores condiciones para abordar el problema nuevamente. diff --git a/docs/CROWDIN/es/Usage/Objectives.md b/docs/CROWDIN/es/Usage/Objectives.md deleted file mode 100644 index 99e2b5f4c2cc..000000000000 --- a/docs/CROWDIN/es/Usage/Objectives.md +++ /dev/null @@ -1,184 +0,0 @@ -# Objetivos - -AAPS has a series of Objectives that need to be completed to walk you through the features and settings of safe looping. Estos, aseguran que ha configurado correctamente todo lo detallado en las secciones anteriores, y que comprende lo que está haciendo su sistema y por qué, de modo que pueda confiar en él. - -If you are **upgrading phones** then you can [export your settings](../Usage/ExportImportSettings.md) to keep your progress through the objectives. Not only will your progress through the objectives be saved, but also your safety settings such as max bolus etc. If you do not export and import your settings then you will need to start the objectives from the beginning again. It is a good idea to [backup your settings](../Usage/ExportImportSettings.html) frequently just in case. - -If you want to go back in objectives see [explanation below](Objectives-go-back-in-objectives). - -## Objetivo 1: Establecimiento de la visualización y la supervisión, análisis de las basales y las tasas - -- Select the right blood glucose source for your setup. See [BG Source](../Configuration/BG-Source.md) for more information. -- Select the right Pump in ConfigBuilder (select Virtual Pump if you are using a pump model with no AAPS driver for looping) to ensure your pump status can communicate with AAPS. -- If using DanaR pump then ensure you have followed [DanaR Insulin Pump](../Configuration/DanaR-Insulin-Pump.md) instructions to ensure the link between pump and AAPS. -- You need to establish a data repository/reporting platform to complete this objective. That can be accomplished with either Nightscout or Tidepool (or both). Follow instructions at the [Nightscout](../Installing-AndroidAPS/Nightscout.md) or [Tidepool](../Installing-AndroidAPS/Tidepool.md) page for instructions. -- Note that URL in NSClient must be **WITHOUT /api/v1/** at the end - see [NSClient settings in Preferences](Preferences-nsclient). - -*You may need to wait for the next blood glucose reading to arrive before AAPS will recognise it.* - -## Objective 2: Learn how to control AAPS - -- Perform several actions in AAPS as described in this objective. - -- Click on the orange text "Not completed yet" to access the to-dos. - -- Links will be provided to guide you in case you are not familiar with a specific action yet. - - ```{image} ../images/Objective2_V2_5.png - :alt: Captura de pantalla de objetivo 2 - ``` - -(Objectives-objective-3-prove-your-knowledge)= - -## Objetivo 3: Demuestra tus conocimientos - -Objective 3 is a multiple choice test based on questions designed to test your theoretical knowledge of **AAPS**. - -Some users find Objective 3 to be the most difficult objective to complete. Please do read the AAPS documents in conjunction with the questions. If you are genuinely stuck after researching the **AAPS** documents, please search or ask for help on the Facebook or Discord group. These groups can provide friendly hints or redirect you to the relevant part of the **AAPS** documents. - -To proceed with Objective 3, click on the orange text “Not completed yet” to access the relevant question. Please read each question and select your answer(s). - - - -Within each question, a hyperlink to the **AAPS** documents will guide you to the relevant section of the document which you should read in order to locate the correct answer. - - -[Obj3_Screenshot 2023-12-05 223422](https://github.com/openaps/AndroidAPSdocs/assets/137224335/77347516-e24e-459d-98ab-acbb49a3d4e8)![imagen](https://github.com/openaps/AndroidAPSdocs/assets/137224335/ca756b8e-efbc-4427-b281-ac953ce16718) - - - -For each question, there may be more than one answer that is correct! If an incorrect answer is selected, the question will be time locked for a certain amount of time (60 minutes) before you can go back and answer the question. - - -After updating to a new version of **AAPS**, new questions may be added to cover a prevalent issue picked up by **AAPS** or alternatively to test your knowledge of a new feature of **AAPS** as released. - - -When **AAPS** is installed for the first time, you will have to complete Objective 3 entirely in order to move onto Objective 4. Each objective is required to be completed in sequential order. New features will gradually be unlocked as progress is made through the objectives. - -__What happens if new questions are added later to Objective 3?__ From time to time, new features are added to **AAPS** which may require a new question to be added to Objective 3. As a result, any new question added to Objective 3 will be marked as “incomplete” because **AAPS** will require you to action this. As each Objective is independent, you will not lose the existing functionality of **AAPS** providing the other objectives remain completed. - - -## Objetivo 4: Iniciar en un lazo abierto - -- Select Open Loop either from Preferences, or by pressing and holding the Loop button in top left of the home screen. -- Work through the [Preferences](../Configuration/Preferences.md) to set up for you. -- Manually enact at least 20 of the temporary basal rate suggestions over a period of 7 days; input them to your pump and confirm in AAPS that you have accepted them. Ensure this data shows in AAPS and Nightscout. -- Enable [temp targets](../Usage/temptarget.md) if necessary. Utilice los objetivos temporales de hipoglucemia para evitar que el sistema se corrija demasiado fuerte debido a un aumento de la glucosa en sangre tras una hipoglucemia. - -### Reducir el número de notificaciones - -- To reduce the Number of decisions to be made while in Open Loop set wide target range like 90 - 150 mg/dl or 5,0 - 8,5 mmol/l. - -- You might even want to wider upper limit (or disable Open Loop) at night. - -- In Preferences you can set a minimum percentage for suggestion of basal rate change. - - ```{image} ../images/OpenLoop_MinimalRequestChange2.png - :alt: Open Loop minimal request change - ``` - -- Also, you do not need to act every 5 minutes on all suggestions... - -## Objetivo 5: Comprensión de su lazo abierto, incluidas sus recomendaciones basales temporales - -- Start to understand the thinking behind the temp basal recommendations by looking at the [determine basal logic](https://openaps.readthedocs.io/en/latest/docs/While%20You%20Wait%20For%20Gear/Understand-determine-basal.html) and both the [forecast line in AAPS homescreen](Screenshots-prediction-lines)/Nightscout and the summary of outputs from the calculations in your OpenAPS tab. - -Usted querrá establecer su objetivo más alto de lo normal hasta que esté seguro en los cálculos y los ajustes. El sistema permite - -- a low target to be a minimum of 4 mmol (72 mg/dl) or maximum of 10 mmol (180 mg/dl) -- a high target to be a minimum of 5 mmol (90 mg/dl) and maximum of 15 mmol (225 mg/dl) -- a temporary target as a single value can be anywhere in the range of 4 mmol to 15 mmol (72 mg/dl to 225 mg/dl) - -El objetivo es el valor en el que se basan los cálculos, y no es el mismo que al que apuntamos para mantener la glucosa dentro del rango. If your target is very wide (say, 3 or more mmol \[50 mg/dl or more\] wide), you will often find little AAPS action. Esto se debe a que eventualmente se prevé que la glucosa en sangre esté en algún lugar de esa amplia gama y, por lo tanto, no se sugieran muchas variaciones de basales temporales. - -You may want to experiment with adjusting your targets to be a closer together range (say, 1 or less mmol \[20 mg/dl or less\] wide) and observe how the behavior of your system changes as a result. - -You can view a wider range (green lines) on the graph for the values you aim to keep your blood glucose within by entering different values in [Preferences](../Configuration/Preferences.md) > Range for Visualisation. - -```{image} ../images/sign_stop.png -:alt: Señal de parada -``` - -### Parar aquí si usted está lazo abierto con una bomba virtual - no haga clic en Comprobar al final de este objetivo. - -```{image} ../images/blank.png -:alt: en blanco -``` - -(Objectives-objective-6-starting-to-close-the-loop-with-low-glucose-suspend)= -## Objetivo 6: Empezando a cerrar el lazo con Baja Glucosa Suspender - -```{image} ../images/sign_warning.png -:alt: Señal de advertencia -``` - -### Closed loop will not correct high BG values in objective 6 as it is limited to low glucose suspend. High BG values have to be corrected manually by you! - -- Prerequisite: You need a good profile (basal, ISF, IC) already working in AAPS to start with Loop in Low Glucose Suspend mode. Otherwise you can run in a hypo which you have to manually correct. This will help you a lot to avoid having to treat a low glucose over a period of 5 days. **If you are still having frequent or severe low glucose episodes then consider refining your DIA, basal, ISF and carb ratios and do NOT start objective 6 at this time.** -- You don't have to change your settings now. During objective 6, the maxIOB setting is internally set to zero automatically. **This override will be reversed when moving to objective 7.** -- The system will override your maxIOB settings to zero, which means if blood glucose is dropping it can reduce basal for you. If blood glucose is rising then it will only increase basal if the basal IOB is negative from a previous Low Glucose Suspend. Otherwise basal rates will remain the same as your selected profile. **That means that you have to manually handle high values with insulin corrections.** -- If your basal IOB is negative (see screenshot below) a TBR > 100% can be issued also in objective 6. - -```{image} ../images/Objective6_negIOB.png -:alt: Example negative IOB -``` - -- Set your target range slightly higher than you usually aim for, just to be safe and have a bit more scurity buffer. -- Enable 'Low Glucose Suspend' mode either by by pressing and holding the Loop icon at the top right corner of the home screen and selecting the Loop - LGS mode icon. -- Watch how temporary basals are active by viewing the blue basal text on the homescreen or the blue basal render on the homescreen graph. -- You may temporarily experience spikes following treated hypos without the ability to increase basal on the rebound. - -(Objectives-objective-7-tuning-the-closed-loop-raising-max-iob-above-0-and-gradually-lowering-bg-targets)= -## Objective 7: Tuning the closed loop, raising maxIOB above 0 and gradually lowering BG targets - -- Select 'Closed Loop' either from [Preferences](../Configuration/Preferences.md) or by pressing and holding the Loop icon at the top right corner of the home screen, over a period of 1 day. - -- Raise your 'Maximum total IOB OpenAPS can’t go over' (in OpenAPS called 'max-iob') above 0. The default recommendation is "average mealbolus + 3x max daily basal" (for the SMB algorithm) or "3x max daily basal" (for the older AMA algorithm) but you should slowly work up to this until you know your settings work for you (max daily basal = the maximum hourly value in any time segment of the day). - - Esta recomendación debe considerarse como un punto de partida. If you set to the 3x and you are seeing moves that push you too hard and fast then lower that number. If you are very resistant, raise it very little at a time. - - ```{image} ../images/MaxDailyBasal2.png - :alt: max basal diaria - ``` - -- Once confident on how much IOB suits your looping patterns, then reduce your targets to your desired level. - -(Objectives-objective-8-adjust-basals-and-ratios-if-needed-and-then-enable-autosens)= -## Objetivo 8: ajustar las basales y proporciones si es necesario, y luego habilitar el autosensado - -- You can use [autotune](https://openaps.readthedocs.io/en/latest/docs/Customize-Iterate/autotune.html) as a one off to check your basals remain accurate or do a traditional basal test. -- Enable [autosens](../Usage/Open-APS-features.md) over a period of 7 days and watch the white line on the homescreen graph show how your sensitivity to insulin may be rising or falling as a result of exercise or hormones etc. and keep an eye in the OpenAPS report tab how AAPS is adjusting the basals and/or targets accordingly. - -*Don’t forget to record your looping in* [this form](https://bit.ly/nowlooping) *logging AAPS as your type of DIY loop software, if you have not already done so.* - -(Objectives-objective-9-enabling-additional-oref1-features-for-daytime-use-such-as-super-micro-bolus-smb)= -## Objective 9: Enabling additional oref1 features for daytime use, such as super micro bolus (SMB) - -- You must read the [SMB chapter in this wiki](Open-APS-features-super-micro-bolus-smb) and [chapter oref1 in openAPSdocs](https://openaps.readthedocs.io/en/latest/docs/Customize-Iterate/oref1.html) to understand how SMB works, especially what's the idea behind zero-temping. -- Then you ought to [rise maxIOB](Open-APS-features-maximum-total-iob-openaps-cant-go-over-openaps-max-iob) to get SMBs working fine. maxIOB ahora incluye todo IOB, no sólo la basal añadida. That is, if given a bolus of 8 U for a meal and maxIOB is 7 U, no SMBs will be delivered until IOB drops below 7 U. A good start is maxIOB = average mealbolus + 3x max daily basal (max daily basal = the maximum hourly value in any time segment of the day - see [objective 7](Objectives-objective-7-tuning-the-closed-loop-raising-max-iob-above-0-and-gradually-lowering-bg-targets) for an illustration) -- min_5m_carbimpact default in absorption settings has changed from 3 to 8 going from AMA to SMB. If you are upgrading from AMA to SMB, you have to change it manually. - -(Objectives-objective-10-automation)= -## Objective 10: Automation - -- You have to start objective 10 to be able to use [Automation](../Usage/Automation.md). -- Make sure you have completed all objectives including exam [Objectives-objective-3-prove-your-knowledge](Objectives#objective-3-prove-your-knowledge). -- Completing previous objectives will not effect other objectives you have already finished. You will keep all finished objectives! - -(Objectives-objective-11-DynamicISF)= -## Objective 11: Additional Features such as DynamicISF - -- You have to start objective 11 to be able to use [DynamicISF](../Usage/Open-APS-features.md) - -(Objectives-go-back-in-objectives)= -## Go back in objectives - -If you want to go back in objectives for whatever reason you can do so by clicking at "clear finished". - -```{image} ../images/Objective_ClearFinished.png -:alt: Go back in objectives -``` - -## Objectives in Android APS before version 3.0 - -One objective was removed when Android APS 3.0 was released. Users of Android APS version 2.8.2.1 who are on older Android software (i.e. earlier than version 9) will be using an older set of objectives which can be found [here](../Usage/Objectives_old.md). diff --git a/docs/CROWDIN/es/Usage/Objectives_old.md b/docs/CROWDIN/es/Usage/Objectives_old.md deleted file mode 100644 index 07cf4f6ba827..000000000000 --- a/docs/CROWDIN/es/Usage/Objectives_old.md +++ /dev/null @@ -1,152 +0,0 @@ -# Objectives as of Android APS 2.8.2.1 - -This is not the latest version of the Android APS Objectives. This page details the Objectives that were in place prior to version 3.0. Anyone using an older version of Android (i.e. prior to Android 9) and Android APS version 2.8.2.1 should refer to this page. - -Please see [this page](../Usage/Objectives.md) for the current set of Objectives. - -AndroidAPS tiene una serie de Objetivos que deben completarse para guiarlo a través de las características y configuraciones de lazo cerrado de manera segura. Estos, aseguran que ha configurado correctamente todo lo detallado en las secciones anteriores, y que comprende lo que está haciendo su sistema y por qué, de modo que pueda confiar en él. - -If you are **upgrading phones** then you can [export your settings](../Usage/ExportImportSettings.md) to keep your progress through the objectives. Not only will your progress through the objectives be saved, but also your safety settings such as max bolus etc. If you do not export and import your settings then you will need to start the objectives from the beginning again. It is a good idea to [backup your settings](../Usage/ExportImportSettings.html) frequently just in case. - -If you want to go back in objectives see [explanation below](../Usage/Objectives.md#go-back-in-objectives). - -## Objetivo 1: Establecimiento de la visualización y la supervisión, análisis de las basales y las tasas - -- Select the right blood glucose source for your setup. See [BG Source](../Configuration/BG-Source.md) for more information. -- Select the right Pump in ConfigBuilder (select Virtual Pump if you are using a pump model with no AndroidAPS driver for looping) to ensure your pump status can communicate with AndroidAPS. -- If using DanaR pump then ensure you have followed [DanaR Insulin Pump](../Configuration/DanaR-Insulin-Pump.md) instructions to ensure the link between pump and AndroidAPS. -- Follow instructions in [Nightscout](../Installing-AndroidAPS/Nightscout.md) page to ensure Nightscout can receive and display this data. -- Note that URL in NSClient must be **WITHOUT /api/v1/** at the end - see [NSClient settings in Preferences](../Configuration/Preferences.md#nsclient). - -*You may need to wait for the next blood glucose reading to arrive before AndroidAPS will recognise it.* - -## Objetivo 2: Aprender a controlar AndroidAPS - -- Perform several actions in AndroidAPS as described in this objective. - -- Click on the orange text "Not completed yet" to access the to-dos. - -- Links will be provided to guide you in case you are not familiar with a specific action yet. - - ![Captura de pantalla de objetivo 2](../images/Objective2_V2_5.png) - -## Objetivo 3: Demuestra tus conocimientos - -- Pass a multiple-choice exam testing your AndroidAPS knowledge. - -- Click on the orange text "Not completed yet" to access the page with the question and answering options. - - ![Captura de pantalla de objetivo 3](../images/Objective3_V2_5.png) - -- Links will be provided to guide you in case you are unsure about the correct answers yet. - -- The questions for objective 3 have been completely rewritten by native speakers as of AAPS 2.8. The new ones cover the same basic topics plus a few new ones. - -- These new questions will lead to some not answered questions even though you have successfully completed objective 3 in previous versions. - -- Unanswered questions will affect you only if you start a new objective. In other words: If you have already completed all objectives you can wait and answer the new questions later without loosing AAPS functions. - -## Objetivo 4: Iniciar en un lazo abierto - -- Select Open Loop either from Preferences, or by pressing and holding the Loop button in top left of the home screen. -- Work through the [Preferences](../Configuration/Preferences.md) to set up for you. -- Manually enact at least 20 of the temporary basal rate suggestions over a period of 7 days; input them to your pump and confirm in AndroidAPS that you have accepted them. Asegúrese de que estos datos se muestran en AndroidAPS y Nightscout. -- Enable [temp targets](../Usage/temptarget.md) if necessary. Utilice los objetivos temporales de hipoglucemia para evitar que el sistema se corrija demasiado fuerte debido a un aumento de la glucosa en sangre tras una hipoglucemia. - -### Reducir el número de notificaciones - -- To reduce the Number of decisions to be made while in Open Loop set wide target range like 90 - 150 mg/dl or 5,0 - 8,5 mmol/l. - -- You might even want to wider upper limit (or disable Open Loop) at night. - -- In Preferences you can set a minimum percentage for suggestion of basal rate change. - - ![Open Loop minimal request change](../images/OpenLoop_MinimalRequestChange2.png) - -- Also, you do not need to act every 5 minutes on all suggestions... - -## Objetivo 5: Comprensión de su lazo abierto, incluidas sus recomendaciones basales temporales - -- Start to understand the thinking behind the temp basal recommendations by looking at the [determine basal logic](https://openaps.readthedocs.io/en/latest/docs/While%20You%20Wait%20For%20Gear/Understand-determine-basal.html) and both the [forecast line in AndroidAPS homescreen](../Getting-Started/Screenshots.md#prediction-lines)/Nightscout and the summary of outputs from the calculations in your OpenAPS tab. - -Usted querrá establecer su objetivo más alto de lo normal hasta que esté seguro en los cálculos y los ajustes. El sistema permite - -- a low target to be a minimum of 4 mmol (72 mg/dl) or maximum of 10 mmol (180 mg/dl) -- a high target to be a minimum of 5 mmol (90 mg/dl) and maximum of 15 mmol (225 mg/dl) -- a temporary target as a single value can be anywhere in the range of 4 mmol to 15 mmol (72 mg/dl to 225 mg/dl) - -El objetivo es el valor en el que se basan los cálculos, y no es el mismo que al que apuntamos para mantener la glucosa dentro del rango. If your target is very wide (say, 3 or more mmol \[50 mg/dl or more\] wide), you will often find little AAPS action. Esto se debe a que eventualmente se prevé que la glucosa en sangre esté en algún lugar de esa amplia gama y, por lo tanto, no se sugieran muchas variaciones de basales temporales. - -You may want to experiment with adjusting your targets to be a closer together range (say, 1 or less mmol \[20 mg/dl or less\] wide) and observe how the behavior of your system changes as a result. - -You can view a wider range (green lines) on the graph for the values you aim to keep your blood glucose within by entering different values in [Preferences](../Configuration/Preferences.md) > Range for Visualisation. - -![Señal de parada](../images/sign_stop.png) - -### Parar aquí si usted está lazo abierto con una bomba virtual - no haga clic en Comprobar al final de este objetivo. - -![en blanco](../images/blank.png) - -## Objetivo 6: Empezando a cerrar el lazo con Baja Glucosa Suspender - -![Señal de advertencia](../images/sign_warning.png) - -### El lazo cerrado no corregirá los valores de bg alto en el objetivo 6, ya que se limita a la suspensión por baja glucosa. ¡Los valores altos de BG tienen que ser corregidos manualmente por usted! - -- Select Closed Loop either from [Preferences](../Configuration/Preferences.md) or by pressing and holding the Open Loop button in the top left of the home screen. - -- Set your target range slightly higher than you usually aim for, just to be safe. - -- Watch how temporary basals are active by viewing the blue basal text on the homescreen or the blue basal render on the homescreen graph. - -- Ensure your settings have supported AndroidAPS to avoid having to treat a low glucose over a period of 5 days. Si sigue teniendo episodios frecuentes o graves de glucosa baja, considere la posibilidad de ajustar las proporciones de DIA, basal, ISF y tasa de carbohidratos. - -- You don't have to change your settings. Durante el objetivo 6, el valor de maxIOB se establece internamente en cero automáticamente. Esta alteración temporal se invertirá cuando se mueva al objetivo 7. - -- The system will override your maxIOB settings to zero, which means if blood glucose is dropping it can reduce basal for you, but if blood glucose is rising then it will only increase basal if the basal IOB is negative (from a previous Low Glucose Suspend), otherwise basal rates will remain the same as your selected profile. - - ![Example negative IOB](../images/Objective6_negIOB.png) - -- If your basal IOB is negative (see screenshot above) a TBR > 100% can be issued also in objective 6. - -- You may temporarily experience spikes following treated hypos without the ability to increase basal on the rebound. - -## Objetivo 7: Ajustar el lazo cerrado, elevando el IOB máximo por encima de 0 y reduciendo gradualmente los objetivos de BG - -- Raise your 'Maximum total IOB OpenAPS can’t go over' (in OpenAPS called 'max-iob') above 0 over a period of 1 day, the default recommendation is "average mealbolus + 3x max daily basal"(for SMB algorithm) or "3x max daily basal" (for older AMA algorithm) but you should slowly work up to this until you know your settings work for you (max daily basal = the maximum hourly value in any time segment of the day). - - Esta recomendación debe considerarse como un punto de partida. Si se establece en el 3x y se están viendo movimientos que le empuja a cambios fuertes y rápidos, a continuación, baje ese número. Si eres muy resistente, levanta un poco a la vez. - - ![max basal diaria](../images/MaxDailyBasal2.png) - -- Once confident on how much IOB suits your looping patterns then reduce your targets to your desired level. - -## Objetivo 8: ajustar las basales y proporciones si es necesario, y luego habilitar el autosensado - -- You can use [autotune](https://openaps.readthedocs.io/en/latest/docs/Customize-Iterate/autotune.html) as a one off to check your basals remain accurate or do a traditional basal test. -- Enable [autosens](../Usage/Open-APS-features.md) over a period of 7 days and watch the white line on the homescreen graph show how your sensitivity to insulin may be rising or falling as a result of exercise or hormones etc. and keep an eye in the OpenAPS report tab how AndroidAPS is adjusting the basals and/or targets accordingly. - -*Don’t forget to record your looping in* [this form](https://bit.ly/nowlooping) *logging AndroidAPS as your type of DIY loop software, if you have not already done so.* - -## Objective 9: Try additional features for daytime use and gain confidence in your closed loop system - -- Before AAPS version 2.7 meal assist (MA) was the basic algorithm for AAPS and completing objective 8 was necessary to activate [advanced meal assist (AMA)](../Usage/Open-APS-features.md#advanced-meal-assist-ama). -- As [advanced meal assist (AMA)](../Usage/Open-APS-features.md#advanced-meal-assist-ama) is the standard algorithm from AAPS version 2.7 onwards use the following 28 days to try features you haven't used yet and get more confident with you closed loop system. - -## Objective 10: Enabling additional oref1 features for daytime use, such as super micro bolus (SMB) - -- You must read the [SMB chapter in this wiki](../Usage/Open-APS-features.md#super-micro-bolus-smb) and [chapter oref1 in openAPSdocs](https://openaps.readthedocs.io/en/latest/docs/Customize-Iterate/oref1.html) to understand how SMB works, especially what's the idea behind zero-temping. -- Then you ought to [rise maxIOB](../Usage/Open-APS-features.md#maximum-total-iob-openaps-cant-go-over-openaps-max-iob) to get SMBs working fine. maxIOB ahora incluye todo IOB, no sólo la basal añadida. That is, if given a bolus of 8 U for a meal and maxIOB is 7 U, no SMBs will be delivered until IOB drops below 7 U. A good start is maxIOB = average mealbolus + 3x max daily basal (max daily basal = the maximum hourly value in any time segment of the day - see [objective 7](../Usage/Objectives#objective-7-tuning-the-closed-loop-raising-max-iob-above-0-and-gradually-lowering-bg-targets) for an illustration) -- min_5m_carbimpact default in absorption settings has changed from 3 to 8 going from AMA to SMB. If you are upgrading from AMA to SMB, you have to change it manually. - -## Objective 11: Automation - -- You have to start objective 11 to be able to use [Automation](../Usage/Automation.md). -- Make sure you have completed all objectives including exam [../Usage/Objectives.md#objective-3-prove-your-knowledge](../Usage/Objectives#objective-3-prove-your-knowledge). -- Completing previous objectives will not effect other objectives you have already finished. You will keep all finished objectives! - -## Go back in objectives - -If you want to go back in objectives for whatever reason you can do so by clicking at "clear finished". - -![Go back in objectives](../images/Objective_ClearFinished.png) diff --git a/docs/CROWDIN/es/Usage/Smoothing-Blood-Glucose-Data-in-xDrip.md b/docs/CROWDIN/es/Usage/Smoothing-Blood-Glucose-Data-in-xDrip.md deleted file mode 100644 index af2c4212ab92..000000000000 --- a/docs/CROWDIN/es/Usage/Smoothing-Blood-Glucose-Data-in-xDrip.md +++ /dev/null @@ -1,33 +0,0 @@ -(Smoothing-Blood-Glucose-Data-in-xDrip-smoothing-blood-glucose-data)= - -# Suavizado de los datos de glucosa en la sangre - -If BG data is jumpy/noisy, AAPS may dose insulin incorrectly resulting in high or low BG. For this reason it’s important to disable the loop until the problem is resolved. Depending on your CGM such issues may be due to the CGM’s configuration or sensor problems/site issues. You may need to replace your CGM sensor to resolve this. - -Some CGM systems have internal algorithms to detect the noise level in the readings and AAPS can use this information to avoid giving SMBs if the BG data is too unreliable. However, some CGMs do not transmit this data and for these BG sources 'Enable SMB always' and 'Enable SMB after carbs' are disabled for safety reasons. - -## Dexcom sensors - -### Build Your Own Dexcom App - -When using [BYODA](DexcomG6-if-using-g6-with-build-your-own-dexcom-app) your BG data is smooth and consistent. Furthermore you can take advantage of Dexcom back-smoothing. There are no restrictions in using SMBs, because the noise-level data is shared with AAPS. - -### xDrip+ with Dexcom G6 or Dexcom ONE - -Noise-level data and smooth BG readings are only shared with AAPS if you use xDrip+ [native mode](https://navid200.github.io/xDrip/docs/Native-Algorithm). Using native mode, there are no restrictions in using SMBs. - -### Dexcom G6 or Dexcom ONE with xDrip+ Companion Mode - -The noise-level data is not shared with AAPS using this method. Therefore 'Enable SMB always' and 'Enable SMB after carbs' are disabled. - -## Freestyle Libre sensors - -### xDrip+ with FreeStyle Libre - -None of the FreeStyle Libre systems (FSL1, FSL2, or FSL3) broadcast any information about the level of noise detected in the readings, and therefore 'Enable SMB always' and 'Enable SMB after carbs' are disabled for all setups using the FreeStyle Libre. - -In addition, many people have reported the FreeStyle Libre often produces noisy data. In xDrip+ there are a few options to help with this: - -**Smooth Sensor Noise.** In xDrip+ Settings > xDrip+ Display Settings ensure that Smooth Sensor Noise is turned on. This attempts to apply smoothing to noisy data. - -**Smooth Sensor Noise (Ultrasensitive).** If you are still seeing noisy data in xDrip+ you can apply more aggressive smoothing using the Smooth Sensor Noise (Ultrasensitive) setting. This will attempt to apply smoothing even on very low levels of detected noise. To do this, first enable [engineering mode](Enabling-Engineering-Mode-in-xDrip.md) in xDrip+. Then navigate to Settings > xDrip+ Display Settings and turn on Smooth Sensor Noise (Ultrasensitive). \ No newline at end of file diff --git a/docs/CROWDIN/es/Usage/autotune_b.md b/docs/CROWDIN/es/Usage/autotune_b.md deleted file mode 100644 index f69710bd4704..000000000000 --- a/docs/CROWDIN/es/Usage/autotune_b.md +++ /dev/null @@ -1,186 +0,0 @@ -# How to use Autotune plugin - -Documentation about Autotune algorythm can be found in [OpenAPS documentation](https://openaps.readthedocs.io/en/latest/docs/Customize-Iterate/autotune.html). - -Autotune plugin is an implementation of OpenAPS autotune algorythm within AAPS. - -**Currently Autotune Plugin is only available in dev branch with Engineering mode.** - -## Autotune user interface - -![Autotune default screen](../images/Autotune/Autotune_1b.png) - -- You can select in the Profile dropdown menu the input profile you want to tune (by default your current active profile is selected) - - Note: each time you select a new profile, previous results will be removed and Tune days parameter will be set to default value -- Then Tune days is to select the number of days used in calculation to tune your profile. The minimum value is 1 day and the maximum value 30 days. This number should not be too small to get correct iterative and smooth results (above 7 days for each calculation) - - Note: each time you change Tune days parameter, previous results will be removed -- Last Run il a link that recover your latest valid calculation. If you didn't launch Autotune on current day, or if previous results was removed with a modification of calculation parameter above, then you can recover parameters and results of the latest successfull run. -- Warning show you for example some information about selected profile (if you have several IC values or several ISF values) - - Note: Autotune calculation works with only a single IC and a single ISF value. There is currently no existing Autotune algorythm to tune a circadian IC or circadian ISF. If your input profile has several values, you can see in warning section the average value taken into account to tune your profile. -- Check Input Profile button open the Profile Viewer to allow you a quick verification of your profile (Units, DAI, IC, ISF, basal and target) - - Note: Autotune will only tune your IC (single value), ISF (single value) and basal (with circadian variation). Units, DAI and target will remain unchanged in output profile. - -- "Run Autotune" will launch Autotune calculation with selected profile and the number of Tune days - - Note: Autotune calculation can take a long time. Once launched, you can switch to another view (home, ...) and come back later in Autotune plugin to see results - -![Autotune Run start](../images/Autotune/Autotune_2b.png) - -- Then during the run you will see intermediate results below - - - Note: During run, settings are locked, so you cannot change anymore selected input profile or the number of day. You will have to wait the end of current calculation if you want to launch another run with other parameters. - - ![Autotune during run](../images/Autotune/Autotune_3b.png) - -- When Autotune calculation is finished, you will see the result (Tuned profile) and four buttons below. - -![Autotune Result](../images/Autotune/Autotune_4b.png) - -- It's important to always compare input profile (column "Profile"), output profile (column "Tuned") and the percentage of variation for each value (Column "%"). - -- For basal rates, you also have the number of "missing days". You have missing days when Autotune don't have enough data categorized as "Basal" to tune basal rate for this period (for example after each meal when you have carbs absorption). This number should be as low as possible especially when basal is important (for example during the night or at the end of the afternoon) - -- The "Compare profiles" button open the profile comparator view. Input profile is in blue, and output profile (named "Tuned") is in red. - - - Note: in the example below input profile has circadian variation for IC and ISF, but output calculated profile has a single value. If it's important for you to get a circadian output profile see [Circadian IC or ISF profile](#circadian-ic-or-isf-profile) below. - - ![Autotune Compare profiles](../images/Autotune/Autotune_5.png) - -- If you trust results (low percentage of variation between input profile and output profile), you can click on "Activate profile" button and then click on OK to validated. - - - Activate Tuned profile will automatically create a new profile "Tuned" in your Local profile plugin. - - If you already have a profile named "Tuned" in your local profile plugin, then this profile will be updated with calculated Autotune profile before the activation - - ![Autotune Activate profile](../images/Autotune/Autotune_6.png) - -- If you think Tuned profile must be adjusted (for example if you think some variation are too important), then you can click on "Copy to local profile" button - - - A new profile with the prefix "Tuned" and the date and time of the run will be created in local profile plugin - -![Autotune Copy to local profile](../images/Autotune/Autotune_7.png) - -- You can then select local profile to edit the Tuned profile (it will be selected by default when you open Local profile plugin) - - - the values in local profile will but rounded in the user interface to your pump capabilities - - ![Autotune local profile update](../images/Autotune/Autotune_8.png) - -- If you want to replace your input profile with Autotune result, click on "Update input profile" button and validate the Popup with OK - - - Note: if you click on "Activate profile" after "Update input profile", then you will activate your updated profile and not the default "Tuned" profile? - - ![Autotune Update input profile](../images/Autotune/Autotune_9.png) - -- If you have updated your input profile, then the "Update input profile" button is replaced by "Revert input profile" button (see screenshot below). You can that way immediatly see if your current input profile in Local profile plugin already include the result of last run or not. You also have the possibility to recover you input profile without autotune result with this button - - ![Autotune Update input profile](../images/Autotune/Autotune_10.png) - - - -## Autotune settings - -### Autotune plugin settings - -![Autotune default screen](../images/Autotune/Autotune_11.png) - -- Automation Switch Profile (default Off): see [Run Autotune with an automation rule](#run-autotune-with-an-automation-rule) below. If you change this setting to On, the input profile will automatically be updated by the Tuned profile, and it will be activated. - - **Be Carefull, you must trust and verified during several following days that after an update and activation of Tuned profile without modification, it improves your loop** - -- Categorize UAM as basal (default On): This setting is for the users using AndroidAPS without any carbs entered (Full UAM). It will prevent (when Off) to categorize UAM as basal. - - Note: if you have at least one hour of Carbs absorption detected during one day, then all data categorized as "UAM" will be categorized as basal, whatever this setting (On or Off) -- Number of days of data (default 5): You can define default value with this setting. Each time your select a new profile in Autotune plugin, Tune days parameter will be replaced by this default value -- Apply average result in circadian IC/ISF (default Off): see [Circadian IC or ISF profile](#circadian-ic-or-isf-profile) below. - -### Otros ajustes - -- Autotune also uses Max autosens ratio and Min autotsens ratio to limit variation. You can see and adjust these values in Config Builder > Sensitivity detection plugin > Settings > Advanced Settings - - ![Autotune default screen](../images/Autotune/Autotune_12.png) - - - -## Advanced feature - -### Circadian IC or ISF profile - -- If you have important variation of IC and/or you ISF in your profile, and you fully trust in your circadian time and variation, then you can set "Apply average result in circadiant IC/ISF" - - - Note that Autotune calculation will always be done with a single value, and circadian variation will not be tuned by Autotune. This setting only apply average variation calculated for IC and/or ISF on your circadian values - -- See on screenshot below Tuned profile with Apply average variation Off (on the left) and On (on the right) - - ![Autotune default screen](../images/Autotune/Autotune_13.png) - - - -### Tune specific days of the week - -- If you click on the checkbox with the eye on the right of "Rune days" parameter, you will see the day selection. You can specify which day of the week should be included in Autotune calculation (in screenshot below you can see an example for "working days" with Saturday and Sunday removed from autotune calculation) - - If the number of day included in Autotune calculation is lower than the number of Tune days, then you will see how many days will be included on the right of Tune days selector (10 days in the example below) - - This setting gives good results only if the number of remaining days is not to small (for example if you Tune a specific profile for week end days with only Sunday and Saturday selected, you should select a minimum of 21 or 28 Tune days to have 6 or 8 days included in Autotune calculation) - -![Autotune default screen](../images/Autotune/Autotune_14b.png) - -- During Autotune calculation, you can see the progress of the calculations ("Partial result day 3 / 10 tuned" on example below) - - ![Autotune default screen](../images/Autotune/Autotune_15b.png) - -## Run Autotune with an automation rule - -First step is to define correct trigger for an automation rule with Autotune: - -Note: for more information on how to set an automation rule, see [here](./Automation.rst). - -- You should select Recurring time trigger: only run Autotune once per day, and autotune is designed to be runned daily (each new run you shift one day later and quickly profile modification should be tiny) - - ![Autotune default screen](../images/Autotune/Autotune_16.png) - -- It's better at the beginning to run Autotune during the day to be able to check results. If you want to run Autotune during the night, you have to select in the trigger 4AM or later to include current day in next Autotune Calculation. - - ![Autotune default screen](../images/Autotune/Autotune_17.png) - -- Then you can select "Run Autotune" Action in the list - - ![Autotune default screen](../images/Autotune/Autotune_18.png) - -- You can then select Autotune Action to adjust parameters for your run. Default parameters are "Active Profile", default Tune days value defined in Autotune Plugin preferences, and All days are selected. - - ![Autotune default screen](../images/Autotune/Autotune_19b.png) - -- After a few days, if you fully trust Autotune results and percentage of modification is low, you can modify [Autotune settings](#autotune-plugin-settings) "Automation Switch Profile" to enabled to automatically update and activate profile tuned after calculation. - -Note: if you want to automatically tune profiles for specific days of the week (for example a profile for "Weekend days" and another one for "Working days"), then create one rule for each profile, select the same days in Trigger and in Autotune Action, Tune days must be high enough to be sure tuning will be done with at least 6 or 8 days, and don't forget to select time after 4AM in trigger... - -- See below an example of rule to tune "my profile" on all "Working days" with 14 Tune days selected (so only 10 days included in autotune calculation). - -![Autotune default screen](../images/Autotune/Autotune_20b.png) - - - -## Tips and trick's - -Autotune works with information existing in your database, so if you just installed AAPS on a new phone, you will have to wait several days before being able to launch Autotune with enough days to get relevant results; - -Autotune is just an help, it's important to regularly check if you agree with calculated profile. If you have any doubt, change Autotune settings (for example the number of days) or copy results in local profile and adjust profile before using it. - -Always use Autotune several days manually to check results before applyling them. And it's only when you fully trust Autotune results, and when variation becomes tiny between previous profile and calculated profile than you start to use Automation (Never before) - -- Autotune can work very well for some users and not for others, so **If you don't trust Autotune result, don't use it** - -It's also important to analyse Autotune results to understand (or try to understand) why Autotune propose these modifications - -- you can have a whole increase or decrease of the strength of your profile (for example increase of total basal associated to decrease of ISF and IC values). it could be associated to several following days with autosens correction above 100% (more agressivity required) or below 100% (you are more sensitive) -- Sometimes Autotune propose a different balance between basal rates and IC/ISF (for ex lower basal and more aggressive IC/ISF) - -We advise to not use Autotune in the following cases: - -- You don't enter all your carbs - - If you don't enter carbs correction for an hypoglycemia, Autotune will see an unexcepted increase of your BG value and will increase your basal rates the ' hours earlier, it could be the opposite of what you need to avoid hypo, especially if it's in the middle of the night. That's why it's important to enter all carabs especially correction for hypo. -- You have a lot of period with UAM detected during the day. - - Do you have entered all your carbs and correctly estimated your Carbs ? - - All UAM periods (except if you enter no carbs during a day and categorized UAM as basal is disabled), all your UAM periods will be categorized as basal, this can increase a lot your basal (much more than necessary) - -- Your carbs absorption is very slow: if most of your carbs absorption are calculated with min_5m_carbimpact parameter (you can see these periods with a little orange dot in the top of COB curve), the calculation of COB could be wrong and leads to wrong results. - - We you practice sport, you are generally more sensitive and your BG doesn't rise a lot, so during or after an exercice, it's usual to see some periods with slow carbs. But if you have too often unexpected slow carb absorption, then you may need a profile adjustment (higher value of IC) or a min_5m_carbimpact a bit to high. -- You have a "very bad days", for example stuck several hours in hyperglycemia with a huge amount of insulin to be able to go down within the range, or after a sensor change you got long periods of wrong BG values. -- If the percentage of modification is too important - - You can try to increase the number of days to get smoother results \ No newline at end of file diff --git a/docs/CROWDIN/es/Usage/making-sport-with-AAPS.md b/docs/CROWDIN/es/Usage/making-sport-with-AAPS.md deleted file mode 100644 index 79d2f1c38223..000000000000 --- a/docs/CROWDIN/es/Usage/making-sport-with-AAPS.md +++ /dev/null @@ -1,185 +0,0 @@ -# making sport with AAPS - -In this section we want to address the topic of sport with AAPS. - -The aim is to show you how AAPS can help you to continue doing your favorite sport more easily or even to start doing it. It is relatively common for new type 1 diabetics to ask whether exercise is still possible for them, even if the answer in the training courses is actually a clear yes. Exercise is not only good for healthy people, but also for type 1 diabetics and even moderate exercise can even help to stabilize the blood sugar curve overall. - -:::{admonition} consult with your diabetes team after reading - -::: - -The difficulty here is that the prerequisites that someone brings with them and the expectations of what sport means to them are very different. - -Since we can assume that experienced top athletes with T1D who use AAPS are unlikely to look it up here, we deliberately set the bar low for ourselves when writing and for you when reading and using it, so that as many people as possible can benefit from it. - -Since even sport as a category is far too imprecise, as the effects of endurance sports differ greatly from strength training, for example, we are trying to break it down by type of sport. - -To be concrete and give you something you can test yourself we arrange the explanaiton around a concrete example and explain to you they action, reactions and effects. - -:::{admonition} more examples wanted - -The focus should always be on how others can do sport and not on the top performance someone has achieved. - -It's really about the basics. Your experience, which you share here, can help others to pursue their beloved sport more quickly and successfully and is therefore important. -::: - -## Cycling - -:::{admonition} take a friend with you - at least on your first trials -:class: information -A gerneral very good idea can be to take a good friend with you on the first rides. -This is especially important if you are not experienced in T1D. -Always keep in mind please: arrival comes before speed! Safety for you and the others in road traffic is very, very important. -::: - -### Example - -Let's take about 60 minutes of cycling on a flat route with a moderate heart rate as an example. - -1. we take a flat route in order to have an even load for the first exercise. This is not about performance, but purely about learning how you should react to changes in blood glucose. -2. we take the heart rate as an indicator of the load, as it is easy to see whether you are under load or not. -3. we set ourselves the goal of doing a relaxed lap around the neighborhood and focus on staying within our target range during the lap. In my case, this would be 70 <= x <= 180 mg/dl. - -We **don't** take the speed, as this is heavily dependent on personal physical conditions as well as the bike and surface used. It is therefore not very meaningful. - -You should know from the diabetes training courses you have attended that during endurance sports cycling, the insulin active in the body works significantly better than during times without physical exertion. The insulin active in the body is referred to as insulin on board (IoB). It is our most important parameter when cycling with T1D. - -We try to keep the IoB as low as possible at the start and during exercise. IoB should be around 0 or even slightly negative. You can get it there by not eating 3-4 hours before exercise. In the beginning it can also be helpful to exercise in the morning before breakfast, as with the right profile you should always have around 0 for IoB in the morning. - -AAPS shows us the IoB value on the home screen on the left under the blood glucose value. - -![IoB](../images/cycling_20240104-174035.png) - -:::{admonition} ignoring the IoB rule increases the risk for roller coaster BG dramatically -:class: danger -If you ignore this rule, you can still go cycling, but it will be much more difficult to keep your blood sugar levels in balance, so it is better to save this for later tests after several successful simple tests. -::: - -As you should know from the diabetes training courses, you should reduce the basal rate during exercise. The factor is individual. I have found a value of 50% in tests to be suitable for me. - -In AAPS, you should therefore change your profile to 50% before exercise and keep it active until the end of exercise. Some people even do it a certain amount of time before, e.g. 1 hour. Unfortunately, the pre-run is also individual. We will come to the post-run later. - -You should use two carbohydrates during exercise. - -1. medium-fast carbohydrates for the insulin still in the body and -2. very fast carbohydrates to prevent slipping into a hypo. - -For medium-fast carbohydrates, I treat myself to cookies or a banana before exercise, for example. You can also use something else that is more suitable for you. -For very fast carbohydrates, I take 3 teaspoons of dissolved glucose per 100 ml of still water in a 500 ml water bottle on my bike. If I'm cycling longer distances, I take a larger bottle with me and, if necessary, packaged glucose to refill the bottle. I add a little lemon juice for flavor. You can also use something other than lemon juice for the taste. You shouldn't change anything about the dextrose, as dissolved dextrose raises blood sugar levels super quickly. If you only take it in sips, your blood sugar won't go super high either! You can also do this tip at home beforehand as a dry run and see how quickly the change shows up on the CGMS. - -Why do I place so much emphasis on fast carbohydrates? - -1. once you are in a slight hypo, you may get back into the normal range by drinking the dextrose solution. As a rule, however, the oscillation of the curve then begins, which leads to a rollercoaster ride of the blood sugar. You may even be able to keep this within your target range, but you must be constantly vigilant. Without a hypo it is simply the most stable. -2. if you even slip into a somewhat severe hypo (without the need for outside help, of course), you may even have to pause briefly to avoid getting stuck in the hypo. - With both hypos, there is a risk that you will be tempted to switch from drinking 2-3 sips at a time to larger quantities. Not too bad at first, until the oscillation sets in and pushes you into a hyper. You can correct this, but your blood sugar will most likely go on a rollercoaster ride. - -What else is helpful, but not absolutely necessary? -It is important to keep an eye on your blood sugar, as your blood sugar can change enormously (e.g. 30 - 50 mg/dl) within 15 minutes of riding and a little more IoB or a basal rate that is still too high. The best way to keep an eye on it is if it is visible on the handlebars or if it is also displayed on your watch. It is even possible to install an additional app on some Garmin GPS bike computers that displays the blood glucose from XDrip or Nightscout as a data field on the bike computer. The additional app was developed by Andreas May from the T1D community. It is available free of charge in the official connect IQ Store. Certainly an interesting option for riders interested in sports. - -[Link to Andreas May Data Field App on connect IQ store](https://apps.garmin.com/de-DE/apps/5a3e2cda-12f0-4afd-88ed-000e67a68d84) - -Here is a picture of my Garmin Edge 530 bike computer with map, blood sugar and heart rate. - -![Garmin Edge 530 with BG data field](../images/cycling_IMG_1087.jpeg) - -After you have eaten the medium fast carbohydrates (24 - 36 g I take) and the blood sugar is above 100 mg/dl but also below 160 mg/dl, I carry out the profile change to 50% and set the activity temp target. - -:::{admonition} disable SMBs during high temp targets if necessary -:class: danger -Attention: If you prefer not to receive SMBs during the sport, please disable the option "Enable SMB with hight temp targets" in the settings of SMB or DynIFS Plugin. -::: - -The following picture shows the start and end of the sport. The end was specified as the duration when the profile was changed at the start. - -The temporary profile change has the following effects - -1. for a period of 60 minutes -2. a reduction to 50% of the profile and -3. the target is raised by clicking on the Activity Target option, which may have the side effect of disabling the SMBs - see above. - -![profile switch with temp target](../images/cycling_20240104-174056.png) - -The second image shows that the start at IoB was started towards 0. - -![IoB around 0](../images/cycling_20240104-174111.png) - -If the blood sugar drops faster than 15 mg/dl in 5 minutes or if it is at 120 mg/dl and tends to fall, I drink 1-2 sips of dissolved glucose. Then I wait for the next value and proceed as described above. - -You can hardly see it here, but at the beginning I took 2 sips from the bottle several times when my blood sugar started to fall. When it stabilized, I didn't need any more glucose. - -Here is the picture that illustrates this. The chart is saved on the Garmin as a result of the activity. - -![BG chart Garmin](../images/cycling_20240104-174431.png) - -If you should suddenly break out upwards, i.e. above 180 mg/dl, you should consider whether you should make a correction bolus. Caution: Remember the factor and apply it to the correction, otherwise the correction will be too strong. - -If your blood sugar drops below 80 mg/dl, take a break and drink two sips until your blood sugar is back above 100 mg/dl. - -At the end of the ride, the profile change should be finished as the time is up. - -Since we only rode easy for 60 minutes, there shouldn't be a big muscle bulking effect continuing to pull carbohydrates from your blood sugar. However, if it felt strenuous to you, keep an eye on it. This is especially true if you then go straight to bed. It may be better to change your profile to e.g. 80% for sleep. You may come out of sleep slightly too high, but it's better than having a hypo at night. Over time, you will surely find out what happens to you. - -The following pictures show the low intensity of the sport. - -The elevation profile -![](../images/cycling_20240104-174314.png) - -Speed with average and maximum speed - -![](../images/cycling_20240104-174326.png) - -Note the pause at the level crossing, which is also reflected in the heart rate. - -The heart rate. -![](../images/cycling_20240104-174337.png) - -The training effect. -![](../images/cycling_20240104-174358.png) - -The time in the different heart rate training zones. -![](../images/cycling_20240104-174423.png) - -After succesfully mastering this simple example you could go for further targets by stretching - -1. the distance and time -2. the load during the ride -3. the elevation during the right which should make a big impact on the more necessary carbs or further reduction of IoB and percentage of profile switch. - -Based on my experiences I would not expect to come back 100% with time in range over the whole and every ride. - -### Tipps - -I already gave some tipps for during the ride above. - -Here are some further tipps what can go wrong and how you can act to prevent it or react to compensate it. - -#### sky rocket high after ride - -During the ride everything was fine but after siting down and relax the blood sugar go sky rocket high. - -**Possible reason:** This happens when you have drunk too much dissolved glucose. - -**Reaction:** Drink 500 ml water, go to the shower and then control again. Latest after 30 minutes think about giving a correction bolus but be careful when it is short for bed time. Therefore it can be very good to make the first try runs on weekend mornings. - -**Action:** Next time be a bit more cautious in drinking from the dissolved glucose. - -#### hypo during ride - -During the ride you are going into hypo and can't recover your blood sugar during cycling. - -**Possible reason:** Your body cannot absorb enough carbohydrates quickly enough during exercise. - -**Reaction:** Take a rest and corrrect your blood sugar with drinking dissolved glucose. Stay calm: arrival comes before speed. - -**Action:** Did you started with IoB near 0? Have you eaten a small amount of middle fast carbs? Can you increase this or are the not fast enough for your body? Is it possible to prevent going into hypo by reducing the factor for the profile switch? Have you disbaled SMBs during ride as explained above? - -#### sky rocket high during ride - -During the ride your blood sugar goes sky rocket high. - -**Possible reason:** You have got taken too much carbs for your IoB at that time. Beneath for sure the typical technical problems with your -insulin pump like leakage or blockage of the catheder! - -**Reaction:** If it is too high for you take a rest and correct with a bolus. Keep in mind that you must ride home and therefore make it carefully. Drink 500 ml pure water without carbs. Stay calm: arrival comes before speed. - -**Action:** Have you eaten too much? Especially have you drunk too much from the dissolved glucose during the ride? Is your percentage of reduction the profile during profile switch too low and you can increase this? diff --git a/docs/CROWDIN/es/Where-To-Go-For-Help/How-to-get-support.md b/docs/CROWDIN/es/Where-To-Go-For-Help/How-to-get-support.md deleted file mode 100644 index b58ecc8978b6..000000000000 --- a/docs/CROWDIN/es/Where-To-Go-For-Help/How-to-get-support.md +++ /dev/null @@ -1,11 +0,0 @@ -# How to get support - -**Level 1:** Wiki - we now have a search function! - -**Level 2:** [Facebook](https://www.facebook.com/groups/AndroidAPSUsers/) OR [gitter](https://gitter.im/MilosKozak/AndroidAPS) - -**Level 3:** Gitter (if FB did not get results, wait at least a couple of hours (plural)!!! Direct crossposts will be ignored/deleted on both channels!!!) - -**Level 4:** Create an issue with logs and time of the issue - -**Level 5:** PM (only if personal data is involved that should not go in a public channel) \ No newline at end of file diff --git a/docs/CROWDIN/es/buildingAAPS.md b/docs/CROWDIN/es/buildingAAPS.md deleted file mode 100644 index 98164a09e49b..000000000000 --- a/docs/CROWDIN/es/buildingAAPS.md +++ /dev/null @@ -1,28 +0,0 @@ -# Dummy - -## This is a dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - - -## This is another dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - - -## This is another another dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - diff --git a/docs/CROWDIN/es/completingObjetives.md b/docs/CROWDIN/es/completingObjetives.md deleted file mode 100644 index 98164a09e49b..000000000000 --- a/docs/CROWDIN/es/completingObjetives.md +++ /dev/null @@ -1,28 +0,0 @@ -# Dummy - -## This is a dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - - -## This is another dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - - -## This is another another dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - diff --git a/docs/CROWDIN/es/dummy.md b/docs/CROWDIN/es/dummy.md deleted file mode 100644 index 98164a09e49b..000000000000 --- a/docs/CROWDIN/es/dummy.md +++ /dev/null @@ -1,28 +0,0 @@ -# Dummy - -## This is a dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - - -## This is another dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - - -## This is another another dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - diff --git a/docs/CROWDIN/es/intro.md b/docs/CROWDIN/es/intro.md deleted file mode 100644 index 8534fea91f5d..000000000000 --- a/docs/CROWDIN/es/intro.md +++ /dev/null @@ -1,291 +0,0 @@ -![20-06-23v2 AAPS simple overview-cropped](https://github.com/openaps/AndroidAPSdocs/assets/94044064/e505b73b-09a0-42a4-a1ab-b830a0741234) - -# Introduction to APS and AAPS - -## What is an “Artificial Pancreas System”? - -A human pancreas does a lot of things besides regulating blood sugar. However, the term **“Artificial Pancreas System” (APS)** usually refers to a system which works to automatically keep blood sugar levels within healthy limits. - -The most basic way to do this is by detecting **glucose levels**, using these values to do **calculations**, and then delivering the (predicted) right amount of **insulin** to the body. It repeats the calculation, every few minutes, 24/7. It uses **alarms** and **alerts** to inform the user if intervention or attention is needed. This system is typically made up of a **glucose sensor**, an **insulin pump** and an **app** on a phone. - -You can read more about the different artificial pancreas systems currently in use and in development in this 2022 review article: - -![Frontiers](./images/FRONTIERS_Logo_Grey_RGB.png) [Future Directions in Closed-Loop Technology](https://www.frontiersin.org/articles/10.3389/fendo.2022.919942/full#:~:text=Fully%20closed%2Dloop%20systems%2C%20unlike,user%20input%20for%20mealtime%20boluses). - -In the near future, some so-called "dual-hormone" systems will also have the ability to infuse glucagon alongside insulin, with the aim of preventing severe hypos and allowing even tighter blood glucose control. - -An artificial pancreas can be thought of as an [“autopilot for your diabetes”]. (https://www.artificialpancreasbook.com/) What does that mean? In an aircraft, an autopilot does not do the complete job of the human pilot, the pilot cannot sleep through the entire flight. The autopilot aids the work of the pilot. It relieves them of the burden of permanently monitoring the aircraft, allowing the pilot to concentrate on wider monitoring from time to time. The autopilot receives signals from various sensors, a computer evaluates them together with the pilot’s specifications and then makes the necessary adjustments, alerting the pilot to any concerns. The pilot no longer has to worry about constantly making decisions. - -## What does hybrid closed loop mean? - -The best solution for type 1 diabetes would be a “functional cure” (probably an implant of pancreatic cells which are protected from the immune system). While we are waiting for that, a “full closed loop” artificial pancreas is probably the next best thing. This is a tech system that doesn’t need any user input (like bolusing insulin for meals, or announcing exercise), with good regulation of blood glucose levels. At the moment, there are no widely available systems which are “full” closed loop, they all need some user input. The currently available systems are called “hybrid” closed loop, because they use a combination of automated technology and user input. - -## How and why did looping start? - -The development of commercial technology for people with type 1 diabetes (T1D) is very slow. In 2013 the T1D community founded the #WeAreNotWaiting movement. They developed systems themselves using existing approved technology (insulin pumps and sensors) to improve blood glucose control, safety, and quality of life. These are known as DIY (do-it-yourself) systems, because they are not formally approved by health bodies (FDA, NHS etc). There are four main DIY systems available: OpenAPS, **AAPS**, Loop and iAPS. - -A great way to understand the fundamentals of DIY looping is to read Dana Lewis’s book “Automated Insulin Delivery”. You can access it \[here\] (https://www.artificialpancreasbook.com/) for free (or buy a hardcopy of the book). If you want to understand more about OpenAPS, which** AAPS** has developed from, the \[OpenAPS website\] (https://openaps.org/what-is-openaps/) is also a great resource. - -Several commercial hybrid closed loop systems have been launched, the most recent of which are \[CamAPS FX\] (https://camdiab.com/) (UK and EU) and \[Omnipod 5\] (https://www.omnipod.com/en-gb/what-is-omnipod/omnipod-5) (USA and EU). These are very different to DIY systems, mainly because they both include a “learning algorithm” which adjusts how much insulin is delivered according to your insulin needs from previous days. Many people in the DIY community have already tried out these commercial systems and compared them with their DIY system. You can find out more about how the different systems compare by asking on the dedicated Facebook groups for these systems, on the \[AAPS Facebook group\] (https://www.facebook.com/groups/AndroidAPSUsers/) or on \[Discord\] (https://discord.com/invite/4fQUWHZ4Mw). - -## What is Android APS (AAPS)? - -![image](https://github.com/openaps/AndroidAPSdocs/assets/94044064/0f089d96-b7ee-452a-aa9d-aae10ab58971) - -**Figure 1**. Basic outline of the Android APS (Artificial Pancreas System), AAPS. - -Android APS (AAPS) is a hybrid closed loop system, or Artificial Pancreas System (APS). It makes its insulin dosing calculations using established \[OpenAPS\] (https://openaps.org/) algorithms (a set of rules) developed by the #WeAreNotWaiting type 1 diabetes community. - -Since OpenAPS is only compatible with certain older insulin pumps, AAPS (which can be used with a wider range of insulin pumps) was developed in 2016 by Milos Kozak, for a family member with type 1 diabetes. Since those early days, **AAPS** has been continually developed and refined by a team of volunteer computer developers and other enthusiasts who have a connection to the type 1 diabetes world. Today, **AAPS** is used by approximately 10,000 people. It is a highly customisable and versatile system, and because it is open-source, it is also readily compatible with many other open-source diabetes softwares and platforms. The fundamental components of the current **AAPS** system are outlined in Figure 1 above. - -## What are the basic components of AAPS? - -The “brain” of AAPS is an **app** which you build yourself. There are detailed step-by-step instructions for this. You then install the **AAPS app** on a compatible **Android smartphone** (1). A number of users prefer their loop on a separate phone to their main phone. So, you don’t necessarily have to be using an Android phone for everything else in your life, just for running your AAPS loop. - -The **Android smartphone** will also need to have another app installed on it as well as **AAPS**, either a modified Dexcom app called build-your-own dexcom app (**BYODA**) or Xdrip+. This receives glucose data from a sensor (2) by bluetooth, and then sends the data internally on the phone to the **AAPS app**. - -The **AAPS app** uses a decision making process (**algorithm**) from OpenAPS. Beginners start out using the basic **oref0** algorithm, but it is possible to switch to using the newer **oref1** algorithm as you progress with AAPS. Which algorithm you use (oref0 or oref1), depends on which suits your specific situation best. In both cases, the algorithm takes into account multiple factors, and performs rapid calculations every time a new reading comes in from the sensor. The algorithm then sends instructions to the insulin pump (3) on how much insulin to deliver by bluetooth. All the information can be sent by mobile data or wifi to the internet. This data can also be shared with followers if desired, and/or collected for analysis. - -## What are the advantages of the AAPS system? - -The OpenAPS algorithm used by **AAPS** controls blood sugar levels in the absence of user input, according to the users’ defined parameters (important ones being basal rates, insulin sensitivity factors, insulin-to-carb ratios, duration of insulin activity etc.), reacting every 5 minutes to the new sensor data. Some of the reported advantages of using AAPS are extensive fine-tunable options, automations and increased transparency of the system for the patient/caregiver. This can result in better control over your (or your dependent’s) diabetes, which in turn may give improved quality of life and increased peace of mind. - -Practical advantages include: - -- **Hardware flexibility**: **AAPS** works with a wide range of insulin pumps and sensors. So for example, if you develop an allergy to Dexcom sensor patch glue, you could switch to using a Libre sensor instead. That offers flexibility as life changes. You don't have to rebuild, just tick a different box in the AAPS app to change your hardware. - -- **Highly customisable with wide parameters**: here are some examples of the possibilities with AAPS: a) The ability to set a lower glucose target 30 min before eating; you can set the target as low as 72 mg/dL (4.0 mmol/L). b) If you are insulin-resistant resulting in high blood sugars, **AAPS** allows you to set an **automation** rule to activate when BG rises above 8 mmol/L (144 mg/dL), switching to a 120% profile (resulting in an 20% increase in basal and strengthening of other factors too, compared to your normal **profile** setting). The automation will last according to the scheduled time you set. Such an automation could be set to only be active on certain days of the week, at certain times of day, and even at certain locations. c) If your child is on a trampoline with no advance notice, **AAPS** allows insulin suspension for a set time period, directly via the phone. d) After reconnecting a tubed pump which has been disconnected for swimming, AAPS will calculate the basal insulin you have missed while disconnected and deliver it carefully, according to your current BG. Any insulin not required can be overridden by just “cancelling” the missed basal. f) **AAPS** has the ability to set different profiles for different situations and easily switch between them. Features which make the algorithm quicker to bring down elevated BG (like supermicro boluses (“SMB”), unannounced meals, (“**UAM**”) can be set to only work during the daytime, if you are worried about night-time hypos. - - -These are all examples, the full range of features gives huge flexibility for daily life including sport, illness, hormone cycles etc. Ultimately, it is for the user to decide how to use this flexibility, and there is no one-size-fits-all automation for this. - -- **Remote monitoring**: there are multiple possible monitoring channels (Sugarmate, Dexcom Follow, Xdrip+, Android Auto etc.) which are useful for parents/carers and adults in certain scenarios (sleeping/driving) who need customisable alerts. In some apps (Xdrip+) you can also turn alarms off totally, which is great if you have a new sensor “soaking” or settling down that you don’t want to loop with yet. - -- **Remote control**: a significant advantage of **AAPS **over commercial systems is that it is possible for followers, using authenticated text (SMS) commands or via an app (Nightscout or NSClient) to send a wide range of commands back to the ****AAPS** **system. This is used extensively by parents of kids with type 1 diabetes who use AAPS. It is very useful in the playground, for example, if you want to pre-bolus for a snack from your own phone, and your child is busy playing. It is possible to monitor the system (e.g. Fitbit), send basic commands (e.g. Samsung Galaxy watch 4), or even run the entire AAPS system from a high-spec smartwatch (5) (e.g. LEMFO LEM14). In this last scenario, you don’t need to use a phone to run AAPS. As battery life on watches improves, this last option is likely to become increasingly attractive. - -- **No commercial constraints due to open application interfaces**: beyond the use of an open source approach, which allows the source code of **AAPS** to be viewed at any time, the general principle of providing open programming interfaces gives other developers the opportunity to contribute new ideas that allow users to live more easily with their diabetes. This is complementary to commercial systems which adopt the innovations from DIY, where interfaces are only made possible in return for licensing, thus preventing innovations in particular that are not-for-profit. Good examples for such integrations are NightScout, Nightscout Reporter, Xdrip+ M5 stack etc. - -- **Detailed app interface**: It is easy to keep track of things like: insulin levels, cannula age, sensor age, pump battery age, and many actions can be done through the **AAPS** app (priming the pump, disconnecting the pump etc.), instead of on the pump itself. - -- **Accessibility and affordability**: **AAPS** gives people who currently can’t afford to self-fund, or don’t have funding/insurance, access to a world-class hybrid closed looping system which is conceptually years ahead, in terms of development, of the commercial systems being offered by clinics. You currently need to have a Nightscout account to set up **AAPS**. Although the Nightscout account it not necessarily required after setup, many people continue to use Nightscout for collecting their data, and for remote control. So, although **AAPS **itself is free, setting up Nightscout through one of the various platforms may incur a fee (E0 - E12), depending on what level of support you want (see comparison table). **AAPS** works with a wide range of affordable (starting from approx E150) Android phones. In comparison, Loop currently costs around $80 a year for the Apple development licence and CamAPS FX costs around E80/month (as at 2023). - -- ****Support**: No automated insulin delivery system is perfect. Commercial and open-source systems share many common glitches in both communications and temporary hardware failure. There is a community of AAPS users on both Facebook and Discord and Github who designed, developed and are currently using **AAPS** all over the world. There are Facebook support groups and help from clinic/commercial companies for the commercial APS systems - it is worth speaking to the users, or former users of these systems to get feedback on the common glitches, the quality of the education programme and the level of ongoing support provided. - -- **Predictability, transparency and safety**: with no learning algorithm, **AAPS** is logical and in some respect, more predictable, which may make it easier to know when a setting is wrong, and to adjust it accordingly. You can see exactly what the system is doing, why it is doing it, and set its operational limits, which puts the control (and responsibility) in your hands. This can provide the user with confidence, and a sounder sleep. - -- **Access to advanced features through dev modes including full closed loop**: **AAPS **documentation focuses on the mainstream **“master”** branch of **AAPS**, however, research and development is going on all the time. More experienced users may wish to explore the experimental features in the **development** branch such as integration of Dexcom G7, and automatically adjusting insulin delivery according to short-term sensitivity changes (DYNISF), not having to bolus for meals, and generally trying to make life with type 1 diabetes as convenient as possible. - -- **Ability to contribute yourself to further improvements**: type 1 diabetes can be highly frustrating and isolating. Having control over your own diabetes tech, with the possibility to “pay it forward” as soon as you are making progress by helping others on their journey can be really rewarding. You can educate yourself, discover the roadblocks and look for and even contribute to new developments and the documentation. There will be others with the same quest to bounce ideas off and work with. This is the essence of #WeAreNotWaiting. - - -## How does AAPS compare to MDI and open looping? - -Multiple daily injections (MDI, a) usually involve giving an injection of a long-lasting insulin (e.g. Tresiba) once a day, with injections of faster-acting insulin (e.g. Novorapid, Fiasp) at mealtimes, or for corrections. Open pumping (b) involves using a pump to deliver basal at pre-programmed rates of rapid-acting insulin, and then boluses through the pump at mealtimes or for corrections. The basics of a looping system is that the App uses the glucose data to instruct the pump to stop insulin delivery when it predicts you are heading for a low, and to give you extra insulin if your glucose levels are rising and predicted to go too high (c). Although this is oversimplified, (mostly because hybrid closed looping has a lot of additional useful features) the key features of each system are shown in **Figure 2**. - -![image](https://github.com/openaps/AndroidAPSdocs/assets/94044064/4e7d8608-684d-4c69-9c61-88c9539f5d6f) - -**Figure 2**. Overview of (a) MDI, (b) open-loop pumping and (c) hybrid closed loop pumping - -## How does AAPS compare to other looping systems? - -At present there are four major open source closed loop systems available: OpenAPS, **AAPS**, \[Loop\] (https://loopkit.github.io/loopdocs/#what-is-loop) and iAPS, (formerly FreeAPS X). The features of the different systems are shown in the table below: - -| Devicestyp | Name | [Open APS](https://openaps.readthedocs.io/en/latest/) | [AAPS](https://wiki.aaps.app) | [Loop](https://loopkit.github.io/loopdocs/) | [iAPS](https://iaps.readthedocs.io/en/latest/) | -| ---------- | ---------------------------------------------------------------------------------------------------------- | ----------------------------------------------------- | ------------------------------------------- | ------------------------------------------- | ---------------------------------------------- | -| PUMP | Older Medtronic | ![available](./images/available.png) | ![available](./images/available.png) | ![available](./images/available.png) | ![available](./images/available.png) | -| PUMP | Older Omnipod (Eros) | ![unavailable](./images/unavailable.png) | ![available](./images/available.png) | ![available](./images/available.png) | ![available](./images/available.png) | -| PUMP | Newer Omnipod (Dash) | ![unavailable](./images/unavailable.png) | ![available](./images/available.png) | ![available](./images/available.png) | ![available](./images/available.png) | -| PUMP | DANA R, DANA RS, DANA I | ![unavailable](./images/unavailable.png) | ![available](./images/available.png) | ![unavailable](./images/unavailable.png) | ![unavailable](./images/unavailable.png) | -| PUMP | Roche Combo, Insight | ![unavailable](./images/unavailable.png) | ![available](./images/available.png) | ![unavailable](./images/unavailable.png) | ![unavailable](./images/unavailable.png) | -| MCG | Dexcom G4, G5, G6 | ![available](./images/available.png) | ![available](./images/available.png) | ![available](./images/available.png) | ![available](./images/available.png) | -| MCG | Libre 1 (requires Miao Miao) | ![available](./images/available.png) | ![available](./images/available.png) | ![available](./images/available.png) | ![available](./images/available.png) | -| MCG | Libre 2 | ![available](./images/available.png) | ![available](./images/available.png) | ![available](./images/available.png) | ![available](./images/available.png) | -| MCG | Libre 3 | | ![unavailable](./images/unavailable.png) | --- | ![unavailable](./images/unavailable.png) | -| MCG | Medtronic Enlite | | --- | ![unavailable](./images/unavailable.png) | --- | -| MCG | [Dexcom G7](https://androidaps.readthedocs.io/en/latest/Hardware/DexcomG7.html) | | ![available](./images/available.png) (beta) | ![available](./images/available.png) | ![available](./images/available.png) | -| MCG | [Eversense](https://androidaps.readthedocs.io/en/latest/Hardware/Eversense.html) | | ![available](./images/available.png) | | ![available](./images/available.png) | -| MCG | [MM640G/MM630G](https://androidaps.readthedocs.io/en/latest/Hardware/MM640g.html) | | ![available](./images/available.png) | | ![available](./images/available.png) | -| MCG | [PocTech](https://androidaps.readthedocs.io/en/latest/Hardware/PocTech.html) | | ![available](./images/available.png) | | ![available](./images/available.png) | -| MCG | [Nightscout como origen BG](https://androidaps.readthedocs.io/en/latest/Hardware/CgmNightscoutUpload.html) | | ![available](./images/available.png) | | ![available](./images/available.png) | -| Phone | Android | ![available](./images/available.png) | ![available](./images/available.png) | ![unavailable](./images/unavailable.png) | ![unavailable](./images/unavailable.png) | -| Phone | iPhone | ![available](./images/available.png) | ![unavailable](./images/unavailable.png) | ![available](./images/available.png) | ![available](./images/available.png) | - -[OpenAPS](https://openaps.readthedocs.io/) was the first Open Source Closed Loop System. Utiliza un ordenador pequeño como Raspberry Pi o Intel Edison. Both AndroidAPS (AAPS) and iAPS use the OpenAPS algorithms, whereas Loop uses a separate algorithm. You can read a comparison of iAPS and **AAPS** here. - -An international peer-reviewed consensus statement containing practical guidance on open source looping was written by and for health-care professionals, and published in a leading medical journal in 2022. It is well worth a read (including for your diabetes clinic) and summarises the main technical differences between the different open-source hybrid closed loop systems: - - Lancet Diabetes Endocrinol, 2022; 10: 58–74 - -[https://www.ncbi.nlm.nih.gov/pmc/articles/PMC8720075/](https://www.ncbi.nlm.nih.gov/pmc/articles/PMC8720075/) - -It is hard to get a “feel” for any system without using it, or talking to others who are using it, so do reach out to others on Facebook/Discord and ask. Most people find that AAPS is incredibly sophisticated in comparison to other hybrid closed loop systems (particularly the commercial systems), with a huge number of potentially customisable settings and features, discussed above. Some people can find this a little overwhelming in the beginning, but there is no rush to investigate all the possibilities at once, you can progress as slowly or as fast as you would like, and there is help available at every step of the way. - -## Does AAPS use artificial intelligence or any learning algorithm? - -No. **AAPS** does not have any complicated machine learning algorithms, multiple-parameter insulin response models, or differential equations. As such, the system is open and transparent in how it works, and has the ability to be understood not just by experts, but also by clinicians and patients. It also means that if you have a sharply varying schedule (maybe switching from a stressful week at work to a relaxing holiday) and are likely to need a significantly different amount of insulin, you can immediately switch **AAPS** to run a weaker/stronger profile. A ‘learning system’ will do this adjustment for you automatically, but is likely to take longer to adjust the insulin delivery. - -## Which system is right for me or my dependent? - -Practically, your choice of system is often restricted by which pump you already have, or can obtain from your medical provider, and your choice of phone (Apple or Android). If you don’t yet have a pump you have the biggest choice of systems. Technology is continually evolving, pumps are being discontinued and new pumps and sensors are being released. Most open-source systems work with the main sensors (Libre and Dexcom) or are quickly adapted to work with new sensors a year or so after they are released (with a bit of time delay for safety and stability testing). - -Most **AAPS **users report more time in range, HbA1c reductions, as well as quality of life improvements from having a system that can auto-adjust basal rates overnight during sleep, and this is true for most hybrid closed loop APS. Some people have a preference for a very simple system which is not very customisable (which means you may prefer a commercial system), and others find this lack of control very frustrating (you may prefer an open-source system). If you (or your dependent) are newly diagnosed, a common route is to get the hang of MDI plus sensor first, then progress to a pump which has the potential for looping, then to **AAPS**, but some people (especially small kids) may go straight to a pump. - -It is important to note that the **AAPS** user needs to be proactive to troubleshoot and fix problems themselves, with help from the community. This is a very different mindset to that when using a commercial system. With **AAPS** a user has more control, but also the responsibility, and needs to be comfortable with that. - -## Is it safe to use open-source systems like AAPS? - -A more accurate question is probably “is it safe compared to my current type 1 diabetes insulin delivery system?” since no method of insulin delivery is without risk. There are many checks and balances in place with **AAPS**. A recent paper looked at the use of**** AAPS ****in a computer simulated set-up, [https://www.liebertpub.com/doi/epub/10.1089/dia.2019.0375](https://www.liebertpub.com/doi/epub/10.1089/dia.2019.0375) which was an effective way to unobjectively trial how safe and effective the system is. More generally, it is estimated that over 10,000 individuals worldwide are using open-source automated-insulin delivery systems, and uptake continues to increase globally. - -Any device that uses radio communications could be hacked, and this is true for a non-looping insulin pump as well. Currently, we are not aware of anyone attempting to harm individuals by hacking their diabetes-related medical equipment. However, there are multiple ways to protect against such risks: - -1. In the pump settings, limit both the max bolus allowed and max temporary basal settings to amounts that you believe are safest. These are hard limits that we do not believe any malicious hacker could circumvent. - -2. Set your CGM alarms enabled for both highs and lows. - -3. Monitor your insulin delivery online. Nightscout users can set additional alarms to alert for a wide variety of conditions, including conditions that are much more likely to occur than a malicious attack. In addition to highs and lows, Nightscout can display diagnostic data useful for verifying that the pump is operating as desired, including current IOB, pump temporary basal history, pump bolus history. It can also be configured to proactively alert users to undesirable conditions, such as predicted highs and lows, low insulin reservoir, and low pump battery. - - -If a malicious attack was made on your insulin pump, these strategies would significantly mitigate the risk. Every potential **AAPS** user needs to weigh the risks associated with using **AAPS**, versus the risks of using a different system. - -## How can I approach discussing AAPS with my clinical team? - -Depending on the country - link to doctors section of docs - - Lancet Diabetes Endocrinol, 2022; 10: 58–74 - -[https://www.ncbi.nlm.nih.gov/pmc/articles/PMC8720075/](https://www.ncbi.nlm.nih.gov/pmc/articles/PMC8720075/) - -## Q: Why can’t I just download AAPS and use it straight away? - -The **AAPS** app is not provided in Google Play - you have to build it from source code by yourself for legal reasons. **AAPS** is unlicensed, meaning that it does not have approval by any regulatory body authority in any country. **AAPS**is deemed to be carrying out a medical experiment on yourself, and is carried out at the user’s own risk. - -Setting up the system requires patience, determination and the gradual development of technical knowledge. All the information and support can be found in these documents, elsewhere online, or from others who have already done it. It is estimated that over 2000 people have successfully built and are currently using **AAPS** worldwide. - -The developers of **AAPS**t ake safety incredibly seriously, and want others to have a good experience of using **AAPS**. That is why it is essential that every user (or carer, if the user is a child): - -- builds the AAPS system themself and works through the **objectives** so that they have reasonably good personalised settings and understand the basics of how AAPS ****works by the time they “close the loop”; - -- backs up their system by exporting and saving important files (like keystore and settings .json file) somewhere safe, so you can setup again quickly if needed; - -- updates to newer master versions as and when they become available; and - -- maintains and monitors the system to ensure it is working properly. - - -## Q: What is the connectivity of the AAPS system? - -**Figure 3 (below)** shows one example of the **AAPS** system for a user who do not require any followers interacting with the system: - -![potential AAPS connectivity setup with no followers](./images/intro03.png) - -**Figure 4 (below)** shows the full potential of the **AAPS** system for a user who has followers and requires a monitor and send adjust the system remotely (like a child with T1D): - -![potential AAPS connectivity setup with followers](./images/intro04.png) - -## Q: How does AAPS get continually developed and improved? - -Most **AAPS** users use the fully tested **master** version of AAPS, which has been tested for bugs and problems, before being released to the community. Behind the scenes, the developers try out new improvements, and test these out in “developer” (**dev**) versions of **AAPS** with a user community who are happy to do bug updates at short notice. If the improvements work well, they are then released as a new “master” version of **AAPS**. Any new master release is announced on the Facebook group, so that the mainstream **AAPS** users can read about and update to the new master version. - -Some experienced and confident **AAPS ** users conduct experiments with emerging technologies and with dev versions of the **AAPS** app, which can be interesting for the less adventurous users to read about, without having to do it themselves! People tend to share these experiments on the Facebook group too. - -You can read more about some of these experiments and discussion on emerging tech here: - -[https://www.diabettech.com/](https://www.diabettech.com/) - -[https://bionicwookie.com/](https://bionicwookie.com/) - -## Q: Who can benefit? - -| User Type | -| ------------------------------------------- | -| ✔️ type 1 diabetic | -| ✔️ caregiver or parent of a type 1 diabetic | -| ✔️ blind users type 1 diabetic | -| ✔️ *clincians and healthcare professionals | - -The above table assumes that the user has access to both continuous gluocse monitor and insulin pump. - -*All data from **AAPS** can be made available to healthcare professionals via data sharing platforms, including NightScout that provides logging and real time monitoring of CGM data, insulin delivery, carbohydrate entries, predictions and settings. Nightscout records include daily and weekly reports which can aid healthcare professionals' discussions with type 1 patients with more accurate data on glycemic control and any behavioural considerations. - -## Q: What benefits can I get? - -With investment of your time, **AAPS** can potentially lead to: - -- alleviating the stress and burden of managing type 1 diabetes; - -- reducing the multitude of mundane decisions that arise from type 1 diabetes; - -- the provision of personalised and dynamic insulin dosing based on real-time data which can cut down the need for hypo treatments and reduce hyperglycemia episodes; - -- an increased knowledge of insulin management and confidence to better fine tune your settings; - -- the ability to create automatic settings (**automations**) that are tailored to fit in with your lifestyle; - -- improved sleep quality and overall reduction in the frequency of nighttime interventions; - -- remote monitoring and administration of insulin delivery for caregivers of type 1 diabetics; and - -- streamlining of all your portable diabetic equipment (continuous glucose monitor and insulin portable devices) by replacing them with an android phone controlled by **AAPS**. - - -Ultimately,**AAPS** can empower individuals to better manage their diabetes resulting in stable blood sugars and improved long term health outcomes. - ---- - -## AAPS First Steps - -Welcome. This is an introduction to aid beginners getting started with **AAPS** (or commonly referred to as "looping"). - -## Safety - -“_With great powers comes great responsibilities…_” - -**AAPS** is designed with an extensive set of safety features with limits imposed and gradually removed with completion of the **objectives **(predominately made up of multiple choice questions). An **AAPS** feature will be unlocked as the Objectives are successfully completed. This process will gradually allow the user to migrate from Open Loop to Closed Loop. - -This has been done to achieve the best possible experience with **AAPS** in order to prevent common mistakes that new users tend to make when starting to loop. The safety parameters have been built upon typical errors and general trends **AAPS** developers have observed with new users. Mistakes can happen because the beginner is inexperienced and too eager to get started with AAPS or has overlooked the required materials. Do not worry, we have all been there! - -## Key Principles - -The key principles and concepts of looping must be understood by the user before using **AAPS**. This is achieved by investing your personal time into reading the **AAPS** documentation, and completing the Objectives which is aimed to provide you with a solid platform for safe and effective use of **AAPS**. The volume of **AAPS** documentation may seem overwhelming at first but be patient and trust the process - with the proper approach, you'll get there! The overall process will depend upon the beginner’s progress and completion of objectives can typically take between 6 to 9 weeks . - -## Plan for hiccups - -At the preliminary stages of **AAPS**, you should expect to experience some hiccups whilst trying to fine tune your settings. **AAPS**’ glitches cannot be flushed out until the system is used in everyday life. Please plan accordingly and allow a sensible amount of time to troubleshoot and resolve such issues. - -## Flexibility/Adaptability - -Success with **AAPS** requires a proactive approach, a willingness to reflect on the BG data and flexibility to make the necessary adjustments to **AAPS** in order to improve your outcomes. Just as it is nearly impossible to learn to play a sport by reading about the rules alone, the same can be said of **AAPS**. - -## Technology compatibility - -There are limitations with **AAPS** as it is accessible for only certain types of insulin pumps or CGMs, and some technology may not be available for use in various countries. In order to avoid any disappointment or frustrations, please read please read Component Set Up (Section INSERT). - -## App Build Time - -The time to build the **AAPS**(under Section INSERT) depends on your level of expertise and technical ability. Typically for inexperienced users, it can take up to half a day or a full day (with help from the community) in order to build the **AAPS**. The process will significantly speed up as you become more experienced at building the **AAPS**. To aid the build process there are sections dedicated for: -- list of questions and answers for frequent errors that are likely to occur under FAQs (Section K); -- “How to install AAPS? (Section INSERT) which includes Troubleshooting subsection. - -## Keystore & configurations settings a export file - -A “keystore” is a password encrypted file unique to your own copy of **AAPS**. Your android phone uses it to ensure that nobody else can upgrade your own copy without the keystore. In short, as part of the **AAPS** build, you should: - -- save the your keystore file (.jks file used to sign your app) in a safe place; -- keep a note of your password for your keystore file. - -By doing the above, this will ensure that you can use that exact same keystore file each time an updated version of **AAPS** is created. On average, there will be 2-3 AAPS updates required each year. - -In addition, **AAPS** provides the ability to export all your configuration settings. This ensures that you can safely recover your system while changing phones, upgrading/reinstalling the application with minimum disruption. - -## Troubleshootng - -Please feel free to reach out to the AAPS community if there is anything you feel unsure about - there is no such thing as a silly question! All users with various levels of experience are encouraged to ask questions as necessary. Response times to questions are usually quick, typically only a few hours due to the volume of **AAPS** users. - -a) check the documentation; b) ask AAPS facebook group (https://www.facebook.com/groups/AndroidAPSUsers); and c) ask our discord channel. - -## Section overview - -AAPS documentation is made up of the following Sections: - -[INSERT ONCE SECTIONS /SUB SECTIONS AGREED] ---- diff --git a/docs/CROWDIN/es/maintaining.md b/docs/CROWDIN/es/maintaining.md deleted file mode 100644 index 98164a09e49b..000000000000 --- a/docs/CROWDIN/es/maintaining.md +++ /dev/null @@ -1,28 +0,0 @@ -# Dummy - -## This is a dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - - -## This is another dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - - -## This is another another dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - diff --git a/docs/CROWDIN/es/optimizing.md b/docs/CROWDIN/es/optimizing.md deleted file mode 100644 index 98164a09e49b..000000000000 --- a/docs/CROWDIN/es/optimizing.md +++ /dev/null @@ -1,28 +0,0 @@ -# Dummy - -## This is a dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - - -## This is another dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - - -## This is another another dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - diff --git a/docs/CROWDIN/es/prepairing.md b/docs/CROWDIN/es/prepairing.md deleted file mode 100644 index 0cf317a1a430..000000000000 --- a/docs/CROWDIN/es/prepairing.md +++ /dev/null @@ -1,145 +0,0 @@ -# Prepairing - -## Guide to the Android APS doc - -### First Steps -Welcome. This is an introduction to aid beginners to the concept of Do-It-Yourself-APS (Android-Artificial-Pancreas-Systems “AAPS”) is commonly referred to as ‘looping’.. - -#### Safetys -“With great powers come great responsibilities…” - -AAPS is designed with an extensive set of safety features with limits imposed and gradually removed with completion of the [Objectives](https://androidaps.readthedocs.io/en/latest/Usage/Objectives.html) (predominately made up of multiple choice questions). An AAPS feature will be unlocked as the Objectives are successfully completed. This process will gradually allow the user to migrate from Open Loop to Closed Loop. - -This has been done to achieve the best possible experience with AAPS by preventing common mistakes new users tend to make when starting to loop. The safety parameters have been built upon typical errors and general trends AAPS developers have observed with new users. Mistakes can happen because the beginner is inexperienced and too eager to get started with AAPS or has overlooked the required materials. Do not worry, we have all been there! - -#### Key Principles - -The key principles and concepts of looping must be understood by the user before using AAPS. This is achieved by investing your personal time into reading the AAPS documentation, and completing the [Objectives](https://androidaps.readthedocs.io/en/latest/Usage/Objectives.html) which is aimed to provide you with a solid platform for safe and effective use of AAPS. The volume of AAPS documentation may seem overwhelming at first but be patient and trust the process - with the proper approach, you'll get there! The overall process will depend upon the beginner’s progress and completion of objectives which typically take between 6 to 9 weeks . - -#### Plan for hiccups - -At the preliminary stages of AAPS, you should expect to experience some hiccups whilst trying to fine tune your settings. AAPS’ glitches cannot be flushed out until the system is used in everyday life. Please plan accordingly and allow a sensible amount of time to troubleshoot and resolve such issues. - -#### Flexibility/Adaptability - -Success with AAPS requires a proactive approach, a willingness to reflect on the BG data and flexibility to make the necessary adjustments to AAPS in order to improve your outcomes. Just as it is nearly impossible to learn to play a sport by reading about the rules alone, the same can be said of AAPS. - -#### Technology compatibility -There are limitations with AAPS as it is accessible for only certain types of insulin pumps or CGMs, and some technology may not be available for use in various countries. In order to avoid any disappointment or frustrations, please read [Component Set Up (Section E).](https://androidaps.readthedocs.io/en/latest/Configuration/BG-Source.html) - -#### App Build time -The time to build the AAPS (under Section D) depends on your level of expertise and technical ability. Typically for inexperienced users, it can take up to half a day or a full day (with help from the community) in order to build the AAPS. The process will significantly speed up as you become more experienced at building the AAPS.  - -To aid the build process there are sections dedicated for: - -- list of questions and answers for frequent errors that are likely to occur under [FAQs (Section](https://androidaps.readthedocs.io/en/latest/Getting-Started/FAQ.html) K); - -- “[How to install AAPS](https://androidaps.readthedocs.io/en/latest/Installing-AndroidAPS/Building-APK.html)? (Section D) which includes [Troubleshooting](https://androidaps.readthedocs.io/en/latest/Usage/troubleshooting.html) subsection. - - -#### Keystore & configuration settings export  file - -A “keystore” is a password encrypted file unique to your own copy of AAPS. Your android phone uses it to ensure that nobody else can upgrade your own copy without the keystore.In short, as part of the AAPS build, you should: - -1. save the your keystore file (.jks file used to sign your app) in a safe place; - -2. keep a note of your password for your keystore file. - - -By doing the above, this will ensure that you can use that exact same keystore file each time an updated version of AAPS is created. On average, there will be 2-3 updates to the AAPS required each year. In addition, AAPS provides the ability to [export all your configuration settings](https://androidaps.readthedocs.io/en/latest/Usage/ExportImportSettings.html). This ensures that you can safely recover your system while changing phones, upgrading/reinstalling the application with minimum disruption.  - -#### Solución de problemas - -Please feel free to reach out to the AAPS community if there is anything you feel unsure about - there is no such thing as a silly question!  All users with various levels of experience are encouraged to ask questions as necessary. Response times to questions are usually quick, typically only a few hours due to the volume of AAPS users.  - -##### [check the documentation](https://androidaps.readthedocs.io/en/latest/index.html) - -##### [ask our facebook group](https://www.facebook.com/groups/AndroidAPSUsers/) - -##### [ask our discord channel](https://discord.com/channels/629952586895851530/629954570394533889) - -#### Section overview - -AAPS documentation is made up of the following Sections: - -##### [Getting started](https://androidaps.readthedocs.io/en/latest/Getting-Started/Safety-first.html) - -This is a must read to understand the general concept of what an artificial pancreas system is designed to do. - -##### [What do I need?](https://androidaps.readthedocs.io/en/latest/Module/module.html) - -This explains AAPS’ compatibility with CGMs (Continuous Glucose Monitors) and insulin pumps. It also provides a guide on the correct assembly of an AAPS system to ensure that it functions correctly in everyday life. - -##### How to install AAPS - -This section is the manual for building the AAPS. Strict adherence to the step-by-step instructions are required in order to successfully build the AAPS. Please take your time. - -##### [Component Setup](https://androidaps.readthedocs.io/en/latest/Configuration/BG-Source.html) - -This explains how to properly integrate each of the various different separate component parts into AAPS, as well as how to set them up to work as seamlessly as possible together. All components are listed under the separate sections: CGM/FGM, xDrip Settings, Pumps, Phones, Nightscout setup, and Smartwatches. The sensor (BG) values and control of the insulin pump are particularly important information to understand. - -##### Configuration - -This explains how to set and configure your ‘Profile’, ‘Insulin’, ‘BG Source’, ‘Pump’, ‘Sensitivity Detection’, ‘APS’, ‘Loop’, ‘Treatments’. - -##### AAPS Usage - -This section provides a breakdown of the features provided by AAPS. - -##### [General Hints](https://androidaps.readthedocs.io/en/latest/Usage/Timezone-traveling.html) - -Useful tricks on how to tackle looping issues such as time zones, and daylight saving (i.e. Spring Forward/ - Fall Back). - -##### [AAPS](https://androidaps.readthedocs.io/en/latest/Getting-Started/Screenshots.html) for Children - -This is designed for parents or caregivers who want to build an AAPS for their child. It also explains the extra features necessary in order to support and safely control your child’s AAPS remotely.

The concepts in this section should be fully understood in order to competently use this feature. - -##### Solución de problemas - -This section contains links to help solve issues when building or using AAPS. - -##### FAQ - -This section addresses specific questions which tend to come up when building or using AAPS. - -##### [Glosario](https://androidaps.readthedocs.io/en/latest/Getting-Started/Glossary.html) - -This contains a list of the acronyms (or short-term names) or defined terms developed specifically for AAP (for instance, the terms ‘ISF’ or ‘TT’ have special meanings in AAPS). - -##### [Where to go for help](https://androidaps.readthedocs.io/en/latest/Where-To-Go-For-Help/Background-reading.html)? - -This section is aimed to provide new users with links on resources in order to get help including accessing community support made up of both new and experienced users who can clarify questions, and resolve the usual pitfalls that come with AAPS. - -##### For Clinicians - -This is a section for the clinicians who have expressed interest in open source artificial pancreas technology such as AAPS, or for patients who want to share such information with their clinicians. | - -## what are we going to build? - -### An Android Phone Application - -At the core, AAPS is an android application running from a phone. You are going to build it from scratch by installing tools to download the sourcecode and build the actual application. - -### A reporting server NightScout (or Tidepool) - -In order to fully use AAPS properly you will want to setup a nightscout server. It is used to collect data from AAPS over time and possibly communicate to the application. It is required for parents who want to oversee their children AAPS sessions. It is also key to share data between clinicians and patients to perform analysis over time. - -## How long will it take? - -## Who might AAPS not be suitable for? - -## Where can I get help? - -## Requirements - -### medical - -### technical - -### personal - -### CGMs - -### Insulin Pump - -### Reporting (NS, Tidepool) \ No newline at end of file diff --git a/docs/CROWDIN/fr/Configuration/Dexcom.md b/docs/CROWDIN/fr/Configuration/Dexcom.md deleted file mode 100644 index cb267e23c069..000000000000 --- a/docs/CROWDIN/fr/Configuration/Dexcom.md +++ /dev/null @@ -1,32 +0,0 @@ -# Dexcom G6 - -## Basics first - -* Follow [general CGM hygiene recommendations](../Configuration/BG-Source#cgm-hygiene) -* [Special recommendations for Dexcom G6 and DIY systems](../Configuration/BG-Source#dexcom-g6-diy-systems) *For G6 transmitters manufactured after fall/end of 2018 please make sure to use one of the [latest nightly built xDrip+ versions](https://github.com/NightscoutFoundation/xDrip/releases). Those transmitters have a new firmware and latest stable version of xDrip+ (2019/01/10) cannot deal with it. - -## Setting sensor - -When setting sensor, it is recommended not to press the inserter too firmly in order to avoid bleeding. The sensor thread should not come into contact with blood. - -After setting the sensor, the transmitter can be clicked into the sensor holder. Caution! First click in the square side and then press down the round side. - -## Troubleshooting - -### Connection problems - -Bluetooth connection may be disturbed by other nearby Bluetooth devices such as blood glucose meters, headsets, tablets or kitchen devices such as microwave ovens or ceramic hobs. In this case xdrip does not display any BG values. When bluetooth connection is reestablished the data is backfilled. - -### Sensor Errors - -If recurring sensor errors occur try selecting a different body site to set your sensor. The sensor thread should not come into contact with blood. - -Often a "Sensor Error" can be corrected by immediate drinking and massage around the sensor! - -### Jumpy values - -You might try to change settings for noise blocking in xdrip (Settings - Inter-App Settings - Noise Blocking) i.e. "Block Very High noise and worse". See also [Smoothing BG data](../Usage/Smoothing-Blood-Glucose-Data-in-xDrip.md). - -### New transmitter with running sensor - -If you happen to change transmitter during a running sensor session you might try to remove the transmitter without damaging the sensor mount. A video can be found at . \ No newline at end of file diff --git a/docs/CROWDIN/fr/Configuration/EOFLOW.md b/docs/CROWDIN/fr/Configuration/EOFLOW.md deleted file mode 100644 index b9ada64b66c2..000000000000 --- a/docs/CROWDIN/fr/Configuration/EOFLOW.md +++ /dev/null @@ -1,155 +0,0 @@ -# EOPatch2 Instruction Manual - -The patch requires the use of rapid-acting U-100 type insulin, such as NovoRapid or Humalog. Use a rapid-acting insulin that is suitable for you according to your doctor’s prescription and inject the prescribed dosage. - -The smallest injectable dose of insulin when using the patch is 0.05 U. The Profile BAS should therefore be set at a minimum value of 0.05 U/hr or more and an interval of 0.05 U/hr, as otherwise there may be an error between the estimated total infusion amount in the Profile and the actual infusion amount in the patch. Likewise, the bolus must also be set and infused with a minimum infusion volume of 0.05 U. - -## Pump Setup -1. On the AndroidAPS home screen, click the hamburger menu in the upper left corner and go to Config Builder. -1. Select 'EOPatch2' in the Pump section. -1. Press the Back key to return to the home screen. - -![Bild1](../../images/EOPatch/Bild1.png) ![Bild2](../../images/EOPatch/Bild2.png) - -## Paramètres -Select EOPATCH2 at the top of the home screen to go to the EOPATCH2 tab. - -Select the EOPatch2 Preferences menu by clicking the three dots in the upper right corner. - -The EOPatch2 Preferences menu offers a menu to set 3 types of notifications. - -### Low reservoir Alerts -A warning appears when the amount of insulin remaining in the reservoir reaches the set value or less while using the patch. It can be set from 10 to 50U in 5U increments. - -### Patch expiration Reminder -This is a reminder to notify you of the time remaining before the current patch expires. It can be set from 1 to 24 hours in 1 hour increments. The initial setting value is 4 hours. - -### Patch buzzer Reminder -This is a reminder function for injections other than basal injection. If you are using an (extended) bolus injection or a temporary basal injection, the patch will make a buzzer sound when the injection starts and when the injection is complete. The initial setting value is Off. - -![Bild3](../../images/EOPatch/Bild3.png) - -## Connecting the Patch - -### Move to patch connection screen - -Select EOPATCH2 at the top of the home screen and click the ACTIVATE PATCH button at the bottom left. - -![Bild4](../../images/EOPatch/Bild4.png) - -### Connecting the patch -Insert the syringe needle into the insulin inlet on the patch and then slowly push the piston to inject the insulin. When insulin is filled with more than 80U, the patch makes a booting sound (1 buzzer) and boots. After confirming the buzzer sound, click the START PAIRING button on the screen. - -[Warning] - -- Do not turn the needle action lever until instructed. It can cause serious problems during injection or safety checks otherwise. -- The amount of insulin that can be injected into the patch is 80~200U. If you inject less than 80U into the patch initially, the patch will not work. -- Take the insulin to be put into the patch from the refrigerator and leave it at room temperature for 15 to 30 minutes beforehand. The temperature of the insulin to be injected must be at least 10°C. - -![Bild5](../../images/EOPatch/Bild5.png) - -### patch pairing -The Patch pairing screen will be displayed, and pairing will be attempted automatically. If communication is successful, the Bluetooth pairing request notification appears. Click OK and when the Bluetooth pairing request notification appears a second time with the authentication code, select OK again. - -[Warning] - -- For pairing, the patch and the smartphone must be located within 30 cm of each other. -- After the patch booting is completed, the patch will beep every 3 minutes until the pairing is complete. -- After booting the patch, the patch application must be completed via the app within 60 minutes. If the application cannot be completed within 60 minutes, the patch should be discarded. - -![Bild6](../../images/EOPatch/Bild6.png) ![Bild7](../../images/EOPatch/Bild7.png) ![Bild8](../../images/EOPatch/Bild8.png) - - -### patch preparation -After removing the adhesive tape of the patch, check if the needle is sticking out. If there are no problems with the patch, click NEXT. - -![Bild9](../../images/EOPatch/Bild9.png) - -### Patch attachment -Insulin should be injected in a spot with subcutaneous fat but few nerves or blood vessels, so it is recommended to use the abdomen, arm, or thigh for the patch attachment site. Choose a patch attachment site and apply the patch after disinfecting the location. - -[Warning] - -- Make sure to straighten the side of the patch tape attached to the body evenly, so that the patch adheres completely to the skin. -- If the patch does not stick completely, air may enter between the patch and the skin, which can weaken the adhesive strength and waterproof effect of the patch. - -![Bild10](../../images/EOPatch/Bild10.png) - -### Safety Check -When patching is complete, touch Start Safety Check. When the safety check is completed, the patch will beep once. - -[Warning] - -- For safe use, do not turn the needle action lever until the safety check has been completed. - -![Bild11](../../images/EOPatch/Bild11.png) ![Bild12](../../images/EOPatch/Bild12.png) - - -### Inserting the needle -The needle is inserted by holding around the patch and turning the needle action lever more than 100° in the upward direction of the lever. There is a buzzer sound when the needle is inserted correctly. Turn the needle action lever further clockwise to release the lever. Click NEXT. - -[Caution] - -- If you go to the next step without the buzzer sounding, a needle insertion error warning will appear. - -## Discarding the patch -Patches must be replaced in the case of low insulin levels, usage expiration, and defects. The recommended usage period for each patch is 84 hours after booting the patch. - -### Discarding the patch -Select EOPATCH2 at the top of the home screen and click the DISCARD/CHANGE PATCH button at the bottom. On the next screen, click the DISCARD PATCH button. A dialog box appears to confirm once more and if you select the DISCARD PATCH button, the disposal is completed. - -![Bild13](../../images/EOPatch/Bild13.png) ![Bild14](../../images/EOPatch/Bild14.png) ![Bild15](../../images/EOPatch/Bild15.png) ![Bild16](../../images/EOPatch/Bild16.png) - -## Suspendre et reprendre l'injection d'Insuline -Suspending insulin delivery also cancels both extended bolus and temporary basal. When resuming insulin delivery, the canceled extended bolus and temporary basal will not be resumed. And when insulin delivery is suspended, the patch will give a sound every 15 minutes. - -### Suspending insulin delivery -Select EOPATCH2 at the top of the home screen and click the SUSPEND button at the bottom right. When you select CONFIRM in the confirmation box, a time selection box appears. If you select the CONFIRM button after selecting the time, the insulin delivery will be suspended for the set amount of time. - -![Bild17](../../images/EOPatch/Bild17.png) ![Bild18](../../images/EOPatch/Bild18.png) ![Bild19](../../images/EOPatch/Bild19.png) - - -### Resuming insulin delivery -Select EOPATCH2 at the top of the home screen and click the RESUME button at the bottom right. Insulin delivery will resume by selecting CONFIRM in the confirmation dialog box. - -![Bild20](../../images/EOPatch/Bild20.png) ![Bild21](../../images/EOPatch/Bild21.png) - -## Alarms/Warnings - -### Alarm - -Alarms are issued for emergency situations of the highest priority and require immediate action. The alarm signal does not disappear or time out until it is acknowledged. An alarm occurs when there is a problem with the patch being used, so there may be cases where the patch in use needs to be discarded and replaced with a new patch. The warning is displayed as a dialog box and switching to another screen is not possible until processing is completed. - -![Bild22](../../images/EOPatch/Bild22.png) ![Bild23](../../images/EOPatch/Bild23.png) - -The different types of alarms are explained below. - -| Alarms | Explanation | -| -------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| Empty reservoir | Occurs when the patch’s reservoir runs out of insulin. | -| Patch expired | Occurs when the patch usage time has expired, and no further insulin injections are possible. | -| Occlusion | Occurs when it appears that the patch's insulin inlet is clogged. | -| Power on self-test failure | Occurs when the patch finds an unexpected error during the post-boot self-test process. | -| Inappropriate temperature | Occurs when the patch is outside the normal operating temperature range during patch application and use. To deal with this alarm, move the patch to an appropriate operating temperature (4.4 to 37°C) condition. | -| Needle insertion Error | Occurs when needle insertion is not normal during the patch application process. Check that the needle insertion edge of the patch and the needle activation button are in a straight line. | -| Patch battery Error | Occurs just before the patch’s internal battery runs out and powers off. | -| Patch activation Error | Occurs when the app fails to complete the patching process within 60 minutes after the patch is booted. | -| Patch Error | Occurs when the patch encounters an unexpected error while applying and using the patch. | - -### Warning - -A warning occurs in a medium or low-priority situation. When a warning occurs, it is displayed as a notification in the Overview screen. - -![Bild24](../../images/EOPatch/Bild24.png) - -The different types of warnings are explained below. - -| Warnings | Explanation | -| ---------------------------- | ------------------------------------------------------------------------------------------------------------------------------------- | -| End of insulin suspend | Occurs when the time set by the user has elapsed after the insulin infusion suspension has been completed. | -| Low reservoir | Occurs when the remaining amount of insulin in the patch is below the set amount. | -| Patch operating life expired | Occurs when the patch usage period is over. | -| Patch will expire soon | Occurs 1 hour before the patch must be discarded. | -| Incomplete Patch activation | Occurs when more than 3 minutes have elapsed due to an interruption during patch application in the stage after pairing is completed. | -| Patch battery low | Occurs when the patch's battery is low. | - diff --git a/docs/CROWDIN/fr/Configuration/Hardware/index.md b/docs/CROWDIN/fr/Configuration/Hardware/index.md deleted file mode 100644 index 9215e2770d45..000000000000 --- a/docs/CROWDIN/fr/Configuration/Hardware/index.md +++ /dev/null @@ -1,27 +0,0 @@ -# Hardware-Configuration - -## Configuration - -## BG Source - -- [BG Source](../BG-Source.md) -- [xDrip+ Settings](../xDrip.md) -- [Dexcom G6 hints](../Dexcom.md) -- [Smoothing blood glucose data](../../Usage/Smoothing-Blood-Glucose-Data-in-xDrip.md) - -## Pumps - -- [Dana-R pump](../DanaR-Insulin-Pump.md) -- [Dana-RS pump](../DanaRS-Insulin-Pump.md) -- [Accu-Chek Combo pump](../Accu-Chek-Combo-Pump.md) -- [Accu-Chek Insight pump](../Accu-Chek-Insight-Pump.md) -- [Medtronic pump](../MedtronicPump.md) - -## Phones - -- [Jelly Pro Settings](../../Usage/jelly.md) -- [Huawei Settings](../../Usage/huawei.md) - -## Smartwatch - -- [Watchfaces](../Watchfaces.md) diff --git a/docs/CROWDIN/fr/Getting-Started/ClosedLoop.md b/docs/CROWDIN/fr/Getting-Started/ClosedLoop.md deleted file mode 100644 index b6b013718465..000000000000 --- a/docs/CROWDIN/fr/Getting-Started/ClosedLoop.md +++ /dev/null @@ -1,55 +0,0 @@ -# Qu'est ce qu'un Système de boucle fermée ? - -![AAPS est comme un pilote automatique](../images/autopilot.png) - -Un système de boucle fermée du pancréas artificiel combine différents composants afin de vous faciliter la gestion du diabète. Dans son grand livre [Automated Insulin Delivery](https://www.artificialpancreasbook.com/) Dana M. Lewis, une des fondatrices du mouvement "Open Source closed loop" (Boucle fermée en open Source), appelle cela ["pilote automatique pour votre diabète"](https://www.artificialpancreasbook.com/3.-getting-started-with-your-aps). Mais qu'est-ce que cela signifie ? - -**Pilot automatique dans un avion** - -Le pilote automatique ne fait pas le travail complet et ne donne pas la possibilité au pilote de dormir pendant tout le vol. Il facilite le travail des pilotes. Il les soulage de la charge de la surveillance permanente de l'avion et de l'attitude de vol. Cela permet au pilote de se concentrer sur la surveillance de l'espace aérien et le contrôle des fonctions du pilote automatique. - -Le pilote automatique reçoit des signaux de différents capteurs, un ordinateur les évalue avec les spécifications du pilote et effectue ensuite les ajustements nécessaires. Le pilote n'a plus à s'inquiéter des ajustements constants. - -**Système de boucle fermée** - -Il en va de même pour un système de boucle fermée du pancréas artificiel. Il ne fait pas tout le travail, vous devez toujours faire attention à votre diabète. Un système de boucle fermée combine les données du capteur d'une MGC/MGF avec vos spécifications de gestion du diabète telles que le taux de basal, le facteur de sensibilité à l'insuline (SI) et le ratio du glucides/insuline (G/I). De cette façon, il calcule les propositions de traitements et implémente ces petits ajustements permanents afin de garder votre diabète dans la plage cible et vous soulager. Cela vous laisse plus de temps pour votre vie "à côté" du diabète. - -Tout comme vous ne voudriez pas monter dans un avion où seul un pilote automatique vole sans surveillance humaine, un système de boucle fermée vous aide à gérer votre diabète, mais a toujours besoin de votre soutien! **Même avec une boucle fermée, vous ne pouvez pas simplement oublier votre diabète !** - -Tout comme le pilote automatique dépend des valeurs du capteur ainsi que des spécifications du pilote, un système de boucle fermée nécessite des entrées adaptées, telles que les débits de basal, la SI et le rapport G/I, pour vous aider à réussir. - -## Systèmes de boucle fermée de pancréas artificiels en Open Source - -À l'heure actuelle, il existe trois grands systèmes de boucle fermée en Open Source : - -### AndroidAPS (AAPS) - -AAPS is described in detail in [this documentation](./WhatisAndroidAPS.html). Il utilise un Smartphone Android pour le calcul et le contrôle de votre pompe à insuline. Il est en étroite collaboration avec OpenAPS (par ex. ils partagent les algorithmes). - -Les [pompes](../Hardware/pumps.md) compatibles sont : - -- [DanaR](../Configuration/DanaR-Insulin-Pump.md) / [DanaRS & Dana-i](../Configuration/DanaRS-Insulin-Pump.html) -- [Accu-Chek Combo](../Configuration/Accu-Chek-Combo-Pump.md) -- [Accu-Chek Insight](../Configuration/Accu-Chek-Insight-Pump.md) -- [Diaconn G8](../Configuration/DiaconnG8.md) -- [Omnipod Dash](../Configuration/OmnipodDASH.md) -- [Omnipod Eros](../Configuration/OmnipodEros.md) -- quelques anciennes [Pompes Medtronic](../Configuration/MedtronicPump.md) - -### OpenAPS - -[OpenAPS](https://openaps.readthedocs.io) a été le premier système de boucle fermée Open Source. Il utilise un petit ordinateur comme un Raspberry Pi ou un Intel Edison. - -Les pompes compatibles sont : - -- quelques anciennes pompes Medtronic - -### Loop pour iOS - -[Loop pour iOS](https://loopkit.github.io/loopdocs/) est le système de boucle fermée Open Source à utiliser avec un iPhone Apple. - -Les pompes compatibles sont : - -- Omnipod Dash -- Omnipod Eros -- quelques anciennes pompes Medtronic diff --git a/docs/CROWDIN/fr/Getting-Started/GlossaryTest.md b/docs/CROWDIN/fr/Getting-Started/GlossaryTest.md deleted file mode 100644 index ab0ab32475a6..000000000000 --- a/docs/CROWDIN/fr/Getting-Started/GlossaryTest.md +++ /dev/null @@ -1,391 +0,0 @@ -# Glossaire - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
AcronymeDescriptionvoir aussien savoir plus @
AAPSAndroidAPS - Système Pancréas Artificiel  
AAR (AMA)Assistance Améliorée Repas - Algorithme Amélioré pour gérer les glucides des RepasAR / SMBWiki - AAR
Android AutoAffichage des notifications AAPS sur l'écran intégré au tableau de bord de votre voiture Wiki - Android Auto
APKFichier d'installation du logiciel (package d’application Android) Wiki - Construire le fichier APK
Autosenscalcul de la sensibilité à l'insuline (pouvant varier selon l'exercice physique, les hormones etc). DIABETTECH - Autosens
Azureplateforme cloud pour héberger les données NightscoutHeroku / NightscoutAzure
BATalerte de batterie faible de la pompe sur l'écran d'accueilCAN / INS / RES /SEN Préférences
Copie d'écran
GlyGlycémie  
IG (BGI)Impact Glycémique - degré auquel la glycémie "devrait" monter ou baisser en fonction de la seule activité de l'insuline  
Source des glycémiesD'où proviennent vos valeurs de glycémie?MGC / MGFWiki - source Glycémie
Blukon Nightreadertransmetteur bluetooth pour transformer le Freestyle Libre en MGCBlueReader / MiaoMiaoAmbrosia Blukon Nightreader
DB (BR)Débit de Base  
AgeCAge Canule - affiché dans Nightscout si l'information a été renseignée dans l'onglet / menu Actions de AAPS ou par l'intermédiaire de l'action 'AMORCER' de l'onglet ACTNightscout 
CANalerte de changement de la canule sur l'écran d'accueilINS / RES / SEN / BAT Préférences
Copie d'écran
MGCMesure de Glycémie en Continue  
Boucle Ferméeles systèmes à boucle fermée font les réglages du débit de base automatiquement, sans avoir besoin de l'approbation de l'utilisateur, en se basant sur un algorithmeBoucle OuverteWiki - boucle fermée
GAGlucides Actifs  
DAIDurée d'Action de l'Insuline Wiki - types d'insulines
DIABETTECH - DIA
heure d'étéchangement d'heure Wiki - heure d'été
eGLUC"Glucides Etendus" - glucides mettant plusieurs heures à être assimilés (notamment avec beaucoup de graisses ou de protéines)
les bolus étendus que vous pourriez connaître da,s le cas d'une thérapie sous pompe à insuline n'ont pas beaucoup d'intérêt dans le cas d'une boucle fermée		SMBWiki - eGLUC
Cas d'utilisation des glucides étendus
MGFMesure de Glycémie Flash (Freestyle Libre) Wiki - source Glycémie
gitsystème de contrôle des versions pour le suivi des modifications dans les fichiers informatiques et la coordination des travaux sur les fichiers
-> nécessaire pour les mises à jour APK		 Wiki - mettre à jour le fichier APK
GitHubservice d'hébergement web pour le contrôle de version utilisant Git
-> stockage du code source de AAPS		 Github AndroidAPS
Glimpapplication pour récupérer les glycémies du Freestyle Libre Nightscout avec Glimp
Herokuplateforme cloud pour héberger les données NightscoutAzure / NightscoutHeroku
G/I (IC)ratio Glucide / Insuline (combien de glucides sont couverts par une unité d'insuline ?)  
IAInsuline Active dans votre corps  
SI Sensibilité InsulineSensibilité à l'Insuline - diminution prévue de la glycémie pour une unité d'insuline  
AGB (LGS)Arrêt Glycémie Basse
AAPS réduira le débit de base si la glycémie baisse rapidement. Mais si la glycémie augmente, il ne fera qu'augmenter le débit de base si l'IA (IOB) est négatif (à partir d'un AGB précédent), sinon les débits de base resteront les mêmes que ceux de votre profil sélectionné. Vous pouvez subir temporairement des pics de glycémie à la suite d'hypos sans pouvoir augmenter le débit de base sur le rebond.		objectif 6 
LineageOSSystème d'exploitation open-source pour les smartphones, etc.
OS alternatifs pour les smartphones ne fonctionnant pas Android 8.1 (Oreo)
(lors de l'utilisation de Accu-Chek Combo)		 Wiki - Pompe Combo
Fichiers logenregistrement de toutes les actions d'AAPS (utiles pour le dépannage et le débogage) Wiki - fichiers log
maxIA (maxIOB)fonction de sécurité - niveau d'insuline actvie maximal que AAPS ne peut pas dépasser Wiki - maxIA
Wiki - SMB
MiaoMiaotransmetteur bluetooth pour transformer le Freestyle Libre en MGCBlueReader / Blukon NightreaderMiaoMiao
min_5m_carbimpactfonction de sécurité - quantité de glucides assimilés par défaut lorsque l’absorption ne peut pas être calculée dynamiquement en fonction de vos glycémies Wiki - Générateur de configuration
Nightscoutprojet open source pour accéder aux données MGC (CGM) et faire des rapportsNightscout ReporterNightscout
NS Clientfait partie d'AAPS pour se connecter à votre site Nightscout Wiki - NS Client
Nightscout ReporterOutil permettant aux utilisateurs de la boucle fermée de générer des rapports PDF à partir des données enregistrées dans NightscoutNightscoutNightscout Reporter
NS Reporter @Facebook
Objectifsprogramme d'apprentissage au sein d'AAPS qui vous guide étape par étape, de la boucle ouverte à la boucle fermée Wiki - objectifs
OpenAPSopen artificial pancreas system
APS run on small computers (i.e. Raspberry Pie)
AAPS uses some of the OpenAPS features		 Documentation OpenAPS
Boucle Ouvertele système proposera des ajustements recommandés qui doivent être effectués manuellement sur la pompeBoucle FerméeWiki - Générateur de configuration
Oref0 / Oref1détection de sensibilité
"implémentation de la conception de référence version 0/1" - l'algorithme clé derrière OpenAPS		 Wiki - détection de sensibilité
Temps du picheure de l'effet maximum de l'insuline injectée Wiki - Générateur de configuration
HPhistorique de la pompe (entrée dans l'onglet traitements) Captures d'écran
Prédictionspréditions pour les futures glycémies se basant sur différents calculs Wiki - courbes de préditions
Profilparamètres de traitement (débits de base, DAI, G/I, SI, cible Gly)
peuvent être définis localement ou via Nightscout		NightscoutWiki - profil
Changement de profil(temporaire) changement du profil utilisé ou augmentation / diminution du pourcentage Wiki - changement de profil
RESalerte de changement de réservoir sur l'écran d'accueilCAN / INS / BAT Préférences
Copie d'écran
RileyLinkdispositif matériel open source pour convertir le Bluetooth Low Energy (BLE) vers les communications sans fil 916MHz (utilisé pour les anciennes pompes Medtronic)OpenAPS 
AgeCâge du capteur - affiché dans Nightscout si l'information a été renseignée dans l'onglet / menu Actions de AAPSNightscout 
SENalerte de changement de capteur sur l'écran d'accueilCAN / INS / RES / BAT Préférences
Copie d'écran
Détection de sensibilitécalcul de la sensibilité à l'insuline (pouvant varier selon l'exercice physique, les hormones etc). DIABETTECH - Autosens
Bruit Capteurlectures MGC instables conduisant à des "sauts" de glycémies Wiki - bruit capteur
SMBSuper Micro Bolus
fonction avancée pour un ajustement de la glycémie plus rapide		RNS (UAM)Wiki RNS
Super bolustransfert de l'insuline de base vers le bolus pour accélérer la correction de glycémie John Walsh - Le Super Bolus
DTB (TBB)Débit Total de Base (somme des débits de base sur 24 heures  
DBT (TBR)Débit de Base Temporaire  
DTIDosage Total d'Insuline (bolus + base par jour)  
CTCible Temporaire
augmentation / diminution temporaire de la cible glycémique (plage)		 Wiki - Cibles temp.
RNS (UAM)Repas Non Signalés - détection d'une augmentation significative de la glycémie dûe aux repas, à l'adrénaline ou à d'autres influences et tentative d'ajustement avec SMBSMBWiki RNS
Pompe virtuelleoption permettant d'essayer les fonctions de AndroidAPS à l'aide d'un modèle de pompe sans pilote AAPS pour le bouclageBoucle Ouverte 
Fonds d'écranImage d'arrière-plan de AndroidAPSvoir la page des smartphones
xDrip / xDrip+logiciel open source pour lire les systèmes MGC (CGM) xDrip +
xDrip
Zéro-tempdébit de base temporaire à 0% (pas d'injection d'insuline basale)  
Voir aussi https://openaps.readthedocs.io/en/latest/docs/Resources/glossary.html
diff --git a/docs/CROWDIN/fr/Getting-Started/Safety-first.md b/docs/CROWDIN/fr/Getting-Started/Safety-first.md deleted file mode 100644 index 7606d248b1c9..000000000000 --- a/docs/CROWDIN/fr/Getting-Started/Safety-first.md +++ /dev/null @@ -1,41 +0,0 @@ -# La sécurité avant tout - -**Quand vous décidez de construire votre propre pancréas artificiel, c’est toujours important de penser à la sécurité et à la sûreté, et de bien comprendre les impacts de toutes vos actions** - -## Généralités - -- AAPS is a just a tool to help you manage diabetes, it is not a fully automated system you can install and forget! -- Do not assume that AAPS will never make mistakes. Le dispositif prend le contrôle de la délivrance d’insuline : surveillez le tout le temps, comprenez comment il fonctionne, et apprenez comment interpréter ses actions. -- N’oubliez pas que, une fois appairé, le téléphone peut demander à la pompe de faire n'importe quelle action. Only use this phone for AAPS and, if being used by a child, essential communications. N’installez pas des applications ou des jeux (!!!) inutiles qui pourraient introduire des logiciels malveillants comme des chevaux de troie, des virus ou des robots qui pourraient interférer avec votre système. -- Installez toutes les mises à jour de sécurité proposées par le fabricant de votre téléphone et Google. -- Vous pourriez aussi avoir besoin de modifier vos habitudes en tant que diabétique lorsque vous changez de thérapie en utilisant un système de boucle fermée. Par ex. some people report, they need less hypo treatments as AAPS has already reduced insulin. - -## Communicateur SMS - -- AAPS vous permet de controler le téléphone d’un enfant à distance via un SMS. Si vous activez le Communicateur SMS, rappelez-vous toujours que le téléphone configuré pour donner des commandes distantes pourrait être volé. Donc, toujours le protéger au minimum par un code PIN. -- AAPS vous informera également par SMS si vos commandes à distance, comme un bolus ou un changement de profil, ont été effectuées. Il est conseillé de le configurer de sorte que les SMS de confirmation soient envoyés à au moins deux numéros de téléphone différents au cas où l'un des téléphones destinataires serait volé. - -(Safety-first-aaps-can-also-be-used-by-blind-people)= -## AAPS can also be used by blind people - -Sur les appareils Android, TalkBack fait partie du système d'exploitation. Il s'agit d'un programme pour s'orienter sur l'écran avec la voix. With TalkBack you can operate your smartphone as well as AAPS blind. - -We users create the AAPS app ourselves with Android Studio. Beaucoup utilisent Microsoft Windows à cette fin, à l'aide du lecteur d'écran ("Screenreader"), qui est analogue à TalkBack. Comme Android Studio est une application Java, le composant "Java Access Bridge" doit être activé dans le Panneau de configuration. Dans le cas contraire, le lecteur d'écran du PC ne pourra pas fonctionner dans Android Studio. - -Pour ce faire, veuillez procéder comme suit: - -- Appuyez sur la touche "Windows" et entrez "Panneau de configuration" dans le champ de recherche, appuyez sur la touche "Entrée" pour l'ouvrir. Cela ouvre : "Tous les éléments du panneau de configuration". -- Appuyez sur la lettre C pour aller à "Centre pour la facilité d'utilisation", appuyez sur la touche "Entrée" pour l'ouvrir. -- Puis ouvrez "Utiliser l'ordinateur sans écran" en appuyant sur "Entrée". -- Là, en bas, vous trouverez la case à cocher "Activer Java Access Bridge", sélectionnez-la. -- Terminé, il suffit de fermer la fenêtre ! Le lecteur d'écran devrait fonctionner maintenant. - -```{note} -**AVIS DE SÉCURITÉ IMPORTANT** - -La base des fonctions de sécurité d'AAPS présentée dans cette documentation s'appuie sur les fonctions de sécurité du matériel utilisé pour construire votre système. Il est extrêmement important que vous utilisiez uniquement une pompe à insuline et un capteur de MGC approuvés FDA/CE pour mettre en oeuvre une boucle fermée d'administration automatique d'insuline. Les modifications matérielles ou logicielles de ces composants peuvent entraîner un dosage incorrect de l'insuline, causant un risque significatif pour l'utilisateur. Si vous trouvez ou recevez des pompes à insuline ou des récepteurs MGC cassés, modifiés ou fabriqués par vos soins, *ne les utilisez pas* pour créer un système AAPS. - -De plus, il est également important d'utiliser uniquement des fournitures d'origine telles que serteurs, canules et réservoirs d'insuline approuvés par le fabricant pour une utilisation avec votre pompe ou votre MGC. L'utilisation de consommables non testés ou modifiés peut entraîner une imprécision du MGC et des erreurs de dosage de l'insuline. L'insuline est très dangereuse lorsqu'elle est mal dosée - veuillez ne pas jouer avec votre vie en piratant avec vos fournitures. - -Enfin et surtout, vous ne devez pas prendre d'inhibiteurs du SGLT-2 (gliflozines), car ils abaissent de façon incalculable la glycémie. La combinaison avec un système qui réduit les débits de base pour augmenter la glycémie est particulièrement dangereuse car en raison de la gliflozine, cette augmentation de glycémie pourrait ne pas se produire et un état dangereux d'absence d'insuline peut se produire. -``` diff --git a/docs/CROWDIN/fr/Getting-Started/Sample-Setup.md b/docs/CROWDIN/fr/Getting-Started/Sample-Setup.md deleted file mode 100644 index 01e839cc929c..000000000000 --- a/docs/CROWDIN/fr/Getting-Started/Sample-Setup.md +++ /dev/null @@ -1,151 +0,0 @@ -# Exemple d'installation : Samsung S7, DanaRS, Dexcom G6 et montre connectée Sony - -![Exemple de configuration](../images/SampleSetup.png) - -## Description - -Dans cette configuration, le smartphone Samsung Galaxy S7 est utilisé comme centre de contrôle de la boucle. L'application Dexcom légèrement modifiée lit les valeurs de glycémie du MGC Dexcom G6. AndroidAPS est utilisé pour contrôler la pompe à insuline Dana RS du fabricant coréen SOOIL via bluetooth. D'autres appareils ne sont pas requis. - -Comme l'application Dexcom offre uniquement des options d'alarme limitées, l'application open source xDrip+ est utilisée pour définir non seulement des alarmes élevées et basses, mais aussi des alarmes supplémentaires selon les besoins individuels. - -Une montre smartwatch Android peut être utilisée (dans cet exemple, le Sony Smartwatch 3 (SWR50)) pour afficher les valeurs de glycémie et AndroidAPS sur votre poignet (optionnel). La montre peut même être utilisée pour contrôler AndroidAPS (par ex. pour lancer discrètement un bolus de repas). - -Le système fonctionne hors ligne. Cela signifie qu'il n'est pas nécessaire d'utiliser une connexion de données depuis le smartphone vers Internet. - -Néanmoins, les données sont automatiquement envoyées à Nightscout "in the cloud = dans le nuage" lorsqu'une connexion est établie. En faisant cela, vous pouvez fournir des rapports complets lors de la visite de votre médecin ou partager les valeurs avec les membres de votre famille à tout moment. Il est également possible d'envoyer des données à Nightscout uniquement lorsque vous utilisez une connexion Wi-Fi (prédéfinie) afin de profiter des différents rapports Nightscout. - -## Composants requis - -1. Samsung Galaxy S7 - - * Alternatives : voir [liste des téléphones et montres testés](https://docs.google.com/spreadsheets/d/1gZAsN6f0gv6tkgy9EBsYl0BQNhna0RDqA9QGycAqCQc/edit) pour AndroidAPS - -2. [DanaRS](http://www.sooil.com/eng/product/) - - * Alternatives: - * [Accu-Chek Combo](../Configuration/Accu-Chek-Combo-Pump.md) - * [Accu-Chek Insight](../Configuration/Accu-Chek-Insight-Pump.md) - * [DanaR](../Configuration/DanaR-Insulin-Pump.md) - * [Quelques anciennes pompes Medtronic (également nécessaire : RileyLink/Gnarl hardware, téléphone Android avec bluetooth low energy / BLE-chipset)](../Configuration/MedtronicPump.md) - * D'autres pompes pourraient être disponibles à l'avenir, voir [futures pompes possibles](Future-possible-Pump-Drivers.md) pour plus de détails. - -3. [Dexcom G6](https://dexcom.com) - - * Alternatives: see list of possible [BG sources](../Configuration/BG-Source.md) - -4. Optionnel : Sony Smartwatch 3 (SWR50) - - * Alternatives : Toutes les [montres avec Google Wear OS](https://wearos.google.com/intl/de_de/#find-your-watch) devraient fonctionner correctement, pour plus de détails, voir la [liste des téléphones et montres testés](https://docs.google.com/spreadsheets/d/1gZAsN6f0gv6tkgy9EBsYl0BQNhna0RDqA9QGycAqCQc/edit) pour AndroidAPS (l'OS doit être Android Wear ou Wear OS) - -## Configuration de Nightscout - -Voir la configuration détaillée [Nightscout](../Installing-AndroidAPS/Nightscout.md) - -## Configuration de l'ordinateur - -Pour pouvoir créer une application Android à partir du code source AAPS disponible gratuitement, vous devez disposer d'Android Studio sur votre ordinateur (Windows, Mac, Linux). Les instructions détaillées peuvent être trouvées sur : [construction de l'APK](../Installing-AndroidAPS/Building-APK.md). - -Soyez patient lors de l'installation d'Android Studio car le logiciel télécharge beaucoup de données supplémentaires une fois installé sur votre ordinateur. - -## Configuration du Smartphone - -![Smartphone](../images/SampleSetupSmartphone.png) - -### Vérifier le firmware (logiciel interne) du smartphone - -* Menu > Paramètres > A propose du téléphone > Informations sur le logiciel : au moins "Android-Version 8.0" (testé avec succès jusqu'à Android version 8.0.0 Oreo - Samsung Experience Version 9.0) -* Pour la mise à jour du firmware : menu > paramètres > mise à jour du logiciel - -### Autoriser l'installation d'applications issues de sources inconnues - -Menu > Paramètres > Sécurité de l'appareil > Sources inconnues > curseur vers la droite (= actif) - -Pour des raisons de sécurité, ce paramètre devrait être réglé à nouveau sur inactif une fois l'installation de toutes les applications décrites ici terminée. - -### Activez le Bluetooth - -1. Menu > Paramètres > Connections > Bluetooth > curseur vers le côté droit (= actif) -2. Menu > Paramètres > Connections > Emplacement > curseur vers le côté droit (= actif) - -Les services de géolocalisation ("GPS") doivent être activés pour que Bluetooth fonctionne correctement. - -### Installer l'application Dexcom (version modifiée) - -![App Dexcom (patchée)](../images/SampleSetupDexApp.png) - -L'application Dexcom originale du Google Play Store ne fonctionnera pas parce qu'elle ne diffuse pas de valeurs vers d'autres applications. Par conséquent, une version légèrement modifiée par la communauté est nécessaire. Seule cette application Dexcom modifiée peut communiquer avec AAPS. De plus, l'application Dexcom modifiée peut être utilisée avec tous les smartphones Android et non pas seulement ceux de [la liste de compatibilité Dexcom](https://www.dexcom.com/dexcom-international-compatibility). - -Pour ce faire, effectuez les étapes suivantes sur votre smartphone : - -1. Si l'application Dexcom originale est déjà installée : - * Arrêter le capteur - * Désinstallez l'application via Menu > Paramètres > Apps > Dexcom G6 Mobile > Désinstaller -2. Download and install the [BYODA Dexcom ap](../Hardware/DexcomG6.md#if-using-g6-with-build-your-own-dexcom-app) -3. Démarrez l'application Dexcom G6 patchée, activez/calibrez le capteur selon les instructions données et attendez la fin de la phase de démarrage. -4. Une fois que l'application Dexcom patchée affiche la valeur actuelle de la glycémie, configurez les alertes (menu hamburger sur le côté gauche de l'écran) comme suit : - * Urgent glycémie basse `55mg/dl` / `3.1mmol/l` (impossible à désactiver) - * Glycémie basse `OFF` - * Glyécmie haute `OFF` - * Taux d'augmentation `OFF` - * Taux de baisse `OFF` - * Perte de signal `OFF` - -## Installer AndroidAPS - -1. Follow the instructions to [build the APK](../Installing-AndroidAPS/Building-APK.md#generate-signed-apk) -2. [Transfer](../Installing-AndroidAPS/Building-APK.md#transfer-apk-to-smartphone) the generated APK to your phone -3. [Configurez AndroidAPS](../Configuration/Config-Builder.md) selon vos besoins en utilisant l'assistant de configuration ou manuellement -4. Dans cet exemple de configuration, nous avons utilisé (entre autres) - -* BG source: `Dexcom G6 App (patched)` -- click cock-wheel and activate `Upload BG data to NS` and `Send BG data to xDrip+` (see [BG source](../Configuration/BG-Source.md)) - -![Paramètres G5](../images/SampleSetupG5Settings.png) - -* NSClient activé (voir [Nightscout](../Installing-AndroidAPS/Nightscout.md)) - -## Installer xDrip+ - -xDrip+ est une autre application open source très aboutie qui offre d'innombrables possibilités. Dans cette configuration, contrairement à l'utilisation première prévue par les développeurs, xDrip+ n'est pas utilisée pour collecter des données de glycémie à partir du Dexcom G6, mais seulement pour utiliser des alarmes et afficher la valeur de glycémie actuelle, y compris la courbe sur l'écran d'accueil Android dans le widget. Avec xDrip+ les alarmes peuvent être réglées beaucoup plus individuellement qu'avec le logiciel Dexcom, AAPS ou Nightscout (sans limitation dans la sélection des sons, différentes alarmes selon le jour/nuit etc.). - -1. Téléchargez la dernière version stable de xDrip+ avec votre smartphone - pas la version de Google Play Store! -2. Installez xDrip+ en sélectionnant le fichier APK téléchargé. -3. Démarrez xDrip+ et indiquez les paramètres suivants (menu hamburger en haut à gauche) - * Paramètres > Alarmes et alertes > Liste d'alerte de niveau Glucose > Créer des alertes (hautes et basses) selon vos besoins. - * Les alarmes existantes peuvent être modifiées avec une longue pression sur l'alarme. - * Paramètres > Alarmes et alertes > Alertes de calibrage : désactivées (rappelées via l'application Dexcom modifiée) - * Paramètres > Source de données matérielles > 640G/EverSense - * Paramètres > Paramètres Inter-app > Accepter les calibrations > `ON` - * Menu > Démarrer le capteur (n'est rien qu'un "pro forma" et n'a rien à voir avec le capteur G6 en cours. Ceci est nécessaire sinon un message d'erreur apparaîtra régulièrement.) - -For more information about xDrip+, see here [BG source page](../Configuration/BG-Source.md). - -### Exemple d'une installation d'alarme - -La "Urgent alarme glycémie basse" (en dessous de 55 mg/dl càd. 3,1 mmol) est une alarme standard de l'application Dexcom modifiée qui ne peut pas être désactivée. - -![alarmes xDrip](../images/SampleSetupxDripWarning.png) - -Astuce pour les réunions / visites d'église / cinéma etc..: - -Si le mode "Ne pas déranger" est activé dans le Samsung Galaxy S7 (Menu > Paramètres > Sons et vibrations > Ne pas déranger : curseur vers le côté droit (= actif)), lors d'une alarme basse, le téléphone ne fait que vibrer et ne délivre pas d'avertissement sonore. Pour les autres alarmes configurées via xDrip+ vous pouvez choisir si le mode silencieux doit être ignoré (son joué) ou non. - -## Désactiver l'option économie d'énergie - -Sur votre Samsung Galaxy S7 allez dans Menu > Paramètres > Maintenance de l'appareil > Batterie > Applications non surveillées > + Ajouter des applications : Sélectionnez les applications AndroidAPS, Dexcom G6 Mobile, xDrip+ et Android Wear (si la montre connectée est utilisée) l'une après l'autre - -## Optionnel : Configurer la Sony Smartwatch 3 (SWR50) - -Avec une montre Android Wear, vivre avec son diabète peut être encore plus discrèt. La montre peut être utilisée pour afficher le niveau de glycémie actuel, l'état de la boucle, etc. sur le poignet. La montre peut même être utilisée pour contrôler AndroidAPS (par ex. pour lancer discrètement un bolus de repas). Pour ce faire, appuyez deux fois sur la valeur MGC du cadran d'AAPSv2. Le SWR50 fonctionne généralement pour une journée complète jusqu'à ce que la batterie ait besoin d'être rechargée (même chargeur que le Samsung Galaxy S7 : microUSB). - -![Montres connectées](../images/SampleSetupSmartwatch.png) - -Pour plus d'informations sur les informations affichées sur le cadran, voir [ici](../Configuration/Watchfaces.md). - -* Installez l'application "Android Wear" sur votre smartphone via le Google Play Store et connectez la smartwatch selon les instructions qui y sont données. -* Dans AAPS, choisissez le menu hamburger (coin supérieur gauche) > Générateur de configuration > Général (en bas de la liste) > Wear > Activez sur le côté gauche, cliquez sur la roue crantée > Paramètres de Wear et activez `Commandes depuis la montre` -* Sur votre montre: faites un appui long sur l'afficheur pour changer de cadran et sélectionnez `AAPSv2` -* Si nécessaire redémarrer les deux appareils une fois. - -## Configuration de la pompe - -voir [pompe Dana RS](../Configuration/DanaRS-Insulin-Pump.md) \ No newline at end of file diff --git a/docs/CROWDIN/fr/Getting-Started/WhatisAndroidAPS.md b/docs/CROWDIN/fr/Getting-Started/WhatisAndroidAPS.md deleted file mode 100644 index 270fc7d65846..000000000000 --- a/docs/CROWDIN/fr/Getting-Started/WhatisAndroidAPS.md +++ /dev/null @@ -1,39 +0,0 @@ -# What is a closed loop system with AAPS? - -AAPS is an app that acts as an artificial pancreas system (APS) on an Android smartphone. Qu'est ce qu'un système de pancréas artificiel? C’est un logiciel qui a pour but de faire ce que fait un pancréas vivant : maintenir la glycémie dans les limites saines automatiquement. - -Malheureusement, l’APS ne peut pas faire le même travail qu'un pancréas biologique, mais il peut soulager un diabète de type 1 en le rendant plus facile à gérer avec l’aide des dispositifs disponibles dans le commerce et son logiciel qui est simple et sûr. Those devices include a continuous glucose monitor (CGM) to tell AAPS about your blood sugar levels and an insulin pump which AAPS controls to deliver appropriate doses of insulin. L’application communique avec ces périphériques Bluetooth. Elle effectue les calculs de dosage à l’aide d’un algorithme, ou ensemble de règles, mis au point pour un autre système de pancréas artificiel, appelé OpenAPS, qui a des milliers d’utilisateurs et a accumulé des millions d’heures d’utilisation. - -A note of caution: AAPS is not regulated by any medical authority in any country. Using AAPS is essentially carrying out a medical experiment on yourself. La mise en place du système nécessite détermination et connaissances techniques. Si vous n’avez pas le savoir-faire technique au début, vous l'aurez à la fin. Toutes les informations dont vous avez besoin se trouve dans ces documents, ailleurs en ligne, ou par d’autres personnes qui l'ont déjà fait -- vous pouvez leur demander dans les groupes Facebook ou autres forums. Many people have successfully built AAPS and are now using it entirely safely, but it is essential that every user: - -- Builds the system themselves so that they thoroughly understand how it works -- Adjusts its individual dosage algorithm with his or her diabetes team to work nearly perfect -- Maintains and monitors the system to ensure it is working properly - -```{note} -**Disclaimer and Warning** - -- All information, thought, and code described here is intended for informational and educational purposes only. Nightscout ne fait actuellement aucune tentative de conformité à la confidentialité HIPAA. Utilisez Nightscout et AAPS à vos propres risques et n'utilisez pas les informations ni le code pour prendre des décisions médicales. -- L'utilisation du code de github.com est sans garantie ni support formel d'aucune sorte. Veuillez consulter la LICENCE de ce référentiel pour plus de détails. -- Tous les noms de produits et de sociétés, marques commerciales, marques de service, marques déposées, sont la propriété de leurs détenteurs respectifs. Leur utilisation est à titre informatif et n'implique aucune affiliation avec eux ni aucune approbation de leur part. - -Please note - this project has no association with and is not endorsed by: [SOOIL](http://www.sooil.com/eng/), [Dexcom](https://www.dexcom.com/), [Accu-Chek, Roche Diabetes Care](https://www.accu-chek.com/), [Insulet](https://www.insulet.com/) or [Medtronic](https://www.medtronic.com/). -``` - -Si vous êtes prêt à relever le défi, lisez la suite. - -## Primary goals behind AAPS - -- An app with safety built in. To read about the safety features of the algorithms, known as oref0 and oref1, click here () -- An all-in-one app for managing type 1 diabetes with an artificial pancreas and Nightscout -- An app to which users can easily add or remove modules as needed -- An app with different versions for specific locations and languages. -- An app which can be used in open- and closed-loop mode -- An app that is totally transparent: users can input parameters, see results, and make the final decision -- An app which is independent of particular pump drivers and contains a "virtual pump" so users can safely experiment before using it on themselves -- An app closely integrated with Nightscout -- An app in which the user is in control of safety constraints - -## Comment débuter - -Bien sûr, tout ce contenu ici est très important, mais peut être au début assez déroutant. A good orientation is given by the [Module Overview](../Module/module.md) and the [Objectives](../Usage/Objectives.html). diff --git a/docs/CROWDIN/fr/Hardware/DexcomG4.md b/docs/CROWDIN/fr/Hardware/DexcomG4.md deleted file mode 100644 index 22cc52393536..000000000000 --- a/docs/CROWDIN/fr/Hardware/DexcomG4.md +++ /dev/null @@ -1,6 +0,0 @@ -# Dexcom G4 - -## Si vous utilisez le G4 avec un câble OTG (Nightscout 'traditionnel') -- Si vous ne l'avez pas déjà configuré, téléchargez l'application Nightscout Uploader depuis le Play Store et suivez les instructions sur [Nightscout](https://nightscout.github.io/). -- In AAPS Preferences enter your Nightscout website and API secret. -- Select NSClient in ConfigBuilder (setting in AAPS). diff --git a/docs/CROWDIN/fr/Hardware/Smartwatch.md b/docs/CROWDIN/fr/Hardware/Smartwatch.md deleted file mode 100644 index 797fb1976266..000000000000 --- a/docs/CROWDIN/fr/Hardware/Smartwatch.md +++ /dev/null @@ -1,10 +0,0 @@ -# Montres connectées - -Les montrées connectées sont optionnelles, mais très utiles pour certains utilisateurs. Plus de détails ici : - -- [Liste des téléphones et montres testés](../Getting-Started/Phones.md) -- [Cadrans Wear OS](../Configuration/Watchfaces.md) -- [Dépannage Sony Smartwatch SW 3](../Usage/SonySW3.md) - -## Instructions for Building the AAPS Wear APK for Wear OS -https://androidaps.readthedocs.io/en/latest/remote-control.html#building-the-aaps-wear-apk diff --git a/docs/CROWDIN/fr/Installing-AndroidAPS/Building-APK.md b/docs/CROWDIN/fr/Installing-AndroidAPS/Building-APK.md deleted file mode 100644 index 28a7b03963cf..000000000000 --- a/docs/CROWDIN/fr/Installing-AndroidAPS/Building-APK.md +++ /dev/null @@ -1,369 +0,0 @@ -# Construire l'APK - -## Construire vous-même au lieu de télécharger - -**AAPS is not available as download due to regulation for medical devices. Il est légal de construire l'application pour votre usage personnel, mais vous ne devez en aucun cas donner une copie à d'autres personnes ! Voir la [page FAQ](../Getting-Started/FAQ.md) pour plus de détails.** - -## Remarques importantes - -* Please use **[Android Studio Giraffe" (2022.3.1)](https://developer.android.com/studio/)** or newer to build the apk. -* [Windows 32-bit systems](troubleshooting_androidstudio-unable-to-start-daemon-process) are not supported by Android Studio - -(Building-APK-recommended-specification-of-computer-for-building-apk-file)= - -## Configuration recommandée de l'ordinateur pour construire un fichier apk - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
OS (seulement 64 bits)Windows 8 ou supérieurMac OS 10.14 ou supérieurN'importe quel Linux prend en charge Gnome, KDE, ou Unity DE;  GNU C Library 2.31 ou ultérieure

CPU (seulement 64 bits)

architecture processeur x86_64 ; Core Intel de 2ème génération ou plus récente, ou processeur AMD prenant en charge un
Hypervisor Windows		Intel Core de 2ème génération ou plus récente, ou processeur AMD prenant en charge un
Hypervisor.Framework		architecture du processeur x86_64, Intel Core de 2ème génération ou plus récent ou processeur AMD avec support pour la virtualisation AMD (AMD-V) et SSSE3

RAM

8GB or more

Disque

Au moins 30 Go d'espace libre. Un SSD est recommandé.

Résolution

Minimum 1280 x 800

Internet

Haut débit

- -Please keep in mind that both **64 bit CPU and 64 bit OS are mandatory condition.** If your system DOES NOT meet this condition, you have to change affected hardware or software or the whole system. **Il est fortement recommandé d'utiliser un SSD (Solid State Disk) au lieu d'un HDD (Hard Disk Drive) car cela prend moins de temps lorsque vous construisez le fichier apk d'installation d'AAPS.** Recommandé signifie que c'est juste conseillé mais que ce n'est pas obligatoire. Cependant, vous pouvez toujours utiliser un disque dur lorsque vous construisez un fichier apk, mais notez que le processus de construction peut prendre beaucoup de temps à s'exécuter, si bien qu'une fois démarré, vous pouvez le laisser fonctionner sans surveillance. - -* * * - -### Cet article est divisé en deux parties. - -* La partie "aperçu" indique les étapes nécessaires pour construire le fichier APK. -* Dans la partie "pas à pas", vous trouverez les captures d'écran d'une installation complète. Les versions d'Android Studio - l'environnement de développement logiciel que nous utiliserons pour construire l'APK - changent très rapidement. Les exemples ne seront donc pas identiques à votre installation, mais cela devrait vous donner un bon point de départ. Android Studio fonctionne sous Windows, Mac OS X et Linux et il peut y avoir de petites différences entre chaque plateforme. If you find that something important is wrong or missing, please inform the facebook group "AAPS users" or in the Discord chat [Android APS](https://discord.gg/4fQUWHZ4Mw) so that we can have a look at this. - -## Aperçu - -En général, les étapes nécessaires pour construire le fichier APK sont : - -1. [Installer Git](../Installing-AndroidAPS/git-install.md) -2. [Installer Android Studio](Building-APK-install-android-studio) -3. [Définir le chemin d’accès git dans Android Studio](Building-APK-set-git-path-in-preferences) -4. [Download AAPS code](Building-APK-download-AAPS-code) -5. [Télécharger Android SDK](Building-APK-download-android-sdk) -6. [Générer l'application](Building-APK-generate-signed-apk) (générer un fichier apk signé) -7. [Transférer le fichier apk sur votre téléphone](Building-APK-transfer-apk-to-smartphone) -8. [Identifier le récepteur si vous utilisez xDrip+](xdrip-identify-receiver) - -## Démarche pas à pas - -Description détaillée des étapes nécessaires à la construction du fichier APK. - -## Installer git (si vous ne l'avez pas) - -Suivez la documentation sur la [page d'installation de git](../Installing-AndroidAPS/git-install.md). - -(Building-APK-install-android-studio)= - -## Installer Android Studio - -Les captures d'écran suivantes ont été prises à partir de Android Studio Version Arctic Fox | 2020.3.1. Les écrans peuvent changer dans les versions futures d'Android Studio. Mais vous devriez y arriver. Vous pouvez demande de [l'aide auprès de la commauté](../Where-To-Go-For-Help/Connect-with-other-users.md). - -Une des choses les plus importantes lors de l'installation d'Android Studio : **Soyez patient !** Au cours de l'installation et de la configuration, Android Studio télécharge beaucoup de choses ce qui prendra du temps. - -Téléchargez [Android Studio ici](https://developer.android.com/studio/install.html) et installez le sur votre ordinateur. - -Au premier démarrage, vous trouverez l'assistant d'installation : - -Sélectionnez "Do not import settings" car vous n'avez pas eu d'utilisation préalable. - -![Ne pas importer les paramètres](../images/studioSetup/01_ImportSettings.png) - -Décidez si vous voulez partager les données avec Google ou non. - -![Partager des données avec Google](../images/studioSetup/02_DataSharing.png) - -Dans l'écran suivant, cliquez sur "Next". - -![Écran d'accueil](../images/studioSetup/03_Welcome.png) - -Sélectionnez l'installation "Standard" et cliquez sur "Next". - -![Installation standard](../images/studioSetup/04_InstallType.png) - -Sélectionnez le thème de l'interface utilisateur que vous souhaitez (dans ce manuel, nous avons utilisé "Light"). Cliquez ensuite sur "Next". - -> ***Remarque :*** Ce n'est que le modèle de couleurs. Vous pouvez choisir n'importe quel type (par ex. "Darcula" pour le mode sombre). Cette sélection n'a aucune influence sur la construction de l'APK, mais les captures d'écran suivantes peuvent être différentes. - -![Couleur de l'interface](../images/studioSetup/05_UITheme.png) - -Click "Next" on the "Verify Settings" dialog. - -![Vérifiez les paramètres](../images/studioSetup/06_Overview.png) - -Click on all three license agreement parts and select "Agree". When you have agreed to all, the "Finish" button will be enabled and you can "Finish". - - ![Agree license agreements](../images/studioSetup/07_LicenseAgreement.png) - - -Wait while Android Studio downloads additional components and be patient. Once everything is downloaded button "Finish" turns blue. Click the button now. - -![Downloading components](../images/studioSetup/08_Downloading.png) - -(Building-APK-download-AAPS-code)= - -## Download AAPS code - -* On the Android Studio welcome screen select "Projects" (1) on the left and then "Get from VCS" (2). - - ![Android Studio wizard](../images/studioSetup/20_ProjectVCS.png) - - * If you already opened Android Studio and do not see the welcome screen anymore select File (1) > New (2) > Project from Version Control... (3) - - ![Check out project from version control within Android Studio](../images/AndroidStudio_FileNew.PNG) - - * We will now tell Android Studio were to get the code from: - - * Make sure you have selected "Repository URL" on the left (1). - - * Check if "Git" is selected as version control (2). - * Copy and paste the URL ```https://github.com/nightscout/AndroidAPS``` to the main AAPS repository into the URL textbox (3). - * Choose the directory where you want to save the cloned code (4). - - ![Clone Git](../images/studioSetup/21_CloneURL.png) - -* Click button "Clone" (5). - - ![Clone repository](../images/studioSetup/22_Cloning.png) - -* Do not click "Background" while repository is cloned! - -* After the repository is cloned successfully, Android Studio will open the cloned project. - -* You will be asked whether you want to trust the project. Click on "Trust project"! - - ![Trust project](../images/studioSetup/23_TrustProject.png) - -* In the status bar at the bottom you will see the information that Android Studio is running background tasks. - - ![Background tasks](../images/studioSetup/24_GradleSyncRunning.png) - -* Windows only: Grant access if your firewall is asking for permission. - - ![Firewall permission java](../images/AndroidStudio361_18.png) - -* Once the background tasks are finished you will probably see an error saying that errors occurred (1) or (2) or (3). - - ![SDK licence](../images/studioSetup/25_SyncFailed.png) - - Don't worry, this will be solved soon! - -(Building-APK-set-git-path-in-preferences)= - -## Set git path in preferences - -Make sure [git is installed](../Installing-AndroidAPS/git-install.md) on your computer and you have restarted your computer since installing. - -On the Android Studio welcome screen click "Customize" (1) on the left and then select the link "All settings..." (2): - -![Android Studio settings from welcome screen](../images/studioSetup/10_WizardSettings.png) - -### Windows - -* As windows user, make sure you have restarted your computer after [installing Git](../Installing-AndroidAPS/git-install.md). - -* In the menu, go to File (1) > Settings (2) (or Android Studio > Preferences on Mac). - - ![Ouvrir les paramètres](../images/studioSetup/30_Settings.png) - -* Double-click "Version Control" (1) to open the sub-menu. - -* Click Git (2). -* Make sure update method "Merge" (3) is selected. -* Check if Android Studio can locate path to git.exe automatically by clicking the button "Test" (4). - - ![Android Studio settings](../images/studioSetup/11_GitPath.png) - -* If automatic setting is successful git version will be displayed next to the path. - - ![Git version displayed](../images/studioSetup/12_GitVersion.png) - -* Eventually git.exe cannot be found automatically or the Test will result in an error (1): - - ![Git not found](../images/studioSetup/13_GitVersionError.png) - - In this case click on the folder icon (2). - -* Use [search function](https://www.tenforums.com/tutorials/94452-search-file-explorer-windows-10-a.html) in windows explorer to find "git.exe" if you are unsure where git has been installed. You are looking for a file named "git.exe", located in **\bin** folder. - -* Select path to git.exe and make sure you selected the one in ** \bin\ ** folder (3) and click "OK" (4). - - ![Select git manually](../images/studioSetup/14_GitManualSelection.png) - -* Check your selected git path again with the "Test" button as described above. - -* When the git version is displayed next to the path (see screenshot above), close settings window by clicking "OK" button (5). - -### Mac - -* Any git version should work. For example . -* Use homebrew to install git: ```$ brew install git```. -* For details on installing git see the [official git documentation](https://git-scm.com/book/en/v2/Getting-Started-Installing-Git). -* If you install git via homebrew there is no need to change any preferences. Just in case: They can be found here: Android Studio - Preferences. - -(Building-APK-download-android-sdk)= - -## Télécharger Android SDK - -* In the menu, go to File (1) > Settings (2) (or Android Studio > Preferences on Mac). - - ![Ouvrir les paramètres](../images/studioSetup/30_Settings.png) - -* Double-click on Languages & Frameworks to open its submenu (1). - -* Select Android SDK (2). -* Tick the box left of "Android 9.0 (Pie)" (3) (API Level 28). - - ![Paramètres SDK](../images/studioSetup/31_AndroidSDK.png) - -* Confirmez les modifications en cliquant sur OK. - - ![Confirmer les modifications SDK](../images/studioSetup/32_ConfirmSDK.png) - -* Wait until the SDK download and installation is finished. - - ![Wait during SDK installation](../images/studioSetup/34_DownloadSDK.png) - -* When SDK installation is completed the "Finish" button will turn blue. Click this button. - - ![Finish SDK installation](../images/studioSetup/35_DownloadSDKfinished.png) - -* Android Studio might recommend to update the gradle system. **Never update gradle!** This will lead to difficulties! - -* If you see an information on the lower right side of your Android Studio window that Android Gradle Plugin is ready to update click on the text "upgrade" (1). - - ![Pas de mise à jour de Gradle](../images/studioSetup/36_GradleUpdateRequest.png) - -* In the dialog box the select "Don't remind me again for this project" (2). - - ![Pas de mise à jour de Gradle](../images/studioSetup/37_GradleUpdateDeny.png) - -* Restart Android Studio before you continue. - -(Building-APK-generate-signed-apk)= - -## Générer un APK signé - -Signing means that you indicate your app to be your own creation but in a digital way as a kind of digital fingerprint within the app itself. That is necessary because Android has a rule that it only accepts signed code to run for security reasons. For more information on this topic, follow [this link](https://developer.android.com/studio/publish/app-signing.html#generate-key). - -* Après le démarrage d'Android Studio, attendez que toutes les tâches en arrière-plan soient terminées. - - ![Attendre les tâches en arrière-plan](../images/studioSetup/40_BackgroundTasks.png) - - * ***Avertissement :*** Si des erreurs se produisent, ne continuez pas avec les étapes suivantes. \ Consulter la [section dépannage](../Installing-AndroidAPS/troubleshooting_androidstudio) pour les problèmes connus ! - - ![Erreur de synchronisation Gradle](../images/studioSetup/41_GradleSyncError.png) - -* Cliquez sur "Build" (1) dans la barre de menus et sélectionnez "Generate Signed Bundle / APK ..." (2). - - ![Génération de l'apk](../images/studioSetup/42_MenuBuild.png) - -* Sélectionnez "APK" (1) au lieu de "Android App Bundle" et cliquez sur "Next" (2). - - ![APK au lieu du bundle](../images/studioSetup/43_Apk.png) - -* Make sure that module is set to "AndroidAPS.app" (1). - -* Cliquez sur "Create new..." (2) pour commencer la création de votre fichier de clés. - - ***Remarque :*** Un fichier de clés dans ce cas n'est rien de plus qu'un fichier dans lequel les informations de signature sont stockées. Il est crypté et les informations sont sécurisées avec des mots de passe. - - ![Créer le fichier de clés](../images/studioSetup/44_KeystoreNew.png) - -* Cliquez sur le symbole dossier pour sélectionner un chemin d'accès sur votre ordinateur pour votre fichier de clés. - - ![Créer le fichier de clés](../images/studioSetup/45_KeystoreDialog.png) - -* Sélectionnez le répertoire dans lequel votre fichier de clés doit être sauvé (1). - - ![Créer le fichier de clés](../images/studioSetup/46_KeystorePath.png) - - ***Attention : Ne pas le mettre dans le même répertoire que celui du projet. Vous devez utiliser un dossier différent !*** Un bon emplacement peut être votre répertoire d'accueil. - -* Tapez un nom de fichier pour votre fichier de clés (2) et confirmez avec "OK" (3). - -* Entrez (2) et confirmez (3) le mot de passe de votre fichier de clés.![Sélectionner le chemin d'accès du fichier de clés](../images/studioSetup/47_KeystoreDialog.png) - - ***Remarque :*** Les mots de passe pour le stockage de clés et la clé ne doivent pas être très sophistiqués. Assurez vous de bien vous en souvenir ou notez le dans un endroit sûr. Si plus tard vous avez oublié vos mots de passe, allez voir la page [Dépannages d'Android Studio - Certificats perdus](troubleshooting_androidstudio-lost-keystore). - -* Entrez un alias (4) pour votre clé. Choisissez ce que vous voulez. - -* Entrez (5) et confirmez (6) le mot de passe de votre clé. - -* La validité (7) est de 25 ans par défaut. Vous n'avez pas à modifier la valeur par défaut. - -* Le prénom et le nom sont obligatoires (8). Toutes les autres informations sont facultatives. - -* Cliquez sur "OK" (9) lorsque vous avez terminé. - -* Assurez-vous que la case permettant de mémoriser les mots de passe est cochée (1). So you don't have to enter them again next time you build the apk (i.e. when updating to a new AAPS version). - -* Cliquez sur "Next" (2). - - ![Mémoriser les mots de passe](../images/studioSetup/48_KeystoreSave.png) - -* Sélectionnez la variante de compilation "fullRelease" (1) et appuyez sur "Finish". - - ![Sélectionnez la variante de build](../images/studioSetup/49_BuildVariant.png) - -* Android Studio affichera "Gradle Build running" en bas de page. Cela prend un certain temps, selon votre ordinateur et votre connexion Internet. **Soyez patient !** - - ![Exécution Gradle](../images/studioSetup/50_GradleRunning.png) - -* Android Studio affiche l'information "Generate Signed APK" quand la génération est terminée. - - ![Compilation terminée](../images/studioSetup/51_BuildFinished.png) - -* Dans le cas ou la génération n'a pas réussie, référez vous à la [section dépannage](../Installing-AndroidAPS/troubleshooting_androidstudio). - -* Cliquez sur la notification pour la développer. - -* Cliquez sur le lien "locate". - - ![Localiser le fichier compilé](../images/studioSetup/52_BuildLocate.png) - - * Si la notification est supprimée, vous pouvez toujours ouvrir le "Journal des événements" et sélectionner le même lien ici.![Génération réussie - journal des événements](../images/studioSetup/53_EventLog.png) - -* Votre gestionnaire de fichiers/explorateur va s'ouvrir. Naviguez vers le répertoire "full" (1) > "release" (2). - - ![Emplacement du fichier apk](../images/studioSetup/54_APKlocation.png) - -* Le fichier que vous cherchez est "app-full-release.apk" (3). - -(Building-APK-transfer-apk-to-smartphone)= - -## Transférer le fichier APK sur le smartphone - -Easiest way to transfer app-full-release.apk to your phone is via [USB cable or Google Drive](https://support.google.com/android/answer/9064445?hl=en). Please note that transfer by mail might cause difficulties and is not the preferred way. - -On your phone you have to allow installation from unknown sources. Manuals how to do this can be found on the internet (i.e. [here](https://www.expressvpn.com/de/support/vpn-setup/enable-apk-installs-android/) or [here](https://www.androidcentral.com/unknown-sources)). - -## Résolution de problèmes - -See separate page [troubleshooting Android Studio](../Installing-AndroidAPS/troubleshooting_androidstudio). \ No newline at end of file diff --git a/docs/CROWDIN/fr/Resources/index.md b/docs/CROWDIN/fr/Resources/index.md deleted file mode 100644 index b4c885c164a0..000000000000 --- a/docs/CROWDIN/fr/Resources/index.md +++ /dev/null @@ -1,8 +0,0 @@ -# Ressources - -```{toctree} -:glob: true -:maxdepth: 4 - -clinician-guide-to-AndroidAPS -``` diff --git a/docs/CROWDIN/fr/Sandbox/sandbox2.md b/docs/CROWDIN/fr/Sandbox/sandbox2.md deleted file mode 100644 index e3b35aa9b7ec..000000000000 --- a/docs/CROWDIN/fr/Sandbox/sandbox2.md +++ /dev/null @@ -1,43 +0,0 @@ -# fichier sandbox interne 2 pour les tests - -```{admonition} no need to translate this -:class: note - -No need to translate this. -``` - -Ceci est un fichier sandbox interne pour que l'équipe de documentation puisse tester - -1. syntaxe markdown et - -1. processus en arrière-plan pour - 1. les traductions CROWDIN - 2. Lire la doc de déploiement. - -You can dirctly jump from here to the first label in the sandbox1.md file - ["Jump"](sandbox1-this-is-a-test). - -Vous pouvez sauter directement d'ici à la deuxième étiquette dans ce fichier - ["Sauter"](sandbox1-this-is-another-test). - -Ici vous pouvez aller au premier fichier sandbox - ["Sauter"](./sandbox1.md). - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -(sandbox2-this-is-a-test)= -## Ceci est un test - -Ceci est un test si les étiquettes doivent être uniques. - -### This is spare information from the docs - -cut from index: - -There are "limits" set in place when you are first beginning your AAPS journey. Ces limites de sécurité ont été développées au cours de plusieurs années par les observations des erreurs involontaires que les nouveaux utilisateurs sont les plus susceptibles de commettre lors de la première mise en place, construit, et enfin lorsqu'ils ont réussi avec succès à boucler avec AAPS - comme le plus souvent ces erreurs se produisent simplement parce que l'utilisateur était tellement excité de commencer à utiliser le système qu'ils ont peut-être oublié de s'asseoir et de consacrer le temps nécessaire pour comprendre de façon approfondie l'ensemble des informations présentes dans cette documentation. - - -### spare info from the overview to put into "preparing" - -Étant donné que les exigences sont très différentes de celles que vous avez pu mettre en place dans le passé, nous vous recommandons de suivre vraiment toutes les instructions, pas à pas, les premières fois que vous construisez l'application, afin que vous ayez une meilleure idée de la façon dont le processus de construction de l'application est censé se comporter lorsque toutes les étapes sont suivies exactement. N'oubliez pas de prendre votre temps. Plus tard, cela ira très rapidement lorsque vous devrez reconstruire l'application pour une nouvelle version. De cette façon, vous aurez plus de chances de voir quand quelque chose ne va pas comme prévu avant que trop d'étapes ne soient effectuées. Il est important de sauvegarder votre fichier de clés (fichier .jks utilisé pour signer votre application) dans un endroit sûr, afin que vous puissiez toujours utiliser le même fichier de clés et le même mot de passe chaque fois qu'on vous demande de créer une nouvelle mise à jour d'AAPS, car c"est ve fichier qui garanti que chaque nouvelle version de l'application « se souviendra » de toutes les informations que vous lui avez fournies dans les versions précédentes de l'application et ainsi de permettre que les mises à jour se dérouleront aussi facilement que possible. En moyenne, vous pouvez considérer qu'il y aura une nouvelle version et 2 à 3 mises à jour par an. Ce nombre est basé sur le retour d'expérience et peut changer à l'avenir. Mais nous voulons au moins vous donner une estimation sur ce à quoi vous pouvez vous attendre. Lorsque vous aurez plus d'expérience pour créer les "build" de mises à jour d'AAPS, toutes les étapes nécessaires pour une mise à jour ne prendront que 15 à 30 minutes. en moyenne. Cependant, au début, il peut y avoir une période d'apprentissage assez difficile, car ces étapes ne sont pas toujours considérées comme intuitives par les nouveaux utilisateurs! Donc, ne soyez pas frustré si vous trouvez qu'il vous faut une demi-journée ou une journée entière avec l'aide de la communauté avant d'arriver à faire vos premières mise à jour. Si vous trouvez que vous devenez très frustré, prenez juste des courtes pauses et régulièrement; après un tour du pâté de maisons ou deux, vous trouverez que vous serez plus à même d'aborder le problème à nouveau. diff --git a/docs/CROWDIN/fr/Usage/Objectives.md b/docs/CROWDIN/fr/Usage/Objectives.md deleted file mode 100644 index 64dd848f5443..000000000000 --- a/docs/CROWDIN/fr/Usage/Objectives.md +++ /dev/null @@ -1,184 +0,0 @@ -# Objectifs - -AAPS has a series of Objectives that need to be completed to walk you through the features and settings of safe looping. Ils s'assurent que vous avez correctement configuré tout ce qui est détaillé dans les sections ci-dessus, et que vous comprenez ce que votre système fait et pourquoi vous pouvez lui faire confiance. - -Si vous **mettez à jour les téléphones** alors vous pouvez [exporter vos paramètres](../Usage/ExportImportSettings.md) pour garder votre progression à travers les objectifs. Non seulement vos progrès à travers les objectifs de l'être sauvés, mais également vos paramètres de sécurité, tels que max bolus etc. Si vous n'exportez pas et n'importez pas vos paramètres, vous devrez recommencer les objectifs depuis le début. C'est une bonne idée de [sauvegarder vos paramètres](../Usage/ExportImportSettings.html) souvent juste au cas où. - -Si vous voulez revenir en arrière sur les objectifs terminés voir les [explications ci-dessous](Objectives-go-back-in-objectives). - -## Objectif 1 : Paramétrage de la visualisation et la surveillance des données, analyse des débits Basal et des ratios - -- Sélectionnez la source de glycémie adaptée à votre configuration. Voir [Source GLY](../Configuration/BG-Source.md) pour plus d'informations. -- Select the right Pump in ConfigBuilder (select Virtual Pump if you are using a pump model with no AAPS driver for looping) to ensure your pump status can communicate with AAPS. -- If using DanaR pump then ensure you have followed [DanaR Insulin Pump](../Configuration/DanaR-Insulin-Pump.md) instructions to ensure the link between pump and AAPS. -- You need to establish a data repository/reporting platform to complete this objective. That can be accomplished with either Nightscout or Tidepool (or both). Follow instructions at the [Nightscout](../Installing-AndroidAPS/Nightscout.md) or [Tidepool](../Installing-AndroidAPS/Tidepool.md) page for instructions. -- Notez que l'URL dans NSClient doit être **SANS /api/v1/** à la fin - voir les [paramètres NSClient dans les Préférences](Preferences-nsclient). - -*You may need to wait for the next blood glucose reading to arrive before AAPS will recognise it.* - -## Objective 2: Learn how to control AAPS - -- Perform several actions in AAPS as described in this objective. - -- Cliquez sur le texte orange "Pas encore terminé" pour accéder à la liste des tâches. - -- Des liens seront fournis pour vous guider si vous n'êtes pas encore familiarisé avec une action spécifique. - - ```{image} ../images/Objective2_V2_5.png - :alt: Screenshot objective 2 - ``` - -(Objectives-objective-3-prove-your-knowledge)= - -## Objectif 3 : Prouver ses connaissances - -Objective 3 is a multiple choice test based on questions designed to test your theoretical knowledge of **AAPS**. - -Some users find Objective 3 to be the most difficult objective to complete. Please do read the AAPS documents in conjunction with the questions. If you are genuinely stuck after researching the **AAPS** documents, please search or ask for help on the Facebook or Discord group. These groups can provide friendly hints or redirect you to the relevant part of the **AAPS** documents. - -To proceed with Objective 3, click on the orange text “Not completed yet” to access the relevant question. Please read each question and select your answer(s). - - - -Within each question, a hyperlink to the **AAPS** documents will guide you to the relevant section of the document which you should read in order to locate the correct answer. - - -[Obj3_Screenshot 2023-12-05 223422](https://github.com/openaps/AndroidAPSdocs/assets/137224335/77347516-e24e-459d-98ab-acbb49a3d4e8)![image](https://github.com/openaps/AndroidAPSdocs/assets/137224335/ca756b8e-efbc-4427-b281-ac953ce16718) - - - -For each question, there may be more than one answer that is correct! If an incorrect answer is selected, the question will be time locked for a certain amount of time (60 minutes) before you can go back and answer the question. - - -After updating to a new version of **AAPS**, new questions may be added to cover a prevalent issue picked up by **AAPS** or alternatively to test your knowledge of a new feature of **AAPS** as released. - - -When **AAPS** is installed for the first time, you will have to complete Objective 3 entirely in order to move onto Objective 4. Each objective is required to be completed in sequential order. New features will gradually be unlocked as progress is made through the objectives. - -__What happens if new questions are added later to Objective 3?__ From time to time, new features are added to **AAPS** which may require a new question to be added to Objective 3. As a result, any new question added to Objective 3 will be marked as “incomplete” because **AAPS** will require you to action this. As each Objective is independent, you will not lose the existing functionality of **AAPS** providing the other objectives remain completed. - - -## Objectif 4 : Démarrage de la boucle ouverte - -- Sélectionnez la Boucle Ouverte soit à partir des Préférences, soit en faisant un appui long sur le bouton de boucle en haut à gauche de l'écran d'accueil. -- Travaillez dans les [Préférences](../Configuration/Preferences.md) pour la configurer pour vous. -- Manually enact at least 20 of the temporary basal rate suggestions over a period of 7 days; input them to your pump and confirm in AAPS that you have accepted them. Ensure this data shows in AAPS and Nightscout. -- Activez des [Cibles temporaires](../Usage/temptarget.md), si nécessaire. Utilisez des cibles temp. hypo temp pour éviter que le système ne corrige trop fortement une augmentation de la glycémie après une hypo. - -### Réduire le nombre de notifications - -- Pour réduire le nombre de décisions à prendre en mode Boucle Ouverte, définissez une large plage cible comme 90 - 150 mg/dl ou 5,0 - 8,5 mmol/l. - -- Vous pouvez même augmenter encore la limite supérieure (ou désactiver la Boucle ouverte) pendant la nuit. - -- Dans les Préférences, vous pouvez définir un pourcentage minimum pour suggérer un changement de débit de basal. - - ```{image} ../images/OpenLoop_MinimalRequestChange2.png - :alt: Boucle ouverte Changement minimum - ``` - -- De plus, vous n'avez pas besoin d'agir toutes les 5 minutes sur toutes les suggestions... - -## Objectif 5 : Compréhension de la Boucle Ouverte, y compris les propositions de débits Basal temporaires - -- Start to understand the thinking behind the temp basal recommendations by looking at the [determine basal logic](https://openaps.readthedocs.io/en/latest/docs/While%20You%20Wait%20For%20Gear/Understand-determine-basal.html) and both the [forecast line in AAPS homescreen](Screenshots-prediction-lines)/Nightscout and the summary of outputs from the calculations in your OpenAPS tab. - -Vous voudrez définir votre objectif plus haut que d'habitude jusqu'à ce que vous ayez confiance dans les calculs et les paramètres. Le système permet - -- une cible basse au minimum de 72 mg/dl (4 mmol/l) ou un maximum de 180 mg/dl (10 mmol/l) -- une cible haute au minimum de 90 mg/dl (5 mmol/l) et au maximum de 225 mg/dl (15 mmol/l) -- une cible temporaire en tant que simple valeur peut être n'importe où entre 72 mg/dl et 225 mg/dl (4 mmol/l et 15 mmol/l) - -La cible est la valeur sur laquelle les calculs sont basés, et n'est pas la même que la page dans laquelle vous souhaitez avoir vos glycémies. Si votre cible est très large (disons 50 mg/dl \[3 mmol/l\] ou plus de large), vous aurez souvent peu d'action de AAPS. C'est dû au fait que la glycémie devrait finalement se situer quelque part dans cette large plage, et par conséquent, peu de débits de base temporaires sont suggérés. - -Vous pouvez essayer d'ajuster vos cibles pour qu'elles soient plus proches les unes des autres (disons 20 mg/dl \[1 mmol/l\] ou moins de large) et observer comment le comportement de votre système change en conséquence. - -Vous pouvez afficher une plage plus large (lignes vertes) sur le graphique pour la zone dans laquelle vous souhaitez maintenir votre glycémie en entrant différentes valeurs dans [Préférences](../Configuration/Preferences.md) > Fourchette de visualisation. - -```{image} ../images/sign_stop.png -:alt: Stop sign -``` - -### Arrêtez-vous ici si vous est en boucle ouverte avec une pompe virtuelle - ne cliquez pas sur Vérifier à la fin de cet objectif. - -```{image} ../images/blank.png -:alt: blank -``` - -(Objectives-objective-6-starting-to-close-the-loop-with-low-glucose-suspend)= -## Objectif 6 : Démarrage de la boucle fermée avec le système AGB ( Arrêt pour Glycémie Basse ) - -```{image} ../images/sign_warning.png -:alt: Warning sign -``` - -### La boucle fermée ne corrigera pas les glycémies élevées dans l'objectif 6, car elle est limitée à la suspension glycémie basse. Les hyperglycémies doivent être corrigées manuellement par vous ! - -- Prerequisite: You need a good profile (basal, ISF, IC) already working in AAPS to start with Loop in Low Glucose Suspend mode. Sinon, vous pouvez faire une hypo que vous devrez corriger manuellement. Cela vous aidera beaucoup à éviter d'avoir à traiter des glycémies faible sur une période de 5 jours. **Si vous avez toujours des hypoglycémies fréquentes ou sévères alors envisagez de réajuster votre DAI, ratios basal, SI et G/I et ne démarrez PAS l'objectif 6 pour le moment.** -- Vous n'avez pas à changer vos paramètres pour le moment. Au cours de l'objectif 6, le paramètre maxIA est automatiquement défini sur zéro. **Cette limitations sera supprimée lors du passage à l'objectif 7.** -- Le système remplacera vos paramètres maxIA à zéro, ce qui signifie que si la glycémie diminue, il peut réduire le débit de basal pour vous. Si la glycémie augmente, elle n'augmentera le débit de basal que si l'IA basale est négative du fait d'un Arrêt Glycémie Basse antérieur. Sinon, vos débits de basal resteront les mêmes que votre profil sélectionné. **Cela signifie que vous devez gérer manuellement vos glycémies élevées avec des corrections d'insuline.** -- Si votre IA basale est négative (voir copie d'écran ci-dessous) un DBT > 100% peut également être diffusé à l'objectif 6. - -```{image} ../images/Objective6_negIOB.png -:alt: Exemple IA négative -``` - -- Définissez votre cible légèrement plus haut que vous ne le faites habituellement, simplement pour être sûr et avoir un peu plus de marge de scurité. -- Activez le mode 'Arrêt Glycémie Basse' en appuyant sur l'icône Boucle en haut à droite de l'écran d'accueil et en sélectionnant l'icône Boucle AGB. -- Surveillez comment les basales temporaires sont actives en regardant le texte bleu de la basale sur l'écran d'accueil, ou le rendu de la basale en bleu sur le graphique de l'écran d'accueil. -- Vous pouvez subir temporairement des pics de glycémie à la suite d'hypos sans pouvoir augmenter le débit de base sur le rebond. - -(Objectives-objective-7-tuning-the-closed-loop-raising-max-iob-above-0-and-gradually-lowering-bg-targets)= -## Objectif 7 : Réglage de la Boucle Fermée, augmentation de l'IA (Insuline Active) maximale au dessus de 0 et abaissement progressif des cibles glycémiques - -- Sélectionnez 'Boucle fermée' soit dans les [Préférences](../Configuration/Preferences.md) soit en faisant un appui long sur l'icône Boucle en haut à droite de l'écran d'accueil. sur une période de 1 jour. - -- Augmentez votre 'IA max total qu'OpenAPS ne peut pas dépasser' (dans OpenAPS appelé 'max-IA') au-dessus de 0. La recommandation par défaut est "moyenne bolus repas + 3 x max basal quotidienne"(pour l'algorithme SMB) ou "3 x max basal quotidienne" (pour les algorithme AMA plus anciens) mais devez augmenter très lentement jusqu'à ce que vous trouviez vos propres paramètres qui marchent pour vous (max basal quotidienne = le débit de base maximum sur l'ensemble des plages horaires de la journée). - - Cette recommandation doit être considérée comme un point de départ. Si vous paramétrez 3 x et que vous constatez des variations trop importantes et rapides, alors diminuez cette valeur. Si vous êtes très résistant, augmentez la un peu à la fois. - - ```{image} ../images/MaxDailyBasal2.png - :alt: max daily basal - ``` - -- Une fois confiant sur la quantité d'IA qui convient à votre profil de boucle, réduisez ensuite vos cibles jusqu'au niveau souhaité. - -(Objectives-objective-8-adjust-basals-and-ratios-if-needed-and-then-enable-autosens)= -## Objectif 8 : Ajustement des débits Basal et des ratios si nécessaire, puis activation de la fonction auto-sens - -- Vous pouvez utiliser [autotune](https://openaps.readthedocs.io/en/latest/docs/Customize-Iterate/autotune.html) pour vérifier que votre basale reste précise ou faire un test de basal traditionnel. -- Enable [autosens](../Usage/Open-APS-features.md) over a period of 7 days and watch the white line on the homescreen graph show how your sensitivity to insulin may be rising or falling as a result of exercise or hormones etc. and keep an eye in the OpenAPS report tab how AAPS is adjusting the basals and/or targets accordingly. - -*Don’t forget to record your looping in* [this form](https://bit.ly/nowlooping) *logging AAPS as your type of DIY loop software, if you have not already done so.* - -(Objectives-objective-9-enabling-additional-oref1-features-for-daytime-use-such-as-super-micro-bolus-smb)= -## Objectif 9 : Activation de fonctionnalités supplémentaires pour l'utilisation en journée, telles que la fonction SMB - -- Vous devez lire le [chapitre SMB dans ce wiki](Open-APS-features-super-micro-bolus-smb) et le [chapitre oref1 dans la documentation openAPS](https://openaps.readthedocs.io/en/latest/docs/Customize-Iterate/oref1.html) pour comprendre comment les SMB fonctionnent, en particulier ce qu'il y a derrière le zéro-temp. -- Puis vous devez [augmenter le maxIA](Open-APS-features-maximum-total-iob-openaps-cant-go-over-openaps-max-iob) pour que les SMB marchent correctement. maxIA inclu maintenant toutes les IA, pas seulement la basale ajoutée. Autrement dit, si vous faites un bolus de 8 U pour un repas et que maxIA est à 7 U, aucun SMB ne sera délivré jusqu'à ce que l'IA redescende en dessous de 7 U. Un bon début est maxIA = bolus moyen des repas + 3 x basale max quotidienne (basale max quotidienne = débit horaire max de basale sur n'importe quelle période de la journée - voir [Objectif 7](Objectives-objective-7-tuning-the-closed-loop-raising-max-iob-above-0-and-gradually-lowering-bg-targets) pour une illustration) -- la valeur par défaut de min_5m_carbimpact est passée de 3 à 8 entre AMA et SMB. Si vous passez de AMA vers SMB, vous devez la modifier manuellement. - -(Objectives-objective-10-automation)= -## Objectif 10: Automatisation - -- Vous devez commencer l'objectif 10 pour pouvoir utiliser l'[Automatisation](../Usage/Automation.md). -- Assurez-vous d'avoir complété tous les objectifs, y compris l'examen [Objectif 3 prouver ses connaissances](Objectives#objective-3-prove-your-knowledge). -- Compléter les objectifs précédents n’affectera pas les autres objectifs que vous avez déjà terminés. Vous conserverez tous les objectifs terminés ! - -(Objectives-objective-11-DynamicISF)= -## Objective 11: Additional Features such as DynamicISF - -- You have to start objective 11 to be able to use [DynamicISF](../Usage/Open-APS-features.md) - -(Objectives-go-back-in-objectives)= -## Retour arrière dans les Objectifs - -Si vous voulez revenir en arrière sur les objectifs terminés pour quelque raison que ce soit, vous pouvez le faire en cliquant sur "Refaire l'objectif". - -```{image} ../images/Objective_ClearFinished.png -:alt: Retour arrières objectifs -``` - -## Objectifs dans Android APS avant la version 3.0 - -Un objectif a été supprimé lors de la sortie d'Android APS 3.0. Les utilisateurs d'AAPS version 2.8.2.1 qui sont sur des version d'Android plus anciens (par ex. antérieur à la version 9) utiliseront un jeu d'objectifs plus ancien qui peut être trouvé [ici](../Usage/Objectives_old.md). diff --git a/docs/CROWDIN/fr/Usage/Objectives_old.md b/docs/CROWDIN/fr/Usage/Objectives_old.md deleted file mode 100644 index eabd8c5fba53..000000000000 --- a/docs/CROWDIN/fr/Usage/Objectives_old.md +++ /dev/null @@ -1,152 +0,0 @@ -# Objectifs pour Android APS 2.8.2.1 - -Ce n'est pas la dernière version des objectifs d'Android APS. Cette page détaille les Objectifs qui étaient en place avant la version 3.0. Anyone using an older version of Android (i.e. prior to Android 9) and Android APS version 2.8.2.1 should refer to this page. - -Please see [this page](../Usage/Objectives.md) for the current set of Objectives. - -AndroidAPS a une série d'objectifs qui doivent être complétés pour vous guider à travers les fonctionnalités et les paramètres de la boucle sécurisée. Ils s'assurent que vous avez correctement configuré tout ce qui est détaillé dans les sections ci-dessus, et que vous comprenez ce que votre système fait et pourquoi vous pouvez lui faire confiance. - -If you are **upgrading phones** then you can [export your settings](../Usage/ExportImportSettings.md) to keep your progress through the objectives. Not only will your progress through the objectives be saved, but also your safety settings such as max bolus etc. If you do not export and import your settings then you will need to start the objectives from the beginning again. It is a good idea to [backup your settings](../Usage/ExportImportSettings.html) frequently just in case. - -If you want to go back in objectives see [explanation below](../Usage/Objectives.md#go-back-in-objectives). - -## Objectif 1 : Paramétrage de la visualisation et la surveillance des données, analyse des débits Basal et des ratios - -- Select the right blood glucose source for your setup. See [BG Source](../Configuration/BG-Source.md) for more information. -- Select the right Pump in ConfigBuilder (select Virtual Pump if you are using a pump model with no AndroidAPS driver for looping) to ensure your pump status can communicate with AndroidAPS. -- If using DanaR pump then ensure you have followed [DanaR Insulin Pump](../Configuration/DanaR-Insulin-Pump.md) instructions to ensure the link between pump and AndroidAPS. -- Follow instructions in [Nightscout](../Installing-AndroidAPS/Nightscout.md) page to ensure Nightscout can receive and display this data. -- Note that URL in NSClient must be **WITHOUT /api/v1/** at the end - see [NSClient settings in Preferences](../Configuration/Preferences.md#nsclient). - -*You may need to wait for the next blood glucose reading to arrive before AndroidAPS will recognise it.* - -## Objectif 2 : Apprendre comment contrôler AndroidAPS - -- Perform several actions in AndroidAPS as described in this objective. - -- Click on the orange text "Not completed yet" to access the to-dos. - -- Links will be provided to guide you in case you are not familiar with a specific action yet. - - ![Screenshot objective 2](../images/Objective2_V2_5.png) - -## Objectif 3 : Prouver ses connaissances - -- Pass a multiple-choice exam testing your AndroidAPS knowledge. - -- Click on the orange text "Not completed yet" to access the page with the question and answering options. - - ![Screenshot objective 3](../images/Objective3_V2_5.png) - -- Links will be provided to guide you in case you are unsure about the correct answers yet. - -- The questions for objective 3 have been completely rewritten by native speakers as of AAPS 2.8. Les nouvelles questions couvrent les mêmes sujets de base et quelques nouveaux sujets. - -- These new questions will lead to some not answered questions even though you have successfully completed objective 3 in previous versions. - -- Unanswered questions will affect you only if you start a new objective. En d'autres termes, si vous avez déjà terminé tous les objectifs, vous pouvez attendre et répondre aux nouvelles questions un peu plus tard sans perdre de fonctions AAPS. - -## Objectif 4 : Démarrage de la boucle ouverte - -- Select Open Loop either from Preferences, or by pressing and holding the Loop button in top left of the home screen. -- Work through the [Preferences](../Configuration/Preferences.md) to set up for you. -- Manually enact at least 20 of the temporary basal rate suggestions over a period of 7 days; input them to your pump and confirm in AndroidAPS that you have accepted them. Assurez-vous que ces données apparaissent bien dans AndroidAPS et dans Nightscout. -- Enable [temp targets](../Usage/temptarget.md) if necessary. Utilisez des cibles temp. hypo temp pour éviter que le système ne corrige trop fortement une augmentation de la glycémie après une hypo. - -### Réduire le nombre de notifications - -- To reduce the Number of decisions to be made while in Open Loop set wide target range like 90 - 150 mg/dl or 5,0 - 8,5 mmol/l. - -- You might even want to wider upper limit (or disable Open Loop) at night. - -- In Preferences you can set a minimum percentage for suggestion of basal rate change. - - ![Boucle ouverte Changement minimum](../images/OpenLoop_MinimalRequestChange2.png) - -- Also, you do not need to act every 5 minutes on all suggestions... - -## Objectif 5 : Compréhension de la Boucle Ouverte, y compris les propositions de débits Basal temporaires - -- Start to understand the thinking behind the temp basal recommendations by looking at the [determine basal logic](https://openaps.readthedocs.io/en/latest/docs/While%20You%20Wait%20For%20Gear/Understand-determine-basal.html) and both the [forecast line in AndroidAPS homescreen](../Getting-Started/Screenshots.md#prediction-lines)/Nightscout and the summary of outputs from the calculations in your OpenAPS tab. - -Vous voudrez définir votre objectif plus haut que d'habitude jusqu'à ce que vous ayez confiance dans les calculs et les paramètres. Le système permet - -- a low target to be a minimum of 4 mmol (72 mg/dl) or maximum of 10 mmol (180 mg/dl) -- a high target to be a minimum of 5 mmol (90 mg/dl) and maximum of 15 mmol (225 mg/dl) -- a temporary target as a single value can be anywhere in the range of 4 mmol to 15 mmol (72 mg/dl to 225 mg/dl) - -La cible est la valeur sur laquelle les calculs sont basés, et n'est pas la même que la page dans laquelle vous souhaitez avoir vos glycémies. If your target is very wide (say, 3 or more mmol \[50 mg/dl or more\] wide), you will often find little AAPS action. C'est dû au fait que la glycémie devrait finalement se situer quelque part dans cette large plage, et par conséquent, peu de débits de base temporaires sont suggérés. - -You may want to experiment with adjusting your targets to be a closer together range (say, 1 or less mmol \[20 mg/dl or less\] wide) and observe how the behavior of your system changes as a result. - -You can view a wider range (green lines) on the graph for the values you aim to keep your blood glucose within by entering different values in [Preferences](../Configuration/Preferences.md) > Range for Visualisation. - -![Stop sign](../images/sign_stop.png) - -### Arrêtez-vous ici si vous est en boucle ouverte avec une pompe virtuelle - ne cliquez pas sur Vérifier à la fin de cet objectif. - -![blank](../images/blank.png) - -## Objectif 6 : Démarrage de la boucle fermée avec le système AGB ( Arrêt pour Glycémie Basse ) - -![Warning sign](../images/sign_warning.png) - -### La boucle fermée ne corrigera pas les valeurs de glycémies élevées dans l'objectif 6, car elle est limitée à la suspension glycémie basse. Les hyperglycémies doivent être corrigées manuellement par vous ! - -- Select Closed Loop either from [Preferences](../Configuration/Preferences.md) or by pressing and holding the Open Loop button in the top left of the home screen. - -- Set your target range slightly higher than you usually aim for, just to be safe. - -- Watch how temporary basals are active by viewing the blue basal text on the homescreen or the blue basal render on the homescreen graph. - -- Ensure your settings have supported AndroidAPS to avoid having to treat a low glucose over a period of 5 days. Si vous avez encore des hypoglycémies sévères ou fréquentes, alors envisagez de réajuster votre DAI, basal, SI et ratio G/I. - -- You don't have to change your settings. Au cours de l'objectif 6, le paramètre maxIA est automatiquement défini sur zéro. Le remplacement par zéro de ce paramètre sera annulé lorsque vous serez à l'objectif 7. - -- The system will override your maxIOB settings to zero, which means if blood glucose is dropping it can reduce basal for you, but if blood glucose is rising then it will only increase basal if the basal IOB is negative (from a previous Low Glucose Suspend), otherwise basal rates will remain the same as your selected profile. - - ![Exemple IA négative](../images/Objective6_negIOB.png) - -- If your basal IOB is negative (see screenshot above) a TBR > 100% can be issued also in objective 6. - -- Vous pouvez subir temporairement des pics de glycémie à la suite d'hypos sans pouvoir augmenter le débit de base sur le rebond. - -## Objectif 7 : Réglage de la Boucle Fermée, augmentation de l'IA (Insuline Active) maximale au dessus de 0 et abaissement progressif des cibles glycémiques - -- Raise your 'Maximum total IOB OpenAPS can’t go over' (in OpenAPS called 'max-iob') above 0 over a period of 1 day, the default recommendation is "average mealbolus + 3x max daily basal"(for SMB algorithm) or "3x max daily basal" (for older AMA algorithm) but you should slowly work up to this until you know your settings work for you (max daily basal = the maximum hourly value in any time segment of the day). - - Cette recommandation doit être considérée comme un point de départ. Si vous paramétrez 3 x et que vous constatez des variations dures et rapides, alors diminuez cette valeur. Si vous êtes très résistant, augmentez la un peu à la fois. - - ![max daily basal](../images/MaxDailyBasal2.png) - -- Once confident on how much IOB suits your looping patterns then reduce your targets to your desired level. - -## Objectif 8 : Ajustement des débits Basal et des ratios si nécessaire, puis activation de la fonction auto-sens - -- You can use [autotune](https://openaps.readthedocs.io/en/latest/docs/Customize-Iterate/autotune.html) as a one off to check your basals remain accurate or do a traditional basal test. -- Enable [autosens](../Usage/Open-APS-features.md) over a period of 7 days and watch the white line on the homescreen graph show how your sensitivity to insulin may be rising or falling as a result of exercise or hormones etc. and keep an eye in the OpenAPS report tab how AndroidAPS is adjusting the basals and/or targets accordingly. - -*Don’t forget to record your looping in* [this form](https://bit.ly/nowlooping) *logging AndroidAPS as your type of DIY loop software, if you have not already done so.* - -## Objective 9 : Activation de fonctionnalités supplémentaires pour l'utilisation en journée, telles que la fonction SMB - -- Before AAPS version 2.7 meal assist (MA) was the basic algorithm for AAPS and completing objective 8 was necessary to activate [advanced meal assist (AMA)](../Usage/Open-APS-features.md#advanced-meal-assist-ama). -- As [advanced meal assist (AMA)](../Usage/Open-APS-features.md#advanced-meal-assist-ama) is the standard algorithm from AAPS version 2.7 onwards use the following 28 days to try features you haven't used yet and get more confident with you closed loop system. - -## Objectif 10 : Activation de fonctionnalités supplémentaires pour l'utilisation en journée, telles que la fonction SMB - -- You must read the [SMB chapter in this wiki](../Usage/Open-APS-features.md#super-micro-bolus-smb) and [chapter oref1 in openAPSdocs](https://openaps.readthedocs.io/en/latest/docs/Customize-Iterate/oref1.html) to understand how SMB works, especially what's the idea behind zero-temping. -- Then you ought to [rise maxIOB](../Usage/Open-APS-features.md#maximum-total-iob-openaps-cant-go-over-openaps-max-iob) to get SMBs working fine. maxIA inclu maintenant toutes les IA, pas seulement la basale ajoutée. That is, if given a bolus of 8 U for a meal and maxIOB is 7 U, no SMBs will be delivered until IOB drops below 7 U. A good start is maxIOB = average mealbolus + 3x max daily basal (max daily basal = the maximum hourly value in any time segment of the day - see [objective 7](../Usage/Objectives#objective-7-tuning-the-closed-loop-raising-max-iob-above-0-and-gradually-lowering-bg-targets) for an illustration) -- min_5m_carbimpact default in absorption settings has changed from 3 to 8 going from AMA to SMB. Si vous passez de AMA vers SMB, vous devez la modifier manuellement. - -## Objectif 11: Automatisation - -- You have to start objective 11 to be able to use [Automation](../Usage/Automation.md). -- Make sure you have completed all objectives including exam [../Usage/Objectives.md#objective-3-prove-your-knowledge](../Usage/Objectives#objective-3-prove-your-knowledge). -- Completing previous objectives will not effect other objectives you have already finished. Vous conserverez tous les objectifs terminés ! - -## Retour arrière dans les Objectifs - -Si vous voulez revenir en arrière sur les objectifs terminés pour quelque raison que ce soit, vous pouvez le faire en cliquant sur "Refaire l'objectif". - -![Retour arrières objectifs](../images/Objective_ClearFinished.png) diff --git a/docs/CROWDIN/fr/Usage/Smoothing-Blood-Glucose-Data-in-xDrip.md b/docs/CROWDIN/fr/Usage/Smoothing-Blood-Glucose-Data-in-xDrip.md deleted file mode 100644 index 19e258a63a6d..000000000000 --- a/docs/CROWDIN/fr/Usage/Smoothing-Blood-Glucose-Data-in-xDrip.md +++ /dev/null @@ -1,33 +0,0 @@ -(Smoothing-Blood-Glucose-Data-in-xDrip-smoothing-blood-glucose-data)= - -# Lissage des données de glycémie - -Si les glycémies sont instables/bruitées, AAPS peut mal doser la quantité d'insuline, entraînant des hyper ou hypo. Pour cette raison, il est important de désactiver la boucle jusqu'à ce que le problème soit résolu. Selon votre MGC, de tels problèmes peuvent être dus à la configuration de la MGC ou à des problèmes de capteur ou de site. Vous devrez peut-être remplacer votre capteur MGC pour résoudre ce problème. - -Some CGM systems have internal algorithms to detect the noise level in the readings and AAPS can use this information to avoid giving SMBs if the BG data is too unreliable. Cependant, certaines MGC ne transmettent pas ces données et, pour ces sources de glycémie, 'Activer le SMB toujours' et 'Activer le SMB après les glucides' sont désactivés pour des raisons de sécurité. - -## Capteurs Dexcom - -### Construisez votre propre application Dexcom (BYODA) - -Lorsque vous utilisez [BYODA](DexcomG6-if-using-g6-with-build-your-own-dexcom-app) vos glycémies sont lissées et cohérentes. De plus, vous pouvez profiter du lissage arrière Dexcom. Il n'y a pas de restrictions à l'utilisation des SMB, car les données sur le niveau de bruit sont partagées avec AAPS. - -### xDrip+ avec Dexcom G6 ou Dexcom ONE - -Les niveaux de bruit et les glycémies lissées ne sont partagées avec AAPS que si vous utilisez xDrip+ [mode natif](https://navid200.github.io/xDrip/docs/Native-Algorithm). En utilisant le mode natif, il n'y a aucune restriction dans l'utilisation des SMBs. - -### Dexcom G6 ou Dexcom ONE avec le mode compagnon xDrip+ - -Les niveaux de bruit ne sont pas partagées avec AAPS en utilisant cette méthode. Par conséquent, 'Activer SMB toujours' et 'Activer SMB après les glucides' sont désactivés. - -## Capteurs Freestyle Libre - -### xDrip+ avec FreeStyle Libre - -Aucun des systèmes FreeStyle Libre (FSL1, FSL2, ou FSL3) ne diffuse d'informations sur le niveau de bruit détecté dans les lectures, et donc 'Activer SMB toujours' et 'Activer SMB après glucides' sont désactivés pour toutes les configurations utilisant FreeStyle Libre. - -En outre, de nombreuses personnes ont signalé que FreeStyle Libre produit souvent des données bruitées. Dans xDrip+, il y a quelques options pour vous aider : - -**Lissage des données capteur** Allez dans xDrip+ Paramètres > xDrip+ Paramètres d'affichage, et vérifiez que "Smooth Sensor Noise" est activé. Cela va essayer de lisser les données bruyantes. - -**Lissage des données capteur (Ultra sensible).** Si vous voyez toujours des données bruitées dans xDrip+, vous pouvez appliquer un lissage plus agressif en activant "Smooth Sensor Noise (Ultrasensitive)". Cela essaiera de lisser même si de faibles niveaux de bruits sont détectés. Pour ce faire, vous devez d'abord [activer le mode ingénierie dans xDrip+](Enabling-Engineering-Mode-in-xDrip.md). Ensuite, allez dans Paramètres > xDrip+ Paramètres d'affichage et activez "Smooth Sensor Noise (Ultrasensitive)". \ No newline at end of file diff --git a/docs/CROWDIN/fr/Usage/autotune_b.md b/docs/CROWDIN/fr/Usage/autotune_b.md deleted file mode 100644 index b35d88612891..000000000000 --- a/docs/CROWDIN/fr/Usage/autotune_b.md +++ /dev/null @@ -1,186 +0,0 @@ -# How to use Autotune plugin - -La documentation sur l'algorythme Autotune peut être trouvée dans [la documentation OpenAPS](https://openaps.readthedocs.io/en/latest/docs/Customize-Iterate/autotune.html). - -Le plugin Autotune est une implémentation de l'algorythme autotune OpenAPS dans AAPS. - -**Currently Autotune Plugin is only available in dev branch with Engineering mode.** - -## Interface utilisateur Autotune - -![Autotune écran par défaut](../images/Autotune/Autotune_1b.png) - -- Vous pouvez sélectionner le profil d'entrée que vous voulez régler dans le menu déroulant Profil (par défaut, votre profil actif actuel est sélectionné) - - Remarque : chaque fois que vous sélectionnez un nouveau profil, les résultats précédents seront supprimés et le paramètre Nb jours sera défini à la valeur par défaut -- Ensuite, Nb jours permet de choisir le nombre de jours à utiliser dans le calcul pour calculer votre profil. La valeur minimale est de 1 jour et la valeur maximale de 30 jours. Ce nombre ne devrait pas être trop petit pour obtenir des résultats itératifs et lisses corrects (au-dessus de 7 jours pour chaque calcul) - - Remarque : chaque fois que vous changez le paramètre Nb jours, les résultats précédents seront supprimés -- Dernier run affiche la date du dernier calcul et permet d'afficher votre dernier calcul valide. Si vous n'avez pas lancé Autotune le jour en cours, ou si les résultats précédents ont été supprimés avec une modification du paramètre de calcul ci-dessus, vous pouvez alors récupérer les paramètres et les résultats de la dernière exécution réussie. -- L'avertissement vous montre par exemple des informations sur le profil sélectionné (si vous avez plusieurs valeurs G/I ou plusieurs valeurs SI) - - Remarque : Le calcul Autotune fonctionne avec une seule valeur de G/I et une seule valeur de SI. Il n'existe actuellement aucun algorythme Autotune pour ajuster un G/I circadien ou une SI circadienne. Si votre profil d'entrée a plusieurs valeurs, vous pouvez voir dans la section Avertissement la valeur moyenne prise en compte pour calculer votre profil. -- Le bouton Vérifiez Profil d'entrée permet d'ouvrir la Visionneuse de Profil pour vous permettre de faire une vérification rapide de votre profil (unités, DAI, G/I, SI, basal et cible) - - Remarque : Autotune ne réglera que le G/I (valeur unique), la SI (valeur unique) et les débits de basal (avec variation circadienne). Les unités, la DAI et les cibles resteront inchangées dans le profil de sortie. - -- "Lancer Autotune" exécutera le calcul Autotune avec le profil et le nombre de jours sélectionnés - - Remarque : Le calcul Autotune peut prendre beaucoup de temps. Une fois lancé, vous pouvez passer à une autre vue (écran d'accueil ...) et revenir plus tard dans le plugin Autotune pour voir les résultats - -![Démarrage Run Autotune](../images/Autotune/Autotune_2b.png) - -- Ensuite, au cours de l'exécution vous verrez les résultats intermédiaires ci-dessous - - - Remarque : Pendant l'exécution, les paramètres sont verrouillés, vous ne pouvez donc plus modifier le profil d'entrée sélectionné ou le nombre de jour. Vous devrez attendre la fin du calcul actuel si vous voulez lancer un nouveau calcul avec d'autres paramètres. - - ![Autotune lors de l'exécution](../images/Autotune/Autotune_3b.png) - -- Une fois le calcul automatique terminé, vous verrez le résultat (Tuned Profil) et les quatre boutons ci-dessous. - -![Résultat Autotune](../images/Autotune/Autotune_4b.png) - -- Il est important de toujours comparer le profil d'entrée (colonne "Profil"), le profil de sortie (colonne "Tuned") et le pourcentage de variation pour chaque valeur (colonne "%"). - -- Pour les débits de basal, vous avez aussi le nombre de "jours manquants". Il vous manque des jours quand Autotune n'a pas assez de données catégorisées comme « Basal » pour calculer le débit de basal pour cette période (par exemple après chaque repas lorsque vous avez une absorption de glucides). Ce nombre doit être aussi bas que possible, surtout lors de périodes où la basale est prépondérante (par exemple pendant la nuit ou à la fin de l'après-midi) - -- Le bouton « Comparer les profils » ouvre la vue Comparateur de profil. Le profil d'entrée est en bleu, et le profil de sortie (nommé "Tuned") est en rouge. - - - Remarque : dans l'exemple ci-dessous, le profil d'entrée a une variation circadienne pour le G/I et la SI, mais le profil calculé en sortie a une seule valeur. Si pour vous il est important d'obtenir un profil de sortie circadien, voir [Profil G/I ou SI circadians](#circadian-ic-or-isf-profile) ci-dessous. - - ![Comparer les profils Autotune](../images/Autotune/Autotune_5.png) - -- Si vous faites confiance aux résultats (faible pourcentage de variation entre le profil d'entrée et le profil de sortie), vous pouvez cliquer sur le bouton "Activer le profil" puis cliquer sur OK pour valider. - - - Activer le profil Tuned va automatiquement créer un nouveau profil "Tuned" dans votre plugin de profil local. - - Si vous avez déjà un profil nommé "Tuned" dans votre plugin de profil local, alors ce profil sera mis à jour avec le profil Autotune calculé avant l'activation - - ![Activer Profil Autotune](../images/Autotune/Autotune_6.png) - -- Si vous pensez que le profil Tuned doit être ajusté (par exemple si vous pensez que certaines variations sont trop importantes), puis vous pouvez cliquer sur le bouton "Copier vers profil local" - - - Un nouveau profil avec le préfixe "Tuned" et la date et l'heure de l'exécution seront créés dans le plugin de profil local - -![Copier vers Profil Local](../images/Autotune/Autotune_7.png) - -- Vous pouvez ensuite sélectionner le profil local pour modifier le profil Tuned (il sera sélectionné par défaut lorsque vous ouvrirez le plugin de profil local) - - - les valeurs dans le profil local seront arrondies dans l'interface utilisateur aux capacités de votre pompe - - ![Mise à jour du profil local](../images/Autotune/Autotune_8.png) - -- Si vous souhaitez remplacer votre profil d'entrée par le résultat Autotune, cliquez sur le bouton "Mettre à jour profil d'entrée" et validez la fenêtre pop-up avec OK - - - Remarque : si vous cliquez sur "Activer le profil" après avoir cliqué sur "Mettre à jour profil d'entrée", alors vous activerez votre profil mis à jour et non le profil par défaut "Tuned" ? - - ![Mettre à jour le profil d'entrée](../images/Autotune/Autotune_9.png) - -- Si vous avez mis à jour votre profil d'entrée, alors le bouton "Mettre à jour profil d'entrée" est remplacé par le bouton "Réinitialiser profil d'entrée" (voir capture d'écran ci-dessous). Vous pouvez ainsi voir immédiatement si votre profil d'entrée actuel présent dans le plugin de profil local contient déjà le résultat de la dernière exécution Autotune ou non. Vous avez aussi la possibilité de récupérer votre profil d'entrée initial sans les résultats Autotune avec ce bouton - - ![Mettre à jour le profil d'entrée](../images/Autotune/Autotune_10.png) - - - -## Paramètres Autotune - -### Paramètres du plugin Autotune - -![Autotune écran par défaut](../images/Autotune/Autotune_11.png) - -- Changer le profil avec l'Automation (Désactivé par défaut) : voir [Exécuter Autotune avec une règle d'automatisation](#run-autotune-with-an-automation-rule) ci-dessous. Si vous activez ce paramètre, le profil d'entrée sera automatiquement mis à jour par le profil Tuned, et il sera activé. - - **Soyez prudent, vous devez prendre confiance en vérifiant pendant plusieurs jours qu'après une mise à jour et l'activation du profil Tuned sans aucune modification, cela améliore effectivement votre boucle.** - -- Catégoriser UAM comme basal (par défaut On) : Ce paramètre est pour les utilisateurs utilisant AndroidAPS sans aucun glucide entré (Full UAM). Il empêchera (quand désactivé) de catégoriser les RNS en tant que basal. - - Remarque : si vous avez au moins une heure d'absorption de glucides détectée pendant une journée, alors toutes les données catégorisées comme "RNS" seront catégorisées en tant que basal, quel que soit ce paramètre (Activé ou Désactivé) -- Nombre de jours de données (par défaut 5) : Vous pouvez définir la valeur par défaut avec ce paramètre. À chaque fois que vous sélectionnez un nouveau profil dans le plugin Autotune, le nombre de jours sera remplacé par cette valeur par défaut -- Appliquer le résultat moyen dans l'IC/ISF circadienne (Désactivation par défaut) : voir [Profil avec G/I ou SI Circadiens](#circadian-ic-or-isf-profile) ci-dessous. - -### Autres paramètres - -- Autotune utilise également les ratio Max et Min autotsens pour limiter la variation. Vous pouvez voir et ajuster ces valeurs dans Configuration > Plugin Sensitivité > Paramètres > Paramètres Avancés - - ![Autotune écran par défaut](../images/Autotune/Autotune_12.png) - - - -## Fonctionnalités avancées - -### Profil avec G/I ou SI Circadiens - -- Si vous avez des variations importantes de G/I et/ou de votre SI dans votre profil, et si vous avez entièrement confiance en vos heures et variations circadiens, alors vous pouvez définir "Appliquer le résultat G/I et SI moyen sur le profil circadien" - - - Notez que le calcul Autotune sera toujours fait avec une seule valeur, et que la variation circadienne ne sera pas ajustée par Autotune. Ce paramètre n'applique que la variation moyenne calculée pour le G/I et/ou la SI sur vos valeurs circadiennes - -- Vous pouvez voir dans la copie d'écran ci-dessous le profil Tuned avec ce paramètre desactivé (à gauche) et activé (à droite) - - ![Autotune écran par défaut](../images/Autotune/Autotune_13.png) - - - -### Tune specific days of the week - -- If you click on the checkbox with the eye on the right of "Rune days" parameter, you will see the day selection. You can specify which day of the week should be included in Autotune calculation (in screenshot below you can see an example for "working days" with Saturday and Sunday removed from autotune calculation) - - If the number of day included in Autotune calculation is lower than the number of Tune days, then you will see how many days will be included on the right of Tune days selector (10 days in the example below) - - This setting gives good results only if the number of remaining days is not to small (for example if you Tune a specific profile for week end days with only Sunday and Saturday selected, you should select a minimum of 21 or 28 Tune days to have 6 or 8 days included in Autotune calculation) - -![Autotune écran par défaut](../images/Autotune/Autotune_14b.png) - -- During Autotune calculation, you can see the progress of the calculations ("Partial result day 3 / 10 tuned" on example below) - - ![Autotune écran par défaut](../images/Autotune/Autotune_15b.png) - -## Exécuter Autotune avec une règle d'automatisation - -La première étape est de définir le déclencheur correct pour une règle d'automatisation avec Autotune : - -Note: for more information on how to set an automation rule, see [here](./Automation.rst). - -- Vous devez sélectionner le déclencheur Période répétitive : il ne faut exécuter Autotune au maximum qu'une seule fois par jour, Autotune est conçu pour être exécuté tous les jours (à chaque nouvelle exécution, vous décalez la période de calcul d'un jour et rapidement les modifications du profil devrait être très faibles) - - ![Autotune écran par défaut](../images/Autotune/Autotune_16.png) - -- Il est préférable au début d'exécuter Autotune pendant la journée pour pouvoir vérifier les résultats. Si vous voulez exécuter Autotune dans la nuit, vous devez sélectionner dans le déclencheur 4 heure du matin ou plus tàrd pour inclure le jour courant dans le calcul Autotune suivant. - - ![Autotune écran par défaut](../images/Autotune/Autotune_17.png) - -- Ensuite, vous pouvez sélectionner l'action "Lancer Autotune" dans la liste - - ![Autotune écran par défaut](../images/Autotune/Autotune_18.png) - -- Vous pouvez ensuite sélectionner l'action Profil Autotune pour régler les paramètres. Les paramètres par défaut sont "Profil actif", le nombre de jours défini dans les préférences Autotune, et tous les jours sont sélectionnés. - - ![Autotune écran par défaut](../images/Autotune/Autotune_19b.png) - -- Après quelques jours, si vous faites entièrement confiance aux résultats Autotune et si le pourcentage de modification est faible, vous pouvez modifier les [Paramètres Autotune](#autotune-plugin-settings) "Changer le Profil avec l'automatisation" pour l'activer, cela mettre à jour le profil et l'activera automatiquement après le calcul. - -Note: if you want to automatically tune profiles for specific days of the week (for example a profile for "Weekend days" and another one for "Working days"), then create one rule for each profile, select the same days in Trigger and in Autotune Action, Tune days must be high enough to be sure tuning will be done with at least 6 or 8 days, and don't forget to select time after 4AM in trigger... - -- See below an example of rule to tune "my profile" on all "Working days" with 14 Tune days selected (so only 10 days included in autotune calculation). - -![Autotune écran par défaut](../images/Autotune/Autotune_20b.png) - - - -## Trucs et astuces - -Autotune fonctionne avec les informations existantes dans votre base de données, donc si vous venez d'installer AAPS sur un nouveau téléphone, vous devrez attendre plusieurs jours avant de pouvoir lancer Autotune avec suffisamment de jours pour obtenir des résultats pertinents. - -Autotune n'est qu'une aide, il est important de vérifier régulièrement si vous êtes d'accord avec le profil calculé. Si vous avez le moindre doute, modifiez les paramètres Autotune (par exemple le nombre de jours) ou copiez les résultats dans le profil local et ajustez le profil avant de l'utiliser. - -Utilisez toujours Autotune plusieurs jours manuellement pour vérifier les résultats avant de les appliquer. Et ce n'est que lorsque vous faites entièrement confiance aux résultats Autotune et quand la variation devient très faible entre le profil précédent et le profil calculé que vous pouvez commencer à utiliser l'automatisation (jamais avant) - -- Autotune peut très bien fonctionner pour certains utilisateurs et pas du tout pour d'autres, donc **Si vous ne faites pas confiance au résultat Autotune, ne l'utilisez pas** - -Il est également important d'analyser les résultats d'Autotune pour comprendre (ou essayer de comprendre) pourquoi Autotune propose ces modifications - -- vous pouvez avoir une augmentation ou une diminution de la globalité du profil (par exemple une augmentation du débit de basal total associé à la diminution des valeurs de la SI et du G/I). il pourrait être associé à plusieurs jours successifs avec correction autosens supérieure à 100% (plus d'agressivité requise) ou inférieure à 100% (vous êtes plus sensible) -- Parfois, Autotune propose un équilibre différent entre les taux de basal et la SI et G/I (ex basal inférieur et SI / G/I plus agressifs) - -Nous recommandons de ne pas utiliser Autotune dans les cas suivants : - -- Vous n'entrez pas tous vos glucides - - Si vous n'entrez pas de correction de glucides pour une hypoglycémie, Autotune verra une augmentation imprévue de votre glycémie et augmentera vos taux de basal les 4 heures précédentes, cela pourrait être le contraire de ce que vous avez besoin pour éviter une hypoglycémie, en particulier si c'est au milieu de la nuit. C'est pourquoi il est important d'entrer tous les glucides en particulier pour la correction des hypo. -- Vous avez beaucoup de périodes avec des RNS détectée lors de la journée - - Avez-vous entré tous vos glucides et les avez vous correctement estimés ? - - Toutes les périodes RNS (sauf si vous n'entrez jamais vos glucides dans AAPS et que le paramètre Categoriser UAM en tant que basal est désactivé) seront catégorisées en basal, cela peut augmenter beaucoup votre Basal (beaucoup plus que nécessaire). - -- L'absorption des glucides est très lente : si la plupart de vos glucides sont calculés avec un paramètre min_5m_carbimpact (vous pouvez voir ces périodes avec un petit point orange en haut de la courbe), le calcul des GA pourrait être erroné et conduire à de mauvais résultats. - - Quand vous faites du sport, vous êtes généralement plus sensible et votre glycémie ne monte pas beaucoup, donc pendant ou après un exercice, il est habituel de voir quelques périodes avec des glucides lents. Mais si vous avez trop souvent une absorption lente inattendue des glucides, alors vous aurez besoin d'un ajustement de profil (valeur plus élevée de G/I) ou d'un min_5m_carbimpact un peu plus élevé. -- Vous avez un "très mauvais jours", par exemple coincé plusieurs heures en hyperglycémie avec une énorme quantité d'insuline pour pouvoir descendre à l'intérieur de la cible, ou après un changement de capteur, vous avez obtenu de longues périodes avec des glycémies erronées. -- Si le pourcentage de modification est trop important - - Vous pouvez essayer d'augmenter le nombre de jours pour obtenir des résultats plus lisses \ No newline at end of file diff --git a/docs/CROWDIN/fr/Usage/making-sport-with-AAPS.md b/docs/CROWDIN/fr/Usage/making-sport-with-AAPS.md deleted file mode 100644 index 79d2f1c38223..000000000000 --- a/docs/CROWDIN/fr/Usage/making-sport-with-AAPS.md +++ /dev/null @@ -1,185 +0,0 @@ -# making sport with AAPS - -In this section we want to address the topic of sport with AAPS. - -The aim is to show you how AAPS can help you to continue doing your favorite sport more easily or even to start doing it. It is relatively common for new type 1 diabetics to ask whether exercise is still possible for them, even if the answer in the training courses is actually a clear yes. Exercise is not only good for healthy people, but also for type 1 diabetics and even moderate exercise can even help to stabilize the blood sugar curve overall. - -:::{admonition} consult with your diabetes team after reading - -::: - -The difficulty here is that the prerequisites that someone brings with them and the expectations of what sport means to them are very different. - -Since we can assume that experienced top athletes with T1D who use AAPS are unlikely to look it up here, we deliberately set the bar low for ourselves when writing and for you when reading and using it, so that as many people as possible can benefit from it. - -Since even sport as a category is far too imprecise, as the effects of endurance sports differ greatly from strength training, for example, we are trying to break it down by type of sport. - -To be concrete and give you something you can test yourself we arrange the explanaiton around a concrete example and explain to you they action, reactions and effects. - -:::{admonition} more examples wanted - -The focus should always be on how others can do sport and not on the top performance someone has achieved. - -It's really about the basics. Your experience, which you share here, can help others to pursue their beloved sport more quickly and successfully and is therefore important. -::: - -## Cycling - -:::{admonition} take a friend with you - at least on your first trials -:class: information -A gerneral very good idea can be to take a good friend with you on the first rides. -This is especially important if you are not experienced in T1D. -Always keep in mind please: arrival comes before speed! Safety for you and the others in road traffic is very, very important. -::: - -### Example - -Let's take about 60 minutes of cycling on a flat route with a moderate heart rate as an example. - -1. we take a flat route in order to have an even load for the first exercise. This is not about performance, but purely about learning how you should react to changes in blood glucose. -2. we take the heart rate as an indicator of the load, as it is easy to see whether you are under load or not. -3. we set ourselves the goal of doing a relaxed lap around the neighborhood and focus on staying within our target range during the lap. In my case, this would be 70 <= x <= 180 mg/dl. - -We **don't** take the speed, as this is heavily dependent on personal physical conditions as well as the bike and surface used. It is therefore not very meaningful. - -You should know from the diabetes training courses you have attended that during endurance sports cycling, the insulin active in the body works significantly better than during times without physical exertion. The insulin active in the body is referred to as insulin on board (IoB). It is our most important parameter when cycling with T1D. - -We try to keep the IoB as low as possible at the start and during exercise. IoB should be around 0 or even slightly negative. You can get it there by not eating 3-4 hours before exercise. In the beginning it can also be helpful to exercise in the morning before breakfast, as with the right profile you should always have around 0 for IoB in the morning. - -AAPS shows us the IoB value on the home screen on the left under the blood glucose value. - -![IoB](../images/cycling_20240104-174035.png) - -:::{admonition} ignoring the IoB rule increases the risk for roller coaster BG dramatically -:class: danger -If you ignore this rule, you can still go cycling, but it will be much more difficult to keep your blood sugar levels in balance, so it is better to save this for later tests after several successful simple tests. -::: - -As you should know from the diabetes training courses, you should reduce the basal rate during exercise. The factor is individual. I have found a value of 50% in tests to be suitable for me. - -In AAPS, you should therefore change your profile to 50% before exercise and keep it active until the end of exercise. Some people even do it a certain amount of time before, e.g. 1 hour. Unfortunately, the pre-run is also individual. We will come to the post-run later. - -You should use two carbohydrates during exercise. - -1. medium-fast carbohydrates for the insulin still in the body and -2. very fast carbohydrates to prevent slipping into a hypo. - -For medium-fast carbohydrates, I treat myself to cookies or a banana before exercise, for example. You can also use something else that is more suitable for you. -For very fast carbohydrates, I take 3 teaspoons of dissolved glucose per 100 ml of still water in a 500 ml water bottle on my bike. If I'm cycling longer distances, I take a larger bottle with me and, if necessary, packaged glucose to refill the bottle. I add a little lemon juice for flavor. You can also use something other than lemon juice for the taste. You shouldn't change anything about the dextrose, as dissolved dextrose raises blood sugar levels super quickly. If you only take it in sips, your blood sugar won't go super high either! You can also do this tip at home beforehand as a dry run and see how quickly the change shows up on the CGMS. - -Why do I place so much emphasis on fast carbohydrates? - -1. once you are in a slight hypo, you may get back into the normal range by drinking the dextrose solution. As a rule, however, the oscillation of the curve then begins, which leads to a rollercoaster ride of the blood sugar. You may even be able to keep this within your target range, but you must be constantly vigilant. Without a hypo it is simply the most stable. -2. if you even slip into a somewhat severe hypo (without the need for outside help, of course), you may even have to pause briefly to avoid getting stuck in the hypo. - With both hypos, there is a risk that you will be tempted to switch from drinking 2-3 sips at a time to larger quantities. Not too bad at first, until the oscillation sets in and pushes you into a hyper. You can correct this, but your blood sugar will most likely go on a rollercoaster ride. - -What else is helpful, but not absolutely necessary? -It is important to keep an eye on your blood sugar, as your blood sugar can change enormously (e.g. 30 - 50 mg/dl) within 15 minutes of riding and a little more IoB or a basal rate that is still too high. The best way to keep an eye on it is if it is visible on the handlebars or if it is also displayed on your watch. It is even possible to install an additional app on some Garmin GPS bike computers that displays the blood glucose from XDrip or Nightscout as a data field on the bike computer. The additional app was developed by Andreas May from the T1D community. It is available free of charge in the official connect IQ Store. Certainly an interesting option for riders interested in sports. - -[Link to Andreas May Data Field App on connect IQ store](https://apps.garmin.com/de-DE/apps/5a3e2cda-12f0-4afd-88ed-000e67a68d84) - -Here is a picture of my Garmin Edge 530 bike computer with map, blood sugar and heart rate. - -![Garmin Edge 530 with BG data field](../images/cycling_IMG_1087.jpeg) - -After you have eaten the medium fast carbohydrates (24 - 36 g I take) and the blood sugar is above 100 mg/dl but also below 160 mg/dl, I carry out the profile change to 50% and set the activity temp target. - -:::{admonition} disable SMBs during high temp targets if necessary -:class: danger -Attention: If you prefer not to receive SMBs during the sport, please disable the option "Enable SMB with hight temp targets" in the settings of SMB or DynIFS Plugin. -::: - -The following picture shows the start and end of the sport. The end was specified as the duration when the profile was changed at the start. - -The temporary profile change has the following effects - -1. for a period of 60 minutes -2. a reduction to 50% of the profile and -3. the target is raised by clicking on the Activity Target option, which may have the side effect of disabling the SMBs - see above. - -![profile switch with temp target](../images/cycling_20240104-174056.png) - -The second image shows that the start at IoB was started towards 0. - -![IoB around 0](../images/cycling_20240104-174111.png) - -If the blood sugar drops faster than 15 mg/dl in 5 minutes or if it is at 120 mg/dl and tends to fall, I drink 1-2 sips of dissolved glucose. Then I wait for the next value and proceed as described above. - -You can hardly see it here, but at the beginning I took 2 sips from the bottle several times when my blood sugar started to fall. When it stabilized, I didn't need any more glucose. - -Here is the picture that illustrates this. The chart is saved on the Garmin as a result of the activity. - -![BG chart Garmin](../images/cycling_20240104-174431.png) - -If you should suddenly break out upwards, i.e. above 180 mg/dl, you should consider whether you should make a correction bolus. Caution: Remember the factor and apply it to the correction, otherwise the correction will be too strong. - -If your blood sugar drops below 80 mg/dl, take a break and drink two sips until your blood sugar is back above 100 mg/dl. - -At the end of the ride, the profile change should be finished as the time is up. - -Since we only rode easy for 60 minutes, there shouldn't be a big muscle bulking effect continuing to pull carbohydrates from your blood sugar. However, if it felt strenuous to you, keep an eye on it. This is especially true if you then go straight to bed. It may be better to change your profile to e.g. 80% for sleep. You may come out of sleep slightly too high, but it's better than having a hypo at night. Over time, you will surely find out what happens to you. - -The following pictures show the low intensity of the sport. - -The elevation profile -![](../images/cycling_20240104-174314.png) - -Speed with average and maximum speed - -![](../images/cycling_20240104-174326.png) - -Note the pause at the level crossing, which is also reflected in the heart rate. - -The heart rate. -![](../images/cycling_20240104-174337.png) - -The training effect. -![](../images/cycling_20240104-174358.png) - -The time in the different heart rate training zones. -![](../images/cycling_20240104-174423.png) - -After succesfully mastering this simple example you could go for further targets by stretching - -1. the distance and time -2. the load during the ride -3. the elevation during the right which should make a big impact on the more necessary carbs or further reduction of IoB and percentage of profile switch. - -Based on my experiences I would not expect to come back 100% with time in range over the whole and every ride. - -### Tipps - -I already gave some tipps for during the ride above. - -Here are some further tipps what can go wrong and how you can act to prevent it or react to compensate it. - -#### sky rocket high after ride - -During the ride everything was fine but after siting down and relax the blood sugar go sky rocket high. - -**Possible reason:** This happens when you have drunk too much dissolved glucose. - -**Reaction:** Drink 500 ml water, go to the shower and then control again. Latest after 30 minutes think about giving a correction bolus but be careful when it is short for bed time. Therefore it can be very good to make the first try runs on weekend mornings. - -**Action:** Next time be a bit more cautious in drinking from the dissolved glucose. - -#### hypo during ride - -During the ride you are going into hypo and can't recover your blood sugar during cycling. - -**Possible reason:** Your body cannot absorb enough carbohydrates quickly enough during exercise. - -**Reaction:** Take a rest and corrrect your blood sugar with drinking dissolved glucose. Stay calm: arrival comes before speed. - -**Action:** Did you started with IoB near 0? Have you eaten a small amount of middle fast carbs? Can you increase this or are the not fast enough for your body? Is it possible to prevent going into hypo by reducing the factor for the profile switch? Have you disbaled SMBs during ride as explained above? - -#### sky rocket high during ride - -During the ride your blood sugar goes sky rocket high. - -**Possible reason:** You have got taken too much carbs for your IoB at that time. Beneath for sure the typical technical problems with your -insulin pump like leakage or blockage of the catheder! - -**Reaction:** If it is too high for you take a rest and correct with a bolus. Keep in mind that you must ride home and therefore make it carefully. Drink 500 ml pure water without carbs. Stay calm: arrival comes before speed. - -**Action:** Have you eaten too much? Especially have you drunk too much from the dissolved glucose during the ride? Is your percentage of reduction the profile during profile switch too low and you can increase this? diff --git a/docs/CROWDIN/fr/Where-To-Go-For-Help/How-to-get-support.md b/docs/CROWDIN/fr/Where-To-Go-For-Help/How-to-get-support.md deleted file mode 100644 index b58ecc8978b6..000000000000 --- a/docs/CROWDIN/fr/Where-To-Go-For-Help/How-to-get-support.md +++ /dev/null @@ -1,11 +0,0 @@ -# How to get support - -**Level 1:** Wiki - we now have a search function! - -**Level 2:** [Facebook](https://www.facebook.com/groups/AndroidAPSUsers/) OR [gitter](https://gitter.im/MilosKozak/AndroidAPS) - -**Level 3:** Gitter (if FB did not get results, wait at least a couple of hours (plural)!!! Direct crossposts will be ignored/deleted on both channels!!!) - -**Level 4:** Create an issue with logs and time of the issue - -**Level 5:** PM (only if personal data is involved that should not go in a public channel) \ No newline at end of file diff --git a/docs/CROWDIN/fr/buildingAAPS.md b/docs/CROWDIN/fr/buildingAAPS.md deleted file mode 100644 index 98164a09e49b..000000000000 --- a/docs/CROWDIN/fr/buildingAAPS.md +++ /dev/null @@ -1,28 +0,0 @@ -# Dummy - -## This is a dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - - -## This is another dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - - -## This is another another dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - diff --git a/docs/CROWDIN/fr/completingObjetives.md b/docs/CROWDIN/fr/completingObjetives.md deleted file mode 100644 index 98164a09e49b..000000000000 --- a/docs/CROWDIN/fr/completingObjetives.md +++ /dev/null @@ -1,28 +0,0 @@ -# Dummy - -## This is a dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - - -## This is another dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - - -## This is another another dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - diff --git a/docs/CROWDIN/fr/dummy.md b/docs/CROWDIN/fr/dummy.md deleted file mode 100644 index 98164a09e49b..000000000000 --- a/docs/CROWDIN/fr/dummy.md +++ /dev/null @@ -1,28 +0,0 @@ -# Dummy - -## This is a dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - - -## This is another dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - - -## This is another another dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - diff --git a/docs/CROWDIN/fr/intro.md b/docs/CROWDIN/fr/intro.md deleted file mode 100644 index a7633256f719..000000000000 --- a/docs/CROWDIN/fr/intro.md +++ /dev/null @@ -1,291 +0,0 @@ -![20-06-23v2 AAPS simple overview-cropped](https://github.com/openaps/AndroidAPSdocs/assets/94044064/e505b73b-09a0-42a4-a1ab-b830a0741234) - -# Introduction to APS and AAPS - -## What is an “Artificial Pancreas System”? - -A human pancreas does a lot of things besides regulating blood sugar. However, the term **“Artificial Pancreas System” (APS)** usually refers to a system which works to automatically keep blood sugar levels within healthy limits. - -The most basic way to do this is by detecting **glucose levels**, using these values to do **calculations**, and then delivering the (predicted) right amount of **insulin** to the body. It repeats the calculation, every few minutes, 24/7. It uses **alarms** and **alerts** to inform the user if intervention or attention is needed. This system is typically made up of a **glucose sensor**, an **insulin pump** and an **app** on a phone. - -You can read more about the different artificial pancreas systems currently in use and in development in this 2022 review article: - -![Frontiers](./images/FRONTIERS_Logo_Grey_RGB.png) [Future Directions in Closed-Loop Technology](https://www.frontiersin.org/articles/10.3389/fendo.2022.919942/full#:~:text=Fully%20closed%2Dloop%20systems%2C%20unlike,user%20input%20for%20mealtime%20boluses). - -In the near future, some so-called "dual-hormone" systems will also have the ability to infuse glucagon alongside insulin, with the aim of preventing severe hypos and allowing even tighter blood glucose control. - -An artificial pancreas can be thought of as an [“autopilot for your diabetes”]. (https://www.artificialpancreasbook.com/) What does that mean? In an aircraft, an autopilot does not do the complete job of the human pilot, the pilot cannot sleep through the entire flight. The autopilot aids the work of the pilot. It relieves them of the burden of permanently monitoring the aircraft, allowing the pilot to concentrate on wider monitoring from time to time. The autopilot receives signals from various sensors, a computer evaluates them together with the pilot’s specifications and then makes the necessary adjustments, alerting the pilot to any concerns. The pilot no longer has to worry about constantly making decisions. - -## What does hybrid closed loop mean? - -The best solution for type 1 diabetes would be a “functional cure” (probably an implant of pancreatic cells which are protected from the immune system). While we are waiting for that, a “full closed loop” artificial pancreas is probably the next best thing. This is a tech system that doesn’t need any user input (like bolusing insulin for meals, or announcing exercise), with good regulation of blood glucose levels. At the moment, there are no widely available systems which are “full” closed loop, they all need some user input. The currently available systems are called “hybrid” closed loop, because they use a combination of automated technology and user input. - -## How and why did looping start? - -The development of commercial technology for people with type 1 diabetes (T1D) is very slow. In 2013 the T1D community founded the #WeAreNotWaiting movement. They developed systems themselves using existing approved technology (insulin pumps and sensors) to improve blood glucose control, safety, and quality of life. These are known as DIY (do-it-yourself) systems, because they are not formally approved by health bodies (FDA, NHS etc). There are four main DIY systems available: OpenAPS, **AAPS**, Loop and iAPS. - -A great way to understand the fundamentals of DIY looping is to read Dana Lewis’s book “Automated Insulin Delivery”. You can access it \[here\] (https://www.artificialpancreasbook.com/) for free (or buy a hardcopy of the book). If you want to understand more about OpenAPS, which** AAPS** has developed from, the \[OpenAPS website\] (https://openaps.org/what-is-openaps/) is also a great resource. - -Several commercial hybrid closed loop systems have been launched, the most recent of which are \[CamAPS FX\] (https://camdiab.com/) (UK and EU) and \[Omnipod 5\] (https://www.omnipod.com/en-gb/what-is-omnipod/omnipod-5) (USA and EU). These are very different to DIY systems, mainly because they both include a “learning algorithm” which adjusts how much insulin is delivered according to your insulin needs from previous days. Many people in the DIY community have already tried out these commercial systems and compared them with their DIY system. You can find out more about how the different systems compare by asking on the dedicated Facebook groups for these systems, on the \[AAPS Facebook group\] (https://www.facebook.com/groups/AndroidAPSUsers/) or on \[Discord\] (https://discord.com/invite/4fQUWHZ4Mw). - -## What is Android APS (AAPS)? - -![image](https://github.com/openaps/AndroidAPSdocs/assets/94044064/0f089d96-b7ee-452a-aa9d-aae10ab58971) - -**Figure 1**. Basic outline of the Android APS (Artificial Pancreas System), AAPS. - -Android APS (AAPS) is a hybrid closed loop system, or Artificial Pancreas System (APS). It makes its insulin dosing calculations using established \[OpenAPS\] (https://openaps.org/) algorithms (a set of rules) developed by the #WeAreNotWaiting type 1 diabetes community. - -Since OpenAPS is only compatible with certain older insulin pumps, AAPS (which can be used with a wider range of insulin pumps) was developed in 2016 by Milos Kozak, for a family member with type 1 diabetes. Since those early days, **AAPS** has been continually developed and refined by a team of volunteer computer developers and other enthusiasts who have a connection to the type 1 diabetes world. Today, **AAPS** is used by approximately 10,000 people. It is a highly customisable and versatile system, and because it is open-source, it is also readily compatible with many other open-source diabetes softwares and platforms. The fundamental components of the current **AAPS** system are outlined in Figure 1 above. - -## What are the basic components of AAPS? - -The “brain” of AAPS is an **app** which you build yourself. There are detailed step-by-step instructions for this. You then install the **AAPS app** on a compatible **Android smartphone** (1). A number of users prefer their loop on a separate phone to their main phone. So, you don’t necessarily have to be using an Android phone for everything else in your life, just for running your AAPS loop. - -The **Android smartphone** will also need to have another app installed on it as well as **AAPS**, either a modified Dexcom app called build-your-own dexcom app (**BYODA**) or Xdrip+. This receives glucose data from a sensor (2) by bluetooth, and then sends the data internally on the phone to the **AAPS app**. - -The **AAPS app** uses a decision making process (**algorithm**) from OpenAPS. Beginners start out using the basic **oref0** algorithm, but it is possible to switch to using the newer **oref1** algorithm as you progress with AAPS. Which algorithm you use (oref0 or oref1), depends on which suits your specific situation best. In both cases, the algorithm takes into account multiple factors, and performs rapid calculations every time a new reading comes in from the sensor. The algorithm then sends instructions to the insulin pump (3) on how much insulin to deliver by bluetooth. All the information can be sent by mobile data or wifi to the internet. This data can also be shared with followers if desired, and/or collected for analysis. - -## What are the advantages of the AAPS system? - -The OpenAPS algorithm used by **AAPS** controls blood sugar levels in the absence of user input, according to the users’ defined parameters (important ones being basal rates, insulin sensitivity factors, insulin-to-carb ratios, duration of insulin activity etc.), reacting every 5 minutes to the new sensor data. Some of the reported advantages of using AAPS are extensive fine-tunable options, automations and increased transparency of the system for the patient/caregiver. This can result in better control over your (or your dependent’s) diabetes, which in turn may give improved quality of life and increased peace of mind. - -Practical advantages include: - -- **Hardware flexibility**: **AAPS** works with a wide range of insulin pumps and sensors. So for example, if you develop an allergy to Dexcom sensor patch glue, you could switch to using a Libre sensor instead. That offers flexibility as life changes. You don't have to rebuild, just tick a different box in the AAPS app to change your hardware. - -- **Highly customisable with wide parameters**: here are some examples of the possibilities with AAPS: a) The ability to set a lower glucose target 30 min before eating; you can set the target as low as 72 mg/dL (4.0 mmol/L). b) If you are insulin-resistant resulting in high blood sugars, **AAPS** allows you to set an **automation** rule to activate when BG rises above 8 mmol/L (144 mg/dL), switching to a 120% profile (resulting in an 20% increase in basal and strengthening of other factors too, compared to your normal **profile** setting). The automation will last according to the scheduled time you set. Such an automation could be set to only be active on certain days of the week, at certain times of day, and even at certain locations. c) If your child is on a trampoline with no advance notice, **AAPS** allows insulin suspension for a set time period, directly via the phone. d) After reconnecting a tubed pump which has been disconnected for swimming, AAPS will calculate the basal insulin you have missed while disconnected and deliver it carefully, according to your current BG. Any insulin not required can be overridden by just “cancelling” the missed basal. f) **AAPS** has the ability to set different profiles for different situations and easily switch between them. Features which make the algorithm quicker to bring down elevated BG (like supermicro boluses (“SMB”), unannounced meals, (“**UAM**”) can be set to only work during the daytime, if you are worried about night-time hypos. - - -These are all examples, the full range of features gives huge flexibility for daily life including sport, illness, hormone cycles etc. Ultimately, it is for the user to decide how to use this flexibility, and there is no one-size-fits-all automation for this. - -- **Remote monitoring**: there are multiple possible monitoring channels (Sugarmate, Dexcom Follow, Xdrip+, Android Auto etc.) which are useful for parents/carers and adults in certain scenarios (sleeping/driving) who need customisable alerts. In some apps (Xdrip+) you can also turn alarms off totally, which is great if you have a new sensor “soaking” or settling down that you don’t want to loop with yet. - -- **Remote control**: a significant advantage of **AAPS **over commercial systems is that it is possible for followers, using authenticated text (SMS) commands or via an app (Nightscout or NSClient) to send a wide range of commands back to the ****AAPS** **system. This is used extensively by parents of kids with type 1 diabetes who use AAPS. It is very useful in the playground, for example, if you want to pre-bolus for a snack from your own phone, and your child is busy playing. It is possible to monitor the system (e.g. Fitbit), send basic commands (e.g. Samsung Galaxy watch 4), or even run the entire AAPS system from a high-spec smartwatch (5) (e.g. LEMFO LEM14). In this last scenario, you don’t need to use a phone to run AAPS. As battery life on watches improves, this last option is likely to become increasingly attractive. - -- **No commercial constraints due to open application interfaces**: beyond the use of an open source approach, which allows the source code of **AAPS** to be viewed at any time, the general principle of providing open programming interfaces gives other developers the opportunity to contribute new ideas that allow users to live more easily with their diabetes. This is complementary to commercial systems which adopt the innovations from DIY, where interfaces are only made possible in return for licensing, thus preventing innovations in particular that are not-for-profit. Good examples for such integrations are NightScout, Nightscout Reporter, Xdrip+ M5 stack etc. - -- **Detailed app interface**: It is easy to keep track of things like: insulin levels, cannula age, sensor age, pump battery age, and many actions can be done through the **AAPS** app (priming the pump, disconnecting the pump etc.), instead of on the pump itself. - -- **Accessibility and affordability**: **AAPS** gives people who currently can’t afford to self-fund, or don’t have funding/insurance, access to a world-class hybrid closed looping system which is conceptually years ahead, in terms of development, of the commercial systems being offered by clinics. You currently need to have a Nightscout account to set up **AAPS**. Although the Nightscout account it not necessarily required after setup, many people continue to use Nightscout for collecting their data, and for remote control. So, although **AAPS **itself is free, setting up Nightscout through one of the various platforms may incur a fee (E0 - E12), depending on what level of support you want (see comparison table). **AAPS** works with a wide range of affordable (starting from approx E150) Android phones. In comparison, Loop currently costs around $80 a year for the Apple development licence and CamAPS FX costs around E80/month (as at 2023). - -- ****Support**: No automated insulin delivery system is perfect. Commercial and open-source systems share many common glitches in both communications and temporary hardware failure. There is a community of AAPS users on both Facebook and Discord and Github who designed, developed and are currently using **AAPS** all over the world. There are Facebook support groups and help from clinic/commercial companies for the commercial APS systems - it is worth speaking to the users, or former users of these systems to get feedback on the common glitches, the quality of the education programme and the level of ongoing support provided. - -- **Predictability, transparency and safety**: with no learning algorithm, **AAPS** is logical and in some respect, more predictable, which may make it easier to know when a setting is wrong, and to adjust it accordingly. You can see exactly what the system is doing, why it is doing it, and set its operational limits, which puts the control (and responsibility) in your hands. This can provide the user with confidence, and a sounder sleep. - -- **Access to advanced features through dev modes including full closed loop**: **AAPS **documentation focuses on the mainstream **“master”** branch of **AAPS**, however, research and development is going on all the time. More experienced users may wish to explore the experimental features in the **development** branch such as integration of Dexcom G7, and automatically adjusting insulin delivery according to short-term sensitivity changes (DYNISF), not having to bolus for meals, and generally trying to make life with type 1 diabetes as convenient as possible. - -- **Ability to contribute yourself to further improvements**: type 1 diabetes can be highly frustrating and isolating. Having control over your own diabetes tech, with the possibility to “pay it forward” as soon as you are making progress by helping others on their journey can be really rewarding. You can educate yourself, discover the roadblocks and look for and even contribute to new developments and the documentation. There will be others with the same quest to bounce ideas off and work with. This is the essence of #WeAreNotWaiting. - - -## How does AAPS compare to MDI and open looping? - -Multiple daily injections (MDI, a) usually involve giving an injection of a long-lasting insulin (e.g. Tresiba) once a day, with injections of faster-acting insulin (e.g. Novorapid, Fiasp) at mealtimes, or for corrections. Open pumping (b) involves using a pump to deliver basal at pre-programmed rates of rapid-acting insulin, and then boluses through the pump at mealtimes or for corrections. The basics of a looping system is that the App uses the glucose data to instruct the pump to stop insulin delivery when it predicts you are heading for a low, and to give you extra insulin if your glucose levels are rising and predicted to go too high (c). Although this is oversimplified, (mostly because hybrid closed looping has a lot of additional useful features) the key features of each system are shown in **Figure 2**. - -![image](https://github.com/openaps/AndroidAPSdocs/assets/94044064/4e7d8608-684d-4c69-9c61-88c9539f5d6f) - -**Figure 2**. Overview of (a) MDI, (b) open-loop pumping and (c) hybrid closed loop pumping - -## How does AAPS compare to other looping systems? - -At present there are four major open source closed loop systems available: OpenAPS, **AAPS**, \[Loop\] (https://loopkit.github.io/loopdocs/#what-is-loop) and iAPS, (formerly FreeAPS X). The features of the different systems are shown in the table below: - -| Devicestyp | Name | [Open APS](https://openaps.readthedocs.io/en/latest/) | [AAPS](https://wiki.aaps.app) | [Boucle](https://loopkit.github.io/loopdocs/) | [iAPS](https://iaps.readthedocs.io/en/latest/) | -| ---------- | -------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------- | ------------------------------------------- | --------------------------------------------- | ---------------------------------------------- | -| PUMP | Older Medtronic | ![available](./images/available.png) | ![available](./images/available.png) | ![available](./images/available.png) | ![available](./images/available.png) | -| PUMP | Older Omnipod (Eros) | ![unavailable](./images/unavailable.png) | ![available](./images/available.png) | ![available](./images/available.png) | ![available](./images/available.png) | -| PUMP | Newer Omnipod (Dash) | ![unavailable](./images/unavailable.png) | ![available](./images/available.png) | ![available](./images/available.png) | ![available](./images/available.png) | -| PUMP | DANA R, DANA RS, DANA I | ![unavailable](./images/unavailable.png) | ![available](./images/available.png) | ![unavailable](./images/unavailable.png) | ![unavailable](./images/unavailable.png) | -| PUMP | Roche Combo, Insight | ![unavailable](./images/unavailable.png) | ![available](./images/available.png) | ![unavailable](./images/unavailable.png) | ![unavailable](./images/unavailable.png) | -| MGC | Dexcom G4, G5, G6 | ![available](./images/available.png) | ![available](./images/available.png) | ![available](./images/available.png) | ![available](./images/available.png) | -| MGC | Libre 1 (requires Miao Miao) | ![available](./images/available.png) | ![available](./images/available.png) | ![available](./images/available.png) | ![available](./images/available.png) | -| MGC | Libre 2 | ![available](./images/available.png) | ![available](./images/available.png) | ![available](./images/available.png) | ![available](./images/available.png) | -| MGC | Libre 3 | | ![unavailable](./images/unavailable.png) | --- | ![unavailable](./images/unavailable.png) | -| MGC | Medtronic Enlite | | --- | ![unavailable](./images/unavailable.png) | --- | -| MGC | [Dexcom G7](https://androidaps.readthedocs.io/en/latest/Hardware/DexcomG7.html) | | ![available](./images/available.png) (beta) | ![available](./images/available.png) | ![available](./images/available.png) | -| MGC | [Eversense](https://androidaps.readthedocs.io/en/latest/Hardware/Eversense.html) | | ![available](./images/available.png) | | ![available](./images/available.png) | -| MGC | [MM640g/MM630g](https://androidaps.readthedocs.io/en/latest/Hardware/MM640g.html) | | ![available](./images/available.png) | | ![available](./images/available.png) | -| MGC | [PocTech](https://androidaps.readthedocs.io/en/latest/Hardware/PocTech.html) | | ![available](./images/available.png) | | ![available](./images/available.png) | -| MGC | [Nightscout comme source de glycémie](https://androidaps.readthedocs.io/en/latest/Hardware/CgmNightscoutUpload.html) | | ![available](./images/available.png) | | ![available](./images/available.png) | -| Téléphone | Android | ![available](./images/available.png) | ![available](./images/available.png) | ![unavailable](./images/unavailable.png) | ![unavailable](./images/unavailable.png) | -| Téléphone | iPhone | ![available](./images/available.png) | ![unavailable](./images/unavailable.png) | ![available](./images/available.png) | ![available](./images/available.png) | - -[OpenAPS](https://openaps.readthedocs.io/) was the first Open Source Closed Loop System. Il utilise un petit ordinateur comme un Raspberry Pi ou un Intel Edison. Both AndroidAPS (AAPS) and iAPS use the OpenAPS algorithms, whereas Loop uses a separate algorithm. You can read a comparison of iAPS and **AAPS** here. - -An international peer-reviewed consensus statement containing practical guidance on open source looping was written by and for health-care professionals, and published in a leading medical journal in 2022. It is well worth a read (including for your diabetes clinic) and summarises the main technical differences between the different open-source hybrid closed loop systems: - - Lancet Diabetes Endocrinol, 2022; 10: 58–74 - -[https://www.ncbi.nlm.nih.gov/pmc/articles/PMC8720075/](https://www.ncbi.nlm.nih.gov/pmc/articles/PMC8720075/) - -It is hard to get a “feel” for any system without using it, or talking to others who are using it, so do reach out to others on Facebook/Discord and ask. Most people find that AAPS is incredibly sophisticated in comparison to other hybrid closed loop systems (particularly the commercial systems), with a huge number of potentially customisable settings and features, discussed above. Some people can find this a little overwhelming in the beginning, but there is no rush to investigate all the possibilities at once, you can progress as slowly or as fast as you would like, and there is help available at every step of the way. - -## Does AAPS use artificial intelligence or any learning algorithm? - -Non. **AAPS** does not have any complicated machine learning algorithms, multiple-parameter insulin response models, or differential equations. As such, the system is open and transparent in how it works, and has the ability to be understood not just by experts, but also by clinicians and patients. It also means that if you have a sharply varying schedule (maybe switching from a stressful week at work to a relaxing holiday) and are likely to need a significantly different amount of insulin, you can immediately switch **AAPS** to run a weaker/stronger profile. A ‘learning system’ will do this adjustment for you automatically, but is likely to take longer to adjust the insulin delivery. - -## Which system is right for me or my dependent? - -Practically, your choice of system is often restricted by which pump you already have, or can obtain from your medical provider, and your choice of phone (Apple or Android). If you don’t yet have a pump you have the biggest choice of systems. Technology is continually evolving, pumps are being discontinued and new pumps and sensors are being released. Most open-source systems work with the main sensors (Libre and Dexcom) or are quickly adapted to work with new sensors a year or so after they are released (with a bit of time delay for safety and stability testing). - -Most **AAPS **users report more time in range, HbA1c reductions, as well as quality of life improvements from having a system that can auto-adjust basal rates overnight during sleep, and this is true for most hybrid closed loop APS. Some people have a preference for a very simple system which is not very customisable (which means you may prefer a commercial system), and others find this lack of control very frustrating (you may prefer an open-source system). If you (or your dependent) are newly diagnosed, a common route is to get the hang of MDI plus sensor first, then progress to a pump which has the potential for looping, then to **AAPS**, but some people (especially small kids) may go straight to a pump. - -It is important to note that the **AAPS** user needs to be proactive to troubleshoot and fix problems themselves, with help from the community. This is a very different mindset to that when using a commercial system. With **AAPS** a user has more control, but also the responsibility, and needs to be comfortable with that. - -## Is it safe to use open-source systems like AAPS? - -A more accurate question is probably “is it safe compared to my current type 1 diabetes insulin delivery system?” since no method of insulin delivery is without risk. There are many checks and balances in place with **AAPS**. A recent paper looked at the use of**** AAPS ****in a computer simulated set-up, [https://www.liebertpub.com/doi/epub/10.1089/dia.2019.0375](https://www.liebertpub.com/doi/epub/10.1089/dia.2019.0375) which was an effective way to unobjectively trial how safe and effective the system is. More generally, it is estimated that over 10,000 individuals worldwide are using open-source automated-insulin delivery systems, and uptake continues to increase globally. - -Any device that uses radio communications could be hacked, and this is true for a non-looping insulin pump as well. Currently, we are not aware of anyone attempting to harm individuals by hacking their diabetes-related medical equipment. However, there are multiple ways to protect against such risks: - -1. In the pump settings, limit both the max bolus allowed and max temporary basal settings to amounts that you believe are safest. These are hard limits that we do not believe any malicious hacker could circumvent. - -2. Set your CGM alarms enabled for both highs and lows. - -3. Monitor your insulin delivery online. Nightscout users can set additional alarms to alert for a wide variety of conditions, including conditions that are much more likely to occur than a malicious attack. In addition to highs and lows, Nightscout can display diagnostic data useful for verifying that the pump is operating as desired, including current IOB, pump temporary basal history, pump bolus history. It can also be configured to proactively alert users to undesirable conditions, such as predicted highs and lows, low insulin reservoir, and low pump battery. - - -If a malicious attack was made on your insulin pump, these strategies would significantly mitigate the risk. Every potential **AAPS** user needs to weigh the risks associated with using **AAPS**, versus the risks of using a different system. - -## How can I approach discussing AAPS with my clinical team? - -Depending on the country - link to doctors section of docs - - Lancet Diabetes Endocrinol, 2022; 10: 58–74 - -[https://www.ncbi.nlm.nih.gov/pmc/articles/PMC8720075/](https://www.ncbi.nlm.nih.gov/pmc/articles/PMC8720075/) - -## Q: Why can’t I just download AAPS and use it straight away? - -The **AAPS** app is not provided in Google Play - you have to build it from source code by yourself for legal reasons. **AAPS** is unlicensed, meaning that it does not have approval by any regulatory body authority in any country. **AAPS**is deemed to be carrying out a medical experiment on yourself, and is carried out at the user’s own risk. - -Setting up the system requires patience, determination and the gradual development of technical knowledge. All the information and support can be found in these documents, elsewhere online, or from others who have already done it. It is estimated that over 2000 people have successfully built and are currently using **AAPS** worldwide. - -The developers of **AAPS**t ake safety incredibly seriously, and want others to have a good experience of using **AAPS**. That is why it is essential that every user (or carer, if the user is a child): - -- builds the AAPS system themself and works through the **objectives** so that they have reasonably good personalised settings and understand the basics of how AAPS ****works by the time they “close the loop”; - -- backs up their system by exporting and saving important files (like keystore and settings .json file) somewhere safe, so you can setup again quickly if needed; - -- updates to newer master versions as and when they become available; and - -- maintains and monitors the system to ensure it is working properly. - - -## Q: What is the connectivity of the AAPS system? - -**Figure 3 (below)** shows one example of the **AAPS** system for a user who do not require any followers interacting with the system: - -![potential AAPS connectivity setup with no followers](./images/intro03.png) - -**Figure 4 (below)** shows the full potential of the **AAPS** system for a user who has followers and requires a monitor and send adjust the system remotely (like a child with T1D): - -![potential AAPS connectivity setup with followers](./images/intro04.png) - -## Q: How does AAPS get continually developed and improved? - -Most **AAPS** users use the fully tested **master** version of AAPS, which has been tested for bugs and problems, before being released to the community. Behind the scenes, the developers try out new improvements, and test these out in “developer” (**dev**) versions of **AAPS** with a user community who are happy to do bug updates at short notice. If the improvements work well, they are then released as a new “master” version of **AAPS**. Any new master release is announced on the Facebook group, so that the mainstream **AAPS** users can read about and update to the new master version. - -Some experienced and confident **AAPS ** users conduct experiments with emerging technologies and with dev versions of the **AAPS** app, which can be interesting for the less adventurous users to read about, without having to do it themselves! People tend to share these experiments on the Facebook group too. - -You can read more about some of these experiments and discussion on emerging tech here: - -[https://www.diabettech.com/](https://www.diabettech.com/) - -[https://bionicwookie.com/](https://bionicwookie.com/) - -## Q: Who can benefit? - -| User Type | -| ------------------------------------------- | -| ✔️ type 1 diabetic | -| ✔️ caregiver or parent of a type 1 diabetic | -| ✔️ blind users type 1 diabetic | -| ✔️ *clincians and healthcare professionals | - -The above table assumes that the user has access to both continuous gluocse monitor and insulin pump. - -*All data from **AAPS** can be made available to healthcare professionals via data sharing platforms, including NightScout that provides logging and real time monitoring of CGM data, insulin delivery, carbohydrate entries, predictions and settings. Nightscout records include daily and weekly reports which can aid healthcare professionals' discussions with type 1 patients with more accurate data on glycemic control and any behavioural considerations. - -## Q: What benefits can I get? - -With investment of your time, **AAPS** can potentially lead to: - -- alleviating the stress and burden of managing type 1 diabetes; - -- reducing the multitude of mundane decisions that arise from type 1 diabetes; - -- the provision of personalised and dynamic insulin dosing based on real-time data which can cut down the need for hypo treatments and reduce hyperglycemia episodes; - -- an increased knowledge of insulin management and confidence to better fine tune your settings; - -- the ability to create automatic settings (**automations**) that are tailored to fit in with your lifestyle; - -- improved sleep quality and overall reduction in the frequency of nighttime interventions; - -- remote monitoring and administration of insulin delivery for caregivers of type 1 diabetics; and - -- streamlining of all your portable diabetic equipment (continuous glucose monitor and insulin portable devices) by replacing them with an android phone controlled by **AAPS**. - - -Ultimately,**AAPS** can empower individuals to better manage their diabetes resulting in stable blood sugars and improved long term health outcomes. - ---- - -## AAPS First Steps - -Welcome. This is an introduction to aid beginners getting started with **AAPS** (or commonly referred to as "looping"). - -## Safety - -“_With great powers comes great responsibilities…_” - -**AAPS** is designed with an extensive set of safety features with limits imposed and gradually removed with completion of the **objectives **(predominately made up of multiple choice questions). An **AAPS** feature will be unlocked as the Objectives are successfully completed. This process will gradually allow the user to migrate from Open Loop to Closed Loop. - -This has been done to achieve the best possible experience with **AAPS** in order to prevent common mistakes that new users tend to make when starting to loop. The safety parameters have been built upon typical errors and general trends **AAPS** developers have observed with new users. Mistakes can happen because the beginner is inexperienced and too eager to get started with AAPS or has overlooked the required materials. Do not worry, we have all been there! - -## Key Principles - -The key principles and concepts of looping must be understood by the user before using **AAPS**. This is achieved by investing your personal time into reading the **AAPS** documentation, and completing the Objectives which is aimed to provide you with a solid platform for safe and effective use of **AAPS**. The volume of **AAPS** documentation may seem overwhelming at first but be patient and trust the process - with the proper approach, you'll get there! The overall process will depend upon the beginner’s progress and completion of objectives can typically take between 6 to 9 weeks . - -## Plan for hiccups - -At the preliminary stages of **AAPS**, you should expect to experience some hiccups whilst trying to fine tune your settings. **AAPS**’ glitches cannot be flushed out until the system is used in everyday life. Please plan accordingly and allow a sensible amount of time to troubleshoot and resolve such issues. - -## Flexibility/Adaptability - -Success with **AAPS** requires a proactive approach, a willingness to reflect on the BG data and flexibility to make the necessary adjustments to **AAPS** in order to improve your outcomes. Just as it is nearly impossible to learn to play a sport by reading about the rules alone, the same can be said of **AAPS**. - -## Technology compatibility - -There are limitations with **AAPS** as it is accessible for only certain types of insulin pumps or CGMs, and some technology may not be available for use in various countries. In order to avoid any disappointment or frustrations, please read please read Component Set Up (Section INSERT). - -## App Build Time - -The time to build the **AAPS**(under Section INSERT) depends on your level of expertise and technical ability. Typically for inexperienced users, it can take up to half a day or a full day (with help from the community) in order to build the **AAPS**. The process will significantly speed up as you become more experienced at building the **AAPS**. To aid the build process there are sections dedicated for: -- list of questions and answers for frequent errors that are likely to occur under FAQs (Section K); -- “How to install AAPS? (Section INSERT) which includes Troubleshooting subsection. - -## Keystore & configurations settings a export file - -A “keystore” is a password encrypted file unique to your own copy of **AAPS**. Your android phone uses it to ensure that nobody else can upgrade your own copy without the keystore. In short, as part of the **AAPS** build, you should: - -- save the your keystore file (.jks file used to sign your app) in a safe place; -- keep a note of your password for your keystore file. - -By doing the above, this will ensure that you can use that exact same keystore file each time an updated version of **AAPS** is created. On average, there will be 2-3 AAPS updates required each year. - -In addition, **AAPS** provides the ability to export all your configuration settings. This ensures that you can safely recover your system while changing phones, upgrading/reinstalling the application with minimum disruption. - -## Troubleshootng - -Please feel free to reach out to the AAPS community if there is anything you feel unsure about - there is no such thing as a silly question! All users with various levels of experience are encouraged to ask questions as necessary. Response times to questions are usually quick, typically only a few hours due to the volume of **AAPS** users. - -a) check the documentation; b) ask AAPS facebook group (https://www.facebook.com/groups/AndroidAPSUsers); and c) ask our discord channel. - -## Section overview - -AAPS documentation is made up of the following Sections: - -[INSERT ONCE SECTIONS /SUB SECTIONS AGREED] ---- diff --git a/docs/CROWDIN/fr/maintaining.md b/docs/CROWDIN/fr/maintaining.md deleted file mode 100644 index 98164a09e49b..000000000000 --- a/docs/CROWDIN/fr/maintaining.md +++ /dev/null @@ -1,28 +0,0 @@ -# Dummy - -## This is a dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - - -## This is another dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - - -## This is another another dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - diff --git a/docs/CROWDIN/fr/optimizing.md b/docs/CROWDIN/fr/optimizing.md deleted file mode 100644 index 98164a09e49b..000000000000 --- a/docs/CROWDIN/fr/optimizing.md +++ /dev/null @@ -1,28 +0,0 @@ -# Dummy - -## This is a dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - - -## This is another dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - - -## This is another another dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - diff --git a/docs/CROWDIN/fr/prepairing.md b/docs/CROWDIN/fr/prepairing.md deleted file mode 100644 index 3bcca8b43476..000000000000 --- a/docs/CROWDIN/fr/prepairing.md +++ /dev/null @@ -1,145 +0,0 @@ -# Prepairing - -## Guide to the Android APS doc - -### First Steps -Welcome. This is an introduction to aid beginners to the concept of Do-It-Yourself-APS (Android-Artificial-Pancreas-Systems “AAPS”) is commonly referred to as ‘looping’.. - -#### Safetys -“With great powers come great responsibilities…” - -AAPS is designed with an extensive set of safety features with limits imposed and gradually removed with completion of the [Objectives](https://androidaps.readthedocs.io/en/latest/Usage/Objectives.html) (predominately made up of multiple choice questions). An AAPS feature will be unlocked as the Objectives are successfully completed. This process will gradually allow the user to migrate from Open Loop to Closed Loop. - -This has been done to achieve the best possible experience with AAPS by preventing common mistakes new users tend to make when starting to loop. The safety parameters have been built upon typical errors and general trends AAPS developers have observed with new users. Mistakes can happen because the beginner is inexperienced and too eager to get started with AAPS or has overlooked the required materials. Do not worry, we have all been there! - -#### Key Principles - -The key principles and concepts of looping must be understood by the user before using AAPS. This is achieved by investing your personal time into reading the AAPS documentation, and completing the [Objectives](https://androidaps.readthedocs.io/en/latest/Usage/Objectives.html) which is aimed to provide you with a solid platform for safe and effective use of AAPS. The volume of AAPS documentation may seem overwhelming at first but be patient and trust the process - with the proper approach, you'll get there! The overall process will depend upon the beginner’s progress and completion of objectives which typically take between 6 to 9 weeks . - -#### Plan for hiccups - -At the preliminary stages of AAPS, you should expect to experience some hiccups whilst trying to fine tune your settings. AAPS’ glitches cannot be flushed out until the system is used in everyday life. Please plan accordingly and allow a sensible amount of time to troubleshoot and resolve such issues. - -#### Flexibility/Adaptability - -Success with AAPS requires a proactive approach, a willingness to reflect on the BG data and flexibility to make the necessary adjustments to AAPS in order to improve your outcomes. Just as it is nearly impossible to learn to play a sport by reading about the rules alone, the same can be said of AAPS. - -#### Technology compatibility -There are limitations with AAPS as it is accessible for only certain types of insulin pumps or CGMs, and some technology may not be available for use in various countries. In order to avoid any disappointment or frustrations, please read [Component Set Up (Section E).](https://androidaps.readthedocs.io/en/latest/Configuration/BG-Source.html) - -#### App Build time -The time to build the AAPS (under Section D) depends on your level of expertise and technical ability. Typically for inexperienced users, it can take up to half a day or a full day (with help from the community) in order to build the AAPS. The process will significantly speed up as you become more experienced at building the AAPS.  - -To aid the build process there are sections dedicated for: - -- list of questions and answers for frequent errors that are likely to occur under [FAQs (Section](https://androidaps.readthedocs.io/en/latest/Getting-Started/FAQ.html) K); - -- “[How to install AAPS](https://androidaps.readthedocs.io/en/latest/Installing-AndroidAPS/Building-APK.html)? (Section D) which includes [Troubleshooting](https://androidaps.readthedocs.io/en/latest/Usage/troubleshooting.html) subsection. - - -#### Keystore & configuration settings export  file - -A “keystore” is a password encrypted file unique to your own copy of AAPS. Your android phone uses it to ensure that nobody else can upgrade your own copy without the keystore.In short, as part of the AAPS build, you should: - -1. save the your keystore file (.jks file used to sign your app) in a safe place; - -2. keep a note of your password for your keystore file. - - -By doing the above, this will ensure that you can use that exact same keystore file each time an updated version of AAPS is created. On average, there will be 2-3 updates to the AAPS required each year. In addition, AAPS provides the ability to [export all your configuration settings](https://androidaps.readthedocs.io/en/latest/Usage/ExportImportSettings.html). This ensures that you can safely recover your system while changing phones, upgrading/reinstalling the application with minimum disruption.  - -#### Résolution de problèmes - -Please feel free to reach out to the AAPS community if there is anything you feel unsure about - there is no such thing as a silly question!  All users with various levels of experience are encouraged to ask questions as necessary. Response times to questions are usually quick, typically only a few hours due to the volume of AAPS users.  - -##### [check the documentation](https://androidaps.readthedocs.io/en/latest/index.html) - -##### [ask our facebook group](https://www.facebook.com/groups/AndroidAPSUsers/) - -##### [ask our discord channel](https://discord.com/channels/629952586895851530/629954570394533889) - -#### Section overview - -AAPS documentation is made up of the following Sections: - -##### [Getting started](https://androidaps.readthedocs.io/en/latest/Getting-Started/Safety-first.html) - -This is a must read to understand the general concept of what an artificial pancreas system is designed to do. - -##### [What do I need?](https://androidaps.readthedocs.io/en/latest/Module/module.html) - -This explains AAPS’ compatibility with CGMs (Continuous Glucose Monitors) and insulin pumps. It also provides a guide on the correct assembly of an AAPS system to ensure that it functions correctly in everyday life. - -##### How to install AAPS - -This section is the manual for building the AAPS. Strict adherence to the step-by-step instructions are required in order to successfully build the AAPS. Veuillez prendre votre temps. - -##### [Component Setup](https://androidaps.readthedocs.io/en/latest/Configuration/BG-Source.html) - -This explains how to properly integrate each of the various different separate component parts into AAPS, as well as how to set them up to work as seamlessly as possible together. All components are listed under the separate sections: CGM/FGM, xDrip Settings, Pumps, Phones, Nightscout setup, and Smartwatches. The sensor (BG) values and control of the insulin pump are particularly important information to understand. - -##### Configuration - -This explains how to set and configure your ‘Profile’, ‘Insulin’, ‘BG Source’, ‘Pump’, ‘Sensitivity Detection’, ‘APS’, ‘Loop’, ‘Treatments’. - -##### AAPS Usage - -This section provides a breakdown of the features provided by AAPS. - -##### [General Hints](https://androidaps.readthedocs.io/en/latest/Usage/Timezone-traveling.html) - -Useful tricks on how to tackle looping issues such as time zones, and daylight saving (i.e. Spring Forward/ - Fall Back). - -##### [AAPS](https://androidaps.readthedocs.io/en/latest/Getting-Started/Screenshots.html) for Children - -This is designed for parents or caregivers who want to build an AAPS for their child. It also explains the extra features necessary in order to support and safely control your child’s AAPS remotely.

The concepts in this section should be fully understood in order to competently use this feature. - -##### Résolution de problèmes - -This section contains links to help solve issues when building or using AAPS. - -##### Questions fréquentes - -This section addresses specific questions which tend to come up when building or using AAPS. - -##### [Glossaire](https://androidaps.readthedocs.io/en/latest/Getting-Started/Glossary.html) - -This contains a list of the acronyms (or short-term names) or defined terms developed specifically for AAP (for instance, the terms ‘ISF’ or ‘TT’ have special meanings in AAPS). - -##### [Where to go for help](https://androidaps.readthedocs.io/en/latest/Where-To-Go-For-Help/Background-reading.html)? - -This section is aimed to provide new users with links on resources in order to get help including accessing community support made up of both new and experienced users who can clarify questions, and resolve the usual pitfalls that come with AAPS. - -##### For Clinicians - -This is a section for the clinicians who have expressed interest in open source artificial pancreas technology such as AAPS, or for patients who want to share such information with their clinicians. | - -## what are we going to build? - -### An Android Phone Application - -At the core, AAPS is an android application running from a phone. You are going to build it from scratch by installing tools to download the sourcecode and build the actual application. - -### A reporting server NightScout (or Tidepool) - -In order to fully use AAPS properly you will want to setup a nightscout server. It is used to collect data from AAPS over time and possibly communicate to the application. It is required for parents who want to oversee their children AAPS sessions. It is also key to share data between clinicians and patients to perform analysis over time. - -## How long will it take? - -## Who might AAPS not be suitable for? - -## Where can I get help? - -## Requirements - -### medical - -### technical - -### personal - -### CGMs - -### Insulin Pump - -### Reporting (NS, Tidepool) \ No newline at end of file diff --git a/docs/CROWDIN/he/Configuration/EOFLOW.md b/docs/CROWDIN/he/Configuration/EOFLOW.md deleted file mode 100644 index 091c14d563b1..000000000000 --- a/docs/CROWDIN/he/Configuration/EOFLOW.md +++ /dev/null @@ -1,155 +0,0 @@ -# EOPatch2 Instruction Manual - -The patch requires the use of rapid-acting U-100 type insulin, such as NovoRapid or Humalog. Use a rapid-acting insulin that is suitable for you according to your doctor’s prescription and inject the prescribed dosage. - -The smallest injectable dose of insulin when using the patch is 0.05 U. The Profile BAS should therefore be set at a minimum value of 0.05 U/hr or more and an interval of 0.05 U/hr, as otherwise there may be an error between the estimated total infusion amount in the Profile and the actual infusion amount in the patch. Likewise, the bolus must also be set and infused with a minimum infusion volume of 0.05 U. - -## Pump Setup -1. On the AndroidAPS home screen, click the hamburger menu in the upper left corner and go to Config Builder. -1. Select 'EOPatch2' in the Pump section. -1. Press the Back key to return to the home screen. - -![Bild1](../../images/EOPatch/Bild1.png) ![Bild2](../../images/EOPatch/Bild2.png) - -## הגדרות -Select EOPATCH2 at the top of the home screen to go to the EOPATCH2 tab. - -Select the EOPatch2 Preferences menu by clicking the three dots in the upper right corner. - -The EOPatch2 Preferences menu offers a menu to set 3 types of notifications. - -### Low reservoir Alerts -A warning appears when the amount of insulin remaining in the reservoir reaches the set value or less while using the patch. It can be set from 10 to 50U in 5U increments. - -### Patch expiration Reminder -This is a reminder to notify you of the time remaining before the current patch expires. It can be set from 1 to 24 hours in 1 hour increments. The initial setting value is 4 hours. - -### Patch buzzer Reminder -This is a reminder function for injections other than basal injection. If you are using an (extended) bolus injection or a temporary basal injection, the patch will make a buzzer sound when the injection starts and when the injection is complete. The initial setting value is Off. - -![Bild3](../../images/EOPatch/Bild3.png) - -## Connecting the Patch - -### Move to patch connection screen - -Select EOPATCH2 at the top of the home screen and click the ACTIVATE PATCH button at the bottom left. - -![Bild4](../../images/EOPatch/Bild4.png) - -### Connecting the patch -Insert the syringe needle into the insulin inlet on the patch and then slowly push the piston to inject the insulin. When insulin is filled with more than 80U, the patch makes a booting sound (1 buzzer) and boots. After confirming the buzzer sound, click the START PAIRING button on the screen. - -[Warning] - -- Do not turn the needle action lever until instructed. It can cause serious problems during injection or safety checks otherwise. -- The amount of insulin that can be injected into the patch is 80~200U. If you inject less than 80U into the patch initially, the patch will not work. -- Take the insulin to be put into the patch from the refrigerator and leave it at room temperature for 15 to 30 minutes beforehand. The temperature of the insulin to be injected must be at least 10°C. - -![Bild5](../../images/EOPatch/Bild5.png) - -### patch pairing -The Patch pairing screen will be displayed, and pairing will be attempted automatically. If communication is successful, the Bluetooth pairing request notification appears. Click OK and when the Bluetooth pairing request notification appears a second time with the authentication code, select OK again. - -[Warning] - -- For pairing, the patch and the smartphone must be located within 30 cm of each other. -- After the patch booting is completed, the patch will beep every 3 minutes until the pairing is complete. -- After booting the patch, the patch application must be completed via the app within 60 minutes. If the application cannot be completed within 60 minutes, the patch should be discarded. - -![Bild6](../../images/EOPatch/Bild6.png) ![Bild7](../../images/EOPatch/Bild7.png) ![Bild8](../../images/EOPatch/Bild8.png) - - -### patch preparation -After removing the adhesive tape of the patch, check if the needle is sticking out. If there are no problems with the patch, click NEXT. - -![Bild9](../../images/EOPatch/Bild9.png) - -### Patch attachment -Insulin should be injected in a spot with subcutaneous fat but few nerves or blood vessels, so it is recommended to use the abdomen, arm, or thigh for the patch attachment site. Choose a patch attachment site and apply the patch after disinfecting the location. - -[Warning] - -- Make sure to straighten the side of the patch tape attached to the body evenly, so that the patch adheres completely to the skin. -- If the patch does not stick completely, air may enter between the patch and the skin, which can weaken the adhesive strength and waterproof effect of the patch. - -![Bild10](../../images/EOPatch/Bild10.png) - -### Safety Check -When patching is complete, touch Start Safety Check. When the safety check is completed, the patch will beep once. - -[Warning] - -- For safe use, do not turn the needle action lever until the safety check has been completed. - -![Bild11](../../images/EOPatch/Bild11.png) ![Bild12](../../images/EOPatch/Bild12.png) - - -### Inserting the needle -The needle is inserted by holding around the patch and turning the needle action lever more than 100° in the upward direction of the lever. There is a buzzer sound when the needle is inserted correctly. Turn the needle action lever further clockwise to release the lever. Click NEXT. - -[Caution] - -- If you go to the next step without the buzzer sounding, a needle insertion error warning will appear. - -## Discarding the patch -Patches must be replaced in the case of low insulin levels, usage expiration, and defects. The recommended usage period for each patch is 84 hours after booting the patch. - -### Discarding the patch -Select EOPATCH2 at the top of the home screen and click the DISCARD/CHANGE PATCH button at the bottom. On the next screen, click the DISCARD PATCH button. A dialog box appears to confirm once more and if you select the DISCARD PATCH button, the disposal is completed. - -![Bild13](../../images/EOPatch/Bild13.png) ![Bild14](../../images/EOPatch/Bild14.png) ![Bild15](../../images/EOPatch/Bild15.png) ![Bild16](../../images/EOPatch/Bild16.png) - -## הפסקה וחידוש אספקת האינסולין -Suspending insulin delivery also cancels both extended bolus and temporary basal. When resuming insulin delivery, the canceled extended bolus and temporary basal will not be resumed. And when insulin delivery is suspended, the patch will give a sound every 15 minutes. - -### Suspending insulin delivery -Select EOPATCH2 at the top of the home screen and click the SUSPEND button at the bottom right. When you select CONFIRM in the confirmation box, a time selection box appears. If you select the CONFIRM button after selecting the time, the insulin delivery will be suspended for the set amount of time. - -![Bild17](../../images/EOPatch/Bild17.png) ![Bild18](../../images/EOPatch/Bild18.png) ![Bild19](../../images/EOPatch/Bild19.png) - - -### Resuming insulin delivery -Select EOPATCH2 at the top of the home screen and click the RESUME button at the bottom right. Insulin delivery will resume by selecting CONFIRM in the confirmation dialog box. - -![Bild20](../../images/EOPatch/Bild20.png) ![Bild21](../../images/EOPatch/Bild21.png) - -## Alarms/Warnings - -### Alarm - -Alarms are issued for emergency situations of the highest priority and require immediate action. The alarm signal does not disappear or time out until it is acknowledged. An alarm occurs when there is a problem with the patch being used, so there may be cases where the patch in use needs to be discarded and replaced with a new patch. The warning is displayed as a dialog box and switching to another screen is not possible until processing is completed. - -![Bild22](../../images/EOPatch/Bild22.png) ![Bild23](../../images/EOPatch/Bild23.png) - -The different types of alarms are explained below. - -| Alarms | Explanation | -| -------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| Empty reservoir | Occurs when the patch’s reservoir runs out of insulin. | -| Patch expired | Occurs when the patch usage time has expired, and no further insulin injections are possible. | -| Occlusion | Occurs when it appears that the patch's insulin inlet is clogged. | -| Power on self-test failure | Occurs when the patch finds an unexpected error during the post-boot self-test process. | -| Inappropriate temperature | Occurs when the patch is outside the normal operating temperature range during patch application and use. To deal with this alarm, move the patch to an appropriate operating temperature (4.4 to 37°C) condition. | -| Needle insertion Error | Occurs when needle insertion is not normal during the patch application process. Check that the needle insertion edge of the patch and the needle activation button are in a straight line. | -| Patch battery Error | Occurs just before the patch’s internal battery runs out and powers off. | -| Patch activation Error | Occurs when the app fails to complete the patching process within 60 minutes after the patch is booted. | -| Patch Error | Occurs when the patch encounters an unexpected error while applying and using the patch. | - -### Warning - -A warning occurs in a medium or low-priority situation. When a warning occurs, it is displayed as a notification in the Overview screen. - -![Bild24](../../images/EOPatch/Bild24.png) - -The different types of warnings are explained below. - -| Warnings | Explanation | -| ---------------------------- | ------------------------------------------------------------------------------------------------------------------------------------- | -| End of insulin suspend | Occurs when the time set by the user has elapsed after the insulin infusion suspension has been completed. | -| Low reservoir | Occurs when the remaining amount of insulin in the patch is below the set amount. | -| Patch operating life expired | Occurs when the patch usage period is over. | -| Patch will expire soon | Occurs 1 hour before the patch must be discarded. | -| Incomplete Patch activation | Occurs when more than 3 minutes have elapsed due to an interruption during patch application in the stage after pairing is completed. | -| Patch battery low | Occurs when the patch's battery is low. | - diff --git a/docs/CROWDIN/he/Getting-Started/ClosedLoop.md b/docs/CROWDIN/he/Getting-Started/ClosedLoop.md deleted file mode 100644 index ecd01e4fbf5f..000000000000 --- a/docs/CROWDIN/he/Getting-Started/ClosedLoop.md +++ /dev/null @@ -1,55 +0,0 @@ -# מהי מערכת לולאה סגורה (לופ סגור)? - -![AAPS is like an autopilot](../images/autopilot.png) - -מערכת לבלב מלאכותי בלולאה סגורה משלבת רכיבים שונים על מנת להקל את ניהול הסוכרת. In her great book [Automated Insulin Delivery](https://www.artificialpancreasbook.com/) Dana M. Lewis, one of the founders of the open source closed loop movement, calls it an ["autopilot for your diabetes"](https://www.artificialpancreasbook.com/3.-getting-started-with-your-aps). מה זה אומר? - -**Autopilot in an aircraft** - -הטייס האוטומטי אינו עושה את העבודה כולה ואינו נותן אפשרות לטייס לישון לאורך כל הטיסה. אך זה מקל על עבודת הטייסים. זה משחרר אותם מהנטל של ניטור קבוע של מצב המטוס. כך מתאפשר לטייס להתרכז בניטור המרחב האווירי ובבקרה על תפקודי הטייס האוטומטי. - -הטייס האוטומטי מקבל אותות מחיישנים שונים, מחשב אותם יחד עם דרישות הטייס ולאחר מכן מבצע את ההתאמות הנדרשות. הטייס כבר לא צריך לדאוג מכיוונונים תכופים. - -**Closed Loop System** - -אותו דבר לגבי מערכת לולאה סגורה של לבלב מלאכותי. המערכת לא עושה את כל העבודה, עליכם עדיין יש חובה לדאוג לסוכרת. מערכת לולאה סגורה משלבת את נתוני חיישני הסוכר עם מפרטי ניהול הסוכרת שלכם כגון המינון הבזאלי, יחס התיקון ויחס הפחמימות. מכאן הוא מחשב הצעות טיפול ומיישם התאמות קטנות וקבועות אלה על מנת לשמור על איזון הסוכרת בטווח המטרה ולהקל עליך את הטיפול. זה משאיר יותר זמן לחיים "ליד" הסוכרת. - -בדיוק כפי שאינכם רוצים לעלות על מטוס שבו תמיד הטייס האוטומטי טס ללא פיקוח אנושי, מערכת לולאה סגורה עוזרת בניהול הסוכרת, אך תמיד זקוקה לתמיכתכם! **Even with a closed loop you can't just forget your diabetes!** - -בדיוק כפי שהטייס האוטומטי תלוי בערכי החיישן וגם בדרישות הטייס, מערכת לולאה סגורה זקוקה לקלט מתאים כגון ערכי מינון בזאלי, יחס תיקון ויחס פחמימות כדי לאזן אתכם בהצלחה. - -## מערכות לבלב מלאכותיות בלולאה סגורה בקוד פתוח - -כיום קיימות שלוש מערכות קוד פתוח עיקריות: - -### AndroidAPS (AAPS) - -AAPS is described in detail in [this documentation](./WhatisAndroidAPS.html). המערכת משתמשת בסמארטפון אנדרואיד לחישוב ולשליטה על משאבת האינסולין. It is in strong collaboration with OpenAPS (i.e. they share algorithms). - -Compatible [pumps](../Hardware/pumps.md) are: - -- [DanaR](../Configuration/DanaR-Insulin-Pump.md) / [DanaRS & Dana-i](../Configuration/DanaRS-Insulin-Pump.html) -- [Accu-Chek Combo](../Configuration/Accu-Chek-Combo-Pump.md) -- [Accu-Chek Insight](../Configuration/Accu-Chek-Insight-Pump.md) -- [Diaconn G8](../Configuration/DiaconnG8.md) -- [Omnipod DASH](../Configuration/OmnipodDASH.md) -- [Omnipod Eros](../Configuration/OmnipodEros.md) -- some old [Medtronic pumps](../Configuration/MedtronicPump.md) - -### OpenAPS - -[OpenAPS](https://openaps.readthedocs.io) was the first Open Source Closed Loop System. היא משתמשת במחשבים זעירים כמו Raspberry Pi ו-Intel Edison. - -משאבות תואמות: - -- some old Medtronic pumps - -### Loop ל-iOS - -[Loop for iOS](https://loopkit.github.io/loopdocs/) is the Open Source Closed Loop System to be used with Apple iPhones. - -משאבות תואמות: - -- Omnipod DASH -- Omnipod Eros -- some old Medtronic pumps diff --git a/docs/CROWDIN/he/Getting-Started/Safety-first.md b/docs/CROWDIN/he/Getting-Started/Safety-first.md deleted file mode 100644 index f89eec499ed7..000000000000 --- a/docs/CROWDIN/he/Getting-Started/Safety-first.md +++ /dev/null @@ -1,41 +0,0 @@ -# בטיחות מעל הכול - -**When you decide to build your own artificial pancreas, it's always important to think about security and safety, and to understand the impact of all your actions** - -## כללי - -- AAPS is a just a tool to help you manage diabetes, it is not a fully automated system you can install and forget! -- Do not assume that AAPS will never make mistakes. This device is taking control of your insulin delivery: Watch it all the time, understand how it works, and learn how to interpret its actions. -- Remember that, once paired, the phone can instruct the pump to do anything. Only use this phone for AAPS and, if being used by a child, essential communications. Do not install unnecessary apps or games (!!!) which could introduce malware such as trojans, viruses, or bots that could interfere with your system. -- Install all security updates provided by your phone manufacturer and Google. -- You might also need to change your diabetes habits as you change your therapy by using a closed loop system. I.e. some people report, they need less hypo treatments as AAPS has already reduced insulin. - -## תקשורת SMS - -- AAPS allows you to control a child's phone remotely via text message. If you enable this SMS Communicator, always remember that the phone set up to give remote commands could be stolen. So always protect it at least by a PIN code. -- AAPS will also inform you by text message if your remote commands, such as a bolus or a profile change, have been carried out. It is advisable to set this up so that confirmation texts are sent to at least two different phone numbers in case one of the receiving phones is stolen. - -(Safety-first-aaps-can-also-be-used-by-blind-people)= -## AAPS can also be used by blind people - -On Android devices TalkBack is part of the operating system. It is a program for screen orientation via voice output. With TalkBack you can operate your smartphone as well as AAPS blind. - -We users create the AAPS app ourselves with Android Studio. Many use Microsoft Windows for this purpose, where there is the Screenreader analogous to TalkBack. Since Android Studio is a Java application, the "Java Access Bridge" component must be enabled in the Control Panel. Otherwise, the screen reader of the PC will not speak in Android Studio. - -To do this, please proceed as follows: - -- Press WINDOWSTASTE and enter "Control Panel" in the search field, open with Enter. It opens: "All Control Panel Items". -- Press the letter C to get to "Center for Ease of Use", open with Enter. -- Then open "Use computer without a screen" with Enter. -- There, at the bottom, you will find the checkbox "Enable Java Access Bridge", select it. -- Done, just close the window! The screen reader should work now. - -```{note} -**IMPORTANT SAFETY NOTICE** - -The foundation of AAPS safety features discussed in this documentation is built on the safety features of the hardware used to build your system. חשוב מאוד שתשתמשו רק במשאבת אינסולין שנבדקה ואושרה ע"י ה-FDA או CE ובחיישן CGM לסגירת לולאת מינון אינסולין אוטומטית. שינויים בחומרה או בתוכנה ברכיבים אלה עלולים לגרום למינון בלתי צפוי של אינסולין, ולגרום לסיכון משמעותי למשתמש. If you find or get offered broken, modified or self-made insulin pumps or CGM receivers, *do not use* these for creating an AAPS system. - -Additionally, it is equally important to only use original supplies such as inserters, cannulas and insulin containers approved by the manufacturer for use with your pump or CGM. Using untested or modified supplies can cause CGM inaccuracy and insulin dosing errors. Insulin is highly dangerous when misdosed - please do not play with your life by hacking with your supplies. - -Last not least, you must not take SGLT-2 inhibitors (gliflozins) as they incalculably lower blood sugar levels. The combination with a system that lowers basal rates in order to increase BG is especially dangerous as due to the gliflozin this rise in BG might not happen and a dangerous state of lack of insulin can happen. -``` diff --git a/docs/CROWDIN/he/Getting-Started/Sample-Setup.md b/docs/CROWDIN/he/Getting-Started/Sample-Setup.md deleted file mode 100644 index 2da9e4bf5a38..000000000000 --- a/docs/CROWDIN/he/Getting-Started/Sample-Setup.md +++ /dev/null @@ -1,151 +0,0 @@ -# Sample setup: Samsung S7, Dana RS, Dexcom G6 and Sony Smartwatch - -![Sample Setup](../images/SampleSetup.png) - -## Description - -In this setup, the Samsung Galaxy S7 smartphone is used as control center of the loop. The slightly modified Dexcom App reads glucose values from the Dexcom G6 CGM. AndroidAPS is used to control the Dana RS insulin pump from Korean manufacturer SOOIL via bluetooth. Further devices are not required. - -As the Dexcom App only offers limited alarm options the open source app xDrip+ is used to define not only high and low alarms but also additional alarms according to individual requirements. - -Optionally an Android wear smartwatch can be used (in this sample setup the Sony Smartwatch 3 (SWR50)) to display glucose and AndroidAPS values on your wrist. The watch can even be used to control AndroidAPS (i.e. discreetly set a meal bolus). - -The system works offline. This means there is no need for a data connection from the smartphone to the Internet for operation. - -Nevertheless, the data is automatically uploaded to Nightscout "in the cloud" when a data connection is established. By doing so you can provide comprehensive reports for the doctor's visit or share the current values with family members at any time. It is also possible to send data to Nightscout only when using a (predefined) Wi-Fi connection in order to profit from the different Nightscout reports. - -## Required components - -1. Samsung Galaxy S7 - - * Alternatives: see [list of tested phones and watches](https://docs.google.com/spreadsheets/d/1gZAsN6f0gv6tkgy9EBsYl0BQNhna0RDqA9QGycAqCQc/edit) for AndroidAPS - -2. [DanaRS](http://www.sooil.com/eng/product/) - - * Alternatives: - * [Accu-Chek Combo](../Configuration/Accu-Chek-Combo-Pump.md) - * [Accu-Chek Insight](../Configuration/Accu-Chek-Insight-Pump.md) - * [DanaR](../Configuration/DanaR-Insulin-Pump.md) - * [Some old Medtronic pumps (additionally needed: RileyLink/Gnarl hardware, Android Phone with bluetooth low energy / BLE-chipset)](../Configuration/MedtronicPump.md) - * Other pumps might be available in the future, see [future possible pump drivers](Future-possible-Pump-Drivers.md) for details. - -3. [Dexcom G6](https://dexcom.com) - - * Alternatives: see list of possible [BG sources](../Configuration/BG-Source.md) - -4. Optional: Sony Smartwatch 3 (SWR50) - - * Alternatives: All [watches with Google Wear OS](https://wearos.google.com/intl/de_de/#find-your-watch) should work fine, for details see [list of tested phones and watches](https://docs.google.com/spreadsheets/d/1gZAsN6f0gv6tkgy9EBsYl0BQNhna0RDqA9QGycAqCQc/edit) for AndroidAPS (OS must be Android Wear) - -## Nightscout setup - -See detailed [Nightscout setup](../Installing-AndroidAPS/Nightscout.md) - -## Computer setup - -To be able to create an Android app from the freely available AAPS open source code you need Android Studio on your computer or notebook (Windows, Mac, Linux). A detailed instruction can be found at [building the APK](../Installing-AndroidAPS/Building-APK.md). - -Please be patient when installing Android Studio as the software downloads a lot of additional data once installed on your computer. - -## Smartphone setup - -![Smartphone](../images/SampleSetupSmartphone.png) - -### Check smartphone firmware - -* Menu > Settings > Phone info > Software info: At least "Android-Version 8.0" (successfully tested up to Android version 8.0.0 Oreo - Samsung Experience Version 9.0) -* For firmware update: menu > Preferences > software update - -### Allow installation from unknown sources - -Menu > Settings > Device security > Unknown sources > slider to right side (= active) - -For security reasons this setting should be set back to inactive once the installation of all apps described here has been completed. - -### Enable Bluetooth - -1. Menu > Settings > Connections > Bluetooth > slider to right side (= active) -2. Menu > Settings > Connections > Location > slider to right side (= active) - -Location services ("GPS") must be activated in order for Bluetooth to work properly. - -### Install Dexcom App (modified version) - -![Dexcom App patched](../images/SampleSetupDexApp.png) - -The original Dexcom app from the Google Play Store will not work because it does not broadcast the values to other apps. Therefore, a version slightly modified by the community is required. Only this modified Dexcom app can communicate with AAPS. Additionally the modified Dexcom App can be used with all Android smartphones not only the ones in [Dexcom's compatibility list](https://www.dexcom.com/dexcom-international-compatibility). - -To do this perform the following steps on your smartphone: - -1. If the original Dexcom app is already installed: - * Stop sensor - * Uninstall app via Menu > Settings > Apps > Dexcom G6 Mobile > Uninstall -2. Download and install the [BYODA Dexcom ap](../Hardware/DexcomG6.md#if-using-g6-with-build-your-own-dexcom-app) -3. Start modified Dexcom G6 app, activate/calibrate the sensor according to the given instructions and wait until the warm-up phase is finished. -4. Once the modified Dexcom app shows actual glucose value, setup the warnings (hamburger menu on top left side of the screen) as follows: - * Urgent low `55mg/dl` / `3.1mmol/l` (cannot be disabled) - * Low `OFF` - * High `OFF` - * Rise rate `OFF` - * Fall rate `OFF` - * Signal loss `OFF` - -## Install AndroidAPS - -1. Follow the instructions to [build the APK](../Installing-AndroidAPS/Building-APK.md#generate-signed-apk) -2. [Transfer](../Installing-AndroidAPS/Building-APK.md#transfer-apk-to-smartphone) the generated APK to your phone -3. [Configure AndroidAPS](../Configuration/Config-Builder.md) according to your needs using the setup assistant or manually -4. In this sample setup we used (among others) - -* BG source: `Dexcom G6 App (patched)` -- click cock-wheel and activate `Upload BG data to NS` and `Send BG data to xDrip+` (see [BG source](../Configuration/BG-Source.md)) - -![G5 Settings](../images/SampleSetupG5Settings.png) - -* NS Client activated (see [Nightscout setup](../Installing-AndroidAPS/Nightscout.md)) - -## Install xDrip+ - -xDrip+ is another mature open source app that offers countless possibilities. In this setup, contrary to what the developers first wrote the app for, xDrip+ is not used to collect glucose data from the Dexcom G6, but only to output alarms and to display the current glucose value including the curve on the Android home screen in the widget. With xDrip+ the alarms can be set much more individually than with the Dexcom software, AAPS or Nightscout (no limitation in the selection of sounds, different alarms depending on day/night time etc.). - -1. Download the latest stable APK version of xDrip+ with your smartphone - not the version from the Google Play Store! -2. Install xDrip+ by selecting the downloaded APK file. -3. Start xDrip+ and make the following settings (hamburger menu at top left) - * Settings > Alarms and Alerts > Glucose Level Alert List > Create Alerts (high and low) according to your needs. - * The existing alarms can be changed with a long press on the alarm. - * Settings > Alarms and Alerts > Calibration Alerts: disabled (reminded via the modified Dexcom app) - * Settings > Hardware Data Source > 640G/EverSense - * Settings > Inter-app settings > Accept Calibrations > `ON` - * Menu > Start sensor (is only "pro forma" and has nothing to do with the running G6 sensor. This is necessary otherwise an error message will appear regularly.) - -For more information about xDrip+, see here [BG source page](../Configuration/BG-Source.md). - -### Example of an alarm setup - -The "Urgent low alarm" (below 55 mg/dl resp. 3,1 mmol) is a standard alarm from the modified Dexcom app that cannot be disabled. - -![xDrip alarms](../images/SampleSetupxDripWarning.png) - -Tip for meetings / church visits / cinema etc..: - -If "Do not disturb" mode is activated in the Samsung Galaxy S7 (Menu > Settings > Sounds and vibration > Do not disturb: slider to right side (= active)), the phone only vibrates during urgent low alarm and does not issue an acoustic warning. For the other alarms set up via xDrip+ you can select whether the silent mode should be ignored (acoustic sound played) or not. - -## Disable power saving option - -On your Samsung Galaxy S7 go to Menu > Settings > Device Maintenance > Battery > Unmonitored Apps > + Add apps: Select the apps AndroidAPS, Dexcom G6 Mobile, xDrip+ and Android Wear (if smartwatch is used) one after the other - -## Optional: Setup Sony Smartwatch 3 (SWR50) - -With an Android Wear smartwatch life with diabetes can be made even more inconspicuous. The watch can be used to display the current glucose level, the status of the loop etc. on the wrist. The watch can even be used to control AndroidAPS (i.e. discreetly set a meal bolus). To do this, double tap the CGM value of the AAPSv2 watchface. The SWR50 usually runs for a full day until the battery needs to be recharged (same charger as the Samsung Galaxy S7: microUSB). - -![Smartwatch](../images/SampleSetupSmartwatch.png) - -Details about the information displayed on the watchface can be found [here](../Configuration/Watchfaces.md). - -* Install the app "Android Wear" on your smartphone via the Google Play Store and connect the smartwatch according to the instructions there. -* In AAPS choose hamburger menu (top left corner) > Config Builder > General (at the bottom of the list) > Wear > activate on left side, click cock wheel > Wear settings and activate `Controls from Watch` -* On your smartwatch: Long press display to change watchface and select `AAPSv2` -* If necessary restart both devices once. - -## Pump setup - -see [Dana RS pump](../Configuration/DanaRS-Insulin-Pump.md) \ No newline at end of file diff --git a/docs/CROWDIN/he/Getting-Started/WhatisAndroidAPS.md b/docs/CROWDIN/he/Getting-Started/WhatisAndroidAPS.md deleted file mode 100644 index cb5e7f1b49e9..000000000000 --- a/docs/CROWDIN/he/Getting-Started/WhatisAndroidAPS.md +++ /dev/null @@ -1,42 +0,0 @@ -# What is a closed loop system with AAPS? - -AAPS is an app that acts as an artificial pancreas system (APS) on an Android smartphone. מהי מערכת לבלב מלאכותי? זוהי תוכנה שמטרתה לעשות את מה שעושה לבלב טבעי: לשמור על רמות הסוכר בדם בטווח בריא באופן אוטומטי. - -מערכת לבלב מלאכותי לא יכולה לעשות את העבודה כמו לבלב ביולוגי, אבל יכולה להקל על ניהול סוכרת מסוג 1 באמצעות מכשירים זמינים מסחרית ותוכנה פשוטה ובטוחה. Those devices include a continuous glucose monitor (CGM) to tell AAPS about your blood sugar levels and an insulin pump which AAPS controls to deliver appropriate doses of insulin. האפליקציה מתקשרת עם מכשירים אלה באמצעות בלוטות'. היא מבצעת את חישובי המינון שלה באמצעות אלגוריתם, או מערכת כללים, שפותחה עבור מערכת לבלב מלאכותית אחרת, בשם OpenAPS, לה אלפי משתמשים וצברה מיליוני שעות שימוש. - -A note of caution: AAPS is not regulated by any medical authority in any country. Using AAPS is essentially carrying out a medical experiment on yourself. הקמת המערכת דורשת נחישות ויכולת טכנית. אם עדיין אין לכם את הידע הטכני בהתחלה, עד סיום התהליך אתם תרכשו אותו. את כל המידע הדרוש ניתן למצוא במסמכים באתר זה, במקומות אחרים באינטרנט, או אצל אחרים שכבר עשו זאת -- מומלץ לשאול בקבוצות פייסבוק או בפורומים אחרים. Many people have successfully built AAPS and are now using it entirely safely, but it is essential that every user: - -- Builds the system themselves so that they thoroughly understand how it works -- Adjusts its individual dosage algorithm with his or her diabetes team to work nearly perfect -- Maintains and monitors the system to ensure it is working properly - -```{note} -**Disclaimer and Warning** - -- All information, thought, and code described here is intended for informational and educational purposes only. Nightscout לא עושה כרגע ניסיון לתאימות לפרטיות HIPAA. - Use Nightscout and AAPS at your own risk, and do not use the information or code to make medical decisions. -- Use of code from github.com is without warranty or formal support of any kind. אנא עיינו ברישיון של מאגר זה לפרטים. - -- All product and company names, trademarks, servicemarks, registered trademarks, and registered servicemarks are the property of their respective holders. השימוש בהם הוא למטרות מידע ואינו מרמז על כל זיקה או אישור על ידם. - - -Please note - this project has no association with and is not endorsed by: [SOOIL](http://www.sooil.com/eng/), [Dexcom](https://www.dexcom.com/), [Accu-Chek, Roche Diabetes Care](https://www.accu-chek.com/), [Insulet](https://www.insulet.com/) or [Medtronic](https://www.medtronic.com/). -``` - -אם אתם מוכנים לאתגר, המשיכו לקרוא. - -## Primary goals behind AAPS - -- An app with safety built in. To read about the safety features of the algorithms, known as oref0 and oref1, click here () -- An all-in-one app for managing type 1 diabetes with an artificial pancreas and Nightscout -- An app to which users can easily add or remove modules as needed -- An app with different versions for specific locations and languages. -- An app which can be used in open- and closed-loop mode -- An app that is totally transparent: users can input parameters, see results, and make the final decision -- An app which is independent of particular pump drivers and contains a "virtual pump" so users can safely experiment before using it on themselves -- An app closely integrated with Nightscout -- An app in which the user is in control of safety constraints - -## איך מתחילים? - -כמובן, כל התוכן הזה כאן הוא מאוד חשוב, אך יכול לבלבל בהתחלה. A good orientation is given by the [Module Overview](../Module/module.md) and the [Objectives](../Usage/Objectives.html). diff --git a/docs/CROWDIN/he/Hardware/DexcomG4.md b/docs/CROWDIN/he/Hardware/DexcomG4.md deleted file mode 100644 index 3ac2b2b96f4b..000000000000 --- a/docs/CROWDIN/he/Hardware/DexcomG4.md +++ /dev/null @@ -1,6 +0,0 @@ -# Dexcom G4 - -## If using G4 with OTG cable ('traditional' Nightscout) -- If not already set up then download Nightscout Uploader app from the Play Store and follow instructions on [Nightscout](https://nightscout.github.io/). -- In AAPS Preferences enter your Nightscout website and API secret. -- Select NSClient in ConfigBuilder (setting in AAPS). diff --git a/docs/CROWDIN/he/Hardware/Smartwatch.md b/docs/CROWDIN/he/Hardware/Smartwatch.md deleted file mode 100644 index a1dae1bcb03d..000000000000 --- a/docs/CROWDIN/he/Hardware/Smartwatch.md +++ /dev/null @@ -1,10 +0,0 @@ -# שעונים חכמים - -שעונים חכמים הינם אופציונאליים, אך שימושיים מאוד עבור חלק מהמשתמשים. לפרטים נוספים: - -- [רשימת טלפונים ושעונים חכמים שנבדקו](../Getting-Started/Phones.md) -- [תצוגות שעונים ב-Wear OS](../Configuration/Watchfaces.md) -- [פתרון בעיות בשעון Sony Smartwatch SW 3](../Usage/SonySW3.md) - -## Instructions for Building the AAPS Wear APK for Wear OS -https://androidaps.readthedocs.io/en/latest/remote-control.html#building-the-aaps-wear-apk diff --git a/docs/CROWDIN/he/Installing-AndroidAPS/Building-APK.md b/docs/CROWDIN/he/Installing-AndroidAPS/Building-APK.md deleted file mode 100644 index db2cf4b40080..000000000000 --- a/docs/CROWDIN/he/Installing-AndroidAPS/Building-APK.md +++ /dev/null @@ -1,369 +0,0 @@ -# בניית קובץ ה-APK - -## בנייה עצמית במקום הורדה - -**AAPS is not available as download due to regulation for medical devices. בנייה עצמית של היישום לשימוש אישי הינה חוקית אך אסור לתת את היישום לאחרים! ראו [שאלות נפוצות](../Getting-Started/FAQ.md) לפרטים.** - -## הערות חשובות - -* Please use **[Android Studio Giraffe" (2022.3.1)](https://developer.android.com/studio/)** or newer to build the apk. -* [Windows 32-bit systems](troubleshooting_androidstudio-unable-to-start-daemon-process) are not supported by Android Studio - -(Building-APK-recommended-specification-of-computer-for-building-apk-file)= - -## מפרט מומלץ של מחשב לבניית קובץ apk - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
מערכת הפעלה (64 ביט בלבד)חלונות 8 ומעלהMac OS 10.14 ומעלהכל לינוקס שתומך ב-Gnome, KDE, או Unity DE; GNU C Library 2.31 או מאוחר יותר

מעבד (64 ביט בלבד)

ארכיטקטורת מעבד x86_64; דור שני של Intel Core ומעלה, או מעבד AMD עם תמיכה ב-
Windows Hypervisor		מעבדים מבוססי ARM; דור שני של Intel Core ומעלה תמיכה ב-
Windows Hypervisor		ארכיטקטורת מעבד x86_64; דור שני של Intel Core ומעלה, או מעבד AMD עם תמיכה בווירטואליזציה של AMD (AMD-V) ו-SSSE3

RAM

8GB ומעלה

דיסק קשיח

לפחות 30GB פנויים. מומלץ SSD.

רזולוציה

לפחות 1280X800

אינטרנט

פס רחב

- -Please keep in mind that both **64 bit CPU and 64 bit OS are mandatory condition.** If your system DOES NOT meet this condition, you have to change affected hardware or software or the whole system. **מומלץ מאוד להשתמש ב-SSD (Solid State Disk) במקום HDD (כונן קשיח) כי זמן בניית קובץ ה-APK של התקנת AAPS יתקצר משמעותית.** זוהי המלצה ולא דרישה. עם זאת, אין מניעה להשתמש בדיסק קשיח כאשר אתם בונים קובץ apk אך לשים לב שתהליך הבנייה עשוי להימשך זמן רב, אם כי לאחר התחלתה, תוכלו להשאיר אותה פועלת ללא השגחה עד להשלמתה. - -* * * - -### מאמר זה מחולק לשני חלקים. - -* בחלק הסקירה יש הסבר על השלבים הדרושים לבניית קובץ ה-APK. -* בחלק המדריך צעד אחר צעד תמצאו את צילומי המסך של תהליך שלם. מכיוון שהגרסאות של Android Studio - סביבת פיתוח התוכנה בה נשתמש לבניית ה-APK - ישתנו מהר מאוד זה לא יהיה זהה להתקנה שלך אבל זה אמור לתת לך נקודת התחלה טובה. Android Studio פועל גם על Windows, Mac OS X ו-Linux וייתכנו הבדלים קטנים בהיבטים מסוימים בין כל פלטפורמה. If you find that something important is wrong or missing, please inform the facebook group "AAPS users" or in the Discord chat [Android APS](https://discord.gg/4fQUWHZ4Mw) so that we can have a look at this. - -## סקירה כללית - -באופן כללי, השלבים של בניית קובץ ה-APK הם: - -1. [התקנת Git](../Installing-AndroidAPS/git-install.md) -2. [התקנת Android Studio](Building-APK-install-android-studio) -3. [הגדרת נתיב של Git בהעדפות Android Studio](Building-APK-set-git-path-in-preferences) -4. [Download AAPS code](Building-APK-download-AAPS-code) -5. [הורדת Android SDK](Building-APK-download-android-sdk) -6. [בניית האפליקציה](Building-APK-generate-signed-apk) (יצירת apk חתום) -7. [העברת קובץ ה-apk לטלפון](Building-APK-transfer-apk-to-smartphone) -8. [הגדרת זיהוי מקלט אם משתמשים ב-xDrip](xdrip-identify-receiver) - -## מדריך שלב אחר שלב - -תיאור מפורט של השלבים הדרושים לבניית קובץ ה-APK. - -## התקינו git (אם לא מותקן כבר) - -עקבו אחר המדריך ב[דף התקנת של git](../Installing-AndroidAPS/git-install.md). - -(Building-APK-install-android-studio)= - -## התקנת Android Studio - -צילומי המסך הבאים נלקחו מגרסת Android Studio Arctic Fox | 2020.3.1. המסכים עשויים להשתנות בגרסאות עתידיות של Android Studio. אף על פי כן, אתם צפויים להיות מסוגלים למצוא את דרככם. אפשר [לקבל עזרה מהקהילה](../Where-To-Go-For-Help/Connect-with-other-users.md). - -אחד הדברים החשובים ביותר בעת התקנת Android Studio: **היו סבלניים!** במהלך ההתקנה וההגדרה Android Studio מוריד הרבה דברים וזה לוקח זמן. - -הורידו את [Android Studio מכאן](https://developer.android.com/studio/install.html) והתקינו אותו במחשבכם. - -בפעם הראשונה יופיע אשף ההתקנה: - -בחרו "Do not import settings" מכיוון שלא השתמשתם בו בעבר. - -![Do not import settings](../images/studioSetup/01_ImportSettings.png) - -החליטו אם ברצונכם לשתף נתונים עם Google או לא. - -![שיתוף מידע עם גוגל](../images/studioSetup/02_DataSharing.png) - -במסך הבא לחץ על "Next". - -![מסך הכניסה](../images/studioSetup/03_Welcome.png) - -בחר בהתקנה "Standard" ולחצו על "Next". - -![התקנה סטנדרטית](../images/studioSetup/04_InstallType.png) - -בחרו את ערכת הנושא עבור ממשק המשתמש לנוחיותכם. (במדריך זה השתמשנו ב"Light".) לאחר מכן לחצו על "Next". - -> ***הערה:*** זוהי רק סכמת צבעים. תוכלו לבחור את מה שתרצו (לדוגמה "דרקולה" שהוא צבע כהה). לבחירה זו אין השפעה על בניית ה-APK אך צילומי המסך הבאים עשויים להיראות אחרת. - -![צבעי ממשק משתמש](../images/studioSetup/05_UITheme.png) - -Click "Next" on the "Verify Settings" dialog. - -![אימות הגדרות](../images/studioSetup/06_Overview.png) - -Click on all three license agreement parts and select "Agree". When you have agreed to all, the "Finish" button will be enabled and you can "Finish". - - ![Agree license agreements](../images/studioSetup/07_LicenseAgreement.png) - - -Wait while Android Studio downloads additional components and be patient. Once everything is downloaded button "Finish" turns blue. Click the button now. - -![Downloading components](../images/studioSetup/08_Downloading.png) - -(Building-APK-download-AAPS-code)= - -## Download AAPS code - -* On the Android Studio welcome screen select "Projects" (1) on the left and then "Get from VCS" (2). - - ![Android Studio wizard](../images/studioSetup/20_ProjectVCS.png) - - * If you already opened Android Studio and do not see the welcome screen anymore select File (1) > New (2) > Project from Version Control... (3) - - ![Check out project from version control within Android Studio](../images/AndroidStudio_FileNew.PNG) - - * We will now tell Android Studio were to get the code from: - - * Make sure you have selected "Repository URL" on the left (1). - - * Check if "Git" is selected as version control (2). - * Copy and paste the URL ```https://github.com/nightscout/AndroidAPS``` to the main AAPS repository into the URL textbox (3). - * Choose the directory where you want to save the cloned code (4). - - ![Clone Git](../images/studioSetup/21_CloneURL.png) - -* Click button "Clone" (5). - - ![Clone repository](../images/studioSetup/22_Cloning.png) - -* Do not click "Background" while repository is cloned! - -* After the repository is cloned successfully, Android Studio will open the cloned project. - -* You will be asked whether you want to trust the project. Click on "Trust project"! - - ![Trust project](../images/studioSetup/23_TrustProject.png) - -* In the status bar at the bottom you will see the information that Android Studio is running background tasks. - - ![Background tasks](../images/studioSetup/24_GradleSyncRunning.png) - -* Windows only: Grant access if your firewall is asking for permission. - - ![Firewall permission java](../images/AndroidStudio361_18.png) - -* Once the background tasks are finished you will probably see an error saying that errors occurred (1) or (2) or (3). - - ![SDK licence](../images/studioSetup/25_SyncFailed.png) - - Don't worry, this will be solved soon! - -(Building-APK-set-git-path-in-preferences)= - -## Set git path in preferences - -Make sure [git is installed](../Installing-AndroidAPS/git-install.md) on your computer and you have restarted your computer since installing. - -On the Android Studio welcome screen click "Customize" (1) on the left and then select the link "All settings..." (2): - -![Android Studio settings from welcome screen](../images/studioSetup/10_WizardSettings.png) - -### Windows - -* As windows user, make sure you have restarted your computer after [installing Git](../Installing-AndroidAPS/git-install.md). - -* In the menu, go to File (1) > Settings (2) (or Android Studio > Preferences on Mac). - - ![הגדרות פתוחות](../images/studioSetup/30_Settings.png) - -* Double-click "Version Control" (1) to open the sub-menu. - -* Click Git (2). -* Make sure update method "Merge" (3) is selected. -* Check if Android Studio can locate path to git.exe automatically by clicking the button "Test" (4). - - ![Android Studio settings](../images/studioSetup/11_GitPath.png) - -* If automatic setting is successful git version will be displayed next to the path. - - ![Git version displayed](../images/studioSetup/12_GitVersion.png) - -* Eventually git.exe cannot be found automatically or the Test will result in an error (1): - - ![Git not found](../images/studioSetup/13_GitVersionError.png) - - In this case click on the folder icon (2). - -* Use [search function](https://www.tenforums.com/tutorials/94452-search-file-explorer-windows-10-a.html) in windows explorer to find "git.exe" if you are unsure where git has been installed. You are looking for a file named "git.exe", located in **\bin** folder. - -* Select path to git.exe and make sure you selected the one in ** \bin\ ** folder (3) and click "OK" (4). - - ![Select git manually](../images/studioSetup/14_GitManualSelection.png) - -* Check your selected git path again with the "Test" button as described above. - -* When the git version is displayed next to the path (see screenshot above), close settings window by clicking "OK" button (5). - -### Mac - -* Any git version should work. For example . -* Use homebrew to install git: ```$ brew install git```. -* For details on installing git see the [official git documentation](https://git-scm.com/book/en/v2/Getting-Started-Installing-Git). -* If you install git via homebrew there is no need to change any preferences. Just in case: They can be found here: Android Studio - Preferences. - -(Building-APK-download-android-sdk)= - -## הורדת Android SDK - -* In the menu, go to File (1) > Settings (2) (or Android Studio > Preferences on Mac). - - ![הגדרות פתוחות](../images/studioSetup/30_Settings.png) - -* Double-click on Languages & Frameworks to open its submenu (1). - -* Select Android SDK (2). -* Tick the box left of "Android 9.0 (Pie)" (3) (API Level 28). - - ![הגדרות SDK](../images/studioSetup/31_AndroidSDK.png) - -* אשרו את ההודעה על ידי לחיצה על 'אישור'. - - ![אמת רישוי SDK](../images/studioSetup/32_ConfirmSDK.png) - -* Wait until the SDK download and installation is finished. - - ![Wait during SDK installation](../images/studioSetup/34_DownloadSDK.png) - -* When SDK installation is completed the "Finish" button will turn blue. Click this button. - - ![Finish SDK installation](../images/studioSetup/35_DownloadSDKfinished.png) - -* Android Studio might recommend to update the gradle system. **Never update gradle!** This will lead to difficulties! - -* If you see an information on the lower right side of your Android Studio window that Android Gradle Plugin is ready to update click on the text "upgrade" (1). - - ![אי שידרוג Gradle](../images/studioSetup/36_GradleUpdateRequest.png) - -* In the dialog box the select "Don't remind me again for this project" (2). - - ![אי שידרוג Gradle](../images/studioSetup/37_GradleUpdateDeny.png) - -* Restart Android Studio before you continue. - -(Building-APK-generate-signed-apk)= - -## יצירת APK חתום - -Signing means that you indicate your app to be your own creation but in a digital way as a kind of digital fingerprint within the app itself. That is necessary because Android has a rule that it only accepts signed code to run for security reasons. For more information on this topic, follow [this link](https://developer.android.com/studio/publish/app-signing.html#generate-key). - -* לאחר הפעלת Android Studio, המתינו עד לסיום כל משימות הרקע. - - ![חכה למשימות ברקע](../images/studioSetup/40_BackgroundTasks.png) - - * ***אזהרה:*** אם עולות שגיאות, אל תמשיכו אל השלבים הבאים. \ אם צריך, עיינו ב[פתרון בעיות](../Installing-AndroidAPS/troubleshooting_androidstudio) לפיתרון תקלות נפוצות! - - ![טעות סנכרון של Gradle](../images/studioSetup/41_GradleSyncError.png) - -* לחצו על "Build" (1) בשורת התפריטים ובחרו "Generate Signed Bundle / APK..." (2). - - ![בנה קובץ אפליקציה](../images/studioSetup/42_MenuBuild.png) - -* לחצו על "APK" (1) במקום "Android App Bundle" ולאחר מכן לחצו "Next" (2). - - ![קובץ APK במקום חבילה](../images/studioSetup/43_Apk.png) - -* Make sure that module is set to "AndroidAPS.app" (1). - -* לחצו "Create new" (2) על מנת להתחיל יצירת ה-key store (מאגר המפתחות). - - ***הערה:* ** בהקשר זה מאגר המפתחות הוא לא יותר מאשר קובץ בו נשמר המידע לחתימת האפליקציה. הוא מוצפן והמידע מאובטח עם סיסמאות. - - ![צור מפתח מאגר](../images/studioSetup/44_KeystoreNew.png) - -* לחצו על צלמית התיקייה על מנת לבחור את הנתיב במחשב לשמירת מאגר המפתחות. - - ![צור מפתח מאגר](../images/studioSetup/45_KeystoreDialog.png) - -* בחרו בנתיב בו מאגר המפתחות יישמר (1). - - ![צור מפתח מאגר](../images/studioSetup/46_KeystorePath.png) - - ***אזהרה: אל תשמור את המפתח התיקייה בה שמור הפרויקט. אתם חייבים להשתמש בתיקייה שונה!*** מיקום טוב יכול להיות תיקיית הבית שלכם. - -* הקלידו שם קובץ למאגר המפתחות (2) ואשרו בלחיצה על "OK" (3). - -* רשמו (2) ואמתו (3) את סיסמת המאגר המפתחות שלכם. ![בחר נתיב מפתח מאגר](../images/studioSetup/47_KeystoreDialog.png) - - ***הערה:*** הסיסמאות למאגר המפתחות לא חייבות להיות מתוחכמות. וודאו שתזכרו את הסיסמאות על ידי שמירתן במקום בטוח. In case you will not remember your passwords in the future, see [troubleshooting for lost key store](troubleshooting_androidstudio-lost-keystore). - -* רשמו כינוי (4) למאגר המפתחות שלכם. בחרו כל כינוי שתרצו. - -* רשמו (5) ואמתו (6) את הסיסמה למפתח שלך - -* התוקף (7) הוא 25 שנה כברירת מחדל. אין חובה לשנות את ערך ברירת המחדל. - -* חייבים להכניס שם פרטי ושם משפחה (8). כל המידע הנוסף הוא לבחירה. - -* לחצו על "OK" (9) לסיום. - -* וודאו שסימנתם את התיבה לזכירת הסיסמאות (1). So you don't have to enter them again next time you build the apk (i.e. when updating to a new AAPS version). - -* לחצו על "Next" (2). - - ![זכור סיסמאות](../images/studioSetup/48_KeystoreSave.png) - -* בחרו את "fullRelease" (1) כגרסה לבנייה ולחצו על "Finish". - - ![בחר גרסת בנייה](../images/studioSetup/49_BuildVariant.png) - -* Android Studio יראה "Gradle Build running" בתחתית המסך. משימה זו לוקחת זמן, תלוי במחשב ובמהירות חיבור האינטרנט. **התאזרו בסבלנות!** - - ![ריצת G](../images/studioSetup/50_GradleRunning.png) - -* AndroidStudio יציג את ההודעה "Generate Signed APK" לאחר סיום בניית האפליקציה. - - ![ריצת Gradle](../images/studioSetup/51_BuildFinished.png) - -* במקרה שהבנייה לא הסתיימה בהצלחה, פנו ל[פרק פיתרון בעיות](../Installing-AndroidAPS/troubleshooting_androidstudio). - -* לחצו על ההודעות להצגה מורחבת שלהן. - -* לחצו על הקישור "locate". - - ![מצא מיקום הבנייה](../images/studioSetup/52_BuildLocate.png) - - * אם ההודעה אינה מוצגת יותר, תוכלו תמיד לפתוח את ה- "Event log" ולבחור אותו שם.![בנייה מוצלחת - אירוע לוג](../images/studioSetup/53_EventLog.png) - -* מנהל הקבצים במחשבכם ייפתח. נווטו אל הספריה "full" (1) > "release (2). - - ![מיקום קובץ האפליקציה](../images/studioSetup/54_APKlocation.png) - -* "app-full-release.apk" (3) הינו הקובץ שאתם מחפשים! - -(Building-APK-transfer-apk-to-smartphone)= - -## העתיקו את האפליקציה אל הטלפון - -Easiest way to transfer app-full-release.apk to your phone is via [USB cable or Google Drive](https://support.google.com/android/answer/9064445?hl=en). Please note that transfer by mail might cause difficulties and is not the preferred way. - -On your phone you have to allow installation from unknown sources. Manuals how to do this can be found on the internet (i.e. [here](https://www.expressvpn.com/de/support/vpn-setup/enable-apk-installs-android/) or [here](https://www.androidcentral.com/unknown-sources)). - -## פתרון בעיות - -See separate page [troubleshooting Android Studio](../Installing-AndroidAPS/troubleshooting_androidstudio). \ No newline at end of file diff --git a/docs/CROWDIN/he/Sandbox/sandbox2.md b/docs/CROWDIN/he/Sandbox/sandbox2.md deleted file mode 100644 index 33c547956c89..000000000000 --- a/docs/CROWDIN/he/Sandbox/sandbox2.md +++ /dev/null @@ -1,43 +0,0 @@ -# internal sandbox file 2 for testing - -```{admonition} no need to translate this -:class: note - -No need to translate this. -``` - -This is an internal sandbox file for the documentation team to test - -1. markdown syntax and - -1. background process for - 1. CROWDIN translation and - 2. Read The Docs deployment. - -You can dirctly jump from here to the first label in the sandbox1.md file - ["Jump"](sandbox1-this-is-a-test). - -You can dirctly jump from here to the second label in this file - ["Jump"](sandbox1-this-is-another-test). - -Here you can jump to the first sandbox file - ["Jump"](./sandbox1.md). - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -(sandbox2-this-is-a-test)= -## This is a test - -This is a test if labels must be unique. - -### This is spare information from the docs - -cut from index: - -There are "limits" set in place when you are first beginning your AAPS journey. These safety limits have been developed over many years by observations of the inadvertent mistakes that new users are most likely to make when first learning to set up, build, and then successfully loop with AAPS - as most often those mistakes occur simply because the user was so excited to get started using the system that they may have forgotten to sit down and dedicate the time needed to understand the information within this documentation thoroughly. - - -### spare info from the overview to put into "preparing" - -Since the requirements are very different from anything you might have set up in the past, we recommend that you really follow the instructions, step-by-step the first few times you build the app, so that you have a stronger sense of how the app building process is supposed to behave when all directions are followed exactly. Please remember to take your time. Later this will go very quickly when you build the app again for a new version. That way you will have a greater chance of noticing when something doesn't going as planned before too many steps are out of line. It is important to save the your keystore file (.jks file used to sign your app) in a safe place, so that you can always use that exact same keystore file and password each and every time you are asked to create a new updated version of AAPS, as this file is what makes sure that each new version of the app "remembers" all the information that you have provided to it in previous versions of the app and thus ensure that the updates will go as smoothly as possible. On average, you can assume that there will be one new version and 2-3 required updates per year. This number is based on experience and may change in the future. But we do want to at least give you a general guideline on what to expect. When you are more experienced at building updated AAPS app versions all the steps that are required in building an updated app will only take 15-30 minutes, on average. However, in the beginning there can be a rather steep learning curve as these steps are not always considered intuitive by new users! So do not get frustrated if you find that it takes half a day or a whole day with some help from the community before you are finally finished with the update process. If you find that you are getting very frustrated just take a short break, and oftentimes; after a stroll around the block or two...you'll find that you are better able to approach the problem again. diff --git a/docs/CROWDIN/he/Usage/Objectives.md b/docs/CROWDIN/he/Usage/Objectives.md deleted file mode 100644 index 6560424ce084..000000000000 --- a/docs/CROWDIN/he/Usage/Objectives.md +++ /dev/null @@ -1,184 +0,0 @@ -# משימות - -ב-AndroidAPS מספר משימות שנועדו ללמד אתכם את ההגדרות ואת היכולות של הלופ, באופן בטיחותי. המשימות נועדו להבטיח שהגדרתם כראוי את כל מה שתואר בפרקים הקודמים ושאתם מבינים מה המערכת עושה ולמה, כדי שתוכלו לבטוח בה. - -אם **שדרגתם או עברתם טלפונים**, תוכלו [לייצא את ההגדרות שלכם](../Usage/ExportImportSettings.md) כדי לשמור על ההתקדמות שלכם במשימות. לא רק ההתקדמות במשימות תישמר, אלא גם הגדרות הבטיחות שלכם כגון בולוס מקסימלי וכו'. אם לא תייצאו ותייבאו את ההגדרות אז תצטרכו להתחיל את המשימות מחדש. לכן, רצוי מאוד [לגבות](../Usage/ExportImportSettings.html) את ההגדרות לעיתים קרובות, למקרה הצורך. - -אם ברצונכם רוצה לחזור על משימות, ראו את [מטה](Objectives-go-back-in-objectives). - -## משימה 1: הגדרת ויזואליזציה, ניטור, ניתוח המינון הבזאלי והיחסים - -- בחרו את מקור נתוני רמת הסוכר המתאים למערכת שלכם. ראו [מקורות ערכי סוכר](../Configuration/BG-Source.md) למידע נוסף. -- בחרו את המשאבה שלכם בבונה התצורה (בחרו משאבה וירטואלית אם אתם משתמשים בדגם משאבה שאינה נתמכת ע"י AAPS) כדי להבטיח תקשורת תקינה של המשאבה עם AAPS. -- אם משתמשים במשאבת DanaR וודאו שקראתם את הוראות [משאבת DanaR](../Configuration/DanaR-Insulin-Pump.md) כדי להבטיח את חיבור המשאבה ל-AndroidAPS. -- יש להקים מאגר נתונים/פלטפורמת דיווח כדי להשלים משימה זו. לרשותכם שתי אפשרויות: Nightscout או Tidepool (או שתיהם). מלאו אחר ההוראות שבדף [Nightscout](../Installing-AndroidAPS/Nightscout.md) או [Tidepool](../Installing-AndroidAPS/Tidepool.md). -- שימו לב שעל כתובת האתר הרשומה ב-NSClient להיות בלי **/api/v1/** בסוף - ראו [הגדרות NSClient בהעדפות](Preferences-nsclient). - -*ייתכן שתצטרכו לחכות לקריאת הסוכר הבאה שתגיע כל מנת ש-AAPS יזהה אותה.* - -## משימה 2: לימדו כיצד לשלוט בממשק AndoridAPS - -- בצעו מספר פעולות ב-AndroidAPS כמתואר במשימה זו. - -- לחצו על הטקסט הכתום "עוד לא הושלם" כדי לפתוח את סעיפי המשימה. - -- מצורפים קישורים על מנת להדריך אתכם בביצוע הסעיפים. - - ```{image} ../images/Objective2_V2_5.png - :alt: Screenshot objective 2 - ``` - -(Objectives-objective-3-prove-your-knowledge)= - -## משימה 3: הוכיחו את הידע שלכם - -מטרה 3 היא מבחן רב ברירה (אמריקאי) עם שאלות שנועדו לבחון את הידע התיאורטי שלכם ב-**AAPS**. - -חלק מהמשתמשים רואים המשימה 3 כמשימה הקשה ביותר. חובה לקרוא את מסמכי AAPS יחד עם השאלות. אם אתם באמת תקועים לאחר קריאה מעמיקה במסמכי **AAPS**, חפשו או בקשו עזרה בקבוצות ה- Facebook או Discord של AAPS. קבוצות אלה יכולות לספק רמזים או להפנות אתכם לחלק הרלוונטי במסמכי **AAPS**. - -כדי לבצע את המשימה, לחצו על הטקסט הכתום "עדיין לא הושלם" כדי לגשת לשאלה הרלוונטית. יש לקרוא את השאלות ולבחור את תשובותיכם. - - - -לכל שאלה מצורף קישור למסמכי **AAPS** שינחה אותכם לחלק הרלוונטי של ההוראות שעליכם לקרוא כדי לענות על השאלה. - - -[Obj3_Screenshot 2023-12-05 223422](https://github.com/openaps/AndroidAPSdocs/assets/137224335/77347516-e24e-459d-98ab-acbb49a3d4e8)![image](https://github.com/openaps/AndroidAPSdocs/assets/137224335/ca756b8e-efbc-4427-b281-ac953ce16718) - - - -לכל שאלה עשויה להיות יותר מתשובה אחת נכונה! אם נבחרה תשובה שגויה, השאלה תינעל למשך 60 דקות שבתומן תוכלו לחזור ולענות עליה. - - -לאחר עדכון לגרסה חדשה של **AAPS**, שאלות חדשות עשויות להיתווסף למשימה 3 על מנת לכסות תכונות חדשות המתווספות בעדכוני התוכנה או תקלות שנמצאו בגרסה קודמת. - - -כאשר **AAPS** מותקן בפעם הראשונה, תצטרכו להשלים את משימה 3 בכללותה כדי לעבור הלאה למשימה 4. ניתן לסיים משימה רק אם כל המשימות הקודמות לה מושלמות. תכונות חדשות יפתחו בהדרגה ככל שתתקדם דרך היעדים. - -__מה קורה אם שאלות חדשות יתווספו מאוחר יותר ליעד 3?__ מעת לעת, תכונות חדשות מתווספות ל-**AAPS** והן עשויות לדרוש הוספת שאלה חדשה למשימה 3. לכן, כל שאלה חדשה שתתווסף למשימה 3 תסומן כ"לא הושלמה" ויהיה עליכם לענות עליה. מכיוון שכל משימה היא עצמאית, לא תאבדו את הפונקציונליות הקיימת של **AAPS** בתנאי שהמשימות האחרות מושלמות. - - -## משימה 4: התחלת לופ פתוח - -- בחרו בלולאה פתוחה בהעדפות או ע"י לחיצה ארוכה על סמל הלופ בחלק העליון של המסך הראשי, בצד שמאל (אם שפת AAPS היא עברית). -- עברו מחדש על ההעדפות כדי לוודא שהכל מוגדר כרצוי. -- אשרו באופן ידני לפחות 20 הצעות לשינוי במינון הבזאלי הזמני על פני תקופה של 7 ימים. בשימוש במשאבה וירטואלית הזינו את השינויים המוצעים במשאבה ואשרו ב-AAPS שביצעתם אותן. וודאו ששינויי המינון נרשמים ב-AndroidAPS וב-Nightscout. -- הפעילו [ערכי מטרה זמניים](../Usage/temptarget.md) במידת הצורך. הפעילו ערך מטרה זמני היפו כדי למנוע מהמערכת לתקן ביתר עליות ברמת הסוכר בעת יציאה מהיפוגליקמיה. - -### צמצום מספר התראות הלולאה הפתוחה - -- על מנת לצמצם את מספר ההמלצות של הלולאה הפתוחה, הגדירו טווח ערכי מטרה רחב כמו לדוגמה 90-150 mg/dl או 5-8.5 mmol/l. - -- תוכלו גם להגדיר ערך מטרה עליון גבוה עוד יותר ואף לכבות את הלופ בלילה. - -- בהעדפות אתם יכולים להגדיר את אחוז השינוי המינימלי הדרוש להפעלת הצעה לשינוי במינונים הבזאליים. - - ```{image} ../images/OpenLoop_MinimalRequestChange2.png - :alt: Open Loop minimal request change - ``` - -- זכרו שאתם לא חייבים להגיב לכל המלצה של הלופ, כל 5 דקות... - -## משימה 5: העמקת הבנת הלולאה הפתוחה, לרבות המינונים הבזאליים הזמניים וההמלצות - -- התחילו לנסות להבין את המחשבה שמאחורי המלצת המינון הבזאלי הזמני ע"י קריאת [לוגיקת קביעת מינון בזאלי](https://openaps.readthedocs.io/en/latest/docs/While%20You%20Wait%20For%20Gear/Understand-determine-basal.html), את [עקום התחזית במסך הבית](Screenshots-prediction-lines) או בנייטסקאוט ואת סיכום הפלטים של החישובים המופיעים בלשונית OpenAPS. - -רצוי שתקבעו ערכי מטרה גבוהים מהרגיל עד אשר תבטחו בהגדרות ובחישובי הלופ. המערכת מאפשרת - -- ערך מטרה תחתון 72 mg/dl עד 180 mg/dl -- ערך מטרה עליון 90 mg/dl עד 225 mg/dl -- ערך מטרה זמני כערך יחיד יכול להיות בטווח 72 עד 225 mg/dl - -ערך המטרה הוא הערך עליו מבוססים החישובים והוא לא ערך הסוכר אליו אתם מתכוונים להגיע בפועל. אם טווח המטרה שלכם רחב מאוד (לדוגמה טווח של 50 mg/dl), אתם תראו מעט פעילות של AAPS. זה בגלל שרמת הסוכר בדם צפויה להיות בתוך הטווח המטרה הרחב הזה ולכן לא יומלצו הרבה שינויים במינון הבזאלי. - -ייתכן שתרצו להתנסות בכיוונונים של ערכי המטרה להקטנת טווח המטרה (20 mg/dl ואף פחות) ולצפות בהתנהגות המערכת כתוצאה מכך. - -תוכלו לצפות בטווח רחב יותר (עקום ירוק) בגרף עבור ערכי סוכר בהם אתם מעוניינים ע"י בחירת ערכים [בהעדפות > סקירה כללית > טווח הצגה](../Configuration/Preferences.md). - -```{image} ../images/sign_stop.png -:alt: Stop sign -``` - -### עצרו כאן אם אתם משתמשים במשאבה וירטואלית - אל תלחצו על "אמת" לסיום משימה זו. - -```{image} ../images/blank.png -:alt: blank -``` - -(Objectives-objective-6-starting-to-close-the-loop-with-low-glucose-suspend)= -## משימה 6: מתחילים לסגור לולאה עם השהיה עקב ערך סוכר נמוך - -```{image} ../images/sign_warning.png -:alt: Warning sign -``` - -### הלולאה הסגורה שבמשימה 6 לא תתקן ערכי סוכר גבוהים כי היא מוגבלת להפסקת הזרקת אינסולין כתיקון לסוכר נמוך. עליכם לתקן סוכר גבוה ידנית בעצמכם! - -- Prerequisite: You need a good profile (basal, ISF, IC) already working in AAPS to start with Loop in Low Glucose Suspend mode. Otherwise you can run in a hypo which you have to manually correct. This will help you a lot to avoid having to treat a low glucose over a period of 5 days. **If you are still having frequent or severe low glucose episodes then consider refining your DIA, basal, ISF and carb ratios and do NOT start objective 6 at this time.** -- You don't have to change your settings now. During objective 6, the maxIOB setting is internally set to zero automatically. **This override will be reversed when moving to objective 7.** -- The system will override your maxIOB settings to zero, which means if blood glucose is dropping it can reduce basal for you. If blood glucose is rising then it will only increase basal if the basal IOB is negative from a previous Low Glucose Suspend. Otherwise basal rates will remain the same as your selected profile. **That means that you have to manually handle high values with insulin corrections.** -- If your basal IOB is negative (see screenshot below) a TBR > 100% can be issued also in objective 6. - -```{image} ../images/Objective6_negIOB.png -:alt: Example negative IOB -``` - -- Set your target range slightly higher than you usually aim for, just to be safe and have a bit more scurity buffer. -- Enable 'Low Glucose Suspend' mode either by by pressing and holding the Loop icon at the top right corner of the home screen and selecting the Loop - LGS mode icon. -- Watch how temporary basals are active by viewing the blue basal text on the homescreen or the blue basal render on the homescreen graph. -- ייתכן שתחוו קפיצות בסוכר לאחר טיפול בהיפוגליקמיות באופן זמני בגלל שאין עליה במינון הבזאלי לאחר היציאה מהיפוגליקמיה. - -(Objectives-objective-7-tuning-the-closed-loop-raising-max-iob-above-0-and-gradually-lowering-bg-targets)= -## משימה 7: כוונון לולאה סגורה, העלאת האינסולין הפעיל המרבי מ-0 והורדה מדורגת של ערכי המטרה - -- בחרו 'לולאה סגורה' מתוך [העדפות](../Configuration/Preferences.md) או על ידי לחיצה ממושכת על סמל הלולאה בפינה השמאלית העליונה של מסך הבית, במשך יום אחד. - -- העלו את 'מינון אינסולין פעיל מרבי ממנו OpenAPS לא יחרוג' (נקרא גם 'max-IOB' ב-OpenAPS) ליותר מ-0 במשך יממה אחת. המלצת ברירת המחדל היא X3 המינון הבזאלי המקסימלי (עבור אלגוריתם AMA הישן, שנמצא בשימוש של משתמשים חדשים) או X3 המינון הבזאלי המקסימלי + בולוס ארוחה ממוצע (עבור אלגוריתם SMB). עליכם להתקדם אל ערך זה באופן מדורג עד שהגדרה זו עובדת היטב. מינון בזאלי מקסימלי = המינון הבזאלי המרבי שניתן בכל שעה שהיא ביממה. - - המלצה זו היא נקודת התחלה. אם הגדרתם X3 בזאלי מרבי ואתם חווים תגובות חריפות ומהירות ברמת הסוכר, הורידו את ערך. אם יש לכם תנגודת גבוהה, הגדילו את הערך בעדינות ובאופן מדורג. - - ```{image} ../images/MaxDailyBasal2.png - :alt: max daily basal - ``` - -- כאשר תרגישו שערך האינסולין הפעיל מתאים לפעולת הלופ שלכם, הורידו את ערכי מטרה שלכם כרצונכם. - -(Objectives-objective-8-adjust-basals-and-ratios-if-needed-and-then-enable-autosens)= -## משימה 8: התאמת המינון בזאלי והיחסים במקרה הצורך ולאחר מכן הפעלת Autosens - -- תוכלו להשתמש ב-[autotune](https://openaps.readthedocs.io/en/latest/docs/Customize-Iterate/autotune.html) באופן חד פעמי לבדיקת השינוי במינון הבזאלי או שתעשו בדיקת בזאלי מסורתית. -- הפעילו [autosens](../Usage/Open-APS-features.md) למשך 7 ימים וצפו בהתנהגות עקום כתוצאה משינויים הורמונליים, פעילות גופנית וכו'. עקום הרגישות הלבן נמצא הוא גרף משני במסך הבית (יש להפעילו). - -*אל תשכחו לרשום את עצמכם* [בטופס הזה](https://bit.ly/nowlooping) *לרישום סוג הלופ שלכם כ-AndroidAPS אם טרם עשיתם זאת.* - -(Objectives-objective-9-enabling-additional-oref1-features-for-daytime-use-such-as-super-micro-bolus-smb)= -## משימה 9: אפשרו פונקציות oref1 כגון סופר מיקרובולוס (SMB), בשעות היום - -- חובה עליכם לקרוא את [הפרק על SMB באתר הויקי](Open-APS-features-super-micro-bolus-smb) ואת [פרק oref1 באתר openAPSdocs](https://openaps.readthedocs.io/en/latest/docs/Customize-Iterate/oref1.html) כדי להבין כיצד SMB פועל ובמיוחד כיצד פועל איפוס בזאלי זמני. -- [העלו את ערך ה-maxIOB](Open-APS-features-maximum-total-iob-openaps-cant-go-over-openaps-max-iob) כדי לאפשר ל-SMB לעבוד כראוי. מעכשיו, האינסולין הפעיל המרבי כולל את כל האינסולין המוזרק, לא רק בזאלי. כלומר, אם תתנו בולוס בגודל 8 יחידות על ארוחה והאינסולין הפעיל המרבי הוא 7 יחידות, הלופ לא יזריק SMB לפני שהאינסולין שבגוף ירד אל מתחת ל-7 יחידות. אפשר להעריך את ערך האינסולין הפעיל המרבי עם החישוב: בולוס ארוחה ממוצע + X3 ערך הבזאלי המרבי שיש ביממה - ראו איור ב[משימה 7](Objectives-objective-7-tuning-the-closed-loop-raising-max-iob-above-0-and-gradually-lowering-bg-targets) -- ערך ברירת המחדל של min_5m_carbimpact בהגדרות הספיגה השתנו מ-3 ל-8 במעבר מ-AMA ל-SMB. אם אתם עוברים מ-AMA ל-SMB, עליכם לעדכן זאת ידנית. - -(Objectives-objective-10-automation)= -## משימה 10: אוטומציות - -- חובה להתחיל את משימה 10 כדי להיות מסוגלים להשתמש ב[אוטומציות](../Usage/Automation.md). -- ודאו שהשלמתם את כל המשימות כולל כל סעיפי הבחינה ש[במשימה 3](Objectives#objective-3-prove-your-knowledge). -- סיום משימות קודמות לא ישפיע על משימות שאותן כבר השלמתם. המשימות שכבר הושלמו יישמרו כך! - -(Objectives-objective-11-DynamicISF)= -## משימה 11: DynamicISF ותכונות נוספות - -- חובה להתחיל את משימה 11 אם ברצונכם להיות מסוגלים להשתמש ב-[DynamicISF](../Usage/Open-APS-features.md) - -(Objectives-go-back-in-objectives)= -## חזרה על משימות - -אם ברצונכם לחזור על משימה מכל סיבה שהיא, ניתן לעשות זאת ע"י לחיצה על "ביטול השלמה". - -```{image} ../images/Objective_ClearFinished.png -:alt: Go back in objectives -``` - -## משימות ב- AndroidAPS לפני גרסה 3.0 - -מטרה אחת הוסרה כאשר AndroidAPS 3.0 שוחרר. משתמשי AndroidAPS גרסה 2.8.2.1 המשתמשים בגרסת אנדרואיד ישנה יותר (כלומר גרסה 9 ומטה) יעברו את המשימות הישנות, השונות מהמתואר בדף זה. לפרטים על המשימות הישנות לחצו [כאן](../Usage/Objectives_old.md). diff --git a/docs/CROWDIN/he/Usage/Objectives_old.md b/docs/CROWDIN/he/Usage/Objectives_old.md deleted file mode 100644 index 9ddf4b17cf62..000000000000 --- a/docs/CROWDIN/he/Usage/Objectives_old.md +++ /dev/null @@ -1,152 +0,0 @@ -# משימות של AndroidAPS 2.8.2.1 - -זו אינה הגרסה העדכנית ביותר של משימות AndroidAPS. דף זה מפרט את המשימות שהיו קיימות לפני גרסה 3.0. Anyone using an older version of Android (i.e. prior to Android 9) and Android APS version 2.8.2.1 should refer to this page. - -Please see [this page](../Usage/Objectives.md) for the current set of Objectives. - -ל-AndroidAPS מספר משימות שנועדו ללמד אתכם את ההגדרות ואת היכולות של לופ, באופן בטיחותי. המשימות נועדו להבטיח שהגדרתם כראוי את כל מה שתואר בפרקים הקודמים ושאתם מבינים מה המערכת עושה ולמה, כדי שתוכלו לבטוח בה. - -If you are **upgrading phones** then you can [export your settings](../Usage/ExportImportSettings.md) to keep your progress through the objectives. Not only will your progress through the objectives be saved, but also your safety settings such as max bolus etc. If you do not export and import your settings then you will need to start the objectives from the beginning again. It is a good idea to [backup your settings](../Usage/ExportImportSettings.html) frequently just in case. - -If you want to go back in objectives see [explanation below](../Usage/Objectives.md#go-back-in-objectives). - -## משימה 1: הגדרת ויזואליזציה, ניטור, ניתוח המינון הבזאלי והיחסים - -- Select the right blood glucose source for your setup. See [BG Source](../Configuration/BG-Source.md) for more information. -- Select the right Pump in ConfigBuilder (select Virtual Pump if you are using a pump model with no AndroidAPS driver for looping) to ensure your pump status can communicate with AndroidAPS. -- If using DanaR pump then ensure you have followed [DanaR Insulin Pump](../Configuration/DanaR-Insulin-Pump.md) instructions to ensure the link between pump and AndroidAPS. -- Follow instructions in [Nightscout](../Installing-AndroidAPS/Nightscout.md) page to ensure Nightscout can receive and display this data. -- Note that URL in NSClient must be **WITHOUT /api/v1/** at the end - see [NSClient settings in Preferences](../Configuration/Preferences.md#nsclient). - -*You may need to wait for the next blood glucose reading to arrive before AndroidAPS will recognise it.* - -## משימה 2: למדו כיצד לשלוט בממשק AndoridAPS - -- Perform several actions in AndroidAPS as described in this objective. - -- Click on the orange text "Not completed yet" to access the to-dos. - -- Links will be provided to guide you in case you are not familiar with a specific action yet. - - ![Screenshot objective 2](../images/Objective2_V2_5.png) - -## משימה 3: הוכיחו את הידע שלכם - -- Pass a multiple-choice exam testing your AndroidAPS knowledge. - -- Click on the orange text "Not completed yet" to access the page with the question and answering options. - - ![Screenshot objective 3](../images/Objective3_V2_5.png) - -- Links will be provided to guide you in case you are unsure about the correct answers yet. - -- The questions for objective 3 have been completely rewritten by native speakers as of AAPS 2.8. השאלות החדשות מכסות את אותם נושאים בסיסיים בתוספת מספר נושאים נוספים. - -- These new questions will lead to some not answered questions even though you have successfully completed objective 3 in previous versions. - -- Unanswered questions will affect you only if you start a new objective. או במילים אחרות: אם סיימתם את כבר סיימתם את כל המשימות, תוכלו להמתין ולענות על השאלות החדשות אחר כך ללא איבוד פונקציות AAPS שבמשימות מאוחרות יותר. - -## משימה 4: התחלת לופ פתוח - -- Select Open Loop either from Preferences, or by pressing and holding the Loop button in top left of the home screen. -- Work through the [Preferences](../Configuration/Preferences.md) to set up for you. -- Manually enact at least 20 of the temporary basal rate suggestions over a period of 7 days; input them to your pump and confirm in AndroidAPS that you have accepted them. וודאו ששינוי המינון נרשם ב-AndroidAPS וגם ב-Nightscout. -- Enable [temp targets](../Usage/temptarget.md) if necessary. הפעילו ערך מטרה זמני היפו כדי למנוע מהמערכת לתקן ביתר עליות ברמת הסוכר בעת יציאה מהיפוגליקמיה. - -### צמצום מספר התראות הלולאה הפתוחה - -- To reduce the Number of decisions to be made while in Open Loop set wide target range like 90 - 150 mg/dl or 5,0 - 8,5 mmol/l. - -- You might even want to wider upper limit (or disable Open Loop) at night. - -- In Preferences you can set a minimum percentage for suggestion of basal rate change. - - ![Open Loop minimal request change](../images/OpenLoop_MinimalRequestChange2.png) - -- Also, you do not need to act every 5 minutes on all suggestions... - -## משימה 5: העמקת הבנת הלולאה הפתוחה, לרבות המינונים הבזאליים הזמניים וההמלצות - -- Start to understand the thinking behind the temp basal recommendations by looking at the [determine basal logic](https://openaps.readthedocs.io/en/latest/docs/While%20You%20Wait%20For%20Gear/Understand-determine-basal.html) and both the [forecast line in AndroidAPS homescreen](../Getting-Started/Screenshots.md#prediction-lines)/Nightscout and the summary of outputs from the calculations in your OpenAPS tab. - -רצוי שתקבעו ערכי מטרה גבוהים מהרגיל עד אשר תבטחו בהגדרות ובחישובי הלופ. המערכת מאפשרת - -- a low target to be a minimum of 4 mmol (72 mg/dl) or maximum of 10 mmol (180 mg/dl) -- a high target to be a minimum of 5 mmol (90 mg/dl) and maximum of 15 mmol (225 mg/dl) -- a temporary target as a single value can be anywhere in the range of 4 mmol to 15 mmol (72 mg/dl to 225 mg/dl) - -ערך המטרה הוא הערך עליו מבוססים החישובים והוא לא ערך הסוכר אליו אתם מתכוונים להגיע בפועל. If your target is very wide (say, 3 or more mmol \[50 mg/dl or more\] wide), you will often find little AAPS action. זה בגלל שרמת הסוכר בדם צפויה להיות בתוך הטווח המטרה הרחב הזה ולכן לא יומלצו הרבה שינויים במינון הבזאלי. - -You may want to experiment with adjusting your targets to be a closer together range (say, 1 or less mmol \[20 mg/dl or less\] wide) and observe how the behavior of your system changes as a result. - -You can view a wider range (green lines) on the graph for the values you aim to keep your blood glucose within by entering different values in [Preferences](../Configuration/Preferences.md) > Range for Visualisation. - -![Stop sign](../images/sign_stop.png) - -### עצרו כאן אם אתם משתמשים במשאבה וירטואלית - אל תלחצו על "אמת" לסיום משימה זו. - -![blank](../images/blank.png) - -## משימה 6: מתחילים לסגור לולאה עם השהיה עקב ערך סוכר נמוך - -![Warning sign](../images/sign_warning.png) - -### הלולאה הסגורה שבמשימה 6 לא תתקן ערכי סוכר גבוהים כי היא מוגבלת להפסקת הזרקת אינסולין כתיקון לסוכר נמוך. עליכם לתקן סוכר גבוה ידנית בעצמכם! - -- Select Closed Loop either from [Preferences](../Configuration/Preferences.md) or by pressing and holding the Open Loop button in the top left of the home screen. - -- Set your target range slightly higher than you usually aim for, just to be safe. - -- Watch how temporary basals are active by viewing the blue basal text on the homescreen or the blue basal render on the homescreen graph. - -- Ensure your settings have supported AndroidAPS to avoid having to treat a low glucose over a period of 5 days. אם אתם עדיין חווים היפוגליקמיות תכופות, שקלו לבצע שינויים ב-DIA, במינונים הבזאליים, ביחס הפחמימות וביחס התיקון. - -- You don't have to change your settings. לאורך משימה 6, ערכו של maxIOB מוגדר כ-0 מאחורי הקלעים באופן אוטומטי. הגדרה זו תבוטל לאחר התחלת משימה 7. - -- The system will override your maxIOB settings to zero, which means if blood glucose is dropping it can reduce basal for you, but if blood glucose is rising then it will only increase basal if the basal IOB is negative (from a previous Low Glucose Suspend), otherwise basal rates will remain the same as your selected profile. - - ![Example negative IOB](../images/Objective6_negIOB.png) - -- If your basal IOB is negative (see screenshot above) a TBR > 100% can be issued also in objective 6. - -- ייתכן שתחוו קפיצות בסוכר לאחר טיפול בהיפוגליקמיות באופן זמני בגלל שאין עליה במינון הבזאלי לאחר היציאה מהיפוגליקמיה. - -## משימה 7: כוונון לולאה סגורה, העלאת האינסולין הפעיל המרבי מ-0 והורדה מדורגת של ערכי המטרה - -- Raise your 'Maximum total IOB OpenAPS can’t go over' (in OpenAPS called 'max-iob') above 0 over a period of 1 day, the default recommendation is "average mealbolus + 3x max daily basal"(for SMB algorithm) or "3x max daily basal" (for older AMA algorithm) but you should slowly work up to this until you know your settings work for you (max daily basal = the maximum hourly value in any time segment of the day). - - המלצה זו היא נקודת התחלה. אם הגדרתם X3 בזאלי מרבי ואתם חווים תגובות חריפות ומהירות ברמת הסוכר, הורידו את ערך. אם יש לכם תנגודת גבוהה, הגדילו את הערך בעדינות ובאופן מדורג. - - ![max daily basal](../images/MaxDailyBasal2.png) - -- Once confident on how much IOB suits your looping patterns then reduce your targets to your desired level. - -## משימה 8: התאמת המינון בזאלי והיחסים במקרה הצורך ולאחר מכן הפעלת Autosens - -- You can use [autotune](https://openaps.readthedocs.io/en/latest/docs/Customize-Iterate/autotune.html) as a one off to check your basals remain accurate or do a traditional basal test. -- Enable [autosens](../Usage/Open-APS-features.md) over a period of 7 days and watch the white line on the homescreen graph show how your sensitivity to insulin may be rising or falling as a result of exercise or hormones etc. and keep an eye in the OpenAPS report tab how AndroidAPS is adjusting the basals and/or targets accordingly. - -*Don’t forget to record your looping in* [this form](https://bit.ly/nowlooping) *logging AndroidAPS as your type of DIY loop software, if you have not already done so.* - -## משימה 9: ניסוי פונקציות נוספות של הלופ בשעות היום וצבירת ביטחון במערכת הלופ - -- Before AAPS version 2.7 meal assist (MA) was the basic algorithm for AAPS and completing objective 8 was necessary to activate [advanced meal assist (AMA)](../Usage/Open-APS-features.md#advanced-meal-assist-ama). -- As [advanced meal assist (AMA)](../Usage/Open-APS-features.md#advanced-meal-assist-ama) is the standard algorithm from AAPS version 2.7 onwards use the following 28 days to try features you haven't used yet and get more confident with you closed loop system. - -## משימה 10: אפשרו פונקציות oref1 כגון סופר מיקרובולוס (SMB), בשעות היום - -- You must read the [SMB chapter in this wiki](../Usage/Open-APS-features.md#super-micro-bolus-smb) and [chapter oref1 in openAPSdocs](https://openaps.readthedocs.io/en/latest/docs/Customize-Iterate/oref1.html) to understand how SMB works, especially what's the idea behind zero-temping. -- Then you ought to [rise maxIOB](../Usage/Open-APS-features.md#maximum-total-iob-openaps-cant-go-over-openaps-max-iob) to get SMBs working fine. מעכשיו, האינסולין הפעיל המרבי כולל את כל האינסולין המוזרק, לא רק בזאלי. That is, if given a bolus of 8 U for a meal and maxIOB is 7 U, no SMBs will be delivered until IOB drops below 7 U. A good start is maxIOB = average mealbolus + 3x max daily basal (max daily basal = the maximum hourly value in any time segment of the day - see [objective 7](../Usage/Objectives#objective-7-tuning-the-closed-loop-raising-max-iob-above-0-and-gradually-lowering-bg-targets) for an illustration) -- min_5m_carbimpact default in absorption settings has changed from 3 to 8 going from AMA to SMB. אם אתם עוברים מ-AMA ל-SMB, עליכם לעדכן זאת ידנית. - -## משימה 11: אוטומציות - -- You have to start objective 11 to be able to use [Automation](../Usage/Automation.md). -- Make sure you have completed all objectives including exam [../Usage/Objectives.md#objective-3-prove-your-knowledge](../Usage/Objectives#objective-3-prove-your-knowledge). -- Completing previous objectives will not effect other objectives you have already finished. המשימות שכבר הושלמו יישמרו כך! - -## חזרה על משימות - -אם ברצונכם לחזור על משימה מכל סיבה שהיא, ניתן לעשות זאת ע"י לחיצה על "ביטול השלמה". - -![Go back in objectives](../images/Objective_ClearFinished.png) diff --git a/docs/CROWDIN/he/Usage/Smoothing-Blood-Glucose-Data-in-xDrip.md b/docs/CROWDIN/he/Usage/Smoothing-Blood-Glucose-Data-in-xDrip.md deleted file mode 100644 index bf05f21fefa6..000000000000 --- a/docs/CROWDIN/he/Usage/Smoothing-Blood-Glucose-Data-in-xDrip.md +++ /dev/null @@ -1,33 +0,0 @@ -(Smoothing-Blood-Glucose-Data-in-xDrip-smoothing-blood-glucose-data)= - -# החלקת נתוני הגלוקוז בדם - -If BG data is jumpy/noisy, AAPS may dose insulin incorrectly resulting in high or low BG. For this reason it’s important to disable the loop until the problem is resolved. Depending on your CGM such issues may be due to the CGM’s configuration or sensor problems/site issues. You may need to replace your CGM sensor to resolve this. - -Some CGM systems have internal algorithms to detect the noise level in the readings and AAPS can use this information to avoid giving SMBs if the BG data is too unreliable. However, some CGMs do not transmit this data and for these BG sources 'Enable SMB always' and 'Enable SMB after carbs' are disabled for safety reasons. - -## חיישני דקסקום - -### "בנה יישום Dexcom בעצמך" (BYODA) - -When using [BYODA](DexcomG6-if-using-g6-with-build-your-own-dexcom-app) your BG data is smooth and consistent. Furthermore you can take advantage of Dexcom back-smoothing. There are no restrictions in using SMBs, because the noise-level data is shared with AAPS. - -### xDrip+ with Dexcom G6 or Dexcom ONE - -Noise-level data and smooth BG readings are only shared with AAPS if you use xDrip+ [native mode](https://navid200.github.io/xDrip/docs/Native-Algorithm). Using native mode, there are no restrictions in using SMBs. - -### Dexcom G6 or Dexcom ONE with xDrip+ Companion Mode - -The noise-level data is not shared with AAPS using this method. Therefore 'Enable SMB always' and 'Enable SMB after carbs' are disabled. - -## חיישני Freestyle Libre - -### xDrip+ with FreeStyle Libre - -None of the FreeStyle Libre systems (FSL1, FSL2, or FSL3) broadcast any information about the level of noise detected in the readings, and therefore 'Enable SMB always' and 'Enable SMB after carbs' are disabled for all setups using the FreeStyle Libre. - -In addition, many people have reported the FreeStyle Libre often produces noisy data. In xDrip+ there are a few options to help with this: - -**Smooth Sensor Noise.** In xDrip+ Settings > xDrip+ Display Settings ensure that Smooth Sensor Noise is turned on. This attempts to apply smoothing to noisy data. - -**Smooth Sensor Noise (Ultrasensitive).** If you are still seeing noisy data in xDrip+ you can apply more aggressive smoothing using the Smooth Sensor Noise (Ultrasensitive) setting. This will attempt to apply smoothing even on very low levels of detected noise. To do this, first enable [engineering mode](Enabling-Engineering-Mode-in-xDrip.md) in xDrip+. Then navigate to Settings > xDrip+ Display Settings and turn on Smooth Sensor Noise (Ultrasensitive). \ No newline at end of file diff --git a/docs/CROWDIN/he/Usage/autotune_b.md b/docs/CROWDIN/he/Usage/autotune_b.md deleted file mode 100644 index 936fd5e86e50..000000000000 --- a/docs/CROWDIN/he/Usage/autotune_b.md +++ /dev/null @@ -1,186 +0,0 @@ -# How to use Autotune plugin - -Documentation about Autotune algorythm can be found in [OpenAPS documentation](https://openaps.readthedocs.io/en/latest/docs/Customize-Iterate/autotune.html). - -Autotune plugin is an implementation of OpenAPS autotune algorythm within AAPS. - -**Currently Autotune Plugin is only available in dev branch with Engineering mode.** - -## Autotune user interface - -![Autotune default screen](../images/Autotune/Autotune_1b.png) - -- You can select in the Profile dropdown menu the input profile you want to tune (by default your current active profile is selected) - - Note: each time you select a new profile, previous results will be removed and Tune days parameter will be set to default value -- Then Tune days is to select the number of days used in calculation to tune your profile. The minimum value is 1 day and the maximum value 30 days. This number should not be too small to get correct iterative and smooth results (above 7 days for each calculation) - - Note: each time you change Tune days parameter, previous results will be removed -- Last Run il a link that recover your latest valid calculation. If you didn't launch Autotune on current day, or if previous results was removed with a modification of calculation parameter above, then you can recover parameters and results of the latest successfull run. -- Warning show you for example some information about selected profile (if you have several IC values or several ISF values) - - Note: Autotune calculation works with only a single IC and a single ISF value. There is currently no existing Autotune algorythm to tune a circadian IC or circadian ISF. If your input profile has several values, you can see in warning section the average value taken into account to tune your profile. -- Check Input Profile button open the Profile Viewer to allow you a quick verification of your profile (Units, DAI, IC, ISF, basal and target) - - Note: Autotune will only tune your IC (single value), ISF (single value) and basal (with circadian variation). Units, DAI and target will remain unchanged in output profile. - -- "Run Autotune" will launch Autotune calculation with selected profile and the number of Tune days - - Note: Autotune calculation can take a long time. Once launched, you can switch to another view (home, ...) and come back later in Autotune plugin to see results - -![Autotune Run start](../images/Autotune/Autotune_2b.png) - -- Then during the run you will see intermediate results below - - - Note: During run, settings are locked, so you cannot change anymore selected input profile or the number of day. You will have to wait the end of current calculation if you want to launch another run with other parameters. - - ![Autotune during run](../images/Autotune/Autotune_3b.png) - -- When Autotune calculation is finished, you will see the result (Tuned profile) and four buttons below. - -![Autotune Result](../images/Autotune/Autotune_4b.png) - -- It's important to always compare input profile (column "Profile"), output profile (column "Tuned") and the percentage of variation for each value (Column "%"). - -- For basal rates, you also have the number of "missing days". You have missing days when Autotune don't have enough data categorized as "Basal" to tune basal rate for this period (for example after each meal when you have carbs absorption). This number should be as low as possible especially when basal is important (for example during the night or at the end of the afternoon) - -- The "Compare profiles" button open the profile comparator view. Input profile is in blue, and output profile (named "Tuned") is in red. - - - Note: in the example below input profile has circadian variation for IC and ISF, but output calculated profile has a single value. If it's important for you to get a circadian output profile see [Circadian IC or ISF profile](#circadian-ic-or-isf-profile) below. - - ![Autotune Compare profiles](../images/Autotune/Autotune_5.png) - -- If you trust results (low percentage of variation between input profile and output profile), you can click on "Activate profile" button and then click on OK to validated. - - - Activate Tuned profile will automatically create a new profile "Tuned" in your Local profile plugin. - - If you already have a profile named "Tuned" in your local profile plugin, then this profile will be updated with calculated Autotune profile before the activation - - ![Autotune Activate profile](../images/Autotune/Autotune_6.png) - -- If you think Tuned profile must be adjusted (for example if you think some variation are too important), then you can click on "Copy to local profile" button - - - A new profile with the prefix "Tuned" and the date and time of the run will be created in local profile plugin - -![Autotune Copy to local profile](../images/Autotune/Autotune_7.png) - -- You can then select local profile to edit the Tuned profile (it will be selected by default when you open Local profile plugin) - - - the values in local profile will but rounded in the user interface to your pump capabilities - - ![Autotune local profile update](../images/Autotune/Autotune_8.png) - -- If you want to replace your input profile with Autotune result, click on "Update input profile" button and validate the Popup with OK - - - Note: if you click on "Activate profile" after "Update input profile", then you will activate your updated profile and not the default "Tuned" profile? - - ![Autotune Update input profile](../images/Autotune/Autotune_9.png) - -- If you have updated your input profile, then the "Update input profile" button is replaced by "Revert input profile" button (see screenshot below). You can that way immediatly see if your current input profile in Local profile plugin already include the result of last run or not. You also have the possibility to recover you input profile without autotune result with this button - - ![Autotune Update input profile](../images/Autotune/Autotune_10.png) - - - -## Autotune settings - -### Autotune plugin settings - -![Autotune default screen](../images/Autotune/Autotune_11.png) - -- Automation Switch Profile (default Off): see [Run Autotune with an automation rule](#run-autotune-with-an-automation-rule) below. If you change this setting to On, the input profile will automatically be updated by the Tuned profile, and it will be activated. - - **Be Carefull, you must trust and verified during several following days that after an update and activation of Tuned profile without modification, it improves your loop** - -- Categorize UAM as basal (default On): This setting is for the users using AndroidAPS without any carbs entered (Full UAM). It will prevent (when Off) to categorize UAM as basal. - - Note: if you have at least one hour of Carbs absorption detected during one day, then all data categorized as "UAM" will be categorized as basal, whatever this setting (On or Off) -- Number of days of data (default 5): You can define default value with this setting. Each time your select a new profile in Autotune plugin, Tune days parameter will be replaced by this default value -- Apply average result in circadian IC/ISF (default Off): see [Circadian IC or ISF profile](#circadian-ic-or-isf-profile) below. - -### הגדרות אחרות - -- Autotune also uses Max autosens ratio and Min autotsens ratio to limit variation. You can see and adjust these values in Config Builder > Sensitivity detection plugin > Settings > Advanced Settings - - ![Autotune default screen](../images/Autotune/Autotune_12.png) - - - -## Advanced feature - -### Circadian IC or ISF profile - -- If you have important variation of IC and/or you ISF in your profile, and you fully trust in your circadian time and variation, then you can set "Apply average result in circadiant IC/ISF" - - - Note that Autotune calculation will always be done with a single value, and circadian variation will not be tuned by Autotune. This setting only apply average variation calculated for IC and/or ISF on your circadian values - -- See on screenshot below Tuned profile with Apply average variation Off (on the left) and On (on the right) - - ![Autotune default screen](../images/Autotune/Autotune_13.png) - - - -### Tune specific days of the week - -- If you click on the checkbox with the eye on the right of "Rune days" parameter, you will see the day selection. You can specify which day of the week should be included in Autotune calculation (in screenshot below you can see an example for "working days" with Saturday and Sunday removed from autotune calculation) - - If the number of day included in Autotune calculation is lower than the number of Tune days, then you will see how many days will be included on the right of Tune days selector (10 days in the example below) - - This setting gives good results only if the number of remaining days is not to small (for example if you Tune a specific profile for week end days with only Sunday and Saturday selected, you should select a minimum of 21 or 28 Tune days to have 6 or 8 days included in Autotune calculation) - -![Autotune default screen](../images/Autotune/Autotune_14b.png) - -- During Autotune calculation, you can see the progress of the calculations ("Partial result day 3 / 10 tuned" on example below) - - ![Autotune default screen](../images/Autotune/Autotune_15b.png) - -## Run Autotune with an automation rule - -First step is to define correct trigger for an automation rule with Autotune: - -Note: for more information on how to set an automation rule, see [here](./Automation.rst). - -- You should select Recurring time trigger: only run Autotune once per day, and autotune is designed to be runned daily (each new run you shift one day later and quickly profile modification should be tiny) - - ![Autotune default screen](../images/Autotune/Autotune_16.png) - -- It's better at the beginning to run Autotune during the day to be able to check results. If you want to run Autotune during the night, you have to select in the trigger 4AM or later to include current day in next Autotune Calculation. - - ![Autotune default screen](../images/Autotune/Autotune_17.png) - -- Then you can select "Run Autotune" Action in the list - - ![Autotune default screen](../images/Autotune/Autotune_18.png) - -- You can then select Autotune Action to adjust parameters for your run. Default parameters are "Active Profile", default Tune days value defined in Autotune Plugin preferences, and All days are selected. - - ![Autotune default screen](../images/Autotune/Autotune_19b.png) - -- After a few days, if you fully trust Autotune results and percentage of modification is low, you can modify [Autotune settings](#autotune-plugin-settings) "Automation Switch Profile" to enabled to automatically update and activate profile tuned after calculation. - -Note: if you want to automatically tune profiles for specific days of the week (for example a profile for "Weekend days" and another one for "Working days"), then create one rule for each profile, select the same days in Trigger and in Autotune Action, Tune days must be high enough to be sure tuning will be done with at least 6 or 8 days, and don't forget to select time after 4AM in trigger... - -- See below an example of rule to tune "my profile" on all "Working days" with 14 Tune days selected (so only 10 days included in autotune calculation). - -![Autotune default screen](../images/Autotune/Autotune_20b.png) - - - -## Tips and trick's - -Autotune works with information existing in your database, so if you just installed AAPS on a new phone, you will have to wait several days before being able to launch Autotune with enough days to get relevant results; - -Autotune is just an help, it's important to regularly check if you agree with calculated profile. If you have any doubt, change Autotune settings (for example the number of days) or copy results in local profile and adjust profile before using it. - -Always use Autotune several days manually to check results before applyling them. And it's only when you fully trust Autotune results, and when variation becomes tiny between previous profile and calculated profile than you start to use Automation (Never before) - -- Autotune can work very well for some users and not for others, so **If you don't trust Autotune result, don't use it** - -It's also important to analyse Autotune results to understand (or try to understand) why Autotune propose these modifications - -- you can have a whole increase or decrease of the strength of your profile (for example increase of total basal associated to decrease of ISF and IC values). it could be associated to several following days with autosens correction above 100% (more agressivity required) or below 100% (you are more sensitive) -- Sometimes Autotune propose a different balance between basal rates and IC/ISF (for ex lower basal and more aggressive IC/ISF) - -We advise to not use Autotune in the following cases: - -- You don't enter all your carbs - - If you don't enter carbs correction for an hypoglycemia, Autotune will see an unexcepted increase of your BG value and will increase your basal rates the ' hours earlier, it could be the opposite of what you need to avoid hypo, especially if it's in the middle of the night. That's why it's important to enter all carabs especially correction for hypo. -- You have a lot of period with UAM detected during the day. - - Do you have entered all your carbs and correctly estimated your Carbs ? - - All UAM periods (except if you enter no carbs during a day and categorized UAM as basal is disabled), all your UAM periods will be categorized as basal, this can increase a lot your basal (much more than necessary) - -- Your carbs absorption is very slow: if most of your carbs absorption are calculated with min_5m_carbimpact parameter (you can see these periods with a little orange dot in the top of COB curve), the calculation of COB could be wrong and leads to wrong results. - - We you practice sport, you are generally more sensitive and your BG doesn't rise a lot, so during or after an exercice, it's usual to see some periods with slow carbs. But if you have too often unexpected slow carb absorption, then you may need a profile adjustment (higher value of IC) or a min_5m_carbimpact a bit to high. -- You have a "very bad days", for example stuck several hours in hyperglycemia with a huge amount of insulin to be able to go down within the range, or after a sensor change you got long periods of wrong BG values. -- If the percentage of modification is too important - - You can try to increase the number of days to get smoother results \ No newline at end of file diff --git a/docs/CROWDIN/he/Usage/making-sport-with-AAPS.md b/docs/CROWDIN/he/Usage/making-sport-with-AAPS.md deleted file mode 100644 index 79d2f1c38223..000000000000 --- a/docs/CROWDIN/he/Usage/making-sport-with-AAPS.md +++ /dev/null @@ -1,185 +0,0 @@ -# making sport with AAPS - -In this section we want to address the topic of sport with AAPS. - -The aim is to show you how AAPS can help you to continue doing your favorite sport more easily or even to start doing it. It is relatively common for new type 1 diabetics to ask whether exercise is still possible for them, even if the answer in the training courses is actually a clear yes. Exercise is not only good for healthy people, but also for type 1 diabetics and even moderate exercise can even help to stabilize the blood sugar curve overall. - -:::{admonition} consult with your diabetes team after reading - -::: - -The difficulty here is that the prerequisites that someone brings with them and the expectations of what sport means to them are very different. - -Since we can assume that experienced top athletes with T1D who use AAPS are unlikely to look it up here, we deliberately set the bar low for ourselves when writing and for you when reading and using it, so that as many people as possible can benefit from it. - -Since even sport as a category is far too imprecise, as the effects of endurance sports differ greatly from strength training, for example, we are trying to break it down by type of sport. - -To be concrete and give you something you can test yourself we arrange the explanaiton around a concrete example and explain to you they action, reactions and effects. - -:::{admonition} more examples wanted - -The focus should always be on how others can do sport and not on the top performance someone has achieved. - -It's really about the basics. Your experience, which you share here, can help others to pursue their beloved sport more quickly and successfully and is therefore important. -::: - -## Cycling - -:::{admonition} take a friend with you - at least on your first trials -:class: information -A gerneral very good idea can be to take a good friend with you on the first rides. -This is especially important if you are not experienced in T1D. -Always keep in mind please: arrival comes before speed! Safety for you and the others in road traffic is very, very important. -::: - -### Example - -Let's take about 60 minutes of cycling on a flat route with a moderate heart rate as an example. - -1. we take a flat route in order to have an even load for the first exercise. This is not about performance, but purely about learning how you should react to changes in blood glucose. -2. we take the heart rate as an indicator of the load, as it is easy to see whether you are under load or not. -3. we set ourselves the goal of doing a relaxed lap around the neighborhood and focus on staying within our target range during the lap. In my case, this would be 70 <= x <= 180 mg/dl. - -We **don't** take the speed, as this is heavily dependent on personal physical conditions as well as the bike and surface used. It is therefore not very meaningful. - -You should know from the diabetes training courses you have attended that during endurance sports cycling, the insulin active in the body works significantly better than during times without physical exertion. The insulin active in the body is referred to as insulin on board (IoB). It is our most important parameter when cycling with T1D. - -We try to keep the IoB as low as possible at the start and during exercise. IoB should be around 0 or even slightly negative. You can get it there by not eating 3-4 hours before exercise. In the beginning it can also be helpful to exercise in the morning before breakfast, as with the right profile you should always have around 0 for IoB in the morning. - -AAPS shows us the IoB value on the home screen on the left under the blood glucose value. - -![IoB](../images/cycling_20240104-174035.png) - -:::{admonition} ignoring the IoB rule increases the risk for roller coaster BG dramatically -:class: danger -If you ignore this rule, you can still go cycling, but it will be much more difficult to keep your blood sugar levels in balance, so it is better to save this for later tests after several successful simple tests. -::: - -As you should know from the diabetes training courses, you should reduce the basal rate during exercise. The factor is individual. I have found a value of 50% in tests to be suitable for me. - -In AAPS, you should therefore change your profile to 50% before exercise and keep it active until the end of exercise. Some people even do it a certain amount of time before, e.g. 1 hour. Unfortunately, the pre-run is also individual. We will come to the post-run later. - -You should use two carbohydrates during exercise. - -1. medium-fast carbohydrates for the insulin still in the body and -2. very fast carbohydrates to prevent slipping into a hypo. - -For medium-fast carbohydrates, I treat myself to cookies or a banana before exercise, for example. You can also use something else that is more suitable for you. -For very fast carbohydrates, I take 3 teaspoons of dissolved glucose per 100 ml of still water in a 500 ml water bottle on my bike. If I'm cycling longer distances, I take a larger bottle with me and, if necessary, packaged glucose to refill the bottle. I add a little lemon juice for flavor. You can also use something other than lemon juice for the taste. You shouldn't change anything about the dextrose, as dissolved dextrose raises blood sugar levels super quickly. If you only take it in sips, your blood sugar won't go super high either! You can also do this tip at home beforehand as a dry run and see how quickly the change shows up on the CGMS. - -Why do I place so much emphasis on fast carbohydrates? - -1. once you are in a slight hypo, you may get back into the normal range by drinking the dextrose solution. As a rule, however, the oscillation of the curve then begins, which leads to a rollercoaster ride of the blood sugar. You may even be able to keep this within your target range, but you must be constantly vigilant. Without a hypo it is simply the most stable. -2. if you even slip into a somewhat severe hypo (without the need for outside help, of course), you may even have to pause briefly to avoid getting stuck in the hypo. - With both hypos, there is a risk that you will be tempted to switch from drinking 2-3 sips at a time to larger quantities. Not too bad at first, until the oscillation sets in and pushes you into a hyper. You can correct this, but your blood sugar will most likely go on a rollercoaster ride. - -What else is helpful, but not absolutely necessary? -It is important to keep an eye on your blood sugar, as your blood sugar can change enormously (e.g. 30 - 50 mg/dl) within 15 minutes of riding and a little more IoB or a basal rate that is still too high. The best way to keep an eye on it is if it is visible on the handlebars or if it is also displayed on your watch. It is even possible to install an additional app on some Garmin GPS bike computers that displays the blood glucose from XDrip or Nightscout as a data field on the bike computer. The additional app was developed by Andreas May from the T1D community. It is available free of charge in the official connect IQ Store. Certainly an interesting option for riders interested in sports. - -[Link to Andreas May Data Field App on connect IQ store](https://apps.garmin.com/de-DE/apps/5a3e2cda-12f0-4afd-88ed-000e67a68d84) - -Here is a picture of my Garmin Edge 530 bike computer with map, blood sugar and heart rate. - -![Garmin Edge 530 with BG data field](../images/cycling_IMG_1087.jpeg) - -After you have eaten the medium fast carbohydrates (24 - 36 g I take) and the blood sugar is above 100 mg/dl but also below 160 mg/dl, I carry out the profile change to 50% and set the activity temp target. - -:::{admonition} disable SMBs during high temp targets if necessary -:class: danger -Attention: If you prefer not to receive SMBs during the sport, please disable the option "Enable SMB with hight temp targets" in the settings of SMB or DynIFS Plugin. -::: - -The following picture shows the start and end of the sport. The end was specified as the duration when the profile was changed at the start. - -The temporary profile change has the following effects - -1. for a period of 60 minutes -2. a reduction to 50% of the profile and -3. the target is raised by clicking on the Activity Target option, which may have the side effect of disabling the SMBs - see above. - -![profile switch with temp target](../images/cycling_20240104-174056.png) - -The second image shows that the start at IoB was started towards 0. - -![IoB around 0](../images/cycling_20240104-174111.png) - -If the blood sugar drops faster than 15 mg/dl in 5 minutes or if it is at 120 mg/dl and tends to fall, I drink 1-2 sips of dissolved glucose. Then I wait for the next value and proceed as described above. - -You can hardly see it here, but at the beginning I took 2 sips from the bottle several times when my blood sugar started to fall. When it stabilized, I didn't need any more glucose. - -Here is the picture that illustrates this. The chart is saved on the Garmin as a result of the activity. - -![BG chart Garmin](../images/cycling_20240104-174431.png) - -If you should suddenly break out upwards, i.e. above 180 mg/dl, you should consider whether you should make a correction bolus. Caution: Remember the factor and apply it to the correction, otherwise the correction will be too strong. - -If your blood sugar drops below 80 mg/dl, take a break and drink two sips until your blood sugar is back above 100 mg/dl. - -At the end of the ride, the profile change should be finished as the time is up. - -Since we only rode easy for 60 minutes, there shouldn't be a big muscle bulking effect continuing to pull carbohydrates from your blood sugar. However, if it felt strenuous to you, keep an eye on it. This is especially true if you then go straight to bed. It may be better to change your profile to e.g. 80% for sleep. You may come out of sleep slightly too high, but it's better than having a hypo at night. Over time, you will surely find out what happens to you. - -The following pictures show the low intensity of the sport. - -The elevation profile -![](../images/cycling_20240104-174314.png) - -Speed with average and maximum speed - -![](../images/cycling_20240104-174326.png) - -Note the pause at the level crossing, which is also reflected in the heart rate. - -The heart rate. -![](../images/cycling_20240104-174337.png) - -The training effect. -![](../images/cycling_20240104-174358.png) - -The time in the different heart rate training zones. -![](../images/cycling_20240104-174423.png) - -After succesfully mastering this simple example you could go for further targets by stretching - -1. the distance and time -2. the load during the ride -3. the elevation during the right which should make a big impact on the more necessary carbs or further reduction of IoB and percentage of profile switch. - -Based on my experiences I would not expect to come back 100% with time in range over the whole and every ride. - -### Tipps - -I already gave some tipps for during the ride above. - -Here are some further tipps what can go wrong and how you can act to prevent it or react to compensate it. - -#### sky rocket high after ride - -During the ride everything was fine but after siting down and relax the blood sugar go sky rocket high. - -**Possible reason:** This happens when you have drunk too much dissolved glucose. - -**Reaction:** Drink 500 ml water, go to the shower and then control again. Latest after 30 minutes think about giving a correction bolus but be careful when it is short for bed time. Therefore it can be very good to make the first try runs on weekend mornings. - -**Action:** Next time be a bit more cautious in drinking from the dissolved glucose. - -#### hypo during ride - -During the ride you are going into hypo and can't recover your blood sugar during cycling. - -**Possible reason:** Your body cannot absorb enough carbohydrates quickly enough during exercise. - -**Reaction:** Take a rest and corrrect your blood sugar with drinking dissolved glucose. Stay calm: arrival comes before speed. - -**Action:** Did you started with IoB near 0? Have you eaten a small amount of middle fast carbs? Can you increase this or are the not fast enough for your body? Is it possible to prevent going into hypo by reducing the factor for the profile switch? Have you disbaled SMBs during ride as explained above? - -#### sky rocket high during ride - -During the ride your blood sugar goes sky rocket high. - -**Possible reason:** You have got taken too much carbs for your IoB at that time. Beneath for sure the typical technical problems with your -insulin pump like leakage or blockage of the catheder! - -**Reaction:** If it is too high for you take a rest and correct with a bolus. Keep in mind that you must ride home and therefore make it carefully. Drink 500 ml pure water without carbs. Stay calm: arrival comes before speed. - -**Action:** Have you eaten too much? Especially have you drunk too much from the dissolved glucose during the ride? Is your percentage of reduction the profile during profile switch too low and you can increase this? diff --git a/docs/CROWDIN/he/buildingAAPS.md b/docs/CROWDIN/he/buildingAAPS.md deleted file mode 100644 index 98164a09e49b..000000000000 --- a/docs/CROWDIN/he/buildingAAPS.md +++ /dev/null @@ -1,28 +0,0 @@ -# Dummy - -## This is a dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - - -## This is another dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - - -## This is another another dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - diff --git a/docs/CROWDIN/he/completingObjetives.md b/docs/CROWDIN/he/completingObjetives.md deleted file mode 100644 index 98164a09e49b..000000000000 --- a/docs/CROWDIN/he/completingObjetives.md +++ /dev/null @@ -1,28 +0,0 @@ -# Dummy - -## This is a dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - - -## This is another dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - - -## This is another another dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - diff --git a/docs/CROWDIN/he/dummy.md b/docs/CROWDIN/he/dummy.md deleted file mode 100644 index 98164a09e49b..000000000000 --- a/docs/CROWDIN/he/dummy.md +++ /dev/null @@ -1,28 +0,0 @@ -# Dummy - -## This is a dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - - -## This is another dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - - -## This is another another dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - diff --git a/docs/CROWDIN/he/intro.md b/docs/CROWDIN/he/intro.md deleted file mode 100644 index cb0ef3e92a28..000000000000 --- a/docs/CROWDIN/he/intro.md +++ /dev/null @@ -1,291 +0,0 @@ -![20-06-23v2 AAPS simple overview-cropped](https://github.com/openaps/AndroidAPSdocs/assets/94044064/e505b73b-09a0-42a4-a1ab-b830a0741234) - -# Introduction to APS and AAPS - -## What is an “Artificial Pancreas System”? - -A human pancreas does a lot of things besides regulating blood sugar. However, the term **“Artificial Pancreas System” (APS)** usually refers to a system which works to automatically keep blood sugar levels within healthy limits. - -The most basic way to do this is by detecting **glucose levels**, using these values to do **calculations**, and then delivering the (predicted) right amount of **insulin** to the body. It repeats the calculation, every few minutes, 24/7. It uses **alarms** and **alerts** to inform the user if intervention or attention is needed. This system is typically made up of a **glucose sensor**, an **insulin pump** and an **app** on a phone. - -You can read more about the different artificial pancreas systems currently in use and in development in this 2022 review article: - -![Frontiers](./images/FRONTIERS_Logo_Grey_RGB.png) [Future Directions in Closed-Loop Technology](https://www.frontiersin.org/articles/10.3389/fendo.2022.919942/full#:~:text=Fully%20closed%2Dloop%20systems%2C%20unlike,user%20input%20for%20mealtime%20boluses). - -In the near future, some so-called "dual-hormone" systems will also have the ability to infuse glucagon alongside insulin, with the aim of preventing severe hypos and allowing even tighter blood glucose control. - -An artificial pancreas can be thought of as an [“autopilot for your diabetes”]. (https://www.artificialpancreasbook.com/) What does that mean? In an aircraft, an autopilot does not do the complete job of the human pilot, the pilot cannot sleep through the entire flight. The autopilot aids the work of the pilot. It relieves them of the burden of permanently monitoring the aircraft, allowing the pilot to concentrate on wider monitoring from time to time. The autopilot receives signals from various sensors, a computer evaluates them together with the pilot’s specifications and then makes the necessary adjustments, alerting the pilot to any concerns. The pilot no longer has to worry about constantly making decisions. - -## What does hybrid closed loop mean? - -The best solution for type 1 diabetes would be a “functional cure” (probably an implant of pancreatic cells which are protected from the immune system). While we are waiting for that, a “full closed loop” artificial pancreas is probably the next best thing. This is a tech system that doesn’t need any user input (like bolusing insulin for meals, or announcing exercise), with good regulation of blood glucose levels. At the moment, there are no widely available systems which are “full” closed loop, they all need some user input. The currently available systems are called “hybrid” closed loop, because they use a combination of automated technology and user input. - -## How and why did looping start? - -The development of commercial technology for people with type 1 diabetes (T1D) is very slow. In 2013 the T1D community founded the #WeAreNotWaiting movement. They developed systems themselves using existing approved technology (insulin pumps and sensors) to improve blood glucose control, safety, and quality of life. These are known as DIY (do-it-yourself) systems, because they are not formally approved by health bodies (FDA, NHS etc). There are four main DIY systems available: OpenAPS, **AAPS**, Loop and iAPS. - -A great way to understand the fundamentals of DIY looping is to read Dana Lewis’s book “Automated Insulin Delivery”. You can access it \[here\] (https://www.artificialpancreasbook.com/) for free (or buy a hardcopy of the book). If you want to understand more about OpenAPS, which** AAPS** has developed from, the \[OpenAPS website\] (https://openaps.org/what-is-openaps/) is also a great resource. - -Several commercial hybrid closed loop systems have been launched, the most recent of which are \[CamAPS FX\] (https://camdiab.com/) (UK and EU) and \[Omnipod 5\] (https://www.omnipod.com/en-gb/what-is-omnipod/omnipod-5) (USA and EU). These are very different to DIY systems, mainly because they both include a “learning algorithm” which adjusts how much insulin is delivered according to your insulin needs from previous days. Many people in the DIY community have already tried out these commercial systems and compared them with their DIY system. You can find out more about how the different systems compare by asking on the dedicated Facebook groups for these systems, on the \[AAPS Facebook group\] (https://www.facebook.com/groups/AndroidAPSUsers/) or on \[Discord\] (https://discord.com/invite/4fQUWHZ4Mw). - -## What is Android APS (AAPS)? - -![image](https://github.com/openaps/AndroidAPSdocs/assets/94044064/0f089d96-b7ee-452a-aa9d-aae10ab58971) - -**Figure 1**. Basic outline of the Android APS (Artificial Pancreas System), AAPS. - -Android APS (AAPS) is a hybrid closed loop system, or Artificial Pancreas System (APS). It makes its insulin dosing calculations using established \[OpenAPS\] (https://openaps.org/) algorithms (a set of rules) developed by the #WeAreNotWaiting type 1 diabetes community. - -Since OpenAPS is only compatible with certain older insulin pumps, AAPS (which can be used with a wider range of insulin pumps) was developed in 2016 by Milos Kozak, for a family member with type 1 diabetes. Since those early days, **AAPS** has been continually developed and refined by a team of volunteer computer developers and other enthusiasts who have a connection to the type 1 diabetes world. Today, **AAPS** is used by approximately 10,000 people. It is a highly customisable and versatile system, and because it is open-source, it is also readily compatible with many other open-source diabetes softwares and platforms. The fundamental components of the current **AAPS** system are outlined in Figure 1 above. - -## What are the basic components of AAPS? - -The “brain” of AAPS is an **app** which you build yourself. There are detailed step-by-step instructions for this. You then install the **AAPS app** on a compatible **Android smartphone** (1). A number of users prefer their loop on a separate phone to their main phone. So, you don’t necessarily have to be using an Android phone for everything else in your life, just for running your AAPS loop. - -The **Android smartphone** will also need to have another app installed on it as well as **AAPS**, either a modified Dexcom app called build-your-own dexcom app (**BYODA**) or Xdrip+. This receives glucose data from a sensor (2) by bluetooth, and then sends the data internally on the phone to the **AAPS app**. - -The **AAPS app** uses a decision making process (**algorithm**) from OpenAPS. Beginners start out using the basic **oref0** algorithm, but it is possible to switch to using the newer **oref1** algorithm as you progress with AAPS. Which algorithm you use (oref0 or oref1), depends on which suits your specific situation best. In both cases, the algorithm takes into account multiple factors, and performs rapid calculations every time a new reading comes in from the sensor. The algorithm then sends instructions to the insulin pump (3) on how much insulin to deliver by bluetooth. All the information can be sent by mobile data or wifi to the internet. This data can also be shared with followers if desired, and/or collected for analysis. - -## What are the advantages of the AAPS system? - -The OpenAPS algorithm used by **AAPS** controls blood sugar levels in the absence of user input, according to the users’ defined parameters (important ones being basal rates, insulin sensitivity factors, insulin-to-carb ratios, duration of insulin activity etc.), reacting every 5 minutes to the new sensor data. Some of the reported advantages of using AAPS are extensive fine-tunable options, automations and increased transparency of the system for the patient/caregiver. This can result in better control over your (or your dependent’s) diabetes, which in turn may give improved quality of life and increased peace of mind. - -Practical advantages include: - -- **Hardware flexibility**: **AAPS** works with a wide range of insulin pumps and sensors. So for example, if you develop an allergy to Dexcom sensor patch glue, you could switch to using a Libre sensor instead. That offers flexibility as life changes. You don't have to rebuild, just tick a different box in the AAPS app to change your hardware. - -- **Highly customisable with wide parameters**: here are some examples of the possibilities with AAPS: a) The ability to set a lower glucose target 30 min before eating; you can set the target as low as 72 mg/dL (4.0 mmol/L). b) If you are insulin-resistant resulting in high blood sugars, **AAPS** allows you to set an **automation** rule to activate when BG rises above 8 mmol/L (144 mg/dL), switching to a 120% profile (resulting in an 20% increase in basal and strengthening of other factors too, compared to your normal **profile** setting). The automation will last according to the scheduled time you set. Such an automation could be set to only be active on certain days of the week, at certain times of day, and even at certain locations. c) If your child is on a trampoline with no advance notice, **AAPS** allows insulin suspension for a set time period, directly via the phone. d) After reconnecting a tubed pump which has been disconnected for swimming, AAPS will calculate the basal insulin you have missed while disconnected and deliver it carefully, according to your current BG. Any insulin not required can be overridden by just “cancelling” the missed basal. f) **AAPS** has the ability to set different profiles for different situations and easily switch between them. Features which make the algorithm quicker to bring down elevated BG (like supermicro boluses (“SMB”), unannounced meals, (“**UAM**”) can be set to only work during the daytime, if you are worried about night-time hypos. - - -These are all examples, the full range of features gives huge flexibility for daily life including sport, illness, hormone cycles etc. Ultimately, it is for the user to decide how to use this flexibility, and there is no one-size-fits-all automation for this. - -- **Remote monitoring**: there are multiple possible monitoring channels (Sugarmate, Dexcom Follow, Xdrip+, Android Auto etc.) which are useful for parents/carers and adults in certain scenarios (sleeping/driving) who need customisable alerts. In some apps (Xdrip+) you can also turn alarms off totally, which is great if you have a new sensor “soaking” or settling down that you don’t want to loop with yet. - -- **Remote control**: a significant advantage of **AAPS **over commercial systems is that it is possible for followers, using authenticated text (SMS) commands or via an app (Nightscout or NSClient) to send a wide range of commands back to the ****AAPS** **system. This is used extensively by parents of kids with type 1 diabetes who use AAPS. It is very useful in the playground, for example, if you want to pre-bolus for a snack from your own phone, and your child is busy playing. It is possible to monitor the system (e.g. Fitbit), send basic commands (e.g. Samsung Galaxy watch 4), or even run the entire AAPS system from a high-spec smartwatch (5) (e.g. LEMFO LEM14). In this last scenario, you don’t need to use a phone to run AAPS. As battery life on watches improves, this last option is likely to become increasingly attractive. - -- **No commercial constraints due to open application interfaces**: beyond the use of an open source approach, which allows the source code of **AAPS** to be viewed at any time, the general principle of providing open programming interfaces gives other developers the opportunity to contribute new ideas that allow users to live more easily with their diabetes. This is complementary to commercial systems which adopt the innovations from DIY, where interfaces are only made possible in return for licensing, thus preventing innovations in particular that are not-for-profit. Good examples for such integrations are NightScout, Nightscout Reporter, Xdrip+ M5 stack etc. - -- **Detailed app interface**: It is easy to keep track of things like: insulin levels, cannula age, sensor age, pump battery age, and many actions can be done through the **AAPS** app (priming the pump, disconnecting the pump etc.), instead of on the pump itself. - -- **Accessibility and affordability**: **AAPS** gives people who currently can’t afford to self-fund, or don’t have funding/insurance, access to a world-class hybrid closed looping system which is conceptually years ahead, in terms of development, of the commercial systems being offered by clinics. You currently need to have a Nightscout account to set up **AAPS**. Although the Nightscout account it not necessarily required after setup, many people continue to use Nightscout for collecting their data, and for remote control. So, although **AAPS **itself is free, setting up Nightscout through one of the various platforms may incur a fee (E0 - E12), depending on what level of support you want (see comparison table). **AAPS** works with a wide range of affordable (starting from approx E150) Android phones. In comparison, Loop currently costs around $80 a year for the Apple development licence and CamAPS FX costs around E80/month (as at 2023). - -- ****Support**: No automated insulin delivery system is perfect. Commercial and open-source systems share many common glitches in both communications and temporary hardware failure. There is a community of AAPS users on both Facebook and Discord and Github who designed, developed and are currently using **AAPS** all over the world. There are Facebook support groups and help from clinic/commercial companies for the commercial APS systems - it is worth speaking to the users, or former users of these systems to get feedback on the common glitches, the quality of the education programme and the level of ongoing support provided. - -- **Predictability, transparency and safety**: with no learning algorithm, **AAPS** is logical and in some respect, more predictable, which may make it easier to know when a setting is wrong, and to adjust it accordingly. You can see exactly what the system is doing, why it is doing it, and set its operational limits, which puts the control (and responsibility) in your hands. This can provide the user with confidence, and a sounder sleep. - -- **Access to advanced features through dev modes including full closed loop**: **AAPS **documentation focuses on the mainstream **“master”** branch of **AAPS**, however, research and development is going on all the time. More experienced users may wish to explore the experimental features in the **development** branch such as integration of Dexcom G7, and automatically adjusting insulin delivery according to short-term sensitivity changes (DYNISF), not having to bolus for meals, and generally trying to make life with type 1 diabetes as convenient as possible. - -- **Ability to contribute yourself to further improvements**: type 1 diabetes can be highly frustrating and isolating. Having control over your own diabetes tech, with the possibility to “pay it forward” as soon as you are making progress by helping others on their journey can be really rewarding. You can educate yourself, discover the roadblocks and look for and even contribute to new developments and the documentation. There will be others with the same quest to bounce ideas off and work with. This is the essence of #WeAreNotWaiting. - - -## How does AAPS compare to MDI and open looping? - -Multiple daily injections (MDI, a) usually involve giving an injection of a long-lasting insulin (e.g. Tresiba) once a day, with injections of faster-acting insulin (e.g. Novorapid, Fiasp) at mealtimes, or for corrections. Open pumping (b) involves using a pump to deliver basal at pre-programmed rates of rapid-acting insulin, and then boluses through the pump at mealtimes or for corrections. The basics of a looping system is that the App uses the glucose data to instruct the pump to stop insulin delivery when it predicts you are heading for a low, and to give you extra insulin if your glucose levels are rising and predicted to go too high (c). Although this is oversimplified, (mostly because hybrid closed looping has a lot of additional useful features) the key features of each system are shown in **Figure 2**. - -![image](https://github.com/openaps/AndroidAPSdocs/assets/94044064/4e7d8608-684d-4c69-9c61-88c9539f5d6f) - -**Figure 2**. Overview of (a) MDI, (b) open-loop pumping and (c) hybrid closed loop pumping - -## How does AAPS compare to other looping systems? - -At present there are four major open source closed loop systems available: OpenAPS, **AAPS**, \[Loop\] (https://loopkit.github.io/loopdocs/#what-is-loop) and iAPS, (formerly FreeAPS X). The features of the different systems are shown in the table below: - -| Devicestyp | Name | [Open APS](https://openaps.readthedocs.io/en/latest/) | [AAPS](https://wiki.aaps.app) | [לולאה](https://loopkit.github.io/loopdocs/) | [iAPS](https://iaps.readthedocs.io/en/latest/) | -| ---------- | -------------------------------------------------------------------------------------------------------- | ----------------------------------------------------- | ------------------------------------------- | -------------------------------------------- | ---------------------------------------------- | -| PUMP | Older Medtronic | ![available](./images/available.png) | ![available](./images/available.png) | ![available](./images/available.png) | ![available](./images/available.png) | -| PUMP | Older Omnipod (Eros) | ![unavailable](./images/unavailable.png) | ![available](./images/available.png) | ![available](./images/available.png) | ![available](./images/available.png) | -| PUMP | Newer Omnipod (Dash) | ![unavailable](./images/unavailable.png) | ![available](./images/available.png) | ![available](./images/available.png) | ![available](./images/available.png) | -| PUMP | DANA R, DANA RS, DANA I | ![unavailable](./images/unavailable.png) | ![available](./images/available.png) | ![unavailable](./images/unavailable.png) | ![unavailable](./images/unavailable.png) | -| PUMP | Roche Combo, Insight | ![unavailable](./images/unavailable.png) | ![available](./images/available.png) | ![unavailable](./images/unavailable.png) | ![unavailable](./images/unavailable.png) | -| סנסור | Dexcom G4, G5, G6 | ![available](./images/available.png) | ![available](./images/available.png) | ![available](./images/available.png) | ![available](./images/available.png) | -| סנסור | Libre 1 (requires Miao Miao) | ![available](./images/available.png) | ![available](./images/available.png) | ![available](./images/available.png) | ![available](./images/available.png) | -| סנסור | Libre 2 | ![available](./images/available.png) | ![available](./images/available.png) | ![available](./images/available.png) | ![available](./images/available.png) | -| סנסור | Libre 3 | | ![unavailable](./images/unavailable.png) | --- | ![unavailable](./images/unavailable.png) | -| סנסור | Medtronic Enlite | | --- | ![unavailable](./images/unavailable.png) | --- | -| סנסור | [Dexcom G7](https://androidaps.readthedocs.io/en/latest/Hardware/DexcomG7.html) | | ![available](./images/available.png) (beta) | ![available](./images/available.png) | ![available](./images/available.png) | -| סנסור | [Eversense](https://androidaps.readthedocs.io/en/latest/Hardware/Eversense.html) | | ![available](./images/available.png) | | ![available](./images/available.png) | -| סנסור | [MM640g/MM630g](https://androidaps.readthedocs.io/en/latest/Hardware/MM640g.html) | | ![available](./images/available.png) | | ![available](./images/available.png) | -| סנסור | [PocTech](https://androidaps.readthedocs.io/en/latest/Hardware/PocTech.html) | | ![available](./images/available.png) | | ![available](./images/available.png) | -| סנסור | [Nightscout כמקור נתונים](https://androidaps.readthedocs.io/en/latest/Hardware/CgmNightscoutUpload.html) | | ![available](./images/available.png) | | ![available](./images/available.png) | -| Phone | Android | ![available](./images/available.png) | ![available](./images/available.png) | ![unavailable](./images/unavailable.png) | ![unavailable](./images/unavailable.png) | -| Phone | iPhone | ![available](./images/available.png) | ![unavailable](./images/unavailable.png) | ![available](./images/available.png) | ![available](./images/available.png) | - -[OpenAPS](https://openaps.readthedocs.io/) was the first Open Source Closed Loop System. היא משתמשת במחשבים זעירים כמו Raspberry Pi ו-Intel Edison. Both AndroidAPS (AAPS) and iAPS use the OpenAPS algorithms, whereas Loop uses a separate algorithm. You can read a comparison of iAPS and **AAPS** here. - -An international peer-reviewed consensus statement containing practical guidance on open source looping was written by and for health-care professionals, and published in a leading medical journal in 2022. It is well worth a read (including for your diabetes clinic) and summarises the main technical differences between the different open-source hybrid closed loop systems: - - Lancet Diabetes Endocrinol, 2022; 10: 58–74 - -[https://www.ncbi.nlm.nih.gov/pmc/articles/PMC8720075/](https://www.ncbi.nlm.nih.gov/pmc/articles/PMC8720075/) - -It is hard to get a “feel” for any system without using it, or talking to others who are using it, so do reach out to others on Facebook/Discord and ask. Most people find that AAPS is incredibly sophisticated in comparison to other hybrid closed loop systems (particularly the commercial systems), with a huge number of potentially customisable settings and features, discussed above. Some people can find this a little overwhelming in the beginning, but there is no rush to investigate all the possibilities at once, you can progress as slowly or as fast as you would like, and there is help available at every step of the way. - -## Does AAPS use artificial intelligence or any learning algorithm? - -לא. **AAPS** does not have any complicated machine learning algorithms, multiple-parameter insulin response models, or differential equations. As such, the system is open and transparent in how it works, and has the ability to be understood not just by experts, but also by clinicians and patients. It also means that if you have a sharply varying schedule (maybe switching from a stressful week at work to a relaxing holiday) and are likely to need a significantly different amount of insulin, you can immediately switch **AAPS** to run a weaker/stronger profile. A ‘learning system’ will do this adjustment for you automatically, but is likely to take longer to adjust the insulin delivery. - -## Which system is right for me or my dependent? - -Practically, your choice of system is often restricted by which pump you already have, or can obtain from your medical provider, and your choice of phone (Apple or Android). If you don’t yet have a pump you have the biggest choice of systems. Technology is continually evolving, pumps are being discontinued and new pumps and sensors are being released. Most open-source systems work with the main sensors (Libre and Dexcom) or are quickly adapted to work with new sensors a year or so after they are released (with a bit of time delay for safety and stability testing). - -Most **AAPS **users report more time in range, HbA1c reductions, as well as quality of life improvements from having a system that can auto-adjust basal rates overnight during sleep, and this is true for most hybrid closed loop APS. Some people have a preference for a very simple system which is not very customisable (which means you may prefer a commercial system), and others find this lack of control very frustrating (you may prefer an open-source system). If you (or your dependent) are newly diagnosed, a common route is to get the hang of MDI plus sensor first, then progress to a pump which has the potential for looping, then to **AAPS**, but some people (especially small kids) may go straight to a pump. - -It is important to note that the **AAPS** user needs to be proactive to troubleshoot and fix problems themselves, with help from the community. This is a very different mindset to that when using a commercial system. With **AAPS** a user has more control, but also the responsibility, and needs to be comfortable with that. - -## Is it safe to use open-source systems like AAPS? - -A more accurate question is probably “is it safe compared to my current type 1 diabetes insulin delivery system?” since no method of insulin delivery is without risk. There are many checks and balances in place with **AAPS**. A recent paper looked at the use of**** AAPS ****in a computer simulated set-up, [https://www.liebertpub.com/doi/epub/10.1089/dia.2019.0375](https://www.liebertpub.com/doi/epub/10.1089/dia.2019.0375) which was an effective way to unobjectively trial how safe and effective the system is. More generally, it is estimated that over 10,000 individuals worldwide are using open-source automated-insulin delivery systems, and uptake continues to increase globally. - -Any device that uses radio communications could be hacked, and this is true for a non-looping insulin pump as well. Currently, we are not aware of anyone attempting to harm individuals by hacking their diabetes-related medical equipment. However, there are multiple ways to protect against such risks: - -1. In the pump settings, limit both the max bolus allowed and max temporary basal settings to amounts that you believe are safest. These are hard limits that we do not believe any malicious hacker could circumvent. - -2. Set your CGM alarms enabled for both highs and lows. - -3. Monitor your insulin delivery online. Nightscout users can set additional alarms to alert for a wide variety of conditions, including conditions that are much more likely to occur than a malicious attack. In addition to highs and lows, Nightscout can display diagnostic data useful for verifying that the pump is operating as desired, including current IOB, pump temporary basal history, pump bolus history. It can also be configured to proactively alert users to undesirable conditions, such as predicted highs and lows, low insulin reservoir, and low pump battery. - - -If a malicious attack was made on your insulin pump, these strategies would significantly mitigate the risk. Every potential **AAPS** user needs to weigh the risks associated with using **AAPS**, versus the risks of using a different system. - -## How can I approach discussing AAPS with my clinical team? - -Depending on the country - link to doctors section of docs - - Lancet Diabetes Endocrinol, 2022; 10: 58–74 - -[https://www.ncbi.nlm.nih.gov/pmc/articles/PMC8720075/](https://www.ncbi.nlm.nih.gov/pmc/articles/PMC8720075/) - -## Q: Why can’t I just download AAPS and use it straight away? - -The **AAPS** app is not provided in Google Play - you have to build it from source code by yourself for legal reasons. **AAPS** is unlicensed, meaning that it does not have approval by any regulatory body authority in any country. **AAPS**is deemed to be carrying out a medical experiment on yourself, and is carried out at the user’s own risk. - -Setting up the system requires patience, determination and the gradual development of technical knowledge. All the information and support can be found in these documents, elsewhere online, or from others who have already done it. It is estimated that over 2000 people have successfully built and are currently using **AAPS** worldwide. - -The developers of **AAPS**t ake safety incredibly seriously, and want others to have a good experience of using **AAPS**. That is why it is essential that every user (or carer, if the user is a child): - -- builds the AAPS system themself and works through the **objectives** so that they have reasonably good personalised settings and understand the basics of how AAPS ****works by the time they “close the loop”; - -- backs up their system by exporting and saving important files (like keystore and settings .json file) somewhere safe, so you can setup again quickly if needed; - -- updates to newer master versions as and when they become available; and - -- maintains and monitors the system to ensure it is working properly. - - -## Q: What is the connectivity of the AAPS system? - -**Figure 3 (below)** shows one example of the **AAPS** system for a user who do not require any followers interacting with the system: - -![potential AAPS connectivity setup with no followers](./images/intro03.png) - -**Figure 4 (below)** shows the full potential of the **AAPS** system for a user who has followers and requires a monitor and send adjust the system remotely (like a child with T1D): - -![potential AAPS connectivity setup with followers](./images/intro04.png) - -## Q: How does AAPS get continually developed and improved? - -Most **AAPS** users use the fully tested **master** version of AAPS, which has been tested for bugs and problems, before being released to the community. Behind the scenes, the developers try out new improvements, and test these out in “developer” (**dev**) versions of **AAPS** with a user community who are happy to do bug updates at short notice. If the improvements work well, they are then released as a new “master” version of **AAPS**. Any new master release is announced on the Facebook group, so that the mainstream **AAPS** users can read about and update to the new master version. - -Some experienced and confident **AAPS ** users conduct experiments with emerging technologies and with dev versions of the **AAPS** app, which can be interesting for the less adventurous users to read about, without having to do it themselves! People tend to share these experiments on the Facebook group too. - -You can read more about some of these experiments and discussion on emerging tech here: - -[https://www.diabettech.com/](https://www.diabettech.com/) - -[https://bionicwookie.com/](https://bionicwookie.com/) - -## Q: Who can benefit? - -| User Type | -| ------------------------------------------- | -| ✔️ type 1 diabetic | -| ✔️ caregiver or parent of a type 1 diabetic | -| ✔️ blind users type 1 diabetic | -| ✔️ *clincians and healthcare professionals | - -The above table assumes that the user has access to both continuous gluocse monitor and insulin pump. - -*All data from **AAPS** can be made available to healthcare professionals via data sharing platforms, including NightScout that provides logging and real time monitoring of CGM data, insulin delivery, carbohydrate entries, predictions and settings. Nightscout records include daily and weekly reports which can aid healthcare professionals' discussions with type 1 patients with more accurate data on glycemic control and any behavioural considerations. - -## Q: What benefits can I get? - -With investment of your time, **AAPS** can potentially lead to: - -- alleviating the stress and burden of managing type 1 diabetes; - -- reducing the multitude of mundane decisions that arise from type 1 diabetes; - -- the provision of personalised and dynamic insulin dosing based on real-time data which can cut down the need for hypo treatments and reduce hyperglycemia episodes; - -- an increased knowledge of insulin management and confidence to better fine tune your settings; - -- the ability to create automatic settings (**automations**) that are tailored to fit in with your lifestyle; - -- improved sleep quality and overall reduction in the frequency of nighttime interventions; - -- remote monitoring and administration of insulin delivery for caregivers of type 1 diabetics; and - -- streamlining of all your portable diabetic equipment (continuous glucose monitor and insulin portable devices) by replacing them with an android phone controlled by **AAPS**. - - -Ultimately,**AAPS** can empower individuals to better manage their diabetes resulting in stable blood sugars and improved long term health outcomes. - ---- - -## AAPS First Steps - -Welcome. This is an introduction to aid beginners getting started with **AAPS** (or commonly referred to as "looping"). - -## Safety - -“_With great powers comes great responsibilities…_” - -**AAPS** is designed with an extensive set of safety features with limits imposed and gradually removed with completion of the **objectives **(predominately made up of multiple choice questions). An **AAPS** feature will be unlocked as the Objectives are successfully completed. This process will gradually allow the user to migrate from Open Loop to Closed Loop. - -This has been done to achieve the best possible experience with **AAPS** in order to prevent common mistakes that new users tend to make when starting to loop. The safety parameters have been built upon typical errors and general trends **AAPS** developers have observed with new users. Mistakes can happen because the beginner is inexperienced and too eager to get started with AAPS or has overlooked the required materials. Do not worry, we have all been there! - -## Key Principles - -The key principles and concepts of looping must be understood by the user before using **AAPS**. This is achieved by investing your personal time into reading the **AAPS** documentation, and completing the Objectives which is aimed to provide you with a solid platform for safe and effective use of **AAPS**. The volume of **AAPS** documentation may seem overwhelming at first but be patient and trust the process - with the proper approach, you'll get there! The overall process will depend upon the beginner’s progress and completion of objectives can typically take between 6 to 9 weeks . - -## Plan for hiccups - -At the preliminary stages of **AAPS**, you should expect to experience some hiccups whilst trying to fine tune your settings. **AAPS**’ glitches cannot be flushed out until the system is used in everyday life. Please plan accordingly and allow a sensible amount of time to troubleshoot and resolve such issues. - -## Flexibility/Adaptability - -Success with **AAPS** requires a proactive approach, a willingness to reflect on the BG data and flexibility to make the necessary adjustments to **AAPS** in order to improve your outcomes. Just as it is nearly impossible to learn to play a sport by reading about the rules alone, the same can be said of **AAPS**. - -## Technology compatibility - -There are limitations with **AAPS** as it is accessible for only certain types of insulin pumps or CGMs, and some technology may not be available for use in various countries. In order to avoid any disappointment or frustrations, please read please read Component Set Up (Section INSERT). - -## App Build Time - -The time to build the **AAPS**(under Section INSERT) depends on your level of expertise and technical ability. Typically for inexperienced users, it can take up to half a day or a full day (with help from the community) in order to build the **AAPS**. The process will significantly speed up as you become more experienced at building the **AAPS**. To aid the build process there are sections dedicated for: -- list of questions and answers for frequent errors that are likely to occur under FAQs (Section K); -- “How to install AAPS? (Section INSERT) which includes Troubleshooting subsection. - -## Keystore & configurations settings a export file - -A “keystore” is a password encrypted file unique to your own copy of **AAPS**. Your android phone uses it to ensure that nobody else can upgrade your own copy without the keystore. In short, as part of the **AAPS** build, you should: - -- save the your keystore file (.jks file used to sign your app) in a safe place; -- keep a note of your password for your keystore file. - -By doing the above, this will ensure that you can use that exact same keystore file each time an updated version of **AAPS** is created. On average, there will be 2-3 AAPS updates required each year. - -In addition, **AAPS** provides the ability to export all your configuration settings. This ensures that you can safely recover your system while changing phones, upgrading/reinstalling the application with minimum disruption. - -## Troubleshootng - -Please feel free to reach out to the AAPS community if there is anything you feel unsure about - there is no such thing as a silly question! All users with various levels of experience are encouraged to ask questions as necessary. Response times to questions are usually quick, typically only a few hours due to the volume of **AAPS** users. - -a) check the documentation; b) ask AAPS facebook group (https://www.facebook.com/groups/AndroidAPSUsers); and c) ask our discord channel. - -## Section overview - -AAPS documentation is made up of the following Sections: - -[INSERT ONCE SECTIONS /SUB SECTIONS AGREED] ---- diff --git a/docs/CROWDIN/he/maintaining.md b/docs/CROWDIN/he/maintaining.md deleted file mode 100644 index 98164a09e49b..000000000000 --- a/docs/CROWDIN/he/maintaining.md +++ /dev/null @@ -1,28 +0,0 @@ -# Dummy - -## This is a dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - - -## This is another dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - - -## This is another another dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - diff --git a/docs/CROWDIN/he/optimizing.md b/docs/CROWDIN/he/optimizing.md deleted file mode 100644 index 98164a09e49b..000000000000 --- a/docs/CROWDIN/he/optimizing.md +++ /dev/null @@ -1,28 +0,0 @@ -# Dummy - -## This is a dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - - -## This is another dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - - -## This is another another dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - diff --git a/docs/CROWDIN/he/prepairing.md b/docs/CROWDIN/he/prepairing.md deleted file mode 100644 index 0e9c6518ea2a..000000000000 --- a/docs/CROWDIN/he/prepairing.md +++ /dev/null @@ -1,145 +0,0 @@ -# Prepairing - -## Guide to the Android APS doc - -### First Steps -Welcome. This is an introduction to aid beginners to the concept of Do-It-Yourself-APS (Android-Artificial-Pancreas-Systems “AAPS”) is commonly referred to as ‘looping’.. - -#### Safetys -“With great powers come great responsibilities…” - -AAPS is designed with an extensive set of safety features with limits imposed and gradually removed with completion of the [Objectives](https://androidaps.readthedocs.io/en/latest/Usage/Objectives.html) (predominately made up of multiple choice questions). An AAPS feature will be unlocked as the Objectives are successfully completed. This process will gradually allow the user to migrate from Open Loop to Closed Loop. - -This has been done to achieve the best possible experience with AAPS by preventing common mistakes new users tend to make when starting to loop. The safety parameters have been built upon typical errors and general trends AAPS developers have observed with new users. Mistakes can happen because the beginner is inexperienced and too eager to get started with AAPS or has overlooked the required materials. Do not worry, we have all been there! - -#### Key Principles - -The key principles and concepts of looping must be understood by the user before using AAPS. This is achieved by investing your personal time into reading the AAPS documentation, and completing the [Objectives](https://androidaps.readthedocs.io/en/latest/Usage/Objectives.html) which is aimed to provide you with a solid platform for safe and effective use of AAPS. The volume of AAPS documentation may seem overwhelming at first but be patient and trust the process - with the proper approach, you'll get there! The overall process will depend upon the beginner’s progress and completion of objectives which typically take between 6 to 9 weeks . - -#### Plan for hiccups - -At the preliminary stages of AAPS, you should expect to experience some hiccups whilst trying to fine tune your settings. AAPS’ glitches cannot be flushed out until the system is used in everyday life. Please plan accordingly and allow a sensible amount of time to troubleshoot and resolve such issues. - -#### Flexibility/Adaptability - -Success with AAPS requires a proactive approach, a willingness to reflect on the BG data and flexibility to make the necessary adjustments to AAPS in order to improve your outcomes. Just as it is nearly impossible to learn to play a sport by reading about the rules alone, the same can be said of AAPS. - -#### Technology compatibility -There are limitations with AAPS as it is accessible for only certain types of insulin pumps or CGMs, and some technology may not be available for use in various countries. In order to avoid any disappointment or frustrations, please read [Component Set Up (Section E).](https://androidaps.readthedocs.io/en/latest/Configuration/BG-Source.html) - -#### App Build time -The time to build the AAPS (under Section D) depends on your level of expertise and technical ability. Typically for inexperienced users, it can take up to half a day or a full day (with help from the community) in order to build the AAPS. The process will significantly speed up as you become more experienced at building the AAPS.  - -To aid the build process there are sections dedicated for: - -- list of questions and answers for frequent errors that are likely to occur under [FAQs (Section](https://androidaps.readthedocs.io/en/latest/Getting-Started/FAQ.html) K); - -- “[How to install AAPS](https://androidaps.readthedocs.io/en/latest/Installing-AndroidAPS/Building-APK.html)? (Section D) which includes [Troubleshooting](https://androidaps.readthedocs.io/en/latest/Usage/troubleshooting.html) subsection. - - -#### Keystore & configuration settings export  file - -A “keystore” is a password encrypted file unique to your own copy of AAPS. Your android phone uses it to ensure that nobody else can upgrade your own copy without the keystore.In short, as part of the AAPS build, you should: - -1. save the your keystore file (.jks file used to sign your app) in a safe place; - -2. keep a note of your password for your keystore file. - - -By doing the above, this will ensure that you can use that exact same keystore file each time an updated version of AAPS is created. On average, there will be 2-3 updates to the AAPS required each year. In addition, AAPS provides the ability to [export all your configuration settings](https://androidaps.readthedocs.io/en/latest/Usage/ExportImportSettings.html). This ensures that you can safely recover your system while changing phones, upgrading/reinstalling the application with minimum disruption.  - -#### פתרון בעיות - -Please feel free to reach out to the AAPS community if there is anything you feel unsure about - there is no such thing as a silly question!  All users with various levels of experience are encouraged to ask questions as necessary. Response times to questions are usually quick, typically only a few hours due to the volume of AAPS users.  - -##### [check the documentation](https://androidaps.readthedocs.io/en/latest/index.html) - -##### [ask our facebook group](https://www.facebook.com/groups/AndroidAPSUsers/) - -##### [ask our discord channel](https://discord.com/channels/629952586895851530/629954570394533889) - -#### Section overview - -AAPS documentation is made up of the following Sections: - -##### [Getting started](https://androidaps.readthedocs.io/en/latest/Getting-Started/Safety-first.html) - -This is a must read to understand the general concept of what an artificial pancreas system is designed to do. - -##### [What do I need?](https://androidaps.readthedocs.io/en/latest/Module/module.html) - -This explains AAPS’ compatibility with CGMs (Continuous Glucose Monitors) and insulin pumps. It also provides a guide on the correct assembly of an AAPS system to ensure that it functions correctly in everyday life. - -##### How to install AAPS - -This section is the manual for building the AAPS. Strict adherence to the step-by-step instructions are required in order to successfully build the AAPS. Please take your time. - -##### [Component Setup](https://androidaps.readthedocs.io/en/latest/Configuration/BG-Source.html) - -This explains how to properly integrate each of the various different separate component parts into AAPS, as well as how to set them up to work as seamlessly as possible together. All components are listed under the separate sections: CGM/FGM, xDrip Settings, Pumps, Phones, Nightscout setup, and Smartwatches. The sensor (BG) values and control of the insulin pump are particularly important information to understand. - -##### Configuration - -This explains how to set and configure your ‘Profile’, ‘Insulin’, ‘BG Source’, ‘Pump’, ‘Sensitivity Detection’, ‘APS’, ‘Loop’, ‘Treatments’. - -##### AAPS Usage - -This section provides a breakdown of the features provided by AAPS. - -##### [General Hints](https://androidaps.readthedocs.io/en/latest/Usage/Timezone-traveling.html) - -Useful tricks on how to tackle looping issues such as time zones, and daylight saving (i.e. Spring Forward/ - Fall Back). - -##### [AAPS](https://androidaps.readthedocs.io/en/latest/Getting-Started/Screenshots.html) for Children - -This is designed for parents or caregivers who want to build an AAPS for their child. It also explains the extra features necessary in order to support and safely control your child’s AAPS remotely.

The concepts in this section should be fully understood in order to competently use this feature. - -##### פתרון בעיות - -This section contains links to help solve issues when building or using AAPS. - -##### FAQ - -This section addresses specific questions which tend to come up when building or using AAPS. - -##### [מילון מונחים](https://androidaps.readthedocs.io/en/latest/Getting-Started/Glossary.html) - -This contains a list of the acronyms (or short-term names) or defined terms developed specifically for AAP (for instance, the terms ‘ISF’ or ‘TT’ have special meanings in AAPS). - -##### [Where to go for help](https://androidaps.readthedocs.io/en/latest/Where-To-Go-For-Help/Background-reading.html)? - -This section is aimed to provide new users with links on resources in order to get help including accessing community support made up of both new and experienced users who can clarify questions, and resolve the usual pitfalls that come with AAPS. - -##### For Clinicians - -This is a section for the clinicians who have expressed interest in open source artificial pancreas technology such as AAPS, or for patients who want to share such information with their clinicians. | - -## what are we going to build? - -### An Android Phone Application - -At the core, AAPS is an android application running from a phone. You are going to build it from scratch by installing tools to download the sourcecode and build the actual application. - -### A reporting server NightScout (or Tidepool) - -In order to fully use AAPS properly you will want to setup a nightscout server. It is used to collect data from AAPS over time and possibly communicate to the application. It is required for parents who want to oversee their children AAPS sessions. It is also key to share data between clinicians and patients to perform analysis over time. - -## How long will it take? - -## Who might AAPS not be suitable for? - -## Where can I get help? - -## Requirements - -### medical - -### technical - -### personal - -### CGMs - -### Insulin Pump - -### Reporting (NS, Tidepool) \ No newline at end of file diff --git a/docs/CROWDIN/ko/Configuration/Dexcom.md b/docs/CROWDIN/ko/Configuration/Dexcom.md deleted file mode 100644 index cb267e23c069..000000000000 --- a/docs/CROWDIN/ko/Configuration/Dexcom.md +++ /dev/null @@ -1,32 +0,0 @@ -# Dexcom G6 - -## Basics first - -* Follow [general CGM hygiene recommendations](../Configuration/BG-Source#cgm-hygiene) -* [Special recommendations for Dexcom G6 and DIY systems](../Configuration/BG-Source#dexcom-g6-diy-systems) *For G6 transmitters manufactured after fall/end of 2018 please make sure to use one of the [latest nightly built xDrip+ versions](https://github.com/NightscoutFoundation/xDrip/releases). Those transmitters have a new firmware and latest stable version of xDrip+ (2019/01/10) cannot deal with it. - -## Setting sensor - -When setting sensor, it is recommended not to press the inserter too firmly in order to avoid bleeding. The sensor thread should not come into contact with blood. - -After setting the sensor, the transmitter can be clicked into the sensor holder. Caution! First click in the square side and then press down the round side. - -## Troubleshooting - -### Connection problems - -Bluetooth connection may be disturbed by other nearby Bluetooth devices such as blood glucose meters, headsets, tablets or kitchen devices such as microwave ovens or ceramic hobs. In this case xdrip does not display any BG values. When bluetooth connection is reestablished the data is backfilled. - -### Sensor Errors - -If recurring sensor errors occur try selecting a different body site to set your sensor. The sensor thread should not come into contact with blood. - -Often a "Sensor Error" can be corrected by immediate drinking and massage around the sensor! - -### Jumpy values - -You might try to change settings for noise blocking in xdrip (Settings - Inter-App Settings - Noise Blocking) i.e. "Block Very High noise and worse". See also [Smoothing BG data](../Usage/Smoothing-Blood-Glucose-Data-in-xDrip.md). - -### New transmitter with running sensor - -If you happen to change transmitter during a running sensor session you might try to remove the transmitter without damaging the sensor mount. A video can be found at . \ No newline at end of file diff --git a/docs/CROWDIN/ko/Configuration/EOFLOW.md b/docs/CROWDIN/ko/Configuration/EOFLOW.md deleted file mode 100644 index e697feadb732..000000000000 --- a/docs/CROWDIN/ko/Configuration/EOFLOW.md +++ /dev/null @@ -1,155 +0,0 @@ -# EOPatch2 Instruction Manual - -The patch requires the use of rapid-acting U-100 type insulin, such as NovoRapid or Humalog. Use a rapid-acting insulin that is suitable for you according to your doctor’s prescription and inject the prescribed dosage. - -The smallest injectable dose of insulin when using the patch is 0.05 U. The Profile BAS should therefore be set at a minimum value of 0.05 U/hr or more and an interval of 0.05 U/hr, as otherwise there may be an error between the estimated total infusion amount in the Profile and the actual infusion amount in the patch. Likewise, the bolus must also be set and infused with a minimum infusion volume of 0.05 U. - -## Pump Setup -1. On the AndroidAPS home screen, click the hamburger menu in the upper left corner and go to Config Builder. -1. Select 'EOPatch2' in the Pump section. -1. Press the Back key to return to the home screen. - -![Bild1](../../images/EOPatch/Bild1.png) ![Bild2](../../images/EOPatch/Bild2.png) - -## Settings -Select EOPATCH2 at the top of the home screen to go to the EOPATCH2 tab. - -Select the EOPatch2 Preferences menu by clicking the three dots in the upper right corner. - -The EOPatch2 Preferences menu offers a menu to set 3 types of notifications. - -### Low reservoir Alerts -A warning appears when the amount of insulin remaining in the reservoir reaches the set value or less while using the patch. It can be set from 10 to 50U in 5U increments. - -### Patch expiration Reminder -This is a reminder to notify you of the time remaining before the current patch expires. It can be set from 1 to 24 hours in 1 hour increments. The initial setting value is 4 hours. - -### Patch buzzer Reminder -This is a reminder function for injections other than basal injection. If you are using an (extended) bolus injection or a temporary basal injection, the patch will make a buzzer sound when the injection starts and when the injection is complete. The initial setting value is Off. - -![Bild3](../../images/EOPatch/Bild3.png) - -## Connecting the Patch - -### Move to patch connection screen - -Select EOPATCH2 at the top of the home screen and click the ACTIVATE PATCH button at the bottom left. - -![Bild4](../../images/EOPatch/Bild4.png) - -### Connecting the patch -Insert the syringe needle into the insulin inlet on the patch and then slowly push the piston to inject the insulin. When insulin is filled with more than 80U, the patch makes a booting sound (1 buzzer) and boots. After confirming the buzzer sound, click the START PAIRING button on the screen. - -[Warning] - -- Do not turn the needle action lever until instructed. It can cause serious problems during injection or safety checks otherwise. -- The amount of insulin that can be injected into the patch is 80~200U. If you inject less than 80U into the patch initially, the patch will not work. -- Take the insulin to be put into the patch from the refrigerator and leave it at room temperature for 15 to 30 minutes beforehand. The temperature of the insulin to be injected must be at least 10°C. - -![Bild5](../../images/EOPatch/Bild5.png) - -### patch pairing -The Patch pairing screen will be displayed, and pairing will be attempted automatically. If communication is successful, the Bluetooth pairing request notification appears. Click OK and when the Bluetooth pairing request notification appears a second time with the authentication code, select OK again. - -[Warning] - -- For pairing, the patch and the smartphone must be located within 30 cm of each other. -- After the patch booting is completed, the patch will beep every 3 minutes until the pairing is complete. -- After booting the patch, the patch application must be completed via the app within 60 minutes. If the application cannot be completed within 60 minutes, the patch should be discarded. - -![Bild6](../../images/EOPatch/Bild6.png) ![Bild7](../../images/EOPatch/Bild7.png) ![Bild8](../../images/EOPatch/Bild8.png) - - -### patch preparation -After removing the adhesive tape of the patch, check if the needle is sticking out. If there are no problems with the patch, click NEXT. - -![Bild9](../../images/EOPatch/Bild9.png) - -### Patch attachment -Insulin should be injected in a spot with subcutaneous fat but few nerves or blood vessels, so it is recommended to use the abdomen, arm, or thigh for the patch attachment site. Choose a patch attachment site and apply the patch after disinfecting the location. - -[Warning] - -- Make sure to straighten the side of the patch tape attached to the body evenly, so that the patch adheres completely to the skin. -- If the patch does not stick completely, air may enter between the patch and the skin, which can weaken the adhesive strength and waterproof effect of the patch. - -![Bild10](../../images/EOPatch/Bild10.png) - -### Safety Check -When patching is complete, touch Start Safety Check. When the safety check is completed, the patch will beep once. - -[Warning] - -- For safe use, do not turn the needle action lever until the safety check has been completed. - -![Bild11](../../images/EOPatch/Bild11.png) ![Bild12](../../images/EOPatch/Bild12.png) - - -### Inserting the needle -The needle is inserted by holding around the patch and turning the needle action lever more than 100° in the upward direction of the lever. There is a buzzer sound when the needle is inserted correctly. Turn the needle action lever further clockwise to release the lever. Click NEXT. - -[Caution] - -- If you go to the next step without the buzzer sounding, a needle insertion error warning will appear. - -## Discarding the patch -Patches must be replaced in the case of low insulin levels, usage expiration, and defects. The recommended usage period for each patch is 84 hours after booting the patch. - -### Discarding the patch -Select EOPATCH2 at the top of the home screen and click the DISCARD/CHANGE PATCH button at the bottom. On the next screen, click the DISCARD PATCH button. A dialog box appears to confirm once more and if you select the DISCARD PATCH button, the disposal is completed. - -![Bild13](../../images/EOPatch/Bild13.png) ![Bild14](../../images/EOPatch/Bild14.png) ![Bild15](../../images/EOPatch/Bild15.png) ![Bild16](../../images/EOPatch/Bild16.png) - -## Suspending and Resuming Insulin Delivery -Suspending insulin delivery also cancels both extended bolus and temporary basal. When resuming insulin delivery, the canceled extended bolus and temporary basal will not be resumed. And when insulin delivery is suspended, the patch will give a sound every 15 minutes. - -### Suspending insulin delivery -Select EOPATCH2 at the top of the home screen and click the SUSPEND button at the bottom right. When you select CONFIRM in the confirmation box, a time selection box appears. If you select the CONFIRM button after selecting the time, the insulin delivery will be suspended for the set amount of time. - -![Bild17](../../images/EOPatch/Bild17.png) ![Bild18](../../images/EOPatch/Bild18.png) ![Bild19](../../images/EOPatch/Bild19.png) - - -### Resuming insulin delivery -Select EOPATCH2 at the top of the home screen and click the RESUME button at the bottom right. Insulin delivery will resume by selecting CONFIRM in the confirmation dialog box. - -![Bild20](../../images/EOPatch/Bild20.png) ![Bild21](../../images/EOPatch/Bild21.png) - -## Alarms/Warnings - -### Alarm - -Alarms are issued for emergency situations of the highest priority and require immediate action. The alarm signal does not disappear or time out until it is acknowledged. An alarm occurs when there is a problem with the patch being used, so there may be cases where the patch in use needs to be discarded and replaced with a new patch. The warning is displayed as a dialog box and switching to another screen is not possible until processing is completed. - -![Bild22](../../images/EOPatch/Bild22.png) ![Bild23](../../images/EOPatch/Bild23.png) - -The different types of alarms are explained below. - -| Alarms | Explanation | -| -------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| Empty reservoir | Occurs when the patch’s reservoir runs out of insulin. | -| Patch expired | Occurs when the patch usage time has expired, and no further insulin injections are possible. | -| Occlusion | Occurs when it appears that the patch's insulin inlet is clogged. | -| Power on self-test failure | Occurs when the patch finds an unexpected error during the post-boot self-test process. | -| Inappropriate temperature | Occurs when the patch is outside the normal operating temperature range during patch application and use. To deal with this alarm, move the patch to an appropriate operating temperature (4.4 to 37°C) condition. | -| Needle insertion Error | Occurs when needle insertion is not normal during the patch application process. Check that the needle insertion edge of the patch and the needle activation button are in a straight line. | -| Patch battery Error | Occurs just before the patch’s internal battery runs out and powers off. | -| Patch activation Error | Occurs when the app fails to complete the patching process within 60 minutes after the patch is booted. | -| Patch Error | Occurs when the patch encounters an unexpected error while applying and using the patch. | - -### Warning - -A warning occurs in a medium or low-priority situation. When a warning occurs, it is displayed as a notification in the Overview screen. - -![Bild24](../../images/EOPatch/Bild24.png) - -The different types of warnings are explained below. - -| Warnings | Explanation | -| ---------------------------- | ------------------------------------------------------------------------------------------------------------------------------------- | -| End of insulin suspend | Occurs when the time set by the user has elapsed after the insulin infusion suspension has been completed. | -| Low reservoir | Occurs when the remaining amount of insulin in the patch is below the set amount. | -| Patch operating life expired | Occurs when the patch usage period is over. | -| Patch will expire soon | Occurs 1 hour before the patch must be discarded. | -| Incomplete Patch activation | Occurs when more than 3 minutes have elapsed due to an interruption during patch application in the stage after pairing is completed. | -| Patch battery low | Occurs when the patch's battery is low. | - diff --git a/docs/CROWDIN/ko/Configuration/Hardware/index.md b/docs/CROWDIN/ko/Configuration/Hardware/index.md deleted file mode 100644 index 49730690e708..000000000000 --- a/docs/CROWDIN/ko/Configuration/Hardware/index.md +++ /dev/null @@ -1,27 +0,0 @@ -# Hardware-Configuration - -## 환경설정 - -## BG Source - -- [BG Source](../BG-Source.md) -- [xDrip+ Settings](../xDrip.md) -- [Dexcom G6 hints](../Dexcom.md) -- [Smoothing blood glucose data](../../Usage/Smoothing-Blood-Glucose-Data-in-xDrip.md) - -## Pumps - -- [Dana-R pump](../DanaR-Insulin-Pump.md) -- [Dana-RS pump](../DanaRS-Insulin-Pump.md) -- [Accu-Chek Combo pump](../Accu-Chek-Combo-Pump.md) -- [Accu-Chek Insight pump](../Accu-Chek-Insight-Pump.md) -- [Medtronic pump](../MedtronicPump.md) - -## 스마트폰 - -- [Jelly Pro Settings](../../Usage/jelly.md) -- [Huawei Settings](../../Usage/huawei.md) - -## Smartwatch - -- [Watchfaces](../Watchfaces.md) diff --git a/docs/CROWDIN/ko/Getting-Started/ClosedLoop.md b/docs/CROWDIN/ko/Getting-Started/ClosedLoop.md deleted file mode 100644 index 28f506f9ec56..000000000000 --- a/docs/CROWDIN/ko/Getting-Started/ClosedLoop.md +++ /dev/null @@ -1,55 +0,0 @@ -# Closed loop 시스템이란 어떤 것일까요? - -![AAPS는 오토파일럿과 유사합니다.](../images/autopilot.png) - -인공 췌장 closed loop 시스템은 당뇨병 관리를 좀 더 편리하게 하기 위해 다양한 구성 요소들을 결합한 것입니다. In her great book [Automated Insulin Delivery](https://www.artificialpancreasbook.com/) Dana M. Lewis, one of the founders of the open source closed loop movement, calls it an ["autopilot for your diabetes"](https://www.artificialpancreasbook.com/3.-getting-started-with-your-aps). 과연 이게 무엇을 의미할까요? - -**Autopilot in an aircraft** - -오토파일럿이 모든 작업을 수행하는 것은 아니며, 따라서 비행하는 전체 시간 동안 조종사가 잠을 잘 수 있게 해주는 것은 아닙니다. 그것은 조종사들의 일을 용이하게 해주는 것입니다. 이는 항공기와 비행 상태를 계속해서 모니터링해야 하는 부담을 줄여줍니다. 이것은 조종사가 영공을 살피며 오토파일럿 기능들을 제어하는 것에 집중할 수 있도록 도와줍니다. - -오토파일럿은 다양한 센서로부터 신호들을 수신하고, 컴퓨터가 파일럿의 설정에 따라 이를 평가한 다음, 필요한 조정을 시행합니다. 조종사는 계속적인 조정에 대해 걱정하지 않아도 됩니다. - -**Closed Loop System** - -인공 췌장 closed loop 시스템은 오토파일럿과 유사하다고 볼 수 있습니다. 이 시스템이 모든 관리를 대신 해주는 것이 아니며, 사용자는 계속해서 당뇨병 관리에 신경써야합니다. Closed loop 시스템은 CGM/FGM의 센서 데이터와 사용자의 당뇨병 관리 인자(basal 양, 인슐린 민감도 인자 (ISF), 인슐린 탄수화물 비율 (IC) 등)을 결합하여 작동합니다. From this it calculates treatment suggestions and implements these permanent small adjustments in order to keep your diabetes within the target range and to relieve you. 이것은 당뇨병 관리에 "함께 해줌으로써" 사용자의 삶에 시간 여유를 만들어 줍니다. - -우리가 사람 관리자 없이 오토파일럿만 있는 비행기에 탑승하고 싶지 않은 것처럼, closed loop 시스템은 당뇨병 관리를 도와주지만 반드시 사용자의 도움이 필요합니다! **Even with a closed loop you can't just forget your diabetes!** - -오토파일럿이 조종사의 설정 뿐만 아니라 센서 값들에 의존하는 것과 같이, AAPS에서도 적절한 basal 양, ISF, 인슐린 탄수화물 비율 (CR) 등을 적절하게 입력해야 closed loop 시스템이 사용자를 성공적으로 보조할 수 있습니다. - -## 인공 췌장 closed loop 시스템의 오픈 소스 - -현재는 대표적인 세 종류의 오픈 소스 closed loop 시스템을 사용할 수 있습니다: - -### AndroidAPS (AAPS) - -AAPS is described in detail in [this documentation](./WhatisAndroidAPS.html). 이는 안드로이드 스마트폰을 사용하여 인슐린 펌프 사용을 계산하고 제어합니다. It is in strong collaboration with OpenAPS (i.e. they share algorithms). - -Compatible [pumps](../Hardware/pumps.md) are: - -- [DanaR](../Configuration/DanaR-Insulin-Pump.md) / [DanaRS & Dana-i](../Configuration/DanaRS-Insulin-Pump.html) -- [아큐-첵 콤보](../Configuration/Accu-Chek-Combo-Pump.md) -- [Accu-Chek Insight](../Configuration/Accu-Chek-Insight-Pump.md) -- [Diaconn G8](../Configuration/DiaconnG8.md) -- [Omnipod DASH](../Configuration/OmnipodDASH.md) -- [Omnipod Eros](../Configuration/OmnipodEros.md) -- some old [Medtronic pumps](../Configuration/MedtronicPump.md) - -### OpenAPS - -[OpenAPS](https://openaps.readthedocs.io) was the first Open Source Closed Loop System. Raspberry Pi나 Intel Edison 같은 작은 컴퓨터를 사용합니다. - -호환 가능한 펌프는 다음과 같습니다: - -- some old Medtronic pumps - -### iOS 용 loop - -[Loop for iOS](https://loopkit.github.io/loopdocs/) is the Open Source Closed Loop System to be used with Apple iPhones. - -호환 가능한 펌프는 다음과 같습니다: - -- Omnipod DASH -- Omnipod Eros -- some old Medtronic pumps diff --git a/docs/CROWDIN/ko/Getting-Started/GlossaryTest.md b/docs/CROWDIN/ko/Getting-Started/GlossaryTest.md deleted file mode 100644 index 7123a556a42b..000000000000 --- a/docs/CROWDIN/ko/Getting-Started/GlossaryTest.md +++ /dev/null @@ -1,391 +0,0 @@ -# 용어 - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Term상세설명see alsomore details @
AAPSAndroidAPS - artifical pancreas system  
AMAadvanced meal assist - advanced algorithm to handle carbsMA / SMBWiki - AMA
Android autodisplay AAPS notifications on your car's compatible in-dash information and entertainment head unit Wiki - android auto
APKsoftware installation file (Android application package) Wiki - Building APK
Autosenscalculation of sensitivity to insulin as a result of exercise, hormones etc. DIABETTECH - Autosens
Azurecloud computing platform to host Nightscout dataHeroku / NightscoutAzure
BATstatus light low battery on homescreenCAN / RES / SENPreferences
Screenshots
BGblood glucose  
BGIblood glucose interaction -degree to which BG 'should' be rising or falling based on insulin activity alone  
혈당 소스Where do your glucose values come from?CGM / FGMWiki - BG source
Blukon Nightreaderbluetooth transmitter to use Freestyle Libre as CGMBlueReader / MiaoMiaoAmbrosia Blukon Nightreader
BRbasal양  
CAGEcanula age - displayed in Nightscout if information was entered in actions tab / menu tab or through AAPS actions tab 'prime'Nightscout 
CANstatus light overdue canula change on homescreenBAT / RES / SENPreferences
Screenshots
CGMcontinuous glucose monitor  
Closed Loopclosed-loop systems make automatic adjustments to basal delivery, without needing user-approval, based on an algorithmOpen loopWiki closed loop
COBcarbs on board  
DIAduration of insulin action Wiki insulin types
DIABETTECH - DIA
DSTdaylight savings time Wiki DST
eCarbs"extended carbs" - carbs split up over serveral hours (i.e. lot of fat/protein)
extended boluses you might know from regular pump therapy do not make much sense when looping		SMBWiki - eCarbs
eCarbs use case
FGMflash glucose monitor (Freestyle Libre) Wiki - BG source
gitversion-control system for tracking changes in computer files and coordinating work on those files
-> neccessary for APK updates		 Wiki - update APK
Githubweb-based hosting service for version control using Git
-> storage of source code		 Github AndroidAPS
Glimpapp to collect values from Freestyle Libre Nightscout with Glimp
Herokucloud computing platform to host Nightscout dataAzure / NightscoutHeroku
IC (or I:C)insulin to carb ratio (How many carbs are covered by one unit of insulin?)  
IOBinsulin on board - insulin active in your body  
ISFinsulin sensitivity factor - the expected decrease in BG as a result of one unit of insulin  
LGSLow Glucose Suspend
AAPS will reduce basal if blood glucose is dropping. But if blood glucose is rising then it will only increase basal if the IOB is negative (from a previous LGS), otherwise basal rates will remain the same as your selected profile. You may temporarily experience spikes following treated hypos without the ability to increase basal on the rebound.		objective 6 
LineageOSfree and open-source operating system for smartphones etc.
alternative OS for smartphones not running Android 8.1 (Oreo)
(when using Accu-Chek Combo)		 Wiki - Combo pump
Log filesrecord of all AAPS actions (useful for trubbleshooting and debugging) Wiki - log files
maxIOBsafety feature - maximum total IOB AAPS can't go over Wiki - maxIOB
Wiki - SMB
MiaoMiaobluetooth transmitter to use Freestyle Libre as CGMBlueReader / Blukon NightreaderMiaoMiao
min_5m_carbimpactsaftey feature - default carb decay at times when carb absorption can’t be dynamically worked out based on your bloods reactions Wiki - config builder
Nightscoutopen source project to access and report CGM dataNightscout ReporterNightscout
NS Clientpart of AAPS to connect to your Nightscout site Wiki - NS Client
Nightscout ReporterTool from fellow looper to generate PDFs reports from Nightscout dataNightscoutNightscout Reporter
NS Reporter @ Facebook
Objectiveslearning program within AAPS guiding you step by step from open to closed loop Wiki - objectives
OpenAPSopen artificial pancreas system
APS run on small computers (i.e. Raspberry Pie)
AAPS uses some of the OpenAPS features		 OpenAPS docs
Open Loopsystem will suggest recommended adjustments which have to be performed manually on the pumpClosed LoopWiki - config builder
Oref0 / Oref1sensitivity detection
"reference design implementation version 0/1" - the key algorithm behind OpenAPS		 Wiki - sensitivity detection
Peak timetime of maximum effect of insulin given Wiki - config builder
PHpump history (entry in treatments tab) Screenshots
Predictionspreditions for BG in the future based on different calculations Wiki - predition lines
프로파일basic treatment settings (basal rate, DIA, IC, ISF, BG target)
can be defined locally or through Nightscout		NightscoutWiki - profile
프로파일 변경(temporary) change of profile used or percentual increase/decrease Wiki - profile switch
RESstatus light overdue reservoir change on homescreenBAT / CAN / SENPreferences
Screenshots
RileyLinkopen source hardware device to bridge Bluetooth Low Energy (BLE) to 916MHz wireless communication (used for old Medtronic pumps)OpenAPS 
SAGEsensor age - displayed in Nightscout if information was entered in the actions tab / menuNightscout 
SENstatus light sensor change on homescreenBAT / CAN / RESPreferences
Screenshots
Sensivity detectioncalculation of sensitivity to insulin as a result of exercise, hormones etc. DIABETTECH - Autosens
Sensor noiseunstable CGM readings leading to "jumping" values Wiki - sensor noise
SMBsuper micro bolus
advanced feature for faster BG adjustment		UAMWiki - SMB
Super bolusshift of basal to bolus insulin for faster BG adjustment John Walsh - The Super Bolus
TBBtotal base basal (sum of basal rate within 24 hours)  
TBRtemporary basal rate  
TDDtotal daily dose (bolus + basal per day)  
TTtemporary target
temporary increase/decrease of BG target (range)		 Wiki - temp targets
UAMunannounced meals - detection of significant increase in glucose levels due to meals, adrenaline or other influences and attempt to adjust this with SMBSMBWiki - SMB
Virtual pumpoption to try AAPS functions or for PWD using a pump model with no AndroidAPS driver for loopingOpen Loop 
배경화면AndroidAPS background imagesee phones page
xDrip / xDrip+open source software to read CGM systems xDrip+
xDrip
Zero-temptemporary basal rate with 0% (no basal insulin delivery)  
See also https://openaps.readthedocs.io/en/latest/docs/Resources/glossary.html
diff --git a/docs/CROWDIN/ko/Getting-Started/Safety-first.md b/docs/CROWDIN/ko/Getting-Started/Safety-first.md deleted file mode 100644 index 5c35d1bac6f2..000000000000 --- a/docs/CROWDIN/ko/Getting-Started/Safety-first.md +++ /dev/null @@ -1,41 +0,0 @@ -# 가장 중요한 안전 유의사항 - -**When you decide to build your own artificial pancreas, it's always important to think about security and safety, and to understand the impact of all your actions** - -## 포괄적인 정보 - -- AAPS is a just a tool to help you manage diabetes, it is not a fully automated system you can install and forget! -- Do not assume that AAPS will never make mistakes. This device is taking control of your insulin delivery: Watch it all the time, understand how it works, and learn how to interpret its actions. -- Remember that, once paired, the phone can instruct the pump to do anything. Only use this phone for AAPS and, if being used by a child, essential communications. 사용자의 시스템을 방해할 수 있는 트로이 목마, 바이러스 또는 로봇과 같은 악성 소프트웨어를 가져올 수 있는 불필요한 앱이나 게임(!!!)을 설치하지 마십시오. -- Install all security updates provided by your phone manufacturer and Google. -- You might also need to change your diabetes habits as you change your therapy by using a closed loop system. 예를 들어, some people report, they need less hypo treatments as AAPS has already reduced insulin. - -## SMS 통신기 - -- AAPS allows you to control a child's phone remotely via text message. SMS 통신기를 활성화 했다면, 원격 명령어를 사용하기 위해 설정된 폰(부모폰)을 도난 맞을 수도 있다는 사실에 항상 유념하셔야 합니다. 따라서 최소한 PIN 코드 이상의 보안으로 폰을 보호하십시오. -- AAPS will also inform you by text message if your remote commands, such as a bolus or a profile change, have been carried out. 수신 폰 중 하나가 도난 당할 경우를 대비하여, 적어도 2개 이상의 다른 폰에 확인 문자 메시지가 전송되도록 설정하는 것을 권장합니다. - -(Safety-first-aaps-can-also-be-used-by-blind-people)= -## AAPS can also be used by blind people - -On Android devices TalkBack is part of the operating system. It is a program for screen orientation via voice output. With TalkBack you can operate your smartphone as well as AAPS blind. - -We users create the AAPS app ourselves with Android Studio. Many use Microsoft Windows for this purpose, where there is the Screenreader analogous to TalkBack. Since Android Studio is a Java application, the "Java Access Bridge" component must be enabled in the Control Panel. Otherwise, the screen reader of the PC will not speak in Android Studio. - -To do this, please proceed as follows: - -- Press WINDOWSTASTE and enter "Control Panel" in the search field, open with Enter. It opens: "All Control Panel Items". -- Press the letter C to get to "Center for Ease of Use", open with Enter. -- Then open "Use computer without a screen" with Enter. -- There, at the bottom, you will find the checkbox "Enable Java Access Bridge", select it. -- Done, just close the window! The screen reader should work now. - -```{note} -**IMPORTANT SAFETY NOTICE** - -The foundation of AAPS safety features discussed in this documentation is built on the safety features of the hardware used to build your system. 인슐린 자동 주입 시스템을 사용할 시에는 완벽하게 작동한다고 증명하는 테스트와 FDA 또는 CE 승인을 받은 인슐린 펌프과 CGM만을 사용하는 것이 매우 중요합니다. 이러한 구성요소에 대한 하드웨어 또는 소프트웨어의 변형은 예기치 않은 인슐린 투약을 야기하여 사용자에게 상당한 위험을 초래할 수 있습니다. If you find or get offered broken, modified or self-made insulin pumps or CGM receivers, *do not use* these for creating an AAPS system. - -또한, 펌프 또는 CGM을 사용할 때에는 원래 공급되는 물품 즉 제조업자에 의해 승인된 삽입기, 캐뉼러 및 인슐린 용기만을 사용하는 것이 매우 중요합니다. 검증이 되지 않고 변형된 물품을 사용하는 경우에는 CGM의 부정확성과 인슐린의 투약 오류가 발생할 수 있습니다. 인슐린은 남용되면 매우 위험하니 물품들을 해킹하여 사용하는 것과 같이 본인의 목숨을 가지고 노는 행위와 같은 행동들은 삼가해주시기 바랍니다. - -마지막으로는 계산할 수 없을 정도로 혈당을 낮추기 때문에 SGLT-2 억제제 (글 리플로 진)을 절대 사용하면 안된다. 혈당을 올리기 위해 기저양(basal rate)을 낮추는 시스템과 병행하는 것은 글 리폴로 진으로 인해 매우 위헙합니다. 오히려 혈당이 오르지 않을 수 있으며 인슐린 부족의 위험한 상태까지 올 수 있습니다. -``` diff --git a/docs/CROWDIN/ko/Getting-Started/Sample-Setup.md b/docs/CROWDIN/ko/Getting-Started/Sample-Setup.md deleted file mode 100644 index e2f233ad1d07..000000000000 --- a/docs/CROWDIN/ko/Getting-Started/Sample-Setup.md +++ /dev/null @@ -1,151 +0,0 @@ -# Sample setup: Samsung S7, Dana RS, Dexcom G6 and Sony Smartwatch - -![샘플 설정](../images/SampleSetup.png) - -## 상세설명 - -이 셋업에서는 삼성갤럭시 S7이 Loop를 제어하기 위해 사용되었습니다. The slightly modified Dexcom App reads glucose values from the Dexcom G6 CGM. AndroidAPS is used to control the Dana RS insulin pump from Korean manufacturer SOOIL via bluetooth. 추가적인 장치는 요구되어지지 않습니다. - -Dexcom앱은 제한된 알림기능을 제공함에 따라서, 오픈소스앱 xDrip+는 하이/로우 알림기능 외 개인적인 알람기능을 제공하게 됩니다. - -추가적으로 안드로이드 스마트워치 또한 사용될 수 있습니다. 이 번 예시에서는 소니 스마트워치3 (SWR50)이 안드로이드 앱에서 혈당치를 보여주도록 설명됩니다. 스마트워치는 AndroidAPS을 제어할 수도 있습니다. (예를 들면 Bolus 주입도 할 수 있습니다.) - -시스템은 오프라인에서 작동됩니다. 이는 데이터 연결을 위해서 스마트폰이 인터넷에 연결될 필요가 없음을 의미합니다. - -그럼에도 불구하고, 데이트는 인터넷 연결이 될 때, 자동으로 Nightscout에 업로드됩니다. 이렇게 함에 따라서, 병원방문시 사용되는 또는 가족들과 자료를 공유할 수 있는 다양한 보고서를 만들수 있습니다. 사전에 설정된 Wi-fi를 통해서 Nightscout로 데이터를 보낼 수도 있으며, 이는 기존의 Nightscout리포트를 갱신할 수 있습니다. - -## 요구사양. - -1. 삼성 갤럭시 S7 - - * Alternatives: see [list of tested phones and watches](https://docs.google.com/spreadsheets/d/1gZAsN6f0gv6tkgy9EBsYl0BQNhna0RDqA9QGycAqCQc/edit) for AndroidAPS - -2. [DanaRS(다나알에스)](http://www.sooil.com/eng/product/) - - * 대안: - * [아큐-첵 콤보](../Configuration/Accu-Chek-Combo-Pump.md) - * [Accu-Chek Insight (아큐첵 인사이트)](../Configuration/Accu-Chek-Insight-Pump.md) - * [DanaR (다나알)](../Configuration/DanaR-Insulin-Pump.md) - * [Some old Medtronic pumps (additionally needed: RileyLink/Gnarl hardware, Android Phone with bluetooth low energy / BLE-chipset)](../Configuration/MedtronicPump.md) - * Other pumps might be available in the future, see [future possible pump drivers](Future-possible-Pump-Drivers.md) for details. - -3. [Dexcom G6](https://dexcom.com) - - * Alternatives: see list of possible [BG sources](../Configuration/BG-Source.md) - -4. 옵션: 소니 스마트워치3 (SWR50) - - * Alternatives: All [watches with Google Wear OS](https://wearos.google.com/intl/de_de/#find-your-watch) should work fine, for details see [list of tested phones and watches](https://docs.google.com/spreadsheets/d/1gZAsN6f0gv6tkgy9EBsYl0BQNhna0RDqA9QGycAqCQc/edit) for AndroidAPS (OS must be Android Wear) - -## Nightscout 설정 - -[Nightscout 설정](../Installing-AndroidAPS/Nightscout.md)을 참조하세요. - -## 컴퓨터 설정 - -To be able to create an Android app from the freely available AAPS open source code you need Android Studio on your computer or notebook (Windows, Mac, Linux). A detailed instruction can be found at [building the APK](../Installing-AndroidAPS/Building-APK.md). - -Please be patient when installing Android Studio as the software downloads a lot of additional data once installed on your computer. - -## Smartphone setup - -![Smartphone](../images/SampleSetupSmartphone.png) - -### Check smartphone firmware - -* Menu > Settings > Phone info > Software info: At least "Android-Version 8.0" (successfully tested up to Android version 8.0.0 Oreo - Samsung Experience Version 9.0) -* For firmware update: menu > Preferences > software update - -### Allow installation from unknown sources - -Menu > Settings > Device security > Unknown sources > slider to right side (= active) - -For security reasons this setting should be set back to inactive once the installation of all apps described here has been completed. - -### Enable Bluetooth - -1. Menu > Settings > Connections > Bluetooth > slider to right side (= active) -2. Menu > Settings > Connections > Location > slider to right side (= active) - -Location services ("GPS") must be activated in order for Bluetooth to work properly. - -### Install Dexcom App (modified version) - -![Dexcom App patched](../images/SampleSetupDexApp.png) - -The original Dexcom app from the Google Play Store will not work because it does not broadcast the values to other apps. Therefore, a version slightly modified by the community is required. Only this modified Dexcom app can communicate with AAPS. Additionally the modified Dexcom App can be used with all Android smartphones not only the ones in [Dexcom's compatibility list](https://www.dexcom.com/dexcom-international-compatibility). - -To do this perform the following steps on your smartphone: - -1. If the original Dexcom app is already installed: - * Stop sensor - * Uninstall app via Menu > Settings > Apps > Dexcom G6 Mobile > Uninstall -2. Download and install the [BYODA Dexcom ap](../Hardware/DexcomG6.md#if-using-g6-with-build-your-own-dexcom-app) -3. Start modified Dexcom G6 app, activate/calibrate the sensor according to the given instructions and wait until the warm-up phase is finished. -4. Once the modified Dexcom app shows actual glucose value, setup the warnings (hamburger menu on top left side of the screen) as follows: - * Urgent low `55mg/dl` / `3.1mmol/l` (cannot be disabled) - * Low `OFF` - * High `OFF` - * Rise rate `OFF` - * Fall rate `OFF` - * Signal loss `OFF` - -## Install AndroidAPS - -1. Follow the instructions to [build the APK](../Installing-AndroidAPS/Building-APK.md#generate-signed-apk) -2. [Transfer](../Installing-AndroidAPS/Building-APK.md#transfer-apk-to-smartphone) the generated APK to your phone -3. [Configure AndroidAPS](../Configuration/Config-Builder.md) according to your needs using the setup assistant or manually -4. In this sample setup we used (among others) - -* BG source: `Dexcom G6 App (patched)` -- click cock-wheel and activate `Upload BG data to NS` and `Send BG data to xDrip+` (see [BG source](../Configuration/BG-Source.md)) - -![G5 Settings](../images/SampleSetupG5Settings.png) - -* NS Client activated (see [Nightscout setup](../Installing-AndroidAPS/Nightscout.md)) - -## Install xDrip+ - -xDrip+ is another mature open source app that offers countless possibilities. In this setup, contrary to what the developers first wrote the app for, xDrip+ is not used to collect glucose data from the Dexcom G6, but only to output alarms and to display the current glucose value including the curve on the Android home screen in the widget. With xDrip+ the alarms can be set much more individually than with the Dexcom software, AAPS or Nightscout (no limitation in the selection of sounds, different alarms depending on day/night time etc.). - -1. Download the latest stable APK version of xDrip+ with your smartphone - not the version from the Google Play Store! -2. Install xDrip+ by selecting the downloaded APK file. -3. Start xDrip+ and make the following settings (hamburger menu at top left) - * Settings > Alarms and Alerts > Glucose Level Alert List > Create Alerts (high and low) according to your needs. - * The existing alarms can be changed with a long press on the alarm. - * Settings > Alarms and Alerts > Calibration Alerts: disabled (reminded via the modified Dexcom app) - * Settings > Hardware Data Source > 640G/EverSense - * Settings > Inter-app settings > Accept Calibrations > `ON` - * Menu > Start sensor (is only "pro forma" and has nothing to do with the running G6 sensor. This is necessary otherwise an error message will appear regularly.) - -For more information about xDrip+, see here [BG source page](../Configuration/BG-Source.md). - -### Example of an alarm setup - -The "Urgent low alarm" (below 55 mg/dl resp. 3,1 mmol) is a standard alarm from the modified Dexcom app that cannot be disabled. - -![xDrip alarms](../images/SampleSetupxDripWarning.png) - -Tip for meetings / church visits / cinema etc..: - -If "Do not disturb" mode is activated in the Samsung Galaxy S7 (Menu > Settings > Sounds and vibration > Do not disturb: slider to right side (= active)), the phone only vibrates during urgent low alarm and does not issue an acoustic warning. For the other alarms set up via xDrip+ you can select whether the silent mode should be ignored (acoustic sound played) or not. - -## Disable power saving option - -On your Samsung Galaxy S7 go to Menu > Settings > Device Maintenance > Battery > Unmonitored Apps > + Add apps: Select the apps AndroidAPS, Dexcom G6 Mobile, xDrip+ and Android Wear (if smartwatch is used) one after the other - -## Optional: Setup Sony Smartwatch 3 (SWR50) - -With an Android Wear smartwatch life with diabetes can be made even more inconspicuous. The watch can be used to display the current glucose level, the status of the loop etc. on the wrist. 스마트워치는 AndroidAPS을 제어할 수도 있습니다. (예를 들면 Bolus 주입도 할 수 있습니다.) To do this, double tap the CGM value of the AAPSv2 watchface. The SWR50 usually runs for a full day until the battery needs to be recharged (same charger as the Samsung Galaxy S7: microUSB). - -![스마트 워치](../images/SampleSetupSmartwatch.png) - -Details about the information displayed on the watchface can be found [here](../Configuration/Watchfaces.md). - -* Install the app "Android Wear" on your smartphone via the Google Play Store and connect the smartwatch according to the instructions there. -* In AAPS choose hamburger menu (top left corner) > Config Builder > General (at the bottom of the list) > Wear > activate on left side, click cock wheel > Wear settings and activate `Controls from Watch` -* On your smartwatch: Long press display to change watchface and select `AAPSv2` -* If necessary restart both devices once. - -## Pump setup - -see [Dana RS pump](../Configuration/DanaRS-Insulin-Pump.md) \ No newline at end of file diff --git a/docs/CROWDIN/ko/Getting-Started/WhatisAndroidAPS.md b/docs/CROWDIN/ko/Getting-Started/WhatisAndroidAPS.md deleted file mode 100644 index 92c4ae2d2f23..000000000000 --- a/docs/CROWDIN/ko/Getting-Started/WhatisAndroidAPS.md +++ /dev/null @@ -1,39 +0,0 @@ -# What is a closed loop system with AAPS? - -AAPS is an app that acts as an artificial pancreas system (APS) on an Android smartphone. 인공췌장시스템(APS)는 무엇입니까? 혈당을 건강한 범위안에서 유지시켜주는 췌장의 역할을 소프트웨어적으로 하게 만든 프로그램입니다. - -APS가 실제 췌장과 동일한 역할을 하진 못하지만, 1형당뇨인들이 기기를 이용하여 보다 편하고 안전하게 혈당을 관리할 수 있도록 하게해줍니다. Those devices include a continuous glucose monitor (CGM) to tell AAPS about your blood sugar levels and an insulin pump which AAPS controls to deliver appropriate doses of insulin. 이 앱들은 블루투스로 서로 통신합니다. OpenAPS라고 불리는 또 다른 인공췌장시스템을 위해 개발된 특별한 알고리즘 혹은 규칙을 사용하여 적정 인슐린 양을 계산합니다. 이 OpenAPS는 전 세계 수천명의 사람들이 사용하며 수백만 시간의 누적사용양을 기록하고 있습니다. - -A note of caution: AAPS is not regulated by any medical authority in any country. Using AAPS is essentially carrying out a medical experiment on yourself. 이 시스템을 구축하기 위해선 의지와 기술적 지식이 필요합니다. 처음에 이러한 기술적인 지식이 없다면, 스스로 노력하여 익혀야 할것입니다. 당신이 필요로 하는 정보를 이 문서, 인터넷, 혹은 이 시스템을 이미 이용하고 있는 사용자 들로부터 얻을 수 있을 것이며, 페이스북, 슈거트리 혹은 다른 커뮤니티를 통해 질문하실 수 있습니다. Many people have successfully built AAPS and are now using it entirely safely, but it is essential that every user: - -- Builds the system themselves so that they thoroughly understand how it works -- Adjusts its individual dosage algorithm with his or her diabetes team to work nearly perfect -- Maintains and monitors the system to ensure it is working properly - -```{note} -**Disclaimer and Warning** - -- All information, thought, and code described here is intended for informational and educational purposes only. Nightscout은 현재 HIPAA 개인 정보 보호 준수 규약을 따르지 않습니다. Use Nightscout and AAPS at your own risk, and do not use the information or code to make medical decisions. -- Use of code from github.com is without warranty or formal support of any kind. 자세한 것은 이 곳의 라이센스에 대한 자세한 내용을 참고하세요. -- All product and company names, trademarks, servicemarks, registered trademarks, and registered servicemarks are the property of their respective holders. 그것들을 사용한 것은 정보를 제공하기 위한 목적이며, 그들과의 제휴 또는 보증을 의미하지는 않습니다. - -Please note - this project has no association with and is not endorsed by: [SOOIL](http://www.sooil.com/eng/), [Dexcom](https://www.dexcom.com/), [Accu-Chek, Roche Diabetes Care](https://www.accu-chek.com/), [Insulet](https://www.insulet.com/) or [Medtronic](https://www.medtronic.com/). -``` - -이 도전을 하실 준비가 되었다면 계속 읽어주세요. - -## Primary goals behind AAPS - -- An app with safety built in. To read about the safety features of the algorithms, known as oref0 and oref1, click here () -- An all-in-one app for managing type 1 diabetes with an artificial pancreas and Nightscout -- An app to which users can easily add or remove modules as needed -- An app with different versions for specific locations and languages. -- An app which can be used in open- and closed-loop mode -- An app that is totally transparent: users can input parameters, see results, and make the final decision -- An app which is independent of particular pump drivers and contains a "virtual pump" so users can safely experiment before using it on themselves -- An app closely integrated with Nightscout -- An app in which the user is in control of safety constraints - -## How to start - -Of course, all of this content here is very important, but can be in the beginning quite confusing. A good orientation is given by the [Module Overview](../Module/module.md) and the [Objectives](../Usage/Objectives.html). diff --git a/docs/CROWDIN/ko/Hardware/DexcomG4.md b/docs/CROWDIN/ko/Hardware/DexcomG4.md deleted file mode 100644 index 3ac2b2b96f4b..000000000000 --- a/docs/CROWDIN/ko/Hardware/DexcomG4.md +++ /dev/null @@ -1,6 +0,0 @@ -# Dexcom G4 - -## If using G4 with OTG cable ('traditional' Nightscout) -- If not already set up then download Nightscout Uploader app from the Play Store and follow instructions on [Nightscout](https://nightscout.github.io/). -- In AAPS Preferences enter your Nightscout website and API secret. -- Select NSClient in ConfigBuilder (setting in AAPS). diff --git a/docs/CROWDIN/ko/Hardware/Smartwatch.md b/docs/CROWDIN/ko/Hardware/Smartwatch.md deleted file mode 100644 index 12281d6d256a..000000000000 --- a/docs/CROWDIN/ko/Hardware/Smartwatch.md +++ /dev/null @@ -1,10 +0,0 @@ -# Smartwatches - -Smartwatches are optional, but very useful for some users. More details are here: - -- [List of tested phones and smartwatches](../Getting-Started/Phones.md) -- [Watchfaces Wear OS](../Configuration/Watchfaces.md) -- [Troubleshooting Sony Smartwatch SW 3](../Usage/SonySW3.md) - -## Instructions for Building the AAPS Wear APK for Wear OS -https://androidaps.readthedocs.io/en/latest/remote-control.html#building-the-aaps-wear-apk diff --git a/docs/CROWDIN/ko/Installing-AndroidAPS/Building-APK.md b/docs/CROWDIN/ko/Installing-AndroidAPS/Building-APK.md deleted file mode 100644 index 04584d038a00..000000000000 --- a/docs/CROWDIN/ko/Installing-AndroidAPS/Building-APK.md +++ /dev/null @@ -1,369 +0,0 @@ -# Building the APK - -## Build yourself instead of download - -**AAPS is not available as download due to regulation for medical devices. It is legal to build the app for your own use, but you must not give a copy to others! See [FAQ page](../Getting-Started/FAQ.md) for details.** - -## Important notes - -* Please use **[Android Studio Giraffe" (2022.3.1)](https://developer.android.com/studio/)** or newer to build the apk. -* [Windows 32-bit systems](troubleshooting_androidstudio-unable-to-start-daemon-process) are not supported by Android Studio - -(Building-APK-recommended-specification-of-computer-for-building-apk-file)= - -## Recommended specification of computer for building apk file - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
OS (Only 64 bit)Windows 8 or higherMac OS 10.14 or higherAny Linux supports Gnome, KDE, or Unity DE;  GNU C Library 2.31 or later

CPU (Only 64 bit)

x86_64 CPU architecture; 2nd generation Intel Core or newer, or AMD CPU with support for a
Windows Hypervisor		ARM-based chips, or 2nd generation Intel Core or newer with support for
Hypervisor.Framework		x86_64 CPU architecture; 2nd generation Intel Core or newer, or AMD processor with support for AMD Virtualization (AMD-V) and SSSE3

RAM

8GB or more

Disk

At least 30GB free space. SSD is recommended.

Resolution

1280 x 800 Minimum

Internet

Broadband

- -Please keep in mind that both **64 bit CPU and 64 bit OS are mandatory condition.** If your system DOES NOT meet this condition, you have to change affected hardware or software or the whole system. **It is strongly recommended to use SSD (Solid State Disk) instead of HDD (Hard Disk Drive) because it will take less time when you are building the APS installation apk file.** Recommended is just recommended and it is not a mandatory. However, you may still use a HDD when you are building apk file but note that the building process can take a long time to complete, although once started, you can leave it running unattended. - -* * * - -### This article is divided into two parts. - -* In the overview part there is an explanation on what steps are necessary to build the APK file. -* In the step by step walkthrough part you will find the screenshots of a concrete installation. Because the versions of Android Studio - the software development environment which we will use to build the APK - will change very quickly this will be not identical to your installation but it should give you a good starting point. Android Studio also runs on Windows, Mac OS X and Linux and there might be small differences in some aspects between each platform. If you find that something important is wrong or missing, please inform the facebook group "AAPS users" or in the Discord chat [Android APS](https://discord.gg/4fQUWHZ4Mw) so that we can have a look at this. - -## 개요 - -In general, the steps necessary to build the APK file: - -1. [Install git](../Installing-AndroidAPS/git-install.md) -2. [Install Android Studio](Building-APK-install-android-studio) -3. [Set git path in Android Studio preferences](Building-APK-set-git-path-in-preferences) -4. [Download AAPS code](Building-APK-download-AAPS-code) -5. [Download Android SDK](Building-APK-download-android-sdk) -6. [Build the app](Building-APK-generate-signed-apk) (generate signed apk) -7. [Transfer apk file to your phone](Building-APK-transfer-apk-to-smartphone) -8. [Identify receiver if using xDrip+](xdrip-identify-receiver) - -## Step by step walkthrough - -Detailed description of the steps necessary to build the APK file. - -## Git를 설치하세요. (미설치시) - -Follow the manual on the [git installation page](../Installing-AndroidAPS/git-install.md). - -(Building-APK-install-android-studio)= - -## Install Android Studio - -The following screenshots have been taken from Android Studio Version Arctic Fox | 2020.3.1. Screens can change in future versions of Android Studio. But you should be able to find your way through. [Help from the community](../Where-To-Go-For-Help/Connect-with-other-users.md) is provided. - -One of the most important things when installing Android Studio: **Be patient!** During installation and setup Android Studio is downloading a lot of stuff which will take its time. - -Download [Android Studio from here](https://developer.android.com/studio/install.html) and install it on your computer. - -On first start you will find the setup wizard: - -Select "Do not import settings" as you have not used it before. - -![Do not import settings](../images/studioSetup/01_ImportSettings.png) - -Decide whether you want to share data with Google or not. - -![Share data with Google](../images/studioSetup/02_DataSharing.png) - -On the following screen click "Next". - -![Welcome screen](../images/studioSetup/03_Welcome.png) - -Select "Standard" installation and click "Next". - -![Standard installation](../images/studioSetup/04_InstallType.png) - -Select the theme for the user interface you like. (In this manual we used "Light".) Then click "Next". - -> ***Note:*** This is just the color scheme. You can select whatever you like (i.e. "Darcula" for dark mode). This selection has no influence on building the APK but the following screenshots might look different. - -![UI color scheme](../images/studioSetup/05_UITheme.png) - -Click "Next" on the "Verify Settings" dialog. - -![Verify settings](../images/studioSetup/06_Overview.png) - -Click on all three license agreement parts and select "Agree". When you have agreed to all, the "Finish" button will be enabled and you can "Finish". - - ![Agree license agreements](../images/studioSetup/07_LicenseAgreement.png) - - -Wait while Android Studio downloads additional components and be patient. Once everything is downloaded button "Finish" turns blue. Click the button now. - -![Downloading components](../images/studioSetup/08_Downloading.png) - -(Building-APK-download-AAPS-code)= - -## Download AAPS code - -* On the Android Studio welcome screen select "Projects" (1) on the left and then "Get from VCS" (2). - - ![Android Studio wizard](../images/studioSetup/20_ProjectVCS.png) - - * If you already opened Android Studio and do not see the welcome screen anymore select File (1) > New (2) > Project from Version Control... (3) - - ![Check out project from version control within Android Studio](../images/AndroidStudio_FileNew.PNG) - - * We will now tell Android Studio were to get the code from: - - * Make sure you have selected "Repository URL" on the left (1). - - * Check if "Git" is selected as version control (2). - * Copy and paste the URL ```https://github.com/nightscout/AndroidAPS``` to the main AAPS repository into the URL textbox (3). - * Choose the directory where you want to save the cloned code (4). - - ![Clone Git](../images/studioSetup/21_CloneURL.png) - -* Click button "Clone" (5). - - ![Clone repository](../images/studioSetup/22_Cloning.png) - -* Do not click "Background" while repository is cloned! - -* After the repository is cloned successfully, Android Studio will open the cloned project. - -* You will be asked whether you want to trust the project. Click on "Trust project"! - - ![Trust project](../images/studioSetup/23_TrustProject.png) - -* In the status bar at the bottom you will see the information that Android Studio is running background tasks. - - ![Background tasks](../images/studioSetup/24_GradleSyncRunning.png) - -* Windows only: Grant access if your firewall is asking for permission. - - ![Firewall permission java](../images/AndroidStudio361_18.png) - -* Once the background tasks are finished you will probably see an error saying that errors occurred (1) or (2) or (3). - - ![SDK licence](../images/studioSetup/25_SyncFailed.png) - - Don't worry, this will be solved soon! - -(Building-APK-set-git-path-in-preferences)= - -## Set git path in preferences - -Make sure [git is installed](../Installing-AndroidAPS/git-install.md) on your computer and you have restarted your computer since installing. - -On the Android Studio welcome screen click "Customize" (1) on the left and then select the link "All settings..." (2): - -![Android Studio settings from welcome screen](../images/studioSetup/10_WizardSettings.png) - -### Windows - -* As windows user, make sure you have restarted your computer after [installing Git](../Installing-AndroidAPS/git-install.md). - -* In the menu, go to File (1) > Settings (2) (or Android Studio > Preferences on Mac). - - ![Open settings](../images/studioSetup/30_Settings.png) - -* Double-click "Version Control" (1) to open the sub-menu. - -* Click Git (2). -* Make sure update method "Merge" (3) is selected. -* Check if Android Studio can locate path to git.exe automatically by clicking the button "Test" (4). - - ![Android Studio settings](../images/studioSetup/11_GitPath.png) - -* If automatic setting is successful git version will be displayed next to the path. - - ![Git version displayed](../images/studioSetup/12_GitVersion.png) - -* Eventually git.exe cannot be found automatically or the Test will result in an error (1): - - ![Git not found](../images/studioSetup/13_GitVersionError.png) - - In this case click on the folder icon (2). - -* Use [search function](https://www.tenforums.com/tutorials/94452-search-file-explorer-windows-10-a.html) in windows explorer to find "git.exe" if you are unsure where git has been installed. You are looking for a file named "git.exe", located in **\bin** folder. - -* Select path to git.exe and make sure you selected the one in ** \bin\ ** folder (3) and click "OK" (4). - - ![Select git manually](../images/studioSetup/14_GitManualSelection.png) - -* Check your selected git path again with the "Test" button as described above. - -* When the git version is displayed next to the path (see screenshot above), close settings window by clicking "OK" button (5). - -### Mac - -* Any git version should work. For example . -* Use homebrew to install git: ```$ brew install git```. -* For details on installing git see the [official git documentation](https://git-scm.com/book/en/v2/Getting-Started-Installing-Git). -* If you install git via homebrew there is no need to change any preferences. Just in case: They can be found here: Android Studio - Preferences. - -(Building-APK-download-android-sdk)= - -## Download Android SDK - -* In the menu, go to File (1) > Settings (2) (or Android Studio > Preferences on Mac). - - ![Open settings](../images/studioSetup/30_Settings.png) - -* Double-click on Languages & Frameworks to open its submenu (1). - -* Select Android SDK (2). -* Tick the box left of "Android 9.0 (Pie)" (3) (API Level 28). - - ![SDK settings](../images/studioSetup/31_AndroidSDK.png) - -* Confirm changes by clicking OK. - - ![Confirm SDK changes](../images/studioSetup/32_ConfirmSDK.png) - -* Wait until the SDK download and installation is finished. - - ![Wait during SDK installation](../images/studioSetup/34_DownloadSDK.png) - -* When SDK installation is completed the "Finish" button will turn blue. Click this button. - - ![Finish SDK installation](../images/studioSetup/35_DownloadSDKfinished.png) - -* Android Studio might recommend to update the gradle system. **Never update gradle!** This will lead to difficulties! - -* If you see an information on the lower right side of your Android Studio window that Android Gradle Plugin is ready to update click on the text "upgrade" (1). - - ![No gradle update](../images/studioSetup/36_GradleUpdateRequest.png) - -* In the dialog box the select "Don't remind me again for this project" (2). - - ![No gradle update](../images/studioSetup/37_GradleUpdateDeny.png) - -* Restart Android Studio before you continue. - -(Building-APK-generate-signed-apk)= - -## 서명된 Apk파일 설치하기 - -Signing means that you indicate your app to be your own creation but in a digital way as a kind of digital fingerprint within the app itself. That is necessary because Android has a rule that it only accepts signed code to run for security reasons. For more information on this topic, follow [this link](https://developer.android.com/studio/publish/app-signing.html#generate-key). - -* After Android Studio is started, wait until all background tasks are finished. - - ![Wait for background tasks](../images/studioSetup/40_BackgroundTasks.png) - - * ***Warning:*** If errors occur, do not continue with the following steps. \ Consult the [troubleshooting section](../Installing-AndroidAPS/troubleshooting_androidstudio) for known problems! - - ![Gradle Sync Error](../images/studioSetup/41_GradleSyncError.png) - -* Click "Build" (1) in the menu bar and select "Generate Signed Bundle / APK..." (2). - - ![Build apk](../images/studioSetup/42_MenuBuild.png) - -* Select "APK" (1) instead of "Android App Bundle" and click "Next" (2). - - ![APK instead of bundle](../images/studioSetup/43_Apk.png) - -* Make sure that module is set to "AndroidAPS.app" (1). - -* Click "Create new..." (2) to start creating your key store. - - ***Note:*** A key store in this case is nothing more than a file in which the information for signing is stored. It is encrypted and the information is secured with passwords. - - ![Create key store](../images/studioSetup/44_KeystoreNew.png) - -* Click the folder symbol to select a path on your computer for your key store. - - ![Create key store](../images/studioSetup/45_KeystoreDialog.png) - -* Select the path where your key store shall be saved (1). - - ![Create key store](../images/studioSetup/46_KeystorePath.png) - - ***Warning: Do not save in same folder as project. You must use a different directory!*** A good location would be your home folder. - -* Type a file name for your key store (2) and confirm with "OK" (3). - -* Enter (2) and confirm (3) the password for your key store. ![Select key store path](../images/studioSetup/47_KeystoreDialog.png) - - ***Note:*** Passwords for key store and key do not have to be very sophisticated. Make sure to remember those or make a note in a safe place. In case you will not remember your passwords in the future, see [troubleshooting for lost key store](troubleshooting_androidstudio-lost-keystore). - -* Enter an alias (4) for your key. Choose whatever you like. - -* Enter (5) and confirm (6) the password for your key - -* Validity (7) is 25 years by default. You do not have to change the default value. - -* First and last name must be entered (8). All other information is optional. - -* Click "OK" (9) when you are done. - -* Make sure the box to remember passwords is checked (1). So you don't have to enter them again next time you build the apk (i.e. when updating to a new AAPS version). - -* Click "Next" (2). - - ![Remember passwords](../images/studioSetup/48_KeystoreSave.png) - -* Select build variant "fullRelease" (1) and press "Finish". - - ![Select build variant](../images/studioSetup/49_BuildVariant.png) - -* Android Studio will show "Gradle Build running" at the bottom. This takes some time, depending on your computer and internet connection. **Be patient!** - - ![Gradle Running](../images/studioSetup/50_GradleRunning.png) - -* Android Studio will display the information "Generate Signed APK" after build is finished. - - ![Build finished](../images/studioSetup/51_BuildFinished.png) - -* In case build was not successful refer to the [troubleshooting section](../Installing-AndroidAPS/troubleshooting_androidstudio). - -* Click on the notification to expand it. - -* Click on the link "locate". - - ![Locate build](../images/studioSetup/52_BuildLocate.png) - - * If the notification is gone, you can always open the "Event log" and select the same link there. ![Build successfully - event log](../images/studioSetup/53_EventLog.png) - -* Your file manager/explorer will open. Navigate to the directory "full" (1) > "release" (2). - - ![File location apk](../images/studioSetup/54_APKlocation.png) - -* "app-full-release.apk" (3) is the file you are looking for! - -(Building-APK-transfer-apk-to-smartphone)= - -## 스마트폰에 apk파일을 보내기. - -Easiest way to transfer app-full-release.apk to your phone is via [USB cable or Google Drive](https://support.google.com/android/answer/9064445?hl=en). Please note that transfer by mail might cause difficulties and is not the preferred way. - -On your phone you have to allow installation from unknown sources. Manuals how to do this can be found on the internet (i.e. [here](https://www.expressvpn.com/de/support/vpn-setup/enable-apk-installs-android/) or [here](https://www.androidcentral.com/unknown-sources)). - -## 문제 해결 - -See separate page [troubleshooting Android Studio](../Installing-AndroidAPS/troubleshooting_androidstudio). \ No newline at end of file diff --git a/docs/CROWDIN/ko/Resources/index.md b/docs/CROWDIN/ko/Resources/index.md deleted file mode 100644 index 57b2ebe2945e..000000000000 --- a/docs/CROWDIN/ko/Resources/index.md +++ /dev/null @@ -1,8 +0,0 @@ -# Resources - -```{toctree} -:glob: true -:maxdepth: 4 - -clinician-guide-to-AndroidAPS -``` diff --git a/docs/CROWDIN/ko/Sandbox/sandbox2.md b/docs/CROWDIN/ko/Sandbox/sandbox2.md deleted file mode 100644 index 33c547956c89..000000000000 --- a/docs/CROWDIN/ko/Sandbox/sandbox2.md +++ /dev/null @@ -1,43 +0,0 @@ -# internal sandbox file 2 for testing - -```{admonition} no need to translate this -:class: note - -No need to translate this. -``` - -This is an internal sandbox file for the documentation team to test - -1. markdown syntax and - -1. background process for - 1. CROWDIN translation and - 2. Read The Docs deployment. - -You can dirctly jump from here to the first label in the sandbox1.md file - ["Jump"](sandbox1-this-is-a-test). - -You can dirctly jump from here to the second label in this file - ["Jump"](sandbox1-this-is-another-test). - -Here you can jump to the first sandbox file - ["Jump"](./sandbox1.md). - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -(sandbox2-this-is-a-test)= -## This is a test - -This is a test if labels must be unique. - -### This is spare information from the docs - -cut from index: - -There are "limits" set in place when you are first beginning your AAPS journey. These safety limits have been developed over many years by observations of the inadvertent mistakes that new users are most likely to make when first learning to set up, build, and then successfully loop with AAPS - as most often those mistakes occur simply because the user was so excited to get started using the system that they may have forgotten to sit down and dedicate the time needed to understand the information within this documentation thoroughly. - - -### spare info from the overview to put into "preparing" - -Since the requirements are very different from anything you might have set up in the past, we recommend that you really follow the instructions, step-by-step the first few times you build the app, so that you have a stronger sense of how the app building process is supposed to behave when all directions are followed exactly. Please remember to take your time. Later this will go very quickly when you build the app again for a new version. That way you will have a greater chance of noticing when something doesn't going as planned before too many steps are out of line. It is important to save the your keystore file (.jks file used to sign your app) in a safe place, so that you can always use that exact same keystore file and password each and every time you are asked to create a new updated version of AAPS, as this file is what makes sure that each new version of the app "remembers" all the information that you have provided to it in previous versions of the app and thus ensure that the updates will go as smoothly as possible. On average, you can assume that there will be one new version and 2-3 required updates per year. This number is based on experience and may change in the future. But we do want to at least give you a general guideline on what to expect. When you are more experienced at building updated AAPS app versions all the steps that are required in building an updated app will only take 15-30 minutes, on average. However, in the beginning there can be a rather steep learning curve as these steps are not always considered intuitive by new users! So do not get frustrated if you find that it takes half a day or a whole day with some help from the community before you are finally finished with the update process. If you find that you are getting very frustrated just take a short break, and oftentimes; after a stroll around the block or two...you'll find that you are better able to approach the problem again. diff --git a/docs/CROWDIN/ko/Usage/Objectives.md b/docs/CROWDIN/ko/Usage/Objectives.md deleted file mode 100644 index c27b9c02a04c..000000000000 --- a/docs/CROWDIN/ko/Usage/Objectives.md +++ /dev/null @@ -1,184 +0,0 @@ -# Objectives - -AAPS has a series of Objectives that need to be completed to walk you through the features and settings of safe looping. They ensure you have configured everything detailed in the sections above correctly, and that you understand what your system is doing and why so you can trust it. - -If you are **upgrading phones** then you can [export your settings](../Usage/ExportImportSettings.md) to keep your progress through the objectives. Not only will your progress through the objectives be saved, but also your safety settings such as max bolus etc. If you do not export and import your settings then you will need to start the objectives from the beginning again. It is a good idea to [backup your settings](../Usage/ExportImportSettings.html) frequently just in case. - -If you want to go back in objectives see [explanation below](Objectives-go-back-in-objectives). - -## Objective 1: Setting up visualization and monitoring, analysing basals and ratios - -- Select the right blood glucose source for your setup. See [BG Source](../Configuration/BG-Source.md) for more information. -- Select the right Pump in ConfigBuilder (select Virtual Pump if you are using a pump model with no AAPS driver for looping) to ensure your pump status can communicate with AAPS. -- If using DanaR pump then ensure you have followed [DanaR Insulin Pump](../Configuration/DanaR-Insulin-Pump.md) instructions to ensure the link between pump and AAPS. -- You need to establish a data repository/reporting platform to complete this objective. That can be accomplished with either Nightscout or Tidepool (or both). Follow instructions at the [Nightscout](../Installing-AndroidAPS/Nightscout.md) or [Tidepool](../Installing-AndroidAPS/Tidepool.md) page for instructions. -- Note that URL in NSClient must be **WITHOUT /api/v1/** at the end - see [NSClient settings in Preferences](Preferences-nsclient). - -*You may need to wait for the next blood glucose reading to arrive before AAPS will recognise it.* - -## Objective 2: Learn how to control AAPS - -- Perform several actions in AAPS as described in this objective. - -- Click on the orange text "Not completed yet" to access the to-dos. - -- Links will be provided to guide you in case you are not familiar with a specific action yet. - - ```{image} ../images/Objective2_V2_5.png - :alt: Screenshot objective 2 - ``` - -(Objectives-objective-3-prove-your-knowledge)= - -## Objective 3: Prove your knowledge - -Objective 3 is a multiple choice test based on questions designed to test your theoretical knowledge of **AAPS**. - -Some users find Objective 3 to be the most difficult objective to complete. Please do read the AAPS documents in conjunction with the questions. If you are genuinely stuck after researching the **AAPS** documents, please search or ask for help on the Facebook or Discord group. These groups can provide friendly hints or redirect you to the relevant part of the **AAPS** documents. - -To proceed with Objective 3, click on the orange text “Not completed yet” to access the relevant question. Please read each question and select your answer(s). - - - -Within each question, a hyperlink to the **AAPS** documents will guide you to the relevant section of the document which you should read in order to locate the correct answer. - - -[Obj3_Screenshot 2023-12-05 223422](https://github.com/openaps/AndroidAPSdocs/assets/137224335/77347516-e24e-459d-98ab-acbb49a3d4e8)![image](https://github.com/openaps/AndroidAPSdocs/assets/137224335/ca756b8e-efbc-4427-b281-ac953ce16718) - - - -For each question, there may be more than one answer that is correct! If an incorrect answer is selected, the question will be time locked for a certain amount of time (60 minutes) before you can go back and answer the question. - - -After updating to a new version of **AAPS**, new questions may be added to cover a prevalent issue picked up by **AAPS** or alternatively to test your knowledge of a new feature of **AAPS** as released. - - -When **AAPS** is installed for the first time, you will have to complete Objective 3 entirely in order to move onto Objective 4. Each objective is required to be completed in sequential order. New features will gradually be unlocked as progress is made through the objectives. - -__What happens if new questions are added later to Objective 3?__ From time to time, new features are added to **AAPS** which may require a new question to be added to Objective 3. As a result, any new question added to Objective 3 will be marked as “incomplete” because **AAPS** will require you to action this. As each Objective is independent, you will not lose the existing functionality of **AAPS** providing the other objectives remain completed. - - -## Objective 4: Starting on an open loop - -- Select Open Loop either from Preferences, or by pressing and holding the Loop button in top left of the home screen. -- Work through the [Preferences](../Configuration/Preferences.md) to set up for you. -- Manually enact at least 20 of the temporary basal rate suggestions over a period of 7 days; input them to your pump and confirm in AAPS that you have accepted them. Ensure this data shows in AAPS and Nightscout. -- Enable [temp targets](../Usage/temptarget.md) if necessary. Use hypo temp targets to prevent that the system will correct too strong because of a raising blood glucose after a hypo. - -### Reduce number of notifications - -- To reduce the Number of decisions to be made while in Open Loop set wide target range like 90 - 150 mg/dl or 5,0 - 8,5 mmol/l. - -- You might even want to wider upper limit (or disable Open Loop) at night. - -- In Preferences you can set a minimum percentage for suggestion of basal rate change. - - ```{image} ../images/OpenLoop_MinimalRequestChange2.png - :alt: Open Loop minimal request change - ``` - -- Also, you do not need to act every 5 minutes on all suggestions... - -## Objective 5: Understanding your open loop, including its temp basal recommendations - -- Start to understand the thinking behind the temp basal recommendations by looking at the [determine basal logic](https://openaps.readthedocs.io/en/latest/docs/While%20You%20Wait%20For%20Gear/Understand-determine-basal.html) and both the [forecast line in AAPS homescreen](Screenshots-prediction-lines)/Nightscout and the summary of outputs from the calculations in your OpenAPS tab. - -You will want to set your target higher than usual until you are confident in the calculations and settings. System allows - -- a low target to be a minimum of 4 mmol (72 mg/dl) or maximum of 10 mmol (180 mg/dl) -- a high target to be a minimum of 5 mmol (90 mg/dl) and maximum of 15 mmol (225 mg/dl) -- a temporary target as a single value can be anywhere in the range of 4 mmol to 15 mmol (72 mg/dl to 225 mg/dl) - -The target is the value that calculations are based on, and not the same as where you aim to keep your blood glucose values within. If your target is very wide (say, 3 or more mmol \[50 mg/dl or more\] wide), you will often find little AAPS action. This is because blood glucose is eventually predicted to be somewhere in that wide range and therefore not many fluctuating temporary basal rates are suggested. - -You may want to experiment with adjusting your targets to be a closer together range (say, 1 or less mmol \[20 mg/dl or less\] wide) and observe how the behavior of your system changes as a result. - -You can view a wider range (green lines) on the graph for the values you aim to keep your blood glucose within by entering different values in [Preferences](../Configuration/Preferences.md) > Range for Visualisation. - -```{image} ../images/sign_stop.png -:alt: Stop sign -``` - -### Stop here if you are open looping with a virtual pump - do not click Verify at the end of this objective. - -```{image} ../images/blank.png -:alt: blank -``` - -(Objectives-objective-6-starting-to-close-the-loop-with-low-glucose-suspend)= -## Objective 6: Starting to close the loop with Low Glucose Suspend - -```{image} ../images/sign_warning.png -:alt: Warning sign -``` - -### Closed loop will not correct high BG values in objective 6 as it is limited to low glucose suspend. High BG values have to be corrected manually by you! - -- Prerequisite: You need a good profile (basal, ISF, IC) already working in AAPS to start with Loop in Low Glucose Suspend mode. Otherwise you can run in a hypo which you have to manually correct. This will help you a lot to avoid having to treat a low glucose over a period of 5 days. **If you are still having frequent or severe low glucose episodes then consider refining your DIA, basal, ISF and carb ratios and do NOT start objective 6 at this time.** -- You don't have to change your settings now. During objective 6, the maxIOB setting is internally set to zero automatically. **This override will be reversed when moving to objective 7.** -- The system will override your maxIOB settings to zero, which means if blood glucose is dropping it can reduce basal for you. If blood glucose is rising then it will only increase basal if the basal IOB is negative from a previous Low Glucose Suspend. Otherwise basal rates will remain the same as your selected profile. **That means that you have to manually handle high values with insulin corrections.** -- If your basal IOB is negative (see screenshot below) a TBR > 100% can be issued also in objective 6. - -```{image} ../images/Objective6_negIOB.png -:alt: Example negative IOB -``` - -- Set your target range slightly higher than you usually aim for, just to be safe and have a bit more scurity buffer. -- Enable 'Low Glucose Suspend' mode either by by pressing and holding the Loop icon at the top right corner of the home screen and selecting the Loop - LGS mode icon. -- Watch how temporary basals are active by viewing the blue basal text on the homescreen or the blue basal render on the homescreen graph. -- You may temporarily experience spikes following treated hypos without the ability to increase basal on the rebound. - -(Objectives-objective-7-tuning-the-closed-loop-raising-max-iob-above-0-and-gradually-lowering-bg-targets)= -## Objective 7: Tuning the closed loop, raising maxIOB above 0 and gradually lowering BG targets - -- Select 'Closed Loop' either from [Preferences](../Configuration/Preferences.md) or by pressing and holding the Loop icon at the top right corner of the home screen, over a period of 1 day. - -- Raise your 'Maximum total IOB OpenAPS can’t go over' (in OpenAPS called 'max-iob') above 0. The default recommendation is "average mealbolus + 3x max daily basal" (for the SMB algorithm) or "3x max daily basal" (for the older AMA algorithm) but you should slowly work up to this until you know your settings work for you (max daily basal = the maximum hourly value in any time segment of the day). - - This recommendation should be seen as a starting point. If you set to the 3x and you are seeing moves that push you too hard and fast then lower that number. If you are very resistant, raise it very little at a time. - - ```{image} ../images/MaxDailyBasal2.png - :alt: max daily basal - ``` - -- Once confident on how much IOB suits your looping patterns, then reduce your targets to your desired level. - -(Objectives-objective-8-adjust-basals-and-ratios-if-needed-and-then-enable-autosens)= -## Objective 8: Adjust basals and ratios if needed, and then enable autosens - -- You can use [autotune](https://openaps.readthedocs.io/en/latest/docs/Customize-Iterate/autotune.html) as a one off to check your basals remain accurate or do a traditional basal test. -- Enable [autosens](../Usage/Open-APS-features.md) over a period of 7 days and watch the white line on the homescreen graph show how your sensitivity to insulin may be rising or falling as a result of exercise or hormones etc. and keep an eye in the OpenAPS report tab how AAPS is adjusting the basals and/or targets accordingly. - -*Don’t forget to record your looping in* [this form](https://bit.ly/nowlooping) *logging AAPS as your type of DIY loop software, if you have not already done so.* - -(Objectives-objective-9-enabling-additional-oref1-features-for-daytime-use-such-as-super-micro-bolus-smb)= -## Objective 9: Enabling additional oref1 features for daytime use, such as super micro bolus (SMB) - -- You must read the [SMB chapter in this wiki](Open-APS-features-super-micro-bolus-smb) and [chapter oref1 in openAPSdocs](https://openaps.readthedocs.io/en/latest/docs/Customize-Iterate/oref1.html) to understand how SMB works, especially what's the idea behind zero-temping. -- Then you ought to [rise maxIOB](Open-APS-features-maximum-total-iob-openaps-cant-go-over-openaps-max-iob) to get SMBs working fine. maxIOB now includes all IOB, not just added basal. That is, if given a bolus of 8 U for a meal and maxIOB is 7 U, no SMBs will be delivered until IOB drops below 7 U. A good start is maxIOB = average mealbolus + 3x max daily basal (max daily basal = the maximum hourly value in any time segment of the day - see [objective 7](Objectives-objective-7-tuning-the-closed-loop-raising-max-iob-above-0-and-gradually-lowering-bg-targets) for an illustration) -- min_5m_carbimpact default in absorption settings has changed from 3 to 8 going from AMA to SMB. If you are upgrading from AMA to SMB, you have to change it manually. - -(Objectives-objective-10-automation)= -## Objective 10: Automation - -- You have to start objective 10 to be able to use [Automation](../Usage/Automation.md). -- Make sure you have completed all objectives including exam [Objectives-objective-3-prove-your-knowledge](Objectives#objective-3-prove-your-knowledge). -- Completing previous objectives will not effect other objectives you have already finished. You will keep all finished objectives! - -(Objectives-objective-11-DynamicISF)= -## Objective 11: Additional Features such as DynamicISF - -- You have to start objective 11 to be able to use [DynamicISF](../Usage/Open-APS-features.md) - -(Objectives-go-back-in-objectives)= -## Go back in objectives - -If you want to go back in objectives for whatever reason you can do so by clicking at "clear finished". - -```{image} ../images/Objective_ClearFinished.png -:alt: Go back in objectives -``` - -## Objectives in Android APS before version 3.0 - -One objective was removed when Android APS 3.0 was released. Users of Android APS version 2.8.2.1 who are on older Android software (i.e. earlier than version 9) will be using an older set of objectives which can be found [here](../Usage/Objectives_old.md). diff --git a/docs/CROWDIN/ko/Usage/Objectives_old.md b/docs/CROWDIN/ko/Usage/Objectives_old.md deleted file mode 100644 index a3dc8861eae2..000000000000 --- a/docs/CROWDIN/ko/Usage/Objectives_old.md +++ /dev/null @@ -1,152 +0,0 @@ -# Objectives as of Android APS 2.8.2.1 - -This is not the latest version of the Android APS Objectives. This page details the Objectives that were in place prior to version 3.0. Anyone using an older version of Android (i.e. prior to Android 9) and Android APS version 2.8.2.1 should refer to this page. - -Please see [this page](../Usage/Objectives.md) for the current set of Objectives. - -AndroidAPS has a series of Objectives that need to be completed to walk you through the features and settings of safe looping. They ensure you have configured everything detailed in the sections above correctly, and that you understand what your system is doing and why so you can trust it. - -If you are **upgrading phones** then you can [export your settings](../Usage/ExportImportSettings.md) to keep your progress through the objectives. Not only will your progress through the objectives be saved, but also your safety settings such as max bolus etc. If you do not export and import your settings then you will need to start the objectives from the beginning again. It is a good idea to [backup your settings](../Usage/ExportImportSettings.html) frequently just in case. - -If you want to go back in objectives see [explanation below](../Usage/Objectives.md#go-back-in-objectives). - -## Objective 1: Setting up visualization and monitoring, analysing basals and ratios - -- Select the right blood glucose source for your setup. See [BG Source](../Configuration/BG-Source.md) for more information. -- Select the right Pump in ConfigBuilder (select Virtual Pump if you are using a pump model with no AndroidAPS driver for looping) to ensure your pump status can communicate with AndroidAPS. -- If using DanaR pump then ensure you have followed [DanaR Insulin Pump](../Configuration/DanaR-Insulin-Pump.md) instructions to ensure the link between pump and AndroidAPS. -- Follow instructions in [Nightscout](../Installing-AndroidAPS/Nightscout.md) page to ensure Nightscout can receive and display this data. -- Note that URL in NSClient must be **WITHOUT /api/v1/** at the end - see [NSClient settings in Preferences](../Configuration/Preferences.md#nsclient). - -*You may need to wait for the next blood glucose reading to arrive before AndroidAPS will recognise it.* - -## Objective 2: Learn how to control AndroidAPS - -- Perform several actions in AndroidAPS as described in this objective. - -- Click on the orange text "Not completed yet" to access the to-dos. - -- Links will be provided to guide you in case you are not familiar with a specific action yet. - - ![Screenshot objective 2](../images/Objective2_V2_5.png) - -## Objective 3: Prove your knowledge - -- Pass a multiple-choice exam testing your AndroidAPS knowledge. - -- Click on the orange text "Not completed yet" to access the page with the question and answering options. - - ![Screenshot objective 3](../images/Objective3_V2_5.png) - -- Links will be provided to guide you in case you are unsure about the correct answers yet. - -- The questions for objective 3 have been completely rewritten by native speakers as of AAPS 2.8. The new ones cover the same basic topics plus a few new ones. - -- These new questions will lead to some not answered questions even though you have successfully completed objective 3 in previous versions. - -- Unanswered questions will affect you only if you start a new objective. In other words: If you have already completed all objectives you can wait and answer the new questions later without loosing AAPS functions. - -## Objective 4: Starting on an open loop - -- Select Open Loop either from Preferences, or by pressing and holding the Loop button in top left of the home screen. -- Work through the [Preferences](../Configuration/Preferences.md) to set up for you. -- Manually enact at least 20 of the temporary basal rate suggestions over a period of 7 days; input them to your pump and confirm in AndroidAPS that you have accepted them. Ensure this data shows in AndroidAPS and Nightscout. -- Enable [temp targets](../Usage/temptarget.md) if necessary. Use hypo temp targets to prevent that the system will correct too strong because of a raising blood glucose after a hypo. - -### Reduce number of notifications - -- To reduce the Number of decisions to be made while in Open Loop set wide target range like 90 - 150 mg/dl or 5,0 - 8,5 mmol/l. - -- You might even want to wider upper limit (or disable Open Loop) at night. - -- In Preferences you can set a minimum percentage for suggestion of basal rate change. - - ![Open Loop minimal request change](../images/OpenLoop_MinimalRequestChange2.png) - -- Also, you do not need to act every 5 minutes on all suggestions... - -## Objective 5: Understanding your open loop, including its temp basal recommendations - -- Start to understand the thinking behind the temp basal recommendations by looking at the [determine basal logic](https://openaps.readthedocs.io/en/latest/docs/While%20You%20Wait%20For%20Gear/Understand-determine-basal.html) and both the [forecast line in AndroidAPS homescreen](../Getting-Started/Screenshots.md#prediction-lines)/Nightscout and the summary of outputs from the calculations in your OpenAPS tab. - -You will want to set your target higher than usual until you are confident in the calculations and settings. System allows - -- a low target to be a minimum of 4 mmol (72 mg/dl) or maximum of 10 mmol (180 mg/dl) -- a high target to be a minimum of 5 mmol (90 mg/dl) and maximum of 15 mmol (225 mg/dl) -- a temporary target as a single value can be anywhere in the range of 4 mmol to 15 mmol (72 mg/dl to 225 mg/dl) - -The target is the value that calculations are based on, and not the same as where you aim to keep your blood glucose values within. If your target is very wide (say, 3 or more mmol \[50 mg/dl or more\] wide), you will often find little AAPS action. This is because blood glucose is eventually predicted to be somewhere in that wide range and therefore not many fluctuating temporary basal rates are suggested. - -You may want to experiment with adjusting your targets to be a closer together range (say, 1 or less mmol \[20 mg/dl or less\] wide) and observe how the behavior of your system changes as a result. - -You can view a wider range (green lines) on the graph for the values you aim to keep your blood glucose within by entering different values in [Preferences](../Configuration/Preferences.md) > Range for Visualisation. - -![Stop sign](../images/sign_stop.png) - -### Stop here if you are open looping with a virtual pump - do not click Verify at the end of this objective. - -![blank](../images/blank.png) - -## Objective 6: Starting to close the loop with Low Glucose Suspend - -![Warning sign](../images/sign_warning.png) - -### Closed loop will not correct high bg values in objective 6 as it is limited to low glucose suspend. High bg values have to be corrected manually by you! - -- Select Closed Loop either from [Preferences](../Configuration/Preferences.md) or by pressing and holding the Open Loop button in the top left of the home screen. - -- Set your target range slightly higher than you usually aim for, just to be safe. - -- Watch how temporary basals are active by viewing the blue basal text on the homescreen or the blue basal render on the homescreen graph. - -- Ensure your settings have supported AndroidAPS to avoid having to treat a low glucose over a period of 5 days. If you are still having frequent or severe low glucose episodes then consider refining your DIA, basal, ISF and carb ratios. - -- You don't have to change your settings. During objective 6 maxIOB setting is internally set to zero automatically. This override will be reversed when moving to objective 7. - -- The system will override your maxIOB settings to zero, which means if blood glucose is dropping it can reduce basal for you, but if blood glucose is rising then it will only increase basal if the basal IOB is negative (from a previous Low Glucose Suspend), otherwise basal rates will remain the same as your selected profile. - - ![Example negative IOB](../images/Objective6_negIOB.png) - -- If your basal IOB is negative (see screenshot above) a TBR > 100% can be issued also in objective 6. - -- You may temporarily experience spikes following treated hypos without the ability to increase basal on the rebound. - -## Objective 7: Tuning the closed loop, raising max IOB above 0 and gradually lowering BG targets - -- Raise your 'Maximum total IOB OpenAPS can’t go over' (in OpenAPS called 'max-iob') above 0 over a period of 1 day, the default recommendation is "average mealbolus + 3x max daily basal"(for SMB algorithm) or "3x max daily basal" (for older AMA algorithm) but you should slowly work up to this until you know your settings work for you (max daily basal = the maximum hourly value in any time segment of the day). - - This recommendation should be seen as a starting point. If you set to the 3x and you are seeing moves that push you to hard and fast then lower that number. If you are very resistant raise it a very little at a time. - - ![max daily basal](../images/MaxDailyBasal2.png) - -- Once confident on how much IOB suits your looping patterns then reduce your targets to your desired level. - -## Objective 8: Adjust basals and ratios if needed, and then enable autosens - -- You can use [autotune](https://openaps.readthedocs.io/en/latest/docs/Customize-Iterate/autotune.html) as a one off to check your basals remain accurate or do a traditional basal test. -- Enable [autosens](../Usage/Open-APS-features.md) over a period of 7 days and watch the white line on the homescreen graph show how your sensitivity to insulin may be rising or falling as a result of exercise or hormones etc. and keep an eye in the OpenAPS report tab how AndroidAPS is adjusting the basals and/or targets accordingly. - -*Don’t forget to record your looping in* [this form](https://bit.ly/nowlooping) *logging AndroidAPS as your type of DIY loop software, if you have not already done so.* - -## Objective 9: Try additional features for daytime use and gain confidence in your closed loop system - -- Before AAPS version 2.7 meal assist (MA) was the basic algorithm for AAPS and completing objective 8 was necessary to activate [advanced meal assist (AMA)](../Usage/Open-APS-features.md#advanced-meal-assist-ama). -- As [advanced meal assist (AMA)](../Usage/Open-APS-features.md#advanced-meal-assist-ama) is the standard algorithm from AAPS version 2.7 onwards use the following 28 days to try features you haven't used yet and get more confident with you closed loop system. - -## Objective 10: Enabling additional oref1 features for daytime use, such as super micro bolus (SMB) - -- You must read the [SMB chapter in this wiki](../Usage/Open-APS-features.md#super-micro-bolus-smb) and [chapter oref1 in openAPSdocs](https://openaps.readthedocs.io/en/latest/docs/Customize-Iterate/oref1.html) to understand how SMB works, especially what's the idea behind zero-temping. -- Then you ought to [rise maxIOB](../Usage/Open-APS-features.md#maximum-total-iob-openaps-cant-go-over-openaps-max-iob) to get SMBs working fine. maxIOB now includes all IOB, not just added basal. That is, if given a bolus of 8 U for a meal and maxIOB is 7 U, no SMBs will be delivered until IOB drops below 7 U. A good start is maxIOB = average mealbolus + 3x max daily basal (max daily basal = the maximum hourly value in any time segment of the day - see [objective 7](../Usage/Objectives#objective-7-tuning-the-closed-loop-raising-max-iob-above-0-and-gradually-lowering-bg-targets) for an illustration) -- min_5m_carbimpact default in absorption settings has changed from 3 to 8 going from AMA to SMB. If you are upgrading from AMA to SMB, you have to change it manually. - -## Objective 11: Automation - -- You have to start objective 11 to be able to use [Automation](../Usage/Automation.md). -- Make sure you have completed all objectives including exam [../Usage/Objectives.md#objective-3-prove-your-knowledge](../Usage/Objectives#objective-3-prove-your-knowledge). -- Completing previous objectives will not effect other objectives you have already finished. You will keep all finished objectives! - -## Go back in objectives - -If you want to go back in objectives for whatever reason you can do so by clicking at "clear finished". - -![Go back in objectives](../images/Objective_ClearFinished.png) diff --git a/docs/CROWDIN/ko/Usage/Smoothing-Blood-Glucose-Data-in-xDrip.md b/docs/CROWDIN/ko/Usage/Smoothing-Blood-Glucose-Data-in-xDrip.md deleted file mode 100644 index 776c3a370413..000000000000 --- a/docs/CROWDIN/ko/Usage/Smoothing-Blood-Glucose-Data-in-xDrip.md +++ /dev/null @@ -1,33 +0,0 @@ -(Smoothing-Blood-Glucose-Data-in-xDrip-smoothing-blood-glucose-data)= - -# 혈당 데이터 평활화 - -If BG data is jumpy/noisy, AAPS may dose insulin incorrectly resulting in high or low BG. For this reason it’s important to disable the loop until the problem is resolved. Depending on your CGM such issues may be due to the CGM’s configuration or sensor problems/site issues. You may need to replace your CGM sensor to resolve this. - -Some CGM systems have internal algorithms to detect the noise level in the readings and AAPS can use this information to avoid giving SMBs if the BG data is too unreliable. However, some CGMs do not transmit this data and for these BG sources 'Enable SMB always' and 'Enable SMB after carbs' are disabled for safety reasons. - -## Dexcom sensors - -### Build Your Own Dexcom App - -When using [BYODA](DexcomG6-if-using-g6-with-build-your-own-dexcom-app) your BG data is smooth and consistent. Furthermore you can take advantage of Dexcom back-smoothing. There are no restrictions in using SMBs, because the noise-level data is shared with AAPS. - -### xDrip+ with Dexcom G6 or Dexcom ONE - -Noise-level data and smooth BG readings are only shared with AAPS if you use xDrip+ [native mode](https://navid200.github.io/xDrip/docs/Native-Algorithm). Using native mode, there are no restrictions in using SMBs. - -### Dexcom G6 or Dexcom ONE with xDrip+ Companion Mode - -The noise-level data is not shared with AAPS using this method. Therefore 'Enable SMB always' and 'Enable SMB after carbs' are disabled. - -## Freestyle Libre sensors - -### xDrip+ with FreeStyle Libre - -None of the FreeStyle Libre systems (FSL1, FSL2, or FSL3) broadcast any information about the level of noise detected in the readings, and therefore 'Enable SMB always' and 'Enable SMB after carbs' are disabled for all setups using the FreeStyle Libre. - -In addition, many people have reported the FreeStyle Libre often produces noisy data. In xDrip+ there are a few options to help with this: - -**Smooth Sensor Noise.** In xDrip+ Settings > xDrip+ Display Settings ensure that Smooth Sensor Noise is turned on. This attempts to apply smoothing to noisy data. - -**Smooth Sensor Noise (Ultrasensitive).** If you are still seeing noisy data in xDrip+ you can apply more aggressive smoothing using the Smooth Sensor Noise (Ultrasensitive) setting. This will attempt to apply smoothing even on very low levels of detected noise. To do this, first enable [engineering mode](Enabling-Engineering-Mode-in-xDrip.md) in xDrip+. Then navigate to Settings > xDrip+ Display Settings and turn on Smooth Sensor Noise (Ultrasensitive). \ No newline at end of file diff --git a/docs/CROWDIN/ko/Usage/autotune_b.md b/docs/CROWDIN/ko/Usage/autotune_b.md deleted file mode 100644 index 11fe7cd0e9b0..000000000000 --- a/docs/CROWDIN/ko/Usage/autotune_b.md +++ /dev/null @@ -1,186 +0,0 @@ -# How to use Autotune plugin - -Documentation about Autotune algorythm can be found in [OpenAPS documentation](https://openaps.readthedocs.io/en/latest/docs/Customize-Iterate/autotune.html). - -Autotune plugin is an implementation of OpenAPS autotune algorythm within AAPS. - -**Currently Autotune Plugin is only available in dev branch with Engineering mode.** - -## Autotune user interface - -![Autotune default screen](../images/Autotune/Autotune_1b.png) - -- You can select in the Profile dropdown menu the input profile you want to tune (by default your current active profile is selected) - - Note: each time you select a new profile, previous results will be removed and Tune days parameter will be set to default value -- Then Tune days is to select the number of days used in calculation to tune your profile. The minimum value is 1 day and the maximum value 30 days. This number should not be too small to get correct iterative and smooth results (above 7 days for each calculation) - - Note: each time you change Tune days parameter, previous results will be removed -- Last Run il a link that recover your latest valid calculation. If you didn't launch Autotune on current day, or if previous results was removed with a modification of calculation parameter above, then you can recover parameters and results of the latest successfull run. -- Warning show you for example some information about selected profile (if you have several IC values or several ISF values) - - Note: Autotune calculation works with only a single IC and a single ISF value. There is currently no existing Autotune algorythm to tune a circadian IC or circadian ISF. If your input profile has several values, you can see in warning section the average value taken into account to tune your profile. -- Check Input Profile button open the Profile Viewer to allow you a quick verification of your profile (Units, DAI, IC, ISF, basal and target) - - Note: Autotune will only tune your IC (single value), ISF (single value) and basal (with circadian variation). Units, DAI and target will remain unchanged in output profile. - -- "Run Autotune" will launch Autotune calculation with selected profile and the number of Tune days - - Note: Autotune calculation can take a long time. Once launched, you can switch to another view (home, ...) and come back later in Autotune plugin to see results - -![Autotune Run start](../images/Autotune/Autotune_2b.png) - -- Then during the run you will see intermediate results below - - - Note: During run, settings are locked, so you cannot change anymore selected input profile or the number of day. You will have to wait the end of current calculation if you want to launch another run with other parameters. - - ![Autotune during run](../images/Autotune/Autotune_3b.png) - -- When Autotune calculation is finished, you will see the result (Tuned profile) and four buttons below. - -![Autotune Result](../images/Autotune/Autotune_4b.png) - -- It's important to always compare input profile (column "Profile"), output profile (column "Tuned") and the percentage of variation for each value (Column "%"). - -- For basal rates, you also have the number of "missing days". You have missing days when Autotune don't have enough data categorized as "Basal" to tune basal rate for this period (for example after each meal when you have carbs absorption). This number should be as low as possible especially when basal is important (for example during the night or at the end of the afternoon) - -- The "Compare profiles" button open the profile comparator view. Input profile is in blue, and output profile (named "Tuned") is in red. - - - Note: in the example below input profile has circadian variation for IC and ISF, but output calculated profile has a single value. If it's important for you to get a circadian output profile see [Circadian IC or ISF profile](#circadian-ic-or-isf-profile) below. - - ![Autotune Compare profiles](../images/Autotune/Autotune_5.png) - -- If you trust results (low percentage of variation between input profile and output profile), you can click on "Activate profile" button and then click on OK to validated. - - - Activate Tuned profile will automatically create a new profile "Tuned" in your Local profile plugin. - - If you already have a profile named "Tuned" in your local profile plugin, then this profile will be updated with calculated Autotune profile before the activation - - ![Autotune Activate profile](../images/Autotune/Autotune_6.png) - -- If you think Tuned profile must be adjusted (for example if you think some variation are too important), then you can click on "Copy to local profile" button - - - A new profile with the prefix "Tuned" and the date and time of the run will be created in local profile plugin - -![Autotune Copy to local profile](../images/Autotune/Autotune_7.png) - -- You can then select local profile to edit the Tuned profile (it will be selected by default when you open Local profile plugin) - - - the values in local profile will but rounded in the user interface to your pump capabilities - - ![Autotune local profile update](../images/Autotune/Autotune_8.png) - -- If you want to replace your input profile with Autotune result, click on "Update input profile" button and validate the Popup with OK - - - Note: if you click on "Activate profile" after "Update input profile", then you will activate your updated profile and not the default "Tuned" profile? - - ![Autotune Update input profile](../images/Autotune/Autotune_9.png) - -- If you have updated your input profile, then the "Update input profile" button is replaced by "Revert input profile" button (see screenshot below). You can that way immediatly see if your current input profile in Local profile plugin already include the result of last run or not. You also have the possibility to recover you input profile without autotune result with this button - - ![Autotune Update input profile](../images/Autotune/Autotune_10.png) - - - -## Autotune settings - -### Autotune plugin settings - -![Autotune default screen](../images/Autotune/Autotune_11.png) - -- Automation Switch Profile (default Off): see [Run Autotune with an automation rule](#run-autotune-with-an-automation-rule) below. If you change this setting to On, the input profile will automatically be updated by the Tuned profile, and it will be activated. - - **Be Carefull, you must trust and verified during several following days that after an update and activation of Tuned profile without modification, it improves your loop** - -- Categorize UAM as basal (default On): This setting is for the users using AndroidAPS without any carbs entered (Full UAM). It will prevent (when Off) to categorize UAM as basal. - - Note: if you have at least one hour of Carbs absorption detected during one day, then all data categorized as "UAM" will be categorized as basal, whatever this setting (On or Off) -- Number of days of data (default 5): You can define default value with this setting. Each time your select a new profile in Autotune plugin, Tune days parameter will be replaced by this default value -- Apply average result in circadian IC/ISF (default Off): see [Circadian IC or ISF profile](#circadian-ic-or-isf-profile) below. - -### 기타 설정 - -- Autotune also uses Max autosens ratio and Min autotsens ratio to limit variation. You can see and adjust these values in Config Builder > Sensitivity detection plugin > Settings > Advanced Settings - - ![Autotune default screen](../images/Autotune/Autotune_12.png) - - - -## Advanced feature - -### Circadian IC or ISF profile - -- If you have important variation of IC and/or you ISF in your profile, and you fully trust in your circadian time and variation, then you can set "Apply average result in circadiant IC/ISF" - - - Note that Autotune calculation will always be done with a single value, and circadian variation will not be tuned by Autotune. This setting only apply average variation calculated for IC and/or ISF on your circadian values - -- See on screenshot below Tuned profile with Apply average variation Off (on the left) and On (on the right) - - ![Autotune default screen](../images/Autotune/Autotune_13.png) - - - -### Tune specific days of the week - -- If you click on the checkbox with the eye on the right of "Rune days" parameter, you will see the day selection. You can specify which day of the week should be included in Autotune calculation (in screenshot below you can see an example for "working days" with Saturday and Sunday removed from autotune calculation) - - If the number of day included in Autotune calculation is lower than the number of Tune days, then you will see how many days will be included on the right of Tune days selector (10 days in the example below) - - This setting gives good results only if the number of remaining days is not to small (for example if you Tune a specific profile for week end days with only Sunday and Saturday selected, you should select a minimum of 21 or 28 Tune days to have 6 or 8 days included in Autotune calculation) - -![Autotune default screen](../images/Autotune/Autotune_14b.png) - -- During Autotune calculation, you can see the progress of the calculations ("Partial result day 3 / 10 tuned" on example below) - - ![Autotune default screen](../images/Autotune/Autotune_15b.png) - -## Run Autotune with an automation rule - -First step is to define correct trigger for an automation rule with Autotune: - -Note: for more information on how to set an automation rule, see [here](./Automation.rst). - -- You should select Recurring time trigger: only run Autotune once per day, and autotune is designed to be runned daily (each new run you shift one day later and quickly profile modification should be tiny) - - ![Autotune default screen](../images/Autotune/Autotune_16.png) - -- It's better at the beginning to run Autotune during the day to be able to check results. If you want to run Autotune during the night, you have to select in the trigger 4AM or later to include current day in next Autotune Calculation. - - ![Autotune default screen](../images/Autotune/Autotune_17.png) - -- Then you can select "Run Autotune" Action in the list - - ![Autotune default screen](../images/Autotune/Autotune_18.png) - -- You can then select Autotune Action to adjust parameters for your run. Default parameters are "Active Profile", default Tune days value defined in Autotune Plugin preferences, and All days are selected. - - ![Autotune default screen](../images/Autotune/Autotune_19b.png) - -- After a few days, if you fully trust Autotune results and percentage of modification is low, you can modify [Autotune settings](#autotune-plugin-settings) "Automation Switch Profile" to enabled to automatically update and activate profile tuned after calculation. - -Note: if you want to automatically tune profiles for specific days of the week (for example a profile for "Weekend days" and another one for "Working days"), then create one rule for each profile, select the same days in Trigger and in Autotune Action, Tune days must be high enough to be sure tuning will be done with at least 6 or 8 days, and don't forget to select time after 4AM in trigger... - -- See below an example of rule to tune "my profile" on all "Working days" with 14 Tune days selected (so only 10 days included in autotune calculation). - -![Autotune default screen](../images/Autotune/Autotune_20b.png) - - - -## Tips and trick's - -Autotune works with information existing in your database, so if you just installed AAPS on a new phone, you will have to wait several days before being able to launch Autotune with enough days to get relevant results; - -Autotune is just an help, it's important to regularly check if you agree with calculated profile. If you have any doubt, change Autotune settings (for example the number of days) or copy results in local profile and adjust profile before using it. - -Always use Autotune several days manually to check results before applyling them. And it's only when you fully trust Autotune results, and when variation becomes tiny between previous profile and calculated profile than you start to use Automation (Never before) - -- Autotune can work very well for some users and not for others, so **If you don't trust Autotune result, don't use it** - -It's also important to analyse Autotune results to understand (or try to understand) why Autotune propose these modifications - -- you can have a whole increase or decrease of the strength of your profile (for example increase of total basal associated to decrease of ISF and IC values). it could be associated to several following days with autosens correction above 100% (more agressivity required) or below 100% (you are more sensitive) -- Sometimes Autotune propose a different balance between basal rates and IC/ISF (for ex lower basal and more aggressive IC/ISF) - -We advise to not use Autotune in the following cases: - -- You don't enter all your carbs - - If you don't enter carbs correction for an hypoglycemia, Autotune will see an unexcepted increase of your BG value and will increase your basal rates the ' hours earlier, it could be the opposite of what you need to avoid hypo, especially if it's in the middle of the night. That's why it's important to enter all carabs especially correction for hypo. -- You have a lot of period with UAM detected during the day. - - Do you have entered all your carbs and correctly estimated your Carbs ? - - All UAM periods (except if you enter no carbs during a day and categorized UAM as basal is disabled), all your UAM periods will be categorized as basal, this can increase a lot your basal (much more than necessary) - -- Your carbs absorption is very slow: if most of your carbs absorption are calculated with min_5m_carbimpact parameter (you can see these periods with a little orange dot in the top of COB curve), the calculation of COB could be wrong and leads to wrong results. - - We you practice sport, you are generally more sensitive and your BG doesn't rise a lot, so during or after an exercice, it's usual to see some periods with slow carbs. But if you have too often unexpected slow carb absorption, then you may need a profile adjustment (higher value of IC) or a min_5m_carbimpact a bit to high. -- You have a "very bad days", for example stuck several hours in hyperglycemia with a huge amount of insulin to be able to go down within the range, or after a sensor change you got long periods of wrong BG values. -- If the percentage of modification is too important - - You can try to increase the number of days to get smoother results \ No newline at end of file diff --git a/docs/CROWDIN/ko/Usage/making-sport-with-AAPS.md b/docs/CROWDIN/ko/Usage/making-sport-with-AAPS.md deleted file mode 100644 index 79d2f1c38223..000000000000 --- a/docs/CROWDIN/ko/Usage/making-sport-with-AAPS.md +++ /dev/null @@ -1,185 +0,0 @@ -# making sport with AAPS - -In this section we want to address the topic of sport with AAPS. - -The aim is to show you how AAPS can help you to continue doing your favorite sport more easily or even to start doing it. It is relatively common for new type 1 diabetics to ask whether exercise is still possible for them, even if the answer in the training courses is actually a clear yes. Exercise is not only good for healthy people, but also for type 1 diabetics and even moderate exercise can even help to stabilize the blood sugar curve overall. - -:::{admonition} consult with your diabetes team after reading - -::: - -The difficulty here is that the prerequisites that someone brings with them and the expectations of what sport means to them are very different. - -Since we can assume that experienced top athletes with T1D who use AAPS are unlikely to look it up here, we deliberately set the bar low for ourselves when writing and for you when reading and using it, so that as many people as possible can benefit from it. - -Since even sport as a category is far too imprecise, as the effects of endurance sports differ greatly from strength training, for example, we are trying to break it down by type of sport. - -To be concrete and give you something you can test yourself we arrange the explanaiton around a concrete example and explain to you they action, reactions and effects. - -:::{admonition} more examples wanted - -The focus should always be on how others can do sport and not on the top performance someone has achieved. - -It's really about the basics. Your experience, which you share here, can help others to pursue their beloved sport more quickly and successfully and is therefore important. -::: - -## Cycling - -:::{admonition} take a friend with you - at least on your first trials -:class: information -A gerneral very good idea can be to take a good friend with you on the first rides. -This is especially important if you are not experienced in T1D. -Always keep in mind please: arrival comes before speed! Safety for you and the others in road traffic is very, very important. -::: - -### Example - -Let's take about 60 minutes of cycling on a flat route with a moderate heart rate as an example. - -1. we take a flat route in order to have an even load for the first exercise. This is not about performance, but purely about learning how you should react to changes in blood glucose. -2. we take the heart rate as an indicator of the load, as it is easy to see whether you are under load or not. -3. we set ourselves the goal of doing a relaxed lap around the neighborhood and focus on staying within our target range during the lap. In my case, this would be 70 <= x <= 180 mg/dl. - -We **don't** take the speed, as this is heavily dependent on personal physical conditions as well as the bike and surface used. It is therefore not very meaningful. - -You should know from the diabetes training courses you have attended that during endurance sports cycling, the insulin active in the body works significantly better than during times without physical exertion. The insulin active in the body is referred to as insulin on board (IoB). It is our most important parameter when cycling with T1D. - -We try to keep the IoB as low as possible at the start and during exercise. IoB should be around 0 or even slightly negative. You can get it there by not eating 3-4 hours before exercise. In the beginning it can also be helpful to exercise in the morning before breakfast, as with the right profile you should always have around 0 for IoB in the morning. - -AAPS shows us the IoB value on the home screen on the left under the blood glucose value. - -![IoB](../images/cycling_20240104-174035.png) - -:::{admonition} ignoring the IoB rule increases the risk for roller coaster BG dramatically -:class: danger -If you ignore this rule, you can still go cycling, but it will be much more difficult to keep your blood sugar levels in balance, so it is better to save this for later tests after several successful simple tests. -::: - -As you should know from the diabetes training courses, you should reduce the basal rate during exercise. The factor is individual. I have found a value of 50% in tests to be suitable for me. - -In AAPS, you should therefore change your profile to 50% before exercise and keep it active until the end of exercise. Some people even do it a certain amount of time before, e.g. 1 hour. Unfortunately, the pre-run is also individual. We will come to the post-run later. - -You should use two carbohydrates during exercise. - -1. medium-fast carbohydrates for the insulin still in the body and -2. very fast carbohydrates to prevent slipping into a hypo. - -For medium-fast carbohydrates, I treat myself to cookies or a banana before exercise, for example. You can also use something else that is more suitable for you. -For very fast carbohydrates, I take 3 teaspoons of dissolved glucose per 100 ml of still water in a 500 ml water bottle on my bike. If I'm cycling longer distances, I take a larger bottle with me and, if necessary, packaged glucose to refill the bottle. I add a little lemon juice for flavor. You can also use something other than lemon juice for the taste. You shouldn't change anything about the dextrose, as dissolved dextrose raises blood sugar levels super quickly. If you only take it in sips, your blood sugar won't go super high either! You can also do this tip at home beforehand as a dry run and see how quickly the change shows up on the CGMS. - -Why do I place so much emphasis on fast carbohydrates? - -1. once you are in a slight hypo, you may get back into the normal range by drinking the dextrose solution. As a rule, however, the oscillation of the curve then begins, which leads to a rollercoaster ride of the blood sugar. You may even be able to keep this within your target range, but you must be constantly vigilant. Without a hypo it is simply the most stable. -2. if you even slip into a somewhat severe hypo (without the need for outside help, of course), you may even have to pause briefly to avoid getting stuck in the hypo. - With both hypos, there is a risk that you will be tempted to switch from drinking 2-3 sips at a time to larger quantities. Not too bad at first, until the oscillation sets in and pushes you into a hyper. You can correct this, but your blood sugar will most likely go on a rollercoaster ride. - -What else is helpful, but not absolutely necessary? -It is important to keep an eye on your blood sugar, as your blood sugar can change enormously (e.g. 30 - 50 mg/dl) within 15 minutes of riding and a little more IoB or a basal rate that is still too high. The best way to keep an eye on it is if it is visible on the handlebars or if it is also displayed on your watch. It is even possible to install an additional app on some Garmin GPS bike computers that displays the blood glucose from XDrip or Nightscout as a data field on the bike computer. The additional app was developed by Andreas May from the T1D community. It is available free of charge in the official connect IQ Store. Certainly an interesting option for riders interested in sports. - -[Link to Andreas May Data Field App on connect IQ store](https://apps.garmin.com/de-DE/apps/5a3e2cda-12f0-4afd-88ed-000e67a68d84) - -Here is a picture of my Garmin Edge 530 bike computer with map, blood sugar and heart rate. - -![Garmin Edge 530 with BG data field](../images/cycling_IMG_1087.jpeg) - -After you have eaten the medium fast carbohydrates (24 - 36 g I take) and the blood sugar is above 100 mg/dl but also below 160 mg/dl, I carry out the profile change to 50% and set the activity temp target. - -:::{admonition} disable SMBs during high temp targets if necessary -:class: danger -Attention: If you prefer not to receive SMBs during the sport, please disable the option "Enable SMB with hight temp targets" in the settings of SMB or DynIFS Plugin. -::: - -The following picture shows the start and end of the sport. The end was specified as the duration when the profile was changed at the start. - -The temporary profile change has the following effects - -1. for a period of 60 minutes -2. a reduction to 50% of the profile and -3. the target is raised by clicking on the Activity Target option, which may have the side effect of disabling the SMBs - see above. - -![profile switch with temp target](../images/cycling_20240104-174056.png) - -The second image shows that the start at IoB was started towards 0. - -![IoB around 0](../images/cycling_20240104-174111.png) - -If the blood sugar drops faster than 15 mg/dl in 5 minutes or if it is at 120 mg/dl and tends to fall, I drink 1-2 sips of dissolved glucose. Then I wait for the next value and proceed as described above. - -You can hardly see it here, but at the beginning I took 2 sips from the bottle several times when my blood sugar started to fall. When it stabilized, I didn't need any more glucose. - -Here is the picture that illustrates this. The chart is saved on the Garmin as a result of the activity. - -![BG chart Garmin](../images/cycling_20240104-174431.png) - -If you should suddenly break out upwards, i.e. above 180 mg/dl, you should consider whether you should make a correction bolus. Caution: Remember the factor and apply it to the correction, otherwise the correction will be too strong. - -If your blood sugar drops below 80 mg/dl, take a break and drink two sips until your blood sugar is back above 100 mg/dl. - -At the end of the ride, the profile change should be finished as the time is up. - -Since we only rode easy for 60 minutes, there shouldn't be a big muscle bulking effect continuing to pull carbohydrates from your blood sugar. However, if it felt strenuous to you, keep an eye on it. This is especially true if you then go straight to bed. It may be better to change your profile to e.g. 80% for sleep. You may come out of sleep slightly too high, but it's better than having a hypo at night. Over time, you will surely find out what happens to you. - -The following pictures show the low intensity of the sport. - -The elevation profile -![](../images/cycling_20240104-174314.png) - -Speed with average and maximum speed - -![](../images/cycling_20240104-174326.png) - -Note the pause at the level crossing, which is also reflected in the heart rate. - -The heart rate. -![](../images/cycling_20240104-174337.png) - -The training effect. -![](../images/cycling_20240104-174358.png) - -The time in the different heart rate training zones. -![](../images/cycling_20240104-174423.png) - -After succesfully mastering this simple example you could go for further targets by stretching - -1. the distance and time -2. the load during the ride -3. the elevation during the right which should make a big impact on the more necessary carbs or further reduction of IoB and percentage of profile switch. - -Based on my experiences I would not expect to come back 100% with time in range over the whole and every ride. - -### Tipps - -I already gave some tipps for during the ride above. - -Here are some further tipps what can go wrong and how you can act to prevent it or react to compensate it. - -#### sky rocket high after ride - -During the ride everything was fine but after siting down and relax the blood sugar go sky rocket high. - -**Possible reason:** This happens when you have drunk too much dissolved glucose. - -**Reaction:** Drink 500 ml water, go to the shower and then control again. Latest after 30 minutes think about giving a correction bolus but be careful when it is short for bed time. Therefore it can be very good to make the first try runs on weekend mornings. - -**Action:** Next time be a bit more cautious in drinking from the dissolved glucose. - -#### hypo during ride - -During the ride you are going into hypo and can't recover your blood sugar during cycling. - -**Possible reason:** Your body cannot absorb enough carbohydrates quickly enough during exercise. - -**Reaction:** Take a rest and corrrect your blood sugar with drinking dissolved glucose. Stay calm: arrival comes before speed. - -**Action:** Did you started with IoB near 0? Have you eaten a small amount of middle fast carbs? Can you increase this or are the not fast enough for your body? Is it possible to prevent going into hypo by reducing the factor for the profile switch? Have you disbaled SMBs during ride as explained above? - -#### sky rocket high during ride - -During the ride your blood sugar goes sky rocket high. - -**Possible reason:** You have got taken too much carbs for your IoB at that time. Beneath for sure the typical technical problems with your -insulin pump like leakage or blockage of the catheder! - -**Reaction:** If it is too high for you take a rest and correct with a bolus. Keep in mind that you must ride home and therefore make it carefully. Drink 500 ml pure water without carbs. Stay calm: arrival comes before speed. - -**Action:** Have you eaten too much? Especially have you drunk too much from the dissolved glucose during the ride? Is your percentage of reduction the profile during profile switch too low and you can increase this? diff --git a/docs/CROWDIN/ko/Where-To-Go-For-Help/How-to-get-support.md b/docs/CROWDIN/ko/Where-To-Go-For-Help/How-to-get-support.md deleted file mode 100644 index b58ecc8978b6..000000000000 --- a/docs/CROWDIN/ko/Where-To-Go-For-Help/How-to-get-support.md +++ /dev/null @@ -1,11 +0,0 @@ -# How to get support - -**Level 1:** Wiki - we now have a search function! - -**Level 2:** [Facebook](https://www.facebook.com/groups/AndroidAPSUsers/) OR [gitter](https://gitter.im/MilosKozak/AndroidAPS) - -**Level 3:** Gitter (if FB did not get results, wait at least a couple of hours (plural)!!! Direct crossposts will be ignored/deleted on both channels!!!) - -**Level 4:** Create an issue with logs and time of the issue - -**Level 5:** PM (only if personal data is involved that should not go in a public channel) \ No newline at end of file diff --git a/docs/CROWDIN/ko/buildingAAPS.md b/docs/CROWDIN/ko/buildingAAPS.md deleted file mode 100644 index 98164a09e49b..000000000000 --- a/docs/CROWDIN/ko/buildingAAPS.md +++ /dev/null @@ -1,28 +0,0 @@ -# Dummy - -## This is a dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - - -## This is another dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - - -## This is another another dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - diff --git a/docs/CROWDIN/ko/completingObjetives.md b/docs/CROWDIN/ko/completingObjetives.md deleted file mode 100644 index 98164a09e49b..000000000000 --- a/docs/CROWDIN/ko/completingObjetives.md +++ /dev/null @@ -1,28 +0,0 @@ -# Dummy - -## This is a dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - - -## This is another dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - - -## This is another another dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - diff --git a/docs/CROWDIN/ko/dummy.md b/docs/CROWDIN/ko/dummy.md deleted file mode 100644 index 98164a09e49b..000000000000 --- a/docs/CROWDIN/ko/dummy.md +++ /dev/null @@ -1,28 +0,0 @@ -# Dummy - -## This is a dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - - -## This is another dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - - -## This is another another dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - diff --git a/docs/CROWDIN/ko/intro.md b/docs/CROWDIN/ko/intro.md deleted file mode 100644 index 508f26d9c12c..000000000000 --- a/docs/CROWDIN/ko/intro.md +++ /dev/null @@ -1,291 +0,0 @@ -![20-06-23v2 AAPS simple overview-cropped](https://github.com/openaps/AndroidAPSdocs/assets/94044064/e505b73b-09a0-42a4-a1ab-b830a0741234) - -# Introduction to APS and AAPS - -## What is an “Artificial Pancreas System”? - -A human pancreas does a lot of things besides regulating blood sugar. However, the term **“Artificial Pancreas System” (APS)** usually refers to a system which works to automatically keep blood sugar levels within healthy limits. - -The most basic way to do this is by detecting **glucose levels**, using these values to do **calculations**, and then delivering the (predicted) right amount of **insulin** to the body. It repeats the calculation, every few minutes, 24/7. It uses **alarms** and **alerts** to inform the user if intervention or attention is needed. This system is typically made up of a **glucose sensor**, an **insulin pump** and an **app** on a phone. - -You can read more about the different artificial pancreas systems currently in use and in development in this 2022 review article: - -![Frontiers](./images/FRONTIERS_Logo_Grey_RGB.png) [Future Directions in Closed-Loop Technology](https://www.frontiersin.org/articles/10.3389/fendo.2022.919942/full#:~:text=Fully%20closed%2Dloop%20systems%2C%20unlike,user%20input%20for%20mealtime%20boluses). - -In the near future, some so-called "dual-hormone" systems will also have the ability to infuse glucagon alongside insulin, with the aim of preventing severe hypos and allowing even tighter blood glucose control. - -An artificial pancreas can be thought of as an [“autopilot for your diabetes”]. (https://www.artificialpancreasbook.com/) What does that mean? In an aircraft, an autopilot does not do the complete job of the human pilot, the pilot cannot sleep through the entire flight. The autopilot aids the work of the pilot. It relieves them of the burden of permanently monitoring the aircraft, allowing the pilot to concentrate on wider monitoring from time to time. The autopilot receives signals from various sensors, a computer evaluates them together with the pilot’s specifications and then makes the necessary adjustments, alerting the pilot to any concerns. The pilot no longer has to worry about constantly making decisions. - -## What does hybrid closed loop mean? - -The best solution for type 1 diabetes would be a “functional cure” (probably an implant of pancreatic cells which are protected from the immune system). While we are waiting for that, a “full closed loop” artificial pancreas is probably the next best thing. This is a tech system that doesn’t need any user input (like bolusing insulin for meals, or announcing exercise), with good regulation of blood glucose levels. At the moment, there are no widely available systems which are “full” closed loop, they all need some user input. The currently available systems are called “hybrid” closed loop, because they use a combination of automated technology and user input. - -## How and why did looping start? - -The development of commercial technology for people with type 1 diabetes (T1D) is very slow. In 2013 the T1D community founded the #WeAreNotWaiting movement. They developed systems themselves using existing approved technology (insulin pumps and sensors) to improve blood glucose control, safety, and quality of life. These are known as DIY (do-it-yourself) systems, because they are not formally approved by health bodies (FDA, NHS etc). There are four main DIY systems available: OpenAPS, **AAPS**, Loop and iAPS. - -A great way to understand the fundamentals of DIY looping is to read Dana Lewis’s book “Automated Insulin Delivery”. You can access it \[here\] (https://www.artificialpancreasbook.com/) for free (or buy a hardcopy of the book). If you want to understand more about OpenAPS, which** AAPS** has developed from, the \[OpenAPS website\] (https://openaps.org/what-is-openaps/) is also a great resource. - -Several commercial hybrid closed loop systems have been launched, the most recent of which are \[CamAPS FX\] (https://camdiab.com/) (UK and EU) and \[Omnipod 5\] (https://www.omnipod.com/en-gb/what-is-omnipod/omnipod-5) (USA and EU). These are very different to DIY systems, mainly because they both include a “learning algorithm” which adjusts how much insulin is delivered according to your insulin needs from previous days. Many people in the DIY community have already tried out these commercial systems and compared them with their DIY system. You can find out more about how the different systems compare by asking on the dedicated Facebook groups for these systems, on the \[AAPS Facebook group\] (https://www.facebook.com/groups/AndroidAPSUsers/) or on \[Discord\] (https://discord.com/invite/4fQUWHZ4Mw). - -## What is Android APS (AAPS)? - -![image](https://github.com/openaps/AndroidAPSdocs/assets/94044064/0f089d96-b7ee-452a-aa9d-aae10ab58971) - -**Figure 1**. Basic outline of the Android APS (Artificial Pancreas System), AAPS. - -Android APS (AAPS) is a hybrid closed loop system, or Artificial Pancreas System (APS). It makes its insulin dosing calculations using established \[OpenAPS\] (https://openaps.org/) algorithms (a set of rules) developed by the #WeAreNotWaiting type 1 diabetes community. - -Since OpenAPS is only compatible with certain older insulin pumps, AAPS (which can be used with a wider range of insulin pumps) was developed in 2016 by Milos Kozak, for a family member with type 1 diabetes. Since those early days, **AAPS** has been continually developed and refined by a team of volunteer computer developers and other enthusiasts who have a connection to the type 1 diabetes world. Today, **AAPS** is used by approximately 10,000 people. It is a highly customisable and versatile system, and because it is open-source, it is also readily compatible with many other open-source diabetes softwares and platforms. The fundamental components of the current **AAPS** system are outlined in Figure 1 above. - -## What are the basic components of AAPS? - -The “brain” of AAPS is an **app** which you build yourself. There are detailed step-by-step instructions for this. You then install the **AAPS app** on a compatible **Android smartphone** (1). A number of users prefer their loop on a separate phone to their main phone. So, you don’t necessarily have to be using an Android phone for everything else in your life, just for running your AAPS loop. - -The **Android smartphone** will also need to have another app installed on it as well as **AAPS**, either a modified Dexcom app called build-your-own dexcom app (**BYODA**) or Xdrip+. This receives glucose data from a sensor (2) by bluetooth, and then sends the data internally on the phone to the **AAPS app**. - -The **AAPS app** uses a decision making process (**algorithm**) from OpenAPS. Beginners start out using the basic **oref0** algorithm, but it is possible to switch to using the newer **oref1** algorithm as you progress with AAPS. Which algorithm you use (oref0 or oref1), depends on which suits your specific situation best. In both cases, the algorithm takes into account multiple factors, and performs rapid calculations every time a new reading comes in from the sensor. The algorithm then sends instructions to the insulin pump (3) on how much insulin to deliver by bluetooth. All the information can be sent by mobile data or wifi to the internet. This data can also be shared with followers if desired, and/or collected for analysis. - -## What are the advantages of the AAPS system? - -The OpenAPS algorithm used by **AAPS** controls blood sugar levels in the absence of user input, according to the users’ defined parameters (important ones being basal rates, insulin sensitivity factors, insulin-to-carb ratios, duration of insulin activity etc.), reacting every 5 minutes to the new sensor data. Some of the reported advantages of using AAPS are extensive fine-tunable options, automations and increased transparency of the system for the patient/caregiver. This can result in better control over your (or your dependent’s) diabetes, which in turn may give improved quality of life and increased peace of mind. - -Practical advantages include: - -- **Hardware flexibility**: **AAPS** works with a wide range of insulin pumps and sensors. So for example, if you develop an allergy to Dexcom sensor patch glue, you could switch to using a Libre sensor instead. That offers flexibility as life changes. You don't have to rebuild, just tick a different box in the AAPS app to change your hardware. - -- **Highly customisable with wide parameters**: here are some examples of the possibilities with AAPS: a) The ability to set a lower glucose target 30 min before eating; you can set the target as low as 72 mg/dL (4.0 mmol/L). b) If you are insulin-resistant resulting in high blood sugars, **AAPS** allows you to set an **automation** rule to activate when BG rises above 8 mmol/L (144 mg/dL), switching to a 120% profile (resulting in an 20% increase in basal and strengthening of other factors too, compared to your normal **profile** setting). The automation will last according to the scheduled time you set. Such an automation could be set to only be active on certain days of the week, at certain times of day, and even at certain locations. c) If your child is on a trampoline with no advance notice, **AAPS** allows insulin suspension for a set time period, directly via the phone. d) After reconnecting a tubed pump which has been disconnected for swimming, AAPS will calculate the basal insulin you have missed while disconnected and deliver it carefully, according to your current BG. Any insulin not required can be overridden by just “cancelling” the missed basal. f) **AAPS** has the ability to set different profiles for different situations and easily switch between them. Features which make the algorithm quicker to bring down elevated BG (like supermicro boluses (“SMB”), unannounced meals, (“**UAM**”) can be set to only work during the daytime, if you are worried about night-time hypos. - - -These are all examples, the full range of features gives huge flexibility for daily life including sport, illness, hormone cycles etc. Ultimately, it is for the user to decide how to use this flexibility, and there is no one-size-fits-all automation for this. - -- **Remote monitoring**: there are multiple possible monitoring channels (Sugarmate, Dexcom Follow, Xdrip+, Android Auto etc.) which are useful for parents/carers and adults in certain scenarios (sleeping/driving) who need customisable alerts. In some apps (Xdrip+) you can also turn alarms off totally, which is great if you have a new sensor “soaking” or settling down that you don’t want to loop with yet. - -- **Remote control**: a significant advantage of **AAPS **over commercial systems is that it is possible for followers, using authenticated text (SMS) commands or via an app (Nightscout or NSClient) to send a wide range of commands back to the ****AAPS** **system. This is used extensively by parents of kids with type 1 diabetes who use AAPS. It is very useful in the playground, for example, if you want to pre-bolus for a snack from your own phone, and your child is busy playing. It is possible to monitor the system (e.g. Fitbit), send basic commands (e.g. Samsung Galaxy watch 4), or even run the entire AAPS system from a high-spec smartwatch (5) (e.g. LEMFO LEM14). In this last scenario, you don’t need to use a phone to run AAPS. As battery life on watches improves, this last option is likely to become increasingly attractive. - -- **No commercial constraints due to open application interfaces**: beyond the use of an open source approach, which allows the source code of **AAPS** to be viewed at any time, the general principle of providing open programming interfaces gives other developers the opportunity to contribute new ideas that allow users to live more easily with their diabetes. This is complementary to commercial systems which adopt the innovations from DIY, where interfaces are only made possible in return for licensing, thus preventing innovations in particular that are not-for-profit. Good examples for such integrations are NightScout, Nightscout Reporter, Xdrip+ M5 stack etc. - -- **Detailed app interface**: It is easy to keep track of things like: insulin levels, cannula age, sensor age, pump battery age, and many actions can be done through the **AAPS** app (priming the pump, disconnecting the pump etc.), instead of on the pump itself. - -- **Accessibility and affordability**: **AAPS** gives people who currently can’t afford to self-fund, or don’t have funding/insurance, access to a world-class hybrid closed looping system which is conceptually years ahead, in terms of development, of the commercial systems being offered by clinics. You currently need to have a Nightscout account to set up **AAPS**. Although the Nightscout account it not necessarily required after setup, many people continue to use Nightscout for collecting their data, and for remote control. So, although **AAPS **itself is free, setting up Nightscout through one of the various platforms may incur a fee (E0 - E12), depending on what level of support you want (see comparison table). **AAPS** works with a wide range of affordable (starting from approx E150) Android phones. In comparison, Loop currently costs around $80 a year for the Apple development licence and CamAPS FX costs around E80/month (as at 2023). - -- ****Support**: No automated insulin delivery system is perfect. Commercial and open-source systems share many common glitches in both communications and temporary hardware failure. There is a community of AAPS users on both Facebook and Discord and Github who designed, developed and are currently using **AAPS** all over the world. There are Facebook support groups and help from clinic/commercial companies for the commercial APS systems - it is worth speaking to the users, or former users of these systems to get feedback on the common glitches, the quality of the education programme and the level of ongoing support provided. - -- **Predictability, transparency and safety**: with no learning algorithm, **AAPS** is logical and in some respect, more predictable, which may make it easier to know when a setting is wrong, and to adjust it accordingly. You can see exactly what the system is doing, why it is doing it, and set its operational limits, which puts the control (and responsibility) in your hands. This can provide the user with confidence, and a sounder sleep. - -- **Access to advanced features through dev modes including full closed loop**: **AAPS **documentation focuses on the mainstream **“master”** branch of **AAPS**, however, research and development is going on all the time. More experienced users may wish to explore the experimental features in the **development** branch such as integration of Dexcom G7, and automatically adjusting insulin delivery according to short-term sensitivity changes (DYNISF), not having to bolus for meals, and generally trying to make life with type 1 diabetes as convenient as possible. - -- **Ability to contribute yourself to further improvements**: type 1 diabetes can be highly frustrating and isolating. Having control over your own diabetes tech, with the possibility to “pay it forward” as soon as you are making progress by helping others on their journey can be really rewarding. You can educate yourself, discover the roadblocks and look for and even contribute to new developments and the documentation. There will be others with the same quest to bounce ideas off and work with. This is the essence of #WeAreNotWaiting. - - -## How does AAPS compare to MDI and open looping? - -Multiple daily injections (MDI, a) usually involve giving an injection of a long-lasting insulin (e.g. Tresiba) once a day, with injections of faster-acting insulin (e.g. Novorapid, Fiasp) at mealtimes, or for corrections. Open pumping (b) involves using a pump to deliver basal at pre-programmed rates of rapid-acting insulin, and then boluses through the pump at mealtimes or for corrections. The basics of a looping system is that the App uses the glucose data to instruct the pump to stop insulin delivery when it predicts you are heading for a low, and to give you extra insulin if your glucose levels are rising and predicted to go too high (c). Although this is oversimplified, (mostly because hybrid closed looping has a lot of additional useful features) the key features of each system are shown in **Figure 2**. - -![image](https://github.com/openaps/AndroidAPSdocs/assets/94044064/4e7d8608-684d-4c69-9c61-88c9539f5d6f) - -**Figure 2**. Overview of (a) MDI, (b) open-loop pumping and (c) hybrid closed loop pumping - -## How does AAPS compare to other looping systems? - -At present there are four major open source closed loop systems available: OpenAPS, **AAPS**, \[Loop\] (https://loopkit.github.io/loopdocs/#what-is-loop) and iAPS, (formerly FreeAPS X). The features of the different systems are shown in the table below: - -| Devicestyp | Name | [Open APS](https://openaps.readthedocs.io/en/latest/) | [AAPS](https://wiki.aaps.app) | [Loop](https://loopkit.github.io/loopdocs/) | [iAPS](https://iaps.readthedocs.io/en/latest/) | -| ---------- | -------------------------------------------------------------------------------------------------------- | ----------------------------------------------------- | ------------------------------------------- | ------------------------------------------- | ---------------------------------------------- | -| PUMP | Older Medtronic | ![available](./images/available.png) | ![available](./images/available.png) | ![available](./images/available.png) | ![available](./images/available.png) | -| PUMP | Older Omnipod (Eros) | ![unavailable](./images/unavailable.png) | ![available](./images/available.png) | ![available](./images/available.png) | ![available](./images/available.png) | -| PUMP | Newer Omnipod (Dash) | ![unavailable](./images/unavailable.png) | ![available](./images/available.png) | ![available](./images/available.png) | ![available](./images/available.png) | -| PUMP | DANA R, DANA RS, DANA I | ![unavailable](./images/unavailable.png) | ![available](./images/available.png) | ![unavailable](./images/unavailable.png) | ![unavailable](./images/unavailable.png) | -| PUMP | Roche Combo, Insight | ![unavailable](./images/unavailable.png) | ![available](./images/available.png) | ![unavailable](./images/unavailable.png) | ![unavailable](./images/unavailable.png) | -| CGM | Dexcom G4, G5, G6 | ![available](./images/available.png) | ![available](./images/available.png) | ![available](./images/available.png) | ![available](./images/available.png) | -| CGM | Libre 1 (requires Miao Miao) | ![available](./images/available.png) | ![available](./images/available.png) | ![available](./images/available.png) | ![available](./images/available.png) | -| CGM | Libre 2 | ![available](./images/available.png) | ![available](./images/available.png) | ![available](./images/available.png) | ![available](./images/available.png) | -| CGM | Libre 3 | | ![unavailable](./images/unavailable.png) | --- | ![unavailable](./images/unavailable.png) | -| CGM | Medtronic Enlite | | --- | ![unavailable](./images/unavailable.png) | --- | -| CGM | [Dexcom G7](https://androidaps.readthedocs.io/en/latest/Hardware/DexcomG7.html) | | ![available](./images/available.png) (beta) | ![available](./images/available.png) | ![available](./images/available.png) | -| CGM | [Eversense](https://androidaps.readthedocs.io/en/latest/Hardware/Eversense.html) | | ![available](./images/available.png) | | ![available](./images/available.png) | -| CGM | [MM640g/MM630g](https://androidaps.readthedocs.io/en/latest/Hardware/MM640g.html) | | ![available](./images/available.png) | | ![available](./images/available.png) | -| CGM | [PocTech](https://androidaps.readthedocs.io/en/latest/Hardware/PocTech.html) | | ![available](./images/available.png) | | ![available](./images/available.png) | -| CGM | [Nightscout as BG Source](https://androidaps.readthedocs.io/en/latest/Hardware/CgmNightscoutUpload.html) | | ![available](./images/available.png) | | ![available](./images/available.png) | -| Phone | Android | ![available](./images/available.png) | ![available](./images/available.png) | ![unavailable](./images/unavailable.png) | ![unavailable](./images/unavailable.png) | -| Phone | iPhone | ![available](./images/available.png) | ![unavailable](./images/unavailable.png) | ![available](./images/available.png) | ![available](./images/available.png) | - -[OpenAPS](https://openaps.readthedocs.io/) was the first Open Source Closed Loop System. Raspberry Pi나 Intel Edison 같은 작은 컴퓨터를 사용합니다. Both AndroidAPS (AAPS) and iAPS use the OpenAPS algorithms, whereas Loop uses a separate algorithm. You can read a comparison of iAPS and **AAPS** here. - -An international peer-reviewed consensus statement containing practical guidance on open source looping was written by and for health-care professionals, and published in a leading medical journal in 2022. It is well worth a read (including for your diabetes clinic) and summarises the main technical differences between the different open-source hybrid closed loop systems: - - Lancet Diabetes Endocrinol, 2022; 10: 58–74 - -[https://www.ncbi.nlm.nih.gov/pmc/articles/PMC8720075/](https://www.ncbi.nlm.nih.gov/pmc/articles/PMC8720075/) - -It is hard to get a “feel” for any system without using it, or talking to others who are using it, so do reach out to others on Facebook/Discord and ask. Most people find that AAPS is incredibly sophisticated in comparison to other hybrid closed loop systems (particularly the commercial systems), with a huge number of potentially customisable settings and features, discussed above. Some people can find this a little overwhelming in the beginning, but there is no rush to investigate all the possibilities at once, you can progress as slowly or as fast as you would like, and there is help available at every step of the way. - -## Does AAPS use artificial intelligence or any learning algorithm? - -아니오. **AAPS** does not have any complicated machine learning algorithms, multiple-parameter insulin response models, or differential equations. As such, the system is open and transparent in how it works, and has the ability to be understood not just by experts, but also by clinicians and patients. It also means that if you have a sharply varying schedule (maybe switching from a stressful week at work to a relaxing holiday) and are likely to need a significantly different amount of insulin, you can immediately switch **AAPS** to run a weaker/stronger profile. A ‘learning system’ will do this adjustment for you automatically, but is likely to take longer to adjust the insulin delivery. - -## Which system is right for me or my dependent? - -Practically, your choice of system is often restricted by which pump you already have, or can obtain from your medical provider, and your choice of phone (Apple or Android). If you don’t yet have a pump you have the biggest choice of systems. Technology is continually evolving, pumps are being discontinued and new pumps and sensors are being released. Most open-source systems work with the main sensors (Libre and Dexcom) or are quickly adapted to work with new sensors a year or so after they are released (with a bit of time delay for safety and stability testing). - -Most **AAPS **users report more time in range, HbA1c reductions, as well as quality of life improvements from having a system that can auto-adjust basal rates overnight during sleep, and this is true for most hybrid closed loop APS. Some people have a preference for a very simple system which is not very customisable (which means you may prefer a commercial system), and others find this lack of control very frustrating (you may prefer an open-source system). If you (or your dependent) are newly diagnosed, a common route is to get the hang of MDI plus sensor first, then progress to a pump which has the potential for looping, then to **AAPS**, but some people (especially small kids) may go straight to a pump. - -It is important to note that the **AAPS** user needs to be proactive to troubleshoot and fix problems themselves, with help from the community. This is a very different mindset to that when using a commercial system. With **AAPS** a user has more control, but also the responsibility, and needs to be comfortable with that. - -## Is it safe to use open-source systems like AAPS? - -A more accurate question is probably “is it safe compared to my current type 1 diabetes insulin delivery system?” since no method of insulin delivery is without risk. There are many checks and balances in place with **AAPS**. A recent paper looked at the use of**** AAPS ****in a computer simulated set-up, [https://www.liebertpub.com/doi/epub/10.1089/dia.2019.0375](https://www.liebertpub.com/doi/epub/10.1089/dia.2019.0375) which was an effective way to unobjectively trial how safe and effective the system is. More generally, it is estimated that over 10,000 individuals worldwide are using open-source automated-insulin delivery systems, and uptake continues to increase globally. - -Any device that uses radio communications could be hacked, and this is true for a non-looping insulin pump as well. Currently, we are not aware of anyone attempting to harm individuals by hacking their diabetes-related medical equipment. However, there are multiple ways to protect against such risks: - -1. In the pump settings, limit both the max bolus allowed and max temporary basal settings to amounts that you believe are safest. These are hard limits that we do not believe any malicious hacker could circumvent. - -2. Set your CGM alarms enabled for both highs and lows. - -3. Monitor your insulin delivery online. Nightscout users can set additional alarms to alert for a wide variety of conditions, including conditions that are much more likely to occur than a malicious attack. In addition to highs and lows, Nightscout can display diagnostic data useful for verifying that the pump is operating as desired, including current IOB, pump temporary basal history, pump bolus history. It can also be configured to proactively alert users to undesirable conditions, such as predicted highs and lows, low insulin reservoir, and low pump battery. - - -If a malicious attack was made on your insulin pump, these strategies would significantly mitigate the risk. Every potential **AAPS** user needs to weigh the risks associated with using **AAPS**, versus the risks of using a different system. - -## How can I approach discussing AAPS with my clinical team? - -Depending on the country - link to doctors section of docs - - Lancet Diabetes Endocrinol, 2022; 10: 58–74 - -[https://www.ncbi.nlm.nih.gov/pmc/articles/PMC8720075/](https://www.ncbi.nlm.nih.gov/pmc/articles/PMC8720075/) - -## Q: Why can’t I just download AAPS and use it straight away? - -The **AAPS** app is not provided in Google Play - you have to build it from source code by yourself for legal reasons. **AAPS** is unlicensed, meaning that it does not have approval by any regulatory body authority in any country. **AAPS**is deemed to be carrying out a medical experiment on yourself, and is carried out at the user’s own risk. - -Setting up the system requires patience, determination and the gradual development of technical knowledge. All the information and support can be found in these documents, elsewhere online, or from others who have already done it. It is estimated that over 2000 people have successfully built and are currently using **AAPS** worldwide. - -The developers of **AAPS**t ake safety incredibly seriously, and want others to have a good experience of using **AAPS**. That is why it is essential that every user (or carer, if the user is a child): - -- builds the AAPS system themself and works through the **objectives** so that they have reasonably good personalised settings and understand the basics of how AAPS ****works by the time they “close the loop”; - -- backs up their system by exporting and saving important files (like keystore and settings .json file) somewhere safe, so you can setup again quickly if needed; - -- updates to newer master versions as and when they become available; and - -- maintains and monitors the system to ensure it is working properly. - - -## Q: What is the connectivity of the AAPS system? - -**Figure 3 (below)** shows one example of the **AAPS** system for a user who do not require any followers interacting with the system: - -![potential AAPS connectivity setup with no followers](./images/intro03.png) - -**Figure 4 (below)** shows the full potential of the **AAPS** system for a user who has followers and requires a monitor and send adjust the system remotely (like a child with T1D): - -![potential AAPS connectivity setup with followers](./images/intro04.png) - -## Q: How does AAPS get continually developed and improved? - -Most **AAPS** users use the fully tested **master** version of AAPS, which has been tested for bugs and problems, before being released to the community. Behind the scenes, the developers try out new improvements, and test these out in “developer” (**dev**) versions of **AAPS** with a user community who are happy to do bug updates at short notice. If the improvements work well, they are then released as a new “master” version of **AAPS**. Any new master release is announced on the Facebook group, so that the mainstream **AAPS** users can read about and update to the new master version. - -Some experienced and confident **AAPS ** users conduct experiments with emerging technologies and with dev versions of the **AAPS** app, which can be interesting for the less adventurous users to read about, without having to do it themselves! People tend to share these experiments on the Facebook group too. - -You can read more about some of these experiments and discussion on emerging tech here: - -[https://www.diabettech.com/](https://www.diabettech.com/) - -[https://bionicwookie.com/](https://bionicwookie.com/) - -## Q: Who can benefit? - -| User Type | -| ------------------------------------------- | -| ✔️ type 1 diabetic | -| ✔️ caregiver or parent of a type 1 diabetic | -| ✔️ blind users type 1 diabetic | -| ✔️ *clincians and healthcare professionals | - -The above table assumes that the user has access to both continuous gluocse monitor and insulin pump. - -*All data from **AAPS** can be made available to healthcare professionals via data sharing platforms, including NightScout that provides logging and real time monitoring of CGM data, insulin delivery, carbohydrate entries, predictions and settings. Nightscout records include daily and weekly reports which can aid healthcare professionals' discussions with type 1 patients with more accurate data on glycemic control and any behavioural considerations. - -## Q: What benefits can I get? - -With investment of your time, **AAPS** can potentially lead to: - -- alleviating the stress and burden of managing type 1 diabetes; - -- reducing the multitude of mundane decisions that arise from type 1 diabetes; - -- the provision of personalised and dynamic insulin dosing based on real-time data which can cut down the need for hypo treatments and reduce hyperglycemia episodes; - -- an increased knowledge of insulin management and confidence to better fine tune your settings; - -- the ability to create automatic settings (**automations**) that are tailored to fit in with your lifestyle; - -- improved sleep quality and overall reduction in the frequency of nighttime interventions; - -- remote monitoring and administration of insulin delivery for caregivers of type 1 diabetics; and - -- streamlining of all your portable diabetic equipment (continuous glucose monitor and insulin portable devices) by replacing them with an android phone controlled by **AAPS**. - - -Ultimately,**AAPS** can empower individuals to better manage their diabetes resulting in stable blood sugars and improved long term health outcomes. - ---- - -## AAPS First Steps - -Welcome. This is an introduction to aid beginners getting started with **AAPS** (or commonly referred to as "looping"). - -## Safety - -“_With great powers comes great responsibilities…_” - -**AAPS** is designed with an extensive set of safety features with limits imposed and gradually removed with completion of the **objectives **(predominately made up of multiple choice questions). An **AAPS** feature will be unlocked as the Objectives are successfully completed. This process will gradually allow the user to migrate from Open Loop to Closed Loop. - -This has been done to achieve the best possible experience with **AAPS** in order to prevent common mistakes that new users tend to make when starting to loop. The safety parameters have been built upon typical errors and general trends **AAPS** developers have observed with new users. Mistakes can happen because the beginner is inexperienced and too eager to get started with AAPS or has overlooked the required materials. Do not worry, we have all been there! - -## Key Principles - -The key principles and concepts of looping must be understood by the user before using **AAPS**. This is achieved by investing your personal time into reading the **AAPS** documentation, and completing the Objectives which is aimed to provide you with a solid platform for safe and effective use of **AAPS**. The volume of **AAPS** documentation may seem overwhelming at first but be patient and trust the process - with the proper approach, you'll get there! The overall process will depend upon the beginner’s progress and completion of objectives can typically take between 6 to 9 weeks . - -## Plan for hiccups - -At the preliminary stages of **AAPS**, you should expect to experience some hiccups whilst trying to fine tune your settings. **AAPS**’ glitches cannot be flushed out until the system is used in everyday life. Please plan accordingly and allow a sensible amount of time to troubleshoot and resolve such issues. - -## Flexibility/Adaptability - -Success with **AAPS** requires a proactive approach, a willingness to reflect on the BG data and flexibility to make the necessary adjustments to **AAPS** in order to improve your outcomes. Just as it is nearly impossible to learn to play a sport by reading about the rules alone, the same can be said of **AAPS**. - -## Technology compatibility - -There are limitations with **AAPS** as it is accessible for only certain types of insulin pumps or CGMs, and some technology may not be available for use in various countries. In order to avoid any disappointment or frustrations, please read please read Component Set Up (Section INSERT). - -## App Build Time - -The time to build the **AAPS**(under Section INSERT) depends on your level of expertise and technical ability. Typically for inexperienced users, it can take up to half a day or a full day (with help from the community) in order to build the **AAPS**. The process will significantly speed up as you become more experienced at building the **AAPS**. To aid the build process there are sections dedicated for: -- list of questions and answers for frequent errors that are likely to occur under FAQs (Section K); -- “How to install AAPS? (Section INSERT) which includes Troubleshooting subsection. - -## Keystore & configurations settings a export file - -A “keystore” is a password encrypted file unique to your own copy of **AAPS**. Your android phone uses it to ensure that nobody else can upgrade your own copy without the keystore. In short, as part of the **AAPS** build, you should: - -- save the your keystore file (.jks file used to sign your app) in a safe place; -- keep a note of your password for your keystore file. - -By doing the above, this will ensure that you can use that exact same keystore file each time an updated version of **AAPS** is created. On average, there will be 2-3 AAPS updates required each year. - -In addition, **AAPS** provides the ability to export all your configuration settings. This ensures that you can safely recover your system while changing phones, upgrading/reinstalling the application with minimum disruption. - -## Troubleshootng - -Please feel free to reach out to the AAPS community if there is anything you feel unsure about - there is no such thing as a silly question! All users with various levels of experience are encouraged to ask questions as necessary. Response times to questions are usually quick, typically only a few hours due to the volume of **AAPS** users. - -a) check the documentation; b) ask AAPS facebook group (https://www.facebook.com/groups/AndroidAPSUsers); and c) ask our discord channel. - -## Section overview - -AAPS documentation is made up of the following Sections: - -[INSERT ONCE SECTIONS /SUB SECTIONS AGREED] ---- diff --git a/docs/CROWDIN/ko/maintaining.md b/docs/CROWDIN/ko/maintaining.md deleted file mode 100644 index 98164a09e49b..000000000000 --- a/docs/CROWDIN/ko/maintaining.md +++ /dev/null @@ -1,28 +0,0 @@ -# Dummy - -## This is a dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - - -## This is another dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - - -## This is another another dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - diff --git a/docs/CROWDIN/ko/optimizing.md b/docs/CROWDIN/ko/optimizing.md deleted file mode 100644 index 98164a09e49b..000000000000 --- a/docs/CROWDIN/ko/optimizing.md +++ /dev/null @@ -1,28 +0,0 @@ -# Dummy - -## This is a dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - - -## This is another dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - - -## This is another another dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - diff --git a/docs/CROWDIN/ko/prepairing.md b/docs/CROWDIN/ko/prepairing.md deleted file mode 100644 index d26fba7ade61..000000000000 --- a/docs/CROWDIN/ko/prepairing.md +++ /dev/null @@ -1,145 +0,0 @@ -# Prepairing - -## Guide to the Android APS doc - -### First Steps -Welcome. This is an introduction to aid beginners to the concept of Do-It-Yourself-APS (Android-Artificial-Pancreas-Systems “AAPS”) is commonly referred to as ‘looping’.. - -#### Safetys -“With great powers come great responsibilities…” - -AAPS is designed with an extensive set of safety features with limits imposed and gradually removed with completion of the [Objectives](https://androidaps.readthedocs.io/en/latest/Usage/Objectives.html) (predominately made up of multiple choice questions). An AAPS feature will be unlocked as the Objectives are successfully completed. This process will gradually allow the user to migrate from Open Loop to Closed Loop. - -This has been done to achieve the best possible experience with AAPS by preventing common mistakes new users tend to make when starting to loop. The safety parameters have been built upon typical errors and general trends AAPS developers have observed with new users. Mistakes can happen because the beginner is inexperienced and too eager to get started with AAPS or has overlooked the required materials. Do not worry, we have all been there! - -#### Key Principles - -The key principles and concepts of looping must be understood by the user before using AAPS. This is achieved by investing your personal time into reading the AAPS documentation, and completing the [Objectives](https://androidaps.readthedocs.io/en/latest/Usage/Objectives.html) which is aimed to provide you with a solid platform for safe and effective use of AAPS. The volume of AAPS documentation may seem overwhelming at first but be patient and trust the process - with the proper approach, you'll get there! The overall process will depend upon the beginner’s progress and completion of objectives which typically take between 6 to 9 weeks . - -#### Plan for hiccups - -At the preliminary stages of AAPS, you should expect to experience some hiccups whilst trying to fine tune your settings. AAPS’ glitches cannot be flushed out until the system is used in everyday life. Please plan accordingly and allow a sensible amount of time to troubleshoot and resolve such issues. - -#### Flexibility/Adaptability - -Success with AAPS requires a proactive approach, a willingness to reflect on the BG data and flexibility to make the necessary adjustments to AAPS in order to improve your outcomes. Just as it is nearly impossible to learn to play a sport by reading about the rules alone, the same can be said of AAPS. - -#### Technology compatibility -There are limitations with AAPS as it is accessible for only certain types of insulin pumps or CGMs, and some technology may not be available for use in various countries. In order to avoid any disappointment or frustrations, please read [Component Set Up (Section E).](https://androidaps.readthedocs.io/en/latest/Configuration/BG-Source.html) - -#### App Build time -The time to build the AAPS (under Section D) depends on your level of expertise and technical ability. Typically for inexperienced users, it can take up to half a day or a full day (with help from the community) in order to build the AAPS. The process will significantly speed up as you become more experienced at building the AAPS.  - -To aid the build process there are sections dedicated for: - -- list of questions and answers for frequent errors that are likely to occur under [FAQs (Section](https://androidaps.readthedocs.io/en/latest/Getting-Started/FAQ.html) K); - -- “[How to install AAPS](https://androidaps.readthedocs.io/en/latest/Installing-AndroidAPS/Building-APK.html)? (Section D) which includes [Troubleshooting](https://androidaps.readthedocs.io/en/latest/Usage/troubleshooting.html) subsection. - - -#### Keystore & configuration settings export  file - -A “keystore” is a password encrypted file unique to your own copy of AAPS. Your android phone uses it to ensure that nobody else can upgrade your own copy without the keystore.In short, as part of the AAPS build, you should: - -1. save the your keystore file (.jks file used to sign your app) in a safe place; - -2. keep a note of your password for your keystore file. - - -By doing the above, this will ensure that you can use that exact same keystore file each time an updated version of AAPS is created. On average, there will be 2-3 updates to the AAPS required each year. In addition, AAPS provides the ability to [export all your configuration settings](https://androidaps.readthedocs.io/en/latest/Usage/ExportImportSettings.html). This ensures that you can safely recover your system while changing phones, upgrading/reinstalling the application with minimum disruption.  - -#### 문제 해결 - -Please feel free to reach out to the AAPS community if there is anything you feel unsure about - there is no such thing as a silly question!  All users with various levels of experience are encouraged to ask questions as necessary. Response times to questions are usually quick, typically only a few hours due to the volume of AAPS users.  - -##### [check the documentation](https://androidaps.readthedocs.io/en/latest/index.html) - -##### [ask our facebook group](https://www.facebook.com/groups/AndroidAPSUsers/) - -##### [ask our discord channel](https://discord.com/channels/629952586895851530/629954570394533889) - -#### Section overview - -AAPS documentation is made up of the following Sections: - -##### [Getting started](https://androidaps.readthedocs.io/en/latest/Getting-Started/Safety-first.html) - -This is a must read to understand the general concept of what an artificial pancreas system is designed to do. - -##### [What do I need?](https://androidaps.readthedocs.io/en/latest/Module/module.html) - -This explains AAPS’ compatibility with CGMs (Continuous Glucose Monitors) and insulin pumps. It also provides a guide on the correct assembly of an AAPS system to ensure that it functions correctly in everyday life. - -##### How to install AAPS - -This section is the manual for building the AAPS. Strict adherence to the step-by-step instructions are required in order to successfully build the AAPS. Please take your time. - -##### [Component Setup](https://androidaps.readthedocs.io/en/latest/Configuration/BG-Source.html) - -This explains how to properly integrate each of the various different separate component parts into AAPS, as well as how to set them up to work as seamlessly as possible together. All components are listed under the separate sections: CGM/FGM, xDrip Settings, Pumps, Phones, Nightscout setup, and Smartwatches. The sensor (BG) values and control of the insulin pump are particularly important information to understand. - -##### Configuration - -This explains how to set and configure your ‘Profile’, ‘Insulin’, ‘BG Source’, ‘Pump’, ‘Sensitivity Detection’, ‘APS’, ‘Loop’, ‘Treatments’. - -##### AAPS Usage - -This section provides a breakdown of the features provided by AAPS. - -##### [General Hints](https://androidaps.readthedocs.io/en/latest/Usage/Timezone-traveling.html) - -Useful tricks on how to tackle looping issues such as time zones, and daylight saving (i.e. Spring Forward/ - Fall Back). - -##### [AAPS](https://androidaps.readthedocs.io/en/latest/Getting-Started/Screenshots.html) for Children - -This is designed for parents or caregivers who want to build an AAPS for their child. It also explains the extra features necessary in order to support and safely control your child’s AAPS remotely.

The concepts in this section should be fully understood in order to competently use this feature. - -##### 문제 해결 - -This section contains links to help solve issues when building or using AAPS. - -##### FAQ - -This section addresses specific questions which tend to come up when building or using AAPS. - -##### [용어](https://androidaps.readthedocs.io/en/latest/Getting-Started/Glossary.html) - -This contains a list of the acronyms (or short-term names) or defined terms developed specifically for AAP (for instance, the terms ‘ISF’ or ‘TT’ have special meanings in AAPS). - -##### [Where to go for help](https://androidaps.readthedocs.io/en/latest/Where-To-Go-For-Help/Background-reading.html)? - -This section is aimed to provide new users with links on resources in order to get help including accessing community support made up of both new and experienced users who can clarify questions, and resolve the usual pitfalls that come with AAPS. - -##### For Clinicians - -This is a section for the clinicians who have expressed interest in open source artificial pancreas technology such as AAPS, or for patients who want to share such information with their clinicians. | - -## what are we going to build? - -### An Android Phone Application - -At the core, AAPS is an android application running from a phone. You are going to build it from scratch by installing tools to download the sourcecode and build the actual application. - -### A reporting server NightScout (or Tidepool) - -In order to fully use AAPS properly you will want to setup a nightscout server. It is used to collect data from AAPS over time and possibly communicate to the application. It is required for parents who want to oversee their children AAPS sessions. It is also key to share data between clinicians and patients to perform analysis over time. - -## How long will it take? - -## Who might AAPS not be suitable for? - -## Where can I get help? - -## Requirements - -### medical - -### technical - -### personal - -### CGMs - -### Insulin Pump - -### Reporting (NS, Tidepool) \ No newline at end of file diff --git a/docs/CROWDIN/lt/Configuration/Dexcom.md b/docs/CROWDIN/lt/Configuration/Dexcom.md deleted file mode 100644 index cb267e23c069..000000000000 --- a/docs/CROWDIN/lt/Configuration/Dexcom.md +++ /dev/null @@ -1,32 +0,0 @@ -# Dexcom G6 - -## Basics first - -* Follow [general CGM hygiene recommendations](../Configuration/BG-Source#cgm-hygiene) -* [Special recommendations for Dexcom G6 and DIY systems](../Configuration/BG-Source#dexcom-g6-diy-systems) *For G6 transmitters manufactured after fall/end of 2018 please make sure to use one of the [latest nightly built xDrip+ versions](https://github.com/NightscoutFoundation/xDrip/releases). Those transmitters have a new firmware and latest stable version of xDrip+ (2019/01/10) cannot deal with it. - -## Setting sensor - -When setting sensor, it is recommended not to press the inserter too firmly in order to avoid bleeding. The sensor thread should not come into contact with blood. - -After setting the sensor, the transmitter can be clicked into the sensor holder. Caution! First click in the square side and then press down the round side. - -## Troubleshooting - -### Connection problems - -Bluetooth connection may be disturbed by other nearby Bluetooth devices such as blood glucose meters, headsets, tablets or kitchen devices such as microwave ovens or ceramic hobs. In this case xdrip does not display any BG values. When bluetooth connection is reestablished the data is backfilled. - -### Sensor Errors - -If recurring sensor errors occur try selecting a different body site to set your sensor. The sensor thread should not come into contact with blood. - -Often a "Sensor Error" can be corrected by immediate drinking and massage around the sensor! - -### Jumpy values - -You might try to change settings for noise blocking in xdrip (Settings - Inter-App Settings - Noise Blocking) i.e. "Block Very High noise and worse". See also [Smoothing BG data](../Usage/Smoothing-Blood-Glucose-Data-in-xDrip.md). - -### New transmitter with running sensor - -If you happen to change transmitter during a running sensor session you might try to remove the transmitter without damaging the sensor mount. A video can be found at . \ No newline at end of file diff --git a/docs/CROWDIN/lt/Configuration/EOFLOW.md b/docs/CROWDIN/lt/Configuration/EOFLOW.md deleted file mode 100644 index d12101b3135a..000000000000 --- a/docs/CROWDIN/lt/Configuration/EOFLOW.md +++ /dev/null @@ -1,155 +0,0 @@ -# EOPatch2 Instruction Manual - -The patch requires the use of rapid-acting U-100 type insulin, such as NovoRapid or Humalog. Use a rapid-acting insulin that is suitable for you according to your doctor’s prescription and inject the prescribed dosage. - -The smallest injectable dose of insulin when using the patch is 0.05 U. The Profile BAS should therefore be set at a minimum value of 0.05 U/hr or more and an interval of 0.05 U/hr, as otherwise there may be an error between the estimated total infusion amount in the Profile and the actual infusion amount in the patch. Likewise, the bolus must also be set and infused with a minimum infusion volume of 0.05 U. - -## Pump Setup -1. On the AndroidAPS home screen, click the hamburger menu in the upper left corner and go to Config Builder. -1. Select 'EOPatch2' in the Pump section. -1. Press the Back key to return to the home screen. - -![Bild1](../../images/EOPatch/Bild1.png) ![Bild2](../../images/EOPatch/Bild2.png) - -## Parametrai -Select EOPATCH2 at the top of the home screen to go to the EOPATCH2 tab. - -Select the EOPatch2 Preferences menu by clicking the three dots in the upper right corner. - -The EOPatch2 Preferences menu offers a menu to set 3 types of notifications. - -### Low reservoir Alerts -A warning appears when the amount of insulin remaining in the reservoir reaches the set value or less while using the patch. It can be set from 10 to 50U in 5U increments. - -### Patch expiration Reminder -This is a reminder to notify you of the time remaining before the current patch expires. It can be set from 1 to 24 hours in 1 hour increments. The initial setting value is 4 hours. - -### Patch buzzer Reminder -This is a reminder function for injections other than basal injection. If you are using an (extended) bolus injection or a temporary basal injection, the patch will make a buzzer sound when the injection starts and when the injection is complete. The initial setting value is Off. - -![Bild3](../../images/EOPatch/Bild3.png) - -## Connecting the Patch - -### Move to patch connection screen - -Select EOPATCH2 at the top of the home screen and click the ACTIVATE PATCH button at the bottom left. - -![Bild4](../../images/EOPatch/Bild4.png) - -### Connecting the patch -Insert the syringe needle into the insulin inlet on the patch and then slowly push the piston to inject the insulin. When insulin is filled with more than 80U, the patch makes a booting sound (1 buzzer) and boots. After confirming the buzzer sound, click the START PAIRING button on the screen. - -[Warning] - -- Do not turn the needle action lever until instructed. It can cause serious problems during injection or safety checks otherwise. -- The amount of insulin that can be injected into the patch is 80~200U. If you inject less than 80U into the patch initially, the patch will not work. -- Take the insulin to be put into the patch from the refrigerator and leave it at room temperature for 15 to 30 minutes beforehand. The temperature of the insulin to be injected must be at least 10°C. - -![Bild5](../../images/EOPatch/Bild5.png) - -### patch pairing -The Patch pairing screen will be displayed, and pairing will be attempted automatically. If communication is successful, the Bluetooth pairing request notification appears. Click OK and when the Bluetooth pairing request notification appears a second time with the authentication code, select OK again. - -[Warning] - -- For pairing, the patch and the smartphone must be located within 30 cm of each other. -- After the patch booting is completed, the patch will beep every 3 minutes until the pairing is complete. -- After booting the patch, the patch application must be completed via the app within 60 minutes. If the application cannot be completed within 60 minutes, the patch should be discarded. - -![Bild6](../../images/EOPatch/Bild6.png) ![Bild7](../../images/EOPatch/Bild7.png) ![Bild8](../../images/EOPatch/Bild8.png) - - -### patch preparation -After removing the adhesive tape of the patch, check if the needle is sticking out. If there are no problems with the patch, click NEXT. - -![Bild9](../../images/EOPatch/Bild9.png) - -### Patch attachment -Insulin should be injected in a spot with subcutaneous fat but few nerves or blood vessels, so it is recommended to use the abdomen, arm, or thigh for the patch attachment site. Choose a patch attachment site and apply the patch after disinfecting the location. - -[Warning] - -- Make sure to straighten the side of the patch tape attached to the body evenly, so that the patch adheres completely to the skin. -- If the patch does not stick completely, air may enter between the patch and the skin, which can weaken the adhesive strength and waterproof effect of the patch. - -![Bild10](../../images/EOPatch/Bild10.png) - -### Safety Check -When patching is complete, touch Start Safety Check. When the safety check is completed, the patch will beep once. - -[Warning] - -- For safe use, do not turn the needle action lever until the safety check has been completed. - -![Bild11](../../images/EOPatch/Bild11.png) ![Bild12](../../images/EOPatch/Bild12.png) - - -### Inserting the needle -The needle is inserted by holding around the patch and turning the needle action lever more than 100° in the upward direction of the lever. There is a buzzer sound when the needle is inserted correctly. Turn the needle action lever further clockwise to release the lever. Click NEXT. - -[Caution] - -- If you go to the next step without the buzzer sounding, a needle insertion error warning will appear. - -## Discarding the patch -Patches must be replaced in the case of low insulin levels, usage expiration, and defects. The recommended usage period for each patch is 84 hours after booting the patch. - -### Discarding the patch -Select EOPATCH2 at the top of the home screen and click the DISCARD/CHANGE PATCH button at the bottom. On the next screen, click the DISCARD PATCH button. A dialog box appears to confirm once more and if you select the DISCARD PATCH button, the disposal is completed. - -![Bild13](../../images/EOPatch/Bild13.png) ![Bild14](../../images/EOPatch/Bild14.png) ![Bild15](../../images/EOPatch/Bild15.png) ![Bild16](../../images/EOPatch/Bild16.png) - -## Suspending and Resuming Insulin Delivery -Suspending insulin delivery also cancels both extended bolus and temporary basal. When resuming insulin delivery, the canceled extended bolus and temporary basal will not be resumed. And when insulin delivery is suspended, the patch will give a sound every 15 minutes. - -### Suspending insulin delivery -Select EOPATCH2 at the top of the home screen and click the SUSPEND button at the bottom right. When you select CONFIRM in the confirmation box, a time selection box appears. If you select the CONFIRM button after selecting the time, the insulin delivery will be suspended for the set amount of time. - -![Bild17](../../images/EOPatch/Bild17.png) ![Bild18](../../images/EOPatch/Bild18.png) ![Bild19](../../images/EOPatch/Bild19.png) - - -### Resuming insulin delivery -Select EOPATCH2 at the top of the home screen and click the RESUME button at the bottom right. Insulin delivery will resume by selecting CONFIRM in the confirmation dialog box. - -![Bild20](../../images/EOPatch/Bild20.png) ![Bild21](../../images/EOPatch/Bild21.png) - -## Alarms/Warnings - -### Alarm - -Alarms are issued for emergency situations of the highest priority and require immediate action. The alarm signal does not disappear or time out until it is acknowledged. An alarm occurs when there is a problem with the patch being used, so there may be cases where the patch in use needs to be discarded and replaced with a new patch. The warning is displayed as a dialog box and switching to another screen is not possible until processing is completed. - -![Bild22](../../images/EOPatch/Bild22.png) ![Bild23](../../images/EOPatch/Bild23.png) - -The different types of alarms are explained below. - -| Alarms | Explanation | -| -------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| Empty reservoir | Occurs when the patch’s reservoir runs out of insulin. | -| Patch expired | Occurs when the patch usage time has expired, and no further insulin injections are possible. | -| Occlusion | Occurs when it appears that the patch's insulin inlet is clogged. | -| Power on self-test failure | Occurs when the patch finds an unexpected error during the post-boot self-test process. | -| Inappropriate temperature | Occurs when the patch is outside the normal operating temperature range during patch application and use. To deal with this alarm, move the patch to an appropriate operating temperature (4.4 to 37°C) condition. | -| Needle insertion Error | Occurs when needle insertion is not normal during the patch application process. Check that the needle insertion edge of the patch and the needle activation button are in a straight line. | -| Patch battery Error | Occurs just before the patch’s internal battery runs out and powers off. | -| Patch activation Error | Occurs when the app fails to complete the patching process within 60 minutes after the patch is booted. | -| Patch Error | Occurs when the patch encounters an unexpected error while applying and using the patch. | - -### Warning - -A warning occurs in a medium or low-priority situation. When a warning occurs, it is displayed as a notification in the Overview screen. - -![Bild24](../../images/EOPatch/Bild24.png) - -The different types of warnings are explained below. - -| Warnings | Explanation | -| ---------------------------- | ------------------------------------------------------------------------------------------------------------------------------------- | -| End of insulin suspend | Occurs when the time set by the user has elapsed after the insulin infusion suspension has been completed. | -| Low reservoir | Occurs when the remaining amount of insulin in the patch is below the set amount. | -| Patch operating life expired | Occurs when the patch usage period is over. | -| Patch will expire soon | Occurs 1 hour before the patch must be discarded. | -| Incomplete Patch activation | Occurs when more than 3 minutes have elapsed due to an interruption during patch application in the stage after pairing is completed. | -| Patch battery low | Occurs when the patch's battery is low. | - diff --git a/docs/CROWDIN/lt/Configuration/Hardware/index.md b/docs/CROWDIN/lt/Configuration/Hardware/index.md deleted file mode 100644 index 9215e2770d45..000000000000 --- a/docs/CROWDIN/lt/Configuration/Hardware/index.md +++ /dev/null @@ -1,27 +0,0 @@ -# Hardware-Configuration - -## Configuration - -## BG Source - -- [BG Source](../BG-Source.md) -- [xDrip+ Settings](../xDrip.md) -- [Dexcom G6 hints](../Dexcom.md) -- [Smoothing blood glucose data](../../Usage/Smoothing-Blood-Glucose-Data-in-xDrip.md) - -## Pumps - -- [Dana-R pump](../DanaR-Insulin-Pump.md) -- [Dana-RS pump](../DanaRS-Insulin-Pump.md) -- [Accu-Chek Combo pump](../Accu-Chek-Combo-Pump.md) -- [Accu-Chek Insight pump](../Accu-Chek-Insight-Pump.md) -- [Medtronic pump](../MedtronicPump.md) - -## Phones - -- [Jelly Pro Settings](../../Usage/jelly.md) -- [Huawei Settings](../../Usage/huawei.md) - -## Smartwatch - -- [Watchfaces](../Watchfaces.md) diff --git a/docs/CROWDIN/lt/Getting-Started/ClosedLoop.md b/docs/CROWDIN/lt/Getting-Started/ClosedLoop.md deleted file mode 100644 index 78e238b0e05a..000000000000 --- a/docs/CROWDIN/lt/Getting-Started/ClosedLoop.md +++ /dev/null @@ -1,55 +0,0 @@ -# Kas yra uždaro ciklo sistema? - -![AAPS yra tarsi autopilotas](../images/autopilot.png) - -Dirbtinės kasos uždaro ciklo sistema sujungia įvairius komponentus, kad būtų lengviau valdyti diabetą. In her great book [Automated Insulin Delivery](https://www.artificialpancreasbook.com/) Dana M. Lewis, one of the founders of the open source closed loop movement, calls it an ["autopilot for your diabetes"](https://www.artificialpancreasbook.com/3.-getting-started-with-your-aps). Bet ką tai reiškia? - -**Autopilot in an aircraft** - -Autopilotas neatlieka viso darbo, todėl nesuteikia pilotui galimybės miegoti viso skrydžio metu. Jis palengvina pilotų darbą. Jis atleidžia juos nuo nuolatinio orlaivio ir skrydžio stebėjimo naštos. Tai leidžia pilotui sutelkti dėmesį į oro erdvės stebėjimą ir autopiloto funkcijų valdymą. - -Autopilotas priima signalus iš įvairių jutiklių, kompiuteris juos įvertina kartu su piloto specifikacijomis, tada atlieka reikiamus pakeitimus. Pilotui nebereikia jaudintis dėl nuolatinio reguliavimo. - -**Closed Loop System** - -Tas pats pasakytina ir apie dirbtinę kasos sistemą. Ji neatlieka visų darbų, vis tiek turite kontroliuoti savo diabetą. Uždaro ciklo sistema sujungia stebėjimo sensoriaus duomenis su diabeto valdymo parametrais, tokiais kaip valandinė bazė, jautrumo insulinui faktorius ir angliavandenių santykis. Remdamasi tuo, ji apskaičiuoja terapijos pasiūlymus ir atlieka nuolatinius mažus koregavimus, kad diabetas išliktų tiksliniame diapazone ir išgelbėtų jus nuo šios priežiūros. Tai palieka daugiau laiko GYVENTI sergant diabetu. - -Lygiai taip pat, kaip niekas nenori patekti į lėktuvą, kurį valdo tik autopilotas be žmogaus kontrolės, uždaro ciklo sistema padeda mums valdyti diabetą, tačiau visada reikia mūsų palaikymo! **Even with a closed loop you can't just forget your diabetes!** - -Panašiai, kaip autopilotas priklauso nuo jutiklių ir pilotų nustatytų parametrų, norint sėkmingai palaikyti jūsų kūną, uždaro ciklo sistemai reikalingi atitinkami įvesties duomenys, tokie kaip valandinė bazė, jautrumo insulinui faktorius ir angliavandenių santykis. - -## Atvirojo kodo Dirbtinės kasos Uždaro ciklo sistemos - -Šiuo metu yra trys pagrindinės atvirojo kodo uždaro ciklo sistemos: - -### AndroidAPS (AAPS) - -AAPS is described in detail in [this documentation](./WhatisAndroidAPS.html). Insulino pompai valdyti bei skaičiavimams atlikti naudojamas Android išmanusis telefonas. It is in strong collaboration with OpenAPS (i.e. they share algorithms). - -Compatible [pumps](../Hardware/pumps.md) are: - -- [DanaR](../Configuration/DanaR-Insulin-Pump.md) / [DanaRS & Dana-i](../Configuration/DanaRS-Insulin-Pump.html) -- [Accu-Chek Combo](../Sąranka/Accu-Chek-Combo-Siurblys.md) -- [Accu-Chek Insight](../Configuration/Accu-Chek-Insight-Pump.md) -- [Diaconn G8](../Configuration/DiaconnG8.md) -- [Omnipod DASH](../Configuration/OmnipodDASH.md) -- [Omnipod Eros](../Configuration/OmnipodEros.md) -- some old [Medtronic pumps](../Configuration/MedtronicPump.md) - -### OpenAPS - -[OpenAPS](https://openaps.readthedocs.io) was the first Open Source Closed Loop System. Ji naudoja mažąjį kompiuterį, tokį kaip Raspberry Pi ar Intel Edison. - -Suderinamos pompos yra: - -- some old Medtronic pumps - -### Loop - iOS sistemai - -[Loop for iOS](https://loopkit.github.io/loopdocs/) is the Open Source Closed Loop System to be used with Apple iPhones. - -Suderinamos pompos yra: - -- Omnipod DASH -- Omnipod Eros -- some old Medtronic pumps diff --git a/docs/CROWDIN/lt/Getting-Started/GlossaryTest.md b/docs/CROWDIN/lt/Getting-Started/GlossaryTest.md deleted file mode 100644 index 14b131ae5019..000000000000 --- a/docs/CROWDIN/lt/Getting-Started/GlossaryTest.md +++ /dev/null @@ -1,391 +0,0 @@ -# Terminų žodynas - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
TerminasAprašymasTaip pat žiūrėtiIšsamiau
AAPSAndroidAPS - dirbtinės kasos sistema  
AMAaukštesnysis (išmanusis) maisto asistentas - patobulintas algoritmas angliavandeniams tvarkytiMA / SMBWiki - AMA
Android autorodo AAPS pranešimus suderinamose automobilių borto kompiuterių sistemose Wiki - android auto
APKprograminės įrangos įdiegimo failas (Android programų paketas) Wiki - APK kūrimas
Autosensjautrumo insulinui pokyčių dėl fizinio krūvio, hormonų ir kt. nustatymas. DIABETTECH - Autosens
Azuredebesų kompiuterijos platforma Nightscout duomenims talpintiHeroku / NightscoutAzure
BATišsikraunančios baterijos būsenos indikatorius pagrindiniame ekraneKAT / REZ / SENNuostatos
Ekrano vaizdai
KGkraujo glikemija  
KGSkraujo glikemijos sąveika - tikėtinas glikemijos pokytis, pagrįstas vien aktyviu insulinu  
Glikemijos šaltinisDuomenų apie gliukozės kiekį kraujyje šaltinisNGJ / SGJWiki - glikemijos šaltinis
Blukon NightreaderFreestyle Libre sensoriaus Bluetooth siųstuvas, naudojamas kaip NGJBlueReader / MiaoMiaoAmbrosia Blukon Nightreader
VBvalandinė bazė  
KAMŽkaniulės amžius - rodomas Nightscout, jei informacija buvo įvesta AAPS skirtuke Priežiūra arba AAPS veiksmų skirtuke "pradinis užpildymas“Nightscout 
KATpagrindiniame ekrane pateikiamas būsenos indikatorius, kad laiku nepakeistas kateterisBAT / REZ / SENNuostatos
Ekrano vaizdai
NGJnuolatinis gliukozės jutiklis  
Uždaras Ciklasuždaras ciklas - sistema, remdamasi algoritmu, atlieka automatinius bazės pakeitimus, nereikalaudama vartotojo patvirtinimoAtviras CiklasWiki uždaras ciklas
AAOaktyvūs angliavandeniai organizme  
IVTinsulino veikimo trukmė Wiki insulino tipai
DIABETTECH - DIA
DSTvasaros / žiemos laikas  Wiki DST
iAV„Ištęsti angliavandeniai“ organizme išdalinami per kelias valandas, kai maiste yra daug riebalų / baltymų.
Ši funkcija pakeičia ištęstą bolusą, žinomą iš klasikinio pompos naudojimo, kuris netenka prasmės, kai naudojamas uždaras ciklas		SMBWiki - iAV
iAV naudojimo atvejai
SGJskanuojamas gliukozės jutiklis (Freestyle Libre) Wiki - glikemijos šaltinis
gitversijos valdymo sistema, skirta kompiuterių failų pokyčių stebėjimui ir darbui su šiais failais koordinuoti
-> būtina, kai reikia atnaujinti APK		 Wiki - atnaujinti APK
GitHubžiniatinklio versijos valdymo paslauga Git naudotojams
- šaltinio kodo saugykla		 Github AndroidAPS
Glimpprograma duomenų skaitymui iš Freestyle Libre Nightscout su Glimp
Herokudebesų kompiuterijos platforma Nightscout duomenims talpintiAzure / NightscoutHeroku
IA (arba I:A)insulino - angliavandenių santykis (Kiek vienas vienetas insulino dengia angliavandenių?)  
AIOaktyvus insulinas organizme  
JIFjautrumo insulinui faktorius - numatomas glikemijos sumažėjimas, sušvirkštus vieną vienetą insulino  
ŽGSŽemos glikemijos stabdymas
AAPS sumažins valandinę bazę, jei krenta glikemijos lygis. Bet jei gliukozės kiekis kraujyje didėja, AAPS algoritmas padidins valandinę bazę tik tuo atveju, jei aktyvus insulinas AIO yra neigiamas (dėl ankstesnio bazės stabdymo). Kai AIO yra teigiamas, valandinė bazė išliks tokia, kaip nustatyta jūsų pasirinktame profilyje. Dėl to Jūs galite patirti laikinus staigius glikemijos šuolius, ypač po hipoglikemijos korekcijos, nes neturėsite galimybės padidinti valandinės bazės.		6 tikslas 
LineageOSnemokama ir atviro kodo operacinė sistema, skirta išmaniesiems telefonams ir pan.
alternatyvi OS išmaniesiems telefonams, kuriuose neveikia Android 8.1 (Oreo)
(kai naudojate Accu-Chek Combo)		 Wiki - Combo pompa
Žurnalo failaiįrašo visus AAPS veiksmus. Naudojama norint išsiaiškinti, išspręsti problemas, suderinti programinę įrangą Wiki - žurnalo failai
maksAIOsaugumo funkcija: didžiausias leistinas bendras aktyvaus insulino lygis, kurio AAPS negali viršyti Wiki - maksAIO
Wiki - SMB
MiaoMiaoFreestyle Libre sensoriaus Bluetooth siųstuvas, naudojamas kaip NGJBlueReader / Blukon NightreaderMiaoMiao
min_5m_AV_įtakasaugumo funkcija - standartinis angliavandenių įsisavinimo laikas. Naudojamas, jei jo negalima dinamiškai nustatyti atsižvelgiant į glikemiją Wiki - konfigūratorius
Nightscoutatvirojo kodo projektas, skirtas prieigai prie NGJ duomenųNightscout ReporterNightscout
NS ClientAAPS dalis, skirta keistis duomenimis su Nightscout serveriu Wiki - NS Client
Nightscout ReporterNightscout duomenų PDF ataskaitų kūrimo įrankisNightscoutNightscout Reporter
NR Reporter @ Facebook
TikslaiAAPS mokymo programa su palaipsniu perėjimu iš atviro į uždarą ciklą Wiki - tikslai
OpenAPSopen artificial pancreas system
APS run on small computers (i.e. Raspberry Pie)
AAPS uses some of the OpenAPS features		 OpenAPS dokumentacija
Atviras Ciklasbūsena, kai sistema rekomenduoja rankinius pompos nustatymusUždaras CiklasWiki - konfigūratorius
Oref0 / Oref1Jautrumo (insulinui) nustatymas
OpenAPS naudojama pagrindinio algoritmo versija 0/1		 Wiki - Jautrumo nustatymas
Piko laikaslaikas, po kurio suleisto insulino poveikis tampa maksimalus Wiki - konfigūratorius
PIpompos istorija (įrašas Terapijos skirtuke) Ekrano nuotraukos
Prognozėsglikemijos prognozės ateityje, remiantis skirtingais skaičiavimo algoritmais Wiki - glikemijos prognozavimo linijos
Profilispagrindiniai terapijos nustatymai (bazė, IVT, IA, JIF, tikslinė glikemija).
Galima nustatyti lokaliai arba per Nightscout		NightscoutWiki - profilis
Profilio keitimas(laikinas) profilio pakeitimas arba procentinis padidinimas / sumažinimas Wiki - profilio keitimas
REZpagrindiniame ekrane pateikiamas būsenos indikatorius, kad laiku nepakeistas rezervuarasBAT / KAT / SENNuostatos
Ekrano vaizdai
RileyLinkįtaisas, skirtas mažos energijos Bluetooth (BLE) turinčių prietaisų susiejimui su 916 MHz dažnio įrenginiais (senesnėms Medtronic pompoms)OpenAPS 
SAMŽsensoriaus amžius - rodomas Nightscout svetainėje, jei informacija įvedama AAPS Priežiūros skirtukeNightscout 
SENpagrindiniame ekrane pateikiamas būsenos indikatorius, kad laiku nepakeistas sensoriusBAT / KAT / REZNuostatos
Ekrano vaizdai
Jautrumo nustatymasjautrumo insulinui pokyčių dėl fizinio krūvio, hormonų ir kt. nustatymas. DIABETTECH - Autosens
Sensoriaus triukšmasnestabilūs NGJ duomenys, pasireiškiantys dideliais glikemijos reikšmių svyravimais Wiki - sensoriaus triukšmas
SMBsuper mikro bolusas
pažangi technologija, leidžianti greičiau sureguliuoti glikemijos lygį		NDMWiki - SMB
Super bolusasbazinio insulino pridėjimas prie boluso greitesnei glikemijos korekcijai John Walsh - The Super Bolus
PBpagrindinė bazė (bazinis insulino kiekis per 24 valandas)  
LBlaikina bazė  
BPDbendra paros dozė = bolusai + bazė per dieną  
LTlaikinas tikslas
laikinas glikemijos tikslo (diapazono) padidinimas / sumažinimas		 Wiki - laikini tikslai
NDMnedeklaruotas maistas - reikšmingo glikemijos kilimo dėl neįvesto maisto, adrenalino ar kito poveikio nustatymas ir bandymas kompensuoti per SMB mechanizmąSMBWiki - SMB
Virtuali pompagalimybė naudoti AAPS su pompa, kuri neturi palaikomos tvarkyklėsAtviras Ciklas 
FonasAndroidAPS fono paveikslėlisžr. psl. Telefonai
xDrip / xDrip+atviro kodo programinė įranga skaityti NGJ sistemas xDrip+
xDrip
Zero-temp / Laikina nulinė bazė0% laikina valandinė bazė (insulinas netiekiamas)  
Taip pat žr. https://openaps.readthedocs.io/en/latest/docs/Resources/glossary.html
diff --git a/docs/CROWDIN/lt/Getting-Started/Safety-first.md b/docs/CROWDIN/lt/Getting-Started/Safety-first.md deleted file mode 100644 index 3325112d068b..000000000000 --- a/docs/CROWDIN/lt/Getting-Started/Safety-first.md +++ /dev/null @@ -1,41 +0,0 @@ -# Saugumas - svarbiausia - -**When you decide to build your own artificial pancreas, it's always important to think about security and safety, and to understand the impact of all your actions** - -## Bendrieji - -- AAPS is a just a tool to help you manage diabetes, it is not a fully automated system you can install and forget! -- Do not assume that AAPS will never make mistakes. AndroidAPS kontroliuoja jūsų insulino tiekimą: visada stebėkite ją, suvokite, kaip ji veikia, ir mokykitės interpretuoti jos veiksmus. -- Remember that, once paired, the phone can instruct the pump to do anything. Only use this phone for AAPS and, if being used by a child, essential communications. Neįdiekite nereikalingų programų ar žaidimų (!!!!!), kurie galėtų privilioti kenkėjiškas programas, pvz., Trojos arklius, virusus ar botus, kurie gali sutrikdyti jūsų sistemą. -- Install all security updates provided by your phone manufacturer and Google. -- You might also need to change your diabetes habits as you change your therapy by using a closed loop system. pvz., some people report, they need less hypo treatments as AAPS has already reduced insulin. - -## SMS komunikatorius - -- AAPS allows you to control a child's phone remotely via text message. Jei įgalinate šį SMS komunikatorių, visada prisiminkite, kad telefonas, duodantis nuotolinio valdymo komandas, gali būti pavogtas. Todėl visada jį apsaugokite bent PIN kodu. -- AAPS will also inform you by text message if your remote commands, such as a bolus or a profile change, have been carried out. Patartina tai nustatyti taip, kad patvirtinimo tekstai būtų siunčiami bent dviem skirtingais telefono numeriais, jei pavogtas vienas iš priimančių telefonų. - -(Safety-first-aaps-can-also-be-used-by-blind-people)= -## AAPS can also be used by blind people - -On Android devices TalkBack is part of the operating system. It is a program for screen orientation via voice output. With TalkBack you can operate your smartphone as well as AAPS blind. - -We users create the AAPS app ourselves with Android Studio. Many use Microsoft Windows for this purpose, where there is the Screenreader analogous to TalkBack. Since Android Studio is a Java application, the "Java Access Bridge" component must be enabled in the Control Panel. Otherwise, the screen reader of the PC will not speak in Android Studio. - -To do this, please proceed as follows: - -- Press WINDOWSTASTE and enter "Control Panel" in the search field, open with Enter. It opens: "All Control Panel Items". -- Press the letter C to get to "Center for Ease of Use", open with Enter. -- Then open "Use computer without a screen" with Enter. -- There, at the bottom, you will find the checkbox "Enable Java Access Bridge", select it. -- Done, just close the window! The screen reader should work now. - -```{note} -**IMPORTANT SAFETY NOTICE** - -The foundation of AAPS safety features discussed in this documentation is built on the safety features of the hardware used to build your system. Labai svarbu, kad insulino pompa ir CGM sistema, naudojama uždaro ciklo sistemai su automatiniu insulino tiekimu, būtų tinkamai išbandytos ir visiškai veikiančios, pažymėtos CE ženklu (Europoje) kaip medicinos prietaisai. Šių komponentų aparatinės ar programinės įrangos pakeitimai gali sukelti netikėtą insulino tiekimą ir taip sukelti didelę riziką vartotojui. If you find or get offered broken, modified or self-made insulin pumps or CGM receivers, *do not use* these for creating an AAPS system. - -Be to, ne mažiau svarbu naudoti tik originalius priedus, tokius kaip įšovikliai, kateteriai ir insulino rezervuarai, patvirtinti jūsų pompos ar CGM gamintojo. Nepatikrintų ar modifikuotų priedų naudojimas gali sukelti CGM sistemos netikslumus ir insulino tiekimo klaidas. Insulinas yra labai pavojingas, jei jis neteisingai dozuotas. Nežaisk su savo gyvenimu naudodamas neišbandytus ar modifikuotus priedus. - -Galiausiai, jūs neturėtumėte vartoti SGLT-2 inhibitorių (glifozinų), nes jie nenuspėjamai sumažina cukraus kiekį kraujyje. Ypač pavojingas derinys su sistema, kuri sumažina bazę siekdama pakelti glikemiją, nes dėl gliflozinų šis glikemijos padidėjimas gali neįvykti ir gali grėsmingai pritrūkti insulino. -``` diff --git a/docs/CROWDIN/lt/Getting-Started/Sample-Setup.md b/docs/CROWDIN/lt/Getting-Started/Sample-Setup.md deleted file mode 100644 index ad0da74ee40f..000000000000 --- a/docs/CROWDIN/lt/Getting-Started/Sample-Setup.md +++ /dev/null @@ -1,151 +0,0 @@ -# Pavyzdinė sąranka: Samsung S7, DanaRS, Dexcom G6 ir Sony Smartwatch - -![Pavyzdinis nustatymas](../images/SampleSetup.png) - -## Aprašymas - -Šiame derinyje Samsung Galaxy S7 išmanusis telefonas naudojamas kaip ciklo valdymo centras. Šiek tiek pakeista Dexcom programa nuskaito glikemijos reikšmes iš Dexcom G6 sensoriaus. AndroidAPS Bluetooth ryšiu valdo korėjiečių gamintojo SOOIL Dana RS pompą. Nereikia jokių papildomų įrenginių. - -Kadangi Dexcom programa siūlo ribotas įspėjimo parinktis, atvirojo kodo xDrip + programa yra sukonfigūruota ne tik aukštos ir žemos glikemijos aliarmams, bet ir kitiems perspėjimams, atsižvelgiant į individualius poreikius. - -Pasirinktinai galite naudoti Android išmanųjį laikrodį (šiame pavyzdyje naudojamas Sony Smartwatch 3 (SWR50)), norėdami matyti savo glikemijos duomenis ir AndroidAPS parametrus. Laikrodis netgi gali būti naudojamas valdyti AndroidAPS (pvz., diskretiškai nustatyti bolusą maistui). - -Sistema veikia neprisijungus. Tai reiškia, kad norint naudotis sistema nereikia prijungti savo išmaniojo telefono prie interneto. - -Tačiau, kai yra interneto ryšys, duomenys automatiškai įkeliami į Nightscout „debesį“. Ši parinktis leidžia beveik bet kuriuo metu pateikti išsamų glikemijos ataskaitą gydytojui ar šeimos nariams. Taip pat galite siųsti duomenis į Nightscout tik naudodami (jei nustatėte) Wi-Fi ryšį, kad galėtumėte kurti įvairias Nightscout ataskaitas. - -## Būtini komponentai - -1. Samsung Galaxy S7 - - * Alternatives: see [list of tested phones and watches](https://docs.google.com/spreadsheets/d/1gZAsN6f0gv6tkgy9EBsYl0BQNhna0RDqA9QGycAqCQc/edit) for AndroidAPS - -2. [DanaRS](http://www.sooil.com/eng/product/) - - * Alternatyvos: - * [Accu-Chek Combo](../Sąranka/Accu-Chek-Combo-Siurblys.md) - * [Accu-Chek Insight](../Configuration/Accu-Chek-Insight-Pump.md) - * [DanaR](../Configuration/DanaR-Insulin-Pump.md) - * [Tam tikri seni Medtronic pompų modeliai (reikalinga papildoma įranga: RileyLink/Gnarl aparatinė įranga, Android telefonas su Bluetooth Low Energy/BLE mikroschemų rinkiniu)](../Configuration/MedtronicPump.md) - * Kitos pompos gali būti suderinamos ateityje, dėl išsamesnės informacijos žr. [ateityje galimos pompos ](Future-possible-Pump-Drivers.md). - -3. [Dexcom G6](https://dexcom.com) - - * Alternatives: see list of possible [BG sources](../Configuration/BG-Source.md) - -4. Pasirinktinai: Sony Smartwatch 3 (SWR50) - - * Alternatives: All [watches with Google Wear OS](https://wearos.google.com/intl/de_de/#find-your-watch) should work fine, for details see [list of tested phones and watches](https://docs.google.com/spreadsheets/d/1gZAsN6f0gv6tkgy9EBsYl0BQNhna0RDqA9QGycAqCQc/edit) for AndroidAPS (OS must be Android Wear) - -## Nightscout nustatymas - -Žr. detaliau [Nightscout nustatymas](../Installing-AndroidAPS/Nightscout.md) - -## Kompiuterio nustatymas - -Norėdami sukurti Android programą iš nemokamo AAPS kodo, savo kompiuteryje ar nešiojamajame kompiuteryje (Windows, Mac, Linux) turite įdiegti Android Studio. Išsamią instrukciją galima rasti čia [Android programos (APK) kūrimas](../Installing-AndroidAPS/Building-APK.md). - -Diegdami Android Studio būkite kantrūs, nes programa į savo kompiuterį atsisiunčia daug papildomų komponentų. - -## Išmanaus telefono nustatymas - -![Išmanusis telefonas](../images/SampleSetupSmartphone.png) - -### Patikrinkite išmaniojo telefono programinę įrangą - -* Menu > Settings > Phone info > Software info: At least "Android-Version 8.0" (successfully tested up to Android version 8.0.0 Oreo - Samsung Experience Version 9.0) -* Norėdami atnaujinti programinę įrangą: Meniu > Nustatymai > Programos atnaujinimas - -### Leisti diegti iš nežinomų šaltinių - -Meniu > Nustatymai> Įrenginio sauga > Nežinomi šaltiniai> slankiklis dešinėje (= aktyvus) - -Saugumo sumetimais šis nustatymas turėtų būti grąžintas į neaktyvų režimą, kai bus įdiegtos visos čia aprašytos programos. - -### Įjunkite Bluetooth - -1. Meniu > Nustatymai > Ryšiai > Bluetooth > slankiklis dešinėje (= aktyvus) -2. Meniu > Nustatymai > Ryšiai > Vieta > slankiklis dešinėje (= aktyvus) - -Vietovės paslaugos („GPS“) turi būti suaktyvintos, kad Bluetooth tinkamai veiktų. - -### Įdiegti Dexcom App (modifikuota versija) - -![Modifikuota Dexcom programėlė](../images/SampleSetupDexApp.png) - -Originali Dexcom programa iš Google Play Store neveiks, nes ji neperduoda duomenų į kitas programas. Todėl reikalinga šiek tiek pakeista mūsų bendruomenės versija. Tik ši modifikuota Dexcom programa gali bendrauti su AAPS. Be to, modifikuota Dexcom programa gali veikti su visais Android išmaniaisiais telefonais, o ne tik su tais, kurie yra [ Dexcom suderinamumo sąraše](https://www.dexcom.com/dexcom-international-compatibility). - -To do this perform the following steps on your smartphone: - -1. Jei originali Dexcom programėlė yra įdiegta: - * Sustabdykite sensorių - * Ištrinkite programas per Meniu > Nustatymai> Programos> Dexcom G6 Mobile > Pašalinti -2. Download and install the [BYODA Dexcom ap](../Hardware/DexcomG6.md#if-using-g6-with-build-your-own-dexcom-app) -3. Start modified Dexcom G6 app, activate/calibrate the sensor according to the given instructions and wait until the warm-up phase is finished. -4. Once the modified Dexcom app shows actual glucose value, setup the warnings (hamburger menu on top left side of the screen) as follows: - * Urgent low `55mg/dl` / `3.1mmol/l` (cannot be disabled) - * Low `OFF` - * High `OFF` - * Rise rate `OFF` - * Fall rate `OFF` - * Signal loss `OFF` - -## Įdiegti AndroidAPS - -1. Follow the instructions to [build the APK](../Installing-AndroidAPS/Building-APK.md#generate-signed-apk) -2. [Transfer](../Installing-AndroidAPS/Building-APK.md#transfer-apk-to-smartphone) the generated APK to your phone -3. [Konfigūruokite AndroidAPS](../Configuration/Config-Builder.md) pagal savo poreikius, naudodamiesi sąrankos vedliu arba rankiniu būdu -4. Šiame pavyzdyje mes naudojome (be kita ko) - -* BG source: `Dexcom G6 App (patched)` -- click cock-wheel and activate `Upload BG data to NS` and `Send BG data to xDrip+` (see [BG source](../Configuration/BG-Source.md)) - -![G5 Settings](../images/SampleSetupG5Settings.png) - -* NS Client activated (see [Nightscout setup](../Installing-AndroidAPS/Nightscout.md)) - -## Įdiegti xDrip+ - -xDrip+ is another mature open source app that offers countless possibilities. In this setup, contrary to what the developers first wrote the app for, xDrip+ is not used to collect glucose data from the Dexcom G6, but only to output alarms and to display the current glucose value including the curve on the Android home screen in the widget. With xDrip+ the alarms can be set much more individually than with the Dexcom software, AAPS or Nightscout (no limitation in the selection of sounds, different alarms depending on day/night time etc.). - -1. Atsisiųskite naujausią stabilią APK xDrip+ versiją naudodamiesi savo išmaniuoju telefonu iš čia:[https://xdrip-plus-updates.appspot.com/stable/xdrip-plus-latest.apk ](https://xdrip-plus-updates.appspot.com/stable/xdrip-plus-latest.apk) - tik ne versiją iš Google Play Store! -2. Įdiekite xDrip+ pasirinkdami atsisiųstą APK failą. -3. Paleiskite xDrip+ ir atlikite šiuos nustatymus (trijų linijų meniu viršuje kairėje) - * Nustatymai> Aliarmai ir perspėjimai> Įspėjimų apie KG lygį sąrašas> Sukurkite įspėjimus (aukštus ir žemus) pagal jūsų poreikius. - * Esamus įspėjimus galima pakeisti ilgai spustelėjus signalo piktogramą. - * Nustatymai > Aliarmai ir perspėjimai > Kalibravimo įspėjimai: išjungti (priminimas per modifikuotą Dexcom programą) - * Nustatymai > Aparatūros duomenų šaltinis> 640G/EverSense - * Nustatymai> Tarp-programų nustatymai> Priimti kalibravimą> `Įgalinta` - * Meniu> Sensoriaus paleidimas (tai tik „forma“, neturi nieko bendra su veikiančiu G6 sensoriumi. Turite jį įjungti, kitaip klaidos pranešimas reguliariai pasirodys.) - -For more information about xDrip+, see here [BG source page](../Configuration/BG-Source.md). - -### Įspėjimo konfigūracijos pavyzdys - -The "Urgent low alarm" (below 55 mg/dl resp. 3,1 mmol) is a standard alarm from the modified Dexcom app that cannot be disabled. - -![xDrip alarms](../images/SampleSetupxDripWarning.png) - -Tip for meetings / church visits / cinema etc..: - -If "Do not disturb" mode is activated in the Samsung Galaxy S7 (Menu > Settings > Sounds and vibration > Do not disturb: slider to right side (= active)), the phone only vibrates during urgent low alarm and does not issue an acoustic warning. For the other alarms set up via xDrip+ you can select whether the silent mode should be ignored (acoustic sound played) or not. - -## Išjunkite energijos taupymą - -On your Samsung Galaxy S7 go to Menu > Settings > Device Maintenance > Battery > Unmonitored Apps > + Add apps: Select the apps AndroidAPS, Dexcom G6 Mobile, xDrip+ and Android Wear (if smartwatch is used) one after the other - -## Pasirinktinai: Sony Smartwatch 3 (SWR50) - -With an Android Wear smartwatch life with diabetes can be made even more inconspicuous. The watch can be used to display the current glucose level, the status of the loop etc. on the wrist. Laikrodis netgi gali būti naudojamas valdyti AndroidAPS (pvz., diskretiškai nustatyti bolusą maistui). To do this, double tap the CGM value of the AAPSv2 watchface. The SWR50 usually runs for a full day until the battery needs to be recharged (same charger as the Samsung Galaxy S7: microUSB). - -![Išmanieji laikrodžiai](../images/SampleSetupSmartwatch.png) - -Details about the information displayed on the watchface can be found [here](../Configuration/Watchfaces.md). - -* Įdiekite Android Wear programą į išmanųjį telefoną per Google Play parduotuvę ir suporuokite SWR50 pagal ten pateiktas instrukcijas. -* AAPS trijų linijų meniu (viršuje kairėje)> Konfigūracija> Bendroji dalis (sąrašo apačioje)> Išmanieji laikrodžiai> suaktyvinti kairėje pusėje, spustelėkite krumpliaratį> Išmaniojo laikrodžio nustatymai > `Valdymas iš laikrodžio` -* Išmaniajame laikrodyje: Ilgai paspauskite ekraną, kad pakeistumėte laikrodžio numatytą ekraną, tada pasirinkite `AAPSv2` -* Jei reikia, iš naujo perkraukite abu prietaisus. - -## Pompos nustatymai - -see [Dana RS pump](../Configuration/DanaRS-Insulin-Pump.md) \ No newline at end of file diff --git a/docs/CROWDIN/lt/Getting-Started/WhatisAndroidAPS.md b/docs/CROWDIN/lt/Getting-Started/WhatisAndroidAPS.md deleted file mode 100644 index e6276e089efc..000000000000 --- a/docs/CROWDIN/lt/Getting-Started/WhatisAndroidAPS.md +++ /dev/null @@ -1,39 +0,0 @@ -# What is a closed loop system with AAPS? - -AAPS is an app that acts as an artificial pancreas system (APS) on an Android smartphone. Kas yra dirbtinės kasos sistema? Tai programa, kuria siekiama padaryti tai, ką daro funkcionuojanti kasa: automatiškai siekia išlaikyti sveiką gliukozės kiekį kraujyje. - -APS negali atlikti tokio pat darbo kaip biologinė kasa, tačiau tai gali palengvinti I tipo cukrinio diabeto gydymą standartine įranga ir paprasta bei saugia programine įranga. Those devices include a continuous glucose monitor (CGM) to tell AAPS about your blood sugar levels and an insulin pump which AAPS controls to deliver appropriate doses of insulin. Programa susisiekia su šiais įrenginiais Bluetooth ryšiu. Dozė apskaičiuojama naudojant algoritmą ar taisyklių rinkinį, sukurtą kitai dirbtinei kasai, vadinamai OpenAPS. OpenAPS turi tūkstančius vartotojų, kurie sukaupė milijonus valandų naudojimo. - -A note of caution: AAPS is not regulated by any medical authority in any country. Using AAPS is essentially carrying out a medical experiment on yourself. Sistemai sukurti reikia ryžto ir techninių žinių. Jei pradžioje vis dar trūksta techninių žinių, pabaigoje jas turėsite. Visą jums reikalingą informaciją galite rasti šiame ir kituose interneto puslapiuose. Arba galite užduoti savo klausimus Facebook grupėse ar kituose forumuose patyrusiems vartotojams. Many people have successfully built AAPS and are now using it entirely safely, but it is essential that every user: - -- Builds the system themselves so that they thoroughly understand how it works -- Adjusts its individual dosage algorithm with his or her diabetes team to work nearly perfect -- Maintains and monitors the system to ensure it is working properly - -```{note} -**Disclaimer and Warning** - -- All information, thought, and code described here is intended for informational and educational purposes only. Nightscout neatitinka jokių privatumo reikalavimų sveikatos priežiūros srityje. Use Nightscout and AAPS at your own risk, and do not use the information or code to make medical decisions. -- Use of code from github.com is without warranty or formal support of any kind. Norėdami gauti daugiau informacijos, perskaitykite šios saugyklos LICENCIJĄ. -- All product and company names, trademarks, servicemarks, registered trademarks, and registered servicemarks are the property of their respective holders. Jie naudojami tik informaciniais tikslais ir nereiškia, kad AAPS priklauso jiems ir kad jie yra palaikomi. - -Please note - this project has no association with and is not endorsed by: [SOOIL](http://www.sooil.com/eng/), [Dexcom](https://www.dexcom.com/), [Accu-Chek, Roche Diabetes Care](https://www.accu-chek.com/), [Insulet](https://www.insulet.com/) or [Medtronic](https://www.medtronic.com/). -``` - -Jei esate pasirengęs priimti šį iššūkį, skaitykite toliau. - -## Primary goals behind AAPS - -- An app with safety built in. To read about the safety features of the algorithms, known as oref0 and oref1, click here () -- An all-in-one app for managing type 1 diabetes with an artificial pancreas and Nightscout -- An app to which users can easily add or remove modules as needed -- An app with different versions for specific locations and languages. -- An app which can be used in open- and closed-loop mode -- An app that is totally transparent: users can input parameters, see results, and make the final decision -- An app which is independent of particular pump drivers and contains a "virtual pump" so users can safely experiment before using it on themselves -- An app closely integrated with Nightscout -- An app in which the user is in control of safety constraints - -## Kaip pradėti - -Žinoma, visa čia pateikiama informacija yra labai svarbi jūsų uždarojo ciklo sistemai, tačiau taip pat normalu, kad daugelis naujų dalykų iš pradžių atrodo painūs. A good orientation is given by the [Module Overview](../Module/module.md) and the [Objectives](../Usage/Objectives.html). diff --git a/docs/CROWDIN/lt/Hardware/DexcomG4.md b/docs/CROWDIN/lt/Hardware/DexcomG4.md deleted file mode 100644 index 4adae91a5899..000000000000 --- a/docs/CROWDIN/lt/Hardware/DexcomG4.md +++ /dev/null @@ -1,6 +0,0 @@ -# Dexcom G4 - -## Jei naudojate G4 su OTG kabelis ("tradicinis" Nightscout) -- If not already set up then download Nightscout Uploader app from the Play Store and follow instructions on [Nightscout](https://nightscout.github.io/). -- In AAPS Preferences enter your Nightscout website and API secret. -- Select NSClient in ConfigBuilder (setting in AAPS). diff --git a/docs/CROWDIN/lt/Hardware/Smartwatch.md b/docs/CROWDIN/lt/Hardware/Smartwatch.md deleted file mode 100644 index c2244b48d215..000000000000 --- a/docs/CROWDIN/lt/Hardware/Smartwatch.md +++ /dev/null @@ -1,10 +0,0 @@ -# Išmanieji laikrodžiai - -Išmanieji laikrodžiai nėra būtini, bet naudingi kai kuriems vartotojams. More details are here: - -- [List of tested phones and smartwatches](../Getting-Started/Phones.md) -- [Watchfaces Wear OS](../Configuration/Watchfaces.md) -- [Troubleshooting Sony Smartwatch SW 3](../Usage/SonySW3.md) - -## Instructions for Building the AAPS Wear APK for Wear OS -https://androidaps.readthedocs.io/en/latest/remote-control.html#building-the-aaps-wear-apk diff --git a/docs/CROWDIN/lt/Installing-AndroidAPS/Building-APK.md b/docs/CROWDIN/lt/Installing-AndroidAPS/Building-APK.md deleted file mode 100644 index d70c4f4532bb..000000000000 --- a/docs/CROWDIN/lt/Installing-AndroidAPS/Building-APK.md +++ /dev/null @@ -1,369 +0,0 @@ -# Android programos (APK) kūrimas - -## Kurti sau, o ne parsisiųsti - -**AAPS is not available as download due to regulation for medical devices. It is legal to build the app for your own use, but you must not give a copy to others! Žr. [DUK](../Getting-Started/FAQ.md) dėl išsamesnės informacijos.** - -## Svarbios pastabos - -* Please use **[Android Studio Giraffe" (2022.3.1)](https://developer.android.com/studio/)** or newer to build the apk. -* [Windows 32-bit systems](troubleshooting_androidstudio-unable-to-start-daemon-process) are not supported by Android Studio - -(Building-APK-recommended-specification-of-computer-for-building-apk-file)= - -## Recommended specification of computer for building apk file - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
OS (Only 64 bit)Windows 8 ar vėlesnėMac OS 10.14 ar vėlesnėBet kurio Linux palaikoma Gnome, KDE, ar Unity DE;  GNU C Library 2.31 ar vėlesnė

CPU (Only 64 bit)

x86_64 CPU architektūra; 2nd generation Intel Core ar naujesnis, ar AMD CPU palaikoma
Windows Hypervisor		ARM-based chips, or 2nd generation Intel Core or newer with support for
Hypervisor.Framework		x86_64 CPU architecture; 2nd generation Intel Core or newer, or AMD processor with support for AMD Virtualization (AMD-V) and SSSE3

RAM

8GB ar daugiau

Diskas

Mažiausiai 30GB laisvos vietos. SSD rekomenduojama.

Raiška

1280 x 800 Mažiausiai

Internetas

Plačiajuostis

- -Please keep in mind that both **64 bit CPU and 64 bit OS are mandatory condition.** If your system DOES NOT meet this condition, you have to change affected hardware or software or the whole system. **It is strongly recommended to use SSD (Solid State Disk) instead of HDD (Hard Disk Drive) because it will take less time when you are building the APS installation apk file.** Recommended is just recommended and it is not a mandatory. However, you may still use a HDD when you are building apk file but note that the building process can take a long time to complete, although once started, you can leave it running unattended. - -* * * - -### Šis straipsnis yra padalintas į dvi dalis. - -* In the overview part there is an explanation on what steps are necessary to build the APK file. -* In the step by step walkthrough part you will find the screenshots of a concrete installation. Because the versions of Android Studio - the software development environment which we will use to build the APK - will change very quickly this will be not identical to your installation but it should give you a good starting point. Android Studio also runs on Windows, Mac OS X and Linux and there might be small differences in some aspects between each platform. If you find that something important is wrong or missing, please inform the facebook group "AAPS users" or in the Discord chat [Android APS](https://discord.gg/4fQUWHZ4Mw) so that we can have a look at this. - -## Apžvalga - -In general, the steps necessary to build the APK file: - -1. [Git diegimas](../Installing-AndroidAPS/git-install.md) -2. [Android Studio įdiegimas](Building-APK-install-android-studio) -3. [Nustatyti git kelią Android Studio parametruose](Building-APK-set-git-path-in-preferences) -4. [Download AAPS code](Building-APK-download-AAPS-code) -5. [Atsisiųskite AndroidAPS SDK](Building-APK-download-android-sdk) -6. [Build the app](Building-APK-generate-signed-apk) (generate signed apk) -7. [Perkelti apk failą į telefoną](Building-APK-transfer-apk-to-smartphone) -8. [Identifikuoti gavėją, jei naudojate xDrip+](xdrip-identify-receiver) - -## Žingsnis po žingsnio instrukcija - -Detailed description of the steps necessary to build the APK file. - -## Įdiegti git (jei neturite) - -Follow the manual on the [git installation page](../Installing-AndroidAPS/git-install.md). - -(Building-APK-install-android-studio)= - -## Android Studio įdiegimas - -The following screenshots have been taken from Android Studio Version Arctic Fox | 2020.3.1. Screens can change in future versions of Android Studio. But you should be able to find your way through. [Help from the community](../Where-To-Go-For-Help/Connect-with-other-users.md) is provided. - -One of the most important things when installing Android Studio: **Be patient!** During installation and setup Android Studio is downloading a lot of stuff which will take its time. - -Download [Android Studio from here](https://developer.android.com/studio/install.html) and install it on your computer. - -On first start you will find the setup wizard: - -Select "Do not import settings" as you have not used it before. - -![Do not import settings](../images/studioSetup/01_ImportSettings.png) - -Decide whether you want to share data with Google or not. - -![Share data with Google](../images/studioSetup/02_DataSharing.png) - -On the following screen click "Next". - -![Welcome screen](../images/studioSetup/03_Welcome.png) - -Select "Standard" installation and click "Next". - -![Standard installation](../images/studioSetup/04_InstallType.png) - -Select the theme for the user interface you like. (In this manual we used "Light".) Then click "Next". - -> ***Note:*** This is just the color scheme. You can select whatever you like (i.e. "Darcula" for dark mode). This selection has no influence on building the APK but the following screenshots might look different. - -![UI color scheme](../images/studioSetup/05_UITheme.png) - -Click "Next" on the "Verify Settings" dialog. - -![Verify settings](../images/studioSetup/06_Overview.png) - -Click on all three license agreement parts and select "Agree". When you have agreed to all, the "Finish" button will be enabled and you can "Finish". - - ![Agree license agreements](../images/studioSetup/07_LicenseAgreement.png) - - -Wait while Android Studio downloads additional components and be patient. Once everything is downloaded button "Finish" turns blue. Click the button now. - -![Downloading components](../images/studioSetup/08_Downloading.png) - -(Building-APK-download-AAPS-code)= - -## Download AAPS code - -* On the Android Studio welcome screen select "Projects" (1) on the left and then "Get from VCS" (2). - - ![Android Studio wizard](../images/studioSetup/20_ProjectVCS.png) - - * If you already opened Android Studio and do not see the welcome screen anymore select File (1) > New (2) > Project from Version Control... (3) - - ![Check out project from version control within Android Studio](../images/AndroidStudio_FileNew.PNG) - - * We will now tell Android Studio were to get the code from: - - * Make sure you have selected "Repository URL" on the left (1). - - * Check if "Git" is selected as version control (2). - * Copy and paste the URL ```https://github.com/nightscout/AndroidAPS``` to the main AAPS repository into the URL textbox (3). - * Choose the directory where you want to save the cloned code (4). - - ![Clone Git](../images/studioSetup/21_CloneURL.png) - -* Click button "Clone" (5). - - ![Clone repository](../images/studioSetup/22_Cloning.png) - -* Do not click "Background" while repository is cloned! - -* After the repository is cloned successfully, Android Studio will open the cloned project. - -* You will be asked whether you want to trust the project. Click on "Trust project"! - - ![Trust project](../images/studioSetup/23_TrustProject.png) - -* In the status bar at the bottom you will see the information that Android Studio is running background tasks. - - ![Background tasks](../images/studioSetup/24_GradleSyncRunning.png) - -* Windows only: Grant access if your firewall is asking for permission. - - ![Firewall permission java](../images/AndroidStudio361_18.png) - -* Once the background tasks are finished you will probably see an error saying that errors occurred (1) or (2) or (3). - - ![SDK licence](../images/studioSetup/25_SyncFailed.png) - - Don't worry, this will be solved soon! - -(Building-APK-set-git-path-in-preferences)= - -## Set git path in preferences - -Make sure [git is installed](../Installing-AndroidAPS/git-install.md) on your computer and you have restarted your computer since installing. - -On the Android Studio welcome screen click "Customize" (1) on the left and then select the link "All settings..." (2): - -![Android Studio settings from welcome screen](../images/studioSetup/10_WizardSettings.png) - -### Windows - -* As windows user, make sure you have restarted your computer after [installing Git](../Installing-AndroidAPS/git-install.md). - -* In the menu, go to File (1) > Settings (2) (or Android Studio > Preferences on Mac). - - ![Open settings](../images/studioSetup/30_Settings.png) - -* Double-click "Version Control" (1) to open the sub-menu. - -* Click Git (2). -* Make sure update method "Merge" (3) is selected. -* Check if Android Studio can locate path to git.exe automatically by clicking the button "Test" (4). - - ![Android Studio settings](../images/studioSetup/11_GitPath.png) - -* If automatic setting is successful git version will be displayed next to the path. - - ![Git version displayed](../images/studioSetup/12_GitVersion.png) - -* Eventually git.exe cannot be found automatically or the Test will result in an error (1): - - ![Git not found](../images/studioSetup/13_GitVersionError.png) - - In this case click on the folder icon (2). - -* Use [search function](https://www.tenforums.com/tutorials/94452-search-file-explorer-windows-10-a.html) in windows explorer to find "git.exe" if you are unsure where git has been installed. You are looking for a file named "git.exe", located in **\bin** folder. - -* Select path to git.exe and make sure you selected the one in ** \bin\ ** folder (3) and click "OK" (4). - - ![Select git manually](../images/studioSetup/14_GitManualSelection.png) - -* Check your selected git path again with the "Test" button as described above. - -* When the git version is displayed next to the path (see screenshot above), close settings window by clicking "OK" button (5). - -### Mac - -* Any git version should work. For example . -* Use homebrew to install git: ```$ brew install git```. -* For details on installing git see the [official git documentation](https://git-scm.com/book/en/v2/Getting-Started-Installing-Git). -* If you install git via homebrew there is no need to change any preferences. Just in case: They can be found here: Android Studio - Preferences. - -(Building-APK-download-android-sdk)= - -## Atsisiųskite AndroidAPS SDK - -* In the menu, go to File (1) > Settings (2) (or Android Studio > Preferences on Mac). - - ![Open settings](../images/studioSetup/30_Settings.png) - -* Double-click on Languages & Frameworks to open its submenu (1). - -* Select Android SDK (2). -* Tick the box left of "Android 9.0 (Pie)" (3) (API Level 28). - - ![SDK settings](../images/studioSetup/31_AndroidSDK.png) - -* Confirm changes by clicking OK. - - ![Confirm SDK changes](../images/studioSetup/32_ConfirmSDK.png) - -* Wait until the SDK download and installation is finished. - - ![Wait during SDK installation](../images/studioSetup/34_DownloadSDK.png) - -* When SDK installation is completed the "Finish" button will turn blue. Click this button. - - ![Finish SDK installation](../images/studioSetup/35_DownloadSDKfinished.png) - -* Android Studio might recommend to update the gradle system. **Never update gradle!** This will lead to difficulties! - -* If you see an information on the lower right side of your Android Studio window that Android Gradle Plugin is ready to update click on the text "upgrade" (1). - - ![No gradle update](../images/studioSetup/36_GradleUpdateRequest.png) - -* In the dialog box the select "Don't remind me again for this project" (2). - - ![No gradle update](../images/studioSetup/37_GradleUpdateDeny.png) - -* Restart Android Studio before you continue. - -(Building-APK-generate-signed-apk)= - -## Generuoti pasirašytą APK (Generate signed APK) - -Signing means that you indicate your app to be your own creation but in a digital way as a kind of digital fingerprint within the app itself. That is necessary because Android has a rule that it only accepts signed code to run for security reasons. For more information on this topic, follow [this link](https://developer.android.com/studio/publish/app-signing.html#generate-key). - -* After Android Studio is started, wait until all background tasks are finished. - - ![Wait for background tasks](../images/studioSetup/40_BackgroundTasks.png) - - * ***Warning:*** If errors occur, do not continue with the following steps. \ Consult the [troubleshooting section](../Installing-AndroidAPS/troubleshooting_androidstudio) for known problems! - - ![Gradle Sync Error](../images/studioSetup/41_GradleSyncError.png) - -* Click "Build" (1) in the menu bar and select "Generate Signed Bundle / APK..." (2). - - ![Kurti apk](../images/studioSetup/42_MenuBuild.png) - -* Select "APK" (1) instead of "Android App Bundle" and click "Next" (2). - - ![APK vietoj rinkinio](../images/studioSetup/43_Apk.png) - -* Make sure that module is set to "AndroidAPS.app" (1). - -* Click "Create new..." (2) to start creating your key store. - - ***Note:*** A key store in this case is nothing more than a file in which the information for signing is stored. It is encrypted and the information is secured with passwords. - - ![Create key store](../images/studioSetup/44_KeystoreNew.png) - -* Click the folder symbol to select a path on your computer for your key store. - - ![Create key store](../images/studioSetup/45_KeystoreDialog.png) - -* Select the path where your key store shall be saved (1). - - ![Create key store](../images/studioSetup/46_KeystorePath.png) - - ***Warning: Do not save in same folder as project. You must use a different directory!*** A good location would be your home folder. - -* Type a file name for your key store (2) and confirm with "OK" (3). - -* Enter (2) and confirm (3) the password for your key store. ![Select key store path](../images/studioSetup/47_KeystoreDialog.png) - - ***Note:*** Passwords for key store and key do not have to be very sophisticated. Make sure to remember those or make a note in a safe place. In case you will not remember your passwords in the future, see [troubleshooting for lost key store](troubleshooting_androidstudio-lost-keystore). - -* Enter an alias (4) for your key. Choose whatever you like. - -* Enter (5) and confirm (6) the password for your key - -* Validity (7) is 25 years by default. You do not have to change the default value. - -* First and last name must be entered (8). All other information is optional. - -* Click "OK" (9) when you are done. - -* Make sure the box to remember passwords is checked (1). So you don't have to enter them again next time you build the apk (i.e. when updating to a new AAPS version). - -* Click "Next" (2). - - ![Remember passwords](../images/studioSetup/48_KeystoreSave.png) - -* Select build variant "fullRelease" (1) and press "Finish". - - ![Select build variant](../images/studioSetup/49_BuildVariant.png) - -* Android Studio will show "Gradle Build running" at the bottom. This takes some time, depending on your computer and internet connection. **Be patient!** - - ![Gradle Running](../images/studioSetup/50_GradleRunning.png) - -* Android Studio will display the information "Generate Signed APK" after build is finished. - - ![Build finished](../images/studioSetup/51_BuildFinished.png) - -* In case build was not successful refer to the [troubleshooting section](../Installing-AndroidAPS/troubleshooting_androidstudio). - -* Click on the notification to expand it. - -* Click on the link "locate". - - ![Locate build](../images/studioSetup/52_BuildLocate.png) - - * If the notification is gone, you can always open the "Event log" and select the same link there. ![Kūrimas sėkmingas - įvykių žurnalas](../images/studioSetup/53_EventLog.png) - -* Your file manager/explorer will open. Navigate to the directory "full" (1) > "release" (2). - - ![APK failo vieta](../images/studioSetup/54_APKlocation.png) - -* "app-full-release.apk" (3) is the file you are looking for! - -(Building-APK-transfer-apk-to-smartphone)= - -## Perkelkite APK į išmanųjį telefoną - -Easiest way to transfer app-full-release.apk to your phone is via [USB cable or Google Drive](https://support.google.com/android/answer/9064445?hl=en). Please note that transfer by mail might cause difficulties and is not the preferred way. - -On your phone you have to allow installation from unknown sources. Manuals how to do this can be found on the internet (i.e. [here](https://www.expressvpn.com/de/support/vpn-setup/enable-apk-installs-android/) or [here](https://www.androidcentral.com/unknown-sources)). - -## Trikčių šalinimas - -See separate page [troubleshooting Android Studio](../Installing-AndroidAPS/troubleshooting_androidstudio). \ No newline at end of file diff --git a/docs/CROWDIN/lt/Resources/index.md b/docs/CROWDIN/lt/Resources/index.md deleted file mode 100644 index fea155af76bc..000000000000 --- a/docs/CROWDIN/lt/Resources/index.md +++ /dev/null @@ -1,8 +0,0 @@ -# Resursai - -```{toctree} -:glob: true -:maxdepth: 4 - -clinician-guide-to-AndroidAPS -``` diff --git a/docs/CROWDIN/lt/Sandbox/sandbox2.md b/docs/CROWDIN/lt/Sandbox/sandbox2.md deleted file mode 100644 index 33c547956c89..000000000000 --- a/docs/CROWDIN/lt/Sandbox/sandbox2.md +++ /dev/null @@ -1,43 +0,0 @@ -# internal sandbox file 2 for testing - -```{admonition} no need to translate this -:class: note - -No need to translate this. -``` - -This is an internal sandbox file for the documentation team to test - -1. markdown syntax and - -1. background process for - 1. CROWDIN translation and - 2. Read The Docs deployment. - -You can dirctly jump from here to the first label in the sandbox1.md file - ["Jump"](sandbox1-this-is-a-test). - -You can dirctly jump from here to the second label in this file - ["Jump"](sandbox1-this-is-another-test). - -Here you can jump to the first sandbox file - ["Jump"](./sandbox1.md). - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -(sandbox2-this-is-a-test)= -## This is a test - -This is a test if labels must be unique. - -### This is spare information from the docs - -cut from index: - -There are "limits" set in place when you are first beginning your AAPS journey. These safety limits have been developed over many years by observations of the inadvertent mistakes that new users are most likely to make when first learning to set up, build, and then successfully loop with AAPS - as most often those mistakes occur simply because the user was so excited to get started using the system that they may have forgotten to sit down and dedicate the time needed to understand the information within this documentation thoroughly. - - -### spare info from the overview to put into "preparing" - -Since the requirements are very different from anything you might have set up in the past, we recommend that you really follow the instructions, step-by-step the first few times you build the app, so that you have a stronger sense of how the app building process is supposed to behave when all directions are followed exactly. Please remember to take your time. Later this will go very quickly when you build the app again for a new version. That way you will have a greater chance of noticing when something doesn't going as planned before too many steps are out of line. It is important to save the your keystore file (.jks file used to sign your app) in a safe place, so that you can always use that exact same keystore file and password each and every time you are asked to create a new updated version of AAPS, as this file is what makes sure that each new version of the app "remembers" all the information that you have provided to it in previous versions of the app and thus ensure that the updates will go as smoothly as possible. On average, you can assume that there will be one new version and 2-3 required updates per year. This number is based on experience and may change in the future. But we do want to at least give you a general guideline on what to expect. When you are more experienced at building updated AAPS app versions all the steps that are required in building an updated app will only take 15-30 minutes, on average. However, in the beginning there can be a rather steep learning curve as these steps are not always considered intuitive by new users! So do not get frustrated if you find that it takes half a day or a whole day with some help from the community before you are finally finished with the update process. If you find that you are getting very frustrated just take a short break, and oftentimes; after a stroll around the block or two...you'll find that you are better able to approach the problem again. diff --git a/docs/CROWDIN/lt/Usage/Objectives.md b/docs/CROWDIN/lt/Usage/Objectives.md deleted file mode 100644 index a4b3f337eb03..000000000000 --- a/docs/CROWDIN/lt/Usage/Objectives.md +++ /dev/null @@ -1,184 +0,0 @@ -# Tikslai - -AAPS has a series of Objectives that need to be completed to walk you through the features and settings of safe looping. Jie užtikrina, kad aukščiau aprašytus parametrus sukonfigūravote teisingai, ir kad suprantate, ką Jūsų sistema daro ir kodėl galite ja pasitikėti. - -If you are **upgrading phones** then you can [export your settings](../Usage/ExportImportSettings.md) to keep your progress through the objectives. Not only will your progress through the objectives be saved, but also your safety settings such as max bolus etc. If you do not export and import your settings then you will need to start the objectives from the beginning again. It is a good idea to [backup your settings](../Usage/ExportImportSettings.html) frequently just in case. - -If you want to go back in objectives see [explanation below](Objectives-go-back-in-objectives). - -## Tikslas 1: vizualizacijos ir monitoringo nustatymai, bazės ir koeficientų analizė - -- Select the right blood glucose source for your setup. See [BG Source](../Configuration/BG-Source.md) for more information. -- Select the right Pump in ConfigBuilder (select Virtual Pump if you are using a pump model with no AAPS driver for looping) to ensure your pump status can communicate with AAPS. -- If using DanaR pump then ensure you have followed [DanaR Insulin Pump](../Configuration/DanaR-Insulin-Pump.md) instructions to ensure the link between pump and AAPS. -- You need to establish a data repository/reporting platform to complete this objective. That can be accomplished with either Nightscout or Tidepool (or both). Follow instructions at the [Nightscout](../Installing-AndroidAPS/Nightscout.md) or [Tidepool](../Installing-AndroidAPS/Tidepool.md) page for instructions. -- Note that URL in NSClient must be **WITHOUT /api/v1/** at the end - see [NSClient settings in Preferences](Preferences-nsclient). - -*You may need to wait for the next blood glucose reading to arrive before AAPS will recognise it.* - -## Objective 2: Learn how to control AAPS - -- Perform several actions in AAPS as described in this objective. - -- Click on the orange text "Not completed yet" to access the to-dos. - -- Links will be provided to guide you in case you are not familiar with a specific action yet. - - ```{image} ../images/Objective2_V2_5.png - :alt: 2 tikslo ekrano vaizdas - ``` - -(Objectives-objective-3-prove-your-knowledge)= - -## Objective 3: Prove your knowledge - -Objective 3 is a multiple choice test based on questions designed to test your theoretical knowledge of **AAPS**. - -Some users find Objective 3 to be the most difficult objective to complete. Please do read the AAPS documents in conjunction with the questions. If you are genuinely stuck after researching the **AAPS** documents, please search or ask for help on the Facebook or Discord group. These groups can provide friendly hints or redirect you to the relevant part of the **AAPS** documents. - -To proceed with Objective 3, click on the orange text “Not completed yet” to access the relevant question. Please read each question and select your answer(s). - - - -Within each question, a hyperlink to the **AAPS** documents will guide you to the relevant section of the document which you should read in order to locate the correct answer. - - -[Obj3_Screenshot 2023-12-05 223422](https://github.com/openaps/AndroidAPSdocs/assets/137224335/77347516-e24e-459d-98ab-acbb49a3d4e8)![image](https://github.com/openaps/AndroidAPSdocs/assets/137224335/ca756b8e-efbc-4427-b281-ac953ce16718) - - - -For each question, there may be more than one answer that is correct! If an incorrect answer is selected, the question will be time locked for a certain amount of time (60 minutes) before you can go back and answer the question. - - -After updating to a new version of **AAPS**, new questions may be added to cover a prevalent issue picked up by **AAPS** or alternatively to test your knowledge of a new feature of **AAPS** as released. - - -When **AAPS** is installed for the first time, you will have to complete Objective 3 entirely in order to move onto Objective 4. Each objective is required to be completed in sequential order. New features will gradually be unlocked as progress is made through the objectives. - -__What happens if new questions are added later to Objective 3?__ From time to time, new features are added to **AAPS** which may require a new question to be added to Objective 3. As a result, any new question added to Objective 3 will be marked as “incomplete” because **AAPS** will require you to action this. As each Objective is independent, you will not lose the existing functionality of **AAPS** providing the other objectives remain completed. - - -## Tikslas 4: pradėkite naudoti Atvirą ciklą - -- Select Open Loop either from Preferences, or by pressing and holding the Loop button in top left of the home screen. -- Work through the [Preferences](../Configuration/Preferences.md) to set up for you. -- Manually enact at least 20 of the temporary basal rate suggestions over a period of 7 days; input them to your pump and confirm in AAPS that you have accepted them. Ensure this data shows in AAPS and Nightscout. -- Enable [temp targets](../Usage/temptarget.md) if necessary. Naudokite Hipo laikiną tikslą apsisaugoti, kad sistema pernelyg aktyviai nekoreguotų kylančios glikemijos po buvusios hipoglikemijos. - -### Sumažinti pranešimų skaičių - -- To reduce the Number of decisions to be made while in Open Loop set wide target range like 90 - 150 mg/dl or 5,0 - 8,5 mmol/l. - -- You might even want to wider upper limit (or disable Open Loop) at night. - -- In Preferences you can set a minimum percentage for suggestion of basal rate change. - - ```{image} ../images/OpenLoop_MinimalRequestChange2.png - :alt: Atvirojo ciklo minimalaus pokyčio užklausa - ``` - -- Also, you do not need to act every 5 minutes on all suggestions... - -## Tikslas 5: perpraskite atvirojo ciklo veikimą bei laikinos bazės rekomendacijas - -- Start to understand the thinking behind the temp basal recommendations by looking at the [determine basal logic](https://openaps.readthedocs.io/en/latest/docs/While%20You%20Wait%20For%20Gear/Understand-determine-basal.html) and both the [forecast line in AAPS homescreen](Screenshots-prediction-lines)/Nightscout and the summary of outputs from the calculations in your OpenAPS tab. - -Tikslinę glikemiją greičiausiai norėsite nustatyti aukštesnę nei įprastai, kol įsitikinsite skaičiavimais ir nustatymais. Sistema leidžia - -- a low target to be a minimum of 4 mmol (72 mg/dl) or maximum of 10 mmol (180 mg/dl) -- a high target to be a minimum of 5 mmol (90 mg/dl) and maximum of 15 mmol (225 mg/dl) -- a temporary target as a single value can be anywhere in the range of 4 mmol to 15 mmol (72 mg/dl to 225 mg/dl) - -Tikslas yra reikšmė, kuria grindžiami skaičiavimai, o ne reikšmė, kuria norite išlaikyti gliukozės kiekį kraujyje. If your target is very wide (say, 3 or more mmol \[50 mg/dl or more\] wide), you will often find little AAPS action. Numatomas gliukozės lygis greičiausiai bus jūsų tiksliniame diapazone, todėl nebus siūloma daug laikinų bazinio greičio pokyčių. - -You may want to experiment with adjusting your targets to be a closer together range (say, 1 or less mmol \[20 mg/dl or less\] wide) and observe how the behavior of your system changes as a result. - -You can view a wider range (green lines) on the graph for the values you aim to keep your blood glucose within by entering different values in [Preferences](../Configuration/Preferences.md) > Range for Visualisation. - -```{image} ../images/sign_stop.png -:alt: Stop ženklas -``` - -### Jei naudojate virtualią pomp ir atvirą ciklą - nespauskite Patvirtinti šio tikslo pabaigoje. - -```{image} ../images/blank.png -:alt: tuščias -``` - -(Objectives-objective-6-starting-to-close-the-loop-with-low-glucose-suspend)= -## Tikslas 6: pradėkite Uždaro ciklo (Closed Loop) režimą su pompos stabdymu esant žemai gliukozei - -```{image} ../images/sign_warning.png -:alt: Įspėjamasis ženklas -``` - -### Closed loop will not correct high BG values in objective 6 as it is limited to low glucose suspend. High BG values have to be corrected manually by you! - -- Prerequisite: You need a good profile (basal, ISF, IC) already working in AAPS to start with Loop in Low Glucose Suspend mode. Otherwise you can run in a hypo which you have to manually correct. This will help you a lot to avoid having to treat a low glucose over a period of 5 days. **If you are still having frequent or severe low glucose episodes then consider refining your DIA, basal, ISF and carb ratios and do NOT start objective 6 at this time.** -- You don't have to change your settings now. During objective 6, the maxIOB setting is internally set to zero automatically. **This override will be reversed when moving to objective 7.** -- The system will override your maxIOB settings to zero, which means if blood glucose is dropping it can reduce basal for you. If blood glucose is rising then it will only increase basal if the basal IOB is negative from a previous Low Glucose Suspend. Otherwise basal rates will remain the same as your selected profile. **That means that you have to manually handle high values with insulin corrections.** -- If your basal IOB is negative (see screenshot below) a TBR > 100% can be issued also in objective 6. - -```{image} ../images/Objective6_negIOB.png -:alt: Neigiamo AIO pavyzdys -``` - -- Set your target range slightly higher than you usually aim for, just to be safe and have a bit more scurity buffer. -- Enable 'Low Glucose Suspend' mode either by by pressing and holding the Loop icon at the top right corner of the home screen and selecting the Loop - LGS mode icon. -- Watch how temporary basals are active by viewing the blue basal text on the homescreen or the blue basal render on the homescreen graph. -- You may temporarily experience spikes following treated hypos without the ability to increase basal on the rebound. - -(Objectives-objective-7-tuning-the-closed-loop-raising-max-iob-above-0-and-gradually-lowering-bg-targets)= -## Objective 7: Tuning the closed loop, raising maxIOB above 0 and gradually lowering BG targets - -- Select 'Closed Loop' either from [Preferences](../Configuration/Preferences.md) or by pressing and holding the Loop icon at the top right corner of the home screen, over a period of 1 day. - -- Raise your 'Maximum total IOB OpenAPS can’t go over' (in OpenAPS called 'max-iob') above 0. The default recommendation is "average mealbolus + 3x max daily basal" (for the SMB algorithm) or "3x max daily basal" (for the older AMA algorithm) but you should slowly work up to this until you know your settings work for you (max daily basal = the maximum hourly value in any time segment of the day). - - Ši rekomendacija turėtų būti laikoma atskaitos tašku. If you set to the 3x and you are seeing moves that push you too hard and fast then lower that number. If you are very resistant, raise it very little at a time. - - ```{image} ../images/MaxDailyBasal2.png - :alt: max daily basal - ``` - -- Once confident on how much IOB suits your looping patterns, then reduce your targets to your desired level. - -(Objectives-objective-8-adjust-basals-and-ratios-if-needed-and-then-enable-autosens)= -## Tikslas 8: jei reikia, koreguokite valandinės bazės reikšmes bei pagrindinius parametrus ir įgalinkite Autosens funkciją - -- You can use [autotune](https://openaps.readthedocs.io/en/latest/docs/Customize-Iterate/autotune.html) as a one off to check your basals remain accurate or do a traditional basal test. -- Enable [autosens](../Usage/Open-APS-features.md) over a period of 7 days and watch the white line on the homescreen graph show how your sensitivity to insulin may be rising or falling as a result of exercise or hormones etc. and keep an eye in the OpenAPS report tab how AAPS is adjusting the basals and/or targets accordingly. - -*Don’t forget to record your looping in* [this form](https://bit.ly/nowlooping) *logging AAPS as your type of DIY loop software, if you have not already done so.* - -(Objectives-objective-9-enabling-additional-oref1-features-for-daytime-use-such-as-super-micro-bolus-smb)= -## Objective 9: Enabling additional oref1 features for daytime use, such as super micro bolus (SMB) - -- You must read the [SMB chapter in this wiki](Open-APS-features-super-micro-bolus-smb) and [chapter oref1 in openAPSdocs](https://openaps.readthedocs.io/en/latest/docs/Customize-Iterate/oref1.html) to understand how SMB works, especially what's the idea behind zero-temping. -- Then you ought to [rise maxIOB](Open-APS-features-maximum-total-iob-openaps-cant-go-over-openaps-max-iob) to get SMBs working fine. max AIO dabar apima visą AIO, ne tik pridėtą (pakeltą) valandinę bazę. That is, if given a bolus of 8 U for a meal and maxIOB is 7 U, no SMBs will be delivered until IOB drops below 7 U. A good start is maxIOB = average mealbolus + 3x max daily basal (max daily basal = the maximum hourly value in any time segment of the day - see [objective 7](Objectives-objective-7-tuning-the-closed-loop-raising-max-iob-above-0-and-gradually-lowering-bg-targets) for an illustration) -- min_5m_carbimpact default in absorption settings has changed from 3 to 8 going from AMA to SMB. Jeigu Jūs pereinate nuo AMA į SMB, turite jį parametrą pakeisti rankiniu būdu. - -(Objectives-objective-10-automation)= -## Objective 10: Automation - -- You have to start objective 10 to be able to use [Automation](../Usage/Automation.md). -- Make sure you have completed all objectives including exam [Objectives-objective-3-prove-your-knowledge](Objectives#objective-3-prove-your-knowledge). -- Completing previous objectives will not effect other objectives you have already finished. Visi užbaigti tikslai bus išsaugoti! - -(Objectives-objective-11-DynamicISF)= -## Objective 11: Additional Features such as DynamicISF - -- You have to start objective 11 to be able to use [DynamicISF](../Usage/Open-APS-features.md) - -(Objectives-go-back-in-objectives)= -## Grįžti į tikslus - -Jei dėl bet kokios priežasties norite grįžti į tikslų pradžią, galite tai padaryti paspaudę "išvalyti užbaigtus". - -```{image} ../images/Objective_ClearFinished.png -:alt: Grįžti į tikslus -``` - -## Objectives in Android APS before version 3.0 - -One objective was removed when Android APS 3.0 was released. Users of Android APS version 2.8.2.1 who are on older Android software (i.e. earlier than version 9) will be using an older set of objectives which can be found [here](../Usage/Objectives_old.md). diff --git a/docs/CROWDIN/lt/Usage/Objectives_old.md b/docs/CROWDIN/lt/Usage/Objectives_old.md deleted file mode 100644 index e3e9645210c9..000000000000 --- a/docs/CROWDIN/lt/Usage/Objectives_old.md +++ /dev/null @@ -1,152 +0,0 @@ -# Objectives as of Android APS 2.8.2.1 - -This is not the latest version of the Android APS Objectives. This page details the Objectives that were in place prior to version 3.0. Anyone using an older version of Android (i.e. prior to Android 9) and Android APS version 2.8.2.1 should refer to this page. - -Please see [this page](../Usage/Objectives.md) for the current set of Objectives. - -AndroidAPS turi keletą mokymo programos tikslų, kuriuos įvykdę įvaldysite saugaus ciklo naudojimo funkcijas bei nustatymus. Jie užtikrina, kad aukščiau aprašytus parametrus sukonfigūravote teisingai, ir kad suprantate, ką Jūsų sistema daro ir kodėl galite ja pasitikėti. - -If you are **upgrading phones** then you can [export your settings](../Usage/ExportImportSettings.md) to keep your progress through the objectives. Not only will your progress through the objectives be saved, but also your safety settings such as max bolus etc. If you do not export and import your settings then you will need to start the objectives from the beginning again. It is a good idea to [backup your settings](../Usage/ExportImportSettings.html) frequently just in case. - -If you want to go back in objectives see [explanation below](../Usage/Objectives.md#go-back-in-objectives). - -## Tikslas 1: vizualizacijos ir monitoringo nustatymai, bazės ir koeficientų analizė - -- Select the right blood glucose source for your setup. See [BG Source](../Configuration/BG-Source.md) for more information. -- Select the right Pump in ConfigBuilder (select Virtual Pump if you are using a pump model with no AndroidAPS driver for looping) to ensure your pump status can communicate with AndroidAPS. -- If using DanaR pump then ensure you have followed [DanaR Insulin Pump](../Configuration/DanaR-Insulin-Pump.md) instructions to ensure the link between pump and AndroidAPS. -- Follow instructions in [Nightscout](../Installing-AndroidAPS/Nightscout.md) page to ensure Nightscout can receive and display this data. -- Note that URL in NSClient must be **WITHOUT /api/v1/** at the end - see [NSClient settings in Preferences](../Configuration/Preferences.md#nsclient). - -*You may need to wait for the next blood glucose reading to arrive before AndroidAPS will recognise it.* - -## Tikslas 2: išmokite valdyti AndroidAPS - -- Perform several actions in AndroidAPS as described in this objective. - -- Click on the orange text "Not completed yet" to access the to-dos. - -- Links will be provided to guide you in case you are not familiar with a specific action yet. - - ![2 tikslo ekrano vaizdas](../images/Objective2_V2_5.png) - -## Objective 3: Prove your knowledge - -- Pass a multiple-choice exam testing your AndroidAPS knowledge. - -- Click on the orange text "Not completed yet" to access the page with the question and answering options. - - ![3 tikslo ekrano vaizdas](../images/Objective3_V2_5.png) - -- Links will be provided to guide you in case you are unsure about the correct answers yet. - -- The questions for objective 3 have been completely rewritten by native speakers as of AAPS 2.8. The new ones cover the same basic topics plus a few new ones. - -- These new questions will lead to some not answered questions even though you have successfully completed objective 3 in previous versions. - -- Unanswered questions will affect you only if you start a new objective. In other words: If you have already completed all objectives you can wait and answer the new questions later without loosing AAPS functions. - -## Tikslas 4: pradėkite naudoti Atvirą ciklą - -- Select Open Loop either from Preferences, or by pressing and holding the Loop button in top left of the home screen. -- Work through the [Preferences](../Configuration/Preferences.md) to set up for you. -- Manually enact at least 20 of the temporary basal rate suggestions over a period of 7 days; input them to your pump and confirm in AndroidAPS that you have accepted them. Patikrinkite, ar šie duomenys rodomi AndroidAPS ir Nightscout. -- Enable [temp targets](../Usage/temptarget.md) if necessary. Naudokite Hipo laikiną tikslą apsisaugoti, kad sistema pernelyg aktyviai nekoreguotų kylančios glikemijos po buvusios hipoglikemijos. - -### Sumažinti pranešimų skaičių - -- To reduce the Number of decisions to be made while in Open Loop set wide target range like 90 - 150 mg/dl or 5,0 - 8,5 mmol/l. - -- You might even want to wider upper limit (or disable Open Loop) at night. - -- In Preferences you can set a minimum percentage for suggestion of basal rate change. - - ![Atvirojo ciklo minimalaus pokyčio užklausa](../images/OpenLoop_MinimalRequestChange2.png) - -- Also, you do not need to act every 5 minutes on all suggestions... - -## Tikslas 5: perpraskite atvirojo ciklo veikimą bei laikinos bazės rekomendacijas - -- Start to understand the thinking behind the temp basal recommendations by looking at the [determine basal logic](https://openaps.readthedocs.io/en/latest/docs/While%20You%20Wait%20For%20Gear/Understand-determine-basal.html) and both the [forecast line in AndroidAPS homescreen](../Getting-Started/Screenshots.md#prediction-lines)/Nightscout and the summary of outputs from the calculations in your OpenAPS tab. - -Tikslinę glikemiją greičiausiai norėsite nustatyti aukštesnę nei įprastai, kol įsitikinsite skaičiavimais ir nustatymais. Sistema leidžia - -- a low target to be a minimum of 4 mmol (72 mg/dl) or maximum of 10 mmol (180 mg/dl) -- a high target to be a minimum of 5 mmol (90 mg/dl) and maximum of 15 mmol (225 mg/dl) -- a temporary target as a single value can be anywhere in the range of 4 mmol to 15 mmol (72 mg/dl to 225 mg/dl) - -Tikslas yra reikšmė, kuria grindžiami skaičiavimai, o ne reikšmė, kuria norite išlaikyti gliukozės kiekį kraujyje. If your target is very wide (say, 3 or more mmol \[50 mg/dl or more\] wide), you will often find little AAPS action. Numatomas gliukozės lygis greičiausiai bus jūsų tiksliniame diapazone, todėl nebus siūloma daug laikinų bazinio greičio pokyčių. - -You may want to experiment with adjusting your targets to be a closer together range (say, 1 or less mmol \[20 mg/dl or less\] wide) and observe how the behavior of your system changes as a result. - -You can view a wider range (green lines) on the graph for the values you aim to keep your blood glucose within by entering different values in [Preferences](../Configuration/Preferences.md) > Range for Visualisation. - -![Stop ženklas](../images/sign_stop.png) - -### Jei naudojate virtualią pomp ir atvirą ciklą - nespauskite Patvirtinti šio tikslo pabaigoje. - -![tuščias](../images/blank.png) - -## Tikslas 6: pradėkite Uždaro ciklo (Closed Loop) režimą su pompos stabdymu esant žemai gliukozei - -![Įspėjamasis ženklas](../images/sign_warning.png) - -### Uždaras ciklas nekoreguos aukštos glikemijos 6 tiksle, nes jį apriboja sustabdymas dėl žemos gliukozės. Todėl jūs turite patys koreguoti aukštą glikemiją! - -- Select Closed Loop either from [Preferences](../Configuration/Preferences.md) or by pressing and holding the Open Loop button in the top left of the home screen. - -- Set your target range slightly higher than you usually aim for, just to be safe. - -- Watch how temporary basals are active by viewing the blue basal text on the homescreen or the blue basal render on the homescreen graph. - -- Ensure your settings have supported AndroidAPS to avoid having to treat a low glucose over a period of 5 days. Jei vis tiek pasikartoja dažna ar sunki hipoglikemija, turėtumėte koreguoti IVT, valandinę bazę, JIF ar insulino ir angliavandenių santykio rodiklius. - -- You don't have to change your settings. Kol esate 6 tiksle, maksimalus aktyvaus insulino kiekis organizame automatiškai nustatomas ties nuliu. Šio parametro pakeitimas nuliu bus atšauktas, kai pasieksite 7 tikslą. - -- The system will override your maxIOB settings to zero, which means if blood glucose is dropping it can reduce basal for you, but if blood glucose is rising then it will only increase basal if the basal IOB is negative (from a previous Low Glucose Suspend), otherwise basal rates will remain the same as your selected profile. - - ![Neigiamo AIO pavyzdys](../images/Objective6_negIOB.png) - -- If your basal IOB is negative (see screenshot above) a TBR > 100% can be issued also in objective 6. - -- You may temporarily experience spikes following treated hypos without the ability to increase basal on the rebound. - -## Tikslas 7: koreguokite savo uždarąjį ciklą po truputį didindami maks AIO ir mažindami tikslinę glikemijos reikšmę - -- Raise your 'Maximum total IOB OpenAPS can’t go over' (in OpenAPS called 'max-iob') above 0 over a period of 1 day, the default recommendation is "average mealbolus + 3x max daily basal"(for SMB algorithm) or "3x max daily basal" (for older AMA algorithm) but you should slowly work up to this until you know your settings work for you (max daily basal = the maximum hourly value in any time segment of the day). - - Ši rekomendacija turėtų būti laikoma atskaitos tašku. Jei naudosite koeficientą 3x ir pastebėsite, kad AAPS veikia per daug agresyviai, sumažinkite šį koeficientą (pvz., 2x, ...). Jei esate rezistentiškas, galite po truputį jį pakelti. - - ![max daily basal](../images/MaxDailyBasal2.png) - -- Once confident on how much IOB suits your looping patterns then reduce your targets to your desired level. - -## Tikslas 8: jei reikia, koreguokite valandinės bazės reikšmes bei pagrindinius parametrus ir įgalinkite Autosens funkciją - -- You can use [autotune](https://openaps.readthedocs.io/en/latest/docs/Customize-Iterate/autotune.html) as a one off to check your basals remain accurate or do a traditional basal test. -- Enable [autosens](../Usage/Open-APS-features.md) over a period of 7 days and watch the white line on the homescreen graph show how your sensitivity to insulin may be rising or falling as a result of exercise or hormones etc. and keep an eye in the OpenAPS report tab how AndroidAPS is adjusting the basals and/or targets accordingly. - -*Don’t forget to record your looping in* [this form](https://bit.ly/nowlooping) *logging AndroidAPS as your type of DIY loop software, if you have not already done so.* - -## Objective 9: Try additional features for daytime use and gain confidence in your closed loop system - -- Before AAPS version 2.7 meal assist (MA) was the basic algorithm for AAPS and completing objective 8 was necessary to activate [advanced meal assist (AMA)](../Usage/Open-APS-features.md#advanced-meal-assist-ama). -- As [advanced meal assist (AMA)](../Usage/Open-APS-features.md#advanced-meal-assist-ama) is the standard algorithm from AAPS version 2.7 onwards use the following 28 days to try features you haven't used yet and get more confident with you closed loop system. - -## Objective 10: Enabling additional oref1 features for daytime use, such as super micro bolus (SMB) - -- You must read the [SMB chapter in this wiki](../Usage/Open-APS-features.md#super-micro-bolus-smb) and [chapter oref1 in openAPSdocs](https://openaps.readthedocs.io/en/latest/docs/Customize-Iterate/oref1.html) to understand how SMB works, especially what's the idea behind zero-temping. -- Then you ought to [rise maxIOB](../Usage/Open-APS-features.md#maximum-total-iob-openaps-cant-go-over-openaps-max-iob) to get SMBs working fine. max AIO dabar apima visą AIO, ne tik pridėtą (pakeltą) valandinę bazę. That is, if given a bolus of 8 U for a meal and maxIOB is 7 U, no SMBs will be delivered until IOB drops below 7 U. A good start is maxIOB = average mealbolus + 3x max daily basal (max daily basal = the maximum hourly value in any time segment of the day - see [objective 7](../Usage/Objectives#objective-7-tuning-the-closed-loop-raising-max-iob-above-0-and-gradually-lowering-bg-targets) for an illustration) -- min_5m_carbimpact default in absorption settings has changed from 3 to 8 going from AMA to SMB. Jeigu Jūs pereinate nuo AMA į SMB, turite jį parametrą pakeisti rankiniu būdu. - -## Objective 11: Automation - -- You have to start objective 11 to be able to use [Automation](../Usage/Automation.md). -- Make sure you have completed all objectives including exam [../Usage/Objectives.md#objective-3-prove-your-knowledge](../Usage/Objectives#objective-3-prove-your-knowledge). -- Completing previous objectives will not effect other objectives you have already finished. Visi užbaigti tikslai bus išsaugoti! - -## Grįžti į tikslus - -Jei dėl bet kokios priežasties norite grįžti į tikslų pradžią, galite tai padaryti paspaudę "išvalyti užbaigtus". - -![Grįžti į tikslus](../images/Objective_ClearFinished.png) diff --git a/docs/CROWDIN/lt/Usage/Smoothing-Blood-Glucose-Data-in-xDrip.md b/docs/CROWDIN/lt/Usage/Smoothing-Blood-Glucose-Data-in-xDrip.md deleted file mode 100644 index 11026a0db43a..000000000000 --- a/docs/CROWDIN/lt/Usage/Smoothing-Blood-Glucose-Data-in-xDrip.md +++ /dev/null @@ -1,33 +0,0 @@ -(Smoothing-Blood-Glucose-Data-in-xDrip-smoothing-blood-glucose-data)= - -# Gliukozės kraujyje duomenų išlyginimas - -If BG data is jumpy/noisy, AAPS may dose insulin incorrectly resulting in high or low BG. For this reason it’s important to disable the loop until the problem is resolved. Depending on your CGM such issues may be due to the CGM’s configuration or sensor problems/site issues. You may need to replace your CGM sensor to resolve this. - -Some CGM systems have internal algorithms to detect the noise level in the readings and AAPS can use this information to avoid giving SMBs if the BG data is too unreliable. However, some CGMs do not transmit this data and for these BG sources 'Enable SMB always' and 'Enable SMB after carbs' are disabled for safety reasons. - -## Dexcom sensors - -### Build Your Own Dexcom App - -When using [BYODA](DexcomG6-if-using-g6-with-build-your-own-dexcom-app) your BG data is smooth and consistent. Furthermore you can take advantage of Dexcom back-smoothing. There are no restrictions in using SMBs, because the noise-level data is shared with AAPS. - -### xDrip+ with Dexcom G6 or Dexcom ONE - -Noise-level data and smooth BG readings are only shared with AAPS if you use xDrip+ [native mode](https://navid200.github.io/xDrip/docs/Native-Algorithm). Using native mode, there are no restrictions in using SMBs. - -### Dexcom G6 or Dexcom ONE with xDrip+ Companion Mode - -The noise-level data is not shared with AAPS using this method. Therefore 'Enable SMB always' and 'Enable SMB after carbs' are disabled. - -## Freestyle Libre sensors - -### xDrip+ with FreeStyle Libre - -None of the FreeStyle Libre systems (FSL1, FSL2, or FSL3) broadcast any information about the level of noise detected in the readings, and therefore 'Enable SMB always' and 'Enable SMB after carbs' are disabled for all setups using the FreeStyle Libre. - -In addition, many people have reported the FreeStyle Libre often produces noisy data. In xDrip+ there are a few options to help with this: - -**Smooth Sensor Noise.** In xDrip+ Settings > xDrip+ Display Settings ensure that Smooth Sensor Noise is turned on. This attempts to apply smoothing to noisy data. - -**Smooth Sensor Noise (Ultrasensitive).** If you are still seeing noisy data in xDrip+ you can apply more aggressive smoothing using the Smooth Sensor Noise (Ultrasensitive) setting. This will attempt to apply smoothing even on very low levels of detected noise. To do this, first enable [engineering mode](Enabling-Engineering-Mode-in-xDrip.md) in xDrip+. Then navigate to Settings > xDrip+ Display Settings and turn on Smooth Sensor Noise (Ultrasensitive). \ No newline at end of file diff --git a/docs/CROWDIN/lt/Usage/autotune_b.md b/docs/CROWDIN/lt/Usage/autotune_b.md deleted file mode 100644 index 3ece545614f5..000000000000 --- a/docs/CROWDIN/lt/Usage/autotune_b.md +++ /dev/null @@ -1,186 +0,0 @@ -# How to use Autotune plugin - -Documentation about Autotune algorythm can be found in [OpenAPS documentation](https://openaps.readthedocs.io/en/latest/docs/Customize-Iterate/autotune.html). - -Autotune plugin is an implementation of OpenAPS autotune algorythm within AAPS. - -**Currently Autotune Plugin is only available in dev branch with Engineering mode.** - -## Autotune user interface - -![Autotune default screen](../images/Autotune/Autotune_1b.png) - -- You can select in the Profile dropdown menu the input profile you want to tune (by default your current active profile is selected) - - Note: each time you select a new profile, previous results will be removed and Tune days parameter will be set to default value -- Then Tune days is to select the number of days used in calculation to tune your profile. The minimum value is 1 day and the maximum value 30 days. This number should not be too small to get correct iterative and smooth results (above 7 days for each calculation) - - Note: each time you change Tune days parameter, previous results will be removed -- Last Run il a link that recover your latest valid calculation. If you didn't launch Autotune on current day, or if previous results was removed with a modification of calculation parameter above, then you can recover parameters and results of the latest successfull run. -- Warning show you for example some information about selected profile (if you have several IC values or several ISF values) - - Note: Autotune calculation works with only a single IC and a single ISF value. There is currently no existing Autotune algorythm to tune a circadian IC or circadian ISF. If your input profile has several values, you can see in warning section the average value taken into account to tune your profile. -- Check Input Profile button open the Profile Viewer to allow you a quick verification of your profile (Units, DAI, IC, ISF, basal and target) - - Note: Autotune will only tune your IC (single value), ISF (single value) and basal (with circadian variation). Units, DAI and target will remain unchanged in output profile. - -- "Run Autotune" will launch Autotune calculation with selected profile and the number of Tune days - - Note: Autotune calculation can take a long time. Once launched, you can switch to another view (home, ...) and come back later in Autotune plugin to see results - -![Autotune Run start](../images/Autotune/Autotune_2b.png) - -- Then during the run you will see intermediate results below - - - Note: During run, settings are locked, so you cannot change anymore selected input profile or the number of day. You will have to wait the end of current calculation if you want to launch another run with other parameters. - - ![Autotune during run](../images/Autotune/Autotune_3b.png) - -- When Autotune calculation is finished, you will see the result (Tuned profile) and four buttons below. - -![Autotune Result](../images/Autotune/Autotune_4b.png) - -- It's important to always compare input profile (column "Profile"), output profile (column "Tuned") and the percentage of variation for each value (Column "%"). - -- For basal rates, you also have the number of "missing days". You have missing days when Autotune don't have enough data categorized as "Basal" to tune basal rate for this period (for example after each meal when you have carbs absorption). This number should be as low as possible especially when basal is important (for example during the night or at the end of the afternoon) - -- The "Compare profiles" button open the profile comparator view. Input profile is in blue, and output profile (named "Tuned") is in red. - - - Note: in the example below input profile has circadian variation for IC and ISF, but output calculated profile has a single value. If it's important for you to get a circadian output profile see [Circadian IC or ISF profile](#circadian-ic-or-isf-profile) below. - - ![Autotune Compare profiles](../images/Autotune/Autotune_5.png) - -- If you trust results (low percentage of variation between input profile and output profile), you can click on "Activate profile" button and then click on OK to validated. - - - Activate Tuned profile will automatically create a new profile "Tuned" in your Local profile plugin. - - If you already have a profile named "Tuned" in your local profile plugin, then this profile will be updated with calculated Autotune profile before the activation - - ![Autotune Activate profile](../images/Autotune/Autotune_6.png) - -- If you think Tuned profile must be adjusted (for example if you think some variation are too important), then you can click on "Copy to local profile" button - - - A new profile with the prefix "Tuned" and the date and time of the run will be created in local profile plugin - -![Autotune Copy to local profile](../images/Autotune/Autotune_7.png) - -- You can then select local profile to edit the Tuned profile (it will be selected by default when you open Local profile plugin) - - - the values in local profile will but rounded in the user interface to your pump capabilities - - ![Autotune local profile update](../images/Autotune/Autotune_8.png) - -- If you want to replace your input profile with Autotune result, click on "Update input profile" button and validate the Popup with OK - - - Note: if you click on "Activate profile" after "Update input profile", then you will activate your updated profile and not the default "Tuned" profile? - - ![Autotune Update input profile](../images/Autotune/Autotune_9.png) - -- If you have updated your input profile, then the "Update input profile" button is replaced by "Revert input profile" button (see screenshot below). You can that way immediatly see if your current input profile in Local profile plugin already include the result of last run or not. You also have the possibility to recover you input profile without autotune result with this button - - ![Autotune Update input profile](../images/Autotune/Autotune_10.png) - - - -## Autotune settings - -### Autotune plugin settings - -![Autotune default screen](../images/Autotune/Autotune_11.png) - -- Automation Switch Profile (default Off): see [Run Autotune with an automation rule](#run-autotune-with-an-automation-rule) below. If you change this setting to On, the input profile will automatically be updated by the Tuned profile, and it will be activated. - - **Be Carefull, you must trust and verified during several following days that after an update and activation of Tuned profile without modification, it improves your loop** - -- Categorize UAM as basal (default On): This setting is for the users using AndroidAPS without any carbs entered (Full UAM). It will prevent (when Off) to categorize UAM as basal. - - Note: if you have at least one hour of Carbs absorption detected during one day, then all data categorized as "UAM" will be categorized as basal, whatever this setting (On or Off) -- Number of days of data (default 5): You can define default value with this setting. Each time your select a new profile in Autotune plugin, Tune days parameter will be replaced by this default value -- Apply average result in circadian IC/ISF (default Off): see [Circadian IC or ISF profile](#circadian-ic-or-isf-profile) below. - -### Kiti nustatymai - -- Autotune also uses Max autosens ratio and Min autotsens ratio to limit variation. You can see and adjust these values in Config Builder > Sensitivity detection plugin > Settings > Advanced Settings - - ![Autotune default screen](../images/Autotune/Autotune_12.png) - - - -## Advanced feature - -### Circadian IC or ISF profile - -- If you have important variation of IC and/or you ISF in your profile, and you fully trust in your circadian time and variation, then you can set "Apply average result in circadiant IC/ISF" - - - Note that Autotune calculation will always be done with a single value, and circadian variation will not be tuned by Autotune. This setting only apply average variation calculated for IC and/or ISF on your circadian values - -- See on screenshot below Tuned profile with Apply average variation Off (on the left) and On (on the right) - - ![Autotune default screen](../images/Autotune/Autotune_13.png) - - - -### Tune specific days of the week - -- If you click on the checkbox with the eye on the right of "Rune days" parameter, you will see the day selection. You can specify which day of the week should be included in Autotune calculation (in screenshot below you can see an example for "working days" with Saturday and Sunday removed from autotune calculation) - - If the number of day included in Autotune calculation is lower than the number of Tune days, then you will see how many days will be included on the right of Tune days selector (10 days in the example below) - - This setting gives good results only if the number of remaining days is not to small (for example if you Tune a specific profile for week end days with only Sunday and Saturday selected, you should select a minimum of 21 or 28 Tune days to have 6 or 8 days included in Autotune calculation) - -![Autotune default screen](../images/Autotune/Autotune_14b.png) - -- During Autotune calculation, you can see the progress of the calculations ("Partial result day 3 / 10 tuned" on example below) - - ![Autotune default screen](../images/Autotune/Autotune_15b.png) - -## Run Autotune with an automation rule - -First step is to define correct trigger for an automation rule with Autotune: - -Note: for more information on how to set an automation rule, see [here](./Automation.rst). - -- You should select Recurring time trigger: only run Autotune once per day, and autotune is designed to be runned daily (each new run you shift one day later and quickly profile modification should be tiny) - - ![Autotune default screen](../images/Autotune/Autotune_16.png) - -- It's better at the beginning to run Autotune during the day to be able to check results. If you want to run Autotune during the night, you have to select in the trigger 4AM or later to include current day in next Autotune Calculation. - - ![Autotune default screen](../images/Autotune/Autotune_17.png) - -- Then you can select "Run Autotune" Action in the list - - ![Autotune default screen](../images/Autotune/Autotune_18.png) - -- You can then select Autotune Action to adjust parameters for your run. Default parameters are "Active Profile", default Tune days value defined in Autotune Plugin preferences, and All days are selected. - - ![Autotune default screen](../images/Autotune/Autotune_19b.png) - -- After a few days, if you fully trust Autotune results and percentage of modification is low, you can modify [Autotune settings](#autotune-plugin-settings) "Automation Switch Profile" to enabled to automatically update and activate profile tuned after calculation. - -Note: if you want to automatically tune profiles for specific days of the week (for example a profile for "Weekend days" and another one for "Working days"), then create one rule for each profile, select the same days in Trigger and in Autotune Action, Tune days must be high enough to be sure tuning will be done with at least 6 or 8 days, and don't forget to select time after 4AM in trigger... - -- See below an example of rule to tune "my profile" on all "Working days" with 14 Tune days selected (so only 10 days included in autotune calculation). - -![Autotune default screen](../images/Autotune/Autotune_20b.png) - - - -## Tips and trick's - -Autotune works with information existing in your database, so if you just installed AAPS on a new phone, you will have to wait several days before being able to launch Autotune with enough days to get relevant results; - -Autotune is just an help, it's important to regularly check if you agree with calculated profile. If you have any doubt, change Autotune settings (for example the number of days) or copy results in local profile and adjust profile before using it. - -Always use Autotune several days manually to check results before applyling them. And it's only when you fully trust Autotune results, and when variation becomes tiny between previous profile and calculated profile than you start to use Automation (Never before) - -- Autotune can work very well for some users and not for others, so **If you don't trust Autotune result, don't use it** - -It's also important to analyse Autotune results to understand (or try to understand) why Autotune propose these modifications - -- you can have a whole increase or decrease of the strength of your profile (for example increase of total basal associated to decrease of ISF and IC values). it could be associated to several following days with autosens correction above 100% (more agressivity required) or below 100% (you are more sensitive) -- Sometimes Autotune propose a different balance between basal rates and IC/ISF (for ex lower basal and more aggressive IC/ISF) - -We advise to not use Autotune in the following cases: - -- You don't enter all your carbs - - If you don't enter carbs correction for an hypoglycemia, Autotune will see an unexcepted increase of your BG value and will increase your basal rates the ' hours earlier, it could be the opposite of what you need to avoid hypo, especially if it's in the middle of the night. That's why it's important to enter all carabs especially correction for hypo. -- You have a lot of period with UAM detected during the day. - - Do you have entered all your carbs and correctly estimated your Carbs ? - - All UAM periods (except if you enter no carbs during a day and categorized UAM as basal is disabled), all your UAM periods will be categorized as basal, this can increase a lot your basal (much more than necessary) - -- Your carbs absorption is very slow: if most of your carbs absorption are calculated with min_5m_carbimpact parameter (you can see these periods with a little orange dot in the top of COB curve), the calculation of COB could be wrong and leads to wrong results. - - We you practice sport, you are generally more sensitive and your BG doesn't rise a lot, so during or after an exercice, it's usual to see some periods with slow carbs. But if you have too often unexpected slow carb absorption, then you may need a profile adjustment (higher value of IC) or a min_5m_carbimpact a bit to high. -- You have a "very bad days", for example stuck several hours in hyperglycemia with a huge amount of insulin to be able to go down within the range, or after a sensor change you got long periods of wrong BG values. -- If the percentage of modification is too important - - You can try to increase the number of days to get smoother results \ No newline at end of file diff --git a/docs/CROWDIN/lt/Usage/making-sport-with-AAPS.md b/docs/CROWDIN/lt/Usage/making-sport-with-AAPS.md deleted file mode 100644 index 79d2f1c38223..000000000000 --- a/docs/CROWDIN/lt/Usage/making-sport-with-AAPS.md +++ /dev/null @@ -1,185 +0,0 @@ -# making sport with AAPS - -In this section we want to address the topic of sport with AAPS. - -The aim is to show you how AAPS can help you to continue doing your favorite sport more easily or even to start doing it. It is relatively common for new type 1 diabetics to ask whether exercise is still possible for them, even if the answer in the training courses is actually a clear yes. Exercise is not only good for healthy people, but also for type 1 diabetics and even moderate exercise can even help to stabilize the blood sugar curve overall. - -:::{admonition} consult with your diabetes team after reading - -::: - -The difficulty here is that the prerequisites that someone brings with them and the expectations of what sport means to them are very different. - -Since we can assume that experienced top athletes with T1D who use AAPS are unlikely to look it up here, we deliberately set the bar low for ourselves when writing and for you when reading and using it, so that as many people as possible can benefit from it. - -Since even sport as a category is far too imprecise, as the effects of endurance sports differ greatly from strength training, for example, we are trying to break it down by type of sport. - -To be concrete and give you something you can test yourself we arrange the explanaiton around a concrete example and explain to you they action, reactions and effects. - -:::{admonition} more examples wanted - -The focus should always be on how others can do sport and not on the top performance someone has achieved. - -It's really about the basics. Your experience, which you share here, can help others to pursue their beloved sport more quickly and successfully and is therefore important. -::: - -## Cycling - -:::{admonition} take a friend with you - at least on your first trials -:class: information -A gerneral very good idea can be to take a good friend with you on the first rides. -This is especially important if you are not experienced in T1D. -Always keep in mind please: arrival comes before speed! Safety for you and the others in road traffic is very, very important. -::: - -### Example - -Let's take about 60 minutes of cycling on a flat route with a moderate heart rate as an example. - -1. we take a flat route in order to have an even load for the first exercise. This is not about performance, but purely about learning how you should react to changes in blood glucose. -2. we take the heart rate as an indicator of the load, as it is easy to see whether you are under load or not. -3. we set ourselves the goal of doing a relaxed lap around the neighborhood and focus on staying within our target range during the lap. In my case, this would be 70 <= x <= 180 mg/dl. - -We **don't** take the speed, as this is heavily dependent on personal physical conditions as well as the bike and surface used. It is therefore not very meaningful. - -You should know from the diabetes training courses you have attended that during endurance sports cycling, the insulin active in the body works significantly better than during times without physical exertion. The insulin active in the body is referred to as insulin on board (IoB). It is our most important parameter when cycling with T1D. - -We try to keep the IoB as low as possible at the start and during exercise. IoB should be around 0 or even slightly negative. You can get it there by not eating 3-4 hours before exercise. In the beginning it can also be helpful to exercise in the morning before breakfast, as with the right profile you should always have around 0 for IoB in the morning. - -AAPS shows us the IoB value on the home screen on the left under the blood glucose value. - -![IoB](../images/cycling_20240104-174035.png) - -:::{admonition} ignoring the IoB rule increases the risk for roller coaster BG dramatically -:class: danger -If you ignore this rule, you can still go cycling, but it will be much more difficult to keep your blood sugar levels in balance, so it is better to save this for later tests after several successful simple tests. -::: - -As you should know from the diabetes training courses, you should reduce the basal rate during exercise. The factor is individual. I have found a value of 50% in tests to be suitable for me. - -In AAPS, you should therefore change your profile to 50% before exercise and keep it active until the end of exercise. Some people even do it a certain amount of time before, e.g. 1 hour. Unfortunately, the pre-run is also individual. We will come to the post-run later. - -You should use two carbohydrates during exercise. - -1. medium-fast carbohydrates for the insulin still in the body and -2. very fast carbohydrates to prevent slipping into a hypo. - -For medium-fast carbohydrates, I treat myself to cookies or a banana before exercise, for example. You can also use something else that is more suitable for you. -For very fast carbohydrates, I take 3 teaspoons of dissolved glucose per 100 ml of still water in a 500 ml water bottle on my bike. If I'm cycling longer distances, I take a larger bottle with me and, if necessary, packaged glucose to refill the bottle. I add a little lemon juice for flavor. You can also use something other than lemon juice for the taste. You shouldn't change anything about the dextrose, as dissolved dextrose raises blood sugar levels super quickly. If you only take it in sips, your blood sugar won't go super high either! You can also do this tip at home beforehand as a dry run and see how quickly the change shows up on the CGMS. - -Why do I place so much emphasis on fast carbohydrates? - -1. once you are in a slight hypo, you may get back into the normal range by drinking the dextrose solution. As a rule, however, the oscillation of the curve then begins, which leads to a rollercoaster ride of the blood sugar. You may even be able to keep this within your target range, but you must be constantly vigilant. Without a hypo it is simply the most stable. -2. if you even slip into a somewhat severe hypo (without the need for outside help, of course), you may even have to pause briefly to avoid getting stuck in the hypo. - With both hypos, there is a risk that you will be tempted to switch from drinking 2-3 sips at a time to larger quantities. Not too bad at first, until the oscillation sets in and pushes you into a hyper. You can correct this, but your blood sugar will most likely go on a rollercoaster ride. - -What else is helpful, but not absolutely necessary? -It is important to keep an eye on your blood sugar, as your blood sugar can change enormously (e.g. 30 - 50 mg/dl) within 15 minutes of riding and a little more IoB or a basal rate that is still too high. The best way to keep an eye on it is if it is visible on the handlebars or if it is also displayed on your watch. It is even possible to install an additional app on some Garmin GPS bike computers that displays the blood glucose from XDrip or Nightscout as a data field on the bike computer. The additional app was developed by Andreas May from the T1D community. It is available free of charge in the official connect IQ Store. Certainly an interesting option for riders interested in sports. - -[Link to Andreas May Data Field App on connect IQ store](https://apps.garmin.com/de-DE/apps/5a3e2cda-12f0-4afd-88ed-000e67a68d84) - -Here is a picture of my Garmin Edge 530 bike computer with map, blood sugar and heart rate. - -![Garmin Edge 530 with BG data field](../images/cycling_IMG_1087.jpeg) - -After you have eaten the medium fast carbohydrates (24 - 36 g I take) and the blood sugar is above 100 mg/dl but also below 160 mg/dl, I carry out the profile change to 50% and set the activity temp target. - -:::{admonition} disable SMBs during high temp targets if necessary -:class: danger -Attention: If you prefer not to receive SMBs during the sport, please disable the option "Enable SMB with hight temp targets" in the settings of SMB or DynIFS Plugin. -::: - -The following picture shows the start and end of the sport. The end was specified as the duration when the profile was changed at the start. - -The temporary profile change has the following effects - -1. for a period of 60 minutes -2. a reduction to 50% of the profile and -3. the target is raised by clicking on the Activity Target option, which may have the side effect of disabling the SMBs - see above. - -![profile switch with temp target](../images/cycling_20240104-174056.png) - -The second image shows that the start at IoB was started towards 0. - -![IoB around 0](../images/cycling_20240104-174111.png) - -If the blood sugar drops faster than 15 mg/dl in 5 minutes or if it is at 120 mg/dl and tends to fall, I drink 1-2 sips of dissolved glucose. Then I wait for the next value and proceed as described above. - -You can hardly see it here, but at the beginning I took 2 sips from the bottle several times when my blood sugar started to fall. When it stabilized, I didn't need any more glucose. - -Here is the picture that illustrates this. The chart is saved on the Garmin as a result of the activity. - -![BG chart Garmin](../images/cycling_20240104-174431.png) - -If you should suddenly break out upwards, i.e. above 180 mg/dl, you should consider whether you should make a correction bolus. Caution: Remember the factor and apply it to the correction, otherwise the correction will be too strong. - -If your blood sugar drops below 80 mg/dl, take a break and drink two sips until your blood sugar is back above 100 mg/dl. - -At the end of the ride, the profile change should be finished as the time is up. - -Since we only rode easy for 60 minutes, there shouldn't be a big muscle bulking effect continuing to pull carbohydrates from your blood sugar. However, if it felt strenuous to you, keep an eye on it. This is especially true if you then go straight to bed. It may be better to change your profile to e.g. 80% for sleep. You may come out of sleep slightly too high, but it's better than having a hypo at night. Over time, you will surely find out what happens to you. - -The following pictures show the low intensity of the sport. - -The elevation profile -![](../images/cycling_20240104-174314.png) - -Speed with average and maximum speed - -![](../images/cycling_20240104-174326.png) - -Note the pause at the level crossing, which is also reflected in the heart rate. - -The heart rate. -![](../images/cycling_20240104-174337.png) - -The training effect. -![](../images/cycling_20240104-174358.png) - -The time in the different heart rate training zones. -![](../images/cycling_20240104-174423.png) - -After succesfully mastering this simple example you could go for further targets by stretching - -1. the distance and time -2. the load during the ride -3. the elevation during the right which should make a big impact on the more necessary carbs or further reduction of IoB and percentage of profile switch. - -Based on my experiences I would not expect to come back 100% with time in range over the whole and every ride. - -### Tipps - -I already gave some tipps for during the ride above. - -Here are some further tipps what can go wrong and how you can act to prevent it or react to compensate it. - -#### sky rocket high after ride - -During the ride everything was fine but after siting down and relax the blood sugar go sky rocket high. - -**Possible reason:** This happens when you have drunk too much dissolved glucose. - -**Reaction:** Drink 500 ml water, go to the shower and then control again. Latest after 30 minutes think about giving a correction bolus but be careful when it is short for bed time. Therefore it can be very good to make the first try runs on weekend mornings. - -**Action:** Next time be a bit more cautious in drinking from the dissolved glucose. - -#### hypo during ride - -During the ride you are going into hypo and can't recover your blood sugar during cycling. - -**Possible reason:** Your body cannot absorb enough carbohydrates quickly enough during exercise. - -**Reaction:** Take a rest and corrrect your blood sugar with drinking dissolved glucose. Stay calm: arrival comes before speed. - -**Action:** Did you started with IoB near 0? Have you eaten a small amount of middle fast carbs? Can you increase this or are the not fast enough for your body? Is it possible to prevent going into hypo by reducing the factor for the profile switch? Have you disbaled SMBs during ride as explained above? - -#### sky rocket high during ride - -During the ride your blood sugar goes sky rocket high. - -**Possible reason:** You have got taken too much carbs for your IoB at that time. Beneath for sure the typical technical problems with your -insulin pump like leakage or blockage of the catheder! - -**Reaction:** If it is too high for you take a rest and correct with a bolus. Keep in mind that you must ride home and therefore make it carefully. Drink 500 ml pure water without carbs. Stay calm: arrival comes before speed. - -**Action:** Have you eaten too much? Especially have you drunk too much from the dissolved glucose during the ride? Is your percentage of reduction the profile during profile switch too low and you can increase this? diff --git a/docs/CROWDIN/lt/buildingAAPS.md b/docs/CROWDIN/lt/buildingAAPS.md deleted file mode 100644 index 98164a09e49b..000000000000 --- a/docs/CROWDIN/lt/buildingAAPS.md +++ /dev/null @@ -1,28 +0,0 @@ -# Dummy - -## This is a dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - - -## This is another dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - - -## This is another another dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - diff --git a/docs/CROWDIN/lt/completingObjetives.md b/docs/CROWDIN/lt/completingObjetives.md deleted file mode 100644 index 98164a09e49b..000000000000 --- a/docs/CROWDIN/lt/completingObjetives.md +++ /dev/null @@ -1,28 +0,0 @@ -# Dummy - -## This is a dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - - -## This is another dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - - -## This is another another dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - diff --git a/docs/CROWDIN/lt/dummy.md b/docs/CROWDIN/lt/dummy.md deleted file mode 100644 index 98164a09e49b..000000000000 --- a/docs/CROWDIN/lt/dummy.md +++ /dev/null @@ -1,28 +0,0 @@ -# Dummy - -## This is a dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - - -## This is another dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - - -## This is another another dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - diff --git a/docs/CROWDIN/lt/intro.md b/docs/CROWDIN/lt/intro.md deleted file mode 100644 index b0433df9abcf..000000000000 --- a/docs/CROWDIN/lt/intro.md +++ /dev/null @@ -1,291 +0,0 @@ -![20-06-23v2 AAPS simple overview-cropped](https://github.com/openaps/AndroidAPSdocs/assets/94044064/e505b73b-09a0-42a4-a1ab-b830a0741234) - -# Introduction to APS and AAPS - -## What is an “Artificial Pancreas System”? - -A human pancreas does a lot of things besides regulating blood sugar. However, the term **“Artificial Pancreas System” (APS)** usually refers to a system which works to automatically keep blood sugar levels within healthy limits. - -The most basic way to do this is by detecting **glucose levels**, using these values to do **calculations**, and then delivering the (predicted) right amount of **insulin** to the body. It repeats the calculation, every few minutes, 24/7. It uses **alarms** and **alerts** to inform the user if intervention or attention is needed. This system is typically made up of a **glucose sensor**, an **insulin pump** and an **app** on a phone. - -You can read more about the different artificial pancreas systems currently in use and in development in this 2022 review article: - -![Frontiers](./images/FRONTIERS_Logo_Grey_RGB.png) [Future Directions in Closed-Loop Technology](https://www.frontiersin.org/articles/10.3389/fendo.2022.919942/full#:~:text=Fully%20closed%2Dloop%20systems%2C%20unlike,user%20input%20for%20mealtime%20boluses). - -In the near future, some so-called "dual-hormone" systems will also have the ability to infuse glucagon alongside insulin, with the aim of preventing severe hypos and allowing even tighter blood glucose control. - -An artificial pancreas can be thought of as an [“autopilot for your diabetes”]. (https://www.artificialpancreasbook.com/) What does that mean? In an aircraft, an autopilot does not do the complete job of the human pilot, the pilot cannot sleep through the entire flight. The autopilot aids the work of the pilot. It relieves them of the burden of permanently monitoring the aircraft, allowing the pilot to concentrate on wider monitoring from time to time. The autopilot receives signals from various sensors, a computer evaluates them together with the pilot’s specifications and then makes the necessary adjustments, alerting the pilot to any concerns. The pilot no longer has to worry about constantly making decisions. - -## What does hybrid closed loop mean? - -The best solution for type 1 diabetes would be a “functional cure” (probably an implant of pancreatic cells which are protected from the immune system). While we are waiting for that, a “full closed loop” artificial pancreas is probably the next best thing. This is a tech system that doesn’t need any user input (like bolusing insulin for meals, or announcing exercise), with good regulation of blood glucose levels. At the moment, there are no widely available systems which are “full” closed loop, they all need some user input. The currently available systems are called “hybrid” closed loop, because they use a combination of automated technology and user input. - -## How and why did looping start? - -The development of commercial technology for people with type 1 diabetes (T1D) is very slow. In 2013 the T1D community founded the #WeAreNotWaiting movement. They developed systems themselves using existing approved technology (insulin pumps and sensors) to improve blood glucose control, safety, and quality of life. These are known as DIY (do-it-yourself) systems, because they are not formally approved by health bodies (FDA, NHS etc). There are four main DIY systems available: OpenAPS, **AAPS**, Loop and iAPS. - -A great way to understand the fundamentals of DIY looping is to read Dana Lewis’s book “Automated Insulin Delivery”. You can access it \[here\] (https://www.artificialpancreasbook.com/) for free (or buy a hardcopy of the book). If you want to understand more about OpenAPS, which** AAPS** has developed from, the \[OpenAPS website\] (https://openaps.org/what-is-openaps/) is also a great resource. - -Several commercial hybrid closed loop systems have been launched, the most recent of which are \[CamAPS FX\] (https://camdiab.com/) (UK and EU) and \[Omnipod 5\] (https://www.omnipod.com/en-gb/what-is-omnipod/omnipod-5) (USA and EU). These are very different to DIY systems, mainly because they both include a “learning algorithm” which adjusts how much insulin is delivered according to your insulin needs from previous days. Many people in the DIY community have already tried out these commercial systems and compared them with their DIY system. You can find out more about how the different systems compare by asking on the dedicated Facebook groups for these systems, on the \[AAPS Facebook group\] (https://www.facebook.com/groups/AndroidAPSUsers/) or on \[Discord\] (https://discord.com/invite/4fQUWHZ4Mw). - -## What is Android APS (AAPS)? - -![image](https://github.com/openaps/AndroidAPSdocs/assets/94044064/0f089d96-b7ee-452a-aa9d-aae10ab58971) - -**Figure 1**. Basic outline of the Android APS (Artificial Pancreas System), AAPS. - -Android APS (AAPS) is a hybrid closed loop system, or Artificial Pancreas System (APS). It makes its insulin dosing calculations using established \[OpenAPS\] (https://openaps.org/) algorithms (a set of rules) developed by the #WeAreNotWaiting type 1 diabetes community. - -Since OpenAPS is only compatible with certain older insulin pumps, AAPS (which can be used with a wider range of insulin pumps) was developed in 2016 by Milos Kozak, for a family member with type 1 diabetes. Since those early days, **AAPS** has been continually developed and refined by a team of volunteer computer developers and other enthusiasts who have a connection to the type 1 diabetes world. Today, **AAPS** is used by approximately 10,000 people. It is a highly customisable and versatile system, and because it is open-source, it is also readily compatible with many other open-source diabetes softwares and platforms. The fundamental components of the current **AAPS** system are outlined in Figure 1 above. - -## What are the basic components of AAPS? - -The “brain” of AAPS is an **app** which you build yourself. There are detailed step-by-step instructions for this. You then install the **AAPS app** on a compatible **Android smartphone** (1). A number of users prefer their loop on a separate phone to their main phone. So, you don’t necessarily have to be using an Android phone for everything else in your life, just for running your AAPS loop. - -The **Android smartphone** will also need to have another app installed on it as well as **AAPS**, either a modified Dexcom app called build-your-own dexcom app (**BYODA**) or Xdrip+. This receives glucose data from a sensor (2) by bluetooth, and then sends the data internally on the phone to the **AAPS app**. - -The **AAPS app** uses a decision making process (**algorithm**) from OpenAPS. Beginners start out using the basic **oref0** algorithm, but it is possible to switch to using the newer **oref1** algorithm as you progress with AAPS. Which algorithm you use (oref0 or oref1), depends on which suits your specific situation best. In both cases, the algorithm takes into account multiple factors, and performs rapid calculations every time a new reading comes in from the sensor. The algorithm then sends instructions to the insulin pump (3) on how much insulin to deliver by bluetooth. All the information can be sent by mobile data or wifi to the internet. This data can also be shared with followers if desired, and/or collected for analysis. - -## What are the advantages of the AAPS system? - -The OpenAPS algorithm used by **AAPS** controls blood sugar levels in the absence of user input, according to the users’ defined parameters (important ones being basal rates, insulin sensitivity factors, insulin-to-carb ratios, duration of insulin activity etc.), reacting every 5 minutes to the new sensor data. Some of the reported advantages of using AAPS are extensive fine-tunable options, automations and increased transparency of the system for the patient/caregiver. This can result in better control over your (or your dependent’s) diabetes, which in turn may give improved quality of life and increased peace of mind. - -Practical advantages include: - -- **Hardware flexibility**: **AAPS** works with a wide range of insulin pumps and sensors. So for example, if you develop an allergy to Dexcom sensor patch glue, you could switch to using a Libre sensor instead. That offers flexibility as life changes. You don't have to rebuild, just tick a different box in the AAPS app to change your hardware. - -- **Highly customisable with wide parameters**: here are some examples of the possibilities with AAPS: a) The ability to set a lower glucose target 30 min before eating; you can set the target as low as 72 mg/dL (4.0 mmol/L). b) If you are insulin-resistant resulting in high blood sugars, **AAPS** allows you to set an **automation** rule to activate when BG rises above 8 mmol/L (144 mg/dL), switching to a 120% profile (resulting in an 20% increase in basal and strengthening of other factors too, compared to your normal **profile** setting). The automation will last according to the scheduled time you set. Such an automation could be set to only be active on certain days of the week, at certain times of day, and even at certain locations. c) If your child is on a trampoline with no advance notice, **AAPS** allows insulin suspension for a set time period, directly via the phone. d) After reconnecting a tubed pump which has been disconnected for swimming, AAPS will calculate the basal insulin you have missed while disconnected and deliver it carefully, according to your current BG. Any insulin not required can be overridden by just “cancelling” the missed basal. f) **AAPS** has the ability to set different profiles for different situations and easily switch between them. Features which make the algorithm quicker to bring down elevated BG (like supermicro boluses (“SMB”), unannounced meals, (“**UAM**”) can be set to only work during the daytime, if you are worried about night-time hypos. - - -These are all examples, the full range of features gives huge flexibility for daily life including sport, illness, hormone cycles etc. Ultimately, it is for the user to decide how to use this flexibility, and there is no one-size-fits-all automation for this. - -- **Remote monitoring**: there are multiple possible monitoring channels (Sugarmate, Dexcom Follow, Xdrip+, Android Auto etc.) which are useful for parents/carers and adults in certain scenarios (sleeping/driving) who need customisable alerts. In some apps (Xdrip+) you can also turn alarms off totally, which is great if you have a new sensor “soaking” or settling down that you don’t want to loop with yet. - -- **Remote control**: a significant advantage of **AAPS **over commercial systems is that it is possible for followers, using authenticated text (SMS) commands or via an app (Nightscout or NSClient) to send a wide range of commands back to the ****AAPS** **system. This is used extensively by parents of kids with type 1 diabetes who use AAPS. It is very useful in the playground, for example, if you want to pre-bolus for a snack from your own phone, and your child is busy playing. It is possible to monitor the system (e.g. Fitbit), send basic commands (e.g. Samsung Galaxy watch 4), or even run the entire AAPS system from a high-spec smartwatch (5) (e.g. LEMFO LEM14). In this last scenario, you don’t need to use a phone to run AAPS. As battery life on watches improves, this last option is likely to become increasingly attractive. - -- **No commercial constraints due to open application interfaces**: beyond the use of an open source approach, which allows the source code of **AAPS** to be viewed at any time, the general principle of providing open programming interfaces gives other developers the opportunity to contribute new ideas that allow users to live more easily with their diabetes. This is complementary to commercial systems which adopt the innovations from DIY, where interfaces are only made possible in return for licensing, thus preventing innovations in particular that are not-for-profit. Good examples for such integrations are NightScout, Nightscout Reporter, Xdrip+ M5 stack etc. - -- **Detailed app interface**: It is easy to keep track of things like: insulin levels, cannula age, sensor age, pump battery age, and many actions can be done through the **AAPS** app (priming the pump, disconnecting the pump etc.), instead of on the pump itself. - -- **Accessibility and affordability**: **AAPS** gives people who currently can’t afford to self-fund, or don’t have funding/insurance, access to a world-class hybrid closed looping system which is conceptually years ahead, in terms of development, of the commercial systems being offered by clinics. You currently need to have a Nightscout account to set up **AAPS**. Although the Nightscout account it not necessarily required after setup, many people continue to use Nightscout for collecting their data, and for remote control. So, although **AAPS **itself is free, setting up Nightscout through one of the various platforms may incur a fee (E0 - E12), depending on what level of support you want (see comparison table). **AAPS** works with a wide range of affordable (starting from approx E150) Android phones. In comparison, Loop currently costs around $80 a year for the Apple development licence and CamAPS FX costs around E80/month (as at 2023). - -- ****Support**: No automated insulin delivery system is perfect. Commercial and open-source systems share many common glitches in both communications and temporary hardware failure. There is a community of AAPS users on both Facebook and Discord and Github who designed, developed and are currently using **AAPS** all over the world. There are Facebook support groups and help from clinic/commercial companies for the commercial APS systems - it is worth speaking to the users, or former users of these systems to get feedback on the common glitches, the quality of the education programme and the level of ongoing support provided. - -- **Predictability, transparency and safety**: with no learning algorithm, **AAPS** is logical and in some respect, more predictable, which may make it easier to know when a setting is wrong, and to adjust it accordingly. You can see exactly what the system is doing, why it is doing it, and set its operational limits, which puts the control (and responsibility) in your hands. This can provide the user with confidence, and a sounder sleep. - -- **Access to advanced features through dev modes including full closed loop**: **AAPS **documentation focuses on the mainstream **“master”** branch of **AAPS**, however, research and development is going on all the time. More experienced users may wish to explore the experimental features in the **development** branch such as integration of Dexcom G7, and automatically adjusting insulin delivery according to short-term sensitivity changes (DYNISF), not having to bolus for meals, and generally trying to make life with type 1 diabetes as convenient as possible. - -- **Ability to contribute yourself to further improvements**: type 1 diabetes can be highly frustrating and isolating. Having control over your own diabetes tech, with the possibility to “pay it forward” as soon as you are making progress by helping others on their journey can be really rewarding. You can educate yourself, discover the roadblocks and look for and even contribute to new developments and the documentation. There will be others with the same quest to bounce ideas off and work with. This is the essence of #WeAreNotWaiting. - - -## How does AAPS compare to MDI and open looping? - -Multiple daily injections (MDI, a) usually involve giving an injection of a long-lasting insulin (e.g. Tresiba) once a day, with injections of faster-acting insulin (e.g. Novorapid, Fiasp) at mealtimes, or for corrections. Open pumping (b) involves using a pump to deliver basal at pre-programmed rates of rapid-acting insulin, and then boluses through the pump at mealtimes or for corrections. The basics of a looping system is that the App uses the glucose data to instruct the pump to stop insulin delivery when it predicts you are heading for a low, and to give you extra insulin if your glucose levels are rising and predicted to go too high (c). Although this is oversimplified, (mostly because hybrid closed looping has a lot of additional useful features) the key features of each system are shown in **Figure 2**. - -![image](https://github.com/openaps/AndroidAPSdocs/assets/94044064/4e7d8608-684d-4c69-9c61-88c9539f5d6f) - -**Figure 2**. Overview of (a) MDI, (b) open-loop pumping and (c) hybrid closed loop pumping - -## How does AAPS compare to other looping systems? - -At present there are four major open source closed loop systems available: OpenAPS, **AAPS**, \[Loop\] (https://loopkit.github.io/loopdocs/#what-is-loop) and iAPS, (formerly FreeAPS X). The features of the different systems are shown in the table below: - -| Devicestyp | Name | [Open APS](https://openaps.readthedocs.io/en/latest/) | [AAPS](https://wiki.aaps.app) | [Ciklas](https://loopkit.github.io/loopdocs/) | [iAPS](https://iaps.readthedocs.io/en/latest/) | -| ---------- | -------------------------------------------------------------------------------------------------------- | ----------------------------------------------------- | ------------------------------------------- | --------------------------------------------- | ---------------------------------------------- | -| PUMP | Older Medtronic | ![available](./images/available.png) | ![available](./images/available.png) | ![available](./images/available.png) | ![available](./images/available.png) | -| PUMP | Older Omnipod (Eros) | ![unavailable](./images/unavailable.png) | ![available](./images/available.png) | ![available](./images/available.png) | ![available](./images/available.png) | -| PUMP | Newer Omnipod (Dash) | ![unavailable](./images/unavailable.png) | ![available](./images/available.png) | ![available](./images/available.png) | ![available](./images/available.png) | -| PUMP | DANA R, DANA RS, DANA I | ![unavailable](./images/unavailable.png) | ![available](./images/available.png) | ![unavailable](./images/unavailable.png) | ![unavailable](./images/unavailable.png) | -| PUMP | Roche Combo, Insight | ![unavailable](./images/unavailable.png) | ![available](./images/available.png) | ![unavailable](./images/unavailable.png) | ![unavailable](./images/unavailable.png) | -| NGJ | Dexcom G4, G5, G6 | ![available](./images/available.png) | ![available](./images/available.png) | ![available](./images/available.png) | ![available](./images/available.png) | -| NGJ | Libre 1 (requires Miao Miao) | ![available](./images/available.png) | ![available](./images/available.png) | ![available](./images/available.png) | ![available](./images/available.png) | -| NGJ | Libre 2 | ![available](./images/available.png) | ![available](./images/available.png) | ![available](./images/available.png) | ![available](./images/available.png) | -| NGJ | Libre 3 | | ![unavailable](./images/unavailable.png) | --- | ![unavailable](./images/unavailable.png) | -| NGJ | Medtronic Enlite | | --- | ![unavailable](./images/unavailable.png) | --- | -| NGJ | [Dexcom G7](https://androidaps.readthedocs.io/en/latest/Hardware/DexcomG7.html) | | ![available](./images/available.png) (beta) | ![available](./images/available.png) | ![available](./images/available.png) | -| NGJ | [Eversense](https://androidaps.readthedocs.io/en/latest/Hardware/Eversense.html) | | ![available](./images/available.png) | | ![available](./images/available.png) | -| NGJ | [MM640g/MM630g](https://androidaps.readthedocs.io/en/latest/Hardware/MM640g.html) | | ![available](./images/available.png) | | ![available](./images/available.png) | -| NGJ | [PocTech](https://androidaps.readthedocs.io/en/latest/Hardware/PocTech.html) | | ![available](./images/available.png) | | ![available](./images/available.png) | -| NGJ | [Nightscout as BG Source](https://androidaps.readthedocs.io/en/latest/Hardware/CgmNightscoutUpload.html) | | ![available](./images/available.png) | | ![available](./images/available.png) | -| Phone | Android | ![available](./images/available.png) | ![available](./images/available.png) | ![unavailable](./images/unavailable.png) | ![unavailable](./images/unavailable.png) | -| Phone | iPhone | ![available](./images/available.png) | ![unavailable](./images/unavailable.png) | ![available](./images/available.png) | ![available](./images/available.png) | - -[OpenAPS](https://openaps.readthedocs.io/) was the first Open Source Closed Loop System. Ji naudoja mažąjį kompiuterį, tokį kaip Raspberry Pi ar Intel Edison. Both AndroidAPS (AAPS) and iAPS use the OpenAPS algorithms, whereas Loop uses a separate algorithm. You can read a comparison of iAPS and **AAPS** here. - -An international peer-reviewed consensus statement containing practical guidance on open source looping was written by and for health-care professionals, and published in a leading medical journal in 2022. It is well worth a read (including for your diabetes clinic) and summarises the main technical differences between the different open-source hybrid closed loop systems: - - Lancet Diabetes Endocrinol, 2022; 10: 58–74 - -[https://www.ncbi.nlm.nih.gov/pmc/articles/PMC8720075/](https://www.ncbi.nlm.nih.gov/pmc/articles/PMC8720075/) - -It is hard to get a “feel” for any system without using it, or talking to others who are using it, so do reach out to others on Facebook/Discord and ask. Most people find that AAPS is incredibly sophisticated in comparison to other hybrid closed loop systems (particularly the commercial systems), with a huge number of potentially customisable settings and features, discussed above. Some people can find this a little overwhelming in the beginning, but there is no rush to investigate all the possibilities at once, you can progress as slowly or as fast as you would like, and there is help available at every step of the way. - -## Does AAPS use artificial intelligence or any learning algorithm? - -Ne. **AAPS** does not have any complicated machine learning algorithms, multiple-parameter insulin response models, or differential equations. As such, the system is open and transparent in how it works, and has the ability to be understood not just by experts, but also by clinicians and patients. It also means that if you have a sharply varying schedule (maybe switching from a stressful week at work to a relaxing holiday) and are likely to need a significantly different amount of insulin, you can immediately switch **AAPS** to run a weaker/stronger profile. A ‘learning system’ will do this adjustment for you automatically, but is likely to take longer to adjust the insulin delivery. - -## Which system is right for me or my dependent? - -Practically, your choice of system is often restricted by which pump you already have, or can obtain from your medical provider, and your choice of phone (Apple or Android). If you don’t yet have a pump you have the biggest choice of systems. Technology is continually evolving, pumps are being discontinued and new pumps and sensors are being released. Most open-source systems work with the main sensors (Libre and Dexcom) or are quickly adapted to work with new sensors a year or so after they are released (with a bit of time delay for safety and stability testing). - -Most **AAPS **users report more time in range, HbA1c reductions, as well as quality of life improvements from having a system that can auto-adjust basal rates overnight during sleep, and this is true for most hybrid closed loop APS. Some people have a preference for a very simple system which is not very customisable (which means you may prefer a commercial system), and others find this lack of control very frustrating (you may prefer an open-source system). If you (or your dependent) are newly diagnosed, a common route is to get the hang of MDI plus sensor first, then progress to a pump which has the potential for looping, then to **AAPS**, but some people (especially small kids) may go straight to a pump. - -It is important to note that the **AAPS** user needs to be proactive to troubleshoot and fix problems themselves, with help from the community. This is a very different mindset to that when using a commercial system. With **AAPS** a user has more control, but also the responsibility, and needs to be comfortable with that. - -## Is it safe to use open-source systems like AAPS? - -A more accurate question is probably “is it safe compared to my current type 1 diabetes insulin delivery system?” since no method of insulin delivery is without risk. There are many checks and balances in place with **AAPS**. A recent paper looked at the use of**** AAPS ****in a computer simulated set-up, [https://www.liebertpub.com/doi/epub/10.1089/dia.2019.0375](https://www.liebertpub.com/doi/epub/10.1089/dia.2019.0375) which was an effective way to unobjectively trial how safe and effective the system is. More generally, it is estimated that over 10,000 individuals worldwide are using open-source automated-insulin delivery systems, and uptake continues to increase globally. - -Any device that uses radio communications could be hacked, and this is true for a non-looping insulin pump as well. Currently, we are not aware of anyone attempting to harm individuals by hacking their diabetes-related medical equipment. However, there are multiple ways to protect against such risks: - -1. In the pump settings, limit both the max bolus allowed and max temporary basal settings to amounts that you believe are safest. These are hard limits that we do not believe any malicious hacker could circumvent. - -2. Set your CGM alarms enabled for both highs and lows. - -3. Monitor your insulin delivery online. Nightscout users can set additional alarms to alert for a wide variety of conditions, including conditions that are much more likely to occur than a malicious attack. In addition to highs and lows, Nightscout can display diagnostic data useful for verifying that the pump is operating as desired, including current IOB, pump temporary basal history, pump bolus history. It can also be configured to proactively alert users to undesirable conditions, such as predicted highs and lows, low insulin reservoir, and low pump battery. - - -If a malicious attack was made on your insulin pump, these strategies would significantly mitigate the risk. Every potential **AAPS** user needs to weigh the risks associated with using **AAPS**, versus the risks of using a different system. - -## How can I approach discussing AAPS with my clinical team? - -Depending on the country - link to doctors section of docs - - Lancet Diabetes Endocrinol, 2022; 10: 58–74 - -[https://www.ncbi.nlm.nih.gov/pmc/articles/PMC8720075/](https://www.ncbi.nlm.nih.gov/pmc/articles/PMC8720075/) - -## Q: Why can’t I just download AAPS and use it straight away? - -The **AAPS** app is not provided in Google Play - you have to build it from source code by yourself for legal reasons. **AAPS** is unlicensed, meaning that it does not have approval by any regulatory body authority in any country. **AAPS**is deemed to be carrying out a medical experiment on yourself, and is carried out at the user’s own risk. - -Setting up the system requires patience, determination and the gradual development of technical knowledge. All the information and support can be found in these documents, elsewhere online, or from others who have already done it. It is estimated that over 2000 people have successfully built and are currently using **AAPS** worldwide. - -The developers of **AAPS**t ake safety incredibly seriously, and want others to have a good experience of using **AAPS**. That is why it is essential that every user (or carer, if the user is a child): - -- builds the AAPS system themself and works through the **objectives** so that they have reasonably good personalised settings and understand the basics of how AAPS ****works by the time they “close the loop”; - -- backs up their system by exporting and saving important files (like keystore and settings .json file) somewhere safe, so you can setup again quickly if needed; - -- updates to newer master versions as and when they become available; and - -- maintains and monitors the system to ensure it is working properly. - - -## Q: What is the connectivity of the AAPS system? - -**Figure 3 (below)** shows one example of the **AAPS** system for a user who do not require any followers interacting with the system: - -![potential AAPS connectivity setup with no followers](./images/intro03.png) - -**Figure 4 (below)** shows the full potential of the **AAPS** system for a user who has followers and requires a monitor and send adjust the system remotely (like a child with T1D): - -![potential AAPS connectivity setup with followers](./images/intro04.png) - -## Q: How does AAPS get continually developed and improved? - -Most **AAPS** users use the fully tested **master** version of AAPS, which has been tested for bugs and problems, before being released to the community. Behind the scenes, the developers try out new improvements, and test these out in “developer” (**dev**) versions of **AAPS** with a user community who are happy to do bug updates at short notice. If the improvements work well, they are then released as a new “master” version of **AAPS**. Any new master release is announced on the Facebook group, so that the mainstream **AAPS** users can read about and update to the new master version. - -Some experienced and confident **AAPS ** users conduct experiments with emerging technologies and with dev versions of the **AAPS** app, which can be interesting for the less adventurous users to read about, without having to do it themselves! People tend to share these experiments on the Facebook group too. - -You can read more about some of these experiments and discussion on emerging tech here: - -[https://www.diabettech.com/](https://www.diabettech.com/) - -[https://bionicwookie.com/](https://bionicwookie.com/) - -## Q: Who can benefit? - -| User Type | -| ------------------------------------------- | -| ✔️ type 1 diabetic | -| ✔️ caregiver or parent of a type 1 diabetic | -| ✔️ blind users type 1 diabetic | -| ✔️ *clincians and healthcare professionals | - -The above table assumes that the user has access to both continuous gluocse monitor and insulin pump. - -*All data from **AAPS** can be made available to healthcare professionals via data sharing platforms, including NightScout that provides logging and real time monitoring of CGM data, insulin delivery, carbohydrate entries, predictions and settings. Nightscout records include daily and weekly reports which can aid healthcare professionals' discussions with type 1 patients with more accurate data on glycemic control and any behavioural considerations. - -## Q: What benefits can I get? - -With investment of your time, **AAPS** can potentially lead to: - -- alleviating the stress and burden of managing type 1 diabetes; - -- reducing the multitude of mundane decisions that arise from type 1 diabetes; - -- the provision of personalised and dynamic insulin dosing based on real-time data which can cut down the need for hypo treatments and reduce hyperglycemia episodes; - -- an increased knowledge of insulin management and confidence to better fine tune your settings; - -- the ability to create automatic settings (**automations**) that are tailored to fit in with your lifestyle; - -- improved sleep quality and overall reduction in the frequency of nighttime interventions; - -- remote monitoring and administration of insulin delivery for caregivers of type 1 diabetics; and - -- streamlining of all your portable diabetic equipment (continuous glucose monitor and insulin portable devices) by replacing them with an android phone controlled by **AAPS**. - - -Ultimately,**AAPS** can empower individuals to better manage their diabetes resulting in stable blood sugars and improved long term health outcomes. - ---- - -## AAPS First Steps - -Welcome. This is an introduction to aid beginners getting started with **AAPS** (or commonly referred to as "looping"). - -## Safety - -“_With great powers comes great responsibilities…_” - -**AAPS** is designed with an extensive set of safety features with limits imposed and gradually removed with completion of the **objectives **(predominately made up of multiple choice questions). An **AAPS** feature will be unlocked as the Objectives are successfully completed. This process will gradually allow the user to migrate from Open Loop to Closed Loop. - -This has been done to achieve the best possible experience with **AAPS** in order to prevent common mistakes that new users tend to make when starting to loop. The safety parameters have been built upon typical errors and general trends **AAPS** developers have observed with new users. Mistakes can happen because the beginner is inexperienced and too eager to get started with AAPS or has overlooked the required materials. Do not worry, we have all been there! - -## Key Principles - -The key principles and concepts of looping must be understood by the user before using **AAPS**. This is achieved by investing your personal time into reading the **AAPS** documentation, and completing the Objectives which is aimed to provide you with a solid platform for safe and effective use of **AAPS**. The volume of **AAPS** documentation may seem overwhelming at first but be patient and trust the process - with the proper approach, you'll get there! The overall process will depend upon the beginner’s progress and completion of objectives can typically take between 6 to 9 weeks . - -## Plan for hiccups - -At the preliminary stages of **AAPS**, you should expect to experience some hiccups whilst trying to fine tune your settings. **AAPS**’ glitches cannot be flushed out until the system is used in everyday life. Please plan accordingly and allow a sensible amount of time to troubleshoot and resolve such issues. - -## Flexibility/Adaptability - -Success with **AAPS** requires a proactive approach, a willingness to reflect on the BG data and flexibility to make the necessary adjustments to **AAPS** in order to improve your outcomes. Just as it is nearly impossible to learn to play a sport by reading about the rules alone, the same can be said of **AAPS**. - -## Technology compatibility - -There are limitations with **AAPS** as it is accessible for only certain types of insulin pumps or CGMs, and some technology may not be available for use in various countries. In order to avoid any disappointment or frustrations, please read please read Component Set Up (Section INSERT). - -## App Build Time - -The time to build the **AAPS**(under Section INSERT) depends on your level of expertise and technical ability. Typically for inexperienced users, it can take up to half a day or a full day (with help from the community) in order to build the **AAPS**. The process will significantly speed up as you become more experienced at building the **AAPS**. To aid the build process there are sections dedicated for: -- list of questions and answers for frequent errors that are likely to occur under FAQs (Section K); -- “How to install AAPS? (Section INSERT) which includes Troubleshooting subsection. - -## Keystore & configurations settings a export file - -A “keystore” is a password encrypted file unique to your own copy of **AAPS**. Your android phone uses it to ensure that nobody else can upgrade your own copy without the keystore. In short, as part of the **AAPS** build, you should: - -- save the your keystore file (.jks file used to sign your app) in a safe place; -- keep a note of your password for your keystore file. - -By doing the above, this will ensure that you can use that exact same keystore file each time an updated version of **AAPS** is created. On average, there will be 2-3 AAPS updates required each year. - -In addition, **AAPS** provides the ability to export all your configuration settings. This ensures that you can safely recover your system while changing phones, upgrading/reinstalling the application with minimum disruption. - -## Troubleshootng - -Please feel free to reach out to the AAPS community if there is anything you feel unsure about - there is no such thing as a silly question! All users with various levels of experience are encouraged to ask questions as necessary. Response times to questions are usually quick, typically only a few hours due to the volume of **AAPS** users. - -a) check the documentation; b) ask AAPS facebook group (https://www.facebook.com/groups/AndroidAPSUsers); and c) ask our discord channel. - -## Section overview - -AAPS documentation is made up of the following Sections: - -[INSERT ONCE SECTIONS /SUB SECTIONS AGREED] ---- diff --git a/docs/CROWDIN/lt/maintaining.md b/docs/CROWDIN/lt/maintaining.md deleted file mode 100644 index 98164a09e49b..000000000000 --- a/docs/CROWDIN/lt/maintaining.md +++ /dev/null @@ -1,28 +0,0 @@ -# Dummy - -## This is a dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - - -## This is another dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - - -## This is another another dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - diff --git a/docs/CROWDIN/lt/optimizing.md b/docs/CROWDIN/lt/optimizing.md deleted file mode 100644 index 98164a09e49b..000000000000 --- a/docs/CROWDIN/lt/optimizing.md +++ /dev/null @@ -1,28 +0,0 @@ -# Dummy - -## This is a dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - - -## This is another dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - - -## This is another another dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - diff --git a/docs/CROWDIN/lt/prepairing.md b/docs/CROWDIN/lt/prepairing.md deleted file mode 100644 index 0f94b1322db4..000000000000 --- a/docs/CROWDIN/lt/prepairing.md +++ /dev/null @@ -1,145 +0,0 @@ -# Prepairing - -## Guide to the Android APS doc - -### First Steps -Welcome. This is an introduction to aid beginners to the concept of Do-It-Yourself-APS (Android-Artificial-Pancreas-Systems “AAPS”) is commonly referred to as ‘looping’.. - -#### Safetys -“With great powers come great responsibilities…” - -AAPS is designed with an extensive set of safety features with limits imposed and gradually removed with completion of the [Objectives](https://androidaps.readthedocs.io/en/latest/Usage/Objectives.html) (predominately made up of multiple choice questions). An AAPS feature will be unlocked as the Objectives are successfully completed. This process will gradually allow the user to migrate from Open Loop to Closed Loop. - -This has been done to achieve the best possible experience with AAPS by preventing common mistakes new users tend to make when starting to loop. The safety parameters have been built upon typical errors and general trends AAPS developers have observed with new users. Mistakes can happen because the beginner is inexperienced and too eager to get started with AAPS or has overlooked the required materials. Do not worry, we have all been there! - -#### Key Principles - -The key principles and concepts of looping must be understood by the user before using AAPS. This is achieved by investing your personal time into reading the AAPS documentation, and completing the [Objectives](https://androidaps.readthedocs.io/en/latest/Usage/Objectives.html) which is aimed to provide you with a solid platform for safe and effective use of AAPS. The volume of AAPS documentation may seem overwhelming at first but be patient and trust the process - with the proper approach, you'll get there! The overall process will depend upon the beginner’s progress and completion of objectives which typically take between 6 to 9 weeks . - -#### Plan for hiccups - -At the preliminary stages of AAPS, you should expect to experience some hiccups whilst trying to fine tune your settings. AAPS’ glitches cannot be flushed out until the system is used in everyday life. Please plan accordingly and allow a sensible amount of time to troubleshoot and resolve such issues. - -#### Flexibility/Adaptability - -Success with AAPS requires a proactive approach, a willingness to reflect on the BG data and flexibility to make the necessary adjustments to AAPS in order to improve your outcomes. Just as it is nearly impossible to learn to play a sport by reading about the rules alone, the same can be said of AAPS. - -#### Technology compatibility -There are limitations with AAPS as it is accessible for only certain types of insulin pumps or CGMs, and some technology may not be available for use in various countries. In order to avoid any disappointment or frustrations, please read [Component Set Up (Section E).](https://androidaps.readthedocs.io/en/latest/Configuration/BG-Source.html) - -#### App Build time -The time to build the AAPS (under Section D) depends on your level of expertise and technical ability. Typically for inexperienced users, it can take up to half a day or a full day (with help from the community) in order to build the AAPS. The process will significantly speed up as you become more experienced at building the AAPS.  - -To aid the build process there are sections dedicated for: - -- list of questions and answers for frequent errors that are likely to occur under [FAQs (Section](https://androidaps.readthedocs.io/en/latest/Getting-Started/FAQ.html) K); - -- “[How to install AAPS](https://androidaps.readthedocs.io/en/latest/Installing-AndroidAPS/Building-APK.html)? (Section D) which includes [Troubleshooting](https://androidaps.readthedocs.io/en/latest/Usage/troubleshooting.html) subsection. - - -#### Keystore & configuration settings export  file - -A “keystore” is a password encrypted file unique to your own copy of AAPS. Your android phone uses it to ensure that nobody else can upgrade your own copy without the keystore.In short, as part of the AAPS build, you should: - -1. save the your keystore file (.jks file used to sign your app) in a safe place; - -2. keep a note of your password for your keystore file. - - -By doing the above, this will ensure that you can use that exact same keystore file each time an updated version of AAPS is created. On average, there will be 2-3 updates to the AAPS required each year. In addition, AAPS provides the ability to [export all your configuration settings](https://androidaps.readthedocs.io/en/latest/Usage/ExportImportSettings.html). This ensures that you can safely recover your system while changing phones, upgrading/reinstalling the application with minimum disruption.  - -#### Trikčių šalinimas - -Please feel free to reach out to the AAPS community if there is anything you feel unsure about - there is no such thing as a silly question!  All users with various levels of experience are encouraged to ask questions as necessary. Response times to questions are usually quick, typically only a few hours due to the volume of AAPS users.  - -##### [check the documentation](https://androidaps.readthedocs.io/en/latest/index.html) - -##### [ask our facebook group](https://www.facebook.com/groups/AndroidAPSUsers/) - -##### [ask our discord channel](https://discord.com/channels/629952586895851530/629954570394533889) - -#### Section overview - -AAPS documentation is made up of the following Sections: - -##### [Getting started](https://androidaps.readthedocs.io/en/latest/Getting-Started/Safety-first.html) - -This is a must read to understand the general concept of what an artificial pancreas system is designed to do. - -##### [What do I need?](https://androidaps.readthedocs.io/en/latest/Module/module.html) - -This explains AAPS’ compatibility with CGMs (Continuous Glucose Monitors) and insulin pumps. It also provides a guide on the correct assembly of an AAPS system to ensure that it functions correctly in everyday life. - -##### How to install AAPS - -This section is the manual for building the AAPS. Strict adherence to the step-by-step instructions are required in order to successfully build the AAPS. Please take your time. - -##### [Component Setup](https://androidaps.readthedocs.io/en/latest/Configuration/BG-Source.html) - -This explains how to properly integrate each of the various different separate component parts into AAPS, as well as how to set them up to work as seamlessly as possible together. All components are listed under the separate sections: CGM/FGM, xDrip Settings, Pumps, Phones, Nightscout setup, and Smartwatches. The sensor (BG) values and control of the insulin pump are particularly important information to understand. - -##### Configuration - -This explains how to set and configure your ‘Profile’, ‘Insulin’, ‘BG Source’, ‘Pump’, ‘Sensitivity Detection’, ‘APS’, ‘Loop’, ‘Treatments’. - -##### AAPS Usage - -This section provides a breakdown of the features provided by AAPS. - -##### [General Hints](https://androidaps.readthedocs.io/en/latest/Usage/Timezone-traveling.html) - -Useful tricks on how to tackle looping issues such as time zones, and daylight saving (i.e. Spring Forward/ - Fall Back). - -##### [AAPS](https://androidaps.readthedocs.io/en/latest/Getting-Started/Screenshots.html) for Children - -This is designed for parents or caregivers who want to build an AAPS for their child. It also explains the extra features necessary in order to support and safely control your child’s AAPS remotely.

The concepts in this section should be fully understood in order to competently use this feature. - -##### Trikčių šalinimas - -This section contains links to help solve issues when building or using AAPS. - -##### FAQ - -This section addresses specific questions which tend to come up when building or using AAPS. - -##### [Terminų žodynas](https://androidaps.readthedocs.io/en/latest/Getting-Started/Glossary.html) - -This contains a list of the acronyms (or short-term names) or defined terms developed specifically for AAP (for instance, the terms ‘ISF’ or ‘TT’ have special meanings in AAPS). - -##### [Where to go for help](https://androidaps.readthedocs.io/en/latest/Where-To-Go-For-Help/Background-reading.html)? - -This section is aimed to provide new users with links on resources in order to get help including accessing community support made up of both new and experienced users who can clarify questions, and resolve the usual pitfalls that come with AAPS. - -##### For Clinicians - -This is a section for the clinicians who have expressed interest in open source artificial pancreas technology such as AAPS, or for patients who want to share such information with their clinicians. | - -## what are we going to build? - -### An Android Phone Application - -At the core, AAPS is an android application running from a phone. You are going to build it from scratch by installing tools to download the sourcecode and build the actual application. - -### A reporting server NightScout (or Tidepool) - -In order to fully use AAPS properly you will want to setup a nightscout server. It is used to collect data from AAPS over time and possibly communicate to the application. It is required for parents who want to oversee their children AAPS sessions. It is also key to share data between clinicians and patients to perform analysis over time. - -## How long will it take? - -## Who might AAPS not be suitable for? - -## Where can I get help? - -## Requirements - -### medical - -### technical - -### personal - -### CGMs - -### Insulin Pump - -### Reporting (NS, Tidepool) \ No newline at end of file diff --git a/docs/CROWDIN/nl/Configuration/Dexcom.md b/docs/CROWDIN/nl/Configuration/Dexcom.md deleted file mode 100644 index 06bfefd96679..000000000000 --- a/docs/CROWDIN/nl/Configuration/Dexcom.md +++ /dev/null @@ -1,32 +0,0 @@ -# Dexcom G6 - -## Algemeen - -* Volg de [Algemene CGM aanbevelingen](../Configuration/BG-Source#cgm-hygiene) -* [Speciale aanbevelingen voor Dexcom G6 en doe-het-zelf systemen](../Configuration/BG-Source#dexcom-g6-diy-systems) *Voor G6 zenders die na herfst/eind 2018 zijn geproduceerd, zorg dat je een van de nieuwste [ ‘nightly build’ xDrip+](https://github.com/NightscoutFoundation/xDrip/releases) versies hebt. Deze zenders hebben een nieuwe firmware en de nieuwste stabiele versie van xDrip+ (2019/01/10) werkt daar niet mee. - -## Sensor inbrengen - -Bij het inbrengen van de sensor wordt aanbevolen om niet te hard op de inserter te duwen om bloeden te voorkomen. De sensordraad zou niet in contact moeten komen met bloed. - -Na het inbrengen van de sensor moet de zender erop worden geklikt. Let op dat je eerst het rechte uiteinde erin klikt, en druk vervolgens op het ronde uiteinde. - -## Problemen oplossen - -### Verbindingsproblemen - -De Bluetooth-verbinding kan worden verstoord door andere Bluetooth-apparaten zoals bloedglucose meters, koptelefoons, tablets of keukenapparatuur zoals magnetrons (microgolven) of keramische kookplaten. In dat geval toont xDrip+ geen BG-waarden. Wanneer de Bluetooth-verbinding opnieuw is hersteld, worden de ontbrekende glucosegegevens aangevuld (met een maximum van 3 uur). - -### Sensor Fout - -Als je last hebt van terugkerende sensor fouten, kies dan een andere plaats op je lichaam om de sensor in te brengen. De sensordraad zou niet in contact moeten komen met bloed. - -Vaak kan een "Sensor fout" worden gecorrigeerd door te wachten en te zorgen dat er geen druk is op de sensor (bijvoorbeeld 's nachts er niet op gaan liggen). - -### 'Springende' waardes - -Wanneer jouw waardes alle kanten op springen, zou je kunnen proberen om de instellingen voor Noise Blocking in xDrip+ te wijzigen (Settings - Inter-App Settings - Noise Blocking) d.w.z. "Block Very High noise and worse". Zie ook [Filteren van glucosewaardes](../Usage/Smoothing-Blood-Glucose-Data-in-xDrip.md). - -### Nieuwe zender met lopende sensor - -Als je toevallig de zender wilt veranderen tijdens een lopende sensor sessie, dan kun je proberen de zender te verwijderen terwijl je de sensor gewoon laat zitten. Zie deze video . \ No newline at end of file diff --git a/docs/CROWDIN/nl/Configuration/EOFLOW.md b/docs/CROWDIN/nl/Configuration/EOFLOW.md deleted file mode 100644 index b8e999f00996..000000000000 --- a/docs/CROWDIN/nl/Configuration/EOFLOW.md +++ /dev/null @@ -1,155 +0,0 @@ -# EOPatch2 Instruction Manual - -The patch requires the use of rapid-acting U-100 type insulin, such as NovoRapid or Humalog. Use a rapid-acting insulin that is suitable for you according to your doctor’s prescription and inject the prescribed dosage. - -The smallest injectable dose of insulin when using the patch is 0.05 U. The Profile BAS should therefore be set at a minimum value of 0.05 U/hr or more and an interval of 0.05 U/hr, as otherwise there may be an error between the estimated total infusion amount in the Profile and the actual infusion amount in the patch. Likewise, the bolus must also be set and infused with a minimum infusion volume of 0.05 U. - -## Pump Setup -1. On the AndroidAPS home screen, click the hamburger menu in the upper left corner and go to Config Builder. -1. Select 'EOPatch2' in the Pump section. -1. Press the Back key to return to the home screen. - -![Bild1](../../images/EOPatch/Bild1.png) ![Bild2](../../images/EOPatch/Bild2.png) - -## Verdere instellingen -Select EOPATCH2 at the top of the home screen to go to the EOPATCH2 tab. - -Select the EOPatch2 Preferences menu by clicking the three dots in the upper right corner. - -The EOPatch2 Preferences menu offers a menu to set 3 types of notifications. - -### Low reservoir Alerts -A warning appears when the amount of insulin remaining in the reservoir reaches the set value or less while using the patch. It can be set from 10 to 50U in 5U increments. - -### Patch expiration Reminder -This is a reminder to notify you of the time remaining before the current patch expires. It can be set from 1 to 24 hours in 1 hour increments. The initial setting value is 4 hours. - -### Patch buzzer Reminder -This is a reminder function for injections other than basal injection. If you are using an (extended) bolus injection or a temporary basal injection, the patch will make a buzzer sound when the injection starts and when the injection is complete. The initial setting value is Off. - -![Bild3](../../images/EOPatch/Bild3.png) - -## Connecting the Patch - -### Move to patch connection screen - -Select EOPATCH2 at the top of the home screen and click the ACTIVATE PATCH button at the bottom left. - -![Bild4](../../images/EOPatch/Bild4.png) - -### Connecting the patch -Insert the syringe needle into the insulin inlet on the patch and then slowly push the piston to inject the insulin. When insulin is filled with more than 80U, the patch makes a booting sound (1 buzzer) and boots. After confirming the buzzer sound, click the START PAIRING button on the screen. - -[Warning] - -- Do not turn the needle action lever until instructed. It can cause serious problems during injection or safety checks otherwise. -- The amount of insulin that can be injected into the patch is 80~200U. If you inject less than 80U into the patch initially, the patch will not work. -- Take the insulin to be put into the patch from the refrigerator and leave it at room temperature for 15 to 30 minutes beforehand. The temperature of the insulin to be injected must be at least 10°C. - -![Bild5](../../images/EOPatch/Bild5.png) - -### patch pairing -The Patch pairing screen will be displayed, and pairing will be attempted automatically. If communication is successful, the Bluetooth pairing request notification appears. Click OK and when the Bluetooth pairing request notification appears a second time with the authentication code, select OK again. - -[Warning] - -- For pairing, the patch and the smartphone must be located within 30 cm of each other. -- After the patch booting is completed, the patch will beep every 3 minutes until the pairing is complete. -- After booting the patch, the patch application must be completed via the app within 60 minutes. If the application cannot be completed within 60 minutes, the patch should be discarded. - -![Bild6](../../images/EOPatch/Bild6.png) ![Bild7](../../images/EOPatch/Bild7.png) ![Bild8](../../images/EOPatch/Bild8.png) - - -### patch preparation -After removing the adhesive tape of the patch, check if the needle is sticking out. If there are no problems with the patch, click NEXT. - -![Bild9](../../images/EOPatch/Bild9.png) - -### Patch attachment -Insulin should be injected in a spot with subcutaneous fat but few nerves or blood vessels, so it is recommended to use the abdomen, arm, or thigh for the patch attachment site. Choose a patch attachment site and apply the patch after disinfecting the location. - -[Warning] - -- Make sure to straighten the side of the patch tape attached to the body evenly, so that the patch adheres completely to the skin. -- If the patch does not stick completely, air may enter between the patch and the skin, which can weaken the adhesive strength and waterproof effect of the patch. - -![Bild10](../../images/EOPatch/Bild10.png) - -### Safety Check -When patching is complete, touch Start Safety Check. When the safety check is completed, the patch will beep once. - -[Warning] - -- For safe use, do not turn the needle action lever until the safety check has been completed. - -![Bild11](../../images/EOPatch/Bild11.png) ![Bild12](../../images/EOPatch/Bild12.png) - - -### Inserting the needle -The needle is inserted by holding around the patch and turning the needle action lever more than 100° in the upward direction of the lever. There is a buzzer sound when the needle is inserted correctly. Turn the needle action lever further clockwise to release the lever. Click NEXT. - -[Caution] - -- If you go to the next step without the buzzer sounding, a needle insertion error warning will appear. - -## Discarding the patch -Patches must be replaced in the case of low insulin levels, usage expiration, and defects. The recommended usage period for each patch is 84 hours after booting the patch. - -### Discarding the patch -Select EOPATCH2 at the top of the home screen and click the DISCARD/CHANGE PATCH button at the bottom. On the next screen, click the DISCARD PATCH button. A dialog box appears to confirm once more and if you select the DISCARD PATCH button, the disposal is completed. - -![Bild13](../../images/EOPatch/Bild13.png) ![Bild14](../../images/EOPatch/Bild14.png) ![Bild15](../../images/EOPatch/Bild15.png) ![Bild16](../../images/EOPatch/Bild16.png) - -## Suspending and Resuming Insulin Delivery -Suspending insulin delivery also cancels both extended bolus and temporary basal. When resuming insulin delivery, the canceled extended bolus and temporary basal will not be resumed. And when insulin delivery is suspended, the patch will give a sound every 15 minutes. - -### Suspending insulin delivery -Select EOPATCH2 at the top of the home screen and click the SUSPEND button at the bottom right. When you select CONFIRM in the confirmation box, a time selection box appears. If you select the CONFIRM button after selecting the time, the insulin delivery will be suspended for the set amount of time. - -![Bild17](../../images/EOPatch/Bild17.png) ![Bild18](../../images/EOPatch/Bild18.png) ![Bild19](../../images/EOPatch/Bild19.png) - - -### Resuming insulin delivery -Select EOPATCH2 at the top of the home screen and click the RESUME button at the bottom right. Insulin delivery will resume by selecting CONFIRM in the confirmation dialog box. - -![Bild20](../../images/EOPatch/Bild20.png) ![Bild21](../../images/EOPatch/Bild21.png) - -## Alarms/Warnings - -### Alarm - -Alarms are issued for emergency situations of the highest priority and require immediate action. The alarm signal does not disappear or time out until it is acknowledged. An alarm occurs when there is a problem with the patch being used, so there may be cases where the patch in use needs to be discarded and replaced with a new patch. The warning is displayed as a dialog box and switching to another screen is not possible until processing is completed. - -![Bild22](../../images/EOPatch/Bild22.png) ![Bild23](../../images/EOPatch/Bild23.png) - -The different types of alarms are explained below. - -| Alarms | Explanation | -| -------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| Empty reservoir | Occurs when the patch’s reservoir runs out of insulin. | -| Patch expired | Occurs when the patch usage time has expired, and no further insulin injections are possible. | -| Occlusion | Occurs when it appears that the patch's insulin inlet is clogged. | -| Power on self-test failure | Occurs when the patch finds an unexpected error during the post-boot self-test process. | -| Inappropriate temperature | Occurs when the patch is outside the normal operating temperature range during patch application and use. To deal with this alarm, move the patch to an appropriate operating temperature (4.4 to 37°C) condition. | -| Needle insertion Error | Occurs when needle insertion is not normal during the patch application process. Check that the needle insertion edge of the patch and the needle activation button are in a straight line. | -| Patch battery Error | Occurs just before the patch’s internal battery runs out and powers off. | -| Patch activation Error | Occurs when the app fails to complete the patching process within 60 minutes after the patch is booted. | -| Patch Error | Occurs when the patch encounters an unexpected error while applying and using the patch. | - -### Warning - -A warning occurs in a medium or low-priority situation. When a warning occurs, it is displayed as a notification in the Overview screen. - -![Bild24](../../images/EOPatch/Bild24.png) - -The different types of warnings are explained below. - -| Warnings | Explanation | -| ---------------------------- | ------------------------------------------------------------------------------------------------------------------------------------- | -| End of insulin suspend | Occurs when the time set by the user has elapsed after the insulin infusion suspension has been completed. | -| Low reservoir | Occurs when the remaining amount of insulin in the patch is below the set amount. | -| Patch operating life expired | Occurs when the patch usage period is over. | -| Patch will expire soon | Occurs 1 hour before the patch must be discarded. | -| Incomplete Patch activation | Occurs when more than 3 minutes have elapsed due to an interruption during patch application in the stage after pairing is completed. | -| Patch battery low | Occurs when the patch's battery is low. | - diff --git a/docs/CROWDIN/nl/Configuration/Hardware/index.md b/docs/CROWDIN/nl/Configuration/Hardware/index.md deleted file mode 100644 index 2efefb13d331..000000000000 --- a/docs/CROWDIN/nl/Configuration/Hardware/index.md +++ /dev/null @@ -1,27 +0,0 @@ -# Hardware-Configuration - -## AndroidAPS instellingen - -## BG bron - -- [BG Source](../BG-Source.md) -- [xDrip+ Settings](../xDrip.md) -- [Dexcom G6 hints](../Dexcom.md) -- [Smoothing blood glucose data](../../Usage/Smoothing-Blood-Glucose-Data-in-xDrip.md) - -## Pumps - -- [Dana-R pump](../DanaR-Insulin-Pump.md) -- [Dana-RS pump](../DanaRS-Insulin-Pump.md) -- [Accu-Chek Combo pump](../Accu-Chek-Combo-Pump.md) -- [Accu-Chek Insight pump](../Accu-Chek-Insight-Pump.md) -- [Medtronic pump](../MedtronicPump.md) - -## Telefoons - -- [Jelly Pro Settings](../../Usage/jelly.md) -- [Huawei Settings](../../Usage/huawei.md) - -## Smartwatch - -- [Watchfaces](../Watchfaces.md) diff --git a/docs/CROWDIN/nl/Getting-Started/ClosedLoop.md b/docs/CROWDIN/nl/Getting-Started/ClosedLoop.md deleted file mode 100644 index 971355a0d3ae..000000000000 --- a/docs/CROWDIN/nl/Getting-Started/ClosedLoop.md +++ /dev/null @@ -1,55 +0,0 @@ -# Wat is een closed loop systeem? - -![AAPS is als een automatische piloot](../images/autopilot.png) - -Een closed loop systeem combineert verschillende onderdelen om zo de zorg voor jouw diabetes makkelijker te maken. In haar boek [Automated Insulin Delivery](https://www.artificialpancreasbook.com/) noemt Dana M. Lewis, een van de grondleggers van de open-source-beweging, een ["automatische piloot voor je diabetes"](https://www.artificialpancreasbook.com/3.-getting-started-with-your-aps). Maar wat betekent dat? - -**De automatische piloot in een vliegtuig** - -De automatische piloot doet niet al het werk, hij zorgt er niet voor dat een piloot de gehele vlucht kan gaan zitten slapen. Het vergemakkelijkt wel het werk van de piloten. Het neemt hen de taak van het voortdurend besturen van het vliegtuig, uit handen. Hierdoor kan de piloot zijn aandacht richten op het in de gaten houden van het luchtruim en het aansturen van de automatische piloot. - -De automatische piloot ontvangt signalen van verschillende sensoren, een computer vergelijkt die signalen met de instructies van de piloot en maakt dan de noodzakelijke aanpassingen. De piloot hoeft zich geen zorgen meer te maken over voortdurende kleine aanpassingen. - -**Closed Loop Systeem** - -Hetzelfde geldt voor een closed loop systeem. Het doet niet al het werk, je moet nog steeds aandacht aan je diabetes geven. Een closed loop systeem combineert de sensorgegevens van een CGM/FGM met jouw instellingen voor diabetesregulatie, zoals basaal, insulinegevoeligheidsfactor en koolhydraat ratio. Hieruit berekent het systeem behandelsuggesties en voert het voortdurende kleine aanpassingen uit om jouw bloedsuikers binnen jouw streefwaardes te houden en jou op die manier te ontzorgen. Hierdoor hou je tijd en energie over voor je leven 'naast' diabetes. - -Net zoals je niet wilt vliegen in een vliegtuig waar alleen de automatische piloot vliegt zonder menselijk toezicht, helpt een closed loop systeem je met diabetes management, maar heeft het altijd jouw input nodig! ** Zelfs met een closed loop systeem kun je je diabetes niet gewoon 'vergeten'! ** - -Net zoals de automatische piloot afhankelijk is van de sensorwaarden en de aansturing van de piloot, heeft een closed loop goede invoer nodig, zoals CGM/FGM waardes, basaalwaardes, ISF en koolhydraat ratio om jou succesvol te ondersteunen. - -## Open Source Closed Loop Systemen - -Op dit moment zijn er drie grote open-source closed loop systemen beschikbaar: - -### AndroidAPS (AAPS) - -AAPS is described in detail in [this documentation](./WhatisAndroidAPS.html). Alle berekeningen en bediening gaan via een Android smartphone. Ook ontvangt de smartphone jouw sensorgegevens en stuurt deze jouw insulinepomp aan. Er is een sterke samenhang en samenwerking met OpenAPS (dezelfde algoritmes voor berekeningen worden gebruikt). - -Compatibele [pompen](../Hardware/pumps.md) zijn: - -- [DanaR](../Configuration/DanaR-Insulin-Pump.md) / [DanaRS & Dana-i](../Configuration/DanaRS-Insulin-Pump.html) -- [Accu-Chek Combo](../Configuration/Accu-Chek-Combo-Pump.md) -- [Accu-Chek Insight](../Configuration/Accu-Chek-Insight-Pump.md) -- [Diaconn G8](../Configuration/DiaconnG8.md) -- [Omnipod DASH](../Configuration/OmnipodDASH.md) -- [Omnipod Eros](../Configuration/OmnipodEros.md) -- bepaalde oudere modellen [Medtronic pompen](../Configuration/MedtronicPump.md) - -### OpenAPS - -[OpenAPS](https://openaps.readthedocs.io) was het eerste Open Source Closed Loop systeem. Het maakt gebruik van een kleine computer zoals Raspberry Pi of Intel Edison. - -Te gebruiken pompen zijn: - -- bepaalde oudere modellen Medtronic pompen - -### Loop voor iOS - -[Loop voor iOS ](https://loopkit.github.io/loopdocs/) is het Open Source Closed Loop Systeem dat te gebruiken is met Apple iPhones. - -Te gebruiken pompen zijn: - -- Omnipod DASH -- Omnipod Eros -- bepaalde oudere modellen Medtronic pompen diff --git a/docs/CROWDIN/nl/Getting-Started/GlossaryTest.md b/docs/CROWDIN/nl/Getting-Started/GlossaryTest.md deleted file mode 100644 index 7830fcb0c1e7..000000000000 --- a/docs/CROWDIN/nl/Getting-Started/GlossaryTest.md +++ /dev/null @@ -1,391 +0,0 @@ -# Veelgebruikte woordenlijst - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
TermBeschrijvingzie ookmeer details
AAPSAndroidAPS - kunstmatig alvleesklier systeem (Artificial Pancreas System) dat werkt op Android telefoons  
AMAAdvanced Meal Assist - gevorderd algoritme om koolhydraatconsumptie op te vangenMA / SMBWiki - AMA
Android autotoont AAPS meldingen op het dashboard van je auto (wanneer dat hiervoor geschikt is) Wiki - android auto
APKsoftware-installatiebestand van de app (staat voor 'Android application package') Wiki - Bouwen van de app
Autosensberekent veranderingen aan jouw insuline gevoeligheid veroorzaakt door sporten, hormonen, etc. DIABETTECH - Autosens (Engelstalig)
AzureWebsite waar je jouw Nightscout-gegevens kunt opslaan (gegevens hosting in de cloud)Heroku / NightscoutAzure
BATstatusindicator batterij niveau op OverzichtsschermCAN / RES / SENInstellingen
Screenshots
BGbloed glucose  
BGIBloed Glucose Interactie -te verwachten BG stijging of daling, alleen op basis van de insuline activiteit  
BG bronWaar komen je glucosewaardes vandaan?CGM / FSLWiki - BG bron
Blukon Nightreaderbluetooth-zender om Freestyle Libre als CGM te gebruikenBlueReader / MiaoMiaoAmbrosia Blukon Nightreader
BRbasaalstand  
CAGEcanula age - displayed in Nightscout if information was entered in actions tab / menu tab or through AAPS actions tab 'prime'Nightscout 
CANstatus light overdue canula change on homescreenBAT / RES / SENInstellingen
Screenshots
CGMcontinuous glucose monitor  
Closed loopclosed-loop systems make automatic adjustments to basal delivery, without needing user-approval, based on an algorithmOpen loopWiki closed loop
COBcarbs on board  
DIAduration of insulin action Wiki insulin types
DIABETTECH - DIA
DSTdaylight savings time Wiki DST
eCarbs"extended carbs" - carbs split up over serveral hours (i.e. lot of fat/protein)
extended boluses you might know from regular pump therapy do not make much sense when looping		SMBWiki - eCarbs
eCarbs use case
FGMflash glucose monitor (Freestyle Libre) Wiki - BG bron
gitversion-control system for tracking changes in computer files and coordinating work on those files
-> neccessary for APK updates		 Wiki - update APK
Githubweb-based hosting service for version control using Git
-> storage of source code		 Github AndroidAPS
Glimpapp to collect values from Freestyle Libre Nightscout with Glimp
HerokuWebsite waar je jouw Nightscout-gegevens kunt opslaan (gegevens hosting in de cloud)Azure / NightscoutHeroku
IC (or I:C)insulin to carb ratio (How many carbs are covered by one unit of insulin?)  
IOBinsulin on board - insulin active in your body  
ISFinsulin sensitivity factor - the expected decrease in BG as a result of one unit of insulin  
LGSLow Glucose Suspend
AAPS will reduce basal if blood glucose is dropping. But if blood glucose is rising then it will only increase basal if the IOB is negative (from a previous LGS), otherwise basal rates will remain the same as your selected profile. You may temporarily experience spikes following treated hypos without the ability to increase basal on the rebound.		objective 6 
LineageOSfree and open-source operating system for smartphones etc.
alternative OS for smartphones not running Android 8.1 (Oreo)
(when using Accu-Chek Combo)		 Wiki - Combo pump
Log filesrecord of all AAPS actions (useful for trubbleshooting and debugging) Wiki - log files
maxIOBsafety feature - maximum total IOB AAPS can't go over Wiki - maxIOB
Wiki - SMB
MiaoMiaobluetooth-zender om Freestyle Libre als CGM te gebruikenBlueReader / Blukon NightreaderMiaoMiao
min_5m_carbimpactsaftey feature - default carb decay at times when carb absorption can’t be dynamically worked out based on your bloods reactions Wiki - config builder
Nightscoutopen source project to access and report CGM dataNightscout ReporterNightscout
NS Clientpart of AAPS to connect to your Nightscout site Wiki - NS Client
Nightscout ReporterTool from fellow looper to generate PDFs reports from Nightscout dataNightscoutNightscout Reporter
NS Reporter @ Facebook
Doelenlearning program within AAPS guiding you step by step from open to closed loop Wiki - objectives
OpenAPSopen artificial pancreas system
APS run on small computers (i.e. Raspberry Pie)
AAPS uses some of the OpenAPS features		 OpenAPS docs
Open loopsystem will suggest recommended adjustments which have to be performed manually on the pumpClosed loopWiki - config builder
Oref0 / Oref1sensitivity detection
"reference design implementation version 0/1" - the key algorithm behind OpenAPS		 Wiki - sensitivity detection
Peak timetime of maximum effect of insulin given Wiki - config builder
PHpump history (entry in treatments tab) Screenshots
Voorspellingslijnenpreditions for BG in the future based on different calculations Wiki - predition lines
Profielbasic treatment settings (basal rate, DIA, IC, ISF, BG target)
can be defined locally or through Nightscout		NightscoutWiki - profile
Profiel wissel(temporary) change of profile used or percentual increase/decrease Wiki - profile switch
RESstatus light overdue reservoir change on homescreenBAT / CAN / SENInstellingen
Screenshots
RileyLinkopen source hardware device to bridge Bluetooth Low Energy (BLE) to 916MHz wireless communication (used for old Medtronic pumps)OpenAPS 
SAGEsensor age - displayed in Nightscout if information was entered in the actions tab / menuNightscout 
SENstatus light sensor change on homescreenBAT / CAN / RESInstellingen
Screenshots
Sensivity detectionberekent veranderingen aan jouw insuline gevoeligheid veroorzaakt door sporten, hormonen, etc. DIABETTECH - Autosens (Engelstalig)
Sensor noiseunstable CGM readings leading to "jumping" values Wiki - sensor noise
SMBsuper micro bolus
advanced feature for faster BG adjustment		UAMWiki - SMB
Super bolusshift of basal to bolus insulin for faster BG adjustment John Walsh - The Super Bolus
TBBtotal base basal (sum of basal rate within 24 hours)  
TBRtemporary basal rate  
TDDtotal daily dose (bolus + basal per day)  
TTtemporary target
temporary increase/decrease of BG target (range)		 Wiki - temp targets
UAMunannounced meals - detection of significant increase in glucose levels due to meals, adrenaline or other influences and attempt to adjust this with SMBSMBWiki - SMB
Virtual pumpoption to try AAPS functions or for PWD using a pump model with no AndroidAPS driver for loopingOpen loop 
AchtergrondAndroidAPS background imagesee phones page
xDrip / xDrip+open source software to read CGM systems xDrip+
xDrip
Zero-temptemporary basal rate with 0% (no basal insulin delivery)  
See also https://openaps.readthedocs.io/en/latest/docs/Resources/glossary.html
diff --git a/docs/CROWDIN/nl/Getting-Started/Safety-first.md b/docs/CROWDIN/nl/Getting-Started/Safety-first.md deleted file mode 100644 index b4422bee0654..000000000000 --- a/docs/CROWDIN/nl/Getting-Started/Safety-first.md +++ /dev/null @@ -1,41 +0,0 @@ -# Allereerst de veiligheid - -**When you decide to build your own artificial pancreas, it's always important to think about security and safety, and to understand the impact of all your actions** - -## General - -- AAPS is a just a tool to help you manage diabetes, it is not a fully automated system you can install and forget! -- Do not assume that AAPS will never make mistakes. Dit systeem krijgt uiteindelijk de controle over jouw insuline toediening: kijk ernaar, leer hoe het systeem werkt en 'denkt'. En zorg dat je begrijpt hoe je zijn keuzes moet interpreteren. -- Remember that, once paired, the phone can instruct the pump to do anything. Only use this phone for AAPS and, if being used by a child, essential communications. Installeer geen onnodige apps of spelletjes (!!!) die malware zouden kunnen bevatten zoals trojans, virussen of bots die je systeem zouden kunnen verstoren. -- Install all security updates provided by your phone manufacturer and Google. -- You might also need to change your diabetes habits as you change your therapy by using a closed loop system. Bijv. some people report, they need less hypo treatments as AAPS has already reduced insulin. - -## SMS Communicator - -- AAPS allows you to control a child's phone remotely via text message. Bedenk wel, dat de telefoon die is ingesteld om externe commando's te geven, kan worden gestolen. Beveilig die telefoon dus goed, met op z'n minst een pincode. -- AAPS will also inform you by text message if your remote commands, such as a bolus or a profile change, have been carried out. Het wordt aangeraden om ten minste 2 telefoonnummers te koppelen in de SMS communicator instellingen. Mocht één van de gekoppelde telefoons worden gestolen, dan zul je deze bevestigings-SMS'jes evengoed nog op het tweede telefoonnummer binnenkrijgen. - -(Safety-first-aaps-can-also-be-used-by-blind-people)= -## AAPS can also be used by blind people - -On Android devices TalkBack is part of the operating system. It is a program for screen orientation via voice output. With TalkBack you can operate your smartphone as well as AAPS blind. - -We users create the AAPS app ourselves with Android Studio. Many use Microsoft Windows for this purpose, where there is the Screenreader analogous to TalkBack. Since Android Studio is a Java application, the "Java Access Bridge" component must be enabled in the Control Panel. Otherwise, the screen reader of the PC will not speak in Android Studio. - -To do this, please proceed as follows: - -- Press WINDOWSTASTE and enter "Control Panel" in the search field, open with Enter. It opens: "All Control Panel Items". -- Press the letter C to get to "Center for Ease of Use", open with Enter. -- Then open "Use computer without a screen" with Enter. -- There, at the bottom, you will find the checkbox "Enable Java Access Bridge", select it. -- Done, just close the window! The screen reader should work now. - -```{note} -**IMPORTANT SAFETY NOTICE** - -The foundation of AAPS safety features discussed in this documentation is built on the safety features of the hardware used to build your system. Het is daarom van cruciaal belang dat je alleen een volledig functionerende FDA of CE goedgekeurde insulinepomp en CGM gebruikt voor het bouwen van jouw eigen closed loop. Gebruik alleen insulinepompen en CGMs die in deze handleiding beschreven staan, waarvoor de AndroidAPS software is geschreven en getest. Hardware of software wijzigingen aan deze componenten kunnen voor onverwachte uitkomsten zorgen (denk aan het ongewenst afgeven van insuline), waardoor de gebruiker een aanzienlijk risico loopt. If you find or get offered broken, modified or self-made insulin pumps or CGM receivers, *do not use* these for creating an AAPS system. - -Daarnaast is het belangrijk om alleen originele verbruiksartikelen te gebruiken, zoals infuussets, inschiethulpen en reservoirs die door de fabrikant zijn goedgekeurd voor gebruik met jouw pomp of CGM. Door het gebruik van niet-originele, niet-geteste verbruiksmaterialen kunnen CGM metingen onnauwkeurig worden en/of fouten optreden in de insulinedosering. Insuline is zeer gevaarlijk wanneer het verkeerd wordt gedoseerd - speel alstublieft niet met je leven door jouw hulpmiddelen aan te passen. - -Tensotte een belangrijke opmerking: je mag géén SGLT-2 inhibitors (glifozines) gebruiken wanneer je loopt. Omdat deze medicatie ook de bloedsuiker verlaagt. Deze medicatie in combinatie met een systeem dat de basale insuline verlaagt om BG te verhogen is bijzonder gevaarlijk, omdat deze stijging in BG mogelijk niet zal gebeuren en daardoor een gevaarlijk gebrek aan insuline kan ontstaan. -``` diff --git a/docs/CROWDIN/nl/Getting-Started/Sample-Setup.md b/docs/CROWDIN/nl/Getting-Started/Sample-Setup.md deleted file mode 100644 index f670fde006d6..000000000000 --- a/docs/CROWDIN/nl/Getting-Started/Sample-Setup.md +++ /dev/null @@ -1,151 +0,0 @@ -# Gebruiksvoorbeeld: Samsung S7, DanaRS, Dexcom G6 en Sony Smartwatch - -![Gebruiksvoorbeeld](../images/SampleSetup.png) - -## Beschrijving - -In dit voorbeeld is de Samsung Galaxy S7 het centrale onderdeel van de closed loop. Een aangepaste versie van de Dexcom App leest glucose waarden van de Dexcom G6 CGM. AndroidAPS wordt gebruikt om een DanaR insulinepomp (van de Koreaanse fabrikant SOOIL) aan te sturen via Bluetooth. Dit is alles wat nodig is om de closed loop te kunnen draaien. - -Omdat de Dexcom App beperkte alarm opties heeft, wordt in dit voorbeeld ook de opensource-app xDrip+ gebruikt. Hierin worden naast de normale hoog / laag alarmen ook extra alarmen ingesteld, volgens individuele wensen van de gebruiker. - -Optioneel kan een Android Wear-smartwatch jouw glucose- en AndroidAPS gegevens weergeven. In dit voorbeeld wordt de Sony Smartwatch 3 (SWR50) gebruikt. De smartwatch kan ook worden gebruikt om opdrachten te geven aan AndroidAPS (zoals bolussen voor een maaltijd). - -Het systeem werkt offline. Dit betekent dat de smartphone geen internetverbinding nodig heeft om de loop te laten werken. - -Wat wel is ingesteld in dit voorbeeld, is dat alle gegevens automatisch worden geupload naar Nightscout "in de cloud" wanneer de smartphone is verbonden met internet. Met Nightscout kun je alle gegevens terugkijken, en ook uitgebreide rapporten uitdraaien voor doktersbezoeken. Of actuele gegevens delen met anderen (handig voor ouders die real time willen meekijken met de closed loop van hun kind). Het is ook mogelijk om het uploaden van gegevens naar Nightscout alleen te laten gebeuren wanneer je smartphone een Wifi-verbinding heeft. Zo kun je besparen op data- en accuverbruik. Dit is een oplossing als je geen familieleden hebt die real time willen meekijken, maar als je wel gegevens wil terugkijken en rapportages in Nightscout wilt gebruiken. - -## Benodigdheden - -1. Samsung Galaxy S7 - - * Andere telefoons: zie [lijst van geteste telefoons en horloges](https://docs.google.com/spreadsheets/d/1gZAsN6f0gv6tkgy9EBsYl0BQNhna0RDqA9QGycAqCQc/edit) voor AndroidAPS - -2. [DanaRS](http://www.sooil.com/eng/product/) - - * Alternatieven: - * [Accu-Chek Combo](../Configuration/Accu-Chek-Combo-Pump.md) - * [Accu-Chek Insight](../Configuration/Accu-Chek-Insight-Pump.md) - * [DanaR](../Configuration/DanaR-Insulin-Pump.md) - * [Bepaalde oude modellen Medtronic pompen (extra nodig: RileyLink/Gnarl hardware, Android telefoon met Bluetooth Low Energy/BLE-chipset)](../Configuration/MedtronicPump.md) - * In de toekomst kunnen andere pompen ook beschikbaar komen, zie de lijst met [mogelijk toekomstige insulinepompen](Future-possible-Pump-Drivers.md). - -3. [Dexcom G6](https://dexcom.com) - - * Alternatives: see list of possible [BG sources](../Configuration/BG-Source.md) - -4. Optioneel: Sony Smartwatch 3 (SWR50) - - * Alternatieven: Alle [horloges met Google Wear OS](https://wearos.google.com/intl/de_de/#find-your-watch) zouden prima moeten werken, voor details zie [lijst van geteste telefoons en horloges](https://docs.google.com/spreadsheets/d/1gZAsN6f0gv6tkgy9EBsYl0BQNhna0RDqA9QGycAqCQc/edit) voor AndroidAPS (OS moet Android Wear zijn) - -## Nightscout instellen - -Zie details onder [Nightscout instellen](../Installing-AndroidAPS/Nightscout.md) - -## Computer: Android Studio installeren - -De broncode van AAPS is vrij beschikbaar voor iedereen (ook wel 'opensource' genoemd). Om de app te kunnen bouwen vanuit de broncode, heb je Android Studio nodig op jouw computer, dit kan een Windows, Mac of Linux computer zijn. Zie de pagina met gedetailleerde instructies voor het [bouwen van de app](../Installing-AndroidAPS/Building-APK.md). - -Het installeren van Android Studio kost wat tijd, wacht geduldig af terwijl de software de nodige updates downloadt. - -## Smartphone instellen - -![Smartphone](../images/SampleSetupSmartphone.png) - -### Smartphone firmware controleren - -* Menu > instellingen > telefoon info > software info: ten minste "Android-versie 8.0" (getest tot Android versie 8.0.0 Oreo - Samsung Experience versie 9.0) -* Voor de firmware-update: menu > instellingen > software-update - -### Toestaan dat apps uit onbekende bronnen worden geïnstalleerd - -Menu > instellingen > apparaat beveiliging > onbekende bronnen > schuifregelaar naar rechts (= actief) - -Om veiligheidsredenen moet je deze instelling weer terug op inactief zetten zodra je de installatie van alle apps die hier beschreven staan hebt afgerond. - -### Bluetooth inschakelen - -1. Menu > instellingen > verbindingen > Bluetooth > schuifregelaar naar rechts (= actief) -2. Menu > instellingen > verbindingen > locatie > schuifregelaar naar rechts (= actief) - -Locatieservices (GPS) moet worden geactiveerd om Bluetooth goed te laten werken. - -### Installeren van Dexcom App (aangepaste versie) - -![Aangepaste Dexcom app](../images/SampleSetupDexApp.png) - -De officiële Dexcom app uit de Google Play Store werkt niet omdat die geen glucosewaardes naar andere apps kan doorsturen. Daarom is er door mensen uit de doe-het-zelf looping community een aangepaste versie gemaakt. Deze aangepaste Dexcom app kan wel glucosewaardes naar AAPS sturen. Een ander voordeel is dat deze app met alle Android telefoons gebruikt kan worden, ook met telefoons die niet op de [Dexcom compatibiliteitslijst](https://www.dexcom.com/dexcom-international-compatibility) staan. - -To do this perform the following steps on your smartphone: - -1. Als je op dit moment de originele Dexcom app op je telefoon hebt: - * Sensor stoppen - * App deinstalleren onder menu > instellingen > apps > Dexcom G6 Mobile > verwijderen -2. Download and install the [BYODA Dexcom ap](../Hardware/DexcomG6.md#if-using-g6-with-build-your-own-dexcom-app) -3. Start modified Dexcom G6 app, activate/calibrate the sensor according to the given instructions and wait until the warm-up phase is finished. -4. Once the modified Dexcom app shows actual glucose value, setup the warnings (hamburger menu on top left side of the screen) as follows: - * Urgent low `55mg/dl` / `3.1mmol/l` (cannot be disabled) - * Low `OFF` - * High `OFF` - * Rise rate `OFF` - * Fall rate `OFF` - * Signal loss `OFF` - -## AndroidAPS installeren - -1. Follow the instructions to [build the APK](../Installing-AndroidAPS/Building-APK.md#generate-signed-apk) -2. [Transfer](../Installing-AndroidAPS/Building-APK.md#transfer-apk-to-smartphone) the generated APK to your phone -3. [AndroidAPS instellen](../Configuration/Config-Builder.md) met de setup wizard of handmatig -4. In dit voorbeeld gebruikten we (o.a.) - -* BG source: `Dexcom G6 App (patched)` -- click cock-wheel and activate `Upload BG data to NS` and `Send BG data to xDrip+` (see [BG source](../Configuration/BG-Source.md)) - -![G5 Settings](../images/SampleSetupG5Settings.png) - -* NS Client activated (see [Nightscout setup](../Installing-AndroidAPS/Nightscout.md)) - -## xDrip+ installeren - -xDrip+ is another mature open source app that offers countless possibilities. In this setup, contrary to what the developers first wrote the app for, xDrip+ is not used to collect glucose data from the Dexcom G6, but only to output alarms and to display the current glucose value including the curve on the Android home screen in the widget. With xDrip+ the alarms can be set much more individually than with the Dexcom software, AAPS or Nightscout (no limitation in the selection of sounds, different alarms depending on day/night time etc.). - -1. Download de laatste stabiele versie van de xDrip+ app door deze link te openen op jouw smartphone - niet de versie van de Google Play Store! -2. Installeer xDrip+ door te tikken op het gedownloade APK-bestand. -3. Start xDrip+ en open naar het menu (= klik op de drie streepjes linksboven). Stel de volgende dingen in: - * Instellingen > Alarmen en waarschuwingen > Glucoseniveau Alert Lijst > stel nu de alerts in (hoog en laag) naar jouw voorkeuren. - * Bestaande alarmen kunnen worden gewijzigd door een lange druk op het alarm. - * Instellingen > Alarmen en waarschuwingen > Calibratie alerts: UIT (omdat calibraties in ons voorbeeld via de aangepaste Dexcom app zullen gaan) - * Instellingen > Hardware Data Source > 640G/EverSense - * Instellingen > Inter-app settings > Accepteren Calibraties > `AAN` - * Menu > Start Sensor (is alleen voor de vorm en heeft niets te maken met de G6 zelf. Dit is nodig omdat je anders steeds een foutmelding krijgt). - -For more information about xDrip+, see here [BG source page](../Configuration/BG-Source.md). - -### Voorbeeld van alarm instellingen - -The "Urgent low alarm" (below 55 mg/dl resp. 3,1 mmol) is a standard alarm from the modified Dexcom app that cannot be disabled. - -![xDrip alarms](../images/SampleSetupxDripWarning.png) - -Tip for meetings / church visits / cinema etc..: - -If "Do not disturb" mode is activated in the Samsung Galaxy S7 (Menu > Settings > Sounds and vibration > Do not disturb: slider to right side (= active)), the phone only vibrates during urgent low alarm and does not issue an acoustic warning. For the other alarms set up via xDrip+ you can select whether the silent mode should be ignored (acoustic sound played) or not. - -## Accubesparing uitschakelen - -On your Samsung Galaxy S7 go to Menu > Settings > Device Maintenance > Battery > Unmonitored Apps > + Add apps: Select the apps AndroidAPS, Dexcom G6 Mobile, xDrip+ and Android Wear (if smartwatch is used) one after the other - -## Optioneel: Sony Smartwatch 3 (SWR50) instellen - -With an Android Wear smartwatch life with diabetes can be made even more inconspicuous. The watch can be used to display the current glucose level, the status of the loop etc. on the wrist. De smartwatch kan ook worden gebruikt om opdrachten te geven aan AndroidAPS (zoals bolussen voor een maaltijd). To do this, double tap the CGM value of the AAPSv2 watchface. The SWR50 usually runs for a full day until the battery needs to be recharged (same charger as the Samsung Galaxy S7: microUSB). - -![Smartwatch](../images/SampleSetupSmartwatch.png) - -Details about the information displayed on the watchface can be found [here](../Configuration/Watchfaces.md). - -* Installeer de app "Android Wear" op jouw smartphone via de Google Play Store en maak connectie met de smartwatch volgens de instructies die daar staan. -* Kies in het AAPS menu op je telefoon > Config Builder > Algemeen (aan de onderkant van de lijst) > Wear > activeren aan linker kant, klik op wiel-icoon aan rechter kant > Wear instellingen en activeer `besturingselementen van Watch` -* Op je smartwatch: druk lang op het display om jouw watchface te veranderen en selecteer `AAPSv2` -* Indien nodig beide apparaten opnieuw opstarten. - -## Pomp instellen - -see [Dana RS pump](../Configuration/DanaRS-Insulin-Pump.md) \ No newline at end of file diff --git a/docs/CROWDIN/nl/Getting-Started/WhatisAndroidAPS.md b/docs/CROWDIN/nl/Getting-Started/WhatisAndroidAPS.md deleted file mode 100644 index dc3899236ef8..000000000000 --- a/docs/CROWDIN/nl/Getting-Started/WhatisAndroidAPS.md +++ /dev/null @@ -1,39 +0,0 @@ -# What is a closed loop system with AAPS? - -AAPS is an app that acts as an artificial pancreas system (APS) on an Android smartphone. en heeft hetzelfde doel als een menselijke alvleesklier: de bloedglucosewaardes automatisch binnen gezonde grenzen houden. - -AndroidAPS kan dit nooit zo perfect als een echte alvleesklier, maar kan het leven met type 1 diabetes wel makkelijker maken. Door apparaten die commercieel beschikbaar zijn, te koppelen aan software die simpel en veilig is. Those devices include a continuous glucose monitor (CGM) to tell AAPS about your blood sugar levels and an insulin pump which AAPS controls to deliver appropriate doses of insulin. De app communiceert met de glucosesensor en insulinepomp via bluetooth. AndroidAPS gebruikt een algoritme (een set rekenregels) dat al eerder is ontwikkeld voor een ander 'kunstmatige alvleesklier' systeem: OpenAPS. Wereldwijd heeft OpenAPS duizenden gebruikers en al die mensen samen hebben inmiddels miljoenen uren ervaring met dat systeem. - -A note of caution: AAPS is not regulated by any medical authority in any country. Using AAPS is essentially carrying out a medical experiment on yourself. Het bouwen en instellen van het systeem vereist doorzettingsvermogen en technische kennis. Je hoeft deze technische kennis aan het begin nog niet te hebben, je zult die gaandeweg krijgen. Alle informatie die je nodig hebt kun je online vinden: hier in de wiki, op andere websites of van mensen de jou zijn voorgegaan -- je kunt ze vinden in Facebook groepen en andere online platforms. Many people have successfully built AAPS and are now using it entirely safely, but it is essential that every user: - -- Builds the system themselves so that they thoroughly understand how it works -- Adjusts its individual dosage algorithm with his or her diabetes team to work nearly perfect -- Maintains and monitors the system to ensure it is working properly - -```{note} -**Disclaimer and Warning** - -- All information, thought, and code described here is intended for informational and educational purposes only. Nightscout probeert zich op geen enkele wijze te houden aan gegevensbewaking van medische gegevens. Use Nightscout and AAPS at your own risk, and do not use the information or code to make medical decisions. -- Use of code from github.com is without warranty or formal support of any kind. Verdere details zijn te vinden in de licentie, die te vinden is in de Repository op github. -- All product and company names, trademarks, servicemarks, registered trademarks, and registered servicemarks are the property of their respective holders. Hun gebruik is voor informatieve doeleinden en impliceert op geen enkele wijze een samenwerking met of goedkeuring van hen. - -Please note - this project has no association with and is not endorsed by: [SOOIL](http://www.sooil.com/eng/), [Dexcom](https://www.dexcom.com/), [Accu-Chek, Roche Diabetes Care](https://www.accu-chek.com/), [Insulet](https://www.insulet.com/) or [Medtronic](https://www.medtronic.com/). -``` - -Als je klaar bent voor deze uitdaging, lees dan verder. - -## Primary goals behind AAPS - -- An app with safety built in. To read about the safety features of the algorithms, known as oref0 and oref1, click here () -- An all-in-one app for managing type 1 diabetes with an artificial pancreas and Nightscout -- An app to which users can easily add or remove modules as needed -- An app with different versions for specific locations and languages. -- An app which can be used in open- and closed-loop mode -- An app that is totally transparent: users can input parameters, see results, and make the final decision -- An app which is independent of particular pump drivers and contains a "virtual pump" so users can safely experiment before using it on themselves -- An app closely integrated with Nightscout -- An app in which the user is in control of safety constraints - -## Hoe te beginnen - -Natuurlijk is alles wat hier beschreven staat belangrijk, maar de grote hoeveelheid nieuwe informatie kan in het begin behoorlijk verwarrend zijn. A good orientation is given by the [Module Overview](../Module/module.md) and the [Objectives](../Usage/Objectives.html). diff --git a/docs/CROWDIN/nl/Hardware/DexcomG4.md b/docs/CROWDIN/nl/Hardware/DexcomG4.md deleted file mode 100644 index 96ed4e1da162..000000000000 --- a/docs/CROWDIN/nl/Hardware/DexcomG4.md +++ /dev/null @@ -1,6 +0,0 @@ -# Dexcom G4 - -## Bij gebruik van G4 met OTG-kabel ('traditioneel' Nightscout) -- If not already set up then download Nightscout Uploader app from the Play Store and follow instructions on [Nightscout](https://nightscout.github.io/). -- In AAPS Preferences enter your Nightscout website and API secret. -- Select NSClient in ConfigBuilder (setting in AAPS). diff --git a/docs/CROWDIN/nl/Hardware/Smartwatch.md b/docs/CROWDIN/nl/Hardware/Smartwatch.md deleted file mode 100644 index 5f53324ab822..000000000000 --- a/docs/CROWDIN/nl/Hardware/Smartwatch.md +++ /dev/null @@ -1,10 +0,0 @@ -# Smartwatch - -Het gebruik van een smartwatch is optioneel, kies voor jezelf of jij het handig vindt. More details are here: - -- [List of tested phones and smartwatches](../Getting-Started/Phones.md) -- [Watchfaces Wear OS](../Configuration/Watchfaces.md) -- [Troubleshooting Sony Smartwatch SW 3](../Usage/SonySW3.md) - -## Instructions for Building the AAPS Wear APK for Wear OS -https://androidaps.readthedocs.io/en/latest/remote-control.html#building-the-aaps-wear-apk diff --git a/docs/CROWDIN/nl/Installing-AndroidAPS/Building-APK.md b/docs/CROWDIN/nl/Installing-AndroidAPS/Building-APK.md deleted file mode 100644 index fed7fda1ac82..000000000000 --- a/docs/CROWDIN/nl/Installing-AndroidAPS/Building-APK.md +++ /dev/null @@ -1,369 +0,0 @@ -# Bouwen van de app - -## Zelf bouwen, in plaats van downloaden - -**AAPS is not available as download due to regulation for medical devices. It is legal to build the app for your own use, but you must not give a copy to others! Zie de [Veelgestelde vragen](../Getting-Started/FAQ.md) pagina voor meer informatie.** - -## Belangrijk: - -* Please use **[Android Studio Giraffe" (2022.3.1)](https://developer.android.com/studio/)** or newer to build the apk. -* [Windows 32-bit systems](troubleshooting_androidstudio-unable-to-start-daemon-process) are not supported by Android Studio - -(Building-APK-recommended-specification-of-computer-for-building-apk-file)= - -## Recommended specification of computer for building apk file - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
OS (Only 64 bit)Windows 8 or higherMac OS 10.14 or higherAny Linux supports Gnome, KDE, or Unity DE;  GNU C Library 2.31 or later

CPU (Only 64 bit)

x86_64 CPU architecture; 2nd generation Intel Core or newer, or AMD CPU with support for a
Windows Hypervisor		ARM-based chips, or 2nd generation Intel Core or newer with support for
Hypervisor.Framework		x86_64 CPU architecture; 2nd generation Intel Core or newer, or AMD processor with support for AMD Virtualization (AMD-V) and SSSE3

RAM

8GB or more

Disk

At least 30GB free space. SSD is recommended.

Resolution

1280 x 800 Minimum

Internet

Broadband

- -Please keep in mind that both **64 bit CPU and 64 bit OS are mandatory condition.** If your system DOES NOT meet this condition, you have to change affected hardware or software or the whole system. **It is strongly recommended to use SSD (Solid State Disk) instead of HDD (Hard Disk Drive) because it will take less time when you are building the APS installation apk file.** Recommended is just recommended and it is not a mandatory. However, you may still use a HDD when you are building apk file but note that the building process can take a long time to complete, although once started, you can leave it running unattended. - -* * * - -### Dit artikel is verdeeld in twee delen. - -* In the overview part there is an explanation on what steps are necessary to build the APK file. -* In the step by step walkthrough part you will find the screenshots of a concrete installation. Because the versions of Android Studio - the software development environment which we will use to build the APK - will change very quickly this will be not identical to your installation but it should give you a good starting point. Android Studio also runs on Windows, Mac OS X and Linux and there might be small differences in some aspects between each platform. If you find that something important is wrong or missing, please inform the facebook group "AAPS users" or in the Discord chat [Android APS](https://discord.gg/4fQUWHZ4Mw) so that we can have a look at this. - -## Overzicht - -In general, the steps necessary to build the APK file: - -1. [Git installeren](../Installing-AndroidAPS/git-install.md) -2. [Installeer Git + Android Studio](Building-APK-install-android-studio) -3. [Stel git path in Android Studio in](Building-APK-set-git-path-in-preferences) -4. [Download AAPS code](Building-APK-download-AAPS-code) -5. [Android SDK downloaden](Building-APK-download-android-sdk) -6. [Build the app](Building-APK-generate-signed-apk) (generate signed apk) -7. [Apk-bestand overzetten naar je telefoon](Building-APK-transfer-apk-to-smartphone) -8. [Identify receiver (identificeer ontvanger) bij gebruik van xDrip+](xdrip-identify-receiver) - -## Step by step walkthrough - -Detailed description of the steps necessary to build the APK file. - -## Installeer Git (als je dat nog niet hebt) - -Follow the manual on the [git installation page](../Installing-AndroidAPS/git-install.md). - -(Building-APK-install-android-studio)= - -## Installeer Git + Android Studio - -The following screenshots have been taken from Android Studio Version Arctic Fox | 2020.3.1. Screens can change in future versions of Android Studio. But you should be able to find your way through. [Help from the community](../Where-To-Go-For-Help/Connect-with-other-users.md) is provided. - -One of the most important things when installing Android Studio: **Be patient!** During installation and setup Android Studio is downloading a lot of stuff which will take its time. - -Download [Android Studio from here](https://developer.android.com/studio/install.html) and install it on your computer. - -On first start you will find the setup wizard: - -Select "Do not import settings" as you have not used it before. - -![Do not import settings](../images/studioSetup/01_ImportSettings.png) - -Decide whether you want to share data with Google or not. - -![Share data with Google](../images/studioSetup/02_DataSharing.png) - -On the following screen click "Next". - -![Welcome screen](../images/studioSetup/03_Welcome.png) - -Select "Standard" installation and click "Next". - -![Standard installation](../images/studioSetup/04_InstallType.png) - -Select the theme for the user interface you like. (In this manual we used "Light".) Then click "Next". - -> ***Note:*** This is just the color scheme. You can select whatever you like (i.e. "Darcula" for dark mode). This selection has no influence on building the APK but the following screenshots might look different. - -![UI color scheme](../images/studioSetup/05_UITheme.png) - -Click "Next" on the "Verify Settings" dialog. - -![Verify settings](../images/studioSetup/06_Overview.png) - -Click on all three license agreement parts and select "Agree". When you have agreed to all, the "Finish" button will be enabled and you can "Finish". - - ![Agree license agreements](../images/studioSetup/07_LicenseAgreement.png) - - -Wait while Android Studio downloads additional components and be patient. Once everything is downloaded button "Finish" turns blue. Click the button now. - -![Downloading components](../images/studioSetup/08_Downloading.png) - -(Building-APK-download-AAPS-code)= - -## Download AAPS code - -* On the Android Studio welcome screen select "Projects" (1) on the left and then "Get from VCS" (2). - - ![Android Studio wizard](../images/studioSetup/20_ProjectVCS.png) - - * If you already opened Android Studio and do not see the welcome screen anymore select File (1) > New (2) > Project from Version Control... (3) - - ![Check out project from version control within Android Studio](../images/AndroidStudio_FileNew.PNG) - - * We will now tell Android Studio were to get the code from: - - * Make sure you have selected "Repository URL" on the left (1). - - * Check if "Git" is selected as version control (2). - * Copy and paste the URL ```https://github.com/nightscout/AndroidAPS``` to the main AAPS repository into the URL textbox (3). - * Choose the directory where you want to save the cloned code (4). - - ![Clone Git](../images/studioSetup/21_CloneURL.png) - -* Click button "Clone" (5). - - ![Clone repository](../images/studioSetup/22_Cloning.png) - -* Do not click "Background" while repository is cloned! - -* After the repository is cloned successfully, Android Studio will open the cloned project. - -* You will be asked whether you want to trust the project. Click on "Trust project"! - - ![Trust project](../images/studioSetup/23_TrustProject.png) - -* In the status bar at the bottom you will see the information that Android Studio is running background tasks. - - ![Background tasks](../images/studioSetup/24_GradleSyncRunning.png) - -* Windows only: Grant access if your firewall is asking for permission. - - ![Firewall permission java](../images/AndroidStudio361_18.png) - -* Once the background tasks are finished you will probably see an error saying that errors occurred (1) or (2) or (3). - - ![SDK licence](../images/studioSetup/25_SyncFailed.png) - - Don't worry, this will be solved soon! - -(Building-APK-set-git-path-in-preferences)= - -## Set git path in preferences - -Make sure [git is installed](../Installing-AndroidAPS/git-install.md) on your computer and you have restarted your computer since installing. - -On the Android Studio welcome screen click "Customize" (1) on the left and then select the link "All settings..." (2): - -![Android Studio settings from welcome screen](../images/studioSetup/10_WizardSettings.png) - -### Windows - -* As windows user, make sure you have restarted your computer after [installing Git](../Installing-AndroidAPS/git-install.md). - -* In the menu, go to File (1) > Settings (2) (or Android Studio > Preferences on Mac). - - ![Open settings](../images/studioSetup/30_Settings.png) - -* Double-click "Version Control" (1) to open the sub-menu. - -* Click Git (2). -* Make sure update method "Merge" (3) is selected. -* Check if Android Studio can locate path to git.exe automatically by clicking the button "Test" (4). - - ![Android Studio settings](../images/studioSetup/11_GitPath.png) - -* If automatic setting is successful git version will be displayed next to the path. - - ![Git version displayed](../images/studioSetup/12_GitVersion.png) - -* Eventually git.exe cannot be found automatically or the Test will result in an error (1): - - ![Git not found](../images/studioSetup/13_GitVersionError.png) - - In this case click on the folder icon (2). - -* Use [search function](https://www.tenforums.com/tutorials/94452-search-file-explorer-windows-10-a.html) in windows explorer to find "git.exe" if you are unsure where git has been installed. You are looking for a file named "git.exe", located in **\bin** folder. - -* Select path to git.exe and make sure you selected the one in ** \bin\ ** folder (3) and click "OK" (4). - - ![Select git manually](../images/studioSetup/14_GitManualSelection.png) - -* Check your selected git path again with the "Test" button as described above. - -* When the git version is displayed next to the path (see screenshot above), close settings window by clicking "OK" button (5). - -### Mac - -* Any git version should work. For example . -* Use homebrew to install git: ```$ brew install git```. -* For details on installing git see the [official git documentation](https://git-scm.com/book/en/v2/Getting-Started-Installing-Git). -* If you install git via homebrew there is no need to change any preferences. Just in case: They can be found here: Android Studio - Preferences. - -(Building-APK-download-android-sdk)= - -## Android SDK downloaden - -* In the menu, go to File (1) > Settings (2) (or Android Studio > Preferences on Mac). - - ![Open settings](../images/studioSetup/30_Settings.png) - -* Double-click on Languages & Frameworks to open its submenu (1). - -* Select Android SDK (2). -* Tick the box left of "Android 9.0 (Pie)" (3) (API Level 28). - - ![SDK settings](../images/studioSetup/31_AndroidSDK.png) - -* Confirm changes by clicking OK. - - ![Confirm SDK changes](../images/studioSetup/32_ConfirmSDK.png) - -* Wait until the SDK download and installation is finished. - - ![Wait during SDK installation](../images/studioSetup/34_DownloadSDK.png) - -* When SDK installation is completed the "Finish" button will turn blue. Click this button. - - ![Finish SDK installation](../images/studioSetup/35_DownloadSDKfinished.png) - -* Android Studio might recommend to update the gradle system. **Never update gradle!** This will lead to difficulties! - -* If you see an information on the lower right side of your Android Studio window that Android Gradle Plugin is ready to update click on the text "upgrade" (1). - - ![No gradle update](../images/studioSetup/36_GradleUpdateRequest.png) - -* In the dialog box the select "Don't remind me again for this project" (2). - - ![No gradle update](../images/studioSetup/37_GradleUpdateDeny.png) - -* Restart Android Studio before you continue. - -(Building-APK-generate-signed-apk)= - -## Bouwen van de ondertekende APK - -Signing means that you indicate your app to be your own creation but in a digital way as a kind of digital fingerprint within the app itself. That is necessary because Android has a rule that it only accepts signed code to run for security reasons. For more information on this topic, follow [this link](https://developer.android.com/studio/publish/app-signing.html#generate-key). - -* After Android Studio is started, wait until all background tasks are finished. - - ![Wait for background tasks](../images/studioSetup/40_BackgroundTasks.png) - - * ***Warning:*** If errors occur, do not continue with the following steps. \ Consult the [troubleshooting section](../Installing-AndroidAPS/troubleshooting_androidstudio) for known problems! - - ![Gradle Sync Error](../images/studioSetup/41_GradleSyncError.png) - -* Click "Build" (1) in the menu bar and select "Generate Signed Bundle / APK..." (2). - - ![Apk bouwen](../images/studioSetup/42_MenuBuild.png) - -* Select "APK" (1) instead of "Android App Bundle" and click "Next" (2). - - ![APK in plaats van bundel](../images/studioSetup/43_Apk.png) - -* Make sure that module is set to "AndroidAPS.app" (1). - -* Click "Create new..." (2) to start creating your key store. - - ***Note:*** A key store in this case is nothing more than a file in which the information for signing is stored. It is encrypted and the information is secured with passwords. - - ![Create key store](../images/studioSetup/44_KeystoreNew.png) - -* Click the folder symbol to select a path on your computer for your key store. - - ![Create key store](../images/studioSetup/45_KeystoreDialog.png) - -* Select the path where your key store shall be saved (1). - - ![Create key store](../images/studioSetup/46_KeystorePath.png) - - ***Warning: Do not save in same folder as project. You must use a different directory!*** A good location would be your home folder. - -* Type a file name for your key store (2) and confirm with "OK" (3). - -* Enter (2) and confirm (3) the password for your key store. ![Select key store path](../images/studioSetup/47_KeystoreDialog.png) - - ***Note:*** Passwords for key store and key do not have to be very sophisticated. Make sure to remember those or make a note in a safe place. In case you will not remember your passwords in the future, see [troubleshooting for lost key store](troubleshooting_androidstudio-lost-keystore). - -* Enter an alias (4) for your key. Choose whatever you like. - -* Enter (5) and confirm (6) the password for your key - -* Validity (7) is 25 years by default. You do not have to change the default value. - -* First and last name must be entered (8). All other information is optional. - -* Click "OK" (9) when you are done. - -* Make sure the box to remember passwords is checked (1). So you don't have to enter them again next time you build the apk (i.e. when updating to a new AAPS version). - -* Click "Next" (2). - - ![Remember passwords](../images/studioSetup/48_KeystoreSave.png) - -* Select build variant "fullRelease" (1) and press "Finish". - - ![Select build variant](../images/studioSetup/49_BuildVariant.png) - -* Android Studio will show "Gradle Build running" at the bottom. This takes some time, depending on your computer and internet connection. **Be patient!** - - ![Gradle Running](../images/studioSetup/50_GradleRunning.png) - -* Android Studio will display the information "Generate Signed APK" after build is finished. - - ![Build finished](../images/studioSetup/51_BuildFinished.png) - -* In case build was not successful refer to the [troubleshooting section](../Installing-AndroidAPS/troubleshooting_androidstudio). - -* Click on the notification to expand it. - -* Click on the link "locate". - - ![Locate build](../images/studioSetup/52_BuildLocate.png) - - * If the notification is gone, you can always open the "Event log" and select the same link there. ![Succesvol gebouwd - event log](../images/studioSetup/53_EventLog.png) - -* Your file manager/explorer will open. Navigate to the directory "full" (1) > "release" (2). - - ![Bestandslocatie apk](../images/studioSetup/54_APKlocation.png) - -* "app-full-release.apk" (3) is the file you are looking for! - -(Building-APK-transfer-apk-to-smartphone)= - -## Overzetten van de APK naar je telefoon - -Easiest way to transfer app-full-release.apk to your phone is via [USB cable or Google Drive](https://support.google.com/android/answer/9064445?hl=en). Please note that transfer by mail might cause difficulties and is not the preferred way. - -On your phone you have to allow installation from unknown sources. Manuals how to do this can be found on the internet (i.e. [here](https://www.expressvpn.com/de/support/vpn-setup/enable-apk-installs-android/) or [here](https://www.androidcentral.com/unknown-sources)). - -## Problemen oplossen - -See separate page [troubleshooting Android Studio](../Installing-AndroidAPS/troubleshooting_androidstudio). \ No newline at end of file diff --git a/docs/CROWDIN/nl/Resources/index.md b/docs/CROWDIN/nl/Resources/index.md deleted file mode 100644 index 67dbe22cd539..000000000000 --- a/docs/CROWDIN/nl/Resources/index.md +++ /dev/null @@ -1,8 +0,0 @@ -# Achtergrondinformatie - -```{toctree} -:glob: true -:maxdepth: 4 - -Voor zorgprofessionals -``` diff --git a/docs/CROWDIN/nl/Sandbox/sandbox2.md b/docs/CROWDIN/nl/Sandbox/sandbox2.md deleted file mode 100644 index 33c547956c89..000000000000 --- a/docs/CROWDIN/nl/Sandbox/sandbox2.md +++ /dev/null @@ -1,43 +0,0 @@ -# internal sandbox file 2 for testing - -```{admonition} no need to translate this -:class: note - -No need to translate this. -``` - -This is an internal sandbox file for the documentation team to test - -1. markdown syntax and - -1. background process for - 1. CROWDIN translation and - 2. Read The Docs deployment. - -You can dirctly jump from here to the first label in the sandbox1.md file - ["Jump"](sandbox1-this-is-a-test). - -You can dirctly jump from here to the second label in this file - ["Jump"](sandbox1-this-is-another-test). - -Here you can jump to the first sandbox file - ["Jump"](./sandbox1.md). - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -(sandbox2-this-is-a-test)= -## This is a test - -This is a test if labels must be unique. - -### This is spare information from the docs - -cut from index: - -There are "limits" set in place when you are first beginning your AAPS journey. These safety limits have been developed over many years by observations of the inadvertent mistakes that new users are most likely to make when first learning to set up, build, and then successfully loop with AAPS - as most often those mistakes occur simply because the user was so excited to get started using the system that they may have forgotten to sit down and dedicate the time needed to understand the information within this documentation thoroughly. - - -### spare info from the overview to put into "preparing" - -Since the requirements are very different from anything you might have set up in the past, we recommend that you really follow the instructions, step-by-step the first few times you build the app, so that you have a stronger sense of how the app building process is supposed to behave when all directions are followed exactly. Please remember to take your time. Later this will go very quickly when you build the app again for a new version. That way you will have a greater chance of noticing when something doesn't going as planned before too many steps are out of line. It is important to save the your keystore file (.jks file used to sign your app) in a safe place, so that you can always use that exact same keystore file and password each and every time you are asked to create a new updated version of AAPS, as this file is what makes sure that each new version of the app "remembers" all the information that you have provided to it in previous versions of the app and thus ensure that the updates will go as smoothly as possible. On average, you can assume that there will be one new version and 2-3 required updates per year. This number is based on experience and may change in the future. But we do want to at least give you a general guideline on what to expect. When you are more experienced at building updated AAPS app versions all the steps that are required in building an updated app will only take 15-30 minutes, on average. However, in the beginning there can be a rather steep learning curve as these steps are not always considered intuitive by new users! So do not get frustrated if you find that it takes half a day or a whole day with some help from the community before you are finally finished with the update process. If you find that you are getting very frustrated just take a short break, and oftentimes; after a stroll around the block or two...you'll find that you are better able to approach the problem again. diff --git a/docs/CROWDIN/nl/Usage/Objectives.md b/docs/CROWDIN/nl/Usage/Objectives.md deleted file mode 100644 index 7649d19ac7dc..000000000000 --- a/docs/CROWDIN/nl/Usage/Objectives.md +++ /dev/null @@ -1,184 +0,0 @@ -# Doelen - -AAPS has a series of Objectives that need to be completed to walk you through the features and settings of safe looping. De leerdoelen zorgen ervoor dat je alles goed hebt ingesteld, en dat je snapt wat het systeem doet en waarom. Zodat je erop kunt vertrouwen dat het de juiste keuzes maakt. - -If you are **upgrading phones** then you can [export your settings](../Usage/ExportImportSettings.md) to keep your progress through the objectives. Not only will your progress through the objectives be saved, but also your safety settings such as max bolus etc. If you do not export and import your settings then you will need to start the objectives from the beginning again. It is a good idea to [backup your settings](../Usage/ExportImportSettings.html) frequently just in case. - -If you want to go back in objectives see [explanation below](Objectives-go-back-in-objectives). - -## Doel 1: Instellen van visualisatie en monitoring en analyseren van basaal en ratio's - -- Select the right blood glucose source for your setup. See [BG Source](../Configuration/BG-Source.md) for more information. -- Select the right Pump in ConfigBuilder (select Virtual Pump if you are using a pump model with no AAPS driver for looping) to ensure your pump status can communicate with AAPS. -- If using DanaR pump then ensure you have followed [DanaR Insulin Pump](../Configuration/DanaR-Insulin-Pump.md) instructions to ensure the link between pump and AAPS. -- You need to establish a data repository/reporting platform to complete this objective. That can be accomplished with either Nightscout or Tidepool (or both). Follow instructions at the [Nightscout](../Installing-AndroidAPS/Nightscout.md) or [Tidepool](../Installing-AndroidAPS/Tidepool.md) page for instructions. -- Note that URL in NSClient must be **WITHOUT /api/v1/** at the end - see [NSClient settings in Preferences](Preferences-nsclient). - -*You may need to wait for the next blood glucose reading to arrive before AAPS will recognise it.* - -## Objective 2: Learn how to control AAPS - -- Perform several actions in AAPS as described in this objective. - -- Click on the orange text "Not completed yet" to access the to-dos. - -- Links will be provided to guide you in case you are not familiar with a specific action yet. - - ```{image} ../images/Objective2_V2_5.png - :alt: Screenshot doel 2 - ``` - -(Objectives-objective-3-prove-your-knowledge)= - -## Doel 3: Bewijs jouw kennis - -Objective 3 is a multiple choice test based on questions designed to test your theoretical knowledge of **AAPS**. - -Some users find Objective 3 to be the most difficult objective to complete. Please do read the AAPS documents in conjunction with the questions. If you are genuinely stuck after researching the **AAPS** documents, please search or ask for help on the Facebook or Discord group. These groups can provide friendly hints or redirect you to the relevant part of the **AAPS** documents. - -To proceed with Objective 3, click on the orange text “Not completed yet” to access the relevant question. Please read each question and select your answer(s). - - - -Within each question, a hyperlink to the **AAPS** documents will guide you to the relevant section of the document which you should read in order to locate the correct answer. - - -[Obj3_Screenshot 2023-12-05 223422](https://github.com/openaps/AndroidAPSdocs/assets/137224335/77347516-e24e-459d-98ab-acbb49a3d4e8)![image](https://github.com/openaps/AndroidAPSdocs/assets/137224335/ca756b8e-efbc-4427-b281-ac953ce16718) - - - -For each question, there may be more than one answer that is correct! If an incorrect answer is selected, the question will be time locked for a certain amount of time (60 minutes) before you can go back and answer the question. - - -After updating to a new version of **AAPS**, new questions may be added to cover a prevalent issue picked up by **AAPS** or alternatively to test your knowledge of a new feature of **AAPS** as released. - - -When **AAPS** is installed for the first time, you will have to complete Objective 3 entirely in order to move onto Objective 4. Each objective is required to be completed in sequential order. New features will gradually be unlocked as progress is made through the objectives. - -__What happens if new questions are added later to Objective 3?__ From time to time, new features are added to **AAPS** which may require a new question to be added to Objective 3. As a result, any new question added to Objective 3 will be marked as “incomplete” because **AAPS** will require you to action this. As each Objective is independent, you will not lose the existing functionality of **AAPS** providing the other objectives remain completed. - - -## Doel 4: Beginnen met een open loop - -- Select Open Loop either from Preferences, or by pressing and holding the Loop button in top left of the home screen. -- Work through the [Preferences](../Configuration/Preferences.md) to set up for you. -- Manually enact at least 20 of the temporary basal rate suggestions over a period of 7 days; input them to your pump and confirm in AAPS that you have accepted them. Ensure this data shows in AAPS and Nightscout. -- Enable [temp targets](../Usage/temptarget.md) if necessary. Gebruik bijvoorbeeld een tijdelijk hypo streefdoel om te voorkomen dat het systeem te sterk corrigeert voor een stijgende bloedsuiker na een hypo. - -### Verminder het aantal meldingen - -- To reduce the Number of decisions to be made while in Open Loop set wide target range like 90 - 150 mg/dl or 5,0 - 8,5 mmol/l. - -- You might even want to wider upper limit (or disable Open Loop) at night. - -- In Preferences you can set a minimum percentage for suggestion of basal rate change. - - ```{image} ../images/OpenLoop_MinimalRequestChange2.png - :alt: Open Loop Minimale verzoek voor aanpassing - ``` - -- Also, you do not need to act every 5 minutes on all suggestions... - -## Doel 5: De Open Loop begrijpen, inclusief de voorgestelde tijdelijke basaalstanden - -- Start to understand the thinking behind the temp basal recommendations by looking at the [determine basal logic](https://openaps.readthedocs.io/en/latest/docs/While%20You%20Wait%20For%20Gear/Understand-determine-basal.html) and both the [forecast line in AAPS homescreen](Screenshots-prediction-lines)/Nightscout and the summary of outputs from the calculations in your OpenAPS tab. - -Je wilt beginnen met een streefdoel dat hoger is dan normaal, totdat je vertrouwen in de berekeningen en de instellingen hebt gekregen. Het systeem staat toe - -- a low target to be a minimum of 4 mmol (72 mg/dl) or maximum of 10 mmol (180 mg/dl) -- a high target to be a minimum of 5 mmol (90 mg/dl) and maximum of 15 mmol (225 mg/dl) -- a temporary target as a single value can be anywhere in the range of 4 mmol to 15 mmol (72 mg/dl to 225 mg/dl) - -Het streefdoel is de waarde waar de berekeningen op zijn gebaseerd, en is niet hetzelfde als waar je jouw bloedglucose waarden binnen wilt houden. If your target is very wide (say, 3 or more mmol \[50 mg/dl or more\] wide), you will often find little AAPS action. Dit komt omdat de voorspelde bloedglucose meestal binnen dat brede bereik zal liggen en het systeem dus niet vaak een andere tijdelijk basaal voorstelt. - -You may want to experiment with adjusting your targets to be a closer together range (say, 1 or less mmol \[20 mg/dl or less\] wide) and observe how the behavior of your system changes as a result. - -You can view a wider range (green lines) on the graph for the values you aim to keep your blood glucose within by entering different values in [Preferences](../Configuration/Preferences.md) > Range for Visualisation. - -```{image} ../images/sign_stop.png -:alt: Stop-teken -``` - -### Stop hier als je een virtuele pomp gebruikt en in Open Loop wilt blijven - klik NIET op Verificatie aan het einde van dit doel. - -```{image} ../images/blank.png -:alt: blanco -``` - -(Objectives-objective-6-starting-to-close-the-loop-with-low-glucose-suspend)= -## Doel 6: Starten in Closed Loop met bescherming tegen lage BG - -```{image} ../images/sign_warning.png -:alt: Waarschuwings-teken -``` - -### Closed loop will not correct high BG values in objective 6 as it is limited to low glucose suspend. High BG values have to be corrected manually by you! - -- Prerequisite: You need a good profile (basal, ISF, IC) already working in AAPS to start with Loop in Low Glucose Suspend mode. Otherwise you can run in a hypo which you have to manually correct. This will help you a lot to avoid having to treat a low glucose over a period of 5 days. **If you are still having frequent or severe low glucose episodes then consider refining your DIA, basal, ISF and carb ratios and do NOT start objective 6 at this time.** -- You don't have to change your settings now. During objective 6, the maxIOB setting is internally set to zero automatically. **This override will be reversed when moving to objective 7.** -- The system will override your maxIOB settings to zero, which means if blood glucose is dropping it can reduce basal for you. If blood glucose is rising then it will only increase basal if the basal IOB is negative from a previous Low Glucose Suspend. Otherwise basal rates will remain the same as your selected profile. **That means that you have to manually handle high values with insulin corrections.** -- If your basal IOB is negative (see screenshot below) a TBR > 100% can be issued also in objective 6. - -```{image} ../images/Objective6_negIOB.png -:alt: Voorbeeld negatieve IOB -``` - -- Set your target range slightly higher than you usually aim for, just to be safe and have a bit more scurity buffer. -- Enable 'Low Glucose Suspend' mode either by by pressing and holding the Loop icon at the top right corner of the home screen and selecting the Loop - LGS mode icon. -- Watch how temporary basals are active by viewing the blue basal text on the homescreen or the blue basal render on the homescreen graph. -- You may temporarily experience spikes following treated hypos without the ability to increase basal on the rebound. - -(Objectives-objective-7-tuning-the-closed-loop-raising-max-iob-above-0-and-gradually-lowering-bg-targets)= -## Objective 7: Tuning the closed loop, raising maxIOB above 0 and gradually lowering BG targets - -- Select 'Closed Loop' either from [Preferences](../Configuration/Preferences.md) or by pressing and holding the Loop icon at the top right corner of the home screen, over a period of 1 day. - -- Raise your 'Maximum total IOB OpenAPS can’t go over' (in OpenAPS called 'max-iob') above 0. The default recommendation is "average mealbolus + 3x max daily basal" (for the SMB algorithm) or "3x max daily basal" (for the older AMA algorithm) but you should slowly work up to this until you know your settings work for you (max daily basal = the maximum hourly value in any time segment of the day). - - Deze aanbeveling moet als uitgangspunt worden beschouwd. If you set to the 3x and you are seeing moves that push you too hard and fast then lower that number. If you are very resistant, raise it very little at a time. - - ```{image} ../images/MaxDailyBasal2.png - :alt: max dagelijkse basaal - ``` - -- Once confident on how much IOB suits your looping patterns, then reduce your targets to your desired level. - -(Objectives-objective-8-adjust-basals-and-ratios-if-needed-and-then-enable-autosens)= -## Doel 8: Pas basaalstanden en de ratio's aan indien nodig, activeer hierna de Autosens optie - -- You can use [autotune](https://openaps.readthedocs.io/en/latest/docs/Customize-Iterate/autotune.html) as a one off to check your basals remain accurate or do a traditional basal test. -- Enable [autosens](../Usage/Open-APS-features.md) over a period of 7 days and watch the white line on the homescreen graph show how your sensitivity to insulin may be rising or falling as a result of exercise or hormones etc. and keep an eye in the OpenAPS report tab how AAPS is adjusting the basals and/or targets accordingly. - -*Don’t forget to record your looping in* [this form](https://bit.ly/nowlooping) *logging AAPS as your type of DIY loop software, if you have not already done so.* - -(Objectives-objective-9-enabling-additional-oref1-features-for-daytime-use-such-as-super-micro-bolus-smb)= -## Objective 9: Enabling additional oref1 features for daytime use, such as super micro bolus (SMB) - -- You must read the [SMB chapter in this wiki](Open-APS-features-super-micro-bolus-smb) and [chapter oref1 in openAPSdocs](https://openaps.readthedocs.io/en/latest/docs/Customize-Iterate/oref1.html) to understand how SMB works, especially what's the idea behind zero-temping. -- Then you ought to [rise maxIOB](Open-APS-features-maximum-total-iob-openaps-cant-go-over-openaps-max-iob) to get SMBs working fine. maxIOB bevat nu alle IOB, niet alleen de toegediende basale insuline. That is, if given a bolus of 8 U for a meal and maxIOB is 7 U, no SMBs will be delivered until IOB drops below 7 U. A good start is maxIOB = average mealbolus + 3x max daily basal (max daily basal = the maximum hourly value in any time segment of the day - see [objective 7](Objectives-objective-7-tuning-the-closed-loop-raising-max-iob-above-0-and-gradually-lowering-bg-targets) for an illustration) -- min_5m_carbimpact default in absorption settings has changed from 3 to 8 going from AMA to SMB. Je moet dit handmatig doen wanneer je van AMA naar SMB wisselt. - -(Objectives-objective-10-automation)= -## Objective 10: Automation - -- You have to start objective 10 to be able to use [Automation](../Usage/Automation.md). -- Make sure you have completed all objectives including exam [Objectives-objective-3-prove-your-knowledge](Objectives#objective-3-prove-your-knowledge). -- Completing previous objectives will not effect other objectives you have already finished. Je behoudt alle reeds afgeronde doelen! - -(Objectives-objective-11-DynamicISF)= -## Objective 11: Additional Features such as DynamicISF - -- You have to start objective 11 to be able to use [DynamicISF](../Usage/Open-APS-features.md) - -(Objectives-go-back-in-objectives)= -## Teruggaan in doelen - -Als je om welke reden dan ook terug wilt gaan in de leerdoelen druk dan op "voltooiing wissen". - -```{image} ../images/Objective_ClearFinished.png -:alt: Teruggaan in doelen -``` - -## Objectives in Android APS before version 3.0 - -One objective was removed when Android APS 3.0 was released. Users of Android APS version 2.8.2.1 who are on older Android software (i.e. earlier than version 9) will be using an older set of objectives which can be found [here](../Usage/Objectives_old.md). diff --git a/docs/CROWDIN/nl/Usage/Objectives_old.md b/docs/CROWDIN/nl/Usage/Objectives_old.md deleted file mode 100644 index e8992df31201..000000000000 --- a/docs/CROWDIN/nl/Usage/Objectives_old.md +++ /dev/null @@ -1,152 +0,0 @@ -# Objectives as of Android APS 2.8.2.1 - -This is not the latest version of the Android APS Objectives. This page details the Objectives that were in place prior to version 3.0. Anyone using an older version of Android (i.e. prior to Android 9) and Android APS version 2.8.2.1 should refer to this page. - -Please see [this page](../Usage/Objectives.md) for the current set of Objectives. - -AndroidAPS heeft een reeks leerdoelen die je moet doorlopen, zodat je alle opties en instellingen leert kennen om veilig te kunnen loopen. De leerdoelen zorgen ervoor dat je alles goed hebt ingesteld, en dat je snapt wat het systeem doet en waarom. Zodat je erop kunt vertrouwen dat het de juiste keuzes maakt. - -If you are **upgrading phones** then you can [export your settings](../Usage/ExportImportSettings.md) to keep your progress through the objectives. Not only will your progress through the objectives be saved, but also your safety settings such as max bolus etc. If you do not export and import your settings then you will need to start the objectives from the beginning again. It is a good idea to [backup your settings](../Usage/ExportImportSettings.html) frequently just in case. - -If you want to go back in objectives see [explanation below](../Usage/Objectives.md#go-back-in-objectives). - -## Doel 1: Instellen van visualisatie en monitoring en analyseren van basaal en ratio's - -- Select the right blood glucose source for your setup. See [BG Source](../Configuration/BG-Source.md) for more information. -- Select the right Pump in ConfigBuilder (select Virtual Pump if you are using a pump model with no AndroidAPS driver for looping) to ensure your pump status can communicate with AndroidAPS. -- If using DanaR pump then ensure you have followed [DanaR Insulin Pump](../Configuration/DanaR-Insulin-Pump.md) instructions to ensure the link between pump and AndroidAPS. -- Follow instructions in [Nightscout](../Installing-AndroidAPS/Nightscout.md) page to ensure Nightscout can receive and display this data. -- Note that URL in NSClient must be **WITHOUT /api/v1/** at the end - see [NSClient settings in Preferences](../Configuration/Preferences.md#nsclient). - -*You may need to wait for the next blood glucose reading to arrive before AndroidAPS will recognise it.* - -## Doel 2: Leer hoe AndroidAPS te gebruiken - -- Perform several actions in AndroidAPS as described in this objective. - -- Click on the orange text "Not completed yet" to access the to-dos. - -- Links will be provided to guide you in case you are not familiar with a specific action yet. - - ![Screenshot doel 2](../images/Objective2_V2_5.png) - -## Doel 3: Bewijs jouw kennis - -- Pass a multiple-choice exam testing your AndroidAPS knowledge. - -- Click on the orange text "Not completed yet" to access the page with the question and answering options. - - ![Screenshot doel 3](../images/Objective3_V2_5.png) - -- Links will be provided to guide you in case you are unsure about the correct answers yet. - -- The questions for objective 3 have been completely rewritten by native speakers as of AAPS 2.8. De vernieuwde vragen gaan grotendeels over dezelfde inhoud, en er zijn een paar nieuwe vragen toegevoegd. - -- These new questions will lead to some not answered questions even though you have successfully completed objective 3 in previous versions. - -- Unanswered questions will affect you only if you start a new objective. Voor mensen die in een vorige versie alle Doelen al hadden afgerond, geldt dat zij ruim de tijd hebben om deze nieuwe vragen te beantwoorden. Er worden bij hen geen AAPS-functies gedeactiveerd nu deze vragen nog openstaan. Het is wel verstandig om er binnenkort mee aan de slag te gaan; wanneer een volgende versie uitkomt, die wellicht nieuwe functies (en bijbehorende nieuwe Doelen) heeft, dan zou je niet aan een nieuw Doel kunnen beginnen totdat je alle vragen hebt beantwoord. - -## Doel 4: Beginnen met een open loop - -- Select Open Loop either from Preferences, or by pressing and holding the Loop button in top left of the home screen. -- Work through the [Preferences](../Configuration/Preferences.md) to set up for you. -- Manually enact at least 20 of the temporary basal rate suggestions over a period of 7 days; input them to your pump and confirm in AndroidAPS that you have accepted them. Controleer dat deze gegevens zichtbaar zijn in AndroidAPS en Nightscout. -- Enable [temp targets](../Usage/temptarget.md) if necessary. Gebruik bijvoorbeeld een tijdelijk hypo streefdoel om te voorkomen dat het systeem te sterk corrigeert voor een stijgende bloedsuiker na een hypo. - -### Verminder het aantal meldingen - -- To reduce the Number of decisions to be made while in Open Loop set wide target range like 90 - 150 mg/dl or 5,0 - 8,5 mmol/l. - -- You might even want to wider upper limit (or disable Open Loop) at night. - -- In Preferences you can set a minimum percentage for suggestion of basal rate change. - - ![Open Loop Minimale verzoek voor aanpassing](../images/OpenLoop_MinimalRequestChange2.png) - -- Also, you do not need to act every 5 minutes on all suggestions... - -## Doel 5: De Open Loop begrijpen, inclusief de voorgestelde tijdelijke basaalstanden - -- Start to understand the thinking behind the temp basal recommendations by looking at the [determine basal logic](https://openaps.readthedocs.io/en/latest/docs/While%20You%20Wait%20For%20Gear/Understand-determine-basal.html) and both the [forecast line in AndroidAPS homescreen](../Getting-Started/Screenshots.md#prediction-lines)/Nightscout and the summary of outputs from the calculations in your OpenAPS tab. - -Je wilt beginnen met een streefdoel dat hoger is dan normaal, totdat je vertrouwen in de berekeningen en de instellingen hebt gekregen. Het systeem staat toe - -- a low target to be a minimum of 4 mmol (72 mg/dl) or maximum of 10 mmol (180 mg/dl) -- a high target to be a minimum of 5 mmol (90 mg/dl) and maximum of 15 mmol (225 mg/dl) -- a temporary target as a single value can be anywhere in the range of 4 mmol to 15 mmol (72 mg/dl to 225 mg/dl) - -Het streefdoel is de waarde waar de berekeningen op zijn gebaseerd, en is niet hetzelfde als waar je jouw bloedglucose waarden binnen wilt houden. If your target is very wide (say, 3 or more mmol \[50 mg/dl or more\] wide), you will often find little AAPS action. Dit komt omdat de voorspelde bloedglucose meestal binnen dat brede bereik zal liggen en het systeem dus niet vaak een andere tijdelijk basaal voorstelt. - -You may want to experiment with adjusting your targets to be a closer together range (say, 1 or less mmol \[20 mg/dl or less\] wide) and observe how the behavior of your system changes as a result. - -You can view a wider range (green lines) on the graph for the values you aim to keep your blood glucose within by entering different values in [Preferences](../Configuration/Preferences.md) > Range for Visualisation. - -![Stop-teken](../images/sign_stop.png) - -### Stop hier als je een virtuele pomp gebruikt en in Open Loop wilt blijven - klik NIET op Verificatie aan het einde van dit doel. - -![blanco](../images/blank.png) - -## Doel 6: Starten in Closed Loop met bescherming tegen lage BG - -![Waarschuwings-teken](../images/sign_warning.png) - -### De closed loop zal hoge glucosewaarden in doel 6 niet naar beneden kunnen brengen, omdat in dit doel alleen nog de 'pompstop voor laag' functie geactiveerd is. Om hoge glucosewaarden naar beneden te krijgen, moet je zelf nog handmatig ingrijpen! - -- Select Closed Loop either from [Preferences](../Configuration/Preferences.md) or by pressing and holding the Open Loop button in the top left of the home screen. - -- Set your target range slightly higher than you usually aim for, just to be safe. - -- Watch how temporary basals are active by viewing the blue basal text on the homescreen or the blue basal render on the homescreen graph. - -- Ensure your settings have supported AndroidAPS to avoid having to treat a low glucose over a period of 5 days. Mocht je op dit moment nog veelvuldige of heftige lage glucosewaardes hebben, dan moet je waarschijnlijk nog iets verbeteren aan jouw instellingen van DIA, basaal, ISF of KH ratio (in die volgorde). - -- You don't have to change your settings. Tijdens doel 6 wordt de maxIOB automatisch door het systeem op nul gezet in de berekeningen. Deze beperking verdwijnt als je naar doel 7 gaat. - -- The system will override your maxIOB settings to zero, which means if blood glucose is dropping it can reduce basal for you, but if blood glucose is rising then it will only increase basal if the basal IOB is negative (from a previous Low Glucose Suspend), otherwise basal rates will remain the same as your selected profile. - - ![Voorbeeld negatieve IOB](../images/Objective6_negIOB.png) - -- If your basal IOB is negative (see screenshot above) a TBR > 100% can be issued also in objective 6. - -- You may temporarily experience spikes following treated hypos without the ability to increase basal on the rebound. - -## Doel 7: Inregelen van de closed loop, verhoog de max IOB boven 0 en laat geleidelijk de streef BG dalen - -- Raise your 'Maximum total IOB OpenAPS can’t go over' (in OpenAPS called 'max-iob') above 0 over a period of 1 day, the default recommendation is "average mealbolus + 3x max daily basal"(for SMB algorithm) or "3x max daily basal" (for older AMA algorithm) but you should slowly work up to this until you know your settings work for you (max daily basal = the maximum hourly value in any time segment of the day). - - Deze aanbeveling moet als uitgangspunt worden beschouwd. Als je op de 3x zit en je ziet dat het systeem de neiging heeft om jouw bloedglucose te laag uit te laten komen, pas dan deze instelling aan naar een lager getal. Als je zeer insulineresistent bent, pas dan deze instelling met kleine stapjes aan naar een hoger getal. - - ![max dagelijkse basaal](../images/MaxDailyBasal2.png) - -- Once confident on how much IOB suits your looping patterns then reduce your targets to your desired level. - -## Doel 8: Pas basaalstanden en de ratio's aan indien nodig, activeer hierna de Autosens optie - -- You can use [autotune](https://openaps.readthedocs.io/en/latest/docs/Customize-Iterate/autotune.html) as a one off to check your basals remain accurate or do a traditional basal test. -- Enable [autosens](../Usage/Open-APS-features.md) over a period of 7 days and watch the white line on the homescreen graph show how your sensitivity to insulin may be rising or falling as a result of exercise or hormones etc. and keep an eye in the OpenAPS report tab how AndroidAPS is adjusting the basals and/or targets accordingly. - -*Don’t forget to record your looping in* [this form](https://bit.ly/nowlooping) *logging AndroidAPS as your type of DIY loop software, if you have not already done so.* - -## Objective 9: Try additional features for daytime use and gain confidence in your closed loop system - -- Before AAPS version 2.7 meal assist (MA) was the basic algorithm for AAPS and completing objective 8 was necessary to activate [advanced meal assist (AMA)](../Usage/Open-APS-features.md#advanced-meal-assist-ama). -- As [advanced meal assist (AMA)](../Usage/Open-APS-features.md#advanced-meal-assist-ama) is the standard algorithm from AAPS version 2.7 onwards use the following 28 days to try features you haven't used yet and get more confident with you closed loop system. - -## Objective 10: Enabling additional oref1 features for daytime use, such as super micro bolus (SMB) - -- You must read the [SMB chapter in this wiki](../Usage/Open-APS-features.md#super-micro-bolus-smb) and [chapter oref1 in openAPSdocs](https://openaps.readthedocs.io/en/latest/docs/Customize-Iterate/oref1.html) to understand how SMB works, especially what's the idea behind zero-temping. -- Then you ought to [rise maxIOB](../Usage/Open-APS-features.md#maximum-total-iob-openaps-cant-go-over-openaps-max-iob) to get SMBs working fine. maxIOB bevat nu alle IOB, niet alleen de toegediende basale insuline. That is, if given a bolus of 8 U for a meal and maxIOB is 7 U, no SMBs will be delivered until IOB drops below 7 U. A good start is maxIOB = average mealbolus + 3x max daily basal (max daily basal = the maximum hourly value in any time segment of the day - see [objective 7](../Usage/Objectives#objective-7-tuning-the-closed-loop-raising-max-iob-above-0-and-gradually-lowering-bg-targets) for an illustration) -- min_5m_carbimpact default in absorption settings has changed from 3 to 8 going from AMA to SMB. Je moet dit handmatig doen wanneer je van AMA naar SMB wisselt. - -## Objective 11: Automation - -- You have to start objective 11 to be able to use [Automation](../Usage/Automation.md). -- Make sure you have completed all objectives including exam [../Usage/Objectives.md#objective-3-prove-your-knowledge](../Usage/Objectives#objective-3-prove-your-knowledge). -- Completing previous objectives will not effect other objectives you have already finished. Je behoudt alle reeds afgeronde doelen! - -## Teruggaan in doelen - -Als je om welke reden dan ook terug wilt gaan in de leerdoelen druk dan op "voltooiing wissen". - -![Teruggaan in doelen](../images/Objective_ClearFinished.png) diff --git a/docs/CROWDIN/nl/Usage/Smoothing-Blood-Glucose-Data-in-xDrip.md b/docs/CROWDIN/nl/Usage/Smoothing-Blood-Glucose-Data-in-xDrip.md deleted file mode 100644 index 5d0333d4fd3b..000000000000 --- a/docs/CROWDIN/nl/Usage/Smoothing-Blood-Glucose-Data-in-xDrip.md +++ /dev/null @@ -1,33 +0,0 @@ -(Smoothing-Blood-Glucose-Data-in-xDrip-smoothing-blood-glucose-data)= - -# Filteren van bloed glucose waardes - -If BG data is jumpy/noisy, AAPS may dose insulin incorrectly resulting in high or low BG. For this reason it’s important to disable the loop until the problem is resolved. Depending on your CGM such issues may be due to the CGM’s configuration or sensor problems/site issues. You may need to replace your CGM sensor to resolve this. - -Some CGM systems have internal algorithms to detect the noise level in the readings and AAPS can use this information to avoid giving SMBs if the BG data is too unreliable. However, some CGMs do not transmit this data and for these BG sources 'Enable SMB always' and 'Enable SMB after carbs' are disabled for safety reasons. - -## Dexcom sensors - -### Build Your Own Dexcom App - -When using [BYODA](DexcomG6-if-using-g6-with-build-your-own-dexcom-app) your BG data is smooth and consistent. Furthermore you can take advantage of Dexcom back-smoothing. There are no restrictions in using SMBs, because the noise-level data is shared with AAPS. - -### xDrip+ with Dexcom G6 or Dexcom ONE - -Noise-level data and smooth BG readings are only shared with AAPS if you use xDrip+ [native mode](https://navid200.github.io/xDrip/docs/Native-Algorithm). Using native mode, there are no restrictions in using SMBs. - -### Dexcom G6 or Dexcom ONE with xDrip+ Companion Mode - -The noise-level data is not shared with AAPS using this method. Therefore 'Enable SMB always' and 'Enable SMB after carbs' are disabled. - -## Freestyle Libre sensors - -### xDrip+ with FreeStyle Libre - -None of the FreeStyle Libre systems (FSL1, FSL2, or FSL3) broadcast any information about the level of noise detected in the readings, and therefore 'Enable SMB always' and 'Enable SMB after carbs' are disabled for all setups using the FreeStyle Libre. - -In addition, many people have reported the FreeStyle Libre often produces noisy data. In xDrip+ there are a few options to help with this: - -**Smooth Sensor Noise.** In xDrip+ Settings > xDrip+ Display Settings ensure that Smooth Sensor Noise is turned on. This attempts to apply smoothing to noisy data. - -**Smooth Sensor Noise (Ultrasensitive).** If you are still seeing noisy data in xDrip+ you can apply more aggressive smoothing using the Smooth Sensor Noise (Ultrasensitive) setting. This will attempt to apply smoothing even on very low levels of detected noise. To do this, first enable [engineering mode](Enabling-Engineering-Mode-in-xDrip.md) in xDrip+. Then navigate to Settings > xDrip+ Display Settings and turn on Smooth Sensor Noise (Ultrasensitive). \ No newline at end of file diff --git a/docs/CROWDIN/nl/Usage/autotune_b.md b/docs/CROWDIN/nl/Usage/autotune_b.md deleted file mode 100644 index 08e1c3afb594..000000000000 --- a/docs/CROWDIN/nl/Usage/autotune_b.md +++ /dev/null @@ -1,186 +0,0 @@ -# How to use Autotune plugin - -Documentation about Autotune algorythm can be found in [OpenAPS documentation](https://openaps.readthedocs.io/en/latest/docs/Customize-Iterate/autotune.html). - -Autotune plugin is an implementation of OpenAPS autotune algorythm within AAPS. - -**Currently Autotune Plugin is only available in dev branch with Engineering mode.** - -## Autotune user interface - -![Autotune default screen](../images/Autotune/Autotune_1b.png) - -- You can select in the Profile dropdown menu the input profile you want to tune (by default your current active profile is selected) - - Note: each time you select a new profile, previous results will be removed and Tune days parameter will be set to default value -- Then Tune days is to select the number of days used in calculation to tune your profile. The minimum value is 1 day and the maximum value 30 days. This number should not be too small to get correct iterative and smooth results (above 7 days for each calculation) - - Note: each time you change Tune days parameter, previous results will be removed -- Last Run il a link that recover your latest valid calculation. If you didn't launch Autotune on current day, or if previous results was removed with a modification of calculation parameter above, then you can recover parameters and results of the latest successfull run. -- Warning show you for example some information about selected profile (if you have several IC values or several ISF values) - - Note: Autotune calculation works with only a single IC and a single ISF value. There is currently no existing Autotune algorythm to tune a circadian IC or circadian ISF. If your input profile has several values, you can see in warning section the average value taken into account to tune your profile. -- Check Input Profile button open the Profile Viewer to allow you a quick verification of your profile (Units, DAI, IC, ISF, basal and target) - - Note: Autotune will only tune your IC (single value), ISF (single value) and basal (with circadian variation). Units, DAI and target will remain unchanged in output profile. - -- "Run Autotune" will launch Autotune calculation with selected profile and the number of Tune days - - Note: Autotune calculation can take a long time. Once launched, you can switch to another view (home, ...) and come back later in Autotune plugin to see results - -![Autotune Run start](../images/Autotune/Autotune_2b.png) - -- Then during the run you will see intermediate results below - - - Note: During run, settings are locked, so you cannot change anymore selected input profile or the number of day. You will have to wait the end of current calculation if you want to launch another run with other parameters. - - ![Autotune during run](../images/Autotune/Autotune_3b.png) - -- When Autotune calculation is finished, you will see the result (Tuned profile) and four buttons below. - -![Autotune Result](../images/Autotune/Autotune_4b.png) - -- It's important to always compare input profile (column "Profile"), output profile (column "Tuned") and the percentage of variation for each value (Column "%"). - -- For basal rates, you also have the number of "missing days". You have missing days when Autotune don't have enough data categorized as "Basal" to tune basal rate for this period (for example after each meal when you have carbs absorption). This number should be as low as possible especially when basal is important (for example during the night or at the end of the afternoon) - -- The "Compare profiles" button open the profile comparator view. Input profile is in blue, and output profile (named "Tuned") is in red. - - - Note: in the example below input profile has circadian variation for IC and ISF, but output calculated profile has a single value. If it's important for you to get a circadian output profile see [Circadian IC or ISF profile](#circadian-ic-or-isf-profile) below. - - ![Autotune Compare profiles](../images/Autotune/Autotune_5.png) - -- If you trust results (low percentage of variation between input profile and output profile), you can click on "Activate profile" button and then click on OK to validated. - - - Activate Tuned profile will automatically create a new profile "Tuned" in your Local profile plugin. - - If you already have a profile named "Tuned" in your local profile plugin, then this profile will be updated with calculated Autotune profile before the activation - - ![Autotune Activate profile](../images/Autotune/Autotune_6.png) - -- If you think Tuned profile must be adjusted (for example if you think some variation are too important), then you can click on "Copy to local profile" button - - - A new profile with the prefix "Tuned" and the date and time of the run will be created in local profile plugin - -![Autotune Copy to local profile](../images/Autotune/Autotune_7.png) - -- You can then select local profile to edit the Tuned profile (it will be selected by default when you open Local profile plugin) - - - the values in local profile will but rounded in the user interface to your pump capabilities - - ![Autotune local profile update](../images/Autotune/Autotune_8.png) - -- If you want to replace your input profile with Autotune result, click on "Update input profile" button and validate the Popup with OK - - - Note: if you click on "Activate profile" after "Update input profile", then you will activate your updated profile and not the default "Tuned" profile? - - ![Autotune Update input profile](../images/Autotune/Autotune_9.png) - -- If you have updated your input profile, then the "Update input profile" button is replaced by "Revert input profile" button (see screenshot below). You can that way immediatly see if your current input profile in Local profile plugin already include the result of last run or not. You also have the possibility to recover you input profile without autotune result with this button - - ![Autotune Update input profile](../images/Autotune/Autotune_10.png) - - - -## Autotune settings - -### Autotune plugin settings - -![Autotune default screen](../images/Autotune/Autotune_11.png) - -- Automation Switch Profile (default Off): see [Run Autotune with an automation rule](#run-autotune-with-an-automation-rule) below. If you change this setting to On, the input profile will automatically be updated by the Tuned profile, and it will be activated. - - **Be Carefull, you must trust and verified during several following days that after an update and activation of Tuned profile without modification, it improves your loop** - -- Categorize UAM as basal (default On): This setting is for the users using AndroidAPS without any carbs entered (Full UAM). It will prevent (when Off) to categorize UAM as basal. - - Note: if you have at least one hour of Carbs absorption detected during one day, then all data categorized as "UAM" will be categorized as basal, whatever this setting (On or Off) -- Number of days of data (default 5): You can define default value with this setting. Each time your select a new profile in Autotune plugin, Tune days parameter will be replaced by this default value -- Apply average result in circadian IC/ISF (default Off): see [Circadian IC or ISF profile](#circadian-ic-or-isf-profile) below. - -### Overige instellingen - -- Autotune also uses Max autosens ratio and Min autotsens ratio to limit variation. You can see and adjust these values in Config Builder > Sensitivity detection plugin > Settings > Advanced Settings - - ![Autotune default screen](../images/Autotune/Autotune_12.png) - - - -## Advanced feature - -### Circadian IC or ISF profile - -- If you have important variation of IC and/or you ISF in your profile, and you fully trust in your circadian time and variation, then you can set "Apply average result in circadiant IC/ISF" - - - Note that Autotune calculation will always be done with a single value, and circadian variation will not be tuned by Autotune. This setting only apply average variation calculated for IC and/or ISF on your circadian values - -- See on screenshot below Tuned profile with Apply average variation Off (on the left) and On (on the right) - - ![Autotune default screen](../images/Autotune/Autotune_13.png) - - - -### Tune specific days of the week - -- If you click on the checkbox with the eye on the right of "Rune days" parameter, you will see the day selection. You can specify which day of the week should be included in Autotune calculation (in screenshot below you can see an example for "working days" with Saturday and Sunday removed from autotune calculation) - - If the number of day included in Autotune calculation is lower than the number of Tune days, then you will see how many days will be included on the right of Tune days selector (10 days in the example below) - - This setting gives good results only if the number of remaining days is not to small (for example if you Tune a specific profile for week end days with only Sunday and Saturday selected, you should select a minimum of 21 or 28 Tune days to have 6 or 8 days included in Autotune calculation) - -![Autotune default screen](../images/Autotune/Autotune_14b.png) - -- During Autotune calculation, you can see the progress of the calculations ("Partial result day 3 / 10 tuned" on example below) - - ![Autotune default screen](../images/Autotune/Autotune_15b.png) - -## Run Autotune with an automation rule - -First step is to define correct trigger for an automation rule with Autotune: - -Note: for more information on how to set an automation rule, see [here](./Automation.rst). - -- You should select Recurring time trigger: only run Autotune once per day, and autotune is designed to be runned daily (each new run you shift one day later and quickly profile modification should be tiny) - - ![Autotune default screen](../images/Autotune/Autotune_16.png) - -- It's better at the beginning to run Autotune during the day to be able to check results. If you want to run Autotune during the night, you have to select in the trigger 4AM or later to include current day in next Autotune Calculation. - - ![Autotune default screen](../images/Autotune/Autotune_17.png) - -- Then you can select "Run Autotune" Action in the list - - ![Autotune default screen](../images/Autotune/Autotune_18.png) - -- You can then select Autotune Action to adjust parameters for your run. Default parameters are "Active Profile", default Tune days value defined in Autotune Plugin preferences, and All days are selected. - - ![Autotune default screen](../images/Autotune/Autotune_19b.png) - -- After a few days, if you fully trust Autotune results and percentage of modification is low, you can modify [Autotune settings](#autotune-plugin-settings) "Automation Switch Profile" to enabled to automatically update and activate profile tuned after calculation. - -Note: if you want to automatically tune profiles for specific days of the week (for example a profile for "Weekend days" and another one for "Working days"), then create one rule for each profile, select the same days in Trigger and in Autotune Action, Tune days must be high enough to be sure tuning will be done with at least 6 or 8 days, and don't forget to select time after 4AM in trigger... - -- See below an example of rule to tune "my profile" on all "Working days" with 14 Tune days selected (so only 10 days included in autotune calculation). - -![Autotune default screen](../images/Autotune/Autotune_20b.png) - - - -## Tips and trick's - -Autotune works with information existing in your database, so if you just installed AAPS on a new phone, you will have to wait several days before being able to launch Autotune with enough days to get relevant results; - -Autotune is just an help, it's important to regularly check if you agree with calculated profile. If you have any doubt, change Autotune settings (for example the number of days) or copy results in local profile and adjust profile before using it. - -Always use Autotune several days manually to check results before applyling them. And it's only when you fully trust Autotune results, and when variation becomes tiny between previous profile and calculated profile than you start to use Automation (Never before) - -- Autotune can work very well for some users and not for others, so **If you don't trust Autotune result, don't use it** - -It's also important to analyse Autotune results to understand (or try to understand) why Autotune propose these modifications - -- you can have a whole increase or decrease of the strength of your profile (for example increase of total basal associated to decrease of ISF and IC values). it could be associated to several following days with autosens correction above 100% (more agressivity required) or below 100% (you are more sensitive) -- Sometimes Autotune propose a different balance between basal rates and IC/ISF (for ex lower basal and more aggressive IC/ISF) - -We advise to not use Autotune in the following cases: - -- You don't enter all your carbs - - If you don't enter carbs correction for an hypoglycemia, Autotune will see an unexcepted increase of your BG value and will increase your basal rates the ' hours earlier, it could be the opposite of what you need to avoid hypo, especially if it's in the middle of the night. That's why it's important to enter all carabs especially correction for hypo. -- You have a lot of period with UAM detected during the day. - - Do you have entered all your carbs and correctly estimated your Carbs ? - - All UAM periods (except if you enter no carbs during a day and categorized UAM as basal is disabled), all your UAM periods will be categorized as basal, this can increase a lot your basal (much more than necessary) - -- Your carbs absorption is very slow: if most of your carbs absorption are calculated with min_5m_carbimpact parameter (you can see these periods with a little orange dot in the top of COB curve), the calculation of COB could be wrong and leads to wrong results. - - We you practice sport, you are generally more sensitive and your BG doesn't rise a lot, so during or after an exercice, it's usual to see some periods with slow carbs. But if you have too often unexpected slow carb absorption, then you may need a profile adjustment (higher value of IC) or a min_5m_carbimpact a bit to high. -- You have a "very bad days", for example stuck several hours in hyperglycemia with a huge amount of insulin to be able to go down within the range, or after a sensor change you got long periods of wrong BG values. -- If the percentage of modification is too important - - You can try to increase the number of days to get smoother results \ No newline at end of file diff --git a/docs/CROWDIN/nl/Usage/making-sport-with-AAPS.md b/docs/CROWDIN/nl/Usage/making-sport-with-AAPS.md deleted file mode 100644 index 79d2f1c38223..000000000000 --- a/docs/CROWDIN/nl/Usage/making-sport-with-AAPS.md +++ /dev/null @@ -1,185 +0,0 @@ -# making sport with AAPS - -In this section we want to address the topic of sport with AAPS. - -The aim is to show you how AAPS can help you to continue doing your favorite sport more easily or even to start doing it. It is relatively common for new type 1 diabetics to ask whether exercise is still possible for them, even if the answer in the training courses is actually a clear yes. Exercise is not only good for healthy people, but also for type 1 diabetics and even moderate exercise can even help to stabilize the blood sugar curve overall. - -:::{admonition} consult with your diabetes team after reading - -::: - -The difficulty here is that the prerequisites that someone brings with them and the expectations of what sport means to them are very different. - -Since we can assume that experienced top athletes with T1D who use AAPS are unlikely to look it up here, we deliberately set the bar low for ourselves when writing and for you when reading and using it, so that as many people as possible can benefit from it. - -Since even sport as a category is far too imprecise, as the effects of endurance sports differ greatly from strength training, for example, we are trying to break it down by type of sport. - -To be concrete and give you something you can test yourself we arrange the explanaiton around a concrete example and explain to you they action, reactions and effects. - -:::{admonition} more examples wanted - -The focus should always be on how others can do sport and not on the top performance someone has achieved. - -It's really about the basics. Your experience, which you share here, can help others to pursue their beloved sport more quickly and successfully and is therefore important. -::: - -## Cycling - -:::{admonition} take a friend with you - at least on your first trials -:class: information -A gerneral very good idea can be to take a good friend with you on the first rides. -This is especially important if you are not experienced in T1D. -Always keep in mind please: arrival comes before speed! Safety for you and the others in road traffic is very, very important. -::: - -### Example - -Let's take about 60 minutes of cycling on a flat route with a moderate heart rate as an example. - -1. we take a flat route in order to have an even load for the first exercise. This is not about performance, but purely about learning how you should react to changes in blood glucose. -2. we take the heart rate as an indicator of the load, as it is easy to see whether you are under load or not. -3. we set ourselves the goal of doing a relaxed lap around the neighborhood and focus on staying within our target range during the lap. In my case, this would be 70 <= x <= 180 mg/dl. - -We **don't** take the speed, as this is heavily dependent on personal physical conditions as well as the bike and surface used. It is therefore not very meaningful. - -You should know from the diabetes training courses you have attended that during endurance sports cycling, the insulin active in the body works significantly better than during times without physical exertion. The insulin active in the body is referred to as insulin on board (IoB). It is our most important parameter when cycling with T1D. - -We try to keep the IoB as low as possible at the start and during exercise. IoB should be around 0 or even slightly negative. You can get it there by not eating 3-4 hours before exercise. In the beginning it can also be helpful to exercise in the morning before breakfast, as with the right profile you should always have around 0 for IoB in the morning. - -AAPS shows us the IoB value on the home screen on the left under the blood glucose value. - -![IoB](../images/cycling_20240104-174035.png) - -:::{admonition} ignoring the IoB rule increases the risk for roller coaster BG dramatically -:class: danger -If you ignore this rule, you can still go cycling, but it will be much more difficult to keep your blood sugar levels in balance, so it is better to save this for later tests after several successful simple tests. -::: - -As you should know from the diabetes training courses, you should reduce the basal rate during exercise. The factor is individual. I have found a value of 50% in tests to be suitable for me. - -In AAPS, you should therefore change your profile to 50% before exercise and keep it active until the end of exercise. Some people even do it a certain amount of time before, e.g. 1 hour. Unfortunately, the pre-run is also individual. We will come to the post-run later. - -You should use two carbohydrates during exercise. - -1. medium-fast carbohydrates for the insulin still in the body and -2. very fast carbohydrates to prevent slipping into a hypo. - -For medium-fast carbohydrates, I treat myself to cookies or a banana before exercise, for example. You can also use something else that is more suitable for you. -For very fast carbohydrates, I take 3 teaspoons of dissolved glucose per 100 ml of still water in a 500 ml water bottle on my bike. If I'm cycling longer distances, I take a larger bottle with me and, if necessary, packaged glucose to refill the bottle. I add a little lemon juice for flavor. You can also use something other than lemon juice for the taste. You shouldn't change anything about the dextrose, as dissolved dextrose raises blood sugar levels super quickly. If you only take it in sips, your blood sugar won't go super high either! You can also do this tip at home beforehand as a dry run and see how quickly the change shows up on the CGMS. - -Why do I place so much emphasis on fast carbohydrates? - -1. once you are in a slight hypo, you may get back into the normal range by drinking the dextrose solution. As a rule, however, the oscillation of the curve then begins, which leads to a rollercoaster ride of the blood sugar. You may even be able to keep this within your target range, but you must be constantly vigilant. Without a hypo it is simply the most stable. -2. if you even slip into a somewhat severe hypo (without the need for outside help, of course), you may even have to pause briefly to avoid getting stuck in the hypo. - With both hypos, there is a risk that you will be tempted to switch from drinking 2-3 sips at a time to larger quantities. Not too bad at first, until the oscillation sets in and pushes you into a hyper. You can correct this, but your blood sugar will most likely go on a rollercoaster ride. - -What else is helpful, but not absolutely necessary? -It is important to keep an eye on your blood sugar, as your blood sugar can change enormously (e.g. 30 - 50 mg/dl) within 15 minutes of riding and a little more IoB or a basal rate that is still too high. The best way to keep an eye on it is if it is visible on the handlebars or if it is also displayed on your watch. It is even possible to install an additional app on some Garmin GPS bike computers that displays the blood glucose from XDrip or Nightscout as a data field on the bike computer. The additional app was developed by Andreas May from the T1D community. It is available free of charge in the official connect IQ Store. Certainly an interesting option for riders interested in sports. - -[Link to Andreas May Data Field App on connect IQ store](https://apps.garmin.com/de-DE/apps/5a3e2cda-12f0-4afd-88ed-000e67a68d84) - -Here is a picture of my Garmin Edge 530 bike computer with map, blood sugar and heart rate. - -![Garmin Edge 530 with BG data field](../images/cycling_IMG_1087.jpeg) - -After you have eaten the medium fast carbohydrates (24 - 36 g I take) and the blood sugar is above 100 mg/dl but also below 160 mg/dl, I carry out the profile change to 50% and set the activity temp target. - -:::{admonition} disable SMBs during high temp targets if necessary -:class: danger -Attention: If you prefer not to receive SMBs during the sport, please disable the option "Enable SMB with hight temp targets" in the settings of SMB or DynIFS Plugin. -::: - -The following picture shows the start and end of the sport. The end was specified as the duration when the profile was changed at the start. - -The temporary profile change has the following effects - -1. for a period of 60 minutes -2. a reduction to 50% of the profile and -3. the target is raised by clicking on the Activity Target option, which may have the side effect of disabling the SMBs - see above. - -![profile switch with temp target](../images/cycling_20240104-174056.png) - -The second image shows that the start at IoB was started towards 0. - -![IoB around 0](../images/cycling_20240104-174111.png) - -If the blood sugar drops faster than 15 mg/dl in 5 minutes or if it is at 120 mg/dl and tends to fall, I drink 1-2 sips of dissolved glucose. Then I wait for the next value and proceed as described above. - -You can hardly see it here, but at the beginning I took 2 sips from the bottle several times when my blood sugar started to fall. When it stabilized, I didn't need any more glucose. - -Here is the picture that illustrates this. The chart is saved on the Garmin as a result of the activity. - -![BG chart Garmin](../images/cycling_20240104-174431.png) - -If you should suddenly break out upwards, i.e. above 180 mg/dl, you should consider whether you should make a correction bolus. Caution: Remember the factor and apply it to the correction, otherwise the correction will be too strong. - -If your blood sugar drops below 80 mg/dl, take a break and drink two sips until your blood sugar is back above 100 mg/dl. - -At the end of the ride, the profile change should be finished as the time is up. - -Since we only rode easy for 60 minutes, there shouldn't be a big muscle bulking effect continuing to pull carbohydrates from your blood sugar. However, if it felt strenuous to you, keep an eye on it. This is especially true if you then go straight to bed. It may be better to change your profile to e.g. 80% for sleep. You may come out of sleep slightly too high, but it's better than having a hypo at night. Over time, you will surely find out what happens to you. - -The following pictures show the low intensity of the sport. - -The elevation profile -![](../images/cycling_20240104-174314.png) - -Speed with average and maximum speed - -![](../images/cycling_20240104-174326.png) - -Note the pause at the level crossing, which is also reflected in the heart rate. - -The heart rate. -![](../images/cycling_20240104-174337.png) - -The training effect. -![](../images/cycling_20240104-174358.png) - -The time in the different heart rate training zones. -![](../images/cycling_20240104-174423.png) - -After succesfully mastering this simple example you could go for further targets by stretching - -1. the distance and time -2. the load during the ride -3. the elevation during the right which should make a big impact on the more necessary carbs or further reduction of IoB and percentage of profile switch. - -Based on my experiences I would not expect to come back 100% with time in range over the whole and every ride. - -### Tipps - -I already gave some tipps for during the ride above. - -Here are some further tipps what can go wrong and how you can act to prevent it or react to compensate it. - -#### sky rocket high after ride - -During the ride everything was fine but after siting down and relax the blood sugar go sky rocket high. - -**Possible reason:** This happens when you have drunk too much dissolved glucose. - -**Reaction:** Drink 500 ml water, go to the shower and then control again. Latest after 30 minutes think about giving a correction bolus but be careful when it is short for bed time. Therefore it can be very good to make the first try runs on weekend mornings. - -**Action:** Next time be a bit more cautious in drinking from the dissolved glucose. - -#### hypo during ride - -During the ride you are going into hypo and can't recover your blood sugar during cycling. - -**Possible reason:** Your body cannot absorb enough carbohydrates quickly enough during exercise. - -**Reaction:** Take a rest and corrrect your blood sugar with drinking dissolved glucose. Stay calm: arrival comes before speed. - -**Action:** Did you started with IoB near 0? Have you eaten a small amount of middle fast carbs? Can you increase this or are the not fast enough for your body? Is it possible to prevent going into hypo by reducing the factor for the profile switch? Have you disbaled SMBs during ride as explained above? - -#### sky rocket high during ride - -During the ride your blood sugar goes sky rocket high. - -**Possible reason:** You have got taken too much carbs for your IoB at that time. Beneath for sure the typical technical problems with your -insulin pump like leakage or blockage of the catheder! - -**Reaction:** If it is too high for you take a rest and correct with a bolus. Keep in mind that you must ride home and therefore make it carefully. Drink 500 ml pure water without carbs. Stay calm: arrival comes before speed. - -**Action:** Have you eaten too much? Especially have you drunk too much from the dissolved glucose during the ride? Is your percentage of reduction the profile during profile switch too low and you can increase this? diff --git a/docs/CROWDIN/nl/buildingAAPS.md b/docs/CROWDIN/nl/buildingAAPS.md deleted file mode 100644 index 98164a09e49b..000000000000 --- a/docs/CROWDIN/nl/buildingAAPS.md +++ /dev/null @@ -1,28 +0,0 @@ -# Dummy - -## This is a dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - - -## This is another dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - - -## This is another another dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - diff --git a/docs/CROWDIN/nl/completingObjetives.md b/docs/CROWDIN/nl/completingObjetives.md deleted file mode 100644 index 98164a09e49b..000000000000 --- a/docs/CROWDIN/nl/completingObjetives.md +++ /dev/null @@ -1,28 +0,0 @@ -# Dummy - -## This is a dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - - -## This is another dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - - -## This is another another dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - diff --git a/docs/CROWDIN/nl/dummy.md b/docs/CROWDIN/nl/dummy.md deleted file mode 100644 index 98164a09e49b..000000000000 --- a/docs/CROWDIN/nl/dummy.md +++ /dev/null @@ -1,28 +0,0 @@ -# Dummy - -## This is a dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - - -## This is another dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - - -## This is another another dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - diff --git a/docs/CROWDIN/nl/intro.md b/docs/CROWDIN/nl/intro.md deleted file mode 100644 index 868159c21d52..000000000000 --- a/docs/CROWDIN/nl/intro.md +++ /dev/null @@ -1,291 +0,0 @@ -![20-06-23v2 AAPS simple overview-cropped](https://github.com/openaps/AndroidAPSdocs/assets/94044064/e505b73b-09a0-42a4-a1ab-b830a0741234) - -# Introduction to APS and AAPS - -## What is an “Artificial Pancreas System”? - -A human pancreas does a lot of things besides regulating blood sugar. However, the term **“Artificial Pancreas System” (APS)** usually refers to a system which works to automatically keep blood sugar levels within healthy limits. - -The most basic way to do this is by detecting **glucose levels**, using these values to do **calculations**, and then delivering the (predicted) right amount of **insulin** to the body. It repeats the calculation, every few minutes, 24/7. It uses **alarms** and **alerts** to inform the user if intervention or attention is needed. This system is typically made up of a **glucose sensor**, an **insulin pump** and an **app** on a phone. - -You can read more about the different artificial pancreas systems currently in use and in development in this 2022 review article: - -![Frontiers](./images/FRONTIERS_Logo_Grey_RGB.png) [Future Directions in Closed-Loop Technology](https://www.frontiersin.org/articles/10.3389/fendo.2022.919942/full#:~:text=Fully%20closed%2Dloop%20systems%2C%20unlike,user%20input%20for%20mealtime%20boluses). - -In the near future, some so-called "dual-hormone" systems will also have the ability to infuse glucagon alongside insulin, with the aim of preventing severe hypos and allowing even tighter blood glucose control. - -An artificial pancreas can be thought of as an [“autopilot for your diabetes”]. (https://www.artificialpancreasbook.com/) What does that mean? In an aircraft, an autopilot does not do the complete job of the human pilot, the pilot cannot sleep through the entire flight. The autopilot aids the work of the pilot. It relieves them of the burden of permanently monitoring the aircraft, allowing the pilot to concentrate on wider monitoring from time to time. The autopilot receives signals from various sensors, a computer evaluates them together with the pilot’s specifications and then makes the necessary adjustments, alerting the pilot to any concerns. The pilot no longer has to worry about constantly making decisions. - -## What does hybrid closed loop mean? - -The best solution for type 1 diabetes would be a “functional cure” (probably an implant of pancreatic cells which are protected from the immune system). While we are waiting for that, a “full closed loop” artificial pancreas is probably the next best thing. This is a tech system that doesn’t need any user input (like bolusing insulin for meals, or announcing exercise), with good regulation of blood glucose levels. At the moment, there are no widely available systems which are “full” closed loop, they all need some user input. The currently available systems are called “hybrid” closed loop, because they use a combination of automated technology and user input. - -## How and why did looping start? - -The development of commercial technology for people with type 1 diabetes (T1D) is very slow. In 2013 the T1D community founded the #WeAreNotWaiting movement. They developed systems themselves using existing approved technology (insulin pumps and sensors) to improve blood glucose control, safety, and quality of life. These are known as DIY (do-it-yourself) systems, because they are not formally approved by health bodies (FDA, NHS etc). There are four main DIY systems available: OpenAPS, **AAPS**, Loop and iAPS. - -A great way to understand the fundamentals of DIY looping is to read Dana Lewis’s book “Automated Insulin Delivery”. You can access it \[here\] (https://www.artificialpancreasbook.com/) for free (or buy a hardcopy of the book). If you want to understand more about OpenAPS, which** AAPS** has developed from, the \[OpenAPS website\] (https://openaps.org/what-is-openaps/) is also a great resource. - -Several commercial hybrid closed loop systems have been launched, the most recent of which are \[CamAPS FX\] (https://camdiab.com/) (UK and EU) and \[Omnipod 5\] (https://www.omnipod.com/en-gb/what-is-omnipod/omnipod-5) (USA and EU). These are very different to DIY systems, mainly because they both include a “learning algorithm” which adjusts how much insulin is delivered according to your insulin needs from previous days. Many people in the DIY community have already tried out these commercial systems and compared them with their DIY system. You can find out more about how the different systems compare by asking on the dedicated Facebook groups for these systems, on the \[AAPS Facebook group\] (https://www.facebook.com/groups/AndroidAPSUsers/) or on \[Discord\] (https://discord.com/invite/4fQUWHZ4Mw). - -## What is Android APS (AAPS)? - -![image](https://github.com/openaps/AndroidAPSdocs/assets/94044064/0f089d96-b7ee-452a-aa9d-aae10ab58971) - -**Figure 1**. Basic outline of the Android APS (Artificial Pancreas System), AAPS. - -Android APS (AAPS) is a hybrid closed loop system, or Artificial Pancreas System (APS). It makes its insulin dosing calculations using established \[OpenAPS\] (https://openaps.org/) algorithms (a set of rules) developed by the #WeAreNotWaiting type 1 diabetes community. - -Since OpenAPS is only compatible with certain older insulin pumps, AAPS (which can be used with a wider range of insulin pumps) was developed in 2016 by Milos Kozak, for a family member with type 1 diabetes. Since those early days, **AAPS** has been continually developed and refined by a team of volunteer computer developers and other enthusiasts who have a connection to the type 1 diabetes world. Today, **AAPS** is used by approximately 10,000 people. It is a highly customisable and versatile system, and because it is open-source, it is also readily compatible with many other open-source diabetes softwares and platforms. The fundamental components of the current **AAPS** system are outlined in Figure 1 above. - -## What are the basic components of AAPS? - -The “brain” of AAPS is an **app** which you build yourself. There are detailed step-by-step instructions for this. You then install the **AAPS app** on a compatible **Android smartphone** (1). A number of users prefer their loop on a separate phone to their main phone. So, you don’t necessarily have to be using an Android phone for everything else in your life, just for running your AAPS loop. - -The **Android smartphone** will also need to have another app installed on it as well as **AAPS**, either a modified Dexcom app called build-your-own dexcom app (**BYODA**) or Xdrip+. This receives glucose data from a sensor (2) by bluetooth, and then sends the data internally on the phone to the **AAPS app**. - -The **AAPS app** uses a decision making process (**algorithm**) from OpenAPS. Beginners start out using the basic **oref0** algorithm, but it is possible to switch to using the newer **oref1** algorithm as you progress with AAPS. Which algorithm you use (oref0 or oref1), depends on which suits your specific situation best. In both cases, the algorithm takes into account multiple factors, and performs rapid calculations every time a new reading comes in from the sensor. The algorithm then sends instructions to the insulin pump (3) on how much insulin to deliver by bluetooth. All the information can be sent by mobile data or wifi to the internet. This data can also be shared with followers if desired, and/or collected for analysis. - -## What are the advantages of the AAPS system? - -The OpenAPS algorithm used by **AAPS** controls blood sugar levels in the absence of user input, according to the users’ defined parameters (important ones being basal rates, insulin sensitivity factors, insulin-to-carb ratios, duration of insulin activity etc.), reacting every 5 minutes to the new sensor data. Some of the reported advantages of using AAPS are extensive fine-tunable options, automations and increased transparency of the system for the patient/caregiver. This can result in better control over your (or your dependent’s) diabetes, which in turn may give improved quality of life and increased peace of mind. - -Practical advantages include: - -- **Hardware flexibility**: **AAPS** works with a wide range of insulin pumps and sensors. So for example, if you develop an allergy to Dexcom sensor patch glue, you could switch to using a Libre sensor instead. That offers flexibility as life changes. You don't have to rebuild, just tick a different box in the AAPS app to change your hardware. - -- **Highly customisable with wide parameters**: here are some examples of the possibilities with AAPS: a) The ability to set a lower glucose target 30 min before eating; you can set the target as low as 72 mg/dL (4.0 mmol/L). b) If you are insulin-resistant resulting in high blood sugars, **AAPS** allows you to set an **automation** rule to activate when BG rises above 8 mmol/L (144 mg/dL), switching to a 120% profile (resulting in an 20% increase in basal and strengthening of other factors too, compared to your normal **profile** setting). The automation will last according to the scheduled time you set. Such an automation could be set to only be active on certain days of the week, at certain times of day, and even at certain locations. c) If your child is on a trampoline with no advance notice, **AAPS** allows insulin suspension for a set time period, directly via the phone. d) After reconnecting a tubed pump which has been disconnected for swimming, AAPS will calculate the basal insulin you have missed while disconnected and deliver it carefully, according to your current BG. Any insulin not required can be overridden by just “cancelling” the missed basal. f) **AAPS** has the ability to set different profiles for different situations and easily switch between them. Features which make the algorithm quicker to bring down elevated BG (like supermicro boluses (“SMB”), unannounced meals, (“**UAM**”) can be set to only work during the daytime, if you are worried about night-time hypos. - - -These are all examples, the full range of features gives huge flexibility for daily life including sport, illness, hormone cycles etc. Ultimately, it is for the user to decide how to use this flexibility, and there is no one-size-fits-all automation for this. - -- **Remote monitoring**: there are multiple possible monitoring channels (Sugarmate, Dexcom Follow, Xdrip+, Android Auto etc.) which are useful for parents/carers and adults in certain scenarios (sleeping/driving) who need customisable alerts. In some apps (Xdrip+) you can also turn alarms off totally, which is great if you have a new sensor “soaking” or settling down that you don’t want to loop with yet. - -- **Remote control**: a significant advantage of **AAPS **over commercial systems is that it is possible for followers, using authenticated text (SMS) commands or via an app (Nightscout or NSClient) to send a wide range of commands back to the ****AAPS** **system. This is used extensively by parents of kids with type 1 diabetes who use AAPS. It is very useful in the playground, for example, if you want to pre-bolus for a snack from your own phone, and your child is busy playing. It is possible to monitor the system (e.g. Fitbit), send basic commands (e.g. Samsung Galaxy watch 4), or even run the entire AAPS system from a high-spec smartwatch (5) (e.g. LEMFO LEM14). In this last scenario, you don’t need to use a phone to run AAPS. As battery life on watches improves, this last option is likely to become increasingly attractive. - -- **No commercial constraints due to open application interfaces**: beyond the use of an open source approach, which allows the source code of **AAPS** to be viewed at any time, the general principle of providing open programming interfaces gives other developers the opportunity to contribute new ideas that allow users to live more easily with their diabetes. This is complementary to commercial systems which adopt the innovations from DIY, where interfaces are only made possible in return for licensing, thus preventing innovations in particular that are not-for-profit. Good examples for such integrations are NightScout, Nightscout Reporter, Xdrip+ M5 stack etc. - -- **Detailed app interface**: It is easy to keep track of things like: insulin levels, cannula age, sensor age, pump battery age, and many actions can be done through the **AAPS** app (priming the pump, disconnecting the pump etc.), instead of on the pump itself. - -- **Accessibility and affordability**: **AAPS** gives people who currently can’t afford to self-fund, or don’t have funding/insurance, access to a world-class hybrid closed looping system which is conceptually years ahead, in terms of development, of the commercial systems being offered by clinics. You currently need to have a Nightscout account to set up **AAPS**. Although the Nightscout account it not necessarily required after setup, many people continue to use Nightscout for collecting their data, and for remote control. So, although **AAPS **itself is free, setting up Nightscout through one of the various platforms may incur a fee (E0 - E12), depending on what level of support you want (see comparison table). **AAPS** works with a wide range of affordable (starting from approx E150) Android phones. In comparison, Loop currently costs around $80 a year for the Apple development licence and CamAPS FX costs around E80/month (as at 2023). - -- ****Support**: No automated insulin delivery system is perfect. Commercial and open-source systems share many common glitches in both communications and temporary hardware failure. There is a community of AAPS users on both Facebook and Discord and Github who designed, developed and are currently using **AAPS** all over the world. There are Facebook support groups and help from clinic/commercial companies for the commercial APS systems - it is worth speaking to the users, or former users of these systems to get feedback on the common glitches, the quality of the education programme and the level of ongoing support provided. - -- **Predictability, transparency and safety**: with no learning algorithm, **AAPS** is logical and in some respect, more predictable, which may make it easier to know when a setting is wrong, and to adjust it accordingly. You can see exactly what the system is doing, why it is doing it, and set its operational limits, which puts the control (and responsibility) in your hands. This can provide the user with confidence, and a sounder sleep. - -- **Access to advanced features through dev modes including full closed loop**: **AAPS **documentation focuses on the mainstream **“master”** branch of **AAPS**, however, research and development is going on all the time. More experienced users may wish to explore the experimental features in the **development** branch such as integration of Dexcom G7, and automatically adjusting insulin delivery according to short-term sensitivity changes (DYNISF), not having to bolus for meals, and generally trying to make life with type 1 diabetes as convenient as possible. - -- **Ability to contribute yourself to further improvements**: type 1 diabetes can be highly frustrating and isolating. Having control over your own diabetes tech, with the possibility to “pay it forward” as soon as you are making progress by helping others on their journey can be really rewarding. You can educate yourself, discover the roadblocks and look for and even contribute to new developments and the documentation. There will be others with the same quest to bounce ideas off and work with. This is the essence of #WeAreNotWaiting. - - -## How does AAPS compare to MDI and open looping? - -Multiple daily injections (MDI, a) usually involve giving an injection of a long-lasting insulin (e.g. Tresiba) once a day, with injections of faster-acting insulin (e.g. Novorapid, Fiasp) at mealtimes, or for corrections. Open pumping (b) involves using a pump to deliver basal at pre-programmed rates of rapid-acting insulin, and then boluses through the pump at mealtimes or for corrections. The basics of a looping system is that the App uses the glucose data to instruct the pump to stop insulin delivery when it predicts you are heading for a low, and to give you extra insulin if your glucose levels are rising and predicted to go too high (c). Although this is oversimplified, (mostly because hybrid closed looping has a lot of additional useful features) the key features of each system are shown in **Figure 2**. - -![image](https://github.com/openaps/AndroidAPSdocs/assets/94044064/4e7d8608-684d-4c69-9c61-88c9539f5d6f) - -**Figure 2**. Overview of (a) MDI, (b) open-loop pumping and (c) hybrid closed loop pumping - -## How does AAPS compare to other looping systems? - -At present there are four major open source closed loop systems available: OpenAPS, **AAPS**, \[Loop\] (https://loopkit.github.io/loopdocs/#what-is-loop) and iAPS, (formerly FreeAPS X). The features of the different systems are shown in the table below: - -| Devicestyp | Name | [Open APS](https://openaps.readthedocs.io/en/latest/) | [AAPS](https://wiki.aaps.app) | [Loop](https://loopkit.github.io/loopdocs/) | [iAPS](https://iaps.readthedocs.io/en/latest/) | -| ---------- | -------------------------------------------------------------------------------------------------------- | ----------------------------------------------------- | ------------------------------------------- | ------------------------------------------- | ---------------------------------------------- | -| PUMP | Older Medtronic | ![available](./images/available.png) | ![available](./images/available.png) | ![available](./images/available.png) | ![available](./images/available.png) | -| PUMP | Older Omnipod (Eros) | ![unavailable](./images/unavailable.png) | ![available](./images/available.png) | ![available](./images/available.png) | ![available](./images/available.png) | -| PUMP | Newer Omnipod (Dash) | ![unavailable](./images/unavailable.png) | ![available](./images/available.png) | ![available](./images/available.png) | ![available](./images/available.png) | -| PUMP | DANA R, DANA RS, DANA I | ![unavailable](./images/unavailable.png) | ![available](./images/available.png) | ![unavailable](./images/unavailable.png) | ![unavailable](./images/unavailable.png) | -| PUMP | Roche Combo, Insight | ![unavailable](./images/unavailable.png) | ![available](./images/available.png) | ![unavailable](./images/unavailable.png) | ![unavailable](./images/unavailable.png) | -| CGM | Dexcom G4, G5, G6 | ![available](./images/available.png) | ![available](./images/available.png) | ![available](./images/available.png) | ![available](./images/available.png) | -| CGM | Libre 1 (requires Miao Miao) | ![available](./images/available.png) | ![available](./images/available.png) | ![available](./images/available.png) | ![available](./images/available.png) | -| CGM | Libre 2 | ![available](./images/available.png) | ![available](./images/available.png) | ![available](./images/available.png) | ![available](./images/available.png) | -| CGM | Libre 3 | | ![unavailable](./images/unavailable.png) | --- | ![unavailable](./images/unavailable.png) | -| CGM | Medtronic Enlite | | --- | ![unavailable](./images/unavailable.png) | --- | -| CGM | [Dexcom G7](https://androidaps.readthedocs.io/en/latest/Hardware/DexcomG7.html) | | ![available](./images/available.png) (beta) | ![available](./images/available.png) | ![available](./images/available.png) | -| CGM | [Eversense](https://androidaps.readthedocs.io/en/latest/Hardware/Eversense.html) | | ![available](./images/available.png) | | ![available](./images/available.png) | -| CGM | [MM640g/MM630g](https://androidaps.readthedocs.io/en/latest/Hardware/MM640g.html) | | ![available](./images/available.png) | | ![available](./images/available.png) | -| CGM | [PocTech](https://androidaps.readthedocs.io/en/latest/Hardware/PocTech.html) | | ![available](./images/available.png) | | ![available](./images/available.png) | -| CGM | [Nightscout as BG Source](https://androidaps.readthedocs.io/en/latest/Hardware/CgmNightscoutUpload.html) | | ![available](./images/available.png) | | ![available](./images/available.png) | -| Phone | Android | ![available](./images/available.png) | ![available](./images/available.png) | ![unavailable](./images/unavailable.png) | ![unavailable](./images/unavailable.png) | -| Phone | iPhone | ![available](./images/available.png) | ![unavailable](./images/unavailable.png) | ![available](./images/available.png) | ![available](./images/available.png) | - -[OpenAPS](https://openaps.readthedocs.io/) was the first Open Source Closed Loop System. Het maakt gebruik van een kleine computer zoals Raspberry Pi of Intel Edison. Both AndroidAPS (AAPS) and iAPS use the OpenAPS algorithms, whereas Loop uses a separate algorithm. You can read a comparison of iAPS and **AAPS** here. - -An international peer-reviewed consensus statement containing practical guidance on open source looping was written by and for health-care professionals, and published in a leading medical journal in 2022. It is well worth a read (including for your diabetes clinic) and summarises the main technical differences between the different open-source hybrid closed loop systems: - - Lancet Diabetes Endocrinol, 2022; 10: 58–74 - -[https://www.ncbi.nlm.nih.gov/pmc/articles/PMC8720075/](https://www.ncbi.nlm.nih.gov/pmc/articles/PMC8720075/) - -It is hard to get a “feel” for any system without using it, or talking to others who are using it, so do reach out to others on Facebook/Discord and ask. Most people find that AAPS is incredibly sophisticated in comparison to other hybrid closed loop systems (particularly the commercial systems), with a huge number of potentially customisable settings and features, discussed above. Some people can find this a little overwhelming in the beginning, but there is no rush to investigate all the possibilities at once, you can progress as slowly or as fast as you would like, and there is help available at every step of the way. - -## Does AAPS use artificial intelligence or any learning algorithm? - -No. **AAPS** does not have any complicated machine learning algorithms, multiple-parameter insulin response models, or differential equations. As such, the system is open and transparent in how it works, and has the ability to be understood not just by experts, but also by clinicians and patients. It also means that if you have a sharply varying schedule (maybe switching from a stressful week at work to a relaxing holiday) and are likely to need a significantly different amount of insulin, you can immediately switch **AAPS** to run a weaker/stronger profile. A ‘learning system’ will do this adjustment for you automatically, but is likely to take longer to adjust the insulin delivery. - -## Which system is right for me or my dependent? - -Practically, your choice of system is often restricted by which pump you already have, or can obtain from your medical provider, and your choice of phone (Apple or Android). If you don’t yet have a pump you have the biggest choice of systems. Technology is continually evolving, pumps are being discontinued and new pumps and sensors are being released. Most open-source systems work with the main sensors (Libre and Dexcom) or are quickly adapted to work with new sensors a year or so after they are released (with a bit of time delay for safety and stability testing). - -Most **AAPS **users report more time in range, HbA1c reductions, as well as quality of life improvements from having a system that can auto-adjust basal rates overnight during sleep, and this is true for most hybrid closed loop APS. Some people have a preference for a very simple system which is not very customisable (which means you may prefer a commercial system), and others find this lack of control very frustrating (you may prefer an open-source system). If you (or your dependent) are newly diagnosed, a common route is to get the hang of MDI plus sensor first, then progress to a pump which has the potential for looping, then to **AAPS**, but some people (especially small kids) may go straight to a pump. - -It is important to note that the **AAPS** user needs to be proactive to troubleshoot and fix problems themselves, with help from the community. This is a very different mindset to that when using a commercial system. With **AAPS** a user has more control, but also the responsibility, and needs to be comfortable with that. - -## Is it safe to use open-source systems like AAPS? - -A more accurate question is probably “is it safe compared to my current type 1 diabetes insulin delivery system?” since no method of insulin delivery is without risk. There are many checks and balances in place with **AAPS**. A recent paper looked at the use of**** AAPS ****in a computer simulated set-up, [https://www.liebertpub.com/doi/epub/10.1089/dia.2019.0375](https://www.liebertpub.com/doi/epub/10.1089/dia.2019.0375) which was an effective way to unobjectively trial how safe and effective the system is. More generally, it is estimated that over 10,000 individuals worldwide are using open-source automated-insulin delivery systems, and uptake continues to increase globally. - -Any device that uses radio communications could be hacked, and this is true for a non-looping insulin pump as well. Currently, we are not aware of anyone attempting to harm individuals by hacking their diabetes-related medical equipment. However, there are multiple ways to protect against such risks: - -1. In the pump settings, limit both the max bolus allowed and max temporary basal settings to amounts that you believe are safest. These are hard limits that we do not believe any malicious hacker could circumvent. - -2. Set your CGM alarms enabled for both highs and lows. - -3. Monitor your insulin delivery online. Nightscout users can set additional alarms to alert for a wide variety of conditions, including conditions that are much more likely to occur than a malicious attack. In addition to highs and lows, Nightscout can display diagnostic data useful for verifying that the pump is operating as desired, including current IOB, pump temporary basal history, pump bolus history. It can also be configured to proactively alert users to undesirable conditions, such as predicted highs and lows, low insulin reservoir, and low pump battery. - - -If a malicious attack was made on your insulin pump, these strategies would significantly mitigate the risk. Every potential **AAPS** user needs to weigh the risks associated with using **AAPS**, versus the risks of using a different system. - -## How can I approach discussing AAPS with my clinical team? - -Depending on the country - link to doctors section of docs - - Lancet Diabetes Endocrinol, 2022; 10: 58–74 - -[https://www.ncbi.nlm.nih.gov/pmc/articles/PMC8720075/](https://www.ncbi.nlm.nih.gov/pmc/articles/PMC8720075/) - -## Q: Why can’t I just download AAPS and use it straight away? - -The **AAPS** app is not provided in Google Play - you have to build it from source code by yourself for legal reasons. **AAPS** is unlicensed, meaning that it does not have approval by any regulatory body authority in any country. **AAPS**is deemed to be carrying out a medical experiment on yourself, and is carried out at the user’s own risk. - -Setting up the system requires patience, determination and the gradual development of technical knowledge. All the information and support can be found in these documents, elsewhere online, or from others who have already done it. It is estimated that over 2000 people have successfully built and are currently using **AAPS** worldwide. - -The developers of **AAPS**t ake safety incredibly seriously, and want others to have a good experience of using **AAPS**. That is why it is essential that every user (or carer, if the user is a child): - -- builds the AAPS system themself and works through the **objectives** so that they have reasonably good personalised settings and understand the basics of how AAPS ****works by the time they “close the loop”; - -- backs up their system by exporting and saving important files (like keystore and settings .json file) somewhere safe, so you can setup again quickly if needed; - -- updates to newer master versions as and when they become available; and - -- maintains and monitors the system to ensure it is working properly. - - -## Q: What is the connectivity of the AAPS system? - -**Figure 3 (below)** shows one example of the **AAPS** system for a user who do not require any followers interacting with the system: - -![potential AAPS connectivity setup with no followers](./images/intro03.png) - -**Figure 4 (below)** shows the full potential of the **AAPS** system for a user who has followers and requires a monitor and send adjust the system remotely (like a child with T1D): - -![potential AAPS connectivity setup with followers](./images/intro04.png) - -## Q: How does AAPS get continually developed and improved? - -Most **AAPS** users use the fully tested **master** version of AAPS, which has been tested for bugs and problems, before being released to the community. Behind the scenes, the developers try out new improvements, and test these out in “developer” (**dev**) versions of **AAPS** with a user community who are happy to do bug updates at short notice. If the improvements work well, they are then released as a new “master” version of **AAPS**. Any new master release is announced on the Facebook group, so that the mainstream **AAPS** users can read about and update to the new master version. - -Some experienced and confident **AAPS ** users conduct experiments with emerging technologies and with dev versions of the **AAPS** app, which can be interesting for the less adventurous users to read about, without having to do it themselves! People tend to share these experiments on the Facebook group too. - -You can read more about some of these experiments and discussion on emerging tech here: - -[https://www.diabettech.com/](https://www.diabettech.com/) - -[https://bionicwookie.com/](https://bionicwookie.com/) - -## Q: Who can benefit? - -| User Type | -| ------------------------------------------- | -| ✔️ type 1 diabetic | -| ✔️ caregiver or parent of a type 1 diabetic | -| ✔️ blind users type 1 diabetic | -| ✔️ *clincians and healthcare professionals | - -The above table assumes that the user has access to both continuous gluocse monitor and insulin pump. - -*All data from **AAPS** can be made available to healthcare professionals via data sharing platforms, including NightScout that provides logging and real time monitoring of CGM data, insulin delivery, carbohydrate entries, predictions and settings. Nightscout records include daily and weekly reports which can aid healthcare professionals' discussions with type 1 patients with more accurate data on glycemic control and any behavioural considerations. - -## Q: What benefits can I get? - -With investment of your time, **AAPS** can potentially lead to: - -- alleviating the stress and burden of managing type 1 diabetes; - -- reducing the multitude of mundane decisions that arise from type 1 diabetes; - -- the provision of personalised and dynamic insulin dosing based on real-time data which can cut down the need for hypo treatments and reduce hyperglycemia episodes; - -- an increased knowledge of insulin management and confidence to better fine tune your settings; - -- the ability to create automatic settings (**automations**) that are tailored to fit in with your lifestyle; - -- improved sleep quality and overall reduction in the frequency of nighttime interventions; - -- remote monitoring and administration of insulin delivery for caregivers of type 1 diabetics; and - -- streamlining of all your portable diabetic equipment (continuous glucose monitor and insulin portable devices) by replacing them with an android phone controlled by **AAPS**. - - -Ultimately,**AAPS** can empower individuals to better manage their diabetes resulting in stable blood sugars and improved long term health outcomes. - ---- - -## AAPS First Steps - -Welcome. This is an introduction to aid beginners getting started with **AAPS** (or commonly referred to as "looping"). - -## Safety - -“_With great powers comes great responsibilities…_” - -**AAPS** is designed with an extensive set of safety features with limits imposed and gradually removed with completion of the **objectives **(predominately made up of multiple choice questions). An **AAPS** feature will be unlocked as the Objectives are successfully completed. This process will gradually allow the user to migrate from Open Loop to Closed Loop. - -This has been done to achieve the best possible experience with **AAPS** in order to prevent common mistakes that new users tend to make when starting to loop. The safety parameters have been built upon typical errors and general trends **AAPS** developers have observed with new users. Mistakes can happen because the beginner is inexperienced and too eager to get started with AAPS or has overlooked the required materials. Do not worry, we have all been there! - -## Key Principles - -The key principles and concepts of looping must be understood by the user before using **AAPS**. This is achieved by investing your personal time into reading the **AAPS** documentation, and completing the Objectives which is aimed to provide you with a solid platform for safe and effective use of **AAPS**. The volume of **AAPS** documentation may seem overwhelming at first but be patient and trust the process - with the proper approach, you'll get there! The overall process will depend upon the beginner’s progress and completion of objectives can typically take between 6 to 9 weeks . - -## Plan for hiccups - -At the preliminary stages of **AAPS**, you should expect to experience some hiccups whilst trying to fine tune your settings. **AAPS**’ glitches cannot be flushed out until the system is used in everyday life. Please plan accordingly and allow a sensible amount of time to troubleshoot and resolve such issues. - -## Flexibility/Adaptability - -Success with **AAPS** requires a proactive approach, a willingness to reflect on the BG data and flexibility to make the necessary adjustments to **AAPS** in order to improve your outcomes. Just as it is nearly impossible to learn to play a sport by reading about the rules alone, the same can be said of **AAPS**. - -## Technology compatibility - -There are limitations with **AAPS** as it is accessible for only certain types of insulin pumps or CGMs, and some technology may not be available for use in various countries. In order to avoid any disappointment or frustrations, please read please read Component Set Up (Section INSERT). - -## App Build Time - -The time to build the **AAPS**(under Section INSERT) depends on your level of expertise and technical ability. Typically for inexperienced users, it can take up to half a day or a full day (with help from the community) in order to build the **AAPS**. The process will significantly speed up as you become more experienced at building the **AAPS**. To aid the build process there are sections dedicated for: -- list of questions and answers for frequent errors that are likely to occur under FAQs (Section K); -- “How to install AAPS? (Section INSERT) which includes Troubleshooting subsection. - -## Keystore & configurations settings a export file - -A “keystore” is a password encrypted file unique to your own copy of **AAPS**. Your android phone uses it to ensure that nobody else can upgrade your own copy without the keystore. In short, as part of the **AAPS** build, you should: - -- save the your keystore file (.jks file used to sign your app) in a safe place; -- keep a note of your password for your keystore file. - -By doing the above, this will ensure that you can use that exact same keystore file each time an updated version of **AAPS** is created. On average, there will be 2-3 AAPS updates required each year. - -In addition, **AAPS** provides the ability to export all your configuration settings. This ensures that you can safely recover your system while changing phones, upgrading/reinstalling the application with minimum disruption. - -## Troubleshootng - -Please feel free to reach out to the AAPS community if there is anything you feel unsure about - there is no such thing as a silly question! All users with various levels of experience are encouraged to ask questions as necessary. Response times to questions are usually quick, typically only a few hours due to the volume of **AAPS** users. - -a) check the documentation; b) ask AAPS facebook group (https://www.facebook.com/groups/AndroidAPSUsers); and c) ask our discord channel. - -## Section overview - -AAPS documentation is made up of the following Sections: - -[INSERT ONCE SECTIONS /SUB SECTIONS AGREED] ---- diff --git a/docs/CROWDIN/nl/maintaining.md b/docs/CROWDIN/nl/maintaining.md deleted file mode 100644 index 98164a09e49b..000000000000 --- a/docs/CROWDIN/nl/maintaining.md +++ /dev/null @@ -1,28 +0,0 @@ -# Dummy - -## This is a dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - - -## This is another dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - - -## This is another another dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - diff --git a/docs/CROWDIN/nl/optimizing.md b/docs/CROWDIN/nl/optimizing.md deleted file mode 100644 index 98164a09e49b..000000000000 --- a/docs/CROWDIN/nl/optimizing.md +++ /dev/null @@ -1,28 +0,0 @@ -# Dummy - -## This is a dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - - -## This is another dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - - -## This is another another dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - diff --git a/docs/CROWDIN/nl/prepairing.md b/docs/CROWDIN/nl/prepairing.md deleted file mode 100644 index 6cc74a0a3e16..000000000000 --- a/docs/CROWDIN/nl/prepairing.md +++ /dev/null @@ -1,145 +0,0 @@ -# Prepairing - -## Guide to the Android APS doc - -### First Steps -Welcome. This is an introduction to aid beginners to the concept of Do-It-Yourself-APS (Android-Artificial-Pancreas-Systems “AAPS”) is commonly referred to as ‘looping’.. - -#### Safetys -“With great powers come great responsibilities…” - -AAPS is designed with an extensive set of safety features with limits imposed and gradually removed with completion of the [Objectives](https://androidaps.readthedocs.io/en/latest/Usage/Objectives.html) (predominately made up of multiple choice questions). An AAPS feature will be unlocked as the Objectives are successfully completed. This process will gradually allow the user to migrate from Open Loop to Closed Loop. - -This has been done to achieve the best possible experience with AAPS by preventing common mistakes new users tend to make when starting to loop. The safety parameters have been built upon typical errors and general trends AAPS developers have observed with new users. Mistakes can happen because the beginner is inexperienced and too eager to get started with AAPS or has overlooked the required materials. Do not worry, we have all been there! - -#### Key Principles - -The key principles and concepts of looping must be understood by the user before using AAPS. This is achieved by investing your personal time into reading the AAPS documentation, and completing the [Objectives](https://androidaps.readthedocs.io/en/latest/Usage/Objectives.html) which is aimed to provide you with a solid platform for safe and effective use of AAPS. The volume of AAPS documentation may seem overwhelming at first but be patient and trust the process - with the proper approach, you'll get there! The overall process will depend upon the beginner’s progress and completion of objectives which typically take between 6 to 9 weeks . - -#### Plan for hiccups - -At the preliminary stages of AAPS, you should expect to experience some hiccups whilst trying to fine tune your settings. AAPS’ glitches cannot be flushed out until the system is used in everyday life. Please plan accordingly and allow a sensible amount of time to troubleshoot and resolve such issues. - -#### Flexibility/Adaptability - -Success with AAPS requires a proactive approach, a willingness to reflect on the BG data and flexibility to make the necessary adjustments to AAPS in order to improve your outcomes. Just as it is nearly impossible to learn to play a sport by reading about the rules alone, the same can be said of AAPS. - -#### Technology compatibility -There are limitations with AAPS as it is accessible for only certain types of insulin pumps or CGMs, and some technology may not be available for use in various countries. In order to avoid any disappointment or frustrations, please read [Component Set Up (Section E).](https://androidaps.readthedocs.io/en/latest/Configuration/BG-Source.html) - -#### App Build time -The time to build the AAPS (under Section D) depends on your level of expertise and technical ability. Typically for inexperienced users, it can take up to half a day or a full day (with help from the community) in order to build the AAPS. The process will significantly speed up as you become more experienced at building the AAPS.  - -To aid the build process there are sections dedicated for: - -- list of questions and answers for frequent errors that are likely to occur under [FAQs (Section](https://androidaps.readthedocs.io/en/latest/Getting-Started/FAQ.html) K); - -- “[How to install AAPS](https://androidaps.readthedocs.io/en/latest/Installing-AndroidAPS/Building-APK.html)? (Section D) which includes [Troubleshooting](https://androidaps.readthedocs.io/en/latest/Usage/troubleshooting.html) subsection. - - -#### Keystore & configuration settings export  file - -A “keystore” is a password encrypted file unique to your own copy of AAPS. Your android phone uses it to ensure that nobody else can upgrade your own copy without the keystore.In short, as part of the AAPS build, you should: - -1. save the your keystore file (.jks file used to sign your app) in a safe place; - -2. keep a note of your password for your keystore file. - - -By doing the above, this will ensure that you can use that exact same keystore file each time an updated version of AAPS is created. On average, there will be 2-3 updates to the AAPS required each year. In addition, AAPS provides the ability to [export all your configuration settings](https://androidaps.readthedocs.io/en/latest/Usage/ExportImportSettings.html). This ensures that you can safely recover your system while changing phones, upgrading/reinstalling the application with minimum disruption.  - -#### Problemen oplossen - -Please feel free to reach out to the AAPS community if there is anything you feel unsure about - there is no such thing as a silly question!  All users with various levels of experience are encouraged to ask questions as necessary. Response times to questions are usually quick, typically only a few hours due to the volume of AAPS users.  - -##### [check the documentation](https://androidaps.readthedocs.io/en/latest/index.html) - -##### [ask our facebook group](https://www.facebook.com/groups/AndroidAPSUsers/) - -##### [ask our discord channel](https://discord.com/channels/629952586895851530/629954570394533889) - -#### Section overview - -AAPS documentation is made up of the following Sections: - -##### [Getting started](https://androidaps.readthedocs.io/en/latest/Getting-Started/Safety-first.html) - -This is a must read to understand the general concept of what an artificial pancreas system is designed to do. - -##### [What do I need?](https://androidaps.readthedocs.io/en/latest/Module/module.html) - -This explains AAPS’ compatibility with CGMs (Continuous Glucose Monitors) and insulin pumps. It also provides a guide on the correct assembly of an AAPS system to ensure that it functions correctly in everyday life. - -##### How to install AAPS - -This section is the manual for building the AAPS. Strict adherence to the step-by-step instructions are required in order to successfully build the AAPS. Please take your time. - -##### [Component Setup](https://androidaps.readthedocs.io/en/latest/Configuration/BG-Source.html) - -This explains how to properly integrate each of the various different separate component parts into AAPS, as well as how to set them up to work as seamlessly as possible together. All components are listed under the separate sections: CGM/FGM, xDrip Settings, Pumps, Phones, Nightscout setup, and Smartwatches. The sensor (BG) values and control of the insulin pump are particularly important information to understand. - -##### Configuration - -This explains how to set and configure your ‘Profile’, ‘Insulin’, ‘BG Source’, ‘Pump’, ‘Sensitivity Detection’, ‘APS’, ‘Loop’, ‘Treatments’. - -##### AAPS Usage - -This section provides a breakdown of the features provided by AAPS. - -##### [General Hints](https://androidaps.readthedocs.io/en/latest/Usage/Timezone-traveling.html) - -Useful tricks on how to tackle looping issues such as time zones, and daylight saving (i.e. Spring Forward/ - Fall Back). - -##### [AAPS](https://androidaps.readthedocs.io/en/latest/Getting-Started/Screenshots.html) for Children - -This is designed for parents or caregivers who want to build an AAPS for their child. It also explains the extra features necessary in order to support and safely control your child’s AAPS remotely.

The concepts in this section should be fully understood in order to competently use this feature. - -##### Problemen oplossen - -This section contains links to help solve issues when building or using AAPS. - -##### FAQ - -This section addresses specific questions which tend to come up when building or using AAPS. - -##### [Veelgebruikte woordenlijst](https://androidaps.readthedocs.io/en/latest/Getting-Started/Glossary.html) - -This contains a list of the acronyms (or short-term names) or defined terms developed specifically for AAP (for instance, the terms ‘ISF’ or ‘TT’ have special meanings in AAPS). - -##### [Where to go for help](https://androidaps.readthedocs.io/en/latest/Where-To-Go-For-Help/Background-reading.html)? - -This section is aimed to provide new users with links on resources in order to get help including accessing community support made up of both new and experienced users who can clarify questions, and resolve the usual pitfalls that come with AAPS. - -##### For Clinicians - -This is a section for the clinicians who have expressed interest in open source artificial pancreas technology such as AAPS, or for patients who want to share such information with their clinicians. | - -## what are we going to build? - -### An Android Phone Application - -At the core, AAPS is an android application running from a phone. You are going to build it from scratch by installing tools to download the sourcecode and build the actual application. - -### A reporting server NightScout (or Tidepool) - -In order to fully use AAPS properly you will want to setup a nightscout server. It is used to collect data from AAPS over time and possibly communicate to the application. It is required for parents who want to oversee their children AAPS sessions. It is also key to share data between clinicians and patients to perform analysis over time. - -## How long will it take? - -## Who might AAPS not be suitable for? - -## Where can I get help? - -## Requirements - -### medical - -### technical - -### personal - -### CGMs - -### Insulin Pump - -### Reporting (NS, Tidepool) \ No newline at end of file diff --git a/docs/CROWDIN/pb/Configuration/EOFLOW.md b/docs/CROWDIN/pb/Configuration/EOFLOW.md deleted file mode 100644 index e697feadb732..000000000000 --- a/docs/CROWDIN/pb/Configuration/EOFLOW.md +++ /dev/null @@ -1,155 +0,0 @@ -# EOPatch2 Instruction Manual - -The patch requires the use of rapid-acting U-100 type insulin, such as NovoRapid or Humalog. Use a rapid-acting insulin that is suitable for you according to your doctor’s prescription and inject the prescribed dosage. - -The smallest injectable dose of insulin when using the patch is 0.05 U. The Profile BAS should therefore be set at a minimum value of 0.05 U/hr or more and an interval of 0.05 U/hr, as otherwise there may be an error between the estimated total infusion amount in the Profile and the actual infusion amount in the patch. Likewise, the bolus must also be set and infused with a minimum infusion volume of 0.05 U. - -## Pump Setup -1. On the AndroidAPS home screen, click the hamburger menu in the upper left corner and go to Config Builder. -1. Select 'EOPatch2' in the Pump section. -1. Press the Back key to return to the home screen. - -![Bild1](../../images/EOPatch/Bild1.png) ![Bild2](../../images/EOPatch/Bild2.png) - -## Settings -Select EOPATCH2 at the top of the home screen to go to the EOPATCH2 tab. - -Select the EOPatch2 Preferences menu by clicking the three dots in the upper right corner. - -The EOPatch2 Preferences menu offers a menu to set 3 types of notifications. - -### Low reservoir Alerts -A warning appears when the amount of insulin remaining in the reservoir reaches the set value or less while using the patch. It can be set from 10 to 50U in 5U increments. - -### Patch expiration Reminder -This is a reminder to notify you of the time remaining before the current patch expires. It can be set from 1 to 24 hours in 1 hour increments. The initial setting value is 4 hours. - -### Patch buzzer Reminder -This is a reminder function for injections other than basal injection. If you are using an (extended) bolus injection or a temporary basal injection, the patch will make a buzzer sound when the injection starts and when the injection is complete. The initial setting value is Off. - -![Bild3](../../images/EOPatch/Bild3.png) - -## Connecting the Patch - -### Move to patch connection screen - -Select EOPATCH2 at the top of the home screen and click the ACTIVATE PATCH button at the bottom left. - -![Bild4](../../images/EOPatch/Bild4.png) - -### Connecting the patch -Insert the syringe needle into the insulin inlet on the patch and then slowly push the piston to inject the insulin. When insulin is filled with more than 80U, the patch makes a booting sound (1 buzzer) and boots. After confirming the buzzer sound, click the START PAIRING button on the screen. - -[Warning] - -- Do not turn the needle action lever until instructed. It can cause serious problems during injection or safety checks otherwise. -- The amount of insulin that can be injected into the patch is 80~200U. If you inject less than 80U into the patch initially, the patch will not work. -- Take the insulin to be put into the patch from the refrigerator and leave it at room temperature for 15 to 30 minutes beforehand. The temperature of the insulin to be injected must be at least 10°C. - -![Bild5](../../images/EOPatch/Bild5.png) - -### patch pairing -The Patch pairing screen will be displayed, and pairing will be attempted automatically. If communication is successful, the Bluetooth pairing request notification appears. Click OK and when the Bluetooth pairing request notification appears a second time with the authentication code, select OK again. - -[Warning] - -- For pairing, the patch and the smartphone must be located within 30 cm of each other. -- After the patch booting is completed, the patch will beep every 3 minutes until the pairing is complete. -- After booting the patch, the patch application must be completed via the app within 60 minutes. If the application cannot be completed within 60 minutes, the patch should be discarded. - -![Bild6](../../images/EOPatch/Bild6.png) ![Bild7](../../images/EOPatch/Bild7.png) ![Bild8](../../images/EOPatch/Bild8.png) - - -### patch preparation -After removing the adhesive tape of the patch, check if the needle is sticking out. If there are no problems with the patch, click NEXT. - -![Bild9](../../images/EOPatch/Bild9.png) - -### Patch attachment -Insulin should be injected in a spot with subcutaneous fat but few nerves or blood vessels, so it is recommended to use the abdomen, arm, or thigh for the patch attachment site. Choose a patch attachment site and apply the patch after disinfecting the location. - -[Warning] - -- Make sure to straighten the side of the patch tape attached to the body evenly, so that the patch adheres completely to the skin. -- If the patch does not stick completely, air may enter between the patch and the skin, which can weaken the adhesive strength and waterproof effect of the patch. - -![Bild10](../../images/EOPatch/Bild10.png) - -### Safety Check -When patching is complete, touch Start Safety Check. When the safety check is completed, the patch will beep once. - -[Warning] - -- For safe use, do not turn the needle action lever until the safety check has been completed. - -![Bild11](../../images/EOPatch/Bild11.png) ![Bild12](../../images/EOPatch/Bild12.png) - - -### Inserting the needle -The needle is inserted by holding around the patch and turning the needle action lever more than 100° in the upward direction of the lever. There is a buzzer sound when the needle is inserted correctly. Turn the needle action lever further clockwise to release the lever. Click NEXT. - -[Caution] - -- If you go to the next step without the buzzer sounding, a needle insertion error warning will appear. - -## Discarding the patch -Patches must be replaced in the case of low insulin levels, usage expiration, and defects. The recommended usage period for each patch is 84 hours after booting the patch. - -### Discarding the patch -Select EOPATCH2 at the top of the home screen and click the DISCARD/CHANGE PATCH button at the bottom. On the next screen, click the DISCARD PATCH button. A dialog box appears to confirm once more and if you select the DISCARD PATCH button, the disposal is completed. - -![Bild13](../../images/EOPatch/Bild13.png) ![Bild14](../../images/EOPatch/Bild14.png) ![Bild15](../../images/EOPatch/Bild15.png) ![Bild16](../../images/EOPatch/Bild16.png) - -## Suspending and Resuming Insulin Delivery -Suspending insulin delivery also cancels both extended bolus and temporary basal. When resuming insulin delivery, the canceled extended bolus and temporary basal will not be resumed. And when insulin delivery is suspended, the patch will give a sound every 15 minutes. - -### Suspending insulin delivery -Select EOPATCH2 at the top of the home screen and click the SUSPEND button at the bottom right. When you select CONFIRM in the confirmation box, a time selection box appears. If you select the CONFIRM button after selecting the time, the insulin delivery will be suspended for the set amount of time. - -![Bild17](../../images/EOPatch/Bild17.png) ![Bild18](../../images/EOPatch/Bild18.png) ![Bild19](../../images/EOPatch/Bild19.png) - - -### Resuming insulin delivery -Select EOPATCH2 at the top of the home screen and click the RESUME button at the bottom right. Insulin delivery will resume by selecting CONFIRM in the confirmation dialog box. - -![Bild20](../../images/EOPatch/Bild20.png) ![Bild21](../../images/EOPatch/Bild21.png) - -## Alarms/Warnings - -### Alarm - -Alarms are issued for emergency situations of the highest priority and require immediate action. The alarm signal does not disappear or time out until it is acknowledged. An alarm occurs when there is a problem with the patch being used, so there may be cases where the patch in use needs to be discarded and replaced with a new patch. The warning is displayed as a dialog box and switching to another screen is not possible until processing is completed. - -![Bild22](../../images/EOPatch/Bild22.png) ![Bild23](../../images/EOPatch/Bild23.png) - -The different types of alarms are explained below. - -| Alarms | Explanation | -| -------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| Empty reservoir | Occurs when the patch’s reservoir runs out of insulin. | -| Patch expired | Occurs when the patch usage time has expired, and no further insulin injections are possible. | -| Occlusion | Occurs when it appears that the patch's insulin inlet is clogged. | -| Power on self-test failure | Occurs when the patch finds an unexpected error during the post-boot self-test process. | -| Inappropriate temperature | Occurs when the patch is outside the normal operating temperature range during patch application and use. To deal with this alarm, move the patch to an appropriate operating temperature (4.4 to 37°C) condition. | -| Needle insertion Error | Occurs when needle insertion is not normal during the patch application process. Check that the needle insertion edge of the patch and the needle activation button are in a straight line. | -| Patch battery Error | Occurs just before the patch’s internal battery runs out and powers off. | -| Patch activation Error | Occurs when the app fails to complete the patching process within 60 minutes after the patch is booted. | -| Patch Error | Occurs when the patch encounters an unexpected error while applying and using the patch. | - -### Warning - -A warning occurs in a medium or low-priority situation. When a warning occurs, it is displayed as a notification in the Overview screen. - -![Bild24](../../images/EOPatch/Bild24.png) - -The different types of warnings are explained below. - -| Warnings | Explanation | -| ---------------------------- | ------------------------------------------------------------------------------------------------------------------------------------- | -| End of insulin suspend | Occurs when the time set by the user has elapsed after the insulin infusion suspension has been completed. | -| Low reservoir | Occurs when the remaining amount of insulin in the patch is below the set amount. | -| Patch operating life expired | Occurs when the patch usage period is over. | -| Patch will expire soon | Occurs 1 hour before the patch must be discarded. | -| Incomplete Patch activation | Occurs when more than 3 minutes have elapsed due to an interruption during patch application in the stage after pairing is completed. | -| Patch battery low | Occurs when the patch's battery is low. | - diff --git a/docs/CROWDIN/pb/Getting-Started/ClosedLoop.md b/docs/CROWDIN/pb/Getting-Started/ClosedLoop.md deleted file mode 100644 index a0b695f14389..000000000000 --- a/docs/CROWDIN/pb/Getting-Started/ClosedLoop.md +++ /dev/null @@ -1,55 +0,0 @@ -# O que é um Sistema de Loop Fechado? - -![AAPS é como um piloto automático](../images/autopilot.png) - -Um sistema de pâncreas artificial de loop fechado combina diversos componentes para facilitar o gerenciamento do diabetes para você. In her great book [Automated Insulin Delivery](https://www.artificialpancreasbook.com/) Dana M. Lewis, one of the founders of the open source closed loop movement, calls it an ["autopilot for your diabetes"](https://www.artificialpancreasbook.com/3.-getting-started-with-your-aps). Mas o que isso significa? - -**Autopilot in an aircraft** - -O piloto automático não faz o trabalho completo e não dá a possibilidade ao piloto de dormir ao longo de todo o voo. Ele facilita o trabalho dos pilotos. Liberta-os do fardo de uma vigilância constante do avião e da atitude de voo. Isto permite que o piloto se concentre no monitoramento do espaço aéreo e no controle das funções do piloto automático. - -O piloto automático recebe sinais de vários sensores, um computador avalia-os em conjunto com as especificações do piloto e então executa os ajustes necessários. O piloto não precisa mais se preocupar com os ajustes constantes. - -**Closed Loop System** - -O mesmo se aplica a um sistema de pâncreas artificial de loop fechado. Ele não faz todo o trabalho, você ainda tem de cuidar do seu diabetes. Um sistema de loop fechado combina os dados do sensor de um CGM/FGM com as especificações de gerenciamento de diabetes, como taxa de basal, fator de sensibilidade à insulina e relação de carboidratos. A partir daí, calcula as sugestões de tratamento e implementa esses pequenos ajustes permanentes a fim de manter seu diabetes dentro do intervalo de meta para aliviá-lo. Isso deixa mais tempo para a sua vida "ao lado do" diabetes. - -Assim como não quer entrar num avião onde apenas o piloto automático voa sem supervisão humana, um sistema de loop fechado ajuda-o com o gerenciamento do seu diabetes, mas sempre precisa do seu apoio! **Even with a closed loop you can't just forget your diabetes!** - -Assim como o piloto automático depende dos valores dos sensores e das especificações do piloto, um sistema de loop fechado precisa de entradas apropriadas, como taxas de basal, FS e I:C (relação número de gramas de carboidratos para uma unidade de insulina) para apoiar você com sucesso. - -## Sistemas de Pâncreas Artificial de Loop Fechado de Código Aberto - -Atualmente existem três principais sistemas de loop fechado de código aberto disponíveis: - -### AndroidAPS (AAPS) - -AAPS is described in detail in [this documentation](./WhatisAndroidAPS.html). Ele usa um Smartphone Android para cálculo e controle da sua bomba de insulina. It is in strong collaboration with OpenAPS (i.e. they share algorithms). - -Compatible [pumps](../Hardware/pumps.md) are: - -- [DanaR](../Configuration/DanaR-Insulin-Pump.md) / [DanaRS & Dana-i](../Configuration/DanaRS-Insulin-Pump.html) -- [Accu-Chek Combo](../Configuration/Accu-Chek-Combo-Pump.md) -- [Accu-Chek Insight](../Configuration/Accu-Chek-Insight-Pump.md) -- [Diaconn G8](../Configuration/DiaconnG8.md) -- [Omnipod DASH](../Configuration/OmnipodDASH.md) -- [Omnipod Eros](../Configuration/OmnipodEros.md) -- some old [Medtronic pumps](../Configuration/MedtronicPump.md) - -### OpenAPS - -[OpenAPS](https://openaps.readthedocs.io) was the first Open Source Closed Loop System. Ele usa um pequeno computador como Raspberry Pi ou Intel Edison. - -Bombas compatíveis: - -- some old Medtronic pumps - -### Loop para iOS - -[Loop for iOS](https://loopkit.github.io/loopdocs/) is the Open Source Closed Loop System to be used with Apple iPhones. - -Bombas compatíveis: - -- Omnipod DASH -- Omnipod Eros -- some old Medtronic pumps diff --git a/docs/CROWDIN/pb/Getting-Started/Safety-first.md b/docs/CROWDIN/pb/Getting-Started/Safety-first.md deleted file mode 100644 index 7fafc63e68a3..000000000000 --- a/docs/CROWDIN/pb/Getting-Started/Safety-first.md +++ /dev/null @@ -1,41 +0,0 @@ -# Safety first - -**When you decide to build your own artificial pancreas, it's always important to think about security and safety, and to understand the impact of all your actions** - -## Geral - -- AAPS is a just a tool to help you manage diabetes, it is not a fully automated system you can install and forget! -- Do not assume that AAPS will never make mistakes. This device is taking control of your insulin delivery: Watch it all the time, understand how it works, and learn how to interpret its actions. -- Remember that, once paired, the phone can instruct the pump to do anything. Only use this phone for AAPS and, if being used by a child, essential communications. Do not install unnecessary apps or games (!!!) which could introduce malware such as trojans, viruses, or bots that could interfere with your system. -- Install all security updates provided by your phone manufacturer and Google. -- You might also need to change your diabetes habits as you change your therapy by using a closed loop system. I.e. some people report, they need less hypo treatments as AAPS has already reduced insulin. - -## SMS Communicator - -- AAPS allows you to control a child's phone remotely via text message. If you enable this SMS Communicator, always remember that the phone set up to give remote commands could be stolen. So always protect it at least by a PIN code. -- AAPS will also inform you by text message if your remote commands, such as a bolus or a profile change, have been carried out. It is advisable to set this up so that confirmation texts are sent to at least two different phone numbers in case one of the receiving phones is stolen. - -(Safety-first-aaps-can-also-be-used-by-blind-people)= -## AAPS can also be used by blind people - -On Android devices TalkBack is part of the operating system. It is a program for screen orientation via voice output. With TalkBack you can operate your smartphone as well as AAPS blind. - -We users create the AAPS app ourselves with Android Studio. Many use Microsoft Windows for this purpose, where there is the Screenreader analogous to TalkBack. Since Android Studio is a Java application, the "Java Access Bridge" component must be enabled in the Control Panel. Otherwise, the screen reader of the PC will not speak in Android Studio. - -To do this, please proceed as follows: - -- Press WINDOWSTASTE and enter "Control Panel" in the search field, open with Enter. It opens: "All Control Panel Items". -- Press the letter C to get to "Center for Ease of Use", open with Enter. -- Then open "Use computer without a screen" with Enter. -- There, at the bottom, you will find the checkbox "Enable Java Access Bridge", select it. -- Done, just close the window! The screen reader should work now. - -```{note} -**IMPORTANT SAFETY NOTICE** - -The foundation of AAPS safety features discussed in this documentation is built on the safety features of the hardware used to build your system. It is critically important that you only use a tested, fully functioning FDA or CE approved insulin pump and CGM for closing an automated insulin dosing loop. Hardware or software modifications to these components can cause unexpected insulin dosing, causing significant risk to the user. If you find or get offered broken, modified or self-made insulin pumps or CGM receivers, *do not use* these for creating an AAPS system. - -Additionally, it is equally important to only use original supplies such as inserters, cannulas and insulin containers approved by the manufacturer for use with your pump or CGM. Using untested or modified supplies can cause CGM inaccuracy and insulin dosing errors. Insulin is highly dangerous when misdosed - please do not play with your life by hacking with your supplies. - -Last not least, you must not take SGLT-2 inhibitors (gliflozins) as they incalculably lower blood sugar levels. The combination with a system that lowers basal rates in order to increase BG is especially dangerous as due to the gliflozin this rise in BG might not happen and a dangerous state of lack of insulin can happen. -``` diff --git a/docs/CROWDIN/pb/Getting-Started/Sample-Setup.md b/docs/CROWDIN/pb/Getting-Started/Sample-Setup.md deleted file mode 100644 index 2da9e4bf5a38..000000000000 --- a/docs/CROWDIN/pb/Getting-Started/Sample-Setup.md +++ /dev/null @@ -1,151 +0,0 @@ -# Sample setup: Samsung S7, Dana RS, Dexcom G6 and Sony Smartwatch - -![Sample Setup](../images/SampleSetup.png) - -## Description - -In this setup, the Samsung Galaxy S7 smartphone is used as control center of the loop. The slightly modified Dexcom App reads glucose values from the Dexcom G6 CGM. AndroidAPS is used to control the Dana RS insulin pump from Korean manufacturer SOOIL via bluetooth. Further devices are not required. - -As the Dexcom App only offers limited alarm options the open source app xDrip+ is used to define not only high and low alarms but also additional alarms according to individual requirements. - -Optionally an Android wear smartwatch can be used (in this sample setup the Sony Smartwatch 3 (SWR50)) to display glucose and AndroidAPS values on your wrist. The watch can even be used to control AndroidAPS (i.e. discreetly set a meal bolus). - -The system works offline. This means there is no need for a data connection from the smartphone to the Internet for operation. - -Nevertheless, the data is automatically uploaded to Nightscout "in the cloud" when a data connection is established. By doing so you can provide comprehensive reports for the doctor's visit or share the current values with family members at any time. It is also possible to send data to Nightscout only when using a (predefined) Wi-Fi connection in order to profit from the different Nightscout reports. - -## Required components - -1. Samsung Galaxy S7 - - * Alternatives: see [list of tested phones and watches](https://docs.google.com/spreadsheets/d/1gZAsN6f0gv6tkgy9EBsYl0BQNhna0RDqA9QGycAqCQc/edit) for AndroidAPS - -2. [DanaRS](http://www.sooil.com/eng/product/) - - * Alternatives: - * [Accu-Chek Combo](../Configuration/Accu-Chek-Combo-Pump.md) - * [Accu-Chek Insight](../Configuration/Accu-Chek-Insight-Pump.md) - * [DanaR](../Configuration/DanaR-Insulin-Pump.md) - * [Some old Medtronic pumps (additionally needed: RileyLink/Gnarl hardware, Android Phone with bluetooth low energy / BLE-chipset)](../Configuration/MedtronicPump.md) - * Other pumps might be available in the future, see [future possible pump drivers](Future-possible-Pump-Drivers.md) for details. - -3. [Dexcom G6](https://dexcom.com) - - * Alternatives: see list of possible [BG sources](../Configuration/BG-Source.md) - -4. Optional: Sony Smartwatch 3 (SWR50) - - * Alternatives: All [watches with Google Wear OS](https://wearos.google.com/intl/de_de/#find-your-watch) should work fine, for details see [list of tested phones and watches](https://docs.google.com/spreadsheets/d/1gZAsN6f0gv6tkgy9EBsYl0BQNhna0RDqA9QGycAqCQc/edit) for AndroidAPS (OS must be Android Wear) - -## Nightscout setup - -See detailed [Nightscout setup](../Installing-AndroidAPS/Nightscout.md) - -## Computer setup - -To be able to create an Android app from the freely available AAPS open source code you need Android Studio on your computer or notebook (Windows, Mac, Linux). A detailed instruction can be found at [building the APK](../Installing-AndroidAPS/Building-APK.md). - -Please be patient when installing Android Studio as the software downloads a lot of additional data once installed on your computer. - -## Smartphone setup - -![Smartphone](../images/SampleSetupSmartphone.png) - -### Check smartphone firmware - -* Menu > Settings > Phone info > Software info: At least "Android-Version 8.0" (successfully tested up to Android version 8.0.0 Oreo - Samsung Experience Version 9.0) -* For firmware update: menu > Preferences > software update - -### Allow installation from unknown sources - -Menu > Settings > Device security > Unknown sources > slider to right side (= active) - -For security reasons this setting should be set back to inactive once the installation of all apps described here has been completed. - -### Enable Bluetooth - -1. Menu > Settings > Connections > Bluetooth > slider to right side (= active) -2. Menu > Settings > Connections > Location > slider to right side (= active) - -Location services ("GPS") must be activated in order for Bluetooth to work properly. - -### Install Dexcom App (modified version) - -![Dexcom App patched](../images/SampleSetupDexApp.png) - -The original Dexcom app from the Google Play Store will not work because it does not broadcast the values to other apps. Therefore, a version slightly modified by the community is required. Only this modified Dexcom app can communicate with AAPS. Additionally the modified Dexcom App can be used with all Android smartphones not only the ones in [Dexcom's compatibility list](https://www.dexcom.com/dexcom-international-compatibility). - -To do this perform the following steps on your smartphone: - -1. If the original Dexcom app is already installed: - * Stop sensor - * Uninstall app via Menu > Settings > Apps > Dexcom G6 Mobile > Uninstall -2. Download and install the [BYODA Dexcom ap](../Hardware/DexcomG6.md#if-using-g6-with-build-your-own-dexcom-app) -3. Start modified Dexcom G6 app, activate/calibrate the sensor according to the given instructions and wait until the warm-up phase is finished. -4. Once the modified Dexcom app shows actual glucose value, setup the warnings (hamburger menu on top left side of the screen) as follows: - * Urgent low `55mg/dl` / `3.1mmol/l` (cannot be disabled) - * Low `OFF` - * High `OFF` - * Rise rate `OFF` - * Fall rate `OFF` - * Signal loss `OFF` - -## Install AndroidAPS - -1. Follow the instructions to [build the APK](../Installing-AndroidAPS/Building-APK.md#generate-signed-apk) -2. [Transfer](../Installing-AndroidAPS/Building-APK.md#transfer-apk-to-smartphone) the generated APK to your phone -3. [Configure AndroidAPS](../Configuration/Config-Builder.md) according to your needs using the setup assistant or manually -4. In this sample setup we used (among others) - -* BG source: `Dexcom G6 App (patched)` -- click cock-wheel and activate `Upload BG data to NS` and `Send BG data to xDrip+` (see [BG source](../Configuration/BG-Source.md)) - -![G5 Settings](../images/SampleSetupG5Settings.png) - -* NS Client activated (see [Nightscout setup](../Installing-AndroidAPS/Nightscout.md)) - -## Install xDrip+ - -xDrip+ is another mature open source app that offers countless possibilities. In this setup, contrary to what the developers first wrote the app for, xDrip+ is not used to collect glucose data from the Dexcom G6, but only to output alarms and to display the current glucose value including the curve on the Android home screen in the widget. With xDrip+ the alarms can be set much more individually than with the Dexcom software, AAPS or Nightscout (no limitation in the selection of sounds, different alarms depending on day/night time etc.). - -1. Download the latest stable APK version of xDrip+ with your smartphone - not the version from the Google Play Store! -2. Install xDrip+ by selecting the downloaded APK file. -3. Start xDrip+ and make the following settings (hamburger menu at top left) - * Settings > Alarms and Alerts > Glucose Level Alert List > Create Alerts (high and low) according to your needs. - * The existing alarms can be changed with a long press on the alarm. - * Settings > Alarms and Alerts > Calibration Alerts: disabled (reminded via the modified Dexcom app) - * Settings > Hardware Data Source > 640G/EverSense - * Settings > Inter-app settings > Accept Calibrations > `ON` - * Menu > Start sensor (is only "pro forma" and has nothing to do with the running G6 sensor. This is necessary otherwise an error message will appear regularly.) - -For more information about xDrip+, see here [BG source page](../Configuration/BG-Source.md). - -### Example of an alarm setup - -The "Urgent low alarm" (below 55 mg/dl resp. 3,1 mmol) is a standard alarm from the modified Dexcom app that cannot be disabled. - -![xDrip alarms](../images/SampleSetupxDripWarning.png) - -Tip for meetings / church visits / cinema etc..: - -If "Do not disturb" mode is activated in the Samsung Galaxy S7 (Menu > Settings > Sounds and vibration > Do not disturb: slider to right side (= active)), the phone only vibrates during urgent low alarm and does not issue an acoustic warning. For the other alarms set up via xDrip+ you can select whether the silent mode should be ignored (acoustic sound played) or not. - -## Disable power saving option - -On your Samsung Galaxy S7 go to Menu > Settings > Device Maintenance > Battery > Unmonitored Apps > + Add apps: Select the apps AndroidAPS, Dexcom G6 Mobile, xDrip+ and Android Wear (if smartwatch is used) one after the other - -## Optional: Setup Sony Smartwatch 3 (SWR50) - -With an Android Wear smartwatch life with diabetes can be made even more inconspicuous. The watch can be used to display the current glucose level, the status of the loop etc. on the wrist. The watch can even be used to control AndroidAPS (i.e. discreetly set a meal bolus). To do this, double tap the CGM value of the AAPSv2 watchface. The SWR50 usually runs for a full day until the battery needs to be recharged (same charger as the Samsung Galaxy S7: microUSB). - -![Smartwatch](../images/SampleSetupSmartwatch.png) - -Details about the information displayed on the watchface can be found [here](../Configuration/Watchfaces.md). - -* Install the app "Android Wear" on your smartphone via the Google Play Store and connect the smartwatch according to the instructions there. -* In AAPS choose hamburger menu (top left corner) > Config Builder > General (at the bottom of the list) > Wear > activate on left side, click cock wheel > Wear settings and activate `Controls from Watch` -* On your smartwatch: Long press display to change watchface and select `AAPSv2` -* If necessary restart both devices once. - -## Pump setup - -see [Dana RS pump](../Configuration/DanaRS-Insulin-Pump.md) \ No newline at end of file diff --git a/docs/CROWDIN/pb/Getting-Started/WhatisAndroidAPS.md b/docs/CROWDIN/pb/Getting-Started/WhatisAndroidAPS.md deleted file mode 100644 index b10d73731578..000000000000 --- a/docs/CROWDIN/pb/Getting-Started/WhatisAndroidAPS.md +++ /dev/null @@ -1,39 +0,0 @@ -# What is a closed loop system with AAPS? - -AAPS is an app that acts as an artificial pancreas system (APS) on an Android smartphone. What is an artificial pancreas system? It is a software program that aims to do what a living pancreas does: keep blood sugar levels within healthy limits automatically. - -An APS can't do the job as well as a biological pancreas does, but it can make type 1 diabetes easier to manage using devices that are commercially available and software that is simple and safe. Those devices include a continuous glucose monitor (CGM) to tell AAPS about your blood sugar levels and an insulin pump which AAPS controls to deliver appropriate doses of insulin. The app communicates with those devices via bluetooth. It makes its dosing calculations using an algorithm, or set of rules, developed for another artificial pancreas system, called OpenAPS, which has thousands of users and has accumulated millions of hours of use. - -A note of caution: AAPS is not regulated by any medical authority in any country. Using AAPS is essentially carrying out a medical experiment on yourself. Setting up the system requires determination and technical knowledge. If you don't have the technical know-how at the beginning, you will by the end. All the information you need can be found in these documents, elsewhere online, or from others who have already done it -- you can ask them in Facebook groups or other forums. Many people have successfully built AAPS and are now using it entirely safely, but it is essential that every user: - -- Builds the system themselves so that they thoroughly understand how it works -- Adjusts its individual dosage algorithm with his or her diabetes team to work nearly perfect -- Maintains and monitors the system to ensure it is working properly - -```{note} -**Disclaimer and Warning** - -- All information, thought, and code described here is intended for informational and educational purposes only. Nightscout currently makes no attempt at HIPAA privacy compliance. Use Nightscout and AAPS at your own risk, and do not use the information or code to make medical decisions. -- Use of code from github.com is without warranty or formal support of any kind. Please review this repository's LICENSE for details. -- All product and company names, trademarks, servicemarks, registered trademarks, and registered servicemarks are the property of their respective holders. Their use is for information purposes and does not imply any affiliation with or endorsement by them. - -Please note - this project has no association with and is not endorsed by: [SOOIL](http://www.sooil.com/eng/), [Dexcom](https://www.dexcom.com/), [Accu-Chek, Roche Diabetes Care](https://www.accu-chek.com/), [Insulet](https://www.insulet.com/) or [Medtronic](https://www.medtronic.com/). -``` - -If you're ready for the challenge, please read on. - -## Primary goals behind AAPS - -- An app with safety built in. To read about the safety features of the algorithms, known as oref0 and oref1, click here () -- An all-in-one app for managing type 1 diabetes with an artificial pancreas and Nightscout -- An app to which users can easily add or remove modules as needed -- An app with different versions for specific locations and languages. -- An app which can be used in open- and closed-loop mode -- An app that is totally transparent: users can input parameters, see results, and make the final decision -- An app which is independent of particular pump drivers and contains a "virtual pump" so users can safely experiment before using it on themselves -- An app closely integrated with Nightscout -- An app in which the user is in control of safety constraints - -## How to start - -Of course, all of this content here is very important, but can be in the beginning quite confusing. A good orientation is given by the [Module Overview](../Module/module.md) and the [Objectives](../Usage/Objectives.html). diff --git a/docs/CROWDIN/pb/Hardware/DexcomG4.md b/docs/CROWDIN/pb/Hardware/DexcomG4.md deleted file mode 100644 index 3ac2b2b96f4b..000000000000 --- a/docs/CROWDIN/pb/Hardware/DexcomG4.md +++ /dev/null @@ -1,6 +0,0 @@ -# Dexcom G4 - -## If using G4 with OTG cable ('traditional' Nightscout) -- If not already set up then download Nightscout Uploader app from the Play Store and follow instructions on [Nightscout](https://nightscout.github.io/). -- In AAPS Preferences enter your Nightscout website and API secret. -- Select NSClient in ConfigBuilder (setting in AAPS). diff --git a/docs/CROWDIN/pb/Hardware/Smartwatch.md b/docs/CROWDIN/pb/Hardware/Smartwatch.md deleted file mode 100644 index 12281d6d256a..000000000000 --- a/docs/CROWDIN/pb/Hardware/Smartwatch.md +++ /dev/null @@ -1,10 +0,0 @@ -# Smartwatches - -Smartwatches are optional, but very useful for some users. More details are here: - -- [List of tested phones and smartwatches](../Getting-Started/Phones.md) -- [Watchfaces Wear OS](../Configuration/Watchfaces.md) -- [Troubleshooting Sony Smartwatch SW 3](../Usage/SonySW3.md) - -## Instructions for Building the AAPS Wear APK for Wear OS -https://androidaps.readthedocs.io/en/latest/remote-control.html#building-the-aaps-wear-apk diff --git a/docs/CROWDIN/pb/Installing-AndroidAPS/Building-APK.md b/docs/CROWDIN/pb/Installing-AndroidAPS/Building-APK.md deleted file mode 100644 index 8d964f4b41fc..000000000000 --- a/docs/CROWDIN/pb/Installing-AndroidAPS/Building-APK.md +++ /dev/null @@ -1,369 +0,0 @@ -# Building the APK - -## Build yourself instead of download - -**AAPS is not available as download due to regulation for medical devices. It is legal to build the app for your own use, but you must not give a copy to others! See [FAQ page](../Getting-Started/FAQ.md) for details.** - -## Important notes - -* Please use **[Android Studio Giraffe" (2022.3.1)](https://developer.android.com/studio/)** or newer to build the apk. -* [Windows 32-bit systems](troubleshooting_androidstudio-unable-to-start-daemon-process) are not supported by Android Studio - -(Building-APK-recommended-specification-of-computer-for-building-apk-file)= - -## Recommended specification of computer for building apk file - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
OS (Only 64 bit)Windows 8 or higherMac OS 10.14 or higherAny Linux supports Gnome, KDE, or Unity DE;  GNU C Library 2.31 or later

CPU (Only 64 bit)

x86_64 CPU architecture; 2nd generation Intel Core or newer, or AMD CPU with support for a
Windows Hypervisor		ARM-based chips, or 2nd generation Intel Core or newer with support for
Hypervisor.Framework		x86_64 CPU architecture; 2nd generation Intel Core or newer, or AMD processor with support for AMD Virtualization (AMD-V) and SSSE3

RAM

8GB or more

Disk

At least 30GB free space. SSD is recommended.

Resolution

1280 x 800 Minimum

Internet

Broadband

- -Please keep in mind that both **64 bit CPU and 64 bit OS are mandatory condition.** If your system DOES NOT meet this condition, you have to change affected hardware or software or the whole system. **It is strongly recommended to use SSD (Solid State Disk) instead of HDD (Hard Disk Drive) because it will take less time when you are building the APS installation apk file.** Recommended is just recommended and it is not a mandatory. However, you may still use a HDD when you are building apk file but note that the building process can take a long time to complete, although once started, you can leave it running unattended. - -* * * - -### This article is divided into two parts. - -* In the overview part there is an explanation on what steps are necessary to build the APK file. -* In the step by step walkthrough part you will find the screenshots of a concrete installation. Because the versions of Android Studio - the software development environment which we will use to build the APK - will change very quickly this will be not identical to your installation but it should give you a good starting point. Android Studio also runs on Windows, Mac OS X and Linux and there might be small differences in some aspects between each platform. If you find that something important is wrong or missing, please inform the facebook group "AAPS users" or in the Discord chat [Android APS](https://discord.gg/4fQUWHZ4Mw) so that we can have a look at this. - -## Overview - -In general, the steps necessary to build the APK file: - -1. [Install git](../Installing-AndroidAPS/git-install.md) -2. [Install Android Studio](Building-APK-install-android-studio) -3. [Set git path in Android Studio preferences](Building-APK-set-git-path-in-preferences) -4. [Download AAPS code](Building-APK-download-AAPS-code) -5. [Download Android SDK](Building-APK-download-android-sdk) -6. [Build the app](Building-APK-generate-signed-apk) (generate signed apk) -7. [Transfer apk file to your phone](Building-APK-transfer-apk-to-smartphone) -8. [Identify receiver if using xDrip+](xdrip-identify-receiver) - -## Step by step walkthrough - -Detailed description of the steps necessary to build the APK file. - -## Install git (if you don't have it) - -Follow the manual on the [git installation page](../Installing-AndroidAPS/git-install.md). - -(Building-APK-install-android-studio)= - -## Install Android Studio - -The following screenshots have been taken from Android Studio Version Arctic Fox | 2020.3.1. Screens can change in future versions of Android Studio. But you should be able to find your way through. [Help from the community](../Where-To-Go-For-Help/Connect-with-other-users.md) is provided. - -One of the most important things when installing Android Studio: **Be patient!** During installation and setup Android Studio is downloading a lot of stuff which will take its time. - -Download [Android Studio from here](https://developer.android.com/studio/install.html) and install it on your computer. - -On first start you will find the setup wizard: - -Select "Do not import settings" as you have not used it before. - -![Do not import settings](../images/studioSetup/01_ImportSettings.png) - -Decide whether you want to share data with Google or not. - -![Share data with Google](../images/studioSetup/02_DataSharing.png) - -On the following screen click "Next". - -![Welcome screen](../images/studioSetup/03_Welcome.png) - -Select "Standard" installation and click "Next". - -![Standard installation](../images/studioSetup/04_InstallType.png) - -Select the theme for the user interface you like. (In this manual we used "Light".) Then click "Next". - -> ***Note:*** This is just the color scheme. You can select whatever you like (i.e. "Darcula" for dark mode). This selection has no influence on building the APK but the following screenshots might look different. - -![UI color scheme](../images/studioSetup/05_UITheme.png) - -Click "Next" on the "Verify Settings" dialog. - -![Verify settings](../images/studioSetup/06_Overview.png) - -Click on all three license agreement parts and select "Agree". When you have agreed to all, the "Finish" button will be enabled and you can "Finish". - - ![Agree license agreements](../images/studioSetup/07_LicenseAgreement.png) - - -Wait while Android Studio downloads additional components and be patient. Once everything is downloaded button "Finish" turns blue. Click the button now. - -![Downloading components](../images/studioSetup/08_Downloading.png) - -(Building-APK-download-AAPS-code)= - -## Download AAPS code - -* On the Android Studio welcome screen select "Projects" (1) on the left and then "Get from VCS" (2). - - ![Android Studio wizard](../images/studioSetup/20_ProjectVCS.png) - - * If you already opened Android Studio and do not see the welcome screen anymore select File (1) > New (2) > Project from Version Control... (3) - - ![Check out project from version control within Android Studio](../images/AndroidStudio_FileNew.PNG) - - * We will now tell Android Studio were to get the code from: - - * Make sure you have selected "Repository URL" on the left (1). - - * Check if "Git" is selected as version control (2). - * Copy and paste the URL ```https://github.com/nightscout/AndroidAPS``` to the main AAPS repository into the URL textbox (3). - * Choose the directory where you want to save the cloned code (4). - - ![Clone Git](../images/studioSetup/21_CloneURL.png) - -* Click button "Clone" (5). - - ![Clone repository](../images/studioSetup/22_Cloning.png) - -* Do not click "Background" while repository is cloned! - -* After the repository is cloned successfully, Android Studio will open the cloned project. - -* You will be asked whether you want to trust the project. Click on "Trust project"! - - ![Trust project](../images/studioSetup/23_TrustProject.png) - -* In the status bar at the bottom you will see the information that Android Studio is running background tasks. - - ![Background tasks](../images/studioSetup/24_GradleSyncRunning.png) - -* Windows only: Grant access if your firewall is asking for permission. - - ![Firewall permission java](../images/AndroidStudio361_18.png) - -* Once the background tasks are finished you will probably see an error saying that errors occurred (1) or (2) or (3). - - ![SDK licence](../images/studioSetup/25_SyncFailed.png) - - Don't worry, this will be solved soon! - -(Building-APK-set-git-path-in-preferences)= - -## Set git path in preferences - -Make sure [git is installed](../Installing-AndroidAPS/git-install.md) on your computer and you have restarted your computer since installing. - -On the Android Studio welcome screen click "Customize" (1) on the left and then select the link "All settings..." (2): - -![Android Studio settings from welcome screen](../images/studioSetup/10_WizardSettings.png) - -### Windows - -* As windows user, make sure you have restarted your computer after [installing Git](../Installing-AndroidAPS/git-install.md). - -* In the menu, go to File (1) > Settings (2) (or Android Studio > Preferences on Mac). - - ![Open settings](../images/studioSetup/30_Settings.png) - -* Double-click "Version Control" (1) to open the sub-menu. - -* Click Git (2). -* Make sure update method "Merge" (3) is selected. -* Check if Android Studio can locate path to git.exe automatically by clicking the button "Test" (4). - - ![Android Studio settings](../images/studioSetup/11_GitPath.png) - -* If automatic setting is successful git version will be displayed next to the path. - - ![Git version displayed](../images/studioSetup/12_GitVersion.png) - -* Eventually git.exe cannot be found automatically or the Test will result in an error (1): - - ![Git not found](../images/studioSetup/13_GitVersionError.png) - - In this case click on the folder icon (2). - -* Use [search function](https://www.tenforums.com/tutorials/94452-search-file-explorer-windows-10-a.html) in windows explorer to find "git.exe" if you are unsure where git has been installed. You are looking for a file named "git.exe", located in **\bin** folder. - -* Select path to git.exe and make sure you selected the one in ** \bin\ ** folder (3) and click "OK" (4). - - ![Select git manually](../images/studioSetup/14_GitManualSelection.png) - -* Check your selected git path again with the "Test" button as described above. - -* When the git version is displayed next to the path (see screenshot above), close settings window by clicking "OK" button (5). - -### Mac - -* Any git version should work. For example . -* Use homebrew to install git: ```$ brew install git```. -* For details on installing git see the [official git documentation](https://git-scm.com/book/en/v2/Getting-Started-Installing-Git). -* If you install git via homebrew there is no need to change any preferences. Just in case: They can be found here: Android Studio - Preferences. - -(Building-APK-download-android-sdk)= - -## Download Android SDK - -* In the menu, go to File (1) > Settings (2) (or Android Studio > Preferences on Mac). - - ![Open settings](../images/studioSetup/30_Settings.png) - -* Double-click on Languages & Frameworks to open its submenu (1). - -* Select Android SDK (2). -* Tick the box left of "Android 9.0 (Pie)" (3) (API Level 28). - - ![SDK settings](../images/studioSetup/31_AndroidSDK.png) - -* Confirm changes by clicking OK. - - ![Confirm SDK changes](../images/studioSetup/32_ConfirmSDK.png) - -* Wait until the SDK download and installation is finished. - - ![Wait during SDK installation](../images/studioSetup/34_DownloadSDK.png) - -* When SDK installation is completed the "Finish" button will turn blue. Click this button. - - ![Finish SDK installation](../images/studioSetup/35_DownloadSDKfinished.png) - -* Android Studio might recommend to update the gradle system. **Never update gradle!** This will lead to difficulties! - -* If you see an information on the lower right side of your Android Studio window that Android Gradle Plugin is ready to update click on the text "upgrade" (1). - - ![No gradle update](../images/studioSetup/36_GradleUpdateRequest.png) - -* In the dialog box the select "Don't remind me again for this project" (2). - - ![No gradle update](../images/studioSetup/37_GradleUpdateDeny.png) - -* Restart Android Studio before you continue. - -(Building-APK-generate-signed-apk)= - -## Generate signed APK - -Signing means that you indicate your app to be your own creation but in a digital way as a kind of digital fingerprint within the app itself. That is necessary because Android has a rule that it only accepts signed code to run for security reasons. For more information on this topic, follow [this link](https://developer.android.com/studio/publish/app-signing.html#generate-key). - -* After Android Studio is started, wait until all background tasks are finished. - - ![Wait for background tasks](../images/studioSetup/40_BackgroundTasks.png) - - * ***Warning:*** If errors occur, do not continue with the following steps. \ Consult the [troubleshooting section](../Installing-AndroidAPS/troubleshooting_androidstudio) for known problems! - - ![Gradle Sync Error](../images/studioSetup/41_GradleSyncError.png) - -* Click "Build" (1) in the menu bar and select "Generate Signed Bundle / APK..." (2). - - ![Build apk](../images/studioSetup/42_MenuBuild.png) - -* Select "APK" (1) instead of "Android App Bundle" and click "Next" (2). - - ![APK instead of bundle](../images/studioSetup/43_Apk.png) - -* Make sure that module is set to "AndroidAPS.app" (1). - -* Click "Create new..." (2) to start creating your key store. - - ***Note:*** A key store in this case is nothing more than a file in which the information for signing is stored. It is encrypted and the information is secured with passwords. - - ![Create key store](../images/studioSetup/44_KeystoreNew.png) - -* Click the folder symbol to select a path on your computer for your key store. - - ![Create key store](../images/studioSetup/45_KeystoreDialog.png) - -* Select the path where your key store shall be saved (1). - - ![Create key store](../images/studioSetup/46_KeystorePath.png) - - ***Warning: Do not save in same folder as project. You must use a different directory!*** A good location would be your home folder. - -* Type a file name for your key store (2) and confirm with "OK" (3). - -* Enter (2) and confirm (3) the password for your key store. ![Select key store path](../images/studioSetup/47_KeystoreDialog.png) - - ***Note:*** Passwords for key store and key do not have to be very sophisticated. Make sure to remember those or make a note in a safe place. In case you will not remember your passwords in the future, see [troubleshooting for lost key store](troubleshooting_androidstudio-lost-keystore). - -* Enter an alias (4) for your key. Choose whatever you like. - -* Enter (5) and confirm (6) the password for your key - -* Validity (7) is 25 years by default. You do not have to change the default value. - -* First and last name must be entered (8). All other information is optional. - -* Click "OK" (9) when you are done. - -* Make sure the box to remember passwords is checked (1). So you don't have to enter them again next time you build the apk (i.e. when updating to a new AAPS version). - -* Click "Next" (2). - - ![Remember passwords](../images/studioSetup/48_KeystoreSave.png) - -* Select build variant "fullRelease" (1) and press "Finish". - - ![Select build variant](../images/studioSetup/49_BuildVariant.png) - -* Android Studio will show "Gradle Build running" at the bottom. This takes some time, depending on your computer and internet connection. **Be patient!** - - ![Gradle Running](../images/studioSetup/50_GradleRunning.png) - -* Android Studio will display the information "Generate Signed APK" after build is finished. - - ![Build finished](../images/studioSetup/51_BuildFinished.png) - -* In case build was not successful refer to the [troubleshooting section](../Installing-AndroidAPS/troubleshooting_androidstudio). - -* Click on the notification to expand it. - -* Click on the link "locate". - - ![Locate build](../images/studioSetup/52_BuildLocate.png) - - * If the notification is gone, you can always open the "Event log" and select the same link there. ![Build successfully - event log](../images/studioSetup/53_EventLog.png) - -* Your file manager/explorer will open. Navigate to the directory "full" (1) > "release" (2). - - ![File location apk](../images/studioSetup/54_APKlocation.png) - -* "app-full-release.apk" (3) is the file you are looking for! - -(Building-APK-transfer-apk-to-smartphone)= - -## Transfer APK to smartphone - -Easiest way to transfer app-full-release.apk to your phone is via [USB cable or Google Drive](https://support.google.com/android/answer/9064445?hl=en). Please note that transfer by mail might cause difficulties and is not the preferred way. - -On your phone you have to allow installation from unknown sources. Manuals how to do this can be found on the internet (i.e. [here](https://www.expressvpn.com/de/support/vpn-setup/enable-apk-installs-android/) or [here](https://www.androidcentral.com/unknown-sources)). - -## Troubleshooting - -See separate page [troubleshooting Android Studio](../Installing-AndroidAPS/troubleshooting_androidstudio). \ No newline at end of file diff --git a/docs/CROWDIN/pb/Sandbox/sandbox2.md b/docs/CROWDIN/pb/Sandbox/sandbox2.md deleted file mode 100644 index 33c547956c89..000000000000 --- a/docs/CROWDIN/pb/Sandbox/sandbox2.md +++ /dev/null @@ -1,43 +0,0 @@ -# internal sandbox file 2 for testing - -```{admonition} no need to translate this -:class: note - -No need to translate this. -``` - -This is an internal sandbox file for the documentation team to test - -1. markdown syntax and - -1. background process for - 1. CROWDIN translation and - 2. Read The Docs deployment. - -You can dirctly jump from here to the first label in the sandbox1.md file - ["Jump"](sandbox1-this-is-a-test). - -You can dirctly jump from here to the second label in this file - ["Jump"](sandbox1-this-is-another-test). - -Here you can jump to the first sandbox file - ["Jump"](./sandbox1.md). - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -(sandbox2-this-is-a-test)= -## This is a test - -This is a test if labels must be unique. - -### This is spare information from the docs - -cut from index: - -There are "limits" set in place when you are first beginning your AAPS journey. These safety limits have been developed over many years by observations of the inadvertent mistakes that new users are most likely to make when first learning to set up, build, and then successfully loop with AAPS - as most often those mistakes occur simply because the user was so excited to get started using the system that they may have forgotten to sit down and dedicate the time needed to understand the information within this documentation thoroughly. - - -### spare info from the overview to put into "preparing" - -Since the requirements are very different from anything you might have set up in the past, we recommend that you really follow the instructions, step-by-step the first few times you build the app, so that you have a stronger sense of how the app building process is supposed to behave when all directions are followed exactly. Please remember to take your time. Later this will go very quickly when you build the app again for a new version. That way you will have a greater chance of noticing when something doesn't going as planned before too many steps are out of line. It is important to save the your keystore file (.jks file used to sign your app) in a safe place, so that you can always use that exact same keystore file and password each and every time you are asked to create a new updated version of AAPS, as this file is what makes sure that each new version of the app "remembers" all the information that you have provided to it in previous versions of the app and thus ensure that the updates will go as smoothly as possible. On average, you can assume that there will be one new version and 2-3 required updates per year. This number is based on experience and may change in the future. But we do want to at least give you a general guideline on what to expect. When you are more experienced at building updated AAPS app versions all the steps that are required in building an updated app will only take 15-30 minutes, on average. However, in the beginning there can be a rather steep learning curve as these steps are not always considered intuitive by new users! So do not get frustrated if you find that it takes half a day or a whole day with some help from the community before you are finally finished with the update process. If you find that you are getting very frustrated just take a short break, and oftentimes; after a stroll around the block or two...you'll find that you are better able to approach the problem again. diff --git a/docs/CROWDIN/pb/Usage/Objectives.md b/docs/CROWDIN/pb/Usage/Objectives.md deleted file mode 100644 index c27b9c02a04c..000000000000 --- a/docs/CROWDIN/pb/Usage/Objectives.md +++ /dev/null @@ -1,184 +0,0 @@ -# Objectives - -AAPS has a series of Objectives that need to be completed to walk you through the features and settings of safe looping. They ensure you have configured everything detailed in the sections above correctly, and that you understand what your system is doing and why so you can trust it. - -If you are **upgrading phones** then you can [export your settings](../Usage/ExportImportSettings.md) to keep your progress through the objectives. Not only will your progress through the objectives be saved, but also your safety settings such as max bolus etc. If you do not export and import your settings then you will need to start the objectives from the beginning again. It is a good idea to [backup your settings](../Usage/ExportImportSettings.html) frequently just in case. - -If you want to go back in objectives see [explanation below](Objectives-go-back-in-objectives). - -## Objective 1: Setting up visualization and monitoring, analysing basals and ratios - -- Select the right blood glucose source for your setup. See [BG Source](../Configuration/BG-Source.md) for more information. -- Select the right Pump in ConfigBuilder (select Virtual Pump if you are using a pump model with no AAPS driver for looping) to ensure your pump status can communicate with AAPS. -- If using DanaR pump then ensure you have followed [DanaR Insulin Pump](../Configuration/DanaR-Insulin-Pump.md) instructions to ensure the link between pump and AAPS. -- You need to establish a data repository/reporting platform to complete this objective. That can be accomplished with either Nightscout or Tidepool (or both). Follow instructions at the [Nightscout](../Installing-AndroidAPS/Nightscout.md) or [Tidepool](../Installing-AndroidAPS/Tidepool.md) page for instructions. -- Note that URL in NSClient must be **WITHOUT /api/v1/** at the end - see [NSClient settings in Preferences](Preferences-nsclient). - -*You may need to wait for the next blood glucose reading to arrive before AAPS will recognise it.* - -## Objective 2: Learn how to control AAPS - -- Perform several actions in AAPS as described in this objective. - -- Click on the orange text "Not completed yet" to access the to-dos. - -- Links will be provided to guide you in case you are not familiar with a specific action yet. - - ```{image} ../images/Objective2_V2_5.png - :alt: Screenshot objective 2 - ``` - -(Objectives-objective-3-prove-your-knowledge)= - -## Objective 3: Prove your knowledge - -Objective 3 is a multiple choice test based on questions designed to test your theoretical knowledge of **AAPS**. - -Some users find Objective 3 to be the most difficult objective to complete. Please do read the AAPS documents in conjunction with the questions. If you are genuinely stuck after researching the **AAPS** documents, please search or ask for help on the Facebook or Discord group. These groups can provide friendly hints or redirect you to the relevant part of the **AAPS** documents. - -To proceed with Objective 3, click on the orange text “Not completed yet” to access the relevant question. Please read each question and select your answer(s). - - - -Within each question, a hyperlink to the **AAPS** documents will guide you to the relevant section of the document which you should read in order to locate the correct answer. - - -[Obj3_Screenshot 2023-12-05 223422](https://github.com/openaps/AndroidAPSdocs/assets/137224335/77347516-e24e-459d-98ab-acbb49a3d4e8)![image](https://github.com/openaps/AndroidAPSdocs/assets/137224335/ca756b8e-efbc-4427-b281-ac953ce16718) - - - -For each question, there may be more than one answer that is correct! If an incorrect answer is selected, the question will be time locked for a certain amount of time (60 minutes) before you can go back and answer the question. - - -After updating to a new version of **AAPS**, new questions may be added to cover a prevalent issue picked up by **AAPS** or alternatively to test your knowledge of a new feature of **AAPS** as released. - - -When **AAPS** is installed for the first time, you will have to complete Objective 3 entirely in order to move onto Objective 4. Each objective is required to be completed in sequential order. New features will gradually be unlocked as progress is made through the objectives. - -__What happens if new questions are added later to Objective 3?__ From time to time, new features are added to **AAPS** which may require a new question to be added to Objective 3. As a result, any new question added to Objective 3 will be marked as “incomplete” because **AAPS** will require you to action this. As each Objective is independent, you will not lose the existing functionality of **AAPS** providing the other objectives remain completed. - - -## Objective 4: Starting on an open loop - -- Select Open Loop either from Preferences, or by pressing and holding the Loop button in top left of the home screen. -- Work through the [Preferences](../Configuration/Preferences.md) to set up for you. -- Manually enact at least 20 of the temporary basal rate suggestions over a period of 7 days; input them to your pump and confirm in AAPS that you have accepted them. Ensure this data shows in AAPS and Nightscout. -- Enable [temp targets](../Usage/temptarget.md) if necessary. Use hypo temp targets to prevent that the system will correct too strong because of a raising blood glucose after a hypo. - -### Reduce number of notifications - -- To reduce the Number of decisions to be made while in Open Loop set wide target range like 90 - 150 mg/dl or 5,0 - 8,5 mmol/l. - -- You might even want to wider upper limit (or disable Open Loop) at night. - -- In Preferences you can set a minimum percentage for suggestion of basal rate change. - - ```{image} ../images/OpenLoop_MinimalRequestChange2.png - :alt: Open Loop minimal request change - ``` - -- Also, you do not need to act every 5 minutes on all suggestions... - -## Objective 5: Understanding your open loop, including its temp basal recommendations - -- Start to understand the thinking behind the temp basal recommendations by looking at the [determine basal logic](https://openaps.readthedocs.io/en/latest/docs/While%20You%20Wait%20For%20Gear/Understand-determine-basal.html) and both the [forecast line in AAPS homescreen](Screenshots-prediction-lines)/Nightscout and the summary of outputs from the calculations in your OpenAPS tab. - -You will want to set your target higher than usual until you are confident in the calculations and settings. System allows - -- a low target to be a minimum of 4 mmol (72 mg/dl) or maximum of 10 mmol (180 mg/dl) -- a high target to be a minimum of 5 mmol (90 mg/dl) and maximum of 15 mmol (225 mg/dl) -- a temporary target as a single value can be anywhere in the range of 4 mmol to 15 mmol (72 mg/dl to 225 mg/dl) - -The target is the value that calculations are based on, and not the same as where you aim to keep your blood glucose values within. If your target is very wide (say, 3 or more mmol \[50 mg/dl or more\] wide), you will often find little AAPS action. This is because blood glucose is eventually predicted to be somewhere in that wide range and therefore not many fluctuating temporary basal rates are suggested. - -You may want to experiment with adjusting your targets to be a closer together range (say, 1 or less mmol \[20 mg/dl or less\] wide) and observe how the behavior of your system changes as a result. - -You can view a wider range (green lines) on the graph for the values you aim to keep your blood glucose within by entering different values in [Preferences](../Configuration/Preferences.md) > Range for Visualisation. - -```{image} ../images/sign_stop.png -:alt: Stop sign -``` - -### Stop here if you are open looping with a virtual pump - do not click Verify at the end of this objective. - -```{image} ../images/blank.png -:alt: blank -``` - -(Objectives-objective-6-starting-to-close-the-loop-with-low-glucose-suspend)= -## Objective 6: Starting to close the loop with Low Glucose Suspend - -```{image} ../images/sign_warning.png -:alt: Warning sign -``` - -### Closed loop will not correct high BG values in objective 6 as it is limited to low glucose suspend. High BG values have to be corrected manually by you! - -- Prerequisite: You need a good profile (basal, ISF, IC) already working in AAPS to start with Loop in Low Glucose Suspend mode. Otherwise you can run in a hypo which you have to manually correct. This will help you a lot to avoid having to treat a low glucose over a period of 5 days. **If you are still having frequent or severe low glucose episodes then consider refining your DIA, basal, ISF and carb ratios and do NOT start objective 6 at this time.** -- You don't have to change your settings now. During objective 6, the maxIOB setting is internally set to zero automatically. **This override will be reversed when moving to objective 7.** -- The system will override your maxIOB settings to zero, which means if blood glucose is dropping it can reduce basal for you. If blood glucose is rising then it will only increase basal if the basal IOB is negative from a previous Low Glucose Suspend. Otherwise basal rates will remain the same as your selected profile. **That means that you have to manually handle high values with insulin corrections.** -- If your basal IOB is negative (see screenshot below) a TBR > 100% can be issued also in objective 6. - -```{image} ../images/Objective6_negIOB.png -:alt: Example negative IOB -``` - -- Set your target range slightly higher than you usually aim for, just to be safe and have a bit more scurity buffer. -- Enable 'Low Glucose Suspend' mode either by by pressing and holding the Loop icon at the top right corner of the home screen and selecting the Loop - LGS mode icon. -- Watch how temporary basals are active by viewing the blue basal text on the homescreen or the blue basal render on the homescreen graph. -- You may temporarily experience spikes following treated hypos without the ability to increase basal on the rebound. - -(Objectives-objective-7-tuning-the-closed-loop-raising-max-iob-above-0-and-gradually-lowering-bg-targets)= -## Objective 7: Tuning the closed loop, raising maxIOB above 0 and gradually lowering BG targets - -- Select 'Closed Loop' either from [Preferences](../Configuration/Preferences.md) or by pressing and holding the Loop icon at the top right corner of the home screen, over a period of 1 day. - -- Raise your 'Maximum total IOB OpenAPS can’t go over' (in OpenAPS called 'max-iob') above 0. The default recommendation is "average mealbolus + 3x max daily basal" (for the SMB algorithm) or "3x max daily basal" (for the older AMA algorithm) but you should slowly work up to this until you know your settings work for you (max daily basal = the maximum hourly value in any time segment of the day). - - This recommendation should be seen as a starting point. If you set to the 3x and you are seeing moves that push you too hard and fast then lower that number. If you are very resistant, raise it very little at a time. - - ```{image} ../images/MaxDailyBasal2.png - :alt: max daily basal - ``` - -- Once confident on how much IOB suits your looping patterns, then reduce your targets to your desired level. - -(Objectives-objective-8-adjust-basals-and-ratios-if-needed-and-then-enable-autosens)= -## Objective 8: Adjust basals and ratios if needed, and then enable autosens - -- You can use [autotune](https://openaps.readthedocs.io/en/latest/docs/Customize-Iterate/autotune.html) as a one off to check your basals remain accurate or do a traditional basal test. -- Enable [autosens](../Usage/Open-APS-features.md) over a period of 7 days and watch the white line on the homescreen graph show how your sensitivity to insulin may be rising or falling as a result of exercise or hormones etc. and keep an eye in the OpenAPS report tab how AAPS is adjusting the basals and/or targets accordingly. - -*Don’t forget to record your looping in* [this form](https://bit.ly/nowlooping) *logging AAPS as your type of DIY loop software, if you have not already done so.* - -(Objectives-objective-9-enabling-additional-oref1-features-for-daytime-use-such-as-super-micro-bolus-smb)= -## Objective 9: Enabling additional oref1 features for daytime use, such as super micro bolus (SMB) - -- You must read the [SMB chapter in this wiki](Open-APS-features-super-micro-bolus-smb) and [chapter oref1 in openAPSdocs](https://openaps.readthedocs.io/en/latest/docs/Customize-Iterate/oref1.html) to understand how SMB works, especially what's the idea behind zero-temping. -- Then you ought to [rise maxIOB](Open-APS-features-maximum-total-iob-openaps-cant-go-over-openaps-max-iob) to get SMBs working fine. maxIOB now includes all IOB, not just added basal. That is, if given a bolus of 8 U for a meal and maxIOB is 7 U, no SMBs will be delivered until IOB drops below 7 U. A good start is maxIOB = average mealbolus + 3x max daily basal (max daily basal = the maximum hourly value in any time segment of the day - see [objective 7](Objectives-objective-7-tuning-the-closed-loop-raising-max-iob-above-0-and-gradually-lowering-bg-targets) for an illustration) -- min_5m_carbimpact default in absorption settings has changed from 3 to 8 going from AMA to SMB. If you are upgrading from AMA to SMB, you have to change it manually. - -(Objectives-objective-10-automation)= -## Objective 10: Automation - -- You have to start objective 10 to be able to use [Automation](../Usage/Automation.md). -- Make sure you have completed all objectives including exam [Objectives-objective-3-prove-your-knowledge](Objectives#objective-3-prove-your-knowledge). -- Completing previous objectives will not effect other objectives you have already finished. You will keep all finished objectives! - -(Objectives-objective-11-DynamicISF)= -## Objective 11: Additional Features such as DynamicISF - -- You have to start objective 11 to be able to use [DynamicISF](../Usage/Open-APS-features.md) - -(Objectives-go-back-in-objectives)= -## Go back in objectives - -If you want to go back in objectives for whatever reason you can do so by clicking at "clear finished". - -```{image} ../images/Objective_ClearFinished.png -:alt: Go back in objectives -``` - -## Objectives in Android APS before version 3.0 - -One objective was removed when Android APS 3.0 was released. Users of Android APS version 2.8.2.1 who are on older Android software (i.e. earlier than version 9) will be using an older set of objectives which can be found [here](../Usage/Objectives_old.md). diff --git a/docs/CROWDIN/pb/Usage/Objectives_old.md b/docs/CROWDIN/pb/Usage/Objectives_old.md deleted file mode 100644 index a3dc8861eae2..000000000000 --- a/docs/CROWDIN/pb/Usage/Objectives_old.md +++ /dev/null @@ -1,152 +0,0 @@ -# Objectives as of Android APS 2.8.2.1 - -This is not the latest version of the Android APS Objectives. This page details the Objectives that were in place prior to version 3.0. Anyone using an older version of Android (i.e. prior to Android 9) and Android APS version 2.8.2.1 should refer to this page. - -Please see [this page](../Usage/Objectives.md) for the current set of Objectives. - -AndroidAPS has a series of Objectives that need to be completed to walk you through the features and settings of safe looping. They ensure you have configured everything detailed in the sections above correctly, and that you understand what your system is doing and why so you can trust it. - -If you are **upgrading phones** then you can [export your settings](../Usage/ExportImportSettings.md) to keep your progress through the objectives. Not only will your progress through the objectives be saved, but also your safety settings such as max bolus etc. If you do not export and import your settings then you will need to start the objectives from the beginning again. It is a good idea to [backup your settings](../Usage/ExportImportSettings.html) frequently just in case. - -If you want to go back in objectives see [explanation below](../Usage/Objectives.md#go-back-in-objectives). - -## Objective 1: Setting up visualization and monitoring, analysing basals and ratios - -- Select the right blood glucose source for your setup. See [BG Source](../Configuration/BG-Source.md) for more information. -- Select the right Pump in ConfigBuilder (select Virtual Pump if you are using a pump model with no AndroidAPS driver for looping) to ensure your pump status can communicate with AndroidAPS. -- If using DanaR pump then ensure you have followed [DanaR Insulin Pump](../Configuration/DanaR-Insulin-Pump.md) instructions to ensure the link between pump and AndroidAPS. -- Follow instructions in [Nightscout](../Installing-AndroidAPS/Nightscout.md) page to ensure Nightscout can receive and display this data. -- Note that URL in NSClient must be **WITHOUT /api/v1/** at the end - see [NSClient settings in Preferences](../Configuration/Preferences.md#nsclient). - -*You may need to wait for the next blood glucose reading to arrive before AndroidAPS will recognise it.* - -## Objective 2: Learn how to control AndroidAPS - -- Perform several actions in AndroidAPS as described in this objective. - -- Click on the orange text "Not completed yet" to access the to-dos. - -- Links will be provided to guide you in case you are not familiar with a specific action yet. - - ![Screenshot objective 2](../images/Objective2_V2_5.png) - -## Objective 3: Prove your knowledge - -- Pass a multiple-choice exam testing your AndroidAPS knowledge. - -- Click on the orange text "Not completed yet" to access the page with the question and answering options. - - ![Screenshot objective 3](../images/Objective3_V2_5.png) - -- Links will be provided to guide you in case you are unsure about the correct answers yet. - -- The questions for objective 3 have been completely rewritten by native speakers as of AAPS 2.8. The new ones cover the same basic topics plus a few new ones. - -- These new questions will lead to some not answered questions even though you have successfully completed objective 3 in previous versions. - -- Unanswered questions will affect you only if you start a new objective. In other words: If you have already completed all objectives you can wait and answer the new questions later without loosing AAPS functions. - -## Objective 4: Starting on an open loop - -- Select Open Loop either from Preferences, or by pressing and holding the Loop button in top left of the home screen. -- Work through the [Preferences](../Configuration/Preferences.md) to set up for you. -- Manually enact at least 20 of the temporary basal rate suggestions over a period of 7 days; input them to your pump and confirm in AndroidAPS that you have accepted them. Ensure this data shows in AndroidAPS and Nightscout. -- Enable [temp targets](../Usage/temptarget.md) if necessary. Use hypo temp targets to prevent that the system will correct too strong because of a raising blood glucose after a hypo. - -### Reduce number of notifications - -- To reduce the Number of decisions to be made while in Open Loop set wide target range like 90 - 150 mg/dl or 5,0 - 8,5 mmol/l. - -- You might even want to wider upper limit (or disable Open Loop) at night. - -- In Preferences you can set a minimum percentage for suggestion of basal rate change. - - ![Open Loop minimal request change](../images/OpenLoop_MinimalRequestChange2.png) - -- Also, you do not need to act every 5 minutes on all suggestions... - -## Objective 5: Understanding your open loop, including its temp basal recommendations - -- Start to understand the thinking behind the temp basal recommendations by looking at the [determine basal logic](https://openaps.readthedocs.io/en/latest/docs/While%20You%20Wait%20For%20Gear/Understand-determine-basal.html) and both the [forecast line in AndroidAPS homescreen](../Getting-Started/Screenshots.md#prediction-lines)/Nightscout and the summary of outputs from the calculations in your OpenAPS tab. - -You will want to set your target higher than usual until you are confident in the calculations and settings. System allows - -- a low target to be a minimum of 4 mmol (72 mg/dl) or maximum of 10 mmol (180 mg/dl) -- a high target to be a minimum of 5 mmol (90 mg/dl) and maximum of 15 mmol (225 mg/dl) -- a temporary target as a single value can be anywhere in the range of 4 mmol to 15 mmol (72 mg/dl to 225 mg/dl) - -The target is the value that calculations are based on, and not the same as where you aim to keep your blood glucose values within. If your target is very wide (say, 3 or more mmol \[50 mg/dl or more\] wide), you will often find little AAPS action. This is because blood glucose is eventually predicted to be somewhere in that wide range and therefore not many fluctuating temporary basal rates are suggested. - -You may want to experiment with adjusting your targets to be a closer together range (say, 1 or less mmol \[20 mg/dl or less\] wide) and observe how the behavior of your system changes as a result. - -You can view a wider range (green lines) on the graph for the values you aim to keep your blood glucose within by entering different values in [Preferences](../Configuration/Preferences.md) > Range for Visualisation. - -![Stop sign](../images/sign_stop.png) - -### Stop here if you are open looping with a virtual pump - do not click Verify at the end of this objective. - -![blank](../images/blank.png) - -## Objective 6: Starting to close the loop with Low Glucose Suspend - -![Warning sign](../images/sign_warning.png) - -### Closed loop will not correct high bg values in objective 6 as it is limited to low glucose suspend. High bg values have to be corrected manually by you! - -- Select Closed Loop either from [Preferences](../Configuration/Preferences.md) or by pressing and holding the Open Loop button in the top left of the home screen. - -- Set your target range slightly higher than you usually aim for, just to be safe. - -- Watch how temporary basals are active by viewing the blue basal text on the homescreen or the blue basal render on the homescreen graph. - -- Ensure your settings have supported AndroidAPS to avoid having to treat a low glucose over a period of 5 days. If you are still having frequent or severe low glucose episodes then consider refining your DIA, basal, ISF and carb ratios. - -- You don't have to change your settings. During objective 6 maxIOB setting is internally set to zero automatically. This override will be reversed when moving to objective 7. - -- The system will override your maxIOB settings to zero, which means if blood glucose is dropping it can reduce basal for you, but if blood glucose is rising then it will only increase basal if the basal IOB is negative (from a previous Low Glucose Suspend), otherwise basal rates will remain the same as your selected profile. - - ![Example negative IOB](../images/Objective6_negIOB.png) - -- If your basal IOB is negative (see screenshot above) a TBR > 100% can be issued also in objective 6. - -- You may temporarily experience spikes following treated hypos without the ability to increase basal on the rebound. - -## Objective 7: Tuning the closed loop, raising max IOB above 0 and gradually lowering BG targets - -- Raise your 'Maximum total IOB OpenAPS can’t go over' (in OpenAPS called 'max-iob') above 0 over a period of 1 day, the default recommendation is "average mealbolus + 3x max daily basal"(for SMB algorithm) or "3x max daily basal" (for older AMA algorithm) but you should slowly work up to this until you know your settings work for you (max daily basal = the maximum hourly value in any time segment of the day). - - This recommendation should be seen as a starting point. If you set to the 3x and you are seeing moves that push you to hard and fast then lower that number. If you are very resistant raise it a very little at a time. - - ![max daily basal](../images/MaxDailyBasal2.png) - -- Once confident on how much IOB suits your looping patterns then reduce your targets to your desired level. - -## Objective 8: Adjust basals and ratios if needed, and then enable autosens - -- You can use [autotune](https://openaps.readthedocs.io/en/latest/docs/Customize-Iterate/autotune.html) as a one off to check your basals remain accurate or do a traditional basal test. -- Enable [autosens](../Usage/Open-APS-features.md) over a period of 7 days and watch the white line on the homescreen graph show how your sensitivity to insulin may be rising or falling as a result of exercise or hormones etc. and keep an eye in the OpenAPS report tab how AndroidAPS is adjusting the basals and/or targets accordingly. - -*Don’t forget to record your looping in* [this form](https://bit.ly/nowlooping) *logging AndroidAPS as your type of DIY loop software, if you have not already done so.* - -## Objective 9: Try additional features for daytime use and gain confidence in your closed loop system - -- Before AAPS version 2.7 meal assist (MA) was the basic algorithm for AAPS and completing objective 8 was necessary to activate [advanced meal assist (AMA)](../Usage/Open-APS-features.md#advanced-meal-assist-ama). -- As [advanced meal assist (AMA)](../Usage/Open-APS-features.md#advanced-meal-assist-ama) is the standard algorithm from AAPS version 2.7 onwards use the following 28 days to try features you haven't used yet and get more confident with you closed loop system. - -## Objective 10: Enabling additional oref1 features for daytime use, such as super micro bolus (SMB) - -- You must read the [SMB chapter in this wiki](../Usage/Open-APS-features.md#super-micro-bolus-smb) and [chapter oref1 in openAPSdocs](https://openaps.readthedocs.io/en/latest/docs/Customize-Iterate/oref1.html) to understand how SMB works, especially what's the idea behind zero-temping. -- Then you ought to [rise maxIOB](../Usage/Open-APS-features.md#maximum-total-iob-openaps-cant-go-over-openaps-max-iob) to get SMBs working fine. maxIOB now includes all IOB, not just added basal. That is, if given a bolus of 8 U for a meal and maxIOB is 7 U, no SMBs will be delivered until IOB drops below 7 U. A good start is maxIOB = average mealbolus + 3x max daily basal (max daily basal = the maximum hourly value in any time segment of the day - see [objective 7](../Usage/Objectives#objective-7-tuning-the-closed-loop-raising-max-iob-above-0-and-gradually-lowering-bg-targets) for an illustration) -- min_5m_carbimpact default in absorption settings has changed from 3 to 8 going from AMA to SMB. If you are upgrading from AMA to SMB, you have to change it manually. - -## Objective 11: Automation - -- You have to start objective 11 to be able to use [Automation](../Usage/Automation.md). -- Make sure you have completed all objectives including exam [../Usage/Objectives.md#objective-3-prove-your-knowledge](../Usage/Objectives#objective-3-prove-your-knowledge). -- Completing previous objectives will not effect other objectives you have already finished. You will keep all finished objectives! - -## Go back in objectives - -If you want to go back in objectives for whatever reason you can do so by clicking at "clear finished". - -![Go back in objectives](../images/Objective_ClearFinished.png) diff --git a/docs/CROWDIN/pb/Usage/Smoothing-Blood-Glucose-Data-in-xDrip.md b/docs/CROWDIN/pb/Usage/Smoothing-Blood-Glucose-Data-in-xDrip.md deleted file mode 100644 index 716234b04a15..000000000000 --- a/docs/CROWDIN/pb/Usage/Smoothing-Blood-Glucose-Data-in-xDrip.md +++ /dev/null @@ -1,33 +0,0 @@ -(Smoothing-Blood-Glucose-Data-in-xDrip-smoothing-blood-glucose-data)= - -# Smoothing blood glucose data - -If BG data is jumpy/noisy, AAPS may dose insulin incorrectly resulting in high or low BG. For this reason it’s important to disable the loop until the problem is resolved. Depending on your CGM such issues may be due to the CGM’s configuration or sensor problems/site issues. You may need to replace your CGM sensor to resolve this. - -Some CGM systems have internal algorithms to detect the noise level in the readings and AAPS can use this information to avoid giving SMBs if the BG data is too unreliable. However, some CGMs do not transmit this data and for these BG sources 'Enable SMB always' and 'Enable SMB after carbs' are disabled for safety reasons. - -## Dexcom sensors - -### Build Your Own Dexcom App - -When using [BYODA](DexcomG6-if-using-g6-with-build-your-own-dexcom-app) your BG data is smooth and consistent. Furthermore you can take advantage of Dexcom back-smoothing. There are no restrictions in using SMBs, because the noise-level data is shared with AAPS. - -### xDrip+ with Dexcom G6 or Dexcom ONE - -Noise-level data and smooth BG readings are only shared with AAPS if you use xDrip+ [native mode](https://navid200.github.io/xDrip/docs/Native-Algorithm). Using native mode, there are no restrictions in using SMBs. - -### Dexcom G6 or Dexcom ONE with xDrip+ Companion Mode - -The noise-level data is not shared with AAPS using this method. Therefore 'Enable SMB always' and 'Enable SMB after carbs' are disabled. - -## Freestyle Libre sensors - -### xDrip+ with FreeStyle Libre - -None of the FreeStyle Libre systems (FSL1, FSL2, or FSL3) broadcast any information about the level of noise detected in the readings, and therefore 'Enable SMB always' and 'Enable SMB after carbs' are disabled for all setups using the FreeStyle Libre. - -In addition, many people have reported the FreeStyle Libre often produces noisy data. In xDrip+ there are a few options to help with this: - -**Smooth Sensor Noise.** In xDrip+ Settings > xDrip+ Display Settings ensure that Smooth Sensor Noise is turned on. This attempts to apply smoothing to noisy data. - -**Smooth Sensor Noise (Ultrasensitive).** If you are still seeing noisy data in xDrip+ you can apply more aggressive smoothing using the Smooth Sensor Noise (Ultrasensitive) setting. This will attempt to apply smoothing even on very low levels of detected noise. To do this, first enable [engineering mode](Enabling-Engineering-Mode-in-xDrip.md) in xDrip+. Then navigate to Settings > xDrip+ Display Settings and turn on Smooth Sensor Noise (Ultrasensitive). \ No newline at end of file diff --git a/docs/CROWDIN/pb/Usage/autotune_b.md b/docs/CROWDIN/pb/Usage/autotune_b.md deleted file mode 100644 index acd7b241961d..000000000000 --- a/docs/CROWDIN/pb/Usage/autotune_b.md +++ /dev/null @@ -1,186 +0,0 @@ -# How to use Autotune plugin - -Documentation about Autotune algorythm can be found in [OpenAPS documentation](https://openaps.readthedocs.io/en/latest/docs/Customize-Iterate/autotune.html). - -Autotune plugin is an implementation of OpenAPS autotune algorythm within AAPS. - -**Currently Autotune Plugin is only available in dev branch with Engineering mode.** - -## Autotune user interface - -![Autotune default screen](../images/Autotune/Autotune_1b.png) - -- You can select in the Profile dropdown menu the input profile you want to tune (by default your current active profile is selected) - - Note: each time you select a new profile, previous results will be removed and Tune days parameter will be set to default value -- Then Tune days is to select the number of days used in calculation to tune your profile. The minimum value is 1 day and the maximum value 30 days. This number should not be too small to get correct iterative and smooth results (above 7 days for each calculation) - - Note: each time you change Tune days parameter, previous results will be removed -- Last Run il a link that recover your latest valid calculation. If you didn't launch Autotune on current day, or if previous results was removed with a modification of calculation parameter above, then you can recover parameters and results of the latest successfull run. -- Warning show you for example some information about selected profile (if you have several IC values or several ISF values) - - Note: Autotune calculation works with only a single IC and a single ISF value. There is currently no existing Autotune algorythm to tune a circadian IC or circadian ISF. If your input profile has several values, you can see in warning section the average value taken into account to tune your profile. -- Check Input Profile button open the Profile Viewer to allow you a quick verification of your profile (Units, DAI, IC, ISF, basal and target) - - Note: Autotune will only tune your IC (single value), ISF (single value) and basal (with circadian variation). Units, DAI and target will remain unchanged in output profile. - -- "Run Autotune" will launch Autotune calculation with selected profile and the number of Tune days - - Note: Autotune calculation can take a long time. Once launched, you can switch to another view (home, ...) and come back later in Autotune plugin to see results - -![Autotune Run start](../images/Autotune/Autotune_2b.png) - -- Then during the run you will see intermediate results below - - - Note: During run, settings are locked, so you cannot change anymore selected input profile or the number of day. You will have to wait the end of current calculation if you want to launch another run with other parameters. - - ![Autotune during run](../images/Autotune/Autotune_3b.png) - -- When Autotune calculation is finished, you will see the result (Tuned profile) and four buttons below. - -![Autotune Result](../images/Autotune/Autotune_4b.png) - -- It's important to always compare input profile (column "Profile"), output profile (column "Tuned") and the percentage of variation for each value (Column "%"). - -- For basal rates, you also have the number of "missing days". You have missing days when Autotune don't have enough data categorized as "Basal" to tune basal rate for this period (for example after each meal when you have carbs absorption). This number should be as low as possible especially when basal is important (for example during the night or at the end of the afternoon) - -- The "Compare profiles" button open the profile comparator view. Input profile is in blue, and output profile (named "Tuned") is in red. - - - Note: in the example below input profile has circadian variation for IC and ISF, but output calculated profile has a single value. If it's important for you to get a circadian output profile see [Circadian IC or ISF profile](#circadian-ic-or-isf-profile) below. - - ![Autotune Compare profiles](../images/Autotune/Autotune_5.png) - -- If you trust results (low percentage of variation between input profile and output profile), you can click on "Activate profile" button and then click on OK to validated. - - - Activate Tuned profile will automatically create a new profile "Tuned" in your Local profile plugin. - - If you already have a profile named "Tuned" in your local profile plugin, then this profile will be updated with calculated Autotune profile before the activation - - ![Autotune Activate profile](../images/Autotune/Autotune_6.png) - -- If you think Tuned profile must be adjusted (for example if you think some variation are too important), then you can click on "Copy to local profile" button - - - A new profile with the prefix "Tuned" and the date and time of the run will be created in local profile plugin - -![Autotune Copy to local profile](../images/Autotune/Autotune_7.png) - -- You can then select local profile to edit the Tuned profile (it will be selected by default when you open Local profile plugin) - - - the values in local profile will but rounded in the user interface to your pump capabilities - - ![Autotune local profile update](../images/Autotune/Autotune_8.png) - -- If you want to replace your input profile with Autotune result, click on "Update input profile" button and validate the Popup with OK - - - Note: if you click on "Activate profile" after "Update input profile", then you will activate your updated profile and not the default "Tuned" profile? - - ![Autotune Update input profile](../images/Autotune/Autotune_9.png) - -- If you have updated your input profile, then the "Update input profile" button is replaced by "Revert input profile" button (see screenshot below). You can that way immediatly see if your current input profile in Local profile plugin already include the result of last run or not. You also have the possibility to recover you input profile without autotune result with this button - - ![Autotune Update input profile](../images/Autotune/Autotune_10.png) - - - -## Autotune settings - -### Autotune plugin settings - -![Autotune default screen](../images/Autotune/Autotune_11.png) - -- Automation Switch Profile (default Off): see [Run Autotune with an automation rule](#run-autotune-with-an-automation-rule) below. If you change this setting to On, the input profile will automatically be updated by the Tuned profile, and it will be activated. - - **Be Carefull, you must trust and verified during several following days that after an update and activation of Tuned profile without modification, it improves your loop** - -- Categorize UAM as basal (default On): This setting is for the users using AndroidAPS without any carbs entered (Full UAM). It will prevent (when Off) to categorize UAM as basal. - - Note: if you have at least one hour of Carbs absorption detected during one day, then all data categorized as "UAM" will be categorized as basal, whatever this setting (On or Off) -- Number of days of data (default 5): You can define default value with this setting. Each time your select a new profile in Autotune plugin, Tune days parameter will be replaced by this default value -- Apply average result in circadian IC/ISF (default Off): see [Circadian IC or ISF profile](#circadian-ic-or-isf-profile) below. - -### Outras configurações - -- Autotune also uses Max autosens ratio and Min autotsens ratio to limit variation. You can see and adjust these values in Config Builder > Sensitivity detection plugin > Settings > Advanced Settings - - ![Autotune default screen](../images/Autotune/Autotune_12.png) - - - -## Advanced feature - -### Circadian IC or ISF profile - -- If you have important variation of IC and/or you ISF in your profile, and you fully trust in your circadian time and variation, then you can set "Apply average result in circadiant IC/ISF" - - - Note that Autotune calculation will always be done with a single value, and circadian variation will not be tuned by Autotune. This setting only apply average variation calculated for IC and/or ISF on your circadian values - -- See on screenshot below Tuned profile with Apply average variation Off (on the left) and On (on the right) - - ![Autotune default screen](../images/Autotune/Autotune_13.png) - - - -### Tune specific days of the week - -- If you click on the checkbox with the eye on the right of "Rune days" parameter, you will see the day selection. You can specify which day of the week should be included in Autotune calculation (in screenshot below you can see an example for "working days" with Saturday and Sunday removed from autotune calculation) - - If the number of day included in Autotune calculation is lower than the number of Tune days, then you will see how many days will be included on the right of Tune days selector (10 days in the example below) - - This setting gives good results only if the number of remaining days is not to small (for example if you Tune a specific profile for week end days with only Sunday and Saturday selected, you should select a minimum of 21 or 28 Tune days to have 6 or 8 days included in Autotune calculation) - -![Autotune default screen](../images/Autotune/Autotune_14b.png) - -- During Autotune calculation, you can see the progress of the calculations ("Partial result day 3 / 10 tuned" on example below) - - ![Autotune default screen](../images/Autotune/Autotune_15b.png) - -## Run Autotune with an automation rule - -First step is to define correct trigger for an automation rule with Autotune: - -Note: for more information on how to set an automation rule, see [here](./Automation.rst). - -- You should select Recurring time trigger: only run Autotune once per day, and autotune is designed to be runned daily (each new run you shift one day later and quickly profile modification should be tiny) - - ![Autotune default screen](../images/Autotune/Autotune_16.png) - -- It's better at the beginning to run Autotune during the day to be able to check results. If you want to run Autotune during the night, you have to select in the trigger 4AM or later to include current day in next Autotune Calculation. - - ![Autotune default screen](../images/Autotune/Autotune_17.png) - -- Then you can select "Run Autotune" Action in the list - - ![Autotune default screen](../images/Autotune/Autotune_18.png) - -- You can then select Autotune Action to adjust parameters for your run. Default parameters are "Active Profile", default Tune days value defined in Autotune Plugin preferences, and All days are selected. - - ![Autotune default screen](../images/Autotune/Autotune_19b.png) - -- After a few days, if you fully trust Autotune results and percentage of modification is low, you can modify [Autotune settings](#autotune-plugin-settings) "Automation Switch Profile" to enabled to automatically update and activate profile tuned after calculation. - -Note: if you want to automatically tune profiles for specific days of the week (for example a profile for "Weekend days" and another one for "Working days"), then create one rule for each profile, select the same days in Trigger and in Autotune Action, Tune days must be high enough to be sure tuning will be done with at least 6 or 8 days, and don't forget to select time after 4AM in trigger... - -- See below an example of rule to tune "my profile" on all "Working days" with 14 Tune days selected (so only 10 days included in autotune calculation). - -![Autotune default screen](../images/Autotune/Autotune_20b.png) - - - -## Tips and trick's - -Autotune works with information existing in your database, so if you just installed AAPS on a new phone, you will have to wait several days before being able to launch Autotune with enough days to get relevant results; - -Autotune is just an help, it's important to regularly check if you agree with calculated profile. If you have any doubt, change Autotune settings (for example the number of days) or copy results in local profile and adjust profile before using it. - -Always use Autotune several days manually to check results before applyling them. And it's only when you fully trust Autotune results, and when variation becomes tiny between previous profile and calculated profile than you start to use Automation (Never before) - -- Autotune can work very well for some users and not for others, so **If you don't trust Autotune result, don't use it** - -It's also important to analyse Autotune results to understand (or try to understand) why Autotune propose these modifications - -- you can have a whole increase or decrease of the strength of your profile (for example increase of total basal associated to decrease of ISF and IC values). it could be associated to several following days with autosens correction above 100% (more agressivity required) or below 100% (you are more sensitive) -- Sometimes Autotune propose a different balance between basal rates and IC/ISF (for ex lower basal and more aggressive IC/ISF) - -We advise to not use Autotune in the following cases: - -- You don't enter all your carbs - - If you don't enter carbs correction for an hypoglycemia, Autotune will see an unexcepted increase of your BG value and will increase your basal rates the ' hours earlier, it could be the opposite of what you need to avoid hypo, especially if it's in the middle of the night. That's why it's important to enter all carabs especially correction for hypo. -- You have a lot of period with UAM detected during the day. - - Do you have entered all your carbs and correctly estimated your Carbs ? - - All UAM periods (except if you enter no carbs during a day and categorized UAM as basal is disabled), all your UAM periods will be categorized as basal, this can increase a lot your basal (much more than necessary) - -- Your carbs absorption is very slow: if most of your carbs absorption are calculated with min_5m_carbimpact parameter (you can see these periods with a little orange dot in the top of COB curve), the calculation of COB could be wrong and leads to wrong results. - - We you practice sport, you are generally more sensitive and your BG doesn't rise a lot, so during or after an exercice, it's usual to see some periods with slow carbs. But if you have too often unexpected slow carb absorption, then you may need a profile adjustment (higher value of IC) or a min_5m_carbimpact a bit to high. -- You have a "very bad days", for example stuck several hours in hyperglycemia with a huge amount of insulin to be able to go down within the range, or after a sensor change you got long periods of wrong BG values. -- If the percentage of modification is too important - - You can try to increase the number of days to get smoother results \ No newline at end of file diff --git a/docs/CROWDIN/pb/Usage/making-sport-with-AAPS.md b/docs/CROWDIN/pb/Usage/making-sport-with-AAPS.md deleted file mode 100644 index 79d2f1c38223..000000000000 --- a/docs/CROWDIN/pb/Usage/making-sport-with-AAPS.md +++ /dev/null @@ -1,185 +0,0 @@ -# making sport with AAPS - -In this section we want to address the topic of sport with AAPS. - -The aim is to show you how AAPS can help you to continue doing your favorite sport more easily or even to start doing it. It is relatively common for new type 1 diabetics to ask whether exercise is still possible for them, even if the answer in the training courses is actually a clear yes. Exercise is not only good for healthy people, but also for type 1 diabetics and even moderate exercise can even help to stabilize the blood sugar curve overall. - -:::{admonition} consult with your diabetes team after reading - -::: - -The difficulty here is that the prerequisites that someone brings with them and the expectations of what sport means to them are very different. - -Since we can assume that experienced top athletes with T1D who use AAPS are unlikely to look it up here, we deliberately set the bar low for ourselves when writing and for you when reading and using it, so that as many people as possible can benefit from it. - -Since even sport as a category is far too imprecise, as the effects of endurance sports differ greatly from strength training, for example, we are trying to break it down by type of sport. - -To be concrete and give you something you can test yourself we arrange the explanaiton around a concrete example and explain to you they action, reactions and effects. - -:::{admonition} more examples wanted - -The focus should always be on how others can do sport and not on the top performance someone has achieved. - -It's really about the basics. Your experience, which you share here, can help others to pursue their beloved sport more quickly and successfully and is therefore important. -::: - -## Cycling - -:::{admonition} take a friend with you - at least on your first trials -:class: information -A gerneral very good idea can be to take a good friend with you on the first rides. -This is especially important if you are not experienced in T1D. -Always keep in mind please: arrival comes before speed! Safety for you and the others in road traffic is very, very important. -::: - -### Example - -Let's take about 60 minutes of cycling on a flat route with a moderate heart rate as an example. - -1. we take a flat route in order to have an even load for the first exercise. This is not about performance, but purely about learning how you should react to changes in blood glucose. -2. we take the heart rate as an indicator of the load, as it is easy to see whether you are under load or not. -3. we set ourselves the goal of doing a relaxed lap around the neighborhood and focus on staying within our target range during the lap. In my case, this would be 70 <= x <= 180 mg/dl. - -We **don't** take the speed, as this is heavily dependent on personal physical conditions as well as the bike and surface used. It is therefore not very meaningful. - -You should know from the diabetes training courses you have attended that during endurance sports cycling, the insulin active in the body works significantly better than during times without physical exertion. The insulin active in the body is referred to as insulin on board (IoB). It is our most important parameter when cycling with T1D. - -We try to keep the IoB as low as possible at the start and during exercise. IoB should be around 0 or even slightly negative. You can get it there by not eating 3-4 hours before exercise. In the beginning it can also be helpful to exercise in the morning before breakfast, as with the right profile you should always have around 0 for IoB in the morning. - -AAPS shows us the IoB value on the home screen on the left under the blood glucose value. - -![IoB](../images/cycling_20240104-174035.png) - -:::{admonition} ignoring the IoB rule increases the risk for roller coaster BG dramatically -:class: danger -If you ignore this rule, you can still go cycling, but it will be much more difficult to keep your blood sugar levels in balance, so it is better to save this for later tests after several successful simple tests. -::: - -As you should know from the diabetes training courses, you should reduce the basal rate during exercise. The factor is individual. I have found a value of 50% in tests to be suitable for me. - -In AAPS, you should therefore change your profile to 50% before exercise and keep it active until the end of exercise. Some people even do it a certain amount of time before, e.g. 1 hour. Unfortunately, the pre-run is also individual. We will come to the post-run later. - -You should use two carbohydrates during exercise. - -1. medium-fast carbohydrates for the insulin still in the body and -2. very fast carbohydrates to prevent slipping into a hypo. - -For medium-fast carbohydrates, I treat myself to cookies or a banana before exercise, for example. You can also use something else that is more suitable for you. -For very fast carbohydrates, I take 3 teaspoons of dissolved glucose per 100 ml of still water in a 500 ml water bottle on my bike. If I'm cycling longer distances, I take a larger bottle with me and, if necessary, packaged glucose to refill the bottle. I add a little lemon juice for flavor. You can also use something other than lemon juice for the taste. You shouldn't change anything about the dextrose, as dissolved dextrose raises blood sugar levels super quickly. If you only take it in sips, your blood sugar won't go super high either! You can also do this tip at home beforehand as a dry run and see how quickly the change shows up on the CGMS. - -Why do I place so much emphasis on fast carbohydrates? - -1. once you are in a slight hypo, you may get back into the normal range by drinking the dextrose solution. As a rule, however, the oscillation of the curve then begins, which leads to a rollercoaster ride of the blood sugar. You may even be able to keep this within your target range, but you must be constantly vigilant. Without a hypo it is simply the most stable. -2. if you even slip into a somewhat severe hypo (without the need for outside help, of course), you may even have to pause briefly to avoid getting stuck in the hypo. - With both hypos, there is a risk that you will be tempted to switch from drinking 2-3 sips at a time to larger quantities. Not too bad at first, until the oscillation sets in and pushes you into a hyper. You can correct this, but your blood sugar will most likely go on a rollercoaster ride. - -What else is helpful, but not absolutely necessary? -It is important to keep an eye on your blood sugar, as your blood sugar can change enormously (e.g. 30 - 50 mg/dl) within 15 minutes of riding and a little more IoB or a basal rate that is still too high. The best way to keep an eye on it is if it is visible on the handlebars or if it is also displayed on your watch. It is even possible to install an additional app on some Garmin GPS bike computers that displays the blood glucose from XDrip or Nightscout as a data field on the bike computer. The additional app was developed by Andreas May from the T1D community. It is available free of charge in the official connect IQ Store. Certainly an interesting option for riders interested in sports. - -[Link to Andreas May Data Field App on connect IQ store](https://apps.garmin.com/de-DE/apps/5a3e2cda-12f0-4afd-88ed-000e67a68d84) - -Here is a picture of my Garmin Edge 530 bike computer with map, blood sugar and heart rate. - -![Garmin Edge 530 with BG data field](../images/cycling_IMG_1087.jpeg) - -After you have eaten the medium fast carbohydrates (24 - 36 g I take) and the blood sugar is above 100 mg/dl but also below 160 mg/dl, I carry out the profile change to 50% and set the activity temp target. - -:::{admonition} disable SMBs during high temp targets if necessary -:class: danger -Attention: If you prefer not to receive SMBs during the sport, please disable the option "Enable SMB with hight temp targets" in the settings of SMB or DynIFS Plugin. -::: - -The following picture shows the start and end of the sport. The end was specified as the duration when the profile was changed at the start. - -The temporary profile change has the following effects - -1. for a period of 60 minutes -2. a reduction to 50% of the profile and -3. the target is raised by clicking on the Activity Target option, which may have the side effect of disabling the SMBs - see above. - -![profile switch with temp target](../images/cycling_20240104-174056.png) - -The second image shows that the start at IoB was started towards 0. - -![IoB around 0](../images/cycling_20240104-174111.png) - -If the blood sugar drops faster than 15 mg/dl in 5 minutes or if it is at 120 mg/dl and tends to fall, I drink 1-2 sips of dissolved glucose. Then I wait for the next value and proceed as described above. - -You can hardly see it here, but at the beginning I took 2 sips from the bottle several times when my blood sugar started to fall. When it stabilized, I didn't need any more glucose. - -Here is the picture that illustrates this. The chart is saved on the Garmin as a result of the activity. - -![BG chart Garmin](../images/cycling_20240104-174431.png) - -If you should suddenly break out upwards, i.e. above 180 mg/dl, you should consider whether you should make a correction bolus. Caution: Remember the factor and apply it to the correction, otherwise the correction will be too strong. - -If your blood sugar drops below 80 mg/dl, take a break and drink two sips until your blood sugar is back above 100 mg/dl. - -At the end of the ride, the profile change should be finished as the time is up. - -Since we only rode easy for 60 minutes, there shouldn't be a big muscle bulking effect continuing to pull carbohydrates from your blood sugar. However, if it felt strenuous to you, keep an eye on it. This is especially true if you then go straight to bed. It may be better to change your profile to e.g. 80% for sleep. You may come out of sleep slightly too high, but it's better than having a hypo at night. Over time, you will surely find out what happens to you. - -The following pictures show the low intensity of the sport. - -The elevation profile -![](../images/cycling_20240104-174314.png) - -Speed with average and maximum speed - -![](../images/cycling_20240104-174326.png) - -Note the pause at the level crossing, which is also reflected in the heart rate. - -The heart rate. -![](../images/cycling_20240104-174337.png) - -The training effect. -![](../images/cycling_20240104-174358.png) - -The time in the different heart rate training zones. -![](../images/cycling_20240104-174423.png) - -After succesfully mastering this simple example you could go for further targets by stretching - -1. the distance and time -2. the load during the ride -3. the elevation during the right which should make a big impact on the more necessary carbs or further reduction of IoB and percentage of profile switch. - -Based on my experiences I would not expect to come back 100% with time in range over the whole and every ride. - -### Tipps - -I already gave some tipps for during the ride above. - -Here are some further tipps what can go wrong and how you can act to prevent it or react to compensate it. - -#### sky rocket high after ride - -During the ride everything was fine but after siting down and relax the blood sugar go sky rocket high. - -**Possible reason:** This happens when you have drunk too much dissolved glucose. - -**Reaction:** Drink 500 ml water, go to the shower and then control again. Latest after 30 minutes think about giving a correction bolus but be careful when it is short for bed time. Therefore it can be very good to make the first try runs on weekend mornings. - -**Action:** Next time be a bit more cautious in drinking from the dissolved glucose. - -#### hypo during ride - -During the ride you are going into hypo and can't recover your blood sugar during cycling. - -**Possible reason:** Your body cannot absorb enough carbohydrates quickly enough during exercise. - -**Reaction:** Take a rest and corrrect your blood sugar with drinking dissolved glucose. Stay calm: arrival comes before speed. - -**Action:** Did you started with IoB near 0? Have you eaten a small amount of middle fast carbs? Can you increase this or are the not fast enough for your body? Is it possible to prevent going into hypo by reducing the factor for the profile switch? Have you disbaled SMBs during ride as explained above? - -#### sky rocket high during ride - -During the ride your blood sugar goes sky rocket high. - -**Possible reason:** You have got taken too much carbs for your IoB at that time. Beneath for sure the typical technical problems with your -insulin pump like leakage or blockage of the catheder! - -**Reaction:** If it is too high for you take a rest and correct with a bolus. Keep in mind that you must ride home and therefore make it carefully. Drink 500 ml pure water without carbs. Stay calm: arrival comes before speed. - -**Action:** Have you eaten too much? Especially have you drunk too much from the dissolved glucose during the ride? Is your percentage of reduction the profile during profile switch too low and you can increase this? diff --git a/docs/CROWDIN/pb/buildingAAPS.md b/docs/CROWDIN/pb/buildingAAPS.md deleted file mode 100644 index 98164a09e49b..000000000000 --- a/docs/CROWDIN/pb/buildingAAPS.md +++ /dev/null @@ -1,28 +0,0 @@ -# Dummy - -## This is a dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - - -## This is another dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - - -## This is another another dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - diff --git a/docs/CROWDIN/pb/completingObjetives.md b/docs/CROWDIN/pb/completingObjetives.md deleted file mode 100644 index 98164a09e49b..000000000000 --- a/docs/CROWDIN/pb/completingObjetives.md +++ /dev/null @@ -1,28 +0,0 @@ -# Dummy - -## This is a dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - - -## This is another dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - - -## This is another another dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - diff --git a/docs/CROWDIN/pb/dummy.md b/docs/CROWDIN/pb/dummy.md deleted file mode 100644 index 98164a09e49b..000000000000 --- a/docs/CROWDIN/pb/dummy.md +++ /dev/null @@ -1,28 +0,0 @@ -# Dummy - -## This is a dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - - -## This is another dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - - -## This is another another dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - diff --git a/docs/CROWDIN/pb/intro.md b/docs/CROWDIN/pb/intro.md deleted file mode 100644 index 0d1e41729405..000000000000 --- a/docs/CROWDIN/pb/intro.md +++ /dev/null @@ -1,291 +0,0 @@ -![20-06-23v2 AAPS simple overview-cropped](https://github.com/openaps/AndroidAPSdocs/assets/94044064/e505b73b-09a0-42a4-a1ab-b830a0741234) - -# Introduction to APS and AAPS - -## What is an “Artificial Pancreas System”? - -A human pancreas does a lot of things besides regulating blood sugar. However, the term **“Artificial Pancreas System” (APS)** usually refers to a system which works to automatically keep blood sugar levels within healthy limits. - -The most basic way to do this is by detecting **glucose levels**, using these values to do **calculations**, and then delivering the (predicted) right amount of **insulin** to the body. It repeats the calculation, every few minutes, 24/7. It uses **alarms** and **alerts** to inform the user if intervention or attention is needed. This system is typically made up of a **glucose sensor**, an **insulin pump** and an **app** on a phone. - -You can read more about the different artificial pancreas systems currently in use and in development in this 2022 review article: - -![Frontiers](./images/FRONTIERS_Logo_Grey_RGB.png) [Future Directions in Closed-Loop Technology](https://www.frontiersin.org/articles/10.3389/fendo.2022.919942/full#:~:text=Fully%20closed%2Dloop%20systems%2C%20unlike,user%20input%20for%20mealtime%20boluses). - -In the near future, some so-called "dual-hormone" systems will also have the ability to infuse glucagon alongside insulin, with the aim of preventing severe hypos and allowing even tighter blood glucose control. - -An artificial pancreas can be thought of as an [“autopilot for your diabetes”]. (https://www.artificialpancreasbook.com/) What does that mean? In an aircraft, an autopilot does not do the complete job of the human pilot, the pilot cannot sleep through the entire flight. The autopilot aids the work of the pilot. It relieves them of the burden of permanently monitoring the aircraft, allowing the pilot to concentrate on wider monitoring from time to time. The autopilot receives signals from various sensors, a computer evaluates them together with the pilot’s specifications and then makes the necessary adjustments, alerting the pilot to any concerns. The pilot no longer has to worry about constantly making decisions. - -## What does hybrid closed loop mean? - -The best solution for type 1 diabetes would be a “functional cure” (probably an implant of pancreatic cells which are protected from the immune system). While we are waiting for that, a “full closed loop” artificial pancreas is probably the next best thing. This is a tech system that doesn’t need any user input (like bolusing insulin for meals, or announcing exercise), with good regulation of blood glucose levels. At the moment, there are no widely available systems which are “full” closed loop, they all need some user input. The currently available systems are called “hybrid” closed loop, because they use a combination of automated technology and user input. - -## How and why did looping start? - -The development of commercial technology for people with type 1 diabetes (T1D) is very slow. In 2013 the T1D community founded the #WeAreNotWaiting movement. They developed systems themselves using existing approved technology (insulin pumps and sensors) to improve blood glucose control, safety, and quality of life. These are known as DIY (do-it-yourself) systems, because they are not formally approved by health bodies (FDA, NHS etc). There are four main DIY systems available: OpenAPS, **AAPS**, Loop and iAPS. - -A great way to understand the fundamentals of DIY looping is to read Dana Lewis’s book “Automated Insulin Delivery”. You can access it \[here\] (https://www.artificialpancreasbook.com/) for free (or buy a hardcopy of the book). If you want to understand more about OpenAPS, which** AAPS** has developed from, the \[OpenAPS website\] (https://openaps.org/what-is-openaps/) is also a great resource. - -Several commercial hybrid closed loop systems have been launched, the most recent of which are \[CamAPS FX\] (https://camdiab.com/) (UK and EU) and \[Omnipod 5\] (https://www.omnipod.com/en-gb/what-is-omnipod/omnipod-5) (USA and EU). These are very different to DIY systems, mainly because they both include a “learning algorithm” which adjusts how much insulin is delivered according to your insulin needs from previous days. Many people in the DIY community have already tried out these commercial systems and compared them with their DIY system. You can find out more about how the different systems compare by asking on the dedicated Facebook groups for these systems, on the \[AAPS Facebook group\] (https://www.facebook.com/groups/AndroidAPSUsers/) or on \[Discord\] (https://discord.com/invite/4fQUWHZ4Mw). - -## What is Android APS (AAPS)? - -![image](https://github.com/openaps/AndroidAPSdocs/assets/94044064/0f089d96-b7ee-452a-aa9d-aae10ab58971) - -**Figure 1**. Basic outline of the Android APS (Artificial Pancreas System), AAPS. - -Android APS (AAPS) is a hybrid closed loop system, or Artificial Pancreas System (APS). It makes its insulin dosing calculations using established \[OpenAPS\] (https://openaps.org/) algorithms (a set of rules) developed by the #WeAreNotWaiting type 1 diabetes community. - -Since OpenAPS is only compatible with certain older insulin pumps, AAPS (which can be used with a wider range of insulin pumps) was developed in 2016 by Milos Kozak, for a family member with type 1 diabetes. Since those early days, **AAPS** has been continually developed and refined by a team of volunteer computer developers and other enthusiasts who have a connection to the type 1 diabetes world. Today, **AAPS** is used by approximately 10,000 people. It is a highly customisable and versatile system, and because it is open-source, it is also readily compatible with many other open-source diabetes softwares and platforms. The fundamental components of the current **AAPS** system are outlined in Figure 1 above. - -## What are the basic components of AAPS? - -The “brain” of AAPS is an **app** which you build yourself. There are detailed step-by-step instructions for this. You then install the **AAPS app** on a compatible **Android smartphone** (1). A number of users prefer their loop on a separate phone to their main phone. So, you don’t necessarily have to be using an Android phone for everything else in your life, just for running your AAPS loop. - -The **Android smartphone** will also need to have another app installed on it as well as **AAPS**, either a modified Dexcom app called build-your-own dexcom app (**BYODA**) or Xdrip+. This receives glucose data from a sensor (2) by bluetooth, and then sends the data internally on the phone to the **AAPS app**. - -The **AAPS app** uses a decision making process (**algorithm**) from OpenAPS. Beginners start out using the basic **oref0** algorithm, but it is possible to switch to using the newer **oref1** algorithm as you progress with AAPS. Which algorithm you use (oref0 or oref1), depends on which suits your specific situation best. In both cases, the algorithm takes into account multiple factors, and performs rapid calculations every time a new reading comes in from the sensor. The algorithm then sends instructions to the insulin pump (3) on how much insulin to deliver by bluetooth. All the information can be sent by mobile data or wifi to the internet. This data can also be shared with followers if desired, and/or collected for analysis. - -## What are the advantages of the AAPS system? - -The OpenAPS algorithm used by **AAPS** controls blood sugar levels in the absence of user input, according to the users’ defined parameters (important ones being basal rates, insulin sensitivity factors, insulin-to-carb ratios, duration of insulin activity etc.), reacting every 5 minutes to the new sensor data. Some of the reported advantages of using AAPS are extensive fine-tunable options, automations and increased transparency of the system for the patient/caregiver. This can result in better control over your (or your dependent’s) diabetes, which in turn may give improved quality of life and increased peace of mind. - -Practical advantages include: - -- **Hardware flexibility**: **AAPS** works with a wide range of insulin pumps and sensors. So for example, if you develop an allergy to Dexcom sensor patch glue, you could switch to using a Libre sensor instead. That offers flexibility as life changes. You don't have to rebuild, just tick a different box in the AAPS app to change your hardware. - -- **Highly customisable with wide parameters**: here are some examples of the possibilities with AAPS: a) The ability to set a lower glucose target 30 min before eating; you can set the target as low as 72 mg/dL (4.0 mmol/L). b) If you are insulin-resistant resulting in high blood sugars, **AAPS** allows you to set an **automation** rule to activate when BG rises above 8 mmol/L (144 mg/dL), switching to a 120% profile (resulting in an 20% increase in basal and strengthening of other factors too, compared to your normal **profile** setting). The automation will last according to the scheduled time you set. Such an automation could be set to only be active on certain days of the week, at certain times of day, and even at certain locations. c) If your child is on a trampoline with no advance notice, **AAPS** allows insulin suspension for a set time period, directly via the phone. d) After reconnecting a tubed pump which has been disconnected for swimming, AAPS will calculate the basal insulin you have missed while disconnected and deliver it carefully, according to your current BG. Any insulin not required can be overridden by just “cancelling” the missed basal. f) **AAPS** has the ability to set different profiles for different situations and easily switch between them. Features which make the algorithm quicker to bring down elevated BG (like supermicro boluses (“SMB”), unannounced meals, (“**UAM**”) can be set to only work during the daytime, if you are worried about night-time hypos. - - -These are all examples, the full range of features gives huge flexibility for daily life including sport, illness, hormone cycles etc. Ultimately, it is for the user to decide how to use this flexibility, and there is no one-size-fits-all automation for this. - -- **Remote monitoring**: there are multiple possible monitoring channels (Sugarmate, Dexcom Follow, Xdrip+, Android Auto etc.) which are useful for parents/carers and adults in certain scenarios (sleeping/driving) who need customisable alerts. In some apps (Xdrip+) you can also turn alarms off totally, which is great if you have a new sensor “soaking” or settling down that you don’t want to loop with yet. - -- **Remote control**: a significant advantage of **AAPS **over commercial systems is that it is possible for followers, using authenticated text (SMS) commands or via an app (Nightscout or NSClient) to send a wide range of commands back to the ****AAPS** **system. This is used extensively by parents of kids with type 1 diabetes who use AAPS. It is very useful in the playground, for example, if you want to pre-bolus for a snack from your own phone, and your child is busy playing. It is possible to monitor the system (e.g. Fitbit), send basic commands (e.g. Samsung Galaxy watch 4), or even run the entire AAPS system from a high-spec smartwatch (5) (e.g. LEMFO LEM14). In this last scenario, you don’t need to use a phone to run AAPS. As battery life on watches improves, this last option is likely to become increasingly attractive. - -- **No commercial constraints due to open application interfaces**: beyond the use of an open source approach, which allows the source code of **AAPS** to be viewed at any time, the general principle of providing open programming interfaces gives other developers the opportunity to contribute new ideas that allow users to live more easily with their diabetes. This is complementary to commercial systems which adopt the innovations from DIY, where interfaces are only made possible in return for licensing, thus preventing innovations in particular that are not-for-profit. Good examples for such integrations are NightScout, Nightscout Reporter, Xdrip+ M5 stack etc. - -- **Detailed app interface**: It is easy to keep track of things like: insulin levels, cannula age, sensor age, pump battery age, and many actions can be done through the **AAPS** app (priming the pump, disconnecting the pump etc.), instead of on the pump itself. - -- **Accessibility and affordability**: **AAPS** gives people who currently can’t afford to self-fund, or don’t have funding/insurance, access to a world-class hybrid closed looping system which is conceptually years ahead, in terms of development, of the commercial systems being offered by clinics. You currently need to have a Nightscout account to set up **AAPS**. Although the Nightscout account it not necessarily required after setup, many people continue to use Nightscout for collecting their data, and for remote control. So, although **AAPS **itself is free, setting up Nightscout through one of the various platforms may incur a fee (E0 - E12), depending on what level of support you want (see comparison table). **AAPS** works with a wide range of affordable (starting from approx E150) Android phones. In comparison, Loop currently costs around $80 a year for the Apple development licence and CamAPS FX costs around E80/month (as at 2023). - -- ****Support**: No automated insulin delivery system is perfect. Commercial and open-source systems share many common glitches in both communications and temporary hardware failure. There is a community of AAPS users on both Facebook and Discord and Github who designed, developed and are currently using **AAPS** all over the world. There are Facebook support groups and help from clinic/commercial companies for the commercial APS systems - it is worth speaking to the users, or former users of these systems to get feedback on the common glitches, the quality of the education programme and the level of ongoing support provided. - -- **Predictability, transparency and safety**: with no learning algorithm, **AAPS** is logical and in some respect, more predictable, which may make it easier to know when a setting is wrong, and to adjust it accordingly. You can see exactly what the system is doing, why it is doing it, and set its operational limits, which puts the control (and responsibility) in your hands. This can provide the user with confidence, and a sounder sleep. - -- **Access to advanced features through dev modes including full closed loop**: **AAPS **documentation focuses on the mainstream **“master”** branch of **AAPS**, however, research and development is going on all the time. More experienced users may wish to explore the experimental features in the **development** branch such as integration of Dexcom G7, and automatically adjusting insulin delivery according to short-term sensitivity changes (DYNISF), not having to bolus for meals, and generally trying to make life with type 1 diabetes as convenient as possible. - -- **Ability to contribute yourself to further improvements**: type 1 diabetes can be highly frustrating and isolating. Having control over your own diabetes tech, with the possibility to “pay it forward” as soon as you are making progress by helping others on their journey can be really rewarding. You can educate yourself, discover the roadblocks and look for and even contribute to new developments and the documentation. There will be others with the same quest to bounce ideas off and work with. This is the essence of #WeAreNotWaiting. - - -## How does AAPS compare to MDI and open looping? - -Multiple daily injections (MDI, a) usually involve giving an injection of a long-lasting insulin (e.g. Tresiba) once a day, with injections of faster-acting insulin (e.g. Novorapid, Fiasp) at mealtimes, or for corrections. Open pumping (b) involves using a pump to deliver basal at pre-programmed rates of rapid-acting insulin, and then boluses through the pump at mealtimes or for corrections. The basics of a looping system is that the App uses the glucose data to instruct the pump to stop insulin delivery when it predicts you are heading for a low, and to give you extra insulin if your glucose levels are rising and predicted to go too high (c). Although this is oversimplified, (mostly because hybrid closed looping has a lot of additional useful features) the key features of each system are shown in **Figure 2**. - -![image](https://github.com/openaps/AndroidAPSdocs/assets/94044064/4e7d8608-684d-4c69-9c61-88c9539f5d6f) - -**Figure 2**. Overview of (a) MDI, (b) open-loop pumping and (c) hybrid closed loop pumping - -## How does AAPS compare to other looping systems? - -At present there are four major open source closed loop systems available: OpenAPS, **AAPS**, \[Loop\] (https://loopkit.github.io/loopdocs/#what-is-loop) and iAPS, (formerly FreeAPS X). The features of the different systems are shown in the table below: - -| Devicestyp | Name | [Open APS](https://openaps.readthedocs.io/en/latest/) | [AAPS](https://wiki.aaps.app) | [Loop](https://loopkit.github.io/loopdocs/) | [iAPS](https://iaps.readthedocs.io/en/latest/) | -| ---------- | -------------------------------------------------------------------------------------------------------- | ----------------------------------------------------- | ------------------------------------------- | ------------------------------------------- | ---------------------------------------------- | -| PUMP | Older Medtronic | ![available](./images/available.png) | ![available](./images/available.png) | ![available](./images/available.png) | ![available](./images/available.png) | -| PUMP | Older Omnipod (Eros) | ![unavailable](./images/unavailable.png) | ![available](./images/available.png) | ![available](./images/available.png) | ![available](./images/available.png) | -| PUMP | Newer Omnipod (Dash) | ![unavailable](./images/unavailable.png) | ![available](./images/available.png) | ![available](./images/available.png) | ![available](./images/available.png) | -| PUMP | DANA R, DANA RS, DANA I | ![unavailable](./images/unavailable.png) | ![available](./images/available.png) | ![unavailable](./images/unavailable.png) | ![unavailable](./images/unavailable.png) | -| PUMP | Roche Combo, Insight | ![unavailable](./images/unavailable.png) | ![available](./images/available.png) | ![unavailable](./images/unavailable.png) | ![unavailable](./images/unavailable.png) | -| CGM | Dexcom G4, G5, G6 | ![available](./images/available.png) | ![available](./images/available.png) | ![available](./images/available.png) | ![available](./images/available.png) | -| CGM | Libre 1 (requires Miao Miao) | ![available](./images/available.png) | ![available](./images/available.png) | ![available](./images/available.png) | ![available](./images/available.png) | -| CGM | Libre 2 | ![available](./images/available.png) | ![available](./images/available.png) | ![available](./images/available.png) | ![available](./images/available.png) | -| CGM | Libre 3 | | ![unavailable](./images/unavailable.png) | --- | ![unavailable](./images/unavailable.png) | -| CGM | Medtronic Enlite | | --- | ![unavailable](./images/unavailable.png) | --- | -| CGM | [Dexcom G7](https://androidaps.readthedocs.io/en/latest/Hardware/DexcomG7.html) | | ![available](./images/available.png) (beta) | ![available](./images/available.png) | ![available](./images/available.png) | -| CGM | [Eversense](https://androidaps.readthedocs.io/en/latest/Hardware/Eversense.html) | | ![available](./images/available.png) | | ![available](./images/available.png) | -| CGM | [MM640g/MM630g](https://androidaps.readthedocs.io/en/latest/Hardware/MM640g.html) | | ![available](./images/available.png) | | ![available](./images/available.png) | -| CGM | [PocTech](https://androidaps.readthedocs.io/en/latest/Hardware/PocTech.html) | | ![available](./images/available.png) | | ![available](./images/available.png) | -| CGM | [Nightscout as BG Source](https://androidaps.readthedocs.io/en/latest/Hardware/CgmNightscoutUpload.html) | | ![available](./images/available.png) | | ![available](./images/available.png) | -| Phone | Android | ![available](./images/available.png) | ![available](./images/available.png) | ![unavailable](./images/unavailable.png) | ![unavailable](./images/unavailable.png) | -| Phone | iPhone | ![available](./images/available.png) | ![unavailable](./images/unavailable.png) | ![available](./images/available.png) | ![available](./images/available.png) | - -[OpenAPS](https://openaps.readthedocs.io/) was the first Open Source Closed Loop System. Ele usa um pequeno computador como Raspberry Pi ou Intel Edison. Both AndroidAPS (AAPS) and iAPS use the OpenAPS algorithms, whereas Loop uses a separate algorithm. You can read a comparison of iAPS and **AAPS** here. - -An international peer-reviewed consensus statement containing practical guidance on open source looping was written by and for health-care professionals, and published in a leading medical journal in 2022. It is well worth a read (including for your diabetes clinic) and summarises the main technical differences between the different open-source hybrid closed loop systems: - - Lancet Diabetes Endocrinol, 2022; 10: 58–74 - -[https://www.ncbi.nlm.nih.gov/pmc/articles/PMC8720075/](https://www.ncbi.nlm.nih.gov/pmc/articles/PMC8720075/) - -It is hard to get a “feel” for any system without using it, or talking to others who are using it, so do reach out to others on Facebook/Discord and ask. Most people find that AAPS is incredibly sophisticated in comparison to other hybrid closed loop systems (particularly the commercial systems), with a huge number of potentially customisable settings and features, discussed above. Some people can find this a little overwhelming in the beginning, but there is no rush to investigate all the possibilities at once, you can progress as slowly or as fast as you would like, and there is help available at every step of the way. - -## Does AAPS use artificial intelligence or any learning algorithm? - -Não. **AAPS** does not have any complicated machine learning algorithms, multiple-parameter insulin response models, or differential equations. As such, the system is open and transparent in how it works, and has the ability to be understood not just by experts, but also by clinicians and patients. It also means that if you have a sharply varying schedule (maybe switching from a stressful week at work to a relaxing holiday) and are likely to need a significantly different amount of insulin, you can immediately switch **AAPS** to run a weaker/stronger profile. A ‘learning system’ will do this adjustment for you automatically, but is likely to take longer to adjust the insulin delivery. - -## Which system is right for me or my dependent? - -Practically, your choice of system is often restricted by which pump you already have, or can obtain from your medical provider, and your choice of phone (Apple or Android). If you don’t yet have a pump you have the biggest choice of systems. Technology is continually evolving, pumps are being discontinued and new pumps and sensors are being released. Most open-source systems work with the main sensors (Libre and Dexcom) or are quickly adapted to work with new sensors a year or so after they are released (with a bit of time delay for safety and stability testing). - -Most **AAPS **users report more time in range, HbA1c reductions, as well as quality of life improvements from having a system that can auto-adjust basal rates overnight during sleep, and this is true for most hybrid closed loop APS. Some people have a preference for a very simple system which is not very customisable (which means you may prefer a commercial system), and others find this lack of control very frustrating (you may prefer an open-source system). If you (or your dependent) are newly diagnosed, a common route is to get the hang of MDI plus sensor first, then progress to a pump which has the potential for looping, then to **AAPS**, but some people (especially small kids) may go straight to a pump. - -It is important to note that the **AAPS** user needs to be proactive to troubleshoot and fix problems themselves, with help from the community. This is a very different mindset to that when using a commercial system. With **AAPS** a user has more control, but also the responsibility, and needs to be comfortable with that. - -## Is it safe to use open-source systems like AAPS? - -A more accurate question is probably “is it safe compared to my current type 1 diabetes insulin delivery system?” since no method of insulin delivery is without risk. There are many checks and balances in place with **AAPS**. A recent paper looked at the use of**** AAPS ****in a computer simulated set-up, [https://www.liebertpub.com/doi/epub/10.1089/dia.2019.0375](https://www.liebertpub.com/doi/epub/10.1089/dia.2019.0375) which was an effective way to unobjectively trial how safe and effective the system is. More generally, it is estimated that over 10,000 individuals worldwide are using open-source automated-insulin delivery systems, and uptake continues to increase globally. - -Any device that uses radio communications could be hacked, and this is true for a non-looping insulin pump as well. Currently, we are not aware of anyone attempting to harm individuals by hacking their diabetes-related medical equipment. However, there are multiple ways to protect against such risks: - -1. In the pump settings, limit both the max bolus allowed and max temporary basal settings to amounts that you believe are safest. These are hard limits that we do not believe any malicious hacker could circumvent. - -2. Set your CGM alarms enabled for both highs and lows. - -3. Monitor your insulin delivery online. Nightscout users can set additional alarms to alert for a wide variety of conditions, including conditions that are much more likely to occur than a malicious attack. In addition to highs and lows, Nightscout can display diagnostic data useful for verifying that the pump is operating as desired, including current IOB, pump temporary basal history, pump bolus history. It can also be configured to proactively alert users to undesirable conditions, such as predicted highs and lows, low insulin reservoir, and low pump battery. - - -If a malicious attack was made on your insulin pump, these strategies would significantly mitigate the risk. Every potential **AAPS** user needs to weigh the risks associated with using **AAPS**, versus the risks of using a different system. - -## How can I approach discussing AAPS with my clinical team? - -Depending on the country - link to doctors section of docs - - Lancet Diabetes Endocrinol, 2022; 10: 58–74 - -[https://www.ncbi.nlm.nih.gov/pmc/articles/PMC8720075/](https://www.ncbi.nlm.nih.gov/pmc/articles/PMC8720075/) - -## Q: Why can’t I just download AAPS and use it straight away? - -The **AAPS** app is not provided in Google Play - you have to build it from source code by yourself for legal reasons. **AAPS** is unlicensed, meaning that it does not have approval by any regulatory body authority in any country. **AAPS**is deemed to be carrying out a medical experiment on yourself, and is carried out at the user’s own risk. - -Setting up the system requires patience, determination and the gradual development of technical knowledge. All the information and support can be found in these documents, elsewhere online, or from others who have already done it. It is estimated that over 2000 people have successfully built and are currently using **AAPS** worldwide. - -The developers of **AAPS**t ake safety incredibly seriously, and want others to have a good experience of using **AAPS**. That is why it is essential that every user (or carer, if the user is a child): - -- builds the AAPS system themself and works through the **objectives** so that they have reasonably good personalised settings and understand the basics of how AAPS ****works by the time they “close the loop”; - -- backs up their system by exporting and saving important files (like keystore and settings .json file) somewhere safe, so you can setup again quickly if needed; - -- updates to newer master versions as and when they become available; and - -- maintains and monitors the system to ensure it is working properly. - - -## Q: What is the connectivity of the AAPS system? - -**Figure 3 (below)** shows one example of the **AAPS** system for a user who do not require any followers interacting with the system: - -![potential AAPS connectivity setup with no followers](./images/intro03.png) - -**Figure 4 (below)** shows the full potential of the **AAPS** system for a user who has followers and requires a monitor and send adjust the system remotely (like a child with T1D): - -![potential AAPS connectivity setup with followers](./images/intro04.png) - -## Q: How does AAPS get continually developed and improved? - -Most **AAPS** users use the fully tested **master** version of AAPS, which has been tested for bugs and problems, before being released to the community. Behind the scenes, the developers try out new improvements, and test these out in “developer” (**dev**) versions of **AAPS** with a user community who are happy to do bug updates at short notice. If the improvements work well, they are then released as a new “master” version of **AAPS**. Any new master release is announced on the Facebook group, so that the mainstream **AAPS** users can read about and update to the new master version. - -Some experienced and confident **AAPS ** users conduct experiments with emerging technologies and with dev versions of the **AAPS** app, which can be interesting for the less adventurous users to read about, without having to do it themselves! People tend to share these experiments on the Facebook group too. - -You can read more about some of these experiments and discussion on emerging tech here: - -[https://www.diabettech.com/](https://www.diabettech.com/) - -[https://bionicwookie.com/](https://bionicwookie.com/) - -## Q: Who can benefit? - -| User Type | -| ------------------------------------------- | -| ✔️ type 1 diabetic | -| ✔️ caregiver or parent of a type 1 diabetic | -| ✔️ blind users type 1 diabetic | -| ✔️ *clincians and healthcare professionals | - -The above table assumes that the user has access to both continuous gluocse monitor and insulin pump. - -*All data from **AAPS** can be made available to healthcare professionals via data sharing platforms, including NightScout that provides logging and real time monitoring of CGM data, insulin delivery, carbohydrate entries, predictions and settings. Nightscout records include daily and weekly reports which can aid healthcare professionals' discussions with type 1 patients with more accurate data on glycemic control and any behavioural considerations. - -## Q: What benefits can I get? - -With investment of your time, **AAPS** can potentially lead to: - -- alleviating the stress and burden of managing type 1 diabetes; - -- reducing the multitude of mundane decisions that arise from type 1 diabetes; - -- the provision of personalised and dynamic insulin dosing based on real-time data which can cut down the need for hypo treatments and reduce hyperglycemia episodes; - -- an increased knowledge of insulin management and confidence to better fine tune your settings; - -- the ability to create automatic settings (**automations**) that are tailored to fit in with your lifestyle; - -- improved sleep quality and overall reduction in the frequency of nighttime interventions; - -- remote monitoring and administration of insulin delivery for caregivers of type 1 diabetics; and - -- streamlining of all your portable diabetic equipment (continuous glucose monitor and insulin portable devices) by replacing them with an android phone controlled by **AAPS**. - - -Ultimately,**AAPS** can empower individuals to better manage their diabetes resulting in stable blood sugars and improved long term health outcomes. - ---- - -## AAPS First Steps - -Welcome. This is an introduction to aid beginners getting started with **AAPS** (or commonly referred to as "looping"). - -## Safety - -“_With great powers comes great responsibilities…_” - -**AAPS** is designed with an extensive set of safety features with limits imposed and gradually removed with completion of the **objectives **(predominately made up of multiple choice questions). An **AAPS** feature will be unlocked as the Objectives are successfully completed. This process will gradually allow the user to migrate from Open Loop to Closed Loop. - -This has been done to achieve the best possible experience with **AAPS** in order to prevent common mistakes that new users tend to make when starting to loop. The safety parameters have been built upon typical errors and general trends **AAPS** developers have observed with new users. Mistakes can happen because the beginner is inexperienced and too eager to get started with AAPS or has overlooked the required materials. Do not worry, we have all been there! - -## Key Principles - -The key principles and concepts of looping must be understood by the user before using **AAPS**. This is achieved by investing your personal time into reading the **AAPS** documentation, and completing the Objectives which is aimed to provide you with a solid platform for safe and effective use of **AAPS**. The volume of **AAPS** documentation may seem overwhelming at first but be patient and trust the process - with the proper approach, you'll get there! The overall process will depend upon the beginner’s progress and completion of objectives can typically take between 6 to 9 weeks . - -## Plan for hiccups - -At the preliminary stages of **AAPS**, you should expect to experience some hiccups whilst trying to fine tune your settings. **AAPS**’ glitches cannot be flushed out until the system is used in everyday life. Please plan accordingly and allow a sensible amount of time to troubleshoot and resolve such issues. - -## Flexibility/Adaptability - -Success with **AAPS** requires a proactive approach, a willingness to reflect on the BG data and flexibility to make the necessary adjustments to **AAPS** in order to improve your outcomes. Just as it is nearly impossible to learn to play a sport by reading about the rules alone, the same can be said of **AAPS**. - -## Technology compatibility - -There are limitations with **AAPS** as it is accessible for only certain types of insulin pumps or CGMs, and some technology may not be available for use in various countries. In order to avoid any disappointment or frustrations, please read please read Component Set Up (Section INSERT). - -## App Build Time - -The time to build the **AAPS**(under Section INSERT) depends on your level of expertise and technical ability. Typically for inexperienced users, it can take up to half a day or a full day (with help from the community) in order to build the **AAPS**. The process will significantly speed up as you become more experienced at building the **AAPS**. To aid the build process there are sections dedicated for: -- list of questions and answers for frequent errors that are likely to occur under FAQs (Section K); -- “How to install AAPS? (Section INSERT) which includes Troubleshooting subsection. - -## Keystore & configurations settings a export file - -A “keystore” is a password encrypted file unique to your own copy of **AAPS**. Your android phone uses it to ensure that nobody else can upgrade your own copy without the keystore. In short, as part of the **AAPS** build, you should: - -- save the your keystore file (.jks file used to sign your app) in a safe place; -- keep a note of your password for your keystore file. - -By doing the above, this will ensure that you can use that exact same keystore file each time an updated version of **AAPS** is created. On average, there will be 2-3 AAPS updates required each year. - -In addition, **AAPS** provides the ability to export all your configuration settings. This ensures that you can safely recover your system while changing phones, upgrading/reinstalling the application with minimum disruption. - -## Troubleshootng - -Please feel free to reach out to the AAPS community if there is anything you feel unsure about - there is no such thing as a silly question! All users with various levels of experience are encouraged to ask questions as necessary. Response times to questions are usually quick, typically only a few hours due to the volume of **AAPS** users. - -a) check the documentation; b) ask AAPS facebook group (https://www.facebook.com/groups/AndroidAPSUsers); and c) ask our discord channel. - -## Section overview - -AAPS documentation is made up of the following Sections: - -[INSERT ONCE SECTIONS /SUB SECTIONS AGREED] ---- diff --git a/docs/CROWDIN/pb/maintaining.md b/docs/CROWDIN/pb/maintaining.md deleted file mode 100644 index 98164a09e49b..000000000000 --- a/docs/CROWDIN/pb/maintaining.md +++ /dev/null @@ -1,28 +0,0 @@ -# Dummy - -## This is a dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - - -## This is another dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - - -## This is another another dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - diff --git a/docs/CROWDIN/pb/optimizing.md b/docs/CROWDIN/pb/optimizing.md deleted file mode 100644 index 98164a09e49b..000000000000 --- a/docs/CROWDIN/pb/optimizing.md +++ /dev/null @@ -1,28 +0,0 @@ -# Dummy - -## This is a dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - - -## This is another dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - - -## This is another another dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - diff --git a/docs/CROWDIN/pb/prepairing.md b/docs/CROWDIN/pb/prepairing.md deleted file mode 100644 index e729af5f4901..000000000000 --- a/docs/CROWDIN/pb/prepairing.md +++ /dev/null @@ -1,145 +0,0 @@ -# Prepairing - -## Guide to the Android APS doc - -### First Steps -Welcome. This is an introduction to aid beginners to the concept of Do-It-Yourself-APS (Android-Artificial-Pancreas-Systems “AAPS”) is commonly referred to as ‘looping’.. - -#### Safetys -“With great powers come great responsibilities…” - -AAPS is designed with an extensive set of safety features with limits imposed and gradually removed with completion of the [Objectives](https://androidaps.readthedocs.io/en/latest/Usage/Objectives.html) (predominately made up of multiple choice questions). An AAPS feature will be unlocked as the Objectives are successfully completed. This process will gradually allow the user to migrate from Open Loop to Closed Loop. - -This has been done to achieve the best possible experience with AAPS by preventing common mistakes new users tend to make when starting to loop. The safety parameters have been built upon typical errors and general trends AAPS developers have observed with new users. Mistakes can happen because the beginner is inexperienced and too eager to get started with AAPS or has overlooked the required materials. Do not worry, we have all been there! - -#### Key Principles - -The key principles and concepts of looping must be understood by the user before using AAPS. This is achieved by investing your personal time into reading the AAPS documentation, and completing the [Objectives](https://androidaps.readthedocs.io/en/latest/Usage/Objectives.html) which is aimed to provide you with a solid platform for safe and effective use of AAPS. The volume of AAPS documentation may seem overwhelming at first but be patient and trust the process - with the proper approach, you'll get there! The overall process will depend upon the beginner’s progress and completion of objectives which typically take between 6 to 9 weeks . - -#### Plan for hiccups - -At the preliminary stages of AAPS, you should expect to experience some hiccups whilst trying to fine tune your settings. AAPS’ glitches cannot be flushed out until the system is used in everyday life. Please plan accordingly and allow a sensible amount of time to troubleshoot and resolve such issues. - -#### Flexibility/Adaptability - -Success with AAPS requires a proactive approach, a willingness to reflect on the BG data and flexibility to make the necessary adjustments to AAPS in order to improve your outcomes. Just as it is nearly impossible to learn to play a sport by reading about the rules alone, the same can be said of AAPS. - -#### Technology compatibility -There are limitations with AAPS as it is accessible for only certain types of insulin pumps or CGMs, and some technology may not be available for use in various countries. In order to avoid any disappointment or frustrations, please read [Component Set Up (Section E).](https://androidaps.readthedocs.io/en/latest/Configuration/BG-Source.html) - -#### App Build time -The time to build the AAPS (under Section D) depends on your level of expertise and technical ability. Typically for inexperienced users, it can take up to half a day or a full day (with help from the community) in order to build the AAPS. The process will significantly speed up as you become more experienced at building the AAPS.  - -To aid the build process there are sections dedicated for: - -- list of questions and answers for frequent errors that are likely to occur under [FAQs (Section](https://androidaps.readthedocs.io/en/latest/Getting-Started/FAQ.html) K); - -- “[How to install AAPS](https://androidaps.readthedocs.io/en/latest/Installing-AndroidAPS/Building-APK.html)? (Section D) which includes [Troubleshooting](https://androidaps.readthedocs.io/en/latest/Usage/troubleshooting.html) subsection. - - -#### Keystore & configuration settings export  file - -A “keystore” is a password encrypted file unique to your own copy of AAPS. Your android phone uses it to ensure that nobody else can upgrade your own copy without the keystore.In short, as part of the AAPS build, you should: - -1. save the your keystore file (.jks file used to sign your app) in a safe place; - -2. keep a note of your password for your keystore file. - - -By doing the above, this will ensure that you can use that exact same keystore file each time an updated version of AAPS is created. On average, there will be 2-3 updates to the AAPS required each year. In addition, AAPS provides the ability to [export all your configuration settings](https://androidaps.readthedocs.io/en/latest/Usage/ExportImportSettings.html). This ensures that you can safely recover your system while changing phones, upgrading/reinstalling the application with minimum disruption.  - -#### Troubleshooting - -Please feel free to reach out to the AAPS community if there is anything you feel unsure about - there is no such thing as a silly question!  All users with various levels of experience are encouraged to ask questions as necessary. Response times to questions are usually quick, typically only a few hours due to the volume of AAPS users.  - -##### [check the documentation](https://androidaps.readthedocs.io/en/latest/index.html) - -##### [ask our facebook group](https://www.facebook.com/groups/AndroidAPSUsers/) - -##### [ask our discord channel](https://discord.com/channels/629952586895851530/629954570394533889) - -#### Section overview - -AAPS documentation is made up of the following Sections: - -##### [Getting started](https://androidaps.readthedocs.io/en/latest/Getting-Started/Safety-first.html) - -This is a must read to understand the general concept of what an artificial pancreas system is designed to do. - -##### [What do I need?](https://androidaps.readthedocs.io/en/latest/Module/module.html) - -This explains AAPS’ compatibility with CGMs (Continuous Glucose Monitors) and insulin pumps. It also provides a guide on the correct assembly of an AAPS system to ensure that it functions correctly in everyday life. - -##### How to install AAPS - -This section is the manual for building the AAPS. Strict adherence to the step-by-step instructions are required in order to successfully build the AAPS. Please take your time. - -##### [Component Setup](https://androidaps.readthedocs.io/en/latest/Configuration/BG-Source.html) - -This explains how to properly integrate each of the various different separate component parts into AAPS, as well as how to set them up to work as seamlessly as possible together. All components are listed under the separate sections: CGM/FGM, xDrip Settings, Pumps, Phones, Nightscout setup, and Smartwatches. The sensor (BG) values and control of the insulin pump are particularly important information to understand. - -##### Configuration - -This explains how to set and configure your ‘Profile’, ‘Insulin’, ‘BG Source’, ‘Pump’, ‘Sensitivity Detection’, ‘APS’, ‘Loop’, ‘Treatments’. - -##### AAPS Usage - -This section provides a breakdown of the features provided by AAPS. - -##### [General Hints](https://androidaps.readthedocs.io/en/latest/Usage/Timezone-traveling.html) - -Useful tricks on how to tackle looping issues such as time zones, and daylight saving (i.e. Spring Forward/ - Fall Back). - -##### [AAPS](https://androidaps.readthedocs.io/en/latest/Getting-Started/Screenshots.html) for Children - -This is designed for parents or caregivers who want to build an AAPS for their child. It also explains the extra features necessary in order to support and safely control your child’s AAPS remotely.

The concepts in this section should be fully understood in order to competently use this feature. - -##### Troubleshooting - -This section contains links to help solve issues when building or using AAPS. - -##### FAQ - -This section addresses specific questions which tend to come up when building or using AAPS. - -##### [Glossary](https://androidaps.readthedocs.io/en/latest/Getting-Started/Glossary.html) - -This contains a list of the acronyms (or short-term names) or defined terms developed specifically for AAP (for instance, the terms ‘ISF’ or ‘TT’ have special meanings in AAPS). - -##### [Where to go for help](https://androidaps.readthedocs.io/en/latest/Where-To-Go-For-Help/Background-reading.html)? - -This section is aimed to provide new users with links on resources in order to get help including accessing community support made up of both new and experienced users who can clarify questions, and resolve the usual pitfalls that come with AAPS. - -##### For Clinicians - -This is a section for the clinicians who have expressed interest in open source artificial pancreas technology such as AAPS, or for patients who want to share such information with their clinicians. | - -## what are we going to build? - -### An Android Phone Application - -At the core, AAPS is an android application running from a phone. You are going to build it from scratch by installing tools to download the sourcecode and build the actual application. - -### A reporting server NightScout (or Tidepool) - -In order to fully use AAPS properly you will want to setup a nightscout server. It is used to collect data from AAPS over time and possibly communicate to the application. It is required for parents who want to oversee their children AAPS sessions. It is also key to share data between clinicians and patients to perform analysis over time. - -## How long will it take? - -## Who might AAPS not be suitable for? - -## Where can I get help? - -## Requirements - -### medical - -### technical - -### personal - -### CGMs - -### Insulin Pump - -### Reporting (NS, Tidepool) \ No newline at end of file diff --git a/docs/CROWDIN/pl/Configuration/Dexcom.md b/docs/CROWDIN/pl/Configuration/Dexcom.md deleted file mode 100644 index cb267e23c069..000000000000 --- a/docs/CROWDIN/pl/Configuration/Dexcom.md +++ /dev/null @@ -1,32 +0,0 @@ -# Dexcom G6 - -## Basics first - -* Follow [general CGM hygiene recommendations](../Configuration/BG-Source#cgm-hygiene) -* [Special recommendations for Dexcom G6 and DIY systems](../Configuration/BG-Source#dexcom-g6-diy-systems) *For G6 transmitters manufactured after fall/end of 2018 please make sure to use one of the [latest nightly built xDrip+ versions](https://github.com/NightscoutFoundation/xDrip/releases). Those transmitters have a new firmware and latest stable version of xDrip+ (2019/01/10) cannot deal with it. - -## Setting sensor - -When setting sensor, it is recommended not to press the inserter too firmly in order to avoid bleeding. The sensor thread should not come into contact with blood. - -After setting the sensor, the transmitter can be clicked into the sensor holder. Caution! First click in the square side and then press down the round side. - -## Troubleshooting - -### Connection problems - -Bluetooth connection may be disturbed by other nearby Bluetooth devices such as blood glucose meters, headsets, tablets or kitchen devices such as microwave ovens or ceramic hobs. In this case xdrip does not display any BG values. When bluetooth connection is reestablished the data is backfilled. - -### Sensor Errors - -If recurring sensor errors occur try selecting a different body site to set your sensor. The sensor thread should not come into contact with blood. - -Often a "Sensor Error" can be corrected by immediate drinking and massage around the sensor! - -### Jumpy values - -You might try to change settings for noise blocking in xdrip (Settings - Inter-App Settings - Noise Blocking) i.e. "Block Very High noise and worse". See also [Smoothing BG data](../Usage/Smoothing-Blood-Glucose-Data-in-xDrip.md). - -### New transmitter with running sensor - -If you happen to change transmitter during a running sensor session you might try to remove the transmitter without damaging the sensor mount. A video can be found at . \ No newline at end of file diff --git a/docs/CROWDIN/pl/Configuration/EOFLOW.md b/docs/CROWDIN/pl/Configuration/EOFLOW.md deleted file mode 100644 index e697feadb732..000000000000 --- a/docs/CROWDIN/pl/Configuration/EOFLOW.md +++ /dev/null @@ -1,155 +0,0 @@ -# EOPatch2 Instruction Manual - -The patch requires the use of rapid-acting U-100 type insulin, such as NovoRapid or Humalog. Use a rapid-acting insulin that is suitable for you according to your doctor’s prescription and inject the prescribed dosage. - -The smallest injectable dose of insulin when using the patch is 0.05 U. The Profile BAS should therefore be set at a minimum value of 0.05 U/hr or more and an interval of 0.05 U/hr, as otherwise there may be an error between the estimated total infusion amount in the Profile and the actual infusion amount in the patch. Likewise, the bolus must also be set and infused with a minimum infusion volume of 0.05 U. - -## Pump Setup -1. On the AndroidAPS home screen, click the hamburger menu in the upper left corner and go to Config Builder. -1. Select 'EOPatch2' in the Pump section. -1. Press the Back key to return to the home screen. - -![Bild1](../../images/EOPatch/Bild1.png) ![Bild2](../../images/EOPatch/Bild2.png) - -## Settings -Select EOPATCH2 at the top of the home screen to go to the EOPATCH2 tab. - -Select the EOPatch2 Preferences menu by clicking the three dots in the upper right corner. - -The EOPatch2 Preferences menu offers a menu to set 3 types of notifications. - -### Low reservoir Alerts -A warning appears when the amount of insulin remaining in the reservoir reaches the set value or less while using the patch. It can be set from 10 to 50U in 5U increments. - -### Patch expiration Reminder -This is a reminder to notify you of the time remaining before the current patch expires. It can be set from 1 to 24 hours in 1 hour increments. The initial setting value is 4 hours. - -### Patch buzzer Reminder -This is a reminder function for injections other than basal injection. If you are using an (extended) bolus injection or a temporary basal injection, the patch will make a buzzer sound when the injection starts and when the injection is complete. The initial setting value is Off. - -![Bild3](../../images/EOPatch/Bild3.png) - -## Connecting the Patch - -### Move to patch connection screen - -Select EOPATCH2 at the top of the home screen and click the ACTIVATE PATCH button at the bottom left. - -![Bild4](../../images/EOPatch/Bild4.png) - -### Connecting the patch -Insert the syringe needle into the insulin inlet on the patch and then slowly push the piston to inject the insulin. When insulin is filled with more than 80U, the patch makes a booting sound (1 buzzer) and boots. After confirming the buzzer sound, click the START PAIRING button on the screen. - -[Warning] - -- Do not turn the needle action lever until instructed. It can cause serious problems during injection or safety checks otherwise. -- The amount of insulin that can be injected into the patch is 80~200U. If you inject less than 80U into the patch initially, the patch will not work. -- Take the insulin to be put into the patch from the refrigerator and leave it at room temperature for 15 to 30 minutes beforehand. The temperature of the insulin to be injected must be at least 10°C. - -![Bild5](../../images/EOPatch/Bild5.png) - -### patch pairing -The Patch pairing screen will be displayed, and pairing will be attempted automatically. If communication is successful, the Bluetooth pairing request notification appears. Click OK and when the Bluetooth pairing request notification appears a second time with the authentication code, select OK again. - -[Warning] - -- For pairing, the patch and the smartphone must be located within 30 cm of each other. -- After the patch booting is completed, the patch will beep every 3 minutes until the pairing is complete. -- After booting the patch, the patch application must be completed via the app within 60 minutes. If the application cannot be completed within 60 minutes, the patch should be discarded. - -![Bild6](../../images/EOPatch/Bild6.png) ![Bild7](../../images/EOPatch/Bild7.png) ![Bild8](../../images/EOPatch/Bild8.png) - - -### patch preparation -After removing the adhesive tape of the patch, check if the needle is sticking out. If there are no problems with the patch, click NEXT. - -![Bild9](../../images/EOPatch/Bild9.png) - -### Patch attachment -Insulin should be injected in a spot with subcutaneous fat but few nerves or blood vessels, so it is recommended to use the abdomen, arm, or thigh for the patch attachment site. Choose a patch attachment site and apply the patch after disinfecting the location. - -[Warning] - -- Make sure to straighten the side of the patch tape attached to the body evenly, so that the patch adheres completely to the skin. -- If the patch does not stick completely, air may enter between the patch and the skin, which can weaken the adhesive strength and waterproof effect of the patch. - -![Bild10](../../images/EOPatch/Bild10.png) - -### Safety Check -When patching is complete, touch Start Safety Check. When the safety check is completed, the patch will beep once. - -[Warning] - -- For safe use, do not turn the needle action lever until the safety check has been completed. - -![Bild11](../../images/EOPatch/Bild11.png) ![Bild12](../../images/EOPatch/Bild12.png) - - -### Inserting the needle -The needle is inserted by holding around the patch and turning the needle action lever more than 100° in the upward direction of the lever. There is a buzzer sound when the needle is inserted correctly. Turn the needle action lever further clockwise to release the lever. Click NEXT. - -[Caution] - -- If you go to the next step without the buzzer sounding, a needle insertion error warning will appear. - -## Discarding the patch -Patches must be replaced in the case of low insulin levels, usage expiration, and defects. The recommended usage period for each patch is 84 hours after booting the patch. - -### Discarding the patch -Select EOPATCH2 at the top of the home screen and click the DISCARD/CHANGE PATCH button at the bottom. On the next screen, click the DISCARD PATCH button. A dialog box appears to confirm once more and if you select the DISCARD PATCH button, the disposal is completed. - -![Bild13](../../images/EOPatch/Bild13.png) ![Bild14](../../images/EOPatch/Bild14.png) ![Bild15](../../images/EOPatch/Bild15.png) ![Bild16](../../images/EOPatch/Bild16.png) - -## Suspending and Resuming Insulin Delivery -Suspending insulin delivery also cancels both extended bolus and temporary basal. When resuming insulin delivery, the canceled extended bolus and temporary basal will not be resumed. And when insulin delivery is suspended, the patch will give a sound every 15 minutes. - -### Suspending insulin delivery -Select EOPATCH2 at the top of the home screen and click the SUSPEND button at the bottom right. When you select CONFIRM in the confirmation box, a time selection box appears. If you select the CONFIRM button after selecting the time, the insulin delivery will be suspended for the set amount of time. - -![Bild17](../../images/EOPatch/Bild17.png) ![Bild18](../../images/EOPatch/Bild18.png) ![Bild19](../../images/EOPatch/Bild19.png) - - -### Resuming insulin delivery -Select EOPATCH2 at the top of the home screen and click the RESUME button at the bottom right. Insulin delivery will resume by selecting CONFIRM in the confirmation dialog box. - -![Bild20](../../images/EOPatch/Bild20.png) ![Bild21](../../images/EOPatch/Bild21.png) - -## Alarms/Warnings - -### Alarm - -Alarms are issued for emergency situations of the highest priority and require immediate action. The alarm signal does not disappear or time out until it is acknowledged. An alarm occurs when there is a problem with the patch being used, so there may be cases where the patch in use needs to be discarded and replaced with a new patch. The warning is displayed as a dialog box and switching to another screen is not possible until processing is completed. - -![Bild22](../../images/EOPatch/Bild22.png) ![Bild23](../../images/EOPatch/Bild23.png) - -The different types of alarms are explained below. - -| Alarms | Explanation | -| -------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| Empty reservoir | Occurs when the patch’s reservoir runs out of insulin. | -| Patch expired | Occurs when the patch usage time has expired, and no further insulin injections are possible. | -| Occlusion | Occurs when it appears that the patch's insulin inlet is clogged. | -| Power on self-test failure | Occurs when the patch finds an unexpected error during the post-boot self-test process. | -| Inappropriate temperature | Occurs when the patch is outside the normal operating temperature range during patch application and use. To deal with this alarm, move the patch to an appropriate operating temperature (4.4 to 37°C) condition. | -| Needle insertion Error | Occurs when needle insertion is not normal during the patch application process. Check that the needle insertion edge of the patch and the needle activation button are in a straight line. | -| Patch battery Error | Occurs just before the patch’s internal battery runs out and powers off. | -| Patch activation Error | Occurs when the app fails to complete the patching process within 60 minutes after the patch is booted. | -| Patch Error | Occurs when the patch encounters an unexpected error while applying and using the patch. | - -### Warning - -A warning occurs in a medium or low-priority situation. When a warning occurs, it is displayed as a notification in the Overview screen. - -![Bild24](../../images/EOPatch/Bild24.png) - -The different types of warnings are explained below. - -| Warnings | Explanation | -| ---------------------------- | ------------------------------------------------------------------------------------------------------------------------------------- | -| End of insulin suspend | Occurs when the time set by the user has elapsed after the insulin infusion suspension has been completed. | -| Low reservoir | Occurs when the remaining amount of insulin in the patch is below the set amount. | -| Patch operating life expired | Occurs when the patch usage period is over. | -| Patch will expire soon | Occurs 1 hour before the patch must be discarded. | -| Incomplete Patch activation | Occurs when more than 3 minutes have elapsed due to an interruption during patch application in the stage after pairing is completed. | -| Patch battery low | Occurs when the patch's battery is low. | - diff --git a/docs/CROWDIN/pl/Configuration/Hardware/index.md b/docs/CROWDIN/pl/Configuration/Hardware/index.md deleted file mode 100644 index 15ff0b00a776..000000000000 --- a/docs/CROWDIN/pl/Configuration/Hardware/index.md +++ /dev/null @@ -1,27 +0,0 @@ -# Hardware-Configuration - -## Configuration - -## BG Source - -- [BG Source](../BG-Source.md) -- [xDrip+ Settings](../xDrip.md) -- [Dexcom G6 hints](../Dexcom.md) -- [Smoothing blood glucose data](../../Usage/Smoothing-Blood-Glucose-Data-in-xDrip.md) - -## Pumps - -- [Dana-R pump](../DanaR-Insulin-Pump.md) -- [Dana-RS pump](../DanaRS-Insulin-Pump.md) -- [Accu-Chek Combo pump](../Accu-Chek-Combo-Pump.md) -- [Accu-Chek Insight pump](../Accu-Chek-Insight-Pump.md) -- [Medtronic pump](../MedtronicPump.md) - -## Telefony - -- [Jelly Pro Settings](../../Usage/jelly.md) -- [Huawei Settings](../../Usage/huawei.md) - -## Smartwatch - -- [Watchfaces](../Watchfaces.md) diff --git a/docs/CROWDIN/pl/Getting-Started/ClosedLoop.md b/docs/CROWDIN/pl/Getting-Started/ClosedLoop.md deleted file mode 100644 index cbf82cf21392..000000000000 --- a/docs/CROWDIN/pl/Getting-Started/ClosedLoop.md +++ /dev/null @@ -1,55 +0,0 @@ -# What is a Closed Loop System? - -![AAPS is like an autopilot](../images/autopilot.png) - -An artificial pancreas closed loop system combines different components in order to make diabetes management easier for you. In her great book [Automated Insulin Delivery](https://www.artificialpancreasbook.com/) Dana M. Lewis, one of the founders of the open source closed loop movement, calls it an ["autopilot for your diabetes"](https://www.artificialpancreasbook.com/3.-getting-started-with-your-aps). But what does that mean? - -**Autopilot in an aircraft** - -The autopilot does not do the complete job and does not give the possibility to the pilot to sleep throughout the entire flight. It facilitates the work of the pilots. It relieves them of the burden of permanently monitoring the aircraft and the flight attitude. This allows the pilot to concentrate on monitoring the airspace and controlling the autopilot's functions. - -The autopilot receives signals from various sensors, a computer evaluates them together with the pilot's specifications and then makes the necessary adjustments. The pilot no longer has to worry about the constant adjustments. - -**Closed Loop System** - -The same applies to an artificial pancreas closed loop system. It does not do the whole job, you still have to take care of your diabetes. A closed loop system combines the sensor data from a CGM/FGM with your diabetes management specifications such as basal rate, insulin sensitivity factor and carb ratio. From this it calculates treatment suggestions and implements these permanent small adjustments in order to keep your diabetes within the target range and to relieve you. This leaves more time for your life "next to" diabetes. - -Just as you don't want to get on a plane where only the autopilot flies without human supervision, a closed loop system helps you with your diabetes management, but always needs your support! **Even with a closed loop you can't just forget your diabetes!** - -Just as the autopilot depends on the sensor values as well as the pilot's specifications, a closed loop system needs appropriate input such as basal rates, ISF and carb ratio to support you successfully. - -## Open Source Artificial Pancreas Closed Loop Systems - -At present there are three major open source closed loop systems available: - -### AndroidAPS (AAPS) - -AAPS is described in detail in [this documentation](./WhatisAndroidAPS.html). It uses an Android Smartphone for calculation and control of your insulin pump. It is in strong collaboration with OpenAPS (i.e. they share algorithms). - -Compatible [pumps](../Hardware/pumps.md) are: - -- [DanaR](../Configuration/DanaR-Insulin-Pump.md) / [DanaRS & Dana-i](../Configuration/DanaRS-Insulin-Pump.html) -- [Accu-Chek Combo](../Configuration/Accu-Chek-Combo-Pump.md) -- [Accu-Chek Insight](../Configuration/Accu-Chek-Insight-Pump.md) -- [Diaconn G8](../Configuration/DiaconnG8.md) -- [Omnipod DASH](../Configuration/OmnipodDASH.md) -- [Omnipod Eros](../Configuration/OmnipodEros.md) -- some old [Medtronic pumps](../Configuration/MedtronicPump.md) - -### OpenAPS - -[OpenAPS](https://openaps.readthedocs.io) was the first Open Source Closed Loop System. It uses a small computer such as Raspberry Pi or Intel Edison. - -Compatible pumps are: - -- some old Medtronic pumps - -### Loop for iOS - -[Loop for iOS](https://loopkit.github.io/loopdocs/) is the Open Source Closed Loop System to be used with Apple iPhones. - -Compatible pumps are: - -- Omnipod DASH -- Omnipod Eros -- some old Medtronic pumps diff --git a/docs/CROWDIN/pl/Getting-Started/GlossaryTest.md b/docs/CROWDIN/pl/Getting-Started/GlossaryTest.md deleted file mode 100644 index eef7a7722105..000000000000 --- a/docs/CROWDIN/pl/Getting-Started/GlossaryTest.md +++ /dev/null @@ -1,391 +0,0 @@ -# Słowniczek pojęć - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
TerminOpiszobacz teżwięcej szczegółów na
AAPSAndroidAPS - system hybrydowej sztucznej trzustki  
AMAadvance meal assist - zaawansowany algorytm obsługi węglowodanówMA/SMBWiki - AMA
Android autonotyfikacje AAPS wyświetlana jest w samochodzie na kompatybilnych deskach rozdzielczych oraz systemach informacyjno-rozrywkowch Wiki - android auto
APKplik instalacyjny oprogramowania (pakiet systemu Android) Wiki - budowanie APK
Autosensokreślenie wrażliwości na insuline jako efekt ćwiczeń, hormonów itp. DIABETTECH - Autosens
Azureplatforma do hostowania Nightscouta w chmurzeHeroku / NightscoutAzure
BATlampka stanu niski poziom baterii na ekranie głównymCAN / RES / SENPreferencje
Zrzuty ekranu
BGstężenie glukozy we krwi  
BGIoddziaływanie insuliny we krwi - stopień, do którego BG powinno rosnąć lub spadać w oparciu o działanie samej insuliny  
Źródła danych o poziomie cukru we krwi (BG) - CGM/FGMźródło stężenia glukozy we krwi - miejsce z którego pochodzą dane o stężeniu glukozy we krwiCGM / FGMWiki - źródło BG
Blukon Nightreadertransmiter bluetooth dla Freestyle Libre zmieniający go w CGMBlueReader / MiaoMiaoAmbrosia Blukon Nightreader
BRdawka bazowa  
CAGEcanula age - displayed in Nightscout if information was entered in actions tab / menu tab or through AAPS actions tab 'prime'Nightscout 
CANstatus light overdue canula change on homescreenBAT / RES / SENPreferencje
Zrzuty ekranu
CGMcontinuous glucose monitor  
Zamknięta pętla/Closed Loopclosed-loop systems make automatic adjustments to basal delivery, without needing user-approval, based on an algorithmOpen loopWiki closed loop
COBcarbs on board  
DIAduration of insulin action Wiki insulin types
DIABETTECH - DIA
DSTdaylight savings time Wiki DST
eCarbs"extended carbs" - carbs split up over serveral hours (i.e. lot of fat/protein)
extended boluses you might know from regular pump therapy do not make much sense when looping		SMBWiki - eCarbs
eCarbs use case
FGMflash glucose monitor (Freestyle Libre) Wiki - źródło BG
gitversion-control system for tracking changes in computer files and coordinating work on those files
-> neccessary for APK updates		 Wiki - update APK
Githubweb-based hosting service for version control using Git
-> storage of source code		 Github AndroidAPS
Glimpapp to collect values from Freestyle Libre Nightscout with Glimp
Herokuplatforma do hostowania Nightscouta w chmurzeAzure / NightscoutHeroku
IC (or I:C)insulin to carb ratio (How many carbs are covered by one unit of insulin?)  
IOBinsulin on board - insulin active in your body  
ISFinsulin sensitivity factor - the expected decrease in BG as a result of one unit of insulin  
LGSLow Glucose Suspend
AAPS will reduce basal if blood glucose is dropping. But if blood glucose is rising then it will only increase basal if the IOB is negative (from a previous LGS), otherwise basal rates will remain the same as your selected profile. You may temporarily experience spikes following treated hypos without the ability to increase basal on the rebound.		objective 6 
LineageOSfree and open-source operating system for smartphones etc.
alternative OS for smartphones not running Android 8.1 (Oreo)
(when using Accu-Chek Combo)		 Wiki - Combo pump
Log filesrecord of all AAPS actions (useful for trubbleshooting and debugging) Wiki - log files
maxIOBsafety feature - maximum total IOB AAPS can't go over Wiki - maxIOB
Wiki - SMB
MiaoMiaotransmiter bluetooth dla Freestyle Libre zmieniający go w CGMBlueReader / Blukon NightreaderMiaoMiao
min_5m_carbimpactsaftey feature - default carb decay at times when carb absorption can’t be dynamically worked out based on your bloods reactions Wiki - config builder
Nightscoutopen source project to access and report CGM dataNightscout ReporterNightscout
NS Clientpart of AAPS to connect to your Nightscout site Wiki - NS Client
Nightscout ReporterTool from fellow looper to generate PDFs reports from Nightscout dataNightscoutNightscout Reporter
NS Reporter @ Facebook
Cele (samouczek)learning program within AAPS guiding you step by step from open to closed loop Wiki - objectives
OpenAPSopen artificial pancreas system
APS run on small computers (i.e. Raspberry Pie)
AAPS uses some of the OpenAPS features		 OpenAPS docs
Otwarta pętla/Open Loopsystem will suggest recommended adjustments which have to be performed manually on the pumpZamknięta pętla/Closed LoopWiki - config builder
Oref0 / Oref1sensitivity detection
"reference design implementation version 0/1" - the key algorithm behind OpenAPS		 Wiki - sensitivity detection
Peak timetime of maximum effect of insulin given Wiki - config builder
PHpump history (entry in treatments tab) Screenshots
Prognozy/Predictionspreditions for BG in the future based on different calculations Wiki - predition lines
Profilbasic treatment settings (basal rate, DIA, IC, ISF, BG target)
can be defined locally or through Nightscout		NightscoutWiki - profile
Zmiana profilu(temporary) change of profile used or percentual increase/decrease Wiki - profile switch
RESstatus light overdue reservoir change on homescreenBAT / CAN / SENPreferencje
Zrzuty ekranu
RileyLinkopen source hardware device to bridge Bluetooth Low Energy (BLE) to 916MHz wireless communication (used for old Medtronic pumps)OpenAPS 
SAGEsensor age - displayed in Nightscout if information was entered in the actions tab / menuNightscout 
SENstatus light sensor change on homescreenBAT / CAN / RESPreferencje
Zrzuty ekranu
Sensivity detectionokreślenie wrażliwości na insuline jako efekt ćwiczeń, hormonów itp. DIABETTECH - Autosens
Sensor noiseunstable CGM readings leading to "jumping" values Wiki - sensor noise
SMBsuper micro bolus
advanced feature for faster BG adjustment		UAMWiki - SMB
Super bolusshift of basal to bolus insulin for faster BG adjustment John Walsh - The Super Bolus
TBBtotal base basal (sum of basal rate within 24 hours)  
TBRtemporary basal rate  
TDDtotal daily dose (bolus + basal per day)  
TTtemporary target
temporary increase/decrease of BG target (range)		 Wiki - temp targets
UAMunannounced meals - detection of significant increase in glucose levels due to meals, adrenaline or other influences and attempt to adjust this with SMBSMBWiki - SMB
Virtual pumpoption to try AAPS functions or for PWD using a pump model with no AndroidAPS driver for loopingOtwarta pętla/Open Loop 
WallpaperAndroidAPS background imagesee phones page
xDrip / xDrip+open source software to read CGM systems xDrip+
xDrip
Zero-temptemporary basal rate with 0% (no basal insulin delivery)  
See also https://openaps.readthedocs.io/en/latest/docs/Resources/glossary.html
diff --git a/docs/CROWDIN/pl/Getting-Started/Safety-first.md b/docs/CROWDIN/pl/Getting-Started/Safety-first.md deleted file mode 100644 index bc1909021769..000000000000 --- a/docs/CROWDIN/pl/Getting-Started/Safety-first.md +++ /dev/null @@ -1,41 +0,0 @@ -# Najważniejsze jest bezpieczeństwo - -**When you decide to build your own artificial pancreas, it's always important to think about security and safety, and to understand the impact of all your actions** - -## Ogólnie - -- AAPS is a just a tool to help you manage diabetes, it is not a fully automated system you can install and forget! -- Do not assume that AAPS will never make mistakes. To urządzenie przejmuje kontrolę nad podawaniem insuliny: oglądaj je cały czas, zrozum, jak działa i naucz się interpretować jego działanie. -- Remember that, once paired, the phone can instruct the pump to do anything. Only use this phone for AAPS and, if being used by a child, essential communications. Nie instaluj niepotrzebnych aplikacji lub gier (!!!), które mogłyby wprowadzać złośliwe oprogramowanie, takie jak trojany, wirusy lub boty, które mogłyby zakłócać działanie systemu. -- Install all security updates provided by your phone manufacturer and Google. -- You might also need to change your diabetes habits as you change your therapy by using a closed loop system. I.e. some people report, they need less hypo treatments as AAPS has already reduced insulin. - -## Komunikator SMS - -- AAPS allows you to control a child's phone remotely via text message. Jeśli włączysz ten komunikator SMS, zawsze pamiętaj, że telefon skonfigurowany do wydawania poleceń zdalnych może zostać skradziony. Dlatego zawsze chroń go przynajmniej kodem PIN. -- AAPS will also inform you by text message if your remote commands, such as a bolus or a profile change, have been carried out. Zaleca się takie ustawienie funkcji sterowania pompą poprzez sms, aby teksty potwierdzające były wysyłane na co najmniej dwa różne numery telefonów, w przypadku kradzieży jednego z telefonów odbierających drugi telefon odbierze informację o zmianach. - -(Safety-first-aaps-can-also-be-used-by-blind-people)= -## AAPS can also be used by blind people - -On Android devices TalkBack is part of the operating system. It is a program for screen orientation via voice output. With TalkBack you can operate your smartphone as well as AAPS blind. - -We users create the AAPS app ourselves with Android Studio. Many use Microsoft Windows for this purpose, where there is the Screenreader analogous to TalkBack. Since Android Studio is a Java application, the "Java Access Bridge" component must be enabled in the Control Panel. Otherwise, the screen reader of the PC will not speak in Android Studio. - -To do this, please proceed as follows: - -- Press WINDOWSTASTE and enter "Control Panel" in the search field, open with Enter. It opens: "All Control Panel Items". -- Press the letter C to get to "Center for Ease of Use", open with Enter. -- Then open "Use computer without a screen" with Enter. -- There, at the bottom, you will find the checkbox "Enable Java Access Bridge", select it. -- Done, just close the window! The screen reader should work now. - -```{note} -**IMPORTANT SAFETY NOTICE** - -The foundation of AAPS safety features discussed in this documentation is built on the safety features of the hardware used to build your system. It is critically important that you only use a tested, fully functioning FDA or CE approved insulin pump and CGM for closing an automated insulin dosing loop. Hardware or software modifications to these components can cause unexpected insulin dosing, causing significant risk to the user. If you find or get offered broken, modified or self-made insulin pumps or CGM receivers, *do not use* these for creating an AAPS system. - -Additionally, it is equally important to only use original supplies such as inserters, cannulas and insulin containers approved by the manufacturer for use with your pump or CGM. Using untested or modified supplies can cause CGM inaccuracy and insulin dosing errors. Insulin is highly dangerous when misdosed - please do not play with your life by hacking with your supplies. - -Last not least, you must not take SGLT-2 inhibitors (gliflozins) as they incalculably lower blood sugar levels. The combination with a system that lowers basal rates in order to increase BG is especially dangerous as due to the gliflozin this rise in BG might not happen and a dangerous state of lack of insulin can happen. -``` diff --git a/docs/CROWDIN/pl/Getting-Started/Sample-Setup.md b/docs/CROWDIN/pl/Getting-Started/Sample-Setup.md deleted file mode 100644 index 65f2f0c2c721..000000000000 --- a/docs/CROWDIN/pl/Getting-Started/Sample-Setup.md +++ /dev/null @@ -1,151 +0,0 @@ -# Sample setup: Samsung S7, Dana RS, Dexcom G6 and Sony Smartwatch - -![Przykładowa konfiguracja](../images/SampleSetup.png) - -## Opis - -W tym zestawie, telefon Samsung Galaxy S7 jest wykorzystywany jako centrum sterujące loopa. The slightly modified Dexcom App reads glucose values from the Dexcom G6 CGM. AndroidAPS is used to control the Dana RS insulin pump from Korean manufacturer SOOIL via bluetooth. Dodatkowe urządzenia nie są wymagane. - -Ponieważ aplikacja Dexcom oferuje ograniczone możliwości ustawienia alarmów, do tego celu używamy dodatkowej aplikacjai typu open source - xDrip +, może być ona używana nie tylko do określenia alarmów dla niskich i wysokich stanów cukrów ale również określenia dodatkowych alarmów zgodnych z indywidualnymi potrzebami. - -Dodatkowo można skorzystać z zegarka z systemem Android wear do pokazywania wartości cukrów oraz innych informacji dostepnych w AndroidAPS (w tym przykladowym zestawie korzystamy z Sony Smartwatch 3 (SWR50)). Zegarek może nawet służyć do sterowania AndroidAPS (tj. podawanie w sposób dyskretny bolusa na posiłek). - -System działa w trybie offline. Oznacza to że dla prawidłowego dziłania nie ma potrzeby posiadania połączenia do Internetu na telefonie. - -Niemniej jednak, dane są automatycznie przesyłane do Nightscout "w chmurze" po nawiązaniu połączenia do Internetu. W ten sposób można zapewnić kompleksowe raporty podczas wizit u lekarza lub współdzielić bieżące wartości z członkami rodziny. Można również ograniczyć możliwość wysylania danych do Nightscout tylko do sytuacji w której aktywne jest połączenie do zdefiniowanych sieci WI-FI, w ten sposób możesz wciąż korzystać z różnych raportów dostepnych w Nightscout. - -## Wymagane elementy - -1. Samsung Galaxy S7 - - * Alternatives: see [list of tested phones and watches](https://docs.google.com/spreadsheets/d/1gZAsN6f0gv6tkgy9EBsYl0BQNhna0RDqA9QGycAqCQc/edit) for AndroidAPS - -2. [DanaRS](http://www.sooil.com/eng/product/) - - * Inne pompy: - * [Accu-Chek Combo](../Configuration/Accu-Chek-Combo-Pump.md) - * [Pompa Accu-Chek Insight](../Configuration/Accu-Chek-Insight-Pump.md) - * [DanaR](../Configuration/DanaR-Insulin-Pump.md) - * [Some old Medtronic pumps (additionally needed: RileyLink/Gnarl hardware, Android Phone with bluetooth low energy / BLE-chipset)](../Configuration/MedtronicPump.md) - * Other pumps might be available in the future, see [future possible pump drivers](Future-possible-Pump-Drivers.md) for details. - -3. [Dexcom G6](https://dexcom.com) - - * Alternatives: see list of possible [BG sources](../Configuration/BG-Source.md) - -4. Opcjonalnie: Sony Smartwatch 3 (SWR50) - - * Alternatives: All [watches with Google Wear OS](https://wearos.google.com/intl/de_de/#find-your-watch) should work fine, for details see [list of tested phones and watches](https://docs.google.com/spreadsheets/d/1gZAsN6f0gv6tkgy9EBsYl0BQNhna0RDqA9QGycAqCQc/edit) for AndroidAPS (OS must be Android Wear) - -## Konfiguracja Nightscout - -Szczegóły znaidują się pod [Ustawienia Nightscout](../Installing-AndroidAPS/Nightscout.md) - -## Ustawienia komputera - -Aby móc skompilować AAPS z dostępnego publiczne kodu żródłowego potrzebujesz na swoim komputerze lub notebooku aplikacji Android Studio (jest ona dosępna dla tych systemów operacyjnych: Windows, Mac, Linux). Szczegółową instrukcje można znaleźć w [jak stworzyć APK](../Installing-AndroidAPS/Building-APK.md). - -Prosimy o cierpliwość podczas instalacji Android Studio, aplikacja ta pobiera wiele dodatkowych komponentów, po zainstalowaniu na komputerze. - -## Konfiguracja telefonu - -![Telefon](../images/SampleSetupSmartphone.png) - -### Sprawdź wersje oprogramowania na telefonie - -* Menu > Settings > Phone info > Software info: At least "Android-Version 8.0" (successfully tested up to Android version 8.0.0 Oreo - Samsung Experience Version 9.0) -* Aby przeprowadzić update oprogramowania: Ustawienia -> Informacje o telefonie -> Aktualizacja systemu - -### Zezwól na instalację aplikacji z nieznanych źródeł - -Menu > Ustawienia > zabezpieczenia urządzenia > Nieznane żródła > suwak po prawej stronie (= aktywny) - -Ze względów bezpieczeństwa to ustawienie powinna być ustawione ponownie na nieaktywne po zakończeniu instalacji wszystkich aplikacji tu opisanych. - -### Włącz Bluetooth - -1. Menu > Ustawienia > Połączenia > Bluetooth > suwak po prawej stronie (= aktywny) -2. Menu > Ustawienia > Połączenia > Lokalizacja > suwak po prawej stronie (= aktywny) - -Usługa lokalizacyjne ("GPS") musi być aktywna aby Bluetooth działał poprawnie. - -### Instalacja aplikacji Dexcom (w wersji zmodyfikowanej) - -![Aplikacja Dexcom patched](../images/SampleSetupDexApp.png) - -Oryginalna aplikacja Dexcom ze sklepu Google Play nie będzie działać, ponieważ nie rozgłasza wartości BG do innych aplikacji. W związku z tym wymagana jest wersja aplikacji nieco zmodyfikowana. Tylko ta zmodyfikowana wersja może się komunikować z AAPS. Dodatkowo ta wersja aplikacji może być używana z telefonami z Androidem które nie znaidują się na [liście zgodności Dexcom](https://www.dexcom.com/dexcom-international-compatibility). - -To do this perform the following steps on your smartphone: - -1. Jeśli oryginalny aplikacji Dexcom jest już zainstalowana: - * Zastopuj sensor - * Uninstall app via Menu > Settings > Apps > Dexcom G6 Mobile > Uninstall -2. Download and install the [BYODA Dexcom ap](../Hardware/DexcomG6.md#if-using-g6-with-build-your-own-dexcom-app) -3. Start modified Dexcom G6 app, activate/calibrate the sensor according to the given instructions and wait until the warm-up phase is finished. -4. Once the modified Dexcom app shows actual glucose value, setup the warnings (hamburger menu on top left side of the screen) as follows: - * Urgent low `55mg/dl` / `3.1mmol/l` (cannot be disabled) - * Low `OFF` - * High `OFF` - * Rise rate `OFF` - * Fall rate `OFF` - * Signal loss `OFF` - -## Instalacja AndroidAPS - -1. Follow the instructions to [build the APK](../Installing-AndroidAPS/Building-APK.md#generate-signed-apk) -2. [Transfer](../Installing-AndroidAPS/Building-APK.md#transfer-apk-to-smartphone) the generated APK to your phone -3. [Skonfigurować AndroidAPS](../Configuration/Config-Builder.md) zgodie z własnymi potrzebami używając Asystenta ustawień lub ręcznie -4. W tej przykładowej konfiguracji używamy (m.in.) - -* BG source: `Dexcom G6 App (patched)` -- click cock-wheel and activate `Upload BG data to NS` and `Send BG data to xDrip+` (see [BG source](../Configuration/BG-Source.md)) - -![G5 Settings](../images/SampleSetupG5Settings.png) - -* NS Client activated (see [Nightscout setup](../Installing-AndroidAPS/Nightscout.md)) - -## Instalacja xDrip + - -xDrip+ is another mature open source app that offers countless possibilities. In this setup, contrary to what the developers first wrote the app for, xDrip+ is not used to collect glucose data from the Dexcom G6, but only to output alarms and to display the current glucose value including the curve on the Android home screen in the widget. With xDrip+ the alarms can be set much more individually than with the Dexcom software, AAPS or Nightscout (no limitation in the selection of sounds, different alarms depending on day/night time etc.). - -1. Korzystając ze swojego telefonu pobierz najnowszą wersję APK xDrip + - nie używaj wersji z Google Play Store! -2. Zainstaluj xDrip + wybierając pobrany plik APK. -3. Uruchom xDrip + i dokonaj następujących ustawień (wejdz do menu w lewym górnym rogu) - * Ustawienia > Alarmy i Alerty > Glukozy poziomu listy alertów > Stwórz alarm (niski i wysoki poziom) zgodnie z własnymi potrzebami. - * Obecne alarmy mogą zostać zmienione przez naciśnięcie i przytrzymanie ustawionego alarmu. - * Ustawienia > Alarmy i Alerty > Alarmy kalibracji: wyłączone (przypomnienie o kalibracji ralizowane jest z wykorzystaniem aplikacji Dexcom) - * Ustawienia > Sprzętowe żródła danych > 640G / EverSense - * Ustawienia > Inter-app settings > Accept Calibrations > `ON` - * Menu > Start sensor (is only "pro forma" and has nothing to do with the running G6 sensor. ,jes ont wymagany gydż w innym przypadku regularnie będzie wyświetlany informacja o błędzie). - -For more information about xDrip+, see here [BG source page](../Configuration/BG-Source.md). - -### Przykład ustawienia alarmu - -The "Urgent low alarm" (below 55 mg/dl resp. 3,1 mmol) is a standard alarm from the modified Dexcom app that cannot be disabled. - -![xDrip alarms](../images/SampleSetupxDripWarning.png) - -Tip for meetings / church visits / cinema etc..: - -If "Do not disturb" mode is activated in the Samsung Galaxy S7 (Menu > Settings > Sounds and vibration > Do not disturb: slider to right side (= active)), the phone only vibrates during urgent low alarm and does not issue an acoustic warning. For the other alarms set up via xDrip+ you can select whether the silent mode should be ignored (acoustic sound played) or not. - -## Wyłącz opcję oszczędzania energii - -On your Samsung Galaxy S7 go to Menu > Settings > Device Maintenance > Battery > Unmonitored Apps > + Add apps: Select the apps AndroidAPS, Dexcom G6 Mobile, xDrip+ and Android Wear (if smartwatch is used) one after the other - -## Opcjonalnie: Sony Smartwatch 3 (SWR50) - -With an Android Wear smartwatch life with diabetes can be made even more inconspicuous. The watch can be used to display the current glucose level, the status of the loop etc. on the wrist. Zegarek może nawet służyć do sterowania AndroidAPS (tj. podawanie w sposób dyskretny bolusa na posiłek). To do this, double tap the CGM value of the AAPSv2 watchface. The SWR50 usually runs for a full day until the battery needs to be recharged (same charger as the Samsung Galaxy S7: microUSB). - -![Smartwatch](../images/SampleSetupSmartwatch.png) - -Details about the information displayed on the watchface can be found [here](../Configuration/Watchfaces.md). - -* Zainstaluj aplikację "Android Wear" na smartfonie za pośrednictwem sklepu Google Play i podłącz smartwatch zgodnie z instrukcjami. -* W AAPS wybierz menu hamburgera (lewy górny róg)> Konfiguracja> Ogólne (u dołu listy)> Oprogramowanie Wear> aktywuj po lewej stronie, kliknij koło zębate> Ustawienia Wear ` Sterowanie z zegarka` -* Na zegarku smartwatch: naciśnij i przytrzymaj ekran, aby zmienić watchface i wybierz `AAPSv2` -* W razie potrzeby ponownie uruchom oba urządzenia. - -## Ustawienia pompy - -see [Dana RS pump](../Configuration/DanaRS-Insulin-Pump.md) \ No newline at end of file diff --git a/docs/CROWDIN/pl/Getting-Started/WhatisAndroidAPS.md b/docs/CROWDIN/pl/Getting-Started/WhatisAndroidAPS.md deleted file mode 100644 index 619ad5d1169e..000000000000 --- a/docs/CROWDIN/pl/Getting-Started/WhatisAndroidAPS.md +++ /dev/null @@ -1,39 +0,0 @@ -# What is a closed loop system with AAPS? - -AAPS is an app that acts as an artificial pancreas system (APS) on an Android smartphone. What is an artificial pancreas system? It is a software program that aims to do what a living pancreas does: keep blood sugar levels within healthy limits automatically. - -An APS can't do the job as well as a biological pancreas does, but it can make type 1 diabetes easier to manage using devices that are commercially available and software that is simple and safe. Those devices include a continuous glucose monitor (CGM) to tell AAPS about your blood sugar levels and an insulin pump which AAPS controls to deliver appropriate doses of insulin. The app communicates with those devices via bluetooth. It makes its dosing calculations using an algorithm, or set of rules, developed for another artificial pancreas system, called OpenAPS, which has thousands of users and has accumulated millions of hours of use. - -A note of caution: AAPS is not regulated by any medical authority in any country. Using AAPS is essentially carrying out a medical experiment on yourself. Setting up the system requires determination and technical knowledge. If you don't have the technical know-how at the beginning, you will by the end. All the information you need can be found in these documents, elsewhere online, or from others who have already done it -- you can ask them in Facebook groups or other forums. Many people have successfully built AAPS and are now using it entirely safely, but it is essential that every user: - -- Builds the system themselves so that they thoroughly understand how it works -- Adjusts its individual dosage algorithm with his or her diabetes team to work nearly perfect -- Maintains and monitors the system to ensure it is working properly - -```{note} -**Disclaimer and Warning** - -- All information, thought, and code described here is intended for informational and educational purposes only. Nightscout obecnie nie podejmuje prób zachowania zgodności z zasadami ochrony prywatności HIPAA. Use Nightscout and AAPS at your own risk, and do not use the information or code to make medical decisions. -- Use of code from github.com is without warranty or formal support of any kind. Proszę zapoznać się LICENCJA w repozytorium aby poznać szczegóły. -- All product and company names, trademarks, servicemarks, registered trademarks, and registered servicemarks are the property of their respective holders. Ich wykorzystanie służy celom informacyjnym i nie oznacza żadnego powiązania z nimi ani poparcia. - -Please note - this project has no association with and is not endorsed by: [SOOIL](http://www.sooil.com/eng/), [Dexcom](https://www.dexcom.com/), [Accu-Chek, Roche Diabetes Care](https://www.accu-chek.com/), [Insulet](https://www.insulet.com/) or [Medtronic](https://www.medtronic.com/). -``` - -If you're ready for the challenge, please read on. - -## Primary goals behind AAPS - -- An app with safety built in. To read about the safety features of the algorithms, known as oref0 and oref1, click here () -- An all-in-one app for managing type 1 diabetes with an artificial pancreas and Nightscout -- An app to which users can easily add or remove modules as needed -- An app with different versions for specific locations and languages. -- An app which can be used in open- and closed-loop mode -- An app that is totally transparent: users can input parameters, see results, and make the final decision -- An app which is independent of particular pump drivers and contains a "virtual pump" so users can safely experiment before using it on themselves -- An app closely integrated with Nightscout -- An app in which the user is in control of safety constraints - -## How to start - -Of course, all of this content here is very important, but can be in the beginning quite confusing. A good orientation is given by the [Module Overview](../Module/module.md) and the [Objectives](../Usage/Objectives.html). diff --git a/docs/CROWDIN/pl/Hardware/DexcomG4.md b/docs/CROWDIN/pl/Hardware/DexcomG4.md deleted file mode 100644 index 3ac2b2b96f4b..000000000000 --- a/docs/CROWDIN/pl/Hardware/DexcomG4.md +++ /dev/null @@ -1,6 +0,0 @@ -# Dexcom G4 - -## If using G4 with OTG cable ('traditional' Nightscout) -- If not already set up then download Nightscout Uploader app from the Play Store and follow instructions on [Nightscout](https://nightscout.github.io/). -- In AAPS Preferences enter your Nightscout website and API secret. -- Select NSClient in ConfigBuilder (setting in AAPS). diff --git a/docs/CROWDIN/pl/Hardware/Smartwatch.md b/docs/CROWDIN/pl/Hardware/Smartwatch.md deleted file mode 100644 index 3968a2f122f0..000000000000 --- a/docs/CROWDIN/pl/Hardware/Smartwatch.md +++ /dev/null @@ -1,10 +0,0 @@ -# Inteligentne zegarki - -Smartwache są opcjonalne, ale bardzo przydatne dla niektórych użytkowników. More details are here: - -- [List of tested phones and smartwatches](../Getting-Started/Phones.md) -- [Watchfaces Wear OS](../Configuration/Watchfaces.md) -- [Troubleshooting Sony Smartwatch SW 3](../Usage/SonySW3.md) - -## Instructions for Building the AAPS Wear APK for Wear OS -https://androidaps.readthedocs.io/en/latest/remote-control.html#building-the-aaps-wear-apk diff --git a/docs/CROWDIN/pl/Installing-AndroidAPS/Building-APK.md b/docs/CROWDIN/pl/Installing-AndroidAPS/Building-APK.md deleted file mode 100644 index b045f534b27f..000000000000 --- a/docs/CROWDIN/pl/Installing-AndroidAPS/Building-APK.md +++ /dev/null @@ -1,369 +0,0 @@ -# Building the APK - -## Build yourself instead of download - -**AAPS is not available as download due to regulation for medical devices. It is legal to build the app for your own use, but you must not give a copy to others! See [FAQ page](../Getting-Started/FAQ.md) for details.** - -## Important notes - -* Please use **[Android Studio Giraffe" (2022.3.1)](https://developer.android.com/studio/)** or newer to build the apk. -* [Windows 32-bit systems](troubleshooting_androidstudio-unable-to-start-daemon-process) are not supported by Android Studio - -(Building-APK-recommended-specification-of-computer-for-building-apk-file)= - -## Recommended specification of computer for building apk file - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
OS (Only 64 bit)Windows 8 or higherMac OS 10.14 or higherAny Linux supports Gnome, KDE, or Unity DE;  GNU C Library 2.31 or later

CPU (Only 64 bit)

x86_64 CPU architecture; 2nd generation Intel Core or newer, or AMD CPU with support for a
Windows Hypervisor		ARM-based chips, or 2nd generation Intel Core or newer with support for
Hypervisor.Framework		x86_64 CPU architecture; 2nd generation Intel Core or newer, or AMD processor with support for AMD Virtualization (AMD-V) and SSSE3

RAM

8GB or more

Disk

At least 30GB free space. SSD is recommended.

Resolution

1280 x 800 Minimum

Internet

Broadband

- -Please keep in mind that both **64 bit CPU and 64 bit OS are mandatory condition.** If your system DOES NOT meet this condition, you have to change affected hardware or software or the whole system. **It is strongly recommended to use SSD (Solid State Disk) instead of HDD (Hard Disk Drive) because it will take less time when you are building the APS installation apk file.** Recommended is just recommended and it is not a mandatory. However, you may still use a HDD when you are building apk file but note that the building process can take a long time to complete, although once started, you can leave it running unattended. - -* * * - -### This article is divided into two parts. - -* In the overview part there is an explanation on what steps are necessary to build the APK file. -* In the step by step walkthrough part you will find the screenshots of a concrete installation. Because the versions of Android Studio - the software development environment which we will use to build the APK - will change very quickly this will be not identical to your installation but it should give you a good starting point. Android Studio also runs on Windows, Mac OS X and Linux and there might be small differences in some aspects between each platform. If you find that something important is wrong or missing, please inform the facebook group "AAPS users" or in the Discord chat [Android APS](https://discord.gg/4fQUWHZ4Mw) so that we can have a look at this. - -## Overview - -In general, the steps necessary to build the APK file: - -1. [Install git](../Installing-AndroidAPS/git-install.md) -2. [Install Android Studio](Building-APK-install-android-studio) -3. [Set git path in Android Studio preferences](Building-APK-set-git-path-in-preferences) -4. [Download AAPS code](Building-APK-download-AAPS-code) -5. [Download Android SDK](Building-APK-download-android-sdk) -6. [Build the app](Building-APK-generate-signed-apk) (generate signed apk) -7. [Transfer apk file to your phone](Building-APK-transfer-apk-to-smartphone) -8. [Identify receiver if using xDrip+](xdrip-identify-receiver) - -## Step by step walkthrough - -Detailed description of the steps necessary to build the APK file. - -## Install git (if you don't have it) - -Follow the manual on the [git installation page](../Installing-AndroidAPS/git-install.md). - -(Building-APK-install-android-studio)= - -## Install Android Studio - -The following screenshots have been taken from Android Studio Version Arctic Fox | 2020.3.1. Screens can change in future versions of Android Studio. But you should be able to find your way through. [Help from the community](../Where-To-Go-For-Help/Connect-with-other-users.md) is provided. - -One of the most important things when installing Android Studio: **Be patient!** During installation and setup Android Studio is downloading a lot of stuff which will take its time. - -Download [Android Studio from here](https://developer.android.com/studio/install.html) and install it on your computer. - -On first start you will find the setup wizard: - -Select "Do not import settings" as you have not used it before. - -![Do not import settings](../images/studioSetup/01_ImportSettings.png) - -Decide whether you want to share data with Google or not. - -![Share data with Google](../images/studioSetup/02_DataSharing.png) - -On the following screen click "Next". - -![Welcome screen](../images/studioSetup/03_Welcome.png) - -Select "Standard" installation and click "Next". - -![Standard installation](../images/studioSetup/04_InstallType.png) - -Select the theme for the user interface you like. (In this manual we used "Light".) Then click "Next". - -> ***Note:*** This is just the color scheme. You can select whatever you like (i.e. "Darcula" for dark mode). This selection has no influence on building the APK but the following screenshots might look different. - -![UI color scheme](../images/studioSetup/05_UITheme.png) - -Click "Next" on the "Verify Settings" dialog. - -![Verify settings](../images/studioSetup/06_Overview.png) - -Click on all three license agreement parts and select "Agree". When you have agreed to all, the "Finish" button will be enabled and you can "Finish". - - ![Agree license agreements](../images/studioSetup/07_LicenseAgreement.png) - - -Wait while Android Studio downloads additional components and be patient. Once everything is downloaded button "Finish" turns blue. Click the button now. - -![Downloading components](../images/studioSetup/08_Downloading.png) - -(Building-APK-download-AAPS-code)= - -## Download AAPS code - -* On the Android Studio welcome screen select "Projects" (1) on the left and then "Get from VCS" (2). - - ![Android Studio wizard](../images/studioSetup/20_ProjectVCS.png) - - * If you already opened Android Studio and do not see the welcome screen anymore select File (1) > New (2) > Project from Version Control... (3) - - ![Check out project from version control within Android Studio](../images/AndroidStudio_FileNew.PNG) - - * We will now tell Android Studio were to get the code from: - - * Make sure you have selected "Repository URL" on the left (1). - - * Check if "Git" is selected as version control (2). - * Copy and paste the URL ```https://github.com/nightscout/AndroidAPS``` to the main AAPS repository into the URL textbox (3). - * Choose the directory where you want to save the cloned code (4). - - ![Clone Git](../images/studioSetup/21_CloneURL.png) - -* Click button "Clone" (5). - - ![Clone repository](../images/studioSetup/22_Cloning.png) - -* Do not click "Background" while repository is cloned! - -* After the repository is cloned successfully, Android Studio will open the cloned project. - -* You will be asked whether you want to trust the project. Click on "Trust project"! - - ![Trust project](../images/studioSetup/23_TrustProject.png) - -* In the status bar at the bottom you will see the information that Android Studio is running background tasks. - - ![Background tasks](../images/studioSetup/24_GradleSyncRunning.png) - -* Windows only: Grant access if your firewall is asking for permission. - - ![Firewall permission java](../images/AndroidStudio361_18.png) - -* Once the background tasks are finished you will probably see an error saying that errors occurred (1) or (2) or (3). - - ![SDK licence](../images/studioSetup/25_SyncFailed.png) - - Don't worry, this will be solved soon! - -(Building-APK-set-git-path-in-preferences)= - -## Set git path in preferences - -Make sure [git is installed](../Installing-AndroidAPS/git-install.md) on your computer and you have restarted your computer since installing. - -On the Android Studio welcome screen click "Customize" (1) on the left and then select the link "All settings..." (2): - -![Android Studio settings from welcome screen](../images/studioSetup/10_WizardSettings.png) - -### Windows - -* As windows user, make sure you have restarted your computer after [installing Git](../Installing-AndroidAPS/git-install.md). - -* In the menu, go to File (1) > Settings (2) (or Android Studio > Preferences on Mac). - - ![Open settings](../images/studioSetup/30_Settings.png) - -* Double-click "Version Control" (1) to open the sub-menu. - -* Click Git (2). -* Make sure update method "Merge" (3) is selected. -* Check if Android Studio can locate path to git.exe automatically by clicking the button "Test" (4). - - ![Android Studio settings](../images/studioSetup/11_GitPath.png) - -* If automatic setting is successful git version will be displayed next to the path. - - ![Git version displayed](../images/studioSetup/12_GitVersion.png) - -* Eventually git.exe cannot be found automatically or the Test will result in an error (1): - - ![Git not found](../images/studioSetup/13_GitVersionError.png) - - In this case click on the folder icon (2). - -* Use [search function](https://www.tenforums.com/tutorials/94452-search-file-explorer-windows-10-a.html) in windows explorer to find "git.exe" if you are unsure where git has been installed. You are looking for a file named "git.exe", located in **\bin** folder. - -* Select path to git.exe and make sure you selected the one in ** \bin\ ** folder (3) and click "OK" (4). - - ![Select git manually](../images/studioSetup/14_GitManualSelection.png) - -* Check your selected git path again with the "Test" button as described above. - -* When the git version is displayed next to the path (see screenshot above), close settings window by clicking "OK" button (5). - -### Mac - -* Any git version should work. For example . -* Use homebrew to install git: ```$ brew install git```. -* For details on installing git see the [official git documentation](https://git-scm.com/book/en/v2/Getting-Started-Installing-Git). -* If you install git via homebrew there is no need to change any preferences. Just in case: They can be found here: Android Studio - Preferences. - -(Building-APK-download-android-sdk)= - -## Download Android SDK - -* In the menu, go to File (1) > Settings (2) (or Android Studio > Preferences on Mac). - - ![Open settings](../images/studioSetup/30_Settings.png) - -* Double-click on Languages & Frameworks to open its submenu (1). - -* Select Android SDK (2). -* Tick the box left of "Android 9.0 (Pie)" (3) (API Level 28). - - ![SDK settings](../images/studioSetup/31_AndroidSDK.png) - -* Confirm changes by clicking OK. - - ![Confirm SDK changes](../images/studioSetup/32_ConfirmSDK.png) - -* Wait until the SDK download and installation is finished. - - ![Wait during SDK installation](../images/studioSetup/34_DownloadSDK.png) - -* When SDK installation is completed the "Finish" button will turn blue. Click this button. - - ![Finish SDK installation](../images/studioSetup/35_DownloadSDKfinished.png) - -* Android Studio might recommend to update the gradle system. **Never update gradle!** This will lead to difficulties! - -* If you see an information on the lower right side of your Android Studio window that Android Gradle Plugin is ready to update click on the text "upgrade" (1). - - ![No gradle update](../images/studioSetup/36_GradleUpdateRequest.png) - -* In the dialog box the select "Don't remind me again for this project" (2). - - ![No gradle update](../images/studioSetup/37_GradleUpdateDeny.png) - -* Restart Android Studio before you continue. - -(Building-APK-generate-signed-apk)= - -## Generate signed APK - -Signing means that you indicate your app to be your own creation but in a digital way as a kind of digital fingerprint within the app itself. That is necessary because Android has a rule that it only accepts signed code to run for security reasons. For more information on this topic, follow [this link](https://developer.android.com/studio/publish/app-signing.html#generate-key). - -* After Android Studio is started, wait until all background tasks are finished. - - ![Wait for background tasks](../images/studioSetup/40_BackgroundTasks.png) - - * ***Warning:*** If errors occur, do not continue with the following steps. \ Consult the [troubleshooting section](../Installing-AndroidAPS/troubleshooting_androidstudio) for known problems! - - ![Gradle Sync Error](../images/studioSetup/41_GradleSyncError.png) - -* Click "Build" (1) in the menu bar and select "Generate Signed Bundle / APK..." (2). - - ![Build apk](../images/studioSetup/42_MenuBuild.png) - -* Select "APK" (1) instead of "Android App Bundle" and click "Next" (2). - - ![APK instead of bundle](../images/studioSetup/43_Apk.png) - -* Make sure that module is set to "AndroidAPS.app" (1). - -* Click "Create new..." (2) to start creating your key store. - - ***Note:*** A key store in this case is nothing more than a file in which the information for signing is stored. It is encrypted and the information is secured with passwords. - - ![Create key store](../images/studioSetup/44_KeystoreNew.png) - -* Click the folder symbol to select a path on your computer for your key store. - - ![Create key store](../images/studioSetup/45_KeystoreDialog.png) - -* Select the path where your key store shall be saved (1). - - ![Create key store](../images/studioSetup/46_KeystorePath.png) - - ***Warning: Do not save in same folder as project. You must use a different directory!*** A good location would be your home folder. - -* Type a file name for your key store (2) and confirm with "OK" (3). - -* Enter (2) and confirm (3) the password for your key store. ![Select key store path](../images/studioSetup/47_KeystoreDialog.png) - - ***Note:*** Passwords for key store and key do not have to be very sophisticated. Make sure to remember those or make a note in a safe place. In case you will not remember your passwords in the future, see [troubleshooting for lost key store](troubleshooting_androidstudio-lost-keystore). - -* Enter an alias (4) for your key. Choose whatever you like. - -* Enter (5) and confirm (6) the password for your key - -* Validity (7) is 25 years by default. You do not have to change the default value. - -* First and last name must be entered (8). All other information is optional. - -* Click "OK" (9) when you are done. - -* Make sure the box to remember passwords is checked (1). So you don't have to enter them again next time you build the apk (i.e. when updating to a new AAPS version). - -* Click "Next" (2). - - ![Remember passwords](../images/studioSetup/48_KeystoreSave.png) - -* Select build variant "fullRelease" (1) and press "Finish". - - ![Select build variant](../images/studioSetup/49_BuildVariant.png) - -* Android Studio will show "Gradle Build running" at the bottom. This takes some time, depending on your computer and internet connection. **Be patient!** - - ![Gradle Running](../images/studioSetup/50_GradleRunning.png) - -* Android Studio will display the information "Generate Signed APK" after build is finished. - - ![Build finished](../images/studioSetup/51_BuildFinished.png) - -* In case build was not successful refer to the [troubleshooting section](../Installing-AndroidAPS/troubleshooting_androidstudio). - -* Click on the notification to expand it. - -* Click on the link "locate". - - ![Locate build](../images/studioSetup/52_BuildLocate.png) - - * If the notification is gone, you can always open the "Event log" and select the same link there. ![Build successfully - event log](../images/studioSetup/53_EventLog.png) - -* Your file manager/explorer will open. Navigate to the directory "full" (1) > "release" (2). - - ![File location apk](../images/studioSetup/54_APKlocation.png) - -* "app-full-release.apk" (3) is the file you are looking for! - -(Building-APK-transfer-apk-to-smartphone)= - -## Transfer APK to smartphone - -Easiest way to transfer app-full-release.apk to your phone is via [USB cable or Google Drive](https://support.google.com/android/answer/9064445?hl=en). Please note that transfer by mail might cause difficulties and is not the preferred way. - -On your phone you have to allow installation from unknown sources. Manuals how to do this can be found on the internet (i.e. [here](https://www.expressvpn.com/de/support/vpn-setup/enable-apk-installs-android/) or [here](https://www.androidcentral.com/unknown-sources)). - -## Rozwiązywanie problemów - -See separate page [troubleshooting Android Studio](../Installing-AndroidAPS/troubleshooting_androidstudio). \ No newline at end of file diff --git a/docs/CROWDIN/pl/Resources/index.md b/docs/CROWDIN/pl/Resources/index.md deleted file mode 100644 index 9b42c1dc6e7a..000000000000 --- a/docs/CROWDIN/pl/Resources/index.md +++ /dev/null @@ -1,8 +0,0 @@ -# Zasoby - -```{toctree} -:glob: true -:maxdepth: 4 - -clinician-guide-to-AndroidAPS -``` diff --git a/docs/CROWDIN/pl/Sandbox/sandbox2.md b/docs/CROWDIN/pl/Sandbox/sandbox2.md deleted file mode 100644 index 33c547956c89..000000000000 --- a/docs/CROWDIN/pl/Sandbox/sandbox2.md +++ /dev/null @@ -1,43 +0,0 @@ -# internal sandbox file 2 for testing - -```{admonition} no need to translate this -:class: note - -No need to translate this. -``` - -This is an internal sandbox file for the documentation team to test - -1. markdown syntax and - -1. background process for - 1. CROWDIN translation and - 2. Read The Docs deployment. - -You can dirctly jump from here to the first label in the sandbox1.md file - ["Jump"](sandbox1-this-is-a-test). - -You can dirctly jump from here to the second label in this file - ["Jump"](sandbox1-this-is-another-test). - -Here you can jump to the first sandbox file - ["Jump"](./sandbox1.md). - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -(sandbox2-this-is-a-test)= -## This is a test - -This is a test if labels must be unique. - -### This is spare information from the docs - -cut from index: - -There are "limits" set in place when you are first beginning your AAPS journey. These safety limits have been developed over many years by observations of the inadvertent mistakes that new users are most likely to make when first learning to set up, build, and then successfully loop with AAPS - as most often those mistakes occur simply because the user was so excited to get started using the system that they may have forgotten to sit down and dedicate the time needed to understand the information within this documentation thoroughly. - - -### spare info from the overview to put into "preparing" - -Since the requirements are very different from anything you might have set up in the past, we recommend that you really follow the instructions, step-by-step the first few times you build the app, so that you have a stronger sense of how the app building process is supposed to behave when all directions are followed exactly. Please remember to take your time. Later this will go very quickly when you build the app again for a new version. That way you will have a greater chance of noticing when something doesn't going as planned before too many steps are out of line. It is important to save the your keystore file (.jks file used to sign your app) in a safe place, so that you can always use that exact same keystore file and password each and every time you are asked to create a new updated version of AAPS, as this file is what makes sure that each new version of the app "remembers" all the information that you have provided to it in previous versions of the app and thus ensure that the updates will go as smoothly as possible. On average, you can assume that there will be one new version and 2-3 required updates per year. This number is based on experience and may change in the future. But we do want to at least give you a general guideline on what to expect. When you are more experienced at building updated AAPS app versions all the steps that are required in building an updated app will only take 15-30 minutes, on average. However, in the beginning there can be a rather steep learning curve as these steps are not always considered intuitive by new users! So do not get frustrated if you find that it takes half a day or a whole day with some help from the community before you are finally finished with the update process. If you find that you are getting very frustrated just take a short break, and oftentimes; after a stroll around the block or two...you'll find that you are better able to approach the problem again. diff --git a/docs/CROWDIN/pl/Usage/Objectives.md b/docs/CROWDIN/pl/Usage/Objectives.md deleted file mode 100644 index d8e6be3a7917..000000000000 --- a/docs/CROWDIN/pl/Usage/Objectives.md +++ /dev/null @@ -1,184 +0,0 @@ -# Cele (samouczek) - -AAPS has a series of Objectives that need to be completed to walk you through the features and settings of safe looping. Gwarantują, że wszystko poprawnie skonfigurowałeś w sekcjach powyżej i że wiesz, co robi Twój system i dlaczego możesz mu zaufać. - -If you are **upgrading phones** then you can [export your settings](../Usage/ExportImportSettings.md) to keep your progress through the objectives. Not only will your progress through the objectives be saved, but also your safety settings such as max bolus etc. If you do not export and import your settings then you will need to start the objectives from the beginning again. It is a good idea to [backup your settings](../Usage/ExportImportSettings.html) frequently just in case. - -If you want to go back in objectives see [explanation below](Objectives-go-back-in-objectives). - -## Cel 1: Ustawienie wizualizacji i monitorowania, analizowanie profilu podstawowego i parametrów - -- Select the right blood glucose source for your setup. See [BG Source](../Configuration/BG-Source.md) for more information. -- Select the right Pump in ConfigBuilder (select Virtual Pump if you are using a pump model with no AAPS driver for looping) to ensure your pump status can communicate with AAPS. -- If using DanaR pump then ensure you have followed [DanaR Insulin Pump](../Configuration/DanaR-Insulin-Pump.md) instructions to ensure the link between pump and AAPS. -- You need to establish a data repository/reporting platform to complete this objective. That can be accomplished with either Nightscout or Tidepool (or both). Follow instructions at the [Nightscout](../Installing-AndroidAPS/Nightscout.md) or [Tidepool](../Installing-AndroidAPS/Tidepool.md) page for instructions. -- Note that URL in NSClient must be **WITHOUT /api/v1/** at the end - see [NSClient settings in Preferences](Preferences-nsclient). - -*You may need to wait for the next blood glucose reading to arrive before AAPS will recognise it.* - -## Objective 2: Learn how to control AAPS - -- Perform several actions in AAPS as described in this objective. - -- Click on the orange text "Not completed yet" to access the to-dos. - -- Links will be provided to guide you in case you are not familiar with a specific action yet. - - ```{image} ../images/Objective2_V2_5.png - :alt: Screenshot objective 2 - ``` - -(Objectives-objective-3-prove-your-knowledge)= - -## Objective 3: Prove your knowledge - -Objective 3 is a multiple choice test based on questions designed to test your theoretical knowledge of **AAPS**. - -Some users find Objective 3 to be the most difficult objective to complete. Please do read the AAPS documents in conjunction with the questions. If you are genuinely stuck after researching the **AAPS** documents, please search or ask for help on the Facebook or Discord group. These groups can provide friendly hints or redirect you to the relevant part of the **AAPS** documents. - -To proceed with Objective 3, click on the orange text “Not completed yet” to access the relevant question. Please read each question and select your answer(s). - - - -Within each question, a hyperlink to the **AAPS** documents will guide you to the relevant section of the document which you should read in order to locate the correct answer. - - -[Obj3_Screenshot 2023-12-05 223422](https://github.com/openaps/AndroidAPSdocs/assets/137224335/77347516-e24e-459d-98ab-acbb49a3d4e8)![image](https://github.com/openaps/AndroidAPSdocs/assets/137224335/ca756b8e-efbc-4427-b281-ac953ce16718) - - - -For each question, there may be more than one answer that is correct! If an incorrect answer is selected, the question will be time locked for a certain amount of time (60 minutes) before you can go back and answer the question. - - -After updating to a new version of **AAPS**, new questions may be added to cover a prevalent issue picked up by **AAPS** or alternatively to test your knowledge of a new feature of **AAPS** as released. - - -When **AAPS** is installed for the first time, you will have to complete Objective 3 entirely in order to move onto Objective 4. Each objective is required to be completed in sequential order. New features will gradually be unlocked as progress is made through the objectives. - -__What happens if new questions are added later to Objective 3?__ From time to time, new features are added to **AAPS** which may require a new question to be added to Objective 3. As a result, any new question added to Objective 3 will be marked as “incomplete” because **AAPS** will require you to action this. As each Objective is independent, you will not lose the existing functionality of **AAPS** providing the other objectives remain completed. - - -## Objective 4: Starting on an open loop - -- Select Open Loop either from Preferences, or by pressing and holding the Loop button in top left of the home screen. -- Work through the [Preferences](../Configuration/Preferences.md) to set up for you. -- Manually enact at least 20 of the temporary basal rate suggestions over a period of 7 days; input them to your pump and confirm in AAPS that you have accepted them. Ensure this data shows in AAPS and Nightscout. -- Enable [temp targets](../Usage/temptarget.md) if necessary. Use hypo temp targets to prevent that the system will correct too strong because of a raising blood glucose after a hypo. - -### Reduce number of notifications - -- To reduce the Number of decisions to be made while in Open Loop set wide target range like 90 - 150 mg/dl or 5,0 - 8,5 mmol/l. - -- You might even want to wider upper limit (or disable Open Loop) at night. - -- In Preferences you can set a minimum percentage for suggestion of basal rate change. - - ```{image} ../images/OpenLoop_MinimalRequestChange2.png - :alt: Open Loop minimal request change - ``` - -- Also, you do not need to act every 5 minutes on all suggestions... - -## Objective 5: Understanding your open loop, including its temp basal recommendations - -- Start to understand the thinking behind the temp basal recommendations by looking at the [determine basal logic](https://openaps.readthedocs.io/en/latest/docs/While%20You%20Wait%20For%20Gear/Understand-determine-basal.html) and both the [forecast line in AAPS homescreen](Screenshots-prediction-lines)/Nightscout and the summary of outputs from the calculations in your OpenAPS tab. - -You will want to set your target higher than usual until you are confident in the calculations and settings. System allows - -- a low target to be a minimum of 4 mmol (72 mg/dl) or maximum of 10 mmol (180 mg/dl) -- a high target to be a minimum of 5 mmol (90 mg/dl) and maximum of 15 mmol (225 mg/dl) -- a temporary target as a single value can be anywhere in the range of 4 mmol to 15 mmol (72 mg/dl to 225 mg/dl) - -The target is the value that calculations are based on, and not the same as where you aim to keep your blood glucose values within. If your target is very wide (say, 3 or more mmol \[50 mg/dl or more\] wide), you will often find little AAPS action. This is because blood glucose is eventually predicted to be somewhere in that wide range and therefore not many fluctuating temporary basal rates are suggested. - -You may want to experiment with adjusting your targets to be a closer together range (say, 1 or less mmol \[20 mg/dl or less\] wide) and observe how the behavior of your system changes as a result. - -You can view a wider range (green lines) on the graph for the values you aim to keep your blood glucose within by entering different values in [Preferences](../Configuration/Preferences.md) > Range for Visualisation. - -```{image} ../images/sign_stop.png -:alt: Stop sign -``` - -### Stop here if you are open looping with a virtual pump - do not click Verify at the end of this objective. - -```{image} ../images/blank.png -:alt: blank -``` - -(Objectives-objective-6-starting-to-close-the-loop-with-low-glucose-suspend)= -## Objective 6: Starting to close the loop with Low Glucose Suspend - -```{image} ../images/sign_warning.png -:alt: Warning sign -``` - -### Closed loop will not correct high BG values in objective 6 as it is limited to low glucose suspend. High BG values have to be corrected manually by you! - -- Prerequisite: You need a good profile (basal, ISF, IC) already working in AAPS to start with Loop in Low Glucose Suspend mode. Otherwise you can run in a hypo which you have to manually correct. This will help you a lot to avoid having to treat a low glucose over a period of 5 days. **If you are still having frequent or severe low glucose episodes then consider refining your DIA, basal, ISF and carb ratios and do NOT start objective 6 at this time.** -- You don't have to change your settings now. During objective 6, the maxIOB setting is internally set to zero automatically. **This override will be reversed when moving to objective 7.** -- The system will override your maxIOB settings to zero, which means if blood glucose is dropping it can reduce basal for you. If blood glucose is rising then it will only increase basal if the basal IOB is negative from a previous Low Glucose Suspend. Otherwise basal rates will remain the same as your selected profile. **That means that you have to manually handle high values with insulin corrections.** -- If your basal IOB is negative (see screenshot below) a TBR > 100% can be issued also in objective 6. - -```{image} ../images/Objective6_negIOB.png -:alt: Example negative IOB -``` - -- Set your target range slightly higher than you usually aim for, just to be safe and have a bit more scurity buffer. -- Enable 'Low Glucose Suspend' mode either by by pressing and holding the Loop icon at the top right corner of the home screen and selecting the Loop - LGS mode icon. -- Watch how temporary basals are active by viewing the blue basal text on the homescreen or the blue basal render on the homescreen graph. -- You may temporarily experience spikes following treated hypos without the ability to increase basal on the rebound. - -(Objectives-objective-7-tuning-the-closed-loop-raising-max-iob-above-0-and-gradually-lowering-bg-targets)= -## Objective 7: Tuning the closed loop, raising maxIOB above 0 and gradually lowering BG targets - -- Select 'Closed Loop' either from [Preferences](../Configuration/Preferences.md) or by pressing and holding the Loop icon at the top right corner of the home screen, over a period of 1 day. - -- Raise your 'Maximum total IOB OpenAPS can’t go over' (in OpenAPS called 'max-iob') above 0. The default recommendation is "average mealbolus + 3x max daily basal" (for the SMB algorithm) or "3x max daily basal" (for the older AMA algorithm) but you should slowly work up to this until you know your settings work for you (max daily basal = the maximum hourly value in any time segment of the day). - - This recommendation should be seen as a starting point. If you set to the 3x and you are seeing moves that push you too hard and fast then lower that number. If you are very resistant, raise it very little at a time. - - ```{image} ../images/MaxDailyBasal2.png - :alt: max daily basal - ``` - -- Once confident on how much IOB suits your looping patterns, then reduce your targets to your desired level. - -(Objectives-objective-8-adjust-basals-and-ratios-if-needed-and-then-enable-autosens)= -## Objective 8: Adjust basals and ratios if needed, and then enable autosens - -- You can use [autotune](https://openaps.readthedocs.io/en/latest/docs/Customize-Iterate/autotune.html) as a one off to check your basals remain accurate or do a traditional basal test. -- Enable [autosens](../Usage/Open-APS-features.md) over a period of 7 days and watch the white line on the homescreen graph show how your sensitivity to insulin may be rising or falling as a result of exercise or hormones etc. and keep an eye in the OpenAPS report tab how AAPS is adjusting the basals and/or targets accordingly. - -*Don’t forget to record your looping in* [this form](https://bit.ly/nowlooping) *logging AAPS as your type of DIY loop software, if you have not already done so.* - -(Objectives-objective-9-enabling-additional-oref1-features-for-daytime-use-such-as-super-micro-bolus-smb)= -## Objective 9: Enabling additional oref1 features for daytime use, such as super micro bolus (SMB) - -- You must read the [SMB chapter in this wiki](Open-APS-features-super-micro-bolus-smb) and [chapter oref1 in openAPSdocs](https://openaps.readthedocs.io/en/latest/docs/Customize-Iterate/oref1.html) to understand how SMB works, especially what's the idea behind zero-temping. -- Then you ought to [rise maxIOB](Open-APS-features-maximum-total-iob-openaps-cant-go-over-openaps-max-iob) to get SMBs working fine. maxIOB now includes all IOB, not just added basal. That is, if given a bolus of 8 U for a meal and maxIOB is 7 U, no SMBs will be delivered until IOB drops below 7 U. A good start is maxIOB = average mealbolus + 3x max daily basal (max daily basal = the maximum hourly value in any time segment of the day - see [objective 7](Objectives-objective-7-tuning-the-closed-loop-raising-max-iob-above-0-and-gradually-lowering-bg-targets) for an illustration) -- min_5m_carbimpact default in absorption settings has changed from 3 to 8 going from AMA to SMB. If you are upgrading from AMA to SMB, you have to change it manually. - -(Objectives-objective-10-automation)= -## Objective 10: Automation - -- You have to start objective 10 to be able to use [Automation](../Usage/Automation.md). -- Make sure you have completed all objectives including exam [Objectives-objective-3-prove-your-knowledge](Objectives#objective-3-prove-your-knowledge). -- Completing previous objectives will not effect other objectives you have already finished. You will keep all finished objectives! - -(Objectives-objective-11-DynamicISF)= -## Objective 11: Additional Features such as DynamicISF - -- You have to start objective 11 to be able to use [DynamicISF](../Usage/Open-APS-features.md) - -(Objectives-go-back-in-objectives)= -## Go back in objectives - -If you want to go back in objectives for whatever reason you can do so by clicking at "clear finished". - -```{image} ../images/Objective_ClearFinished.png -:alt: Go back in objectives -``` - -## Objectives in Android APS before version 3.0 - -One objective was removed when Android APS 3.0 was released. Users of Android APS version 2.8.2.1 who are on older Android software (i.e. earlier than version 9) will be using an older set of objectives which can be found [here](../Usage/Objectives_old.md). diff --git a/docs/CROWDIN/pl/Usage/Objectives_old.md b/docs/CROWDIN/pl/Usage/Objectives_old.md deleted file mode 100644 index 326d6be24b9a..000000000000 --- a/docs/CROWDIN/pl/Usage/Objectives_old.md +++ /dev/null @@ -1,152 +0,0 @@ -# Objectives as of Android APS 2.8.2.1 - -This is not the latest version of the Android APS Objectives. This page details the Objectives that were in place prior to version 3.0. Anyone using an older version of Android (i.e. prior to Android 9) and Android APS version 2.8.2.1 should refer to this page. - -Please see [this page](../Usage/Objectives.md) for the current set of Objectives. - -AndroidAPS ma szereg zadań (celi), które należy wykonać. Cele służą temu aby przeprowadzić użytkownika przez funkcje i ustawienia systemu dla zapewnienia bezpiecznego używania pętli. Gwarantują, że wszystko poprawnie skonfigurowałeś w sekcjach powyżej i że wiesz, co robi Twój system i dlaczego możesz mu zaufać. - -If you are **upgrading phones** then you can [export your settings](../Usage/ExportImportSettings.md) to keep your progress through the objectives. Not only will your progress through the objectives be saved, but also your safety settings such as max bolus etc. If you do not export and import your settings then you will need to start the objectives from the beginning again. It is a good idea to [backup your settings](../Usage/ExportImportSettings.html) frequently just in case. - -If you want to go back in objectives see [explanation below](../Usage/Objectives.md#go-back-in-objectives). - -## Cel 1: Ustawienie wizualizacji i monitorowania, analizowanie profilu podstawowego i parametrów - -- Select the right blood glucose source for your setup. See [BG Source](../Configuration/BG-Source.md) for more information. -- Select the right Pump in ConfigBuilder (select Virtual Pump if you are using a pump model with no AndroidAPS driver for looping) to ensure your pump status can communicate with AndroidAPS. -- If using DanaR pump then ensure you have followed [DanaR Insulin Pump](../Configuration/DanaR-Insulin-Pump.md) instructions to ensure the link between pump and AndroidAPS. -- Follow instructions in [Nightscout](../Installing-AndroidAPS/Nightscout.md) page to ensure Nightscout can receive and display this data. -- Note that URL in NSClient must be **WITHOUT /api/v1/** at the end - see [NSClient settings in Preferences](../Configuration/Preferences.md#nsclient). - -*You may need to wait for the next blood glucose reading to arrive before AndroidAPS will recognise it.* - -## Objective 2: Learn how to control AndroidAPS - -- Perform several actions in AndroidAPS as described in this objective. - -- Click on the orange text "Not completed yet" to access the to-dos. - -- Links will be provided to guide you in case you are not familiar with a specific action yet. - - ![Screenshot objective 2](../images/Objective2_V2_5.png) - -## Objective 3: Prove your knowledge - -- Pass a multiple-choice exam testing your AndroidAPS knowledge. - -- Click on the orange text "Not completed yet" to access the page with the question and answering options. - - ![Screenshot objective 3](../images/Objective3_V2_5.png) - -- Links will be provided to guide you in case you are unsure about the correct answers yet. - -- The questions for objective 3 have been completely rewritten by native speakers as of AAPS 2.8. The new ones cover the same basic topics plus a few new ones. - -- These new questions will lead to some not answered questions even though you have successfully completed objective 3 in previous versions. - -- Unanswered questions will affect you only if you start a new objective. In other words: If you have already completed all objectives you can wait and answer the new questions later without loosing AAPS functions. - -## Objective 4: Starting on an open loop - -- Select Open Loop either from Preferences, or by pressing and holding the Loop button in top left of the home screen. -- Work through the [Preferences](../Configuration/Preferences.md) to set up for you. -- Manually enact at least 20 of the temporary basal rate suggestions over a period of 7 days; input them to your pump and confirm in AndroidAPS that you have accepted them. Ensure this data shows in AndroidAPS and Nightscout. -- Enable [temp targets](../Usage/temptarget.md) if necessary. Use hypo temp targets to prevent that the system will correct too strong because of a raising blood glucose after a hypo. - -### Reduce number of notifications - -- To reduce the Number of decisions to be made while in Open Loop set wide target range like 90 - 150 mg/dl or 5,0 - 8,5 mmol/l. - -- You might even want to wider upper limit (or disable Open Loop) at night. - -- In Preferences you can set a minimum percentage for suggestion of basal rate change. - - ![Open Loop minimal request change](../images/OpenLoop_MinimalRequestChange2.png) - -- Also, you do not need to act every 5 minutes on all suggestions... - -## Objective 5: Understanding your open loop, including its temp basal recommendations - -- Start to understand the thinking behind the temp basal recommendations by looking at the [determine basal logic](https://openaps.readthedocs.io/en/latest/docs/While%20You%20Wait%20For%20Gear/Understand-determine-basal.html) and both the [forecast line in AndroidAPS homescreen](../Getting-Started/Screenshots.md#prediction-lines)/Nightscout and the summary of outputs from the calculations in your OpenAPS tab. - -You will want to set your target higher than usual until you are confident in the calculations and settings. System allows - -- a low target to be a minimum of 4 mmol (72 mg/dl) or maximum of 10 mmol (180 mg/dl) -- a high target to be a minimum of 5 mmol (90 mg/dl) and maximum of 15 mmol (225 mg/dl) -- a temporary target as a single value can be anywhere in the range of 4 mmol to 15 mmol (72 mg/dl to 225 mg/dl) - -The target is the value that calculations are based on, and not the same as where you aim to keep your blood glucose values within. If your target is very wide (say, 3 or more mmol \[50 mg/dl or more\] wide), you will often find little AAPS action. This is because blood glucose is eventually predicted to be somewhere in that wide range and therefore not many fluctuating temporary basal rates are suggested. - -You may want to experiment with adjusting your targets to be a closer together range (say, 1 or less mmol \[20 mg/dl or less\] wide) and observe how the behavior of your system changes as a result. - -You can view a wider range (green lines) on the graph for the values you aim to keep your blood glucose within by entering different values in [Preferences](../Configuration/Preferences.md) > Range for Visualisation. - -![Stop sign](../images/sign_stop.png) - -### Stop here if you are open looping with a virtual pump - do not click Verify at the end of this objective. - -![blank](../images/blank.png) - -## Objective 6: Starting to close the loop with Low Glucose Suspend - -![Warning sign](../images/sign_warning.png) - -### Closed loop will not correct high bg values in objective 6 as it is limited to low glucose suspend. High bg values have to be corrected manually by you! - -- Select Closed Loop either from [Preferences](../Configuration/Preferences.md) or by pressing and holding the Open Loop button in the top left of the home screen. - -- Set your target range slightly higher than you usually aim for, just to be safe. - -- Watch how temporary basals are active by viewing the blue basal text on the homescreen or the blue basal render on the homescreen graph. - -- Ensure your settings have supported AndroidAPS to avoid having to treat a low glucose over a period of 5 days. If you are still having frequent or severe low glucose episodes then consider refining your DIA, basal, ISF and carb ratios. - -- You don't have to change your settings. During objective 6 maxIOB setting is internally set to zero automatically. This override will be reversed when moving to objective 7. - -- The system will override your maxIOB settings to zero, which means if blood glucose is dropping it can reduce basal for you, but if blood glucose is rising then it will only increase basal if the basal IOB is negative (from a previous Low Glucose Suspend), otherwise basal rates will remain the same as your selected profile. - - ![Example negative IOB](../images/Objective6_negIOB.png) - -- If your basal IOB is negative (see screenshot above) a TBR > 100% can be issued also in objective 6. - -- You may temporarily experience spikes following treated hypos without the ability to increase basal on the rebound. - -## Objective 7: Tuning the closed loop, raising max IOB above 0 and gradually lowering BG targets - -- Raise your 'Maximum total IOB OpenAPS can’t go over' (in OpenAPS called 'max-iob') above 0 over a period of 1 day, the default recommendation is "average mealbolus + 3x max daily basal"(for SMB algorithm) or "3x max daily basal" (for older AMA algorithm) but you should slowly work up to this until you know your settings work for you (max daily basal = the maximum hourly value in any time segment of the day). - - This recommendation should be seen as a starting point. If you set to the 3x and you are seeing moves that push you to hard and fast then lower that number. If you are very resistant raise it a very little at a time. - - ![max daily basal](../images/MaxDailyBasal2.png) - -- Once confident on how much IOB suits your looping patterns then reduce your targets to your desired level. - -## Objective 8: Adjust basals and ratios if needed, and then enable autosens - -- You can use [autotune](https://openaps.readthedocs.io/en/latest/docs/Customize-Iterate/autotune.html) as a one off to check your basals remain accurate or do a traditional basal test. -- Enable [autosens](../Usage/Open-APS-features.md) over a period of 7 days and watch the white line on the homescreen graph show how your sensitivity to insulin may be rising or falling as a result of exercise or hormones etc. and keep an eye in the OpenAPS report tab how AndroidAPS is adjusting the basals and/or targets accordingly. - -*Don’t forget to record your looping in* [this form](https://bit.ly/nowlooping) *logging AndroidAPS as your type of DIY loop software, if you have not already done so.* - -## Objective 9: Try additional features for daytime use and gain confidence in your closed loop system - -- Before AAPS version 2.7 meal assist (MA) was the basic algorithm for AAPS and completing objective 8 was necessary to activate [advanced meal assist (AMA)](../Usage/Open-APS-features.md#advanced-meal-assist-ama). -- As [advanced meal assist (AMA)](../Usage/Open-APS-features.md#advanced-meal-assist-ama) is the standard algorithm from AAPS version 2.7 onwards use the following 28 days to try features you haven't used yet and get more confident with you closed loop system. - -## Objective 10: Enabling additional oref1 features for daytime use, such as super micro bolus (SMB) - -- You must read the [SMB chapter in this wiki](../Usage/Open-APS-features.md#super-micro-bolus-smb) and [chapter oref1 in openAPSdocs](https://openaps.readthedocs.io/en/latest/docs/Customize-Iterate/oref1.html) to understand how SMB works, especially what's the idea behind zero-temping. -- Then you ought to [rise maxIOB](../Usage/Open-APS-features.md#maximum-total-iob-openaps-cant-go-over-openaps-max-iob) to get SMBs working fine. maxIOB now includes all IOB, not just added basal. That is, if given a bolus of 8 U for a meal and maxIOB is 7 U, no SMBs will be delivered until IOB drops below 7 U. A good start is maxIOB = average mealbolus + 3x max daily basal (max daily basal = the maximum hourly value in any time segment of the day - see [objective 7](../Usage/Objectives#objective-7-tuning-the-closed-loop-raising-max-iob-above-0-and-gradually-lowering-bg-targets) for an illustration) -- min_5m_carbimpact default in absorption settings has changed from 3 to 8 going from AMA to SMB. If you are upgrading from AMA to SMB, you have to change it manually. - -## Objective 11: Automation - -- You have to start objective 11 to be able to use [Automation](../Usage/Automation.md). -- Make sure you have completed all objectives including exam [../Usage/Objectives.md#objective-3-prove-your-knowledge](../Usage/Objectives#objective-3-prove-your-knowledge). -- Completing previous objectives will not effect other objectives you have already finished. You will keep all finished objectives! - -## Go back in objectives - -If you want to go back in objectives for whatever reason you can do so by clicking at "clear finished". - -![Go back in objectives](../images/Objective_ClearFinished.png) diff --git a/docs/CROWDIN/pl/Usage/Smoothing-Blood-Glucose-Data-in-xDrip.md b/docs/CROWDIN/pl/Usage/Smoothing-Blood-Glucose-Data-in-xDrip.md deleted file mode 100644 index 3c016e09dba8..000000000000 --- a/docs/CROWDIN/pl/Usage/Smoothing-Blood-Glucose-Data-in-xDrip.md +++ /dev/null @@ -1,33 +0,0 @@ -(Smoothing-Blood-Glucose-Data-in-xDrip-smoothing-blood-glucose-data)= - -# Wygładzanie danych dotyczących poziomu glukozy we krwi - -If BG data is jumpy/noisy, AAPS may dose insulin incorrectly resulting in high or low BG. For this reason it’s important to disable the loop until the problem is resolved. Depending on your CGM such issues may be due to the CGM’s configuration or sensor problems/site issues. You may need to replace your CGM sensor to resolve this. - -Some CGM systems have internal algorithms to detect the noise level in the readings and AAPS can use this information to avoid giving SMBs if the BG data is too unreliable. However, some CGMs do not transmit this data and for these BG sources 'Enable SMB always' and 'Enable SMB after carbs' are disabled for safety reasons. - -## Dexcom sensors - -### Build Your Own Dexcom App - -When using [BYODA](DexcomG6-if-using-g6-with-build-your-own-dexcom-app) your BG data is smooth and consistent. Furthermore you can take advantage of Dexcom back-smoothing. There are no restrictions in using SMBs, because the noise-level data is shared with AAPS. - -### xDrip+ with Dexcom G6 or Dexcom ONE - -Noise-level data and smooth BG readings are only shared with AAPS if you use xDrip+ [native mode](https://navid200.github.io/xDrip/docs/Native-Algorithm). Using native mode, there are no restrictions in using SMBs. - -### Dexcom G6 or Dexcom ONE with xDrip+ Companion Mode - -The noise-level data is not shared with AAPS using this method. Therefore 'Enable SMB always' and 'Enable SMB after carbs' are disabled. - -## Freestyle Libre sensors - -### xDrip+ with FreeStyle Libre - -None of the FreeStyle Libre systems (FSL1, FSL2, or FSL3) broadcast any information about the level of noise detected in the readings, and therefore 'Enable SMB always' and 'Enable SMB after carbs' are disabled for all setups using the FreeStyle Libre. - -In addition, many people have reported the FreeStyle Libre often produces noisy data. In xDrip+ there are a few options to help with this: - -**Smooth Sensor Noise.** In xDrip+ Settings > xDrip+ Display Settings ensure that Smooth Sensor Noise is turned on. This attempts to apply smoothing to noisy data. - -**Smooth Sensor Noise (Ultrasensitive).** If you are still seeing noisy data in xDrip+ you can apply more aggressive smoothing using the Smooth Sensor Noise (Ultrasensitive) setting. This will attempt to apply smoothing even on very low levels of detected noise. To do this, first enable [engineering mode](Enabling-Engineering-Mode-in-xDrip.md) in xDrip+. Then navigate to Settings > xDrip+ Display Settings and turn on Smooth Sensor Noise (Ultrasensitive). \ No newline at end of file diff --git a/docs/CROWDIN/pl/Usage/autotune_b.md b/docs/CROWDIN/pl/Usage/autotune_b.md deleted file mode 100644 index ae85c34d4638..000000000000 --- a/docs/CROWDIN/pl/Usage/autotune_b.md +++ /dev/null @@ -1,186 +0,0 @@ -# How to use Autotune plugin - -Documentation about Autotune algorythm can be found in [OpenAPS documentation](https://openaps.readthedocs.io/en/latest/docs/Customize-Iterate/autotune.html). - -Autotune plugin is an implementation of OpenAPS autotune algorythm within AAPS. - -**Currently Autotune Plugin is only available in dev branch with Engineering mode.** - -## Autotune user interface - -![Autotune default screen](../images/Autotune/Autotune_1b.png) - -- You can select in the Profile dropdown menu the input profile you want to tune (by default your current active profile is selected) - - Note: each time you select a new profile, previous results will be removed and Tune days parameter will be set to default value -- Then Tune days is to select the number of days used in calculation to tune your profile. The minimum value is 1 day and the maximum value 30 days. This number should not be too small to get correct iterative and smooth results (above 7 days for each calculation) - - Note: each time you change Tune days parameter, previous results will be removed -- Last Run il a link that recover your latest valid calculation. If you didn't launch Autotune on current day, or if previous results was removed with a modification of calculation parameter above, then you can recover parameters and results of the latest successfull run. -- Warning show you for example some information about selected profile (if you have several IC values or several ISF values) - - Note: Autotune calculation works with only a single IC and a single ISF value. There is currently no existing Autotune algorythm to tune a circadian IC or circadian ISF. If your input profile has several values, you can see in warning section the average value taken into account to tune your profile. -- Check Input Profile button open the Profile Viewer to allow you a quick verification of your profile (Units, DAI, IC, ISF, basal and target) - - Note: Autotune will only tune your IC (single value), ISF (single value) and basal (with circadian variation). Units, DAI and target will remain unchanged in output profile. - -- "Run Autotune" will launch Autotune calculation with selected profile and the number of Tune days - - Note: Autotune calculation can take a long time. Once launched, you can switch to another view (home, ...) and come back later in Autotune plugin to see results - -![Autotune Run start](../images/Autotune/Autotune_2b.png) - -- Then during the run you will see intermediate results below - - - Note: During run, settings are locked, so you cannot change anymore selected input profile or the number of day. You will have to wait the end of current calculation if you want to launch another run with other parameters. - - ![Autotune during run](../images/Autotune/Autotune_3b.png) - -- When Autotune calculation is finished, you will see the result (Tuned profile) and four buttons below. - -![Autotune Result](../images/Autotune/Autotune_4b.png) - -- It's important to always compare input profile (column "Profile"), output profile (column "Tuned") and the percentage of variation for each value (Column "%"). - -- For basal rates, you also have the number of "missing days". You have missing days when Autotune don't have enough data categorized as "Basal" to tune basal rate for this period (for example after each meal when you have carbs absorption). This number should be as low as possible especially when basal is important (for example during the night or at the end of the afternoon) - -- The "Compare profiles" button open the profile comparator view. Input profile is in blue, and output profile (named "Tuned") is in red. - - - Note: in the example below input profile has circadian variation for IC and ISF, but output calculated profile has a single value. If it's important for you to get a circadian output profile see [Circadian IC or ISF profile](#circadian-ic-or-isf-profile) below. - - ![Autotune Compare profiles](../images/Autotune/Autotune_5.png) - -- If you trust results (low percentage of variation between input profile and output profile), you can click on "Activate profile" button and then click on OK to validated. - - - Activate Tuned profile will automatically create a new profile "Tuned" in your Local profile plugin. - - If you already have a profile named "Tuned" in your local profile plugin, then this profile will be updated with calculated Autotune profile before the activation - - ![Autotune Activate profile](../images/Autotune/Autotune_6.png) - -- If you think Tuned profile must be adjusted (for example if you think some variation are too important), then you can click on "Copy to local profile" button - - - A new profile with the prefix "Tuned" and the date and time of the run will be created in local profile plugin - -![Autotune Copy to local profile](../images/Autotune/Autotune_7.png) - -- You can then select local profile to edit the Tuned profile (it will be selected by default when you open Local profile plugin) - - - the values in local profile will but rounded in the user interface to your pump capabilities - - ![Autotune local profile update](../images/Autotune/Autotune_8.png) - -- If you want to replace your input profile with Autotune result, click on "Update input profile" button and validate the Popup with OK - - - Note: if you click on "Activate profile" after "Update input profile", then you will activate your updated profile and not the default "Tuned" profile? - - ![Autotune Update input profile](../images/Autotune/Autotune_9.png) - -- If you have updated your input profile, then the "Update input profile" button is replaced by "Revert input profile" button (see screenshot below). You can that way immediatly see if your current input profile in Local profile plugin already include the result of last run or not. You also have the possibility to recover you input profile without autotune result with this button - - ![Autotune Update input profile](../images/Autotune/Autotune_10.png) - - - -## Autotune settings - -### Autotune plugin settings - -![Autotune default screen](../images/Autotune/Autotune_11.png) - -- Automation Switch Profile (default Off): see [Run Autotune with an automation rule](#run-autotune-with-an-automation-rule) below. If you change this setting to On, the input profile will automatically be updated by the Tuned profile, and it will be activated. - - **Be Carefull, you must trust and verified during several following days that after an update and activation of Tuned profile without modification, it improves your loop** - -- Categorize UAM as basal (default On): This setting is for the users using AndroidAPS without any carbs entered (Full UAM). It will prevent (when Off) to categorize UAM as basal. - - Note: if you have at least one hour of Carbs absorption detected during one day, then all data categorized as "UAM" will be categorized as basal, whatever this setting (On or Off) -- Number of days of data (default 5): You can define default value with this setting. Each time your select a new profile in Autotune plugin, Tune days parameter will be replaced by this default value -- Apply average result in circadian IC/ISF (default Off): see [Circadian IC or ISF profile](#circadian-ic-or-isf-profile) below. - -### Other settings - -- Autotune also uses Max autosens ratio and Min autotsens ratio to limit variation. You can see and adjust these values in Config Builder > Sensitivity detection plugin > Settings > Advanced Settings - - ![Autotune default screen](../images/Autotune/Autotune_12.png) - - - -## Advanced feature - -### Circadian IC or ISF profile - -- If you have important variation of IC and/or you ISF in your profile, and you fully trust in your circadian time and variation, then you can set "Apply average result in circadiant IC/ISF" - - - Note that Autotune calculation will always be done with a single value, and circadian variation will not be tuned by Autotune. This setting only apply average variation calculated for IC and/or ISF on your circadian values - -- See on screenshot below Tuned profile with Apply average variation Off (on the left) and On (on the right) - - ![Autotune default screen](../images/Autotune/Autotune_13.png) - - - -### Tune specific days of the week - -- If you click on the checkbox with the eye on the right of "Rune days" parameter, you will see the day selection. You can specify which day of the week should be included in Autotune calculation (in screenshot below you can see an example for "working days" with Saturday and Sunday removed from autotune calculation) - - If the number of day included in Autotune calculation is lower than the number of Tune days, then you will see how many days will be included on the right of Tune days selector (10 days in the example below) - - This setting gives good results only if the number of remaining days is not to small (for example if you Tune a specific profile for week end days with only Sunday and Saturday selected, you should select a minimum of 21 or 28 Tune days to have 6 or 8 days included in Autotune calculation) - -![Autotune default screen](../images/Autotune/Autotune_14b.png) - -- During Autotune calculation, you can see the progress of the calculations ("Partial result day 3 / 10 tuned" on example below) - - ![Autotune default screen](../images/Autotune/Autotune_15b.png) - -## Run Autotune with an automation rule - -First step is to define correct trigger for an automation rule with Autotune: - -Note: for more information on how to set an automation rule, see [here](./Automation.rst). - -- You should select Recurring time trigger: only run Autotune once per day, and autotune is designed to be runned daily (each new run you shift one day later and quickly profile modification should be tiny) - - ![Autotune default screen](../images/Autotune/Autotune_16.png) - -- It's better at the beginning to run Autotune during the day to be able to check results. If you want to run Autotune during the night, you have to select in the trigger 4AM or later to include current day in next Autotune Calculation. - - ![Autotune default screen](../images/Autotune/Autotune_17.png) - -- Then you can select "Run Autotune" Action in the list - - ![Autotune default screen](../images/Autotune/Autotune_18.png) - -- You can then select Autotune Action to adjust parameters for your run. Default parameters are "Active Profile", default Tune days value defined in Autotune Plugin preferences, and All days are selected. - - ![Autotune default screen](../images/Autotune/Autotune_19b.png) - -- After a few days, if you fully trust Autotune results and percentage of modification is low, you can modify [Autotune settings](#autotune-plugin-settings) "Automation Switch Profile" to enabled to automatically update and activate profile tuned after calculation. - -Note: if you want to automatically tune profiles for specific days of the week (for example a profile for "Weekend days" and another one for "Working days"), then create one rule for each profile, select the same days in Trigger and in Autotune Action, Tune days must be high enough to be sure tuning will be done with at least 6 or 8 days, and don't forget to select time after 4AM in trigger... - -- See below an example of rule to tune "my profile" on all "Working days" with 14 Tune days selected (so only 10 days included in autotune calculation). - -![Autotune default screen](../images/Autotune/Autotune_20b.png) - - - -## Tips and trick's - -Autotune works with information existing in your database, so if you just installed AAPS on a new phone, you will have to wait several days before being able to launch Autotune with enough days to get relevant results; - -Autotune is just an help, it's important to regularly check if you agree with calculated profile. If you have any doubt, change Autotune settings (for example the number of days) or copy results in local profile and adjust profile before using it. - -Always use Autotune several days manually to check results before applyling them. And it's only when you fully trust Autotune results, and when variation becomes tiny between previous profile and calculated profile than you start to use Automation (Never before) - -- Autotune can work very well for some users and not for others, so **If you don't trust Autotune result, don't use it** - -It's also important to analyse Autotune results to understand (or try to understand) why Autotune propose these modifications - -- you can have a whole increase or decrease of the strength of your profile (for example increase of total basal associated to decrease of ISF and IC values). it could be associated to several following days with autosens correction above 100% (more agressivity required) or below 100% (you are more sensitive) -- Sometimes Autotune propose a different balance between basal rates and IC/ISF (for ex lower basal and more aggressive IC/ISF) - -We advise to not use Autotune in the following cases: - -- You don't enter all your carbs - - If you don't enter carbs correction for an hypoglycemia, Autotune will see an unexcepted increase of your BG value and will increase your basal rates the ' hours earlier, it could be the opposite of what you need to avoid hypo, especially if it's in the middle of the night. That's why it's important to enter all carabs especially correction for hypo. -- You have a lot of period with UAM detected during the day. - - Do you have entered all your carbs and correctly estimated your Carbs ? - - All UAM periods (except if you enter no carbs during a day and categorized UAM as basal is disabled), all your UAM periods will be categorized as basal, this can increase a lot your basal (much more than necessary) - -- Your carbs absorption is very slow: if most of your carbs absorption are calculated with min_5m_carbimpact parameter (you can see these periods with a little orange dot in the top of COB curve), the calculation of COB could be wrong and leads to wrong results. - - We you practice sport, you are generally more sensitive and your BG doesn't rise a lot, so during or after an exercice, it's usual to see some periods with slow carbs. But if you have too often unexpected slow carb absorption, then you may need a profile adjustment (higher value of IC) or a min_5m_carbimpact a bit to high. -- You have a "very bad days", for example stuck several hours in hyperglycemia with a huge amount of insulin to be able to go down within the range, or after a sensor change you got long periods of wrong BG values. -- If the percentage of modification is too important - - You can try to increase the number of days to get smoother results \ No newline at end of file diff --git a/docs/CROWDIN/pl/Usage/making-sport-with-AAPS.md b/docs/CROWDIN/pl/Usage/making-sport-with-AAPS.md deleted file mode 100644 index 79d2f1c38223..000000000000 --- a/docs/CROWDIN/pl/Usage/making-sport-with-AAPS.md +++ /dev/null @@ -1,185 +0,0 @@ -# making sport with AAPS - -In this section we want to address the topic of sport with AAPS. - -The aim is to show you how AAPS can help you to continue doing your favorite sport more easily or even to start doing it. It is relatively common for new type 1 diabetics to ask whether exercise is still possible for them, even if the answer in the training courses is actually a clear yes. Exercise is not only good for healthy people, but also for type 1 diabetics and even moderate exercise can even help to stabilize the blood sugar curve overall. - -:::{admonition} consult with your diabetes team after reading - -::: - -The difficulty here is that the prerequisites that someone brings with them and the expectations of what sport means to them are very different. - -Since we can assume that experienced top athletes with T1D who use AAPS are unlikely to look it up here, we deliberately set the bar low for ourselves when writing and for you when reading and using it, so that as many people as possible can benefit from it. - -Since even sport as a category is far too imprecise, as the effects of endurance sports differ greatly from strength training, for example, we are trying to break it down by type of sport. - -To be concrete and give you something you can test yourself we arrange the explanaiton around a concrete example and explain to you they action, reactions and effects. - -:::{admonition} more examples wanted - -The focus should always be on how others can do sport and not on the top performance someone has achieved. - -It's really about the basics. Your experience, which you share here, can help others to pursue their beloved sport more quickly and successfully and is therefore important. -::: - -## Cycling - -:::{admonition} take a friend with you - at least on your first trials -:class: information -A gerneral very good idea can be to take a good friend with you on the first rides. -This is especially important if you are not experienced in T1D. -Always keep in mind please: arrival comes before speed! Safety for you and the others in road traffic is very, very important. -::: - -### Example - -Let's take about 60 minutes of cycling on a flat route with a moderate heart rate as an example. - -1. we take a flat route in order to have an even load for the first exercise. This is not about performance, but purely about learning how you should react to changes in blood glucose. -2. we take the heart rate as an indicator of the load, as it is easy to see whether you are under load or not. -3. we set ourselves the goal of doing a relaxed lap around the neighborhood and focus on staying within our target range during the lap. In my case, this would be 70 <= x <= 180 mg/dl. - -We **don't** take the speed, as this is heavily dependent on personal physical conditions as well as the bike and surface used. It is therefore not very meaningful. - -You should know from the diabetes training courses you have attended that during endurance sports cycling, the insulin active in the body works significantly better than during times without physical exertion. The insulin active in the body is referred to as insulin on board (IoB). It is our most important parameter when cycling with T1D. - -We try to keep the IoB as low as possible at the start and during exercise. IoB should be around 0 or even slightly negative. You can get it there by not eating 3-4 hours before exercise. In the beginning it can also be helpful to exercise in the morning before breakfast, as with the right profile you should always have around 0 for IoB in the morning. - -AAPS shows us the IoB value on the home screen on the left under the blood glucose value. - -![IoB](../images/cycling_20240104-174035.png) - -:::{admonition} ignoring the IoB rule increases the risk for roller coaster BG dramatically -:class: danger -If you ignore this rule, you can still go cycling, but it will be much more difficult to keep your blood sugar levels in balance, so it is better to save this for later tests after several successful simple tests. -::: - -As you should know from the diabetes training courses, you should reduce the basal rate during exercise. The factor is individual. I have found a value of 50% in tests to be suitable for me. - -In AAPS, you should therefore change your profile to 50% before exercise and keep it active until the end of exercise. Some people even do it a certain amount of time before, e.g. 1 hour. Unfortunately, the pre-run is also individual. We will come to the post-run later. - -You should use two carbohydrates during exercise. - -1. medium-fast carbohydrates for the insulin still in the body and -2. very fast carbohydrates to prevent slipping into a hypo. - -For medium-fast carbohydrates, I treat myself to cookies or a banana before exercise, for example. You can also use something else that is more suitable for you. -For very fast carbohydrates, I take 3 teaspoons of dissolved glucose per 100 ml of still water in a 500 ml water bottle on my bike. If I'm cycling longer distances, I take a larger bottle with me and, if necessary, packaged glucose to refill the bottle. I add a little lemon juice for flavor. You can also use something other than lemon juice for the taste. You shouldn't change anything about the dextrose, as dissolved dextrose raises blood sugar levels super quickly. If you only take it in sips, your blood sugar won't go super high either! You can also do this tip at home beforehand as a dry run and see how quickly the change shows up on the CGMS. - -Why do I place so much emphasis on fast carbohydrates? - -1. once you are in a slight hypo, you may get back into the normal range by drinking the dextrose solution. As a rule, however, the oscillation of the curve then begins, which leads to a rollercoaster ride of the blood sugar. You may even be able to keep this within your target range, but you must be constantly vigilant. Without a hypo it is simply the most stable. -2. if you even slip into a somewhat severe hypo (without the need for outside help, of course), you may even have to pause briefly to avoid getting stuck in the hypo. - With both hypos, there is a risk that you will be tempted to switch from drinking 2-3 sips at a time to larger quantities. Not too bad at first, until the oscillation sets in and pushes you into a hyper. You can correct this, but your blood sugar will most likely go on a rollercoaster ride. - -What else is helpful, but not absolutely necessary? -It is important to keep an eye on your blood sugar, as your blood sugar can change enormously (e.g. 30 - 50 mg/dl) within 15 minutes of riding and a little more IoB or a basal rate that is still too high. The best way to keep an eye on it is if it is visible on the handlebars or if it is also displayed on your watch. It is even possible to install an additional app on some Garmin GPS bike computers that displays the blood glucose from XDrip or Nightscout as a data field on the bike computer. The additional app was developed by Andreas May from the T1D community. It is available free of charge in the official connect IQ Store. Certainly an interesting option for riders interested in sports. - -[Link to Andreas May Data Field App on connect IQ store](https://apps.garmin.com/de-DE/apps/5a3e2cda-12f0-4afd-88ed-000e67a68d84) - -Here is a picture of my Garmin Edge 530 bike computer with map, blood sugar and heart rate. - -![Garmin Edge 530 with BG data field](../images/cycling_IMG_1087.jpeg) - -After you have eaten the medium fast carbohydrates (24 - 36 g I take) and the blood sugar is above 100 mg/dl but also below 160 mg/dl, I carry out the profile change to 50% and set the activity temp target. - -:::{admonition} disable SMBs during high temp targets if necessary -:class: danger -Attention: If you prefer not to receive SMBs during the sport, please disable the option "Enable SMB with hight temp targets" in the settings of SMB or DynIFS Plugin. -::: - -The following picture shows the start and end of the sport. The end was specified as the duration when the profile was changed at the start. - -The temporary profile change has the following effects - -1. for a period of 60 minutes -2. a reduction to 50% of the profile and -3. the target is raised by clicking on the Activity Target option, which may have the side effect of disabling the SMBs - see above. - -![profile switch with temp target](../images/cycling_20240104-174056.png) - -The second image shows that the start at IoB was started towards 0. - -![IoB around 0](../images/cycling_20240104-174111.png) - -If the blood sugar drops faster than 15 mg/dl in 5 minutes or if it is at 120 mg/dl and tends to fall, I drink 1-2 sips of dissolved glucose. Then I wait for the next value and proceed as described above. - -You can hardly see it here, but at the beginning I took 2 sips from the bottle several times when my blood sugar started to fall. When it stabilized, I didn't need any more glucose. - -Here is the picture that illustrates this. The chart is saved on the Garmin as a result of the activity. - -![BG chart Garmin](../images/cycling_20240104-174431.png) - -If you should suddenly break out upwards, i.e. above 180 mg/dl, you should consider whether you should make a correction bolus. Caution: Remember the factor and apply it to the correction, otherwise the correction will be too strong. - -If your blood sugar drops below 80 mg/dl, take a break and drink two sips until your blood sugar is back above 100 mg/dl. - -At the end of the ride, the profile change should be finished as the time is up. - -Since we only rode easy for 60 minutes, there shouldn't be a big muscle bulking effect continuing to pull carbohydrates from your blood sugar. However, if it felt strenuous to you, keep an eye on it. This is especially true if you then go straight to bed. It may be better to change your profile to e.g. 80% for sleep. You may come out of sleep slightly too high, but it's better than having a hypo at night. Over time, you will surely find out what happens to you. - -The following pictures show the low intensity of the sport. - -The elevation profile -![](../images/cycling_20240104-174314.png) - -Speed with average and maximum speed - -![](../images/cycling_20240104-174326.png) - -Note the pause at the level crossing, which is also reflected in the heart rate. - -The heart rate. -![](../images/cycling_20240104-174337.png) - -The training effect. -![](../images/cycling_20240104-174358.png) - -The time in the different heart rate training zones. -![](../images/cycling_20240104-174423.png) - -After succesfully mastering this simple example you could go for further targets by stretching - -1. the distance and time -2. the load during the ride -3. the elevation during the right which should make a big impact on the more necessary carbs or further reduction of IoB and percentage of profile switch. - -Based on my experiences I would not expect to come back 100% with time in range over the whole and every ride. - -### Tipps - -I already gave some tipps for during the ride above. - -Here are some further tipps what can go wrong and how you can act to prevent it or react to compensate it. - -#### sky rocket high after ride - -During the ride everything was fine but after siting down and relax the blood sugar go sky rocket high. - -**Possible reason:** This happens when you have drunk too much dissolved glucose. - -**Reaction:** Drink 500 ml water, go to the shower and then control again. Latest after 30 minutes think about giving a correction bolus but be careful when it is short for bed time. Therefore it can be very good to make the first try runs on weekend mornings. - -**Action:** Next time be a bit more cautious in drinking from the dissolved glucose. - -#### hypo during ride - -During the ride you are going into hypo and can't recover your blood sugar during cycling. - -**Possible reason:** Your body cannot absorb enough carbohydrates quickly enough during exercise. - -**Reaction:** Take a rest and corrrect your blood sugar with drinking dissolved glucose. Stay calm: arrival comes before speed. - -**Action:** Did you started with IoB near 0? Have you eaten a small amount of middle fast carbs? Can you increase this or are the not fast enough for your body? Is it possible to prevent going into hypo by reducing the factor for the profile switch? Have you disbaled SMBs during ride as explained above? - -#### sky rocket high during ride - -During the ride your blood sugar goes sky rocket high. - -**Possible reason:** You have got taken too much carbs for your IoB at that time. Beneath for sure the typical technical problems with your -insulin pump like leakage or blockage of the catheder! - -**Reaction:** If it is too high for you take a rest and correct with a bolus. Keep in mind that you must ride home and therefore make it carefully. Drink 500 ml pure water without carbs. Stay calm: arrival comes before speed. - -**Action:** Have you eaten too much? Especially have you drunk too much from the dissolved glucose during the ride? Is your percentage of reduction the profile during profile switch too low and you can increase this? diff --git a/docs/CROWDIN/pl/buildingAAPS.md b/docs/CROWDIN/pl/buildingAAPS.md deleted file mode 100644 index 98164a09e49b..000000000000 --- a/docs/CROWDIN/pl/buildingAAPS.md +++ /dev/null @@ -1,28 +0,0 @@ -# Dummy - -## This is a dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - - -## This is another dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - - -## This is another another dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - diff --git a/docs/CROWDIN/pl/completingObjetives.md b/docs/CROWDIN/pl/completingObjetives.md deleted file mode 100644 index 98164a09e49b..000000000000 --- a/docs/CROWDIN/pl/completingObjetives.md +++ /dev/null @@ -1,28 +0,0 @@ -# Dummy - -## This is a dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - - -## This is another dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - - -## This is another another dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - diff --git a/docs/CROWDIN/pl/dummy.md b/docs/CROWDIN/pl/dummy.md deleted file mode 100644 index 98164a09e49b..000000000000 --- a/docs/CROWDIN/pl/dummy.md +++ /dev/null @@ -1,28 +0,0 @@ -# Dummy - -## This is a dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - - -## This is another dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - - -## This is another another dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - diff --git a/docs/CROWDIN/pl/intro.md b/docs/CROWDIN/pl/intro.md deleted file mode 100644 index 373cdc4fea7c..000000000000 --- a/docs/CROWDIN/pl/intro.md +++ /dev/null @@ -1,291 +0,0 @@ -![20-06-23v2 AAPS simple overview-cropped](https://github.com/openaps/AndroidAPSdocs/assets/94044064/e505b73b-09a0-42a4-a1ab-b830a0741234) - -# Introduction to APS and AAPS - -## What is an “Artificial Pancreas System”? - -A human pancreas does a lot of things besides regulating blood sugar. However, the term **“Artificial Pancreas System” (APS)** usually refers to a system which works to automatically keep blood sugar levels within healthy limits. - -The most basic way to do this is by detecting **glucose levels**, using these values to do **calculations**, and then delivering the (predicted) right amount of **insulin** to the body. It repeats the calculation, every few minutes, 24/7. It uses **alarms** and **alerts** to inform the user if intervention or attention is needed. This system is typically made up of a **glucose sensor**, an **insulin pump** and an **app** on a phone. - -You can read more about the different artificial pancreas systems currently in use and in development in this 2022 review article: - -![Frontiers](./images/FRONTIERS_Logo_Grey_RGB.png) [Future Directions in Closed-Loop Technology](https://www.frontiersin.org/articles/10.3389/fendo.2022.919942/full#:~:text=Fully%20closed%2Dloop%20systems%2C%20unlike,user%20input%20for%20mealtime%20boluses). - -In the near future, some so-called "dual-hormone" systems will also have the ability to infuse glucagon alongside insulin, with the aim of preventing severe hypos and allowing even tighter blood glucose control. - -An artificial pancreas can be thought of as an [“autopilot for your diabetes”]. (https://www.artificialpancreasbook.com/) What does that mean? In an aircraft, an autopilot does not do the complete job of the human pilot, the pilot cannot sleep through the entire flight. The autopilot aids the work of the pilot. It relieves them of the burden of permanently monitoring the aircraft, allowing the pilot to concentrate on wider monitoring from time to time. The autopilot receives signals from various sensors, a computer evaluates them together with the pilot’s specifications and then makes the necessary adjustments, alerting the pilot to any concerns. The pilot no longer has to worry about constantly making decisions. - -## What does hybrid closed loop mean? - -The best solution for type 1 diabetes would be a “functional cure” (probably an implant of pancreatic cells which are protected from the immune system). While we are waiting for that, a “full closed loop” artificial pancreas is probably the next best thing. This is a tech system that doesn’t need any user input (like bolusing insulin for meals, or announcing exercise), with good regulation of blood glucose levels. At the moment, there are no widely available systems which are “full” closed loop, they all need some user input. The currently available systems are called “hybrid” closed loop, because they use a combination of automated technology and user input. - -## How and why did looping start? - -The development of commercial technology for people with type 1 diabetes (T1D) is very slow. In 2013 the T1D community founded the #WeAreNotWaiting movement. They developed systems themselves using existing approved technology (insulin pumps and sensors) to improve blood glucose control, safety, and quality of life. These are known as DIY (do-it-yourself) systems, because they are not formally approved by health bodies (FDA, NHS etc). There are four main DIY systems available: OpenAPS, **AAPS**, Loop and iAPS. - -A great way to understand the fundamentals of DIY looping is to read Dana Lewis’s book “Automated Insulin Delivery”. You can access it \[here\] (https://www.artificialpancreasbook.com/) for free (or buy a hardcopy of the book). If you want to understand more about OpenAPS, which** AAPS** has developed from, the \[OpenAPS website\] (https://openaps.org/what-is-openaps/) is also a great resource. - -Several commercial hybrid closed loop systems have been launched, the most recent of which are \[CamAPS FX\] (https://camdiab.com/) (UK and EU) and \[Omnipod 5\] (https://www.omnipod.com/en-gb/what-is-omnipod/omnipod-5) (USA and EU). These are very different to DIY systems, mainly because they both include a “learning algorithm” which adjusts how much insulin is delivered according to your insulin needs from previous days. Many people in the DIY community have already tried out these commercial systems and compared them with their DIY system. You can find out more about how the different systems compare by asking on the dedicated Facebook groups for these systems, on the \[AAPS Facebook group\] (https://www.facebook.com/groups/AndroidAPSUsers/) or on \[Discord\] (https://discord.com/invite/4fQUWHZ4Mw). - -## What is Android APS (AAPS)? - -![image](https://github.com/openaps/AndroidAPSdocs/assets/94044064/0f089d96-b7ee-452a-aa9d-aae10ab58971) - -**Figure 1**. Basic outline of the Android APS (Artificial Pancreas System), AAPS. - -Android APS (AAPS) is a hybrid closed loop system, or Artificial Pancreas System (APS). It makes its insulin dosing calculations using established \[OpenAPS\] (https://openaps.org/) algorithms (a set of rules) developed by the #WeAreNotWaiting type 1 diabetes community. - -Since OpenAPS is only compatible with certain older insulin pumps, AAPS (which can be used with a wider range of insulin pumps) was developed in 2016 by Milos Kozak, for a family member with type 1 diabetes. Since those early days, **AAPS** has been continually developed and refined by a team of volunteer computer developers and other enthusiasts who have a connection to the type 1 diabetes world. Today, **AAPS** is used by approximately 10,000 people. It is a highly customisable and versatile system, and because it is open-source, it is also readily compatible with many other open-source diabetes softwares and platforms. The fundamental components of the current **AAPS** system are outlined in Figure 1 above. - -## What are the basic components of AAPS? - -The “brain” of AAPS is an **app** which you build yourself. There are detailed step-by-step instructions for this. You then install the **AAPS app** on a compatible **Android smartphone** (1). A number of users prefer their loop on a separate phone to their main phone. So, you don’t necessarily have to be using an Android phone for everything else in your life, just for running your AAPS loop. - -The **Android smartphone** will also need to have another app installed on it as well as **AAPS**, either a modified Dexcom app called build-your-own dexcom app (**BYODA**) or Xdrip+. This receives glucose data from a sensor (2) by bluetooth, and then sends the data internally on the phone to the **AAPS app**. - -The **AAPS app** uses a decision making process (**algorithm**) from OpenAPS. Beginners start out using the basic **oref0** algorithm, but it is possible to switch to using the newer **oref1** algorithm as you progress with AAPS. Which algorithm you use (oref0 or oref1), depends on which suits your specific situation best. In both cases, the algorithm takes into account multiple factors, and performs rapid calculations every time a new reading comes in from the sensor. The algorithm then sends instructions to the insulin pump (3) on how much insulin to deliver by bluetooth. All the information can be sent by mobile data or wifi to the internet. This data can also be shared with followers if desired, and/or collected for analysis. - -## What are the advantages of the AAPS system? - -The OpenAPS algorithm used by **AAPS** controls blood sugar levels in the absence of user input, according to the users’ defined parameters (important ones being basal rates, insulin sensitivity factors, insulin-to-carb ratios, duration of insulin activity etc.), reacting every 5 minutes to the new sensor data. Some of the reported advantages of using AAPS are extensive fine-tunable options, automations and increased transparency of the system for the patient/caregiver. This can result in better control over your (or your dependent’s) diabetes, which in turn may give improved quality of life and increased peace of mind. - -Practical advantages include: - -- **Hardware flexibility**: **AAPS** works with a wide range of insulin pumps and sensors. So for example, if you develop an allergy to Dexcom sensor patch glue, you could switch to using a Libre sensor instead. That offers flexibility as life changes. You don't have to rebuild, just tick a different box in the AAPS app to change your hardware. - -- **Highly customisable with wide parameters**: here are some examples of the possibilities with AAPS: a) The ability to set a lower glucose target 30 min before eating; you can set the target as low as 72 mg/dL (4.0 mmol/L). b) If you are insulin-resistant resulting in high blood sugars, **AAPS** allows you to set an **automation** rule to activate when BG rises above 8 mmol/L (144 mg/dL), switching to a 120% profile (resulting in an 20% increase in basal and strengthening of other factors too, compared to your normal **profile** setting). The automation will last according to the scheduled time you set. Such an automation could be set to only be active on certain days of the week, at certain times of day, and even at certain locations. c) If your child is on a trampoline with no advance notice, **AAPS** allows insulin suspension for a set time period, directly via the phone. d) After reconnecting a tubed pump which has been disconnected for swimming, AAPS will calculate the basal insulin you have missed while disconnected and deliver it carefully, according to your current BG. Any insulin not required can be overridden by just “cancelling” the missed basal. f) **AAPS** has the ability to set different profiles for different situations and easily switch between them. Features which make the algorithm quicker to bring down elevated BG (like supermicro boluses (“SMB”), unannounced meals, (“**UAM**”) can be set to only work during the daytime, if you are worried about night-time hypos. - - -These are all examples, the full range of features gives huge flexibility for daily life including sport, illness, hormone cycles etc. Ultimately, it is for the user to decide how to use this flexibility, and there is no one-size-fits-all automation for this. - -- **Remote monitoring**: there are multiple possible monitoring channels (Sugarmate, Dexcom Follow, Xdrip+, Android Auto etc.) which are useful for parents/carers and adults in certain scenarios (sleeping/driving) who need customisable alerts. In some apps (Xdrip+) you can also turn alarms off totally, which is great if you have a new sensor “soaking” or settling down that you don’t want to loop with yet. - -- **Remote control**: a significant advantage of **AAPS **over commercial systems is that it is possible for followers, using authenticated text (SMS) commands or via an app (Nightscout or NSClient) to send a wide range of commands back to the ****AAPS** **system. This is used extensively by parents of kids with type 1 diabetes who use AAPS. It is very useful in the playground, for example, if you want to pre-bolus for a snack from your own phone, and your child is busy playing. It is possible to monitor the system (e.g. Fitbit), send basic commands (e.g. Samsung Galaxy watch 4), or even run the entire AAPS system from a high-spec smartwatch (5) (e.g. LEMFO LEM14). In this last scenario, you don’t need to use a phone to run AAPS. As battery life on watches improves, this last option is likely to become increasingly attractive. - -- **No commercial constraints due to open application interfaces**: beyond the use of an open source approach, which allows the source code of **AAPS** to be viewed at any time, the general principle of providing open programming interfaces gives other developers the opportunity to contribute new ideas that allow users to live more easily with their diabetes. This is complementary to commercial systems which adopt the innovations from DIY, where interfaces are only made possible in return for licensing, thus preventing innovations in particular that are not-for-profit. Good examples for such integrations are NightScout, Nightscout Reporter, Xdrip+ M5 stack etc. - -- **Detailed app interface**: It is easy to keep track of things like: insulin levels, cannula age, sensor age, pump battery age, and many actions can be done through the **AAPS** app (priming the pump, disconnecting the pump etc.), instead of on the pump itself. - -- **Accessibility and affordability**: **AAPS** gives people who currently can’t afford to self-fund, or don’t have funding/insurance, access to a world-class hybrid closed looping system which is conceptually years ahead, in terms of development, of the commercial systems being offered by clinics. You currently need to have a Nightscout account to set up **AAPS**. Although the Nightscout account it not necessarily required after setup, many people continue to use Nightscout for collecting their data, and for remote control. So, although **AAPS **itself is free, setting up Nightscout through one of the various platforms may incur a fee (E0 - E12), depending on what level of support you want (see comparison table). **AAPS** works with a wide range of affordable (starting from approx E150) Android phones. In comparison, Loop currently costs around $80 a year for the Apple development licence and CamAPS FX costs around E80/month (as at 2023). - -- ****Support**: No automated insulin delivery system is perfect. Commercial and open-source systems share many common glitches in both communications and temporary hardware failure. There is a community of AAPS users on both Facebook and Discord and Github who designed, developed and are currently using **AAPS** all over the world. There are Facebook support groups and help from clinic/commercial companies for the commercial APS systems - it is worth speaking to the users, or former users of these systems to get feedback on the common glitches, the quality of the education programme and the level of ongoing support provided. - -- **Predictability, transparency and safety**: with no learning algorithm, **AAPS** is logical and in some respect, more predictable, which may make it easier to know when a setting is wrong, and to adjust it accordingly. You can see exactly what the system is doing, why it is doing it, and set its operational limits, which puts the control (and responsibility) in your hands. This can provide the user with confidence, and a sounder sleep. - -- **Access to advanced features through dev modes including full closed loop**: **AAPS **documentation focuses on the mainstream **“master”** branch of **AAPS**, however, research and development is going on all the time. More experienced users may wish to explore the experimental features in the **development** branch such as integration of Dexcom G7, and automatically adjusting insulin delivery according to short-term sensitivity changes (DYNISF), not having to bolus for meals, and generally trying to make life with type 1 diabetes as convenient as possible. - -- **Ability to contribute yourself to further improvements**: type 1 diabetes can be highly frustrating and isolating. Having control over your own diabetes tech, with the possibility to “pay it forward” as soon as you are making progress by helping others on their journey can be really rewarding. You can educate yourself, discover the roadblocks and look for and even contribute to new developments and the documentation. There will be others with the same quest to bounce ideas off and work with. This is the essence of #WeAreNotWaiting. - - -## How does AAPS compare to MDI and open looping? - -Multiple daily injections (MDI, a) usually involve giving an injection of a long-lasting insulin (e.g. Tresiba) once a day, with injections of faster-acting insulin (e.g. Novorapid, Fiasp) at mealtimes, or for corrections. Open pumping (b) involves using a pump to deliver basal at pre-programmed rates of rapid-acting insulin, and then boluses through the pump at mealtimes or for corrections. The basics of a looping system is that the App uses the glucose data to instruct the pump to stop insulin delivery when it predicts you are heading for a low, and to give you extra insulin if your glucose levels are rising and predicted to go too high (c). Although this is oversimplified, (mostly because hybrid closed looping has a lot of additional useful features) the key features of each system are shown in **Figure 2**. - -![image](https://github.com/openaps/AndroidAPSdocs/assets/94044064/4e7d8608-684d-4c69-9c61-88c9539f5d6f) - -**Figure 2**. Overview of (a) MDI, (b) open-loop pumping and (c) hybrid closed loop pumping - -## How does AAPS compare to other looping systems? - -At present there are four major open source closed loop systems available: OpenAPS, **AAPS**, \[Loop\] (https://loopkit.github.io/loopdocs/#what-is-loop) and iAPS, (formerly FreeAPS X). The features of the different systems are shown in the table below: - -| Devicestyp | Name | [Open APS](https://openaps.readthedocs.io/en/latest/) | [AAPS](https://wiki.aaps.app) | [Loop](https://loopkit.github.io/loopdocs/) | [iAPS](https://iaps.readthedocs.io/en/latest/) | -| ---------- | -------------------------------------------------------------------------------------------------------- | ----------------------------------------------------- | ------------------------------------------- | ------------------------------------------- | ---------------------------------------------- | -| PUMP | Older Medtronic | ![available](./images/available.png) | ![available](./images/available.png) | ![available](./images/available.png) | ![available](./images/available.png) | -| PUMP | Older Omnipod (Eros) | ![unavailable](./images/unavailable.png) | ![available](./images/available.png) | ![available](./images/available.png) | ![available](./images/available.png) | -| PUMP | Newer Omnipod (Dash) | ![unavailable](./images/unavailable.png) | ![available](./images/available.png) | ![available](./images/available.png) | ![available](./images/available.png) | -| PUMP | DANA R, DANA RS, DANA I | ![unavailable](./images/unavailable.png) | ![available](./images/available.png) | ![unavailable](./images/unavailable.png) | ![unavailable](./images/unavailable.png) | -| PUMP | Roche Combo, Insight | ![unavailable](./images/unavailable.png) | ![available](./images/available.png) | ![unavailable](./images/unavailable.png) | ![unavailable](./images/unavailable.png) | -| CGM | Dexcom G4, G5, G6 | ![available](./images/available.png) | ![available](./images/available.png) | ![available](./images/available.png) | ![available](./images/available.png) | -| CGM | Libre 1 (requires Miao Miao) | ![available](./images/available.png) | ![available](./images/available.png) | ![available](./images/available.png) | ![available](./images/available.png) | -| CGM | Libre 2 | ![available](./images/available.png) | ![available](./images/available.png) | ![available](./images/available.png) | ![available](./images/available.png) | -| CGM | Libre 3 | | ![unavailable](./images/unavailable.png) | --- | ![unavailable](./images/unavailable.png) | -| CGM | Medtronic Enlite | | --- | ![unavailable](./images/unavailable.png) | --- | -| CGM | [Dexcom G7](https://androidaps.readthedocs.io/en/latest/Hardware/DexcomG7.html) | | ![available](./images/available.png) (beta) | ![available](./images/available.png) | ![available](./images/available.png) | -| CGM | [Eversense](https://androidaps.readthedocs.io/en/latest/Hardware/Eversense.html) | | ![available](./images/available.png) | | ![available](./images/available.png) | -| CGM | [MM640g/MM630g](https://androidaps.readthedocs.io/en/latest/Hardware/MM640g.html) | | ![available](./images/available.png) | | ![available](./images/available.png) | -| CGM | [PocTech](https://androidaps.readthedocs.io/en/latest/Hardware/PocTech.html) | | ![available](./images/available.png) | | ![available](./images/available.png) | -| CGM | [Nightscout as BG Source](https://androidaps.readthedocs.io/en/latest/Hardware/CgmNightscoutUpload.html) | | ![available](./images/available.png) | | ![available](./images/available.png) | -| Phone | Android | ![available](./images/available.png) | ![available](./images/available.png) | ![unavailable](./images/unavailable.png) | ![unavailable](./images/unavailable.png) | -| Phone | iPhone | ![available](./images/available.png) | ![unavailable](./images/unavailable.png) | ![available](./images/available.png) | ![available](./images/available.png) | - -[OpenAPS](https://openaps.readthedocs.io/) was the first Open Source Closed Loop System. It uses a small computer such as Raspberry Pi or Intel Edison. Both AndroidAPS (AAPS) and iAPS use the OpenAPS algorithms, whereas Loop uses a separate algorithm. You can read a comparison of iAPS and **AAPS** here. - -An international peer-reviewed consensus statement containing practical guidance on open source looping was written by and for health-care professionals, and published in a leading medical journal in 2022. It is well worth a read (including for your diabetes clinic) and summarises the main technical differences between the different open-source hybrid closed loop systems: - - Lancet Diabetes Endocrinol, 2022; 10: 58–74 - -[https://www.ncbi.nlm.nih.gov/pmc/articles/PMC8720075/](https://www.ncbi.nlm.nih.gov/pmc/articles/PMC8720075/) - -It is hard to get a “feel” for any system without using it, or talking to others who are using it, so do reach out to others on Facebook/Discord and ask. Most people find that AAPS is incredibly sophisticated in comparison to other hybrid closed loop systems (particularly the commercial systems), with a huge number of potentially customisable settings and features, discussed above. Some people can find this a little overwhelming in the beginning, but there is no rush to investigate all the possibilities at once, you can progress as slowly or as fast as you would like, and there is help available at every step of the way. - -## Does AAPS use artificial intelligence or any learning algorithm? - -No. **AAPS** does not have any complicated machine learning algorithms, multiple-parameter insulin response models, or differential equations. As such, the system is open and transparent in how it works, and has the ability to be understood not just by experts, but also by clinicians and patients. It also means that if you have a sharply varying schedule (maybe switching from a stressful week at work to a relaxing holiday) and are likely to need a significantly different amount of insulin, you can immediately switch **AAPS** to run a weaker/stronger profile. A ‘learning system’ will do this adjustment for you automatically, but is likely to take longer to adjust the insulin delivery. - -## Which system is right for me or my dependent? - -Practically, your choice of system is often restricted by which pump you already have, or can obtain from your medical provider, and your choice of phone (Apple or Android). If you don’t yet have a pump you have the biggest choice of systems. Technology is continually evolving, pumps are being discontinued and new pumps and sensors are being released. Most open-source systems work with the main sensors (Libre and Dexcom) or are quickly adapted to work with new sensors a year or so after they are released (with a bit of time delay for safety and stability testing). - -Most **AAPS **users report more time in range, HbA1c reductions, as well as quality of life improvements from having a system that can auto-adjust basal rates overnight during sleep, and this is true for most hybrid closed loop APS. Some people have a preference for a very simple system which is not very customisable (which means you may prefer a commercial system), and others find this lack of control very frustrating (you may prefer an open-source system). If you (or your dependent) are newly diagnosed, a common route is to get the hang of MDI plus sensor first, then progress to a pump which has the potential for looping, then to **AAPS**, but some people (especially small kids) may go straight to a pump. - -It is important to note that the **AAPS** user needs to be proactive to troubleshoot and fix problems themselves, with help from the community. This is a very different mindset to that when using a commercial system. With **AAPS** a user has more control, but also the responsibility, and needs to be comfortable with that. - -## Is it safe to use open-source systems like AAPS? - -A more accurate question is probably “is it safe compared to my current type 1 diabetes insulin delivery system?” since no method of insulin delivery is without risk. There are many checks and balances in place with **AAPS**. A recent paper looked at the use of**** AAPS ****in a computer simulated set-up, [https://www.liebertpub.com/doi/epub/10.1089/dia.2019.0375](https://www.liebertpub.com/doi/epub/10.1089/dia.2019.0375) which was an effective way to unobjectively trial how safe and effective the system is. More generally, it is estimated that over 10,000 individuals worldwide are using open-source automated-insulin delivery systems, and uptake continues to increase globally. - -Any device that uses radio communications could be hacked, and this is true for a non-looping insulin pump as well. Currently, we are not aware of anyone attempting to harm individuals by hacking their diabetes-related medical equipment. However, there are multiple ways to protect against such risks: - -1. In the pump settings, limit both the max bolus allowed and max temporary basal settings to amounts that you believe are safest. These are hard limits that we do not believe any malicious hacker could circumvent. - -2. Set your CGM alarms enabled for both highs and lows. - -3. Monitor your insulin delivery online. Nightscout users can set additional alarms to alert for a wide variety of conditions, including conditions that are much more likely to occur than a malicious attack. In addition to highs and lows, Nightscout can display diagnostic data useful for verifying that the pump is operating as desired, including current IOB, pump temporary basal history, pump bolus history. It can also be configured to proactively alert users to undesirable conditions, such as predicted highs and lows, low insulin reservoir, and low pump battery. - - -If a malicious attack was made on your insulin pump, these strategies would significantly mitigate the risk. Every potential **AAPS** user needs to weigh the risks associated with using **AAPS**, versus the risks of using a different system. - -## How can I approach discussing AAPS with my clinical team? - -Depending on the country - link to doctors section of docs - - Lancet Diabetes Endocrinol, 2022; 10: 58–74 - -[https://www.ncbi.nlm.nih.gov/pmc/articles/PMC8720075/](https://www.ncbi.nlm.nih.gov/pmc/articles/PMC8720075/) - -## Q: Why can’t I just download AAPS and use it straight away? - -The **AAPS** app is not provided in Google Play - you have to build it from source code by yourself for legal reasons. **AAPS** is unlicensed, meaning that it does not have approval by any regulatory body authority in any country. **AAPS**is deemed to be carrying out a medical experiment on yourself, and is carried out at the user’s own risk. - -Setting up the system requires patience, determination and the gradual development of technical knowledge. All the information and support can be found in these documents, elsewhere online, or from others who have already done it. It is estimated that over 2000 people have successfully built and are currently using **AAPS** worldwide. - -The developers of **AAPS**t ake safety incredibly seriously, and want others to have a good experience of using **AAPS**. That is why it is essential that every user (or carer, if the user is a child): - -- builds the AAPS system themself and works through the **objectives** so that they have reasonably good personalised settings and understand the basics of how AAPS ****works by the time they “close the loop”; - -- backs up their system by exporting and saving important files (like keystore and settings .json file) somewhere safe, so you can setup again quickly if needed; - -- updates to newer master versions as and when they become available; and - -- maintains and monitors the system to ensure it is working properly. - - -## Q: What is the connectivity of the AAPS system? - -**Figure 3 (below)** shows one example of the **AAPS** system for a user who do not require any followers interacting with the system: - -![potential AAPS connectivity setup with no followers](./images/intro03.png) - -**Figure 4 (below)** shows the full potential of the **AAPS** system for a user who has followers and requires a monitor and send adjust the system remotely (like a child with T1D): - -![potential AAPS connectivity setup with followers](./images/intro04.png) - -## Q: How does AAPS get continually developed and improved? - -Most **AAPS** users use the fully tested **master** version of AAPS, which has been tested for bugs and problems, before being released to the community. Behind the scenes, the developers try out new improvements, and test these out in “developer” (**dev**) versions of **AAPS** with a user community who are happy to do bug updates at short notice. If the improvements work well, they are then released as a new “master” version of **AAPS**. Any new master release is announced on the Facebook group, so that the mainstream **AAPS** users can read about and update to the new master version. - -Some experienced and confident **AAPS ** users conduct experiments with emerging technologies and with dev versions of the **AAPS** app, which can be interesting for the less adventurous users to read about, without having to do it themselves! People tend to share these experiments on the Facebook group too. - -You can read more about some of these experiments and discussion on emerging tech here: - -[https://www.diabettech.com/](https://www.diabettech.com/) - -[https://bionicwookie.com/](https://bionicwookie.com/) - -## Q: Who can benefit? - -| User Type | -| ------------------------------------------- | -| ✔️ type 1 diabetic | -| ✔️ caregiver or parent of a type 1 diabetic | -| ✔️ blind users type 1 diabetic | -| ✔️ *clincians and healthcare professionals | - -The above table assumes that the user has access to both continuous gluocse monitor and insulin pump. - -*All data from **AAPS** can be made available to healthcare professionals via data sharing platforms, including NightScout that provides logging and real time monitoring of CGM data, insulin delivery, carbohydrate entries, predictions and settings. Nightscout records include daily and weekly reports which can aid healthcare professionals' discussions with type 1 patients with more accurate data on glycemic control and any behavioural considerations. - -## Q: What benefits can I get? - -With investment of your time, **AAPS** can potentially lead to: - -- alleviating the stress and burden of managing type 1 diabetes; - -- reducing the multitude of mundane decisions that arise from type 1 diabetes; - -- the provision of personalised and dynamic insulin dosing based on real-time data which can cut down the need for hypo treatments and reduce hyperglycemia episodes; - -- an increased knowledge of insulin management and confidence to better fine tune your settings; - -- the ability to create automatic settings (**automations**) that are tailored to fit in with your lifestyle; - -- improved sleep quality and overall reduction in the frequency of nighttime interventions; - -- remote monitoring and administration of insulin delivery for caregivers of type 1 diabetics; and - -- streamlining of all your portable diabetic equipment (continuous glucose monitor and insulin portable devices) by replacing them with an android phone controlled by **AAPS**. - - -Ultimately,**AAPS** can empower individuals to better manage their diabetes resulting in stable blood sugars and improved long term health outcomes. - ---- - -## AAPS First Steps - -Welcome. This is an introduction to aid beginners getting started with **AAPS** (or commonly referred to as "looping"). - -## Safety - -“_With great powers comes great responsibilities…_” - -**AAPS** is designed with an extensive set of safety features with limits imposed and gradually removed with completion of the **objectives **(predominately made up of multiple choice questions). An **AAPS** feature will be unlocked as the Objectives are successfully completed. This process will gradually allow the user to migrate from Open Loop to Closed Loop. - -This has been done to achieve the best possible experience with **AAPS** in order to prevent common mistakes that new users tend to make when starting to loop. The safety parameters have been built upon typical errors and general trends **AAPS** developers have observed with new users. Mistakes can happen because the beginner is inexperienced and too eager to get started with AAPS or has overlooked the required materials. Do not worry, we have all been there! - -## Key Principles - -The key principles and concepts of looping must be understood by the user before using **AAPS**. This is achieved by investing your personal time into reading the **AAPS** documentation, and completing the Objectives which is aimed to provide you with a solid platform for safe and effective use of **AAPS**. The volume of **AAPS** documentation may seem overwhelming at first but be patient and trust the process - with the proper approach, you'll get there! The overall process will depend upon the beginner’s progress and completion of objectives can typically take between 6 to 9 weeks . - -## Plan for hiccups - -At the preliminary stages of **AAPS**, you should expect to experience some hiccups whilst trying to fine tune your settings. **AAPS**’ glitches cannot be flushed out until the system is used in everyday life. Please plan accordingly and allow a sensible amount of time to troubleshoot and resolve such issues. - -## Flexibility/Adaptability - -Success with **AAPS** requires a proactive approach, a willingness to reflect on the BG data and flexibility to make the necessary adjustments to **AAPS** in order to improve your outcomes. Just as it is nearly impossible to learn to play a sport by reading about the rules alone, the same can be said of **AAPS**. - -## Technology compatibility - -There are limitations with **AAPS** as it is accessible for only certain types of insulin pumps or CGMs, and some technology may not be available for use in various countries. In order to avoid any disappointment or frustrations, please read please read Component Set Up (Section INSERT). - -## App Build Time - -The time to build the **AAPS**(under Section INSERT) depends on your level of expertise and technical ability. Typically for inexperienced users, it can take up to half a day or a full day (with help from the community) in order to build the **AAPS**. The process will significantly speed up as you become more experienced at building the **AAPS**. To aid the build process there are sections dedicated for: -- list of questions and answers for frequent errors that are likely to occur under FAQs (Section K); -- “How to install AAPS? (Section INSERT) which includes Troubleshooting subsection. - -## Keystore & configurations settings a export file - -A “keystore” is a password encrypted file unique to your own copy of **AAPS**. Your android phone uses it to ensure that nobody else can upgrade your own copy without the keystore. In short, as part of the **AAPS** build, you should: - -- save the your keystore file (.jks file used to sign your app) in a safe place; -- keep a note of your password for your keystore file. - -By doing the above, this will ensure that you can use that exact same keystore file each time an updated version of **AAPS** is created. On average, there will be 2-3 AAPS updates required each year. - -In addition, **AAPS** provides the ability to export all your configuration settings. This ensures that you can safely recover your system while changing phones, upgrading/reinstalling the application with minimum disruption. - -## Troubleshootng - -Please feel free to reach out to the AAPS community if there is anything you feel unsure about - there is no such thing as a silly question! All users with various levels of experience are encouraged to ask questions as necessary. Response times to questions are usually quick, typically only a few hours due to the volume of **AAPS** users. - -a) check the documentation; b) ask AAPS facebook group (https://www.facebook.com/groups/AndroidAPSUsers); and c) ask our discord channel. - -## Section overview - -AAPS documentation is made up of the following Sections: - -[INSERT ONCE SECTIONS /SUB SECTIONS AGREED] ---- diff --git a/docs/CROWDIN/pl/maintaining.md b/docs/CROWDIN/pl/maintaining.md deleted file mode 100644 index 98164a09e49b..000000000000 --- a/docs/CROWDIN/pl/maintaining.md +++ /dev/null @@ -1,28 +0,0 @@ -# Dummy - -## This is a dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - - -## This is another dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - - -## This is another another dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - diff --git a/docs/CROWDIN/pl/optimizing.md b/docs/CROWDIN/pl/optimizing.md deleted file mode 100644 index 98164a09e49b..000000000000 --- a/docs/CROWDIN/pl/optimizing.md +++ /dev/null @@ -1,28 +0,0 @@ -# Dummy - -## This is a dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - - -## This is another dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - - -## This is another another dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - diff --git a/docs/CROWDIN/pl/prepairing.md b/docs/CROWDIN/pl/prepairing.md deleted file mode 100644 index 00a6038c1737..000000000000 --- a/docs/CROWDIN/pl/prepairing.md +++ /dev/null @@ -1,145 +0,0 @@ -# Prepairing - -## Guide to the Android APS doc - -### First Steps -Welcome. This is an introduction to aid beginners to the concept of Do-It-Yourself-APS (Android-Artificial-Pancreas-Systems “AAPS”) is commonly referred to as ‘looping’.. - -#### Safetys -“With great powers come great responsibilities…” - -AAPS is designed with an extensive set of safety features with limits imposed and gradually removed with completion of the [Objectives](https://androidaps.readthedocs.io/en/latest/Usage/Objectives.html) (predominately made up of multiple choice questions). An AAPS feature will be unlocked as the Objectives are successfully completed. This process will gradually allow the user to migrate from Open Loop to Closed Loop. - -This has been done to achieve the best possible experience with AAPS by preventing common mistakes new users tend to make when starting to loop. The safety parameters have been built upon typical errors and general trends AAPS developers have observed with new users. Mistakes can happen because the beginner is inexperienced and too eager to get started with AAPS or has overlooked the required materials. Do not worry, we have all been there! - -#### Key Principles - -The key principles and concepts of looping must be understood by the user before using AAPS. This is achieved by investing your personal time into reading the AAPS documentation, and completing the [Objectives](https://androidaps.readthedocs.io/en/latest/Usage/Objectives.html) which is aimed to provide you with a solid platform for safe and effective use of AAPS. The volume of AAPS documentation may seem overwhelming at first but be patient and trust the process - with the proper approach, you'll get there! The overall process will depend upon the beginner’s progress and completion of objectives which typically take between 6 to 9 weeks . - -#### Plan for hiccups - -At the preliminary stages of AAPS, you should expect to experience some hiccups whilst trying to fine tune your settings. AAPS’ glitches cannot be flushed out until the system is used in everyday life. Please plan accordingly and allow a sensible amount of time to troubleshoot and resolve such issues. - -#### Flexibility/Adaptability - -Success with AAPS requires a proactive approach, a willingness to reflect on the BG data and flexibility to make the necessary adjustments to AAPS in order to improve your outcomes. Just as it is nearly impossible to learn to play a sport by reading about the rules alone, the same can be said of AAPS. - -#### Technology compatibility -There are limitations with AAPS as it is accessible for only certain types of insulin pumps or CGMs, and some technology may not be available for use in various countries. In order to avoid any disappointment or frustrations, please read [Component Set Up (Section E).](https://androidaps.readthedocs.io/en/latest/Configuration/BG-Source.html) - -#### App Build time -The time to build the AAPS (under Section D) depends on your level of expertise and technical ability. Typically for inexperienced users, it can take up to half a day or a full day (with help from the community) in order to build the AAPS. The process will significantly speed up as you become more experienced at building the AAPS.  - -To aid the build process there are sections dedicated for: - -- list of questions and answers for frequent errors that are likely to occur under [FAQs (Section](https://androidaps.readthedocs.io/en/latest/Getting-Started/FAQ.html) K); - -- “[How to install AAPS](https://androidaps.readthedocs.io/en/latest/Installing-AndroidAPS/Building-APK.html)? (Section D) which includes [Troubleshooting](https://androidaps.readthedocs.io/en/latest/Usage/troubleshooting.html) subsection. - - -#### Keystore & configuration settings export  file - -A “keystore” is a password encrypted file unique to your own copy of AAPS. Your android phone uses it to ensure that nobody else can upgrade your own copy without the keystore.In short, as part of the AAPS build, you should: - -1. save the your keystore file (.jks file used to sign your app) in a safe place; - -2. keep a note of your password for your keystore file. - - -By doing the above, this will ensure that you can use that exact same keystore file each time an updated version of AAPS is created. On average, there will be 2-3 updates to the AAPS required each year. In addition, AAPS provides the ability to [export all your configuration settings](https://androidaps.readthedocs.io/en/latest/Usage/ExportImportSettings.html). This ensures that you can safely recover your system while changing phones, upgrading/reinstalling the application with minimum disruption.  - -#### Rozwiązywanie problemów - -Please feel free to reach out to the AAPS community if there is anything you feel unsure about - there is no such thing as a silly question!  All users with various levels of experience are encouraged to ask questions as necessary. Response times to questions are usually quick, typically only a few hours due to the volume of AAPS users.  - -##### [check the documentation](https://androidaps.readthedocs.io/en/latest/index.html) - -##### [ask our facebook group](https://www.facebook.com/groups/AndroidAPSUsers/) - -##### [ask our discord channel](https://discord.com/channels/629952586895851530/629954570394533889) - -#### Section overview - -AAPS documentation is made up of the following Sections: - -##### [Getting started](https://androidaps.readthedocs.io/en/latest/Getting-Started/Safety-first.html) - -This is a must read to understand the general concept of what an artificial pancreas system is designed to do. - -##### [What do I need?](https://androidaps.readthedocs.io/en/latest/Module/module.html) - -This explains AAPS’ compatibility with CGMs (Continuous Glucose Monitors) and insulin pumps. It also provides a guide on the correct assembly of an AAPS system to ensure that it functions correctly in everyday life. - -##### How to install AAPS - -This section is the manual for building the AAPS. Strict adherence to the step-by-step instructions are required in order to successfully build the AAPS. Please take your time. - -##### [Component Setup](https://androidaps.readthedocs.io/en/latest/Configuration/BG-Source.html) - -This explains how to properly integrate each of the various different separate component parts into AAPS, as well as how to set them up to work as seamlessly as possible together. All components are listed under the separate sections: CGM/FGM, xDrip Settings, Pumps, Phones, Nightscout setup, and Smartwatches. The sensor (BG) values and control of the insulin pump are particularly important information to understand. - -##### Configuration - -This explains how to set and configure your ‘Profile’, ‘Insulin’, ‘BG Source’, ‘Pump’, ‘Sensitivity Detection’, ‘APS’, ‘Loop’, ‘Treatments’. - -##### AAPS Usage - -This section provides a breakdown of the features provided by AAPS. - -##### [General Hints](https://androidaps.readthedocs.io/en/latest/Usage/Timezone-traveling.html) - -Useful tricks on how to tackle looping issues such as time zones, and daylight saving (i.e. Spring Forward/ - Fall Back). - -##### [AAPS](https://androidaps.readthedocs.io/en/latest/Getting-Started/Screenshots.html) for Children - -This is designed for parents or caregivers who want to build an AAPS for their child. It also explains the extra features necessary in order to support and safely control your child’s AAPS remotely.

The concepts in this section should be fully understood in order to competently use this feature. - -##### Rozwiązywanie problemów - -This section contains links to help solve issues when building or using AAPS. - -##### FAQ - -This section addresses specific questions which tend to come up when building or using AAPS. - -##### [Słowniczek pojęć](https://androidaps.readthedocs.io/en/latest/Getting-Started/Glossary.html) - -This contains a list of the acronyms (or short-term names) or defined terms developed specifically for AAP (for instance, the terms ‘ISF’ or ‘TT’ have special meanings in AAPS). - -##### [Where to go for help](https://androidaps.readthedocs.io/en/latest/Where-To-Go-For-Help/Background-reading.html)? - -This section is aimed to provide new users with links on resources in order to get help including accessing community support made up of both new and experienced users who can clarify questions, and resolve the usual pitfalls that come with AAPS. - -##### For Clinicians - -This is a section for the clinicians who have expressed interest in open source artificial pancreas technology such as AAPS, or for patients who want to share such information with their clinicians. | - -## what are we going to build? - -### An Android Phone Application - -At the core, AAPS is an android application running from a phone. You are going to build it from scratch by installing tools to download the sourcecode and build the actual application. - -### A reporting server NightScout (or Tidepool) - -In order to fully use AAPS properly you will want to setup a nightscout server. It is used to collect data from AAPS over time and possibly communicate to the application. It is required for parents who want to oversee their children AAPS sessions. It is also key to share data between clinicians and patients to perform analysis over time. - -## How long will it take? - -## Who might AAPS not be suitable for? - -## Where can I get help? - -## Requirements - -### medical - -### technical - -### personal - -### CGMs - -### Insulin Pump - -### Reporting (NS, Tidepool) \ No newline at end of file diff --git a/docs/CROWDIN/pt/Configuration/Dexcom.md b/docs/CROWDIN/pt/Configuration/Dexcom.md deleted file mode 100644 index cb267e23c069..000000000000 --- a/docs/CROWDIN/pt/Configuration/Dexcom.md +++ /dev/null @@ -1,32 +0,0 @@ -# Dexcom G6 - -## Basics first - -* Follow [general CGM hygiene recommendations](../Configuration/BG-Source#cgm-hygiene) -* [Special recommendations for Dexcom G6 and DIY systems](../Configuration/BG-Source#dexcom-g6-diy-systems) *For G6 transmitters manufactured after fall/end of 2018 please make sure to use one of the [latest nightly built xDrip+ versions](https://github.com/NightscoutFoundation/xDrip/releases). Those transmitters have a new firmware and latest stable version of xDrip+ (2019/01/10) cannot deal with it. - -## Setting sensor - -When setting sensor, it is recommended not to press the inserter too firmly in order to avoid bleeding. The sensor thread should not come into contact with blood. - -After setting the sensor, the transmitter can be clicked into the sensor holder. Caution! First click in the square side and then press down the round side. - -## Troubleshooting - -### Connection problems - -Bluetooth connection may be disturbed by other nearby Bluetooth devices such as blood glucose meters, headsets, tablets or kitchen devices such as microwave ovens or ceramic hobs. In this case xdrip does not display any BG values. When bluetooth connection is reestablished the data is backfilled. - -### Sensor Errors - -If recurring sensor errors occur try selecting a different body site to set your sensor. The sensor thread should not come into contact with blood. - -Often a "Sensor Error" can be corrected by immediate drinking and massage around the sensor! - -### Jumpy values - -You might try to change settings for noise blocking in xdrip (Settings - Inter-App Settings - Noise Blocking) i.e. "Block Very High noise and worse". See also [Smoothing BG data](../Usage/Smoothing-Blood-Glucose-Data-in-xDrip.md). - -### New transmitter with running sensor - -If you happen to change transmitter during a running sensor session you might try to remove the transmitter without damaging the sensor mount. A video can be found at . \ No newline at end of file diff --git a/docs/CROWDIN/pt/Configuration/EOFLOW.md b/docs/CROWDIN/pt/Configuration/EOFLOW.md deleted file mode 100644 index 71d75de86ff3..000000000000 --- a/docs/CROWDIN/pt/Configuration/EOFLOW.md +++ /dev/null @@ -1,155 +0,0 @@ -# EOPatch2 Instruction Manual - -The patch requires the use of rapid-acting U-100 type insulin, such as NovoRapid or Humalog. Use a rapid-acting insulin that is suitable for you according to your doctor’s prescription and inject the prescribed dosage. - -The smallest injectable dose of insulin when using the patch is 0.05 U. The Profile BAS should therefore be set at a minimum value of 0.05 U/hr or more and an interval of 0.05 U/hr, as otherwise there may be an error between the estimated total infusion amount in the Profile and the actual infusion amount in the patch. Likewise, the bolus must also be set and infused with a minimum infusion volume of 0.05 U. - -## Pump Setup -1. On the AndroidAPS home screen, click the hamburger menu in the upper left corner and go to Config Builder. -1. Select 'EOPatch2' in the Pump section. -1. Press the Back key to return to the home screen. - -![Bild1](../../images/EOPatch/Bild1.png) ![Bild2](../../images/EOPatch/Bild2.png) - -## Configurações -Select EOPATCH2 at the top of the home screen to go to the EOPATCH2 tab. - -Select the EOPatch2 Preferences menu by clicking the three dots in the upper right corner. - -The EOPatch2 Preferences menu offers a menu to set 3 types of notifications. - -### Low reservoir Alerts -A warning appears when the amount of insulin remaining in the reservoir reaches the set value or less while using the patch. It can be set from 10 to 50U in 5U increments. - -### Patch expiration Reminder -This is a reminder to notify you of the time remaining before the current patch expires. It can be set from 1 to 24 hours in 1 hour increments. The initial setting value is 4 hours. - -### Patch buzzer Reminder -This is a reminder function for injections other than basal injection. If you are using an (extended) bolus injection or a temporary basal injection, the patch will make a buzzer sound when the injection starts and when the injection is complete. The initial setting value is Off. - -![Bild3](../../images/EOPatch/Bild3.png) - -## Connecting the Patch - -### Move to patch connection screen - -Select EOPATCH2 at the top of the home screen and click the ACTIVATE PATCH button at the bottom left. - -![Bild4](../../images/EOPatch/Bild4.png) - -### Connecting the patch -Insert the syringe needle into the insulin inlet on the patch and then slowly push the piston to inject the insulin. When insulin is filled with more than 80U, the patch makes a booting sound (1 buzzer) and boots. After confirming the buzzer sound, click the START PAIRING button on the screen. - -[Warning] - -- Do not turn the needle action lever until instructed. It can cause serious problems during injection or safety checks otherwise. -- The amount of insulin that can be injected into the patch is 80~200U. If you inject less than 80U into the patch initially, the patch will not work. -- Take the insulin to be put into the patch from the refrigerator and leave it at room temperature for 15 to 30 minutes beforehand. The temperature of the insulin to be injected must be at least 10°C. - -![Bild5](../../images/EOPatch/Bild5.png) - -### patch pairing -The Patch pairing screen will be displayed, and pairing will be attempted automatically. If communication is successful, the Bluetooth pairing request notification appears. Click OK and when the Bluetooth pairing request notification appears a second time with the authentication code, select OK again. - -[Warning] - -- For pairing, the patch and the smartphone must be located within 30 cm of each other. -- After the patch booting is completed, the patch will beep every 3 minutes until the pairing is complete. -- After booting the patch, the patch application must be completed via the app within 60 minutes. If the application cannot be completed within 60 minutes, the patch should be discarded. - -![Bild6](../../images/EOPatch/Bild6.png) ![Bild7](../../images/EOPatch/Bild7.png) ![Bild8](../../images/EOPatch/Bild8.png) - - -### patch preparation -After removing the adhesive tape of the patch, check if the needle is sticking out. If there are no problems with the patch, click NEXT. - -![Bild9](../../images/EOPatch/Bild9.png) - -### Patch attachment -Insulin should be injected in a spot with subcutaneous fat but few nerves or blood vessels, so it is recommended to use the abdomen, arm, or thigh for the patch attachment site. Choose a patch attachment site and apply the patch after disinfecting the location. - -[Warning] - -- Make sure to straighten the side of the patch tape attached to the body evenly, so that the patch adheres completely to the skin. -- If the patch does not stick completely, air may enter between the patch and the skin, which can weaken the adhesive strength and waterproof effect of the patch. - -![Bild10](../../images/EOPatch/Bild10.png) - -### Safety Check -When patching is complete, touch Start Safety Check. When the safety check is completed, the patch will beep once. - -[Warning] - -- For safe use, do not turn the needle action lever until the safety check has been completed. - -![Bild11](../../images/EOPatch/Bild11.png) ![Bild12](../../images/EOPatch/Bild12.png) - - -### Inserting the needle -The needle is inserted by holding around the patch and turning the needle action lever more than 100° in the upward direction of the lever. There is a buzzer sound when the needle is inserted correctly. Turn the needle action lever further clockwise to release the lever. Click NEXT. - -[Caution] - -- If you go to the next step without the buzzer sounding, a needle insertion error warning will appear. - -## Discarding the patch -Patches must be replaced in the case of low insulin levels, usage expiration, and defects. The recommended usage period for each patch is 84 hours after booting the patch. - -### Discarding the patch -Select EOPATCH2 at the top of the home screen and click the DISCARD/CHANGE PATCH button at the bottom. On the next screen, click the DISCARD PATCH button. A dialog box appears to confirm once more and if you select the DISCARD PATCH button, the disposal is completed. - -![Bild13](../../images/EOPatch/Bild13.png) ![Bild14](../../images/EOPatch/Bild14.png) ![Bild15](../../images/EOPatch/Bild15.png) ![Bild16](../../images/EOPatch/Bild16.png) - -## Suspending and Resuming Insulin Delivery -Suspending insulin delivery also cancels both extended bolus and temporary basal. When resuming insulin delivery, the canceled extended bolus and temporary basal will not be resumed. And when insulin delivery is suspended, the patch will give a sound every 15 minutes. - -### Suspending insulin delivery -Select EOPATCH2 at the top of the home screen and click the SUSPEND button at the bottom right. When you select CONFIRM in the confirmation box, a time selection box appears. If you select the CONFIRM button after selecting the time, the insulin delivery will be suspended for the set amount of time. - -![Bild17](../../images/EOPatch/Bild17.png) ![Bild18](../../images/EOPatch/Bild18.png) ![Bild19](../../images/EOPatch/Bild19.png) - - -### Resuming insulin delivery -Select EOPATCH2 at the top of the home screen and click the RESUME button at the bottom right. Insulin delivery will resume by selecting CONFIRM in the confirmation dialog box. - -![Bild20](../../images/EOPatch/Bild20.png) ![Bild21](../../images/EOPatch/Bild21.png) - -## Alarms/Warnings - -### Alarm - -Alarms are issued for emergency situations of the highest priority and require immediate action. The alarm signal does not disappear or time out until it is acknowledged. An alarm occurs when there is a problem with the patch being used, so there may be cases where the patch in use needs to be discarded and replaced with a new patch. The warning is displayed as a dialog box and switching to another screen is not possible until processing is completed. - -![Bild22](../../images/EOPatch/Bild22.png) ![Bild23](../../images/EOPatch/Bild23.png) - -The different types of alarms are explained below. - -| Alarms | Explanation | -| -------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| Empty reservoir | Occurs when the patch’s reservoir runs out of insulin. | -| Patch expired | Occurs when the patch usage time has expired, and no further insulin injections are possible. | -| Occlusion | Occurs when it appears that the patch's insulin inlet is clogged. | -| Power on self-test failure | Occurs when the patch finds an unexpected error during the post-boot self-test process. | -| Inappropriate temperature | Occurs when the patch is outside the normal operating temperature range during patch application and use. To deal with this alarm, move the patch to an appropriate operating temperature (4.4 to 37°C) condition. | -| Needle insertion Error | Occurs when needle insertion is not normal during the patch application process. Check that the needle insertion edge of the patch and the needle activation button are in a straight line. | -| Patch battery Error | Occurs just before the patch’s internal battery runs out and powers off. | -| Patch activation Error | Occurs when the app fails to complete the patching process within 60 minutes after the patch is booted. | -| Patch Error | Occurs when the patch encounters an unexpected error while applying and using the patch. | - -### Warning - -A warning occurs in a medium or low-priority situation. When a warning occurs, it is displayed as a notification in the Overview screen. - -![Bild24](../../images/EOPatch/Bild24.png) - -The different types of warnings are explained below. - -| Warnings | Explanation | -| ---------------------------- | ------------------------------------------------------------------------------------------------------------------------------------- | -| End of insulin suspend | Occurs when the time set by the user has elapsed after the insulin infusion suspension has been completed. | -| Low reservoir | Occurs when the remaining amount of insulin in the patch is below the set amount. | -| Patch operating life expired | Occurs when the patch usage period is over. | -| Patch will expire soon | Occurs 1 hour before the patch must be discarded. | -| Incomplete Patch activation | Occurs when more than 3 minutes have elapsed due to an interruption during patch application in the stage after pairing is completed. | -| Patch battery low | Occurs when the patch's battery is low. | - diff --git a/docs/CROWDIN/pt/Configuration/Hardware/index.md b/docs/CROWDIN/pt/Configuration/Hardware/index.md deleted file mode 100644 index 4b0d8059e608..000000000000 --- a/docs/CROWDIN/pt/Configuration/Hardware/index.md +++ /dev/null @@ -1,27 +0,0 @@ -# Hardware-Configuration - -## Configuração - -## Fonte de BG - -- [BG Source](../BG-Source.md) -- [xDrip+ Settings](../xDrip.md) -- [Dexcom G6 hints](../Dexcom.md) -- [Smoothing blood glucose data](../../Usage/Smoothing-Blood-Glucose-Data-in-xDrip.md) - -## Pumps - -- [Dana-R pump](../DanaR-Insulin-Pump.md) -- [Dana-RS pump](../DanaRS-Insulin-Pump.md) -- [Accu-Chek Combo pump](../Accu-Chek-Combo-Pump.md) -- [Accu-Chek Insight pump](../Accu-Chek-Insight-Pump.md) -- [Medtronic pump](../MedtronicPump.md) - -## Telefones - -- [Jelly Pro Settings](../../Usage/jelly.md) -- [Huawei Settings](../../Usage/huawei.md) - -## Smartwatch - -- [Watchfaces](../Watchfaces.md) diff --git a/docs/CROWDIN/pt/Getting-Started/ClosedLoop.md b/docs/CROWDIN/pt/Getting-Started/ClosedLoop.md deleted file mode 100644 index 5903de6b1526..000000000000 --- a/docs/CROWDIN/pt/Getting-Started/ClosedLoop.md +++ /dev/null @@ -1,55 +0,0 @@ -# O que é um Sistema de Loop Fechado? - -![AAPS é como um piloto automático](../images/autopilot.png) - -Um sistema artificial de pâncreas em loop fechado combina diferentes componentes para facilitar o controlo da diabetes por si. In her great book [Automated Insulin Delivery](https://www.artificialpancreasbook.com/) Dana M. Lewis, one of the founders of the open source closed loop movement, calls it an ["autopilot for your diabetes"](https://www.artificialpancreasbook.com/3.-getting-started-with-your-aps). Mas o que é que isso significa? - -**Autopilot in an aircraft** - -O piloto automático não faz o trabalho completo e com isso não dá a possibilidade ao piloto de dormir durante todo o voo. Facilita o trabalho dos pilotos. Isso os livra do fardo de monitorizar permanentemente a aeronave e a altitude do voo. Isto permite que o piloto se concentre em monitorizar o espaço aéreo e controlar as funções do piloto automático. - -O piloto automático recebe sinais de vários sensores, um computador e avalia-os juntamente com as especificações do piloto e, faz então os ajustes necessários. O piloto não irá mais preocupar-se com os constantes ajustes. - -**Closed Loop System** - -O mesmo se aplica a um sistema de pâncreas artificial de loop fechado. Não faz o trabalho todo, você ainda terá de cuidar da sua diabetes. Um sistema de loop fechado combina os dados do sensor de um MCG/MFG com as especificações do seu tratamento da diabetes, tais como taxa basal, fator de sensibilidade à insulina e rácio de hidratos de carbono. A partir desses dados ele calcula sugestões de tratamento e implementa esses pequenos ajustes permanentes com a finalidade de manter a sua diabetes dentro do intervalo alvo e aliviá-lo deste trabalho. Isto deixa mais tempo para a sua vida "além" da diabetes. - -Assim como não quer entrar num avião em que apenas o piloto automático voa sem supervisão humana, um sistema de loop fechado ajuda-o com a sua gestão da diabetes, mas irá sempre precisar do seu apoio! **Even with a closed loop you can't just forget your diabetes!** - -Da mesma forma que o piloto automático depende dos valores do sensor, bem como das especificações do piloto , um sistema de loop fechado precisa da "entrada" dos dados certos, tais como: taxas de basal, FSI e rácios de hidratos de carbono para o apoiar com sucesso. - -## Sistemas de Código Aberto de Pâncreas Artificial de Loop Fechado - -Neste momento existem três grandes sistemas código aberto de loop fechado disponíveis: - -### AndroidAPS (AAPS) - -AAPS is described in detail in [this documentation](./WhatisAndroidAPS.html). Ele usa um smartphone Android para o cálculo e controlo da sua bomba de insulina. It is in strong collaboration with OpenAPS (i.e. they share algorithms). - -Compatible [pumps](../Hardware/pumps.md) are: - -- [DanaR](../Configuration/DanaR-Insulin-Pump.md) / [DanaRS & Dana-i](../Configuration/DanaRS-Insulin-Pump.html) -- [Accu-Chek Combo](../Configuration/Accu-Chek-Combo-Pump.md) -- [Accu-Chek Insight](../Configuration/Accu-Chek-Insight-Pump.md) -- [Diaconn G8](../Configuration/DiaconnG8.md) -- [Omnipod DASH](../Configuration/OmnipodDASH.md) -- [Omnipod Eros](../Configuration/OmnipodEros.md) -- some old [Medtronic pumps](../Configuration/MedtronicPump.md) - -### OpenAPS - -[OpenAPS](https://openaps.readthedocs.io) was the first Open Source Closed Loop System. Ele usa um pequeno computador como Raspberry Pi ou Intel Edison. - -As bombas compatíveis são: - -- some old Medtronic pumps - -### Loop para iOS - -[Loop for iOS](https://loopkit.github.io/loopdocs/) is the Open Source Closed Loop System to be used with Apple iPhones. - -As bombas compatíveis são: - -- Omnipod DASH -- Omnipod Eros -- some old Medtronic pumps diff --git a/docs/CROWDIN/pt/Getting-Started/GlossaryTest.md b/docs/CROWDIN/pt/Getting-Started/GlossaryTest.md deleted file mode 100644 index f67e1194aba1..000000000000 --- a/docs/CROWDIN/pt/Getting-Started/GlossaryTest.md +++ /dev/null @@ -1,391 +0,0 @@ -# Glossário - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
TermDescriptionsee alsomore details @
AAPSAndroidAPS - sistema pâncreas artificial  
AMAadvanced meal assist - advanced algorithm to handle carbsMA / SMBWiki - AMA
Android autodisplay AAPS notifications on your car's compatible in-dash information and entertainment head unit Wiki - android auto
APKsoftware installation file (Android application package) Wiki - Criando APK
Autosenscalculation of sensitivity to insulin as a result of exercise, hormones etc. DIABETTECH - Autosens
Azurecloud computing platform to host Nightscout dataHeroku / NightscoutAzure
BATstatus light low battery on homescreenCAN / RES / SENPreferences
Screenshots
GLICblood glucose  
BGIblood glucose interaction -degree to which BG 'should' be rising or falling based on insulin activity alone  
Origem da GlicemiaWhere do your glucose values come from?CGM / MGFWiki - Fonte Glic
Blukon Nightreaderbluetooth transmitter to use Freestyle Libre as CGMBlueReader / MiaoMiaoAmbrosia Blukon Nightreader
BRtaxa basal  
CAGEcanula age - displayed in Nightscout if information was entered in actions tab / menu tab or through AAPS actions tab 'prime'Nightscout 
CANstatus light overdue canula change on homescreenBAT / RES / SENPreferences
Screenshots
CGMcontinuous glucose monitor  
Closed Loopclosed-loop systems make automatic adjustments to basal delivery, without needing user-approval, based on an algorithmOpen loopWiki closed loop
COBcarbs on board  
DIAduration of insulin action Wiki insulin types
DIABETTECH - DIA
DSTdaylight savings time Wiki DST
eCarbs"extended carbs" - carbs split up over serveral hours (i.e. lot of fat/protein)
extended boluses you might know from regular pump therapy do not make much sense when looping		SMBWiki - eCarbs
eCarbs use case
FGMflash glucose monitor (Freestyle Libre) Wiki - Fonte Glic
gitversion-control system for tracking changes in computer files and coordinating work on those files
-> neccessary for APK updates		 Wiki - update APK
Githubweb-based hosting service for version control using Git
-> storage of source code		 Github AndroidAPS
Glimpapp to collect values from Freestyle Libre Nightscout with Glimp
Herokucloud computing platform to host Nightscout dataAzure / NightscoutHeroku
IC (or I:C)insulin to carb ratio (How many carbs are covered by one unit of insulin?)  
IOBinsulin on board - insulin active in your body  
ISFinsulin sensitivity factor - the expected decrease in BG as a result of one unit of insulin  
LGSLow Glucose Suspend
AAPS will reduce basal if blood glucose is dropping. But if blood glucose is rising then it will only increase basal if the IOB is negative (from a previous LGS), otherwise basal rates will remain the same as your selected profile. You may temporarily experience spikes following treated hypos without the ability to increase basal on the rebound.		objective 6 
LineageOSfree and open-source operating system for smartphones etc.
alternative OS for smartphones not running Android 8.1 (Oreo)
(when using Accu-Chek Combo)		 Wiki - Combo pump
Log filesrecord of all AAPS actions (useful for trubbleshooting and debugging) Wiki - log files
maxIOBsafety feature - maximum total IOB AAPS can't go over Wiki - maxIOB
Wiki - SMB
MiaoMiaobluetooth transmitter to use Freestyle Libre as CGMBlueReader / Blukon NightreaderMiaoMiao
min_5m_carbimpactsaftey feature - default carb decay at times when carb absorption can’t be dynamically worked out based on your bloods reactions Wiki - config builder
Nightscoutopen source project to access and report CGM dataNightscout ReporterNightscout
NS Clientpart of AAPS to connect to your Nightscout site Wiki - NS Client
Nightscout ReporterTool from fellow looper to generate PDFs reports from Nightscout dataNightscoutNightscout Reporter
NS Reporter @ Facebook
Objectivoslearning program within AAPS guiding you step by step from open to closed loop Wiki - objectives
OpenAPSopen artificial pancreas system
APS run on small computers (i.e. Raspberry Pie)
AAPS uses some of the OpenAPS features		 OpenAPS docs
Open Loopsystem will suggest recommended adjustments which have to be performed manually on the pumpClosed LoopWiki - config builder
Oref0 / Oref1sensitivity detection
"reference design implementation version 0/1" - the key algorithm behind OpenAPS		 Wiki - sensitivity detection
Peak timetime of maximum effect of insulin given Wiki - config builder
PHpump history (entry in treatments tab) Screenshots
Previsãopreditions for BG in the future based on different calculations Wiki - predition lines
Perfilbasic treatment settings (basal rate, DIA, IC, ISF, BG target)
can be defined locally or through Nightscout		NightscoutWiki - profile
Troca de Perfil(temporary) change of profile used or percentual increase/decrease Wiki - profile switch
RESstatus light overdue reservoir change on homescreenBAT / CAN / SENPreferences
Screenshots
RileyLinkopen source hardware device to bridge Bluetooth Low Energy (BLE) to 916MHz wireless communication (used for old Medtronic pumps)OpenAPS 
SAGEsensor age - displayed in Nightscout if information was entered in the actions tab / menuNightscout 
SENstatus light sensor change on homescreenBAT / CAN / RESPreferences
Screenshots
Sensivity detectioncalculation of sensitivity to insulin as a result of exercise, hormones etc. DIABETTECH - Autosens
Sensor noiseunstable CGM readings leading to "jumping" values Wiki - sensor noise
SMBsuper micro bolus
advanced feature for faster BG adjustment		UAMWiki - SMB
Super bolusshift of basal to bolus insulin for faster BG adjustment John Walsh - The Super Bolus
TBBtotal base basal (sum of basal rate within 24 hours)  
TBRtemporary basal rate  
TDDtotal daily dose (bolus + basal per day)  
TTtemporary target
temporary increase/decrease of BG target (range)		 Wiki - temp targets
UAMunannounced meals - detection of significant increase in glucose levels due to meals, adrenaline or other influences and attempt to adjust this with SMBSMBWiki - SMB
Virtual pumpoption to try AAPS functions or for PWD using a pump model with no AndroidAPS driver for loopingOpen Loop 
WallpaperAndroidAPS background imagesee phones page
xDrip / xDrip+open source software to read CGM systems xDrip+
xDrip
Zero-temptemporary basal rate with 0% (no basal insulin delivery)  
See also https://openaps.readthedocs.io/en/latest/docs/Resources/glossary.html
diff --git a/docs/CROWDIN/pt/Getting-Started/Safety-first.md b/docs/CROWDIN/pt/Getting-Started/Safety-first.md deleted file mode 100644 index 33d837dd2970..000000000000 --- a/docs/CROWDIN/pt/Getting-Started/Safety-first.md +++ /dev/null @@ -1,41 +0,0 @@ -# Segurança primeiro - -**When you decide to build your own artificial pancreas, it's always important to think about security and safety, and to understand the impact of all your actions** - -## Geral - -- AAPS is a just a tool to help you manage diabetes, it is not a fully automated system you can install and forget! -- Do not assume that AAPS will never make mistakes. Este dispositivo está a assumir o controlo da administração da sua insulina: observe-o constantemente, entenda como ele funciona e aprenda a interpretar as suas ações. -- Remember that, once paired, the phone can instruct the pump to do anything. Only use this phone for AAPS and, if being used by a child, essential communications. Não instale aplicações ou jogos desnecessários (!!!) o que pode introduzir malwares como trojans, vírus ou bots que podem interferir no seu sistema. -- Install all security updates provided by your phone manufacturer and Google. -- You might also need to change your diabetes habits as you change your therapy by using a closed loop system. Por exemplo some people report, they need less hypo treatments as AAPS has already reduced insulin. - -## Comunicador SMS - -- AAPS allows you to control a child's phone remotely via text message. Se os comandos por SMS estiverem ativos, lembre-se sempre de que o telemóvel configurado para estes comandos remotos pode ser roubado. Então, proteja-o sempre, pelo menos, através de um código PIN. -- AAPS will also inform you by text message if your remote commands, such as a bolus or a profile change, have been carried out. Ao configurar é aconselhável que as mensagens de confirmação sejam enviados para, pelo menos, dois números de telefone distintos, para o caso de um dos telefones ser roubado. - -(Safety-first-aaps-can-also-be-used-by-blind-people)= -## AAPS can also be used by blind people - -On Android devices TalkBack is part of the operating system. It is a program for screen orientation via voice output. With TalkBack you can operate your smartphone as well as AAPS blind. - -We users create the AAPS app ourselves with Android Studio. Many use Microsoft Windows for this purpose, where there is the Screenreader analogous to TalkBack. Since Android Studio is a Java application, the "Java Access Bridge" component must be enabled in the Control Panel. Otherwise, the screen reader of the PC will not speak in Android Studio. - -To do this, please proceed as follows: - -- Press WINDOWSTASTE and enter "Control Panel" in the search field, open with Enter. It opens: "All Control Panel Items". -- Press the letter C to get to "Center for Ease of Use", open with Enter. -- Then open "Use computer without a screen" with Enter. -- There, at the bottom, you will find the checkbox "Enable Java Access Bridge", select it. -- Done, just close the window! The screen reader should work now. - -```{note} -**IMPORTANT SAFETY NOTICE** - -The foundation of AAPS safety features discussed in this documentation is built on the safety features of the hardware used to build your system. It is critically important that you only use a tested, fully functioning FDA or CE approved insulin pump and CGM for closing an automated insulin dosing loop. Hardware or software modifications to these components can cause unexpected insulin dosing, causing significant risk to the user. If you find or get offered broken, modified or self-made insulin pumps or CGM receivers, *do not use* these for creating an AAPS system. - -Additionally, it is equally important to only use original supplies such as inserters, cannulas and insulin containers approved by the manufacturer for use with your pump or CGM. Using untested or modified supplies can cause CGM inaccuracy and insulin dosing errors. Insulin is highly dangerous when misdosed - please do not play with your life by hacking with your supplies. - -Por último, mas não menos importante, você não deve tomar inibidores SGLT-2 (gliflozins), pois eles reduzem incalculavelmente os níveis de açúcar no sangue. A combinação com um sistema que reduz as taxas basais a fim de aumentar a GLIC é especialmente perigosa já que devido ao gliflozin esse aumento na GLIC pode não acontecer e um estado perigoso de falta de insulina pode acontecer. -``` diff --git a/docs/CROWDIN/pt/Getting-Started/Sample-Setup.md b/docs/CROWDIN/pt/Getting-Started/Sample-Setup.md deleted file mode 100644 index 4f48ec78eb00..000000000000 --- a/docs/CROWDIN/pt/Getting-Started/Sample-Setup.md +++ /dev/null @@ -1,151 +0,0 @@ -# Sample setup: Samsung S7, Dana RS, Dexcom G6 and Sony Smartwatch - -![Configuração de Exemplo](../images/SampleSetup.png) - -## Descrição - -In this setup, the Samsung Galaxy S7 smartphone is used as control center of the loop. The slightly modified Dexcom App reads glucose values from the Dexcom G6 CGM. AndroidAPS is used to control the Dana RS insulin pump from Korean manufacturer SOOIL via bluetooth. Further devices are not required. - -As the Dexcom App only offers limited alarm options the open source app xDrip+ is used to define not only high and low alarms but also additional alarms according to individual requirements. - -Optionally an Android wear smartwatch can be used (in this sample setup the Sony Smartwatch 3 (SWR50)) to display glucose and AndroidAPS values on your wrist. The watch can even be used to control AndroidAPS (i.e. discreetly set a meal bolus). - -The system works offline. This means there is no need for a data connection from the smartphone to the Internet for operation. - -Nevertheless, the data is automatically uploaded to Nightscout "in the cloud" when a data connection is established. By doing so you can provide comprehensive reports for the doctor's visit or share the current values with family members at any time. It is also possible to send data to Nightscout only when using a (predefined) Wi-Fi connection in order to profit from the different Nightscout reports. - -## Required components - -1. Samsung Galaxy S7 - - * Alternatives: see [list of tested phones and watches](https://docs.google.com/spreadsheets/d/1gZAsN6f0gv6tkgy9EBsYl0BQNhna0RDqA9QGycAqCQc/edit) for AndroidAPS - -2. [DanaRS](http://www.sooil.com/eng/product/) - - * Alternatives: - * [Accu-Chek Combo](../Configuration/Accu-Chek-Combo-Pump.md) - * [Accu-Chek Insight](../Configuration/Accu-Chek-Insight-Pump.md) - * [DanaR](../Configuration/DanaR-Insulin-Pump.md) - * [Some old Medtronic pumps (additionally needed: RileyLink/Gnarl hardware, Android Phone with bluetooth low energy / BLE-chipset)](../Configuration/MedtronicPump.md) - * Other pumps might be available in the future, see [future possible pump drivers](Future-possible-Pump-Drivers.md) for details. - -3. [Dexcom G6](https://dexcom.com) - - * Alternatives: see list of possible [BG sources](../Configuration/BG-Source.md) - -4. Optional: Sony Smartwatch 3 (SWR50) - - * Alternatives: All [watches with Google Wear OS](https://wearos.google.com/intl/de_de/#find-your-watch) should work fine, for details see [list of tested phones and watches](https://docs.google.com/spreadsheets/d/1gZAsN6f0gv6tkgy9EBsYl0BQNhna0RDqA9QGycAqCQc/edit) for AndroidAPS (OS must be Android Wear) - -## Configuração do Nightscout - -See detailed [Nightscout setup](../Installing-AndroidAPS/Nightscout.md) - -## Computer setup - -To be able to create an Android app from the freely available AAPS open source code you need Android Studio on your computer or notebook (Windows, Mac, Linux). A detailed instruction can be found at [building the APK](../Installing-AndroidAPS/Building-APK.md). - -Please be patient when installing Android Studio as the software downloads a lot of additional data once installed on your computer. - -## Smartphone setup - -![Smartphone](../images/SampleSetupSmartphone.png) - -### Check smartphone firmware - -* Menu > Settings > Phone info > Software info: At least "Android-Version 8.0" (successfully tested up to Android version 8.0.0 Oreo - Samsung Experience Version 9.0) -* For firmware update: menu > Preferences > software update - -### Allow installation from unknown sources - -Menu > Settings > Device security > Unknown sources > slider to right side (= active) - -For security reasons this setting should be set back to inactive once the installation of all apps described here has been completed. - -### Activar bluetooth - -1. Menu > Settings > Connections > Bluetooth > slider to right side (= active) -2. Menu > Settings > Connections > Location > slider to right side (= active) - -Location services ("GPS") must be activated in order for Bluetooth to work properly. - -### Install Dexcom App (modified version) - -![Dexcom App patched](../images/SampleSetupDexApp.png) - -The original Dexcom app from the Google Play Store will not work because it does not broadcast the values to other apps. Therefore, a version slightly modified by the community is required. Only this modified Dexcom app can communicate with AAPS. Additionally the modified Dexcom App can be used with all Android smartphones not only the ones in [Dexcom's compatibility list](https://www.dexcom.com/dexcom-international-compatibility). - -To do this perform the following steps on your smartphone: - -1. If the original Dexcom app is already installed: - * Stop sensor - * Uninstall app via Menu > Settings > Apps > Dexcom G6 Mobile > Uninstall -2. Download and install the [BYODA Dexcom ap](../Hardware/DexcomG6.md#if-using-g6-with-build-your-own-dexcom-app) -3. Start modified Dexcom G6 app, activate/calibrate the sensor according to the given instructions and wait until the warm-up phase is finished. -4. Once the modified Dexcom app shows actual glucose value, setup the warnings (hamburger menu on top left side of the screen) as follows: - * Urgent low `55mg/dl` / `3.1mmol/l` (cannot be disabled) - * Low `OFF` - * High `OFF` - * Rise rate `OFF` - * Fall rate `OFF` - * Signal loss `OFF` - -## Install AndroidAPS - -1. Follow the instructions to [build the APK](../Installing-AndroidAPS/Building-APK.md#generate-signed-apk) -2. [Transfer](../Installing-AndroidAPS/Building-APK.md#transfer-apk-to-smartphone) the generated APK to your phone -3. [Configure AndroidAPS](../Configuration/Config-Builder.md) according to your needs using the setup assistant or manually -4. In this sample setup we used (among others) - -* BG source: `Dexcom G6 App (patched)` -- click cock-wheel and activate `Upload BG data to NS` and `Send BG data to xDrip+` (see [BG source](../Configuration/BG-Source.md)) - -![G5 Settings](../images/SampleSetupG5Settings.png) - -* NS Client activated (see [Nightscout setup](../Installing-AndroidAPS/Nightscout.md)) - -## Install xDrip+ - -xDrip+ is another mature open source app that offers countless possibilities. In this setup, contrary to what the developers first wrote the app for, xDrip+ is not used to collect glucose data from the Dexcom G6, but only to output alarms and to display the current glucose value including the curve on the Android home screen in the widget. With xDrip+ the alarms can be set much more individually than with the Dexcom software, AAPS or Nightscout (no limitation in the selection of sounds, different alarms depending on day/night time etc.). - -1. Download the latest stable APK version of xDrip+ with your smartphone - not the version from the Google Play Store! -2. Install xDrip+ by selecting the downloaded APK file. -3. Start xDrip+ and make the following settings (hamburger menu at top left) - * Settings > Alarms and Alerts > Glucose Level Alert List > Create Alerts (high and low) according to your needs. - * The existing alarms can be changed with a long press on the alarm. - * Settings > Alarms and Alerts > Calibration Alerts: disabled (reminded via the modified Dexcom app) - * Settings > Hardware Data Source > 640G/EverSense - * Settings > Inter-app settings > Accept Calibrations > `ON` - * Menu > Start sensor (is only "pro forma" and has nothing to do with the running G6 sensor. This is necessary otherwise an error message will appear regularly.) - -For more information about xDrip+, see here [BG source page](../Configuration/BG-Source.md). - -### Example of an alarm setup - -The "Urgent low alarm" (below 55 mg/dl resp. 3,1 mmol) is a standard alarm from the modified Dexcom app that cannot be disabled. - -![xDrip alarms](../images/SampleSetupxDripWarning.png) - -Tip for meetings / church visits / cinema etc..: - -If "Do not disturb" mode is activated in the Samsung Galaxy S7 (Menu > Settings > Sounds and vibration > Do not disturb: slider to right side (= active)), the phone only vibrates during urgent low alarm and does not issue an acoustic warning. For the other alarms set up via xDrip+ you can select whether the silent mode should be ignored (acoustic sound played) or not. - -## Disable power saving option - -On your Samsung Galaxy S7 go to Menu > Settings > Device Maintenance > Battery > Unmonitored Apps > + Add apps: Select the apps AndroidAPS, Dexcom G6 Mobile, xDrip+ and Android Wear (if smartwatch is used) one after the other - -## Optional: Setup Sony Smartwatch 3 (SWR50) - -With an Android Wear smartwatch life with diabetes can be made even more inconspicuous. The watch can be used to display the current glucose level, the status of the loop etc. on the wrist. The watch can even be used to control AndroidAPS (i.e. discreetly set a meal bolus). To do this, double tap the CGM value of the AAPSv2 watchface. The SWR50 usually runs for a full day until the battery needs to be recharged (same charger as the Samsung Galaxy S7: microUSB). - -![Smartwatch](../images/SampleSetupSmartwatch.png) - -Details about the information displayed on the watchface can be found [here](../Configuration/Watchfaces.md). - -* Install the app "Android Wear" on your smartphone via the Google Play Store and connect the smartwatch according to the instructions there. -* In AAPS choose hamburger menu (top left corner) > Config Builder > General (at the bottom of the list) > Wear > activate on left side, click cock wheel > Wear settings and activate `Controls from Watch` -* On your smartwatch: Long press display to change watchface and select `AAPSv2` -* If necessary restart both devices once. - -## Configurações da bomba - -see [Dana RS pump](../Configuration/DanaRS-Insulin-Pump.md) \ No newline at end of file diff --git a/docs/CROWDIN/pt/Getting-Started/WhatisAndroidAPS.md b/docs/CROWDIN/pt/Getting-Started/WhatisAndroidAPS.md deleted file mode 100644 index 1347d30368b2..000000000000 --- a/docs/CROWDIN/pt/Getting-Started/WhatisAndroidAPS.md +++ /dev/null @@ -1,39 +0,0 @@ -# What is a closed loop system with AAPS? - -AAPS is an app that acts as an artificial pancreas system (APS) on an Android smartphone. What is an artificial pancreas system? It is a software program that aims to do what a living pancreas does: keep blood sugar levels within healthy limits automatically. - -An APS can't do the job as well as a biological pancreas does, but it can make type 1 diabetes easier to manage using devices that are commercially available and software that is simple and safe. Those devices include a continuous glucose monitor (CGM) to tell AAPS about your blood sugar levels and an insulin pump which AAPS controls to deliver appropriate doses of insulin. The app communicates with those devices via bluetooth. It makes its dosing calculations using an algorithm, or set of rules, developed for another artificial pancreas system, called OpenAPS, which has thousands of users and has accumulated millions of hours of use. - -A note of caution: AAPS is not regulated by any medical authority in any country. Using AAPS is essentially carrying out a medical experiment on yourself. Setting up the system requires determination and technical knowledge. If you don't have the technical know-how at the beginning, you will by the end. All the information you need can be found in these documents, elsewhere online, or from others who have already done it -- you can ask them in Facebook groups or other forums. Many people have successfully built AAPS and are now using it entirely safely, but it is essential that every user: - -- Builds the system themselves so that they thoroughly understand how it works -- Adjusts its individual dosage algorithm with his or her diabetes team to work nearly perfect -- Maintains and monitors the system to ensure it is working properly - -```{note} -**Disclaimer and Warning** - -- All information, thought, and code described here is intended for informational and educational purposes only. Nightscout atualmente não faz nenhuma tentativa de conformidade de privacidade do HIPAA. Use Nightscout and AAPS at your own risk, and do not use the information or code to make medical decisions. -- Use of code from github.com is without warranty or formal support of any kind. Por favor, consulte a LICENÇA deste repositório para detalhes. -- All product and company names, trademarks, servicemarks, registered trademarks, and registered servicemarks are the property of their respective holders. A sua utilização é para fins informativos e não implica nenhuma afiliação ou apoio por parte deles. - -Please note - this project has no association with and is not endorsed by: [SOOIL](http://www.sooil.com/eng/), [Dexcom](https://www.dexcom.com/), [Accu-Chek, Roche Diabetes Care](https://www.accu-chek.com/), [Insulet](https://www.insulet.com/) or [Medtronic](https://www.medtronic.com/). -``` - -If you're ready for the challenge, please read on. - -## Primary goals behind AAPS - -- An app with safety built in. To read about the safety features of the algorithms, known as oref0 and oref1, click here () -- An all-in-one app for managing type 1 diabetes with an artificial pancreas and Nightscout -- An app to which users can easily add or remove modules as needed -- An app with different versions for specific locations and languages. -- An app which can be used in open- and closed-loop mode -- An app that is totally transparent: users can input parameters, see results, and make the final decision -- An app which is independent of particular pump drivers and contains a "virtual pump" so users can safely experiment before using it on themselves -- An app closely integrated with Nightscout -- An app in which the user is in control of safety constraints - -## How to start - -Of course, all of this content here is very important, but can be in the beginning quite confusing. A good orientation is given by the [Module Overview](../Module/module.md) and the [Objectives](../Usage/Objectives.html). diff --git a/docs/CROWDIN/pt/Hardware/DexcomG4.md b/docs/CROWDIN/pt/Hardware/DexcomG4.md deleted file mode 100644 index 99ac53f84489..000000000000 --- a/docs/CROWDIN/pt/Hardware/DexcomG4.md +++ /dev/null @@ -1,6 +0,0 @@ -# Dexcom G4 - -## Se usar G4 com cabo OTG ('tradicional' Nightscout) -- If not already set up then download Nightscout Uploader app from the Play Store and follow instructions on [Nightscout](https://nightscout.github.io/). -- In AAPS Preferences enter your Nightscout website and API secret. -- Select NSClient in ConfigBuilder (setting in AAPS). diff --git a/docs/CROWDIN/pt/Hardware/Smartwatch.md b/docs/CROWDIN/pt/Hardware/Smartwatch.md deleted file mode 100644 index 12281d6d256a..000000000000 --- a/docs/CROWDIN/pt/Hardware/Smartwatch.md +++ /dev/null @@ -1,10 +0,0 @@ -# Smartwatches - -Smartwatches are optional, but very useful for some users. More details are here: - -- [List of tested phones and smartwatches](../Getting-Started/Phones.md) -- [Watchfaces Wear OS](../Configuration/Watchfaces.md) -- [Troubleshooting Sony Smartwatch SW 3](../Usage/SonySW3.md) - -## Instructions for Building the AAPS Wear APK for Wear OS -https://androidaps.readthedocs.io/en/latest/remote-control.html#building-the-aaps-wear-apk diff --git a/docs/CROWDIN/pt/Installing-AndroidAPS/Building-APK.md b/docs/CROWDIN/pt/Installing-AndroidAPS/Building-APK.md deleted file mode 100644 index 4766d9836e3c..000000000000 --- a/docs/CROWDIN/pt/Installing-AndroidAPS/Building-APK.md +++ /dev/null @@ -1,369 +0,0 @@ -# Construir o ficheiro APK - -## Construa você em vez de fazer download - -**AAPS is not available as download due to regulation for medical devices. It is legal to build the app for your own use, but you must not give a copy to others! Consulte a [página de perguntas frequentes-FAQ](../Getting-Started/FAQ.md) para mais detalhes.** - -## Notas importantes - -* Please use **[Android Studio Giraffe" (2022.3.1)](https://developer.android.com/studio/)** or newer to build the apk. -* [Windows 32-bit systems](troubleshooting_androidstudio-unable-to-start-daemon-process) are not supported by Android Studio - -(Building-APK-recommended-specification-of-computer-for-building-apk-file)= - -## Recommended specification of computer for building apk file - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
OS (Only 64 bit)Windows 8 or higherMac OS 10.14 or higherAny Linux supports Gnome, KDE, or Unity DE;  GNU C Library 2.31 or later

CPU (Only 64 bit)

x86_64 CPU architecture; 2nd generation Intel Core or newer, or AMD CPU with support for a
Windows Hypervisor		ARM-based chips, or 2nd generation Intel Core or newer with support for
Hypervisor.Framework		x86_64 CPU architecture; 2nd generation Intel Core or newer, or AMD processor with support for AMD Virtualization (AMD-V) and SSSE3

RAM

8GB or more

Disk

At least 30GB free space. SSD is recommended.

Resolution

1280 x 800 Minimum

Internet

Broadband

- -Please keep in mind that both **64 bit CPU and 64 bit OS are mandatory condition.** If your system DOES NOT meet this condition, you have to change affected hardware or software or the whole system. **It is strongly recommended to use SSD (Solid State Disk) instead of HDD (Hard Disk Drive) because it will take less time when you are building the APS installation apk file.** Recommended is just recommended and it is not a mandatory. However, you may still use a HDD when you are building apk file but note that the building process can take a long time to complete, although once started, you can leave it running unattended. - -* * * - -### Este artigo é dividido em duas partes. - -* In the overview part there is an explanation on what steps are necessary to build the APK file. -* In the step by step walkthrough part you will find the screenshots of a concrete installation. Because the versions of Android Studio - the software development environment which we will use to build the APK - will change very quickly this will be not identical to your installation but it should give you a good starting point. Android Studio also runs on Windows, Mac OS X and Linux and there might be small differences in some aspects between each platform. If you find that something important is wrong or missing, please inform the facebook group "AAPS users" or in the Discord chat [Android APS](https://discord.gg/4fQUWHZ4Mw) so that we can have a look at this. - -## Visão Geral - -In general, the steps necessary to build the APK file: - -1. [Instalar Git](../Installing-AndroidAPS/git-install.md) -2. [Instalar o Android Studio](Building-APK-install-android-studio) -3. [Definir o caminho git nas preferências do Android Studio](Building-APK-set-git-path-in-preferences) -4. [Download AAPS code](Building-APK-download-AAPS-code) -5. [Download do Android SDK](Building-APK-download-android-sdk) -6. [Build the app](Building-APK-generate-signed-apk) (generate signed apk) -7. [Transferir o arquivo apk para o seu telefone](Building-APK-transfer-apk-to-smartphone) -8. [Identificar o receptor de estiver a utilizar o xDrip+](xdrip-identify-receiver) - -## Step by step walkthrough - -Detailed description of the steps necessary to build the APK file. - -## Install git (if you don't have it) - -Follow the manual on the [git installation page](../Installing-AndroidAPS/git-install.md). - -(Building-APK-install-android-studio)= - -## Instalar o Android Studio - -The following screenshots have been taken from Android Studio Version Arctic Fox | 2020.3.1. Screens can change in future versions of Android Studio. But you should be able to find your way through. [Help from the community](../Where-To-Go-For-Help/Connect-with-other-users.md) is provided. - -One of the most important things when installing Android Studio: **Be patient!** During installation and setup Android Studio is downloading a lot of stuff which will take its time. - -Download [Android Studio from here](https://developer.android.com/studio/install.html) and install it on your computer. - -On first start you will find the setup wizard: - -Select "Do not import settings" as you have not used it before. - -![Do not import settings](../images/studioSetup/01_ImportSettings.png) - -Decide whether you want to share data with Google or not. - -![Share data with Google](../images/studioSetup/02_DataSharing.png) - -On the following screen click "Next". - -![Welcome screen](../images/studioSetup/03_Welcome.png) - -Select "Standard" installation and click "Next". - -![Standard installation](../images/studioSetup/04_InstallType.png) - -Select the theme for the user interface you like. (In this manual we used "Light".) Then click "Next". - -> ***Note:*** This is just the color scheme. You can select whatever you like (i.e. "Darcula" for dark mode). This selection has no influence on building the APK but the following screenshots might look different. - -![UI color scheme](../images/studioSetup/05_UITheme.png) - -Click "Next" on the "Verify Settings" dialog. - -![Verify settings](../images/studioSetup/06_Overview.png) - -Click on all three license agreement parts and select "Agree". When you have agreed to all, the "Finish" button will be enabled and you can "Finish". - - ![Agree license agreements](../images/studioSetup/07_LicenseAgreement.png) - - -Wait while Android Studio downloads additional components and be patient. Once everything is downloaded button "Finish" turns blue. Click the button now. - -![Downloading components](../images/studioSetup/08_Downloading.png) - -(Building-APK-download-AAPS-code)= - -## Download AAPS code - -* On the Android Studio welcome screen select "Projects" (1) on the left and then "Get from VCS" (2). - - ![Android Studio wizard](../images/studioSetup/20_ProjectVCS.png) - - * If you already opened Android Studio and do not see the welcome screen anymore select File (1) > New (2) > Project from Version Control... (3) - - ![Check out project from version control within Android Studio](../images/AndroidStudio_FileNew.PNG) - - * We will now tell Android Studio were to get the code from: - - * Make sure you have selected "Repository URL" on the left (1). - - * Check if "Git" is selected as version control (2). - * Copy and paste the URL ```https://github.com/nightscout/AndroidAPS``` to the main AAPS repository into the URL textbox (3). - * Choose the directory where you want to save the cloned code (4). - - ![Clone Git](../images/studioSetup/21_CloneURL.png) - -* Click button "Clone" (5). - - ![Clone repository](../images/studioSetup/22_Cloning.png) - -* Do not click "Background" while repository is cloned! - -* After the repository is cloned successfully, Android Studio will open the cloned project. - -* You will be asked whether you want to trust the project. Click on "Trust project"! - - ![Trust project](../images/studioSetup/23_TrustProject.png) - -* In the status bar at the bottom you will see the information that Android Studio is running background tasks. - - ![Background tasks](../images/studioSetup/24_GradleSyncRunning.png) - -* Windows only: Grant access if your firewall is asking for permission. - - ![Firewall permission java](../images/AndroidStudio361_18.png) - -* Once the background tasks are finished you will probably see an error saying that errors occurred (1) or (2) or (3). - - ![SDK licence](../images/studioSetup/25_SyncFailed.png) - - Don't worry, this will be solved soon! - -(Building-APK-set-git-path-in-preferences)= - -## Set git path in preferences - -Make sure [git is installed](../Installing-AndroidAPS/git-install.md) on your computer and you have restarted your computer since installing. - -On the Android Studio welcome screen click "Customize" (1) on the left and then select the link "All settings..." (2): - -![Android Studio settings from welcome screen](../images/studioSetup/10_WizardSettings.png) - -### Windows - -* As windows user, make sure you have restarted your computer after [installing Git](../Installing-AndroidAPS/git-install.md). - -* In the menu, go to File (1) > Settings (2) (or Android Studio > Preferences on Mac). - - ![Open settings](../images/studioSetup/30_Settings.png) - -* Double-click "Version Control" (1) to open the sub-menu. - -* Click Git (2). -* Make sure update method "Merge" (3) is selected. -* Check if Android Studio can locate path to git.exe automatically by clicking the button "Test" (4). - - ![Android Studio settings](../images/studioSetup/11_GitPath.png) - -* If automatic setting is successful git version will be displayed next to the path. - - ![Git version displayed](../images/studioSetup/12_GitVersion.png) - -* Eventually git.exe cannot be found automatically or the Test will result in an error (1): - - ![Git not found](../images/studioSetup/13_GitVersionError.png) - - In this case click on the folder icon (2). - -* Use [search function](https://www.tenforums.com/tutorials/94452-search-file-explorer-windows-10-a.html) in windows explorer to find "git.exe" if you are unsure where git has been installed. You are looking for a file named "git.exe", located in **\bin** folder. - -* Select path to git.exe and make sure you selected the one in ** \bin\ ** folder (3) and click "OK" (4). - - ![Select git manually](../images/studioSetup/14_GitManualSelection.png) - -* Check your selected git path again with the "Test" button as described above. - -* When the git version is displayed next to the path (see screenshot above), close settings window by clicking "OK" button (5). - -### Mac - -* Any git version should work. For example . -* Use homebrew to install git: ```$ brew install git```. -* For details on installing git see the [official git documentation](https://git-scm.com/book/en/v2/Getting-Started-Installing-Git). -* If you install git via homebrew there is no need to change any preferences. Just in case: They can be found here: Android Studio - Preferences. - -(Building-APK-download-android-sdk)= - -## Download do Android SDK - -* In the menu, go to File (1) > Settings (2) (or Android Studio > Preferences on Mac). - - ![Open settings](../images/studioSetup/30_Settings.png) - -* Double-click on Languages & Frameworks to open its submenu (1). - -* Select Android SDK (2). -* Tick the box left of "Android 9.0 (Pie)" (3) (API Level 28). - - ![SDK settings](../images/studioSetup/31_AndroidSDK.png) - -* Confirm changes by clicking OK. - - ![Confirm SDK changes](../images/studioSetup/32_ConfirmSDK.png) - -* Wait until the SDK download and installation is finished. - - ![Wait during SDK installation](../images/studioSetup/34_DownloadSDK.png) - -* When SDK installation is completed the "Finish" button will turn blue. Click this button. - - ![Finish SDK installation](../images/studioSetup/35_DownloadSDKfinished.png) - -* Android Studio might recommend to update the gradle system. **Never update gradle!** This will lead to difficulties! - -* If you see an information on the lower right side of your Android Studio window that Android Gradle Plugin is ready to update click on the text "upgrade" (1). - - ![No gradle update](../images/studioSetup/36_GradleUpdateRequest.png) - -* In the dialog box the select "Don't remind me again for this project" (2). - - ![No gradle update](../images/studioSetup/37_GradleUpdateDeny.png) - -* Restart Android Studio before you continue. - -(Building-APK-generate-signed-apk)= - -## Generate signed APK - -Signing means that you indicate your app to be your own creation but in a digital way as a kind of digital fingerprint within the app itself. That is necessary because Android has a rule that it only accepts signed code to run for security reasons. For more information on this topic, follow [this link](https://developer.android.com/studio/publish/app-signing.html#generate-key). - -* After Android Studio is started, wait until all background tasks are finished. - - ![Wait for background tasks](../images/studioSetup/40_BackgroundTasks.png) - - * ***Warning:*** If errors occur, do not continue with the following steps. \ Consult the [troubleshooting section](../Installing-AndroidAPS/troubleshooting_androidstudio) for known problems! - - ![Gradle Sync Error](../images/studioSetup/41_GradleSyncError.png) - -* Click "Build" (1) in the menu bar and select "Generate Signed Bundle / APK..." (2). - - ![Build apk](../images/studioSetup/42_MenuBuild.png) - -* Select "APK" (1) instead of "Android App Bundle" and click "Next" (2). - - ![APK instead of bundle](../images/studioSetup/43_Apk.png) - -* Make sure that module is set to "AndroidAPS.app" (1). - -* Click "Create new..." (2) to start creating your key store. - - ***Note:*** A key store in this case is nothing more than a file in which the information for signing is stored. It is encrypted and the information is secured with passwords. - - ![Create key store](../images/studioSetup/44_KeystoreNew.png) - -* Click the folder symbol to select a path on your computer for your key store. - - ![Create key store](../images/studioSetup/45_KeystoreDialog.png) - -* Select the path where your key store shall be saved (1). - - ![Create key store](../images/studioSetup/46_KeystorePath.png) - - ***Warning: Do not save in same folder as project. You must use a different directory!*** A good location would be your home folder. - -* Type a file name for your key store (2) and confirm with "OK" (3). - -* Enter (2) and confirm (3) the password for your key store. ![Select key store path](../images/studioSetup/47_KeystoreDialog.png) - - ***Note:*** Passwords for key store and key do not have to be very sophisticated. Make sure to remember those or make a note in a safe place. In case you will not remember your passwords in the future, see [troubleshooting for lost key store](troubleshooting_androidstudio-lost-keystore). - -* Enter an alias (4) for your key. Choose whatever you like. - -* Enter (5) and confirm (6) the password for your key - -* Validity (7) is 25 years by default. You do not have to change the default value. - -* First and last name must be entered (8). All other information is optional. - -* Click "OK" (9) when you are done. - -* Make sure the box to remember passwords is checked (1). So you don't have to enter them again next time you build the apk (i.e. when updating to a new AAPS version). - -* Click "Next" (2). - - ![Remember passwords](../images/studioSetup/48_KeystoreSave.png) - -* Select build variant "fullRelease" (1) and press "Finish". - - ![Select build variant](../images/studioSetup/49_BuildVariant.png) - -* Android Studio will show "Gradle Build running" at the bottom. This takes some time, depending on your computer and internet connection. **Be patient!** - - ![Gradle Running](../images/studioSetup/50_GradleRunning.png) - -* Android Studio will display the information "Generate Signed APK" after build is finished. - - ![Build finished](../images/studioSetup/51_BuildFinished.png) - -* In case build was not successful refer to the [troubleshooting section](../Installing-AndroidAPS/troubleshooting_androidstudio). - -* Click on the notification to expand it. - -* Click on the link "locate". - - ![Locate build](../images/studioSetup/52_BuildLocate.png) - - * If the notification is gone, you can always open the "Event log" and select the same link there. ![Build successfully - event log](../images/studioSetup/53_EventLog.png) - -* Your file manager/explorer will open. Navigate to the directory "full" (1) > "release" (2). - - ![File location apk](../images/studioSetup/54_APKlocation.png) - -* "app-full-release.apk" (3) is the file you are looking for! - -(Building-APK-transfer-apk-to-smartphone)= - -## Transfer APK to smartphone - -Easiest way to transfer app-full-release.apk to your phone is via [USB cable or Google Drive](https://support.google.com/android/answer/9064445?hl=en). Please note that transfer by mail might cause difficulties and is not the preferred way. - -On your phone you have to allow installation from unknown sources. Manuals how to do this can be found on the internet (i.e. [here](https://www.expressvpn.com/de/support/vpn-setup/enable-apk-installs-android/) or [here](https://www.androidcentral.com/unknown-sources)). - -## Resolução de Problemas - -See separate page [troubleshooting Android Studio](../Installing-AndroidAPS/troubleshooting_androidstudio). \ No newline at end of file diff --git a/docs/CROWDIN/pt/Resources/index.md b/docs/CROWDIN/pt/Resources/index.md deleted file mode 100644 index 57b2ebe2945e..000000000000 --- a/docs/CROWDIN/pt/Resources/index.md +++ /dev/null @@ -1,8 +0,0 @@ -# Resources - -```{toctree} -:glob: true -:maxdepth: 4 - -clinician-guide-to-AndroidAPS -``` diff --git a/docs/CROWDIN/pt/Sandbox/sandbox2.md b/docs/CROWDIN/pt/Sandbox/sandbox2.md deleted file mode 100644 index 33c547956c89..000000000000 --- a/docs/CROWDIN/pt/Sandbox/sandbox2.md +++ /dev/null @@ -1,43 +0,0 @@ -# internal sandbox file 2 for testing - -```{admonition} no need to translate this -:class: note - -No need to translate this. -``` - -This is an internal sandbox file for the documentation team to test - -1. markdown syntax and - -1. background process for - 1. CROWDIN translation and - 2. Read The Docs deployment. - -You can dirctly jump from here to the first label in the sandbox1.md file - ["Jump"](sandbox1-this-is-a-test). - -You can dirctly jump from here to the second label in this file - ["Jump"](sandbox1-this-is-another-test). - -Here you can jump to the first sandbox file - ["Jump"](./sandbox1.md). - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -(sandbox2-this-is-a-test)= -## This is a test - -This is a test if labels must be unique. - -### This is spare information from the docs - -cut from index: - -There are "limits" set in place when you are first beginning your AAPS journey. These safety limits have been developed over many years by observations of the inadvertent mistakes that new users are most likely to make when first learning to set up, build, and then successfully loop with AAPS - as most often those mistakes occur simply because the user was so excited to get started using the system that they may have forgotten to sit down and dedicate the time needed to understand the information within this documentation thoroughly. - - -### spare info from the overview to put into "preparing" - -Since the requirements are very different from anything you might have set up in the past, we recommend that you really follow the instructions, step-by-step the first few times you build the app, so that you have a stronger sense of how the app building process is supposed to behave when all directions are followed exactly. Please remember to take your time. Later this will go very quickly when you build the app again for a new version. That way you will have a greater chance of noticing when something doesn't going as planned before too many steps are out of line. It is important to save the your keystore file (.jks file used to sign your app) in a safe place, so that you can always use that exact same keystore file and password each and every time you are asked to create a new updated version of AAPS, as this file is what makes sure that each new version of the app "remembers" all the information that you have provided to it in previous versions of the app and thus ensure that the updates will go as smoothly as possible. On average, you can assume that there will be one new version and 2-3 required updates per year. This number is based on experience and may change in the future. But we do want to at least give you a general guideline on what to expect. When you are more experienced at building updated AAPS app versions all the steps that are required in building an updated app will only take 15-30 minutes, on average. However, in the beginning there can be a rather steep learning curve as these steps are not always considered intuitive by new users! So do not get frustrated if you find that it takes half a day or a whole day with some help from the community before you are finally finished with the update process. If you find that you are getting very frustrated just take a short break, and oftentimes; after a stroll around the block or two...you'll find that you are better able to approach the problem again. diff --git a/docs/CROWDIN/pt/Usage/Objectives.md b/docs/CROWDIN/pt/Usage/Objectives.md deleted file mode 100644 index e1e806cf8ce4..000000000000 --- a/docs/CROWDIN/pt/Usage/Objectives.md +++ /dev/null @@ -1,184 +0,0 @@ -# Objetivos - -AAPS has a series of Objectives that need to be completed to walk you through the features and settings of safe looping. Eles garantem que configurou corretamente tudo o que foi detalhado nas seções acima e que entende o que o seu sistema está a fazer e por que assim pode confiar nele. - -If you are **upgrading phones** then you can [export your settings](../Usage/ExportImportSettings.md) to keep your progress through the objectives. Not only will your progress through the objectives be saved, but also your safety settings such as max bolus etc. If you do not export and import your settings then you will need to start the objectives from the beginning again. It is a good idea to [backup your settings](../Usage/ExportImportSettings.html) frequently just in case. - -If you want to go back in objectives see [explanation below](Objectives-go-back-in-objectives). - -## Objetivo 1: Configurar a visualização e monitorização, analisando basais e rácios - -- Select the right blood glucose source for your setup. See [BG Source](../Configuration/BG-Source.md) for more information. -- Select the right Pump in ConfigBuilder (select Virtual Pump if you are using a pump model with no AAPS driver for looping) to ensure your pump status can communicate with AAPS. -- If using DanaR pump then ensure you have followed [DanaR Insulin Pump](../Configuration/DanaR-Insulin-Pump.md) instructions to ensure the link between pump and AAPS. -- You need to establish a data repository/reporting platform to complete this objective. That can be accomplished with either Nightscout or Tidepool (or both). Follow instructions at the [Nightscout](../Installing-AndroidAPS/Nightscout.md) or [Tidepool](../Installing-AndroidAPS/Tidepool.md) page for instructions. -- Note that URL in NSClient must be **WITHOUT /api/v1/** at the end - see [NSClient settings in Preferences](Preferences-nsclient). - -*You may need to wait for the next blood glucose reading to arrive before AAPS will recognise it.* - -## Objective 2: Learn how to control AAPS - -- Perform several actions in AAPS as described in this objective. - -- Click on the orange text "Not completed yet" to access the to-dos. - -- Links will be provided to guide you in case you are not familiar with a specific action yet. - - ```{image} ../images/Objective2_V2_5.png - :alt: Captura de ecrã do Objetivo 2 - ``` - -(Objectives-objective-3-prove-your-knowledge)= - -## Objetivo 3: Prove o seu conhecimento - -Objective 3 is a multiple choice test based on questions designed to test your theoretical knowledge of **AAPS**. - -Some users find Objective 3 to be the most difficult objective to complete. Please do read the AAPS documents in conjunction with the questions. If you are genuinely stuck after researching the **AAPS** documents, please search or ask for help on the Facebook or Discord group. These groups can provide friendly hints or redirect you to the relevant part of the **AAPS** documents. - -To proceed with Objective 3, click on the orange text “Not completed yet” to access the relevant question. Please read each question and select your answer(s). - - - -Within each question, a hyperlink to the **AAPS** documents will guide you to the relevant section of the document which you should read in order to locate the correct answer. - - -[Obj3_Screenshot 2023-12-05 223422](https://github.com/openaps/AndroidAPSdocs/assets/137224335/77347516-e24e-459d-98ab-acbb49a3d4e8)![image](https://github.com/openaps/AndroidAPSdocs/assets/137224335/ca756b8e-efbc-4427-b281-ac953ce16718) - - - -For each question, there may be more than one answer that is correct! If an incorrect answer is selected, the question will be time locked for a certain amount of time (60 minutes) before you can go back and answer the question. - - -After updating to a new version of **AAPS**, new questions may be added to cover a prevalent issue picked up by **AAPS** or alternatively to test your knowledge of a new feature of **AAPS** as released. - - -When **AAPS** is installed for the first time, you will have to complete Objective 3 entirely in order to move onto Objective 4. Each objective is required to be completed in sequential order. New features will gradually be unlocked as progress is made through the objectives. - -__What happens if new questions are added later to Objective 3?__ From time to time, new features are added to **AAPS** which may require a new question to be added to Objective 3. As a result, any new question added to Objective 3 will be marked as “incomplete” because **AAPS** will require you to action this. As each Objective is independent, you will not lose the existing functionality of **AAPS** providing the other objectives remain completed. - - -## Objetivo 4: Iniciar um loop aberto - -- Select Open Loop either from Preferences, or by pressing and holding the Loop button in top left of the home screen. -- Work through the [Preferences](../Configuration/Preferences.md) to set up for you. -- Manually enact at least 20 of the temporary basal rate suggestions over a period of 7 days; input them to your pump and confirm in AAPS that you have accepted them. Ensure this data shows in AAPS and Nightscout. -- Enable [temp targets](../Usage/temptarget.md) if necessary. Use hypo temp targets to prevent that the system will correct too strong because of a raising blood glucose after a hypo. - -### Reduce number of notifications - -- To reduce the Number of decisions to be made while in Open Loop set wide target range like 90 - 150 mg/dl or 5,0 - 8,5 mmol/l. - -- You might even want to wider upper limit (or disable Open Loop) at night. - -- In Preferences you can set a minimum percentage for suggestion of basal rate change. - - ```{image} ../images/OpenLoop_MinimalRequestChange2.png - :alt: Open Loop minimal request change - ``` - -- Also, you do not need to act every 5 minutes on all suggestions... - -## Objective 5: Understanding your open loop, including its temp basal recommendations - -- Start to understand the thinking behind the temp basal recommendations by looking at the [determine basal logic](https://openaps.readthedocs.io/en/latest/docs/While%20You%20Wait%20For%20Gear/Understand-determine-basal.html) and both the [forecast line in AAPS homescreen](Screenshots-prediction-lines)/Nightscout and the summary of outputs from the calculations in your OpenAPS tab. - -You will want to set your target higher than usual until you are confident in the calculations and settings. System allows - -- a low target to be a minimum of 4 mmol (72 mg/dl) or maximum of 10 mmol (180 mg/dl) -- a high target to be a minimum of 5 mmol (90 mg/dl) and maximum of 15 mmol (225 mg/dl) -- a temporary target as a single value can be anywhere in the range of 4 mmol to 15 mmol (72 mg/dl to 225 mg/dl) - -The target is the value that calculations are based on, and not the same as where you aim to keep your blood glucose values within. If your target is very wide (say, 3 or more mmol \[50 mg/dl or more\] wide), you will often find little AAPS action. This is because blood glucose is eventually predicted to be somewhere in that wide range and therefore not many fluctuating temporary basal rates are suggested. - -You may want to experiment with adjusting your targets to be a closer together range (say, 1 or less mmol \[20 mg/dl or less\] wide) and observe how the behavior of your system changes as a result. - -You can view a wider range (green lines) on the graph for the values you aim to keep your blood glucose within by entering different values in [Preferences](../Configuration/Preferences.md) > Range for Visualisation. - -```{image} ../images/sign_stop.png -:alt: Stop sign -``` - -### Stop here if you are open looping with a virtual pump - do not click Verify at the end of this objective. - -```{image} ../images/blank.png -:alt: blank -``` - -(Objectives-objective-6-starting-to-close-the-loop-with-low-glucose-suspend)= -## Objective 6: Starting to close the loop with Low Glucose Suspend - -```{image} ../images/sign_warning.png -:alt: Warning sign -``` - -### Closed loop will not correct high BG values in objective 6 as it is limited to low glucose suspend. High BG values have to be corrected manually by you! - -- Prerequisite: You need a good profile (basal, ISF, IC) already working in AAPS to start with Loop in Low Glucose Suspend mode. Otherwise you can run in a hypo which you have to manually correct. This will help you a lot to avoid having to treat a low glucose over a period of 5 days. **If you are still having frequent or severe low glucose episodes then consider refining your DIA, basal, ISF and carb ratios and do NOT start objective 6 at this time.** -- You don't have to change your settings now. During objective 6, the maxIOB setting is internally set to zero automatically. **This override will be reversed when moving to objective 7.** -- The system will override your maxIOB settings to zero, which means if blood glucose is dropping it can reduce basal for you. If blood glucose is rising then it will only increase basal if the basal IOB is negative from a previous Low Glucose Suspend. Otherwise basal rates will remain the same as your selected profile. **That means that you have to manually handle high values with insulin corrections.** -- If your basal IOB is negative (see screenshot below) a TBR > 100% can be issued also in objective 6. - -```{image} ../images/Objective6_negIOB.png -:alt: Example negative IOB -``` - -- Set your target range slightly higher than you usually aim for, just to be safe and have a bit more scurity buffer. -- Enable 'Low Glucose Suspend' mode either by by pressing and holding the Loop icon at the top right corner of the home screen and selecting the Loop - LGS mode icon. -- Watch how temporary basals are active by viewing the blue basal text on the homescreen or the blue basal render on the homescreen graph. -- You may temporarily experience spikes following treated hypos without the ability to increase basal on the rebound. - -(Objectives-objective-7-tuning-the-closed-loop-raising-max-iob-above-0-and-gradually-lowering-bg-targets)= -## Objective 7: Tuning the closed loop, raising maxIOB above 0 and gradually lowering BG targets - -- Select 'Closed Loop' either from [Preferences](../Configuration/Preferences.md) or by pressing and holding the Loop icon at the top right corner of the home screen, over a period of 1 day. - -- Raise your 'Maximum total IOB OpenAPS can’t go over' (in OpenAPS called 'max-iob') above 0. The default recommendation is "average mealbolus + 3x max daily basal" (for the SMB algorithm) or "3x max daily basal" (for the older AMA algorithm) but you should slowly work up to this until you know your settings work for you (max daily basal = the maximum hourly value in any time segment of the day). - - This recommendation should be seen as a starting point. If you set to the 3x and you are seeing moves that push you too hard and fast then lower that number. If you are very resistant, raise it very little at a time. - - ```{image} ../images/MaxDailyBasal2.png - :alt: max daily basal - ``` - -- Once confident on how much IOB suits your looping patterns, then reduce your targets to your desired level. - -(Objectives-objective-8-adjust-basals-and-ratios-if-needed-and-then-enable-autosens)= -## Objective 8: Adjust basals and ratios if needed, and then enable autosens - -- You can use [autotune](https://openaps.readthedocs.io/en/latest/docs/Customize-Iterate/autotune.html) as a one off to check your basals remain accurate or do a traditional basal test. -- Enable [autosens](../Usage/Open-APS-features.md) over a period of 7 days and watch the white line on the homescreen graph show how your sensitivity to insulin may be rising or falling as a result of exercise or hormones etc. and keep an eye in the OpenAPS report tab how AAPS is adjusting the basals and/or targets accordingly. - -*Don’t forget to record your looping in* [this form](https://bit.ly/nowlooping) *logging AAPS as your type of DIY loop software, if you have not already done so.* - -(Objectives-objective-9-enabling-additional-oref1-features-for-daytime-use-such-as-super-micro-bolus-smb)= -## Objective 9: Enabling additional oref1 features for daytime use, such as super micro bolus (SMB) - -- You must read the [SMB chapter in this wiki](Open-APS-features-super-micro-bolus-smb) and [chapter oref1 in openAPSdocs](https://openaps.readthedocs.io/en/latest/docs/Customize-Iterate/oref1.html) to understand how SMB works, especially what's the idea behind zero-temping. -- Then you ought to [rise maxIOB](Open-APS-features-maximum-total-iob-openaps-cant-go-over-openaps-max-iob) to get SMBs working fine. maxIOB now includes all IOB, not just added basal. That is, if given a bolus of 8 U for a meal and maxIOB is 7 U, no SMBs will be delivered until IOB drops below 7 U. A good start is maxIOB = average mealbolus + 3x max daily basal (max daily basal = the maximum hourly value in any time segment of the day - see [objective 7](Objectives-objective-7-tuning-the-closed-loop-raising-max-iob-above-0-and-gradually-lowering-bg-targets) for an illustration) -- min_5m_carbimpact default in absorption settings has changed from 3 to 8 going from AMA to SMB. If you are upgrading from AMA to SMB, you have to change it manually. - -(Objectives-objective-10-automation)= -## Objective 10: Automation - -- You have to start objective 10 to be able to use [Automation](../Usage/Automation.md). -- Make sure you have completed all objectives including exam [Objectives-objective-3-prove-your-knowledge](Objectives#objective-3-prove-your-knowledge). -- Completing previous objectives will not effect other objectives you have already finished. You will keep all finished objectives! - -(Objectives-objective-11-DynamicISF)= -## Objective 11: Additional Features such as DynamicISF - -- You have to start objective 11 to be able to use [DynamicISF](../Usage/Open-APS-features.md) - -(Objectives-go-back-in-objectives)= -## Go back in objectives - -If you want to go back in objectives for whatever reason you can do so by clicking at "clear finished". - -```{image} ../images/Objective_ClearFinished.png -:alt: Go back in objectives -``` - -## Objectives in Android APS before version 3.0 - -One objective was removed when Android APS 3.0 was released. Users of Android APS version 2.8.2.1 who are on older Android software (i.e. earlier than version 9) will be using an older set of objectives which can be found [here](../Usage/Objectives_old.md). diff --git a/docs/CROWDIN/pt/Usage/Objectives_old.md b/docs/CROWDIN/pt/Usage/Objectives_old.md deleted file mode 100644 index 5c87d9388679..000000000000 --- a/docs/CROWDIN/pt/Usage/Objectives_old.md +++ /dev/null @@ -1,152 +0,0 @@ -# Objectives as of Android APS 2.8.2.1 - -This is not the latest version of the Android APS Objectives. This page details the Objectives that were in place prior to version 3.0. Anyone using an older version of Android (i.e. prior to Android 9) and Android APS version 2.8.2.1 should refer to this page. - -Please see [this page](../Usage/Objectives.md) for the current set of Objectives. - -A AndroidAPS possui uma série de objetivos que precisam ser completados para o encaminhar pelos recursos e configurações de um loop seguro. Eles garantem que configurou corretamente tudo o que foi detalhado nas seções acima e que entende o que o seu sistema está a fazer e por que assim pode confiar nele. - -If you are **upgrading phones** then you can [export your settings](../Usage/ExportImportSettings.md) to keep your progress through the objectives. Not only will your progress through the objectives be saved, but also your safety settings such as max bolus etc. If you do not export and import your settings then you will need to start the objectives from the beginning again. It is a good idea to [backup your settings](../Usage/ExportImportSettings.html) frequently just in case. - -If you want to go back in objectives see [explanation below](../Usage/Objectives.md#go-back-in-objectives). - -## Objetivo 1: Configurar a visualização e monitorização, analisando basais e rácios - -- Select the right blood glucose source for your setup. See [BG Source](../Configuration/BG-Source.md) for more information. -- Select the right Pump in ConfigBuilder (select Virtual Pump if you are using a pump model with no AndroidAPS driver for looping) to ensure your pump status can communicate with AndroidAPS. -- If using DanaR pump then ensure you have followed [DanaR Insulin Pump](../Configuration/DanaR-Insulin-Pump.md) instructions to ensure the link between pump and AndroidAPS. -- Follow instructions in [Nightscout](../Installing-AndroidAPS/Nightscout.md) page to ensure Nightscout can receive and display this data. -- Note that URL in NSClient must be **WITHOUT /api/v1/** at the end - see [NSClient settings in Preferences](../Configuration/Preferences.md#nsclient). - -*You may need to wait for the next blood glucose reading to arrive before AndroidAPS will recognise it.* - -## Objetivo 2: Aprenda a controlar a AndroidAPS - -- Perform several actions in AndroidAPS as described in this objective. - -- Click on the orange text "Not completed yet" to access the to-dos. - -- Links will be provided to guide you in case you are not familiar with a specific action yet. - - ![Captura de ecrã do Objetivo 2](../images/Objective2_V2_5.png) - -## Objetivo 3: Prove o seu conhecimento - -- Pass a multiple-choice exam testing your AndroidAPS knowledge. - -- Click on the orange text "Not completed yet" to access the page with the question and answering options. - - ![Captura de ecrã do Objetivo 3](../images/Objective3_V2_5.png) - -- Links will be provided to guide you in case you are unsure about the correct answers yet. - -- The questions for objective 3 have been completely rewritten by native speakers as of AAPS 2.8. Os novos cobrem os mesmos tópicos básicos e mais alguns novos. - -- These new questions will lead to some not answered questions even though you have successfully completed objective 3 in previous versions. - -- Unanswered questions will affect you only if you start a new objective. Por outras palavras: Se já completou todos os objetivos, pode esperar e responder às novas perguntas mais tarde, sem perder as funções da AAPS. - -## Objetivo 4: Iniciar um loop aberto - -- Select Open Loop either from Preferences, or by pressing and holding the Loop button in top left of the home screen. -- Work through the [Preferences](../Configuration/Preferences.md) to set up for you. -- Manually enact at least 20 of the temporary basal rate suggestions over a period of 7 days; input them to your pump and confirm in AndroidAPS that you have accepted them. Garanta que esses dados estão registados na AndroidAPS e no Nightscout. -- Enable [temp targets](../Usage/temptarget.md) if necessary. Use hypo temp targets to prevent that the system will correct too strong because of a raising blood glucose after a hypo. - -### Reduce number of notifications - -- To reduce the Number of decisions to be made while in Open Loop set wide target range like 90 - 150 mg/dl or 5,0 - 8,5 mmol/l. - -- You might even want to wider upper limit (or disable Open Loop) at night. - -- In Preferences you can set a minimum percentage for suggestion of basal rate change. - - ![Open Loop minimal request change](../images/OpenLoop_MinimalRequestChange2.png) - -- Also, you do not need to act every 5 minutes on all suggestions... - -## Objective 5: Understanding your open loop, including its temp basal recommendations - -- Start to understand the thinking behind the temp basal recommendations by looking at the [determine basal logic](https://openaps.readthedocs.io/en/latest/docs/While%20You%20Wait%20For%20Gear/Understand-determine-basal.html) and both the [forecast line in AndroidAPS homescreen](../Getting-Started/Screenshots.md#prediction-lines)/Nightscout and the summary of outputs from the calculations in your OpenAPS tab. - -You will want to set your target higher than usual until you are confident in the calculations and settings. System allows - -- a low target to be a minimum of 4 mmol (72 mg/dl) or maximum of 10 mmol (180 mg/dl) -- a high target to be a minimum of 5 mmol (90 mg/dl) and maximum of 15 mmol (225 mg/dl) -- a temporary target as a single value can be anywhere in the range of 4 mmol to 15 mmol (72 mg/dl to 225 mg/dl) - -The target is the value that calculations are based on, and not the same as where you aim to keep your blood glucose values within. If your target is very wide (say, 3 or more mmol \[50 mg/dl or more\] wide), you will often find little AAPS action. This is because blood glucose is eventually predicted to be somewhere in that wide range and therefore not many fluctuating temporary basal rates are suggested. - -You may want to experiment with adjusting your targets to be a closer together range (say, 1 or less mmol \[20 mg/dl or less\] wide) and observe how the behavior of your system changes as a result. - -You can view a wider range (green lines) on the graph for the values you aim to keep your blood glucose within by entering different values in [Preferences](../Configuration/Preferences.md) > Range for Visualisation. - -![Stop sign](../images/sign_stop.png) - -### Stop here if you are open looping with a virtual pump - do not click Verify at the end of this objective. - -![blank](../images/blank.png) - -## Objective 6: Starting to close the loop with Low Glucose Suspend - -![Warning sign](../images/sign_warning.png) - -### Closed loop will not correct high bg values in objective 6 as it is limited to low glucose suspend. High bg values have to be corrected manually by you! - -- Select Closed Loop either from [Preferences](../Configuration/Preferences.md) or by pressing and holding the Open Loop button in the top left of the home screen. - -- Set your target range slightly higher than you usually aim for, just to be safe. - -- Watch how temporary basals are active by viewing the blue basal text on the homescreen or the blue basal render on the homescreen graph. - -- Ensure your settings have supported AndroidAPS to avoid having to treat a low glucose over a period of 5 days. If you are still having frequent or severe low glucose episodes then consider refining your DIA, basal, ISF and carb ratios. - -- You don't have to change your settings. During objective 6 maxIOB setting is internally set to zero automatically. This override will be reversed when moving to objective 7. - -- The system will override your maxIOB settings to zero, which means if blood glucose is dropping it can reduce basal for you, but if blood glucose is rising then it will only increase basal if the basal IOB is negative (from a previous Low Glucose Suspend), otherwise basal rates will remain the same as your selected profile. - - ![Example negative IOB](../images/Objective6_negIOB.png) - -- If your basal IOB is negative (see screenshot above) a TBR > 100% can be issued also in objective 6. - -- You may temporarily experience spikes following treated hypos without the ability to increase basal on the rebound. - -## Objective 7: Tuning the closed loop, raising max IOB above 0 and gradually lowering BG targets - -- Raise your 'Maximum total IOB OpenAPS can’t go over' (in OpenAPS called 'max-iob') above 0 over a period of 1 day, the default recommendation is "average mealbolus + 3x max daily basal"(for SMB algorithm) or "3x max daily basal" (for older AMA algorithm) but you should slowly work up to this until you know your settings work for you (max daily basal = the maximum hourly value in any time segment of the day). - - This recommendation should be seen as a starting point. If you set to the 3x and you are seeing moves that push you to hard and fast then lower that number. If you are very resistant raise it a very little at a time. - - ![max daily basal](../images/MaxDailyBasal2.png) - -- Once confident on how much IOB suits your looping patterns then reduce your targets to your desired level. - -## Objective 8: Adjust basals and ratios if needed, and then enable autosens - -- You can use [autotune](https://openaps.readthedocs.io/en/latest/docs/Customize-Iterate/autotune.html) as a one off to check your basals remain accurate or do a traditional basal test. -- Enable [autosens](../Usage/Open-APS-features.md) over a period of 7 days and watch the white line on the homescreen graph show how your sensitivity to insulin may be rising or falling as a result of exercise or hormones etc. and keep an eye in the OpenAPS report tab how AndroidAPS is adjusting the basals and/or targets accordingly. - -*Don’t forget to record your looping in* [this form](https://bit.ly/nowlooping) *logging AndroidAPS as your type of DIY loop software, if you have not already done so.* - -## Objective 9: Try additional features for daytime use and gain confidence in your closed loop system - -- Before AAPS version 2.7 meal assist (MA) was the basic algorithm for AAPS and completing objective 8 was necessary to activate [advanced meal assist (AMA)](../Usage/Open-APS-features.md#advanced-meal-assist-ama). -- As [advanced meal assist (AMA)](../Usage/Open-APS-features.md#advanced-meal-assist-ama) is the standard algorithm from AAPS version 2.7 onwards use the following 28 days to try features you haven't used yet and get more confident with you closed loop system. - -## Objective 10: Enabling additional oref1 features for daytime use, such as super micro bolus (SMB) - -- You must read the [SMB chapter in this wiki](../Usage/Open-APS-features.md#super-micro-bolus-smb) and [chapter oref1 in openAPSdocs](https://openaps.readthedocs.io/en/latest/docs/Customize-Iterate/oref1.html) to understand how SMB works, especially what's the idea behind zero-temping. -- Then you ought to [rise maxIOB](../Usage/Open-APS-features.md#maximum-total-iob-openaps-cant-go-over-openaps-max-iob) to get SMBs working fine. maxIOB now includes all IOB, not just added basal. That is, if given a bolus of 8 U for a meal and maxIOB is 7 U, no SMBs will be delivered until IOB drops below 7 U. A good start is maxIOB = average mealbolus + 3x max daily basal (max daily basal = the maximum hourly value in any time segment of the day - see [objective 7](../Usage/Objectives#objective-7-tuning-the-closed-loop-raising-max-iob-above-0-and-gradually-lowering-bg-targets) for an illustration) -- min_5m_carbimpact default in absorption settings has changed from 3 to 8 going from AMA to SMB. If you are upgrading from AMA to SMB, you have to change it manually. - -## Objective 11: Automation - -- You have to start objective 11 to be able to use [Automation](../Usage/Automation.md). -- Make sure you have completed all objectives including exam [../Usage/Objectives.md#objective-3-prove-your-knowledge](../Usage/Objectives#objective-3-prove-your-knowledge). -- Completing previous objectives will not effect other objectives you have already finished. You will keep all finished objectives! - -## Go back in objectives - -If you want to go back in objectives for whatever reason you can do so by clicking at "clear finished". - -![Go back in objectives](../images/Objective_ClearFinished.png) diff --git a/docs/CROWDIN/pt/Usage/Smoothing-Blood-Glucose-Data-in-xDrip.md b/docs/CROWDIN/pt/Usage/Smoothing-Blood-Glucose-Data-in-xDrip.md deleted file mode 100644 index 716234b04a15..000000000000 --- a/docs/CROWDIN/pt/Usage/Smoothing-Blood-Glucose-Data-in-xDrip.md +++ /dev/null @@ -1,33 +0,0 @@ -(Smoothing-Blood-Glucose-Data-in-xDrip-smoothing-blood-glucose-data)= - -# Smoothing blood glucose data - -If BG data is jumpy/noisy, AAPS may dose insulin incorrectly resulting in high or low BG. For this reason it’s important to disable the loop until the problem is resolved. Depending on your CGM such issues may be due to the CGM’s configuration or sensor problems/site issues. You may need to replace your CGM sensor to resolve this. - -Some CGM systems have internal algorithms to detect the noise level in the readings and AAPS can use this information to avoid giving SMBs if the BG data is too unreliable. However, some CGMs do not transmit this data and for these BG sources 'Enable SMB always' and 'Enable SMB after carbs' are disabled for safety reasons. - -## Dexcom sensors - -### Build Your Own Dexcom App - -When using [BYODA](DexcomG6-if-using-g6-with-build-your-own-dexcom-app) your BG data is smooth and consistent. Furthermore you can take advantage of Dexcom back-smoothing. There are no restrictions in using SMBs, because the noise-level data is shared with AAPS. - -### xDrip+ with Dexcom G6 or Dexcom ONE - -Noise-level data and smooth BG readings are only shared with AAPS if you use xDrip+ [native mode](https://navid200.github.io/xDrip/docs/Native-Algorithm). Using native mode, there are no restrictions in using SMBs. - -### Dexcom G6 or Dexcom ONE with xDrip+ Companion Mode - -The noise-level data is not shared with AAPS using this method. Therefore 'Enable SMB always' and 'Enable SMB after carbs' are disabled. - -## Freestyle Libre sensors - -### xDrip+ with FreeStyle Libre - -None of the FreeStyle Libre systems (FSL1, FSL2, or FSL3) broadcast any information about the level of noise detected in the readings, and therefore 'Enable SMB always' and 'Enable SMB after carbs' are disabled for all setups using the FreeStyle Libre. - -In addition, many people have reported the FreeStyle Libre often produces noisy data. In xDrip+ there are a few options to help with this: - -**Smooth Sensor Noise.** In xDrip+ Settings > xDrip+ Display Settings ensure that Smooth Sensor Noise is turned on. This attempts to apply smoothing to noisy data. - -**Smooth Sensor Noise (Ultrasensitive).** If you are still seeing noisy data in xDrip+ you can apply more aggressive smoothing using the Smooth Sensor Noise (Ultrasensitive) setting. This will attempt to apply smoothing even on very low levels of detected noise. To do this, first enable [engineering mode](Enabling-Engineering-Mode-in-xDrip.md) in xDrip+. Then navigate to Settings > xDrip+ Display Settings and turn on Smooth Sensor Noise (Ultrasensitive). \ No newline at end of file diff --git a/docs/CROWDIN/pt/Usage/autotune_b.md b/docs/CROWDIN/pt/Usage/autotune_b.md deleted file mode 100644 index acd7b241961d..000000000000 --- a/docs/CROWDIN/pt/Usage/autotune_b.md +++ /dev/null @@ -1,186 +0,0 @@ -# How to use Autotune plugin - -Documentation about Autotune algorythm can be found in [OpenAPS documentation](https://openaps.readthedocs.io/en/latest/docs/Customize-Iterate/autotune.html). - -Autotune plugin is an implementation of OpenAPS autotune algorythm within AAPS. - -**Currently Autotune Plugin is only available in dev branch with Engineering mode.** - -## Autotune user interface - -![Autotune default screen](../images/Autotune/Autotune_1b.png) - -- You can select in the Profile dropdown menu the input profile you want to tune (by default your current active profile is selected) - - Note: each time you select a new profile, previous results will be removed and Tune days parameter will be set to default value -- Then Tune days is to select the number of days used in calculation to tune your profile. The minimum value is 1 day and the maximum value 30 days. This number should not be too small to get correct iterative and smooth results (above 7 days for each calculation) - - Note: each time you change Tune days parameter, previous results will be removed -- Last Run il a link that recover your latest valid calculation. If you didn't launch Autotune on current day, or if previous results was removed with a modification of calculation parameter above, then you can recover parameters and results of the latest successfull run. -- Warning show you for example some information about selected profile (if you have several IC values or several ISF values) - - Note: Autotune calculation works with only a single IC and a single ISF value. There is currently no existing Autotune algorythm to tune a circadian IC or circadian ISF. If your input profile has several values, you can see in warning section the average value taken into account to tune your profile. -- Check Input Profile button open the Profile Viewer to allow you a quick verification of your profile (Units, DAI, IC, ISF, basal and target) - - Note: Autotune will only tune your IC (single value), ISF (single value) and basal (with circadian variation). Units, DAI and target will remain unchanged in output profile. - -- "Run Autotune" will launch Autotune calculation with selected profile and the number of Tune days - - Note: Autotune calculation can take a long time. Once launched, you can switch to another view (home, ...) and come back later in Autotune plugin to see results - -![Autotune Run start](../images/Autotune/Autotune_2b.png) - -- Then during the run you will see intermediate results below - - - Note: During run, settings are locked, so you cannot change anymore selected input profile or the number of day. You will have to wait the end of current calculation if you want to launch another run with other parameters. - - ![Autotune during run](../images/Autotune/Autotune_3b.png) - -- When Autotune calculation is finished, you will see the result (Tuned profile) and four buttons below. - -![Autotune Result](../images/Autotune/Autotune_4b.png) - -- It's important to always compare input profile (column "Profile"), output profile (column "Tuned") and the percentage of variation for each value (Column "%"). - -- For basal rates, you also have the number of "missing days". You have missing days when Autotune don't have enough data categorized as "Basal" to tune basal rate for this period (for example after each meal when you have carbs absorption). This number should be as low as possible especially when basal is important (for example during the night or at the end of the afternoon) - -- The "Compare profiles" button open the profile comparator view. Input profile is in blue, and output profile (named "Tuned") is in red. - - - Note: in the example below input profile has circadian variation for IC and ISF, but output calculated profile has a single value. If it's important for you to get a circadian output profile see [Circadian IC or ISF profile](#circadian-ic-or-isf-profile) below. - - ![Autotune Compare profiles](../images/Autotune/Autotune_5.png) - -- If you trust results (low percentage of variation between input profile and output profile), you can click on "Activate profile" button and then click on OK to validated. - - - Activate Tuned profile will automatically create a new profile "Tuned" in your Local profile plugin. - - If you already have a profile named "Tuned" in your local profile plugin, then this profile will be updated with calculated Autotune profile before the activation - - ![Autotune Activate profile](../images/Autotune/Autotune_6.png) - -- If you think Tuned profile must be adjusted (for example if you think some variation are too important), then you can click on "Copy to local profile" button - - - A new profile with the prefix "Tuned" and the date and time of the run will be created in local profile plugin - -![Autotune Copy to local profile](../images/Autotune/Autotune_7.png) - -- You can then select local profile to edit the Tuned profile (it will be selected by default when you open Local profile plugin) - - - the values in local profile will but rounded in the user interface to your pump capabilities - - ![Autotune local profile update](../images/Autotune/Autotune_8.png) - -- If you want to replace your input profile with Autotune result, click on "Update input profile" button and validate the Popup with OK - - - Note: if you click on "Activate profile" after "Update input profile", then you will activate your updated profile and not the default "Tuned" profile? - - ![Autotune Update input profile](../images/Autotune/Autotune_9.png) - -- If you have updated your input profile, then the "Update input profile" button is replaced by "Revert input profile" button (see screenshot below). You can that way immediatly see if your current input profile in Local profile plugin already include the result of last run or not. You also have the possibility to recover you input profile without autotune result with this button - - ![Autotune Update input profile](../images/Autotune/Autotune_10.png) - - - -## Autotune settings - -### Autotune plugin settings - -![Autotune default screen](../images/Autotune/Autotune_11.png) - -- Automation Switch Profile (default Off): see [Run Autotune with an automation rule](#run-autotune-with-an-automation-rule) below. If you change this setting to On, the input profile will automatically be updated by the Tuned profile, and it will be activated. - - **Be Carefull, you must trust and verified during several following days that after an update and activation of Tuned profile without modification, it improves your loop** - -- Categorize UAM as basal (default On): This setting is for the users using AndroidAPS without any carbs entered (Full UAM). It will prevent (when Off) to categorize UAM as basal. - - Note: if you have at least one hour of Carbs absorption detected during one day, then all data categorized as "UAM" will be categorized as basal, whatever this setting (On or Off) -- Number of days of data (default 5): You can define default value with this setting. Each time your select a new profile in Autotune plugin, Tune days parameter will be replaced by this default value -- Apply average result in circadian IC/ISF (default Off): see [Circadian IC or ISF profile](#circadian-ic-or-isf-profile) below. - -### Outras configurações - -- Autotune also uses Max autosens ratio and Min autotsens ratio to limit variation. You can see and adjust these values in Config Builder > Sensitivity detection plugin > Settings > Advanced Settings - - ![Autotune default screen](../images/Autotune/Autotune_12.png) - - - -## Advanced feature - -### Circadian IC or ISF profile - -- If you have important variation of IC and/or you ISF in your profile, and you fully trust in your circadian time and variation, then you can set "Apply average result in circadiant IC/ISF" - - - Note that Autotune calculation will always be done with a single value, and circadian variation will not be tuned by Autotune. This setting only apply average variation calculated for IC and/or ISF on your circadian values - -- See on screenshot below Tuned profile with Apply average variation Off (on the left) and On (on the right) - - ![Autotune default screen](../images/Autotune/Autotune_13.png) - - - -### Tune specific days of the week - -- If you click on the checkbox with the eye on the right of "Rune days" parameter, you will see the day selection. You can specify which day of the week should be included in Autotune calculation (in screenshot below you can see an example for "working days" with Saturday and Sunday removed from autotune calculation) - - If the number of day included in Autotune calculation is lower than the number of Tune days, then you will see how many days will be included on the right of Tune days selector (10 days in the example below) - - This setting gives good results only if the number of remaining days is not to small (for example if you Tune a specific profile for week end days with only Sunday and Saturday selected, you should select a minimum of 21 or 28 Tune days to have 6 or 8 days included in Autotune calculation) - -![Autotune default screen](../images/Autotune/Autotune_14b.png) - -- During Autotune calculation, you can see the progress of the calculations ("Partial result day 3 / 10 tuned" on example below) - - ![Autotune default screen](../images/Autotune/Autotune_15b.png) - -## Run Autotune with an automation rule - -First step is to define correct trigger for an automation rule with Autotune: - -Note: for more information on how to set an automation rule, see [here](./Automation.rst). - -- You should select Recurring time trigger: only run Autotune once per day, and autotune is designed to be runned daily (each new run you shift one day later and quickly profile modification should be tiny) - - ![Autotune default screen](../images/Autotune/Autotune_16.png) - -- It's better at the beginning to run Autotune during the day to be able to check results. If you want to run Autotune during the night, you have to select in the trigger 4AM or later to include current day in next Autotune Calculation. - - ![Autotune default screen](../images/Autotune/Autotune_17.png) - -- Then you can select "Run Autotune" Action in the list - - ![Autotune default screen](../images/Autotune/Autotune_18.png) - -- You can then select Autotune Action to adjust parameters for your run. Default parameters are "Active Profile", default Tune days value defined in Autotune Plugin preferences, and All days are selected. - - ![Autotune default screen](../images/Autotune/Autotune_19b.png) - -- After a few days, if you fully trust Autotune results and percentage of modification is low, you can modify [Autotune settings](#autotune-plugin-settings) "Automation Switch Profile" to enabled to automatically update and activate profile tuned after calculation. - -Note: if you want to automatically tune profiles for specific days of the week (for example a profile for "Weekend days" and another one for "Working days"), then create one rule for each profile, select the same days in Trigger and in Autotune Action, Tune days must be high enough to be sure tuning will be done with at least 6 or 8 days, and don't forget to select time after 4AM in trigger... - -- See below an example of rule to tune "my profile" on all "Working days" with 14 Tune days selected (so only 10 days included in autotune calculation). - -![Autotune default screen](../images/Autotune/Autotune_20b.png) - - - -## Tips and trick's - -Autotune works with information existing in your database, so if you just installed AAPS on a new phone, you will have to wait several days before being able to launch Autotune with enough days to get relevant results; - -Autotune is just an help, it's important to regularly check if you agree with calculated profile. If you have any doubt, change Autotune settings (for example the number of days) or copy results in local profile and adjust profile before using it. - -Always use Autotune several days manually to check results before applyling them. And it's only when you fully trust Autotune results, and when variation becomes tiny between previous profile and calculated profile than you start to use Automation (Never before) - -- Autotune can work very well for some users and not for others, so **If you don't trust Autotune result, don't use it** - -It's also important to analyse Autotune results to understand (or try to understand) why Autotune propose these modifications - -- you can have a whole increase or decrease of the strength of your profile (for example increase of total basal associated to decrease of ISF and IC values). it could be associated to several following days with autosens correction above 100% (more agressivity required) or below 100% (you are more sensitive) -- Sometimes Autotune propose a different balance between basal rates and IC/ISF (for ex lower basal and more aggressive IC/ISF) - -We advise to not use Autotune in the following cases: - -- You don't enter all your carbs - - If you don't enter carbs correction for an hypoglycemia, Autotune will see an unexcepted increase of your BG value and will increase your basal rates the ' hours earlier, it could be the opposite of what you need to avoid hypo, especially if it's in the middle of the night. That's why it's important to enter all carabs especially correction for hypo. -- You have a lot of period with UAM detected during the day. - - Do you have entered all your carbs and correctly estimated your Carbs ? - - All UAM periods (except if you enter no carbs during a day and categorized UAM as basal is disabled), all your UAM periods will be categorized as basal, this can increase a lot your basal (much more than necessary) - -- Your carbs absorption is very slow: if most of your carbs absorption are calculated with min_5m_carbimpact parameter (you can see these periods with a little orange dot in the top of COB curve), the calculation of COB could be wrong and leads to wrong results. - - We you practice sport, you are generally more sensitive and your BG doesn't rise a lot, so during or after an exercice, it's usual to see some periods with slow carbs. But if you have too often unexpected slow carb absorption, then you may need a profile adjustment (higher value of IC) or a min_5m_carbimpact a bit to high. -- You have a "very bad days", for example stuck several hours in hyperglycemia with a huge amount of insulin to be able to go down within the range, or after a sensor change you got long periods of wrong BG values. -- If the percentage of modification is too important - - You can try to increase the number of days to get smoother results \ No newline at end of file diff --git a/docs/CROWDIN/pt/Usage/making-sport-with-AAPS.md b/docs/CROWDIN/pt/Usage/making-sport-with-AAPS.md deleted file mode 100644 index 79d2f1c38223..000000000000 --- a/docs/CROWDIN/pt/Usage/making-sport-with-AAPS.md +++ /dev/null @@ -1,185 +0,0 @@ -# making sport with AAPS - -In this section we want to address the topic of sport with AAPS. - -The aim is to show you how AAPS can help you to continue doing your favorite sport more easily or even to start doing it. It is relatively common for new type 1 diabetics to ask whether exercise is still possible for them, even if the answer in the training courses is actually a clear yes. Exercise is not only good for healthy people, but also for type 1 diabetics and even moderate exercise can even help to stabilize the blood sugar curve overall. - -:::{admonition} consult with your diabetes team after reading - -::: - -The difficulty here is that the prerequisites that someone brings with them and the expectations of what sport means to them are very different. - -Since we can assume that experienced top athletes with T1D who use AAPS are unlikely to look it up here, we deliberately set the bar low for ourselves when writing and for you when reading and using it, so that as many people as possible can benefit from it. - -Since even sport as a category is far too imprecise, as the effects of endurance sports differ greatly from strength training, for example, we are trying to break it down by type of sport. - -To be concrete and give you something you can test yourself we arrange the explanaiton around a concrete example and explain to you they action, reactions and effects. - -:::{admonition} more examples wanted - -The focus should always be on how others can do sport and not on the top performance someone has achieved. - -It's really about the basics. Your experience, which you share here, can help others to pursue their beloved sport more quickly and successfully and is therefore important. -::: - -## Cycling - -:::{admonition} take a friend with you - at least on your first trials -:class: information -A gerneral very good idea can be to take a good friend with you on the first rides. -This is especially important if you are not experienced in T1D. -Always keep in mind please: arrival comes before speed! Safety for you and the others in road traffic is very, very important. -::: - -### Example - -Let's take about 60 minutes of cycling on a flat route with a moderate heart rate as an example. - -1. we take a flat route in order to have an even load for the first exercise. This is not about performance, but purely about learning how you should react to changes in blood glucose. -2. we take the heart rate as an indicator of the load, as it is easy to see whether you are under load or not. -3. we set ourselves the goal of doing a relaxed lap around the neighborhood and focus on staying within our target range during the lap. In my case, this would be 70 <= x <= 180 mg/dl. - -We **don't** take the speed, as this is heavily dependent on personal physical conditions as well as the bike and surface used. It is therefore not very meaningful. - -You should know from the diabetes training courses you have attended that during endurance sports cycling, the insulin active in the body works significantly better than during times without physical exertion. The insulin active in the body is referred to as insulin on board (IoB). It is our most important parameter when cycling with T1D. - -We try to keep the IoB as low as possible at the start and during exercise. IoB should be around 0 or even slightly negative. You can get it there by not eating 3-4 hours before exercise. In the beginning it can also be helpful to exercise in the morning before breakfast, as with the right profile you should always have around 0 for IoB in the morning. - -AAPS shows us the IoB value on the home screen on the left under the blood glucose value. - -![IoB](../images/cycling_20240104-174035.png) - -:::{admonition} ignoring the IoB rule increases the risk for roller coaster BG dramatically -:class: danger -If you ignore this rule, you can still go cycling, but it will be much more difficult to keep your blood sugar levels in balance, so it is better to save this for later tests after several successful simple tests. -::: - -As you should know from the diabetes training courses, you should reduce the basal rate during exercise. The factor is individual. I have found a value of 50% in tests to be suitable for me. - -In AAPS, you should therefore change your profile to 50% before exercise and keep it active until the end of exercise. Some people even do it a certain amount of time before, e.g. 1 hour. Unfortunately, the pre-run is also individual. We will come to the post-run later. - -You should use two carbohydrates during exercise. - -1. medium-fast carbohydrates for the insulin still in the body and -2. very fast carbohydrates to prevent slipping into a hypo. - -For medium-fast carbohydrates, I treat myself to cookies or a banana before exercise, for example. You can also use something else that is more suitable for you. -For very fast carbohydrates, I take 3 teaspoons of dissolved glucose per 100 ml of still water in a 500 ml water bottle on my bike. If I'm cycling longer distances, I take a larger bottle with me and, if necessary, packaged glucose to refill the bottle. I add a little lemon juice for flavor. You can also use something other than lemon juice for the taste. You shouldn't change anything about the dextrose, as dissolved dextrose raises blood sugar levels super quickly. If you only take it in sips, your blood sugar won't go super high either! You can also do this tip at home beforehand as a dry run and see how quickly the change shows up on the CGMS. - -Why do I place so much emphasis on fast carbohydrates? - -1. once you are in a slight hypo, you may get back into the normal range by drinking the dextrose solution. As a rule, however, the oscillation of the curve then begins, which leads to a rollercoaster ride of the blood sugar. You may even be able to keep this within your target range, but you must be constantly vigilant. Without a hypo it is simply the most stable. -2. if you even slip into a somewhat severe hypo (without the need for outside help, of course), you may even have to pause briefly to avoid getting stuck in the hypo. - With both hypos, there is a risk that you will be tempted to switch from drinking 2-3 sips at a time to larger quantities. Not too bad at first, until the oscillation sets in and pushes you into a hyper. You can correct this, but your blood sugar will most likely go on a rollercoaster ride. - -What else is helpful, but not absolutely necessary? -It is important to keep an eye on your blood sugar, as your blood sugar can change enormously (e.g. 30 - 50 mg/dl) within 15 minutes of riding and a little more IoB or a basal rate that is still too high. The best way to keep an eye on it is if it is visible on the handlebars or if it is also displayed on your watch. It is even possible to install an additional app on some Garmin GPS bike computers that displays the blood glucose from XDrip or Nightscout as a data field on the bike computer. The additional app was developed by Andreas May from the T1D community. It is available free of charge in the official connect IQ Store. Certainly an interesting option for riders interested in sports. - -[Link to Andreas May Data Field App on connect IQ store](https://apps.garmin.com/de-DE/apps/5a3e2cda-12f0-4afd-88ed-000e67a68d84) - -Here is a picture of my Garmin Edge 530 bike computer with map, blood sugar and heart rate. - -![Garmin Edge 530 with BG data field](../images/cycling_IMG_1087.jpeg) - -After you have eaten the medium fast carbohydrates (24 - 36 g I take) and the blood sugar is above 100 mg/dl but also below 160 mg/dl, I carry out the profile change to 50% and set the activity temp target. - -:::{admonition} disable SMBs during high temp targets if necessary -:class: danger -Attention: If you prefer not to receive SMBs during the sport, please disable the option "Enable SMB with hight temp targets" in the settings of SMB or DynIFS Plugin. -::: - -The following picture shows the start and end of the sport. The end was specified as the duration when the profile was changed at the start. - -The temporary profile change has the following effects - -1. for a period of 60 minutes -2. a reduction to 50% of the profile and -3. the target is raised by clicking on the Activity Target option, which may have the side effect of disabling the SMBs - see above. - -![profile switch with temp target](../images/cycling_20240104-174056.png) - -The second image shows that the start at IoB was started towards 0. - -![IoB around 0](../images/cycling_20240104-174111.png) - -If the blood sugar drops faster than 15 mg/dl in 5 minutes or if it is at 120 mg/dl and tends to fall, I drink 1-2 sips of dissolved glucose. Then I wait for the next value and proceed as described above. - -You can hardly see it here, but at the beginning I took 2 sips from the bottle several times when my blood sugar started to fall. When it stabilized, I didn't need any more glucose. - -Here is the picture that illustrates this. The chart is saved on the Garmin as a result of the activity. - -![BG chart Garmin](../images/cycling_20240104-174431.png) - -If you should suddenly break out upwards, i.e. above 180 mg/dl, you should consider whether you should make a correction bolus. Caution: Remember the factor and apply it to the correction, otherwise the correction will be too strong. - -If your blood sugar drops below 80 mg/dl, take a break and drink two sips until your blood sugar is back above 100 mg/dl. - -At the end of the ride, the profile change should be finished as the time is up. - -Since we only rode easy for 60 minutes, there shouldn't be a big muscle bulking effect continuing to pull carbohydrates from your blood sugar. However, if it felt strenuous to you, keep an eye on it. This is especially true if you then go straight to bed. It may be better to change your profile to e.g. 80% for sleep. You may come out of sleep slightly too high, but it's better than having a hypo at night. Over time, you will surely find out what happens to you. - -The following pictures show the low intensity of the sport. - -The elevation profile -![](../images/cycling_20240104-174314.png) - -Speed with average and maximum speed - -![](../images/cycling_20240104-174326.png) - -Note the pause at the level crossing, which is also reflected in the heart rate. - -The heart rate. -![](../images/cycling_20240104-174337.png) - -The training effect. -![](../images/cycling_20240104-174358.png) - -The time in the different heart rate training zones. -![](../images/cycling_20240104-174423.png) - -After succesfully mastering this simple example you could go for further targets by stretching - -1. the distance and time -2. the load during the ride -3. the elevation during the right which should make a big impact on the more necessary carbs or further reduction of IoB and percentage of profile switch. - -Based on my experiences I would not expect to come back 100% with time in range over the whole and every ride. - -### Tipps - -I already gave some tipps for during the ride above. - -Here are some further tipps what can go wrong and how you can act to prevent it or react to compensate it. - -#### sky rocket high after ride - -During the ride everything was fine but after siting down and relax the blood sugar go sky rocket high. - -**Possible reason:** This happens when you have drunk too much dissolved glucose. - -**Reaction:** Drink 500 ml water, go to the shower and then control again. Latest after 30 minutes think about giving a correction bolus but be careful when it is short for bed time. Therefore it can be very good to make the first try runs on weekend mornings. - -**Action:** Next time be a bit more cautious in drinking from the dissolved glucose. - -#### hypo during ride - -During the ride you are going into hypo and can't recover your blood sugar during cycling. - -**Possible reason:** Your body cannot absorb enough carbohydrates quickly enough during exercise. - -**Reaction:** Take a rest and corrrect your blood sugar with drinking dissolved glucose. Stay calm: arrival comes before speed. - -**Action:** Did you started with IoB near 0? Have you eaten a small amount of middle fast carbs? Can you increase this or are the not fast enough for your body? Is it possible to prevent going into hypo by reducing the factor for the profile switch? Have you disbaled SMBs during ride as explained above? - -#### sky rocket high during ride - -During the ride your blood sugar goes sky rocket high. - -**Possible reason:** You have got taken too much carbs for your IoB at that time. Beneath for sure the typical technical problems with your -insulin pump like leakage or blockage of the catheder! - -**Reaction:** If it is too high for you take a rest and correct with a bolus. Keep in mind that you must ride home and therefore make it carefully. Drink 500 ml pure water without carbs. Stay calm: arrival comes before speed. - -**Action:** Have you eaten too much? Especially have you drunk too much from the dissolved glucose during the ride? Is your percentage of reduction the profile during profile switch too low and you can increase this? diff --git a/docs/CROWDIN/pt/buildingAAPS.md b/docs/CROWDIN/pt/buildingAAPS.md deleted file mode 100644 index 98164a09e49b..000000000000 --- a/docs/CROWDIN/pt/buildingAAPS.md +++ /dev/null @@ -1,28 +0,0 @@ -# Dummy - -## This is a dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - - -## This is another dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - - -## This is another another dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - diff --git a/docs/CROWDIN/pt/completingObjetives.md b/docs/CROWDIN/pt/completingObjetives.md deleted file mode 100644 index 98164a09e49b..000000000000 --- a/docs/CROWDIN/pt/completingObjetives.md +++ /dev/null @@ -1,28 +0,0 @@ -# Dummy - -## This is a dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - - -## This is another dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - - -## This is another another dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - diff --git a/docs/CROWDIN/pt/dummy.md b/docs/CROWDIN/pt/dummy.md deleted file mode 100644 index 98164a09e49b..000000000000 --- a/docs/CROWDIN/pt/dummy.md +++ /dev/null @@ -1,28 +0,0 @@ -# Dummy - -## This is a dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - - -## This is another dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - - -## This is another another dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - diff --git a/docs/CROWDIN/pt/intro.md b/docs/CROWDIN/pt/intro.md deleted file mode 100644 index 0d1e41729405..000000000000 --- a/docs/CROWDIN/pt/intro.md +++ /dev/null @@ -1,291 +0,0 @@ -![20-06-23v2 AAPS simple overview-cropped](https://github.com/openaps/AndroidAPSdocs/assets/94044064/e505b73b-09a0-42a4-a1ab-b830a0741234) - -# Introduction to APS and AAPS - -## What is an “Artificial Pancreas System”? - -A human pancreas does a lot of things besides regulating blood sugar. However, the term **“Artificial Pancreas System” (APS)** usually refers to a system which works to automatically keep blood sugar levels within healthy limits. - -The most basic way to do this is by detecting **glucose levels**, using these values to do **calculations**, and then delivering the (predicted) right amount of **insulin** to the body. It repeats the calculation, every few minutes, 24/7. It uses **alarms** and **alerts** to inform the user if intervention or attention is needed. This system is typically made up of a **glucose sensor**, an **insulin pump** and an **app** on a phone. - -You can read more about the different artificial pancreas systems currently in use and in development in this 2022 review article: - -![Frontiers](./images/FRONTIERS_Logo_Grey_RGB.png) [Future Directions in Closed-Loop Technology](https://www.frontiersin.org/articles/10.3389/fendo.2022.919942/full#:~:text=Fully%20closed%2Dloop%20systems%2C%20unlike,user%20input%20for%20mealtime%20boluses). - -In the near future, some so-called "dual-hormone" systems will also have the ability to infuse glucagon alongside insulin, with the aim of preventing severe hypos and allowing even tighter blood glucose control. - -An artificial pancreas can be thought of as an [“autopilot for your diabetes”]. (https://www.artificialpancreasbook.com/) What does that mean? In an aircraft, an autopilot does not do the complete job of the human pilot, the pilot cannot sleep through the entire flight. The autopilot aids the work of the pilot. It relieves them of the burden of permanently monitoring the aircraft, allowing the pilot to concentrate on wider monitoring from time to time. The autopilot receives signals from various sensors, a computer evaluates them together with the pilot’s specifications and then makes the necessary adjustments, alerting the pilot to any concerns. The pilot no longer has to worry about constantly making decisions. - -## What does hybrid closed loop mean? - -The best solution for type 1 diabetes would be a “functional cure” (probably an implant of pancreatic cells which are protected from the immune system). While we are waiting for that, a “full closed loop” artificial pancreas is probably the next best thing. This is a tech system that doesn’t need any user input (like bolusing insulin for meals, or announcing exercise), with good regulation of blood glucose levels. At the moment, there are no widely available systems which are “full” closed loop, they all need some user input. The currently available systems are called “hybrid” closed loop, because they use a combination of automated technology and user input. - -## How and why did looping start? - -The development of commercial technology for people with type 1 diabetes (T1D) is very slow. In 2013 the T1D community founded the #WeAreNotWaiting movement. They developed systems themselves using existing approved technology (insulin pumps and sensors) to improve blood glucose control, safety, and quality of life. These are known as DIY (do-it-yourself) systems, because they are not formally approved by health bodies (FDA, NHS etc). There are four main DIY systems available: OpenAPS, **AAPS**, Loop and iAPS. - -A great way to understand the fundamentals of DIY looping is to read Dana Lewis’s book “Automated Insulin Delivery”. You can access it \[here\] (https://www.artificialpancreasbook.com/) for free (or buy a hardcopy of the book). If you want to understand more about OpenAPS, which** AAPS** has developed from, the \[OpenAPS website\] (https://openaps.org/what-is-openaps/) is also a great resource. - -Several commercial hybrid closed loop systems have been launched, the most recent of which are \[CamAPS FX\] (https://camdiab.com/) (UK and EU) and \[Omnipod 5\] (https://www.omnipod.com/en-gb/what-is-omnipod/omnipod-5) (USA and EU). These are very different to DIY systems, mainly because they both include a “learning algorithm” which adjusts how much insulin is delivered according to your insulin needs from previous days. Many people in the DIY community have already tried out these commercial systems and compared them with their DIY system. You can find out more about how the different systems compare by asking on the dedicated Facebook groups for these systems, on the \[AAPS Facebook group\] (https://www.facebook.com/groups/AndroidAPSUsers/) or on \[Discord\] (https://discord.com/invite/4fQUWHZ4Mw). - -## What is Android APS (AAPS)? - -![image](https://github.com/openaps/AndroidAPSdocs/assets/94044064/0f089d96-b7ee-452a-aa9d-aae10ab58971) - -**Figure 1**. Basic outline of the Android APS (Artificial Pancreas System), AAPS. - -Android APS (AAPS) is a hybrid closed loop system, or Artificial Pancreas System (APS). It makes its insulin dosing calculations using established \[OpenAPS\] (https://openaps.org/) algorithms (a set of rules) developed by the #WeAreNotWaiting type 1 diabetes community. - -Since OpenAPS is only compatible with certain older insulin pumps, AAPS (which can be used with a wider range of insulin pumps) was developed in 2016 by Milos Kozak, for a family member with type 1 diabetes. Since those early days, **AAPS** has been continually developed and refined by a team of volunteer computer developers and other enthusiasts who have a connection to the type 1 diabetes world. Today, **AAPS** is used by approximately 10,000 people. It is a highly customisable and versatile system, and because it is open-source, it is also readily compatible with many other open-source diabetes softwares and platforms. The fundamental components of the current **AAPS** system are outlined in Figure 1 above. - -## What are the basic components of AAPS? - -The “brain” of AAPS is an **app** which you build yourself. There are detailed step-by-step instructions for this. You then install the **AAPS app** on a compatible **Android smartphone** (1). A number of users prefer their loop on a separate phone to their main phone. So, you don’t necessarily have to be using an Android phone for everything else in your life, just for running your AAPS loop. - -The **Android smartphone** will also need to have another app installed on it as well as **AAPS**, either a modified Dexcom app called build-your-own dexcom app (**BYODA**) or Xdrip+. This receives glucose data from a sensor (2) by bluetooth, and then sends the data internally on the phone to the **AAPS app**. - -The **AAPS app** uses a decision making process (**algorithm**) from OpenAPS. Beginners start out using the basic **oref0** algorithm, but it is possible to switch to using the newer **oref1** algorithm as you progress with AAPS. Which algorithm you use (oref0 or oref1), depends on which suits your specific situation best. In both cases, the algorithm takes into account multiple factors, and performs rapid calculations every time a new reading comes in from the sensor. The algorithm then sends instructions to the insulin pump (3) on how much insulin to deliver by bluetooth. All the information can be sent by mobile data or wifi to the internet. This data can also be shared with followers if desired, and/or collected for analysis. - -## What are the advantages of the AAPS system? - -The OpenAPS algorithm used by **AAPS** controls blood sugar levels in the absence of user input, according to the users’ defined parameters (important ones being basal rates, insulin sensitivity factors, insulin-to-carb ratios, duration of insulin activity etc.), reacting every 5 minutes to the new sensor data. Some of the reported advantages of using AAPS are extensive fine-tunable options, automations and increased transparency of the system for the patient/caregiver. This can result in better control over your (or your dependent’s) diabetes, which in turn may give improved quality of life and increased peace of mind. - -Practical advantages include: - -- **Hardware flexibility**: **AAPS** works with a wide range of insulin pumps and sensors. So for example, if you develop an allergy to Dexcom sensor patch glue, you could switch to using a Libre sensor instead. That offers flexibility as life changes. You don't have to rebuild, just tick a different box in the AAPS app to change your hardware. - -- **Highly customisable with wide parameters**: here are some examples of the possibilities with AAPS: a) The ability to set a lower glucose target 30 min before eating; you can set the target as low as 72 mg/dL (4.0 mmol/L). b) If you are insulin-resistant resulting in high blood sugars, **AAPS** allows you to set an **automation** rule to activate when BG rises above 8 mmol/L (144 mg/dL), switching to a 120% profile (resulting in an 20% increase in basal and strengthening of other factors too, compared to your normal **profile** setting). The automation will last according to the scheduled time you set. Such an automation could be set to only be active on certain days of the week, at certain times of day, and even at certain locations. c) If your child is on a trampoline with no advance notice, **AAPS** allows insulin suspension for a set time period, directly via the phone. d) After reconnecting a tubed pump which has been disconnected for swimming, AAPS will calculate the basal insulin you have missed while disconnected and deliver it carefully, according to your current BG. Any insulin not required can be overridden by just “cancelling” the missed basal. f) **AAPS** has the ability to set different profiles for different situations and easily switch between them. Features which make the algorithm quicker to bring down elevated BG (like supermicro boluses (“SMB”), unannounced meals, (“**UAM**”) can be set to only work during the daytime, if you are worried about night-time hypos. - - -These are all examples, the full range of features gives huge flexibility for daily life including sport, illness, hormone cycles etc. Ultimately, it is for the user to decide how to use this flexibility, and there is no one-size-fits-all automation for this. - -- **Remote monitoring**: there are multiple possible monitoring channels (Sugarmate, Dexcom Follow, Xdrip+, Android Auto etc.) which are useful for parents/carers and adults in certain scenarios (sleeping/driving) who need customisable alerts. In some apps (Xdrip+) you can also turn alarms off totally, which is great if you have a new sensor “soaking” or settling down that you don’t want to loop with yet. - -- **Remote control**: a significant advantage of **AAPS **over commercial systems is that it is possible for followers, using authenticated text (SMS) commands or via an app (Nightscout or NSClient) to send a wide range of commands back to the ****AAPS** **system. This is used extensively by parents of kids with type 1 diabetes who use AAPS. It is very useful in the playground, for example, if you want to pre-bolus for a snack from your own phone, and your child is busy playing. It is possible to monitor the system (e.g. Fitbit), send basic commands (e.g. Samsung Galaxy watch 4), or even run the entire AAPS system from a high-spec smartwatch (5) (e.g. LEMFO LEM14). In this last scenario, you don’t need to use a phone to run AAPS. As battery life on watches improves, this last option is likely to become increasingly attractive. - -- **No commercial constraints due to open application interfaces**: beyond the use of an open source approach, which allows the source code of **AAPS** to be viewed at any time, the general principle of providing open programming interfaces gives other developers the opportunity to contribute new ideas that allow users to live more easily with their diabetes. This is complementary to commercial systems which adopt the innovations from DIY, where interfaces are only made possible in return for licensing, thus preventing innovations in particular that are not-for-profit. Good examples for such integrations are NightScout, Nightscout Reporter, Xdrip+ M5 stack etc. - -- **Detailed app interface**: It is easy to keep track of things like: insulin levels, cannula age, sensor age, pump battery age, and many actions can be done through the **AAPS** app (priming the pump, disconnecting the pump etc.), instead of on the pump itself. - -- **Accessibility and affordability**: **AAPS** gives people who currently can’t afford to self-fund, or don’t have funding/insurance, access to a world-class hybrid closed looping system which is conceptually years ahead, in terms of development, of the commercial systems being offered by clinics. You currently need to have a Nightscout account to set up **AAPS**. Although the Nightscout account it not necessarily required after setup, many people continue to use Nightscout for collecting their data, and for remote control. So, although **AAPS **itself is free, setting up Nightscout through one of the various platforms may incur a fee (E0 - E12), depending on what level of support you want (see comparison table). **AAPS** works with a wide range of affordable (starting from approx E150) Android phones. In comparison, Loop currently costs around $80 a year for the Apple development licence and CamAPS FX costs around E80/month (as at 2023). - -- ****Support**: No automated insulin delivery system is perfect. Commercial and open-source systems share many common glitches in both communications and temporary hardware failure. There is a community of AAPS users on both Facebook and Discord and Github who designed, developed and are currently using **AAPS** all over the world. There are Facebook support groups and help from clinic/commercial companies for the commercial APS systems - it is worth speaking to the users, or former users of these systems to get feedback on the common glitches, the quality of the education programme and the level of ongoing support provided. - -- **Predictability, transparency and safety**: with no learning algorithm, **AAPS** is logical and in some respect, more predictable, which may make it easier to know when a setting is wrong, and to adjust it accordingly. You can see exactly what the system is doing, why it is doing it, and set its operational limits, which puts the control (and responsibility) in your hands. This can provide the user with confidence, and a sounder sleep. - -- **Access to advanced features through dev modes including full closed loop**: **AAPS **documentation focuses on the mainstream **“master”** branch of **AAPS**, however, research and development is going on all the time. More experienced users may wish to explore the experimental features in the **development** branch such as integration of Dexcom G7, and automatically adjusting insulin delivery according to short-term sensitivity changes (DYNISF), not having to bolus for meals, and generally trying to make life with type 1 diabetes as convenient as possible. - -- **Ability to contribute yourself to further improvements**: type 1 diabetes can be highly frustrating and isolating. Having control over your own diabetes tech, with the possibility to “pay it forward” as soon as you are making progress by helping others on their journey can be really rewarding. You can educate yourself, discover the roadblocks and look for and even contribute to new developments and the documentation. There will be others with the same quest to bounce ideas off and work with. This is the essence of #WeAreNotWaiting. - - -## How does AAPS compare to MDI and open looping? - -Multiple daily injections (MDI, a) usually involve giving an injection of a long-lasting insulin (e.g. Tresiba) once a day, with injections of faster-acting insulin (e.g. Novorapid, Fiasp) at mealtimes, or for corrections. Open pumping (b) involves using a pump to deliver basal at pre-programmed rates of rapid-acting insulin, and then boluses through the pump at mealtimes or for corrections. The basics of a looping system is that the App uses the glucose data to instruct the pump to stop insulin delivery when it predicts you are heading for a low, and to give you extra insulin if your glucose levels are rising and predicted to go too high (c). Although this is oversimplified, (mostly because hybrid closed looping has a lot of additional useful features) the key features of each system are shown in **Figure 2**. - -![image](https://github.com/openaps/AndroidAPSdocs/assets/94044064/4e7d8608-684d-4c69-9c61-88c9539f5d6f) - -**Figure 2**. Overview of (a) MDI, (b) open-loop pumping and (c) hybrid closed loop pumping - -## How does AAPS compare to other looping systems? - -At present there are four major open source closed loop systems available: OpenAPS, **AAPS**, \[Loop\] (https://loopkit.github.io/loopdocs/#what-is-loop) and iAPS, (formerly FreeAPS X). The features of the different systems are shown in the table below: - -| Devicestyp | Name | [Open APS](https://openaps.readthedocs.io/en/latest/) | [AAPS](https://wiki.aaps.app) | [Loop](https://loopkit.github.io/loopdocs/) | [iAPS](https://iaps.readthedocs.io/en/latest/) | -| ---------- | -------------------------------------------------------------------------------------------------------- | ----------------------------------------------------- | ------------------------------------------- | ------------------------------------------- | ---------------------------------------------- | -| PUMP | Older Medtronic | ![available](./images/available.png) | ![available](./images/available.png) | ![available](./images/available.png) | ![available](./images/available.png) | -| PUMP | Older Omnipod (Eros) | ![unavailable](./images/unavailable.png) | ![available](./images/available.png) | ![available](./images/available.png) | ![available](./images/available.png) | -| PUMP | Newer Omnipod (Dash) | ![unavailable](./images/unavailable.png) | ![available](./images/available.png) | ![available](./images/available.png) | ![available](./images/available.png) | -| PUMP | DANA R, DANA RS, DANA I | ![unavailable](./images/unavailable.png) | ![available](./images/available.png) | ![unavailable](./images/unavailable.png) | ![unavailable](./images/unavailable.png) | -| PUMP | Roche Combo, Insight | ![unavailable](./images/unavailable.png) | ![available](./images/available.png) | ![unavailable](./images/unavailable.png) | ![unavailable](./images/unavailable.png) | -| CGM | Dexcom G4, G5, G6 | ![available](./images/available.png) | ![available](./images/available.png) | ![available](./images/available.png) | ![available](./images/available.png) | -| CGM | Libre 1 (requires Miao Miao) | ![available](./images/available.png) | ![available](./images/available.png) | ![available](./images/available.png) | ![available](./images/available.png) | -| CGM | Libre 2 | ![available](./images/available.png) | ![available](./images/available.png) | ![available](./images/available.png) | ![available](./images/available.png) | -| CGM | Libre 3 | | ![unavailable](./images/unavailable.png) | --- | ![unavailable](./images/unavailable.png) | -| CGM | Medtronic Enlite | | --- | ![unavailable](./images/unavailable.png) | --- | -| CGM | [Dexcom G7](https://androidaps.readthedocs.io/en/latest/Hardware/DexcomG7.html) | | ![available](./images/available.png) (beta) | ![available](./images/available.png) | ![available](./images/available.png) | -| CGM | [Eversense](https://androidaps.readthedocs.io/en/latest/Hardware/Eversense.html) | | ![available](./images/available.png) | | ![available](./images/available.png) | -| CGM | [MM640g/MM630g](https://androidaps.readthedocs.io/en/latest/Hardware/MM640g.html) | | ![available](./images/available.png) | | ![available](./images/available.png) | -| CGM | [PocTech](https://androidaps.readthedocs.io/en/latest/Hardware/PocTech.html) | | ![available](./images/available.png) | | ![available](./images/available.png) | -| CGM | [Nightscout as BG Source](https://androidaps.readthedocs.io/en/latest/Hardware/CgmNightscoutUpload.html) | | ![available](./images/available.png) | | ![available](./images/available.png) | -| Phone | Android | ![available](./images/available.png) | ![available](./images/available.png) | ![unavailable](./images/unavailable.png) | ![unavailable](./images/unavailable.png) | -| Phone | iPhone | ![available](./images/available.png) | ![unavailable](./images/unavailable.png) | ![available](./images/available.png) | ![available](./images/available.png) | - -[OpenAPS](https://openaps.readthedocs.io/) was the first Open Source Closed Loop System. Ele usa um pequeno computador como Raspberry Pi ou Intel Edison. Both AndroidAPS (AAPS) and iAPS use the OpenAPS algorithms, whereas Loop uses a separate algorithm. You can read a comparison of iAPS and **AAPS** here. - -An international peer-reviewed consensus statement containing practical guidance on open source looping was written by and for health-care professionals, and published in a leading medical journal in 2022. It is well worth a read (including for your diabetes clinic) and summarises the main technical differences between the different open-source hybrid closed loop systems: - - Lancet Diabetes Endocrinol, 2022; 10: 58–74 - -[https://www.ncbi.nlm.nih.gov/pmc/articles/PMC8720075/](https://www.ncbi.nlm.nih.gov/pmc/articles/PMC8720075/) - -It is hard to get a “feel” for any system without using it, or talking to others who are using it, so do reach out to others on Facebook/Discord and ask. Most people find that AAPS is incredibly sophisticated in comparison to other hybrid closed loop systems (particularly the commercial systems), with a huge number of potentially customisable settings and features, discussed above. Some people can find this a little overwhelming in the beginning, but there is no rush to investigate all the possibilities at once, you can progress as slowly or as fast as you would like, and there is help available at every step of the way. - -## Does AAPS use artificial intelligence or any learning algorithm? - -Não. **AAPS** does not have any complicated machine learning algorithms, multiple-parameter insulin response models, or differential equations. As such, the system is open and transparent in how it works, and has the ability to be understood not just by experts, but also by clinicians and patients. It also means that if you have a sharply varying schedule (maybe switching from a stressful week at work to a relaxing holiday) and are likely to need a significantly different amount of insulin, you can immediately switch **AAPS** to run a weaker/stronger profile. A ‘learning system’ will do this adjustment for you automatically, but is likely to take longer to adjust the insulin delivery. - -## Which system is right for me or my dependent? - -Practically, your choice of system is often restricted by which pump you already have, or can obtain from your medical provider, and your choice of phone (Apple or Android). If you don’t yet have a pump you have the biggest choice of systems. Technology is continually evolving, pumps are being discontinued and new pumps and sensors are being released. Most open-source systems work with the main sensors (Libre and Dexcom) or are quickly adapted to work with new sensors a year or so after they are released (with a bit of time delay for safety and stability testing). - -Most **AAPS **users report more time in range, HbA1c reductions, as well as quality of life improvements from having a system that can auto-adjust basal rates overnight during sleep, and this is true for most hybrid closed loop APS. Some people have a preference for a very simple system which is not very customisable (which means you may prefer a commercial system), and others find this lack of control very frustrating (you may prefer an open-source system). If you (or your dependent) are newly diagnosed, a common route is to get the hang of MDI plus sensor first, then progress to a pump which has the potential for looping, then to **AAPS**, but some people (especially small kids) may go straight to a pump. - -It is important to note that the **AAPS** user needs to be proactive to troubleshoot and fix problems themselves, with help from the community. This is a very different mindset to that when using a commercial system. With **AAPS** a user has more control, but also the responsibility, and needs to be comfortable with that. - -## Is it safe to use open-source systems like AAPS? - -A more accurate question is probably “is it safe compared to my current type 1 diabetes insulin delivery system?” since no method of insulin delivery is without risk. There are many checks and balances in place with **AAPS**. A recent paper looked at the use of**** AAPS ****in a computer simulated set-up, [https://www.liebertpub.com/doi/epub/10.1089/dia.2019.0375](https://www.liebertpub.com/doi/epub/10.1089/dia.2019.0375) which was an effective way to unobjectively trial how safe and effective the system is. More generally, it is estimated that over 10,000 individuals worldwide are using open-source automated-insulin delivery systems, and uptake continues to increase globally. - -Any device that uses radio communications could be hacked, and this is true for a non-looping insulin pump as well. Currently, we are not aware of anyone attempting to harm individuals by hacking their diabetes-related medical equipment. However, there are multiple ways to protect against such risks: - -1. In the pump settings, limit both the max bolus allowed and max temporary basal settings to amounts that you believe are safest. These are hard limits that we do not believe any malicious hacker could circumvent. - -2. Set your CGM alarms enabled for both highs and lows. - -3. Monitor your insulin delivery online. Nightscout users can set additional alarms to alert for a wide variety of conditions, including conditions that are much more likely to occur than a malicious attack. In addition to highs and lows, Nightscout can display diagnostic data useful for verifying that the pump is operating as desired, including current IOB, pump temporary basal history, pump bolus history. It can also be configured to proactively alert users to undesirable conditions, such as predicted highs and lows, low insulin reservoir, and low pump battery. - - -If a malicious attack was made on your insulin pump, these strategies would significantly mitigate the risk. Every potential **AAPS** user needs to weigh the risks associated with using **AAPS**, versus the risks of using a different system. - -## How can I approach discussing AAPS with my clinical team? - -Depending on the country - link to doctors section of docs - - Lancet Diabetes Endocrinol, 2022; 10: 58–74 - -[https://www.ncbi.nlm.nih.gov/pmc/articles/PMC8720075/](https://www.ncbi.nlm.nih.gov/pmc/articles/PMC8720075/) - -## Q: Why can’t I just download AAPS and use it straight away? - -The **AAPS** app is not provided in Google Play - you have to build it from source code by yourself for legal reasons. **AAPS** is unlicensed, meaning that it does not have approval by any regulatory body authority in any country. **AAPS**is deemed to be carrying out a medical experiment on yourself, and is carried out at the user’s own risk. - -Setting up the system requires patience, determination and the gradual development of technical knowledge. All the information and support can be found in these documents, elsewhere online, or from others who have already done it. It is estimated that over 2000 people have successfully built and are currently using **AAPS** worldwide. - -The developers of **AAPS**t ake safety incredibly seriously, and want others to have a good experience of using **AAPS**. That is why it is essential that every user (or carer, if the user is a child): - -- builds the AAPS system themself and works through the **objectives** so that they have reasonably good personalised settings and understand the basics of how AAPS ****works by the time they “close the loop”; - -- backs up their system by exporting and saving important files (like keystore and settings .json file) somewhere safe, so you can setup again quickly if needed; - -- updates to newer master versions as and when they become available; and - -- maintains and monitors the system to ensure it is working properly. - - -## Q: What is the connectivity of the AAPS system? - -**Figure 3 (below)** shows one example of the **AAPS** system for a user who do not require any followers interacting with the system: - -![potential AAPS connectivity setup with no followers](./images/intro03.png) - -**Figure 4 (below)** shows the full potential of the **AAPS** system for a user who has followers and requires a monitor and send adjust the system remotely (like a child with T1D): - -![potential AAPS connectivity setup with followers](./images/intro04.png) - -## Q: How does AAPS get continually developed and improved? - -Most **AAPS** users use the fully tested **master** version of AAPS, which has been tested for bugs and problems, before being released to the community. Behind the scenes, the developers try out new improvements, and test these out in “developer” (**dev**) versions of **AAPS** with a user community who are happy to do bug updates at short notice. If the improvements work well, they are then released as a new “master” version of **AAPS**. Any new master release is announced on the Facebook group, so that the mainstream **AAPS** users can read about and update to the new master version. - -Some experienced and confident **AAPS ** users conduct experiments with emerging technologies and with dev versions of the **AAPS** app, which can be interesting for the less adventurous users to read about, without having to do it themselves! People tend to share these experiments on the Facebook group too. - -You can read more about some of these experiments and discussion on emerging tech here: - -[https://www.diabettech.com/](https://www.diabettech.com/) - -[https://bionicwookie.com/](https://bionicwookie.com/) - -## Q: Who can benefit? - -| User Type | -| ------------------------------------------- | -| ✔️ type 1 diabetic | -| ✔️ caregiver or parent of a type 1 diabetic | -| ✔️ blind users type 1 diabetic | -| ✔️ *clincians and healthcare professionals | - -The above table assumes that the user has access to both continuous gluocse monitor and insulin pump. - -*All data from **AAPS** can be made available to healthcare professionals via data sharing platforms, including NightScout that provides logging and real time monitoring of CGM data, insulin delivery, carbohydrate entries, predictions and settings. Nightscout records include daily and weekly reports which can aid healthcare professionals' discussions with type 1 patients with more accurate data on glycemic control and any behavioural considerations. - -## Q: What benefits can I get? - -With investment of your time, **AAPS** can potentially lead to: - -- alleviating the stress and burden of managing type 1 diabetes; - -- reducing the multitude of mundane decisions that arise from type 1 diabetes; - -- the provision of personalised and dynamic insulin dosing based on real-time data which can cut down the need for hypo treatments and reduce hyperglycemia episodes; - -- an increased knowledge of insulin management and confidence to better fine tune your settings; - -- the ability to create automatic settings (**automations**) that are tailored to fit in with your lifestyle; - -- improved sleep quality and overall reduction in the frequency of nighttime interventions; - -- remote monitoring and administration of insulin delivery for caregivers of type 1 diabetics; and - -- streamlining of all your portable diabetic equipment (continuous glucose monitor and insulin portable devices) by replacing them with an android phone controlled by **AAPS**. - - -Ultimately,**AAPS** can empower individuals to better manage their diabetes resulting in stable blood sugars and improved long term health outcomes. - ---- - -## AAPS First Steps - -Welcome. This is an introduction to aid beginners getting started with **AAPS** (or commonly referred to as "looping"). - -## Safety - -“_With great powers comes great responsibilities…_” - -**AAPS** is designed with an extensive set of safety features with limits imposed and gradually removed with completion of the **objectives **(predominately made up of multiple choice questions). An **AAPS** feature will be unlocked as the Objectives are successfully completed. This process will gradually allow the user to migrate from Open Loop to Closed Loop. - -This has been done to achieve the best possible experience with **AAPS** in order to prevent common mistakes that new users tend to make when starting to loop. The safety parameters have been built upon typical errors and general trends **AAPS** developers have observed with new users. Mistakes can happen because the beginner is inexperienced and too eager to get started with AAPS or has overlooked the required materials. Do not worry, we have all been there! - -## Key Principles - -The key principles and concepts of looping must be understood by the user before using **AAPS**. This is achieved by investing your personal time into reading the **AAPS** documentation, and completing the Objectives which is aimed to provide you with a solid platform for safe and effective use of **AAPS**. The volume of **AAPS** documentation may seem overwhelming at first but be patient and trust the process - with the proper approach, you'll get there! The overall process will depend upon the beginner’s progress and completion of objectives can typically take between 6 to 9 weeks . - -## Plan for hiccups - -At the preliminary stages of **AAPS**, you should expect to experience some hiccups whilst trying to fine tune your settings. **AAPS**’ glitches cannot be flushed out until the system is used in everyday life. Please plan accordingly and allow a sensible amount of time to troubleshoot and resolve such issues. - -## Flexibility/Adaptability - -Success with **AAPS** requires a proactive approach, a willingness to reflect on the BG data and flexibility to make the necessary adjustments to **AAPS** in order to improve your outcomes. Just as it is nearly impossible to learn to play a sport by reading about the rules alone, the same can be said of **AAPS**. - -## Technology compatibility - -There are limitations with **AAPS** as it is accessible for only certain types of insulin pumps or CGMs, and some technology may not be available for use in various countries. In order to avoid any disappointment or frustrations, please read please read Component Set Up (Section INSERT). - -## App Build Time - -The time to build the **AAPS**(under Section INSERT) depends on your level of expertise and technical ability. Typically for inexperienced users, it can take up to half a day or a full day (with help from the community) in order to build the **AAPS**. The process will significantly speed up as you become more experienced at building the **AAPS**. To aid the build process there are sections dedicated for: -- list of questions and answers for frequent errors that are likely to occur under FAQs (Section K); -- “How to install AAPS? (Section INSERT) which includes Troubleshooting subsection. - -## Keystore & configurations settings a export file - -A “keystore” is a password encrypted file unique to your own copy of **AAPS**. Your android phone uses it to ensure that nobody else can upgrade your own copy without the keystore. In short, as part of the **AAPS** build, you should: - -- save the your keystore file (.jks file used to sign your app) in a safe place; -- keep a note of your password for your keystore file. - -By doing the above, this will ensure that you can use that exact same keystore file each time an updated version of **AAPS** is created. On average, there will be 2-3 AAPS updates required each year. - -In addition, **AAPS** provides the ability to export all your configuration settings. This ensures that you can safely recover your system while changing phones, upgrading/reinstalling the application with minimum disruption. - -## Troubleshootng - -Please feel free to reach out to the AAPS community if there is anything you feel unsure about - there is no such thing as a silly question! All users with various levels of experience are encouraged to ask questions as necessary. Response times to questions are usually quick, typically only a few hours due to the volume of **AAPS** users. - -a) check the documentation; b) ask AAPS facebook group (https://www.facebook.com/groups/AndroidAPSUsers); and c) ask our discord channel. - -## Section overview - -AAPS documentation is made up of the following Sections: - -[INSERT ONCE SECTIONS /SUB SECTIONS AGREED] ---- diff --git a/docs/CROWDIN/pt/maintaining.md b/docs/CROWDIN/pt/maintaining.md deleted file mode 100644 index 98164a09e49b..000000000000 --- a/docs/CROWDIN/pt/maintaining.md +++ /dev/null @@ -1,28 +0,0 @@ -# Dummy - -## This is a dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - - -## This is another dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - - -## This is another another dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - diff --git a/docs/CROWDIN/pt/optimizing.md b/docs/CROWDIN/pt/optimizing.md deleted file mode 100644 index 98164a09e49b..000000000000 --- a/docs/CROWDIN/pt/optimizing.md +++ /dev/null @@ -1,28 +0,0 @@ -# Dummy - -## This is a dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - - -## This is another dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - - -## This is another another dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - diff --git a/docs/CROWDIN/pt/prepairing.md b/docs/CROWDIN/pt/prepairing.md deleted file mode 100644 index 3d6c53e03e96..000000000000 --- a/docs/CROWDIN/pt/prepairing.md +++ /dev/null @@ -1,145 +0,0 @@ -# Prepairing - -## Guide to the Android APS doc - -### First Steps -Welcome. This is an introduction to aid beginners to the concept of Do-It-Yourself-APS (Android-Artificial-Pancreas-Systems “AAPS”) is commonly referred to as ‘looping’.. - -#### Safetys -“With great powers come great responsibilities…” - -AAPS is designed with an extensive set of safety features with limits imposed and gradually removed with completion of the [Objectives](https://androidaps.readthedocs.io/en/latest/Usage/Objectives.html) (predominately made up of multiple choice questions). An AAPS feature will be unlocked as the Objectives are successfully completed. This process will gradually allow the user to migrate from Open Loop to Closed Loop. - -This has been done to achieve the best possible experience with AAPS by preventing common mistakes new users tend to make when starting to loop. The safety parameters have been built upon typical errors and general trends AAPS developers have observed with new users. Mistakes can happen because the beginner is inexperienced and too eager to get started with AAPS or has overlooked the required materials. Do not worry, we have all been there! - -#### Key Principles - -The key principles and concepts of looping must be understood by the user before using AAPS. This is achieved by investing your personal time into reading the AAPS documentation, and completing the [Objectives](https://androidaps.readthedocs.io/en/latest/Usage/Objectives.html) which is aimed to provide you with a solid platform for safe and effective use of AAPS. The volume of AAPS documentation may seem overwhelming at first but be patient and trust the process - with the proper approach, you'll get there! The overall process will depend upon the beginner’s progress and completion of objectives which typically take between 6 to 9 weeks . - -#### Plan for hiccups - -At the preliminary stages of AAPS, you should expect to experience some hiccups whilst trying to fine tune your settings. AAPS’ glitches cannot be flushed out until the system is used in everyday life. Please plan accordingly and allow a sensible amount of time to troubleshoot and resolve such issues. - -#### Flexibility/Adaptability - -Success with AAPS requires a proactive approach, a willingness to reflect on the BG data and flexibility to make the necessary adjustments to AAPS in order to improve your outcomes. Just as it is nearly impossible to learn to play a sport by reading about the rules alone, the same can be said of AAPS. - -#### Technology compatibility -There are limitations with AAPS as it is accessible for only certain types of insulin pumps or CGMs, and some technology may not be available for use in various countries. In order to avoid any disappointment or frustrations, please read [Component Set Up (Section E).](https://androidaps.readthedocs.io/en/latest/Configuration/BG-Source.html) - -#### App Build time -The time to build the AAPS (under Section D) depends on your level of expertise and technical ability. Typically for inexperienced users, it can take up to half a day or a full day (with help from the community) in order to build the AAPS. The process will significantly speed up as you become more experienced at building the AAPS.  - -To aid the build process there are sections dedicated for: - -- list of questions and answers for frequent errors that are likely to occur under [FAQs (Section](https://androidaps.readthedocs.io/en/latest/Getting-Started/FAQ.html) K); - -- “[How to install AAPS](https://androidaps.readthedocs.io/en/latest/Installing-AndroidAPS/Building-APK.html)? (Section D) which includes [Troubleshooting](https://androidaps.readthedocs.io/en/latest/Usage/troubleshooting.html) subsection. - - -#### Keystore & configuration settings export  file - -A “keystore” is a password encrypted file unique to your own copy of AAPS. Your android phone uses it to ensure that nobody else can upgrade your own copy without the keystore.In short, as part of the AAPS build, you should: - -1. save the your keystore file (.jks file used to sign your app) in a safe place; - -2. keep a note of your password for your keystore file. - - -By doing the above, this will ensure that you can use that exact same keystore file each time an updated version of AAPS is created. On average, there will be 2-3 updates to the AAPS required each year. In addition, AAPS provides the ability to [export all your configuration settings](https://androidaps.readthedocs.io/en/latest/Usage/ExportImportSettings.html). This ensures that you can safely recover your system while changing phones, upgrading/reinstalling the application with minimum disruption.  - -#### Resolução de Problemas - -Please feel free to reach out to the AAPS community if there is anything you feel unsure about - there is no such thing as a silly question!  All users with various levels of experience are encouraged to ask questions as necessary. Response times to questions are usually quick, typically only a few hours due to the volume of AAPS users.  - -##### [check the documentation](https://androidaps.readthedocs.io/en/latest/index.html) - -##### [ask our facebook group](https://www.facebook.com/groups/AndroidAPSUsers/) - -##### [ask our discord channel](https://discord.com/channels/629952586895851530/629954570394533889) - -#### Section overview - -AAPS documentation is made up of the following Sections: - -##### [Getting started](https://androidaps.readthedocs.io/en/latest/Getting-Started/Safety-first.html) - -This is a must read to understand the general concept of what an artificial pancreas system is designed to do. - -##### [What do I need?](https://androidaps.readthedocs.io/en/latest/Module/module.html) - -This explains AAPS’ compatibility with CGMs (Continuous Glucose Monitors) and insulin pumps. It also provides a guide on the correct assembly of an AAPS system to ensure that it functions correctly in everyday life. - -##### How to install AAPS - -This section is the manual for building the AAPS. Strict adherence to the step-by-step instructions are required in order to successfully build the AAPS. Please take your time. - -##### [Component Setup](https://androidaps.readthedocs.io/en/latest/Configuration/BG-Source.html) - -This explains how to properly integrate each of the various different separate component parts into AAPS, as well as how to set them up to work as seamlessly as possible together. All components are listed under the separate sections: CGM/FGM, xDrip Settings, Pumps, Phones, Nightscout setup, and Smartwatches. The sensor (BG) values and control of the insulin pump are particularly important information to understand. - -##### Configuration - -This explains how to set and configure your ‘Profile’, ‘Insulin’, ‘BG Source’, ‘Pump’, ‘Sensitivity Detection’, ‘APS’, ‘Loop’, ‘Treatments’. - -##### AAPS Usage - -This section provides a breakdown of the features provided by AAPS. - -##### [General Hints](https://androidaps.readthedocs.io/en/latest/Usage/Timezone-traveling.html) - -Useful tricks on how to tackle looping issues such as time zones, and daylight saving (i.e. Spring Forward/ - Fall Back). - -##### [AAPS](https://androidaps.readthedocs.io/en/latest/Getting-Started/Screenshots.html) for Children - -This is designed for parents or caregivers who want to build an AAPS for their child. It also explains the extra features necessary in order to support and safely control your child’s AAPS remotely.

The concepts in this section should be fully understood in order to competently use this feature. - -##### Resolução de Problemas - -This section contains links to help solve issues when building or using AAPS. - -##### FAQ - -This section addresses specific questions which tend to come up when building or using AAPS. - -##### [Glossário](https://androidaps.readthedocs.io/en/latest/Getting-Started/Glossary.html) - -This contains a list of the acronyms (or short-term names) or defined terms developed specifically for AAP (for instance, the terms ‘ISF’ or ‘TT’ have special meanings in AAPS). - -##### [Where to go for help](https://androidaps.readthedocs.io/en/latest/Where-To-Go-For-Help/Background-reading.html)? - -This section is aimed to provide new users with links on resources in order to get help including accessing community support made up of both new and experienced users who can clarify questions, and resolve the usual pitfalls that come with AAPS. - -##### For Clinicians - -This is a section for the clinicians who have expressed interest in open source artificial pancreas technology such as AAPS, or for patients who want to share such information with their clinicians. | - -## what are we going to build? - -### An Android Phone Application - -At the core, AAPS is an android application running from a phone. You are going to build it from scratch by installing tools to download the sourcecode and build the actual application. - -### A reporting server NightScout (or Tidepool) - -In order to fully use AAPS properly you will want to setup a nightscout server. It is used to collect data from AAPS over time and possibly communicate to the application. It is required for parents who want to oversee their children AAPS sessions. It is also key to share data between clinicians and patients to perform analysis over time. - -## How long will it take? - -## Who might AAPS not be suitable for? - -## Where can I get help? - -## Requirements - -### medical - -### technical - -### personal - -### CGMs - -### Insulin Pump - -### Reporting (NS, Tidepool) \ No newline at end of file diff --git a/docs/CROWDIN/ro/Configuration/Dexcom.md b/docs/CROWDIN/ro/Configuration/Dexcom.md deleted file mode 100644 index cb267e23c069..000000000000 --- a/docs/CROWDIN/ro/Configuration/Dexcom.md +++ /dev/null @@ -1,32 +0,0 @@ -# Dexcom G6 - -## Basics first - -* Follow [general CGM hygiene recommendations](../Configuration/BG-Source#cgm-hygiene) -* [Special recommendations for Dexcom G6 and DIY systems](../Configuration/BG-Source#dexcom-g6-diy-systems) *For G6 transmitters manufactured after fall/end of 2018 please make sure to use one of the [latest nightly built xDrip+ versions](https://github.com/NightscoutFoundation/xDrip/releases). Those transmitters have a new firmware and latest stable version of xDrip+ (2019/01/10) cannot deal with it. - -## Setting sensor - -When setting sensor, it is recommended not to press the inserter too firmly in order to avoid bleeding. The sensor thread should not come into contact with blood. - -After setting the sensor, the transmitter can be clicked into the sensor holder. Caution! First click in the square side and then press down the round side. - -## Troubleshooting - -### Connection problems - -Bluetooth connection may be disturbed by other nearby Bluetooth devices such as blood glucose meters, headsets, tablets or kitchen devices such as microwave ovens or ceramic hobs. In this case xdrip does not display any BG values. When bluetooth connection is reestablished the data is backfilled. - -### Sensor Errors - -If recurring sensor errors occur try selecting a different body site to set your sensor. The sensor thread should not come into contact with blood. - -Often a "Sensor Error" can be corrected by immediate drinking and massage around the sensor! - -### Jumpy values - -You might try to change settings for noise blocking in xdrip (Settings - Inter-App Settings - Noise Blocking) i.e. "Block Very High noise and worse". See also [Smoothing BG data](../Usage/Smoothing-Blood-Glucose-Data-in-xDrip.md). - -### New transmitter with running sensor - -If you happen to change transmitter during a running sensor session you might try to remove the transmitter without damaging the sensor mount. A video can be found at . \ No newline at end of file diff --git a/docs/CROWDIN/ro/Configuration/EOFLOW.md b/docs/CROWDIN/ro/Configuration/EOFLOW.md deleted file mode 100644 index 2a24d8a6f55a..000000000000 --- a/docs/CROWDIN/ro/Configuration/EOFLOW.md +++ /dev/null @@ -1,155 +0,0 @@ -# EOPatch2 Instruction Manual - -The patch requires the use of rapid-acting U-100 type insulin, such as NovoRapid or Humalog. Use a rapid-acting insulin that is suitable for you according to your doctor’s prescription and inject the prescribed dosage. - -The smallest injectable dose of insulin when using the patch is 0.05 U. The Profile BAS should therefore be set at a minimum value of 0.05 U/hr or more and an interval of 0.05 U/hr, as otherwise there may be an error between the estimated total infusion amount in the Profile and the actual infusion amount in the patch. Likewise, the bolus must also be set and infused with a minimum infusion volume of 0.05 U. - -## Pump Setup -1. On the AndroidAPS home screen, click the hamburger menu in the upper left corner and go to Config Builder. -1. Select 'EOPatch2' in the Pump section. -1. Press the Back key to return to the home screen. - -![Bild1](../../images/EOPatch/Bild1.png) ![Bild2](../../images/EOPatch/Bild2.png) - -## Setări -Select EOPATCH2 at the top of the home screen to go to the EOPATCH2 tab. - -Select the EOPatch2 Preferences menu by clicking the three dots in the upper right corner. - -The EOPatch2 Preferences menu offers a menu to set 3 types of notifications. - -### Low reservoir Alerts -A warning appears when the amount of insulin remaining in the reservoir reaches the set value or less while using the patch. It can be set from 10 to 50U in 5U increments. - -### Patch expiration Reminder -This is a reminder to notify you of the time remaining before the current patch expires. It can be set from 1 to 24 hours in 1 hour increments. The initial setting value is 4 hours. - -### Patch buzzer Reminder -This is a reminder function for injections other than basal injection. If you are using an (extended) bolus injection or a temporary basal injection, the patch will make a buzzer sound when the injection starts and when the injection is complete. The initial setting value is Off. - -![Bild3](../../images/EOPatch/Bild3.png) - -## Connecting the Patch - -### Move to patch connection screen - -Select EOPATCH2 at the top of the home screen and click the ACTIVATE PATCH button at the bottom left. - -![Bild4](../../images/EOPatch/Bild4.png) - -### Connecting the patch -Insert the syringe needle into the insulin inlet on the patch and then slowly push the piston to inject the insulin. When insulin is filled with more than 80U, the patch makes a booting sound (1 buzzer) and boots. After confirming the buzzer sound, click the START PAIRING button on the screen. - -[Warning] - -- Do not turn the needle action lever until instructed. It can cause serious problems during injection or safety checks otherwise. -- The amount of insulin that can be injected into the patch is 80~200U. If you inject less than 80U into the patch initially, the patch will not work. -- Take the insulin to be put into the patch from the refrigerator and leave it at room temperature for 15 to 30 minutes beforehand. The temperature of the insulin to be injected must be at least 10°C. - -![Bild5](../../images/EOPatch/Bild5.png) - -### patch pairing -The Patch pairing screen will be displayed, and pairing will be attempted automatically. If communication is successful, the Bluetooth pairing request notification appears. Click OK and when the Bluetooth pairing request notification appears a second time with the authentication code, select OK again. - -[Warning] - -- For pairing, the patch and the smartphone must be located within 30 cm of each other. -- After the patch booting is completed, the patch will beep every 3 minutes until the pairing is complete. -- After booting the patch, the patch application must be completed via the app within 60 minutes. If the application cannot be completed within 60 minutes, the patch should be discarded. - -![Bild6](../../images/EOPatch/Bild6.png) ![Bild7](../../images/EOPatch/Bild7.png) ![Bild8](../../images/EOPatch/Bild8.png) - - -### patch preparation -After removing the adhesive tape of the patch, check if the needle is sticking out. If there are no problems with the patch, click NEXT. - -![Bild9](../../images/EOPatch/Bild9.png) - -### Patch attachment -Insulin should be injected in a spot with subcutaneous fat but few nerves or blood vessels, so it is recommended to use the abdomen, arm, or thigh for the patch attachment site. Choose a patch attachment site and apply the patch after disinfecting the location. - -[Warning] - -- Make sure to straighten the side of the patch tape attached to the body evenly, so that the patch adheres completely to the skin. -- If the patch does not stick completely, air may enter between the patch and the skin, which can weaken the adhesive strength and waterproof effect of the patch. - -![Bild10](../../images/EOPatch/Bild10.png) - -### Safety Check -When patching is complete, touch Start Safety Check. When the safety check is completed, the patch will beep once. - -[Warning] - -- For safe use, do not turn the needle action lever until the safety check has been completed. - -![Bild11](../../images/EOPatch/Bild11.png) ![Bild12](../../images/EOPatch/Bild12.png) - - -### Inserting the needle -The needle is inserted by holding around the patch and turning the needle action lever more than 100° in the upward direction of the lever. There is a buzzer sound when the needle is inserted correctly. Turn the needle action lever further clockwise to release the lever. Click NEXT. - -[Caution] - -- If you go to the next step without the buzzer sounding, a needle insertion error warning will appear. - -## Discarding the patch -Patches must be replaced in the case of low insulin levels, usage expiration, and defects. The recommended usage period for each patch is 84 hours after booting the patch. - -### Discarding the patch -Select EOPATCH2 at the top of the home screen and click the DISCARD/CHANGE PATCH button at the bottom. On the next screen, click the DISCARD PATCH button. A dialog box appears to confirm once more and if you select the DISCARD PATCH button, the disposal is completed. - -![Bild13](../../images/EOPatch/Bild13.png) ![Bild14](../../images/EOPatch/Bild14.png) ![Bild15](../../images/EOPatch/Bild15.png) ![Bild16](../../images/EOPatch/Bild16.png) - -## Suspending and Resuming Insulin Delivery -Suspending insulin delivery also cancels both extended bolus and temporary basal. When resuming insulin delivery, the canceled extended bolus and temporary basal will not be resumed. And when insulin delivery is suspended, the patch will give a sound every 15 minutes. - -### Suspending insulin delivery -Select EOPATCH2 at the top of the home screen and click the SUSPEND button at the bottom right. When you select CONFIRM in the confirmation box, a time selection box appears. If you select the CONFIRM button after selecting the time, the insulin delivery will be suspended for the set amount of time. - -![Bild17](../../images/EOPatch/Bild17.png) ![Bild18](../../images/EOPatch/Bild18.png) ![Bild19](../../images/EOPatch/Bild19.png) - - -### Resuming insulin delivery -Select EOPATCH2 at the top of the home screen and click the RESUME button at the bottom right. Insulin delivery will resume by selecting CONFIRM in the confirmation dialog box. - -![Bild20](../../images/EOPatch/Bild20.png) ![Bild21](../../images/EOPatch/Bild21.png) - -## Alarms/Warnings - -### Alarm - -Alarms are issued for emergency situations of the highest priority and require immediate action. The alarm signal does not disappear or time out until it is acknowledged. An alarm occurs when there is a problem with the patch being used, so there may be cases where the patch in use needs to be discarded and replaced with a new patch. The warning is displayed as a dialog box and switching to another screen is not possible until processing is completed. - -![Bild22](../../images/EOPatch/Bild22.png) ![Bild23](../../images/EOPatch/Bild23.png) - -The different types of alarms are explained below. - -| Alarms | Explanation | -| -------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| Empty reservoir | Occurs when the patch’s reservoir runs out of insulin. | -| Patch expired | Occurs when the patch usage time has expired, and no further insulin injections are possible. | -| Occlusion | Occurs when it appears that the patch's insulin inlet is clogged. | -| Power on self-test failure | Occurs when the patch finds an unexpected error during the post-boot self-test process. | -| Inappropriate temperature | Occurs when the patch is outside the normal operating temperature range during patch application and use. To deal with this alarm, move the patch to an appropriate operating temperature (4.4 to 37°C) condition. | -| Needle insertion Error | Occurs when needle insertion is not normal during the patch application process. Check that the needle insertion edge of the patch and the needle activation button are in a straight line. | -| Patch battery Error | Occurs just before the patch’s internal battery runs out and powers off. | -| Patch activation Error | Occurs when the app fails to complete the patching process within 60 minutes after the patch is booted. | -| Patch Error | Occurs when the patch encounters an unexpected error while applying and using the patch. | - -### Warning - -A warning occurs in a medium or low-priority situation. When a warning occurs, it is displayed as a notification in the Overview screen. - -![Bild24](../../images/EOPatch/Bild24.png) - -The different types of warnings are explained below. - -| Warnings | Explanation | -| ---------------------------- | ------------------------------------------------------------------------------------------------------------------------------------- | -| End of insulin suspend | Occurs when the time set by the user has elapsed after the insulin infusion suspension has been completed. | -| Low reservoir | Occurs when the remaining amount of insulin in the patch is below the set amount. | -| Patch operating life expired | Occurs when the patch usage period is over. | -| Patch will expire soon | Occurs 1 hour before the patch must be discarded. | -| Incomplete Patch activation | Occurs when more than 3 minutes have elapsed due to an interruption during patch application in the stage after pairing is completed. | -| Patch battery low | Occurs when the patch's battery is low. | - diff --git a/docs/CROWDIN/ro/Configuration/Hardware/index.md b/docs/CROWDIN/ro/Configuration/Hardware/index.md deleted file mode 100644 index 9215e2770d45..000000000000 --- a/docs/CROWDIN/ro/Configuration/Hardware/index.md +++ /dev/null @@ -1,27 +0,0 @@ -# Hardware-Configuration - -## Configuration - -## BG Source - -- [BG Source](../BG-Source.md) -- [xDrip+ Settings](../xDrip.md) -- [Dexcom G6 hints](../Dexcom.md) -- [Smoothing blood glucose data](../../Usage/Smoothing-Blood-Glucose-Data-in-xDrip.md) - -## Pumps - -- [Dana-R pump](../DanaR-Insulin-Pump.md) -- [Dana-RS pump](../DanaRS-Insulin-Pump.md) -- [Accu-Chek Combo pump](../Accu-Chek-Combo-Pump.md) -- [Accu-Chek Insight pump](../Accu-Chek-Insight-Pump.md) -- [Medtronic pump](../MedtronicPump.md) - -## Phones - -- [Jelly Pro Settings](../../Usage/jelly.md) -- [Huawei Settings](../../Usage/huawei.md) - -## Smartwatch - -- [Watchfaces](../Watchfaces.md) diff --git a/docs/CROWDIN/ro/Getting-Started/ClosedLoop.md b/docs/CROWDIN/ro/Getting-Started/ClosedLoop.md deleted file mode 100644 index cbf82cf21392..000000000000 --- a/docs/CROWDIN/ro/Getting-Started/ClosedLoop.md +++ /dev/null @@ -1,55 +0,0 @@ -# What is a Closed Loop System? - -![AAPS is like an autopilot](../images/autopilot.png) - -An artificial pancreas closed loop system combines different components in order to make diabetes management easier for you. In her great book [Automated Insulin Delivery](https://www.artificialpancreasbook.com/) Dana M. Lewis, one of the founders of the open source closed loop movement, calls it an ["autopilot for your diabetes"](https://www.artificialpancreasbook.com/3.-getting-started-with-your-aps). But what does that mean? - -**Autopilot in an aircraft** - -The autopilot does not do the complete job and does not give the possibility to the pilot to sleep throughout the entire flight. It facilitates the work of the pilots. It relieves them of the burden of permanently monitoring the aircraft and the flight attitude. This allows the pilot to concentrate on monitoring the airspace and controlling the autopilot's functions. - -The autopilot receives signals from various sensors, a computer evaluates them together with the pilot's specifications and then makes the necessary adjustments. The pilot no longer has to worry about the constant adjustments. - -**Closed Loop System** - -The same applies to an artificial pancreas closed loop system. It does not do the whole job, you still have to take care of your diabetes. A closed loop system combines the sensor data from a CGM/FGM with your diabetes management specifications such as basal rate, insulin sensitivity factor and carb ratio. From this it calculates treatment suggestions and implements these permanent small adjustments in order to keep your diabetes within the target range and to relieve you. This leaves more time for your life "next to" diabetes. - -Just as you don't want to get on a plane where only the autopilot flies without human supervision, a closed loop system helps you with your diabetes management, but always needs your support! **Even with a closed loop you can't just forget your diabetes!** - -Just as the autopilot depends on the sensor values as well as the pilot's specifications, a closed loop system needs appropriate input such as basal rates, ISF and carb ratio to support you successfully. - -## Open Source Artificial Pancreas Closed Loop Systems - -At present there are three major open source closed loop systems available: - -### AndroidAPS (AAPS) - -AAPS is described in detail in [this documentation](./WhatisAndroidAPS.html). It uses an Android Smartphone for calculation and control of your insulin pump. It is in strong collaboration with OpenAPS (i.e. they share algorithms). - -Compatible [pumps](../Hardware/pumps.md) are: - -- [DanaR](../Configuration/DanaR-Insulin-Pump.md) / [DanaRS & Dana-i](../Configuration/DanaRS-Insulin-Pump.html) -- [Accu-Chek Combo](../Configuration/Accu-Chek-Combo-Pump.md) -- [Accu-Chek Insight](../Configuration/Accu-Chek-Insight-Pump.md) -- [Diaconn G8](../Configuration/DiaconnG8.md) -- [Omnipod DASH](../Configuration/OmnipodDASH.md) -- [Omnipod Eros](../Configuration/OmnipodEros.md) -- some old [Medtronic pumps](../Configuration/MedtronicPump.md) - -### OpenAPS - -[OpenAPS](https://openaps.readthedocs.io) was the first Open Source Closed Loop System. It uses a small computer such as Raspberry Pi or Intel Edison. - -Compatible pumps are: - -- some old Medtronic pumps - -### Loop for iOS - -[Loop for iOS](https://loopkit.github.io/loopdocs/) is the Open Source Closed Loop System to be used with Apple iPhones. - -Compatible pumps are: - -- Omnipod DASH -- Omnipod Eros -- some old Medtronic pumps diff --git a/docs/CROWDIN/ro/Getting-Started/GlossaryTest.md b/docs/CROWDIN/ro/Getting-Started/GlossaryTest.md deleted file mode 100644 index d7e37bb7df0c..000000000000 --- a/docs/CROWDIN/ro/Getting-Started/GlossaryTest.md +++ /dev/null @@ -1,391 +0,0 @@ -# Glossary - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
TermDescriptionsee alsomore details @
AAPSAndroidAPS - artifical pancreas system  
AMAadvanced meal assist - advanced algorithm to handle carbsMA / SMBWiki - AMA
Android autodisplay AAPS notifications on your car's compatible in-dash information and entertainment head unit Wiki - android auto
APKsoftware installation file (Android application package) Wiki - Building APK
Autosenscalculation of sensitivity to insulin as a result of exercise, hormones etc. DIABETTECH - Autosens
Azurecloud computing platform to host Nightscout dataHeroku / NightscoutAzure
BATstatus light low battery on homescreenCAN / RES / SENPreferences
Screenshots
BGblood glucose  
BGIblood glucose interaction -degree to which BG 'should' be rising or falling based on insulin activity alone  
BG sourceWhere do your glucose values come from?CGM / FGMWiki - BG source
Blukon Nightreaderbluetooth transmitter to use Freestyle Libre as CGMBlueReader / MiaoMiaoAmbrosia Blukon Nightreader
BRbasal rate  
CAGEcanula age - displayed in Nightscout if information was entered in actions tab / menu tab or through AAPS actions tab 'prime'Nightscout 
CANstatus light overdue canula change on homescreenBAT / RES / SENPreferences
Screenshots
CGMcontinuous glucose monitor  
Closed Loopclosed-loop systems make automatic adjustments to basal delivery, without needing user-approval, based on an algorithmOpen loopWiki closed loop
COBcarbs on board  
DIAduration of insulin action Wiki insulin types
DIABETTECH - DIA
DSTdaylight savings time Wiki DST
eCarbs"extended carbs" - carbs split up over serveral hours (i.e. lot of fat/protein)
extended boluses you might know from regular pump therapy do not make much sense when looping		SMBWiki - eCarbs
eCarbs use case
FGMflash glucose monitor (Freestyle Libre) Wiki - BG source
gitversion-control system for tracking changes in computer files and coordinating work on those files
-> neccessary for APK updates		 Wiki - update APK
Githubweb-based hosting service for version control using Git
-> storage of source code		 Github AndroidAPS
Glimpapp to collect values from Freestyle Libre Nightscout with Glimp
Herokucloud computing platform to host Nightscout dataAzure / NightscoutHeroku
IC (or I:C)insulin to carb ratio (How many carbs are covered by one unit of insulin?)  
IOBinsulin on board - insulin active in your body  
ISFinsulin sensitivity factor - the expected decrease in BG as a result of one unit of insulin  
LGSLow Glucose Suspend
AAPS will reduce basal if blood glucose is dropping. But if blood glucose is rising then it will only increase basal if the IOB is negative (from a previous LGS), otherwise basal rates will remain the same as your selected profile. You may temporarily experience spikes following treated hypos without the ability to increase basal on the rebound.		objective 6 
LineageOSfree and open-source operating system for smartphones etc.
alternative OS for smartphones not running Android 8.1 (Oreo)
(when using Accu-Chek Combo)		 Wiki - Combo pump
Log filesrecord of all AAPS actions (useful for trubbleshooting and debugging) Wiki - log files
maxIOBsafety feature - maximum total IOB AAPS can't go over Wiki - maxIOB
Wiki - SMB
MiaoMiaobluetooth transmitter to use Freestyle Libre as CGMBlueReader / Blukon NightreaderMiaoMiao
min_5m_carbimpactsaftey feature - default carb decay at times when carb absorption can’t be dynamically worked out based on your bloods reactions Wiki - config builder
Nightscoutopen source project to access and report CGM dataNightscout ReporterNightscout
NS Clientpart of AAPS to connect to your Nightscout site Wiki - NS Client
Nightscout ReporterTool from fellow looper to generate PDFs reports from Nightscout dataNightscoutNightscout Reporter
NS Reporter @ Facebook
Objectiveslearning program within AAPS guiding you step by step from open to closed loop Wiki - objectives
OpenAPSopen artificial pancreas system
APS run on small computers (i.e. Raspberry Pie)
AAPS uses some of the OpenAPS features		 OpenAPS docs
Open Loopsystem will suggest recommended adjustments which have to be performed manually on the pumpClosed LoopWiki - config builder
Oref0 / Oref1sensitivity detection
"reference design implementation version 0/1" - the key algorithm behind OpenAPS		 Wiki - sensitivity detection
Peak timetime of maximum effect of insulin given Wiki - config builder
PHpump history (entry in treatments tab) Screenshots
Predictionspreditions for BG in the future based on different calculations Wiki - predition lines
Profilebasic treatment settings (basal rate, DIA, IC, ISF, BG target)
can be defined locally or through Nightscout		NightscoutWiki - profile
Profile switch(temporary) change of profile used or percentual increase/decrease Wiki - profile switch
RESstatus light overdue reservoir change on homescreenBAT / CAN / SENPreferences
Screenshots
RileyLinkopen source hardware device to bridge Bluetooth Low Energy (BLE) to 916MHz wireless communication (used for old Medtronic pumps)OpenAPS 
SAGEsensor age - displayed in Nightscout if information was entered in the actions tab / menuNightscout 
SENstatus light sensor change on homescreenBAT / CAN / RESPreferences
Screenshots
Sensivity detectioncalculation of sensitivity to insulin as a result of exercise, hormones etc. DIABETTECH - Autosens
Sensor noiseunstable CGM readings leading to "jumping" values Wiki - sensor noise
SMBsuper micro bolus
advanced feature for faster BG adjustment		UAMWiki - SMB
Super bolusshift of basal to bolus insulin for faster BG adjustment John Walsh - The Super Bolus
TBBtotal base basal (sum of basal rate within 24 hours)  
TBRtemporary basal rate  
TDDtotal daily dose (bolus + basal per day)  
TTtemporary target
temporary increase/decrease of BG target (range)		 Wiki - temp targets
UAMunannounced meals - detection of significant increase in glucose levels due to meals, adrenaline or other influences and attempt to adjust this with SMBSMBWiki - SMB
Virtual pumpoption to try AAPS functions or for PWD using a pump model with no AndroidAPS driver for loopingOpen Loop 
WallpaperAndroidAPS background imagesee phones page
xDrip / xDrip+open source software to read CGM systems xDrip+
xDrip
Zero-temptemporary basal rate with 0% (no basal insulin delivery)  
See also https://openaps.readthedocs.io/en/latest/docs/Resources/glossary.html
diff --git a/docs/CROWDIN/ro/Getting-Started/Safety-first.md b/docs/CROWDIN/ro/Getting-Started/Safety-first.md deleted file mode 100644 index 23d9ffb12959..000000000000 --- a/docs/CROWDIN/ro/Getting-Started/Safety-first.md +++ /dev/null @@ -1,41 +0,0 @@ -# Safety first - -**When you decide to build your own artificial pancreas, it's always important to think about security and safety, and to understand the impact of all your actions** - -## General - -- AAPS is a just a tool to help you manage diabetes, it is not a fully automated system you can install and forget! -- Do not assume that AAPS will never make mistakes. This device is taking control of your insulin delivery: Watch it all the time, understand how it works, and learn how to interpret its actions. -- Remember that, once paired, the phone can instruct the pump to do anything. Only use this phone for AAPS and, if being used by a child, essential communications. Do not install unnecessary apps or games (!!!) which could introduce malware such as trojans, viruses, or bots that could interfere with your system. -- Install all security updates provided by your phone manufacturer and Google. -- You might also need to change your diabetes habits as you change your therapy by using a closed loop system. I.e. some people report, they need less hypo treatments as AAPS has already reduced insulin. - -## Comunicator SMS - -- AAPS allows you to control a child's phone remotely via text message. If you enable this SMS Communicator, always remember that the phone set up to give remote commands could be stolen. So always protect it at least by a PIN code. -- AAPS will also inform you by text message if your remote commands, such as a bolus or a profile change, have been carried out. It is advisable to set this up so that confirmation texts are sent to at least two different phone numbers in case one of the receiving phones is stolen. - -(Safety-first-aaps-can-also-be-used-by-blind-people)= -## AAPS can also be used by blind people - -On Android devices TalkBack is part of the operating system. It is a program for screen orientation via voice output. With TalkBack you can operate your smartphone as well as AAPS blind. - -We users create the AAPS app ourselves with Android Studio. Many use Microsoft Windows for this purpose, where there is the Screenreader analogous to TalkBack. Since Android Studio is a Java application, the "Java Access Bridge" component must be enabled in the Control Panel. Otherwise, the screen reader of the PC will not speak in Android Studio. - -To do this, please proceed as follows: - -- Press WINDOWSTASTE and enter "Control Panel" in the search field, open with Enter. It opens: "All Control Panel Items". -- Press the letter C to get to "Center for Ease of Use", open with Enter. -- Then open "Use computer without a screen" with Enter. -- There, at the bottom, you will find the checkbox "Enable Java Access Bridge", select it. -- Done, just close the window! The screen reader should work now. - -```{note} -**IMPORTANT SAFETY NOTICE** - -The foundation of AAPS safety features discussed in this documentation is built on the safety features of the hardware used to build your system. It is critically important that you only use a tested, fully functioning FDA or CE approved insulin pump and CGM for closing an automated insulin dosing loop. Hardware or software modifications to these components can cause unexpected insulin dosing, causing significant risk to the user. If you find or get offered broken, modified or self-made insulin pumps or CGM receivers, *do not use* these for creating an AAPS system. - -Additionally, it is equally important to only use original supplies such as inserters, cannulas and insulin containers approved by the manufacturer for use with your pump or CGM. Using untested or modified supplies can cause CGM inaccuracy and insulin dosing errors. Insulin is highly dangerous when misdosed - please do not play with your life by hacking with your supplies. - -Last not least, you must not take SGLT-2 inhibitors (gliflozins) as they incalculably lower blood sugar levels. The combination with a system that lowers basal rates in order to increase BG is especially dangerous as due to the gliflozin this rise in BG might not happen and a dangerous state of lack of insulin can happen. -``` diff --git a/docs/CROWDIN/ro/Getting-Started/Sample-Setup.md b/docs/CROWDIN/ro/Getting-Started/Sample-Setup.md deleted file mode 100644 index 01fe0a5e86cd..000000000000 --- a/docs/CROWDIN/ro/Getting-Started/Sample-Setup.md +++ /dev/null @@ -1,151 +0,0 @@ -# Sample setup: Samsung S7, Dana RS, Dexcom G6 and Sony Smartwatch - -![Sample Setup](../images/SampleSetup.png) - -## Descriere - -In this setup, the Samsung Galaxy S7 smartphone is used as control center of the loop. The slightly modified Dexcom App reads glucose values from the Dexcom G6 CGM. AndroidAPS is used to control the Dana RS insulin pump from Korean manufacturer SOOIL via bluetooth. Further devices are not required. - -As the Dexcom App only offers limited alarm options the open source app xDrip+ is used to define not only high and low alarms but also additional alarms according to individual requirements. - -Optionally an Android wear smartwatch can be used (in this sample setup the Sony Smartwatch 3 (SWR50)) to display glucose and AndroidAPS values on your wrist. The watch can even be used to control AndroidAPS (i.e. discreetly set a meal bolus). - -The system works offline. This means there is no need for a data connection from the smartphone to the Internet for operation. - -Nevertheless, the data is automatically uploaded to Nightscout "in the cloud" when a data connection is established. By doing so you can provide comprehensive reports for the doctor's visit or share the current values with family members at any time. It is also possible to send data to Nightscout only when using a (predefined) Wi-Fi connection in order to profit from the different Nightscout reports. - -## Required components - -1. Samsung Galaxy S7 - - * Alternatives: see [list of tested phones and watches](https://docs.google.com/spreadsheets/d/1gZAsN6f0gv6tkgy9EBsYl0BQNhna0RDqA9QGycAqCQc/edit) for AndroidAPS - -2. [DanaRS](http://www.sooil.com/eng/product/) - - * Alternative: - * [Accu-Chek Combo](../Configuration/Accu-Chek-Combo-Pump.md) - * [Accu-Chek Insight](../Configuration/Accu-Chek-Insight-Pump.md) - * [DanaR](../Configuration/DanaR-Insulin-Pump.md) - * [Some old Medtronic pumps (additionally needed: RileyLink/Gnarl hardware, Android Phone with bluetooth low energy / BLE-chipset)](../Configuration/MedtronicPump.md) - * Other pumps might be available in the future, see [future possible pump drivers](Future-possible-Pump-Drivers.md) for details. - -3. [Dexcom G6](https://dexcom.com) - - * Alternatives: see list of possible [BG sources](../Configuration/BG-Source.md) - -4. Optional: Sony Smartwatch 3 (SWR50) - - * Alternatives: All [watches with Google Wear OS](https://wearos.google.com/intl/de_de/#find-your-watch) should work fine, for details see [list of tested phones and watches](https://docs.google.com/spreadsheets/d/1gZAsN6f0gv6tkgy9EBsYl0BQNhna0RDqA9QGycAqCQc/edit) for AndroidAPS (OS must be Android Wear) - -## Nightscout setup - -See detailed [Nightscout setup](../Installing-AndroidAPS/Nightscout.md) - -## Computer setup - -To be able to create an Android app from the freely available AAPS open source code you need Android Studio on your computer or notebook (Windows, Mac, Linux). A detailed instruction can be found at [building the APK](../Installing-AndroidAPS/Building-APK.md). - -Please be patient when installing Android Studio as the software downloads a lot of additional data once installed on your computer. - -## Smartphone setup - -![Smartphone](../images/SampleSetupSmartphone.png) - -### Check smartphone firmware - -* Menu > Settings > Phone info > Software info: At least "Android-Version 8.0" (successfully tested up to Android version 8.0.0 Oreo - Samsung Experience Version 9.0) -* For firmware update: menu > Preferences > software update - -### Allow installation from unknown sources - -Menu > Settings > Device security > Unknown sources > slider to right side (= active) - -For security reasons this setting should be set back to inactive once the installation of all apps described here has been completed. - -### Activați Bluetooth-ul - -1. Menu > Settings > Connections > Bluetooth > slider to right side (= active) -2. Menu > Settings > Connections > Location > slider to right side (= active) - -Location services ("GPS") must be activated in order for Bluetooth to work properly. - -### Install Dexcom App (modified version) - -![Dexcom App patched](../images/SampleSetupDexApp.png) - -The original Dexcom app from the Google Play Store will not work because it does not broadcast the values to other apps. Therefore, a version slightly modified by the community is required. Only this modified Dexcom app can communicate with AAPS. Additionally the modified Dexcom App can be used with all Android smartphones not only the ones in [Dexcom's compatibility list](https://www.dexcom.com/dexcom-international-compatibility). - -To do this perform the following steps on your smartphone: - -1. If the original Dexcom app is already installed: - * Stop sensor - * Uninstall app via Menu > Settings > Apps > Dexcom G6 Mobile > Uninstall -2. Download and install the [BYODA Dexcom ap](../Hardware/DexcomG6.md#if-using-g6-with-build-your-own-dexcom-app) -3. Start modified Dexcom G6 app, activate/calibrate the sensor according to the given instructions and wait until the warm-up phase is finished. -4. Once the modified Dexcom app shows actual glucose value, setup the warnings (hamburger menu on top left side of the screen) as follows: - * Urgent low `55mg/dl` / `3.1mmol/l` (cannot be disabled) - * Low `OFF` - * High `OFF` - * Rise rate `OFF` - * Fall rate `OFF` - * Signal loss `OFF` - -## Install AndroidAPS - -1. Follow the instructions to [build the APK](../Installing-AndroidAPS/Building-APK.md#generate-signed-apk) -2. [Transfer](../Installing-AndroidAPS/Building-APK.md#transfer-apk-to-smartphone) the generated APK to your phone -3. [Configure AndroidAPS](../Configuration/Config-Builder.md) according to your needs using the setup assistant or manually -4. In this sample setup we used (among others) - -* BG source: `Dexcom G6 App (patched)` -- click cock-wheel and activate `Upload BG data to NS` and `Send BG data to xDrip+` (see [BG source](../Configuration/BG-Source.md)) - -![G5 Settings](../images/SampleSetupG5Settings.png) - -* NS Client activated (see [Nightscout setup](../Installing-AndroidAPS/Nightscout.md)) - -## Install xDrip+ - -xDrip+ is another mature open source app that offers countless possibilities. In this setup, contrary to what the developers first wrote the app for, xDrip+ is not used to collect glucose data from the Dexcom G6, but only to output alarms and to display the current glucose value including the curve on the Android home screen in the widget. With xDrip+ the alarms can be set much more individually than with the Dexcom software, AAPS or Nightscout (no limitation in the selection of sounds, different alarms depending on day/night time etc.). - -1. Download the latest stable APK version of xDrip+ with your smartphone - not the version from the Google Play Store! -2. Install xDrip+ by selecting the downloaded APK file. -3. Start xDrip+ and make the following settings (hamburger menu at top left) - * Settings > Alarms and Alerts > Glucose Level Alert List > Create Alerts (high and low) according to your needs. - * The existing alarms can be changed with a long press on the alarm. - * Settings > Alarms and Alerts > Calibration Alerts: disabled (reminded via the modified Dexcom app) - * Settings > Hardware Data Source > 640G/EverSense - * Settings > Inter-app settings > Accept Calibrations > `ON` - * Menu > Start sensor (is only "pro forma" and has nothing to do with the running G6 sensor. This is necessary otherwise an error message will appear regularly.) - -For more information about xDrip+, see here [BG source page](../Configuration/BG-Source.md). - -### Example of an alarm setup - -The "Urgent low alarm" (below 55 mg/dl resp. 3,1 mmol) is a standard alarm from the modified Dexcom app that cannot be disabled. - -![xDrip alarms](../images/SampleSetupxDripWarning.png) - -Tip for meetings / church visits / cinema etc..: - -If "Do not disturb" mode is activated in the Samsung Galaxy S7 (Menu > Settings > Sounds and vibration > Do not disturb: slider to right side (= active)), the phone only vibrates during urgent low alarm and does not issue an acoustic warning. For the other alarms set up via xDrip+ you can select whether the silent mode should be ignored (acoustic sound played) or not. - -## Disable power saving option - -On your Samsung Galaxy S7 go to Menu > Settings > Device Maintenance > Battery > Unmonitored Apps > + Add apps: Select the apps AndroidAPS, Dexcom G6 Mobile, xDrip+ and Android Wear (if smartwatch is used) one after the other - -## Optional: Setup Sony Smartwatch 3 (SWR50) - -With an Android Wear smartwatch life with diabetes can be made even more inconspicuous. The watch can be used to display the current glucose level, the status of the loop etc. on the wrist. The watch can even be used to control AndroidAPS (i.e. discreetly set a meal bolus). To do this, double tap the CGM value of the AAPSv2 watchface. The SWR50 usually runs for a full day until the battery needs to be recharged (same charger as the Samsung Galaxy S7: microUSB). - -![Smartwatch](../images/SampleSetupSmartwatch.png) - -Details about the information displayed on the watchface can be found [here](../Configuration/Watchfaces.md). - -* Install the app "Android Wear" on your smartphone via the Google Play Store and connect the smartwatch according to the instructions there. -* In AAPS choose hamburger menu (top left corner) > Config Builder > General (at the bottom of the list) > Wear > activate on left side, click cock wheel > Wear settings and activate `Controls from Watch` -* On your smartwatch: Long press display to change watchface and select `AAPSv2` -* If necessary restart both devices once. - -## Setări pompă - -see [Dana RS pump](../Configuration/DanaRS-Insulin-Pump.md) \ No newline at end of file diff --git a/docs/CROWDIN/ro/Getting-Started/WhatisAndroidAPS.md b/docs/CROWDIN/ro/Getting-Started/WhatisAndroidAPS.md deleted file mode 100644 index 6fc82dfa1eb9..000000000000 --- a/docs/CROWDIN/ro/Getting-Started/WhatisAndroidAPS.md +++ /dev/null @@ -1,39 +0,0 @@ -# What is a closed loop system with AAPS? - -AAPS is an app that acts as an artificial pancreas system (APS) on an Android smartphone. Ce este un sistem de pancreas artificial? Este un program software care are ca scop să facă ce face un pancreas: să tina în mod automat valorile glicemiei în limite sănătoase. - -Un APS nu poate face treaba la fel de bine ca un pancreas biologic dar poate face ca diabetul de tip 1 să fie mai uşor de gestionat folosind dispozitive disponibile pe piaţă şi programe software uşor de utilizat şi sigure. Those devices include a continuous glucose monitor (CGM) to tell AAPS about your blood sugar levels and an insulin pump which AAPS controls to deliver appropriate doses of insulin. Aplicaţia comunică cu aceste dispozitive prin bluetooth. Aceasta calculează doze folosind un algoritm, sau set de reguli, dezvoltat pentru un alt sistem de pancreas artificial, OpenAPS, cu mii de utilizatori și milioane de ore de funcționare. - -A note of caution: AAPS is not regulated by any medical authority in any country. Using AAPS is essentially carrying out a medical experiment on yourself. Setarea sistemului necesită determinare şi cunoştinţe tehnice. Dacă nu ai cunoștințele tehnice la început, până ajungi la sfârșit vei avea. Toate informațiile de care ai nevoie pot fi găsite în aceste documente, în altă parte online sau le poti afla de la alții care au făcut deja AAPS- poti întreba în grupuri Facebook sau alte forumuri. Many people have successfully built AAPS and are now using it entirely safely, but it is essential that every user: - -- Builds the system themselves so that they thoroughly understand how it works -- Adjusts its individual dosage algorithm with his or her diabetes team to work nearly perfect -- Maintains and monitors the system to ensure it is working properly - -```{note} -**Disclaimer and Warning** - -- All information, thought, and code described here is intended for informational and educational purposes only. Nightscout currently makes no attempt at HIPAA privacy compliance. Use Nightscout and AAPS at your own risk, and do not use the information or code to make medical decisions. -- Use of code from github.com is without warranty or formal support of any kind. Please review this repository's LICENSE for details. -- All product and company names, trademarks, servicemarks, registered trademarks, and registered servicemarks are the property of their respective holders. Their use is for information purposes and does not imply any affiliation with or endorsement by them. - -Please note - this project has no association with and is not endorsed by: [SOOIL](http://www.sooil.com/eng/), [Dexcom](https://www.dexcom.com/), [Accu-Chek, Roche Diabetes Care](https://www.accu-chek.com/), [Insulet](https://www.insulet.com/) or [Medtronic](https://www.medtronic.com/). -``` - -Dacă ești pregătit pentru provocare, citește mai departe. - -## Primary goals behind AAPS - -- An app with safety built in. To read about the safety features of the algorithms, known as oref0 and oref1, click here () -- An all-in-one app for managing type 1 diabetes with an artificial pancreas and Nightscout -- An app to which users can easily add or remove modules as needed -- An app with different versions for specific locations and languages. -- An app which can be used in open- and closed-loop mode -- An app that is totally transparent: users can input parameters, see results, and make the final decision -- An app which is independent of particular pump drivers and contains a "virtual pump" so users can safely experiment before using it on themselves -- An app closely integrated with Nightscout -- An app in which the user is in control of safety constraints - -## Cum să începi - -Desigur, tot acest conținut este foarte important, dar poate fi la început destul de confuz. A good orientation is given by the [Module Overview](../Module/module.md) and the [Objectives](../Usage/Objectives.html). diff --git a/docs/CROWDIN/ro/Hardware/DexcomG4.md b/docs/CROWDIN/ro/Hardware/DexcomG4.md deleted file mode 100644 index 7044364d4dd7..000000000000 --- a/docs/CROWDIN/ro/Hardware/DexcomG4.md +++ /dev/null @@ -1,6 +0,0 @@ -# Dexcom G4 - -## Dacă utilizaţi G4 cu cablu OTG (Nightscout "tradiţional") -- If not already set up then download Nightscout Uploader app from the Play Store and follow instructions on [Nightscout](https://nightscout.github.io/). -- In AAPS Preferences enter your Nightscout website and API secret. -- Select NSClient in ConfigBuilder (setting in AAPS). diff --git a/docs/CROWDIN/ro/Hardware/Smartwatch.md b/docs/CROWDIN/ro/Hardware/Smartwatch.md deleted file mode 100644 index a9c26f844de6..000000000000 --- a/docs/CROWDIN/ro/Hardware/Smartwatch.md +++ /dev/null @@ -1,10 +0,0 @@ -# Smartwatch - -Ceasurile sunt opţionale, dar foarte utile pentru unii utilizatori. More details are here: - -- [List of tested phones and smartwatches](../Getting-Started/Phones.md) -- [Watchfaces Wear OS](../Configuration/Watchfaces.md) -- [Troubleshooting Sony Smartwatch SW 3](../Usage/SonySW3.md) - -## Instructions for Building the AAPS Wear APK for Wear OS -https://androidaps.readthedocs.io/en/latest/remote-control.html#building-the-aaps-wear-apk diff --git a/docs/CROWDIN/ro/Installing-AndroidAPS/Building-APK.md b/docs/CROWDIN/ro/Installing-AndroidAPS/Building-APK.md deleted file mode 100644 index 4873d7edf38c..000000000000 --- a/docs/CROWDIN/ro/Installing-AndroidAPS/Building-APK.md +++ /dev/null @@ -1,369 +0,0 @@ -# Building the APK - -## Build yourself instead of download - -**AAPS is not available as download due to regulation for medical devices. It is legal to build the app for your own use, but you must not give a copy to others! See [FAQ page](../Getting-Started/FAQ.md) for details.** - -## Important notes - -* Please use **[Android Studio Giraffe" (2022.3.1)](https://developer.android.com/studio/)** or newer to build the apk. -* [Windows 32-bit systems](troubleshooting_androidstudio-unable-to-start-daemon-process) are not supported by Android Studio - -(Building-APK-recommended-specification-of-computer-for-building-apk-file)= - -## Recommended specification of computer for building apk file - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
OS (Only 64 bit)Windows 8 or higherMac OS 10.14 or higherAny Linux supports Gnome, KDE, or Unity DE;  GNU C Library 2.31 or later

CPU (Only 64 bit)

x86_64 CPU architecture; 2nd generation Intel Core or newer, or AMD CPU with support for a
Windows Hypervisor		ARM-based chips, or 2nd generation Intel Core or newer with support for
Hypervisor.Framework		x86_64 CPU architecture; 2nd generation Intel Core or newer, or AMD processor with support for AMD Virtualization (AMD-V) and SSSE3

RAM

8GB or more

Disk

At least 30GB free space. SSD is recommended.

Resolution

1280 x 800 Minimum

Internet

Broadband

- -Please keep in mind that both **64 bit CPU and 64 bit OS are mandatory condition.** If your system DOES NOT meet this condition, you have to change affected hardware or software or the whole system. **It is strongly recommended to use SSD (Solid State Disk) instead of HDD (Hard Disk Drive) because it will take less time when you are building the APS installation apk file.** Recommended is just recommended and it is not a mandatory. However, you may still use a HDD when you are building apk file but note that the building process can take a long time to complete, although once started, you can leave it running unattended. - -* * * - -### This article is divided into two parts. - -* In the overview part there is an explanation on what steps are necessary to build the APK file. -* In the step by step walkthrough part you will find the screenshots of a concrete installation. Because the versions of Android Studio - the software development environment which we will use to build the APK - will change very quickly this will be not identical to your installation but it should give you a good starting point. Android Studio also runs on Windows, Mac OS X and Linux and there might be small differences in some aspects between each platform. If you find that something important is wrong or missing, please inform the facebook group "AAPS users" or in the Discord chat [Android APS](https://discord.gg/4fQUWHZ4Mw) so that we can have a look at this. - -## Privire de ansamblu - -In general, the steps necessary to build the APK file: - -1. [Install git](../Installing-AndroidAPS/git-install.md) -2. [Install Android Studio](Building-APK-install-android-studio) -3. [Set git path in Android Studio preferences](Building-APK-set-git-path-in-preferences) -4. [Download AAPS code](Building-APK-download-AAPS-code) -5. [Download Android SDK](Building-APK-download-android-sdk) -6. [Build the app](Building-APK-generate-signed-apk) (generate signed apk) -7. [Transfer apk file to your phone](Building-APK-transfer-apk-to-smartphone) -8. [Identify receiver if using xDrip+](xdrip-identify-receiver) - -## Step by step walkthrough - -Detailed description of the steps necessary to build the APK file. - -## Install git (if you don't have it) - -Follow the manual on the [git installation page](../Installing-AndroidAPS/git-install.md). - -(Building-APK-install-android-studio)= - -## Install Android Studio - -The following screenshots have been taken from Android Studio Version Arctic Fox | 2020.3.1. Screens can change in future versions of Android Studio. But you should be able to find your way through. [Help from the community](../Where-To-Go-For-Help/Connect-with-other-users.md) is provided. - -One of the most important things when installing Android Studio: **Be patient!** During installation and setup Android Studio is downloading a lot of stuff which will take its time. - -Download [Android Studio from here](https://developer.android.com/studio/install.html) and install it on your computer. - -On first start you will find the setup wizard: - -Select "Do not import settings" as you have not used it before. - -![Do not import settings](../images/studioSetup/01_ImportSettings.png) - -Decide whether you want to share data with Google or not. - -![Share data with Google](../images/studioSetup/02_DataSharing.png) - -On the following screen click "Next". - -![Welcome screen](../images/studioSetup/03_Welcome.png) - -Select "Standard" installation and click "Next". - -![Standard installation](../images/studioSetup/04_InstallType.png) - -Select the theme for the user interface you like. (In this manual we used "Light".) Then click "Next". - -> ***Note:*** This is just the color scheme. You can select whatever you like (i.e. "Darcula" for dark mode). This selection has no influence on building the APK but the following screenshots might look different. - -![UI color scheme](../images/studioSetup/05_UITheme.png) - -Click "Next" on the "Verify Settings" dialog. - -![Verify settings](../images/studioSetup/06_Overview.png) - -Click on all three license agreement parts and select "Agree". When you have agreed to all, the "Finish" button will be enabled and you can "Finish". - - ![Agree license agreements](../images/studioSetup/07_LicenseAgreement.png) - - -Wait while Android Studio downloads additional components and be patient. Once everything is downloaded button "Finish" turns blue. Click the button now. - -![Downloading components](../images/studioSetup/08_Downloading.png) - -(Building-APK-download-AAPS-code)= - -## Download AAPS code - -* On the Android Studio welcome screen select "Projects" (1) on the left and then "Get from VCS" (2). - - ![Android Studio wizard](../images/studioSetup/20_ProjectVCS.png) - - * If you already opened Android Studio and do not see the welcome screen anymore select File (1) > New (2) > Project from Version Control... (3) - - ![Check out project from version control within Android Studio](../images/AndroidStudio_FileNew.PNG) - - * We will now tell Android Studio were to get the code from: - - * Make sure you have selected "Repository URL" on the left (1). - - * Check if "Git" is selected as version control (2). - * Copy and paste the URL ```https://github.com/nightscout/AndroidAPS``` to the main AAPS repository into the URL textbox (3). - * Choose the directory where you want to save the cloned code (4). - - ![Clone Git](../images/studioSetup/21_CloneURL.png) - -* Click button "Clone" (5). - - ![Clone repository](../images/studioSetup/22_Cloning.png) - -* Do not click "Background" while repository is cloned! - -* After the repository is cloned successfully, Android Studio will open the cloned project. - -* You will be asked whether you want to trust the project. Click on "Trust project"! - - ![Trust project](../images/studioSetup/23_TrustProject.png) - -* In the status bar at the bottom you will see the information that Android Studio is running background tasks. - - ![Background tasks](../images/studioSetup/24_GradleSyncRunning.png) - -* Windows only: Grant access if your firewall is asking for permission. - - ![Firewall permission java](../images/AndroidStudio361_18.png) - -* Once the background tasks are finished you will probably see an error saying that errors occurred (1) or (2) or (3). - - ![SDK licence](../images/studioSetup/25_SyncFailed.png) - - Don't worry, this will be solved soon! - -(Building-APK-set-git-path-in-preferences)= - -## Set git path in preferences - -Make sure [git is installed](../Installing-AndroidAPS/git-install.md) on your computer and you have restarted your computer since installing. - -On the Android Studio welcome screen click "Customize" (1) on the left and then select the link "All settings..." (2): - -![Android Studio settings from welcome screen](../images/studioSetup/10_WizardSettings.png) - -### Windows - -* As windows user, make sure you have restarted your computer after [installing Git](../Installing-AndroidAPS/git-install.md). - -* In the menu, go to File (1) > Settings (2) (or Android Studio > Preferences on Mac). - - ![Open settings](../images/studioSetup/30_Settings.png) - -* Double-click "Version Control" (1) to open the sub-menu. - -* Click Git (2). -* Make sure update method "Merge" (3) is selected. -* Check if Android Studio can locate path to git.exe automatically by clicking the button "Test" (4). - - ![Android Studio settings](../images/studioSetup/11_GitPath.png) - -* If automatic setting is successful git version will be displayed next to the path. - - ![Git version displayed](../images/studioSetup/12_GitVersion.png) - -* Eventually git.exe cannot be found automatically or the Test will result in an error (1): - - ![Git not found](../images/studioSetup/13_GitVersionError.png) - - In this case click on the folder icon (2). - -* Use [search function](https://www.tenforums.com/tutorials/94452-search-file-explorer-windows-10-a.html) in windows explorer to find "git.exe" if you are unsure where git has been installed. You are looking for a file named "git.exe", located in **\bin** folder. - -* Select path to git.exe and make sure you selected the one in ** \bin\ ** folder (3) and click "OK" (4). - - ![Select git manually](../images/studioSetup/14_GitManualSelection.png) - -* Check your selected git path again with the "Test" button as described above. - -* When the git version is displayed next to the path (see screenshot above), close settings window by clicking "OK" button (5). - -### Mac - -* Any git version should work. For example . -* Use homebrew to install git: ```$ brew install git```. -* For details on installing git see the [official git documentation](https://git-scm.com/book/en/v2/Getting-Started-Installing-Git). -* If you install git via homebrew there is no need to change any preferences. Just in case: They can be found here: Android Studio - Preferences. - -(Building-APK-download-android-sdk)= - -## Download Android SDK - -* In the menu, go to File (1) > Settings (2) (or Android Studio > Preferences on Mac). - - ![Open settings](../images/studioSetup/30_Settings.png) - -* Double-click on Languages & Frameworks to open its submenu (1). - -* Select Android SDK (2). -* Tick the box left of "Android 9.0 (Pie)" (3) (API Level 28). - - ![SDK settings](../images/studioSetup/31_AndroidSDK.png) - -* Confirm changes by clicking OK. - - ![Confirm SDK changes](../images/studioSetup/32_ConfirmSDK.png) - -* Wait until the SDK download and installation is finished. - - ![Wait during SDK installation](../images/studioSetup/34_DownloadSDK.png) - -* When SDK installation is completed the "Finish" button will turn blue. Click this button. - - ![Finish SDK installation](../images/studioSetup/35_DownloadSDKfinished.png) - -* Android Studio might recommend to update the gradle system. **Never update gradle!** This will lead to difficulties! - -* If you see an information on the lower right side of your Android Studio window that Android Gradle Plugin is ready to update click on the text "upgrade" (1). - - ![No gradle update](../images/studioSetup/36_GradleUpdateRequest.png) - -* In the dialog box the select "Don't remind me again for this project" (2). - - ![No gradle update](../images/studioSetup/37_GradleUpdateDeny.png) - -* Restart Android Studio before you continue. - -(Building-APK-generate-signed-apk)= - -## Generate signed APK - -Signing means that you indicate your app to be your own creation but in a digital way as a kind of digital fingerprint within the app itself. That is necessary because Android has a rule that it only accepts signed code to run for security reasons. For more information on this topic, follow [this link](https://developer.android.com/studio/publish/app-signing.html#generate-key). - -* After Android Studio is started, wait until all background tasks are finished. - - ![Wait for background tasks](../images/studioSetup/40_BackgroundTasks.png) - - * ***Warning:*** If errors occur, do not continue with the following steps. \ Consult the [troubleshooting section](../Installing-AndroidAPS/troubleshooting_androidstudio) for known problems! - - ![Gradle Sync Error](../images/studioSetup/41_GradleSyncError.png) - -* Click "Build" (1) in the menu bar and select "Generate Signed Bundle / APK..." (2). - - ![Build apk](../images/studioSetup/42_MenuBuild.png) - -* Select "APK" (1) instead of "Android App Bundle" and click "Next" (2). - - ![APK instead of bundle](../images/studioSetup/43_Apk.png) - -* Make sure that module is set to "AndroidAPS.app" (1). - -* Click "Create new..." (2) to start creating your key store. - - ***Note:*** A key store in this case is nothing more than a file in which the information for signing is stored. It is encrypted and the information is secured with passwords. - - ![Create key store](../images/studioSetup/44_KeystoreNew.png) - -* Click the folder symbol to select a path on your computer for your key store. - - ![Create key store](../images/studioSetup/45_KeystoreDialog.png) - -* Select the path where your key store shall be saved (1). - - ![Create key store](../images/studioSetup/46_KeystorePath.png) - - ***Warning: Do not save in same folder as project. You must use a different directory!*** A good location would be your home folder. - -* Type a file name for your key store (2) and confirm with "OK" (3). - -* Enter (2) and confirm (3) the password for your key store. ![Select key store path](../images/studioSetup/47_KeystoreDialog.png) - - ***Note:*** Passwords for key store and key do not have to be very sophisticated. Make sure to remember those or make a note in a safe place. In case you will not remember your passwords in the future, see [troubleshooting for lost key store](troubleshooting_androidstudio-lost-keystore). - -* Enter an alias (4) for your key. Choose whatever you like. - -* Enter (5) and confirm (6) the password for your key - -* Validity (7) is 25 years by default. You do not have to change the default value. - -* First and last name must be entered (8). All other information is optional. - -* Click "OK" (9) when you are done. - -* Make sure the box to remember passwords is checked (1). So you don't have to enter them again next time you build the apk (i.e. when updating to a new AAPS version). - -* Click "Next" (2). - - ![Remember passwords](../images/studioSetup/48_KeystoreSave.png) - -* Select build variant "fullRelease" (1) and press "Finish". - - ![Select build variant](../images/studioSetup/49_BuildVariant.png) - -* Android Studio will show "Gradle Build running" at the bottom. This takes some time, depending on your computer and internet connection. **Be patient!** - - ![Gradle Running](../images/studioSetup/50_GradleRunning.png) - -* Android Studio will display the information "Generate Signed APK" after build is finished. - - ![Build finished](../images/studioSetup/51_BuildFinished.png) - -* In case build was not successful refer to the [troubleshooting section](../Installing-AndroidAPS/troubleshooting_androidstudio). - -* Click on the notification to expand it. - -* Click on the link "locate". - - ![Locate build](../images/studioSetup/52_BuildLocate.png) - - * If the notification is gone, you can always open the "Event log" and select the same link there. ![Build successfully - event log](../images/studioSetup/53_EventLog.png) - -* Your file manager/explorer will open. Navigate to the directory "full" (1) > "release" (2). - - ![File location apk](../images/studioSetup/54_APKlocation.png) - -* "app-full-release.apk" (3) is the file you are looking for! - -(Building-APK-transfer-apk-to-smartphone)= - -## Transfer APK to smartphone - -Easiest way to transfer app-full-release.apk to your phone is via [USB cable or Google Drive](https://support.google.com/android/answer/9064445?hl=en). Please note that transfer by mail might cause difficulties and is not the preferred way. - -On your phone you have to allow installation from unknown sources. Manuals how to do this can be found on the internet (i.e. [here](https://www.expressvpn.com/de/support/vpn-setup/enable-apk-installs-android/) or [here](https://www.androidcentral.com/unknown-sources)). - -## Depanare - -See separate page [troubleshooting Android Studio](../Installing-AndroidAPS/troubleshooting_androidstudio). \ No newline at end of file diff --git a/docs/CROWDIN/ro/Resources/index.md b/docs/CROWDIN/ro/Resources/index.md deleted file mode 100644 index 57b2ebe2945e..000000000000 --- a/docs/CROWDIN/ro/Resources/index.md +++ /dev/null @@ -1,8 +0,0 @@ -# Resources - -```{toctree} -:glob: true -:maxdepth: 4 - -clinician-guide-to-AndroidAPS -``` diff --git a/docs/CROWDIN/ro/Sandbox/sandbox2.md b/docs/CROWDIN/ro/Sandbox/sandbox2.md deleted file mode 100644 index 33c547956c89..000000000000 --- a/docs/CROWDIN/ro/Sandbox/sandbox2.md +++ /dev/null @@ -1,43 +0,0 @@ -# internal sandbox file 2 for testing - -```{admonition} no need to translate this -:class: note - -No need to translate this. -``` - -This is an internal sandbox file for the documentation team to test - -1. markdown syntax and - -1. background process for - 1. CROWDIN translation and - 2. Read The Docs deployment. - -You can dirctly jump from here to the first label in the sandbox1.md file - ["Jump"](sandbox1-this-is-a-test). - -You can dirctly jump from here to the second label in this file - ["Jump"](sandbox1-this-is-another-test). - -Here you can jump to the first sandbox file - ["Jump"](./sandbox1.md). - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -(sandbox2-this-is-a-test)= -## This is a test - -This is a test if labels must be unique. - -### This is spare information from the docs - -cut from index: - -There are "limits" set in place when you are first beginning your AAPS journey. These safety limits have been developed over many years by observations of the inadvertent mistakes that new users are most likely to make when first learning to set up, build, and then successfully loop with AAPS - as most often those mistakes occur simply because the user was so excited to get started using the system that they may have forgotten to sit down and dedicate the time needed to understand the information within this documentation thoroughly. - - -### spare info from the overview to put into "preparing" - -Since the requirements are very different from anything you might have set up in the past, we recommend that you really follow the instructions, step-by-step the first few times you build the app, so that you have a stronger sense of how the app building process is supposed to behave when all directions are followed exactly. Please remember to take your time. Later this will go very quickly when you build the app again for a new version. That way you will have a greater chance of noticing when something doesn't going as planned before too many steps are out of line. It is important to save the your keystore file (.jks file used to sign your app) in a safe place, so that you can always use that exact same keystore file and password each and every time you are asked to create a new updated version of AAPS, as this file is what makes sure that each new version of the app "remembers" all the information that you have provided to it in previous versions of the app and thus ensure that the updates will go as smoothly as possible. On average, you can assume that there will be one new version and 2-3 required updates per year. This number is based on experience and may change in the future. But we do want to at least give you a general guideline on what to expect. When you are more experienced at building updated AAPS app versions all the steps that are required in building an updated app will only take 15-30 minutes, on average. However, in the beginning there can be a rather steep learning curve as these steps are not always considered intuitive by new users! So do not get frustrated if you find that it takes half a day or a whole day with some help from the community before you are finally finished with the update process. If you find that you are getting very frustrated just take a short break, and oftentimes; after a stroll around the block or two...you'll find that you are better able to approach the problem again. diff --git a/docs/CROWDIN/ro/Usage/Objectives.md b/docs/CROWDIN/ro/Usage/Objectives.md deleted file mode 100644 index c72b0d79e75c..000000000000 --- a/docs/CROWDIN/ro/Usage/Objectives.md +++ /dev/null @@ -1,184 +0,0 @@ -# Obiective - -AAPS has a series of Objectives that need to be completed to walk you through the features and settings of safe looping. They ensure you have configured everything detailed in the sections above correctly, and that you understand what your system is doing and why so you can trust it. - -If you are **upgrading phones** then you can [export your settings](../Usage/ExportImportSettings.md) to keep your progress through the objectives. Not only will your progress through the objectives be saved, but also your safety settings such as max bolus etc. If you do not export and import your settings then you will need to start the objectives from the beginning again. It is a good idea to [backup your settings](../Usage/ExportImportSettings.html) frequently just in case. - -If you want to go back in objectives see [explanation below](Objectives-go-back-in-objectives). - -## Objective 1: Setting up visualization and monitoring, analysing basals and ratios - -- Select the right blood glucose source for your setup. See [BG Source](../Configuration/BG-Source.md) for more information. -- Select the right Pump in ConfigBuilder (select Virtual Pump if you are using a pump model with no AAPS driver for looping) to ensure your pump status can communicate with AAPS. -- If using DanaR pump then ensure you have followed [DanaR Insulin Pump](../Configuration/DanaR-Insulin-Pump.md) instructions to ensure the link between pump and AAPS. -- You need to establish a data repository/reporting platform to complete this objective. That can be accomplished with either Nightscout or Tidepool (or both). Follow instructions at the [Nightscout](../Installing-AndroidAPS/Nightscout.md) or [Tidepool](../Installing-AndroidAPS/Tidepool.md) page for instructions. -- Note that URL in NSClient must be **WITHOUT /api/v1/** at the end - see [NSClient settings in Preferences](Preferences-nsclient). - -*You may need to wait for the next blood glucose reading to arrive before AAPS will recognise it.* - -## Objective 2: Learn how to control AAPS - -- Perform several actions in AAPS as described in this objective. - -- Click on the orange text "Not completed yet" to access the to-dos. - -- Links will be provided to guide you in case you are not familiar with a specific action yet. - - ```{image} ../images/Objective2_V2_5.png - :alt: Screenshot objective 2 - ``` - -(Objectives-objective-3-prove-your-knowledge)= - -## Objective 3: Prove your knowledge - -Objective 3 is a multiple choice test based on questions designed to test your theoretical knowledge of **AAPS**. - -Some users find Objective 3 to be the most difficult objective to complete. Please do read the AAPS documents in conjunction with the questions. If you are genuinely stuck after researching the **AAPS** documents, please search or ask for help on the Facebook or Discord group. These groups can provide friendly hints or redirect you to the relevant part of the **AAPS** documents. - -To proceed with Objective 3, click on the orange text “Not completed yet” to access the relevant question. Please read each question and select your answer(s). - - - -Within each question, a hyperlink to the **AAPS** documents will guide you to the relevant section of the document which you should read in order to locate the correct answer. - - -[Obj3_Screenshot 2023-12-05 223422](https://github.com/openaps/AndroidAPSdocs/assets/137224335/77347516-e24e-459d-98ab-acbb49a3d4e8)![image](https://github.com/openaps/AndroidAPSdocs/assets/137224335/ca756b8e-efbc-4427-b281-ac953ce16718) - - - -For each question, there may be more than one answer that is correct! If an incorrect answer is selected, the question will be time locked for a certain amount of time (60 minutes) before you can go back and answer the question. - - -After updating to a new version of **AAPS**, new questions may be added to cover a prevalent issue picked up by **AAPS** or alternatively to test your knowledge of a new feature of **AAPS** as released. - - -When **AAPS** is installed for the first time, you will have to complete Objective 3 entirely in order to move onto Objective 4. Each objective is required to be completed in sequential order. New features will gradually be unlocked as progress is made through the objectives. - -__What happens if new questions are added later to Objective 3?__ From time to time, new features are added to **AAPS** which may require a new question to be added to Objective 3. As a result, any new question added to Objective 3 will be marked as “incomplete” because **AAPS** will require you to action this. As each Objective is independent, you will not lose the existing functionality of **AAPS** providing the other objectives remain completed. - - -## Objective 4: Starting on an open loop - -- Select Open Loop either from Preferences, or by pressing and holding the Loop button in top left of the home screen. -- Work through the [Preferences](../Configuration/Preferences.md) to set up for you. -- Manually enact at least 20 of the temporary basal rate suggestions over a period of 7 days; input them to your pump and confirm in AAPS that you have accepted them. Ensure this data shows in AAPS and Nightscout. -- Enable [temp targets](../Usage/temptarget.md) if necessary. Use hypo temp targets to prevent that the system will correct too strong because of a raising blood glucose after a hypo. - -### Reduce number of notifications - -- To reduce the Number of decisions to be made while in Open Loop set wide target range like 90 - 150 mg/dl or 5,0 - 8,5 mmol/l. - -- You might even want to wider upper limit (or disable Open Loop) at night. - -- In Preferences you can set a minimum percentage for suggestion of basal rate change. - - ```{image} ../images/OpenLoop_MinimalRequestChange2.png - :alt: Open Loop minimal request change - ``` - -- Also, you do not need to act every 5 minutes on all suggestions... - -## Objective 5: Understanding your open loop, including its temp basal recommendations - -- Start to understand the thinking behind the temp basal recommendations by looking at the [determine basal logic](https://openaps.readthedocs.io/en/latest/docs/While%20You%20Wait%20For%20Gear/Understand-determine-basal.html) and both the [forecast line in AAPS homescreen](Screenshots-prediction-lines)/Nightscout and the summary of outputs from the calculations in your OpenAPS tab. - -You will want to set your target higher than usual until you are confident in the calculations and settings. System allows - -- a low target to be a minimum of 4 mmol (72 mg/dl) or maximum of 10 mmol (180 mg/dl) -- a high target to be a minimum of 5 mmol (90 mg/dl) and maximum of 15 mmol (225 mg/dl) -- a temporary target as a single value can be anywhere in the range of 4 mmol to 15 mmol (72 mg/dl to 225 mg/dl) - -The target is the value that calculations are based on, and not the same as where you aim to keep your blood glucose values within. If your target is very wide (say, 3 or more mmol \[50 mg/dl or more\] wide), you will often find little AAPS action. This is because blood glucose is eventually predicted to be somewhere in that wide range and therefore not many fluctuating temporary basal rates are suggested. - -You may want to experiment with adjusting your targets to be a closer together range (say, 1 or less mmol \[20 mg/dl or less\] wide) and observe how the behavior of your system changes as a result. - -You can view a wider range (green lines) on the graph for the values you aim to keep your blood glucose within by entering different values in [Preferences](../Configuration/Preferences.md) > Range for Visualisation. - -```{image} ../images/sign_stop.png -:alt: Stop sign -``` - -### Stop here if you are open looping with a virtual pump - do not click Verify at the end of this objective. - -```{image} ../images/blank.png -:alt: blank -``` - -(Objectives-objective-6-starting-to-close-the-loop-with-low-glucose-suspend)= -## Objective 6: Starting to close the loop with Low Glucose Suspend - -```{image} ../images/sign_warning.png -:alt: Warning sign -``` - -### Closed loop will not correct high BG values in objective 6 as it is limited to low glucose suspend. High BG values have to be corrected manually by you! - -- Prerequisite: You need a good profile (basal, ISF, IC) already working in AAPS to start with Loop in Low Glucose Suspend mode. Otherwise you can run in a hypo which you have to manually correct. This will help you a lot to avoid having to treat a low glucose over a period of 5 days. **If you are still having frequent or severe low glucose episodes then consider refining your DIA, basal, ISF and carb ratios and do NOT start objective 6 at this time.** -- You don't have to change your settings now. During objective 6, the maxIOB setting is internally set to zero automatically. **This override will be reversed when moving to objective 7.** -- The system will override your maxIOB settings to zero, which means if blood glucose is dropping it can reduce basal for you. If blood glucose is rising then it will only increase basal if the basal IOB is negative from a previous Low Glucose Suspend. Otherwise basal rates will remain the same as your selected profile. **That means that you have to manually handle high values with insulin corrections.** -- If your basal IOB is negative (see screenshot below) a TBR > 100% can be issued also in objective 6. - -```{image} ../images/Objective6_negIOB.png -:alt: Example negative IOB -``` - -- Set your target range slightly higher than you usually aim for, just to be safe and have a bit more scurity buffer. -- Enable 'Low Glucose Suspend' mode either by by pressing and holding the Loop icon at the top right corner of the home screen and selecting the Loop - LGS mode icon. -- Watch how temporary basals are active by viewing the blue basal text on the homescreen or the blue basal render on the homescreen graph. -- You may temporarily experience spikes following treated hypos without the ability to increase basal on the rebound. - -(Objectives-objective-7-tuning-the-closed-loop-raising-max-iob-above-0-and-gradually-lowering-bg-targets)= -## Objective 7: Tuning the closed loop, raising maxIOB above 0 and gradually lowering BG targets - -- Select 'Closed Loop' either from [Preferences](../Configuration/Preferences.md) or by pressing and holding the Loop icon at the top right corner of the home screen, over a period of 1 day. - -- Raise your 'Maximum total IOB OpenAPS can’t go over' (in OpenAPS called 'max-iob') above 0. The default recommendation is "average mealbolus + 3x max daily basal" (for the SMB algorithm) or "3x max daily basal" (for the older AMA algorithm) but you should slowly work up to this until you know your settings work for you (max daily basal = the maximum hourly value in any time segment of the day). - - This recommendation should be seen as a starting point. If you set to the 3x and you are seeing moves that push you too hard and fast then lower that number. If you are very resistant, raise it very little at a time. - - ```{image} ../images/MaxDailyBasal2.png - :alt: max daily basal - ``` - -- Once confident on how much IOB suits your looping patterns, then reduce your targets to your desired level. - -(Objectives-objective-8-adjust-basals-and-ratios-if-needed-and-then-enable-autosens)= -## Objective 8: Adjust basals and ratios if needed, and then enable autosens - -- You can use [autotune](https://openaps.readthedocs.io/en/latest/docs/Customize-Iterate/autotune.html) as a one off to check your basals remain accurate or do a traditional basal test. -- Enable [autosens](../Usage/Open-APS-features.md) over a period of 7 days and watch the white line on the homescreen graph show how your sensitivity to insulin may be rising or falling as a result of exercise or hormones etc. and keep an eye in the OpenAPS report tab how AAPS is adjusting the basals and/or targets accordingly. - -*Don’t forget to record your looping in* [this form](https://bit.ly/nowlooping) *logging AAPS as your type of DIY loop software, if you have not already done so.* - -(Objectives-objective-9-enabling-additional-oref1-features-for-daytime-use-such-as-super-micro-bolus-smb)= -## Objective 9: Enabling additional oref1 features for daytime use, such as super micro bolus (SMB) - -- You must read the [SMB chapter in this wiki](Open-APS-features-super-micro-bolus-smb) and [chapter oref1 in openAPSdocs](https://openaps.readthedocs.io/en/latest/docs/Customize-Iterate/oref1.html) to understand how SMB works, especially what's the idea behind zero-temping. -- Then you ought to [rise maxIOB](Open-APS-features-maximum-total-iob-openaps-cant-go-over-openaps-max-iob) to get SMBs working fine. maxIOB now includes all IOB, not just added basal. That is, if given a bolus of 8 U for a meal and maxIOB is 7 U, no SMBs will be delivered until IOB drops below 7 U. A good start is maxIOB = average mealbolus + 3x max daily basal (max daily basal = the maximum hourly value in any time segment of the day - see [objective 7](Objectives-objective-7-tuning-the-closed-loop-raising-max-iob-above-0-and-gradually-lowering-bg-targets) for an illustration) -- min_5m_carbimpact default in absorption settings has changed from 3 to 8 going from AMA to SMB. If you are upgrading from AMA to SMB, you have to change it manually. - -(Objectives-objective-10-automation)= -## Objective 10: Automation - -- You have to start objective 10 to be able to use [Automation](../Usage/Automation.md). -- Make sure you have completed all objectives including exam [Objectives-objective-3-prove-your-knowledge](Objectives#objective-3-prove-your-knowledge). -- Completing previous objectives will not effect other objectives you have already finished. You will keep all finished objectives! - -(Objectives-objective-11-DynamicISF)= -## Objective 11: Additional Features such as DynamicISF - -- You have to start objective 11 to be able to use [DynamicISF](../Usage/Open-APS-features.md) - -(Objectives-go-back-in-objectives)= -## Go back in objectives - -If you want to go back in objectives for whatever reason you can do so by clicking at "clear finished". - -```{image} ../images/Objective_ClearFinished.png -:alt: Go back in objectives -``` - -## Objectives in Android APS before version 3.0 - -One objective was removed when Android APS 3.0 was released. Users of Android APS version 2.8.2.1 who are on older Android software (i.e. earlier than version 9) will be using an older set of objectives which can be found [here](../Usage/Objectives_old.md). diff --git a/docs/CROWDIN/ro/Usage/Objectives_old.md b/docs/CROWDIN/ro/Usage/Objectives_old.md deleted file mode 100644 index a3dc8861eae2..000000000000 --- a/docs/CROWDIN/ro/Usage/Objectives_old.md +++ /dev/null @@ -1,152 +0,0 @@ -# Objectives as of Android APS 2.8.2.1 - -This is not the latest version of the Android APS Objectives. This page details the Objectives that were in place prior to version 3.0. Anyone using an older version of Android (i.e. prior to Android 9) and Android APS version 2.8.2.1 should refer to this page. - -Please see [this page](../Usage/Objectives.md) for the current set of Objectives. - -AndroidAPS has a series of Objectives that need to be completed to walk you through the features and settings of safe looping. They ensure you have configured everything detailed in the sections above correctly, and that you understand what your system is doing and why so you can trust it. - -If you are **upgrading phones** then you can [export your settings](../Usage/ExportImportSettings.md) to keep your progress through the objectives. Not only will your progress through the objectives be saved, but also your safety settings such as max bolus etc. If you do not export and import your settings then you will need to start the objectives from the beginning again. It is a good idea to [backup your settings](../Usage/ExportImportSettings.html) frequently just in case. - -If you want to go back in objectives see [explanation below](../Usage/Objectives.md#go-back-in-objectives). - -## Objective 1: Setting up visualization and monitoring, analysing basals and ratios - -- Select the right blood glucose source for your setup. See [BG Source](../Configuration/BG-Source.md) for more information. -- Select the right Pump in ConfigBuilder (select Virtual Pump if you are using a pump model with no AndroidAPS driver for looping) to ensure your pump status can communicate with AndroidAPS. -- If using DanaR pump then ensure you have followed [DanaR Insulin Pump](../Configuration/DanaR-Insulin-Pump.md) instructions to ensure the link between pump and AndroidAPS. -- Follow instructions in [Nightscout](../Installing-AndroidAPS/Nightscout.md) page to ensure Nightscout can receive and display this data. -- Note that URL in NSClient must be **WITHOUT /api/v1/** at the end - see [NSClient settings in Preferences](../Configuration/Preferences.md#nsclient). - -*You may need to wait for the next blood glucose reading to arrive before AndroidAPS will recognise it.* - -## Objective 2: Learn how to control AndroidAPS - -- Perform several actions in AndroidAPS as described in this objective. - -- Click on the orange text "Not completed yet" to access the to-dos. - -- Links will be provided to guide you in case you are not familiar with a specific action yet. - - ![Screenshot objective 2](../images/Objective2_V2_5.png) - -## Objective 3: Prove your knowledge - -- Pass a multiple-choice exam testing your AndroidAPS knowledge. - -- Click on the orange text "Not completed yet" to access the page with the question and answering options. - - ![Screenshot objective 3](../images/Objective3_V2_5.png) - -- Links will be provided to guide you in case you are unsure about the correct answers yet. - -- The questions for objective 3 have been completely rewritten by native speakers as of AAPS 2.8. The new ones cover the same basic topics plus a few new ones. - -- These new questions will lead to some not answered questions even though you have successfully completed objective 3 in previous versions. - -- Unanswered questions will affect you only if you start a new objective. In other words: If you have already completed all objectives you can wait and answer the new questions later without loosing AAPS functions. - -## Objective 4: Starting on an open loop - -- Select Open Loop either from Preferences, or by pressing and holding the Loop button in top left of the home screen. -- Work through the [Preferences](../Configuration/Preferences.md) to set up for you. -- Manually enact at least 20 of the temporary basal rate suggestions over a period of 7 days; input them to your pump and confirm in AndroidAPS that you have accepted them. Ensure this data shows in AndroidAPS and Nightscout. -- Enable [temp targets](../Usage/temptarget.md) if necessary. Use hypo temp targets to prevent that the system will correct too strong because of a raising blood glucose after a hypo. - -### Reduce number of notifications - -- To reduce the Number of decisions to be made while in Open Loop set wide target range like 90 - 150 mg/dl or 5,0 - 8,5 mmol/l. - -- You might even want to wider upper limit (or disable Open Loop) at night. - -- In Preferences you can set a minimum percentage for suggestion of basal rate change. - - ![Open Loop minimal request change](../images/OpenLoop_MinimalRequestChange2.png) - -- Also, you do not need to act every 5 minutes on all suggestions... - -## Objective 5: Understanding your open loop, including its temp basal recommendations - -- Start to understand the thinking behind the temp basal recommendations by looking at the [determine basal logic](https://openaps.readthedocs.io/en/latest/docs/While%20You%20Wait%20For%20Gear/Understand-determine-basal.html) and both the [forecast line in AndroidAPS homescreen](../Getting-Started/Screenshots.md#prediction-lines)/Nightscout and the summary of outputs from the calculations in your OpenAPS tab. - -You will want to set your target higher than usual until you are confident in the calculations and settings. System allows - -- a low target to be a minimum of 4 mmol (72 mg/dl) or maximum of 10 mmol (180 mg/dl) -- a high target to be a minimum of 5 mmol (90 mg/dl) and maximum of 15 mmol (225 mg/dl) -- a temporary target as a single value can be anywhere in the range of 4 mmol to 15 mmol (72 mg/dl to 225 mg/dl) - -The target is the value that calculations are based on, and not the same as where you aim to keep your blood glucose values within. If your target is very wide (say, 3 or more mmol \[50 mg/dl or more\] wide), you will often find little AAPS action. This is because blood glucose is eventually predicted to be somewhere in that wide range and therefore not many fluctuating temporary basal rates are suggested. - -You may want to experiment with adjusting your targets to be a closer together range (say, 1 or less mmol \[20 mg/dl or less\] wide) and observe how the behavior of your system changes as a result. - -You can view a wider range (green lines) on the graph for the values you aim to keep your blood glucose within by entering different values in [Preferences](../Configuration/Preferences.md) > Range for Visualisation. - -![Stop sign](../images/sign_stop.png) - -### Stop here if you are open looping with a virtual pump - do not click Verify at the end of this objective. - -![blank](../images/blank.png) - -## Objective 6: Starting to close the loop with Low Glucose Suspend - -![Warning sign](../images/sign_warning.png) - -### Closed loop will not correct high bg values in objective 6 as it is limited to low glucose suspend. High bg values have to be corrected manually by you! - -- Select Closed Loop either from [Preferences](../Configuration/Preferences.md) or by pressing and holding the Open Loop button in the top left of the home screen. - -- Set your target range slightly higher than you usually aim for, just to be safe. - -- Watch how temporary basals are active by viewing the blue basal text on the homescreen or the blue basal render on the homescreen graph. - -- Ensure your settings have supported AndroidAPS to avoid having to treat a low glucose over a period of 5 days. If you are still having frequent or severe low glucose episodes then consider refining your DIA, basal, ISF and carb ratios. - -- You don't have to change your settings. During objective 6 maxIOB setting is internally set to zero automatically. This override will be reversed when moving to objective 7. - -- The system will override your maxIOB settings to zero, which means if blood glucose is dropping it can reduce basal for you, but if blood glucose is rising then it will only increase basal if the basal IOB is negative (from a previous Low Glucose Suspend), otherwise basal rates will remain the same as your selected profile. - - ![Example negative IOB](../images/Objective6_negIOB.png) - -- If your basal IOB is negative (see screenshot above) a TBR > 100% can be issued also in objective 6. - -- You may temporarily experience spikes following treated hypos without the ability to increase basal on the rebound. - -## Objective 7: Tuning the closed loop, raising max IOB above 0 and gradually lowering BG targets - -- Raise your 'Maximum total IOB OpenAPS can’t go over' (in OpenAPS called 'max-iob') above 0 over a period of 1 day, the default recommendation is "average mealbolus + 3x max daily basal"(for SMB algorithm) or "3x max daily basal" (for older AMA algorithm) but you should slowly work up to this until you know your settings work for you (max daily basal = the maximum hourly value in any time segment of the day). - - This recommendation should be seen as a starting point. If you set to the 3x and you are seeing moves that push you to hard and fast then lower that number. If you are very resistant raise it a very little at a time. - - ![max daily basal](../images/MaxDailyBasal2.png) - -- Once confident on how much IOB suits your looping patterns then reduce your targets to your desired level. - -## Objective 8: Adjust basals and ratios if needed, and then enable autosens - -- You can use [autotune](https://openaps.readthedocs.io/en/latest/docs/Customize-Iterate/autotune.html) as a one off to check your basals remain accurate or do a traditional basal test. -- Enable [autosens](../Usage/Open-APS-features.md) over a period of 7 days and watch the white line on the homescreen graph show how your sensitivity to insulin may be rising or falling as a result of exercise or hormones etc. and keep an eye in the OpenAPS report tab how AndroidAPS is adjusting the basals and/or targets accordingly. - -*Don’t forget to record your looping in* [this form](https://bit.ly/nowlooping) *logging AndroidAPS as your type of DIY loop software, if you have not already done so.* - -## Objective 9: Try additional features for daytime use and gain confidence in your closed loop system - -- Before AAPS version 2.7 meal assist (MA) was the basic algorithm for AAPS and completing objective 8 was necessary to activate [advanced meal assist (AMA)](../Usage/Open-APS-features.md#advanced-meal-assist-ama). -- As [advanced meal assist (AMA)](../Usage/Open-APS-features.md#advanced-meal-assist-ama) is the standard algorithm from AAPS version 2.7 onwards use the following 28 days to try features you haven't used yet and get more confident with you closed loop system. - -## Objective 10: Enabling additional oref1 features for daytime use, such as super micro bolus (SMB) - -- You must read the [SMB chapter in this wiki](../Usage/Open-APS-features.md#super-micro-bolus-smb) and [chapter oref1 in openAPSdocs](https://openaps.readthedocs.io/en/latest/docs/Customize-Iterate/oref1.html) to understand how SMB works, especially what's the idea behind zero-temping. -- Then you ought to [rise maxIOB](../Usage/Open-APS-features.md#maximum-total-iob-openaps-cant-go-over-openaps-max-iob) to get SMBs working fine. maxIOB now includes all IOB, not just added basal. That is, if given a bolus of 8 U for a meal and maxIOB is 7 U, no SMBs will be delivered until IOB drops below 7 U. A good start is maxIOB = average mealbolus + 3x max daily basal (max daily basal = the maximum hourly value in any time segment of the day - see [objective 7](../Usage/Objectives#objective-7-tuning-the-closed-loop-raising-max-iob-above-0-and-gradually-lowering-bg-targets) for an illustration) -- min_5m_carbimpact default in absorption settings has changed from 3 to 8 going from AMA to SMB. If you are upgrading from AMA to SMB, you have to change it manually. - -## Objective 11: Automation - -- You have to start objective 11 to be able to use [Automation](../Usage/Automation.md). -- Make sure you have completed all objectives including exam [../Usage/Objectives.md#objective-3-prove-your-knowledge](../Usage/Objectives#objective-3-prove-your-knowledge). -- Completing previous objectives will not effect other objectives you have already finished. You will keep all finished objectives! - -## Go back in objectives - -If you want to go back in objectives for whatever reason you can do so by clicking at "clear finished". - -![Go back in objectives](../images/Objective_ClearFinished.png) diff --git a/docs/CROWDIN/ro/Usage/Smoothing-Blood-Glucose-Data-in-xDrip.md b/docs/CROWDIN/ro/Usage/Smoothing-Blood-Glucose-Data-in-xDrip.md deleted file mode 100644 index 716234b04a15..000000000000 --- a/docs/CROWDIN/ro/Usage/Smoothing-Blood-Glucose-Data-in-xDrip.md +++ /dev/null @@ -1,33 +0,0 @@ -(Smoothing-Blood-Glucose-Data-in-xDrip-smoothing-blood-glucose-data)= - -# Smoothing blood glucose data - -If BG data is jumpy/noisy, AAPS may dose insulin incorrectly resulting in high or low BG. For this reason it’s important to disable the loop until the problem is resolved. Depending on your CGM such issues may be due to the CGM’s configuration or sensor problems/site issues. You may need to replace your CGM sensor to resolve this. - -Some CGM systems have internal algorithms to detect the noise level in the readings and AAPS can use this information to avoid giving SMBs if the BG data is too unreliable. However, some CGMs do not transmit this data and for these BG sources 'Enable SMB always' and 'Enable SMB after carbs' are disabled for safety reasons. - -## Dexcom sensors - -### Build Your Own Dexcom App - -When using [BYODA](DexcomG6-if-using-g6-with-build-your-own-dexcom-app) your BG data is smooth and consistent. Furthermore you can take advantage of Dexcom back-smoothing. There are no restrictions in using SMBs, because the noise-level data is shared with AAPS. - -### xDrip+ with Dexcom G6 or Dexcom ONE - -Noise-level data and smooth BG readings are only shared with AAPS if you use xDrip+ [native mode](https://navid200.github.io/xDrip/docs/Native-Algorithm). Using native mode, there are no restrictions in using SMBs. - -### Dexcom G6 or Dexcom ONE with xDrip+ Companion Mode - -The noise-level data is not shared with AAPS using this method. Therefore 'Enable SMB always' and 'Enable SMB after carbs' are disabled. - -## Freestyle Libre sensors - -### xDrip+ with FreeStyle Libre - -None of the FreeStyle Libre systems (FSL1, FSL2, or FSL3) broadcast any information about the level of noise detected in the readings, and therefore 'Enable SMB always' and 'Enable SMB after carbs' are disabled for all setups using the FreeStyle Libre. - -In addition, many people have reported the FreeStyle Libre often produces noisy data. In xDrip+ there are a few options to help with this: - -**Smooth Sensor Noise.** In xDrip+ Settings > xDrip+ Display Settings ensure that Smooth Sensor Noise is turned on. This attempts to apply smoothing to noisy data. - -**Smooth Sensor Noise (Ultrasensitive).** If you are still seeing noisy data in xDrip+ you can apply more aggressive smoothing using the Smooth Sensor Noise (Ultrasensitive) setting. This will attempt to apply smoothing even on very low levels of detected noise. To do this, first enable [engineering mode](Enabling-Engineering-Mode-in-xDrip.md) in xDrip+. Then navigate to Settings > xDrip+ Display Settings and turn on Smooth Sensor Noise (Ultrasensitive). \ No newline at end of file diff --git a/docs/CROWDIN/ro/Usage/autotune_b.md b/docs/CROWDIN/ro/Usage/autotune_b.md deleted file mode 100644 index 989d9c230519..000000000000 --- a/docs/CROWDIN/ro/Usage/autotune_b.md +++ /dev/null @@ -1,186 +0,0 @@ -# How to use Autotune plugin - -Documentation about Autotune algorythm can be found in [OpenAPS documentation](https://openaps.readthedocs.io/en/latest/docs/Customize-Iterate/autotune.html). - -Autotune plugin is an implementation of OpenAPS autotune algorythm within AAPS. - -**Currently Autotune Plugin is only available in dev branch with Engineering mode.** - -## Autotune user interface - -![Autotune default screen](../images/Autotune/Autotune_1b.png) - -- You can select in the Profile dropdown menu the input profile you want to tune (by default your current active profile is selected) - - Note: each time you select a new profile, previous results will be removed and Tune days parameter will be set to default value -- Then Tune days is to select the number of days used in calculation to tune your profile. The minimum value is 1 day and the maximum value 30 days. This number should not be too small to get correct iterative and smooth results (above 7 days for each calculation) - - Note: each time you change Tune days parameter, previous results will be removed -- Last Run il a link that recover your latest valid calculation. If you didn't launch Autotune on current day, or if previous results was removed with a modification of calculation parameter above, then you can recover parameters and results of the latest successfull run. -- Warning show you for example some information about selected profile (if you have several IC values or several ISF values) - - Note: Autotune calculation works with only a single IC and a single ISF value. There is currently no existing Autotune algorythm to tune a circadian IC or circadian ISF. If your input profile has several values, you can see in warning section the average value taken into account to tune your profile. -- Check Input Profile button open the Profile Viewer to allow you a quick verification of your profile (Units, DAI, IC, ISF, basal and target) - - Note: Autotune will only tune your IC (single value), ISF (single value) and basal (with circadian variation). Units, DAI and target will remain unchanged in output profile. - -- "Run Autotune" will launch Autotune calculation with selected profile and the number of Tune days - - Note: Autotune calculation can take a long time. Once launched, you can switch to another view (home, ...) and come back later in Autotune plugin to see results - -![Autotune Run start](../images/Autotune/Autotune_2b.png) - -- Then during the run you will see intermediate results below - - - Note: During run, settings are locked, so you cannot change anymore selected input profile or the number of day. You will have to wait the end of current calculation if you want to launch another run with other parameters. - - ![Autotune during run](../images/Autotune/Autotune_3b.png) - -- When Autotune calculation is finished, you will see the result (Tuned profile) and four buttons below. - -![Autotune Result](../images/Autotune/Autotune_4b.png) - -- It's important to always compare input profile (column "Profile"), output profile (column "Tuned") and the percentage of variation for each value (Column "%"). - -- For basal rates, you also have the number of "missing days". You have missing days when Autotune don't have enough data categorized as "Basal" to tune basal rate for this period (for example after each meal when you have carbs absorption). This number should be as low as possible especially when basal is important (for example during the night or at the end of the afternoon) - -- The "Compare profiles" button open the profile comparator view. Input profile is in blue, and output profile (named "Tuned") is in red. - - - Note: in the example below input profile has circadian variation for IC and ISF, but output calculated profile has a single value. If it's important for you to get a circadian output profile see [Circadian IC or ISF profile](#circadian-ic-or-isf-profile) below. - - ![Autotune Compare profiles](../images/Autotune/Autotune_5.png) - -- If you trust results (low percentage of variation between input profile and output profile), you can click on "Activate profile" button and then click on OK to validated. - - - Activate Tuned profile will automatically create a new profile "Tuned" in your Local profile plugin. - - If you already have a profile named "Tuned" in your local profile plugin, then this profile will be updated with calculated Autotune profile before the activation - - ![Autotune Activate profile](../images/Autotune/Autotune_6.png) - -- If you think Tuned profile must be adjusted (for example if you think some variation are too important), then you can click on "Copy to local profile" button - - - A new profile with the prefix "Tuned" and the date and time of the run will be created in local profile plugin - -![Autotune Copy to local profile](../images/Autotune/Autotune_7.png) - -- You can then select local profile to edit the Tuned profile (it will be selected by default when you open Local profile plugin) - - - the values in local profile will but rounded in the user interface to your pump capabilities - - ![Autotune local profile update](../images/Autotune/Autotune_8.png) - -- If you want to replace your input profile with Autotune result, click on "Update input profile" button and validate the Popup with OK - - - Note: if you click on "Activate profile" after "Update input profile", then you will activate your updated profile and not the default "Tuned" profile? - - ![Autotune Update input profile](../images/Autotune/Autotune_9.png) - -- If you have updated your input profile, then the "Update input profile" button is replaced by "Revert input profile" button (see screenshot below). You can that way immediatly see if your current input profile in Local profile plugin already include the result of last run or not. You also have the possibility to recover you input profile without autotune result with this button - - ![Autotune Update input profile](../images/Autotune/Autotune_10.png) - - - -## Autotune settings - -### Autotune plugin settings - -![Autotune default screen](../images/Autotune/Autotune_11.png) - -- Automation Switch Profile (default Off): see [Run Autotune with an automation rule](#run-autotune-with-an-automation-rule) below. If you change this setting to On, the input profile will automatically be updated by the Tuned profile, and it will be activated. - - **Be Carefull, you must trust and verified during several following days that after an update and activation of Tuned profile without modification, it improves your loop** - -- Categorize UAM as basal (default On): This setting is for the users using AndroidAPS without any carbs entered (Full UAM). It will prevent (when Off) to categorize UAM as basal. - - Note: if you have at least one hour of Carbs absorption detected during one day, then all data categorized as "UAM" will be categorized as basal, whatever this setting (On or Off) -- Number of days of data (default 5): You can define default value with this setting. Each time your select a new profile in Autotune plugin, Tune days parameter will be replaced by this default value -- Apply average result in circadian IC/ISF (default Off): see [Circadian IC or ISF profile](#circadian-ic-or-isf-profile) below. - -### Alte setări - -- Autotune also uses Max autosens ratio and Min autotsens ratio to limit variation. You can see and adjust these values in Config Builder > Sensitivity detection plugin > Settings > Advanced Settings - - ![Autotune default screen](../images/Autotune/Autotune_12.png) - - - -## Advanced feature - -### Circadian IC or ISF profile - -- If you have important variation of IC and/or you ISF in your profile, and you fully trust in your circadian time and variation, then you can set "Apply average result in circadiant IC/ISF" - - - Note that Autotune calculation will always be done with a single value, and circadian variation will not be tuned by Autotune. This setting only apply average variation calculated for IC and/or ISF on your circadian values - -- See on screenshot below Tuned profile with Apply average variation Off (on the left) and On (on the right) - - ![Autotune default screen](../images/Autotune/Autotune_13.png) - - - -### Tune specific days of the week - -- If you click on the checkbox with the eye on the right of "Rune days" parameter, you will see the day selection. You can specify which day of the week should be included in Autotune calculation (in screenshot below you can see an example for "working days" with Saturday and Sunday removed from autotune calculation) - - If the number of day included in Autotune calculation is lower than the number of Tune days, then you will see how many days will be included on the right of Tune days selector (10 days in the example below) - - This setting gives good results only if the number of remaining days is not to small (for example if you Tune a specific profile for week end days with only Sunday and Saturday selected, you should select a minimum of 21 or 28 Tune days to have 6 or 8 days included in Autotune calculation) - -![Autotune default screen](../images/Autotune/Autotune_14b.png) - -- During Autotune calculation, you can see the progress of the calculations ("Partial result day 3 / 10 tuned" on example below) - - ![Autotune default screen](../images/Autotune/Autotune_15b.png) - -## Run Autotune with an automation rule - -First step is to define correct trigger for an automation rule with Autotune: - -Note: for more information on how to set an automation rule, see [here](./Automation.rst). - -- You should select Recurring time trigger: only run Autotune once per day, and autotune is designed to be runned daily (each new run you shift one day later and quickly profile modification should be tiny) - - ![Autotune default screen](../images/Autotune/Autotune_16.png) - -- It's better at the beginning to run Autotune during the day to be able to check results. If you want to run Autotune during the night, you have to select in the trigger 4AM or later to include current day in next Autotune Calculation. - - ![Autotune default screen](../images/Autotune/Autotune_17.png) - -- Then you can select "Run Autotune" Action in the list - - ![Autotune default screen](../images/Autotune/Autotune_18.png) - -- You can then select Autotune Action to adjust parameters for your run. Default parameters are "Active Profile", default Tune days value defined in Autotune Plugin preferences, and All days are selected. - - ![Autotune default screen](../images/Autotune/Autotune_19b.png) - -- After a few days, if you fully trust Autotune results and percentage of modification is low, you can modify [Autotune settings](#autotune-plugin-settings) "Automation Switch Profile" to enabled to automatically update and activate profile tuned after calculation. - -Note: if you want to automatically tune profiles for specific days of the week (for example a profile for "Weekend days" and another one for "Working days"), then create one rule for each profile, select the same days in Trigger and in Autotune Action, Tune days must be high enough to be sure tuning will be done with at least 6 or 8 days, and don't forget to select time after 4AM in trigger... - -- See below an example of rule to tune "my profile" on all "Working days" with 14 Tune days selected (so only 10 days included in autotune calculation). - -![Autotune default screen](../images/Autotune/Autotune_20b.png) - - - -## Tips and trick's - -Autotune works with information existing in your database, so if you just installed AAPS on a new phone, you will have to wait several days before being able to launch Autotune with enough days to get relevant results; - -Autotune is just an help, it's important to regularly check if you agree with calculated profile. If you have any doubt, change Autotune settings (for example the number of days) or copy results in local profile and adjust profile before using it. - -Always use Autotune several days manually to check results before applyling them. And it's only when you fully trust Autotune results, and when variation becomes tiny between previous profile and calculated profile than you start to use Automation (Never before) - -- Autotune can work very well for some users and not for others, so **If you don't trust Autotune result, don't use it** - -It's also important to analyse Autotune results to understand (or try to understand) why Autotune propose these modifications - -- you can have a whole increase or decrease of the strength of your profile (for example increase of total basal associated to decrease of ISF and IC values). it could be associated to several following days with autosens correction above 100% (more agressivity required) or below 100% (you are more sensitive) -- Sometimes Autotune propose a different balance between basal rates and IC/ISF (for ex lower basal and more aggressive IC/ISF) - -We advise to not use Autotune in the following cases: - -- You don't enter all your carbs - - If you don't enter carbs correction for an hypoglycemia, Autotune will see an unexcepted increase of your BG value and will increase your basal rates the ' hours earlier, it could be the opposite of what you need to avoid hypo, especially if it's in the middle of the night. That's why it's important to enter all carabs especially correction for hypo. -- You have a lot of period with UAM detected during the day. - - Do you have entered all your carbs and correctly estimated your Carbs ? - - All UAM periods (except if you enter no carbs during a day and categorized UAM as basal is disabled), all your UAM periods will be categorized as basal, this can increase a lot your basal (much more than necessary) - -- Your carbs absorption is very slow: if most of your carbs absorption are calculated with min_5m_carbimpact parameter (you can see these periods with a little orange dot in the top of COB curve), the calculation of COB could be wrong and leads to wrong results. - - We you practice sport, you are generally more sensitive and your BG doesn't rise a lot, so during or after an exercice, it's usual to see some periods with slow carbs. But if you have too often unexpected slow carb absorption, then you may need a profile adjustment (higher value of IC) or a min_5m_carbimpact a bit to high. -- You have a "very bad days", for example stuck several hours in hyperglycemia with a huge amount of insulin to be able to go down within the range, or after a sensor change you got long periods of wrong BG values. -- If the percentage of modification is too important - - You can try to increase the number of days to get smoother results \ No newline at end of file diff --git a/docs/CROWDIN/ro/Usage/making-sport-with-AAPS.md b/docs/CROWDIN/ro/Usage/making-sport-with-AAPS.md deleted file mode 100644 index 79d2f1c38223..000000000000 --- a/docs/CROWDIN/ro/Usage/making-sport-with-AAPS.md +++ /dev/null @@ -1,185 +0,0 @@ -# making sport with AAPS - -In this section we want to address the topic of sport with AAPS. - -The aim is to show you how AAPS can help you to continue doing your favorite sport more easily or even to start doing it. It is relatively common for new type 1 diabetics to ask whether exercise is still possible for them, even if the answer in the training courses is actually a clear yes. Exercise is not only good for healthy people, but also for type 1 diabetics and even moderate exercise can even help to stabilize the blood sugar curve overall. - -:::{admonition} consult with your diabetes team after reading - -::: - -The difficulty here is that the prerequisites that someone brings with them and the expectations of what sport means to them are very different. - -Since we can assume that experienced top athletes with T1D who use AAPS are unlikely to look it up here, we deliberately set the bar low for ourselves when writing and for you when reading and using it, so that as many people as possible can benefit from it. - -Since even sport as a category is far too imprecise, as the effects of endurance sports differ greatly from strength training, for example, we are trying to break it down by type of sport. - -To be concrete and give you something you can test yourself we arrange the explanaiton around a concrete example and explain to you they action, reactions and effects. - -:::{admonition} more examples wanted - -The focus should always be on how others can do sport and not on the top performance someone has achieved. - -It's really about the basics. Your experience, which you share here, can help others to pursue their beloved sport more quickly and successfully and is therefore important. -::: - -## Cycling - -:::{admonition} take a friend with you - at least on your first trials -:class: information -A gerneral very good idea can be to take a good friend with you on the first rides. -This is especially important if you are not experienced in T1D. -Always keep in mind please: arrival comes before speed! Safety for you and the others in road traffic is very, very important. -::: - -### Example - -Let's take about 60 minutes of cycling on a flat route with a moderate heart rate as an example. - -1. we take a flat route in order to have an even load for the first exercise. This is not about performance, but purely about learning how you should react to changes in blood glucose. -2. we take the heart rate as an indicator of the load, as it is easy to see whether you are under load or not. -3. we set ourselves the goal of doing a relaxed lap around the neighborhood and focus on staying within our target range during the lap. In my case, this would be 70 <= x <= 180 mg/dl. - -We **don't** take the speed, as this is heavily dependent on personal physical conditions as well as the bike and surface used. It is therefore not very meaningful. - -You should know from the diabetes training courses you have attended that during endurance sports cycling, the insulin active in the body works significantly better than during times without physical exertion. The insulin active in the body is referred to as insulin on board (IoB). It is our most important parameter when cycling with T1D. - -We try to keep the IoB as low as possible at the start and during exercise. IoB should be around 0 or even slightly negative. You can get it there by not eating 3-4 hours before exercise. In the beginning it can also be helpful to exercise in the morning before breakfast, as with the right profile you should always have around 0 for IoB in the morning. - -AAPS shows us the IoB value on the home screen on the left under the blood glucose value. - -![IoB](../images/cycling_20240104-174035.png) - -:::{admonition} ignoring the IoB rule increases the risk for roller coaster BG dramatically -:class: danger -If you ignore this rule, you can still go cycling, but it will be much more difficult to keep your blood sugar levels in balance, so it is better to save this for later tests after several successful simple tests. -::: - -As you should know from the diabetes training courses, you should reduce the basal rate during exercise. The factor is individual. I have found a value of 50% in tests to be suitable for me. - -In AAPS, you should therefore change your profile to 50% before exercise and keep it active until the end of exercise. Some people even do it a certain amount of time before, e.g. 1 hour. Unfortunately, the pre-run is also individual. We will come to the post-run later. - -You should use two carbohydrates during exercise. - -1. medium-fast carbohydrates for the insulin still in the body and -2. very fast carbohydrates to prevent slipping into a hypo. - -For medium-fast carbohydrates, I treat myself to cookies or a banana before exercise, for example. You can also use something else that is more suitable for you. -For very fast carbohydrates, I take 3 teaspoons of dissolved glucose per 100 ml of still water in a 500 ml water bottle on my bike. If I'm cycling longer distances, I take a larger bottle with me and, if necessary, packaged glucose to refill the bottle. I add a little lemon juice for flavor. You can also use something other than lemon juice for the taste. You shouldn't change anything about the dextrose, as dissolved dextrose raises blood sugar levels super quickly. If you only take it in sips, your blood sugar won't go super high either! You can also do this tip at home beforehand as a dry run and see how quickly the change shows up on the CGMS. - -Why do I place so much emphasis on fast carbohydrates? - -1. once you are in a slight hypo, you may get back into the normal range by drinking the dextrose solution. As a rule, however, the oscillation of the curve then begins, which leads to a rollercoaster ride of the blood sugar. You may even be able to keep this within your target range, but you must be constantly vigilant. Without a hypo it is simply the most stable. -2. if you even slip into a somewhat severe hypo (without the need for outside help, of course), you may even have to pause briefly to avoid getting stuck in the hypo. - With both hypos, there is a risk that you will be tempted to switch from drinking 2-3 sips at a time to larger quantities. Not too bad at first, until the oscillation sets in and pushes you into a hyper. You can correct this, but your blood sugar will most likely go on a rollercoaster ride. - -What else is helpful, but not absolutely necessary? -It is important to keep an eye on your blood sugar, as your blood sugar can change enormously (e.g. 30 - 50 mg/dl) within 15 minutes of riding and a little more IoB or a basal rate that is still too high. The best way to keep an eye on it is if it is visible on the handlebars or if it is also displayed on your watch. It is even possible to install an additional app on some Garmin GPS bike computers that displays the blood glucose from XDrip or Nightscout as a data field on the bike computer. The additional app was developed by Andreas May from the T1D community. It is available free of charge in the official connect IQ Store. Certainly an interesting option for riders interested in sports. - -[Link to Andreas May Data Field App on connect IQ store](https://apps.garmin.com/de-DE/apps/5a3e2cda-12f0-4afd-88ed-000e67a68d84) - -Here is a picture of my Garmin Edge 530 bike computer with map, blood sugar and heart rate. - -![Garmin Edge 530 with BG data field](../images/cycling_IMG_1087.jpeg) - -After you have eaten the medium fast carbohydrates (24 - 36 g I take) and the blood sugar is above 100 mg/dl but also below 160 mg/dl, I carry out the profile change to 50% and set the activity temp target. - -:::{admonition} disable SMBs during high temp targets if necessary -:class: danger -Attention: If you prefer not to receive SMBs during the sport, please disable the option "Enable SMB with hight temp targets" in the settings of SMB or DynIFS Plugin. -::: - -The following picture shows the start and end of the sport. The end was specified as the duration when the profile was changed at the start. - -The temporary profile change has the following effects - -1. for a period of 60 minutes -2. a reduction to 50% of the profile and -3. the target is raised by clicking on the Activity Target option, which may have the side effect of disabling the SMBs - see above. - -![profile switch with temp target](../images/cycling_20240104-174056.png) - -The second image shows that the start at IoB was started towards 0. - -![IoB around 0](../images/cycling_20240104-174111.png) - -If the blood sugar drops faster than 15 mg/dl in 5 minutes or if it is at 120 mg/dl and tends to fall, I drink 1-2 sips of dissolved glucose. Then I wait for the next value and proceed as described above. - -You can hardly see it here, but at the beginning I took 2 sips from the bottle several times when my blood sugar started to fall. When it stabilized, I didn't need any more glucose. - -Here is the picture that illustrates this. The chart is saved on the Garmin as a result of the activity. - -![BG chart Garmin](../images/cycling_20240104-174431.png) - -If you should suddenly break out upwards, i.e. above 180 mg/dl, you should consider whether you should make a correction bolus. Caution: Remember the factor and apply it to the correction, otherwise the correction will be too strong. - -If your blood sugar drops below 80 mg/dl, take a break and drink two sips until your blood sugar is back above 100 mg/dl. - -At the end of the ride, the profile change should be finished as the time is up. - -Since we only rode easy for 60 minutes, there shouldn't be a big muscle bulking effect continuing to pull carbohydrates from your blood sugar. However, if it felt strenuous to you, keep an eye on it. This is especially true if you then go straight to bed. It may be better to change your profile to e.g. 80% for sleep. You may come out of sleep slightly too high, but it's better than having a hypo at night. Over time, you will surely find out what happens to you. - -The following pictures show the low intensity of the sport. - -The elevation profile -![](../images/cycling_20240104-174314.png) - -Speed with average and maximum speed - -![](../images/cycling_20240104-174326.png) - -Note the pause at the level crossing, which is also reflected in the heart rate. - -The heart rate. -![](../images/cycling_20240104-174337.png) - -The training effect. -![](../images/cycling_20240104-174358.png) - -The time in the different heart rate training zones. -![](../images/cycling_20240104-174423.png) - -After succesfully mastering this simple example you could go for further targets by stretching - -1. the distance and time -2. the load during the ride -3. the elevation during the right which should make a big impact on the more necessary carbs or further reduction of IoB and percentage of profile switch. - -Based on my experiences I would not expect to come back 100% with time in range over the whole and every ride. - -### Tipps - -I already gave some tipps for during the ride above. - -Here are some further tipps what can go wrong and how you can act to prevent it or react to compensate it. - -#### sky rocket high after ride - -During the ride everything was fine but after siting down and relax the blood sugar go sky rocket high. - -**Possible reason:** This happens when you have drunk too much dissolved glucose. - -**Reaction:** Drink 500 ml water, go to the shower and then control again. Latest after 30 minutes think about giving a correction bolus but be careful when it is short for bed time. Therefore it can be very good to make the first try runs on weekend mornings. - -**Action:** Next time be a bit more cautious in drinking from the dissolved glucose. - -#### hypo during ride - -During the ride you are going into hypo and can't recover your blood sugar during cycling. - -**Possible reason:** Your body cannot absorb enough carbohydrates quickly enough during exercise. - -**Reaction:** Take a rest and corrrect your blood sugar with drinking dissolved glucose. Stay calm: arrival comes before speed. - -**Action:** Did you started with IoB near 0? Have you eaten a small amount of middle fast carbs? Can you increase this or are the not fast enough for your body? Is it possible to prevent going into hypo by reducing the factor for the profile switch? Have you disbaled SMBs during ride as explained above? - -#### sky rocket high during ride - -During the ride your blood sugar goes sky rocket high. - -**Possible reason:** You have got taken too much carbs for your IoB at that time. Beneath for sure the typical technical problems with your -insulin pump like leakage or blockage of the catheder! - -**Reaction:** If it is too high for you take a rest and correct with a bolus. Keep in mind that you must ride home and therefore make it carefully. Drink 500 ml pure water without carbs. Stay calm: arrival comes before speed. - -**Action:** Have you eaten too much? Especially have you drunk too much from the dissolved glucose during the ride? Is your percentage of reduction the profile during profile switch too low and you can increase this? diff --git a/docs/CROWDIN/ro/Where-To-Go-For-Help/How-to-get-support.md b/docs/CROWDIN/ro/Where-To-Go-For-Help/How-to-get-support.md deleted file mode 100644 index b58ecc8978b6..000000000000 --- a/docs/CROWDIN/ro/Where-To-Go-For-Help/How-to-get-support.md +++ /dev/null @@ -1,11 +0,0 @@ -# How to get support - -**Level 1:** Wiki - we now have a search function! - -**Level 2:** [Facebook](https://www.facebook.com/groups/AndroidAPSUsers/) OR [gitter](https://gitter.im/MilosKozak/AndroidAPS) - -**Level 3:** Gitter (if FB did not get results, wait at least a couple of hours (plural)!!! Direct crossposts will be ignored/deleted on both channels!!!) - -**Level 4:** Create an issue with logs and time of the issue - -**Level 5:** PM (only if personal data is involved that should not go in a public channel) \ No newline at end of file diff --git a/docs/CROWDIN/ro/buildingAAPS.md b/docs/CROWDIN/ro/buildingAAPS.md deleted file mode 100644 index 98164a09e49b..000000000000 --- a/docs/CROWDIN/ro/buildingAAPS.md +++ /dev/null @@ -1,28 +0,0 @@ -# Dummy - -## This is a dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - - -## This is another dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - - -## This is another another dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - diff --git a/docs/CROWDIN/ro/completingObjetives.md b/docs/CROWDIN/ro/completingObjetives.md deleted file mode 100644 index 98164a09e49b..000000000000 --- a/docs/CROWDIN/ro/completingObjetives.md +++ /dev/null @@ -1,28 +0,0 @@ -# Dummy - -## This is a dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - - -## This is another dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - - -## This is another another dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - diff --git a/docs/CROWDIN/ro/dummy.md b/docs/CROWDIN/ro/dummy.md deleted file mode 100644 index 98164a09e49b..000000000000 --- a/docs/CROWDIN/ro/dummy.md +++ /dev/null @@ -1,28 +0,0 @@ -# Dummy - -## This is a dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - - -## This is another dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - - -## This is another another dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - diff --git a/docs/CROWDIN/ro/intro.md b/docs/CROWDIN/ro/intro.md deleted file mode 100644 index 0b441085b769..000000000000 --- a/docs/CROWDIN/ro/intro.md +++ /dev/null @@ -1,291 +0,0 @@ -![20-06-23v2 AAPS simple overview-cropped](https://github.com/openaps/AndroidAPSdocs/assets/94044064/e505b73b-09a0-42a4-a1ab-b830a0741234) - -# Introduction to APS and AAPS - -## What is an “Artificial Pancreas System”? - -A human pancreas does a lot of things besides regulating blood sugar. However, the term **“Artificial Pancreas System” (APS)** usually refers to a system which works to automatically keep blood sugar levels within healthy limits. - -The most basic way to do this is by detecting **glucose levels**, using these values to do **calculations**, and then delivering the (predicted) right amount of **insulin** to the body. It repeats the calculation, every few minutes, 24/7. It uses **alarms** and **alerts** to inform the user if intervention or attention is needed. This system is typically made up of a **glucose sensor**, an **insulin pump** and an **app** on a phone. - -You can read more about the different artificial pancreas systems currently in use and in development in this 2022 review article: - -![Frontiers](./images/FRONTIERS_Logo_Grey_RGB.png) [Future Directions in Closed-Loop Technology](https://www.frontiersin.org/articles/10.3389/fendo.2022.919942/full#:~:text=Fully%20closed%2Dloop%20systems%2C%20unlike,user%20input%20for%20mealtime%20boluses). - -In the near future, some so-called "dual-hormone" systems will also have the ability to infuse glucagon alongside insulin, with the aim of preventing severe hypos and allowing even tighter blood glucose control. - -An artificial pancreas can be thought of as an [“autopilot for your diabetes”]. (https://www.artificialpancreasbook.com/) What does that mean? In an aircraft, an autopilot does not do the complete job of the human pilot, the pilot cannot sleep through the entire flight. The autopilot aids the work of the pilot. It relieves them of the burden of permanently monitoring the aircraft, allowing the pilot to concentrate on wider monitoring from time to time. The autopilot receives signals from various sensors, a computer evaluates them together with the pilot’s specifications and then makes the necessary adjustments, alerting the pilot to any concerns. The pilot no longer has to worry about constantly making decisions. - -## What does hybrid closed loop mean? - -The best solution for type 1 diabetes would be a “functional cure” (probably an implant of pancreatic cells which are protected from the immune system). While we are waiting for that, a “full closed loop” artificial pancreas is probably the next best thing. This is a tech system that doesn’t need any user input (like bolusing insulin for meals, or announcing exercise), with good regulation of blood glucose levels. At the moment, there are no widely available systems which are “full” closed loop, they all need some user input. The currently available systems are called “hybrid” closed loop, because they use a combination of automated technology and user input. - -## How and why did looping start? - -The development of commercial technology for people with type 1 diabetes (T1D) is very slow. In 2013 the T1D community founded the #WeAreNotWaiting movement. They developed systems themselves using existing approved technology (insulin pumps and sensors) to improve blood glucose control, safety, and quality of life. These are known as DIY (do-it-yourself) systems, because they are not formally approved by health bodies (FDA, NHS etc). There are four main DIY systems available: OpenAPS, **AAPS**, Loop and iAPS. - -A great way to understand the fundamentals of DIY looping is to read Dana Lewis’s book “Automated Insulin Delivery”. You can access it \[here\] (https://www.artificialpancreasbook.com/) for free (or buy a hardcopy of the book). If you want to understand more about OpenAPS, which** AAPS** has developed from, the \[OpenAPS website\] (https://openaps.org/what-is-openaps/) is also a great resource. - -Several commercial hybrid closed loop systems have been launched, the most recent of which are \[CamAPS FX\] (https://camdiab.com/) (UK and EU) and \[Omnipod 5\] (https://www.omnipod.com/en-gb/what-is-omnipod/omnipod-5) (USA and EU). These are very different to DIY systems, mainly because they both include a “learning algorithm” which adjusts how much insulin is delivered according to your insulin needs from previous days. Many people in the DIY community have already tried out these commercial systems and compared them with their DIY system. You can find out more about how the different systems compare by asking on the dedicated Facebook groups for these systems, on the \[AAPS Facebook group\] (https://www.facebook.com/groups/AndroidAPSUsers/) or on \[Discord\] (https://discord.com/invite/4fQUWHZ4Mw). - -## What is Android APS (AAPS)? - -![image](https://github.com/openaps/AndroidAPSdocs/assets/94044064/0f089d96-b7ee-452a-aa9d-aae10ab58971) - -**Figure 1**. Basic outline of the Android APS (Artificial Pancreas System), AAPS. - -Android APS (AAPS) is a hybrid closed loop system, or Artificial Pancreas System (APS). It makes its insulin dosing calculations using established \[OpenAPS\] (https://openaps.org/) algorithms (a set of rules) developed by the #WeAreNotWaiting type 1 diabetes community. - -Since OpenAPS is only compatible with certain older insulin pumps, AAPS (which can be used with a wider range of insulin pumps) was developed in 2016 by Milos Kozak, for a family member with type 1 diabetes. Since those early days, **AAPS** has been continually developed and refined by a team of volunteer computer developers and other enthusiasts who have a connection to the type 1 diabetes world. Today, **AAPS** is used by approximately 10,000 people. It is a highly customisable and versatile system, and because it is open-source, it is also readily compatible with many other open-source diabetes softwares and platforms. The fundamental components of the current **AAPS** system are outlined in Figure 1 above. - -## What are the basic components of AAPS? - -The “brain” of AAPS is an **app** which you build yourself. There are detailed step-by-step instructions for this. You then install the **AAPS app** on a compatible **Android smartphone** (1). A number of users prefer their loop on a separate phone to their main phone. So, you don’t necessarily have to be using an Android phone for everything else in your life, just for running your AAPS loop. - -The **Android smartphone** will also need to have another app installed on it as well as **AAPS**, either a modified Dexcom app called build-your-own dexcom app (**BYODA**) or Xdrip+. This receives glucose data from a sensor (2) by bluetooth, and then sends the data internally on the phone to the **AAPS app**. - -The **AAPS app** uses a decision making process (**algorithm**) from OpenAPS. Beginners start out using the basic **oref0** algorithm, but it is possible to switch to using the newer **oref1** algorithm as you progress with AAPS. Which algorithm you use (oref0 or oref1), depends on which suits your specific situation best. In both cases, the algorithm takes into account multiple factors, and performs rapid calculations every time a new reading comes in from the sensor. The algorithm then sends instructions to the insulin pump (3) on how much insulin to deliver by bluetooth. All the information can be sent by mobile data or wifi to the internet. This data can also be shared with followers if desired, and/or collected for analysis. - -## What are the advantages of the AAPS system? - -The OpenAPS algorithm used by **AAPS** controls blood sugar levels in the absence of user input, according to the users’ defined parameters (important ones being basal rates, insulin sensitivity factors, insulin-to-carb ratios, duration of insulin activity etc.), reacting every 5 minutes to the new sensor data. Some of the reported advantages of using AAPS are extensive fine-tunable options, automations and increased transparency of the system for the patient/caregiver. This can result in better control over your (or your dependent’s) diabetes, which in turn may give improved quality of life and increased peace of mind. - -Practical advantages include: - -- **Hardware flexibility**: **AAPS** works with a wide range of insulin pumps and sensors. So for example, if you develop an allergy to Dexcom sensor patch glue, you could switch to using a Libre sensor instead. That offers flexibility as life changes. You don't have to rebuild, just tick a different box in the AAPS app to change your hardware. - -- **Highly customisable with wide parameters**: here are some examples of the possibilities with AAPS: a) The ability to set a lower glucose target 30 min before eating; you can set the target as low as 72 mg/dL (4.0 mmol/L). b) If you are insulin-resistant resulting in high blood sugars, **AAPS** allows you to set an **automation** rule to activate when BG rises above 8 mmol/L (144 mg/dL), switching to a 120% profile (resulting in an 20% increase in basal and strengthening of other factors too, compared to your normal **profile** setting). The automation will last according to the scheduled time you set. Such an automation could be set to only be active on certain days of the week, at certain times of day, and even at certain locations. c) If your child is on a trampoline with no advance notice, **AAPS** allows insulin suspension for a set time period, directly via the phone. d) After reconnecting a tubed pump which has been disconnected for swimming, AAPS will calculate the basal insulin you have missed while disconnected and deliver it carefully, according to your current BG. Any insulin not required can be overridden by just “cancelling” the missed basal. f) **AAPS** has the ability to set different profiles for different situations and easily switch between them. Features which make the algorithm quicker to bring down elevated BG (like supermicro boluses (“SMB”), unannounced meals, (“**UAM**”) can be set to only work during the daytime, if you are worried about night-time hypos. - - -These are all examples, the full range of features gives huge flexibility for daily life including sport, illness, hormone cycles etc. Ultimately, it is for the user to decide how to use this flexibility, and there is no one-size-fits-all automation for this. - -- **Remote monitoring**: there are multiple possible monitoring channels (Sugarmate, Dexcom Follow, Xdrip+, Android Auto etc.) which are useful for parents/carers and adults in certain scenarios (sleeping/driving) who need customisable alerts. In some apps (Xdrip+) you can also turn alarms off totally, which is great if you have a new sensor “soaking” or settling down that you don’t want to loop with yet. - -- **Remote control**: a significant advantage of **AAPS **over commercial systems is that it is possible for followers, using authenticated text (SMS) commands or via an app (Nightscout or NSClient) to send a wide range of commands back to the ****AAPS** **system. This is used extensively by parents of kids with type 1 diabetes who use AAPS. It is very useful in the playground, for example, if you want to pre-bolus for a snack from your own phone, and your child is busy playing. It is possible to monitor the system (e.g. Fitbit), send basic commands (e.g. Samsung Galaxy watch 4), or even run the entire AAPS system from a high-spec smartwatch (5) (e.g. LEMFO LEM14). In this last scenario, you don’t need to use a phone to run AAPS. As battery life on watches improves, this last option is likely to become increasingly attractive. - -- **No commercial constraints due to open application interfaces**: beyond the use of an open source approach, which allows the source code of **AAPS** to be viewed at any time, the general principle of providing open programming interfaces gives other developers the opportunity to contribute new ideas that allow users to live more easily with their diabetes. This is complementary to commercial systems which adopt the innovations from DIY, where interfaces are only made possible in return for licensing, thus preventing innovations in particular that are not-for-profit. Good examples for such integrations are NightScout, Nightscout Reporter, Xdrip+ M5 stack etc. - -- **Detailed app interface**: It is easy to keep track of things like: insulin levels, cannula age, sensor age, pump battery age, and many actions can be done through the **AAPS** app (priming the pump, disconnecting the pump etc.), instead of on the pump itself. - -- **Accessibility and affordability**: **AAPS** gives people who currently can’t afford to self-fund, or don’t have funding/insurance, access to a world-class hybrid closed looping system which is conceptually years ahead, in terms of development, of the commercial systems being offered by clinics. You currently need to have a Nightscout account to set up **AAPS**. Although the Nightscout account it not necessarily required after setup, many people continue to use Nightscout for collecting their data, and for remote control. So, although **AAPS **itself is free, setting up Nightscout through one of the various platforms may incur a fee (E0 - E12), depending on what level of support you want (see comparison table). **AAPS** works with a wide range of affordable (starting from approx E150) Android phones. In comparison, Loop currently costs around $80 a year for the Apple development licence and CamAPS FX costs around E80/month (as at 2023). - -- ****Support**: No automated insulin delivery system is perfect. Commercial and open-source systems share many common glitches in both communications and temporary hardware failure. There is a community of AAPS users on both Facebook and Discord and Github who designed, developed and are currently using **AAPS** all over the world. There are Facebook support groups and help from clinic/commercial companies for the commercial APS systems - it is worth speaking to the users, or former users of these systems to get feedback on the common glitches, the quality of the education programme and the level of ongoing support provided. - -- **Predictability, transparency and safety**: with no learning algorithm, **AAPS** is logical and in some respect, more predictable, which may make it easier to know when a setting is wrong, and to adjust it accordingly. You can see exactly what the system is doing, why it is doing it, and set its operational limits, which puts the control (and responsibility) in your hands. This can provide the user with confidence, and a sounder sleep. - -- **Access to advanced features through dev modes including full closed loop**: **AAPS **documentation focuses on the mainstream **“master”** branch of **AAPS**, however, research and development is going on all the time. More experienced users may wish to explore the experimental features in the **development** branch such as integration of Dexcom G7, and automatically adjusting insulin delivery according to short-term sensitivity changes (DYNISF), not having to bolus for meals, and generally trying to make life with type 1 diabetes as convenient as possible. - -- **Ability to contribute yourself to further improvements**: type 1 diabetes can be highly frustrating and isolating. Having control over your own diabetes tech, with the possibility to “pay it forward” as soon as you are making progress by helping others on their journey can be really rewarding. You can educate yourself, discover the roadblocks and look for and even contribute to new developments and the documentation. There will be others with the same quest to bounce ideas off and work with. This is the essence of #WeAreNotWaiting. - - -## How does AAPS compare to MDI and open looping? - -Multiple daily injections (MDI, a) usually involve giving an injection of a long-lasting insulin (e.g. Tresiba) once a day, with injections of faster-acting insulin (e.g. Novorapid, Fiasp) at mealtimes, or for corrections. Open pumping (b) involves using a pump to deliver basal at pre-programmed rates of rapid-acting insulin, and then boluses through the pump at mealtimes or for corrections. The basics of a looping system is that the App uses the glucose data to instruct the pump to stop insulin delivery when it predicts you are heading for a low, and to give you extra insulin if your glucose levels are rising and predicted to go too high (c). Although this is oversimplified, (mostly because hybrid closed looping has a lot of additional useful features) the key features of each system are shown in **Figure 2**. - -![image](https://github.com/openaps/AndroidAPSdocs/assets/94044064/4e7d8608-684d-4c69-9c61-88c9539f5d6f) - -**Figure 2**. Overview of (a) MDI, (b) open-loop pumping and (c) hybrid closed loop pumping - -## How does AAPS compare to other looping systems? - -At present there are four major open source closed loop systems available: OpenAPS, **AAPS**, \[Loop\] (https://loopkit.github.io/loopdocs/#what-is-loop) and iAPS, (formerly FreeAPS X). The features of the different systems are shown in the table below: - -| Devicestyp | Name | [Open APS](https://openaps.readthedocs.io/en/latest/) | [AAPS](https://wiki.aaps.app) | [Buclă](https://loopkit.github.io/loopdocs/) | [iAPS](https://iaps.readthedocs.io/en/latest/) | -| ---------- | -------------------------------------------------------------------------------------------------------- | ----------------------------------------------------- | ------------------------------------------- | -------------------------------------------- | ---------------------------------------------- | -| PUMP | Older Medtronic | ![available](./images/available.png) | ![available](./images/available.png) | ![available](./images/available.png) | ![available](./images/available.png) | -| PUMP | Older Omnipod (Eros) | ![unavailable](./images/unavailable.png) | ![available](./images/available.png) | ![available](./images/available.png) | ![available](./images/available.png) | -| PUMP | Newer Omnipod (Dash) | ![unavailable](./images/unavailable.png) | ![available](./images/available.png) | ![available](./images/available.png) | ![available](./images/available.png) | -| PUMP | DANA R, DANA RS, DANA I | ![unavailable](./images/unavailable.png) | ![available](./images/available.png) | ![unavailable](./images/unavailable.png) | ![unavailable](./images/unavailable.png) | -| PUMP | Roche Combo, Insight | ![unavailable](./images/unavailable.png) | ![available](./images/available.png) | ![unavailable](./images/unavailable.png) | ![unavailable](./images/unavailable.png) | -| CGM | Dexcom G4, G5, G6 | ![available](./images/available.png) | ![available](./images/available.png) | ![available](./images/available.png) | ![available](./images/available.png) | -| CGM | Libre 1 (requires Miao Miao) | ![available](./images/available.png) | ![available](./images/available.png) | ![available](./images/available.png) | ![available](./images/available.png) | -| CGM | Libre 2 | ![available](./images/available.png) | ![available](./images/available.png) | ![available](./images/available.png) | ![available](./images/available.png) | -| CGM | Libre 3 | | ![unavailable](./images/unavailable.png) | --- | ![unavailable](./images/unavailable.png) | -| CGM | Medtronic Enlite | | --- | ![unavailable](./images/unavailable.png) | --- | -| CGM | [Dexcom G7](https://androidaps.readthedocs.io/en/latest/Hardware/DexcomG7.html) | | ![available](./images/available.png) (beta) | ![available](./images/available.png) | ![available](./images/available.png) | -| CGM | [Eversense](https://androidaps.readthedocs.io/en/latest/Hardware/Eversense.html) | | ![available](./images/available.png) | | ![available](./images/available.png) | -| CGM | [MM640g/MM630g](https://androidaps.readthedocs.io/en/latest/Hardware/MM640g.html) | | ![available](./images/available.png) | | ![available](./images/available.png) | -| CGM | [PocTech](https://androidaps.readthedocs.io/en/latest/Hardware/PocTech.html) | | ![available](./images/available.png) | | ![available](./images/available.png) | -| CGM | [Nightscout as BG Source](https://androidaps.readthedocs.io/en/latest/Hardware/CgmNightscoutUpload.html) | | ![available](./images/available.png) | | ![available](./images/available.png) | -| Phone | Android | ![available](./images/available.png) | ![available](./images/available.png) | ![unavailable](./images/unavailable.png) | ![unavailable](./images/unavailable.png) | -| Phone | iPhone | ![available](./images/available.png) | ![unavailable](./images/unavailable.png) | ![available](./images/available.png) | ![available](./images/available.png) | - -[OpenAPS](https://openaps.readthedocs.io/) was the first Open Source Closed Loop System. It uses a small computer such as Raspberry Pi or Intel Edison. Both AndroidAPS (AAPS) and iAPS use the OpenAPS algorithms, whereas Loop uses a separate algorithm. You can read a comparison of iAPS and **AAPS** here. - -An international peer-reviewed consensus statement containing practical guidance on open source looping was written by and for health-care professionals, and published in a leading medical journal in 2022. It is well worth a read (including for your diabetes clinic) and summarises the main technical differences between the different open-source hybrid closed loop systems: - - Lancet Diabetes Endocrinol, 2022; 10: 58–74 - -[https://www.ncbi.nlm.nih.gov/pmc/articles/PMC8720075/](https://www.ncbi.nlm.nih.gov/pmc/articles/PMC8720075/) - -It is hard to get a “feel” for any system without using it, or talking to others who are using it, so do reach out to others on Facebook/Discord and ask. Most people find that AAPS is incredibly sophisticated in comparison to other hybrid closed loop systems (particularly the commercial systems), with a huge number of potentially customisable settings and features, discussed above. Some people can find this a little overwhelming in the beginning, but there is no rush to investigate all the possibilities at once, you can progress as slowly or as fast as you would like, and there is help available at every step of the way. - -## Does AAPS use artificial intelligence or any learning algorithm? - -Nu. **AAPS** does not have any complicated machine learning algorithms, multiple-parameter insulin response models, or differential equations. As such, the system is open and transparent in how it works, and has the ability to be understood not just by experts, but also by clinicians and patients. It also means that if you have a sharply varying schedule (maybe switching from a stressful week at work to a relaxing holiday) and are likely to need a significantly different amount of insulin, you can immediately switch **AAPS** to run a weaker/stronger profile. A ‘learning system’ will do this adjustment for you automatically, but is likely to take longer to adjust the insulin delivery. - -## Which system is right for me or my dependent? - -Practically, your choice of system is often restricted by which pump you already have, or can obtain from your medical provider, and your choice of phone (Apple or Android). If you don’t yet have a pump you have the biggest choice of systems. Technology is continually evolving, pumps are being discontinued and new pumps and sensors are being released. Most open-source systems work with the main sensors (Libre and Dexcom) or are quickly adapted to work with new sensors a year or so after they are released (with a bit of time delay for safety and stability testing). - -Most **AAPS **users report more time in range, HbA1c reductions, as well as quality of life improvements from having a system that can auto-adjust basal rates overnight during sleep, and this is true for most hybrid closed loop APS. Some people have a preference for a very simple system which is not very customisable (which means you may prefer a commercial system), and others find this lack of control very frustrating (you may prefer an open-source system). If you (or your dependent) are newly diagnosed, a common route is to get the hang of MDI plus sensor first, then progress to a pump which has the potential for looping, then to **AAPS**, but some people (especially small kids) may go straight to a pump. - -It is important to note that the **AAPS** user needs to be proactive to troubleshoot and fix problems themselves, with help from the community. This is a very different mindset to that when using a commercial system. With **AAPS** a user has more control, but also the responsibility, and needs to be comfortable with that. - -## Is it safe to use open-source systems like AAPS? - -A more accurate question is probably “is it safe compared to my current type 1 diabetes insulin delivery system?” since no method of insulin delivery is without risk. There are many checks and balances in place with **AAPS**. A recent paper looked at the use of**** AAPS ****in a computer simulated set-up, [https://www.liebertpub.com/doi/epub/10.1089/dia.2019.0375](https://www.liebertpub.com/doi/epub/10.1089/dia.2019.0375) which was an effective way to unobjectively trial how safe and effective the system is. More generally, it is estimated that over 10,000 individuals worldwide are using open-source automated-insulin delivery systems, and uptake continues to increase globally. - -Any device that uses radio communications could be hacked, and this is true for a non-looping insulin pump as well. Currently, we are not aware of anyone attempting to harm individuals by hacking their diabetes-related medical equipment. However, there are multiple ways to protect against such risks: - -1. In the pump settings, limit both the max bolus allowed and max temporary basal settings to amounts that you believe are safest. These are hard limits that we do not believe any malicious hacker could circumvent. - -2. Set your CGM alarms enabled for both highs and lows. - -3. Monitor your insulin delivery online. Nightscout users can set additional alarms to alert for a wide variety of conditions, including conditions that are much more likely to occur than a malicious attack. In addition to highs and lows, Nightscout can display diagnostic data useful for verifying that the pump is operating as desired, including current IOB, pump temporary basal history, pump bolus history. It can also be configured to proactively alert users to undesirable conditions, such as predicted highs and lows, low insulin reservoir, and low pump battery. - - -If a malicious attack was made on your insulin pump, these strategies would significantly mitigate the risk. Every potential **AAPS** user needs to weigh the risks associated with using **AAPS**, versus the risks of using a different system. - -## How can I approach discussing AAPS with my clinical team? - -Depending on the country - link to doctors section of docs - - Lancet Diabetes Endocrinol, 2022; 10: 58–74 - -[https://www.ncbi.nlm.nih.gov/pmc/articles/PMC8720075/](https://www.ncbi.nlm.nih.gov/pmc/articles/PMC8720075/) - -## Q: Why can’t I just download AAPS and use it straight away? - -The **AAPS** app is not provided in Google Play - you have to build it from source code by yourself for legal reasons. **AAPS** is unlicensed, meaning that it does not have approval by any regulatory body authority in any country. **AAPS**is deemed to be carrying out a medical experiment on yourself, and is carried out at the user’s own risk. - -Setting up the system requires patience, determination and the gradual development of technical knowledge. All the information and support can be found in these documents, elsewhere online, or from others who have already done it. It is estimated that over 2000 people have successfully built and are currently using **AAPS** worldwide. - -The developers of **AAPS**t ake safety incredibly seriously, and want others to have a good experience of using **AAPS**. That is why it is essential that every user (or carer, if the user is a child): - -- builds the AAPS system themself and works through the **objectives** so that they have reasonably good personalised settings and understand the basics of how AAPS ****works by the time they “close the loop”; - -- backs up their system by exporting and saving important files (like keystore and settings .json file) somewhere safe, so you can setup again quickly if needed; - -- updates to newer master versions as and when they become available; and - -- maintains and monitors the system to ensure it is working properly. - - -## Q: What is the connectivity of the AAPS system? - -**Figure 3 (below)** shows one example of the **AAPS** system for a user who do not require any followers interacting with the system: - -![potential AAPS connectivity setup with no followers](./images/intro03.png) - -**Figure 4 (below)** shows the full potential of the **AAPS** system for a user who has followers and requires a monitor and send adjust the system remotely (like a child with T1D): - -![potential AAPS connectivity setup with followers](./images/intro04.png) - -## Q: How does AAPS get continually developed and improved? - -Most **AAPS** users use the fully tested **master** version of AAPS, which has been tested for bugs and problems, before being released to the community. Behind the scenes, the developers try out new improvements, and test these out in “developer” (**dev**) versions of **AAPS** with a user community who are happy to do bug updates at short notice. If the improvements work well, they are then released as a new “master” version of **AAPS**. Any new master release is announced on the Facebook group, so that the mainstream **AAPS** users can read about and update to the new master version. - -Some experienced and confident **AAPS ** users conduct experiments with emerging technologies and with dev versions of the **AAPS** app, which can be interesting for the less adventurous users to read about, without having to do it themselves! People tend to share these experiments on the Facebook group too. - -You can read more about some of these experiments and discussion on emerging tech here: - -[https://www.diabettech.com/](https://www.diabettech.com/) - -[https://bionicwookie.com/](https://bionicwookie.com/) - -## Q: Who can benefit? - -| User Type | -| ------------------------------------------- | -| ✔️ type 1 diabetic | -| ✔️ caregiver or parent of a type 1 diabetic | -| ✔️ blind users type 1 diabetic | -| ✔️ *clincians and healthcare professionals | - -The above table assumes that the user has access to both continuous gluocse monitor and insulin pump. - -*All data from **AAPS** can be made available to healthcare professionals via data sharing platforms, including NightScout that provides logging and real time monitoring of CGM data, insulin delivery, carbohydrate entries, predictions and settings. Nightscout records include daily and weekly reports which can aid healthcare professionals' discussions with type 1 patients with more accurate data on glycemic control and any behavioural considerations. - -## Q: What benefits can I get? - -With investment of your time, **AAPS** can potentially lead to: - -- alleviating the stress and burden of managing type 1 diabetes; - -- reducing the multitude of mundane decisions that arise from type 1 diabetes; - -- the provision of personalised and dynamic insulin dosing based on real-time data which can cut down the need for hypo treatments and reduce hyperglycemia episodes; - -- an increased knowledge of insulin management and confidence to better fine tune your settings; - -- the ability to create automatic settings (**automations**) that are tailored to fit in with your lifestyle; - -- improved sleep quality and overall reduction in the frequency of nighttime interventions; - -- remote monitoring and administration of insulin delivery for caregivers of type 1 diabetics; and - -- streamlining of all your portable diabetic equipment (continuous glucose monitor and insulin portable devices) by replacing them with an android phone controlled by **AAPS**. - - -Ultimately,**AAPS** can empower individuals to better manage their diabetes resulting in stable blood sugars and improved long term health outcomes. - ---- - -## AAPS First Steps - -Welcome. This is an introduction to aid beginners getting started with **AAPS** (or commonly referred to as "looping"). - -## Safety - -“_With great powers comes great responsibilities…_” - -**AAPS** is designed with an extensive set of safety features with limits imposed and gradually removed with completion of the **objectives **(predominately made up of multiple choice questions). An **AAPS** feature will be unlocked as the Objectives are successfully completed. This process will gradually allow the user to migrate from Open Loop to Closed Loop. - -This has been done to achieve the best possible experience with **AAPS** in order to prevent common mistakes that new users tend to make when starting to loop. The safety parameters have been built upon typical errors and general trends **AAPS** developers have observed with new users. Mistakes can happen because the beginner is inexperienced and too eager to get started with AAPS or has overlooked the required materials. Do not worry, we have all been there! - -## Key Principles - -The key principles and concepts of looping must be understood by the user before using **AAPS**. This is achieved by investing your personal time into reading the **AAPS** documentation, and completing the Objectives which is aimed to provide you with a solid platform for safe and effective use of **AAPS**. The volume of **AAPS** documentation may seem overwhelming at first but be patient and trust the process - with the proper approach, you'll get there! The overall process will depend upon the beginner’s progress and completion of objectives can typically take between 6 to 9 weeks . - -## Plan for hiccups - -At the preliminary stages of **AAPS**, you should expect to experience some hiccups whilst trying to fine tune your settings. **AAPS**’ glitches cannot be flushed out until the system is used in everyday life. Please plan accordingly and allow a sensible amount of time to troubleshoot and resolve such issues. - -## Flexibility/Adaptability - -Success with **AAPS** requires a proactive approach, a willingness to reflect on the BG data and flexibility to make the necessary adjustments to **AAPS** in order to improve your outcomes. Just as it is nearly impossible to learn to play a sport by reading about the rules alone, the same can be said of **AAPS**. - -## Technology compatibility - -There are limitations with **AAPS** as it is accessible for only certain types of insulin pumps or CGMs, and some technology may not be available for use in various countries. In order to avoid any disappointment or frustrations, please read please read Component Set Up (Section INSERT). - -## App Build Time - -The time to build the **AAPS**(under Section INSERT) depends on your level of expertise and technical ability. Typically for inexperienced users, it can take up to half a day or a full day (with help from the community) in order to build the **AAPS**. The process will significantly speed up as you become more experienced at building the **AAPS**. To aid the build process there are sections dedicated for: -- list of questions and answers for frequent errors that are likely to occur under FAQs (Section K); -- “How to install AAPS? (Section INSERT) which includes Troubleshooting subsection. - -## Keystore & configurations settings a export file - -A “keystore” is a password encrypted file unique to your own copy of **AAPS**. Your android phone uses it to ensure that nobody else can upgrade your own copy without the keystore. In short, as part of the **AAPS** build, you should: - -- save the your keystore file (.jks file used to sign your app) in a safe place; -- keep a note of your password for your keystore file. - -By doing the above, this will ensure that you can use that exact same keystore file each time an updated version of **AAPS** is created. On average, there will be 2-3 AAPS updates required each year. - -In addition, **AAPS** provides the ability to export all your configuration settings. This ensures that you can safely recover your system while changing phones, upgrading/reinstalling the application with minimum disruption. - -## Troubleshootng - -Please feel free to reach out to the AAPS community if there is anything you feel unsure about - there is no such thing as a silly question! All users with various levels of experience are encouraged to ask questions as necessary. Response times to questions are usually quick, typically only a few hours due to the volume of **AAPS** users. - -a) check the documentation; b) ask AAPS facebook group (https://www.facebook.com/groups/AndroidAPSUsers); and c) ask our discord channel. - -## Section overview - -AAPS documentation is made up of the following Sections: - -[INSERT ONCE SECTIONS /SUB SECTIONS AGREED] ---- diff --git a/docs/CROWDIN/ro/maintaining.md b/docs/CROWDIN/ro/maintaining.md deleted file mode 100644 index 98164a09e49b..000000000000 --- a/docs/CROWDIN/ro/maintaining.md +++ /dev/null @@ -1,28 +0,0 @@ -# Dummy - -## This is a dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - - -## This is another dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - - -## This is another another dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - diff --git a/docs/CROWDIN/ro/optimizing.md b/docs/CROWDIN/ro/optimizing.md deleted file mode 100644 index 98164a09e49b..000000000000 --- a/docs/CROWDIN/ro/optimizing.md +++ /dev/null @@ -1,28 +0,0 @@ -# Dummy - -## This is a dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - - -## This is another dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - - -## This is another another dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - diff --git a/docs/CROWDIN/ro/prepairing.md b/docs/CROWDIN/ro/prepairing.md deleted file mode 100644 index 2b4eda4428b3..000000000000 --- a/docs/CROWDIN/ro/prepairing.md +++ /dev/null @@ -1,145 +0,0 @@ -# Prepairing - -## Guide to the Android APS doc - -### First Steps -Welcome. This is an introduction to aid beginners to the concept of Do-It-Yourself-APS (Android-Artificial-Pancreas-Systems “AAPS”) is commonly referred to as ‘looping’.. - -#### Safetys -“With great powers come great responsibilities…” - -AAPS is designed with an extensive set of safety features with limits imposed and gradually removed with completion of the [Objectives](https://androidaps.readthedocs.io/en/latest/Usage/Objectives.html) (predominately made up of multiple choice questions). An AAPS feature will be unlocked as the Objectives are successfully completed. This process will gradually allow the user to migrate from Open Loop to Closed Loop. - -This has been done to achieve the best possible experience with AAPS by preventing common mistakes new users tend to make when starting to loop. The safety parameters have been built upon typical errors and general trends AAPS developers have observed with new users. Mistakes can happen because the beginner is inexperienced and too eager to get started with AAPS or has overlooked the required materials. Do not worry, we have all been there! - -#### Key Principles - -The key principles and concepts of looping must be understood by the user before using AAPS. This is achieved by investing your personal time into reading the AAPS documentation, and completing the [Objectives](https://androidaps.readthedocs.io/en/latest/Usage/Objectives.html) which is aimed to provide you with a solid platform for safe and effective use of AAPS. The volume of AAPS documentation may seem overwhelming at first but be patient and trust the process - with the proper approach, you'll get there! The overall process will depend upon the beginner’s progress and completion of objectives which typically take between 6 to 9 weeks . - -#### Plan for hiccups - -At the preliminary stages of AAPS, you should expect to experience some hiccups whilst trying to fine tune your settings. AAPS’ glitches cannot be flushed out until the system is used in everyday life. Please plan accordingly and allow a sensible amount of time to troubleshoot and resolve such issues. - -#### Flexibility/Adaptability - -Success with AAPS requires a proactive approach, a willingness to reflect on the BG data and flexibility to make the necessary adjustments to AAPS in order to improve your outcomes. Just as it is nearly impossible to learn to play a sport by reading about the rules alone, the same can be said of AAPS. - -#### Technology compatibility -There are limitations with AAPS as it is accessible for only certain types of insulin pumps or CGMs, and some technology may not be available for use in various countries. In order to avoid any disappointment or frustrations, please read [Component Set Up (Section E).](https://androidaps.readthedocs.io/en/latest/Configuration/BG-Source.html) - -#### App Build time -The time to build the AAPS (under Section D) depends on your level of expertise and technical ability. Typically for inexperienced users, it can take up to half a day or a full day (with help from the community) in order to build the AAPS. The process will significantly speed up as you become more experienced at building the AAPS.  - -To aid the build process there are sections dedicated for: - -- list of questions and answers for frequent errors that are likely to occur under [FAQs (Section](https://androidaps.readthedocs.io/en/latest/Getting-Started/FAQ.html) K); - -- “[How to install AAPS](https://androidaps.readthedocs.io/en/latest/Installing-AndroidAPS/Building-APK.html)? (Section D) which includes [Troubleshooting](https://androidaps.readthedocs.io/en/latest/Usage/troubleshooting.html) subsection. - - -#### Keystore & configuration settings export  file - -A “keystore” is a password encrypted file unique to your own copy of AAPS. Your android phone uses it to ensure that nobody else can upgrade your own copy without the keystore.In short, as part of the AAPS build, you should: - -1. save the your keystore file (.jks file used to sign your app) in a safe place; - -2. keep a note of your password for your keystore file. - - -By doing the above, this will ensure that you can use that exact same keystore file each time an updated version of AAPS is created. On average, there will be 2-3 updates to the AAPS required each year. In addition, AAPS provides the ability to [export all your configuration settings](https://androidaps.readthedocs.io/en/latest/Usage/ExportImportSettings.html). This ensures that you can safely recover your system while changing phones, upgrading/reinstalling the application with minimum disruption.  - -#### Depanare - -Please feel free to reach out to the AAPS community if there is anything you feel unsure about - there is no such thing as a silly question!  All users with various levels of experience are encouraged to ask questions as necessary. Response times to questions are usually quick, typically only a few hours due to the volume of AAPS users.  - -##### [check the documentation](https://androidaps.readthedocs.io/en/latest/index.html) - -##### [ask our facebook group](https://www.facebook.com/groups/AndroidAPSUsers/) - -##### [ask our discord channel](https://discord.com/channels/629952586895851530/629954570394533889) - -#### Section overview - -AAPS documentation is made up of the following Sections: - -##### [Getting started](https://androidaps.readthedocs.io/en/latest/Getting-Started/Safety-first.html) - -This is a must read to understand the general concept of what an artificial pancreas system is designed to do. - -##### [What do I need?](https://androidaps.readthedocs.io/en/latest/Module/module.html) - -This explains AAPS’ compatibility with CGMs (Continuous Glucose Monitors) and insulin pumps. It also provides a guide on the correct assembly of an AAPS system to ensure that it functions correctly in everyday life. - -##### How to install AAPS - -This section is the manual for building the AAPS. Strict adherence to the step-by-step instructions are required in order to successfully build the AAPS. Please take your time. - -##### [Component Setup](https://androidaps.readthedocs.io/en/latest/Configuration/BG-Source.html) - -This explains how to properly integrate each of the various different separate component parts into AAPS, as well as how to set them up to work as seamlessly as possible together. All components are listed under the separate sections: CGM/FGM, xDrip Settings, Pumps, Phones, Nightscout setup, and Smartwatches. The sensor (BG) values and control of the insulin pump are particularly important information to understand. - -##### Configuration - -This explains how to set and configure your ‘Profile’, ‘Insulin’, ‘BG Source’, ‘Pump’, ‘Sensitivity Detection’, ‘APS’, ‘Loop’, ‘Treatments’. - -##### AAPS Usage - -This section provides a breakdown of the features provided by AAPS. - -##### [General Hints](https://androidaps.readthedocs.io/en/latest/Usage/Timezone-traveling.html) - -Useful tricks on how to tackle looping issues such as time zones, and daylight saving (i.e. Spring Forward/ - Fall Back). - -##### [AAPS](https://androidaps.readthedocs.io/en/latest/Getting-Started/Screenshots.html) for Children - -This is designed for parents or caregivers who want to build an AAPS for their child. It also explains the extra features necessary in order to support and safely control your child’s AAPS remotely.

The concepts in this section should be fully understood in order to competently use this feature. - -##### Depanare - -This section contains links to help solve issues when building or using AAPS. - -##### FAQ - -This section addresses specific questions which tend to come up when building or using AAPS. - -##### [Glosar](https://androidaps.readthedocs.io/en/latest/Getting-Started/Glossary.html) - -This contains a list of the acronyms (or short-term names) or defined terms developed specifically for AAP (for instance, the terms ‘ISF’ or ‘TT’ have special meanings in AAPS). - -##### [Where to go for help](https://androidaps.readthedocs.io/en/latest/Where-To-Go-For-Help/Background-reading.html)? - -This section is aimed to provide new users with links on resources in order to get help including accessing community support made up of both new and experienced users who can clarify questions, and resolve the usual pitfalls that come with AAPS. - -##### For Clinicians - -This is a section for the clinicians who have expressed interest in open source artificial pancreas technology such as AAPS, or for patients who want to share such information with their clinicians. | - -## what are we going to build? - -### An Android Phone Application - -At the core, AAPS is an android application running from a phone. You are going to build it from scratch by installing tools to download the sourcecode and build the actual application. - -### A reporting server NightScout (or Tidepool) - -In order to fully use AAPS properly you will want to setup a nightscout server. It is used to collect data from AAPS over time and possibly communicate to the application. It is required for parents who want to oversee their children AAPS sessions. It is also key to share data between clinicians and patients to perform analysis over time. - -## How long will it take? - -## Who might AAPS not be suitable for? - -## Where can I get help? - -## Requirements - -### medical - -### technical - -### personal - -### CGMs - -### Insulin Pump - -### Reporting (NS, Tidepool) \ No newline at end of file diff --git a/docs/CROWDIN/ru/Configuration/Dexcom.md b/docs/CROWDIN/ru/Configuration/Dexcom.md deleted file mode 100644 index 233cc66ca38e..000000000000 --- a/docs/CROWDIN/ru/Configuration/Dexcom.md +++ /dev/null @@ -1,32 +0,0 @@ -# Dexcom G6 - -## Сначала основное - -* Следуйте общим рекомендациям по [гигиене мониторинга](../Configuration/BG-Source#cgm-hygiene) -* [Специальные рекомендации для систем Dexcom G6 и самодельных систем](../Configuration/BG-Source#dexcom-g6-diy-systems) *С трансмиттерами G6, изготовленными после осени 2018 года, пользуйтесь одной из [последних ночных сборок xDrip+ ](https://github.com/NightscoutFoundation/xDrip/releases). У этих трансмиттеров новая прошивка и новая стабильная версия xDrip+ (2019/01/10) с ней не работает. - -## Установка сенсора - -При установке сенсора не рекомендуется слишком сильно давить на манипулятор, чтобы избежать кровотечения. Нить сенсора не должна вступать в контакт с кровью. - -После установки сенсора трансмиттер может быть защелкнут на его платформе. Осторожно! Сначала защелкните квадратную сторону, затем надавите на круглую. - -## Устранение неполадок - -### Проблемы с подключением - -Соединение Bluetooth может быть нарушено другими близлежащими устройствами Bluetooth, такими как глюкометры, гарнитуры, планшеты, кухонные устройства, микроволновые печи или керамические плиты. В этом случае xdrip не отображает данные ГК. Когда соединение Bluetooth восстанавливается, пропущенные данные заполняются. - -### Ошибки сенсора - -Если возникают повторяющиеся ошибки сенсора, попробуйте выбрать другое место на теле для его установки. Нить сенсора не должна вступать в контакт с кровью. - -Часто "Ошибка сенсора" может быть исправлена обильным питьем и массажем вокруг сенсора! - -### Скачки данных - -Можно попробовать изменить настройки блокировки шума в xdrip (Настройки - Настройки между приложениями - Блокировка шумов), т.е. "Блокировать очень высокие шумы". См. также [Сглаживание данных ГК](../Usage/Smoothing-Blood-Glucose-Data-in-xDrip.md). - -### Установка нового трансмиттера на работающий сенсор - -Если вы меняете трансмиттер во время работы сенсора, вы можете попробовать снять его, не повредив платформу сенсора. Видео как это сделать . \ No newline at end of file diff --git a/docs/CROWDIN/ru/Configuration/EOFLOW.md b/docs/CROWDIN/ru/Configuration/EOFLOW.md deleted file mode 100644 index e420a9fbec81..000000000000 --- a/docs/CROWDIN/ru/Configuration/EOFLOW.md +++ /dev/null @@ -1,155 +0,0 @@ -# EOPatch2 Instruction Manual - -The patch requires the use of rapid-acting U-100 type insulin, such as NovoRapid or Humalog. Use a rapid-acting insulin that is suitable for you according to your doctor’s prescription and inject the prescribed dosage. - -The smallest injectable dose of insulin when using the patch is 0.05 U. The Profile BAS should therefore be set at a minimum value of 0.05 U/hr or more and an interval of 0.05 U/hr, as otherwise there may be an error between the estimated total infusion amount in the Profile and the actual infusion amount in the patch. Likewise, the bolus must also be set and infused with a minimum infusion volume of 0.05 U. - -## Pump Setup -1. On the AndroidAPS home screen, click the hamburger menu in the upper left corner and go to Config Builder. -1. Select 'EOPatch2' in the Pump section. -1. Press the Back key to return to the home screen. - -![Bild1](../../images/EOPatch/Bild1.png) ![Bild2](../../images/EOPatch/Bild2.png) - -## Настройки -Select EOPATCH2 at the top of the home screen to go to the EOPATCH2 tab. - -Select the EOPatch2 Preferences menu by clicking the three dots in the upper right corner. - -The EOPatch2 Preferences menu offers a menu to set 3 types of notifications. - -### Low reservoir Alerts -A warning appears when the amount of insulin remaining in the reservoir reaches the set value or less while using the patch. It can be set from 10 to 50U in 5U increments. - -### Patch expiration Reminder -This is a reminder to notify you of the time remaining before the current patch expires. It can be set from 1 to 24 hours in 1 hour increments. The initial setting value is 4 hours. - -### Patch buzzer Reminder -This is a reminder function for injections other than basal injection. If you are using an (extended) bolus injection or a temporary basal injection, the patch will make a buzzer sound when the injection starts and when the injection is complete. The initial setting value is Off. - -![Bild3](../../images/EOPatch/Bild3.png) - -## Connecting the Patch - -### Move to patch connection screen - -Select EOPATCH2 at the top of the home screen and click the ACTIVATE PATCH button at the bottom left. - -![Bild4](../../images/EOPatch/Bild4.png) - -### Connecting the patch -Insert the syringe needle into the insulin inlet on the patch and then slowly push the piston to inject the insulin. When insulin is filled with more than 80U, the patch makes a booting sound (1 buzzer) and boots. After confirming the buzzer sound, click the START PAIRING button on the screen. - -[Warning] - -- Do not turn the needle action lever until instructed. It can cause serious problems during injection or safety checks otherwise. -- The amount of insulin that can be injected into the patch is 80~200U. If you inject less than 80U into the patch initially, the patch will not work. -- Take the insulin to be put into the patch from the refrigerator and leave it at room temperature for 15 to 30 minutes beforehand. The temperature of the insulin to be injected must be at least 10°C. - -![Bild5](../../images/EOPatch/Bild5.png) - -### patch pairing -The Patch pairing screen will be displayed, and pairing will be attempted automatically. If communication is successful, the Bluetooth pairing request notification appears. Click OK and when the Bluetooth pairing request notification appears a second time with the authentication code, select OK again. - -[Warning] - -- For pairing, the patch and the smartphone must be located within 30 cm of each other. -- After the patch booting is completed, the patch will beep every 3 minutes until the pairing is complete. -- After booting the patch, the patch application must be completed via the app within 60 minutes. If the application cannot be completed within 60 minutes, the patch should be discarded. - -![Bild6](../../images/EOPatch/Bild6.png) ![Bild7](../../images/EOPatch/Bild7.png) ![Bild8](../../images/EOPatch/Bild8.png) - - -### patch preparation -After removing the adhesive tape of the patch, check if the needle is sticking out. If there are no problems with the patch, click NEXT. - -![Bild9](../../images/EOPatch/Bild9.png) - -### Patch attachment -Insulin should be injected in a spot with subcutaneous fat but few nerves or blood vessels, so it is recommended to use the abdomen, arm, or thigh for the patch attachment site. Choose a patch attachment site and apply the patch after disinfecting the location. - -[Warning] - -- Make sure to straighten the side of the patch tape attached to the body evenly, so that the patch adheres completely to the skin. -- If the patch does not stick completely, air may enter between the patch and the skin, which can weaken the adhesive strength and waterproof effect of the patch. - -![Bild10](../../images/EOPatch/Bild10.png) - -### Safety Check -When patching is complete, touch Start Safety Check. When the safety check is completed, the patch will beep once. - -[Warning] - -- For safe use, do not turn the needle action lever until the safety check has been completed. - -![Bild11](../../images/EOPatch/Bild11.png) ![Bild12](../../images/EOPatch/Bild12.png) - - -### Inserting the needle -The needle is inserted by holding around the patch and turning the needle action lever more than 100° in the upward direction of the lever. There is a buzzer sound when the needle is inserted correctly. Turn the needle action lever further clockwise to release the lever. Click NEXT. - -[Caution] - -- If you go to the next step without the buzzer sounding, a needle insertion error warning will appear. - -## Discarding the patch -Patches must be replaced in the case of low insulin levels, usage expiration, and defects. The recommended usage period for each patch is 84 hours after booting the patch. - -### Discarding the patch -Select EOPATCH2 at the top of the home screen and click the DISCARD/CHANGE PATCH button at the bottom. On the next screen, click the DISCARD PATCH button. A dialog box appears to confirm once more and if you select the DISCARD PATCH button, the disposal is completed. - -![Bild13](../../images/EOPatch/Bild13.png) ![Bild14](../../images/EOPatch/Bild14.png) ![Bild15](../../images/EOPatch/Bild15.png) ![Bild16](../../images/EOPatch/Bild16.png) - -## Suspending and Resuming Insulin Delivery -Suspending insulin delivery also cancels both extended bolus and temporary basal. When resuming insulin delivery, the canceled extended bolus and temporary basal will not be resumed. And when insulin delivery is suspended, the patch will give a sound every 15 minutes. - -### Suspending insulin delivery -Select EOPATCH2 at the top of the home screen and click the SUSPEND button at the bottom right. When you select CONFIRM in the confirmation box, a time selection box appears. If you select the CONFIRM button after selecting the time, the insulin delivery will be suspended for the set amount of time. - -![Bild17](../../images/EOPatch/Bild17.png) ![Bild18](../../images/EOPatch/Bild18.png) ![Bild19](../../images/EOPatch/Bild19.png) - - -### Resuming insulin delivery -Select EOPATCH2 at the top of the home screen and click the RESUME button at the bottom right. Insulin delivery will resume by selecting CONFIRM in the confirmation dialog box. - -![Bild20](../../images/EOPatch/Bild20.png) ![Bild21](../../images/EOPatch/Bild21.png) - -## Alarms/Warnings - -### Alarm - -Alarms are issued for emergency situations of the highest priority and require immediate action. The alarm signal does not disappear or time out until it is acknowledged. An alarm occurs when there is a problem with the patch being used, so there may be cases where the patch in use needs to be discarded and replaced with a new patch. The warning is displayed as a dialog box and switching to another screen is not possible until processing is completed. - -![Bild22](../../images/EOPatch/Bild22.png) ![Bild23](../../images/EOPatch/Bild23.png) - -The different types of alarms are explained below. - -| Alarms | Explanation | -| -------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| Empty reservoir | Occurs when the patch’s reservoir runs out of insulin. | -| Patch expired | Occurs when the patch usage time has expired, and no further insulin injections are possible. | -| Occlusion | Occurs when it appears that the patch's insulin inlet is clogged. | -| Power on self-test failure | Occurs when the patch finds an unexpected error during the post-boot self-test process. | -| Inappropriate temperature | Occurs when the patch is outside the normal operating temperature range during patch application and use. To deal with this alarm, move the patch to an appropriate operating temperature (4.4 to 37°C) condition. | -| Needle insertion Error | Occurs when needle insertion is not normal during the patch application process. Check that the needle insertion edge of the patch and the needle activation button are in a straight line. | -| Patch battery Error | Occurs just before the patch’s internal battery runs out and powers off. | -| Patch activation Error | Occurs when the app fails to complete the patching process within 60 minutes after the patch is booted. | -| Patch Error | Occurs when the patch encounters an unexpected error while applying and using the patch. | - -### Warning - -A warning occurs in a medium or low-priority situation. When a warning occurs, it is displayed as a notification in the Overview screen. - -![Bild24](../../images/EOPatch/Bild24.png) - -The different types of warnings are explained below. - -| Warnings | Explanation | -| ---------------------------- | ------------------------------------------------------------------------------------------------------------------------------------- | -| End of insulin suspend | Occurs when the time set by the user has elapsed after the insulin infusion suspension has been completed. | -| Low reservoir | Occurs when the remaining amount of insulin in the patch is below the set amount. | -| Patch operating life expired | Occurs when the patch usage period is over. | -| Patch will expire soon | Occurs 1 hour before the patch must be discarded. | -| Incomplete Patch activation | Occurs when more than 3 minutes have elapsed due to an interruption during patch application in the stage after pairing is completed. | -| Patch battery low | Occurs when the patch's battery is low. | - diff --git a/docs/CROWDIN/ru/Configuration/Hardware/index.md b/docs/CROWDIN/ru/Configuration/Hardware/index.md deleted file mode 100644 index f78d01a2e4d7..000000000000 --- a/docs/CROWDIN/ru/Configuration/Hardware/index.md +++ /dev/null @@ -1,27 +0,0 @@ -# Аппаратная конфигурация - -## Конфигурация - -## Источник данных гликемии - -- Источник ГК \<./BG-Source.html>\`\_ -- Настройки\`xDrip+ \<./xDrip.html>\`\_ -- Советы по Dexcom G6 \<./Dexcom.html>\`\_ -- [Выравнивание данных ГК](../../Usage/Smoothing-Blood-Glucose-Data-in-xDrip.md) - -## Помпы - -- Помпа\`Dana-R \<./DanaR-Insulin-Pump.html>\`\_ -- [Помпа Dana-RS](./DanaRS-Insulin-Pump.html) -- [Помпа Аксу-Чек Комбо](./Accu-Chek-Combo-Pump.html) -- [Помпа Акку-Чек Инсайт](./Accu-Chek-Insight-Pump.html) -- [Помпа Медтроник](./MedtronicPump.html) - -## Телефоны - -- [Настройки Jelly Pro](./../../Usage/jelly.md) -- [Настройки Huawei](../../Usage/huawei.md) - -## Смарт часы - -- [Циферблаты](../Watchfaces.md) diff --git a/docs/CROWDIN/ru/Getting-Started/ClosedLoop.md b/docs/CROWDIN/ru/Getting-Started/ClosedLoop.md deleted file mode 100644 index 45a86edb2bec..000000000000 --- a/docs/CROWDIN/ru/Getting-Started/ClosedLoop.md +++ /dev/null @@ -1,55 +0,0 @@ -# Что такое система замкнутого цикла? - -![AAPS-как автопилот](../images/autopilot.png) - -Искусственная поджелудочная железа замкнутой системы сочетает в себе различные компоненты чтобы облегчить управление диабетом. В своей замечательной книге [Автоматизированная подача инсулина ](https://www.artificialpancreasbook.com/), в оригинале - Automated Insulin Delivery, Дана М. Льюис, одна из основоположниц движения закрытой петли с открытым исходным кодом, называет ее ["автопилот твоего диабета"](https://www.artificialpancreasbook.com/3.-getting-started-with-your-aps). Что это означает? - -**Автопилот в самолете** - -Автопилот не выполняет всю работу и не дает возможности пилоту спать в течение всего полета. Он облегчает работу пилотов. Он освобождает их от бремени постоянного наблюдения за самолетом и ходом полета. Это позволяет пилоту сосредоточиться на мониторинге воздушного пространства и управлении функциями автопилота. - -Автопилот получает сигналы от различных датчиков, компьютер оценивает их наряду со спецификациями пилота, а затем вносит необходимые корректировки. Пилоту больше не нужно беспокоиться о постоянных корректировках. - -**Замкнутая система ИПЖ (Замкнутый цикл)** - -То же самое относится и к и системе искусственной поджелудочной железы. Она не делает всю работу, вы все равно должны контролировать свой диабет. Система замкнутого цикла объединяет данные датчиков мониторинга с такими параметрами управления диабетом, как скорость базала, коэффициент чувствительности к инсулину и углеводный коэффициент. Исходя из этого, она рассчитывает предложения по лечению и выполняет постоянные небольшие корректировки, чтобы держать диабет в целевом диапазоне и избавить вас от этой заботы. Это оставляет больше времени для жизни "рядом с" диабетом. - -Так же, как никто не хочет попасть на самолет, которым управляет только автопилот без контроля человека, система замкнутого цикла помогает нам в управлении диабетом, но всегда нуждается в нашей поддержке! **Даже с закрытой петлей нельзя просто взять и забыть про свой диабет!** - -Точно так же, как автопилот зависит от показателей датчиков, а также от параметров, задаваемых летчиками, система замкнутой петли требует соответствующих вводных данных, таких как скорость базала, чувствительность к инсулину ISF и углеводный коэффициент, чтобы успешно обеспечить поддержку вашего организма. - -## Замкнутые системы ИПЖ с открытым исходным кодом - -В настоящее время существует три основных замкнутых системы с открытым исходным кодом: - -### AndroidAPS (AAPS) - -AAPS is described in detail in [this documentation](./WhatisAndroidAPS.html). Он использует смартфон Android для вычислений и контроля инсулиновой помпы. Для него используются те же алгоритмы, что и для системы OpenAPS. - -Совместимые [инсулиновые помпы](../Hardware/pumps.md): - -- [DanaR](../Configuration/DanaR-Insulin-Pump.md) / [DanaRS & Dana-i](../Configuration/DanaRS-Insulin-Pump.html) -- [Помпа Accu Chek Combo](../Configuration/Accu-Chek-Combo-Pump.md) -- [Accu-Chek Insight](../Configuration/Accu-Chek-Insight-Pump.md) -- [Diaconn G8](../Configuration/DiaconnG8.md) -- [Omnipod DASH](../Configuration/OmnipodDASH.md) -- [Omnompod Eros](../Configuration/OmnipodEros.md) -- некоторые старые [помпы Medtronic](../Configuration/MedtronicPump.md) - -### OpenAPS - -[OpenAPS](https://openaps.readthedocs.io) была первой системой замкнутого цикла ИПЖ с открытым исходным кодом. Она использует мини-компьютер, Raspberry Pi или Intel Edison. - -Совместимые помпы: - -- некоторые старые помпы Medtronic - -### Петля iOS - -[Loop для iOS](https://loopkit.github.io/loopdocs/), или петля для iOS, - система замкнутого цикла ИПЖ с открытым исходным кодом для пользователей телефонов Apple iPhone. - -Совместимые помпы: - -- Omnipod DASH -- Omnompod Eros -- некоторые старые помпы Medtronic diff --git a/docs/CROWDIN/ru/Getting-Started/GlossaryTest.md b/docs/CROWDIN/ru/Getting-Started/GlossaryTest.md deleted file mode 100644 index abeea4f501c8..000000000000 --- a/docs/CROWDIN/ru/Getting-Started/GlossaryTest.md +++ /dev/null @@ -1,391 +0,0 @@ -# Глоссарий - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Термин англ./Термин рус.Описаниесмотри такжеподробнее по ссылке @
AAPS/ИПЖAndroidAPS - искусственная поджелудочная железа.  
AMA/УАРулучшенный алгоритм расчета болюсного инсулинаMA / SMBWiki - AMA
Android Autoподсистема Google для создания приложений, отображающих уведомления на дисплее вашего автомобиля Wiki - android auto
APKдистрибутив с программным обеспечением (установочный файл) Wiki - Создание APK
Autosensрасчет чувствительности к инсулину с учетом физической нагрузки, гормонального фона и пр. DIABETTECH - Autosens
Azureоблачный сервис для размещения данных системы NightscoutHeroku / NightscoutAzure
BAT/БАТнизкий уровень заряда батареи на главном экранеCAN / RES / SENНастройки
Снимок экрана
BG/ГКуровень глюкозы в крови (ГК)  
BGIвзаимодействие с глюкозой крови - коэффициент, влиющий на рост или падение уровня сахара, основанный лишь на активности инсулина, без учета факторов физической нагрузки, гормонального фона и пр.  
BG source / Источник данных ГКисточник данных уровня глюкозы в крови.CGM / FGMWiki - источник BG
Blukon Nightreaderbluetooth-передатчик, использующий сенсор Freestyle Libre в качестве CGMBlueReader / MiaoMiaoAmbrosia Blukon Nightreader
BRскорость базала  
CAGEcanula age - displayed in Nightscout if information was entered in actions tab / menu tab or through AAPS actions tab 'prime'Nightscout 
CANstatus light overdue canula change on homescreenBAT / RES / SENНастройки
Снимок экрана
CGM/НМГcontinuous glucose monitor  
Closed Loop/Замкнутый цикл (петля, контур)closed-loop systems make automatic adjustments to basal delivery, without needing user-approval, based on an algorithmOpen loopWiki closed loop
COBcarbs on board  
DIAduration of insulin action Wiki insulin types
DIABETTECH - DIA
DSTdaylight savings time Wiki DST
eCarbs"extended carbs" - carbs split up over serveral hours (i.e. lot of fat/protein)
extended boluses you might know from regular pump therapy do not make much sense when looping		SMBWiki - eCarbs
eCarbs use case
FGMflash glucose monitor (Freestyle Libre) Wiki - источник BG
gitversion-control system for tracking changes in computer files and coordinating work on those files
-> neccessary for APK updates		 Wiki - update APK
Githubweb-based hosting service for version control using Git
-> storage of source code		 Github AndroidAPS
Glimpapp to collect values from Freestyle Libre Nightscout with Glimp
Herokuоблачный сервис для размещения данных системы NightscoutAzure / NightscoutHeroku
IC (or I:C)insulin to carb ratio (How many carbs are covered by one unit of insulin?)  
IOBinsulin on board - insulin active in your body  
ISFinsulin sensitivity factor - the expected decrease in BG as a result of one unit of insulin  
LGSLow Glucose Suspend
AAPS will reduce basal if blood glucose is dropping. But if blood glucose is rising then it will only increase basal if the IOB is negative (from a previous LGS), otherwise basal rates will remain the same as your selected profile. You may temporarily experience spikes following treated hypos without the ability to increase basal on the rebound.		objective 6 
LineageOSfree and open-source operating system for smartphones etc.
alternative OS for smartphones not running Android 8.1 (Oreo)
(when using Accu-Chek Combo)		 Wiki - Combo pump
Log filesrecord of all AAPS actions (useful for trubbleshooting and debugging) Wiki - log files
maxIOBsafety feature - maximum total IOB AAPS can't go over Wiki - maxIOB
Wiki - SMB
MiaoMiaobluetooth-передатчик, использующий сенсор Freestyle Libre в качестве CGMBlueReader / Blukon NightreaderMiaoMiao
min_5m_carbimpactsaftey feature - default carb decay at times when carb absorption can’t be dynamically worked out based on your bloods reactions Wiki - config builder
Nightscoutopen source project to access and report CGM dataNightscout ReporterNightscout
NS Clientpart of AAPS to connect to your Nightscout site Wiki - NS Client
Nightscout ReporterTool from fellow looper to generate PDFs reports from Nightscout dataNightscoutNightscout Reporter
NS Reporter @ Facebook
Целиlearning program within AAPS guiding you step by step from open to closed loop Wiki - objectives
OpenAPSopen artificial pancreas system
APS run on small computers (i.e. Raspberry Pie)
AAPS uses some of the OpenAPS features		 OpenAPS docs
Открытый циклsystem will suggest recommended adjustments which have to be performed manually on the pumpClosed Loop/Замкнутый цикл (петля, контур)Wiki - config builder
Oref0 / Oref1sensitivity detection
"reference design implementation version 0/1" - the key algorithm behind OpenAPS		 Wiki - sensitivity detection
Peak timetime of maximum effect of insulin given Wiki - config builder
PHpump history (entry in treatments tab) Screenshots
Прогнозированиеpreditions for BG in the future based on different calculations Wiki - predition lines
Профильbasic treatment settings (basal rate, DIA, IC, ISF, BG target)
can be defined locally or through Nightscout		NightscoutWiki - profile
Profile switch/смена профиля(temporary) change of profile used or percentual increase/decrease Wiki - profile switch
RESstatus light overdue reservoir change on homescreenBAT / CAN / SENНастройки
Снимок экрана
RileyLinkopen source hardware device to bridge Bluetooth Low Energy (BLE) to 916MHz wireless communication (used for old Medtronic pumps)OpenAPS 
SAGEsensor age - displayed in Nightscout if information was entered in the actions tab / menuNightscout 
SENstatus light sensor change on homescreenBAT / CAN / RESНастройки
Снимок экрана
Sensivity detectionрасчет чувствительности к инсулину с учетом физической нагрузки, гормонального фона и пр. DIABETTECH - Autosens
Sensor noiseunstable CGM readings leading to "jumping" values Wiki - sensor noise
SMBsuper micro bolus
advanced feature for faster BG adjustment		UAMWiki - SMB
Super bolusshift of basal to bolus insulin for faster BG adjustment John Walsh - The Super Bolus
TBBtotal base basal (sum of basal rate within 24 hours)  
TBRtemporary basal rate  
TDDtotal daily dose (bolus + basal per day)  
TTtemporary target
temporary increase/decrease of BG target (range)		 Wiki - temp targets
UAMunannounced meals - detection of significant increase in glucose levels due to meals, adrenaline or other influences and attempt to adjust this with SMBSMBWiki - SMB
Virtual pumpoption to try AAPS functions or for PWD using a pump model with no AndroidAPS driver for loopingОткрытый цикл 
Фоновый рисунокAndroidAPS background imagesee phones page
xDrip / xDrip+open source software to read CGM systems xDrip+
xDrip
Zero-temptemporary basal rate with 0% (no basal insulin delivery)  
See also https://openaps.readthedocs.io/en/latest/docs/Resources/glossary.html
diff --git a/docs/CROWDIN/ru/Getting-Started/Safety-first.md b/docs/CROWDIN/ru/Getting-Started/Safety-first.md deleted file mode 100644 index c7e9ec3511e4..000000000000 --- a/docs/CROWDIN/ru/Getting-Started/Safety-first.md +++ /dev/null @@ -1,41 +0,0 @@ -# Безопасность прежде всего - -**Когда вы решили сделать собственную искусственную поджелудочную железу, важно помнить о безопасности и понимать последствия всех ваших действий** - -## Общие настройки - -- AAPS is a just a tool to help you manage diabetes, it is not a fully automated system you can install and forget! -- Do not assume that AAPS will never make mistakes. Эта система контролирует подачу инсулина в ваш организм: наблюдайте за ней все время, понимайте, как она работает, научитесь интерпретировать ее действия. -- Помните, что, после того, как телефон сопряжен с помпой, он может заставить ее делать все что угодно. Only use this phone for AAPS and, if being used by a child, essential communications. Не устанавливайте ненужных приложений или игр (!). С ними могут проникнуть вредоносные программы, трояны, вирусы или боты, которые могут нарушить или остановить работу вашей системы. -- Устанавливайте все обновления безопасности, предоставляемые разработчиком вашего смартфона и Google. -- Также, при работе с замкнутой системой ИПЖ придется изменить привычки управления диабетом. Например, some people report, they need less hypo treatments as AAPS has already reduced insulin. - -## СМС-коммуникатор - -- AAPS allows you to control a child's phone remotely via text message. Если смс-коммуникатор активирован, не забывайте, что телефон, настроенный на подачу удаленных команд, может быть украден. Поэтому всегда защищайте смартфон хотя бы ПИН-кодом. -- AAPS will also inform you by text message if your remote commands, such as a bolus or a profile change, have been carried out. Рекомендуется сделать такую настройку, чтобы подтверждающие тексты направлялись по меньшей мере на два разных телефона на тот случай, если один из них украден. - -(Safety-first-aaps-can-also-be-used-by-blind-people)= -## AAPS can also be used by blind people - -On Android devices TalkBack is part of the operating system. It is a program for screen orientation via voice output. With TalkBack you can operate your smartphone as well as AAPS blind. - -We users create the AAPS app ourselves with Android Studio. Many use Microsoft Windows for this purpose, where there is the Screenreader analogous to TalkBack. Since Android Studio is a Java application, the "Java Access Bridge" component must be enabled in the Control Panel. Otherwise, the screen reader of the PC will not speak in Android Studio. - -To do this, please proceed as follows: - -- Press WINDOWSTASTE and enter "Control Panel" in the search field, open with Enter. It opens: "All Control Panel Items". -- Press the letter C to get to "Center for Ease of Use", open with Enter. -- Then open "Use computer without a screen" with Enter. -- There, at the bottom, you will find the checkbox "Enable Java Access Bridge", select it. -- Done, just close the window! The screen reader should work now. - -```{note} -**IMPORTANT SAFETY NOTICE** - -The foundation of AAPS safety features discussed in this documentation is built on the safety features of the hardware used to build your system. В системе "замкнутого цикла" с автоматической дозировкой инсулина допускается использовать только испытанные, работоспособные инсулиновые помпы и системы непрерывного мониторинга глюкозы, которые получили соответствующее разрешение таких зарубежных регуляторов как FDA (США) и CE (Европейский союз). Внесение аппаратных или программных технических изменений в это оборудование может стать причиной неконтролируемого введения инсулина, что может повлечь опасные последствия для пациента. If you find or get offered broken, modified or self-made insulin pumps or CGM receivers, *do not use* these for creating an AAPS system. - -Допустимо использовать только оригинальные, сертифицированные производителем расходные материалы, такие как инсулиновые картриджи, инфузионные наборы, пристреливатели к ним и т. п. Использование непроверенных или модифицированных материалов может вызвать неточность мониторинга и ошибки дозировки инсулина. Инсулин опасен при неверной дозировке - не рискуйте жизнью, пользуясь неумело переделанными компонентами. - -И последнее, вы не должны принимать ингибиторы SGLT-2 (глифлозины), так как они непредсказуемо понижают уровень сахара в крови. Сочетание с системой, которая снижает базальную скорость для повышения ГК является особенно опасным, поскольку из-за глифлозинов этот подъем ГК может не произойти и возникнет нехватка инсулина. -``` diff --git a/docs/CROWDIN/ru/Getting-Started/Sample-Setup.md b/docs/CROWDIN/ru/Getting-Started/Sample-Setup.md deleted file mode 100644 index 47285df79ac0..000000000000 --- a/docs/CROWDIN/ru/Getting-Started/Sample-Setup.md +++ /dev/null @@ -1,151 +0,0 @@ -# Пример настройки: Samsung S7, DanaR, Dexcom G6 и Sony Smartwatch - -![Пример настройки](../images/SampleSetup.png) - -## Описание - -В этой комбинации смартфон Samsung Galaxy S7 используется в качестве центра управления циклом. Слегка модифицированное приложение Dexcom считывает значения ГК из CGM Dexcom G6. AndroidAPS управляет помпой Dana R корейского производителя SOOIL через Bluetooth. Дополнительные устройства не требуются. - -Поскольку приложение Dexcom предлагает ограниченные параметры оповещений, приложение с открытым исходным кодом xDrip+ настраивается не только на высокие и низкие значения но и на другие оповещения под индивидуальные потребности. - -По желанию можно использовать смарт-часы Android (в этой выборке применяется Sony Smartwatch 3 (SWR50)) для отображения значений глюкозы и параметров AndroidAPS на вашей руке. Часы могут даже применяться для контроля AndroidAPS (напр. для дискретной подачи болюса на еду). - -Система работает в автономном режиме. Это означает, что для работы нет необходимости подключения смартфона к Интернету. - -Тем не менее, данные автоматически загружаются в Nightscout "в облаке", когда соединение с интернетом присутствует. Эта опция позволяет предоставить полную картину ГК для врача или для членов семьи практически в любое время. Также можно отправлять данные в Nightscout только с (вами определенным) Wi-Fi соединением для создания различных отчетов. - -## Обязательные компоненты - -1. Samsung Galaxy S7 - - * Альтернативы: см. [список проверенных телефонов и часов](https://docs.google.com/spreadsheets/d/1gZAsN6f0gv6tkgy9EBsYl0BQNhna0RDqA9QGycAqCQc/edit) для AndroidAPS - -2. [DanaRS](http://www.sooil.com/eng/product/) - - * Альтернативы: - * [Помпа Accu Chek Combo](../Configuration/Accu-Chek-Combo-Pump.md) - * [Accu-Chek Insight](../Configuration/Accu-Chek-Insight-Pump.md) - * [DanaR](../Configuration/DanaR-Insulin-Pump.md) - * [Некоторые старые помпы Medtronic (дополнительно требуются аппаратная часть: RileyLink/Gnarl, телефон Android с чипом bluetooth low Energy/BLE-chipset)](../Configuration/MedtronicPump.md) - * В будущем возможны другие помпы, см. подробнее в [возможные будущие драйверы помп](Future-possible-Pump-Drivers.md). - -3. [Dexcom G6](https://dexcom.com) - - * Alternatives: see list of possible [BG sources](../Configuration/BG-Source.md) - -4. Дополнительно: Sony Smartwatch 3 (SWR50) - - * Альтернативы: Все [ часы с Google Wear OS ](https://wearos.google.com/intl/de_de/#find-your-watch) должны работать, см. [ список проверенных телефонов и часов ](https://docs.google.com/spreadsheets/d/1gZAsN6f0gv6tkgy9EBsYl0BQNhna0RDqA9QGycAqCQc/edit) для AndroidAPS (OS должна быть Android Wear) - -## Настройки Nightscout - -Подробнее см. [Настройка Nightscout](../Installing-AndroidAPS/Nightscout.md) - -## Настройка компьютера - -Чтобы создать приложение на Android из свободно распространяемого кода AAPS, вам нужно установить Android Studio на компьютере или ноутбуке (Windows, Mac, Linux). Подробная инструкция находится на [создание APK](../Installing-AndroidAPS/Building-APK.md). - -Пожалуйста, будьте терпеливы при установке Android Studio так как программа загружает много дополнительных компонентов на вашем компьютере. - -## Настройка смартфона - -![Смартфон](../images/SampleSetupSmartphone.png) - -### Проверьте прошивку смартфона - -* Меню > Настройки > Настройки > Информация о телефоне > Информация о Программном обеспечении: не ниже "Android-Version 8.0" (успешно протестирована до версии 8.0.0 Oreo - Samsung Experience Version 9.0) -* Для обновления прошивки: меню > Настройки > Обновление программы - -### Разрешите установку приложений из неизвестных источников - -Меню > Настройки > Безопасность устройства > Неизвестные источники > ползунок справа (= active) - -По соображениям безопасности эта настройка должна быть возвращена в неактивный режим по завершении установки всех описанных здесь приложений. - -### Включите Bluetooth - -1. Меню > Настройки > Подключения > Bluetooth > ползунок справа (= active) -2. Меню > Настройки > Подключения > Местоположение > ползунок справа (= active) - -Службы местоположения ("GPS") должны быть активированы для корректной работы Bluetooth. - -### Установить приложение Dexcom (модифицированная версия) - -![Приложение Dexcom G (модифицированное)](../images/SampleSetupDexApp.png) - -Оригинальное приложение Dexcom из Google Play Store не будет работать, так как оно не передает данные другим приложениям. Поэтому требуется немного модифицированная версия от нашего сообщества. Только это измененное приложение Dexcom может общаться с AAPS. Кроме того, модифицированное приложение Dexcom может работать со всеми смартфонами Android, а не только находящимися в списке совместимости [Dexcom](https://www.dexcom.com/dexcom-international-compatibility). - -Для этого выполните следующие шаги на вашем смартфоне: - -1. Если оригинальное приложение Dexcom уже установлено: - * Остановить сенсор - * Удалить приложения через меню > Настройки > Приложения > Dexcom G6 Mobile > Удалить -2. Download and install the [BYODA Dexcom ap](../Hardware/DexcomG6.md#if-using-g6-with-build-your-own-dexcom-app) -3. Запустите модифицированное приложение Dexcom, активируйте/закалибруйте сенсор в соответствии с инструкциями и подождите, пока завершится процесс разогрева. -4. После того, как измененное приложение Dexcom покажет фактическое значение глюкозы, настройте оповещения (сэндвич-меню в левом верхнем углу экрана) следующим образом: - * Чрезвычайно низкий `55mg/dl` / `3.1mmol/l` (не может быть отключен) - * Низкий `ВЫКЛ` - * Высокий `ВЫКЛ` - * Скорость подъема `ВЫКЛ` - * Скорость понижения `ВЫКЛ` - * Потеря сигнала `ВЫКЛ` - -## Установите AndroidAPS - -1. Follow the instructions to [build the APK](../Installing-AndroidAPS/Building-APK.md#generate-signed-apk) -2. [Transfer](../Installing-AndroidAPS/Building-APK.md#transfer-apk-to-smartphone) the generated APK to your phone -3. [Сконфигурируйте AndroidAPS](../Configuration/Config-Builder.md) в соответствии с Вашими потребностями, используя мастер настройки или вручную -4. В этом примере мы использовали (среди прочего) - -* BG source: `Dexcom G6 App (patched)` -- click cock-wheel and activate `Upload BG data to NS` and `Send BG data to xDrip+` (see [BG source](../Configuration/BG-Source.md)) - -![Настройки G5](../images/SampleSetupG5Settings.png) - -* NS клиент активирован (см. [Клиент NS и Настройки Nightscout](../Installing-AndroidAPS/Nightscout.md)) - -## Установите xDrip+ - -xDrip+ это великолепное приложение с открытым исходным кодом, предлагающее бесчисленные возможности. В этой компоновке, вопреки целям разработчиков xDrip+, оно не используется для получения данных ГК с Dexcom G6, а только для вывода оповещений и для отображения текущего значения Гк, включая кривую в виджете на домашнем экране Android. С xDrip+ оповещения могут быть настроены гораздо более индивидуально, чем с программным обеспечением Dexcom, AAPS или Nightscout (без ограничений в выборе звуков, сигналов для дня/ночи и т. д.). - -1. Скачайте последнюю стабильную версию APK xDrip+ с помощью смартфона - а не версию из Google Play Store! -2. Установите xDrip+ при помощи выбора загруженного файла APK. -3. Запустите xDrip+ и произведите следующие настройки (сэндвич-меню слева сверху) - * Настройки > Будильники и оповещения > Список оповещений об уровне ГК > Создание оповещений (высокое и низкое) в соответствии с Вашими потребностями. - * Существующие оповещения могут быть изменены длинным нажатием на значок сигнала. - * Настройки > Будильники и оповещения > Оповещения о калибровке: отключены (напоминание через измененное приложение Dexcom) - * Настройки > Источник аппаратных данных > 640G/EverSense - * Настройки > Настройки Inter-app > Принимать Калибровки > `включено` - * Меню > Запуск сенсора (только "pro forma", не имеет ничего общего с работающим датчиком G6.). Необходимо включить иначе будет регулярно появляться сообщение об ошибке.) - -For more information about xDrip+, see here [BG source page](../Configuration/BG-Source.md). - -### Пример настройки оповещения - -"Чрезвычайно низкая ГК" (ниже 55 мг/дл. 3,1 ммол) является стандартным оповещением модифицированного приложения Dexcom, которое не может быть отключено. - -![Оповещения xDrip](../images/SampleSetupxDripWarning.png) - -Совет на случай переговоров / посещений церкви / кино и т. д..: - -Если в Samsung Galaxy S7 активирован режим "Не беспокоить" (меню > Настройки > Звуки и вибрация > Не беспокоить: ползунок вправо сторону (= вкл)), телефон только вибрирует во время оповещения о чрезвычайно низкой ГК и не подает звукового сигнала. Для других оповещений, настроенных через xDrip+ можно выбрать, игнорировать ли звуковой режим. - -## Отключите энергосбережение - -На вашем Samsung Galaxy S7 перейдите в меню > Настройки > Поддержка устройства > Батарея > Неотслеживаемые приложения > + Добавить приложения: Выберите одно за другим приложения AndroidAPS, Dexcom G6 Mobile, xDrip+ и Android Wear (если используете) - -## Дополнительно: настройте Sony Smartwatch 3 (SWR50) - -С Android Wear жизнь с диабетом можно сделать еще более незаметной для окружающих. Часы могут использоваться для отображения текущего уровня глюкозы, состояния цикла и т. д. на запястье. Часы могут даже применяться для контроля AndroidAPS (напр. для дискретной подачи болюса на еду). Для этого дважды нажмите на значение ГК на циферблате AAPSv2. SWR50 обычно работает полный день до подзарядки (то же зарядное устройство, что и для Samsung Galaxy S7: microUSB). - -![Смарт часы](../images/SampleSetupSmartwatch.png) - -Подробности о информации, отображаемой на экране часов, можно найти [здесь](../Configuration/Watchfaces.md). - -* Установите приложение "Android Wear" на вашем смартфоне через Google Play Store и подключите смартфон в соответствии с инструкциями. -* В AAPS выберите сэндвич-меню (в верхнем левом углу) > Конфигуратор > Общее (в нижней части списка) > Wear > активировать, на левой стороне нажмите на шестеренку > Настройки Wear и активируйте `Управление c часов` -* На вашем смартфоне: Удерживайте дисплей для изменения циферблата и выберите `AAPSv2` -* При необходимости однократно перезапустите оба устройства. - -## Настройки помпы - -см [помпа DanaRS ](../Configuration/DanaRS-Insulin-Pump.md) \ No newline at end of file diff --git a/docs/CROWDIN/ru/Getting-Started/WhatisAndroidAPS.md b/docs/CROWDIN/ru/Getting-Started/WhatisAndroidAPS.md deleted file mode 100644 index c0c2e64106aa..000000000000 --- a/docs/CROWDIN/ru/Getting-Started/WhatisAndroidAPS.md +++ /dev/null @@ -1,39 +0,0 @@ -# What is a closed loop system with AAPS? - -AAPS is an app that acts as an artificial pancreas system (APS) on an Android smartphone. Что такое система искусственной поджелудочной железы? Это программа, которая призвана делать то, что делает живая поджелудочная: автоматически поддерживать уровень сахара в крови в допустимых пределах. - -ИПЖ не может выполнять все функции биологической поджелудочной железы, но она может сделать диабет типа 1 более легким в управлении с использованием коммерчески доступных устройств и простого и безопасного ПО. Those devices include a continuous glucose monitor (CGM) to tell AAPS about your blood sugar levels and an insulin pump which AAPS controls to deliver appropriate doses of insulin. Приложение взаимодействует с этими устройствами через Bluetooth. Она производит расчет дозирования с использованием алгоритма или набора правил, разработанных для другой системы ИПЖ, OpenAPS, которая имеет тысячи пользователей и миллионы часов использования. - -A note of caution: AAPS is not regulated by any medical authority in any country. Using AAPS is essentially carrying out a medical experiment on yourself. Настройка системы требует настойчивости и технических знаний. Если у вас нет технических знаний, вы их постепенно приобретете. Вся нужная информация есть в этих документах, на соответствующих сайтах интернете или у других пользователей, которые уже спостроили APS -вы можете спросить их в группах Facebook или на форумах. Many people have successfully built AAPS and are now using it entirely safely, but it is essential that every user: - -- Builds the system themselves so that they thoroughly understand how it works -- Adjusts its individual dosage algorithm with his or her diabetes team to work nearly perfect -- Maintains and monitors the system to ensure it is working properly - -```{note} -**Disclaimer and Warning** - -- All information, thought, and code described here is intended for informational and educational purposes only. Nightscout в настоящее время не пытается соответствовать принципам конфиденциальности HIPAA. Use Nightscout and AAPS at your own risk, and do not use the information or code to make medical decisions. -- Use of code from github.com is without warranty or formal support of any kind. Пожалуйста, ознакомьтесь с ЛИЦЕНЗИЕЙ этого репозитория. -- All product and company names, trademarks, servicemarks, registered trademarks, and registered servicemarks are the property of their respective holders. Их использование - в информационных целях и не подразумевает какой-либо принадлежности к ним или их одобрения. - -Please note - this project has no association with and is not endorsed by: [SOOIL](http://www.sooil.com/eng/), [Dexcom](https://www.dexcom.com/), [Accu-Chek, Roche Diabetes Care](https://www.accu-chek.com/), [Insulet](https://www.insulet.com/) or [Medtronic](https://www.medtronic.com/). -``` - -Если вы готовы продолжать, читайте дальше. - -## Primary goals behind AAPS - -- An app with safety built in. To read about the safety features of the algorithms, known as oref0 and oref1, click here () -- An all-in-one app for managing type 1 diabetes with an artificial pancreas and Nightscout -- An app to which users can easily add or remove modules as needed -- An app with different versions for specific locations and languages. -- An app which can be used in open- and closed-loop mode -- An app that is totally transparent: users can input parameters, see results, and make the final decision -- An app which is independent of particular pump drivers and contains a "virtual pump" so users can safely experiment before using it on themselves -- An app closely integrated with Nightscout -- An app in which the user is in control of safety constraints - -## Как начать - -Все, что здесь написано, очень важно, но поначалу может показаться довольно запутанным. A good orientation is given by the [Module Overview](../Module/module.md) and the [Objectives](../Usage/Objectives.html). diff --git a/docs/CROWDIN/ru/Hardware/DexcomG4.md b/docs/CROWDIN/ru/Hardware/DexcomG4.md deleted file mode 100644 index c15f3793eb33..000000000000 --- a/docs/CROWDIN/ru/Hardware/DexcomG4.md +++ /dev/null @@ -1,6 +0,0 @@ -# Dexcom G4 - -## При использовании G4 с кабелем OTG («традиционный» Nightscout) -- Если это еще не сделано, скачайте загрузчик Nightscout из Play Store и следуйте инструкциям на [Nightscout](https://nightscout.github.io/). -- В настройках AAPS введите адрес вашего веб-сайта Nightscout и пароль API secret. -- В конфигураторе (настройки AAPS) выберите NSClient. diff --git a/docs/CROWDIN/ru/Hardware/Smartwatch.md b/docs/CROWDIN/ru/Hardware/Smartwatch.md deleted file mode 100644 index 553631bb1702..000000000000 --- a/docs/CROWDIN/ru/Hardware/Smartwatch.md +++ /dev/null @@ -1,10 +0,0 @@ -# Смарт-часы - -Смарт-часы не обязательны, но полезны для некоторых пользователей. Подробнее здесь: - -- [Список телефонов и смарт-часов, прошедших тестирование](../Getting-Started/Phones.md) -- [Циферблаты для Wear OS](../Configuration/Watchfaces.md) -- [Устранение неполадок со смарт-часами Sony SW 3](../Usage/SonySW3.md) - -## Инструкции по созданию APK AAPS для Wear OS -https://androidaps.readthedocs.io/en/latest/remote-control.html#building-the-aaps-wear-apk diff --git a/docs/CROWDIN/ru/Installing-AndroidAPS/Building-APK.md b/docs/CROWDIN/ru/Installing-AndroidAPS/Building-APK.md deleted file mode 100644 index 0a13f91ec7f2..000000000000 --- a/docs/CROWDIN/ru/Installing-AndroidAPS/Building-APK.md +++ /dev/null @@ -1,369 +0,0 @@ -# Создание андроид-приложения (APK) - -## Постройте сами вместо скачивания - -**AndroidAPS недоступен для скачивания из-за законодательства, касающегося медицинских устройств. Построить приложение для собственного использования вполне законно, но передавать копию другим не разрешается! См. раздел [ FAQ ](../Getting-Started/FAQ.md).** - -## Важные Примечания - -* Используйте **[ Android Studio версии 2022.3.1 ](https://developer.android.com/studio/)** или новее для построения apk. -* [Windows для 32-разрядных систем](troubleshooting_androidstudio-unable-to-start-daemon-process) не поддерживаются в Android Studio - -(Building-APK-recommended-specification-of-computer-for-building-apk-file)= - -## Рекомендуемые спецификации компьютеров для сборки файла apk - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Операционная система (только 64 бит)Windows 8 или вышеMac OS 10.14 или вышеЛюбой Linux поддерживающий Gnome, KDE, или Unity DE;  GNU C Library 2.31 или более поздние версии

Процессор CPU (Только 64 бит)

x86_64 архитектура CPU; ядро Intel или новее, или процессор AMD с поддержкой
Windows Hypervisor		Чипы на базе ARM или Intel Core 2 поколения или новее с поддержкой
среды Hypervisor 		архитектура процессора x86_64, процессор Intel Core 2 поколения или новее, или процессор AMD с поддержкой AMD-виртуализации (AMD-V) и SSSE3

Оперативная память

8ГБ или более

Диск

Не менее 30ГБ свободного места. Рекомендуется использовать SSD.

Разрешение

минимум 1280 x 800

Интернет

Широкополосный

- -Имейте в виду, что и **64-разрядная процессор, и 64-разрядная ОС являются обязательным условием.** Если ваша система не соответствует этому условию, следует изменить аппаратное или программное обеспечение или всю систему. **Рекомендуется использовать SSD(Solid State Disk) вместо HDD(Hard Disk Drive), так как при создании APS-файла потребуется меньше времени.** Рекомендация не является обязательной. Однако вы можете использовать HDD при создании apk файла, но процесс сборки может занять много времени, хотяпосле начала процесс можно оставить без присмотра. - -* * * - -### Эта статья разделена на две части. - -* В обзорной части находится объяснение того, какие шаги необходимы для создания файла APK. -* В пошаговой инструкции вы найдете снимки экранов установки. Поскольку версии Android Studio - среды разработки программного обеспечения, в которой мы будем создавать APK - меняются очень быстро, точного соответствия вашей сборке вы не увидите, но общее представление о том, как это делается, получите. Android Studio работает на Windows, Mac OS X и Linux, и между каждой платформой возможны незначительные различия. Если вы обнаружите, что что-то важное выполняется неправильно или отсутствует, сообщите в группе facebook "AAPS users" или в чате Discord [AAPS](https://discord.gg/4fQUWHZ4Mw) чтобы мы могли устранить проблему. - -## Общие замечания - -В целом, шаги, необходимые для создания файла APK таковы: - -1. [Установите Git](../Installing-AndroidAPS/git-install.md) -2. [Установите Android Studio](Building-APK-install-android-studio) -3. [Задайте путь к git в параметрах Android Studio](Building-APK-set-git-path-in-preferences) -4. [Скачайте код AAPS](Building-APK-download-AAPS-code) -5. [Загрузите Android SDK](Building-APK-download-android-sdk) -6. [Соберите приложение ](Building-APK-generate-signed-apk) (сгенерируйте подписанный apk) -7. [Перенесите файл apk на телефон](Building-APK-transfer-apk-to-smartphone) -8. [Идентифицируйте ресивер при использовании xDrip+](xdrip-identify-receiver) - -## Пошаговое руководство - -Подробное описание шагов, необходимых для создания файла APK. - -## Установите git (если у вас его нет) - -Следуйте инструкциям на странице установки [git](../Installing-AndroidAPS/git-install.md). - -(Building-APK-install-android-studio)= - -## Установите Android Studio - -Следующие снимки экрана были сделаны из Android Studio Version Arctic Fox | 2020.3.1. Экраны могут меняться в будущих версиях Android Studio. Но у вас должно получиться. [Здесь можно найти помощь участников](../Where-To-Go-For-Help/Connect-with-other-users.md). - -Одна из наиболее важных заповедей при установке Android Studio: ** Будьте терпеливы! ** Во время установки и настройки Android Studio загружает многие элементы, которые отнимают время. - -Загрузите [ Android Studio отсюда](https://developer.android.com/studio/install.html) и настройте при первом запуске. - -При первом запуске вы найдете мастер установки: - -Выберите "Не импортировать настройки", так как вы не использовали их раньше. - -![Не импортируйте настройки](../images/studioSetup/01_ImportSettings.png) - -Решите, хотите вы совместно использовать данные с Google или нет. - -![Обмен данными с Google](../images/studioSetup/02_DataSharing.png) - -На следующем экране нажмите кнопку "Далее". - -![Экран приветствия](../images/studioSetup/03_Welcome.png) - -Выберите "Стандартная" установка и нажмите "Далее". - -![Стандартная установка](../images/studioSetup/04_InstallType.png) - -Для интерфейса выберите тему, которая вам нравится. (В этом руководстве мы использовали "Светлую".) Затем нажмите кнопку "Далее". - -> ***Примечание:*** Это всего лишь цветовая схема. Можете выбрать любую (напр. Darcula для темного режима). Этот выбор не влияет на создание APK, но следующие скриншоты могут выглядеть иначе. - -![Цветовая схема интерфейса](../images/studioSetup/05_UITheme.png) - -Нажмите "Далее" в диалоге "Подтвердить настройки". - -![Подтвердить настройки](../images/studioSetup/06_Overview.png) - -Нажмите на все три части лицензионного соглашения и выберите "Согласен". Когда вы согласились со всеми, будет включена кнопка "Завершить", и вы можете "Завершить". - - ![Принимайте лицензионные соглашения](../images/studioSetup/07_LicenseAgreement.png) - - -Подождите, пока Android Studio скачивает дополнительные компоненты и будьте терпеливы. После того, как все загрузится кнопка "Готово", станет синей. Теперь нажмите на кнопку. - -![Загрузка компонентов](../images/studioSetup/08_Downloading.png) - -(Сборка-APK-загрузка-AAPS-кода)= - -## Скачайте код AAPS - -* На экране Android Studio выберите "Проекты" (1) слева и затем "Получить с VCS" (2). - - ![Мастер Android Studio](../images/studioSetup/20_ProjectVCS.png) - - * Если вы уже открыли Android Studio и не видите экран приветствия, то выберите File (1.) > New (2.) > Project from Version Control... (3) - - ![Извлечение проекта из системы управления версиями в Android Studio](../images/AndroidStudio_FileNew.PNG) - - * Теперь мы расскажем программе Android Studio, откуда получить код: - - * Убедитесь, что вы выбрали "URL репозитория" слева (1). - - * Отметьте, выбран ли "Git" в качестве контроля версий (2). - * Скопируйте и вставьте URL-адрес ```https://github.com/nightscout/AndroidAPS``` в основной репозиторий AAPS в текстовом поле URL (3). - * Выберите каталог для сохранения клонированного кода(4). - - ![Клонируйте Git](../images/studioSetup/21_CloneURL.png) - -* Нажмите кнопку "Клонировать" (5). - - ![Клонирование репозитория](../images/studioSetup/22_Cloning.png) - -* Не нажимайте "Background", пока клонируется репозиторий! - -* После успешного клонирования репозитория, Android Studio откроет клонированный проект. - -* Вам будет задан вопрос, хотите ли вы доверять проекту. Нажмите на "Доверять проекту"! - - ![Доверять проекту](../images/studioSetup/23_TrustProject.png) - -* На шкале состояния появится информация о том, что в Android Studio выполняются фоновые задачи. - - ![Фоновые задания](../images/studioSetup/24_GradleSyncRunning.png) - -* Только для Windows: предоставьте доступ, если брандмауэр просит разрешение. - - ![Разрешение брандмауэра (Java)](../images/AndroidStudio361_18.png) - -* После завершения фоновых задач вы увидите сообщение, указывающее на ошибки (1) или (2) или (3). - - ![Лицензия SDK](../images/studioSetup/25_SyncFailed.png) - - Не волнуйтесь, вскоре они снимутся! - -(Сборка-APK-задать-путь-к-git-в-настройках) = - -## Задайте путь к git в параметрах - -Убедитесь, что [git установлен](../Installing-AndroidAPS/git-install.md) на компьютере и компьютер перезагрузили после установки. - -На экране приветствия Android Studio нажмите кнопку "Настроить" (1) слева и затем выберите ссылку "Все настройкиs..." (2): - -![Параметры Android Studio с экрана приветствия](../images/studioSetup/10_WizardSettings.png) - -### Windows - -* Как пользователь Windows, убедитесь, что вы перезагрузили компьютер после [установки Git](../Installing-AndroidAPS/git-install.md). - -* В меню перейдите в Файл (1) > Настройки (2) (или Android Studio > Настройки на Mac). - - ![Открыть настройки](../images/studioSetup/30_Settings.png) - -* Дважды нажмите "Управление версиями" (1) для открытия подменю. - -* Нажмите Git (2). -* Убедитесь, что "Слияние" (merge) (3.) выбрано как метод обновления. -* Проверьте, может ли Android Studio найти путь к файлу git.exe автоматически, нажав кнопку "Тест" (4). - - ![Параметры Android Studio](../images/studioSetup/11_GitPath.png) - -* Если автоматическая настройка прошла успешно, то рядом с путем к git будет показана его версия. - - ![Отображается версия Git](../images/studioSetup/12_GitVersion.png) - -* Иногда git.exe не может быть найден автоматически или тест приведет к ошибке (1): - - ![Git не найден](../images/studioSetup/13_GitVersionError.png) - - В этом случае нажмите на значок папки (2). - -* Используйте [ поиск ](https://www.tenforums.com/tutorials/94452-search-file-explorer-windows-10-a.html) в проводнике Windows чтобы найти "git.exe", если не уверены, где он расположен. Вы ищете файл "git.exe", расположенный в папке **\bin**. - -* Выберите путь к файлу git.exe и убедитесь, что выбрали папку ** \bin\ ** (3.) и нажмите кнопку "OK" (4). - - ![Выберите git вручную](../images/studioSetup/14_GitManualSelection.png) - -* Проверьте ваш выбранный путь git еще раз кнопкой «Тест», как описано выше. - -* Когда версия git отображается рядом с путем (см. снимок экрана выше), закройте окно настроек, нажав кнопку "OK" (5). - -### Mac - -* Любая версия git должна работать. Например . -* Используйте homebrew для установки git: ```$ установка brew git```. -* Подробности об установке git см. в [официальной git документации](https://git-scm.com/book/en/v2/Getting-Started-Installing-Git). -* Если вы устанавливаете git через homebrew, то нет необходимости изменять какие-либо настройки. На всякий случай: Их можно найти здесь: Android Studio - Настройки. - -(Сборка-APK-загрузка-андроид-sdk)= - -## Загрузите Android SDK - -* В меню перейдите в Файл (1) > Настройки (2) (или Android Studio > Настройки на Mac). - - ![Открыть настройки](../images/studioSetup/30_Settings.png) - -* Дважды щелкните по Языки & и откройте подменю (1). - -* Выберите Android SDK (2). -* Установите флажок слева от "Android 9.0 (Pie)" (3.) (API Level 28). - - ![Параметры SDK](../images/studioSetup/31_AndroidSDK.png) - -* Подтвердите изменения, нажав кнопку OK. - - ![Подтвердить изменения SDK](../images/studioSetup/32_ConfirmSDK.png) - -* Дождитесь окончания загрузки и установки SDK. - - ![Ожидание во время установки SDK](../images/studioSetup/34_DownloadSDK.png) - -* После завершения установки SDK кнопка "Finish" станет синей. Нажмите на кнопку. - - ![Завершить установку SDK](../images/studioSetup/35_DownloadSDKfinished.png) - -* Android Studio может рекомендовать обновить систему gradle. **Не обновляйте gradle!** Это может привести к трудностям! - -* Если вы видите информацию на нижней правой стороне окна Android Studio, что плагин Android Gradle готов к обновлению, нажмите на текст "upgrade" (1). - - ![Не обновляем gradle](../images/studioSetup/36_GradleUpdateRequest.png) - -* В диалоговом окне выберите "Don't remind me again for this project" (2). - - ![Не обновляем gradle](../images/studioSetup/37_GradleUpdateDeny.png) - -* Перезапустите Android Studio прежде чем продолжить. - -(Сборка-APK-генерировать-подписанный-apk)= - -## Создание подписанного APK - -Подписание означает, что вы подписываете созданное вами приложение, но цифровым способом, как цифровым отпечатком пальца в самом приложении. Это необходимо потому, что Android имеет правило, согласно которому по соображениям безопасности к исполнению принимается только подписанный код. Для получения дополнительной информации перейдите по [ этой ссылке](https://developer.android.com/studio/publish/app-signing.html#generate-key). - -* После запуска Android Studio дождитесь завершения всех фоновых задач. - - ![Дождитесь фоновых задач](../images/studioSetup/40_BackgroundTasks.png) - - * ***Предупреждение:*** Если возникают ошибки, не делайте следующие шаги. Обращайтесь в раздел [устранение неполадок](../Installing-AndroidAPS/troubleshooting_androidstudio) для решения возникающих проблем! - - ![Ошибка синхронизации Gradle](../images/studioSetup/41_GradleSyncError.png) - -* Нажмите "Build" (1) в строке меню и выберите "Generate Signed Bundle / APK..."(генерировать подписанное приложение (2). - - ![Построение apk](../images/studioSetup/42_MenuBuild.png) - -* Выберите "APK" (1.) вместо "Android App Bundle" и нажмите кнопку "Далее" (2). - - ![Apk вместо пакета](../images/studioSetup/43_Apk.png) - -* Убедитесь, что модуль переключен на "app" (1). - -* Нажмите "Create new" (cоздать новый...) для создания хранилища ключей. - - ***Примечание***Хранилище ключей это файл, в котором хранится информация о цифровой подписи. Он зашифрован и информация защищена паролями. - - ![Создание хранилища ключей](../images/studioSetup/44_KeystoreNew.png) - -* Нажмите на символ папки и выберите путь к хранилищу ключей. - - ![Создание хранилища ключей](../images/studioSetup/45_KeystoreDialog.png) - -* Выберите путь к хранилищу ключей (1). - - ![Создание хранилища ключей](../images/studioSetup/46_KeystorePath.png) - - ***Внимание: Не сохраняйте в той же папке, что и сам проект. Выберите другой каталог! *** Например, домашнюю папку. - -* Введите имя файла хранилища ключей (2) и подтвердите, нажав "OK" (3). - -* Введите (2.) и подтвердите (3.) пароль для хранилища ключей. ![Выберите путь хранения ключей](../images/studioSetup/47_KeystoreDialog.png) - - ***Примечание:*** Пароли не должны быть очень сложными. Обязательно запомните их или запишите в безопасное место. В случае, если вы не запомните пароли смотрите [ устранение неполадок для потерянных ключей ](troubleshooting_androidstudio-lost-keystore). - -* Введите псевдоним (4) для вашего ключа. Выберите, что нравится. - -* Введите (5.) и подтвердите (6.) пароль для ключа - -* Срок действия (7.) по умолчанию составляет 25 лет. Изменять значение по умолчанию не требуется. - -* Необходимо ввести имя и фамилию (8). Вся остальная информация необязательна. - -* Когда закончите, нажмите кнопку "OK" (9.). - -* Убедитесь, что поле для запоминания паролей отмечено (1). Так что не потребуется вводить их снова при следующей сборке apk (то есть при обновлении до новой версии AAPS). - -* Нажмите "Далее" (2). - - ![Запомните пароли](../images/studioSetup/48_KeystoreSave.png) - -* Выберите вариант сборки "fullRelease" (1) и нажмите "Finish". - - ![Выберите вариант сборки](../images/studioSetup/49_BuildVariant.png) - -* Android Studio покажет «Gradle Build running» внизу. Это занимает некоторое время, в зависимости от компьютера и подключения к Интернету. **Наберитесь терпения!** - - ![Выполняется Gradle](../images/studioSetup/50_GradleRunning.png) - -* После завершения сборки Android Studio покажет информацию "APK (s) сгенерировано успешно...". - - ![Сборка завершена](../images/studioSetup/51_BuildFinished.png) - -* В случае, если сборка не удалась, обратитесь к разделу [поиск и устранение неисправностей ](../Installing-AndroidAPS/troubleshooting_androidstudio). - -* Нажмите на уведомление, чтобы развернуть его. - -* Нажмите на ссылку "locate". (найти расположение). - - ![Найти сборку](../images/studioSetup/52_BuildLocate.png) - - * Если уведомление пропало, откройте "журнал событий" и нажмите на ту же ссылку в нем. ![Построено успешно - журнал событий](../images/studioSetup/53_EventLog.png) - -* Откроется файловый менеджер/проводник. Перейдите в директорию "full" (1) > "release" (2). - - ![Расположение файла apk](../images/studioSetup/54_APKlocation.png) - -* "app-full-release.apk (3) это файл, который вы ищете! - -(Building-APK-перенос-apk-на-телефон) = - -## Перенос приложения на смартфон - -Самый простой способ перенести приложение на ваш телефон - [через кабель USB или Google Drive](https://support.google.com/android/answer/9064445?hl=en). Обратите внимание, что передача по почте может вызвать трудности и не является предпочтительным способом. - -На телефоне необходимо разрешить установку из неизвестных источников. Инструкции, как это сделать, можно найти в интернете (например [здесь](https://www.expressvpn.com/de/support/vpn-setup/enable-apk-installs-android/) или [здесь](https://www.androidcentral.com/unknown-sources)). - -## Устранение неполадок - -См. отдельную страницу [ устранение неполадок Android Studio ](../Installing-AndroidAPS/troubleshooting_androidstudio). \ No newline at end of file diff --git a/docs/CROWDIN/ru/Resources/index.md b/docs/CROWDIN/ru/Resources/index.md deleted file mode 100644 index c663eaf0fca8..000000000000 --- a/docs/CROWDIN/ru/Resources/index.md +++ /dev/null @@ -1,8 +0,0 @@ -# Ресурсы - -```{toctree} -:glob: true -:maxdepth: 4 - -руководство по AndroidAPS для клиницистов -``` diff --git a/docs/CROWDIN/ru/Sandbox/sandbox2.md b/docs/CROWDIN/ru/Sandbox/sandbox2.md deleted file mode 100644 index dfc6c6114b64..000000000000 --- a/docs/CROWDIN/ru/Sandbox/sandbox2.md +++ /dev/null @@ -1,43 +0,0 @@ -# internal sandbox file 2 for testing - -```{admonition} no need to translate this -:class: note - -No need to translate this. -``` - -This is an internal sandbox file for the documentation team to test - -1. markdown syntax and - -1. background process for - 1. CROWDIN translation and - 2. Read The Docs deployment. - -You can dirctly jump from here to the first label in the sandbox1.md file - ["Jump"](sandbox1-this-is-a-test). - -You can dirctly jump from here to the second label in this file - ["Jump"](sandbox1-this-is-another-test). - -Here you can jump to the first sandbox file - ["Jump"](./sandbox1.md). - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -(sandbox2-this-is-a-test)= -## This is a test - -This is a test if labels must be unique. - -### This is spare information from the docs - -cut from index: - -There are "limits" set in place when you are first beginning your AAPS journey. Эти ограничения безопасности были разработаны на протяжении многих лет в результате наблюдений за непреднамеренными ошибками, которые появляются у новых пользователей при обучении создании и первом успешном запуске AAPS - как правило, эти ошибки возникают просто потому, что пользователь был так рад начату работы с системой, что забыл посвятить время глубокому пониманию информации в этой документации. - - -### spare info from the overview to put into "preparing" - -Поскольку требования сильно отличаются от всего, что вы, возможно, устанавливали раньше, мы рекомендуем следовать инструкциям, шаг за шагом в первые несколько раз при создании приложения, чтобы у вас было более четкое представление о том, как происходит процесс если все указания выполняются в точности. Помните, что спешить здесь не надо. В дальнейшем, когда вы будете собирать новую версию, все пойдет гораздо быстрее. Таким образом, у вас будет больше возможностей заметить, что что-то пошло не так, не отклоняясь слишком далеко. Важно сохранить файл хранилища ключей (файл.jks, используемый для подписи приложения) в безопасном месте, чтобы всегда использовать один и тот же файл хранилища ключей и пароль при создании новой версии AAPS, поскольку именно этот файл гарантирует, что каждая новая версия приложения «запоминает» всю информацию, которую вы предоставили ей в предыдущих версиях приложения, и, таким образом, обновления будут проходить максимально гладко. В среднем можно предполагать, что будет одна новая версия и 2-3 обязательных обновления в год. Эта цифра основана на опыте и может измениться в будущем. Но мы хотим дать вам представление о том, чего ожидать. Когда вы наберетесь опыта в обновлении AAPS, все шаги, необходимые для создания обновлённого приложения, займут в среднем всего 15-30 минут. Однако, в начале кривая обучения может быть довольно крутой, так как многие шаги не всегда интуитивно понятны для новых пользователей! Так что не отчаивайтесь, если обнаружите, что у вас ушло полдня или даже целый день не без помощи сообщества до того, как вы наконец закончили процесс обновления. Если вы почувствуете разочарование, сделайте небольшой перерыв и часто, после прогулки, вы обнаружите, что готовы возобновить работу. diff --git a/docs/CROWDIN/ru/Usage/Objectives.md b/docs/CROWDIN/ru/Usage/Objectives.md deleted file mode 100644 index 553af2ce920a..000000000000 --- a/docs/CROWDIN/ru/Usage/Objectives.md +++ /dev/null @@ -1,184 +0,0 @@ -# Цели - -AAPS ставит ряд Целей, которые необходимо выполнить, чтобы изучить все возможности и настройки программы для дальнейшей безопасной работы. Цели позволяют удостовериться, что все настроено правильно, что вы понимаете что, как и почему делает программа, и что ей можно доверять. - -Если вы **обновляете телефон**, то можете [экспортировать настройки](../Usage/ExportImportSettings.md) чтобы сохранить прохождение целей. При этом будут сохранен не только ваш прогресс в прохождении целей, но и настройки безопасности, такие как максимальный болюс и т. п. Если вы не сделаете экспорт-импорт настроек - вам придется заново проходить все цели. Рекомендуется на всякий случай периодически [делать резервную копию актуальных настроек](../Usage/ExportImportSettings.html). - -Если вы захотите снова пройти цели - смотрите [объяснения ниже](Objectives-go-back-in-objectives). - -## Цель 1: Настройка визуализации и мониторинга, анализ базальной скорости и коэффициентов - -- Выберите свой источник данных ГК. См. [Источники ГК](../Configuration/BG-Source.md) для дополнительной информации. -- Выберите нужную помпу в Конфигураторе (если нет возможности подключить помпу к телефону - вберите виртуальную помпу), чтобы подключить ее к AAPS. -- При работе с [помпой Dana R ](../Configuration/DanaR-Insulin-Pump.md) следуйте отдельным инструкциям по привязке помпы к AndroidAPS. -- Для достижения этой цели необходимо создать хранилище данных/платформу для отчетов. Это можно сделать с помощью Nightscout или Tidepool (или обоих). Следуйте инструкциям на странице [Nightscout](../Installing-AndroidAPS/Nightscout.md) или [Tidepool](../Installing-AndroidAPS/Tidepool.md). -- Обратите внимание: URL в AAPSClient **не должен содержать строку /api/v1/** в конце - см. подробнее в [настройках Клиент NS](Preferences-nsclient). - -*Возможно, потребуется дождаться следующего значения ГК, прежде чем AAPS распознает его и примет в обработку.* - -## Цель 2: Научитесь контролировать AAPS - -- Выполните несколько действий в AAPS, которые описаны в этой цели. - -- Нажмите на оранжевый текст «Не завершено» для доступа к каждому заданию. - -- Если вы еще не знакомы с конкретным действием - вам будут предоставлены ссылки на инструкции из этой документации. - - ```{image} ../images/Objective2_V2_5.png - :alt: снимок экрана Цель 2 - ``` - -(Objectives-objective-3-prove-your-knowledge)= - -## Цель 3: Подтвердите ваши знания - -Цель3 - это тест с множественным выбором на основе вопросов, призванных проверить теоретические знания **AAPS**. - -Некоторые пользователи считают цель 3 самой трудной. Прочитайте документы ААПС в сочетании с вопросами. Если вы действительно застряли после изучения документации **AAPS**, найдите или запросите помощь в Facebook или группе Discord. Эти группы могут дать подсказки или перенаправить вас на соответствующую часть документов **AAPS**. - -Чтобы приступить к реализации цели 3, нажмите на оранжевый текст «Не завершено», чтобы получить доступ к соответствующему вопросу. Прочтите каждый вопрос и выберите ответ(ы). - - - -В каждом вопросе есть гиперссылка на документы **AAPS** для поиска правильного ответа. - - -[Obj3_Снимок экрана 2023-12-05 223422](https://github.com/openaps/AndroidAPSdocs/assets/137224335/77347516-e24e-459d-98ab-acbb49a3d4e8)![изображение](https://github.com/openaps/AndroidAPSdocs/assets/137224335/ca756b8e-efbc-4427-b281-ac953ce16718) - - - -Для каждого вопроса правильным может быть больше одного ответа! Если выбран неверный ответ, вопрос будет заблокирован на определенное время (60 минут), прежде чем вы сможете вернуться и ответить на вопрос. - - -После обновления до новой версии **AAPS**, могут быть добавлены новые вопросы для преодоления распространенных затруднений **AAPS** или, по мере появления, для проверки знаний о новых функциях **AAPS**. - - -Когда **AAPS** устанавливается в первый раз, необходимо полностью пройти цель 3 для того, чтобы перейти к цели 4. Каждая цель должна быть выполнена в последовательном порядке. Постепенно, по мере преодоления целей, будут открываться новые возможности приложения. - -__Что произойдет, если в цель 3 позднее будут добавлены новые вопросы?__ Время от времени в **AAPS** добавляются новые функции, что может потребовать добавления нового вопроса к цели 3. В результате любой новый вопрос, добавленный к цели 3, будет помечен как «незавершенный», потому что **AAPS** потребует на него ответа. Поскольку каждая цель независима, вы не потеряете существующую функциональность **AAPS** при условии, что другие цели останутся выполненными. - - -## Цель 4: Начните с открытого цикла - -- Выберите открытый цикл либо в настройках, либо нажав кнопку "Открытый цикл" в левом верхнем углу главного экрана. -- Зайдите в [Настройки](../Configuration/Preferences.md) и измените их исходя из своих потребностей. -- Вручную активируйте по крайней мере 20 предложений временного базала на протяжении 7 дней, введите их в помпу и подтвердите в AAPS что вы их приняли. Убедитесь, что изменения появились как в AAPS, так и в Nightscout. -- При необходимости применяйте [временные цели (ВЦ)](../Usage/temptarget.md). Используйте ВЦ Гипо для купирования гипогликемии, чтобы предотвратить слишком активное скалывание растущей после купирования гипо ГК. - -### Сократите количество уведомлений - -- Для сокращения количества предложений во время работы в режиме Открытого цикла установите широкий целевой диапазон, например, 90-150 мг/дл или 5,0-8,5 ммоль/л. - -- Возможно, вам захочется увеличить верхнюю границу диапазона на ночь (или вовсе отключить цикл на это время). - -- В настройках можно установить минимальный процент для предложений по изменению базальной скорости. - - ```{image} ../images/OpenLoop_MinimalRequestChange2.png - :alt: изменение минимального запроса на незамкнутом цикле - ``` - -- Необязательно принимать все-все предложения алгоритма каждые 5 минут... - -## Цель 5: Глубже понимаем работу системы в режиме незамкнутого цикла, включая ее рекомендации по временным базалам - -- Начинаем вникать в рекомендации по временному базалу, изучая [логику определения базала](https://openaps.readthedocs.io/en/latest/docs/While%20You%20Wait%20For%20Gear/Understand-determine-basal.html), а также [линии прогнозируемой гликемии на главном экране AAPS](Screenshots-prediction-lines) / Nightscout и результаты вычислений на вкладке OpenAps). - -Целевые значения гликемии следует несколько завысить до тех пор, пока вы не убедитесь в правильности всех вычислений и настроек. Система позволяет - -- установить нижнюю границу целевого значения ГК в диапазоне между 4 ммоль/л (72 мг/дл) и 10 ммоль/л (180 мг/дл) -- установить верхнюю границу целевого значения ГК в диапазоне между 5 ммоль/л (90 мг/дл) и 15 ммоль/л (225 мг/дл) -- временная цель как самостоятельная величина ГК может находиться в диапазоне от 4 до 15 ммоль/л (от 72 до 225 мг/дл) - -Целевое значение - это значение, на котором основываются расчеты, это не тот диапазон, в рамках которого вам надо стараться удерживать вашу ГК. Если ваш целевой диапазон очень широк (скажем, 3 или более ммоль/л \[ 50 мг/дл или более\]), то AAPS будет редко запрашивать какие-либо изменения. Это связано с тем, что расчетные значения ГК будут располагаться где-то в этом широком диапазоне и, следовательно, изменения базальной скорости не потребуются. - -Можете поэкспериментировать и задать более узкий диапазон значений (например, чтобы разность между нижней и верхней границами не превышала 1 ммоль/л) и понаблюдать, как при этом изменится поведение системы. - -Для визуализации на графике того целевого диапазона, в котором надо удерживать ГК (зеленая область), установите границы этого диапазона в [Настройках](../Configuration/Preferences.md) > Начало > Диапазон для визуализации. - -```{image} ../images/sign_stop.png -:alt: знак "Стоп" -``` - -### Остановитесь здесь, если пользуетесь открытым циклом с виртуальной помпой - не нажимайте на кнопку «Подтвердить» в конце цели. - -```{image} ../images/blank.png -:alt: пусто -``` - -(Objectives-objective-6-starting-to-close-the-loop-with-low-glucose-suspend)= -## Цель 6: Начинаем замыкать цикл с Low Glucose Suspend (прекращением подачи инсулина на низких сахарах) - -```{image} ../images/sign_warning.png -:alt: предупреждающий знак -``` - -### В цели 6 система не будет пытаться снижать высокие сахара, так как здесь она ограничена только приостановкой на низкой ГК. Высокие значения ГК необходимо корректировать самостоятельно! - -- Предварительное условие: для того, чтобы начать работать в режиме приостановки на низких необходимо уже иметь хорошо работающий в AAPS профиль (подобранные базал, фактор чувствительности к инсулину ISF, углеводный коэффициент IC). Иначе можно уйти в гипогликемию, которую придется компенсировать вручную. Это позволит вам эффективно избегать гип на протяжении более 5 дней. **Если у вас еще часто случаются эпизоды гипогликемии, или они бывают очень сильными, то вам следует пересмотреть настройки DIA, базала, ISF или IC и пока НЕ приступать к выполнению 6 цели.** -- На этом этапе менять настройки не нужно. На протяжении выполнения Цели 6 значение maxIOB будет считаться равным 0. **При переходе на Цель 7 снова будет использоваться установленное ранее значение.** -- Система будет основывать свои расчеты на maxIOB = 0, а значит при резком снижении ГК сможет уменьшить базальную скорость. Если ГК растет, то базальная скорость будет увеличена только если IOB будет отрицательным в связи с отработавшим алгоритмом приостановки на низких. В ином случае скорость базала будет соответствовать значению из профиля. **Это значит, что вам необходимо вручную компенсировать повышение ГК.** -- Если текущее значение IOB отрицательное (см. снимки экрана ниже), то при прохождении цели 6 может также быть установлена ВБС> 100%. - -```{image} ../images/Objective6_negIOB.png -:alt: Пример отрицательного IOB -``` - -- В качестве дополнительной предосторожности установите целевой диапазон немного шире, чем ваш обычный. -- Включите режим «Приостановка на низких» нажав и удерживая значок Цикла в правом верхнем углу главного экрана и выбрав значок «Цикл - LGS». -- Наблюдайте за работой временного базала по тексту синего цвета или по синему графику на главном экране. -- Возможны временные пики вслед за мерами против гипогликемии без возможности увеличить базу на откате._ - -(Objectives-objective-7-tuning-the-closed-loop-raising-max-iob-above-0-and-gradually-lowering-bg-targets)= -## Цель 7: Настройка замкнутого цикла с поднятием макс величины IOB выше 0 и постепенным понижением целевой ГК - -- В течение одного дня выберите "Замкнутый цикл" либо в [Настройках](../Configuration/Preferences.md), либо нажав и удерживая значок цикла в правом верхнем углу главного экрана. - -- Поднимите значение "Максимальный суммарный активный инсулин которое не может превысить алгоритм OpenAPS " (в OpenAPS называется "max-iob") выше 0. Рекомендация по умолчанию - "средний болюс на прием пищи + 3-кратная максимальная базальная доза" (для алгоритма SMB) или "3-кратная максимальная базальная доза" (для более старого алгоритма AMA), но переходить к этому следует постепенно, пока не убедитесь, что настройки подходят для вас (максимальная базальная доза (в течение суток) = максимальное почасовое значение в любой временной отрезок дня). - - Эта рекомендация должна рассматриваться как отправная точка. Если вы установили троекратную величину и видите признаки того, что для вас это слишком жестко, понизьте ее. Если у вас высокая резистентность повышайте эту величину постепенно. - - ```{image} ../images/MaxDailyBasal2.png - :alt: максимальный суточный базал - ``` - -- Определив величину активного инсулина IOB, подходящую именно вам, понизьте целевое значение ГК до желаемого уровня. - -(Objectives-objective-8-adjust-basals-and-ratios-if-needed-and-then-enable-autosens)= -## Цель 8: Настраиваем базал и коэффициенты с последующей активацией autosens - -- Можно однократно воспользоваться автонастройкой [autotune](https://openaps.readthedocs.io/en/latest/docs/Customize-Iterate/autotune.html), чтобы проверить, остаются ли точными настройки базала или провести традиционный тест базы. -- Активируйте авточувствительность [autosens](../Usage/Open-APS-features.md) на 7 дней и понаблюдайте за тем, как опускается или поднимается белая линия чувствительности к инсулину на графике домашнего экрана в результате нагрузок, гормонов и т. п. не забывая о вкладке отчетов OpenAPS, где AAPS соответствующим образом корректирует базу и/или цели. - -Если это еще не сделано, *зарегистрируйтесь как пользователь системы ИПЖ*, заполнив [анкету](https://bit.ly/nowlooping)* и указав AAPS в качестве самостоятельно собранного ПО* - -(Objectives-objective-9-enabling-additional-oref1-features-for-daytime-use-such-as-super-micro-bolus-smb)= -## Цель 9: Активация таких дополнительных функций для дневного времени как супер микро болюс SMB - -- Следует прочитать [раздел СМБ в этой документации](Open-APS-features-super-micro-bolus-smb) и [главу oref1 в документации по openAPSdocs](https://openaps.readthedocs.io/en/latest/docs/Customize-Iterate/oref1.html) чтобы понять, как работает СМБ, и какая идея стоит за отключением базала при использовании этого алгоритма. -- Затем следует [поднять maxIOB](Open-APS-features-maximum-total-iob-openaps-cant-go-over-openaps-max-iob), чтобы заставить СМБ работать должным образом. maxIOB теперь учитывает весь активный инсулин IOB, а не только дополнительный базал. То есть, если подан болюс 8 ед. на еду, а maxIOB равен 7 ед., то СМБ не будет подан до тех пор, пока активный инсулин IOB не упадет ниже 7 ед. Хорошим стартом является расчет maxIOB = средний подаваемый на еду болюс + 3 максимальных ежедневных базала (макс. ежедневный базал = максимальное значение базальной скорости в течении дня) - см. [Цель 7](Objectives-objective-7-tuning-the-closed-loop-raising-max-iob-above-0-and-gradually-lowering-bg-targets) -- При переходе с алгоритма AMA на СМБ значение усвоения углеводов по умолчанию (min_5m_carbimpact) изменится с 3 до 8. Если вы переходите с AMA на СМБ - вам нужно изменить это значение самостоятельно. - -(Objectives-objective-10-automation)= -## Цель 10: Автоматизация - -- Вы должны начать цель 10 для использования [Автоматизации](../Usage/Automation.md). -- Убедитесь, что вы завершили все предыдущие цели, включая [Цель 3: Подтвердите ваши знания](Objectives#objective-3-prove-your-knowledge). -- Повторное прохождение более ранних целей не приведет к сбросу более поздних, если они уже были успешно завершены. У вас сохранятся все завершенные цели! - -(Цели-цель-11-DynamicISF)= -## Цель 11: Дополнительные функции, такие как Динамический ISF - -- Вы должны начать цель 11 для работы в режиме [DynamicISF](../Usage/Open-APS-features.md) - -(Objectives-go-back-in-objectives)= -## Возможность возврата к предыдущим целям - -Если вы по какой-либо причине хотите вернуться к более ранним целям, можете сделать это, нажав на "очистить завершенное". - -```{image} ../images/Objective_ClearFinished.png -:alt: Вернуться в цели -``` - -## Цели в Android APS до версии 3.0 - -Одна из целей была удалена после выхода Android APS 3.0. Для пользователей Android APS версии 2.8.2.1 на старых телефонах (версия ОС Android ниже 9) будет использован прежний набор целей, который можно найти [тут](../Usage/Objectives_old.md). diff --git a/docs/CROWDIN/ru/Usage/Objectives2019.md b/docs/CROWDIN/ru/Usage/Objectives2019.md deleted file mode 100644 index a746dff6f6e7..000000000000 --- a/docs/CROWDIN/ru/Usage/Objectives2019.md +++ /dev/null @@ -1,111 +0,0 @@ -# Цели - -AndroidAPS ставит ряд Целей, которые необходимо выполнить, чтобы подготовиться к свойствам и параметрам настроек для безопасной работы алгоритма ИПЖ. Цели позволяют удостовериться, что все сконфигурировано правильно, что мы понимаем, что, как и почему делает система и что мы можем доверять ей. - -If you are **upgrading phones** then you can [export your settings](../Usage/ExportImportSettings.md) to keep your progress through the objectives. Ваш прогресс будет сохранен не только в прохождении целей, но и в настройках безопасности, таких как максимальный болюс и т. д. Если настройки не переносить, то движение к целям придется начинать заново. It is a good idea to [backup your settings](../Usage/ExportImportSettings.html) frequently just in case. - -## Цель 1: Настройка визуализации и мониторинга, анализ базальной скорости и коэффициентов - -- Select the right blood glucose source for your setup. See [BG Source](../Configuration/BG-Source.md) for more information. -- Select the right Pump in ConfigBuilder (select Virtual Pump if you are using a pump model with no AndroidAPS driver for looping) to ensure your pump status can communicate with AndroidAPS. -- If using DanaR pump then ensure you have followed [DanaR Insulin Pump](../Configuration/DanaR-Insulin-Pump.md) instructions to ensure the link between pump and AndroidAPS. -- Follow instructions in [Nightscout](../Installing-AndroidAPS/Nightscout.md) page to ensure Nightscout can receive and display this data. -- Note that URL in NSClient must be **WITHOUT /api/v1/** at the end - see [NSClient settings in Preferences](../Configuration/Preferences#ns-client). - -*You may need to wait for the next blood glucose reading to arrive before AndroidAPS will recognise it.* - -## Objective 2: Learn how to control AndroidAPS - -- Perform several actions in AndroidAPS as described in this objective. - -- Click on the orange text "Not completed yet" to access the to-dos. - -- Links will be provided to guide you in case you are not familiar with a specific action yet. - - > ```{image} ../images/Objective2_V2_5.png - > :alt: Screenshot objective 2 - > ``` - -## Objective 3: Prove your knowledge - -- Pass a multiple-choice exam testing your AndroidAPS knowledge. - -- Click on the orange text "Not completed yet" to access the page with the question and answering optons. - -- Links will be provided to guide you in case you are unsure abouit the correct answers yet. - - > ```{image} ../images/Objective3_V2_5.png - > :alt: Screenshot objective 3 - > ``` - -## Objective 4: Starting on an open loop - -- Select Open Loop either from Preferences, or by pressing and holding the Loop button in top left of the home screen. -- Work through the [Preferences](../Configuration/Preferences.md) to set up for you. -- Manually enact at least 20 of the temporary basal rate suggestions over a period of 7 days; input them to your pump and confirm in AndroidAPS that you have accepted them. Убедитесь, что эти данные представлены в AndroidAPS и Nightscout. -- Enable [temp targets](../Usage/temptarget.md) if necessary. Используйте врем. цели для купирования гипогликемии чтобы предотвратить слишком сильные коррекции после гипо. - -## Objective 5: Understanding your open loop, including its temp basal recommendations - -- Start to understand the thinking behind the temp basal recommendations by looking at the [determine basal logic](https://openaps.readthedocs.io/en/latest/docs/While%20You%20Wait%20For%20Gear/Understand-determine-basal.html) and both the [forecast line in AndroidAPS homescreen](../Getting-Started/Screenshots#section-e)/Nightscout and the summary of outputs from the calculations in your OpenAPS tab. - -До тех пор, пока мы не убедимся в правильности вычислений и настроек, целевые значения гликемии следует несколько завысить. System allows - -- a low target to be a minimum of 4 mmol (72 mg/dl) or maximum of 10 mmol (180 mg/dl) -- a high target to be a minimum of 5 mmol (90 mg/dl) and maximum of 15 mmol (225 mg/dl) -- a temporary target as a single value can be anywhere in the range of 4 mmol to 15 mmol (72 mg/dl to 225 mg/dl) - -Целевое значение - это значение, на котором основываются расчеты, а не то же самое, что долгосрочные целевые значения вашей ГК. If your target is very wide (say, 3 or more mmol \[50 mg/dl or more\] wide), you will often find little AAPS action. This is because blood glucose is eventually predicted to be somewhere in that wide range and therefore not many fluctuating temporary basal rates are suggested. - -You may want to experiment with adjusting your targets to be a closer together range (say, 1 or less mmol \[20 mg/dl or less\] wide), and observe how the behavior of your system changes as a result. - -You can view a wider range (green lines) on the graph for the values you aim to keep your blood glucose within by entering different values in [Preferences](../Configuration/Preferences.md) > Range for Visualisation. - -![Stop sign](../images/sign_stop.png) - -### Остановитесь здесь, если пользуетесь незамкнутым циклом с виртуальной помпой - не нажимайте на кнопку «Верифицировать» в конце цели. - -![blank](../images/blank.png) - -## Objective 6: Starting to close the loop with Low Glucose Suspend - -![Warning sign](../images/sign_warning.png) - -### Closed loop will not correct high bg values in objective 6 as it is limited to low glucose suspend. Вы сами вручную должны корректировать высокие значения ГК! - -- Select Closed Loop either from [Preferences](../Configuration/Preferences.md) or by pressing and holding the Open Loop button in the top left of the home screen. -- Set your target range slightly higher than you usually aim for, just to be safe. -- Watch how temporary basals are active by viewing the blue basal text on the homescreen or the blue basal render on the homescreen graph. -- Ensure your settings have supported AndroidAPS to avoid having to treat a low glucose over a period of 5 days. Если эпизоды низкой гликемии все же сохраняются, поправьте параметры DIA (продолжительность действия инсулина), скорость базала, ISF (фактор чувствительности к инсулину) и пропорции инсулин-углеводы. - -*The system will override your maxIOB settings to zero, which means if blood glucose is dropping it can reduce basal for you, but if blood glucose is rising then it will only increase basal if the IOB is negative (from a previous Low Glucose Suspend), otherwise basal rates will remain the same as your selected profile. You may temporarily experience spikes following treated hypos without the ability to increase basal on the rebound.* - -## Objective 7: Tuning the closed loop, raising max IOB above 0 and gradually lowering BG targets - -- Raise your 'Maximum total IOB OpenAPS can’t go over' (in OpenAPS called 'max-iob') above 0 over a period of 1 day, the default recommendation is "average mealbolus + 3x max daily basal"(for SMB algorithm) or "3x max daily basal" (for older AMA algorithm) but you should slowly work up to this until you know your settings work for you (max daily basal = the maximum hourly value in any time segment of the day). - - Эта рекомендация должна рассматриваться как отправная точка. Если вы установили троекратную величину и видите признаки того, что для вас это слишком жестко, понизьте ее. Если у вас высокая резистентность повышайте эту величину постепенно. - - > ```{image} ../images/MaxDailyBasal2.png - > :alt: max daily basal - > ``` - -- Once confident on how much IOB suits your looping patterns then reduce your targets to your desired level. - -## Objective 8: Adjust basals and ratios if needed, and then enable autosens - -- You can use [autotune](https://openaps.readthedocs.io/en/latest/docs/Customize-Iterate/autotune.html) as a one off to check your basals remain accurate, or do a traditional basal test. -- Enable [autosens](../Usage/Open-APS-features.md) over a period of 7 days and watch the white line on the homescreen graph show how your sensitivity to insulin may be rising or falling as a result of exercise or hormones etc, and keep an eye in the OpenAPS report tab how AndroidAPS is adjusting the basals and/or targets accordingly. - -*Don’t forget to record your looping in \`this form \\`\_ logging AndroidAPS as your type of DIY loop software, if you have not already done so.* - -## Objective 9: Enabling additional oref0 features for daytime use, such as advanced meal assist (AMA) - -- Now you should feel confident with how AndroidAPS works and what settings reflect your diabetes best -- Then over a period of 28 days you can try additional features that automate even more of the work for you such as the [advanced meal assist](../Usage/Open-APS-features#advanced-meal-assist-ama) - -## Objective 10: Enabling additional oref1 features for daytime use, such as super micro bolus (SMB) - -- You must read the [SMB chapter in this wiki](../Usage/Open-APS-features#super-micro-bolus-smb) and [chapter oref1 in openAPSdocs](https://openaps.readthedocs.io/en/latest/docs/Customize-Iterate/oref1.html) to understand how SMB works, especially what's the idea behind zero-temping. -- Then you ought to [rise maxIOB](../Usage/Open-APS-features#maximum-total-iob-openaps-cant-go-over-openaps-max-iob) to get SMBs working fine. maxIOB теперь включает весь активный инсулин IOB, а не только добавленный базал. That is, if given a bolus of 8 U for a meal and maxIOB is 7 U, no SMBs will be delivered until IOB drops below 7 U. A good start is maxIOB = average mealbolus + 3x max daily basal (max daily basal = the maximum hourly value in any time segment of the day - see [objective 7](../Usage/Objectives2019.md#objective-7-tuning-the-closed-loop-raising-max-iob-above-0-and-gradually-lowering-bg-targets) for an illustration) -- min_5m_carbimpact default in absorption settings has changed from 3 to 8 going from AMA to SMB. Если вы переходите с AMA на SMB, то вам нужно изменить его вручную diff --git a/docs/CROWDIN/ru/Usage/Objectives_old.md b/docs/CROWDIN/ru/Usage/Objectives_old.md deleted file mode 100644 index 6d8954ce7b92..000000000000 --- a/docs/CROWDIN/ru/Usage/Objectives_old.md +++ /dev/null @@ -1,152 +0,0 @@ -# Цели - начиная с Android APS 2.8.2.1 - -Это не новейшая версия целей Android APS. На этой странице описываются Цели, которые существовали до версии 3.0. Anyone using an older version of Android (i.e. prior to Android 9) and Android APS version 2.8.2.1 should refer to this page. - -Please see [this page](../Usage/Objectives.md) for the current set of Objectives. - -AndroidAPS ставит ряд Целей, которые необходимо выполнить, чтобы подготовиться к свойствам и параметрам настроек для безопасной работы алгоритма ИПЖ. Цели позволяют удостовериться, что все сконфигурировано правильно, что мы понимаем, что, как и почему делает система и что мы можем доверять ей. - -If you are **upgrading phones** then you can [export your settings](../Usage/ExportImportSettings.md) to keep your progress through the objectives. Not only will your progress through the objectives be saved, but also your safety settings such as max bolus etc. If you do not export and import your settings then you will need to start the objectives from the beginning again. It is a good idea to [backup your settings](../Usage/ExportImportSettings.html) frequently just in case. - -If you want to go back in objectives see [explanation below](../Usage/Objectives.md#go-back-in-objectives). - -## Цель 1: Настройка визуализации и мониторинга, анализ базальной скорости и коэффициентов - -- Select the right blood glucose source for your setup. See [BG Source](../Configuration/BG-Source.md) for more information. -- Select the right Pump in ConfigBuilder (select Virtual Pump if you are using a pump model with no AndroidAPS driver for looping) to ensure your pump status can communicate with AndroidAPS. -- If using DanaR pump then ensure you have followed [DanaR Insulin Pump](../Configuration/DanaR-Insulin-Pump.md) instructions to ensure the link between pump and AndroidAPS. -- Follow instructions in [Nightscout](../Installing-AndroidAPS/Nightscout.md) page to ensure Nightscout can receive and display this data. -- Note that URL in NSClient must be **WITHOUT /api/v1/** at the end - see [NSClient settings in Preferences](../Configuration/Preferences.md#nsclient). - -*You may need to wait for the next blood glucose reading to arrive before AndroidAPS will recognise it.* - -## Цель 2: научиться контролировать AndroidAPS - -- Perform several actions in AndroidAPS as described in this objective. - -- Click on the orange text "Not completed yet" to access the to-dos. - -- Links will be provided to guide you in case you are not familiar with a specific action yet. - - ![снимок экрана Цель 2](../images/Objective2_V2_5.png) - -## Цель 3: доказательство знаний - -- Pass a multiple-choice exam testing your AndroidAPS knowledge. - -- Click on the orange text "Not completed yet" to access the page with the question and answering options. - - ![снимок экрана Цель 3](../images/Objective3_V2_5.png) - -- Links will be provided to guide you in case you are unsure about the correct answers yet. - -- The questions for objective 3 have been completely rewritten by native speakers as of AAPS 2.8. Новые темы охватывают те же основные вопросы плюс несколько новых. - -- These new questions will lead to some not answered questions even though you have successfully completed objective 3 in previous versions. - -- Unanswered questions will affect you only if you start a new objective. Другими словами, если вы уже достигли всех целей, вы можете подождать и отвечать на новые вопросы позже, не теряя функционал AAPS. - -## Цель 4: Начало на незамкнутом цикле - -- Select Open Loop either from Preferences, or by pressing and holding the Loop button in top left of the home screen. -- Work through the [Preferences](../Configuration/Preferences.md) to set up for you. -- Manually enact at least 20 of the temporary basal rate suggestions over a period of 7 days; input them to your pump and confirm in AndroidAPS that you have accepted them. Убедитесь, что эти данные представлены в AndroidAPS и Nightscout. -- Enable [temp targets](../Usage/temptarget.md) if necessary. Используйте врем. цели для купирования гипогликемии чтобы предотвратить слишком сильные коррекции после гипо. - -### Сократите количество уведомлений - -- To reduce the Number of decisions to be made while in Open Loop set wide target range like 90 - 150 mg/dl or 5,0 - 8,5 mmol/l. - -- You might even want to wider upper limit (or disable Open Loop) at night. - -- In Preferences you can set a minimum percentage for suggestion of basal rate change. - - ![изменение минимального запроса на незамкнутом цикле](../images/OpenLoop_MinimalRequestChange2.png) - -- Also, you do not need to act every 5 minutes on all suggestions... - -## Глубже понимаем незамкнутую систему Open Loop, включая ее рекомендации по временным базалам - -- Start to understand the thinking behind the temp basal recommendations by looking at the [determine basal logic](https://openaps.readthedocs.io/en/latest/docs/While%20You%20Wait%20For%20Gear/Understand-determine-basal.html) and both the [forecast line in AndroidAPS homescreen](../Getting-Started/Screenshots.md#prediction-lines)/Nightscout and the summary of outputs from the calculations in your OpenAPS tab. - -До тех пор, пока мы не убедимся в правильности вычислений и настроек, целевые значения гликемии следует несколько завышать. Система позволяет - -- a low target to be a minimum of 4 mmol (72 mg/dl) or maximum of 10 mmol (180 mg/dl) -- a high target to be a minimum of 5 mmol (90 mg/dl) and maximum of 15 mmol (225 mg/dl) -- a temporary target as a single value can be anywhere in the range of 4 mmol to 15 mmol (72 mg/dl to 225 mg/dl) - -Целевое значение - это значение, на котором основываются расчеты, а не то же самое, что долгосрочные целевые значения вашей ГК. If your target is very wide (say, 3 or more mmol \[50 mg/dl or more\] wide), you will often find little AAPS action. Это связано с тем, что конечные значения ГК предполагаются где-то в этом широком диапазоне и, следовательно, не происходит много изменений базальной скорости. - -You may want to experiment with adjusting your targets to be a closer together range (say, 1 or less mmol \[20 mg/dl or less\] wide) and observe how the behavior of your system changes as a result. - -You can view a wider range (green lines) on the graph for the values you aim to keep your blood glucose within by entering different values in [Preferences](../Configuration/Preferences.md) > Range for Visualisation. - -![знак "Стоп"](../images/sign_stop.png) - -### Остановитесь здесь, если пользуетесь незамкнутым циклом с виртуальной помпой - не нажимайте на кнопку «Верифицировать» в конце цели. - -![пусто](../images/blank.png) - -## Цель 6: Начинаем замыкать цикл с Low Glucose Suspend (прекращением подачи инсулина на низких сахарах) - -![предупреждающий знак](../images/sign_warning.png) - -### Замкнутый цикл не будет исправлять значения высокой ГК в цели 6, поскольку он ограничен приостановкой подачи инсулина на низких сахарах. Вы сами вручную должны корректировать высокие значения ГК! - -- Select Closed Loop either from [Preferences](../Configuration/Preferences.md) or by pressing and holding the Open Loop button in the top left of the home screen. - -- Set your target range slightly higher than you usually aim for, just to be safe. - -- Watch how temporary basals are active by viewing the blue basal text on the homescreen or the blue basal render on the homescreen graph. - -- Ensure your settings have supported AndroidAPS to avoid having to treat a low glucose over a period of 5 days. Если эпизоды низкой гликемии все же сохраняются, поправьте параметры DIA (продолжительность действия инсулина), скорость базала, ISF (фактор чувствительности к инсулину) и пропорции инсулин-углеводы. - -- You don't have to change your settings. В процессе выполнения цели 6 maxIOB автоматически устанавливается на ноль. Это переопределение будет отменено при переходе к цели 7. - -- The system will override your maxIOB settings to zero, which means if blood glucose is dropping it can reduce basal for you, but if blood glucose is rising then it will only increase basal if the basal IOB is negative (from a previous Low Glucose Suspend), otherwise basal rates will remain the same as your selected profile. - - ![Пример отрицательного IOB](../images/Objective6_negIOB.png) - -- If your basal IOB is negative (see screenshot above) a TBR > 100% can be issued also in objective 6. - -- Возможны временные пики вслед за мерами против гипогликемии без возможности увеличить базу на откате._ - -## Цель 7: настройка замкнутого цикла с поднятием макс величины активного инсулина IOB выше 0 и постепенным понижением целевых значений ГК - -- Raise your 'Maximum total IOB OpenAPS can’t go over' (in OpenAPS called 'max-iob') above 0 over a period of 1 day, the default recommendation is "average mealbolus + 3x max daily basal"(for SMB algorithm) or "3x max daily basal" (for older AMA algorithm) but you should slowly work up to this until you know your settings work for you (max daily basal = the maximum hourly value in any time segment of the day). - - Эта рекомендация должна рассматриваться как отправная точка. Если вы установили троекратную величину и видите признаки того, что для вас это слишком жестко, понизьте ее. Если у вас высокая резистентность повышайте эту величину постепенно. - - ![максимальный суточный базал](../images/MaxDailyBasal2.png) - -- Once confident on how much IOB suits your looping patterns then reduce your targets to your desired level. - -## Цель 8: При необходимости скорректируйте базал и коэффициенты и затем активируйте авто-чувствительность autosens - -- You can use [autotune](https://openaps.readthedocs.io/en/latest/docs/Customize-Iterate/autotune.html) as a one off to check your basals remain accurate or do a traditional basal test. -- Enable [autosens](../Usage/Open-APS-features.md) over a period of 7 days and watch the white line on the homescreen graph show how your sensitivity to insulin may be rising or falling as a result of exercise or hormones etc. and keep an eye in the OpenAPS report tab how AndroidAPS is adjusting the basals and/or targets accordingly. - -*Don’t forget to record your looping in* [this form](https://bit.ly/nowlooping) *logging AndroidAPS as your type of DIY loop software, if you have not already done so.* - -## Цель 9: Пробуйте дополнительные функции для дневного времени и убедитесь в надежности закрытой системы - -- Before AAPS version 2.7 meal assist (MA) was the basic algorithm for AAPS and completing objective 8 was necessary to activate [advanced meal assist (AMA)](../Usage/Open-APS-features.md#advanced-meal-assist-ama). -- As [advanced meal assist (AMA)](../Usage/Open-APS-features.md#advanced-meal-assist-ama) is the standard algorithm from AAPS version 2.7 onwards use the following 28 days to try features you haven't used yet and get more confident with you closed loop system. - -## Цель 10: Активация таких дополнительных функций алгоритма oref1 для работы в дневное время, как супер микроболюс SMB - -- You must read the [SMB chapter in this wiki](../Usage/Open-APS-features.md#super-micro-bolus-smb) and [chapter oref1 in openAPSdocs](https://openaps.readthedocs.io/en/latest/docs/Customize-Iterate/oref1.html) to understand how SMB works, especially what's the idea behind zero-temping. -- Then you ought to [rise maxIOB](../Usage/Open-APS-features.md#maximum-total-iob-openaps-cant-go-over-openaps-max-iob) to get SMBs working fine. maxIOB теперь включает весь активный инсулин IOB, а не только добавленный базал. That is, if given a bolus of 8 U for a meal and maxIOB is 7 U, no SMBs will be delivered until IOB drops below 7 U. A good start is maxIOB = average mealbolus + 3x max daily basal (max daily basal = the maximum hourly value in any time segment of the day - see [objective 7](../Usage/Objectives#objective-7-tuning-the-closed-loop-raising-max-iob-above-0-and-gradually-lowering-bg-targets) for an illustration) -- min_5m_carbimpact default in absorption settings has changed from 3 to 8 going from AMA to SMB. Если вы переходите с AMA к SMB, то вам нужно изменить его вручную. - -## Цель 11: Автоматизация - -- You have to start objective 11 to be able to use [Automation](../Usage/Automation.md). -- Make sure you have completed all objectives including exam [../Usage/Objectives.md#objective-3-prove-your-knowledge](../Usage/Objectives#objective-3-prove-your-knowledge). -- Completing previous objectives will not effect other objectives you have already finished. You will keep all finished objectives! - -## Возможность возврата к предыдущим целям - -Если вы хотите вернуться к целям по какой-либо причине, вы можете сделать это, нажав на "очистить завершенное". - -![Вернуться в цели](../images/Objective_ClearFinished.png) diff --git a/docs/CROWDIN/ru/Usage/Smoothing-Blood-Glucose-Data-in-xDrip.md b/docs/CROWDIN/ru/Usage/Smoothing-Blood-Glucose-Data-in-xDrip.md deleted file mode 100644 index 3aa45a2f6bcc..000000000000 --- a/docs/CROWDIN/ru/Usage/Smoothing-Blood-Glucose-Data-in-xDrip.md +++ /dev/null @@ -1,33 +0,0 @@ -(Smoothing-Blood-Glucose-Data-in-xDrip-smoothing-blood-glucose-data)= - -# Сглаживание данных о глюкозе в крови - -If BG data is jumpy/noisy, AAPS may dose insulin incorrectly resulting in high or low BG. For this reason it’s important to disable the loop until the problem is resolved. Depending on your CGM such issues may be due to the CGM’s configuration or sensor problems/site issues. You may need to replace your CGM sensor to resolve this. - -Some CGM systems have internal algorithms to detect the noise level in the readings and AAPS can use this information to avoid giving SMBs if the BG data is too unreliable. However, some CGMs do not transmit this data and for these BG sources 'Enable SMB always' and 'Enable SMB after carbs' are disabled for safety reasons. - -## Сенсоры Dexcom - -### Создайте свое собственное приложение Dexcom - -When using [BYODA](DexcomG6-if-using-g6-with-build-your-own-dexcom-app) your BG data is smooth and consistent. Furthermore you can take advantage of Dexcom back-smoothing. There are no restrictions in using SMBs, because the noise-level data is shared with AAPS. - -### xDrip+ with Dexcom G6 or Dexcom ONE - -Noise-level data and smooth BG readings are only shared with AAPS if you use xDrip+ [native mode](https://navid200.github.io/xDrip/docs/Native-Algorithm). Using native mode, there are no restrictions in using SMBs. - -### Dexcom G6 or Dexcom ONE with xDrip+ Companion Mode - -The noise-level data is not shared with AAPS using this method. Therefore 'Enable SMB always' and 'Enable SMB after carbs' are disabled. - -## Сенсоры Freestyle Libre - -### xDrip+ with FreeStyle Libre - -None of the FreeStyle Libre systems (FSL1, FSL2, or FSL3) broadcast any information about the level of noise detected in the readings, and therefore 'Enable SMB always' and 'Enable SMB after carbs' are disabled for all setups using the FreeStyle Libre. - -In addition, many people have reported the FreeStyle Libre often produces noisy data. In xDrip+ there are a few options to help with this: - -**Smooth Sensor Noise.** In xDrip+ Settings > xDrip+ Display Settings ensure that Smooth Sensor Noise is turned on. This attempts to apply smoothing to noisy data. - -**Smooth Sensor Noise (Ultrasensitive).** If you are still seeing noisy data in xDrip+ you can apply more aggressive smoothing using the Smooth Sensor Noise (Ultrasensitive) setting. This will attempt to apply smoothing even on very low levels of detected noise. To do this, first enable [engineering mode](Enabling-Engineering-Mode-in-xDrip.md) in xDrip+. Then navigate to Settings > xDrip+ Display Settings and turn on Smooth Sensor Noise (Ultrasensitive). \ No newline at end of file diff --git a/docs/CROWDIN/ru/Usage/autotune_b.md b/docs/CROWDIN/ru/Usage/autotune_b.md deleted file mode 100644 index daf5d0313616..000000000000 --- a/docs/CROWDIN/ru/Usage/autotune_b.md +++ /dev/null @@ -1,186 +0,0 @@ -# How to use Autotune plugin - -Documentation about Autotune algorythm can be found in [OpenAPS documentation](https://openaps.readthedocs.io/en/latest/docs/Customize-Iterate/autotune.html). - -Autotune plugin is an implementation of OpenAPS autotune algorythm within AAPS. - -**Currently Autotune Plugin is only available in dev branch with Engineering mode.** - -## Autotune user interface - -![Autotune default screen](../images/Autotune/Autotune_1b.png) - -- You can select in the Profile dropdown menu the input profile you want to tune (by default your current active profile is selected) - - Note: each time you select a new profile, previous results will be removed and Tune days parameter will be set to default value -- Then Tune days is to select the number of days used in calculation to tune your profile. The minimum value is 1 day and the maximum value 30 days. This number should not be too small to get correct iterative and smooth results (above 7 days for each calculation) - - Note: each time you change Tune days parameter, previous results will be removed -- Last Run il a link that recover your latest valid calculation. If you didn't launch Autotune on current day, or if previous results was removed with a modification of calculation parameter above, then you can recover parameters and results of the latest successfull run. -- Warning show you for example some information about selected profile (if you have several IC values or several ISF values) - - Note: Autotune calculation works with only a single IC and a single ISF value. There is currently no existing Autotune algorythm to tune a circadian IC or circadian ISF. If your input profile has several values, you can see in warning section the average value taken into account to tune your profile. -- Check Input Profile button open the Profile Viewer to allow you a quick verification of your profile (Units, DAI, IC, ISF, basal and target) - - Note: Autotune will only tune your IC (single value), ISF (single value) and basal (with circadian variation). Units, DAI and target will remain unchanged in output profile. - -- "Run Autotune" will launch Autotune calculation with selected profile and the number of Tune days - - Note: Autotune calculation can take a long time. Once launched, you can switch to another view (home, ...) and come back later in Autotune plugin to see results - -![Autotune Run start](../images/Autotune/Autotune_2b.png) - -- Then during the run you will see intermediate results below - - - Note: During run, settings are locked, so you cannot change anymore selected input profile or the number of day. You will have to wait the end of current calculation if you want to launch another run with other parameters. - - ![Autotune during run](../images/Autotune/Autotune_3b.png) - -- When Autotune calculation is finished, you will see the result (Tuned profile) and four buttons below. - -![Autotune Result](../images/Autotune/Autotune_4b.png) - -- It's important to always compare input profile (column "Profile"), output profile (column "Tuned") and the percentage of variation for each value (Column "%"). - -- For basal rates, you also have the number of "missing days". You have missing days when Autotune don't have enough data categorized as "Basal" to tune basal rate for this period (for example after each meal when you have carbs absorption). This number should be as low as possible especially when basal is important (for example during the night or at the end of the afternoon) - -- The "Compare profiles" button open the profile comparator view. Input profile is in blue, and output profile (named "Tuned") is in red. - - - Note: in the example below input profile has circadian variation for IC and ISF, but output calculated profile has a single value. If it's important for you to get a circadian output profile see [Circadian IC or ISF profile](#circadian-ic-or-isf-profile) below. - - ![Autotune Compare profiles](../images/Autotune/Autotune_5.png) - -- If you trust results (low percentage of variation between input profile and output profile), you can click on "Activate profile" button and then click on OK to validated. - - - Activate Tuned profile will automatically create a new profile "Tuned" in your Local profile plugin. - - If you already have a profile named "Tuned" in your local profile plugin, then this profile will be updated with calculated Autotune profile before the activation - - ![Autotune Activate profile](../images/Autotune/Autotune_6.png) - -- If you think Tuned profile must be adjusted (for example if you think some variation are too important), then you can click on "Copy to local profile" button - - - A new profile with the prefix "Tuned" and the date and time of the run will be created in local profile plugin - -![Autotune Copy to local profile](../images/Autotune/Autotune_7.png) - -- You can then select local profile to edit the Tuned profile (it will be selected by default when you open Local profile plugin) - - - the values in local profile will but rounded in the user interface to your pump capabilities - - ![Autotune local profile update](../images/Autotune/Autotune_8.png) - -- If you want to replace your input profile with Autotune result, click on "Update input profile" button and validate the Popup with OK - - - Note: if you click on "Activate profile" after "Update input profile", then you will activate your updated profile and not the default "Tuned" profile? - - ![Autotune Update input profile](../images/Autotune/Autotune_9.png) - -- If you have updated your input profile, then the "Update input profile" button is replaced by "Revert input profile" button (see screenshot below). You can that way immediatly see if your current input profile in Local profile plugin already include the result of last run or not. You also have the possibility to recover you input profile without autotune result with this button - - ![Autotune Update input profile](../images/Autotune/Autotune_10.png) - - - -## Autotune settings - -### Autotune plugin settings - -![Autotune default screen](../images/Autotune/Autotune_11.png) - -- Automation Switch Profile (default Off): see [Run Autotune with an automation rule](#run-autotune-with-an-automation-rule) below. If you change this setting to On, the input profile will automatically be updated by the Tuned profile, and it will be activated. - - **Be Carefull, you must trust and verified during several following days that after an update and activation of Tuned profile without modification, it improves your loop** - -- Categorize UAM as basal (default On): This setting is for the users using AndroidAPS without any carbs entered (Full UAM). It will prevent (when Off) to categorize UAM as basal. - - Note: if you have at least one hour of Carbs absorption detected during one day, then all data categorized as "UAM" will be categorized as basal, whatever this setting (On or Off) -- Number of days of data (default 5): You can define default value with this setting. Each time your select a new profile in Autotune plugin, Tune days parameter will be replaced by this default value -- Apply average result in circadian IC/ISF (default Off): see [Circadian IC or ISF profile](#circadian-ic-or-isf-profile) below. - -### Другие настройки - -- Autotune also uses Max autosens ratio and Min autotsens ratio to limit variation. You can see and adjust these values in Config Builder > Sensitivity detection plugin > Settings > Advanced Settings - - ![Autotune default screen](../images/Autotune/Autotune_12.png) - - - -## Advanced feature - -### Circadian IC or ISF profile - -- If you have important variation of IC and/or you ISF in your profile, and you fully trust in your circadian time and variation, then you can set "Apply average result in circadiant IC/ISF" - - - Note that Autotune calculation will always be done with a single value, and circadian variation will not be tuned by Autotune. This setting only apply average variation calculated for IC and/or ISF on your circadian values - -- See on screenshot below Tuned profile with Apply average variation Off (on the left) and On (on the right) - - ![Autotune default screen](../images/Autotune/Autotune_13.png) - - - -### Tune specific days of the week - -- If you click on the checkbox with the eye on the right of "Rune days" parameter, you will see the day selection. You can specify which day of the week should be included in Autotune calculation (in screenshot below you can see an example for "working days" with Saturday and Sunday removed from autotune calculation) - - If the number of day included in Autotune calculation is lower than the number of Tune days, then you will see how many days will be included on the right of Tune days selector (10 days in the example below) - - This setting gives good results only if the number of remaining days is not to small (for example if you Tune a specific profile for week end days with only Sunday and Saturday selected, you should select a minimum of 21 or 28 Tune days to have 6 or 8 days included in Autotune calculation) - -![Autotune default screen](../images/Autotune/Autotune_14b.png) - -- During Autotune calculation, you can see the progress of the calculations ("Partial result day 3 / 10 tuned" on example below) - - ![Autotune default screen](../images/Autotune/Autotune_15b.png) - -## Run Autotune with an automation rule - -First step is to define correct trigger for an automation rule with Autotune: - -Note: for more information on how to set an automation rule, see [here](./Automation.rst). - -- You should select Recurring time trigger: only run Autotune once per day, and autotune is designed to be runned daily (each new run you shift one day later and quickly profile modification should be tiny) - - ![Autotune default screen](../images/Autotune/Autotune_16.png) - -- It's better at the beginning to run Autotune during the day to be able to check results. If you want to run Autotune during the night, you have to select in the trigger 4AM or later to include current day in next Autotune Calculation. - - ![Autotune default screen](../images/Autotune/Autotune_17.png) - -- Then you can select "Run Autotune" Action in the list - - ![Autotune default screen](../images/Autotune/Autotune_18.png) - -- You can then select Autotune Action to adjust parameters for your run. Default parameters are "Active Profile", default Tune days value defined in Autotune Plugin preferences, and All days are selected. - - ![Autotune default screen](../images/Autotune/Autotune_19b.png) - -- After a few days, if you fully trust Autotune results and percentage of modification is low, you can modify [Autotune settings](#autotune-plugin-settings) "Automation Switch Profile" to enabled to automatically update and activate profile tuned after calculation. - -Note: if you want to automatically tune profiles for specific days of the week (for example a profile for "Weekend days" and another one for "Working days"), then create one rule for each profile, select the same days in Trigger and in Autotune Action, Tune days must be high enough to be sure tuning will be done with at least 6 or 8 days, and don't forget to select time after 4AM in trigger... - -- See below an example of rule to tune "my profile" on all "Working days" with 14 Tune days selected (so only 10 days included in autotune calculation). - -![Autotune default screen](../images/Autotune/Autotune_20b.png) - - - -## Tips and trick's - -Autotune works with information existing in your database, so if you just installed AAPS on a new phone, you will have to wait several days before being able to launch Autotune with enough days to get relevant results; - -Autotune is just an help, it's important to regularly check if you agree with calculated profile. If you have any doubt, change Autotune settings (for example the number of days) or copy results in local profile and adjust profile before using it. - -Always use Autotune several days manually to check results before applyling them. And it's only when you fully trust Autotune results, and when variation becomes tiny between previous profile and calculated profile than you start to use Automation (Never before) - -- Autotune can work very well for some users and not for others, so **If you don't trust Autotune result, don't use it** - -It's also important to analyse Autotune results to understand (or try to understand) why Autotune propose these modifications - -- you can have a whole increase or decrease of the strength of your profile (for example increase of total basal associated to decrease of ISF and IC values). it could be associated to several following days with autosens correction above 100% (more agressivity required) or below 100% (you are more sensitive) -- Sometimes Autotune propose a different balance between basal rates and IC/ISF (for ex lower basal and more aggressive IC/ISF) - -We advise to not use Autotune in the following cases: - -- You don't enter all your carbs - - If you don't enter carbs correction for an hypoglycemia, Autotune will see an unexcepted increase of your BG value and will increase your basal rates the ' hours earlier, it could be the opposite of what you need to avoid hypo, especially if it's in the middle of the night. That's why it's important to enter all carabs especially correction for hypo. -- You have a lot of period with UAM detected during the day. - - Do you have entered all your carbs and correctly estimated your Carbs ? - - All UAM periods (except if you enter no carbs during a day and categorized UAM as basal is disabled), all your UAM periods will be categorized as basal, this can increase a lot your basal (much more than necessary) - -- Your carbs absorption is very slow: if most of your carbs absorption are calculated with min_5m_carbimpact parameter (you can see these periods with a little orange dot in the top of COB curve), the calculation of COB could be wrong and leads to wrong results. - - We you practice sport, you are generally more sensitive and your BG doesn't rise a lot, so during or after an exercice, it's usual to see some periods with slow carbs. But if you have too often unexpected slow carb absorption, then you may need a profile adjustment (higher value of IC) or a min_5m_carbimpact a bit to high. -- You have a "very bad days", for example stuck several hours in hyperglycemia with a huge amount of insulin to be able to go down within the range, or after a sensor change you got long periods of wrong BG values. -- If the percentage of modification is too important - - You can try to increase the number of days to get smoother results \ No newline at end of file diff --git a/docs/CROWDIN/ru/Usage/making-sport-with-AAPS.md b/docs/CROWDIN/ru/Usage/making-sport-with-AAPS.md deleted file mode 100644 index 79d2f1c38223..000000000000 --- a/docs/CROWDIN/ru/Usage/making-sport-with-AAPS.md +++ /dev/null @@ -1,185 +0,0 @@ -# making sport with AAPS - -In this section we want to address the topic of sport with AAPS. - -The aim is to show you how AAPS can help you to continue doing your favorite sport more easily or even to start doing it. It is relatively common for new type 1 diabetics to ask whether exercise is still possible for them, even if the answer in the training courses is actually a clear yes. Exercise is not only good for healthy people, but also for type 1 diabetics and even moderate exercise can even help to stabilize the blood sugar curve overall. - -:::{admonition} consult with your diabetes team after reading - -::: - -The difficulty here is that the prerequisites that someone brings with them and the expectations of what sport means to them are very different. - -Since we can assume that experienced top athletes with T1D who use AAPS are unlikely to look it up here, we deliberately set the bar low for ourselves when writing and for you when reading and using it, so that as many people as possible can benefit from it. - -Since even sport as a category is far too imprecise, as the effects of endurance sports differ greatly from strength training, for example, we are trying to break it down by type of sport. - -To be concrete and give you something you can test yourself we arrange the explanaiton around a concrete example and explain to you they action, reactions and effects. - -:::{admonition} more examples wanted - -The focus should always be on how others can do sport and not on the top performance someone has achieved. - -It's really about the basics. Your experience, which you share here, can help others to pursue their beloved sport more quickly and successfully and is therefore important. -::: - -## Cycling - -:::{admonition} take a friend with you - at least on your first trials -:class: information -A gerneral very good idea can be to take a good friend with you on the first rides. -This is especially important if you are not experienced in T1D. -Always keep in mind please: arrival comes before speed! Safety for you and the others in road traffic is very, very important. -::: - -### Example - -Let's take about 60 minutes of cycling on a flat route with a moderate heart rate as an example. - -1. we take a flat route in order to have an even load for the first exercise. This is not about performance, but purely about learning how you should react to changes in blood glucose. -2. we take the heart rate as an indicator of the load, as it is easy to see whether you are under load or not. -3. we set ourselves the goal of doing a relaxed lap around the neighborhood and focus on staying within our target range during the lap. In my case, this would be 70 <= x <= 180 mg/dl. - -We **don't** take the speed, as this is heavily dependent on personal physical conditions as well as the bike and surface used. It is therefore not very meaningful. - -You should know from the diabetes training courses you have attended that during endurance sports cycling, the insulin active in the body works significantly better than during times without physical exertion. The insulin active in the body is referred to as insulin on board (IoB). It is our most important parameter when cycling with T1D. - -We try to keep the IoB as low as possible at the start and during exercise. IoB should be around 0 or even slightly negative. You can get it there by not eating 3-4 hours before exercise. In the beginning it can also be helpful to exercise in the morning before breakfast, as with the right profile you should always have around 0 for IoB in the morning. - -AAPS shows us the IoB value on the home screen on the left under the blood glucose value. - -![IoB](../images/cycling_20240104-174035.png) - -:::{admonition} ignoring the IoB rule increases the risk for roller coaster BG dramatically -:class: danger -If you ignore this rule, you can still go cycling, but it will be much more difficult to keep your blood sugar levels in balance, so it is better to save this for later tests after several successful simple tests. -::: - -As you should know from the diabetes training courses, you should reduce the basal rate during exercise. The factor is individual. I have found a value of 50% in tests to be suitable for me. - -In AAPS, you should therefore change your profile to 50% before exercise and keep it active until the end of exercise. Some people even do it a certain amount of time before, e.g. 1 hour. Unfortunately, the pre-run is also individual. We will come to the post-run later. - -You should use two carbohydrates during exercise. - -1. medium-fast carbohydrates for the insulin still in the body and -2. very fast carbohydrates to prevent slipping into a hypo. - -For medium-fast carbohydrates, I treat myself to cookies or a banana before exercise, for example. You can also use something else that is more suitable for you. -For very fast carbohydrates, I take 3 teaspoons of dissolved glucose per 100 ml of still water in a 500 ml water bottle on my bike. If I'm cycling longer distances, I take a larger bottle with me and, if necessary, packaged glucose to refill the bottle. I add a little lemon juice for flavor. You can also use something other than lemon juice for the taste. You shouldn't change anything about the dextrose, as dissolved dextrose raises blood sugar levels super quickly. If you only take it in sips, your blood sugar won't go super high either! You can also do this tip at home beforehand as a dry run and see how quickly the change shows up on the CGMS. - -Why do I place so much emphasis on fast carbohydrates? - -1. once you are in a slight hypo, you may get back into the normal range by drinking the dextrose solution. As a rule, however, the oscillation of the curve then begins, which leads to a rollercoaster ride of the blood sugar. You may even be able to keep this within your target range, but you must be constantly vigilant. Without a hypo it is simply the most stable. -2. if you even slip into a somewhat severe hypo (without the need for outside help, of course), you may even have to pause briefly to avoid getting stuck in the hypo. - With both hypos, there is a risk that you will be tempted to switch from drinking 2-3 sips at a time to larger quantities. Not too bad at first, until the oscillation sets in and pushes you into a hyper. You can correct this, but your blood sugar will most likely go on a rollercoaster ride. - -What else is helpful, but not absolutely necessary? -It is important to keep an eye on your blood sugar, as your blood sugar can change enormously (e.g. 30 - 50 mg/dl) within 15 minutes of riding and a little more IoB or a basal rate that is still too high. The best way to keep an eye on it is if it is visible on the handlebars or if it is also displayed on your watch. It is even possible to install an additional app on some Garmin GPS bike computers that displays the blood glucose from XDrip or Nightscout as a data field on the bike computer. The additional app was developed by Andreas May from the T1D community. It is available free of charge in the official connect IQ Store. Certainly an interesting option for riders interested in sports. - -[Link to Andreas May Data Field App on connect IQ store](https://apps.garmin.com/de-DE/apps/5a3e2cda-12f0-4afd-88ed-000e67a68d84) - -Here is a picture of my Garmin Edge 530 bike computer with map, blood sugar and heart rate. - -![Garmin Edge 530 with BG data field](../images/cycling_IMG_1087.jpeg) - -After you have eaten the medium fast carbohydrates (24 - 36 g I take) and the blood sugar is above 100 mg/dl but also below 160 mg/dl, I carry out the profile change to 50% and set the activity temp target. - -:::{admonition} disable SMBs during high temp targets if necessary -:class: danger -Attention: If you prefer not to receive SMBs during the sport, please disable the option "Enable SMB with hight temp targets" in the settings of SMB or DynIFS Plugin. -::: - -The following picture shows the start and end of the sport. The end was specified as the duration when the profile was changed at the start. - -The temporary profile change has the following effects - -1. for a period of 60 minutes -2. a reduction to 50% of the profile and -3. the target is raised by clicking on the Activity Target option, which may have the side effect of disabling the SMBs - see above. - -![profile switch with temp target](../images/cycling_20240104-174056.png) - -The second image shows that the start at IoB was started towards 0. - -![IoB around 0](../images/cycling_20240104-174111.png) - -If the blood sugar drops faster than 15 mg/dl in 5 minutes or if it is at 120 mg/dl and tends to fall, I drink 1-2 sips of dissolved glucose. Then I wait for the next value and proceed as described above. - -You can hardly see it here, but at the beginning I took 2 sips from the bottle several times when my blood sugar started to fall. When it stabilized, I didn't need any more glucose. - -Here is the picture that illustrates this. The chart is saved on the Garmin as a result of the activity. - -![BG chart Garmin](../images/cycling_20240104-174431.png) - -If you should suddenly break out upwards, i.e. above 180 mg/dl, you should consider whether you should make a correction bolus. Caution: Remember the factor and apply it to the correction, otherwise the correction will be too strong. - -If your blood sugar drops below 80 mg/dl, take a break and drink two sips until your blood sugar is back above 100 mg/dl. - -At the end of the ride, the profile change should be finished as the time is up. - -Since we only rode easy for 60 minutes, there shouldn't be a big muscle bulking effect continuing to pull carbohydrates from your blood sugar. However, if it felt strenuous to you, keep an eye on it. This is especially true if you then go straight to bed. It may be better to change your profile to e.g. 80% for sleep. You may come out of sleep slightly too high, but it's better than having a hypo at night. Over time, you will surely find out what happens to you. - -The following pictures show the low intensity of the sport. - -The elevation profile -![](../images/cycling_20240104-174314.png) - -Speed with average and maximum speed - -![](../images/cycling_20240104-174326.png) - -Note the pause at the level crossing, which is also reflected in the heart rate. - -The heart rate. -![](../images/cycling_20240104-174337.png) - -The training effect. -![](../images/cycling_20240104-174358.png) - -The time in the different heart rate training zones. -![](../images/cycling_20240104-174423.png) - -After succesfully mastering this simple example you could go for further targets by stretching - -1. the distance and time -2. the load during the ride -3. the elevation during the right which should make a big impact on the more necessary carbs or further reduction of IoB and percentage of profile switch. - -Based on my experiences I would not expect to come back 100% with time in range over the whole and every ride. - -### Tipps - -I already gave some tipps for during the ride above. - -Here are some further tipps what can go wrong and how you can act to prevent it or react to compensate it. - -#### sky rocket high after ride - -During the ride everything was fine but after siting down and relax the blood sugar go sky rocket high. - -**Possible reason:** This happens when you have drunk too much dissolved glucose. - -**Reaction:** Drink 500 ml water, go to the shower and then control again. Latest after 30 minutes think about giving a correction bolus but be careful when it is short for bed time. Therefore it can be very good to make the first try runs on weekend mornings. - -**Action:** Next time be a bit more cautious in drinking from the dissolved glucose. - -#### hypo during ride - -During the ride you are going into hypo and can't recover your blood sugar during cycling. - -**Possible reason:** Your body cannot absorb enough carbohydrates quickly enough during exercise. - -**Reaction:** Take a rest and corrrect your blood sugar with drinking dissolved glucose. Stay calm: arrival comes before speed. - -**Action:** Did you started with IoB near 0? Have you eaten a small amount of middle fast carbs? Can you increase this or are the not fast enough for your body? Is it possible to prevent going into hypo by reducing the factor for the profile switch? Have you disbaled SMBs during ride as explained above? - -#### sky rocket high during ride - -During the ride your blood sugar goes sky rocket high. - -**Possible reason:** You have got taken too much carbs for your IoB at that time. Beneath for sure the typical technical problems with your -insulin pump like leakage or blockage of the catheder! - -**Reaction:** If it is too high for you take a rest and correct with a bolus. Keep in mind that you must ride home and therefore make it carefully. Drink 500 ml pure water without carbs. Stay calm: arrival comes before speed. - -**Action:** Have you eaten too much? Especially have you drunk too much from the dissolved glucose during the ride? Is your percentage of reduction the profile during profile switch too low and you can increase this? diff --git a/docs/CROWDIN/ru/Where-To-Go-For-Help/How-to-get-support.md b/docs/CROWDIN/ru/Where-To-Go-For-Help/How-to-get-support.md deleted file mode 100644 index b58ecc8978b6..000000000000 --- a/docs/CROWDIN/ru/Where-To-Go-For-Help/How-to-get-support.md +++ /dev/null @@ -1,11 +0,0 @@ -# How to get support - -**Level 1:** Wiki - we now have a search function! - -**Level 2:** [Facebook](https://www.facebook.com/groups/AndroidAPSUsers/) OR [gitter](https://gitter.im/MilosKozak/AndroidAPS) - -**Level 3:** Gitter (if FB did not get results, wait at least a couple of hours (plural)!!! Direct crossposts will be ignored/deleted on both channels!!!) - -**Level 4:** Create an issue with logs and time of the issue - -**Level 5:** PM (only if personal data is involved that should not go in a public channel) \ No newline at end of file diff --git a/docs/CROWDIN/ru/buildingAAPS.md b/docs/CROWDIN/ru/buildingAAPS.md deleted file mode 100644 index 98164a09e49b..000000000000 --- a/docs/CROWDIN/ru/buildingAAPS.md +++ /dev/null @@ -1,28 +0,0 @@ -# Dummy - -## This is a dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - - -## This is another dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - - -## This is another another dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - diff --git a/docs/CROWDIN/ru/completingObjetives.md b/docs/CROWDIN/ru/completingObjetives.md deleted file mode 100644 index 98164a09e49b..000000000000 --- a/docs/CROWDIN/ru/completingObjetives.md +++ /dev/null @@ -1,28 +0,0 @@ -# Dummy - -## This is a dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - - -## This is another dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - - -## This is another another dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - diff --git a/docs/CROWDIN/ru/dummy.md b/docs/CROWDIN/ru/dummy.md deleted file mode 100644 index 98164a09e49b..000000000000 --- a/docs/CROWDIN/ru/dummy.md +++ /dev/null @@ -1,28 +0,0 @@ -# Dummy - -## This is a dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - - -## This is another dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - - -## This is another another dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - diff --git a/docs/CROWDIN/ru/intro.md b/docs/CROWDIN/ru/intro.md deleted file mode 100644 index 6df7353cf0d5..000000000000 --- a/docs/CROWDIN/ru/intro.md +++ /dev/null @@ -1,291 +0,0 @@ -![20-06-23v2 AAPS simple overview-cropped](https://github.com/openaps/AndroidAPSdocs/assets/94044064/e505b73b-09a0-42a4-a1ab-b830a0741234) - -# Introduction to APS and AAPS - -## What is an “Artificial Pancreas System”? - -A human pancreas does a lot of things besides regulating blood sugar. However, the term **“Artificial Pancreas System” (APS)** usually refers to a system which works to automatically keep blood sugar levels within healthy limits. - -The most basic way to do this is by detecting **glucose levels**, using these values to do **calculations**, and then delivering the (predicted) right amount of **insulin** to the body. It repeats the calculation, every few minutes, 24/7. It uses **alarms** and **alerts** to inform the user if intervention or attention is needed. This system is typically made up of a **glucose sensor**, an **insulin pump** and an **app** on a phone. - -You can read more about the different artificial pancreas systems currently in use and in development in this 2022 review article: - -![Frontiers](./images/FRONTIERS_Logo_Grey_RGB.png) [Future Directions in Closed-Loop Technology](https://www.frontiersin.org/articles/10.3389/fendo.2022.919942/full#:~:text=Fully%20closed%2Dloop%20systems%2C%20unlike,user%20input%20for%20mealtime%20boluses). - -In the near future, some so-called "dual-hormone" systems will also have the ability to infuse glucagon alongside insulin, with the aim of preventing severe hypos and allowing even tighter blood glucose control. - -An artificial pancreas can be thought of as an [“autopilot for your diabetes”]. (https://www.artificialpancreasbook.com/) What does that mean? In an aircraft, an autopilot does not do the complete job of the human pilot, the pilot cannot sleep through the entire flight. The autopilot aids the work of the pilot. It relieves them of the burden of permanently monitoring the aircraft, allowing the pilot to concentrate on wider monitoring from time to time. The autopilot receives signals from various sensors, a computer evaluates them together with the pilot’s specifications and then makes the necessary adjustments, alerting the pilot to any concerns. The pilot no longer has to worry about constantly making decisions. - -## What does hybrid closed loop mean? - -The best solution for type 1 diabetes would be a “functional cure” (probably an implant of pancreatic cells which are protected from the immune system). While we are waiting for that, a “full closed loop” artificial pancreas is probably the next best thing. This is a tech system that doesn’t need any user input (like bolusing insulin for meals, or announcing exercise), with good regulation of blood glucose levels. At the moment, there are no widely available systems which are “full” closed loop, they all need some user input. The currently available systems are called “hybrid” closed loop, because they use a combination of automated technology and user input. - -## How and why did looping start? - -The development of commercial technology for people with type 1 diabetes (T1D) is very slow. In 2013 the T1D community founded the #WeAreNotWaiting movement. They developed systems themselves using existing approved technology (insulin pumps and sensors) to improve blood glucose control, safety, and quality of life. These are known as DIY (do-it-yourself) systems, because they are not formally approved by health bodies (FDA, NHS etc). There are four main DIY systems available: OpenAPS, **AAPS**, Loop and iAPS. - -A great way to understand the fundamentals of DIY looping is to read Dana Lewis’s book “Automated Insulin Delivery”. You can access it \[here\] (https://www.artificialpancreasbook.com/) for free (or buy a hardcopy of the book). If you want to understand more about OpenAPS, which** AAPS** has developed from, the \[OpenAPS website\] (https://openaps.org/what-is-openaps/) is also a great resource. - -Several commercial hybrid closed loop systems have been launched, the most recent of which are \[CamAPS FX\] (https://camdiab.com/) (UK and EU) and \[Omnipod 5\] (https://www.omnipod.com/en-gb/what-is-omnipod/omnipod-5) (USA and EU). These are very different to DIY systems, mainly because they both include a “learning algorithm” which adjusts how much insulin is delivered according to your insulin needs from previous days. Many people in the DIY community have already tried out these commercial systems and compared them with their DIY system. You can find out more about how the different systems compare by asking on the dedicated Facebook groups for these systems, on the \[AAPS Facebook group\] (https://www.facebook.com/groups/AndroidAPSUsers/) or on \[Discord\] (https://discord.com/invite/4fQUWHZ4Mw). - -## What is Android APS (AAPS)? - -![image](https://github.com/openaps/AndroidAPSdocs/assets/94044064/0f089d96-b7ee-452a-aa9d-aae10ab58971) - -**Figure 1**. Basic outline of the Android APS (Artificial Pancreas System), AAPS. - -Android APS (AAPS) is a hybrid closed loop system, or Artificial Pancreas System (APS). It makes its insulin dosing calculations using established \[OpenAPS\] (https://openaps.org/) algorithms (a set of rules) developed by the #WeAreNotWaiting type 1 diabetes community. - -Since OpenAPS is only compatible with certain older insulin pumps, AAPS (which can be used with a wider range of insulin pumps) was developed in 2016 by Milos Kozak, for a family member with type 1 diabetes. Since those early days, **AAPS** has been continually developed and refined by a team of volunteer computer developers and other enthusiasts who have a connection to the type 1 diabetes world. Today, **AAPS** is used by approximately 10,000 people. It is a highly customisable and versatile system, and because it is open-source, it is also readily compatible with many other open-source diabetes softwares and platforms. The fundamental components of the current **AAPS** system are outlined in Figure 1 above. - -## What are the basic components of AAPS? - -The “brain” of AAPS is an **app** which you build yourself. There are detailed step-by-step instructions for this. You then install the **AAPS app** on a compatible **Android smartphone** (1). A number of users prefer their loop on a separate phone to their main phone. So, you don’t necessarily have to be using an Android phone for everything else in your life, just for running your AAPS loop. - -The **Android smartphone** will also need to have another app installed on it as well as **AAPS**, either a modified Dexcom app called build-your-own dexcom app (**BYODA**) or Xdrip+. This receives glucose data from a sensor (2) by bluetooth, and then sends the data internally on the phone to the **AAPS app**. - -The **AAPS app** uses a decision making process (**algorithm**) from OpenAPS. Beginners start out using the basic **oref0** algorithm, but it is possible to switch to using the newer **oref1** algorithm as you progress with AAPS. Which algorithm you use (oref0 or oref1), depends on which suits your specific situation best. In both cases, the algorithm takes into account multiple factors, and performs rapid calculations every time a new reading comes in from the sensor. The algorithm then sends instructions to the insulin pump (3) on how much insulin to deliver by bluetooth. All the information can be sent by mobile data or wifi to the internet. This data can also be shared with followers if desired, and/or collected for analysis. - -## What are the advantages of the AAPS system? - -The OpenAPS algorithm used by **AAPS** controls blood sugar levels in the absence of user input, according to the users’ defined parameters (important ones being basal rates, insulin sensitivity factors, insulin-to-carb ratios, duration of insulin activity etc.), reacting every 5 minutes to the new sensor data. Some of the reported advantages of using AAPS are extensive fine-tunable options, automations and increased transparency of the system for the patient/caregiver. This can result in better control over your (or your dependent’s) diabetes, which in turn may give improved quality of life and increased peace of mind. - -Practical advantages include: - -- **Hardware flexibility**: **AAPS** works with a wide range of insulin pumps and sensors. So for example, if you develop an allergy to Dexcom sensor patch glue, you could switch to using a Libre sensor instead. That offers flexibility as life changes. You don't have to rebuild, just tick a different box in the AAPS app to change your hardware. - -- **Highly customisable with wide parameters**: here are some examples of the possibilities with AAPS: a) The ability to set a lower glucose target 30 min before eating; you can set the target as low as 72 mg/dL (4.0 mmol/L). b) If you are insulin-resistant resulting in high blood sugars, **AAPS** allows you to set an **automation** rule to activate when BG rises above 8 mmol/L (144 mg/dL), switching to a 120% profile (resulting in an 20% increase in basal and strengthening of other factors too, compared to your normal **profile** setting). The automation will last according to the scheduled time you set. Such an automation could be set to only be active on certain days of the week, at certain times of day, and even at certain locations. c) If your child is on a trampoline with no advance notice, **AAPS** allows insulin suspension for a set time period, directly via the phone. d) After reconnecting a tubed pump which has been disconnected for swimming, AAPS will calculate the basal insulin you have missed while disconnected and deliver it carefully, according to your current BG. Any insulin not required can be overridden by just “cancelling” the missed basal. f) **AAPS** has the ability to set different profiles for different situations and easily switch between them. Features which make the algorithm quicker to bring down elevated BG (like supermicro boluses (“SMB”), unannounced meals, (“**UAM**”) can be set to only work during the daytime, if you are worried about night-time hypos. - - -These are all examples, the full range of features gives huge flexibility for daily life including sport, illness, hormone cycles etc. Ultimately, it is for the user to decide how to use this flexibility, and there is no one-size-fits-all automation for this. - -- **Remote monitoring**: there are multiple possible monitoring channels (Sugarmate, Dexcom Follow, Xdrip+, Android Auto etc.) which are useful for parents/carers and adults in certain scenarios (sleeping/driving) who need customisable alerts. In some apps (Xdrip+) you can also turn alarms off totally, which is great if you have a new sensor “soaking” or settling down that you don’t want to loop with yet. - -- **Remote control**: a significant advantage of **AAPS **over commercial systems is that it is possible for followers, using authenticated text (SMS) commands or via an app (Nightscout or NSClient) to send a wide range of commands back to the ****AAPS** **system. This is used extensively by parents of kids with type 1 diabetes who use AAPS. It is very useful in the playground, for example, if you want to pre-bolus for a snack from your own phone, and your child is busy playing. It is possible to monitor the system (e.g. Fitbit), send basic commands (e.g. Samsung Galaxy watch 4), or even run the entire AAPS system from a high-spec smartwatch (5) (e.g. LEMFO LEM14). In this last scenario, you don’t need to use a phone to run AAPS. As battery life on watches improves, this last option is likely to become increasingly attractive. - -- **No commercial constraints due to open application interfaces**: beyond the use of an open source approach, which allows the source code of **AAPS** to be viewed at any time, the general principle of providing open programming interfaces gives other developers the opportunity to contribute new ideas that allow users to live more easily with their diabetes. This is complementary to commercial systems which adopt the innovations from DIY, where interfaces are only made possible in return for licensing, thus preventing innovations in particular that are not-for-profit. Good examples for such integrations are NightScout, Nightscout Reporter, Xdrip+ M5 stack etc. - -- **Detailed app interface**: It is easy to keep track of things like: insulin levels, cannula age, sensor age, pump battery age, and many actions can be done through the **AAPS** app (priming the pump, disconnecting the pump etc.), instead of on the pump itself. - -- **Accessibility and affordability**: **AAPS** gives people who currently can’t afford to self-fund, or don’t have funding/insurance, access to a world-class hybrid closed looping system which is conceptually years ahead, in terms of development, of the commercial systems being offered by clinics. You currently need to have a Nightscout account to set up **AAPS**. Although the Nightscout account it not necessarily required after setup, many people continue to use Nightscout for collecting their data, and for remote control. So, although **AAPS **itself is free, setting up Nightscout through one of the various platforms may incur a fee (E0 - E12), depending on what level of support you want (see comparison table). **AAPS** works with a wide range of affordable (starting from approx E150) Android phones. In comparison, Loop currently costs around $80 a year for the Apple development licence and CamAPS FX costs around E80/month (as at 2023). - -- ****Support**: No automated insulin delivery system is perfect. Commercial and open-source systems share many common glitches in both communications and temporary hardware failure. There is a community of AAPS users on both Facebook and Discord and Github who designed, developed and are currently using **AAPS** all over the world. There are Facebook support groups and help from clinic/commercial companies for the commercial APS systems - it is worth speaking to the users, or former users of these systems to get feedback on the common glitches, the quality of the education programme and the level of ongoing support provided. - -- **Predictability, transparency and safety**: with no learning algorithm, **AAPS** is logical and in some respect, more predictable, which may make it easier to know when a setting is wrong, and to adjust it accordingly. You can see exactly what the system is doing, why it is doing it, and set its operational limits, which puts the control (and responsibility) in your hands. This can provide the user with confidence, and a sounder sleep. - -- **Access to advanced features through dev modes including full closed loop**: **AAPS **documentation focuses on the mainstream **“master”** branch of **AAPS**, however, research and development is going on all the time. More experienced users may wish to explore the experimental features in the **development** branch such as integration of Dexcom G7, and automatically adjusting insulin delivery according to short-term sensitivity changes (DYNISF), not having to bolus for meals, and generally trying to make life with type 1 diabetes as convenient as possible. - -- **Ability to contribute yourself to further improvements**: type 1 diabetes can be highly frustrating and isolating. Having control over your own diabetes tech, with the possibility to “pay it forward” as soon as you are making progress by helping others on their journey can be really rewarding. You can educate yourself, discover the roadblocks and look for and even contribute to new developments and the documentation. There will be others with the same quest to bounce ideas off and work with. This is the essence of #WeAreNotWaiting. - - -## How does AAPS compare to MDI and open looping? - -Multiple daily injections (MDI, a) usually involve giving an injection of a long-lasting insulin (e.g. Tresiba) once a day, with injections of faster-acting insulin (e.g. Novorapid, Fiasp) at mealtimes, or for corrections. Open pumping (b) involves using a pump to deliver basal at pre-programmed rates of rapid-acting insulin, and then boluses through the pump at mealtimes or for corrections. The basics of a looping system is that the App uses the glucose data to instruct the pump to stop insulin delivery when it predicts you are heading for a low, and to give you extra insulin if your glucose levels are rising and predicted to go too high (c). Although this is oversimplified, (mostly because hybrid closed looping has a lot of additional useful features) the key features of each system are shown in **Figure 2**. - -![image](https://github.com/openaps/AndroidAPSdocs/assets/94044064/4e7d8608-684d-4c69-9c61-88c9539f5d6f) - -**Figure 2**. Overview of (a) MDI, (b) open-loop pumping and (c) hybrid closed loop pumping - -## How does AAPS compare to other looping systems? - -At present there are four major open source closed loop systems available: OpenAPS, **AAPS**, \[Loop\] (https://loopkit.github.io/loopdocs/#what-is-loop) and iAPS, (formerly FreeAPS X). The features of the different systems are shown in the table below: - -| Devicestyp | Name | [Open APS](https://openaps.readthedocs.io/en/latest/) | [AAPS/ИПЖ](https://wiki.aaps.app) | [Замкнутый цикл](https://loopkit.github.io/loopdocs/) | [iAPS](https://iaps.readthedocs.io/en/latest/) | -| ----------------------------- | -------------------------------------------------------------------------------------------------------- | ----------------------------------------------------- | ------------------------------------------- | ----------------------------------------------------- | ---------------------------------------------- | -| PUMP | Older Medtronic | ![available](./images/available.png) | ![available](./images/available.png) | ![available](./images/available.png) | ![available](./images/available.png) | -| PUMP | Older Omnipod (Eros) | ![unavailable](./images/unavailable.png) | ![available](./images/available.png) | ![available](./images/available.png) | ![available](./images/available.png) | -| PUMP | Newer Omnipod (Dash) | ![unavailable](./images/unavailable.png) | ![available](./images/available.png) | ![available](./images/available.png) | ![available](./images/available.png) | -| PUMP | DANA R, DANA RS, DANA I | ![unavailable](./images/unavailable.png) | ![available](./images/available.png) | ![unavailable](./images/unavailable.png) | ![unavailable](./images/unavailable.png) | -| PUMP | Roche Combo, Insight | ![unavailable](./images/unavailable.png) | ![available](./images/available.png) | ![unavailable](./images/unavailable.png) | ![unavailable](./images/unavailable.png) | -| CGM/Непрерывный мониторинг ГК | Dexcom G4, G5, G6 | ![available](./images/available.png) | ![available](./images/available.png) | ![available](./images/available.png) | ![available](./images/available.png) | -| CGM/Непрерывный мониторинг ГК | Libre 1 (requires Miao Miao) | ![available](./images/available.png) | ![available](./images/available.png) | ![available](./images/available.png) | ![available](./images/available.png) | -| CGM/Непрерывный мониторинг ГК | Libre 2 | ![available](./images/available.png) | ![available](./images/available.png) | ![available](./images/available.png) | ![available](./images/available.png) | -| CGM/Непрерывный мониторинг ГК | Libre 3 | | ![unavailable](./images/unavailable.png) | --- | ![unavailable](./images/unavailable.png) | -| CGM/Непрерывный мониторинг ГК | Medtronic Enlite | | --- | ![unavailable](./images/unavailable.png) | --- | -| CGM/Непрерывный мониторинг ГК | [Dexcom G7](https://androidaps.readthedocs.io/en/latest/Hardware/DexcomG7.html) | | ![available](./images/available.png) (beta) | ![available](./images/available.png) | ![available](./images/available.png) | -| CGM/Непрерывный мониторинг ГК | [Eversense](https://androidaps.readthedocs.io/en/latest/Hardware/Eversense.html) | | ![available](./images/available.png) | | ![available](./images/available.png) | -| CGM/Непрерывный мониторинг ГК | [MM640g/MM630g](https://androidaps.readthedocs.io/en/latest/Hardware/MM640g.html) | | ![available](./images/available.png) | | ![available](./images/available.png) | -| CGM/Непрерывный мониторинг ГК | [PocTech](https://androidaps.readthedocs.io/en/latest/Hardware/PocTech.html) | | ![available](./images/available.png) | | ![available](./images/available.png) | -| CGM/Непрерывный мониторинг ГК | [Nightscout as BG Source](https://androidaps.readthedocs.io/en/latest/Hardware/CgmNightscoutUpload.html) | | ![available](./images/available.png) | | ![available](./images/available.png) | -| Phone | Android | ![available](./images/available.png) | ![available](./images/available.png) | ![unavailable](./images/unavailable.png) | ![unavailable](./images/unavailable.png) | -| Phone | iPhone | ![available](./images/available.png) | ![unavailable](./images/unavailable.png) | ![available](./images/available.png) | ![available](./images/available.png) | - -[OpenAPS](https://openaps.readthedocs.io/) was the first Open Source Closed Loop System. Она использует мини-компьютер, Raspberry Pi или Intel Edison. Both AndroidAPS (AAPS) and iAPS use the OpenAPS algorithms, whereas Loop uses a separate algorithm. You can read a comparison of iAPS and **AAPS** here. - -An international peer-reviewed consensus statement containing practical guidance on open source looping was written by and for health-care professionals, and published in a leading medical journal in 2022. It is well worth a read (including for your diabetes clinic) and summarises the main technical differences between the different open-source hybrid closed loop systems: - - Lancet Diabetes Endocrinol, 2022; 10: 58–74 - -[https://www.ncbi.nlm.nih.gov/pmc/articles/PMC8720075/](https://www.ncbi.nlm.nih.gov/pmc/articles/PMC8720075/) - -It is hard to get a “feel” for any system without using it, or talking to others who are using it, so do reach out to others on Facebook/Discord and ask. Most people find that AAPS is incredibly sophisticated in comparison to other hybrid closed loop systems (particularly the commercial systems), with a huge number of potentially customisable settings and features, discussed above. Some people can find this a little overwhelming in the beginning, but there is no rush to investigate all the possibilities at once, you can progress as slowly or as fast as you would like, and there is help available at every step of the way. - -## Does AAPS use artificial intelligence or any learning algorithm? - -Нет. **AAPS** does not have any complicated machine learning algorithms, multiple-parameter insulin response models, or differential equations. As such, the system is open and transparent in how it works, and has the ability to be understood not just by experts, but also by clinicians and patients. It also means that if you have a sharply varying schedule (maybe switching from a stressful week at work to a relaxing holiday) and are likely to need a significantly different amount of insulin, you can immediately switch **AAPS** to run a weaker/stronger profile. A ‘learning system’ will do this adjustment for you automatically, but is likely to take longer to adjust the insulin delivery. - -## Which system is right for me or my dependent? - -Practically, your choice of system is often restricted by which pump you already have, or can obtain from your medical provider, and your choice of phone (Apple or Android). If you don’t yet have a pump you have the biggest choice of systems. Technology is continually evolving, pumps are being discontinued and new pumps and sensors are being released. Most open-source systems work with the main sensors (Libre and Dexcom) or are quickly adapted to work with new sensors a year or so after they are released (with a bit of time delay for safety and stability testing). - -Most **AAPS **users report more time in range, HbA1c reductions, as well as quality of life improvements from having a system that can auto-adjust basal rates overnight during sleep, and this is true for most hybrid closed loop APS. Some people have a preference for a very simple system which is not very customisable (which means you may prefer a commercial system), and others find this lack of control very frustrating (you may prefer an open-source system). If you (or your dependent) are newly diagnosed, a common route is to get the hang of MDI plus sensor first, then progress to a pump which has the potential for looping, then to **AAPS**, but some people (especially small kids) may go straight to a pump. - -It is important to note that the **AAPS** user needs to be proactive to troubleshoot and fix problems themselves, with help from the community. This is a very different mindset to that when using a commercial system. With **AAPS** a user has more control, but also the responsibility, and needs to be comfortable with that. - -## Is it safe to use open-source systems like AAPS? - -A more accurate question is probably “is it safe compared to my current type 1 diabetes insulin delivery system?” since no method of insulin delivery is without risk. There are many checks and balances in place with **AAPS**. A recent paper looked at the use of**** AAPS ****in a computer simulated set-up, [https://www.liebertpub.com/doi/epub/10.1089/dia.2019.0375](https://www.liebertpub.com/doi/epub/10.1089/dia.2019.0375) which was an effective way to unobjectively trial how safe and effective the system is. More generally, it is estimated that over 10,000 individuals worldwide are using open-source automated-insulin delivery systems, and uptake continues to increase globally. - -Any device that uses radio communications could be hacked, and this is true for a non-looping insulin pump as well. Currently, we are not aware of anyone attempting to harm individuals by hacking their diabetes-related medical equipment. However, there are multiple ways to protect against such risks: - -1. In the pump settings, limit both the max bolus allowed and max temporary basal settings to amounts that you believe are safest. These are hard limits that we do not believe any malicious hacker could circumvent. - -2. Set your CGM alarms enabled for both highs and lows. - -3. Monitor your insulin delivery online. Nightscout users can set additional alarms to alert for a wide variety of conditions, including conditions that are much more likely to occur than a malicious attack. In addition to highs and lows, Nightscout can display diagnostic data useful for verifying that the pump is operating as desired, including current IOB, pump temporary basal history, pump bolus history. It can also be configured to proactively alert users to undesirable conditions, such as predicted highs and lows, low insulin reservoir, and low pump battery. - - -If a malicious attack was made on your insulin pump, these strategies would significantly mitigate the risk. Every potential **AAPS** user needs to weigh the risks associated with using **AAPS**, versus the risks of using a different system. - -## How can I approach discussing AAPS with my clinical team? - -Depending on the country - link to doctors section of docs - - Lancet Diabetes Endocrinol, 2022; 10: 58–74 - -[https://www.ncbi.nlm.nih.gov/pmc/articles/PMC8720075/](https://www.ncbi.nlm.nih.gov/pmc/articles/PMC8720075/) - -## Q: Why can’t I just download AAPS and use it straight away? - -The **AAPS** app is not provided in Google Play - you have to build it from source code by yourself for legal reasons. **AAPS** is unlicensed, meaning that it does not have approval by any regulatory body authority in any country. **AAPS**is deemed to be carrying out a medical experiment on yourself, and is carried out at the user’s own risk. - -Setting up the system requires patience, determination and the gradual development of technical knowledge. All the information and support can be found in these documents, elsewhere online, or from others who have already done it. It is estimated that over 2000 people have successfully built and are currently using **AAPS** worldwide. - -The developers of **AAPS**t ake safety incredibly seriously, and want others to have a good experience of using **AAPS**. That is why it is essential that every user (or carer, if the user is a child): - -- builds the AAPS system themself and works through the **objectives** so that they have reasonably good personalised settings and understand the basics of how AAPS ****works by the time they “close the loop”; - -- backs up their system by exporting and saving important files (like keystore and settings .json file) somewhere safe, so you can setup again quickly if needed; - -- updates to newer master versions as and when they become available; and - -- maintains and monitors the system to ensure it is working properly. - - -## Q: What is the connectivity of the AAPS system? - -**Figure 3 (below)** shows one example of the **AAPS** system for a user who do not require any followers interacting with the system: - -![potential AAPS connectivity setup with no followers](./images/intro03.png) - -**Figure 4 (below)** shows the full potential of the **AAPS** system for a user who has followers and requires a monitor and send adjust the system remotely (like a child with T1D): - -![potential AAPS connectivity setup with followers](./images/intro04.png) - -## Q: How does AAPS get continually developed and improved? - -Most **AAPS** users use the fully tested **master** version of AAPS, which has been tested for bugs and problems, before being released to the community. Behind the scenes, the developers try out new improvements, and test these out in “developer” (**dev**) versions of **AAPS** with a user community who are happy to do bug updates at short notice. If the improvements work well, they are then released as a new “master” version of **AAPS**. Any new master release is announced on the Facebook group, so that the mainstream **AAPS** users can read about and update to the new master version. - -Some experienced and confident **AAPS ** users conduct experiments with emerging technologies and with dev versions of the **AAPS** app, which can be interesting for the less adventurous users to read about, without having to do it themselves! People tend to share these experiments on the Facebook group too. - -You can read more about some of these experiments and discussion on emerging tech here: - -[https://www.diabettech.com/](https://www.diabettech.com/) - -[https://bionicwookie.com/](https://bionicwookie.com/) - -## Q: Who can benefit? - -| User Type | -| ------------------------------------------- | -| ✔️ type 1 diabetic | -| ✔️ caregiver or parent of a type 1 diabetic | -| ✔️ blind users type 1 diabetic | -| ✔️ *clincians and healthcare professionals | - -The above table assumes that the user has access to both continuous gluocse monitor and insulin pump. - -*All data from **AAPS** can be made available to healthcare professionals via data sharing platforms, including NightScout that provides logging and real time monitoring of CGM data, insulin delivery, carbohydrate entries, predictions and settings. Nightscout records include daily and weekly reports which can aid healthcare professionals' discussions with type 1 patients with more accurate data on glycemic control and any behavioural considerations. - -## Q: What benefits can I get? - -With investment of your time, **AAPS** can potentially lead to: - -- alleviating the stress and burden of managing type 1 diabetes; - -- reducing the multitude of mundane decisions that arise from type 1 diabetes; - -- the provision of personalised and dynamic insulin dosing based on real-time data which can cut down the need for hypo treatments and reduce hyperglycemia episodes; - -- an increased knowledge of insulin management and confidence to better fine tune your settings; - -- the ability to create automatic settings (**automations**) that are tailored to fit in with your lifestyle; - -- improved sleep quality and overall reduction in the frequency of nighttime interventions; - -- remote monitoring and administration of insulin delivery for caregivers of type 1 diabetics; and - -- streamlining of all your portable diabetic equipment (continuous glucose monitor and insulin portable devices) by replacing them with an android phone controlled by **AAPS**. - - -Ultimately,**AAPS** can empower individuals to better manage their diabetes resulting in stable blood sugars and improved long term health outcomes. - ---- - -## AAPS First Steps - -Welcome. This is an introduction to aid beginners getting started with **AAPS** (or commonly referred to as "looping"). - -## Safety - -“_With great powers comes great responsibilities…_” - -**AAPS** is designed with an extensive set of safety features with limits imposed and gradually removed with completion of the **objectives **(predominately made up of multiple choice questions). An **AAPS** feature will be unlocked as the Objectives are successfully completed. This process will gradually allow the user to migrate from Open Loop to Closed Loop. - -This has been done to achieve the best possible experience with **AAPS** in order to prevent common mistakes that new users tend to make when starting to loop. The safety parameters have been built upon typical errors and general trends **AAPS** developers have observed with new users. Mistakes can happen because the beginner is inexperienced and too eager to get started with AAPS or has overlooked the required materials. Do not worry, we have all been there! - -## Key Principles - -The key principles and concepts of looping must be understood by the user before using **AAPS**. This is achieved by investing your personal time into reading the **AAPS** documentation, and completing the Objectives which is aimed to provide you with a solid platform for safe and effective use of **AAPS**. The volume of **AAPS** documentation may seem overwhelming at first but be patient and trust the process - with the proper approach, you'll get there! The overall process will depend upon the beginner’s progress and completion of objectives can typically take between 6 to 9 weeks . - -## Plan for hiccups - -At the preliminary stages of **AAPS**, you should expect to experience some hiccups whilst trying to fine tune your settings. **AAPS**’ glitches cannot be flushed out until the system is used in everyday life. Please plan accordingly and allow a sensible amount of time to troubleshoot and resolve such issues. - -## Flexibility/Adaptability - -Success with **AAPS** requires a proactive approach, a willingness to reflect on the BG data and flexibility to make the necessary adjustments to **AAPS** in order to improve your outcomes. Just as it is nearly impossible to learn to play a sport by reading about the rules alone, the same can be said of **AAPS**. - -## Technology compatibility - -There are limitations with **AAPS** as it is accessible for only certain types of insulin pumps or CGMs, and some technology may not be available for use in various countries. In order to avoid any disappointment or frustrations, please read please read Component Set Up (Section INSERT). - -## App Build Time - -The time to build the **AAPS**(under Section INSERT) depends on your level of expertise and technical ability. Typically for inexperienced users, it can take up to half a day or a full day (with help from the community) in order to build the **AAPS**. The process will significantly speed up as you become more experienced at building the **AAPS**. To aid the build process there are sections dedicated for: -- list of questions and answers for frequent errors that are likely to occur under FAQs (Section K); -- “How to install AAPS? (Section INSERT) which includes Troubleshooting subsection. - -## Keystore & configurations settings a export file - -A “keystore” is a password encrypted file unique to your own copy of **AAPS**. Your android phone uses it to ensure that nobody else can upgrade your own copy without the keystore. In short, as part of the **AAPS** build, you should: - -- save the your keystore file (.jks file used to sign your app) in a safe place; -- keep a note of your password for your keystore file. - -By doing the above, this will ensure that you can use that exact same keystore file each time an updated version of **AAPS** is created. On average, there will be 2-3 AAPS updates required each year. - -In addition, **AAPS** provides the ability to export all your configuration settings. This ensures that you can safely recover your system while changing phones, upgrading/reinstalling the application with minimum disruption. - -## Troubleshootng - -Please feel free to reach out to the AAPS community if there is anything you feel unsure about - there is no such thing as a silly question! All users with various levels of experience are encouraged to ask questions as necessary. Response times to questions are usually quick, typically only a few hours due to the volume of **AAPS** users. - -a) check the documentation; b) ask AAPS facebook group (https://www.facebook.com/groups/AndroidAPSUsers); and c) ask our discord channel. - -## Section overview - -AAPS documentation is made up of the following Sections: - -[INSERT ONCE SECTIONS /SUB SECTIONS AGREED] ---- diff --git a/docs/CROWDIN/ru/maintaining.md b/docs/CROWDIN/ru/maintaining.md deleted file mode 100644 index 98164a09e49b..000000000000 --- a/docs/CROWDIN/ru/maintaining.md +++ /dev/null @@ -1,28 +0,0 @@ -# Dummy - -## This is a dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - - -## This is another dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - - -## This is another another dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - diff --git a/docs/CROWDIN/ru/optimizing.md b/docs/CROWDIN/ru/optimizing.md deleted file mode 100644 index 98164a09e49b..000000000000 --- a/docs/CROWDIN/ru/optimizing.md +++ /dev/null @@ -1,28 +0,0 @@ -# Dummy - -## This is a dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - - -## This is another dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - - -## This is another another dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - diff --git a/docs/CROWDIN/ru/prepairing.md b/docs/CROWDIN/ru/prepairing.md deleted file mode 100644 index cc3ab9fa4eac..000000000000 --- a/docs/CROWDIN/ru/prepairing.md +++ /dev/null @@ -1,145 +0,0 @@ -# Prepairing - -## Guide to the Android APS doc - -### First Steps -Welcome. This is an introduction to aid beginners to the concept of Do-It-Yourself-APS (Android-Artificial-Pancreas-Systems “AAPS”) is commonly referred to as ‘looping’.. - -#### Safetys -“With great powers come great responsibilities…” - -AAPS is designed with an extensive set of safety features with limits imposed and gradually removed with completion of the [Objectives](https://androidaps.readthedocs.io/en/latest/Usage/Objectives.html) (predominately made up of multiple choice questions). An AAPS feature will be unlocked as the Objectives are successfully completed. This process will gradually allow the user to migrate from Open Loop to Closed Loop. - -This has been done to achieve the best possible experience with AAPS by preventing common mistakes new users tend to make when starting to loop. The safety parameters have been built upon typical errors and general trends AAPS developers have observed with new users. Mistakes can happen because the beginner is inexperienced and too eager to get started with AAPS or has overlooked the required materials. Do not worry, we have all been there! - -#### Key Principles - -The key principles and concepts of looping must be understood by the user before using AAPS. This is achieved by investing your personal time into reading the AAPS documentation, and completing the [Objectives](https://androidaps.readthedocs.io/en/latest/Usage/Objectives.html) which is aimed to provide you with a solid platform for safe and effective use of AAPS. The volume of AAPS documentation may seem overwhelming at first but be patient and trust the process - with the proper approach, you'll get there! The overall process will depend upon the beginner’s progress and completion of objectives which typically take between 6 to 9 weeks . - -#### Plan for hiccups - -At the preliminary stages of AAPS, you should expect to experience some hiccups whilst trying to fine tune your settings. AAPS’ glitches cannot be flushed out until the system is used in everyday life. Please plan accordingly and allow a sensible amount of time to troubleshoot and resolve such issues. - -#### Flexibility/Adaptability - -Success with AAPS requires a proactive approach, a willingness to reflect on the BG data and flexibility to make the necessary adjustments to AAPS in order to improve your outcomes. Just as it is nearly impossible to learn to play a sport by reading about the rules alone, the same can be said of AAPS. - -#### Technology compatibility -There are limitations with AAPS as it is accessible for only certain types of insulin pumps or CGMs, and some technology may not be available for use in various countries. In order to avoid any disappointment or frustrations, please read [Component Set Up (Section E).](https://androidaps.readthedocs.io/en/latest/Configuration/BG-Source.html) - -#### App Build time -The time to build the AAPS (under Section D) depends on your level of expertise and technical ability. Typically for inexperienced users, it can take up to half a day or a full day (with help from the community) in order to build the AAPS. The process will significantly speed up as you become more experienced at building the AAPS.  - -To aid the build process there are sections dedicated for: - -- list of questions and answers for frequent errors that are likely to occur under [FAQs (Section](https://androidaps.readthedocs.io/en/latest/Getting-Started/FAQ.html) K); - -- “[How to install AAPS](https://androidaps.readthedocs.io/en/latest/Installing-AndroidAPS/Building-APK.html)? (Section D) which includes [Troubleshooting](https://androidaps.readthedocs.io/en/latest/Usage/troubleshooting.html) subsection. - - -#### Keystore & configuration settings export  file - -A “keystore” is a password encrypted file unique to your own copy of AAPS. Your android phone uses it to ensure that nobody else can upgrade your own copy without the keystore.In short, as part of the AAPS build, you should: - -1. save the your keystore file (.jks file used to sign your app) in a safe place; - -2. keep a note of your password for your keystore file. - - -By doing the above, this will ensure that you can use that exact same keystore file each time an updated version of AAPS is created. On average, there will be 2-3 updates to the AAPS required each year. In addition, AAPS provides the ability to [export all your configuration settings](https://androidaps.readthedocs.io/en/latest/Usage/ExportImportSettings.html). This ensures that you can safely recover your system while changing phones, upgrading/reinstalling the application with minimum disruption.  - -#### Troubleshooting - -Please feel free to reach out to the AAPS community if there is anything you feel unsure about - there is no such thing as a silly question!  All users with various levels of experience are encouraged to ask questions as necessary. Response times to questions are usually quick, typically only a few hours due to the volume of AAPS users.  - -##### [check the documentation](https://androidaps.readthedocs.io/en/latest/index.html) - -##### [ask our facebook group](https://www.facebook.com/groups/AndroidAPSUsers/) - -##### [ask our discord channel](https://discord.com/channels/629952586895851530/629954570394533889) - -#### Section overview - -AAPS documentation is made up of the following Sections: - -##### [Getting started](https://androidaps.readthedocs.io/en/latest/Getting-Started/Safety-first.html) - -This is a must read to understand the general concept of what an artificial pancreas system is designed to do. - -##### [What do I need?](https://androidaps.readthedocs.io/en/latest/Module/module.html) - -This explains AAPS’ compatibility with CGMs (Continuous Glucose Monitors) and insulin pumps. It also provides a guide on the correct assembly of an AAPS system to ensure that it functions correctly in everyday life. - -##### How to install AAPS - -This section is the manual for building the AAPS. Strict adherence to the step-by-step instructions are required in order to successfully build the AAPS. Please take your time. - -##### [Component Setup](https://androidaps.readthedocs.io/en/latest/Configuration/BG-Source.html) - -This explains how to properly integrate each of the various different separate component parts into AAPS, as well as how to set them up to work as seamlessly as possible together. All components are listed under the separate sections: CGM/FGM, xDrip Settings, Pumps, Phones, Nightscout setup, and Smartwatches. The sensor (BG) values and control of the insulin pump are particularly important information to understand. - -##### Configuration - -This explains how to set and configure your ‘Profile’, ‘Insulin’, ‘BG Source’, ‘Pump’, ‘Sensitivity Detection’, ‘APS’, ‘Loop’, ‘Treatments’. - -##### AAPS Usage - -This section provides a breakdown of the features provided by AAPS. - -##### [General Hints](https://androidaps.readthedocs.io/en/latest/Usage/Timezone-traveling.html) - -Useful tricks on how to tackle looping issues such as time zones, and daylight saving (i.e. Spring Forward/ - Fall Back). - -##### [AAPS](https://androidaps.readthedocs.io/en/latest/Getting-Started/Screenshots.html) for Children - -This is designed for parents or caregivers who want to build an AAPS for their child. It also explains the extra features necessary in order to support and safely control your child’s AAPS remotely.

The concepts in this section should be fully understood in order to competently use this feature. - -##### Troubleshooting - -This section contains links to help solve issues when building or using AAPS. - -##### FAQ - -This section addresses specific questions which tend to come up when building or using AAPS. - -##### [Глоссарий](https://androidaps.readthedocs.io/en/latest/Getting-Started/Glossary.html) - -This contains a list of the acronyms (or short-term names) or defined terms developed specifically for AAP (for instance, the terms ‘ISF’ or ‘TT’ have special meanings in AAPS). - -##### [Where to go for help](https://androidaps.readthedocs.io/en/latest/Where-To-Go-For-Help/Background-reading.html)? - -This section is aimed to provide new users with links on resources in order to get help including accessing community support made up of both new and experienced users who can clarify questions, and resolve the usual pitfalls that come with AAPS. - -##### For Clinicians - -This is a section for the clinicians who have expressed interest in open source artificial pancreas technology such as AAPS, or for patients who want to share such information with their clinicians. | - -## what are we going to build? - -### An Android Phone Application - -At the core, AAPS is an android application running from a phone. You are going to build it from scratch by installing tools to download the sourcecode and build the actual application. - -### A reporting server NightScout (or Tidepool) - -In order to fully use AAPS properly you will want to setup a nightscout server. It is used to collect data from AAPS over time and possibly communicate to the application. It is required for parents who want to oversee their children AAPS sessions. It is also key to share data between clinicians and patients to perform analysis over time. - -## How long will it take? - -## Who might AAPS not be suitable for? - -## Where can I get help? - -## Requirements - -### medical - -### technical - -### personal - -### CGMs - -### Insulin Pump - -### Reporting (NS, Tidepool) \ No newline at end of file diff --git a/docs/CROWDIN/sk/Children/SMS-commands2019.md b/docs/CROWDIN/sk/Children/SMS-commands2019.md deleted file mode 100644 index 68e341f65f7e..000000000000 --- a/docs/CROWDIN/sk/Children/SMS-commands2019.md +++ /dev/null @@ -1,105 +0,0 @@ -# SMS Commands - -## Safety First - -- AndroidAPS allows you to control a child's phone remotely via text message. If you enable this SMS Communicator, always remember that the phone set up to give remote commands could be stolen. So always protect it at least by a PIN code. -- AndroidAPS will also inform you by text message if your remote commands, such as a bolus or a profile change, have been carried out. It is advisable to set this up so that confirmation texts are sent to at least two different phone numbers in case one of the receiving phones is stolen. -- **If you bolus through SMS Commands you must enter carbs through Nightscout (NSClient, Website...)!** If you fail to do so IOB would be correct with too low COB potentially leading to not performed correction bolus as AAPS assumes that you have too much active insulin. - -## How it works - -- Most of the adjustments of temp targets, following AAPS etc. can be done on [NSclient app](../Children/Children.md) on an Android phone with an internet connection. - -- Boluses can't be given through Nightscout, but you can use SMS commands. - -- If you use an iPhone as a follower and therefore cannot use NSclient, there are additional SMS commands available. - -- In your android phone setting go to Applications > AndroidAPS > Permissions and enable SMS - -- In AndroidAPS go to Preferences > SMS Communicator and enter the phone number(s) that you will allow SMS commands to come from (separated by semicolons, no spaces or other characters anywhere - i.e. +4412345678;+4412345679) and also enable 'Allow remote commands via SMS'. - - ![SMS Commands Setup](../images/SMSCommandsSetup.png) - -- Send a SMS to the phone with AndroidAPS running from your approved phone number(s) using any of the commands below in **CAPITAL LETTERS**, the phone will respond to confirm success of command or status requested. Confirm command by sending the code provided in SMS from AndroidAPS phone where neccessary. - -**Hint**: It can be useful to have SMS flat for both phones if a lot of SMS will be sent. - -## Commands - -Commands must be send in English, response will be in your local language if the response string is already [translated](../translations#translate-strings-for-androidaps-app). - -![SMS Commands Example](../images/SMSCommands.png) - -### Loop - -- LOOP STOP/DISABLE - : - Response: Loop has been disabled -- LOOP START/ENABLE - : - Response: Loop has been enabled -- LOOP STATUS - : - Response depends on actual status - : - Loop is disabled - - Loop is enabled - - Suspended (10 min) -- LOOP SUSPEND 20 - : - Response: Loop suspended for 20 minutes -- LOOP RESUME - : - Response: Loop resumed - -### CGM data - -- BG - : - Response: Last BG: 5.6 4min ago, Delta: -0,2 mmol, IOB: 0.20U (Bolus: 0.10U Basal: 0.10U) -- CAL 5.6 - : - Response: To send calibration 5.6 reply with code Rrt - - Response after correct code was received: Calibration sent (**If xDrip is installed. Accepting calibrations must be enabled in xDrip+**) - -### Basal - -- BASAL STOP/CANCEL - : - Response: To stop temp basal reply with code EmF \[Note: Code EmF is just an example\] -- BASAL 0.3 - : - Response: To start basal 0.3U/h for 30 min reply with code Swe -- BASAL 0.3 20 - : - Response: To start basal 0.3U/h for 20 min reply with code Swe -- BASAL 30% - : - Response: To start basal 30% for 30 min reply with code Swe -- BASAL 30% 50 - : - Response: To start basal 30% for 50 min reply with code Swe - -### Bolus - -- BOLUS 1.2 - : - Response depends time last bolus was given - : - To deliver bolus 1.2U reply with code Rrt - - Remote bolus not available. Try again later. (**Remote bolus not allowed within 15 min after last bolus command or remote commands!**) -- EXTENDED STOP/CANCEL - : - Response: To stop extended bolus reply with code EmF -- EXTENDED 2 120 - : - Response: To start extended bolus 2U for 120 min reply with code EmF - -### Profile - -- PROFILE STATUS - : - Response: Profile1 -- PROFILE LIST - : - Response: 1.\`Profile1\` 2.\`Profile2\` -- PROFILE 1 - : - Response: To switch profile to Profile1 100% reply with code Any -- PROFILE 2 30 - : - Response: To switch profile to Profile2 30% reply with code Any - -### Other - -- TREATMENTS REFRESH - : - Response: Refresh treatments from NS -- NSCLIENT RESTART - : - Response: NSCLIENT RESTART 1 receivers -- PUMP - : - Response: Last conn: 1 minago Temp: 0.00U/h @11:38 5/30min IOB: 0.5U Reserv: 34U Batt: 100 - -## Troubleshooting - -There was a report on SMS commands stopping after an update on Galaxy S10 phone. Could be solved by disabeling 'send as chat message'. - -![Disable SMS as chat message](../images/SMSdisableChat.png) diff --git a/docs/CROWDIN/sk/Configuration/Dexcom.md b/docs/CROWDIN/sk/Configuration/Dexcom.md deleted file mode 100644 index cb267e23c069..000000000000 --- a/docs/CROWDIN/sk/Configuration/Dexcom.md +++ /dev/null @@ -1,32 +0,0 @@ -# Dexcom G6 - -## Basics first - -* Follow [general CGM hygiene recommendations](../Configuration/BG-Source#cgm-hygiene) -* [Special recommendations for Dexcom G6 and DIY systems](../Configuration/BG-Source#dexcom-g6-diy-systems) *For G6 transmitters manufactured after fall/end of 2018 please make sure to use one of the [latest nightly built xDrip+ versions](https://github.com/NightscoutFoundation/xDrip/releases). Those transmitters have a new firmware and latest stable version of xDrip+ (2019/01/10) cannot deal with it. - -## Setting sensor - -When setting sensor, it is recommended not to press the inserter too firmly in order to avoid bleeding. The sensor thread should not come into contact with blood. - -After setting the sensor, the transmitter can be clicked into the sensor holder. Caution! First click in the square side and then press down the round side. - -## Troubleshooting - -### Connection problems - -Bluetooth connection may be disturbed by other nearby Bluetooth devices such as blood glucose meters, headsets, tablets or kitchen devices such as microwave ovens or ceramic hobs. In this case xdrip does not display any BG values. When bluetooth connection is reestablished the data is backfilled. - -### Sensor Errors - -If recurring sensor errors occur try selecting a different body site to set your sensor. The sensor thread should not come into contact with blood. - -Often a "Sensor Error" can be corrected by immediate drinking and massage around the sensor! - -### Jumpy values - -You might try to change settings for noise blocking in xdrip (Settings - Inter-App Settings - Noise Blocking) i.e. "Block Very High noise and worse". See also [Smoothing BG data](../Usage/Smoothing-Blood-Glucose-Data-in-xDrip.md). - -### New transmitter with running sensor - -If you happen to change transmitter during a running sensor session you might try to remove the transmitter without damaging the sensor mount. A video can be found at . \ No newline at end of file diff --git a/docs/CROWDIN/sk/Configuration/EOFLOW.md b/docs/CROWDIN/sk/Configuration/EOFLOW.md deleted file mode 100644 index e697feadb732..000000000000 --- a/docs/CROWDIN/sk/Configuration/EOFLOW.md +++ /dev/null @@ -1,155 +0,0 @@ -# EOPatch2 Instruction Manual - -The patch requires the use of rapid-acting U-100 type insulin, such as NovoRapid or Humalog. Use a rapid-acting insulin that is suitable for you according to your doctor’s prescription and inject the prescribed dosage. - -The smallest injectable dose of insulin when using the patch is 0.05 U. The Profile BAS should therefore be set at a minimum value of 0.05 U/hr or more and an interval of 0.05 U/hr, as otherwise there may be an error between the estimated total infusion amount in the Profile and the actual infusion amount in the patch. Likewise, the bolus must also be set and infused with a minimum infusion volume of 0.05 U. - -## Pump Setup -1. On the AndroidAPS home screen, click the hamburger menu in the upper left corner and go to Config Builder. -1. Select 'EOPatch2' in the Pump section. -1. Press the Back key to return to the home screen. - -![Bild1](../../images/EOPatch/Bild1.png) ![Bild2](../../images/EOPatch/Bild2.png) - -## Settings -Select EOPATCH2 at the top of the home screen to go to the EOPATCH2 tab. - -Select the EOPatch2 Preferences menu by clicking the three dots in the upper right corner. - -The EOPatch2 Preferences menu offers a menu to set 3 types of notifications. - -### Low reservoir Alerts -A warning appears when the amount of insulin remaining in the reservoir reaches the set value or less while using the patch. It can be set from 10 to 50U in 5U increments. - -### Patch expiration Reminder -This is a reminder to notify you of the time remaining before the current patch expires. It can be set from 1 to 24 hours in 1 hour increments. The initial setting value is 4 hours. - -### Patch buzzer Reminder -This is a reminder function for injections other than basal injection. If you are using an (extended) bolus injection or a temporary basal injection, the patch will make a buzzer sound when the injection starts and when the injection is complete. The initial setting value is Off. - -![Bild3](../../images/EOPatch/Bild3.png) - -## Connecting the Patch - -### Move to patch connection screen - -Select EOPATCH2 at the top of the home screen and click the ACTIVATE PATCH button at the bottom left. - -![Bild4](../../images/EOPatch/Bild4.png) - -### Connecting the patch -Insert the syringe needle into the insulin inlet on the patch and then slowly push the piston to inject the insulin. When insulin is filled with more than 80U, the patch makes a booting sound (1 buzzer) and boots. After confirming the buzzer sound, click the START PAIRING button on the screen. - -[Warning] - -- Do not turn the needle action lever until instructed. It can cause serious problems during injection or safety checks otherwise. -- The amount of insulin that can be injected into the patch is 80~200U. If you inject less than 80U into the patch initially, the patch will not work. -- Take the insulin to be put into the patch from the refrigerator and leave it at room temperature for 15 to 30 minutes beforehand. The temperature of the insulin to be injected must be at least 10°C. - -![Bild5](../../images/EOPatch/Bild5.png) - -### patch pairing -The Patch pairing screen will be displayed, and pairing will be attempted automatically. If communication is successful, the Bluetooth pairing request notification appears. Click OK and when the Bluetooth pairing request notification appears a second time with the authentication code, select OK again. - -[Warning] - -- For pairing, the patch and the smartphone must be located within 30 cm of each other. -- After the patch booting is completed, the patch will beep every 3 minutes until the pairing is complete. -- After booting the patch, the patch application must be completed via the app within 60 minutes. If the application cannot be completed within 60 minutes, the patch should be discarded. - -![Bild6](../../images/EOPatch/Bild6.png) ![Bild7](../../images/EOPatch/Bild7.png) ![Bild8](../../images/EOPatch/Bild8.png) - - -### patch preparation -After removing the adhesive tape of the patch, check if the needle is sticking out. If there are no problems with the patch, click NEXT. - -![Bild9](../../images/EOPatch/Bild9.png) - -### Patch attachment -Insulin should be injected in a spot with subcutaneous fat but few nerves or blood vessels, so it is recommended to use the abdomen, arm, or thigh for the patch attachment site. Choose a patch attachment site and apply the patch after disinfecting the location. - -[Warning] - -- Make sure to straighten the side of the patch tape attached to the body evenly, so that the patch adheres completely to the skin. -- If the patch does not stick completely, air may enter between the patch and the skin, which can weaken the adhesive strength and waterproof effect of the patch. - -![Bild10](../../images/EOPatch/Bild10.png) - -### Safety Check -When patching is complete, touch Start Safety Check. When the safety check is completed, the patch will beep once. - -[Warning] - -- For safe use, do not turn the needle action lever until the safety check has been completed. - -![Bild11](../../images/EOPatch/Bild11.png) ![Bild12](../../images/EOPatch/Bild12.png) - - -### Inserting the needle -The needle is inserted by holding around the patch and turning the needle action lever more than 100° in the upward direction of the lever. There is a buzzer sound when the needle is inserted correctly. Turn the needle action lever further clockwise to release the lever. Click NEXT. - -[Caution] - -- If you go to the next step without the buzzer sounding, a needle insertion error warning will appear. - -## Discarding the patch -Patches must be replaced in the case of low insulin levels, usage expiration, and defects. The recommended usage period for each patch is 84 hours after booting the patch. - -### Discarding the patch -Select EOPATCH2 at the top of the home screen and click the DISCARD/CHANGE PATCH button at the bottom. On the next screen, click the DISCARD PATCH button. A dialog box appears to confirm once more and if you select the DISCARD PATCH button, the disposal is completed. - -![Bild13](../../images/EOPatch/Bild13.png) ![Bild14](../../images/EOPatch/Bild14.png) ![Bild15](../../images/EOPatch/Bild15.png) ![Bild16](../../images/EOPatch/Bild16.png) - -## Suspending and Resuming Insulin Delivery -Suspending insulin delivery also cancels both extended bolus and temporary basal. When resuming insulin delivery, the canceled extended bolus and temporary basal will not be resumed. And when insulin delivery is suspended, the patch will give a sound every 15 minutes. - -### Suspending insulin delivery -Select EOPATCH2 at the top of the home screen and click the SUSPEND button at the bottom right. When you select CONFIRM in the confirmation box, a time selection box appears. If you select the CONFIRM button after selecting the time, the insulin delivery will be suspended for the set amount of time. - -![Bild17](../../images/EOPatch/Bild17.png) ![Bild18](../../images/EOPatch/Bild18.png) ![Bild19](../../images/EOPatch/Bild19.png) - - -### Resuming insulin delivery -Select EOPATCH2 at the top of the home screen and click the RESUME button at the bottom right. Insulin delivery will resume by selecting CONFIRM in the confirmation dialog box. - -![Bild20](../../images/EOPatch/Bild20.png) ![Bild21](../../images/EOPatch/Bild21.png) - -## Alarms/Warnings - -### Alarm - -Alarms are issued for emergency situations of the highest priority and require immediate action. The alarm signal does not disappear or time out until it is acknowledged. An alarm occurs when there is a problem with the patch being used, so there may be cases where the patch in use needs to be discarded and replaced with a new patch. The warning is displayed as a dialog box and switching to another screen is not possible until processing is completed. - -![Bild22](../../images/EOPatch/Bild22.png) ![Bild23](../../images/EOPatch/Bild23.png) - -The different types of alarms are explained below. - -| Alarms | Explanation | -| -------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| Empty reservoir | Occurs when the patch’s reservoir runs out of insulin. | -| Patch expired | Occurs when the patch usage time has expired, and no further insulin injections are possible. | -| Occlusion | Occurs when it appears that the patch's insulin inlet is clogged. | -| Power on self-test failure | Occurs when the patch finds an unexpected error during the post-boot self-test process. | -| Inappropriate temperature | Occurs when the patch is outside the normal operating temperature range during patch application and use. To deal with this alarm, move the patch to an appropriate operating temperature (4.4 to 37°C) condition. | -| Needle insertion Error | Occurs when needle insertion is not normal during the patch application process. Check that the needle insertion edge of the patch and the needle activation button are in a straight line. | -| Patch battery Error | Occurs just before the patch’s internal battery runs out and powers off. | -| Patch activation Error | Occurs when the app fails to complete the patching process within 60 minutes after the patch is booted. | -| Patch Error | Occurs when the patch encounters an unexpected error while applying and using the patch. | - -### Warning - -A warning occurs in a medium or low-priority situation. When a warning occurs, it is displayed as a notification in the Overview screen. - -![Bild24](../../images/EOPatch/Bild24.png) - -The different types of warnings are explained below. - -| Warnings | Explanation | -| ---------------------------- | ------------------------------------------------------------------------------------------------------------------------------------- | -| End of insulin suspend | Occurs when the time set by the user has elapsed after the insulin infusion suspension has been completed. | -| Low reservoir | Occurs when the remaining amount of insulin in the patch is below the set amount. | -| Patch operating life expired | Occurs when the patch usage period is over. | -| Patch will expire soon | Occurs 1 hour before the patch must be discarded. | -| Incomplete Patch activation | Occurs when more than 3 minutes have elapsed due to an interruption during patch application in the stage after pairing is completed. | -| Patch battery low | Occurs when the patch's battery is low. | - diff --git a/docs/CROWDIN/sk/Configuration/Hardware/index.md b/docs/CROWDIN/sk/Configuration/Hardware/index.md deleted file mode 100644 index 9215e2770d45..000000000000 --- a/docs/CROWDIN/sk/Configuration/Hardware/index.md +++ /dev/null @@ -1,27 +0,0 @@ -# Hardware-Configuration - -## Configuration - -## BG Source - -- [BG Source](../BG-Source.md) -- [xDrip+ Settings](../xDrip.md) -- [Dexcom G6 hints](../Dexcom.md) -- [Smoothing blood glucose data](../../Usage/Smoothing-Blood-Glucose-Data-in-xDrip.md) - -## Pumps - -- [Dana-R pump](../DanaR-Insulin-Pump.md) -- [Dana-RS pump](../DanaRS-Insulin-Pump.md) -- [Accu-Chek Combo pump](../Accu-Chek-Combo-Pump.md) -- [Accu-Chek Insight pump](../Accu-Chek-Insight-Pump.md) -- [Medtronic pump](../MedtronicPump.md) - -## Phones - -- [Jelly Pro Settings](../../Usage/jelly.md) -- [Huawei Settings](../../Usage/huawei.md) - -## Smartwatch - -- [Watchfaces](../Watchfaces.md) diff --git a/docs/CROWDIN/sk/Getting-Started/ClosedLoop.md b/docs/CROWDIN/sk/Getting-Started/ClosedLoop.md deleted file mode 100644 index 5f89d6080ce5..000000000000 --- a/docs/CROWDIN/sk/Getting-Started/ClosedLoop.md +++ /dev/null @@ -1,55 +0,0 @@ -# Čo je to Uzavretý Okruh? - -![AAPS je ako autopilot](../images/autopilot.png) - -Uzavretý okruh využíva rôzne komponenty aby pre vás bol manažment diabetu jednoduchší. In her great book [Automated Insulin Delivery](https://www.artificialpancreasbook.com/) Dana M. Lewis, one of the founders of the open source closed loop movement, calls it an ["autopilot for your diabetes"](https://www.artificialpancreasbook.com/3.-getting-started-with-your-aps). Ale čo to vlastne znamená? - -**Autopilot in an aircraft** - -Autopilot nespraví všetku prácu namiesto pilota a neumožňuje mu prespať celý let. Výrazne ale jeho prácu uľahčuje. Zmierňuje jeho záťaž, spôsobenú neustálou potrebou monitorovať funkcie lietadla a letovú hladinu. To umožňuje pilotovi sústrediť sa na monitorovanie vzdušného priestoru a kontrolu funkcií autopilota. - -Autopilot prijíma signály z rôznych senzorov, počítač ich vyhodnotí spolu so špecifikáciami pilota, a potom vykoná potrebné úpravy. Pilot sa už nemusí starať o neustále úpravy. - -**Closed Loop System** - -To isté platí aj pre uzavretý okruh. Nespraví za vás všetku prácu. Stále sa ešte budete musieť o svoj diabetes starať. Uzavretý okruh skombinuje údaje zo senzorov CGM/FGM s vašimi nastaveniami, ako bazálne dávky, citlivosť na inzulín a inzulínovo-sacharidový pomer. Na základe toho vypočítava návrhy ako upraviť dávky. Tieto drobné zmeny vykonáva neustále, aby udržal vaše glykémie v požadovanom rozmedzí. Vďaka tomuto si môžete užívať viac času "mimo diabetes". - -Rovnako, ako sa nechcete nachádzať v lietadle, ktoré riadi iba autopilot bez ľudskej posádky, tak aj uzavretý okruh vám síce uľahčí manažment diabetu, ale stále potrebuje vašu pomoc a dohľad! **Even with a closed loop you can't just forget your diabetes!** - -Rovnako ako sa autopilot spolieha na údaje zo senzorov a na špecifikácie od pilota, tak aj uzavretý okruh potrebuje určité informácie ako bazálne dávky, senzitivitu na inzulín a inzulínovo-sacharidový pomer aby mohol správne pracovať. - -## Open Source Systémy Uzavretého Okruhu - -V súčasnosti existujú tri hlavné open source systémy uzavretého okruhu: - -### AndroidAPS (AAPS) - -AAPS is described in detail in [this documentation](./WhatisAndroidAPS.html). Pre výpočty a ovládanie inzulínovej pumpy používa telefón so systémom Android. It is in strong collaboration with OpenAPS (i.e. they share algorithms). - -Compatible [pumps](../Hardware/pumps.md) are: - -- [DanaR](../Configuration/DanaR-Insulin-Pump.md) / [DanaRS & Dana-i](../Configuration/DanaRS-Insulin-Pump.html) -- [Accu-Chek Combo](../Configuration/Accu-Chek-Combo-Pump.md) -- [Accu-Chek Insight](../Configuration/Accu-Chek-Insight-Pump.md) -- [Diaconn G8](../Configuration/DiaconnG8.md) -- [Omnipod DASH](../Configuration/OmnipodDASH.md) -- [Omnipod Eros](../Configuration/OmnipodEros.md) -- some old [Medtronic pumps](../Configuration/MedtronicPump.md) - -### OpenAPS - -[OpenAPS](https://openaps.readthedocs.io) was the first Open Source Closed Loop System. Používa malý počítač ako Raspberry Pi alebo Intel Edison. - -Kompatibilné pumpy sú: - -- some old Medtronic pumps - -### Loop pre iOS - -[Loop for iOS](https://loopkit.github.io/loopdocs/) is the Open Source Closed Loop System to be used with Apple iPhones. - -Kompatibilné pumpy sú: - -- Omnipod DASH -- Omnipod Eros -- some old Medtronic pumps diff --git a/docs/CROWDIN/sk/Getting-Started/GlossaryTest.md b/docs/CROWDIN/sk/Getting-Started/GlossaryTest.md deleted file mode 100644 index d7e37bb7df0c..000000000000 --- a/docs/CROWDIN/sk/Getting-Started/GlossaryTest.md +++ /dev/null @@ -1,391 +0,0 @@ -# Glossary - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
TermDescriptionsee alsomore details @
AAPSAndroidAPS - artifical pancreas system  
AMAadvanced meal assist - advanced algorithm to handle carbsMA / SMBWiki - AMA
Android autodisplay AAPS notifications on your car's compatible in-dash information and entertainment head unit Wiki - android auto
APKsoftware installation file (Android application package) Wiki - Building APK
Autosenscalculation of sensitivity to insulin as a result of exercise, hormones etc. DIABETTECH - Autosens
Azurecloud computing platform to host Nightscout dataHeroku / NightscoutAzure
BATstatus light low battery on homescreenCAN / RES / SENPreferences
Screenshots
BGblood glucose  
BGIblood glucose interaction -degree to which BG 'should' be rising or falling based on insulin activity alone  
BG sourceWhere do your glucose values come from?CGM / FGMWiki - BG source
Blukon Nightreaderbluetooth transmitter to use Freestyle Libre as CGMBlueReader / MiaoMiaoAmbrosia Blukon Nightreader
BRbasal rate  
CAGEcanula age - displayed in Nightscout if information was entered in actions tab / menu tab or through AAPS actions tab 'prime'Nightscout 
CANstatus light overdue canula change on homescreenBAT / RES / SENPreferences
Screenshots
CGMcontinuous glucose monitor  
Closed Loopclosed-loop systems make automatic adjustments to basal delivery, without needing user-approval, based on an algorithmOpen loopWiki closed loop
COBcarbs on board  
DIAduration of insulin action Wiki insulin types
DIABETTECH - DIA
DSTdaylight savings time Wiki DST
eCarbs"extended carbs" - carbs split up over serveral hours (i.e. lot of fat/protein)
extended boluses you might know from regular pump therapy do not make much sense when looping		SMBWiki - eCarbs
eCarbs use case
FGMflash glucose monitor (Freestyle Libre) Wiki - BG source
gitversion-control system for tracking changes in computer files and coordinating work on those files
-> neccessary for APK updates		 Wiki - update APK
Githubweb-based hosting service for version control using Git
-> storage of source code		 Github AndroidAPS
Glimpapp to collect values from Freestyle Libre Nightscout with Glimp
Herokucloud computing platform to host Nightscout dataAzure / NightscoutHeroku
IC (or I:C)insulin to carb ratio (How many carbs are covered by one unit of insulin?)  
IOBinsulin on board - insulin active in your body  
ISFinsulin sensitivity factor - the expected decrease in BG as a result of one unit of insulin  
LGSLow Glucose Suspend
AAPS will reduce basal if blood glucose is dropping. But if blood glucose is rising then it will only increase basal if the IOB is negative (from a previous LGS), otherwise basal rates will remain the same as your selected profile. You may temporarily experience spikes following treated hypos without the ability to increase basal on the rebound.		objective 6 
LineageOSfree and open-source operating system for smartphones etc.
alternative OS for smartphones not running Android 8.1 (Oreo)
(when using Accu-Chek Combo)		 Wiki - Combo pump
Log filesrecord of all AAPS actions (useful for trubbleshooting and debugging) Wiki - log files
maxIOBsafety feature - maximum total IOB AAPS can't go over Wiki - maxIOB
Wiki - SMB
MiaoMiaobluetooth transmitter to use Freestyle Libre as CGMBlueReader / Blukon NightreaderMiaoMiao
min_5m_carbimpactsaftey feature - default carb decay at times when carb absorption can’t be dynamically worked out based on your bloods reactions Wiki - config builder
Nightscoutopen source project to access and report CGM dataNightscout ReporterNightscout
NS Clientpart of AAPS to connect to your Nightscout site Wiki - NS Client
Nightscout ReporterTool from fellow looper to generate PDFs reports from Nightscout dataNightscoutNightscout Reporter
NS Reporter @ Facebook
Objectiveslearning program within AAPS guiding you step by step from open to closed loop Wiki - objectives
OpenAPSopen artificial pancreas system
APS run on small computers (i.e. Raspberry Pie)
AAPS uses some of the OpenAPS features		 OpenAPS docs
Open Loopsystem will suggest recommended adjustments which have to be performed manually on the pumpClosed LoopWiki - config builder
Oref0 / Oref1sensitivity detection
"reference design implementation version 0/1" - the key algorithm behind OpenAPS		 Wiki - sensitivity detection
Peak timetime of maximum effect of insulin given Wiki - config builder
PHpump history (entry in treatments tab) Screenshots
Predictionspreditions for BG in the future based on different calculations Wiki - predition lines
Profilebasic treatment settings (basal rate, DIA, IC, ISF, BG target)
can be defined locally or through Nightscout		NightscoutWiki - profile
Profile switch(temporary) change of profile used or percentual increase/decrease Wiki - profile switch
RESstatus light overdue reservoir change on homescreenBAT / CAN / SENPreferences
Screenshots
RileyLinkopen source hardware device to bridge Bluetooth Low Energy (BLE) to 916MHz wireless communication (used for old Medtronic pumps)OpenAPS 
SAGEsensor age - displayed in Nightscout if information was entered in the actions tab / menuNightscout 
SENstatus light sensor change on homescreenBAT / CAN / RESPreferences
Screenshots
Sensivity detectioncalculation of sensitivity to insulin as a result of exercise, hormones etc. DIABETTECH - Autosens
Sensor noiseunstable CGM readings leading to "jumping" values Wiki - sensor noise
SMBsuper micro bolus
advanced feature for faster BG adjustment		UAMWiki - SMB
Super bolusshift of basal to bolus insulin for faster BG adjustment John Walsh - The Super Bolus
TBBtotal base basal (sum of basal rate within 24 hours)  
TBRtemporary basal rate  
TDDtotal daily dose (bolus + basal per day)  
TTtemporary target
temporary increase/decrease of BG target (range)		 Wiki - temp targets
UAMunannounced meals - detection of significant increase in glucose levels due to meals, adrenaline or other influences and attempt to adjust this with SMBSMBWiki - SMB
Virtual pumpoption to try AAPS functions or for PWD using a pump model with no AndroidAPS driver for loopingOpen Loop 
WallpaperAndroidAPS background imagesee phones page
xDrip / xDrip+open source software to read CGM systems xDrip+
xDrip
Zero-temptemporary basal rate with 0% (no basal insulin delivery)  
See also https://openaps.readthedocs.io/en/latest/docs/Resources/glossary.html
diff --git a/docs/CROWDIN/sk/Getting-Started/Safety-first.md b/docs/CROWDIN/sk/Getting-Started/Safety-first.md deleted file mode 100644 index 30d380261ead..000000000000 --- a/docs/CROWDIN/sk/Getting-Started/Safety-first.md +++ /dev/null @@ -1,41 +0,0 @@ -# Safety first - -**When you decide to build your own artificial pancreas, it's always important to think about security and safety, and to understand the impact of all your actions** - -## General - -- AAPS is a just a tool to help you manage diabetes, it is not a fully automated system you can install and forget! -- Do not assume that AAPS will never make mistakes. This device is taking control of your insulin delivery: Watch it all the time, understand how it works, and learn how to interpret its actions. -- Remember that, once paired, the phone can instruct the pump to do anything. Only use this phone for AAPS and, if being used by a child, essential communications. Do not install unnecessary apps or games (!!!) which could introduce malware such as trojans, viruses, or bots that could interfere with your system. -- Install all security updates provided by your phone manufacturer and Google. -- You might also need to change your diabetes habits as you change your therapy by using a closed loop system. I.e. some people report, they need less hypo treatments as AAPS has already reduced insulin. - -## SMS Communicator - -- AAPS allows you to control a child's phone remotely via text message. If you enable this SMS Communicator, always remember that the phone set up to give remote commands could be stolen. So always protect it at least by a PIN code. -- AAPS will also inform you by text message if your remote commands, such as a bolus or a profile change, have been carried out. It is advisable to set this up so that confirmation texts are sent to at least two different phone numbers in case one of the receiving phones is stolen. - -(Safety-first-aaps-can-also-be-used-by-blind-people)= -## AAPS can also be used by blind people - -On Android devices TalkBack is part of the operating system. It is a program for screen orientation via voice output. With TalkBack you can operate your smartphone as well as AAPS blind. - -We users create the AAPS app ourselves with Android Studio. Many use Microsoft Windows for this purpose, where there is the Screenreader analogous to TalkBack. Since Android Studio is a Java application, the "Java Access Bridge" component must be enabled in the Control Panel. Otherwise, the screen reader of the PC will not speak in Android Studio. - -To do this, please proceed as follows: - -- Press WINDOWSTASTE and enter "Control Panel" in the search field, open with Enter. It opens: "All Control Panel Items". -- Press the letter C to get to "Center for Ease of Use", open with Enter. -- Then open "Use computer without a screen" with Enter. -- There, at the bottom, you will find the checkbox "Enable Java Access Bridge", select it. -- Done, just close the window! The screen reader should work now. - -```{note} -**IMPORTANT SAFETY NOTICE** - -The foundation of AAPS safety features discussed in this documentation is built on the safety features of the hardware used to build your system. It is critically important that you only use a tested, fully functioning FDA or CE approved insulin pump and CGM for closing an automated insulin dosing loop. Hardware or software modifications to these components can cause unexpected insulin dosing, causing significant risk to the user. If you find or get offered broken, modified or self-made insulin pumps or CGM receivers, *do not use* these for creating an AAPS system. - -Additionally, it is equally important to only use original supplies such as inserters, cannulas and insulin containers approved by the manufacturer for use with your pump or CGM. Using untested or modified supplies can cause CGM inaccuracy and insulin dosing errors. Insulin is highly dangerous when misdosed - please do not play with your life by hacking with your supplies. - -Last not least, you must not take SGLT-2 inhibitors (gliflozins) as they incalculably lower blood sugar levels. The combination with a system that lowers basal rates in order to increase BG is especially dangerous as due to the gliflozin this rise in BG might not happen and a dangerous state of lack of insulin can happen. -``` diff --git a/docs/CROWDIN/sk/Getting-Started/Sample-Setup.md b/docs/CROWDIN/sk/Getting-Started/Sample-Setup.md deleted file mode 100644 index 2da9e4bf5a38..000000000000 --- a/docs/CROWDIN/sk/Getting-Started/Sample-Setup.md +++ /dev/null @@ -1,151 +0,0 @@ -# Sample setup: Samsung S7, Dana RS, Dexcom G6 and Sony Smartwatch - -![Sample Setup](../images/SampleSetup.png) - -## Description - -In this setup, the Samsung Galaxy S7 smartphone is used as control center of the loop. The slightly modified Dexcom App reads glucose values from the Dexcom G6 CGM. AndroidAPS is used to control the Dana RS insulin pump from Korean manufacturer SOOIL via bluetooth. Further devices are not required. - -As the Dexcom App only offers limited alarm options the open source app xDrip+ is used to define not only high and low alarms but also additional alarms according to individual requirements. - -Optionally an Android wear smartwatch can be used (in this sample setup the Sony Smartwatch 3 (SWR50)) to display glucose and AndroidAPS values on your wrist. The watch can even be used to control AndroidAPS (i.e. discreetly set a meal bolus). - -The system works offline. This means there is no need for a data connection from the smartphone to the Internet for operation. - -Nevertheless, the data is automatically uploaded to Nightscout "in the cloud" when a data connection is established. By doing so you can provide comprehensive reports for the doctor's visit or share the current values with family members at any time. It is also possible to send data to Nightscout only when using a (predefined) Wi-Fi connection in order to profit from the different Nightscout reports. - -## Required components - -1. Samsung Galaxy S7 - - * Alternatives: see [list of tested phones and watches](https://docs.google.com/spreadsheets/d/1gZAsN6f0gv6tkgy9EBsYl0BQNhna0RDqA9QGycAqCQc/edit) for AndroidAPS - -2. [DanaRS](http://www.sooil.com/eng/product/) - - * Alternatives: - * [Accu-Chek Combo](../Configuration/Accu-Chek-Combo-Pump.md) - * [Accu-Chek Insight](../Configuration/Accu-Chek-Insight-Pump.md) - * [DanaR](../Configuration/DanaR-Insulin-Pump.md) - * [Some old Medtronic pumps (additionally needed: RileyLink/Gnarl hardware, Android Phone with bluetooth low energy / BLE-chipset)](../Configuration/MedtronicPump.md) - * Other pumps might be available in the future, see [future possible pump drivers](Future-possible-Pump-Drivers.md) for details. - -3. [Dexcom G6](https://dexcom.com) - - * Alternatives: see list of possible [BG sources](../Configuration/BG-Source.md) - -4. Optional: Sony Smartwatch 3 (SWR50) - - * Alternatives: All [watches with Google Wear OS](https://wearos.google.com/intl/de_de/#find-your-watch) should work fine, for details see [list of tested phones and watches](https://docs.google.com/spreadsheets/d/1gZAsN6f0gv6tkgy9EBsYl0BQNhna0RDqA9QGycAqCQc/edit) for AndroidAPS (OS must be Android Wear) - -## Nightscout setup - -See detailed [Nightscout setup](../Installing-AndroidAPS/Nightscout.md) - -## Computer setup - -To be able to create an Android app from the freely available AAPS open source code you need Android Studio on your computer or notebook (Windows, Mac, Linux). A detailed instruction can be found at [building the APK](../Installing-AndroidAPS/Building-APK.md). - -Please be patient when installing Android Studio as the software downloads a lot of additional data once installed on your computer. - -## Smartphone setup - -![Smartphone](../images/SampleSetupSmartphone.png) - -### Check smartphone firmware - -* Menu > Settings > Phone info > Software info: At least "Android-Version 8.0" (successfully tested up to Android version 8.0.0 Oreo - Samsung Experience Version 9.0) -* For firmware update: menu > Preferences > software update - -### Allow installation from unknown sources - -Menu > Settings > Device security > Unknown sources > slider to right side (= active) - -For security reasons this setting should be set back to inactive once the installation of all apps described here has been completed. - -### Enable Bluetooth - -1. Menu > Settings > Connections > Bluetooth > slider to right side (= active) -2. Menu > Settings > Connections > Location > slider to right side (= active) - -Location services ("GPS") must be activated in order for Bluetooth to work properly. - -### Install Dexcom App (modified version) - -![Dexcom App patched](../images/SampleSetupDexApp.png) - -The original Dexcom app from the Google Play Store will not work because it does not broadcast the values to other apps. Therefore, a version slightly modified by the community is required. Only this modified Dexcom app can communicate with AAPS. Additionally the modified Dexcom App can be used with all Android smartphones not only the ones in [Dexcom's compatibility list](https://www.dexcom.com/dexcom-international-compatibility). - -To do this perform the following steps on your smartphone: - -1. If the original Dexcom app is already installed: - * Stop sensor - * Uninstall app via Menu > Settings > Apps > Dexcom G6 Mobile > Uninstall -2. Download and install the [BYODA Dexcom ap](../Hardware/DexcomG6.md#if-using-g6-with-build-your-own-dexcom-app) -3. Start modified Dexcom G6 app, activate/calibrate the sensor according to the given instructions and wait until the warm-up phase is finished. -4. Once the modified Dexcom app shows actual glucose value, setup the warnings (hamburger menu on top left side of the screen) as follows: - * Urgent low `55mg/dl` / `3.1mmol/l` (cannot be disabled) - * Low `OFF` - * High `OFF` - * Rise rate `OFF` - * Fall rate `OFF` - * Signal loss `OFF` - -## Install AndroidAPS - -1. Follow the instructions to [build the APK](../Installing-AndroidAPS/Building-APK.md#generate-signed-apk) -2. [Transfer](../Installing-AndroidAPS/Building-APK.md#transfer-apk-to-smartphone) the generated APK to your phone -3. [Configure AndroidAPS](../Configuration/Config-Builder.md) according to your needs using the setup assistant or manually -4. In this sample setup we used (among others) - -* BG source: `Dexcom G6 App (patched)` -- click cock-wheel and activate `Upload BG data to NS` and `Send BG data to xDrip+` (see [BG source](../Configuration/BG-Source.md)) - -![G5 Settings](../images/SampleSetupG5Settings.png) - -* NS Client activated (see [Nightscout setup](../Installing-AndroidAPS/Nightscout.md)) - -## Install xDrip+ - -xDrip+ is another mature open source app that offers countless possibilities. In this setup, contrary to what the developers first wrote the app for, xDrip+ is not used to collect glucose data from the Dexcom G6, but only to output alarms and to display the current glucose value including the curve on the Android home screen in the widget. With xDrip+ the alarms can be set much more individually than with the Dexcom software, AAPS or Nightscout (no limitation in the selection of sounds, different alarms depending on day/night time etc.). - -1. Download the latest stable APK version of xDrip+ with your smartphone - not the version from the Google Play Store! -2. Install xDrip+ by selecting the downloaded APK file. -3. Start xDrip+ and make the following settings (hamburger menu at top left) - * Settings > Alarms and Alerts > Glucose Level Alert List > Create Alerts (high and low) according to your needs. - * The existing alarms can be changed with a long press on the alarm. - * Settings > Alarms and Alerts > Calibration Alerts: disabled (reminded via the modified Dexcom app) - * Settings > Hardware Data Source > 640G/EverSense - * Settings > Inter-app settings > Accept Calibrations > `ON` - * Menu > Start sensor (is only "pro forma" and has nothing to do with the running G6 sensor. This is necessary otherwise an error message will appear regularly.) - -For more information about xDrip+, see here [BG source page](../Configuration/BG-Source.md). - -### Example of an alarm setup - -The "Urgent low alarm" (below 55 mg/dl resp. 3,1 mmol) is a standard alarm from the modified Dexcom app that cannot be disabled. - -![xDrip alarms](../images/SampleSetupxDripWarning.png) - -Tip for meetings / church visits / cinema etc..: - -If "Do not disturb" mode is activated in the Samsung Galaxy S7 (Menu > Settings > Sounds and vibration > Do not disturb: slider to right side (= active)), the phone only vibrates during urgent low alarm and does not issue an acoustic warning. For the other alarms set up via xDrip+ you can select whether the silent mode should be ignored (acoustic sound played) or not. - -## Disable power saving option - -On your Samsung Galaxy S7 go to Menu > Settings > Device Maintenance > Battery > Unmonitored Apps > + Add apps: Select the apps AndroidAPS, Dexcom G6 Mobile, xDrip+ and Android Wear (if smartwatch is used) one after the other - -## Optional: Setup Sony Smartwatch 3 (SWR50) - -With an Android Wear smartwatch life with diabetes can be made even more inconspicuous. The watch can be used to display the current glucose level, the status of the loop etc. on the wrist. The watch can even be used to control AndroidAPS (i.e. discreetly set a meal bolus). To do this, double tap the CGM value of the AAPSv2 watchface. The SWR50 usually runs for a full day until the battery needs to be recharged (same charger as the Samsung Galaxy S7: microUSB). - -![Smartwatch](../images/SampleSetupSmartwatch.png) - -Details about the information displayed on the watchface can be found [here](../Configuration/Watchfaces.md). - -* Install the app "Android Wear" on your smartphone via the Google Play Store and connect the smartwatch according to the instructions there. -* In AAPS choose hamburger menu (top left corner) > Config Builder > General (at the bottom of the list) > Wear > activate on left side, click cock wheel > Wear settings and activate `Controls from Watch` -* On your smartwatch: Long press display to change watchface and select `AAPSv2` -* If necessary restart both devices once. - -## Pump setup - -see [Dana RS pump](../Configuration/DanaRS-Insulin-Pump.md) \ No newline at end of file diff --git a/docs/CROWDIN/sk/Getting-Started/WhatisAndroidAPS.md b/docs/CROWDIN/sk/Getting-Started/WhatisAndroidAPS.md deleted file mode 100644 index b10d73731578..000000000000 --- a/docs/CROWDIN/sk/Getting-Started/WhatisAndroidAPS.md +++ /dev/null @@ -1,39 +0,0 @@ -# What is a closed loop system with AAPS? - -AAPS is an app that acts as an artificial pancreas system (APS) on an Android smartphone. What is an artificial pancreas system? It is a software program that aims to do what a living pancreas does: keep blood sugar levels within healthy limits automatically. - -An APS can't do the job as well as a biological pancreas does, but it can make type 1 diabetes easier to manage using devices that are commercially available and software that is simple and safe. Those devices include a continuous glucose monitor (CGM) to tell AAPS about your blood sugar levels and an insulin pump which AAPS controls to deliver appropriate doses of insulin. The app communicates with those devices via bluetooth. It makes its dosing calculations using an algorithm, or set of rules, developed for another artificial pancreas system, called OpenAPS, which has thousands of users and has accumulated millions of hours of use. - -A note of caution: AAPS is not regulated by any medical authority in any country. Using AAPS is essentially carrying out a medical experiment on yourself. Setting up the system requires determination and technical knowledge. If you don't have the technical know-how at the beginning, you will by the end. All the information you need can be found in these documents, elsewhere online, or from others who have already done it -- you can ask them in Facebook groups or other forums. Many people have successfully built AAPS and are now using it entirely safely, but it is essential that every user: - -- Builds the system themselves so that they thoroughly understand how it works -- Adjusts its individual dosage algorithm with his or her diabetes team to work nearly perfect -- Maintains and monitors the system to ensure it is working properly - -```{note} -**Disclaimer and Warning** - -- All information, thought, and code described here is intended for informational and educational purposes only. Nightscout currently makes no attempt at HIPAA privacy compliance. Use Nightscout and AAPS at your own risk, and do not use the information or code to make medical decisions. -- Use of code from github.com is without warranty or formal support of any kind. Please review this repository's LICENSE for details. -- All product and company names, trademarks, servicemarks, registered trademarks, and registered servicemarks are the property of their respective holders. Their use is for information purposes and does not imply any affiliation with or endorsement by them. - -Please note - this project has no association with and is not endorsed by: [SOOIL](http://www.sooil.com/eng/), [Dexcom](https://www.dexcom.com/), [Accu-Chek, Roche Diabetes Care](https://www.accu-chek.com/), [Insulet](https://www.insulet.com/) or [Medtronic](https://www.medtronic.com/). -``` - -If you're ready for the challenge, please read on. - -## Primary goals behind AAPS - -- An app with safety built in. To read about the safety features of the algorithms, known as oref0 and oref1, click here () -- An all-in-one app for managing type 1 diabetes with an artificial pancreas and Nightscout -- An app to which users can easily add or remove modules as needed -- An app with different versions for specific locations and languages. -- An app which can be used in open- and closed-loop mode -- An app that is totally transparent: users can input parameters, see results, and make the final decision -- An app which is independent of particular pump drivers and contains a "virtual pump" so users can safely experiment before using it on themselves -- An app closely integrated with Nightscout -- An app in which the user is in control of safety constraints - -## How to start - -Of course, all of this content here is very important, but can be in the beginning quite confusing. A good orientation is given by the [Module Overview](../Module/module.md) and the [Objectives](../Usage/Objectives.html). diff --git a/docs/CROWDIN/sk/Hardware/DexcomG4.md b/docs/CROWDIN/sk/Hardware/DexcomG4.md deleted file mode 100644 index 3ac2b2b96f4b..000000000000 --- a/docs/CROWDIN/sk/Hardware/DexcomG4.md +++ /dev/null @@ -1,6 +0,0 @@ -# Dexcom G4 - -## If using G4 with OTG cable ('traditional' Nightscout) -- If not already set up then download Nightscout Uploader app from the Play Store and follow instructions on [Nightscout](https://nightscout.github.io/). -- In AAPS Preferences enter your Nightscout website and API secret. -- Select NSClient in ConfigBuilder (setting in AAPS). diff --git a/docs/CROWDIN/sk/Hardware/Smartwatch.md b/docs/CROWDIN/sk/Hardware/Smartwatch.md deleted file mode 100644 index 12281d6d256a..000000000000 --- a/docs/CROWDIN/sk/Hardware/Smartwatch.md +++ /dev/null @@ -1,10 +0,0 @@ -# Smartwatches - -Smartwatches are optional, but very useful for some users. More details are here: - -- [List of tested phones and smartwatches](../Getting-Started/Phones.md) -- [Watchfaces Wear OS](../Configuration/Watchfaces.md) -- [Troubleshooting Sony Smartwatch SW 3](../Usage/SonySW3.md) - -## Instructions for Building the AAPS Wear APK for Wear OS -https://androidaps.readthedocs.io/en/latest/remote-control.html#building-the-aaps-wear-apk diff --git a/docs/CROWDIN/sk/Installing-AndroidAPS/Building-APK.md b/docs/CROWDIN/sk/Installing-AndroidAPS/Building-APK.md deleted file mode 100644 index 8d964f4b41fc..000000000000 --- a/docs/CROWDIN/sk/Installing-AndroidAPS/Building-APK.md +++ /dev/null @@ -1,369 +0,0 @@ -# Building the APK - -## Build yourself instead of download - -**AAPS is not available as download due to regulation for medical devices. It is legal to build the app for your own use, but you must not give a copy to others! See [FAQ page](../Getting-Started/FAQ.md) for details.** - -## Important notes - -* Please use **[Android Studio Giraffe" (2022.3.1)](https://developer.android.com/studio/)** or newer to build the apk. -* [Windows 32-bit systems](troubleshooting_androidstudio-unable-to-start-daemon-process) are not supported by Android Studio - -(Building-APK-recommended-specification-of-computer-for-building-apk-file)= - -## Recommended specification of computer for building apk file - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
OS (Only 64 bit)Windows 8 or higherMac OS 10.14 or higherAny Linux supports Gnome, KDE, or Unity DE;  GNU C Library 2.31 or later

CPU (Only 64 bit)

x86_64 CPU architecture; 2nd generation Intel Core or newer, or AMD CPU with support for a
Windows Hypervisor		ARM-based chips, or 2nd generation Intel Core or newer with support for
Hypervisor.Framework		x86_64 CPU architecture; 2nd generation Intel Core or newer, or AMD processor with support for AMD Virtualization (AMD-V) and SSSE3

RAM

8GB or more

Disk

At least 30GB free space. SSD is recommended.

Resolution

1280 x 800 Minimum

Internet

Broadband

- -Please keep in mind that both **64 bit CPU and 64 bit OS are mandatory condition.** If your system DOES NOT meet this condition, you have to change affected hardware or software or the whole system. **It is strongly recommended to use SSD (Solid State Disk) instead of HDD (Hard Disk Drive) because it will take less time when you are building the APS installation apk file.** Recommended is just recommended and it is not a mandatory. However, you may still use a HDD when you are building apk file but note that the building process can take a long time to complete, although once started, you can leave it running unattended. - -* * * - -### This article is divided into two parts. - -* In the overview part there is an explanation on what steps are necessary to build the APK file. -* In the step by step walkthrough part you will find the screenshots of a concrete installation. Because the versions of Android Studio - the software development environment which we will use to build the APK - will change very quickly this will be not identical to your installation but it should give you a good starting point. Android Studio also runs on Windows, Mac OS X and Linux and there might be small differences in some aspects between each platform. If you find that something important is wrong or missing, please inform the facebook group "AAPS users" or in the Discord chat [Android APS](https://discord.gg/4fQUWHZ4Mw) so that we can have a look at this. - -## Overview - -In general, the steps necessary to build the APK file: - -1. [Install git](../Installing-AndroidAPS/git-install.md) -2. [Install Android Studio](Building-APK-install-android-studio) -3. [Set git path in Android Studio preferences](Building-APK-set-git-path-in-preferences) -4. [Download AAPS code](Building-APK-download-AAPS-code) -5. [Download Android SDK](Building-APK-download-android-sdk) -6. [Build the app](Building-APK-generate-signed-apk) (generate signed apk) -7. [Transfer apk file to your phone](Building-APK-transfer-apk-to-smartphone) -8. [Identify receiver if using xDrip+](xdrip-identify-receiver) - -## Step by step walkthrough - -Detailed description of the steps necessary to build the APK file. - -## Install git (if you don't have it) - -Follow the manual on the [git installation page](../Installing-AndroidAPS/git-install.md). - -(Building-APK-install-android-studio)= - -## Install Android Studio - -The following screenshots have been taken from Android Studio Version Arctic Fox | 2020.3.1. Screens can change in future versions of Android Studio. But you should be able to find your way through. [Help from the community](../Where-To-Go-For-Help/Connect-with-other-users.md) is provided. - -One of the most important things when installing Android Studio: **Be patient!** During installation and setup Android Studio is downloading a lot of stuff which will take its time. - -Download [Android Studio from here](https://developer.android.com/studio/install.html) and install it on your computer. - -On first start you will find the setup wizard: - -Select "Do not import settings" as you have not used it before. - -![Do not import settings](../images/studioSetup/01_ImportSettings.png) - -Decide whether you want to share data with Google or not. - -![Share data with Google](../images/studioSetup/02_DataSharing.png) - -On the following screen click "Next". - -![Welcome screen](../images/studioSetup/03_Welcome.png) - -Select "Standard" installation and click "Next". - -![Standard installation](../images/studioSetup/04_InstallType.png) - -Select the theme for the user interface you like. (In this manual we used "Light".) Then click "Next". - -> ***Note:*** This is just the color scheme. You can select whatever you like (i.e. "Darcula" for dark mode). This selection has no influence on building the APK but the following screenshots might look different. - -![UI color scheme](../images/studioSetup/05_UITheme.png) - -Click "Next" on the "Verify Settings" dialog. - -![Verify settings](../images/studioSetup/06_Overview.png) - -Click on all three license agreement parts and select "Agree". When you have agreed to all, the "Finish" button will be enabled and you can "Finish". - - ![Agree license agreements](../images/studioSetup/07_LicenseAgreement.png) - - -Wait while Android Studio downloads additional components and be patient. Once everything is downloaded button "Finish" turns blue. Click the button now. - -![Downloading components](../images/studioSetup/08_Downloading.png) - -(Building-APK-download-AAPS-code)= - -## Download AAPS code - -* On the Android Studio welcome screen select "Projects" (1) on the left and then "Get from VCS" (2). - - ![Android Studio wizard](../images/studioSetup/20_ProjectVCS.png) - - * If you already opened Android Studio and do not see the welcome screen anymore select File (1) > New (2) > Project from Version Control... (3) - - ![Check out project from version control within Android Studio](../images/AndroidStudio_FileNew.PNG) - - * We will now tell Android Studio were to get the code from: - - * Make sure you have selected "Repository URL" on the left (1). - - * Check if "Git" is selected as version control (2). - * Copy and paste the URL ```https://github.com/nightscout/AndroidAPS``` to the main AAPS repository into the URL textbox (3). - * Choose the directory where you want to save the cloned code (4). - - ![Clone Git](../images/studioSetup/21_CloneURL.png) - -* Click button "Clone" (5). - - ![Clone repository](../images/studioSetup/22_Cloning.png) - -* Do not click "Background" while repository is cloned! - -* After the repository is cloned successfully, Android Studio will open the cloned project. - -* You will be asked whether you want to trust the project. Click on "Trust project"! - - ![Trust project](../images/studioSetup/23_TrustProject.png) - -* In the status bar at the bottom you will see the information that Android Studio is running background tasks. - - ![Background tasks](../images/studioSetup/24_GradleSyncRunning.png) - -* Windows only: Grant access if your firewall is asking for permission. - - ![Firewall permission java](../images/AndroidStudio361_18.png) - -* Once the background tasks are finished you will probably see an error saying that errors occurred (1) or (2) or (3). - - ![SDK licence](../images/studioSetup/25_SyncFailed.png) - - Don't worry, this will be solved soon! - -(Building-APK-set-git-path-in-preferences)= - -## Set git path in preferences - -Make sure [git is installed](../Installing-AndroidAPS/git-install.md) on your computer and you have restarted your computer since installing. - -On the Android Studio welcome screen click "Customize" (1) on the left and then select the link "All settings..." (2): - -![Android Studio settings from welcome screen](../images/studioSetup/10_WizardSettings.png) - -### Windows - -* As windows user, make sure you have restarted your computer after [installing Git](../Installing-AndroidAPS/git-install.md). - -* In the menu, go to File (1) > Settings (2) (or Android Studio > Preferences on Mac). - - ![Open settings](../images/studioSetup/30_Settings.png) - -* Double-click "Version Control" (1) to open the sub-menu. - -* Click Git (2). -* Make sure update method "Merge" (3) is selected. -* Check if Android Studio can locate path to git.exe automatically by clicking the button "Test" (4). - - ![Android Studio settings](../images/studioSetup/11_GitPath.png) - -* If automatic setting is successful git version will be displayed next to the path. - - ![Git version displayed](../images/studioSetup/12_GitVersion.png) - -* Eventually git.exe cannot be found automatically or the Test will result in an error (1): - - ![Git not found](../images/studioSetup/13_GitVersionError.png) - - In this case click on the folder icon (2). - -* Use [search function](https://www.tenforums.com/tutorials/94452-search-file-explorer-windows-10-a.html) in windows explorer to find "git.exe" if you are unsure where git has been installed. You are looking for a file named "git.exe", located in **\bin** folder. - -* Select path to git.exe and make sure you selected the one in ** \bin\ ** folder (3) and click "OK" (4). - - ![Select git manually](../images/studioSetup/14_GitManualSelection.png) - -* Check your selected git path again with the "Test" button as described above. - -* When the git version is displayed next to the path (see screenshot above), close settings window by clicking "OK" button (5). - -### Mac - -* Any git version should work. For example . -* Use homebrew to install git: ```$ brew install git```. -* For details on installing git see the [official git documentation](https://git-scm.com/book/en/v2/Getting-Started-Installing-Git). -* If you install git via homebrew there is no need to change any preferences. Just in case: They can be found here: Android Studio - Preferences. - -(Building-APK-download-android-sdk)= - -## Download Android SDK - -* In the menu, go to File (1) > Settings (2) (or Android Studio > Preferences on Mac). - - ![Open settings](../images/studioSetup/30_Settings.png) - -* Double-click on Languages & Frameworks to open its submenu (1). - -* Select Android SDK (2). -* Tick the box left of "Android 9.0 (Pie)" (3) (API Level 28). - - ![SDK settings](../images/studioSetup/31_AndroidSDK.png) - -* Confirm changes by clicking OK. - - ![Confirm SDK changes](../images/studioSetup/32_ConfirmSDK.png) - -* Wait until the SDK download and installation is finished. - - ![Wait during SDK installation](../images/studioSetup/34_DownloadSDK.png) - -* When SDK installation is completed the "Finish" button will turn blue. Click this button. - - ![Finish SDK installation](../images/studioSetup/35_DownloadSDKfinished.png) - -* Android Studio might recommend to update the gradle system. **Never update gradle!** This will lead to difficulties! - -* If you see an information on the lower right side of your Android Studio window that Android Gradle Plugin is ready to update click on the text "upgrade" (1). - - ![No gradle update](../images/studioSetup/36_GradleUpdateRequest.png) - -* In the dialog box the select "Don't remind me again for this project" (2). - - ![No gradle update](../images/studioSetup/37_GradleUpdateDeny.png) - -* Restart Android Studio before you continue. - -(Building-APK-generate-signed-apk)= - -## Generate signed APK - -Signing means that you indicate your app to be your own creation but in a digital way as a kind of digital fingerprint within the app itself. That is necessary because Android has a rule that it only accepts signed code to run for security reasons. For more information on this topic, follow [this link](https://developer.android.com/studio/publish/app-signing.html#generate-key). - -* After Android Studio is started, wait until all background tasks are finished. - - ![Wait for background tasks](../images/studioSetup/40_BackgroundTasks.png) - - * ***Warning:*** If errors occur, do not continue with the following steps. \ Consult the [troubleshooting section](../Installing-AndroidAPS/troubleshooting_androidstudio) for known problems! - - ![Gradle Sync Error](../images/studioSetup/41_GradleSyncError.png) - -* Click "Build" (1) in the menu bar and select "Generate Signed Bundle / APK..." (2). - - ![Build apk](../images/studioSetup/42_MenuBuild.png) - -* Select "APK" (1) instead of "Android App Bundle" and click "Next" (2). - - ![APK instead of bundle](../images/studioSetup/43_Apk.png) - -* Make sure that module is set to "AndroidAPS.app" (1). - -* Click "Create new..." (2) to start creating your key store. - - ***Note:*** A key store in this case is nothing more than a file in which the information for signing is stored. It is encrypted and the information is secured with passwords. - - ![Create key store](../images/studioSetup/44_KeystoreNew.png) - -* Click the folder symbol to select a path on your computer for your key store. - - ![Create key store](../images/studioSetup/45_KeystoreDialog.png) - -* Select the path where your key store shall be saved (1). - - ![Create key store](../images/studioSetup/46_KeystorePath.png) - - ***Warning: Do not save in same folder as project. You must use a different directory!*** A good location would be your home folder. - -* Type a file name for your key store (2) and confirm with "OK" (3). - -* Enter (2) and confirm (3) the password for your key store. ![Select key store path](../images/studioSetup/47_KeystoreDialog.png) - - ***Note:*** Passwords for key store and key do not have to be very sophisticated. Make sure to remember those or make a note in a safe place. In case you will not remember your passwords in the future, see [troubleshooting for lost key store](troubleshooting_androidstudio-lost-keystore). - -* Enter an alias (4) for your key. Choose whatever you like. - -* Enter (5) and confirm (6) the password for your key - -* Validity (7) is 25 years by default. You do not have to change the default value. - -* First and last name must be entered (8). All other information is optional. - -* Click "OK" (9) when you are done. - -* Make sure the box to remember passwords is checked (1). So you don't have to enter them again next time you build the apk (i.e. when updating to a new AAPS version). - -* Click "Next" (2). - - ![Remember passwords](../images/studioSetup/48_KeystoreSave.png) - -* Select build variant "fullRelease" (1) and press "Finish". - - ![Select build variant](../images/studioSetup/49_BuildVariant.png) - -* Android Studio will show "Gradle Build running" at the bottom. This takes some time, depending on your computer and internet connection. **Be patient!** - - ![Gradle Running](../images/studioSetup/50_GradleRunning.png) - -* Android Studio will display the information "Generate Signed APK" after build is finished. - - ![Build finished](../images/studioSetup/51_BuildFinished.png) - -* In case build was not successful refer to the [troubleshooting section](../Installing-AndroidAPS/troubleshooting_androidstudio). - -* Click on the notification to expand it. - -* Click on the link "locate". - - ![Locate build](../images/studioSetup/52_BuildLocate.png) - - * If the notification is gone, you can always open the "Event log" and select the same link there. ![Build successfully - event log](../images/studioSetup/53_EventLog.png) - -* Your file manager/explorer will open. Navigate to the directory "full" (1) > "release" (2). - - ![File location apk](../images/studioSetup/54_APKlocation.png) - -* "app-full-release.apk" (3) is the file you are looking for! - -(Building-APK-transfer-apk-to-smartphone)= - -## Transfer APK to smartphone - -Easiest way to transfer app-full-release.apk to your phone is via [USB cable or Google Drive](https://support.google.com/android/answer/9064445?hl=en). Please note that transfer by mail might cause difficulties and is not the preferred way. - -On your phone you have to allow installation from unknown sources. Manuals how to do this can be found on the internet (i.e. [here](https://www.expressvpn.com/de/support/vpn-setup/enable-apk-installs-android/) or [here](https://www.androidcentral.com/unknown-sources)). - -## Troubleshooting - -See separate page [troubleshooting Android Studio](../Installing-AndroidAPS/troubleshooting_androidstudio). \ No newline at end of file diff --git a/docs/CROWDIN/sk/Resources/index.md b/docs/CROWDIN/sk/Resources/index.md deleted file mode 100644 index 57b2ebe2945e..000000000000 --- a/docs/CROWDIN/sk/Resources/index.md +++ /dev/null @@ -1,8 +0,0 @@ -# Resources - -```{toctree} -:glob: true -:maxdepth: 4 - -clinician-guide-to-AndroidAPS -``` diff --git a/docs/CROWDIN/sk/Sandbox/sandbox2.md b/docs/CROWDIN/sk/Sandbox/sandbox2.md deleted file mode 100644 index 33c547956c89..000000000000 --- a/docs/CROWDIN/sk/Sandbox/sandbox2.md +++ /dev/null @@ -1,43 +0,0 @@ -# internal sandbox file 2 for testing - -```{admonition} no need to translate this -:class: note - -No need to translate this. -``` - -This is an internal sandbox file for the documentation team to test - -1. markdown syntax and - -1. background process for - 1. CROWDIN translation and - 2. Read The Docs deployment. - -You can dirctly jump from here to the first label in the sandbox1.md file - ["Jump"](sandbox1-this-is-a-test). - -You can dirctly jump from here to the second label in this file - ["Jump"](sandbox1-this-is-another-test). - -Here you can jump to the first sandbox file - ["Jump"](./sandbox1.md). - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -(sandbox2-this-is-a-test)= -## This is a test - -This is a test if labels must be unique. - -### This is spare information from the docs - -cut from index: - -There are "limits" set in place when you are first beginning your AAPS journey. These safety limits have been developed over many years by observations of the inadvertent mistakes that new users are most likely to make when first learning to set up, build, and then successfully loop with AAPS - as most often those mistakes occur simply because the user was so excited to get started using the system that they may have forgotten to sit down and dedicate the time needed to understand the information within this documentation thoroughly. - - -### spare info from the overview to put into "preparing" - -Since the requirements are very different from anything you might have set up in the past, we recommend that you really follow the instructions, step-by-step the first few times you build the app, so that you have a stronger sense of how the app building process is supposed to behave when all directions are followed exactly. Please remember to take your time. Later this will go very quickly when you build the app again for a new version. That way you will have a greater chance of noticing when something doesn't going as planned before too many steps are out of line. It is important to save the your keystore file (.jks file used to sign your app) in a safe place, so that you can always use that exact same keystore file and password each and every time you are asked to create a new updated version of AAPS, as this file is what makes sure that each new version of the app "remembers" all the information that you have provided to it in previous versions of the app and thus ensure that the updates will go as smoothly as possible. On average, you can assume that there will be one new version and 2-3 required updates per year. This number is based on experience and may change in the future. But we do want to at least give you a general guideline on what to expect. When you are more experienced at building updated AAPS app versions all the steps that are required in building an updated app will only take 15-30 minutes, on average. However, in the beginning there can be a rather steep learning curve as these steps are not always considered intuitive by new users! So do not get frustrated if you find that it takes half a day or a whole day with some help from the community before you are finally finished with the update process. If you find that you are getting very frustrated just take a short break, and oftentimes; after a stroll around the block or two...you'll find that you are better able to approach the problem again. diff --git a/docs/CROWDIN/sk/Usage/Objectives.md b/docs/CROWDIN/sk/Usage/Objectives.md deleted file mode 100644 index c27b9c02a04c..000000000000 --- a/docs/CROWDIN/sk/Usage/Objectives.md +++ /dev/null @@ -1,184 +0,0 @@ -# Objectives - -AAPS has a series of Objectives that need to be completed to walk you through the features and settings of safe looping. They ensure you have configured everything detailed in the sections above correctly, and that you understand what your system is doing and why so you can trust it. - -If you are **upgrading phones** then you can [export your settings](../Usage/ExportImportSettings.md) to keep your progress through the objectives. Not only will your progress through the objectives be saved, but also your safety settings such as max bolus etc. If you do not export and import your settings then you will need to start the objectives from the beginning again. It is a good idea to [backup your settings](../Usage/ExportImportSettings.html) frequently just in case. - -If you want to go back in objectives see [explanation below](Objectives-go-back-in-objectives). - -## Objective 1: Setting up visualization and monitoring, analysing basals and ratios - -- Select the right blood glucose source for your setup. See [BG Source](../Configuration/BG-Source.md) for more information. -- Select the right Pump in ConfigBuilder (select Virtual Pump if you are using a pump model with no AAPS driver for looping) to ensure your pump status can communicate with AAPS. -- If using DanaR pump then ensure you have followed [DanaR Insulin Pump](../Configuration/DanaR-Insulin-Pump.md) instructions to ensure the link between pump and AAPS. -- You need to establish a data repository/reporting platform to complete this objective. That can be accomplished with either Nightscout or Tidepool (or both). Follow instructions at the [Nightscout](../Installing-AndroidAPS/Nightscout.md) or [Tidepool](../Installing-AndroidAPS/Tidepool.md) page for instructions. -- Note that URL in NSClient must be **WITHOUT /api/v1/** at the end - see [NSClient settings in Preferences](Preferences-nsclient). - -*You may need to wait for the next blood glucose reading to arrive before AAPS will recognise it.* - -## Objective 2: Learn how to control AAPS - -- Perform several actions in AAPS as described in this objective. - -- Click on the orange text "Not completed yet" to access the to-dos. - -- Links will be provided to guide you in case you are not familiar with a specific action yet. - - ```{image} ../images/Objective2_V2_5.png - :alt: Screenshot objective 2 - ``` - -(Objectives-objective-3-prove-your-knowledge)= - -## Objective 3: Prove your knowledge - -Objective 3 is a multiple choice test based on questions designed to test your theoretical knowledge of **AAPS**. - -Some users find Objective 3 to be the most difficult objective to complete. Please do read the AAPS documents in conjunction with the questions. If you are genuinely stuck after researching the **AAPS** documents, please search or ask for help on the Facebook or Discord group. These groups can provide friendly hints or redirect you to the relevant part of the **AAPS** documents. - -To proceed with Objective 3, click on the orange text “Not completed yet” to access the relevant question. Please read each question and select your answer(s). - - - -Within each question, a hyperlink to the **AAPS** documents will guide you to the relevant section of the document which you should read in order to locate the correct answer. - - -[Obj3_Screenshot 2023-12-05 223422](https://github.com/openaps/AndroidAPSdocs/assets/137224335/77347516-e24e-459d-98ab-acbb49a3d4e8)![image](https://github.com/openaps/AndroidAPSdocs/assets/137224335/ca756b8e-efbc-4427-b281-ac953ce16718) - - - -For each question, there may be more than one answer that is correct! If an incorrect answer is selected, the question will be time locked for a certain amount of time (60 minutes) before you can go back and answer the question. - - -After updating to a new version of **AAPS**, new questions may be added to cover a prevalent issue picked up by **AAPS** or alternatively to test your knowledge of a new feature of **AAPS** as released. - - -When **AAPS** is installed for the first time, you will have to complete Objective 3 entirely in order to move onto Objective 4. Each objective is required to be completed in sequential order. New features will gradually be unlocked as progress is made through the objectives. - -__What happens if new questions are added later to Objective 3?__ From time to time, new features are added to **AAPS** which may require a new question to be added to Objective 3. As a result, any new question added to Objective 3 will be marked as “incomplete” because **AAPS** will require you to action this. As each Objective is independent, you will not lose the existing functionality of **AAPS** providing the other objectives remain completed. - - -## Objective 4: Starting on an open loop - -- Select Open Loop either from Preferences, or by pressing and holding the Loop button in top left of the home screen. -- Work through the [Preferences](../Configuration/Preferences.md) to set up for you. -- Manually enact at least 20 of the temporary basal rate suggestions over a period of 7 days; input them to your pump and confirm in AAPS that you have accepted them. Ensure this data shows in AAPS and Nightscout. -- Enable [temp targets](../Usage/temptarget.md) if necessary. Use hypo temp targets to prevent that the system will correct too strong because of a raising blood glucose after a hypo. - -### Reduce number of notifications - -- To reduce the Number of decisions to be made while in Open Loop set wide target range like 90 - 150 mg/dl or 5,0 - 8,5 mmol/l. - -- You might even want to wider upper limit (or disable Open Loop) at night. - -- In Preferences you can set a minimum percentage for suggestion of basal rate change. - - ```{image} ../images/OpenLoop_MinimalRequestChange2.png - :alt: Open Loop minimal request change - ``` - -- Also, you do not need to act every 5 minutes on all suggestions... - -## Objective 5: Understanding your open loop, including its temp basal recommendations - -- Start to understand the thinking behind the temp basal recommendations by looking at the [determine basal logic](https://openaps.readthedocs.io/en/latest/docs/While%20You%20Wait%20For%20Gear/Understand-determine-basal.html) and both the [forecast line in AAPS homescreen](Screenshots-prediction-lines)/Nightscout and the summary of outputs from the calculations in your OpenAPS tab. - -You will want to set your target higher than usual until you are confident in the calculations and settings. System allows - -- a low target to be a minimum of 4 mmol (72 mg/dl) or maximum of 10 mmol (180 mg/dl) -- a high target to be a minimum of 5 mmol (90 mg/dl) and maximum of 15 mmol (225 mg/dl) -- a temporary target as a single value can be anywhere in the range of 4 mmol to 15 mmol (72 mg/dl to 225 mg/dl) - -The target is the value that calculations are based on, and not the same as where you aim to keep your blood glucose values within. If your target is very wide (say, 3 or more mmol \[50 mg/dl or more\] wide), you will often find little AAPS action. This is because blood glucose is eventually predicted to be somewhere in that wide range and therefore not many fluctuating temporary basal rates are suggested. - -You may want to experiment with adjusting your targets to be a closer together range (say, 1 or less mmol \[20 mg/dl or less\] wide) and observe how the behavior of your system changes as a result. - -You can view a wider range (green lines) on the graph for the values you aim to keep your blood glucose within by entering different values in [Preferences](../Configuration/Preferences.md) > Range for Visualisation. - -```{image} ../images/sign_stop.png -:alt: Stop sign -``` - -### Stop here if you are open looping with a virtual pump - do not click Verify at the end of this objective. - -```{image} ../images/blank.png -:alt: blank -``` - -(Objectives-objective-6-starting-to-close-the-loop-with-low-glucose-suspend)= -## Objective 6: Starting to close the loop with Low Glucose Suspend - -```{image} ../images/sign_warning.png -:alt: Warning sign -``` - -### Closed loop will not correct high BG values in objective 6 as it is limited to low glucose suspend. High BG values have to be corrected manually by you! - -- Prerequisite: You need a good profile (basal, ISF, IC) already working in AAPS to start with Loop in Low Glucose Suspend mode. Otherwise you can run in a hypo which you have to manually correct. This will help you a lot to avoid having to treat a low glucose over a period of 5 days. **If you are still having frequent or severe low glucose episodes then consider refining your DIA, basal, ISF and carb ratios and do NOT start objective 6 at this time.** -- You don't have to change your settings now. During objective 6, the maxIOB setting is internally set to zero automatically. **This override will be reversed when moving to objective 7.** -- The system will override your maxIOB settings to zero, which means if blood glucose is dropping it can reduce basal for you. If blood glucose is rising then it will only increase basal if the basal IOB is negative from a previous Low Glucose Suspend. Otherwise basal rates will remain the same as your selected profile. **That means that you have to manually handle high values with insulin corrections.** -- If your basal IOB is negative (see screenshot below) a TBR > 100% can be issued also in objective 6. - -```{image} ../images/Objective6_negIOB.png -:alt: Example negative IOB -``` - -- Set your target range slightly higher than you usually aim for, just to be safe and have a bit more scurity buffer. -- Enable 'Low Glucose Suspend' mode either by by pressing and holding the Loop icon at the top right corner of the home screen and selecting the Loop - LGS mode icon. -- Watch how temporary basals are active by viewing the blue basal text on the homescreen or the blue basal render on the homescreen graph. -- You may temporarily experience spikes following treated hypos without the ability to increase basal on the rebound. - -(Objectives-objective-7-tuning-the-closed-loop-raising-max-iob-above-0-and-gradually-lowering-bg-targets)= -## Objective 7: Tuning the closed loop, raising maxIOB above 0 and gradually lowering BG targets - -- Select 'Closed Loop' either from [Preferences](../Configuration/Preferences.md) or by pressing and holding the Loop icon at the top right corner of the home screen, over a period of 1 day. - -- Raise your 'Maximum total IOB OpenAPS can’t go over' (in OpenAPS called 'max-iob') above 0. The default recommendation is "average mealbolus + 3x max daily basal" (for the SMB algorithm) or "3x max daily basal" (for the older AMA algorithm) but you should slowly work up to this until you know your settings work for you (max daily basal = the maximum hourly value in any time segment of the day). - - This recommendation should be seen as a starting point. If you set to the 3x and you are seeing moves that push you too hard and fast then lower that number. If you are very resistant, raise it very little at a time. - - ```{image} ../images/MaxDailyBasal2.png - :alt: max daily basal - ``` - -- Once confident on how much IOB suits your looping patterns, then reduce your targets to your desired level. - -(Objectives-objective-8-adjust-basals-and-ratios-if-needed-and-then-enable-autosens)= -## Objective 8: Adjust basals and ratios if needed, and then enable autosens - -- You can use [autotune](https://openaps.readthedocs.io/en/latest/docs/Customize-Iterate/autotune.html) as a one off to check your basals remain accurate or do a traditional basal test. -- Enable [autosens](../Usage/Open-APS-features.md) over a period of 7 days and watch the white line on the homescreen graph show how your sensitivity to insulin may be rising or falling as a result of exercise or hormones etc. and keep an eye in the OpenAPS report tab how AAPS is adjusting the basals and/or targets accordingly. - -*Don’t forget to record your looping in* [this form](https://bit.ly/nowlooping) *logging AAPS as your type of DIY loop software, if you have not already done so.* - -(Objectives-objective-9-enabling-additional-oref1-features-for-daytime-use-such-as-super-micro-bolus-smb)= -## Objective 9: Enabling additional oref1 features for daytime use, such as super micro bolus (SMB) - -- You must read the [SMB chapter in this wiki](Open-APS-features-super-micro-bolus-smb) and [chapter oref1 in openAPSdocs](https://openaps.readthedocs.io/en/latest/docs/Customize-Iterate/oref1.html) to understand how SMB works, especially what's the idea behind zero-temping. -- Then you ought to [rise maxIOB](Open-APS-features-maximum-total-iob-openaps-cant-go-over-openaps-max-iob) to get SMBs working fine. maxIOB now includes all IOB, not just added basal. That is, if given a bolus of 8 U for a meal and maxIOB is 7 U, no SMBs will be delivered until IOB drops below 7 U. A good start is maxIOB = average mealbolus + 3x max daily basal (max daily basal = the maximum hourly value in any time segment of the day - see [objective 7](Objectives-objective-7-tuning-the-closed-loop-raising-max-iob-above-0-and-gradually-lowering-bg-targets) for an illustration) -- min_5m_carbimpact default in absorption settings has changed from 3 to 8 going from AMA to SMB. If you are upgrading from AMA to SMB, you have to change it manually. - -(Objectives-objective-10-automation)= -## Objective 10: Automation - -- You have to start objective 10 to be able to use [Automation](../Usage/Automation.md). -- Make sure you have completed all objectives including exam [Objectives-objective-3-prove-your-knowledge](Objectives#objective-3-prove-your-knowledge). -- Completing previous objectives will not effect other objectives you have already finished. You will keep all finished objectives! - -(Objectives-objective-11-DynamicISF)= -## Objective 11: Additional Features such as DynamicISF - -- You have to start objective 11 to be able to use [DynamicISF](../Usage/Open-APS-features.md) - -(Objectives-go-back-in-objectives)= -## Go back in objectives - -If you want to go back in objectives for whatever reason you can do so by clicking at "clear finished". - -```{image} ../images/Objective_ClearFinished.png -:alt: Go back in objectives -``` - -## Objectives in Android APS before version 3.0 - -One objective was removed when Android APS 3.0 was released. Users of Android APS version 2.8.2.1 who are on older Android software (i.e. earlier than version 9) will be using an older set of objectives which can be found [here](../Usage/Objectives_old.md). diff --git a/docs/CROWDIN/sk/Usage/Objectives2019.md b/docs/CROWDIN/sk/Usage/Objectives2019.md deleted file mode 100644 index c67a978f7a4f..000000000000 --- a/docs/CROWDIN/sk/Usage/Objectives2019.md +++ /dev/null @@ -1,111 +0,0 @@ -# Objectives - -AndroidAPS has a series of Objectives that need to be completed to walk you through the features and settings of safe looping. They ensure you have configured everything detailed in the sections above correctly, and that you understand what your system is doing and why so you can trust it. - -If you are **upgrading phones** then you can [export your settings](../Usage/ExportImportSettings.md) to keep your progress through the objectives. Not only will your progress through the objectives be saved, but also your safety settings such as max bolus etc. If you do not export and import your settings then you will need to start the objectives from the beginning again. It is a good idea to [backup your settings](../Usage/ExportImportSettings.html) frequently just in case. - -## Objective 1: Setting up visualization and monitoring, analysing basals and ratios - -- Select the right blood glucose source for your setup. See [BG Source](../Configuration/BG-Source.md) for more information. -- Select the right Pump in ConfigBuilder (select Virtual Pump if you are using a pump model with no AndroidAPS driver for looping) to ensure your pump status can communicate with AndroidAPS. -- If using DanaR pump then ensure you have followed [DanaR Insulin Pump](../Configuration/DanaR-Insulin-Pump.md) instructions to ensure the link between pump and AndroidAPS. -- Follow instructions in [Nightscout](../Installing-AndroidAPS/Nightscout.md) page to ensure Nightscout can receive and display this data. -- Note that URL in NSClient must be **WITHOUT /api/v1/** at the end - see [NSClient settings in Preferences](../Configuration/Preferences#ns-client). - -*You may need to wait for the next blood glucose reading to arrive before AndroidAPS will recognise it.* - -## Objective 2: Learn how to control AndroidAPS - -- Perform several actions in AndroidAPS as described in this objective. - -- Click on the orange text "Not completed yet" to access the to-dos. - -- Links will be provided to guide you in case you are not familiar with a specific action yet. - - > ```{image} ../images/Objective2_V2_5.png - > :alt: Screenshot objective 2 - > ``` - -## Objective 3: Prove your knowledge - -- Pass a multiple-choice exam testing your AndroidAPS knowledge. - -- Click on the orange text "Not completed yet" to access the page with the question and answering optons. - -- Links will be provided to guide you in case you are unsure abouit the correct answers yet. - - > ```{image} ../images/Objective3_V2_5.png - > :alt: Screenshot objective 3 - > ``` - -## Objective 4: Starting on an open loop - -- Select Open Loop either from Preferences, or by pressing and holding the Loop button in top left of the home screen. -- Work through the [Preferences](../Configuration/Preferences.md) to set up for you. -- Manually enact at least 20 of the temporary basal rate suggestions over a period of 7 days; input them to your pump and confirm in AndroidAPS that you have accepted them. Ensure this data shows in AndroidAPS and Nightscout. -- Enable [temp targets](../Usage/temptarget.md) if necessary. Use hypo temp targets to prevent that the system will correct too strong because of a raising blood glucose after a hypo. - -## Objective 5: Understanding your open loop, including its temp basal recommendations - -- Start to understand the thinking behind the temp basal recommendations by looking at the [determine basal logic](https://openaps.readthedocs.io/en/latest/docs/While%20You%20Wait%20For%20Gear/Understand-determine-basal.html) and both the [forecast line in AndroidAPS homescreen](../Getting-Started/Screenshots#section-e)/Nightscout and the summary of outputs from the calculations in your OpenAPS tab. - -You will want to set your target higher than usual until you are confident in the calculations and settings. System allows - -- a low target to be a minimum of 4 mmol (72 mg/dl) or maximum of 10 mmol (180 mg/dl) -- a high target to be a minimum of 5 mmol (90 mg/dl) and maximum of 15 mmol (225 mg/dl) -- a temporary target as a single value can be anywhere in the range of 4 mmol to 15 mmol (72 mg/dl to 225 mg/dl) - -The target is the value that calculations are based on, and not the same as where you aim to keep your blood glucose values within. If your target is very wide (say, 3 or more mmol \[50 mg/dl or more\] wide), you will often find little AAPS action. This is because blood glucose is eventually predicted to be somewhere in that wide range and therefore not many fluctuating temporary basal rates are suggested. - -You may want to experiment with adjusting your targets to be a closer together range (say, 1 or less mmol \[20 mg/dl or less\] wide), and observe how the behavior of your system changes as a result. - -You can view a wider range (green lines) on the graph for the values you aim to keep your blood glucose within by entering different values in [Preferences](../Configuration/Preferences.md) > Range for Visualisation. - -![Stop sign](../images/sign_stop.png) - -### Stop here if you are open looping with a virtual pump - do not click Verify at the end of this objective. - -![blank](../images/blank.png) - -## Objective 6: Starting to close the loop with Low Glucose Suspend - -![Warning sign](../images/sign_warning.png) - -### Closed loop will not correct high bg values in objective 6 as it is limited to low glucose suspend. High bg values have to be corrected manually by you! - -- Select Closed Loop either from [Preferences](../Configuration/Preferences.md) or by pressing and holding the Open Loop button in the top left of the home screen. -- Set your target range slightly higher than you usually aim for, just to be safe. -- Watch how temporary basals are active by viewing the blue basal text on the homescreen or the blue basal render on the homescreen graph. -- Ensure your settings have supported AndroidAPS to avoid having to treat a low glucose over a period of 5 days. If you are still having frequent or severe low glucose episodes then consider refining your DIA, basal, ISF and carb ratios. - -*The system will override your maxIOB settings to zero, which means if blood glucose is dropping it can reduce basal for you, but if blood glucose is rising then it will only increase basal if the IOB is negative (from a previous Low Glucose Suspend), otherwise basal rates will remain the same as your selected profile. You may temporarily experience spikes following treated hypos without the ability to increase basal on the rebound.* - -## Objective 7: Tuning the closed loop, raising max IOB above 0 and gradually lowering BG targets - -- Raise your 'Maximum total IOB OpenAPS can’t go over' (in OpenAPS called 'max-iob') above 0 over a period of 1 day, the default recommendation is "average mealbolus + 3x max daily basal"(for SMB algorithm) or "3x max daily basal" (for older AMA algorithm) but you should slowly work up to this until you know your settings work for you (max daily basal = the maximum hourly value in any time segment of the day). - - This recommendation should be seen as a starting point. If you set to the 3x and you are seeing moves that push you to hard and fast then lower that number. If you are very resistant raise it a very little at a time. - - > ```{image} ../images/MaxDailyBasal2.png - > :alt: max daily basal - > ``` - -- Once confident on how much IOB suits your looping patterns then reduce your targets to your desired level. - -## Objective 8: Adjust basals and ratios if needed, and then enable autosens - -- You can use [autotune](https://openaps.readthedocs.io/en/latest/docs/Customize-Iterate/autotune.html) as a one off to check your basals remain accurate, or do a traditional basal test. -- Enable [autosens](../Usage/Open-APS-features.md) over a period of 7 days and watch the white line on the homescreen graph show how your sensitivity to insulin may be rising or falling as a result of exercise or hormones etc, and keep an eye in the OpenAPS report tab how AndroidAPS is adjusting the basals and/or targets accordingly. - -*Don’t forget to record your looping in \`this form \\`\_ logging AndroidAPS as your type of DIY loop software, if you have not already done so.* - -## Objective 9: Enabling additional oref0 features for daytime use, such as advanced meal assist (AMA) - -- Now you should feel confident with how AndroidAPS works and what settings reflect your diabetes best -- Then over a period of 28 days you can try additional features that automate even more of the work for you such as the [advanced meal assist](../Usage/Open-APS-features#advanced-meal-assist-ama) - -## Objective 10: Enabling additional oref1 features for daytime use, such as super micro bolus (SMB) - -- You must read the [SMB chapter in this wiki](../Usage/Open-APS-features#super-micro-bolus-smb) and [chapter oref1 in openAPSdocs](https://openaps.readthedocs.io/en/latest/docs/Customize-Iterate/oref1.html) to understand how SMB works, especially what's the idea behind zero-temping. -- Then you ought to [rise maxIOB](../Usage/Open-APS-features#maximum-total-iob-openaps-cant-go-over-openaps-max-iob) to get SMBs working fine. maxIOB now includes all IOB, not just added basal. That is, if given a bolus of 8 U for a meal and maxIOB is 7 U, no SMBs will be delivered until IOB drops below 7 U. A good start is maxIOB = average mealbolus + 3x max daily basal (max daily basal = the maximum hourly value in any time segment of the day - see [objective 7](../Usage/Objectives2019.md#objective-7-tuning-the-closed-loop-raising-max-iob-above-0-and-gradually-lowering-bg-targets) for an illustration) -- min_5m_carbimpact default in absorption settings has changed from 3 to 8 going from AMA to SMB. If you are upgrading from AMA to SMB, you have to change it manualy diff --git a/docs/CROWDIN/sk/Usage/Objectives_old.md b/docs/CROWDIN/sk/Usage/Objectives_old.md deleted file mode 100644 index a3dc8861eae2..000000000000 --- a/docs/CROWDIN/sk/Usage/Objectives_old.md +++ /dev/null @@ -1,152 +0,0 @@ -# Objectives as of Android APS 2.8.2.1 - -This is not the latest version of the Android APS Objectives. This page details the Objectives that were in place prior to version 3.0. Anyone using an older version of Android (i.e. prior to Android 9) and Android APS version 2.8.2.1 should refer to this page. - -Please see [this page](../Usage/Objectives.md) for the current set of Objectives. - -AndroidAPS has a series of Objectives that need to be completed to walk you through the features and settings of safe looping. They ensure you have configured everything detailed in the sections above correctly, and that you understand what your system is doing and why so you can trust it. - -If you are **upgrading phones** then you can [export your settings](../Usage/ExportImportSettings.md) to keep your progress through the objectives. Not only will your progress through the objectives be saved, but also your safety settings such as max bolus etc. If you do not export and import your settings then you will need to start the objectives from the beginning again. It is a good idea to [backup your settings](../Usage/ExportImportSettings.html) frequently just in case. - -If you want to go back in objectives see [explanation below](../Usage/Objectives.md#go-back-in-objectives). - -## Objective 1: Setting up visualization and monitoring, analysing basals and ratios - -- Select the right blood glucose source for your setup. See [BG Source](../Configuration/BG-Source.md) for more information. -- Select the right Pump in ConfigBuilder (select Virtual Pump if you are using a pump model with no AndroidAPS driver for looping) to ensure your pump status can communicate with AndroidAPS. -- If using DanaR pump then ensure you have followed [DanaR Insulin Pump](../Configuration/DanaR-Insulin-Pump.md) instructions to ensure the link between pump and AndroidAPS. -- Follow instructions in [Nightscout](../Installing-AndroidAPS/Nightscout.md) page to ensure Nightscout can receive and display this data. -- Note that URL in NSClient must be **WITHOUT /api/v1/** at the end - see [NSClient settings in Preferences](../Configuration/Preferences.md#nsclient). - -*You may need to wait for the next blood glucose reading to arrive before AndroidAPS will recognise it.* - -## Objective 2: Learn how to control AndroidAPS - -- Perform several actions in AndroidAPS as described in this objective. - -- Click on the orange text "Not completed yet" to access the to-dos. - -- Links will be provided to guide you in case you are not familiar with a specific action yet. - - ![Screenshot objective 2](../images/Objective2_V2_5.png) - -## Objective 3: Prove your knowledge - -- Pass a multiple-choice exam testing your AndroidAPS knowledge. - -- Click on the orange text "Not completed yet" to access the page with the question and answering options. - - ![Screenshot objective 3](../images/Objective3_V2_5.png) - -- Links will be provided to guide you in case you are unsure about the correct answers yet. - -- The questions for objective 3 have been completely rewritten by native speakers as of AAPS 2.8. The new ones cover the same basic topics plus a few new ones. - -- These new questions will lead to some not answered questions even though you have successfully completed objective 3 in previous versions. - -- Unanswered questions will affect you only if you start a new objective. In other words: If you have already completed all objectives you can wait and answer the new questions later without loosing AAPS functions. - -## Objective 4: Starting on an open loop - -- Select Open Loop either from Preferences, or by pressing and holding the Loop button in top left of the home screen. -- Work through the [Preferences](../Configuration/Preferences.md) to set up for you. -- Manually enact at least 20 of the temporary basal rate suggestions over a period of 7 days; input them to your pump and confirm in AndroidAPS that you have accepted them. Ensure this data shows in AndroidAPS and Nightscout. -- Enable [temp targets](../Usage/temptarget.md) if necessary. Use hypo temp targets to prevent that the system will correct too strong because of a raising blood glucose after a hypo. - -### Reduce number of notifications - -- To reduce the Number of decisions to be made while in Open Loop set wide target range like 90 - 150 mg/dl or 5,0 - 8,5 mmol/l. - -- You might even want to wider upper limit (or disable Open Loop) at night. - -- In Preferences you can set a minimum percentage for suggestion of basal rate change. - - ![Open Loop minimal request change](../images/OpenLoop_MinimalRequestChange2.png) - -- Also, you do not need to act every 5 minutes on all suggestions... - -## Objective 5: Understanding your open loop, including its temp basal recommendations - -- Start to understand the thinking behind the temp basal recommendations by looking at the [determine basal logic](https://openaps.readthedocs.io/en/latest/docs/While%20You%20Wait%20For%20Gear/Understand-determine-basal.html) and both the [forecast line in AndroidAPS homescreen](../Getting-Started/Screenshots.md#prediction-lines)/Nightscout and the summary of outputs from the calculations in your OpenAPS tab. - -You will want to set your target higher than usual until you are confident in the calculations and settings. System allows - -- a low target to be a minimum of 4 mmol (72 mg/dl) or maximum of 10 mmol (180 mg/dl) -- a high target to be a minimum of 5 mmol (90 mg/dl) and maximum of 15 mmol (225 mg/dl) -- a temporary target as a single value can be anywhere in the range of 4 mmol to 15 mmol (72 mg/dl to 225 mg/dl) - -The target is the value that calculations are based on, and not the same as where you aim to keep your blood glucose values within. If your target is very wide (say, 3 or more mmol \[50 mg/dl or more\] wide), you will often find little AAPS action. This is because blood glucose is eventually predicted to be somewhere in that wide range and therefore not many fluctuating temporary basal rates are suggested. - -You may want to experiment with adjusting your targets to be a closer together range (say, 1 or less mmol \[20 mg/dl or less\] wide) and observe how the behavior of your system changes as a result. - -You can view a wider range (green lines) on the graph for the values you aim to keep your blood glucose within by entering different values in [Preferences](../Configuration/Preferences.md) > Range for Visualisation. - -![Stop sign](../images/sign_stop.png) - -### Stop here if you are open looping with a virtual pump - do not click Verify at the end of this objective. - -![blank](../images/blank.png) - -## Objective 6: Starting to close the loop with Low Glucose Suspend - -![Warning sign](../images/sign_warning.png) - -### Closed loop will not correct high bg values in objective 6 as it is limited to low glucose suspend. High bg values have to be corrected manually by you! - -- Select Closed Loop either from [Preferences](../Configuration/Preferences.md) or by pressing and holding the Open Loop button in the top left of the home screen. - -- Set your target range slightly higher than you usually aim for, just to be safe. - -- Watch how temporary basals are active by viewing the blue basal text on the homescreen or the blue basal render on the homescreen graph. - -- Ensure your settings have supported AndroidAPS to avoid having to treat a low glucose over a period of 5 days. If you are still having frequent or severe low glucose episodes then consider refining your DIA, basal, ISF and carb ratios. - -- You don't have to change your settings. During objective 6 maxIOB setting is internally set to zero automatically. This override will be reversed when moving to objective 7. - -- The system will override your maxIOB settings to zero, which means if blood glucose is dropping it can reduce basal for you, but if blood glucose is rising then it will only increase basal if the basal IOB is negative (from a previous Low Glucose Suspend), otherwise basal rates will remain the same as your selected profile. - - ![Example negative IOB](../images/Objective6_negIOB.png) - -- If your basal IOB is negative (see screenshot above) a TBR > 100% can be issued also in objective 6. - -- You may temporarily experience spikes following treated hypos without the ability to increase basal on the rebound. - -## Objective 7: Tuning the closed loop, raising max IOB above 0 and gradually lowering BG targets - -- Raise your 'Maximum total IOB OpenAPS can’t go over' (in OpenAPS called 'max-iob') above 0 over a period of 1 day, the default recommendation is "average mealbolus + 3x max daily basal"(for SMB algorithm) or "3x max daily basal" (for older AMA algorithm) but you should slowly work up to this until you know your settings work for you (max daily basal = the maximum hourly value in any time segment of the day). - - This recommendation should be seen as a starting point. If you set to the 3x and you are seeing moves that push you to hard and fast then lower that number. If you are very resistant raise it a very little at a time. - - ![max daily basal](../images/MaxDailyBasal2.png) - -- Once confident on how much IOB suits your looping patterns then reduce your targets to your desired level. - -## Objective 8: Adjust basals and ratios if needed, and then enable autosens - -- You can use [autotune](https://openaps.readthedocs.io/en/latest/docs/Customize-Iterate/autotune.html) as a one off to check your basals remain accurate or do a traditional basal test. -- Enable [autosens](../Usage/Open-APS-features.md) over a period of 7 days and watch the white line on the homescreen graph show how your sensitivity to insulin may be rising or falling as a result of exercise or hormones etc. and keep an eye in the OpenAPS report tab how AndroidAPS is adjusting the basals and/or targets accordingly. - -*Don’t forget to record your looping in* [this form](https://bit.ly/nowlooping) *logging AndroidAPS as your type of DIY loop software, if you have not already done so.* - -## Objective 9: Try additional features for daytime use and gain confidence in your closed loop system - -- Before AAPS version 2.7 meal assist (MA) was the basic algorithm for AAPS and completing objective 8 was necessary to activate [advanced meal assist (AMA)](../Usage/Open-APS-features.md#advanced-meal-assist-ama). -- As [advanced meal assist (AMA)](../Usage/Open-APS-features.md#advanced-meal-assist-ama) is the standard algorithm from AAPS version 2.7 onwards use the following 28 days to try features you haven't used yet and get more confident with you closed loop system. - -## Objective 10: Enabling additional oref1 features for daytime use, such as super micro bolus (SMB) - -- You must read the [SMB chapter in this wiki](../Usage/Open-APS-features.md#super-micro-bolus-smb) and [chapter oref1 in openAPSdocs](https://openaps.readthedocs.io/en/latest/docs/Customize-Iterate/oref1.html) to understand how SMB works, especially what's the idea behind zero-temping. -- Then you ought to [rise maxIOB](../Usage/Open-APS-features.md#maximum-total-iob-openaps-cant-go-over-openaps-max-iob) to get SMBs working fine. maxIOB now includes all IOB, not just added basal. That is, if given a bolus of 8 U for a meal and maxIOB is 7 U, no SMBs will be delivered until IOB drops below 7 U. A good start is maxIOB = average mealbolus + 3x max daily basal (max daily basal = the maximum hourly value in any time segment of the day - see [objective 7](../Usage/Objectives#objective-7-tuning-the-closed-loop-raising-max-iob-above-0-and-gradually-lowering-bg-targets) for an illustration) -- min_5m_carbimpact default in absorption settings has changed from 3 to 8 going from AMA to SMB. If you are upgrading from AMA to SMB, you have to change it manually. - -## Objective 11: Automation - -- You have to start objective 11 to be able to use [Automation](../Usage/Automation.md). -- Make sure you have completed all objectives including exam [../Usage/Objectives.md#objective-3-prove-your-knowledge](../Usage/Objectives#objective-3-prove-your-knowledge). -- Completing previous objectives will not effect other objectives you have already finished. You will keep all finished objectives! - -## Go back in objectives - -If you want to go back in objectives for whatever reason you can do so by clicking at "clear finished". - -![Go back in objectives](../images/Objective_ClearFinished.png) diff --git a/docs/CROWDIN/sk/Usage/Smoothing-Blood-Glucose-Data-in-xDrip.md b/docs/CROWDIN/sk/Usage/Smoothing-Blood-Glucose-Data-in-xDrip.md deleted file mode 100644 index 716234b04a15..000000000000 --- a/docs/CROWDIN/sk/Usage/Smoothing-Blood-Glucose-Data-in-xDrip.md +++ /dev/null @@ -1,33 +0,0 @@ -(Smoothing-Blood-Glucose-Data-in-xDrip-smoothing-blood-glucose-data)= - -# Smoothing blood glucose data - -If BG data is jumpy/noisy, AAPS may dose insulin incorrectly resulting in high or low BG. For this reason it’s important to disable the loop until the problem is resolved. Depending on your CGM such issues may be due to the CGM’s configuration or sensor problems/site issues. You may need to replace your CGM sensor to resolve this. - -Some CGM systems have internal algorithms to detect the noise level in the readings and AAPS can use this information to avoid giving SMBs if the BG data is too unreliable. However, some CGMs do not transmit this data and for these BG sources 'Enable SMB always' and 'Enable SMB after carbs' are disabled for safety reasons. - -## Dexcom sensors - -### Build Your Own Dexcom App - -When using [BYODA](DexcomG6-if-using-g6-with-build-your-own-dexcom-app) your BG data is smooth and consistent. Furthermore you can take advantage of Dexcom back-smoothing. There are no restrictions in using SMBs, because the noise-level data is shared with AAPS. - -### xDrip+ with Dexcom G6 or Dexcom ONE - -Noise-level data and smooth BG readings are only shared with AAPS if you use xDrip+ [native mode](https://navid200.github.io/xDrip/docs/Native-Algorithm). Using native mode, there are no restrictions in using SMBs. - -### Dexcom G6 or Dexcom ONE with xDrip+ Companion Mode - -The noise-level data is not shared with AAPS using this method. Therefore 'Enable SMB always' and 'Enable SMB after carbs' are disabled. - -## Freestyle Libre sensors - -### xDrip+ with FreeStyle Libre - -None of the FreeStyle Libre systems (FSL1, FSL2, or FSL3) broadcast any information about the level of noise detected in the readings, and therefore 'Enable SMB always' and 'Enable SMB after carbs' are disabled for all setups using the FreeStyle Libre. - -In addition, many people have reported the FreeStyle Libre often produces noisy data. In xDrip+ there are a few options to help with this: - -**Smooth Sensor Noise.** In xDrip+ Settings > xDrip+ Display Settings ensure that Smooth Sensor Noise is turned on. This attempts to apply smoothing to noisy data. - -**Smooth Sensor Noise (Ultrasensitive).** If you are still seeing noisy data in xDrip+ you can apply more aggressive smoothing using the Smooth Sensor Noise (Ultrasensitive) setting. This will attempt to apply smoothing even on very low levels of detected noise. To do this, first enable [engineering mode](Enabling-Engineering-Mode-in-xDrip.md) in xDrip+. Then navigate to Settings > xDrip+ Display Settings and turn on Smooth Sensor Noise (Ultrasensitive). \ No newline at end of file diff --git a/docs/CROWDIN/sk/Usage/autotune_b.md b/docs/CROWDIN/sk/Usage/autotune_b.md deleted file mode 100644 index ae85c34d4638..000000000000 --- a/docs/CROWDIN/sk/Usage/autotune_b.md +++ /dev/null @@ -1,186 +0,0 @@ -# How to use Autotune plugin - -Documentation about Autotune algorythm can be found in [OpenAPS documentation](https://openaps.readthedocs.io/en/latest/docs/Customize-Iterate/autotune.html). - -Autotune plugin is an implementation of OpenAPS autotune algorythm within AAPS. - -**Currently Autotune Plugin is only available in dev branch with Engineering mode.** - -## Autotune user interface - -![Autotune default screen](../images/Autotune/Autotune_1b.png) - -- You can select in the Profile dropdown menu the input profile you want to tune (by default your current active profile is selected) - - Note: each time you select a new profile, previous results will be removed and Tune days parameter will be set to default value -- Then Tune days is to select the number of days used in calculation to tune your profile. The minimum value is 1 day and the maximum value 30 days. This number should not be too small to get correct iterative and smooth results (above 7 days for each calculation) - - Note: each time you change Tune days parameter, previous results will be removed -- Last Run il a link that recover your latest valid calculation. If you didn't launch Autotune on current day, or if previous results was removed with a modification of calculation parameter above, then you can recover parameters and results of the latest successfull run. -- Warning show you for example some information about selected profile (if you have several IC values or several ISF values) - - Note: Autotune calculation works with only a single IC and a single ISF value. There is currently no existing Autotune algorythm to tune a circadian IC or circadian ISF. If your input profile has several values, you can see in warning section the average value taken into account to tune your profile. -- Check Input Profile button open the Profile Viewer to allow you a quick verification of your profile (Units, DAI, IC, ISF, basal and target) - - Note: Autotune will only tune your IC (single value), ISF (single value) and basal (with circadian variation). Units, DAI and target will remain unchanged in output profile. - -- "Run Autotune" will launch Autotune calculation with selected profile and the number of Tune days - - Note: Autotune calculation can take a long time. Once launched, you can switch to another view (home, ...) and come back later in Autotune plugin to see results - -![Autotune Run start](../images/Autotune/Autotune_2b.png) - -- Then during the run you will see intermediate results below - - - Note: During run, settings are locked, so you cannot change anymore selected input profile or the number of day. You will have to wait the end of current calculation if you want to launch another run with other parameters. - - ![Autotune during run](../images/Autotune/Autotune_3b.png) - -- When Autotune calculation is finished, you will see the result (Tuned profile) and four buttons below. - -![Autotune Result](../images/Autotune/Autotune_4b.png) - -- It's important to always compare input profile (column "Profile"), output profile (column "Tuned") and the percentage of variation for each value (Column "%"). - -- For basal rates, you also have the number of "missing days". You have missing days when Autotune don't have enough data categorized as "Basal" to tune basal rate for this period (for example after each meal when you have carbs absorption). This number should be as low as possible especially when basal is important (for example during the night or at the end of the afternoon) - -- The "Compare profiles" button open the profile comparator view. Input profile is in blue, and output profile (named "Tuned") is in red. - - - Note: in the example below input profile has circadian variation for IC and ISF, but output calculated profile has a single value. If it's important for you to get a circadian output profile see [Circadian IC or ISF profile](#circadian-ic-or-isf-profile) below. - - ![Autotune Compare profiles](../images/Autotune/Autotune_5.png) - -- If you trust results (low percentage of variation between input profile and output profile), you can click on "Activate profile" button and then click on OK to validated. - - - Activate Tuned profile will automatically create a new profile "Tuned" in your Local profile plugin. - - If you already have a profile named "Tuned" in your local profile plugin, then this profile will be updated with calculated Autotune profile before the activation - - ![Autotune Activate profile](../images/Autotune/Autotune_6.png) - -- If you think Tuned profile must be adjusted (for example if you think some variation are too important), then you can click on "Copy to local profile" button - - - A new profile with the prefix "Tuned" and the date and time of the run will be created in local profile plugin - -![Autotune Copy to local profile](../images/Autotune/Autotune_7.png) - -- You can then select local profile to edit the Tuned profile (it will be selected by default when you open Local profile plugin) - - - the values in local profile will but rounded in the user interface to your pump capabilities - - ![Autotune local profile update](../images/Autotune/Autotune_8.png) - -- If you want to replace your input profile with Autotune result, click on "Update input profile" button and validate the Popup with OK - - - Note: if you click on "Activate profile" after "Update input profile", then you will activate your updated profile and not the default "Tuned" profile? - - ![Autotune Update input profile](../images/Autotune/Autotune_9.png) - -- If you have updated your input profile, then the "Update input profile" button is replaced by "Revert input profile" button (see screenshot below). You can that way immediatly see if your current input profile in Local profile plugin already include the result of last run or not. You also have the possibility to recover you input profile without autotune result with this button - - ![Autotune Update input profile](../images/Autotune/Autotune_10.png) - - - -## Autotune settings - -### Autotune plugin settings - -![Autotune default screen](../images/Autotune/Autotune_11.png) - -- Automation Switch Profile (default Off): see [Run Autotune with an automation rule](#run-autotune-with-an-automation-rule) below. If you change this setting to On, the input profile will automatically be updated by the Tuned profile, and it will be activated. - - **Be Carefull, you must trust and verified during several following days that after an update and activation of Tuned profile without modification, it improves your loop** - -- Categorize UAM as basal (default On): This setting is for the users using AndroidAPS without any carbs entered (Full UAM). It will prevent (when Off) to categorize UAM as basal. - - Note: if you have at least one hour of Carbs absorption detected during one day, then all data categorized as "UAM" will be categorized as basal, whatever this setting (On or Off) -- Number of days of data (default 5): You can define default value with this setting. Each time your select a new profile in Autotune plugin, Tune days parameter will be replaced by this default value -- Apply average result in circadian IC/ISF (default Off): see [Circadian IC or ISF profile](#circadian-ic-or-isf-profile) below. - -### Other settings - -- Autotune also uses Max autosens ratio and Min autotsens ratio to limit variation. You can see and adjust these values in Config Builder > Sensitivity detection plugin > Settings > Advanced Settings - - ![Autotune default screen](../images/Autotune/Autotune_12.png) - - - -## Advanced feature - -### Circadian IC or ISF profile - -- If you have important variation of IC and/or you ISF in your profile, and you fully trust in your circadian time and variation, then you can set "Apply average result in circadiant IC/ISF" - - - Note that Autotune calculation will always be done with a single value, and circadian variation will not be tuned by Autotune. This setting only apply average variation calculated for IC and/or ISF on your circadian values - -- See on screenshot below Tuned profile with Apply average variation Off (on the left) and On (on the right) - - ![Autotune default screen](../images/Autotune/Autotune_13.png) - - - -### Tune specific days of the week - -- If you click on the checkbox with the eye on the right of "Rune days" parameter, you will see the day selection. You can specify which day of the week should be included in Autotune calculation (in screenshot below you can see an example for "working days" with Saturday and Sunday removed from autotune calculation) - - If the number of day included in Autotune calculation is lower than the number of Tune days, then you will see how many days will be included on the right of Tune days selector (10 days in the example below) - - This setting gives good results only if the number of remaining days is not to small (for example if you Tune a specific profile for week end days with only Sunday and Saturday selected, you should select a minimum of 21 or 28 Tune days to have 6 or 8 days included in Autotune calculation) - -![Autotune default screen](../images/Autotune/Autotune_14b.png) - -- During Autotune calculation, you can see the progress of the calculations ("Partial result day 3 / 10 tuned" on example below) - - ![Autotune default screen](../images/Autotune/Autotune_15b.png) - -## Run Autotune with an automation rule - -First step is to define correct trigger for an automation rule with Autotune: - -Note: for more information on how to set an automation rule, see [here](./Automation.rst). - -- You should select Recurring time trigger: only run Autotune once per day, and autotune is designed to be runned daily (each new run you shift one day later and quickly profile modification should be tiny) - - ![Autotune default screen](../images/Autotune/Autotune_16.png) - -- It's better at the beginning to run Autotune during the day to be able to check results. If you want to run Autotune during the night, you have to select in the trigger 4AM or later to include current day in next Autotune Calculation. - - ![Autotune default screen](../images/Autotune/Autotune_17.png) - -- Then you can select "Run Autotune" Action in the list - - ![Autotune default screen](../images/Autotune/Autotune_18.png) - -- You can then select Autotune Action to adjust parameters for your run. Default parameters are "Active Profile", default Tune days value defined in Autotune Plugin preferences, and All days are selected. - - ![Autotune default screen](../images/Autotune/Autotune_19b.png) - -- After a few days, if you fully trust Autotune results and percentage of modification is low, you can modify [Autotune settings](#autotune-plugin-settings) "Automation Switch Profile" to enabled to automatically update and activate profile tuned after calculation. - -Note: if you want to automatically tune profiles for specific days of the week (for example a profile for "Weekend days" and another one for "Working days"), then create one rule for each profile, select the same days in Trigger and in Autotune Action, Tune days must be high enough to be sure tuning will be done with at least 6 or 8 days, and don't forget to select time after 4AM in trigger... - -- See below an example of rule to tune "my profile" on all "Working days" with 14 Tune days selected (so only 10 days included in autotune calculation). - -![Autotune default screen](../images/Autotune/Autotune_20b.png) - - - -## Tips and trick's - -Autotune works with information existing in your database, so if you just installed AAPS on a new phone, you will have to wait several days before being able to launch Autotune with enough days to get relevant results; - -Autotune is just an help, it's important to regularly check if you agree with calculated profile. If you have any doubt, change Autotune settings (for example the number of days) or copy results in local profile and adjust profile before using it. - -Always use Autotune several days manually to check results before applyling them. And it's only when you fully trust Autotune results, and when variation becomes tiny between previous profile and calculated profile than you start to use Automation (Never before) - -- Autotune can work very well for some users and not for others, so **If you don't trust Autotune result, don't use it** - -It's also important to analyse Autotune results to understand (or try to understand) why Autotune propose these modifications - -- you can have a whole increase or decrease of the strength of your profile (for example increase of total basal associated to decrease of ISF and IC values). it could be associated to several following days with autosens correction above 100% (more agressivity required) or below 100% (you are more sensitive) -- Sometimes Autotune propose a different balance between basal rates and IC/ISF (for ex lower basal and more aggressive IC/ISF) - -We advise to not use Autotune in the following cases: - -- You don't enter all your carbs - - If you don't enter carbs correction for an hypoglycemia, Autotune will see an unexcepted increase of your BG value and will increase your basal rates the ' hours earlier, it could be the opposite of what you need to avoid hypo, especially if it's in the middle of the night. That's why it's important to enter all carabs especially correction for hypo. -- You have a lot of period with UAM detected during the day. - - Do you have entered all your carbs and correctly estimated your Carbs ? - - All UAM periods (except if you enter no carbs during a day and categorized UAM as basal is disabled), all your UAM periods will be categorized as basal, this can increase a lot your basal (much more than necessary) - -- Your carbs absorption is very slow: if most of your carbs absorption are calculated with min_5m_carbimpact parameter (you can see these periods with a little orange dot in the top of COB curve), the calculation of COB could be wrong and leads to wrong results. - - We you practice sport, you are generally more sensitive and your BG doesn't rise a lot, so during or after an exercice, it's usual to see some periods with slow carbs. But if you have too often unexpected slow carb absorption, then you may need a profile adjustment (higher value of IC) or a min_5m_carbimpact a bit to high. -- You have a "very bad days", for example stuck several hours in hyperglycemia with a huge amount of insulin to be able to go down within the range, or after a sensor change you got long periods of wrong BG values. -- If the percentage of modification is too important - - You can try to increase the number of days to get smoother results \ No newline at end of file diff --git a/docs/CROWDIN/sk/Usage/making-sport-with-AAPS.md b/docs/CROWDIN/sk/Usage/making-sport-with-AAPS.md deleted file mode 100644 index 79d2f1c38223..000000000000 --- a/docs/CROWDIN/sk/Usage/making-sport-with-AAPS.md +++ /dev/null @@ -1,185 +0,0 @@ -# making sport with AAPS - -In this section we want to address the topic of sport with AAPS. - -The aim is to show you how AAPS can help you to continue doing your favorite sport more easily or even to start doing it. It is relatively common for new type 1 diabetics to ask whether exercise is still possible for them, even if the answer in the training courses is actually a clear yes. Exercise is not only good for healthy people, but also for type 1 diabetics and even moderate exercise can even help to stabilize the blood sugar curve overall. - -:::{admonition} consult with your diabetes team after reading - -::: - -The difficulty here is that the prerequisites that someone brings with them and the expectations of what sport means to them are very different. - -Since we can assume that experienced top athletes with T1D who use AAPS are unlikely to look it up here, we deliberately set the bar low for ourselves when writing and for you when reading and using it, so that as many people as possible can benefit from it. - -Since even sport as a category is far too imprecise, as the effects of endurance sports differ greatly from strength training, for example, we are trying to break it down by type of sport. - -To be concrete and give you something you can test yourself we arrange the explanaiton around a concrete example and explain to you they action, reactions and effects. - -:::{admonition} more examples wanted - -The focus should always be on how others can do sport and not on the top performance someone has achieved. - -It's really about the basics. Your experience, which you share here, can help others to pursue their beloved sport more quickly and successfully and is therefore important. -::: - -## Cycling - -:::{admonition} take a friend with you - at least on your first trials -:class: information -A gerneral very good idea can be to take a good friend with you on the first rides. -This is especially important if you are not experienced in T1D. -Always keep in mind please: arrival comes before speed! Safety for you and the others in road traffic is very, very important. -::: - -### Example - -Let's take about 60 minutes of cycling on a flat route with a moderate heart rate as an example. - -1. we take a flat route in order to have an even load for the first exercise. This is not about performance, but purely about learning how you should react to changes in blood glucose. -2. we take the heart rate as an indicator of the load, as it is easy to see whether you are under load or not. -3. we set ourselves the goal of doing a relaxed lap around the neighborhood and focus on staying within our target range during the lap. In my case, this would be 70 <= x <= 180 mg/dl. - -We **don't** take the speed, as this is heavily dependent on personal physical conditions as well as the bike and surface used. It is therefore not very meaningful. - -You should know from the diabetes training courses you have attended that during endurance sports cycling, the insulin active in the body works significantly better than during times without physical exertion. The insulin active in the body is referred to as insulin on board (IoB). It is our most important parameter when cycling with T1D. - -We try to keep the IoB as low as possible at the start and during exercise. IoB should be around 0 or even slightly negative. You can get it there by not eating 3-4 hours before exercise. In the beginning it can also be helpful to exercise in the morning before breakfast, as with the right profile you should always have around 0 for IoB in the morning. - -AAPS shows us the IoB value on the home screen on the left under the blood glucose value. - -![IoB](../images/cycling_20240104-174035.png) - -:::{admonition} ignoring the IoB rule increases the risk for roller coaster BG dramatically -:class: danger -If you ignore this rule, you can still go cycling, but it will be much more difficult to keep your blood sugar levels in balance, so it is better to save this for later tests after several successful simple tests. -::: - -As you should know from the diabetes training courses, you should reduce the basal rate during exercise. The factor is individual. I have found a value of 50% in tests to be suitable for me. - -In AAPS, you should therefore change your profile to 50% before exercise and keep it active until the end of exercise. Some people even do it a certain amount of time before, e.g. 1 hour. Unfortunately, the pre-run is also individual. We will come to the post-run later. - -You should use two carbohydrates during exercise. - -1. medium-fast carbohydrates for the insulin still in the body and -2. very fast carbohydrates to prevent slipping into a hypo. - -For medium-fast carbohydrates, I treat myself to cookies or a banana before exercise, for example. You can also use something else that is more suitable for you. -For very fast carbohydrates, I take 3 teaspoons of dissolved glucose per 100 ml of still water in a 500 ml water bottle on my bike. If I'm cycling longer distances, I take a larger bottle with me and, if necessary, packaged glucose to refill the bottle. I add a little lemon juice for flavor. You can also use something other than lemon juice for the taste. You shouldn't change anything about the dextrose, as dissolved dextrose raises blood sugar levels super quickly. If you only take it in sips, your blood sugar won't go super high either! You can also do this tip at home beforehand as a dry run and see how quickly the change shows up on the CGMS. - -Why do I place so much emphasis on fast carbohydrates? - -1. once you are in a slight hypo, you may get back into the normal range by drinking the dextrose solution. As a rule, however, the oscillation of the curve then begins, which leads to a rollercoaster ride of the blood sugar. You may even be able to keep this within your target range, but you must be constantly vigilant. Without a hypo it is simply the most stable. -2. if you even slip into a somewhat severe hypo (without the need for outside help, of course), you may even have to pause briefly to avoid getting stuck in the hypo. - With both hypos, there is a risk that you will be tempted to switch from drinking 2-3 sips at a time to larger quantities. Not too bad at first, until the oscillation sets in and pushes you into a hyper. You can correct this, but your blood sugar will most likely go on a rollercoaster ride. - -What else is helpful, but not absolutely necessary? -It is important to keep an eye on your blood sugar, as your blood sugar can change enormously (e.g. 30 - 50 mg/dl) within 15 minutes of riding and a little more IoB or a basal rate that is still too high. The best way to keep an eye on it is if it is visible on the handlebars or if it is also displayed on your watch. It is even possible to install an additional app on some Garmin GPS bike computers that displays the blood glucose from XDrip or Nightscout as a data field on the bike computer. The additional app was developed by Andreas May from the T1D community. It is available free of charge in the official connect IQ Store. Certainly an interesting option for riders interested in sports. - -[Link to Andreas May Data Field App on connect IQ store](https://apps.garmin.com/de-DE/apps/5a3e2cda-12f0-4afd-88ed-000e67a68d84) - -Here is a picture of my Garmin Edge 530 bike computer with map, blood sugar and heart rate. - -![Garmin Edge 530 with BG data field](../images/cycling_IMG_1087.jpeg) - -After you have eaten the medium fast carbohydrates (24 - 36 g I take) and the blood sugar is above 100 mg/dl but also below 160 mg/dl, I carry out the profile change to 50% and set the activity temp target. - -:::{admonition} disable SMBs during high temp targets if necessary -:class: danger -Attention: If you prefer not to receive SMBs during the sport, please disable the option "Enable SMB with hight temp targets" in the settings of SMB or DynIFS Plugin. -::: - -The following picture shows the start and end of the sport. The end was specified as the duration when the profile was changed at the start. - -The temporary profile change has the following effects - -1. for a period of 60 minutes -2. a reduction to 50% of the profile and -3. the target is raised by clicking on the Activity Target option, which may have the side effect of disabling the SMBs - see above. - -![profile switch with temp target](../images/cycling_20240104-174056.png) - -The second image shows that the start at IoB was started towards 0. - -![IoB around 0](../images/cycling_20240104-174111.png) - -If the blood sugar drops faster than 15 mg/dl in 5 minutes or if it is at 120 mg/dl and tends to fall, I drink 1-2 sips of dissolved glucose. Then I wait for the next value and proceed as described above. - -You can hardly see it here, but at the beginning I took 2 sips from the bottle several times when my blood sugar started to fall. When it stabilized, I didn't need any more glucose. - -Here is the picture that illustrates this. The chart is saved on the Garmin as a result of the activity. - -![BG chart Garmin](../images/cycling_20240104-174431.png) - -If you should suddenly break out upwards, i.e. above 180 mg/dl, you should consider whether you should make a correction bolus. Caution: Remember the factor and apply it to the correction, otherwise the correction will be too strong. - -If your blood sugar drops below 80 mg/dl, take a break and drink two sips until your blood sugar is back above 100 mg/dl. - -At the end of the ride, the profile change should be finished as the time is up. - -Since we only rode easy for 60 minutes, there shouldn't be a big muscle bulking effect continuing to pull carbohydrates from your blood sugar. However, if it felt strenuous to you, keep an eye on it. This is especially true if you then go straight to bed. It may be better to change your profile to e.g. 80% for sleep. You may come out of sleep slightly too high, but it's better than having a hypo at night. Over time, you will surely find out what happens to you. - -The following pictures show the low intensity of the sport. - -The elevation profile -![](../images/cycling_20240104-174314.png) - -Speed with average and maximum speed - -![](../images/cycling_20240104-174326.png) - -Note the pause at the level crossing, which is also reflected in the heart rate. - -The heart rate. -![](../images/cycling_20240104-174337.png) - -The training effect. -![](../images/cycling_20240104-174358.png) - -The time in the different heart rate training zones. -![](../images/cycling_20240104-174423.png) - -After succesfully mastering this simple example you could go for further targets by stretching - -1. the distance and time -2. the load during the ride -3. the elevation during the right which should make a big impact on the more necessary carbs or further reduction of IoB and percentage of profile switch. - -Based on my experiences I would not expect to come back 100% with time in range over the whole and every ride. - -### Tipps - -I already gave some tipps for during the ride above. - -Here are some further tipps what can go wrong and how you can act to prevent it or react to compensate it. - -#### sky rocket high after ride - -During the ride everything was fine but after siting down and relax the blood sugar go sky rocket high. - -**Possible reason:** This happens when you have drunk too much dissolved glucose. - -**Reaction:** Drink 500 ml water, go to the shower and then control again. Latest after 30 minutes think about giving a correction bolus but be careful when it is short for bed time. Therefore it can be very good to make the first try runs on weekend mornings. - -**Action:** Next time be a bit more cautious in drinking from the dissolved glucose. - -#### hypo during ride - -During the ride you are going into hypo and can't recover your blood sugar during cycling. - -**Possible reason:** Your body cannot absorb enough carbohydrates quickly enough during exercise. - -**Reaction:** Take a rest and corrrect your blood sugar with drinking dissolved glucose. Stay calm: arrival comes before speed. - -**Action:** Did you started with IoB near 0? Have you eaten a small amount of middle fast carbs? Can you increase this or are the not fast enough for your body? Is it possible to prevent going into hypo by reducing the factor for the profile switch? Have you disbaled SMBs during ride as explained above? - -#### sky rocket high during ride - -During the ride your blood sugar goes sky rocket high. - -**Possible reason:** You have got taken too much carbs for your IoB at that time. Beneath for sure the typical technical problems with your -insulin pump like leakage or blockage of the catheder! - -**Reaction:** If it is too high for you take a rest and correct with a bolus. Keep in mind that you must ride home and therefore make it carefully. Drink 500 ml pure water without carbs. Stay calm: arrival comes before speed. - -**Action:** Have you eaten too much? Especially have you drunk too much from the dissolved glucose during the ride? Is your percentage of reduction the profile during profile switch too low and you can increase this? diff --git a/docs/CROWDIN/sk/buildingAAPS.md b/docs/CROWDIN/sk/buildingAAPS.md deleted file mode 100644 index 98164a09e49b..000000000000 --- a/docs/CROWDIN/sk/buildingAAPS.md +++ /dev/null @@ -1,28 +0,0 @@ -# Dummy - -## This is a dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - - -## This is another dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - - -## This is another another dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - diff --git a/docs/CROWDIN/sk/completingObjetives.md b/docs/CROWDIN/sk/completingObjetives.md deleted file mode 100644 index 98164a09e49b..000000000000 --- a/docs/CROWDIN/sk/completingObjetives.md +++ /dev/null @@ -1,28 +0,0 @@ -# Dummy - -## This is a dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - - -## This is another dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - - -## This is another another dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - diff --git a/docs/CROWDIN/sk/dummy.md b/docs/CROWDIN/sk/dummy.md deleted file mode 100644 index 98164a09e49b..000000000000 --- a/docs/CROWDIN/sk/dummy.md +++ /dev/null @@ -1,28 +0,0 @@ -# Dummy - -## This is a dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - - -## This is another dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - - -## This is another another dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - diff --git a/docs/CROWDIN/sk/intro.md b/docs/CROWDIN/sk/intro.md deleted file mode 100644 index 153998cb2262..000000000000 --- a/docs/CROWDIN/sk/intro.md +++ /dev/null @@ -1,291 +0,0 @@ -![20-06-23v2 AAPS simple overview-cropped](https://github.com/openaps/AndroidAPSdocs/assets/94044064/e505b73b-09a0-42a4-a1ab-b830a0741234) - -# Introduction to APS and AAPS - -## What is an “Artificial Pancreas System”? - -A human pancreas does a lot of things besides regulating blood sugar. However, the term **“Artificial Pancreas System” (APS)** usually refers to a system which works to automatically keep blood sugar levels within healthy limits. - -The most basic way to do this is by detecting **glucose levels**, using these values to do **calculations**, and then delivering the (predicted) right amount of **insulin** to the body. It repeats the calculation, every few minutes, 24/7. It uses **alarms** and **alerts** to inform the user if intervention or attention is needed. This system is typically made up of a **glucose sensor**, an **insulin pump** and an **app** on a phone. - -You can read more about the different artificial pancreas systems currently in use and in development in this 2022 review article: - -![Frontiers](./images/FRONTIERS_Logo_Grey_RGB.png) [Future Directions in Closed-Loop Technology](https://www.frontiersin.org/articles/10.3389/fendo.2022.919942/full#:~:text=Fully%20closed%2Dloop%20systems%2C%20unlike,user%20input%20for%20mealtime%20boluses). - -In the near future, some so-called "dual-hormone" systems will also have the ability to infuse glucagon alongside insulin, with the aim of preventing severe hypos and allowing even tighter blood glucose control. - -An artificial pancreas can be thought of as an [“autopilot for your diabetes”]. (https://www.artificialpancreasbook.com/) What does that mean? In an aircraft, an autopilot does not do the complete job of the human pilot, the pilot cannot sleep through the entire flight. The autopilot aids the work of the pilot. It relieves them of the burden of permanently monitoring the aircraft, allowing the pilot to concentrate on wider monitoring from time to time. The autopilot receives signals from various sensors, a computer evaluates them together with the pilot’s specifications and then makes the necessary adjustments, alerting the pilot to any concerns. The pilot no longer has to worry about constantly making decisions. - -## What does hybrid closed loop mean? - -The best solution for type 1 diabetes would be a “functional cure” (probably an implant of pancreatic cells which are protected from the immune system). While we are waiting for that, a “full closed loop” artificial pancreas is probably the next best thing. This is a tech system that doesn’t need any user input (like bolusing insulin for meals, or announcing exercise), with good regulation of blood glucose levels. At the moment, there are no widely available systems which are “full” closed loop, they all need some user input. The currently available systems are called “hybrid” closed loop, because they use a combination of automated technology and user input. - -## How and why did looping start? - -The development of commercial technology for people with type 1 diabetes (T1D) is very slow. In 2013 the T1D community founded the #WeAreNotWaiting movement. They developed systems themselves using existing approved technology (insulin pumps and sensors) to improve blood glucose control, safety, and quality of life. These are known as DIY (do-it-yourself) systems, because they are not formally approved by health bodies (FDA, NHS etc). There are four main DIY systems available: OpenAPS, **AAPS**, Loop and iAPS. - -A great way to understand the fundamentals of DIY looping is to read Dana Lewis’s book “Automated Insulin Delivery”. You can access it \[here\] (https://www.artificialpancreasbook.com/) for free (or buy a hardcopy of the book). If you want to understand more about OpenAPS, which** AAPS** has developed from, the \[OpenAPS website\] (https://openaps.org/what-is-openaps/) is also a great resource. - -Several commercial hybrid closed loop systems have been launched, the most recent of which are \[CamAPS FX\] (https://camdiab.com/) (UK and EU) and \[Omnipod 5\] (https://www.omnipod.com/en-gb/what-is-omnipod/omnipod-5) (USA and EU). These are very different to DIY systems, mainly because they both include a “learning algorithm” which adjusts how much insulin is delivered according to your insulin needs from previous days. Many people in the DIY community have already tried out these commercial systems and compared them with their DIY system. You can find out more about how the different systems compare by asking on the dedicated Facebook groups for these systems, on the \[AAPS Facebook group\] (https://www.facebook.com/groups/AndroidAPSUsers/) or on \[Discord\] (https://discord.com/invite/4fQUWHZ4Mw). - -## What is Android APS (AAPS)? - -![image](https://github.com/openaps/AndroidAPSdocs/assets/94044064/0f089d96-b7ee-452a-aa9d-aae10ab58971) - -**Figure 1**. Basic outline of the Android APS (Artificial Pancreas System), AAPS. - -Android APS (AAPS) is a hybrid closed loop system, or Artificial Pancreas System (APS). It makes its insulin dosing calculations using established \[OpenAPS\] (https://openaps.org/) algorithms (a set of rules) developed by the #WeAreNotWaiting type 1 diabetes community. - -Since OpenAPS is only compatible with certain older insulin pumps, AAPS (which can be used with a wider range of insulin pumps) was developed in 2016 by Milos Kozak, for a family member with type 1 diabetes. Since those early days, **AAPS** has been continually developed and refined by a team of volunteer computer developers and other enthusiasts who have a connection to the type 1 diabetes world. Today, **AAPS** is used by approximately 10,000 people. It is a highly customisable and versatile system, and because it is open-source, it is also readily compatible with many other open-source diabetes softwares and platforms. The fundamental components of the current **AAPS** system are outlined in Figure 1 above. - -## What are the basic components of AAPS? - -The “brain” of AAPS is an **app** which you build yourself. There are detailed step-by-step instructions for this. You then install the **AAPS app** on a compatible **Android smartphone** (1). A number of users prefer their loop on a separate phone to their main phone. So, you don’t necessarily have to be using an Android phone for everything else in your life, just for running your AAPS loop. - -The **Android smartphone** will also need to have another app installed on it as well as **AAPS**, either a modified Dexcom app called build-your-own dexcom app (**BYODA**) or Xdrip+. This receives glucose data from a sensor (2) by bluetooth, and then sends the data internally on the phone to the **AAPS app**. - -The **AAPS app** uses a decision making process (**algorithm**) from OpenAPS. Beginners start out using the basic **oref0** algorithm, but it is possible to switch to using the newer **oref1** algorithm as you progress with AAPS. Which algorithm you use (oref0 or oref1), depends on which suits your specific situation best. In both cases, the algorithm takes into account multiple factors, and performs rapid calculations every time a new reading comes in from the sensor. The algorithm then sends instructions to the insulin pump (3) on how much insulin to deliver by bluetooth. All the information can be sent by mobile data or wifi to the internet. This data can also be shared with followers if desired, and/or collected for analysis. - -## What are the advantages of the AAPS system? - -The OpenAPS algorithm used by **AAPS** controls blood sugar levels in the absence of user input, according to the users’ defined parameters (important ones being basal rates, insulin sensitivity factors, insulin-to-carb ratios, duration of insulin activity etc.), reacting every 5 minutes to the new sensor data. Some of the reported advantages of using AAPS are extensive fine-tunable options, automations and increased transparency of the system for the patient/caregiver. This can result in better control over your (or your dependent’s) diabetes, which in turn may give improved quality of life and increased peace of mind. - -Practical advantages include: - -- **Hardware flexibility**: **AAPS** works with a wide range of insulin pumps and sensors. So for example, if you develop an allergy to Dexcom sensor patch glue, you could switch to using a Libre sensor instead. That offers flexibility as life changes. You don't have to rebuild, just tick a different box in the AAPS app to change your hardware. - -- **Highly customisable with wide parameters**: here are some examples of the possibilities with AAPS: a) The ability to set a lower glucose target 30 min before eating; you can set the target as low as 72 mg/dL (4.0 mmol/L). b) If you are insulin-resistant resulting in high blood sugars, **AAPS** allows you to set an **automation** rule to activate when BG rises above 8 mmol/L (144 mg/dL), switching to a 120% profile (resulting in an 20% increase in basal and strengthening of other factors too, compared to your normal **profile** setting). The automation will last according to the scheduled time you set. Such an automation could be set to only be active on certain days of the week, at certain times of day, and even at certain locations. c) If your child is on a trampoline with no advance notice, **AAPS** allows insulin suspension for a set time period, directly via the phone. d) After reconnecting a tubed pump which has been disconnected for swimming, AAPS will calculate the basal insulin you have missed while disconnected and deliver it carefully, according to your current BG. Any insulin not required can be overridden by just “cancelling” the missed basal. f) **AAPS** has the ability to set different profiles for different situations and easily switch between them. Features which make the algorithm quicker to bring down elevated BG (like supermicro boluses (“SMB”), unannounced meals, (“**UAM**”) can be set to only work during the daytime, if you are worried about night-time hypos. - - -These are all examples, the full range of features gives huge flexibility for daily life including sport, illness, hormone cycles etc. Ultimately, it is for the user to decide how to use this flexibility, and there is no one-size-fits-all automation for this. - -- **Remote monitoring**: there are multiple possible monitoring channels (Sugarmate, Dexcom Follow, Xdrip+, Android Auto etc.) which are useful for parents/carers and adults in certain scenarios (sleeping/driving) who need customisable alerts. In some apps (Xdrip+) you can also turn alarms off totally, which is great if you have a new sensor “soaking” or settling down that you don’t want to loop with yet. - -- **Remote control**: a significant advantage of **AAPS **over commercial systems is that it is possible for followers, using authenticated text (SMS) commands or via an app (Nightscout or NSClient) to send a wide range of commands back to the ****AAPS** **system. This is used extensively by parents of kids with type 1 diabetes who use AAPS. It is very useful in the playground, for example, if you want to pre-bolus for a snack from your own phone, and your child is busy playing. It is possible to monitor the system (e.g. Fitbit), send basic commands (e.g. Samsung Galaxy watch 4), or even run the entire AAPS system from a high-spec smartwatch (5) (e.g. LEMFO LEM14). In this last scenario, you don’t need to use a phone to run AAPS. As battery life on watches improves, this last option is likely to become increasingly attractive. - -- **No commercial constraints due to open application interfaces**: beyond the use of an open source approach, which allows the source code of **AAPS** to be viewed at any time, the general principle of providing open programming interfaces gives other developers the opportunity to contribute new ideas that allow users to live more easily with their diabetes. This is complementary to commercial systems which adopt the innovations from DIY, where interfaces are only made possible in return for licensing, thus preventing innovations in particular that are not-for-profit. Good examples for such integrations are NightScout, Nightscout Reporter, Xdrip+ M5 stack etc. - -- **Detailed app interface**: It is easy to keep track of things like: insulin levels, cannula age, sensor age, pump battery age, and many actions can be done through the **AAPS** app (priming the pump, disconnecting the pump etc.), instead of on the pump itself. - -- **Accessibility and affordability**: **AAPS** gives people who currently can’t afford to self-fund, or don’t have funding/insurance, access to a world-class hybrid closed looping system which is conceptually years ahead, in terms of development, of the commercial systems being offered by clinics. You currently need to have a Nightscout account to set up **AAPS**. Although the Nightscout account it not necessarily required after setup, many people continue to use Nightscout for collecting their data, and for remote control. So, although **AAPS **itself is free, setting up Nightscout through one of the various platforms may incur a fee (E0 - E12), depending on what level of support you want (see comparison table). **AAPS** works with a wide range of affordable (starting from approx E150) Android phones. In comparison, Loop currently costs around $80 a year for the Apple development licence and CamAPS FX costs around E80/month (as at 2023). - -- ****Support**: No automated insulin delivery system is perfect. Commercial and open-source systems share many common glitches in both communications and temporary hardware failure. There is a community of AAPS users on both Facebook and Discord and Github who designed, developed and are currently using **AAPS** all over the world. There are Facebook support groups and help from clinic/commercial companies for the commercial APS systems - it is worth speaking to the users, or former users of these systems to get feedback on the common glitches, the quality of the education programme and the level of ongoing support provided. - -- **Predictability, transparency and safety**: with no learning algorithm, **AAPS** is logical and in some respect, more predictable, which may make it easier to know when a setting is wrong, and to adjust it accordingly. You can see exactly what the system is doing, why it is doing it, and set its operational limits, which puts the control (and responsibility) in your hands. This can provide the user with confidence, and a sounder sleep. - -- **Access to advanced features through dev modes including full closed loop**: **AAPS **documentation focuses on the mainstream **“master”** branch of **AAPS**, however, research and development is going on all the time. More experienced users may wish to explore the experimental features in the **development** branch such as integration of Dexcom G7, and automatically adjusting insulin delivery according to short-term sensitivity changes (DYNISF), not having to bolus for meals, and generally trying to make life with type 1 diabetes as convenient as possible. - -- **Ability to contribute yourself to further improvements**: type 1 diabetes can be highly frustrating and isolating. Having control over your own diabetes tech, with the possibility to “pay it forward” as soon as you are making progress by helping others on their journey can be really rewarding. You can educate yourself, discover the roadblocks and look for and even contribute to new developments and the documentation. There will be others with the same quest to bounce ideas off and work with. This is the essence of #WeAreNotWaiting. - - -## How does AAPS compare to MDI and open looping? - -Multiple daily injections (MDI, a) usually involve giving an injection of a long-lasting insulin (e.g. Tresiba) once a day, with injections of faster-acting insulin (e.g. Novorapid, Fiasp) at mealtimes, or for corrections. Open pumping (b) involves using a pump to deliver basal at pre-programmed rates of rapid-acting insulin, and then boluses through the pump at mealtimes or for corrections. The basics of a looping system is that the App uses the glucose data to instruct the pump to stop insulin delivery when it predicts you are heading for a low, and to give you extra insulin if your glucose levels are rising and predicted to go too high (c). Although this is oversimplified, (mostly because hybrid closed looping has a lot of additional useful features) the key features of each system are shown in **Figure 2**. - -![image](https://github.com/openaps/AndroidAPSdocs/assets/94044064/4e7d8608-684d-4c69-9c61-88c9539f5d6f) - -**Figure 2**. Overview of (a) MDI, (b) open-loop pumping and (c) hybrid closed loop pumping - -## How does AAPS compare to other looping systems? - -At present there are four major open source closed loop systems available: OpenAPS, **AAPS**, \[Loop\] (https://loopkit.github.io/loopdocs/#what-is-loop) and iAPS, (formerly FreeAPS X). The features of the different systems are shown in the table below: - -| Devicestyp | Name | [Open APS](https://openaps.readthedocs.io/en/latest/) | [AAPS](https://wiki.aaps.app) | [Loop](https://loopkit.github.io/loopdocs/) | [iAPS](https://iaps.readthedocs.io/en/latest/) | -| ---------- | -------------------------------------------------------------------------------------------------------- | ----------------------------------------------------- | ------------------------------------------- | ------------------------------------------- | ---------------------------------------------- | -| PUMP | Older Medtronic | ![available](./images/available.png) | ![available](./images/available.png) | ![available](./images/available.png) | ![available](./images/available.png) | -| PUMP | Older Omnipod (Eros) | ![unavailable](./images/unavailable.png) | ![available](./images/available.png) | ![available](./images/available.png) | ![available](./images/available.png) | -| PUMP | Newer Omnipod (Dash) | ![unavailable](./images/unavailable.png) | ![available](./images/available.png) | ![available](./images/available.png) | ![available](./images/available.png) | -| PUMP | DANA R, DANA RS, DANA I | ![unavailable](./images/unavailable.png) | ![available](./images/available.png) | ![unavailable](./images/unavailable.png) | ![unavailable](./images/unavailable.png) | -| PUMP | Roche Combo, Insight | ![unavailable](./images/unavailable.png) | ![available](./images/available.png) | ![unavailable](./images/unavailable.png) | ![unavailable](./images/unavailable.png) | -| CGM | Dexcom G4, G5, G6 | ![available](./images/available.png) | ![available](./images/available.png) | ![available](./images/available.png) | ![available](./images/available.png) | -| CGM | Libre 1 (requires Miao Miao) | ![available](./images/available.png) | ![available](./images/available.png) | ![available](./images/available.png) | ![available](./images/available.png) | -| CGM | Libre 2 | ![available](./images/available.png) | ![available](./images/available.png) | ![available](./images/available.png) | ![available](./images/available.png) | -| CGM | Libre 3 | | ![unavailable](./images/unavailable.png) | --- | ![unavailable](./images/unavailable.png) | -| CGM | Medtronic Enlite | | --- | ![unavailable](./images/unavailable.png) | --- | -| CGM | [Dexcom G7](https://androidaps.readthedocs.io/en/latest/Hardware/DexcomG7.html) | | ![available](./images/available.png) (beta) | ![available](./images/available.png) | ![available](./images/available.png) | -| CGM | [Eversense](https://androidaps.readthedocs.io/en/latest/Hardware/Eversense.html) | | ![available](./images/available.png) | | ![available](./images/available.png) | -| CGM | [MM640g/MM630g](https://androidaps.readthedocs.io/en/latest/Hardware/MM640g.html) | | ![available](./images/available.png) | | ![available](./images/available.png) | -| CGM | [PocTech](https://androidaps.readthedocs.io/en/latest/Hardware/PocTech.html) | | ![available](./images/available.png) | | ![available](./images/available.png) | -| CGM | [Nightscout as BG Source](https://androidaps.readthedocs.io/en/latest/Hardware/CgmNightscoutUpload.html) | | ![available](./images/available.png) | | ![available](./images/available.png) | -| Phone | Android | ![available](./images/available.png) | ![available](./images/available.png) | ![unavailable](./images/unavailable.png) | ![unavailable](./images/unavailable.png) | -| Phone | iPhone | ![available](./images/available.png) | ![unavailable](./images/unavailable.png) | ![available](./images/available.png) | ![available](./images/available.png) | - -[OpenAPS](https://openaps.readthedocs.io/) was the first Open Source Closed Loop System. Používa malý počítač ako Raspberry Pi alebo Intel Edison. Both AndroidAPS (AAPS) and iAPS use the OpenAPS algorithms, whereas Loop uses a separate algorithm. You can read a comparison of iAPS and **AAPS** here. - -An international peer-reviewed consensus statement containing practical guidance on open source looping was written by and for health-care professionals, and published in a leading medical journal in 2022. It is well worth a read (including for your diabetes clinic) and summarises the main technical differences between the different open-source hybrid closed loop systems: - - Lancet Diabetes Endocrinol, 2022; 10: 58–74 - -[https://www.ncbi.nlm.nih.gov/pmc/articles/PMC8720075/](https://www.ncbi.nlm.nih.gov/pmc/articles/PMC8720075/) - -It is hard to get a “feel” for any system without using it, or talking to others who are using it, so do reach out to others on Facebook/Discord and ask. Most people find that AAPS is incredibly sophisticated in comparison to other hybrid closed loop systems (particularly the commercial systems), with a huge number of potentially customisable settings and features, discussed above. Some people can find this a little overwhelming in the beginning, but there is no rush to investigate all the possibilities at once, you can progress as slowly or as fast as you would like, and there is help available at every step of the way. - -## Does AAPS use artificial intelligence or any learning algorithm? - -No. **AAPS** does not have any complicated machine learning algorithms, multiple-parameter insulin response models, or differential equations. As such, the system is open and transparent in how it works, and has the ability to be understood not just by experts, but also by clinicians and patients. It also means that if you have a sharply varying schedule (maybe switching from a stressful week at work to a relaxing holiday) and are likely to need a significantly different amount of insulin, you can immediately switch **AAPS** to run a weaker/stronger profile. A ‘learning system’ will do this adjustment for you automatically, but is likely to take longer to adjust the insulin delivery. - -## Which system is right for me or my dependent? - -Practically, your choice of system is often restricted by which pump you already have, or can obtain from your medical provider, and your choice of phone (Apple or Android). If you don’t yet have a pump you have the biggest choice of systems. Technology is continually evolving, pumps are being discontinued and new pumps and sensors are being released. Most open-source systems work with the main sensors (Libre and Dexcom) or are quickly adapted to work with new sensors a year or so after they are released (with a bit of time delay for safety and stability testing). - -Most **AAPS **users report more time in range, HbA1c reductions, as well as quality of life improvements from having a system that can auto-adjust basal rates overnight during sleep, and this is true for most hybrid closed loop APS. Some people have a preference for a very simple system which is not very customisable (which means you may prefer a commercial system), and others find this lack of control very frustrating (you may prefer an open-source system). If you (or your dependent) are newly diagnosed, a common route is to get the hang of MDI plus sensor first, then progress to a pump which has the potential for looping, then to **AAPS**, but some people (especially small kids) may go straight to a pump. - -It is important to note that the **AAPS** user needs to be proactive to troubleshoot and fix problems themselves, with help from the community. This is a very different mindset to that when using a commercial system. With **AAPS** a user has more control, but also the responsibility, and needs to be comfortable with that. - -## Is it safe to use open-source systems like AAPS? - -A more accurate question is probably “is it safe compared to my current type 1 diabetes insulin delivery system?” since no method of insulin delivery is without risk. There are many checks and balances in place with **AAPS**. A recent paper looked at the use of**** AAPS ****in a computer simulated set-up, [https://www.liebertpub.com/doi/epub/10.1089/dia.2019.0375](https://www.liebertpub.com/doi/epub/10.1089/dia.2019.0375) which was an effective way to unobjectively trial how safe and effective the system is. More generally, it is estimated that over 10,000 individuals worldwide are using open-source automated-insulin delivery systems, and uptake continues to increase globally. - -Any device that uses radio communications could be hacked, and this is true for a non-looping insulin pump as well. Currently, we are not aware of anyone attempting to harm individuals by hacking their diabetes-related medical equipment. However, there are multiple ways to protect against such risks: - -1. In the pump settings, limit both the max bolus allowed and max temporary basal settings to amounts that you believe are safest. These are hard limits that we do not believe any malicious hacker could circumvent. - -2. Set your CGM alarms enabled for both highs and lows. - -3. Monitor your insulin delivery online. Nightscout users can set additional alarms to alert for a wide variety of conditions, including conditions that are much more likely to occur than a malicious attack. In addition to highs and lows, Nightscout can display diagnostic data useful for verifying that the pump is operating as desired, including current IOB, pump temporary basal history, pump bolus history. It can also be configured to proactively alert users to undesirable conditions, such as predicted highs and lows, low insulin reservoir, and low pump battery. - - -If a malicious attack was made on your insulin pump, these strategies would significantly mitigate the risk. Every potential **AAPS** user needs to weigh the risks associated with using **AAPS**, versus the risks of using a different system. - -## How can I approach discussing AAPS with my clinical team? - -Depending on the country - link to doctors section of docs - - Lancet Diabetes Endocrinol, 2022; 10: 58–74 - -[https://www.ncbi.nlm.nih.gov/pmc/articles/PMC8720075/](https://www.ncbi.nlm.nih.gov/pmc/articles/PMC8720075/) - -## Q: Why can’t I just download AAPS and use it straight away? - -The **AAPS** app is not provided in Google Play - you have to build it from source code by yourself for legal reasons. **AAPS** is unlicensed, meaning that it does not have approval by any regulatory body authority in any country. **AAPS**is deemed to be carrying out a medical experiment on yourself, and is carried out at the user’s own risk. - -Setting up the system requires patience, determination and the gradual development of technical knowledge. All the information and support can be found in these documents, elsewhere online, or from others who have already done it. It is estimated that over 2000 people have successfully built and are currently using **AAPS** worldwide. - -The developers of **AAPS**t ake safety incredibly seriously, and want others to have a good experience of using **AAPS**. That is why it is essential that every user (or carer, if the user is a child): - -- builds the AAPS system themself and works through the **objectives** so that they have reasonably good personalised settings and understand the basics of how AAPS ****works by the time they “close the loop”; - -- backs up their system by exporting and saving important files (like keystore and settings .json file) somewhere safe, so you can setup again quickly if needed; - -- updates to newer master versions as and when they become available; and - -- maintains and monitors the system to ensure it is working properly. - - -## Q: What is the connectivity of the AAPS system? - -**Figure 3 (below)** shows one example of the **AAPS** system for a user who do not require any followers interacting with the system: - -![potential AAPS connectivity setup with no followers](./images/intro03.png) - -**Figure 4 (below)** shows the full potential of the **AAPS** system for a user who has followers and requires a monitor and send adjust the system remotely (like a child with T1D): - -![potential AAPS connectivity setup with followers](./images/intro04.png) - -## Q: How does AAPS get continually developed and improved? - -Most **AAPS** users use the fully tested **master** version of AAPS, which has been tested for bugs and problems, before being released to the community. Behind the scenes, the developers try out new improvements, and test these out in “developer” (**dev**) versions of **AAPS** with a user community who are happy to do bug updates at short notice. If the improvements work well, they are then released as a new “master” version of **AAPS**. Any new master release is announced on the Facebook group, so that the mainstream **AAPS** users can read about and update to the new master version. - -Some experienced and confident **AAPS ** users conduct experiments with emerging technologies and with dev versions of the **AAPS** app, which can be interesting for the less adventurous users to read about, without having to do it themselves! People tend to share these experiments on the Facebook group too. - -You can read more about some of these experiments and discussion on emerging tech here: - -[https://www.diabettech.com/](https://www.diabettech.com/) - -[https://bionicwookie.com/](https://bionicwookie.com/) - -## Q: Who can benefit? - -| User Type | -| ------------------------------------------- | -| ✔️ type 1 diabetic | -| ✔️ caregiver or parent of a type 1 diabetic | -| ✔️ blind users type 1 diabetic | -| ✔️ *clincians and healthcare professionals | - -The above table assumes that the user has access to both continuous gluocse monitor and insulin pump. - -*All data from **AAPS** can be made available to healthcare professionals via data sharing platforms, including NightScout that provides logging and real time monitoring of CGM data, insulin delivery, carbohydrate entries, predictions and settings. Nightscout records include daily and weekly reports which can aid healthcare professionals' discussions with type 1 patients with more accurate data on glycemic control and any behavioural considerations. - -## Q: What benefits can I get? - -With investment of your time, **AAPS** can potentially lead to: - -- alleviating the stress and burden of managing type 1 diabetes; - -- reducing the multitude of mundane decisions that arise from type 1 diabetes; - -- the provision of personalised and dynamic insulin dosing based on real-time data which can cut down the need for hypo treatments and reduce hyperglycemia episodes; - -- an increased knowledge of insulin management and confidence to better fine tune your settings; - -- the ability to create automatic settings (**automations**) that are tailored to fit in with your lifestyle; - -- improved sleep quality and overall reduction in the frequency of nighttime interventions; - -- remote monitoring and administration of insulin delivery for caregivers of type 1 diabetics; and - -- streamlining of all your portable diabetic equipment (continuous glucose monitor and insulin portable devices) by replacing them with an android phone controlled by **AAPS**. - - -Ultimately,**AAPS** can empower individuals to better manage their diabetes resulting in stable blood sugars and improved long term health outcomes. - ---- - -## AAPS First Steps - -Welcome. This is an introduction to aid beginners getting started with **AAPS** (or commonly referred to as "looping"). - -## Safety - -“_With great powers comes great responsibilities…_” - -**AAPS** is designed with an extensive set of safety features with limits imposed and gradually removed with completion of the **objectives **(predominately made up of multiple choice questions). An **AAPS** feature will be unlocked as the Objectives are successfully completed. This process will gradually allow the user to migrate from Open Loop to Closed Loop. - -This has been done to achieve the best possible experience with **AAPS** in order to prevent common mistakes that new users tend to make when starting to loop. The safety parameters have been built upon typical errors and general trends **AAPS** developers have observed with new users. Mistakes can happen because the beginner is inexperienced and too eager to get started with AAPS or has overlooked the required materials. Do not worry, we have all been there! - -## Key Principles - -The key principles and concepts of looping must be understood by the user before using **AAPS**. This is achieved by investing your personal time into reading the **AAPS** documentation, and completing the Objectives which is aimed to provide you with a solid platform for safe and effective use of **AAPS**. The volume of **AAPS** documentation may seem overwhelming at first but be patient and trust the process - with the proper approach, you'll get there! The overall process will depend upon the beginner’s progress and completion of objectives can typically take between 6 to 9 weeks . - -## Plan for hiccups - -At the preliminary stages of **AAPS**, you should expect to experience some hiccups whilst trying to fine tune your settings. **AAPS**’ glitches cannot be flushed out until the system is used in everyday life. Please plan accordingly and allow a sensible amount of time to troubleshoot and resolve such issues. - -## Flexibility/Adaptability - -Success with **AAPS** requires a proactive approach, a willingness to reflect on the BG data and flexibility to make the necessary adjustments to **AAPS** in order to improve your outcomes. Just as it is nearly impossible to learn to play a sport by reading about the rules alone, the same can be said of **AAPS**. - -## Technology compatibility - -There are limitations with **AAPS** as it is accessible for only certain types of insulin pumps or CGMs, and some technology may not be available for use in various countries. In order to avoid any disappointment or frustrations, please read please read Component Set Up (Section INSERT). - -## App Build Time - -The time to build the **AAPS**(under Section INSERT) depends on your level of expertise and technical ability. Typically for inexperienced users, it can take up to half a day or a full day (with help from the community) in order to build the **AAPS**. The process will significantly speed up as you become more experienced at building the **AAPS**. To aid the build process there are sections dedicated for: -- list of questions and answers for frequent errors that are likely to occur under FAQs (Section K); -- “How to install AAPS? (Section INSERT) which includes Troubleshooting subsection. - -## Keystore & configurations settings a export file - -A “keystore” is a password encrypted file unique to your own copy of **AAPS**. Your android phone uses it to ensure that nobody else can upgrade your own copy without the keystore. In short, as part of the **AAPS** build, you should: - -- save the your keystore file (.jks file used to sign your app) in a safe place; -- keep a note of your password for your keystore file. - -By doing the above, this will ensure that you can use that exact same keystore file each time an updated version of **AAPS** is created. On average, there will be 2-3 AAPS updates required each year. - -In addition, **AAPS** provides the ability to export all your configuration settings. This ensures that you can safely recover your system while changing phones, upgrading/reinstalling the application with minimum disruption. - -## Troubleshootng - -Please feel free to reach out to the AAPS community if there is anything you feel unsure about - there is no such thing as a silly question! All users with various levels of experience are encouraged to ask questions as necessary. Response times to questions are usually quick, typically only a few hours due to the volume of **AAPS** users. - -a) check the documentation; b) ask AAPS facebook group (https://www.facebook.com/groups/AndroidAPSUsers); and c) ask our discord channel. - -## Section overview - -AAPS documentation is made up of the following Sections: - -[INSERT ONCE SECTIONS /SUB SECTIONS AGREED] ---- diff --git a/docs/CROWDIN/sk/maintaining.md b/docs/CROWDIN/sk/maintaining.md deleted file mode 100644 index 98164a09e49b..000000000000 --- a/docs/CROWDIN/sk/maintaining.md +++ /dev/null @@ -1,28 +0,0 @@ -# Dummy - -## This is a dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - - -## This is another dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - - -## This is another another dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - diff --git a/docs/CROWDIN/sk/optimizing.md b/docs/CROWDIN/sk/optimizing.md deleted file mode 100644 index 98164a09e49b..000000000000 --- a/docs/CROWDIN/sk/optimizing.md +++ /dev/null @@ -1,28 +0,0 @@ -# Dummy - -## This is a dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - - -## This is another dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - - -## This is another another dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - diff --git a/docs/CROWDIN/sk/prepairing.md b/docs/CROWDIN/sk/prepairing.md deleted file mode 100644 index e729af5f4901..000000000000 --- a/docs/CROWDIN/sk/prepairing.md +++ /dev/null @@ -1,145 +0,0 @@ -# Prepairing - -## Guide to the Android APS doc - -### First Steps -Welcome. This is an introduction to aid beginners to the concept of Do-It-Yourself-APS (Android-Artificial-Pancreas-Systems “AAPS”) is commonly referred to as ‘looping’.. - -#### Safetys -“With great powers come great responsibilities…” - -AAPS is designed with an extensive set of safety features with limits imposed and gradually removed with completion of the [Objectives](https://androidaps.readthedocs.io/en/latest/Usage/Objectives.html) (predominately made up of multiple choice questions). An AAPS feature will be unlocked as the Objectives are successfully completed. This process will gradually allow the user to migrate from Open Loop to Closed Loop. - -This has been done to achieve the best possible experience with AAPS by preventing common mistakes new users tend to make when starting to loop. The safety parameters have been built upon typical errors and general trends AAPS developers have observed with new users. Mistakes can happen because the beginner is inexperienced and too eager to get started with AAPS or has overlooked the required materials. Do not worry, we have all been there! - -#### Key Principles - -The key principles and concepts of looping must be understood by the user before using AAPS. This is achieved by investing your personal time into reading the AAPS documentation, and completing the [Objectives](https://androidaps.readthedocs.io/en/latest/Usage/Objectives.html) which is aimed to provide you with a solid platform for safe and effective use of AAPS. The volume of AAPS documentation may seem overwhelming at first but be patient and trust the process - with the proper approach, you'll get there! The overall process will depend upon the beginner’s progress and completion of objectives which typically take between 6 to 9 weeks . - -#### Plan for hiccups - -At the preliminary stages of AAPS, you should expect to experience some hiccups whilst trying to fine tune your settings. AAPS’ glitches cannot be flushed out until the system is used in everyday life. Please plan accordingly and allow a sensible amount of time to troubleshoot and resolve such issues. - -#### Flexibility/Adaptability - -Success with AAPS requires a proactive approach, a willingness to reflect on the BG data and flexibility to make the necessary adjustments to AAPS in order to improve your outcomes. Just as it is nearly impossible to learn to play a sport by reading about the rules alone, the same can be said of AAPS. - -#### Technology compatibility -There are limitations with AAPS as it is accessible for only certain types of insulin pumps or CGMs, and some technology may not be available for use in various countries. In order to avoid any disappointment or frustrations, please read [Component Set Up (Section E).](https://androidaps.readthedocs.io/en/latest/Configuration/BG-Source.html) - -#### App Build time -The time to build the AAPS (under Section D) depends on your level of expertise and technical ability. Typically for inexperienced users, it can take up to half a day or a full day (with help from the community) in order to build the AAPS. The process will significantly speed up as you become more experienced at building the AAPS.  - -To aid the build process there are sections dedicated for: - -- list of questions and answers for frequent errors that are likely to occur under [FAQs (Section](https://androidaps.readthedocs.io/en/latest/Getting-Started/FAQ.html) K); - -- “[How to install AAPS](https://androidaps.readthedocs.io/en/latest/Installing-AndroidAPS/Building-APK.html)? (Section D) which includes [Troubleshooting](https://androidaps.readthedocs.io/en/latest/Usage/troubleshooting.html) subsection. - - -#### Keystore & configuration settings export  file - -A “keystore” is a password encrypted file unique to your own copy of AAPS. Your android phone uses it to ensure that nobody else can upgrade your own copy without the keystore.In short, as part of the AAPS build, you should: - -1. save the your keystore file (.jks file used to sign your app) in a safe place; - -2. keep a note of your password for your keystore file. - - -By doing the above, this will ensure that you can use that exact same keystore file each time an updated version of AAPS is created. On average, there will be 2-3 updates to the AAPS required each year. In addition, AAPS provides the ability to [export all your configuration settings](https://androidaps.readthedocs.io/en/latest/Usage/ExportImportSettings.html). This ensures that you can safely recover your system while changing phones, upgrading/reinstalling the application with minimum disruption.  - -#### Troubleshooting - -Please feel free to reach out to the AAPS community if there is anything you feel unsure about - there is no such thing as a silly question!  All users with various levels of experience are encouraged to ask questions as necessary. Response times to questions are usually quick, typically only a few hours due to the volume of AAPS users.  - -##### [check the documentation](https://androidaps.readthedocs.io/en/latest/index.html) - -##### [ask our facebook group](https://www.facebook.com/groups/AndroidAPSUsers/) - -##### [ask our discord channel](https://discord.com/channels/629952586895851530/629954570394533889) - -#### Section overview - -AAPS documentation is made up of the following Sections: - -##### [Getting started](https://androidaps.readthedocs.io/en/latest/Getting-Started/Safety-first.html) - -This is a must read to understand the general concept of what an artificial pancreas system is designed to do. - -##### [What do I need?](https://androidaps.readthedocs.io/en/latest/Module/module.html) - -This explains AAPS’ compatibility with CGMs (Continuous Glucose Monitors) and insulin pumps. It also provides a guide on the correct assembly of an AAPS system to ensure that it functions correctly in everyday life. - -##### How to install AAPS - -This section is the manual for building the AAPS. Strict adherence to the step-by-step instructions are required in order to successfully build the AAPS. Please take your time. - -##### [Component Setup](https://androidaps.readthedocs.io/en/latest/Configuration/BG-Source.html) - -This explains how to properly integrate each of the various different separate component parts into AAPS, as well as how to set them up to work as seamlessly as possible together. All components are listed under the separate sections: CGM/FGM, xDrip Settings, Pumps, Phones, Nightscout setup, and Smartwatches. The sensor (BG) values and control of the insulin pump are particularly important information to understand. - -##### Configuration - -This explains how to set and configure your ‘Profile’, ‘Insulin’, ‘BG Source’, ‘Pump’, ‘Sensitivity Detection’, ‘APS’, ‘Loop’, ‘Treatments’. - -##### AAPS Usage - -This section provides a breakdown of the features provided by AAPS. - -##### [General Hints](https://androidaps.readthedocs.io/en/latest/Usage/Timezone-traveling.html) - -Useful tricks on how to tackle looping issues such as time zones, and daylight saving (i.e. Spring Forward/ - Fall Back). - -##### [AAPS](https://androidaps.readthedocs.io/en/latest/Getting-Started/Screenshots.html) for Children - -This is designed for parents or caregivers who want to build an AAPS for their child. It also explains the extra features necessary in order to support and safely control your child’s AAPS remotely.

The concepts in this section should be fully understood in order to competently use this feature. - -##### Troubleshooting - -This section contains links to help solve issues when building or using AAPS. - -##### FAQ - -This section addresses specific questions which tend to come up when building or using AAPS. - -##### [Glossary](https://androidaps.readthedocs.io/en/latest/Getting-Started/Glossary.html) - -This contains a list of the acronyms (or short-term names) or defined terms developed specifically for AAP (for instance, the terms ‘ISF’ or ‘TT’ have special meanings in AAPS). - -##### [Where to go for help](https://androidaps.readthedocs.io/en/latest/Where-To-Go-For-Help/Background-reading.html)? - -This section is aimed to provide new users with links on resources in order to get help including accessing community support made up of both new and experienced users who can clarify questions, and resolve the usual pitfalls that come with AAPS. - -##### For Clinicians - -This is a section for the clinicians who have expressed interest in open source artificial pancreas technology such as AAPS, or for patients who want to share such information with their clinicians. | - -## what are we going to build? - -### An Android Phone Application - -At the core, AAPS is an android application running from a phone. You are going to build it from scratch by installing tools to download the sourcecode and build the actual application. - -### A reporting server NightScout (or Tidepool) - -In order to fully use AAPS properly you will want to setup a nightscout server. It is used to collect data from AAPS over time and possibly communicate to the application. It is required for parents who want to oversee their children AAPS sessions. It is also key to share data between clinicians and patients to perform analysis over time. - -## How long will it take? - -## Who might AAPS not be suitable for? - -## Where can I get help? - -## Requirements - -### medical - -### technical - -### personal - -### CGMs - -### Insulin Pump - -### Reporting (NS, Tidepool) \ No newline at end of file diff --git a/docs/CROWDIN/tr/Configuration/EOFLOW.md b/docs/CROWDIN/tr/Configuration/EOFLOW.md deleted file mode 100644 index 53ab62b8dc44..000000000000 --- a/docs/CROWDIN/tr/Configuration/EOFLOW.md +++ /dev/null @@ -1,155 +0,0 @@ -# EOPatch2 Instruction Manual - -The patch requires the use of rapid-acting U-100 type insulin, such as NovoRapid or Humalog. Use a rapid-acting insulin that is suitable for you according to your doctor’s prescription and inject the prescribed dosage. - -The smallest injectable dose of insulin when using the patch is 0.05 U. The Profile BAS should therefore be set at a minimum value of 0.05 U/hr or more and an interval of 0.05 U/hr, as otherwise there may be an error between the estimated total infusion amount in the Profile and the actual infusion amount in the patch. Likewise, the bolus must also be set and infused with a minimum infusion volume of 0.05 U. - -## Pump Setup -1. On the AndroidAPS home screen, click the hamburger menu in the upper left corner and go to Config Builder. -1. Select 'EOPatch2' in the Pump section. -1. Press the Back key to return to the home screen. - -![Bild1](../../images/EOPatch/Bild1.png) ![Bild2](../../images/EOPatch/Bild2.png) - -## Ayarlar -Select EOPATCH2 at the top of the home screen to go to the EOPATCH2 tab. - -Select the EOPatch2 Preferences menu by clicking the three dots in the upper right corner. - -The EOPatch2 Preferences menu offers a menu to set 3 types of notifications. - -### Low reservoir Alerts -A warning appears when the amount of insulin remaining in the reservoir reaches the set value or less while using the patch. It can be set from 10 to 50U in 5U increments. - -### Patch expiration Reminder -This is a reminder to notify you of the time remaining before the current patch expires. It can be set from 1 to 24 hours in 1 hour increments. The initial setting value is 4 hours. - -### Patch buzzer Reminder -This is a reminder function for injections other than basal injection. If you are using an (extended) bolus injection or a temporary basal injection, the patch will make a buzzer sound when the injection starts and when the injection is complete. The initial setting value is Off. - -![Bild3](../../images/EOPatch/Bild3.png) - -## Connecting the Patch - -### Move to patch connection screen - -Select EOPATCH2 at the top of the home screen and click the ACTIVATE PATCH button at the bottom left. - -![Bild4](../../images/EOPatch/Bild4.png) - -### Connecting the patch -Insert the syringe needle into the insulin inlet on the patch and then slowly push the piston to inject the insulin. When insulin is filled with more than 80U, the patch makes a booting sound (1 buzzer) and boots. After confirming the buzzer sound, click the START PAIRING button on the screen. - -[Warning] - -- Do not turn the needle action lever until instructed. It can cause serious problems during injection or safety checks otherwise. -- The amount of insulin that can be injected into the patch is 80~200U. If you inject less than 80U into the patch initially, the patch will not work. -- Take the insulin to be put into the patch from the refrigerator and leave it at room temperature for 15 to 30 minutes beforehand. The temperature of the insulin to be injected must be at least 10°C. - -![Bild5](../../images/EOPatch/Bild5.png) - -### patch pairing -The Patch pairing screen will be displayed, and pairing will be attempted automatically. If communication is successful, the Bluetooth pairing request notification appears. Click OK and when the Bluetooth pairing request notification appears a second time with the authentication code, select OK again. - -[Warning] - -- For pairing, the patch and the smartphone must be located within 30 cm of each other. -- After the patch booting is completed, the patch will beep every 3 minutes until the pairing is complete. -- After booting the patch, the patch application must be completed via the app within 60 minutes. If the application cannot be completed within 60 minutes, the patch should be discarded. - -![Bild6](../../images/EOPatch/Bild6.png) ![Bild7](../../images/EOPatch/Bild7.png) ![Bild8](../../images/EOPatch/Bild8.png) - - -### patch preparation -After removing the adhesive tape of the patch, check if the needle is sticking out. If there are no problems with the patch, click NEXT. - -![Bild9](../../images/EOPatch/Bild9.png) - -### Patch attachment -Insulin should be injected in a spot with subcutaneous fat but few nerves or blood vessels, so it is recommended to use the abdomen, arm, or thigh for the patch attachment site. Choose a patch attachment site and apply the patch after disinfecting the location. - -[Warning] - -- Make sure to straighten the side of the patch tape attached to the body evenly, so that the patch adheres completely to the skin. -- If the patch does not stick completely, air may enter between the patch and the skin, which can weaken the adhesive strength and waterproof effect of the patch. - -![Bild10](../../images/EOPatch/Bild10.png) - -### Safety Check -When patching is complete, touch Start Safety Check. When the safety check is completed, the patch will beep once. - -[Warning] - -- For safe use, do not turn the needle action lever until the safety check has been completed. - -![Bild11](../../images/EOPatch/Bild11.png) ![Bild12](../../images/EOPatch/Bild12.png) - - -### Inserting the needle -The needle is inserted by holding around the patch and turning the needle action lever more than 100° in the upward direction of the lever. There is a buzzer sound when the needle is inserted correctly. Turn the needle action lever further clockwise to release the lever. Click NEXT. - -[Caution] - -- If you go to the next step without the buzzer sounding, a needle insertion error warning will appear. - -## Discarding the patch -Patches must be replaced in the case of low insulin levels, usage expiration, and defects. The recommended usage period for each patch is 84 hours after booting the patch. - -### Discarding the patch -Select EOPATCH2 at the top of the home screen and click the DISCARD/CHANGE PATCH button at the bottom. On the next screen, click the DISCARD PATCH button. A dialog box appears to confirm once more and if you select the DISCARD PATCH button, the disposal is completed. - -![Bild13](../../images/EOPatch/Bild13.png) ![Bild14](../../images/EOPatch/Bild14.png) ![Bild15](../../images/EOPatch/Bild15.png) ![Bild16](../../images/EOPatch/Bild16.png) - -## İnsülin İletimini Askıya Alma ve Devam Ettirme -Suspending insulin delivery also cancels both extended bolus and temporary basal. When resuming insulin delivery, the canceled extended bolus and temporary basal will not be resumed. And when insulin delivery is suspended, the patch will give a sound every 15 minutes. - -### Suspending insulin delivery -Select EOPATCH2 at the top of the home screen and click the SUSPEND button at the bottom right. When you select CONFIRM in the confirmation box, a time selection box appears. If you select the CONFIRM button after selecting the time, the insulin delivery will be suspended for the set amount of time. - -![Bild17](../../images/EOPatch/Bild17.png) ![Bild18](../../images/EOPatch/Bild18.png) ![Bild19](../../images/EOPatch/Bild19.png) - - -### Resuming insulin delivery -Select EOPATCH2 at the top of the home screen and click the RESUME button at the bottom right. Insulin delivery will resume by selecting CONFIRM in the confirmation dialog box. - -![Bild20](../../images/EOPatch/Bild20.png) ![Bild21](../../images/EOPatch/Bild21.png) - -## Alarms/Warnings - -### Alarm - -Alarms are issued for emergency situations of the highest priority and require immediate action. The alarm signal does not disappear or time out until it is acknowledged. An alarm occurs when there is a problem with the patch being used, so there may be cases where the patch in use needs to be discarded and replaced with a new patch. The warning is displayed as a dialog box and switching to another screen is not possible until processing is completed. - -![Bild22](../../images/EOPatch/Bild22.png) ![Bild23](../../images/EOPatch/Bild23.png) - -The different types of alarms are explained below. - -| Alarms | Explanation | -| -------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| Empty reservoir | Occurs when the patch’s reservoir runs out of insulin. | -| Patch expired | Occurs when the patch usage time has expired, and no further insulin injections are possible. | -| Occlusion | Occurs when it appears that the patch's insulin inlet is clogged. | -| Power on self-test failure | Occurs when the patch finds an unexpected error during the post-boot self-test process. | -| Inappropriate temperature | Occurs when the patch is outside the normal operating temperature range during patch application and use. To deal with this alarm, move the patch to an appropriate operating temperature (4.4 to 37°C) condition. | -| Needle insertion Error | Occurs when needle insertion is not normal during the patch application process. Check that the needle insertion edge of the patch and the needle activation button are in a straight line. | -| Patch battery Error | Occurs just before the patch’s internal battery runs out and powers off. | -| Patch activation Error | Occurs when the app fails to complete the patching process within 60 minutes after the patch is booted. | -| Patch Error | Occurs when the patch encounters an unexpected error while applying and using the patch. | - -### Warning - -A warning occurs in a medium or low-priority situation. When a warning occurs, it is displayed as a notification in the Overview screen. - -![Bild24](../../images/EOPatch/Bild24.png) - -The different types of warnings are explained below. - -| Warnings | Explanation | -| ---------------------------- | ------------------------------------------------------------------------------------------------------------------------------------- | -| End of insulin suspend | Occurs when the time set by the user has elapsed after the insulin infusion suspension has been completed. | -| Low reservoir | Occurs when the remaining amount of insulin in the patch is below the set amount. | -| Patch operating life expired | Occurs when the patch usage period is over. | -| Patch will expire soon | Occurs 1 hour before the patch must be discarded. | -| Incomplete Patch activation | Occurs when more than 3 minutes have elapsed due to an interruption during patch application in the stage after pairing is completed. | -| Patch battery low | Occurs when the patch's battery is low. | - diff --git a/docs/CROWDIN/tr/Getting-Started/ClosedLoop.md b/docs/CROWDIN/tr/Getting-Started/ClosedLoop.md deleted file mode 100644 index 4064bb1c1808..000000000000 --- a/docs/CROWDIN/tr/Getting-Started/ClosedLoop.md +++ /dev/null @@ -1,55 +0,0 @@ -# Kapalı Döngü Sistemi Nedir? - -![AAPS AAPS sanki bir otopilot gibidir](../images/autopilot.png) - -Yapay pankreas kapalı döngü sistemi, diyabet yönetimini sizin için daha kolay hale getirmek için farklı bileşenleri birleştirir. Açık kaynaklı kapalı döngü hareketinin kurucularından biri olan Dana M. Lewis, [Otomatik İnsülin İletimi](https://www.artificialpancreasbook.com/) adlı harika kitabında, onu ["diyabetiniz için otomatik pilot"](https://www.artificialpancreasbook.com/3.-getting-started-with-your-aps) olarak adlandırıyor. Ama bu ne anlama geliyor? - -**Uçakta otopilot** - -Otopilot, işin tamamını yapmaz ve pilotun tüm uçuş boyunca uyumasına imkan vermez. Pilotların işini kolaylaştırır. Onları uçağın ve uçuş durumunun sürekli olarak izlenmesi yükünden kurtarır. Bu pilotun hava sahasını izlemeye ve otopilotun işlevlerini kontrol etmeye konsantre olmasını sağlar. - -Otopilot çeşitli sensörlerden gelen sinyalleri alır, bir bilgisayar bunları pilotun özellikleriyle birlikte değerlendirir ve ardından gerekli ayarlamaları yapar. Pilotun artık sürekli ayarlamalar hakkında endişelenmesine gerek yoktur. - -**Kapalı Döngü Sistemi** - -Aynısı yapay bir pankreas kapalı döngü sistemi için de geçerlidir. Bütün işi yapmıyor, yine de şeker hastalığınızla ilgilenmeniz gerekiyor. Kapalı döngü sistemi, bir CGM/FGM'den alınan sensör verilerini bazal oran, insülin duyarlılık faktörü ve karbonhidrat oranı gibi diyabet yönetimi spesifikasyonlarınızla birleştirir. Buradan diyabetinizi hedef aralıkta tutmak ve sizi rahatlatmak için tedavi önerilerini hesaplar ve bu kalıcı küçük ayarlamaları uygular. Bu diyabetin "yanında" hayatınız için daha fazla zaman bırakır. - -İnsan gözetimi olmadan sadece otopilotun uçtuğu bir uçağa binmek istemediğiniz gibi, kapalı döngü sistemi diyabet yönetiminizde size yardımcı olur, ancak her zaman desteğinize ihtiyaç duyar! **Kapalı bir döngüde bile diyabetinizi tamamen unutamazsınız!** - -Otopilot, pilotun özelliklerine olduğu kadar sensör değerlerine de bağlı olduğu gibi, bir kapalı döngü sistemi de sizi başarılı bir şekilde desteklemek için bazal oranlar, ISF ve karbonhidrat oranı gibi uygun girdilere ihtiyaç duyar. - -## Açık Kaynaklı Yapay Pankreas Kapalı Döngü Sistemleri - -Şu anda üç ana açık kaynaklı kapalı döngü sistemi mevcuttur: - -### AndroidAPS (AAPS) - -AAPS is described in detail in [this documentation](./WhatisAndroidAPS.html). İnsülin pompanızın hesaplanması ve kontrolü için bir Android Akıllı Telefon kullanır. OpenAPS ile güçlü bir işbirliği içindedir (yani algoritmaları paylaşırlar). - -Uyumlu [pompalar](../Hardware/pumps.md) şunlardır: - -- [DanaR](../Configuration/DanaR-Insulin-Pump.md) / [DanaRS & Dana-i](../Configuration/DanaRS-Insulin-Pump.html) -- [Accu-Chek Combo](../Configuration/Accu-Chek-Combo-Pump.md) -- [Accu-Chek Insight](../Configuration/Accu-Chek-Insight-Pump.md) -- [Diaconn G8](../Configuration/DiaconnG8.md) -- [Omnipod DASH](../Configuration/OmnipodDASH.md) -- [Omnipod Eros](../Configuration/OmnipodEros.md) -- Bazı eski [Medtronic pompaları](../Configuration/MedtronicPump.md) - -### OpenAPS - -[OpenAPS](https://openaps.readthedocs.io) ilk Açık Kaynak kodlu Kapalı Döngü Sistemidir. Raspberry Pi veya Intel Edison gibi küçük bir bilgisayar kullanır. - -Uyumlu pompalar şunlardır: - -- Bazı Eski Medtronic pompalar - -### IOS için Loop - -iOS için [Loop](https://loopkit.github.io/loopdocs/) Apple iPhone'larla kullanılabilecek Açık Kaynak kodlu bir Kapalı Döngü Sistemidir. - -Uyumlu pompalar şunlardır: - -- Omnipod DASH -- Omnipod Eros -- Bazı Eski Medtronic pompalar diff --git a/docs/CROWDIN/tr/Getting-Started/Safety-first.md b/docs/CROWDIN/tr/Getting-Started/Safety-first.md deleted file mode 100644 index 07ab25ff51c3..000000000000 --- a/docs/CROWDIN/tr/Getting-Started/Safety-first.md +++ /dev/null @@ -1,41 +0,0 @@ -# Önce Güvenlik - -**Kendi yapay pankreas sisteminizi oluşturmaya karar verdiğinizde, her zaman güvenlik ve emniyet hakkında düşünmek ve tüm eylemlerinizin etkisini anlamak önemlidir** - -## Genel - -- AAPS is a just a tool to help you manage diabetes, it is not a fully automated system you can install and forget! -- Do not assume that AAPS will never make mistakes. Bu program, insülin iletiminizin kontrolünü ele alıyor. Her zaman izleyin, nasıl çalıştığını anlayın ve eylemlerini nasıl yorumlayacağınızı öğrenin. -- Telefonun pompa ile eşleştirildiğinde, pompaya her türlü talimatı verebileceğini unutmayın. Only use this phone for AAPS and, if being used by a child, essential communications. Truva atları, virüsler veya sisteminize müdahale edebilecek botlar gibi kötü amaçlı yazılımları bulaştırabilecek gereksiz uygulamalar veya oyunlar (!!!) yüklemeyin. -- Telefon üreticiniz ve Google tarafından sağlanan tüm güvenlik güncellemelerini yükleyin. -- Kapalı döngü sistemi kullanarak tedavinizi değiştirirken diyabet alışkanlıklarınızı da değiştirmeniz gerekebilir. Örneğin some people report, they need less hypo treatments as AAPS has already reduced insulin. - -## SMS Kominikatör - -- AAPS, çocuğunuzun telefonunu kısa mesaj yoluyla uzaktan kontrol etmenizi sağlar. Bu SMS kominikatörü etkinleştirirseniz, uzak komutlar verecek şekilde ayarlanmış telefonun çalınabileceğini unutmayın. Bu yüzden her zaman en azından bir PIN kodu ile telefonu koruyun. -- AAPS ayrıca bolus veya profil değişikliği gibi uzak komutlarınızın gerçekleşip gerçekleşmediğini kısa mesajla size bildirecektir. Alıcı telefonlardan birinin çalınması durumuna karşı en az iki farklı telefon numarasına onay metinleri gönderilecek şekilde ayarlamanız önerilir. - -(Safety-first-aaps-can-also-be-used-by-blind-people)= -## AAPS can also be used by blind people - -Android cihazlarda TalkBack, işletim sisteminin bir parçasıdır. Ses çıkışı yoluyla ekran yönlendirmesi için bir programdır. With TalkBack you can operate your smartphone as well as AAPS blind. - -We users create the AAPS app ourselves with Android Studio. Birçoğu, TalkBack'e benzer bir Ekran Okuyucunun bulunduğu Microsoft Windows'u bu amaç için kullanır. Android Studio bir Java uygulaması olduğundan, Kontrol Panelinde "Java Access Bridge" bileşeni etkinleştirilmelidir. Aksi takdirde, PC'nin ekran okuyucusu Android Studio'da konuşmayacaktır. - -Bunu yapmak için lütfen aşağıdaki şekilde ilerleyin: - -- Klavyede WINDOWS butonuna basın ve arama alanına "Denetim Masası" yazın ve Enter ile açın. "Tüm Kontrol Paneli Öğeleri" açılır. -- E harfine basarak "Erişim Kolaylığı Merkezi"ne girin, Enter ile açın. -- Ardından Enter ile "Bilgisayarı ekransız kullan"ı açın. -- Aşağıda "Enable Java Access Bridge" onay kutusunu bulacaksınız, onu seçin. -- Bitti, pencereyi kapatın! Ekran okuyucu şimdi çalışmalıdır. - -```{note} -** ÖNEMLİ GÜVENLİK BİLDİRİMİ ** - -Bu dokümantasyonda anlatılan AAPS güvenlik özelliklerinin temeli, sisteminizi oluşturmak için kullanılan donanımın güvenlik özellikleri üzerine kurulmuştur. Kapalı döngü kullanımı ile otomatik insülin dozlama için yalnızca test edilmiş, tam işlevli FDA veya CE onaylı insülin pompası ve CGM kullanmanız kritik derecede önemlidir. Bu bileşenlerin donanımında veya yazılımında yapılan değişiklikler, beklenmeyen insülin iletimine ve dolayısıyla kullanıcı için önemli risklere yol açabilir. Bir AAPS sistemi oluşturmak veya çalıştırmak için bozulmuş, değiştirilmiş veya kendi kendine yapılmış insülin pompaları veya CGM alıcıları bulursanız veya size teklif edilirse *kesinlikle kullanmayın*. - -Ek olarak, sadece orijinal aksesuarların kullanılması da bir o kadar önemlidir. Yerleştirme yardımcıları, kanüller ve rezervuarlar, pompanız veya CGM ile kullanım için üretici tarafından onaylanmalıdır. Test edilmemiş veya modifiye edilmiş aksesuarların kullanılması, CGM Sisteminin yanlış olmasına ve insülin iletim hatalarına neden olabilir. Yanlış dozda insülin çok tehlikelidir. Test edilmemiş veya modifiye edilmiş aksesuarlar kullanarak hayatınız ile oynamayın. - -Son olarak, SGLT-2 inhibitörlerini (gliflozinler) kan şekeri düzeylerini inanılmaz derecede düşürdükleri için bu programla beraber bu ilaçları kullanmamalısınız. Kan Şekerini artırmak için bazal oranları düşüren bir sistemle kombinasyon tehlikelidir. Çünkü gliflozin nedeniyle Kan Şekerindeki bu artış gerçekleşmeyebilir ve tehlikeli bir insülin eksikliği durumu meydana gelerek ketoasidoza sebep olabilir. -``` diff --git a/docs/CROWDIN/tr/Getting-Started/Sample-Setup.md b/docs/CROWDIN/tr/Getting-Started/Sample-Setup.md deleted file mode 100644 index f1dcdc0840d4..000000000000 --- a/docs/CROWDIN/tr/Getting-Started/Sample-Setup.md +++ /dev/null @@ -1,151 +0,0 @@ -# Örnek kurulum: Samsung S7, Dana RS, Dexcom G6 ve Sony Smartwatch - -![Örnek kurulum](../images/SampleSetup.png) - -## Açıklama - -Bu kurulumda, döngünün kontrol merkezi olarak Samsung Galaxy S7 akıllı telefon kullanılıyor. Biraz değiştirilmiş Dexcom Uygulaması, Dexcom G6 CGM'den glikoz değerlerini okur. AndroidAPS, Koreli üretici SOOIL'in Dana RS insülin pompasını bluetooth üzerinden kontrol etmek için kullanır. Başka bir cihaza gerek yoktur. - -Dexcom Uygulaması yalnızca sınırlı uyarı seçenekleri sunduğundan, açık kaynak uygulaması xDrip+ yalnızca yüksek ve düşük alarmları değil, aynı zamanda bireysel gereksinimlere göre ek uyarıları da tanımlamak için kullanılır. - -İsteğe bağlı olarak, glikoz ve AndroidAPS değerlerini bileğinizde görüntülemek için bir Android wear akıllı saati kullanılabilir (bu örnek kurulumda Sony Smartwatch 3 (SWR50) kullanılmakta). Saat AndroidAPS'i kontrol etmek için bile kullanılabilir (örn. gizlice bir yemek bolusu ayarlamak). - -Sistem çevrimdışı olarak çalışır. Bu operasyon için akıllı telefonun internete veya mobil bağlantıya gerek olmadığı anlamına gelir. - -Bununla birlikte, bir veri bağlantısı kurulduğunda veriler otomatik olarak "bulutta" Nightscout'a yüklenir. Bunu yaparak, doktor ziyareti için kapsamlı raporlar sağlayabilir veya mevcut değerleri istediğiniz zaman aile üyeleriyle paylaşabilirsiniz. Farklı Nightscout raporlarından yararlanmak için yalnızca (önceden tanımlanmış) bir Wi-Fi bağlantısı kullanırken Nightscout'a veri göndermek de mümkündür. - -## Gerekli bileşenler - -1. Samsung Galaxy S7 - - * Alternatifler: AndroidAPS için [test edilen telefonların ve saatlerin listesine](https://docs.google.com/spreadsheets/d/1gZAsN6f0gv6tkgy9EBsYl0BQNhna0RDqA9QGycAqCQc/edit) bakın - -2. [DanaRS](http://www.sooil.com/eng/product/) - - * Alternatifler: - * [Accu-Chek Combo](../Configuration/Accu-Chek-Combo-Pump.md) - * [Accu-Chek Insight](../Configuration/Accu-Chek-Insight-Pump.md) - * [DanaR](../Configuration/DanaR-Insulin-Pump.md) - * [Bazı eski Medtronic pompaları (ilave olarak gerekli: RileyLink/Gnarl donanımı, bluetooth düşük enerjili Android Telefon / BLE-chipset)](../Configuration/MedtronicPump.md) - * Gelecekte başka pompalar da mevcut olabilir, ayrıntılar için [gelecekteki olası pompa sürücülerine](Future-possible-Pump-Drivers.md) bakın. - -3. [Dexcom G6](https://dexcom.com) - - * Alternatives: see list of possible [BG sources](../Configuration/BG-Source.md) - -4. İsteğe bağlı: Sony Smartwatch 3 (SWR50) - - * Alternatifler: Tüm [Google Wear OS ile](https://wearos.google.com/intl/de_de/#find-your-watch) saatler iyi çalışmalıdır, ayrıntılar için AndroidAPS için [test edilen telefonlar ve saatler listesine](https://docs.google.com/spreadsheets/d/1gZAsN6f0gv6tkgy9EBsYl0BQNhna0RDqA9QGycAqCQc/edit) bakın (OS Android Wear olmalıdır) - -## Nightscout kurulumu - -Ayrıntılı [Nightscout kurulumu](../Installing-AndroidAPS/Nightscout.md)'na bakın - -## Bilgisayar kurulumu - -Ücretsiz olarak kullanılabilen AAPS açık kaynak kodundan bir Android uygulaması oluşturabilmek için bilgisayarınızda veya dizüstü bilgisayarınızda (Windows, Mac, Linux) Android Studio'ya ihtiyacınız vardır. [APK'yı oluşturma](../Installing-AndroidAPS/Building-APK.md) bölümünde ayrıntılı bir talimat bulunabilir. - -Yazılım, bilgisayarınıza yüklendikten sonra birçok ek veri indirdiğinden, Android Studio'yu kurarken lütfen sabırlı olun. - -## Akıllı telefon kurulumu - -![Akıllı telefon](../images/SampleSetupSmartphone.png) - -### Akıllı telefon donanım yazılımını kontrol edin - -* Menü > Ayarlar > Telefon bilgisi > Yazılım bilgisi: En az "Android Sürümü 8.0" (Android 8.0.0 sürümüne kadar başarıyla test edilmiştir Oreo - Samsung Experience Sürüm 9.0) -* Donanım yazılımı güncellemesi için: menü > Tercihler > yazılım güncellemesi - -### Bilinmeyen kaynaklardan uygulama yüklemeye izin ver - -Menü > Ayarlar > Cihaz güvenliği > Bilinmeyen kaynaklar > sağa kaydır (= etkin) - -Güvenlik nedeniyle, burada açıklanan tüm uygulamaların yüklenmesi tamamlandıktan sonra bu ayar tekrar devre dışı bırakılmalıdır. - -### Bluetooth'u Etkinleştir - -1. Menü > Ayarlar > Bağlantılar > Bluetooth > sağa kaydır (= etkin) -2. Menü > Ayarlar > Bağlantılar > Konum > sağa kaydır (= etkin) - -Bluetooth'un düzgün çalışması için konum servisleri ("GPS") etkinleştirilmelidir. - -### Dexcom Uygulamasını yükleyin (değiştirilmiş sürüm) - -![Yamalı Dexcom Uygulaması](../images/SampleSetupDexApp.png) - -Google Play Store'daki orijinal Dexcom uygulaması, değerleri diğer uygulamalara yayınlamadığından çalışmayacaktır. Bu nedenle, topluluk tarafından biraz değiştirilmiş bir sürüm gereklidir. Yalnızca bu değiştirilmiş Dexcom uygulaması AAPS ile iletişim kurabilir. Ek olarak, değiştirilmiş Dexcom Uygulaması, yalnızca [Dexcom'un uyumluluk listesindeki](https://www.dexcom.com/dexcom-international-complete) değil, tüm Android akıllı telefonlarla kullanılabilir. - -Bunu yapmak için akıllı telefonunuzda aşağıdaki adımları uygulayın: - -1. Orijinal Dexcom uygulaması zaten yüklüyse: - * Sensörü durdurun - * Menü > Ayarlar > Uygulamalar > Dexcom G6 Mobile > Kaldır yoluyla uygulamayı kaldırın -2. Download and install the [BYODA Dexcom ap](../Hardware/DexcomG6.md#if-using-g6-with-build-your-own-dexcom-app) -3. Değiştirilmiş Dexcom G6 uygulamasını başlatın, sensörü verilen talimatlara göre etkinleştirin/kalibre edin ve ısınma aşaması bitene kadar bekleyin. -4. Değiştirilen Dexcom uygulaması glikoz değerini gösterdiğinde, uyarıları (ekranın sol üst tarafındaki hamburger menüsü) aşağıdaki gibi ayarlayın: - * Acil düşük `55mg/dl` / `3.1mmol/l` (devre dışı bırakılamaz) - * Düşük `KAPALI` - * Yüksek `KAPALI` - * Artış oranı `KAPALI` - * Düşme oranı `KAPALI` - * Sinyal kaybı `KAPALI` - -## AndroidAPS'i yükleyin - -1. Follow the instructions to [build the APK](../Installing-AndroidAPS/Building-APK.md#generate-signed-apk) -2. [Transfer](../Installing-AndroidAPS/Building-APK.md#transfer-apk-to-smartphone) the generated APK to your phone -3. Kurulum yardımcısını kullanarak veya manuel olarak ihtiyaçlarınıza göre [AndroidAPS'i yapılandırın](../Configuration/Config-Builder.md) -4. Bu örnek kurulumda yardımcıyı kullandık - -* BG source: `Dexcom G6 App (patched)` -- click cock-wheel and activate `Upload BG data to NS` and `Send BG data to xDrip+` (see [BG source](../Configuration/BG-Source.md)) - -![G5 Ayarları](../images/SampleSetupG5Settings.png) - -* NS İstemcisi etkinleştirildi (bkz. [Nightscout kurulumu](../Installing-AndroidAPS/Nightscout.md)) - -## xDrip+'ı yükleyin - -xDrip+, sayısız olasılık sunan başka bir olgun açık kaynak uygulamasıdır. Bu kurulumda, geliştiricilerin uygulamayı ilk yazdıklarının aksine, xDrip+ bu yöntemle Dexcom G6'dan glikoz verilerini toplamak için değil, yalnızca alarmlar vermek ve widget'taki Android ana ekranında mevcut glikoz değerini ve eğrisini görüntülemek için kullanılır. XDrip+ ile alarmlar, Dexcom yazılımı, AAPS veya Nightscout'tan çok daha fazla bireysel olarak ayarlanabilir (ses seçiminde herhangi bir sınırlama yoktur, gündüz/gece saatine bağlı olarak farklı alarmlar vb.). - -1. Akıllı telefonunuzla xDrip+'ın en son kararlı APK sürümünü indirin - Google Play Store'daki sürümü değil! -2. İndirilen APK dosyasını seçerek xDrip+'ı yükleyin. -3. xDrip+'ı başlatın ve aşağıdaki ayarları yapın (sol üstte hamburger menüsü) - * Ayarlar > Alarmlar ve Uyarılar > Glikoz Seviyesi Uyarı Listesi > İhtiyaçlarınıza göre Uyarı Oluştur (yüksek ve düşük). - * Mevcut alarmlar, alarma uzun basılarak değiştirilebilir. - * Ayarlar > Alarmlar ve Uyarılar > Kalibrasyon Uyarıları: devre dışı (değiştirilmiş Dexcom uygulaması aracılığıyla hatırlatılır) - * Ayarlar > Donanım Veri Kaynağı > 640G/EverSense - * Ayarlar > Uygulamalar arası ayarlar > Kalibrasyonları Kabul Et > `AÇIK` - * Menü > Sensörü Başlat (Formalitedir ve çalışan G6 sensörüyle bir ilgisi yoktur. Bu gereklidir, aksi takdirde düzenli olarak bir hata mesajı görünecektir.) - -For more information about xDrip+, see here [BG source page](../Configuration/BG-Source.md). - -### Alarm kurulum örneği - -"Acil düşük alarmı" (55 mg/dl - 3,1mmol altında), değiştirilmiş Dexcom uygulamasından devre dışı bırakılamayan standart bir alarmdır. - -![xDrip alarmları](../images/SampleSetupxDripWarning.png) - -Toplantılar / ibadethaneler / sinema vb. için ipucu: - -Samsung Galaxy S7'de "Rahatsız etmeyin" modu etkinleştirilirse (Menü > Ayarlar > Sesler ve titreşim > Rahatsız etmeyin: sağa kaydırarark (= etkin)), telefon yalnızca acil düşük alarmı sırasında titrer ve herhangi bir akustik uyarı vermez. xDrip+ aracılığıyla kurulan diğer alarmlar için sessiz modun göz ardı edilip edilmeyeceğini (akustik sesin çalınıp çalınmayacağını) seçebilirsiniz. - -## Güç tasarrufu seçeneğini devre dışı bırakma - -Samsung Galaxy S7 cihazınızda Menü > Ayarlar > Cihaz Bakımı > Pil > İzlenmeyen Uygulamalar > + Uygulama ekle seçeneğine gidin: AndroidAPS, Dexcom G6 Mobile, xDrip+ ve Android Wear (akıllı saat kullanılıyorsa) uygulamalarını arka arkaya seçin - -## İsteğe bağlı: Sony Smartwatch 3'ü (SWR50) kurun - -Bir Android Wear akıllı saat ile diyabetli yaşam daha da göze çarpmayan bir hale getirilebilir. Saat, bileğinizde mevcut glikoz seviyesini, döngünün durumunu vb. görüntülemek için kullanılabilir. Saat AndroidAPS'i kontrol etmek için bile kullanılabilir (örn. gizlice bir yemek bolusu ayarlamak). Bunu yapmak için AAPSv2 saat arayüzünün CGM değerine iki kez dokunun. SWR50 genellikle pil yeniden şarj edilene kadar tam gün çalışır (Samsung Galaxy S7 ile aynı şarj cihazı: microUSB). - -![Akıllı saat](../images/SampleSetupSmartwatch.png) - -Saat arayüzünde görüntülenen bilgilerle ilgili ayrıntılar [burada](../Configuration/Watchfaces.md) bulunabilir. - -* Google Play Store aracılığıyla akıllı telefonunuza "Android Wear" uygulamasını yükleyin ve oradaki talimatlara göre akıllı saati bağlayın. -* AAPS'de hamburger menüsü (sol üst köşe) > Konfigürasyon ayarları > Genel (listenin altında) > Wear > sol tarafta etkinleştir'i ve ayar çarkını seçin > Saat ayarları'nı tıklayın ve `Saat tarafından kontrol`'ü etkinleştirin -* Akıllı saatinizde: Saat yüzünü değiştirmek için ekrana uzun basın ve `AAPSv2` öğesini seçin -* Gerekirse her iki cihazı da bir kez yeniden başlatın. - -## Pompa Ayarları - -[Dana RS pompasına](../Configuration/DanaRS-Insulin-Pump.md) bakın \ No newline at end of file diff --git a/docs/CROWDIN/tr/Getting-Started/WhatisAndroidAPS.md b/docs/CROWDIN/tr/Getting-Started/WhatisAndroidAPS.md deleted file mode 100644 index 6c24310a6e78..000000000000 --- a/docs/CROWDIN/tr/Getting-Started/WhatisAndroidAPS.md +++ /dev/null @@ -1,39 +0,0 @@ -# What is a closed loop system with AAPS? - -AAPS is an app that acts as an artificial pancreas system (APS) on an Android smartphone. Yapay pankreas sistemi nedir? Canlı bir pankreasın yaptığını yapmayı amaçlayan (otomatik olarak kan şekerini sağlıklı sınırlar içinde tutmak) bir yazılım programıdır. - -Bir APS, biyolojik pankreasın yaptığı kadar iyi yapamaz, ancak ticari olarak mevcut cihazları ve basit ve güvenli yazılımları kullanarak tip 1 diyabetin daha kolay yönetilmesini sağlayabilir. Those devices include a continuous glucose monitor (CGM) to tell AAPS about your blood sugar levels and an insulin pump which AAPS controls to deliver appropriate doses of insulin. Uygulama, bu cihazlarla bluetooth üzerinden iletişim kurar. Dozaj hesaplamalarını, binlerce kullanıcısı olan ve milyonlarca saatlik kullanımı birikmiş olan OpenAPS adı verilen başka bir yapay pankreas sistemi için geliştirilmiş bir algoritma ya da kurallar dizisi kullanarak yapmaktadır. - -A note of caution: AAPS is not regulated by any medical authority in any country. Using AAPS is essentially carrying out a medical experiment on yourself. Sistemin kurulumu kararlılık ve teknik bilgi gerektirir. Başlangıçta teknik bilgiye sahip değilseniz, sonunda kesinlkle olacaktır. İhtiyacınız olan tüm bilgiler bu belgelerde, başka bir yerde çevrimiçi olarak veya daha önce yapmış olanlardan bulunabilir - onlara Facebook gruplarında veya diğer forumlarda sorabilirsiniz. Many people have successfully built AAPS and are now using it entirely safely, but it is essential that every user: - -- Sistemin nasıl çalıştığını tam olarak anlamak için sistemi kendiniz kurun -- Bireysel diyabet ayarlarını diyabet ekibi ile birlikte en iyi şekilde çalışacak şekilde ayarlar -- Sistemin düzgün çalıştığından emin olmak için bakımını yapar ve izler - -```{note} -**Sorumluluk Reddi ve Uyarı** - -- Burada açıklanan tüm bilgiler, düşünce ve kodlar yalnızca bilgilendirme ve eğitim amaçlıdır. Nightscout şu anda HIPAA gizlilik uyumluluğu için herhangi bir girişimde bulunmamaktadır. Nightscout ve AAPS'i kendi sorumluluğunuzda kullanın. Tıbbi kararlar almak için bilgileri veya kodu kullanmayın. -- github.com'dan alınan kodun kullanımı herhangi bir garanti veya resmi destek içermez. Ayrıntılar için lütfen bu deponun LİSANSINI gözden geçirin. -- Tüm ürün ve şirket adları, ticari markalar, hizmet markaları, tescilli ticari markalar ve tescilli hizmet markaları ilgili sahiplerinin mülkiyetindedir. Kullanımları bilgi amaçlıdır ve onlar tarafından herhangi bir bağlantı veya onay anlamına gelmez. - -Lütfen unutmayın - bu projenin [SOOIL](http://www.sooil.com/eng/), [Dexcom](https://www.dexcom.com/), [Accu-Chek, Roche Diabetes Care](https://www.accu-chek.com/), [Insulet](https://www.insulet.com/) veya [Medtronic](https://www.medtronic.com/) ile hiçbir ilişkisi yoktur ve bunlar tarafından desteklenmemektedir. -``` - -Meydan okumaya hazırsanız, lütfen okumaya devam edin. - -## Primary goals behind AAPS - -- Dahili güvenliği olan bir uygulama. Oref0 ve oref1 olarak bilinen algoritmaların güvenlik özelliklerini okumak için [burayı ](https://openaps.org/reference-design/) tıklayın. -- Yapay pankreas ve Nightscout ile tip 1 diyabeti yönetmek için hepsi bir arada uygulama -- Kullanıcıların gerektiğinde modülleri kolayca ekleyebileceği veya çıkarabileceği bir uygulama -- Belirli konumlar ve diller için farklı sürümleri olan bir uygulama. -- Açık ve kapalı döngü modunda kullanılabilen bir uygulama -- Tamamen şeffaf bir uygulama: kullanıcılar parametreleri girebilir, sonuçları görebilir ve nihai kararı verebilir -- Belirli pompa sürücülerinden bağımsız olan ve kullanıcıların kendi kendilerine kullanmadan önce güvenle deney yapabilmeleri için bir "sanal pompa" içeren bir uygulama -- Nightscout ile yakından entegre edilmiş bir uygulama -- Kullanıcının güvenlik kısıtlamalarını kontrol ettiği bir uygulama - -## Nasıl başlanır - -Tabii ki, buradaki tüm bu içerikler çok önemlidir, ancak başlangıçta oldukça kafa karıştırıcı olabilir. [Modüle Genel Bakış](../Module/module.md) ve [Hedefler](../Usage/Objectives.html) iyi bir yönlendirme sağlar. diff --git a/docs/CROWDIN/tr/Hardware/DexcomG4.md b/docs/CROWDIN/tr/Hardware/DexcomG4.md deleted file mode 100644 index 001752139925..000000000000 --- a/docs/CROWDIN/tr/Hardware/DexcomG4.md +++ /dev/null @@ -1,6 +0,0 @@ -# Dexcom G4 - -## OTG kablosuyla G4 kullanılıyorsa ('geleneksel' Nightscout) -- Henüz kurulmadıysa, Nightscout Uploader uygulamasını Play Store'dan indirin ve [Nightscout](https://nightscout.github.io/) bulunan talimatlarını takip edin. -- In AAPS Preferences enter your Nightscout website and API secret. -- Select NSClient in ConfigBuilder (setting in AAPS). diff --git a/docs/CROWDIN/tr/Hardware/Smartwatch.md b/docs/CROWDIN/tr/Hardware/Smartwatch.md deleted file mode 100644 index 28209107d5c7..000000000000 --- a/docs/CROWDIN/tr/Hardware/Smartwatch.md +++ /dev/null @@ -1,10 +0,0 @@ -# Akıllı saatler - -Akıllı saatler isteğe bağlıdır, ancak bazı kullanıcılar (özellikle uzaktan takip eden ebeveynler) için çok kullanışlıdır. Daha fazla detay için: - -- [Test edilen telefonların ve akıllı saatlerin listesi](../Getting-Started/Phones.md) -- [Wear OS için saatarayüzleri](../Configuration/Watchfaces.md) -- [Sony Smartwatch SW 3'te Sorun Giderme](../Usage/SonySW3.md) - -## Instructions for Building the AAPS Wear APK for Wear OS -https://androidaps.readthedocs.io/en/latest/remote-control.html#building-the-aaps-wear-apk diff --git a/docs/CROWDIN/tr/Installing-AndroidAPS/Building-APK.md b/docs/CROWDIN/tr/Installing-AndroidAPS/Building-APK.md deleted file mode 100644 index 062766c76348..000000000000 --- a/docs/CROWDIN/tr/Installing-AndroidAPS/Building-APK.md +++ /dev/null @@ -1,369 +0,0 @@ -# APK oluşturma - -## Programı İndirmek yerine kendiniz oluşturun... - -**AAPS, tıbbi cihazlarla ilgili düzenlemeler nedeniyle indirilebilen bir uygulama değildir. Uygulamayı kendi kullanımınız için oluşturmak yasaldır, ancak bir kopyasını başkasına vermemelisiniz! Ayrıntılar için [SSS sayfasına](../Getting-Started/FAQ.md) bakın.** - -## Önemli notlar - -* Please use **[Android Studio Giraffe" (2022.3.1)](https://developer.android.com/studio/)** or newer to build the apk. -* [Windows 32-bit systems](troubleshooting_androidstudio-unable-to-start-daemon-process) are not supported by Android Studio - -(Building-APK-recommended-specification-of-computer-for-building-apk-file)= - -## apk dosyası oluşturmak için önerilen bilgisayar özellikleri - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
İşletim Sistemi (Sadece 64 bit)Windows 8 veya üstüMac OS 10.14 veya üstüHerhangi bir Linux, Gnome, KDE veya Unity DE;  GNU C Library 2.31 veya sonraki sürümünü destekler

CPU (Sadece 64 bit)

x86_64 2. nesil CPU mimarisi Intel Core veya daha yenisi ya da
Windows Hypervisor desteğine sahip AMD CPU		ARM tabanlı yongalar veya
Hypervisor.Framework desteğine sahip 2. nesil Intel Core veya daha yenisi		x86_64 CPU mimarisi; 2. nesil Intel Core veya daha yenisi veya AMD Sanallaştırma (Virtualization) (AMD-V) ve SSSE3 desteğine sahip AMD işlemci

Bellek(RAM)

8Gb veya daha fazla

Depolama alanı

En az 30GB boş alan. SSD önerilir.

Çözünürlük

Minimum 1280 x 800

İnternet

Geniş bant

- -Please keep in mind that both **64 bit CPU and 64 bit OS are mandatory condition.** If your system DOES NOT meet this condition, you have to change affected hardware or software or the whole system. **APS kurulum apk dosyasını oluştururken daha az zaman alacağından HDD (Sabit Disk Sürücüsü) yerine SSD (Katı Hal Diski) kullanılması şiddetle tavsiye edilir.** Sadece tavsiye edilir ancak zorunlu değildir. Bununla birlikte, apk dosyası oluştururken yine de bir HDD kullanabilirsiniz, ancak oluşturma işleminin tamamlanmasının uzun zaman alabileceğini unutmayın, ancak bir kez başlatıldığında, gözetimsiz çalışır durumda bırakabilirsiniz. - -* * * - -### Bu makale iki bölüme ayrılmıştır. - -* Genel bakış bölümünde, APK dosyasını oluşturmak için hangi adımların gerekli olduğuna dair bir açıklama vardır. -* Adım adım izleme bölümünde, somut bir kurulumun ekran görüntülerini bulacaksınız. APK'yı oluşturmak için kullanacağımız yazılım geliştirme ortamı olan Android Studio'nun sürümleri çok hızlı değişeceğinden, bu sizin kurulumunuzla aynı olmayacak ancak size iyi bir başlangıç noktası sunacaktır. Android Studio ayrıca Windows, Mac OS X ve Linux üzerinde çalışır ve her platform arasında bazı yönlerden küçük farklılıklar olabilir. Önemli bir şeyin yanlış veya eksik olduğunu fark ederseniz, lütfen "AAPS kullanıcıları" facebook grubuna haber verin veya Discord chat sohbet grubu altında [Android APS](https://discord.gg/4fQUWHZ4Mw)'a bir göz atabilirsiniz. - -## Genel Bakış - -Genel olarak, APK dosyasını oluşturmak için gerekli adımlar: - -1. [Git yükleyin](../Installing-AndroidAPS/git-install.md) -2. [Android Studio'yu yükleyin](Building-APK-install-android-studio) -3. [Android Studio tercihlerinde git yolunu ayarlayın](Building-APK-set-git-path-in-preferences) -4. [AAPS kodlarını indirin](Building-APK-download-AAPS-code) -5. [Android SDK'i indirin](Building-APK-download-android-sdk) -6. [Uygulamayı oluşturun](Building-APK-generate-signed-apk) (imzalı apk oluşturun) -7. [Telefonunuza apk dosyasını aktarın](Building-APK-transfer-apk-to-smartphone) -8. [Eğer xDrip+ kullanıyorsanız, alıcıyı tanımlayın](xdrip-identify-receiver) - -## Adım adım izlenecek yol - -APK dosyasını oluşturmak için gerekli adımların ayrıntılı açıklaması. - -## Git'i kurun (eğer yüklü değilse) - -[git kurulum sayfasındaki](../Installing-AndroidAPS/git-install.md) kılavuzu izleyin. - -(Building-APK-install-android-studio)= - -## Android Studio'yu yükleyin - -Aşağıdaki ekran görüntüleri Android Studio Arctic Fox | 2020.3.1 Versiyonu. Android Studio'nun gelecekteki sürümlerinde ekranlar değişebilir. Ama üstesinden gelebilmelisiniz. [Topluluktan yardım](../Where-To-Go-For-Help/Connect-with-other-users.md) alınabilir. - -Android Studio'yu kurarken en önemli şeylerden biri: **Sabırlı olun!** Kurulum ve kurulum sırasında Android Studio, zaman alacak pek çok şey indirecektir. - -[Android Studio'yu buradan](https://developer.android.com/studio/install.html) indirin ve bilgisayarınıza kurun. - -İlk çalıştırmada kurulum sihirbazıyla karşılaşacaksınız: - -Daha önce kullanmadığınız için "Ayarları içe aktarmayın" seçeneğini seçin. - -![Ayarları içe aktarmayın](../images/studioSetup/01_ImportSettings.png) - -Google ile veri paylaşmak isteyip istemediğinize karar verin. - -![Google ile veri paylaşın](../images/studioSetup/02_DataSharing.png) - -Aşağıdaki ekranda "İleri" ye tıklayın. - -![Hoşgeldin ekranı](../images/studioSetup/03_Welcome.png) - -"Standart" kurulumu seçin ve "İleri"ye tıklayın. - -![Standart kurulum](../images/studioSetup/04_InstallType.png) - -Beğendiğiniz kullanıcı arayüzü için temayı seçin. (Bu kılavuzda biz "Light" kullandık.) Ardından "İleri" ye tıklayın. - -> ***Not:*** Bu yalnızca renk şemasıdır. İstediğinizi seçebilirsiniz (yani karanlık mod için "Darcula"). Bu seçimin APK oluşturma üzerinde hiçbir etkisi yoktur, ancak aşağıdaki ekran görüntüleri farklı görünebilir. - -![UI renk şeması](../images/studioSetup/05_UITheme.png) - -Click "Next" on the "Verify Settings" dialog. - -![Ayarları doğrulayın](../images/studioSetup/06_Overview.png) - -Click on all three license agreement parts and select "Agree". When you have agreed to all, the "Finish" button will be enabled and you can "Finish". - - ![Agree license agreements](../images/studioSetup/07_LicenseAgreement.png) - - -Wait while Android Studio downloads additional components and be patient. Once everything is downloaded button "Finish" turns blue. Click the button now. - -![Downloading components](../images/studioSetup/08_Downloading.png) - -(Building-APK-download-AAPS-code)= - -## AAPS kodlarını indirin - -* On the Android Studio welcome screen select "Projects" (1) on the left and then "Get from VCS" (2). - - ![Android Studio wizard](../images/studioSetup/20_ProjectVCS.png) - - * If you already opened Android Studio and do not see the welcome screen anymore select File (1) > New (2) > Project from Version Control... (3) - - ![Check out project from version control within Android Studio](../images/AndroidStudio_FileNew.PNG) - - * We will now tell Android Studio were to get the code from: - - * Make sure you have selected "Repository URL" on the left (1). - - * Check if "Git" is selected as version control (2). - * Copy and paste the URL ```https://github.com/nightscout/AndroidAPS``` to the main AAPS repository into the URL textbox (3). - * Choose the directory where you want to save the cloned code (4). - - ![Clone Git](../images/studioSetup/21_CloneURL.png) - -* Click button "Clone" (5). - - ![Clone repository](../images/studioSetup/22_Cloning.png) - -* Do not click "Background" while repository is cloned! - -* After the repository is cloned successfully, Android Studio will open the cloned project. - -* You will be asked whether you want to trust the project. Click on "Trust project"! - - ![Trust project](../images/studioSetup/23_TrustProject.png) - -* In the status bar at the bottom you will see the information that Android Studio is running background tasks. - - ![Background tasks](../images/studioSetup/24_GradleSyncRunning.png) - -* Windows only: Grant access if your firewall is asking for permission. - - ![Firewall permission java](../images/AndroidStudio361_18.png) - -* Once the background tasks are finished you will probably see an error saying that errors occurred (1) or (2) or (3). - - ![SDK licence](../images/studioSetup/25_SyncFailed.png) - - Don't worry, this will be solved soon! - -(Building-APK-set-git-path-in-preferences)= - -## Set git path in preferences - -Make sure [git is installed](../Installing-AndroidAPS/git-install.md) on your computer and you have restarted your computer since installing. - -On the Android Studio welcome screen click "Customize" (1) on the left and then select the link "All settings..." (2): - -![Android Studio settings from welcome screen](../images/studioSetup/10_WizardSettings.png) - -### Windows - -* As windows user, make sure you have restarted your computer after [installing Git](../Installing-AndroidAPS/git-install.md). - -* Menüde Dosya (1) > Ayarlar (2) (veya Mac'te Android Studio > Tercihler) seçeneğine gidin. - - ![Ayarları aç](../images/studioSetup/30_Settings.png) - -* Double-click "Version Control" (1) to open the sub-menu. - -* Click Git (2). -* Make sure update method "Merge" (3) is selected. -* Check if Android Studio can locate path to git.exe automatically by clicking the button "Test" (4). - - ![Android Studio settings](../images/studioSetup/11_GitPath.png) - -* If automatic setting is successful git version will be displayed next to the path. - - ![Git version displayed](../images/studioSetup/12_GitVersion.png) - -* Eventually git.exe cannot be found automatically or the Test will result in an error (1): - - ![Git not found](../images/studioSetup/13_GitVersionError.png) - - In this case click on the folder icon (2). - -* Use [search function](https://www.tenforums.com/tutorials/94452-search-file-explorer-windows-10-a.html) in windows explorer to find "git.exe" if you are unsure where git has been installed. You are looking for a file named "git.exe", located in **\bin** folder. - -* Select path to git.exe and make sure you selected the one in ** \bin\ ** folder (3) and click "OK" (4). - - ![Select git manually](../images/studioSetup/14_GitManualSelection.png) - -* Check your selected git path again with the "Test" button as described above. - -* When the git version is displayed next to the path (see screenshot above), close settings window by clicking "OK" button (5). - -### Mac - -* Any git version should work. For example . -* Use homebrew to install git: ```$ brew install git```. -* For details on installing git see the [official git documentation](https://git-scm.com/book/en/v2/Getting-Started-Installing-Git). -* If you install git via homebrew there is no need to change any preferences. Just in case: They can be found here: Android Studio - Preferences. - -(Building-APK-download-android-sdk)= - -## Android SDK'i indirin - -* Menüde Dosya (1) > Ayarlar (2) (veya Mac'te Android Studio > Tercihler) seçeneğine gidin. - - ![Ayarları aç](../images/studioSetup/30_Settings.png) - -* Languages & Frameworks tıklayarak menüyü açın (1) - -* Android SDK (2)'yi seçin. -* "Android 9.0 (Pie)" (3) (API Level 28) öğesinin solundaki kutuyu işaretleyin. - - ![SDK ayarları](../images/studioSetup/31_AndroidSDK.png) - -* Ok tıklatarak değişiklikleri onaylayın. - - ![SDK değişikliklerini onaylayın](../images/studioSetup/32_ConfirmSDK.png) - -* Wait until the SDK download and installation is finished. - - ![Wait during SDK installation](../images/studioSetup/34_DownloadSDK.png) - -* When SDK installation is completed the "Finish" button will turn blue. Click this button. - - ![Finish SDK installation](../images/studioSetup/35_DownloadSDKfinished.png) - -* Android Studio might recommend to update the gradle system. **Never update gradle!** This will lead to difficulties! - -* If you see an information on the lower right side of your Android Studio window that Android Gradle Plugin is ready to update click on the text "upgrade" (1). - - ![Gradle güncellemesi yok](../images/studioSetup/36_GradleUpdateRequest.png) - -* In the dialog box the select "Don't remind me again for this project" (2). - - ![Gradle güncellemesi yok](../images/studioSetup/37_GradleUpdateDeny.png) - -* Restart Android Studio before you continue. - -(Building-APK-generate-signed-apk)= - -## İmzalı APK oluştur - -Signing means that you indicate your app to be your own creation but in a digital way as a kind of digital fingerprint within the app itself. That is necessary because Android has a rule that it only accepts signed code to run for security reasons. For more information on this topic, follow [this link](https://developer.android.com/studio/publish/app-signing.html#generate-key). - -* Android Studio başlatıldıktan sonra tüm arka plan görevleri bitene kadar bekleyin. - - ![Arka plan görevlerini bekleyin](../images/studioSetup/40_BackgroundTasks.png) - - * ***Uyarı:*** Hata oluşursa, aşağıdaki adımlara devam etmeyin. \ Bilinen sorunlar için [sorun giderme bölümüne](../Installing-AndroidAPS/troubleshooting_androidstudio) bakın! - - ![Gradle Sync Hatası](../images/studioSetup/41_GradleSyncError.png) - -* Menü çubuğunda "Build"a (1) tıklayın ve "Generate Signed Bundle / APK..." (2) öğesini seçin. - - ![Apk derleme](../images/studioSetup/42_MenuBuild.png) - -* "Android App Bundle" yerine "APK"yı (1) seçin ve "İleri"ye (2) tıklayın. - - ![Bundle yerine APK](../images/studioSetup/43_Apk.png) - -* Make sure that module is set to "AndroidAPS.app" (1). - -* Kendi "key store" oluşturmaya başlamak için "Create new..." (2) öğesini tıklayın. - - ***Not:*** Bu durumda bir key store imzalama bilgilerinin depolandığı bir dosyadan başka bir şey değildir. Şifrelenir ve bilgiler şifrelerle güvence altına alınır. - - ![Key store oluştur](../images/studioSetup/44_KeystoreNew.png) - -* Anahtar deponuz için bilgisayarınızda bir yol seçmek için klasör sembolüne tıklayın. - - ![Key store oluştur](../images/studioSetup/45_KeystoreDialog.png) - -* Key store'un kaydedileceği yolu seçin (1). - - ![Key store oluştur](../images/studioSetup/46_KeystorePath.png) - - ***Uyarı: Proje ile aynı klasöre kaydetmeyin. Farklı bir dizin kullanmalısınız!*** İyi bir konum, Ev klasörünüz olacaktır. - -* Key store (2) için bir dosya adı yazın ve "OK" (3) ile onaylayın. - -* Key store parolasına girin (2) ve onaylayın(3). ![Key store yolunu seçin](../images/studioSetup/47_KeystoreDialog.png) - - ***Not:*** key store ve key için parolaların çok karmaşık olması gerekmez. Bunları hatırladığınızdan veya güvenli bir yere not aldığınızdan emin olun. Gelecekte şifrelerinizi hatırlamayacaksanız, [kayıp key store için sorun giderme](troubleshooting_androidstudio-lost-keystore) konusuna bakın. - -* Key için bir takma ad alias (4) girin. Ne isterseniz seçebilirsiniz. - -* Girin (5) ve key parolasını onaylayın (6) - -* Geçerlilik Validity (7) varsayılan olarak 25 yıldır. Varsayılan değeri değiştirmeniz gerekmez. - -* Adı ve soyadı girilmelidir (8). Diğer tüm bilgiler isteğe bağlıdır. - -* İşiniz bittiğinde "OK"yi (9) tıklayın. - -* Şifreleri hatırlama kutusunun işaretli olduğundan emin olun (1). Böylece, apk'yi bir sonraki oluşturduğunuzda (yani yeni bir AAPS sürümüne güncelleme yaparken) bunları tekrar girmeniz gerekmez. - -* "Next"i (2) tıklayın. - - ![Parolaları hatırla](../images/studioSetup/48_KeystoreSave.png) - -* Derleme varyantını seçin "fullRelease" (1) seçin ve "Finish"e basın. - - ![Derleme varyantı seçin](../images/studioSetup/49_BuildVariant.png) - -* Android Studio, altta "Gradle Build running" gösterecektir. Bu, bilgisayarınıza ve internet bağlantınıza bağlı olarak biraz zaman alır. **Sabırlı olun!** - - ![Gradle Çalışıyor](../images/studioSetup/50_GradleRunning.png) - -* Android Studio, derleme tamamlandıktan sonra "Generate Signed APK" bilgisini görüntüler. - - ![Derleme tamamlandı](../images/studioSetup/51_BuildFinished.png) - -* Derlemenin başarılı olmaması durumunda [sorun giderme bölümüne](../Installing-AndroidAPS/troubleshooting_androidstudio) bakın. - -* Genişletmek için bildirime tıklayın. - -* "Bul" bağlantısını tıklayın. - - ![Derleneni bul](../images/studioSetup/52_BuildLocate.png) - - * Bildirim kaybolursa, her zaman "Olay günlüğü"nü açabilir ve orada aynı bağlantıyı seçebilirsiniz. ![Başarıyla Derlendi - event log](../images/studioSetup/53_EventLog.png) - -* Dosya yöneticiniz (Windows Gezgini) açılacaktır. "full" (1) > "release" (2) dizinine gidin. - - ![Apk dosya konumu](../images/studioSetup/54_APKlocation.png) - -* "app-full-release.apk" (3) aradığınız dosyadır! - -(Building-APK-transfer-apk-to-smartphone)= - -## APK'yı akıllı telefona aktarın - -Easiest way to transfer app-full-release.apk to your phone is via [USB cable or Google Drive](https://support.google.com/android/answer/9064445?hl=en). Please note that transfer by mail might cause difficulties and is not the preferred way. - -On your phone you have to allow installation from unknown sources. Manuals how to do this can be found on the internet (i.e. [here](https://www.expressvpn.com/de/support/vpn-setup/enable-apk-installs-android/) or [here](https://www.androidcentral.com/unknown-sources)). - -## Sorun giderme - -See separate page [troubleshooting Android Studio](../Installing-AndroidAPS/troubleshooting_androidstudio). \ No newline at end of file diff --git a/docs/CROWDIN/tr/Sandbox/sandbox2.md b/docs/CROWDIN/tr/Sandbox/sandbox2.md deleted file mode 100644 index e45528459e1b..000000000000 --- a/docs/CROWDIN/tr/Sandbox/sandbox2.md +++ /dev/null @@ -1,43 +0,0 @@ -# test için dahili sanal alan dosyası 2 - -```{admonition} no need to translate this -:class: Not - -Bunu tercüme etmenize gerek yok. -``` - -Bu, dokümantasyon ekibinin test etmesi için dahili bir sanal alan dosyasıdır - -1. işaretleme sözdizimi ve - -1. aşağıdakiler için arka plan süreci - 1. CROWDIN çevirisi ve - 2. Dok. dağıtımını okuyun. - -You can dirctly jump from here to the first label in the sandbox1.md file - ["Jump"](sandbox1-this-is-a-test). - -Buradan doğrudan bu dosyadaki ikinci etikete atlayabilirsiniz - ["Atla"](sandbox1-this-is-another-test). - -Bu linkten ilk sanal alan dosyasına atlayabilirsiniz - ["Atla"](./sandbox1.md). - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -(sandbox2-this-is-a-test)= -## Bu bir testtir - -Etiketlerin benzersiz olması gerekiyorsa bu bir testtir. - -### This is spare information from the docs - -cut from index: - -There are "limits" set in place when you are first beginning your AAPS journey. Bu güvenlik sınırları, yeni kullanıcıların AAPS'yi ilk kez kurmayı, oluşturmayı ve ardından başarılı bir şekilde döngü yapmayı öğrenirken yanlışlıkla yapmaları muhtemel olan hataların gözlemlenmesiyle uzun yıllar boyunca geliştirilmiştir. Kullanıcılar sistemi kullanmaya başlamak için o kadar heyecanlılar ki, çoğu zaman oturup bu dokümantasyondaki bilgileri tam olarak anlamak için gereken zamanı ayırmayı unutuyorlar. - - -### spare info from the overview to put into "preparing" - -Gereksinimler geçmişte kurmuş olabileceğiniz herhangi bir şeyden çok farklı olduğundan, uygulamayı ilk birkaç kez oluştururken talimatları adım adım uygulamanızı öneririz, böylece tüm yönergeler tam olarak izlendiğinde uygulama oluşturma sürecinin nasıl davranması gerektiğine dair daha güçlü bir fikir sahibi olursunuz. Lütfen zaman ayırmayı unutmayın. Daha sonra, uygulamayı yeni bir sürüm için yeniden oluşturduğunuzda bu süreç daha hızlı olacaktır. Bu şekilde, diğer yüklemelerinizde çok fazla adımın dışına çıkmadan bir şeylerin planlandığı gibi gitmediğini fark etme şansınız daha yüksek olacaktır. Anahtar deposu dosyanızı (uygulamanızı imzalamak için kullanılan .jks dosyası) güvenli bir yere kaydetmeniz önemlidir, böylece her yeni AAPS güncellenmiş sürüm oluşturmanız istendiğinde her zaman aynı anahtar deposu dosyasını ve parolayı kullanabilirsiniz. Bu dosya, uygulamanın her yeni sürümünün, uygulamanın önceki sürümlerinde kendisine sağladığınız tüm bilgileri "hatırlamasını" ve böylece güncellemelerin olabildiğince sorunsuz gitmesini sağlayan anahtardır. Ortalama olarak, yılda bir yeni sürüm ve 2-3 gerekli güncelleme olacağını varsayabilirsiniz. Bu sayı deneyime dayanmaktadır ve değişebilir. Ama en azından size ne olabileceği konusunda genel bir bilgi vermek istiyoruz. Güncellenmiş AAPS uygulama sürümlerini oluşturma konusunda daha deneyimli olduğunuzda, güncellenmiş bir uygulama oluşturmak için gereken tüm adımlar ortalama olarak yalnızca 15-30 dakika sürer. Ancak, bu adımlar her zaman yeni kullanıcılar tarafından sezgisel olarak bilinmediğinden, başlangıçta oldukça dik bir öğrenme eğrisi olabilir! Bu nedenle, güncelleme sürecini tamamlamadan önce topluluktan biraz yardım alarak yarım gün veya tam bir gün sürdüğünü fark ederseniz sinirlenmeyin. Çok sinirli veya sabırsız olduğunuzu fark ederseniz, kısa bir ara verin ve çoğu zaman bir veya iki blok etrafında bir gezintiden sonra soruna yeniden denemenin daha iyi olduğunu göreceksiniz. diff --git a/docs/CROWDIN/tr/Usage/Objectives.md b/docs/CROWDIN/tr/Usage/Objectives.md deleted file mode 100644 index 7d43b15b4fa8..000000000000 --- a/docs/CROWDIN/tr/Usage/Objectives.md +++ /dev/null @@ -1,184 +0,0 @@ -# Görevler - -AAPS has a series of Objectives that need to be completed to walk you through the features and settings of safe looping. Yukarıdaki bölümlerde ayrıntıları verilen her şeyi doğru bir şekilde yapılandırdığınızdan ve sisteminizin ne yaptığını ve neden ona güvenebileceğinizi anladığınızdan emin olurlar. - -**Telefonları yükseltiyorsanız** görevlerde ilerlemenizi sürdürmek için [ayarlarınızı dışa aktarabilirsiniz](../Usage/ExportImportSettings.md). Yalnızca hedeflerdeki ilerlemeniz değil, aynı zamanda maksimum bolus gibi güvenlik ayarlarınız da kaydedilecektir. Ayarlarınızı dışa ve içe aktarmazsanız, görevlere baştan başlamanız gerekecektir. Her ihtimale karşı sık sık [ayarlarınızı yedeklemeniz](../Usage/ExportImportSettings.html) iyi bir fikirdir. - -Görevlere geri dönmek istiyorsanız [aşağıdaki açıklamaya](Objectives-go-back-in-objectives) bakın. - -## Görev 1: Görselleştirme ve izleme ayarları, bazal ve oranlarını analize etme - -- Kurulumunuz için doğru kan şekeri kaynağını seçin. Daha fazla bilgi için [KŞ Kaynağı](../Configuration/BG-Source.md)na bakın. -- Select the right Pump in ConfigBuilder (select Virtual Pump if you are using a pump model with no AAPS driver for looping) to ensure your pump status can communicate with AAPS. -- If using DanaR pump then ensure you have followed [DanaR Insulin Pump](../Configuration/DanaR-Insulin-Pump.md) instructions to ensure the link between pump and AAPS. -- You need to establish a data repository/reporting platform to complete this objective. That can be accomplished with either Nightscout or Tidepool (or both). Follow instructions at the [Nightscout](../Installing-AndroidAPS/Nightscout.md) or [Tidepool](../Installing-AndroidAPS/Tidepool.md) page for instructions. -- NSClientteki URL'nin sonunda **/api/v1/ OLMADAN** yazılması gerektiğini unutmayın - [Tercihler'deki NSClient ayarları](Preferences-nsclient)'na bakın. - -*You may need to wait for the next blood glucose reading to arrive before AAPS will recognise it.* - -## Objective 2: Learn how to control AAPS - -- Perform several actions in AAPS as described in this objective. - -- Tek tek görevlere ulaşmak için turuncu renkli "Henüz tamamlanmadı" metnine tıklayın. - -- Henüz belirli bir eyleme aşina değilseniz, size rehberlik edecek bağlantılar sağlanacaktır. - - ```{image} ../images/Objective2_V2_5.png - :alt: Screenshot Görev 2 - ``` - -(Objectives-objective-3-prove-your-knowledge)= - -## Görev 3: Bilginizi kanıtlayın - -Objective 3 is a multiple choice test based on questions designed to test your theoretical knowledge of **AAPS**. - -Some users find Objective 3 to be the most difficult objective to complete. Please do read the AAPS documents in conjunction with the questions. If you are genuinely stuck after researching the **AAPS** documents, please search or ask for help on the Facebook or Discord group. These groups can provide friendly hints or redirect you to the relevant part of the **AAPS** documents. - -To proceed with Objective 3, click on the orange text “Not completed yet” to access the relevant question. Please read each question and select your answer(s). - - - -Within each question, a hyperlink to the **AAPS** documents will guide you to the relevant section of the document which you should read in order to locate the correct answer. - - -[Obj3_Screenshot 2023-12-05 223422](https://github.com/openaps/AndroidAPSdocs/assets/137224335/77347516-e24e-459d-98ab-acbb49a3d4e8)![image](https://github.com/openaps/AndroidAPSdocs/assets/137224335/ca756b8e-efbc-4427-b281-ac953ce16718) - - - -For each question, there may be more than one answer that is correct! If an incorrect answer is selected, the question will be time locked for a certain amount of time (60 minutes) before you can go back and answer the question. - - -After updating to a new version of **AAPS**, new questions may be added to cover a prevalent issue picked up by **AAPS** or alternatively to test your knowledge of a new feature of **AAPS** as released. - - -When **AAPS** is installed for the first time, you will have to complete Objective 3 entirely in order to move onto Objective 4. Each objective is required to be completed in sequential order. New features will gradually be unlocked as progress is made through the objectives. - -__What happens if new questions are added later to Objective 3?__ From time to time, new features are added to **AAPS** which may require a new question to be added to Objective 3. As a result, any new question added to Objective 3 will be marked as “incomplete” because **AAPS** will require you to action this. As each Objective is independent, you will not lose the existing functionality of **AAPS** providing the other objectives remain completed. - - -## Görev 4: Bir Açık döngüye başlamak - -- Tercihler'den veya ana ekranın sol üst köşesindeki Döngü düğmesini basılı tutarak Döngü Aç'ı seçin. -- Ayarlarınız için [Tercihler](../Configuration/Preferences.md) üzerinde çalışın. -- Manually enact at least 20 of the temporary basal rate suggestions over a period of 7 days; input them to your pump and confirm in AAPS that you have accepted them. Ensure this data shows in AAPS and Nightscout. -- Gerekirse [geçici hedefleri](../Usage/temptarget.md) etkinleştirin. Bir hipodan sonra yükselen kan şekeri nedeniyle sistemin çok güçlü düzeltme yapmasını önlemek için hipo geçici hedeflerini kullanın. - -### Bildirim sayısını azaltın - -- Açık Döngüdeyken alınacak karar sayısını azaltmak için 90 - 150 mg/dl veya 5,0 - 8,5 mmol/l gibi geniş bir hedef aralığı belirleyin. - -- Hatta geceleri üst sınırı genişletmek (veya Açık Döngüyü devre dışı bırakmak) isteyebilirsiniz. - -- Tercihler'de bazal oran değişikliği önerisi için bir minimum yüzde belirleyebilirsiniz. - - ```{image} ../images/OpenLoop_MinimalRequestChange2.png - :alt: Açık Döngü minimum istek değişikliği - ``` - -- Ayrıca her öneriye her 5 dakikada bir cevap vermek zorunda da değilsiniz... - -## Görev 5: Geçici bazal önerileri de dahil olmak üzere açık döngünüzü anlamak - -- Start to understand the thinking behind the temp basal recommendations by looking at the [determine basal logic](https://openaps.readthedocs.io/en/latest/docs/While%20You%20Wait%20For%20Gear/Understand-determine-basal.html) and both the [forecast line in AAPS homescreen](Screenshots-prediction-lines)/Nightscout and the summary of outputs from the calculations in your OpenAPS tab. - -Hesaplamalardan ve ayarlardan emin olana kadar hedefinizi normalden daha yükseğe koymak isteyeceksiniz. Sistem izin verdiğince - -- düşük hedef için minimum 4 mmol (72 mg/dl) veya maksimum 10 mmol (180 mg/dl) olacak şekilde -- yüksek hedef için minimum 5 mmol (90 mg/dl) veya maksimum 15 mmol (225 mg/dl) olacak şekilde -- tek bir değer olacak şekilde geçici bir hedef, 4 mmol ila 15 mmol (72 mg/dl ila 225 mg/dl) aralığında herhangi bir yerde olabilir - -Hedef hesaplamaların dayandığı değerdir ve kan şekeri değerlerinizi içinde tutmayı amaçladığınız değerle aynı değildir. Hedefiniz çok genişse (diyelim ki 3 veya daha fazla mmol \[50 mg/dl veya daha fazla\]), genellikle çok az AAPS etkisi bulacaksınız. Bunun nedeni, kan şekerinin eninde sonunda bu geniş aralıkta bir yerde olacağı tahmin edilmesidir ve bu nedenle çok fazla dalgalı geçici bazal hız önerilmemektedir. - -Hedeflerinizi birbirine daha yakın bir aralık (diyelim ki 1 veya daha az mmol \[20 mg/dl veya daha az\]) olacak şekilde ayarlamayı deneyebilir ve sonuç olarak sisteminizin davranışının nasıl değiştiğini gözlemleyebilirsiniz. - -[Tercihler](../Configuration/Preferences.md)'de > Görselleştirme Aralığına farklı değerler girerek kan şekerinizi içinde tutmayı amaçladığınız değerler için grafik üzerinde daha geniş bir aralık (yeşil çizgiler) görüntüleyebilirsiniz. - -```{image} ../images/sign_stop.png -:alt: Dur işareti -``` - -### Sanal bir pompa ile açık döngü yapıyorsanız burada durun - bu hedefin sonunda sakın Doğrula'ya tıklamayın. - -```{image} ../images/blank.png -:alt: boş -``` - -(Objectives-objective-6-starting-to-close-the-loop-with-low-glucose-suspend)= -## Görev 6: Düşük KŞ'de Duraklatma ile döngüyü kapatmaya başlamak - -```{image} ../images/sign_warning.png -:alt: Uyarı işareti -``` - -### Kapalı döngü, düşük glikoz duraklatma ile sınırlı olduğundan, görev 6'daki yüksek KŞ değerlerini düzeltmeyecektir. Yüksek KŞ değerleri sizin tarafınızdan manuel olarak düzeltilmelidir! - -- Prerequisite: You need a good profile (basal, ISF, IC) already working in AAPS to start with Loop in Low Glucose Suspend mode. Aksi takdirde, kendinizi manuel olarak düzeltmeniz gereken bir hipoda bulabilirsiniz. Bu seçenek, hipodan 5 gün boyunca kaçınmanıza yardımcı olacaktır. **Hala sık veya şiddetli düşük glikoz atakları yaşıyorsanız, İES, bazal, İDF ve karbonhidrat oranlarınızı iyileştirmeyi, düzeltmeyi düşünün ve şu anda 6. görevle BAŞLAMAYIN.** -- Ayarlarınızı şimdi değiştirmenize gerek yok. Görev 6 sırasında maxAİNS ayarı dahili olarak otomatik sıfıra ayarlanır. **Bu geçersiz kılma, görev 7'ye geçildiğinde tersine çevrilecektir.** -- Sistem, maxAİNS ayarınızı sıfır olarak geçersiz kılar; bu, kan şekerinin düşmesi durumunda sizin için bazalı düşürebileceği anlamına gelir. Kan şekeri yükseliyorsa, yalnızca bazal AİNS önceki bir Düşük Glikoz Askıya Alma işlemine göre negatifse bazal artacaktır. Aksi takdirde, bazal oranlar seçtiğiniz profille aynı kalacaktır. **Bu, yüksek KŞ değerleriyle insülin düzeltmeleri yaparak manuel başa çıkmanız gerektiği anlamına gelir.** -- Bazal AİNS negatifse (aşağıdaki ekran görüntüsüne bakın) Görev 6'da da bir GBO > %100 verilebilir. - -```{image} ../images/Objective6_negIOB.png -:alt: Örnek negatif AİNS -``` - -- Güvende olmak ve daha fazla koruma tamponuna sahip olmak için hedef aralığınızı genellikle biraz daha yüksek tutun. -- Ana ekranın sağ üst köşesindeki Döngü simgesini basılı tutarak ve Döngü - LGS modu simgesini seçerek 'Düşük Glikoz Askıya Alma' modunu etkinleştirin. -- Ana ekrandaki mavi bazal metnini veya ana ekran grafiğindeki mavi bazal oluşumunu görüntüleyerek geçici bazalların aktivitesini izleyin. -- Bazal artırma yeteneği olmadan tedavi edilen hipoları takiben geçici olarak ani artışlar yaşayabilirsiniz. - -(Objectives-objective-7-tuning-the-closed-loop-raising-max-iob-above-0-and-gradually-lowering-bg-targets)= -## Görev 7: Kapalı döngüyü ayarlamak, maksimum AİNS'i 0'ın üzerine çıkarmak ve KŞ hedeflerini kademeli olarak düşürmek - -- [Tercihler](../Configuration/Preferences.md)'den veya ana ekranın sağ üst köşesindeki Döngü simgesine basılı tutarak 1 gün için 'Kapalı Döngü'yü seçin. - -- 'Maksimum toplam AİNS OpenAPS'i aşamaz' (OpenAPS'de 'max-iob' olarak adlandırılır) değerinizi 0'ın üzerine çıkarın. Varsayılan öneri "ortalama yemek bolusu + 3x maksimum günlük bazal" (SMB algoritması için) veya "3x maksimum günlük bazal" (eski AMA algoritması için) şeklindedir. Ancak ayarların sizde nasıl tepki verdiğini anlayana kadar bu değeri yavaş yavaş yükseltmelisiniz.( maks günlük bazal = günün herhangi bir zaman diliminde maksimum saatlik değer). - - Bu öneri bir başlangıç noktası olarak görülmelidir. 3x'e ayarladıysanız ve sizi sert ve hızlı şekilde düşürüyorsa, o sayıyı düşürün. Eğer çok dirençliyseniz, her seferinde çok az yükseltin. - - ```{image} ../images/MaxDailyBasal2.png - :alt: maks günlük bazal - ``` - -- Döngü modellerinize ne kadar AİNS uyduğundan emin olduktan sonra hedeflerinizi istediğiniz seviyeye indirin. - -(Objectives-objective-8-adjust-basals-and-ratios-if-needed-and-then-enable-autosens)= -## Görev 8: Gerekirse bazalleri ve oranları ayarlayın ve ardından otoduyarlılığı etkinleştirin - -- Bazallarınızın doğruluğunu kontrol etmek veya geleneksel bir bazal testi yapmak için [otoayarı](https://openaps.readthedocs.io/en/latest/docs/Customize-Iterate/autotune.html) bir defaya mahsus olarak kullanabilirsiniz. -- Enable [autosens](../Usage/Open-APS-features.md) over a period of 7 days and watch the white line on the homescreen graph show how your sensitivity to insulin may be rising or falling as a result of exercise or hormones etc. and keep an eye in the OpenAPS report tab how AAPS is adjusting the basals and/or targets accordingly. - -*Don’t forget to record your looping in* [this form](https://bit.ly/nowlooping) *logging AAPS as your type of DIY loop software, if you have not already done so.* - -(Objectives-objective-9-enabling-additional-oref1-features-for-daytime-use-such-as-super-micro-bolus-smb)= -## Görev 9: Süper mikro bolus (SMB) gibi gündüz kullanımı için ek oref1 özelliklerinin etkinleştirilmesi - -- SMB'nin nasıl çalıştığını, özellikle de sıfır-geçici ardındaki fikri anlamak için [bu wiki'deki SMB bölümünü](Open-APS-features-super-micro-bolus-smb) ve [openAPSdocs'taki oref1 bölümünü](https://openaps.readthedocs.io/en/latest/docs/Customize-Iterate/oref1.html) okumalısınız. -- Daha sonra, SMB'lerin düzgün çalışmasını sağlamak için [maxAİNS'i artırmanız](Open-APS-features-maximum-total-iob-openaps-cant-go-over-openaps-max-iob) gerekir. maxAİNS artık yalnızca eklenmiş bazal değil, tüm AİNS'leri içeriyor. Yani bir öğün için 8 Ü bolus verilirse ve maksAİNS 7 Ü ise, AİNS 7 Ü'nin altına düşene kadar hiçbir SMB iletilmez. İyi bir başlangıç maksAİNS = ortalama yemek bolusu + 3x maks günlük bazaldir (maks günlük bazal = günün herhangi bir zaman diliminde maksimum saatlik değer - bir örnek için [Görev 7'ye](Objectives-objective-7-tuning-the-closed-loop-raising-max-iob-above-0-and-gradually-lowering-bg-targets) bakın) -- absorpsiyon ayarlarındaki min_5m_carbimpact varsayılanı, AMA'dan SMB'ye giderken 3'ten 8'e değiştirildi. AMA'dan SMB'ye yükseltme yapıyorsanız, bunu manuel olarak değiştirmeniz gerekir. - -(Objectives-objective-10-automation)= -## Görev 10: Otomasyon - -- [Otomasyon](../Usage/Automation.md)u kullanabilmek için 10. göreve başlamanız gerekir. -- [Görevler-görev-3-bilgini-kanıtla](Objectives#objective-3-prove-your-knowledge) sınavı dahil tüm görevleri tamamladığınızdan emin olun. -- Önceki görevleri tamamlamak, halihazırda tamamladığınız diğer görevleri etkilemeyecektir. Tüm tamamlanmış görevler korunacaktır! - -(Objectives-objective-11-DynamicISF)= -## Objective 11: Additional Features such as DynamicISF - -- You have to start objective 11 to be able to use [DynamicISF](../Usage/Open-APS-features.md) - -(Objectives-go-back-in-objectives)= -## Görevlere geri dön - -Herhangi bir nedenle görevlere geri dönmek istiyorsanız, bunu "Komple tamamlandı" seçeneğine tıklayarak yapabilirsiniz. - -```{image} ../images/Objective_ClearFinished.png -:alt: Görevlere geri dön -``` - -## 3.0 sürümünden önceki Android APS'deki görevler - -Android APS 3.0 yayınlandığında bir hedef kaldırıldı. Android APS sürüm 2.8.2.1'in eski Android yazılımı (yani sürüm 9'dan önceki) kullanıcıları [burada](../Usage/Objectives_old.md) bulunabilecek daha eski bir görev seti kullanıyor olacak. diff --git a/docs/CROWDIN/tr/Usage/Objectives_old.md b/docs/CROWDIN/tr/Usage/Objectives_old.md deleted file mode 100644 index bf67dcea3311..000000000000 --- a/docs/CROWDIN/tr/Usage/Objectives_old.md +++ /dev/null @@ -1,152 +0,0 @@ -# Android APS 2.8.2.1 itibariyle görevler - -Bu, Android APS Görevlerinin en son sürümü değil. Bu sayfa, sürüm 3.0'dan önce yürürlükte olan görevleri detaylandırır. Anyone using an older version of Android (i.e. prior to Android 9) and Android APS version 2.8.2.1 should refer to this page. - -Please see [this page](../Usage/Objectives.md) for the current set of Objectives. - -AndroidAPS, güvenli döngü özellikleri ve ayarlarında size yol göstermek için tamamlanması gereken bir dizi Görevlere sahiptir. Yukarıdaki bölümlerde ayrıntıları verilen her şeyi doğru bir şekilde yapılandırdığınızdan ve sisteminizin ne yaptığını ve neden ona güvenebileceğinizi anladığınızdan emin olurlar. - -If you are **upgrading phones** then you can [export your settings](../Usage/ExportImportSettings.md) to keep your progress through the objectives. Not only will your progress through the objectives be saved, but also your safety settings such as max bolus etc. If you do not export and import your settings then you will need to start the objectives from the beginning again. It is a good idea to [backup your settings](../Usage/ExportImportSettings.html) frequently just in case. - -If you want to go back in objectives see [explanation below](../Usage/Objectives.md#go-back-in-objectives). - -## Görev 1: Görselleştirme ve izleme ayarları, bazal ve oranlarını analize etme - -- Select the right blood glucose source for your setup. See [BG Source](../Configuration/BG-Source.md) for more information. -- Select the right Pump in ConfigBuilder (select Virtual Pump if you are using a pump model with no AndroidAPS driver for looping) to ensure your pump status can communicate with AndroidAPS. -- If using DanaR pump then ensure you have followed [DanaR Insulin Pump](../Configuration/DanaR-Insulin-Pump.md) instructions to ensure the link between pump and AndroidAPS. -- Follow instructions in [Nightscout](../Installing-AndroidAPS/Nightscout.md) page to ensure Nightscout can receive and display this data. -- Note that URL in NSClient must be **WITHOUT /api/v1/** at the end - see [NSClient settings in Preferences](../Configuration/Preferences.md#nsclient). - -*You may need to wait for the next blood glucose reading to arrive before AndroidAPS will recognise it.* - -## Görev 2: AndroidAPS'yi nasıl kontrol edeceğinizi öğrenin - -- Perform several actions in AndroidAPS as described in this objective. - -- Click on the orange text "Not completed yet" to access the to-dos. - -- Links will be provided to guide you in case you are not familiar with a specific action yet. - - ![Screenshot Görev 2](../images/Objective2_V2_5.png) - -## Görev 3: Bilginizi kanıtlayın - -- Pass a multiple-choice exam testing your AndroidAPS knowledge. - -- Click on the orange text "Not completed yet" to access the page with the question and answering options. - - ![Screenshot Görev 3](../images/Objective3_V2_5.png) - -- Links will be provided to guide you in case you are unsure about the correct answers yet. - -- The questions for objective 3 have been completely rewritten by native speakers as of AAPS 2.8. Yenileri aynı temel konuları ve birkaç yeni konuyu kapsar. - -- These new questions will lead to some not answered questions even though you have successfully completed objective 3 in previous versions. - -- Unanswered questions will affect you only if you start a new objective. Başka bir deyişle: Tüm görevleri zaten tamamladıysanız, daha sonra AAPS işlevlerini kaybetmeden bekleyebilir ve yeni soruları yanıtlayabilirsiniz. - -## Görev 4: Bir Açık döngüye başlamak - -- Select Open Loop either from Preferences, or by pressing and holding the Loop button in top left of the home screen. -- Work through the [Preferences](../Configuration/Preferences.md) to set up for you. -- Manually enact at least 20 of the temporary basal rate suggestions over a period of 7 days; input them to your pump and confirm in AndroidAPS that you have accepted them. Bu verilerin AndroidAPS ve Nightscout'ta gösterildiğinden emin olun. -- Enable [temp targets](../Usage/temptarget.md) if necessary. Bir hipodan sonra yükselen kan şekeri nedeniyle sistemin çok güçlü düzeltme yapmasını önlemek için hipo geçici hedeflerini kullanın. - -### Bildirim sayısını azaltın - -- To reduce the Number of decisions to be made while in Open Loop set wide target range like 90 - 150 mg/dl or 5,0 - 8,5 mmol/l. - -- You might even want to wider upper limit (or disable Open Loop) at night. - -- In Preferences you can set a minimum percentage for suggestion of basal rate change. - - ![Açık Döngü minimum istek değişikliği](../images/OpenLoop_MinimalRequestChange2.png) - -- Also, you do not need to act every 5 minutes on all suggestions... - -## Görev 5: Geçici bazal önerileri de dahil olmak üzere açık döngünüzü anlamak - -- Start to understand the thinking behind the temp basal recommendations by looking at the [determine basal logic](https://openaps.readthedocs.io/en/latest/docs/While%20You%20Wait%20For%20Gear/Understand-determine-basal.html) and both the [forecast line in AndroidAPS homescreen](../Getting-Started/Screenshots.md#prediction-lines)/Nightscout and the summary of outputs from the calculations in your OpenAPS tab. - -Hesaplamalardan ve ayarlardan emin olana kadar hedefinizi normalden daha yükseğe koymak isteyeceksiniz. Sistem izin verdiğince - -- a low target to be a minimum of 4 mmol (72 mg/dl) or maximum of 10 mmol (180 mg/dl) -- a high target to be a minimum of 5 mmol (90 mg/dl) and maximum of 15 mmol (225 mg/dl) -- a temporary target as a single value can be anywhere in the range of 4 mmol to 15 mmol (72 mg/dl to 225 mg/dl) - -Hedef hesaplamaların dayandığı değerdir ve kan şekeri değerlerinizi içinde tutmayı amaçladığınız değerle aynı değildir. If your target is very wide (say, 3 or more mmol \[50 mg/dl or more\] wide), you will often find little AAPS action. Bunun nedeni, kan şekerinin eninde sonunda bu geniş aralıkta bir yerde olacağı tahmin edilmesidir ve bu nedenle çok fazla dalgalı geçici bazal hız önerilmemektedir. - -You may want to experiment with adjusting your targets to be a closer together range (say, 1 or less mmol \[20 mg/dl or less\] wide) and observe how the behavior of your system changes as a result. - -You can view a wider range (green lines) on the graph for the values you aim to keep your blood glucose within by entering different values in [Preferences](../Configuration/Preferences.md) > Range for Visualisation. - -![Dur işareti](../images/sign_stop.png) - -### Sanal bir pompa ile açık döngü yapıyorsanız burada durun - bu hedefin sonunda sakın Doğrula'ya tıklamayın. - -![boş](../images/blank.png) - -## Görev 6: Düşük KŞ'de Duraklatma ile döngüyü kapatmaya başlamak - -![Uyarı işareti](../images/sign_warning.png) - -### Kapalı döngü, düşük glikoz duraklatma ile sınırlı olduğundan, görev 6'daki yüksek kş değerlerini düzeltmeyecektir. Yüksek kş değerleri sizin tarafınızdan manuel olarak düzeltilmelidir! - -- Select Closed Loop either from [Preferences](../Configuration/Preferences.md) or by pressing and holding the Open Loop button in the top left of the home screen. - -- Set your target range slightly higher than you usually aim for, just to be safe. - -- Watch how temporary basals are active by viewing the blue basal text on the homescreen or the blue basal render on the homescreen graph. - -- Ensure your settings have supported AndroidAPS to avoid having to treat a low glucose over a period of 5 days. Hala sık veya şiddetli düşük glikoz atakları yaşıyorsanız, DIA, bazal, ISF ve karbonhidrat oranlarınızı iyileştirmeyi düşünün. - -- You don't have to change your settings. Görev 6 sırasında maxAİNS ayarı dahili olarak otomatik olarak sıfıra ayarlanır. Görev 7'ye geçildiğinde bu geçersiz kılma tersine çevrilecektir. - -- The system will override your maxIOB settings to zero, which means if blood glucose is dropping it can reduce basal for you, but if blood glucose is rising then it will only increase basal if the basal IOB is negative (from a previous Low Glucose Suspend), otherwise basal rates will remain the same as your selected profile. - - ![Örnek negatif AİNS](../images/Objective6_negIOB.png) - -- If your basal IOB is negative (see screenshot above) a TBR > 100% can be issued also in objective 6. - -- Bazal artırma yeteneği olmadan tedavi edilen hipoları takiben geçici olarak ani artışlar yaşayabilirsiniz. - -## Görev 7: Kapalı döngüyü ayarlamak, maksimum AİNS'i 0'ın üzerine çıkarmak ve KŞ hedeflerini kademeli olarak düşürmek - -- Raise your 'Maximum total IOB OpenAPS can’t go over' (in OpenAPS called 'max-iob') above 0 over a period of 1 day, the default recommendation is "average mealbolus + 3x max daily basal"(for SMB algorithm) or "3x max daily basal" (for older AMA algorithm) but you should slowly work up to this until you know your settings work for you (max daily basal = the maximum hourly value in any time segment of the day). - - Bu öneri bir başlangıç noktası olarak görülmelidir. 3x'e ayarladıysanız ve sizi sert ve hızlı şekilde düşürüyorsa, o sayıyı düşürün. Eğer çok dirençliyseniz, her seferinde çok az yükseltin. - - ![maks günlük bazal](../images/MaxDailyBasal2.png) - -- Once confident on how much IOB suits your looping patterns then reduce your targets to your desired level. - -## Görev 8: Gerekirse bazalleri ve oranları ayarlayın ve ardından otoduyarlılığı etkinleştirin - -- You can use [autotune](https://openaps.readthedocs.io/en/latest/docs/Customize-Iterate/autotune.html) as a one off to check your basals remain accurate or do a traditional basal test. -- Enable [autosens](../Usage/Open-APS-features.md) over a period of 7 days and watch the white line on the homescreen graph show how your sensitivity to insulin may be rising or falling as a result of exercise or hormones etc. and keep an eye in the OpenAPS report tab how AndroidAPS is adjusting the basals and/or targets accordingly. - -*Don’t forget to record your looping in* [this form](https://bit.ly/nowlooping) *logging AndroidAPS as your type of DIY loop software, if you have not already done so.* - -## Görev 9: Gündüz kullanımı için ek özellikleri deneyin ve kapalı döngü sisteminize güvenin - -- Before AAPS version 2.7 meal assist (MA) was the basic algorithm for AAPS and completing objective 8 was necessary to activate [advanced meal assist (AMA)](../Usage/Open-APS-features.md#advanced-meal-assist-ama). -- As [advanced meal assist (AMA)](../Usage/Open-APS-features.md#advanced-meal-assist-ama) is the standard algorithm from AAPS version 2.7 onwards use the following 28 days to try features you haven't used yet and get more confident with you closed loop system. - -## Görev 10: Süper mikro bolus (SMB) gibi gündüz kullanımı için ek oref1 özelliklerinin etkinleştirilmesi - -- You must read the [SMB chapter in this wiki](../Usage/Open-APS-features.md#super-micro-bolus-smb) and [chapter oref1 in openAPSdocs](https://openaps.readthedocs.io/en/latest/docs/Customize-Iterate/oref1.html) to understand how SMB works, especially what's the idea behind zero-temping. -- Then you ought to [rise maxIOB](../Usage/Open-APS-features.md#maximum-total-iob-openaps-cant-go-over-openaps-max-iob) to get SMBs working fine. maxAİNS artık yalnızca eklenmiş bazal değil, tüm AİNS'leri içeriyor. That is, if given a bolus of 8 U for a meal and maxIOB is 7 U, no SMBs will be delivered until IOB drops below 7 U. A good start is maxIOB = average mealbolus + 3x max daily basal (max daily basal = the maximum hourly value in any time segment of the day - see [objective 7](../Usage/Objectives#objective-7-tuning-the-closed-loop-raising-max-iob-above-0-and-gradually-lowering-bg-targets) for an illustration) -- min_5m_carbimpact default in absorption settings has changed from 3 to 8 going from AMA to SMB. AMA'dan SMB'ye yükseltme yapıyorsanız, bunu manuel olarak değiştirmeniz gerekir. - -## Görev 11: Otomasyon - -- You have to start objective 11 to be able to use [Automation](../Usage/Automation.md). -- Make sure you have completed all objectives including exam [../Usage/Objectives.md#objective-3-prove-your-knowledge](../Usage/Objectives#objective-3-prove-your-knowledge). -- Completing previous objectives will not effect other objectives you have already finished. Tüm tamamlanmış görevler korunacaktır! - -## Görevlere geri dön - -Herhangi bir nedenle görevlere geri dönmek istiyorsanız, bunu "Komple tamamlandı" seçeneğine tıklayarak yapabilirsiniz. - -![Görevlere geri dön](../images/Objective_ClearFinished.png) diff --git a/docs/CROWDIN/tr/Usage/Smoothing-Blood-Glucose-Data-in-xDrip.md b/docs/CROWDIN/tr/Usage/Smoothing-Blood-Glucose-Data-in-xDrip.md deleted file mode 100644 index 9b30e918883e..000000000000 --- a/docs/CROWDIN/tr/Usage/Smoothing-Blood-Glucose-Data-in-xDrip.md +++ /dev/null @@ -1,33 +0,0 @@ -(Smoothing-Blood-Glucose-Data-in-xDrip-smoothing-blood-glucose-data)= - -# Kan şekeri verilerini yumuşatma - -KŞ verileri atlamalı/gürültülü ise, AAPS insülini yanlış dozlayarak yüksek veya düşük KŞ'ne sebep olabilir. Bu nedenle, sorun çözülene kadar döngüyü devre dışı bırakmak önemlidir. CGM'nize bağlı olarak, bu tür sorunlar CGM'in yapılandırmasından veya sensör/set sorunlarından kaynaklanabilir. Bunu çözmek için CGM sensörünüzü değiştirmeniz gerekebilir. - -Some CGM systems have internal algorithms to detect the noise level in the readings and AAPS can use this information to avoid giving SMBs if the BG data is too unreliable. Ancak, bazı CGM'ler bu verileri iletmez ve bu KŞ kaynakları için 'SMB'yi her zaman etkinleştir' ve 'Karbonhidrattan sonra SMB'yi etkinleştir' güvenlik nedenleriyle devre dışı bırakılır. - -## Dexcom sensörleri - -### Kendi Dexcom Uygulamanızı Oluşturun (BYODA) - -[BYODA](DexcomG6-if-using-g6-with-build-your-own-dexcom-app) kullanırken KŞ verileriniz sorunsuz ve tutarlıdır. Ayrıca Dexcom'un geri-yumuşatma özelliğinden yararlanabilirsiniz. Gürültü seviyesi verileri AAPS ile paylaşıldığı için SMB'lerin kullanımında herhangi bir kısıtlama yoktur. - -### Dexcom G6 veya Dexcom ONE ile xDrip+ - -Gürültü düzeyi verileri ve yumuşak KŞ okumaları, yalnızca xDrip+ [yerel modunu](https://navid200.github.io/xDrip/docs/Native-Algorithm) kullanıyorsanız AAPS ile paylaşılır. Yerel modu kullanırken, SMB'lerin kullanımında herhangi bir kısıtlama yoktur. - -### Dexcom G6 veya Dexcom ONE ile xDrip+ Tamamlayıcı Mod - -Gürültü düzeyi verileri, bu yöntem kullanılarak AAPS ile paylaşılmaz. Bu nedenle 'SMB'yi her zaman etkinleştir' ve 'Karbonhidrattan sonra SMB'yi etkinleştir' devre dışı bırakılır. - -## Freestyle Libre sensörleri - -### FreeStyle Libre ile xDrip+ - -FreeStyle Libre sistemlerinin hiçbiri (FSL1, FSL2 veya FSL3), okumalarda algılanan gürültü seviyesi hakkında herhangi bir bilgi yayınlamaz ve bu nedenle FreeStyle Libre kullanan tüm kurulumlar için 'SMB'yi her zaman etkinleştir' ve 'Karbonhidrattan sonra SMB'yi etkinleştir' devre dışı bırakılır. - -Ek olarak, birçok kişi FreeStyle Libre'nin genellikle gürültülü veriler ürettiğini bildirmiştir. xDrip+'ta bu konuda yardımcı olacak birkaç seçenek vardır: - -**Pürüzsüz Sensör Gürültüsü.** xDrip Ayarları > xDrip Ekran Ayarları'nda, smooth sensor noise "Pürüzsüz Sensör Gürültüsü"nün açık olduğundan emin olun. Bu, gürültülü verilerde yumuşatma uygulamaya çalışır. - -**Pürüzsüz Sensör Gürültüsü (Ultra Duyarlı).** xDrip+'ta hala parazitli veriler görüyorsanız, Pürüzsüz Sensör Gürültüsü (Ultra Duyarlı) ayarını kullanarak daha agresif yumuşatma uygulayabilirsiniz. Bu, algılanan gürültünün çok düşük seviyelerinde bile yumuşatma uygulamaya çalışacaktır. Bunu yapmak için önce xDrip+'ta [mühendislik modunu](Enabling-Engineering-Mode-in-xDrip.md) etkinleştirin. Ardından Ayarlar > xDrip+ Ekran Ayarları'na gidin ve Pürüzsüz Sensör Gürültüsü'nü (Ultra Duyarlı) açın. \ No newline at end of file diff --git a/docs/CROWDIN/tr/Usage/autotune_b.md b/docs/CROWDIN/tr/Usage/autotune_b.md deleted file mode 100644 index 4ba8469e68d7..000000000000 --- a/docs/CROWDIN/tr/Usage/autotune_b.md +++ /dev/null @@ -1,186 +0,0 @@ -# Otoayar eklentisi nasıl kullanılır? - -Otoayar algoritması hakkında daha fazla ayrıntıyı [OpenAPS dokümantasyonu](https://openaps.readthedocs.io/en/latest/docs/Customize-Iterate/autotune.html)nda bulabilirsiniz. - -Otoayar eklentisi, AAPS içindeki OpenAPS otoayar algoritmasının uygulanmasıdır. - -**Şu anda otoayar eklentisi yalnızca mühendislik modundaki geliştirici sürümünde mevcuttur.** - -## Otoayar kullanıcı arabirimi - -![Otoayar varsayılan ekranı](../images/Autotune/Autotune_1b.png) - -- Ayarlamak istediğiniz giriş profilini Profil açılır menüsünden seçebilirsiniz (varsayılan olarak mevcut etkin profiliniz seçilidir) - - Not: Her yeni profil seçiminde, önceki sonuçlar kaldırılacak ve Gün Ayar parametreleri varsayılan değere ayarlanacaktır. -- Ayar günleri, profilinizi ayarlamak için hesaplamada kullanılan gün sayısını içermektedir. Minimum değer 1 gün ve maksimum değer 30 gündür. Doğru yinelemeli ve sorunsuz sonuçlar elde etmek için bu sayı çok küçük olmamalıdır (her hesaplama için 7 günden fazla) - - Not: Ayar günleri parametresini her değiştirdiğinizde, önceki sonuçlar kaldırılacaktır -- Son Çalıştırma, en son geçerli hesaplamanızı kurtaran bir bağlantıdır. Otoayarı o gün başlatmadıysanız veya yukarıdaki hesaplama parametresinin değiştirilmesiyle önceki sonuçlar kaldırıldıysa, en son başarılı çalıştırmanın parametrelerini ve sonuçlarını kurtarabilirsiniz. -- Uyarı size örneğin seçilen profil hakkında bazı bilgiler gösterir (birkaç Kİ değeriniz veya birkaç İDF değeriniz varsa) - - Not: Otomatik ayar hesaplaması yalnızca tek bir Kİ ve tek bir İDF değeriyle çalışır. Şu anda bir sirkadiyen Kİ veya sirkadiyen İDF'yi ayarlamak için mevcut bir OtoAyar algoritması yoktur. Giriş profilinizin birkaç değeri varsa, profilinizi ayarlamak için dikkate alınan ortalama değeri uyarı bölümünde görebilirsiniz. -- Giriş Profilini Kontrol Et düğmesi, profilinizi (Ünite, İES, Kİ, İDF, bazal ve hedef) hızlı bir şekilde doğrulamanıza izin vermek için Profil Görüntüleyiciyi açar. - - Not: OtoAyar, yalnızca Kİ (tek değer), İDF (tek değer) ve bazal (sirkadiyen varyasyonlu) ayarlarınızı yapacaktır. Üniteler, İES ve hedef, çıktı profilinde değişmeden kalacaktır. - -- "OtoAyarı Çalıştır", seçili profil ve ayarlama gün sayısı ile OtoAyar hesaplamasını başlatır - - Not: Otomatik ayar hesaplaması uzun sürebilir. Başlatıldıktan sonra, başka bir görünüme (ev, ...) geçebilir ve sonuçları görmek için daha sonra otoayar eklentisinde geri dönebilirsiniz - -![Otoayar Çalışmayı başlat](../images/Autotune/Autotune_2b.png) - -- Ardından çalıştırma sırasında aşağıda ara sonuçları göreceksiniz - - - Not: Çalıştırma sırasında ayarlar kilitlenir, bu nedenle artık seçilen giriş profilini veya gün sayısını değiştiremezsiniz. Diğer parametrelerle başka bir çalıştırma başlatmak istiyorsanız mevcut hesaplamanın bitmesini beklemeniz gerekecektir. - - ![Otoayar çalışıyor](../images/Autotune/Autotune_3b.png) - -- OtoAyar hesaplaması bittiğinde, sonucu (Ayarlanmış profil) ve aşağıda dört buton göreceksiniz. - -![Otoayar Sonucu](../images/Autotune/Autotune_4b.png) - -- Girdi profilini ("Profil" sütunu), çıktı profilini ("Ayar" sütunu) ve her değer için varyasyon yüzdesini ("%" Sütunu) her zaman karşılaştırmak önemlidir. - -- Bazal oranlar için "kayıp gün" sayısına da sahipsiniz. Otoayarın bu dönemde bazal oranı ayarlamak için "Bazal" olarak kategorize edilmiş yeterli veriye sahip olmadığı durumlarda (örneğin, her yemekten sonra karbonhidrat emilimi durumunda) eksik günleriniz olacaktır. Bu sayı, özellikle bazal önemli olduğunda (örneğin gece veya öğleden sonra) mümkün olduğunca düşük olmalıdır. - -- "Profilleri karşılaştır" butonu, profil karşılaştırıcı görünümünü açar. Giriş profili mavi ve çıkış profili ("Ayarlanmış" olarak adlandırılır) kırmızıdır. - - - Not: Aşağıdaki örnekte, giriş profilinin Kİ ve İDF için sirkadiyen değişimi vardır, ancak hesaplanan çıktı profilinin tek bir değeri vardır. Bir sirkadiyen çıktı profili almanız sizin için önemliyse aşağıdaki [Sirkadiyen Kİ veya İDF profiline](#circadian-ic-or-isf-profile) bakın. - - ![Otoayar profil karşılaştırma](../images/Autotune/Autotune_5.png) - -- Sonuçlara güveniyorsanız, (giriş profili ile çıktı profili arasında düşük yüzdeli farklılık) "Profili etkinleştir" düğmesine tıklayabilir ve ardından doğrulamak için Tamam'a tıklayabilirsiniz. - - - Ayarlanmış profili etkinleştirin, Yerel profil eklentinizde otomatik olarak yeni bir "Ayarlanmış" profil oluşturacaktır. - - Yerel profil eklentinizde zaten "Ayarlanmış" (Tuned) adlı bir profiliniz varsa, bu profil aktivasyondan önce hesaplanan Otoayar profiliyle güncellenecektir. - - ![Otoayar profil etkinleştirme](../images/Autotune/Autotune_6.png) - -- Ayarlanmış profilin gerektiğini düşünüyorsanız (örneğin, bazı varyasyonların çok önemli olduğunu düşünüyorsanız), "Yerel profile kopyala" düğmesine tıklayabilirsiniz. - - - Yerel profil eklentisinde "Ayarlanmış" ön ekine ve çalıştırmanın tarih ve saatine sahip yeni bir profil oluşturulacak - -![Otoayar yerel profile kopyalama](../images/Autotune/Autotune_7.png) - -- Ardından, Ayarlanmış profilini düzenlemek için yerel profili seçebilirsiniz (Yerel profil eklentisini açtığınızda varsayılan olarak seçilecektir) - - - yerel profildeki değerler ancak kullanıcı arabiriminde pompa kapasitenize yuvarlanır - - ![Otoayar yerel profil güncelleme](../images/Autotune/Autotune_8.png) - -- Giriş profilinizi Otoayar sonuçlarıyla değiştirmek isterseniz, "Giriş profilini güncelle" düğmesine tıklayın ve açılan pencereyi Tamam ile onaylayın - - - Not: "Giriş profilini güncelle"den sonra "Profili etkinleştir"e tıklarsanız, varsayılan "Ayarlanmış" profili değil, güncellenmiş profilinizi etkinleştirirsiniz. - - ![Otoayar giriş profilini güncelleme](../images/Autotune/Autotune_9.png) - -- Giriş profilinizi güncellediyseniz, "Giriş profilini güncelle" butonunun yerini "Giriş profilini geri al" butonu alır (aşağıdaki ekran görüntüsüne bakın). Bu şekilde, Yerel profil eklentisindeki mevcut giriş profilinizin zaten son çalıştırmanın sonucunu içerip içermediğini hemen görebilirsiniz. Ayrıca, bu buton ile otoayar sonucu olmadan giriş profilinizi kurtarma olanağına da sahipsiniz. - - ![Otoayar giriş profilini güncelleme](../images/Autotune/Autotune_10.png) - - - -## OtoAyar ayarları - -### Otoayar eklenti ayarları - -![Otoayar varsayılan ekranı](../images/Autotune/Autotune_11.png) - -- Otomasyon ile Profil değiştirme (varsayılan Kapalı): aşağıdaki [Otoayarı bir otomasyon kuralıyla çalıştırma](#run-autotune-with-an-automation-rule) bölümüne bakın. Bu ayarı Açık olarak değiştirirseniz, giriş profili Ayarlanmış profil tarafından otomatik olarak güncellenecek ve etkinleştirilecektir. - - **Dikkatli Olun, Ayarlanmış profilin güncellenmesi ve etkinleştirilmesinden sonra döngünüzü iyileştirdiğine güvenmeli ve takip eden birkaç gün boyunca bunu doğrulamalısınız.** - -- UAM'ı bazal olarak kategorize et (varsayılan Açık): Bu ayar, herhangi bir karbonhidrat girmeden AndroidAPS kullanan kullanıcılar içindir (Tam UAM). (Kapalı olduğunda) UAM'ın bazal olarak kategorize edilmesini önleyecektir. - - Not: Bir gün boyunca tespit edilen en az bir saatlik karbonhidrat emiliminiz varsa, bu ayar ne olursa olsun (Açık veya Kapalı) "UAM" olarak sınıflandırılan tüm veriler bazal olarak kategorize edilir. -- Veri gün sayısı (varsayılan 5): Bu ayar ile varsayılan değer tanımlayabilirsiniz. Otoayar eklentisinde her yeni profil seçtiğinizde, Ayar günleri parametresi bu varsayılan değerle değiştirilecektir. -- Ortalama sonucu sirkadiyen Kİ/İDF olarak uygulayın (varsayılan Kapalı): aşağıdaki [Sirkadiyen Kİ veya İDF profiline](#circadian-ic-or-isf-profile) bakın. - -### Diğer ayarlar - -- Otoayar, varyasyonu sınırlandırmak için Maks. otoduyarlılık oranı ve Min. otoduyarlılık oranı da kullanır. Bu değerleri; Konfigürasyon ayarları > Hassasiyet algılama eklentisi > Ayarlar > Gelişmiş Ayarlarda görebilir ve ayarlayabilirsiniz. - - ![Otoayar varsayılan ekranı](../images/Autotune/Autotune_12.png) - - - -## Gelişmiş özellik - -### Sirkadiyen Kİ veya İDF profili - -- Profilinizde önemli Kİ ve/veya İDF varyasyonlarınız varsa ve sirkadiyen zamanınıza ve varyasyonunuza tamamen güveniyorsanız, "Sirkadiyen İK/İDF'de ortalama sonucu uygula" ayarını yapabilirsiniz. - - - Otoayar hesaplamasının her zaman tek bir değerle yapılacağını ve sirkadiyen varyasyonun Otoayar tarafından ayarlanmayacağına dikkat edin. Bu ayar yalnızca sirkadiyen değerlerinizde Kİ ve/veya İDF için hesaplanan ortalama değişimi uygular. - -- Ortalama varyasyonu uygula Kapalı (solda) ve Açık (sağda) ile Ayarlanmış profilin altındaki ekran görüntüsüne bakın - - ![Otoayar varsayılan ekranı](../images/Autotune/Autotune_13.png) - - - -### Haftanın belirli günlerine ayarlama - -- "Çalışma günleri" parametresinin sağındaki göz ile onay kutusuna tıklarsanız, gün seçimini göreceksiniz. Haftanın hangi gününün Otoayar hesaplamasına dahil edileceğini belirleyebilirsiniz (aşağıdaki ekran görüntüsünde Cumartesi ve Pazar günleri otoayar hesaplamasından çıkarılmış "çalışma günleri" örneğini görebilirsiniz) - - Otoayar hesaplamasına dahil edilen gün sayısı Ayar gün sayısından az ise Ayar günleri seçicinin sağında kaç gün dahil edileceğini göreceksiniz (aşağıdaki örnekte 10 gün) - - Bu ayar, ancak kalan gün sayısı küçük değilse iyi sonuçlar verir (örneğin, yalnızca Pazar ve Cumartesi seçili olarak hafta sonu günleri için belirli bir profili Ayarladıysanız, Otomatik Ayar hesaplamasına 6 veya 8 gün dahil etmek için en az 21 veya 28 Ayar günü seçmelisiniz) - -![Otoayar varsayılan ekranı](../images/Autotune/Autotune_14b.png) - -- OtoAyar hesaplaması sırasında, hesaplamaların ilerleyişini görebilirsiniz (Aşağıdaki örnekte "Kısmi sonuç 3 / 10 gün ayarlandı") - - ![Otoayar varsayılan ekranı](../images/Autotune/Autotune_15b.png) - -## Otomasyon kuralı ile Otoayar çalıştırma - -İlk adım, otomasyon kuralı için doğru tetikleyiciyi Otoayar tanımlamaktır: - -Not: Bir otomasyon kuralının nasıl ayarlanacağı hakkında daha fazla bilgi için [buraya](./Automation.rst) bakın. - -- Yinelenen Zaman Tetikleyicisi'ni seçmelisiniz: sadece günde bir kez otomatik olarak çalıştırın ve Otoayar günlük olarak çalıştırılacak şekilde tasarlanmıştır (bir gün sonraki her yeni çalışma için profil modifikasyonu minik olmalıdır) - - ![Otoayar varsayılan ekranı](../images/Autotune/Autotune_16.png) - -- Sonuçları kontrol edebilmek için Otoayarı gün boyunca çalıştırmak daha iyidir. Gece boyunca Otoayarı çalıştırmak istiyorsanız, bir sonraki Otoayar hesaplamasına şu anki gün de dahil tetikleme için saat 4 veya daha sonrasını seçmeniz gerekir. - - ![Otoayar varsayılan ekranı](../images/Autotune/Autotune_17.png) - -- Ardından listede "Otoayarı Çalıştır" eylemini seçebilirsiniz - - ![Otoayar varsayılan ekranı](../images/Autotune/Autotune_18.png) - -- Ardından, çalıştırmanız için gerekli parametreleri ayarlamak için Otoayar eylemini seçebilirsiniz. Varsayılan parametreler "Aktif Profil", Otoayar eklentisi tercihlerinde tanımlanan varsayılan ayar günleri değeridir ve tüm günler seçilir. - - ![Otoayar varsayılan ekranı](../images/Autotune/Autotune_19b.png) - -- Birkaç gün sonra, Otoayar sonuçlarına tam olarak güveniyorsanız ve değişiklik yüzdesi düşükse, [ Otoayar Ayarları ](#autotune-plugin-settings) "Profili değiştirme Otomasyonu" modifiye edilerek hesaplamadan sonra ayarlanan profil otomatik olarak güncellenebilir ve etkinleştirebilir. - -Not: Profilleri haftanın belirli günleri için otomatik olarak ayarlamak istiyorsanız (örneğin, "Hafta sonu günleri" için bir profil ve "Çalışma günleri" için başka bir profil) her profil için bir kural oluşturun. OtoAyar eyleminde tetiklemede aynı günleri seçin ve ayar günlerinin yeterince yüksek olduğundan emin olmak için en az 6 veya 8 gün ve tetiklemede saat 4:00'ten sonraki zaman seçilmelidir... - -- Aşağıda, 14 Ayar günü seçili olarak tüm "Çalışma günleri"nde "profilim"i ayarlamak için bir kural örneğine bakabilirsiniz (yani, otomatik ayar hesaplamasına yalnızca 10 gün dahildir). - -![Otoayar varsayılan ekranı](../images/Autotune/Autotune_20b.png) - - - -## Ipuçları ve Püf noktaları - -Otoayar, veritabanınızda bulunan bilgilerle çalışır, bu nedenle AAPS yeni bir telefona henüz yüklendiyse, ilgili sonuçları almak için yeterli günle Otoayarı başlatmadan önce birkaç gün beklemeniz gerekecektir; - -Otoayar sadece bir yardımdır, hesaplanan profille hemfikir olup olmadığınızı düzenli olarak kontrol etmek önemlidir. Herhangi bir şüpheniz varsa, Otoayar (örneğin gün sayısını) ayarlarını değiştirin veya yerel profildeki sonuçları kopyalayın ve kullanmadan önce profili ayarlayın. - -Her zaman Otoayarı birkaç gün manuel olarak kullanın ve uygulamadan önce sonuçları kontrol edin. Ve yalnızca, Otoayar sonuçlarına tam olarak güvendiğinizde ve önceki profil ile hesaplanan profil arasında değerler, otomasyonu kullanmaya başladığınızdan bu yana küçükse kullanın. (Daha önce değil) - -- Otoayar, bazı kullanıcılar için çok iyi çalışabilir ve bazıları için çalışmaz, bu nedenle ** Otoayara güvenmiyorsanız, kullanmayın ** - -Otoayarın neden bu değişiklikleri önerdiğini anlamak (veya anlamaya çalışmak) için otoayar sonuçlarını analiz etmek de önemlidir. - -- Profil direncinizin bir artışı veya azalması olabilir (örneğin, İDF ve Kİ değerlerinin azalmasıyla ilişkili toplam bazal artışı). Otoduyarlılık % 100'ün üzerinde (daha fazla agresif) veya% 100'ün altında (daha hassassınız) sonraki birkaç gün ile ilişkilendirilebilir. -- Bazen Otoayar, bazal oranlar ve Kİ/İDF arasında farklı bir denge önerir (önceki düşük bazal ve daha agresif Kİ/İDF için) - -Aşağıdaki durumlarda Otoayar kullanmayı tavsiye etmiyoruz: - -- Tüm karbonhidratları girmiyorsanız - - Bir hipoglisemideki karbonhidrat düzeltmesini girmezseniz, Otoayar, KŞ değerinizde anlaşılmaz bir artış görecek ve saatlerce bazal oranlarınızı arttıracaktır. Özellikle de gece yarısı hipodan kaçınmanız gerekirken tam tersi olabilir. Bu yüzden tüm karbonhidraları, özellikle hipo için yapılan düzeltmeleri girmek önemlidir. -- Gün boyunca UAM tespit edilen çok fazla periyot varsa. - - Tüm karbonhidratlarınızı girdiniz ve karbonhidratlarınızı doğru tahmin ettiniz mi? - - Tüm UAM dönemleri (bir gün boyunca karbonhidrat girmezseniz ve bazal devre dışı bırakıldığı için UAM kategorize edilmezse) bazal olarak kategorize edilir ve bu bazalınızı çok artırabilir (gerekenden çok daha fazla) - -- Karbonhidrat emiliminiz çok yavaş: Karbonhidrat emiliminizin çoğu min_5m_carbimpact parametresi ile hesaplanıyorsa (bu periyotları AKRB eğrisinin üst kısmında küçük bir turuncu nokta ile görebilirsiniz), AKRB hesaplaması yanlış olabilir ve yanlış sonuçlara yol açabilir. - - Spor yapıyorsanız, genellikle daha hassassınız ve kan şekeriniz çok fazla yükselmez, bu nedenle egzersiz sırasında veya sonrasında, yavaş karbonhidratlı bazı dönemler görmek normaldir. Ancak çok sık beklenmedik yavaş karbonhidrat emiliminiz varsa, o zaman bir profil ayarlamasına (daha yüksek Kİ değeri) veya biraz yüksek bir min_5m_carbimpact'e ihtiyacınız olabilir. -- "Çok kötü günler" geçiriyorsunuz, örneğin, aralığın içine inebilmek için yüksek miktarda insülinle birkaç saat hiperglisemide kalmışsınız veya bir sensör değişikliğinden sonra uzun süre yanlış kan şekeri değerleriniz olmuş. -- Değişiklik yüzdesi çok önemliyse - - Daha sorunsuz sonuçlar almak için gün sayısını artırmayı deneyebilirsiniz. \ No newline at end of file diff --git a/docs/CROWDIN/tr/Usage/making-sport-with-AAPS.md b/docs/CROWDIN/tr/Usage/making-sport-with-AAPS.md deleted file mode 100644 index 79d2f1c38223..000000000000 --- a/docs/CROWDIN/tr/Usage/making-sport-with-AAPS.md +++ /dev/null @@ -1,185 +0,0 @@ -# making sport with AAPS - -In this section we want to address the topic of sport with AAPS. - -The aim is to show you how AAPS can help you to continue doing your favorite sport more easily or even to start doing it. It is relatively common for new type 1 diabetics to ask whether exercise is still possible for them, even if the answer in the training courses is actually a clear yes. Exercise is not only good for healthy people, but also for type 1 diabetics and even moderate exercise can even help to stabilize the blood sugar curve overall. - -:::{admonition} consult with your diabetes team after reading - -::: - -The difficulty here is that the prerequisites that someone brings with them and the expectations of what sport means to them are very different. - -Since we can assume that experienced top athletes with T1D who use AAPS are unlikely to look it up here, we deliberately set the bar low for ourselves when writing and for you when reading and using it, so that as many people as possible can benefit from it. - -Since even sport as a category is far too imprecise, as the effects of endurance sports differ greatly from strength training, for example, we are trying to break it down by type of sport. - -To be concrete and give you something you can test yourself we arrange the explanaiton around a concrete example and explain to you they action, reactions and effects. - -:::{admonition} more examples wanted - -The focus should always be on how others can do sport and not on the top performance someone has achieved. - -It's really about the basics. Your experience, which you share here, can help others to pursue their beloved sport more quickly and successfully and is therefore important. -::: - -## Cycling - -:::{admonition} take a friend with you - at least on your first trials -:class: information -A gerneral very good idea can be to take a good friend with you on the first rides. -This is especially important if you are not experienced in T1D. -Always keep in mind please: arrival comes before speed! Safety for you and the others in road traffic is very, very important. -::: - -### Example - -Let's take about 60 minutes of cycling on a flat route with a moderate heart rate as an example. - -1. we take a flat route in order to have an even load for the first exercise. This is not about performance, but purely about learning how you should react to changes in blood glucose. -2. we take the heart rate as an indicator of the load, as it is easy to see whether you are under load or not. -3. we set ourselves the goal of doing a relaxed lap around the neighborhood and focus on staying within our target range during the lap. In my case, this would be 70 <= x <= 180 mg/dl. - -We **don't** take the speed, as this is heavily dependent on personal physical conditions as well as the bike and surface used. It is therefore not very meaningful. - -You should know from the diabetes training courses you have attended that during endurance sports cycling, the insulin active in the body works significantly better than during times without physical exertion. The insulin active in the body is referred to as insulin on board (IoB). It is our most important parameter when cycling with T1D. - -We try to keep the IoB as low as possible at the start and during exercise. IoB should be around 0 or even slightly negative. You can get it there by not eating 3-4 hours before exercise. In the beginning it can also be helpful to exercise in the morning before breakfast, as with the right profile you should always have around 0 for IoB in the morning. - -AAPS shows us the IoB value on the home screen on the left under the blood glucose value. - -![IoB](../images/cycling_20240104-174035.png) - -:::{admonition} ignoring the IoB rule increases the risk for roller coaster BG dramatically -:class: danger -If you ignore this rule, you can still go cycling, but it will be much more difficult to keep your blood sugar levels in balance, so it is better to save this for later tests after several successful simple tests. -::: - -As you should know from the diabetes training courses, you should reduce the basal rate during exercise. The factor is individual. I have found a value of 50% in tests to be suitable for me. - -In AAPS, you should therefore change your profile to 50% before exercise and keep it active until the end of exercise. Some people even do it a certain amount of time before, e.g. 1 hour. Unfortunately, the pre-run is also individual. We will come to the post-run later. - -You should use two carbohydrates during exercise. - -1. medium-fast carbohydrates for the insulin still in the body and -2. very fast carbohydrates to prevent slipping into a hypo. - -For medium-fast carbohydrates, I treat myself to cookies or a banana before exercise, for example. You can also use something else that is more suitable for you. -For very fast carbohydrates, I take 3 teaspoons of dissolved glucose per 100 ml of still water in a 500 ml water bottle on my bike. If I'm cycling longer distances, I take a larger bottle with me and, if necessary, packaged glucose to refill the bottle. I add a little lemon juice for flavor. You can also use something other than lemon juice for the taste. You shouldn't change anything about the dextrose, as dissolved dextrose raises blood sugar levels super quickly. If you only take it in sips, your blood sugar won't go super high either! You can also do this tip at home beforehand as a dry run and see how quickly the change shows up on the CGMS. - -Why do I place so much emphasis on fast carbohydrates? - -1. once you are in a slight hypo, you may get back into the normal range by drinking the dextrose solution. As a rule, however, the oscillation of the curve then begins, which leads to a rollercoaster ride of the blood sugar. You may even be able to keep this within your target range, but you must be constantly vigilant. Without a hypo it is simply the most stable. -2. if you even slip into a somewhat severe hypo (without the need for outside help, of course), you may even have to pause briefly to avoid getting stuck in the hypo. - With both hypos, there is a risk that you will be tempted to switch from drinking 2-3 sips at a time to larger quantities. Not too bad at first, until the oscillation sets in and pushes you into a hyper. You can correct this, but your blood sugar will most likely go on a rollercoaster ride. - -What else is helpful, but not absolutely necessary? -It is important to keep an eye on your blood sugar, as your blood sugar can change enormously (e.g. 30 - 50 mg/dl) within 15 minutes of riding and a little more IoB or a basal rate that is still too high. The best way to keep an eye on it is if it is visible on the handlebars or if it is also displayed on your watch. It is even possible to install an additional app on some Garmin GPS bike computers that displays the blood glucose from XDrip or Nightscout as a data field on the bike computer. The additional app was developed by Andreas May from the T1D community. It is available free of charge in the official connect IQ Store. Certainly an interesting option for riders interested in sports. - -[Link to Andreas May Data Field App on connect IQ store](https://apps.garmin.com/de-DE/apps/5a3e2cda-12f0-4afd-88ed-000e67a68d84) - -Here is a picture of my Garmin Edge 530 bike computer with map, blood sugar and heart rate. - -![Garmin Edge 530 with BG data field](../images/cycling_IMG_1087.jpeg) - -After you have eaten the medium fast carbohydrates (24 - 36 g I take) and the blood sugar is above 100 mg/dl but also below 160 mg/dl, I carry out the profile change to 50% and set the activity temp target. - -:::{admonition} disable SMBs during high temp targets if necessary -:class: danger -Attention: If you prefer not to receive SMBs during the sport, please disable the option "Enable SMB with hight temp targets" in the settings of SMB or DynIFS Plugin. -::: - -The following picture shows the start and end of the sport. The end was specified as the duration when the profile was changed at the start. - -The temporary profile change has the following effects - -1. for a period of 60 minutes -2. a reduction to 50% of the profile and -3. the target is raised by clicking on the Activity Target option, which may have the side effect of disabling the SMBs - see above. - -![profile switch with temp target](../images/cycling_20240104-174056.png) - -The second image shows that the start at IoB was started towards 0. - -![IoB around 0](../images/cycling_20240104-174111.png) - -If the blood sugar drops faster than 15 mg/dl in 5 minutes or if it is at 120 mg/dl and tends to fall, I drink 1-2 sips of dissolved glucose. Then I wait for the next value and proceed as described above. - -You can hardly see it here, but at the beginning I took 2 sips from the bottle several times when my blood sugar started to fall. When it stabilized, I didn't need any more glucose. - -Here is the picture that illustrates this. The chart is saved on the Garmin as a result of the activity. - -![BG chart Garmin](../images/cycling_20240104-174431.png) - -If you should suddenly break out upwards, i.e. above 180 mg/dl, you should consider whether you should make a correction bolus. Caution: Remember the factor and apply it to the correction, otherwise the correction will be too strong. - -If your blood sugar drops below 80 mg/dl, take a break and drink two sips until your blood sugar is back above 100 mg/dl. - -At the end of the ride, the profile change should be finished as the time is up. - -Since we only rode easy for 60 minutes, there shouldn't be a big muscle bulking effect continuing to pull carbohydrates from your blood sugar. However, if it felt strenuous to you, keep an eye on it. This is especially true if you then go straight to bed. It may be better to change your profile to e.g. 80% for sleep. You may come out of sleep slightly too high, but it's better than having a hypo at night. Over time, you will surely find out what happens to you. - -The following pictures show the low intensity of the sport. - -The elevation profile -![](../images/cycling_20240104-174314.png) - -Speed with average and maximum speed - -![](../images/cycling_20240104-174326.png) - -Note the pause at the level crossing, which is also reflected in the heart rate. - -The heart rate. -![](../images/cycling_20240104-174337.png) - -The training effect. -![](../images/cycling_20240104-174358.png) - -The time in the different heart rate training zones. -![](../images/cycling_20240104-174423.png) - -After succesfully mastering this simple example you could go for further targets by stretching - -1. the distance and time -2. the load during the ride -3. the elevation during the right which should make a big impact on the more necessary carbs or further reduction of IoB and percentage of profile switch. - -Based on my experiences I would not expect to come back 100% with time in range over the whole and every ride. - -### Tipps - -I already gave some tipps for during the ride above. - -Here are some further tipps what can go wrong and how you can act to prevent it or react to compensate it. - -#### sky rocket high after ride - -During the ride everything was fine but after siting down and relax the blood sugar go sky rocket high. - -**Possible reason:** This happens when you have drunk too much dissolved glucose. - -**Reaction:** Drink 500 ml water, go to the shower and then control again. Latest after 30 minutes think about giving a correction bolus but be careful when it is short for bed time. Therefore it can be very good to make the first try runs on weekend mornings. - -**Action:** Next time be a bit more cautious in drinking from the dissolved glucose. - -#### hypo during ride - -During the ride you are going into hypo and can't recover your blood sugar during cycling. - -**Possible reason:** Your body cannot absorb enough carbohydrates quickly enough during exercise. - -**Reaction:** Take a rest and corrrect your blood sugar with drinking dissolved glucose. Stay calm: arrival comes before speed. - -**Action:** Did you started with IoB near 0? Have you eaten a small amount of middle fast carbs? Can you increase this or are the not fast enough for your body? Is it possible to prevent going into hypo by reducing the factor for the profile switch? Have you disbaled SMBs during ride as explained above? - -#### sky rocket high during ride - -During the ride your blood sugar goes sky rocket high. - -**Possible reason:** You have got taken too much carbs for your IoB at that time. Beneath for sure the typical technical problems with your -insulin pump like leakage or blockage of the catheder! - -**Reaction:** If it is too high for you take a rest and correct with a bolus. Keep in mind that you must ride home and therefore make it carefully. Drink 500 ml pure water without carbs. Stay calm: arrival comes before speed. - -**Action:** Have you eaten too much? Especially have you drunk too much from the dissolved glucose during the ride? Is your percentage of reduction the profile during profile switch too low and you can increase this? diff --git a/docs/CROWDIN/tr/buildingAAPS.md b/docs/CROWDIN/tr/buildingAAPS.md deleted file mode 100644 index 98164a09e49b..000000000000 --- a/docs/CROWDIN/tr/buildingAAPS.md +++ /dev/null @@ -1,28 +0,0 @@ -# Dummy - -## This is a dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - - -## This is another dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - - -## This is another another dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - diff --git a/docs/CROWDIN/tr/completingObjetives.md b/docs/CROWDIN/tr/completingObjetives.md deleted file mode 100644 index 98164a09e49b..000000000000 --- a/docs/CROWDIN/tr/completingObjetives.md +++ /dev/null @@ -1,28 +0,0 @@ -# Dummy - -## This is a dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - - -## This is another dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - - -## This is another another dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - diff --git a/docs/CROWDIN/tr/dummy.md b/docs/CROWDIN/tr/dummy.md deleted file mode 100644 index 98164a09e49b..000000000000 --- a/docs/CROWDIN/tr/dummy.md +++ /dev/null @@ -1,28 +0,0 @@ -# Dummy - -## This is a dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - - -## This is another dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - - -## This is another another dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - diff --git a/docs/CROWDIN/tr/intro.md b/docs/CROWDIN/tr/intro.md deleted file mode 100644 index d14b62d4176e..000000000000 --- a/docs/CROWDIN/tr/intro.md +++ /dev/null @@ -1,291 +0,0 @@ -![20-06-23v2 AAPS simple overview-cropped](https://github.com/openaps/AndroidAPSdocs/assets/94044064/e505b73b-09a0-42a4-a1ab-b830a0741234) - -# Introduction to APS and AAPS - -## What is an “Artificial Pancreas System”? - -A human pancreas does a lot of things besides regulating blood sugar. However, the term **“Artificial Pancreas System” (APS)** usually refers to a system which works to automatically keep blood sugar levels within healthy limits. - -The most basic way to do this is by detecting **glucose levels**, using these values to do **calculations**, and then delivering the (predicted) right amount of **insulin** to the body. It repeats the calculation, every few minutes, 24/7. It uses **alarms** and **alerts** to inform the user if intervention or attention is needed. This system is typically made up of a **glucose sensor**, an **insulin pump** and an **app** on a phone. - -You can read more about the different artificial pancreas systems currently in use and in development in this 2022 review article: - -![Frontiers](./images/FRONTIERS_Logo_Grey_RGB.png) [Future Directions in Closed-Loop Technology](https://www.frontiersin.org/articles/10.3389/fendo.2022.919942/full#:~:text=Fully%20closed%2Dloop%20systems%2C%20unlike,user%20input%20for%20mealtime%20boluses). - -In the near future, some so-called "dual-hormone" systems will also have the ability to infuse glucagon alongside insulin, with the aim of preventing severe hypos and allowing even tighter blood glucose control. - -An artificial pancreas can be thought of as an [“autopilot for your diabetes”]. (https://www.artificialpancreasbook.com/) What does that mean? In an aircraft, an autopilot does not do the complete job of the human pilot, the pilot cannot sleep through the entire flight. The autopilot aids the work of the pilot. It relieves them of the burden of permanently monitoring the aircraft, allowing the pilot to concentrate on wider monitoring from time to time. The autopilot receives signals from various sensors, a computer evaluates them together with the pilot’s specifications and then makes the necessary adjustments, alerting the pilot to any concerns. The pilot no longer has to worry about constantly making decisions. - -## What does hybrid closed loop mean? - -The best solution for type 1 diabetes would be a “functional cure” (probably an implant of pancreatic cells which are protected from the immune system). While we are waiting for that, a “full closed loop” artificial pancreas is probably the next best thing. This is a tech system that doesn’t need any user input (like bolusing insulin for meals, or announcing exercise), with good regulation of blood glucose levels. At the moment, there are no widely available systems which are “full” closed loop, they all need some user input. The currently available systems are called “hybrid” closed loop, because they use a combination of automated technology and user input. - -## How and why did looping start? - -The development of commercial technology for people with type 1 diabetes (T1D) is very slow. In 2013 the T1D community founded the #WeAreNotWaiting movement. They developed systems themselves using existing approved technology (insulin pumps and sensors) to improve blood glucose control, safety, and quality of life. These are known as DIY (do-it-yourself) systems, because they are not formally approved by health bodies (FDA, NHS etc). There are four main DIY systems available: OpenAPS, **AAPS**, Loop and iAPS. - -A great way to understand the fundamentals of DIY looping is to read Dana Lewis’s book “Automated Insulin Delivery”. You can access it \[here\] (https://www.artificialpancreasbook.com/) for free (or buy a hardcopy of the book). If you want to understand more about OpenAPS, which** AAPS** has developed from, the \[OpenAPS website\] (https://openaps.org/what-is-openaps/) is also a great resource. - -Several commercial hybrid closed loop systems have been launched, the most recent of which are \[CamAPS FX\] (https://camdiab.com/) (UK and EU) and \[Omnipod 5\] (https://www.omnipod.com/en-gb/what-is-omnipod/omnipod-5) (USA and EU). These are very different to DIY systems, mainly because they both include a “learning algorithm” which adjusts how much insulin is delivered according to your insulin needs from previous days. Many people in the DIY community have already tried out these commercial systems and compared them with their DIY system. You can find out more about how the different systems compare by asking on the dedicated Facebook groups for these systems, on the \[AAPS Facebook group\] (https://www.facebook.com/groups/AndroidAPSUsers/) or on \[Discord\] (https://discord.com/invite/4fQUWHZ4Mw). - -## What is Android APS (AAPS)? - -![image](https://github.com/openaps/AndroidAPSdocs/assets/94044064/0f089d96-b7ee-452a-aa9d-aae10ab58971) - -**Figure 1**. Basic outline of the Android APS (Artificial Pancreas System), AAPS. - -Android APS (AAPS) is a hybrid closed loop system, or Artificial Pancreas System (APS). It makes its insulin dosing calculations using established \[OpenAPS\] (https://openaps.org/) algorithms (a set of rules) developed by the #WeAreNotWaiting type 1 diabetes community. - -Since OpenAPS is only compatible with certain older insulin pumps, AAPS (which can be used with a wider range of insulin pumps) was developed in 2016 by Milos Kozak, for a family member with type 1 diabetes. Since those early days, **AAPS** has been continually developed and refined by a team of volunteer computer developers and other enthusiasts who have a connection to the type 1 diabetes world. Today, **AAPS** is used by approximately 10,000 people. It is a highly customisable and versatile system, and because it is open-source, it is also readily compatible with many other open-source diabetes softwares and platforms. The fundamental components of the current **AAPS** system are outlined in Figure 1 above. - -## What are the basic components of AAPS? - -The “brain” of AAPS is an **app** which you build yourself. There are detailed step-by-step instructions for this. You then install the **AAPS app** on a compatible **Android smartphone** (1). A number of users prefer their loop on a separate phone to their main phone. So, you don’t necessarily have to be using an Android phone for everything else in your life, just for running your AAPS loop. - -The **Android smartphone** will also need to have another app installed on it as well as **AAPS**, either a modified Dexcom app called build-your-own dexcom app (**BYODA**) or Xdrip+. This receives glucose data from a sensor (2) by bluetooth, and then sends the data internally on the phone to the **AAPS app**. - -The **AAPS app** uses a decision making process (**algorithm**) from OpenAPS. Beginners start out using the basic **oref0** algorithm, but it is possible to switch to using the newer **oref1** algorithm as you progress with AAPS. Which algorithm you use (oref0 or oref1), depends on which suits your specific situation best. In both cases, the algorithm takes into account multiple factors, and performs rapid calculations every time a new reading comes in from the sensor. The algorithm then sends instructions to the insulin pump (3) on how much insulin to deliver by bluetooth. All the information can be sent by mobile data or wifi to the internet. This data can also be shared with followers if desired, and/or collected for analysis. - -## What are the advantages of the AAPS system? - -The OpenAPS algorithm used by **AAPS** controls blood sugar levels in the absence of user input, according to the users’ defined parameters (important ones being basal rates, insulin sensitivity factors, insulin-to-carb ratios, duration of insulin activity etc.), reacting every 5 minutes to the new sensor data. Some of the reported advantages of using AAPS are extensive fine-tunable options, automations and increased transparency of the system for the patient/caregiver. This can result in better control over your (or your dependent’s) diabetes, which in turn may give improved quality of life and increased peace of mind. - -Practical advantages include: - -- **Hardware flexibility**: **AAPS** works with a wide range of insulin pumps and sensors. So for example, if you develop an allergy to Dexcom sensor patch glue, you could switch to using a Libre sensor instead. That offers flexibility as life changes. You don't have to rebuild, just tick a different box in the AAPS app to change your hardware. - -- **Highly customisable with wide parameters**: here are some examples of the possibilities with AAPS: a) The ability to set a lower glucose target 30 min before eating; you can set the target as low as 72 mg/dL (4.0 mmol/L). b) If you are insulin-resistant resulting in high blood sugars, **AAPS** allows you to set an **automation** rule to activate when BG rises above 8 mmol/L (144 mg/dL), switching to a 120% profile (resulting in an 20% increase in basal and strengthening of other factors too, compared to your normal **profile** setting). The automation will last according to the scheduled time you set. Such an automation could be set to only be active on certain days of the week, at certain times of day, and even at certain locations. c) If your child is on a trampoline with no advance notice, **AAPS** allows insulin suspension for a set time period, directly via the phone. d) After reconnecting a tubed pump which has been disconnected for swimming, AAPS will calculate the basal insulin you have missed while disconnected and deliver it carefully, according to your current BG. Any insulin not required can be overridden by just “cancelling” the missed basal. f) **AAPS** has the ability to set different profiles for different situations and easily switch between them. Features which make the algorithm quicker to bring down elevated BG (like supermicro boluses (“SMB”), unannounced meals, (“**UAM**”) can be set to only work during the daytime, if you are worried about night-time hypos. - - -These are all examples, the full range of features gives huge flexibility for daily life including sport, illness, hormone cycles etc. Ultimately, it is for the user to decide how to use this flexibility, and there is no one-size-fits-all automation for this. - -- **Remote monitoring**: there are multiple possible monitoring channels (Sugarmate, Dexcom Follow, Xdrip+, Android Auto etc.) which are useful for parents/carers and adults in certain scenarios (sleeping/driving) who need customisable alerts. In some apps (Xdrip+) you can also turn alarms off totally, which is great if you have a new sensor “soaking” or settling down that you don’t want to loop with yet. - -- **Remote control**: a significant advantage of **AAPS **over commercial systems is that it is possible for followers, using authenticated text (SMS) commands or via an app (Nightscout or NSClient) to send a wide range of commands back to the ****AAPS** **system. This is used extensively by parents of kids with type 1 diabetes who use AAPS. It is very useful in the playground, for example, if you want to pre-bolus for a snack from your own phone, and your child is busy playing. It is possible to monitor the system (e.g. Fitbit), send basic commands (e.g. Samsung Galaxy watch 4), or even run the entire AAPS system from a high-spec smartwatch (5) (e.g. LEMFO LEM14). In this last scenario, you don’t need to use a phone to run AAPS. As battery life on watches improves, this last option is likely to become increasingly attractive. - -- **No commercial constraints due to open application interfaces**: beyond the use of an open source approach, which allows the source code of **AAPS** to be viewed at any time, the general principle of providing open programming interfaces gives other developers the opportunity to contribute new ideas that allow users to live more easily with their diabetes. This is complementary to commercial systems which adopt the innovations from DIY, where interfaces are only made possible in return for licensing, thus preventing innovations in particular that are not-for-profit. Good examples for such integrations are NightScout, Nightscout Reporter, Xdrip+ M5 stack etc. - -- **Detailed app interface**: It is easy to keep track of things like: insulin levels, cannula age, sensor age, pump battery age, and many actions can be done through the **AAPS** app (priming the pump, disconnecting the pump etc.), instead of on the pump itself. - -- **Accessibility and affordability**: **AAPS** gives people who currently can’t afford to self-fund, or don’t have funding/insurance, access to a world-class hybrid closed looping system which is conceptually years ahead, in terms of development, of the commercial systems being offered by clinics. You currently need to have a Nightscout account to set up **AAPS**. Although the Nightscout account it not necessarily required after setup, many people continue to use Nightscout for collecting their data, and for remote control. So, although **AAPS **itself is free, setting up Nightscout through one of the various platforms may incur a fee (E0 - E12), depending on what level of support you want (see comparison table). **AAPS** works with a wide range of affordable (starting from approx E150) Android phones. In comparison, Loop currently costs around $80 a year for the Apple development licence and CamAPS FX costs around E80/month (as at 2023). - -- ****Support**: No automated insulin delivery system is perfect. Commercial and open-source systems share many common glitches in both communications and temporary hardware failure. There is a community of AAPS users on both Facebook and Discord and Github who designed, developed and are currently using **AAPS** all over the world. There are Facebook support groups and help from clinic/commercial companies for the commercial APS systems - it is worth speaking to the users, or former users of these systems to get feedback on the common glitches, the quality of the education programme and the level of ongoing support provided. - -- **Predictability, transparency and safety**: with no learning algorithm, **AAPS** is logical and in some respect, more predictable, which may make it easier to know when a setting is wrong, and to adjust it accordingly. You can see exactly what the system is doing, why it is doing it, and set its operational limits, which puts the control (and responsibility) in your hands. This can provide the user with confidence, and a sounder sleep. - -- **Access to advanced features through dev modes including full closed loop**: **AAPS **documentation focuses on the mainstream **“master”** branch of **AAPS**, however, research and development is going on all the time. More experienced users may wish to explore the experimental features in the **development** branch such as integration of Dexcom G7, and automatically adjusting insulin delivery according to short-term sensitivity changes (DYNISF), not having to bolus for meals, and generally trying to make life with type 1 diabetes as convenient as possible. - -- **Ability to contribute yourself to further improvements**: type 1 diabetes can be highly frustrating and isolating. Having control over your own diabetes tech, with the possibility to “pay it forward” as soon as you are making progress by helping others on their journey can be really rewarding. You can educate yourself, discover the roadblocks and look for and even contribute to new developments and the documentation. There will be others with the same quest to bounce ideas off and work with. This is the essence of #WeAreNotWaiting. - - -## How does AAPS compare to MDI and open looping? - -Multiple daily injections (MDI, a) usually involve giving an injection of a long-lasting insulin (e.g. Tresiba) once a day, with injections of faster-acting insulin (e.g. Novorapid, Fiasp) at mealtimes, or for corrections. Open pumping (b) involves using a pump to deliver basal at pre-programmed rates of rapid-acting insulin, and then boluses through the pump at mealtimes or for corrections. The basics of a looping system is that the App uses the glucose data to instruct the pump to stop insulin delivery when it predicts you are heading for a low, and to give you extra insulin if your glucose levels are rising and predicted to go too high (c). Although this is oversimplified, (mostly because hybrid closed looping has a lot of additional useful features) the key features of each system are shown in **Figure 2**. - -![image](https://github.com/openaps/AndroidAPSdocs/assets/94044064/4e7d8608-684d-4c69-9c61-88c9539f5d6f) - -**Figure 2**. Overview of (a) MDI, (b) open-loop pumping and (c) hybrid closed loop pumping - -## How does AAPS compare to other looping systems? - -At present there are four major open source closed loop systems available: OpenAPS, **AAPS**, \[Loop\] (https://loopkit.github.io/loopdocs/#what-is-loop) and iAPS, (formerly FreeAPS X). The features of the different systems are shown in the table below: - -| Devicestyp | Name | [Open APS](https://openaps.readthedocs.io/en/latest/) | [AAPS](https://wiki.aaps.app) | [Döngü](https://loopkit.github.io/loopdocs/) | [iAPS](https://iaps.readthedocs.io/en/latest/) | -| ---------- | ------------------------------------------------------------------------------------------------------ | ----------------------------------------------------- | ------------------------------------------- | -------------------------------------------- | ---------------------------------------------- | -| PUMP | Older Medtronic | ![available](./images/available.png) | ![available](./images/available.png) | ![available](./images/available.png) | ![available](./images/available.png) | -| PUMP | Older Omnipod (Eros) | ![unavailable](./images/unavailable.png) | ![available](./images/available.png) | ![available](./images/available.png) | ![available](./images/available.png) | -| PUMP | Newer Omnipod (Dash) | ![unavailable](./images/unavailable.png) | ![available](./images/available.png) | ![available](./images/available.png) | ![available](./images/available.png) | -| PUMP | DANA R, DANA RS, DANA I | ![unavailable](./images/unavailable.png) | ![available](./images/available.png) | ![unavailable](./images/unavailable.png) | ![unavailable](./images/unavailable.png) | -| PUMP | Roche Combo, Insight | ![unavailable](./images/unavailable.png) | ![available](./images/available.png) | ![unavailable](./images/unavailable.png) | ![unavailable](./images/unavailable.png) | -| CGM | Dexcom G4, G5, G6 | ![available](./images/available.png) | ![available](./images/available.png) | ![available](./images/available.png) | ![available](./images/available.png) | -| CGM | Libre 1 (requires Miao Miao) | ![available](./images/available.png) | ![available](./images/available.png) | ![available](./images/available.png) | ![available](./images/available.png) | -| CGM | Libre 2 | ![available](./images/available.png) | ![available](./images/available.png) | ![available](./images/available.png) | ![available](./images/available.png) | -| CGM | Libre 3 | | ![unavailable](./images/unavailable.png) | --- | ![unavailable](./images/unavailable.png) | -| CGM | Medtronic Enlite | | --- | ![unavailable](./images/unavailable.png) | --- | -| CGM | [Dexcom G7](https://androidaps.readthedocs.io/en/latest/Hardware/DexcomG7.html) | | ![available](./images/available.png) (beta) | ![available](./images/available.png) | ![available](./images/available.png) | -| CGM | [Eversense](https://androidaps.readthedocs.io/en/latest/Hardware/Eversense.html) | | ![available](./images/available.png) | | ![available](./images/available.png) | -| CGM | [MM640g/MM630g](https://androidaps.readthedocs.io/en/latest/Hardware/MM640g.html) | | ![available](./images/available.png) | | ![available](./images/available.png) | -| CGM | [PocTech](https://androidaps.readthedocs.io/en/latest/Hardware/PocTech.html) | | ![available](./images/available.png) | | ![available](./images/available.png) | -| CGM | [KŞ kaynağı Nightscout](https://androidaps.readthedocs.io/en/latest/Hardware/CgmNightscoutUpload.html) | | ![available](./images/available.png) | | ![available](./images/available.png) | -| Telefon | Android | ![available](./images/available.png) | ![available](./images/available.png) | ![unavailable](./images/unavailable.png) | ![unavailable](./images/unavailable.png) | -| Telefon | iPhone | ![available](./images/available.png) | ![unavailable](./images/unavailable.png) | ![available](./images/available.png) | ![available](./images/available.png) | - -[OpenAPS](https://openaps.readthedocs.io/) was the first Open Source Closed Loop System. Raspberry Pi veya Intel Edison gibi küçük bir bilgisayar kullanır. Both AndroidAPS (AAPS) and iAPS use the OpenAPS algorithms, whereas Loop uses a separate algorithm. You can read a comparison of iAPS and **AAPS** here. - -An international peer-reviewed consensus statement containing practical guidance on open source looping was written by and for health-care professionals, and published in a leading medical journal in 2022. It is well worth a read (including for your diabetes clinic) and summarises the main technical differences between the different open-source hybrid closed loop systems: - - Lancet Diabetes Endocrinol, 2022; 10: 58–74 - -[https://www.ncbi.nlm.nih.gov/pmc/articles/PMC8720075/](https://www.ncbi.nlm.nih.gov/pmc/articles/PMC8720075/) - -It is hard to get a “feel” for any system without using it, or talking to others who are using it, so do reach out to others on Facebook/Discord and ask. Most people find that AAPS is incredibly sophisticated in comparison to other hybrid closed loop systems (particularly the commercial systems), with a huge number of potentially customisable settings and features, discussed above. Some people can find this a little overwhelming in the beginning, but there is no rush to investigate all the possibilities at once, you can progress as slowly or as fast as you would like, and there is help available at every step of the way. - -## Does AAPS use artificial intelligence or any learning algorithm? - -Hayır. **AAPS** does not have any complicated machine learning algorithms, multiple-parameter insulin response models, or differential equations. As such, the system is open and transparent in how it works, and has the ability to be understood not just by experts, but also by clinicians and patients. It also means that if you have a sharply varying schedule (maybe switching from a stressful week at work to a relaxing holiday) and are likely to need a significantly different amount of insulin, you can immediately switch **AAPS** to run a weaker/stronger profile. A ‘learning system’ will do this adjustment for you automatically, but is likely to take longer to adjust the insulin delivery. - -## Which system is right for me or my dependent? - -Practically, your choice of system is often restricted by which pump you already have, or can obtain from your medical provider, and your choice of phone (Apple or Android). If you don’t yet have a pump you have the biggest choice of systems. Technology is continually evolving, pumps are being discontinued and new pumps and sensors are being released. Most open-source systems work with the main sensors (Libre and Dexcom) or are quickly adapted to work with new sensors a year or so after they are released (with a bit of time delay for safety and stability testing). - -Most **AAPS **users report more time in range, HbA1c reductions, as well as quality of life improvements from having a system that can auto-adjust basal rates overnight during sleep, and this is true for most hybrid closed loop APS. Some people have a preference for a very simple system which is not very customisable (which means you may prefer a commercial system), and others find this lack of control very frustrating (you may prefer an open-source system). If you (or your dependent) are newly diagnosed, a common route is to get the hang of MDI plus sensor first, then progress to a pump which has the potential for looping, then to **AAPS**, but some people (especially small kids) may go straight to a pump. - -It is important to note that the **AAPS** user needs to be proactive to troubleshoot and fix problems themselves, with help from the community. This is a very different mindset to that when using a commercial system. With **AAPS** a user has more control, but also the responsibility, and needs to be comfortable with that. - -## Is it safe to use open-source systems like AAPS? - -A more accurate question is probably “is it safe compared to my current type 1 diabetes insulin delivery system?” since no method of insulin delivery is without risk. There are many checks and balances in place with **AAPS**. A recent paper looked at the use of**** AAPS ****in a computer simulated set-up, [https://www.liebertpub.com/doi/epub/10.1089/dia.2019.0375](https://www.liebertpub.com/doi/epub/10.1089/dia.2019.0375) which was an effective way to unobjectively trial how safe and effective the system is. More generally, it is estimated that over 10,000 individuals worldwide are using open-source automated-insulin delivery systems, and uptake continues to increase globally. - -Any device that uses radio communications could be hacked, and this is true for a non-looping insulin pump as well. Currently, we are not aware of anyone attempting to harm individuals by hacking their diabetes-related medical equipment. However, there are multiple ways to protect against such risks: - -1. In the pump settings, limit both the max bolus allowed and max temporary basal settings to amounts that you believe are safest. These are hard limits that we do not believe any malicious hacker could circumvent. - -2. Set your CGM alarms enabled for both highs and lows. - -3. Monitor your insulin delivery online. Nightscout users can set additional alarms to alert for a wide variety of conditions, including conditions that are much more likely to occur than a malicious attack. In addition to highs and lows, Nightscout can display diagnostic data useful for verifying that the pump is operating as desired, including current IOB, pump temporary basal history, pump bolus history. It can also be configured to proactively alert users to undesirable conditions, such as predicted highs and lows, low insulin reservoir, and low pump battery. - - -If a malicious attack was made on your insulin pump, these strategies would significantly mitigate the risk. Every potential **AAPS** user needs to weigh the risks associated with using **AAPS**, versus the risks of using a different system. - -## How can I approach discussing AAPS with my clinical team? - -Depending on the country - link to doctors section of docs - - Lancet Diabetes Endocrinol, 2022; 10: 58–74 - -[https://www.ncbi.nlm.nih.gov/pmc/articles/PMC8720075/](https://www.ncbi.nlm.nih.gov/pmc/articles/PMC8720075/) - -## Q: Why can’t I just download AAPS and use it straight away? - -The **AAPS** app is not provided in Google Play - you have to build it from source code by yourself for legal reasons. **AAPS** is unlicensed, meaning that it does not have approval by any regulatory body authority in any country. **AAPS**is deemed to be carrying out a medical experiment on yourself, and is carried out at the user’s own risk. - -Setting up the system requires patience, determination and the gradual development of technical knowledge. All the information and support can be found in these documents, elsewhere online, or from others who have already done it. It is estimated that over 2000 people have successfully built and are currently using **AAPS** worldwide. - -The developers of **AAPS**t ake safety incredibly seriously, and want others to have a good experience of using **AAPS**. That is why it is essential that every user (or carer, if the user is a child): - -- builds the AAPS system themself and works through the **objectives** so that they have reasonably good personalised settings and understand the basics of how AAPS ****works by the time they “close the loop”; - -- backs up their system by exporting and saving important files (like keystore and settings .json file) somewhere safe, so you can setup again quickly if needed; - -- updates to newer master versions as and when they become available; and - -- maintains and monitors the system to ensure it is working properly. - - -## Q: What is the connectivity of the AAPS system? - -**Figure 3 (below)** shows one example of the **AAPS** system for a user who do not require any followers interacting with the system: - -![potential AAPS connectivity setup with no followers](./images/intro03.png) - -**Figure 4 (below)** shows the full potential of the **AAPS** system for a user who has followers and requires a monitor and send adjust the system remotely (like a child with T1D): - -![potential AAPS connectivity setup with followers](./images/intro04.png) - -## Q: How does AAPS get continually developed and improved? - -Most **AAPS** users use the fully tested **master** version of AAPS, which has been tested for bugs and problems, before being released to the community. Behind the scenes, the developers try out new improvements, and test these out in “developer” (**dev**) versions of **AAPS** with a user community who are happy to do bug updates at short notice. If the improvements work well, they are then released as a new “master” version of **AAPS**. Any new master release is announced on the Facebook group, so that the mainstream **AAPS** users can read about and update to the new master version. - -Some experienced and confident **AAPS ** users conduct experiments with emerging technologies and with dev versions of the **AAPS** app, which can be interesting for the less adventurous users to read about, without having to do it themselves! People tend to share these experiments on the Facebook group too. - -You can read more about some of these experiments and discussion on emerging tech here: - -[https://www.diabettech.com/](https://www.diabettech.com/) - -[https://bionicwookie.com/](https://bionicwookie.com/) - -## Q: Who can benefit? - -| User Type | -| ------------------------------------------- | -| ✔️ type 1 diabetic | -| ✔️ caregiver or parent of a type 1 diabetic | -| ✔️ blind users type 1 diabetic | -| ✔️ *clincians and healthcare professionals | - -The above table assumes that the user has access to both continuous gluocse monitor and insulin pump. - -*All data from **AAPS** can be made available to healthcare professionals via data sharing platforms, including NightScout that provides logging and real time monitoring of CGM data, insulin delivery, carbohydrate entries, predictions and settings. Nightscout records include daily and weekly reports which can aid healthcare professionals' discussions with type 1 patients with more accurate data on glycemic control and any behavioural considerations. - -## Q: What benefits can I get? - -With investment of your time, **AAPS** can potentially lead to: - -- alleviating the stress and burden of managing type 1 diabetes; - -- reducing the multitude of mundane decisions that arise from type 1 diabetes; - -- the provision of personalised and dynamic insulin dosing based on real-time data which can cut down the need for hypo treatments and reduce hyperglycemia episodes; - -- an increased knowledge of insulin management and confidence to better fine tune your settings; - -- the ability to create automatic settings (**automations**) that are tailored to fit in with your lifestyle; - -- improved sleep quality and overall reduction in the frequency of nighttime interventions; - -- remote monitoring and administration of insulin delivery for caregivers of type 1 diabetics; and - -- streamlining of all your portable diabetic equipment (continuous glucose monitor and insulin portable devices) by replacing them with an android phone controlled by **AAPS**. - - -Ultimately,**AAPS** can empower individuals to better manage their diabetes resulting in stable blood sugars and improved long term health outcomes. - ---- - -## AAPS First Steps - -Welcome. This is an introduction to aid beginners getting started with **AAPS** (or commonly referred to as "looping"). - -## Safety - -“_With great powers comes great responsibilities…_” - -**AAPS** is designed with an extensive set of safety features with limits imposed and gradually removed with completion of the **objectives **(predominately made up of multiple choice questions). An **AAPS** feature will be unlocked as the Objectives are successfully completed. This process will gradually allow the user to migrate from Open Loop to Closed Loop. - -This has been done to achieve the best possible experience with **AAPS** in order to prevent common mistakes that new users tend to make when starting to loop. The safety parameters have been built upon typical errors and general trends **AAPS** developers have observed with new users. Mistakes can happen because the beginner is inexperienced and too eager to get started with AAPS or has overlooked the required materials. Do not worry, we have all been there! - -## Key Principles - -The key principles and concepts of looping must be understood by the user before using **AAPS**. This is achieved by investing your personal time into reading the **AAPS** documentation, and completing the Objectives which is aimed to provide you with a solid platform for safe and effective use of **AAPS**. The volume of **AAPS** documentation may seem overwhelming at first but be patient and trust the process - with the proper approach, you'll get there! The overall process will depend upon the beginner’s progress and completion of objectives can typically take between 6 to 9 weeks . - -## Plan for hiccups - -At the preliminary stages of **AAPS**, you should expect to experience some hiccups whilst trying to fine tune your settings. **AAPS**’ glitches cannot be flushed out until the system is used in everyday life. Please plan accordingly and allow a sensible amount of time to troubleshoot and resolve such issues. - -## Flexibility/Adaptability - -Success with **AAPS** requires a proactive approach, a willingness to reflect on the BG data and flexibility to make the necessary adjustments to **AAPS** in order to improve your outcomes. Just as it is nearly impossible to learn to play a sport by reading about the rules alone, the same can be said of **AAPS**. - -## Technology compatibility - -There are limitations with **AAPS** as it is accessible for only certain types of insulin pumps or CGMs, and some technology may not be available for use in various countries. In order to avoid any disappointment or frustrations, please read please read Component Set Up (Section INSERT). - -## App Build Time - -The time to build the **AAPS**(under Section INSERT) depends on your level of expertise and technical ability. Typically for inexperienced users, it can take up to half a day or a full day (with help from the community) in order to build the **AAPS**. The process will significantly speed up as you become more experienced at building the **AAPS**. To aid the build process there are sections dedicated for: -- list of questions and answers for frequent errors that are likely to occur under FAQs (Section K); -- “How to install AAPS? (Section INSERT) which includes Troubleshooting subsection. - -## Keystore & configurations settings a export file - -A “keystore” is a password encrypted file unique to your own copy of **AAPS**. Your android phone uses it to ensure that nobody else can upgrade your own copy without the keystore. In short, as part of the **AAPS** build, you should: - -- save the your keystore file (.jks file used to sign your app) in a safe place; -- keep a note of your password for your keystore file. - -By doing the above, this will ensure that you can use that exact same keystore file each time an updated version of **AAPS** is created. On average, there will be 2-3 AAPS updates required each year. - -In addition, **AAPS** provides the ability to export all your configuration settings. This ensures that you can safely recover your system while changing phones, upgrading/reinstalling the application with minimum disruption. - -## Troubleshootng - -Please feel free to reach out to the AAPS community if there is anything you feel unsure about - there is no such thing as a silly question! All users with various levels of experience are encouraged to ask questions as necessary. Response times to questions are usually quick, typically only a few hours due to the volume of **AAPS** users. - -a) check the documentation; b) ask AAPS facebook group (https://www.facebook.com/groups/AndroidAPSUsers); and c) ask our discord channel. - -## Section overview - -AAPS documentation is made up of the following Sections: - -[INSERT ONCE SECTIONS /SUB SECTIONS AGREED] ---- diff --git a/docs/CROWDIN/tr/maintaining.md b/docs/CROWDIN/tr/maintaining.md deleted file mode 100644 index 98164a09e49b..000000000000 --- a/docs/CROWDIN/tr/maintaining.md +++ /dev/null @@ -1,28 +0,0 @@ -# Dummy - -## This is a dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - - -## This is another dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - - -## This is another another dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - diff --git a/docs/CROWDIN/tr/optimizing.md b/docs/CROWDIN/tr/optimizing.md deleted file mode 100644 index 98164a09e49b..000000000000 --- a/docs/CROWDIN/tr/optimizing.md +++ /dev/null @@ -1,28 +0,0 @@ -# Dummy - -## This is a dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - - -## This is another dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - - -## This is another another dummy heading - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. - diff --git a/docs/CROWDIN/tr/prepairing.md b/docs/CROWDIN/tr/prepairing.md deleted file mode 100644 index 70aa9a521b7e..000000000000 --- a/docs/CROWDIN/tr/prepairing.md +++ /dev/null @@ -1,145 +0,0 @@ -# Prepairing - -## Guide to the Android APS doc - -### First Steps -Welcome. This is an introduction to aid beginners to the concept of Do-It-Yourself-APS (Android-Artificial-Pancreas-Systems “AAPS”) is commonly referred to as ‘looping’.. - -#### Safetys -“With great powers come great responsibilities…” - -AAPS is designed with an extensive set of safety features with limits imposed and gradually removed with completion of the [Objectives](https://androidaps.readthedocs.io/en/latest/Usage/Objectives.html) (predominately made up of multiple choice questions). An AAPS feature will be unlocked as the Objectives are successfully completed. This process will gradually allow the user to migrate from Open Loop to Closed Loop. - -This has been done to achieve the best possible experience with AAPS by preventing common mistakes new users tend to make when starting to loop. The safety parameters have been built upon typical errors and general trends AAPS developers have observed with new users. Mistakes can happen because the beginner is inexperienced and too eager to get started with AAPS or has overlooked the required materials. Do not worry, we have all been there! - -#### Key Principles - -The key principles and concepts of looping must be understood by the user before using AAPS. This is achieved by investing your personal time into reading the AAPS documentation, and completing the [Objectives](https://androidaps.readthedocs.io/en/latest/Usage/Objectives.html) which is aimed to provide you with a solid platform for safe and effective use of AAPS. The volume of AAPS documentation may seem overwhelming at first but be patient and trust the process - with the proper approach, you'll get there! The overall process will depend upon the beginner’s progress and completion of objectives which typically take between 6 to 9 weeks . - -#### Plan for hiccups - -At the preliminary stages of AAPS, you should expect to experience some hiccups whilst trying to fine tune your settings. AAPS’ glitches cannot be flushed out until the system is used in everyday life. Please plan accordingly and allow a sensible amount of time to troubleshoot and resolve such issues. - -#### Flexibility/Adaptability - -Success with AAPS requires a proactive approach, a willingness to reflect on the BG data and flexibility to make the necessary adjustments to AAPS in order to improve your outcomes. Just as it is nearly impossible to learn to play a sport by reading about the rules alone, the same can be said of AAPS. - -#### Technology compatibility -There are limitations with AAPS as it is accessible for only certain types of insulin pumps or CGMs, and some technology may not be available for use in various countries. In order to avoid any disappointment or frustrations, please read [Component Set Up (Section E).](https://androidaps.readthedocs.io/en/latest/Configuration/BG-Source.html) - -#### App Build time -The time to build the AAPS (under Section D) depends on your level of expertise and technical ability. Typically for inexperienced users, it can take up to half a day or a full day (with help from the community) in order to build the AAPS. The process will significantly speed up as you become more experienced at building the AAPS.  - -To aid the build process there are sections dedicated for: - -- list of questions and answers for frequent errors that are likely to occur under [FAQs (Section](https://androidaps.readthedocs.io/en/latest/Getting-Started/FAQ.html) K); - -- “[How to install AAPS](https://androidaps.readthedocs.io/en/latest/Installing-AndroidAPS/Building-APK.html)? (Section D) which includes [Troubleshooting](https://androidaps.readthedocs.io/en/latest/Usage/troubleshooting.html) subsection. - - -#### Keystore & configuration settings export  file - -A “keystore” is a password encrypted file unique to your own copy of AAPS. Your android phone uses it to ensure that nobody else can upgrade your own copy without the keystore.In short, as part of the AAPS build, you should: - -1. save the your keystore file (.jks file used to sign your app) in a safe place; - -2. keep a note of your password for your keystore file. - - -By doing the above, this will ensure that you can use that exact same keystore file each time an updated version of AAPS is created. On average, there will be 2-3 updates to the AAPS required each year. In addition, AAPS provides the ability to [export all your configuration settings](https://androidaps.readthedocs.io/en/latest/Usage/ExportImportSettings.html). This ensures that you can safely recover your system while changing phones, upgrading/reinstalling the application with minimum disruption.  - -#### Sorun giderme - -Please feel free to reach out to the AAPS community if there is anything you feel unsure about - there is no such thing as a silly question!  All users with various levels of experience are encouraged to ask questions as necessary. Response times to questions are usually quick, typically only a few hours due to the volume of AAPS users.  - -##### [check the documentation](https://androidaps.readthedocs.io/en/latest/index.html) - -##### [ask our facebook group](https://www.facebook.com/groups/AndroidAPSUsers/) - -##### [ask our discord channel](https://discord.com/channels/629952586895851530/629954570394533889) - -#### Section overview - -AAPS documentation is made up of the following Sections: - -##### [Getting started](https://androidaps.readthedocs.io/en/latest/Getting-Started/Safety-first.html) - -This is a must read to understand the general concept of what an artificial pancreas system is designed to do. - -##### [What do I need?](https://androidaps.readthedocs.io/en/latest/Module/module.html) - -This explains AAPS’ compatibility with CGMs (Continuous Glucose Monitors) and insulin pumps. It also provides a guide on the correct assembly of an AAPS system to ensure that it functions correctly in everyday life. - -##### How to install AAPS - -This section is the manual for building the AAPS. Strict adherence to the step-by-step instructions are required in order to successfully build the AAPS. Lütfen acele etmeyin. - -##### [Component Setup](https://androidaps.readthedocs.io/en/latest/Configuration/BG-Source.html) - -This explains how to properly integrate each of the various different separate component parts into AAPS, as well as how to set them up to work as seamlessly as possible together. All components are listed under the separate sections: CGM/FGM, xDrip Settings, Pumps, Phones, Nightscout setup, and Smartwatches. The sensor (BG) values and control of the insulin pump are particularly important information to understand. - -##### Configuration - -This explains how to set and configure your ‘Profile’, ‘Insulin’, ‘BG Source’, ‘Pump’, ‘Sensitivity Detection’, ‘APS’, ‘Loop’, ‘Treatments’. - -##### AAPS Usage - -This section provides a breakdown of the features provided by AAPS. - -##### [General Hints](https://androidaps.readthedocs.io/en/latest/Usage/Timezone-traveling.html) - -Useful tricks on how to tackle looping issues such as time zones, and daylight saving (i.e. Spring Forward/ - Fall Back). - -##### [AAPS](https://androidaps.readthedocs.io/en/latest/Getting-Started/Screenshots.html) for Children - -This is designed for parents or caregivers who want to build an AAPS for their child. It also explains the extra features necessary in order to support and safely control your child’s AAPS remotely.

The concepts in this section should be fully understood in order to competently use this feature. - -##### Sorun giderme - -This section contains links to help solve issues when building or using AAPS. - -##### SSS - -This section addresses specific questions which tend to come up when building or using AAPS. - -##### [Sözlük](https://androidaps.readthedocs.io/en/latest/Getting-Started/Glossary.html) - -This contains a list of the acronyms (or short-term names) or defined terms developed specifically for AAP (for instance, the terms ‘ISF’ or ‘TT’ have special meanings in AAPS). - -##### [Where to go for help](https://androidaps.readthedocs.io/en/latest/Where-To-Go-For-Help/Background-reading.html)? - -This section is aimed to provide new users with links on resources in order to get help including accessing community support made up of both new and experienced users who can clarify questions, and resolve the usual pitfalls that come with AAPS. - -##### For Clinicians - -This is a section for the clinicians who have expressed interest in open source artificial pancreas technology such as AAPS, or for patients who want to share such information with their clinicians. | - -## what are we going to build? - -### An Android Phone Application - -At the core, AAPS is an android application running from a phone. You are going to build it from scratch by installing tools to download the sourcecode and build the actual application. - -### A reporting server NightScout (or Tidepool) - -In order to fully use AAPS properly you will want to setup a nightscout server. It is used to collect data from AAPS over time and possibly communicate to the application. It is required for parents who want to oversee their children AAPS sessions. It is also key to share data between clinicians and patients to perform analysis over time. - -## How long will it take? - -## Who might AAPS not be suitable for? - -## Where can I get help? - -## Requirements - -### medical - -### technical - -### personal - -### CGMs - -### Insulin Pump - -### Reporting (NS, Tidepool) \ No newline at end of file diff --git a/docs/CROWDIN/zh/Getting-Started/ClosedLoop.md b/docs/CROWDIN/zh/Getting-Started/ClosedLoop.md deleted file mode 100644 index cbf82cf21392..000000000000 --- a/docs/CROWDIN/zh/Getting-Started/ClosedLoop.md +++ /dev/null @@ -1,55 +0,0 @@ -# What is a Closed Loop System? - -![AAPS is like an autopilot](../images/autopilot.png) - -An artificial pancreas closed loop system combines different components in order to make diabetes management easier for you. In her great book [Automated Insulin Delivery](https://www.artificialpancreasbook.com/) Dana M. Lewis, one of the founders of the open source closed loop movement, calls it an ["autopilot for your diabetes"](https://www.artificialpancreasbook.com/3.-getting-started-with-your-aps). But what does that mean? - -**Autopilot in an aircraft** - -The autopilot does not do the complete job and does not give the possibility to the pilot to sleep throughout the entire flight. It facilitates the work of the pilots. It relieves them of the burden of permanently monitoring the aircraft and the flight attitude. This allows the pilot to concentrate on monitoring the airspace and controlling the autopilot's functions. - -The autopilot receives signals from various sensors, a computer evaluates them together with the pilot's specifications and then makes the necessary adjustments. The pilot no longer has to worry about the constant adjustments. - -**Closed Loop System** - -The same applies to an artificial pancreas closed loop system. It does not do the whole job, you still have to take care of your diabetes. A closed loop system combines the sensor data from a CGM/FGM with your diabetes management specifications such as basal rate, insulin sensitivity factor and carb ratio. From this it calculates treatment suggestions and implements these permanent small adjustments in order to keep your diabetes within the target range and to relieve you. This leaves more time for your life "next to" diabetes. - -Just as you don't want to get on a plane where only the autopilot flies without human supervision, a closed loop system helps you with your diabetes management, but always needs your support! **Even with a closed loop you can't just forget your diabetes!** - -Just as the autopilot depends on the sensor values as well as the pilot's specifications, a closed loop system needs appropriate input such as basal rates, ISF and carb ratio to support you successfully. - -## Open Source Artificial Pancreas Closed Loop Systems - -At present there are three major open source closed loop systems available: - -### AndroidAPS (AAPS) - -AAPS is described in detail in [this documentation](./WhatisAndroidAPS.html). It uses an Android Smartphone for calculation and control of your insulin pump. It is in strong collaboration with OpenAPS (i.e. they share algorithms). - -Compatible [pumps](../Hardware/pumps.md) are: - -- [DanaR](../Configuration/DanaR-Insulin-Pump.md) / [DanaRS & Dana-i](../Configuration/DanaRS-Insulin-Pump.html) -- [Accu-Chek Combo](../Configuration/Accu-Chek-Combo-Pump.md) -- [Accu-Chek Insight](../Configuration/Accu-Chek-Insight-Pump.md) -- [Diaconn G8](../Configuration/DiaconnG8.md) -- [Omnipod DASH](../Configuration/OmnipodDASH.md) -- [Omnipod Eros](../Configuration/OmnipodEros.md) -- some old [Medtronic pumps](../Configuration/MedtronicPump.md) - -### OpenAPS - -[OpenAPS](https://openaps.readthedocs.io) was the first Open Source Closed Loop System. It uses a small computer such as Raspberry Pi or Intel Edison. - -Compatible pumps are: - -- some old Medtronic pumps - -### Loop for iOS - -[Loop for iOS](https://loopkit.github.io/loopdocs/) is the Open Source Closed Loop System to be used with Apple iPhones. - -Compatible pumps are: - -- Omnipod DASH -- Omnipod Eros -- some old Medtronic pumps diff --git a/docs/CROWDIN/zh/Getting-Started/Safety-first.md b/docs/CROWDIN/zh/Getting-Started/Safety-first.md deleted file mode 100644 index 30d380261ead..000000000000 --- a/docs/CROWDIN/zh/Getting-Started/Safety-first.md +++ /dev/null @@ -1,41 +0,0 @@ -# Safety first - -**When you decide to build your own artificial pancreas, it's always important to think about security and safety, and to understand the impact of all your actions** - -## General - -- AAPS is a just a tool to help you manage diabetes, it is not a fully automated system you can install and forget! -- Do not assume that AAPS will never make mistakes. This device is taking control of your insulin delivery: Watch it all the time, understand how it works, and learn how to interpret its actions. -- Remember that, once paired, the phone can instruct the pump to do anything. Only use this phone for AAPS and, if being used by a child, essential communications. Do not install unnecessary apps or games (!!!) which could introduce malware such as trojans, viruses, or bots that could interfere with your system. -- Install all security updates provided by your phone manufacturer and Google. -- You might also need to change your diabetes habits as you change your therapy by using a closed loop system. I.e. some people report, they need less hypo treatments as AAPS has already reduced insulin. - -## SMS Communicator - -- AAPS allows you to control a child's phone remotely via text message. If you enable this SMS Communicator, always remember that the phone set up to give remote commands could be stolen. So always protect it at least by a PIN code. -- AAPS will also inform you by text message if your remote commands, such as a bolus or a profile change, have been carried out. It is advisable to set this up so that confirmation texts are sent to at least two different phone numbers in case one of the receiving phones is stolen. - -(Safety-first-aaps-can-also-be-used-by-blind-people)= -## AAPS can also be used by blind people - -On Android devices TalkBack is part of the operating system. It is a program for screen orientation via voice output. With TalkBack you can operate your smartphone as well as AAPS blind. - -We users create the AAPS app ourselves with Android Studio. Many use Microsoft Windows for this purpose, where there is the Screenreader analogous to TalkBack. Since Android Studio is a Java application, the "Java Access Bridge" component must be enabled in the Control Panel. Otherwise, the screen reader of the PC will not speak in Android Studio. - -To do this, please proceed as follows: - -- Press WINDOWSTASTE and enter "Control Panel" in the search field, open with Enter. It opens: "All Control Panel Items". -- Press the letter C to get to "Center for Ease of Use", open with Enter. -- Then open "Use computer without a screen" with Enter. -- There, at the bottom, you will find the checkbox "Enable Java Access Bridge", select it. -- Done, just close the window! The screen reader should work now. - -```{note} -**IMPORTANT SAFETY NOTICE** - -The foundation of AAPS safety features discussed in this documentation is built on the safety features of the hardware used to build your system. It is critically important that you only use a tested, fully functioning FDA or CE approved insulin pump and CGM for closing an automated insulin dosing loop. Hardware or software modifications to these components can cause unexpected insulin dosing, causing significant risk to the user. If you find or get offered broken, modified or self-made insulin pumps or CGM receivers, *do not use* these for creating an AAPS system. - -Additionally, it is equally important to only use original supplies such as inserters, cannulas and insulin containers approved by the manufacturer for use with your pump or CGM. Using untested or modified supplies can cause CGM inaccuracy and insulin dosing errors. Insulin is highly dangerous when misdosed - please do not play with your life by hacking with your supplies. - -Last not least, you must not take SGLT-2 inhibitors (gliflozins) as they incalculably lower blood sugar levels. The combination with a system that lowers basal rates in order to increase BG is especially dangerous as due to the gliflozin this rise in BG might not happen and a dangerous state of lack of insulin can happen. -``` diff --git a/docs/CROWDIN/zh/Getting-Started/WhatisAndroidAPS.md b/docs/CROWDIN/zh/Getting-Started/WhatisAndroidAPS.md deleted file mode 100644 index b10d73731578..000000000000 --- a/docs/CROWDIN/zh/Getting-Started/WhatisAndroidAPS.md +++ /dev/null @@ -1,39 +0,0 @@ -# What is a closed loop system with AAPS? - -AAPS is an app that acts as an artificial pancreas system (APS) on an Android smartphone. What is an artificial pancreas system? It is a software program that aims to do what a living pancreas does: keep blood sugar levels within healthy limits automatically. - -An APS can't do the job as well as a biological pancreas does, but it can make type 1 diabetes easier to manage using devices that are commercially available and software that is simple and safe. Those devices include a continuous glucose monitor (CGM) to tell AAPS about your blood sugar levels and an insulin pump which AAPS controls to deliver appropriate doses of insulin. The app communicates with those devices via bluetooth. It makes its dosing calculations using an algorithm, or set of rules, developed for another artificial pancreas system, called OpenAPS, which has thousands of users and has accumulated millions of hours of use. - -A note of caution: AAPS is not regulated by any medical authority in any country. Using AAPS is essentially carrying out a medical experiment on yourself. Setting up the system requires determination and technical knowledge. If you don't have the technical know-how at the beginning, you will by the end. All the information you need can be found in these documents, elsewhere online, or from others who have already done it -- you can ask them in Facebook groups or other forums. Many people have successfully built AAPS and are now using it entirely safely, but it is essential that every user: - -- Builds the system themselves so that they thoroughly understand how it works -- Adjusts its individual dosage algorithm with his or her diabetes team to work nearly perfect -- Maintains and monitors the system to ensure it is working properly - -```{note} -**Disclaimer and Warning** - -- All information, thought, and code described here is intended for informational and educational purposes only. Nightscout currently makes no attempt at HIPAA privacy compliance. Use Nightscout and AAPS at your own risk, and do not use the information or code to make medical decisions. -- Use of code from github.com is without warranty or formal support of any kind. Please review this repository's LICENSE for details. -- All product and company names, trademarks, servicemarks, registered trademarks, and registered servicemarks are the property of their respective holders. Their use is for information purposes and does not imply any affiliation with or endorsement by them. - -Please note - this project has no association with and is not endorsed by: [SOOIL](http://www.sooil.com/eng/), [Dexcom](https://www.dexcom.com/), [Accu-Chek, Roche Diabetes Care](https://www.accu-chek.com/), [Insulet](https://www.insulet.com/) or [Medtronic](https://www.medtronic.com/). -``` - -If you're ready for the challenge, please read on. - -## Primary goals behind AAPS - -- An app with safety built in. To read about the safety features of the algorithms, known as oref0 and oref1, click here () -- An all-in-one app for managing type 1 diabetes with an artificial pancreas and Nightscout -- An app to which users can easily add or remove modules as needed -- An app with different versions for specific locations and languages. -- An app which can be used in open- and closed-loop mode -- An app that is totally transparent: users can input parameters, see results, and make the final decision -- An app which is independent of particular pump drivers and contains a "virtual pump" so users can safely experiment before using it on themselves -- An app closely integrated with Nightscout -- An app in which the user is in control of safety constraints - -## How to start - -Of course, all of this content here is very important, but can be in the beginning quite confusing. A good orientation is given by the [Module Overview](../Module/module.md) and the [Objectives](../Usage/Objectives.html). diff --git a/docs/CROWDIN/zh/Hardware/DexcomG4.md b/docs/CROWDIN/zh/Hardware/DexcomG4.md deleted file mode 100644 index 3ac2b2b96f4b..000000000000 --- a/docs/CROWDIN/zh/Hardware/DexcomG4.md +++ /dev/null @@ -1,6 +0,0 @@ -# Dexcom G4 - -## If using G4 with OTG cable ('traditional' Nightscout) -- If not already set up then download Nightscout Uploader app from the Play Store and follow instructions on [Nightscout](https://nightscout.github.io/). -- In AAPS Preferences enter your Nightscout website and API secret. -- Select NSClient in ConfigBuilder (setting in AAPS). diff --git a/docs/CROWDIN/zh/Hardware/Smartwatch.md b/docs/CROWDIN/zh/Hardware/Smartwatch.md deleted file mode 100644 index 12281d6d256a..000000000000 --- a/docs/CROWDIN/zh/Hardware/Smartwatch.md +++ /dev/null @@ -1,10 +0,0 @@ -# Smartwatches - -Smartwatches are optional, but very useful for some users. More details are here: - -- [List of tested phones and smartwatches](../Getting-Started/Phones.md) -- [Watchfaces Wear OS](../Configuration/Watchfaces.md) -- [Troubleshooting Sony Smartwatch SW 3](../Usage/SonySW3.md) - -## Instructions for Building the AAPS Wear APK for Wear OS -https://androidaps.readthedocs.io/en/latest/remote-control.html#building-the-aaps-wear-apk diff --git a/docs/CROWDIN/zh/Installing-AndroidAPS/Building-APK.md b/docs/CROWDIN/zh/Installing-AndroidAPS/Building-APK.md deleted file mode 100644 index 8d964f4b41fc..000000000000 --- a/docs/CROWDIN/zh/Installing-AndroidAPS/Building-APK.md +++ /dev/null @@ -1,369 +0,0 @@ -# Building the APK - -## Build yourself instead of download - -**AAPS is not available as download due to regulation for medical devices. It is legal to build the app for your own use, but you must not give a copy to others! See [FAQ page](../Getting-Started/FAQ.md) for details.** - -## Important notes - -* Please use **[Android Studio Giraffe" (2022.3.1)](https://developer.android.com/studio/)** or newer to build the apk. -* [Windows 32-bit systems](troubleshooting_androidstudio-unable-to-start-daemon-process) are not supported by Android Studio - -(Building-APK-recommended-specification-of-computer-for-building-apk-file)= - -## Recommended specification of computer for building apk file - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
OS (Only 64 bit)Windows 8 or higherMac OS 10.14 or higherAny Linux supports Gnome, KDE, or Unity DE;  GNU C Library 2.31 or later

CPU (Only 64 bit)

x86_64 CPU architecture; 2nd generation Intel Core or newer, or AMD CPU with support for a
Windows Hypervisor		ARM-based chips, or 2nd generation Intel Core or newer with support for
Hypervisor.Framework		x86_64 CPU architecture; 2nd generation Intel Core or newer, or AMD processor with support for AMD Virtualization (AMD-V) and SSSE3

RAM

8GB or more

Disk

At least 30GB free space. SSD is recommended.

Resolution

1280 x 800 Minimum

Internet

Broadband

- -Please keep in mind that both **64 bit CPU and 64 bit OS are mandatory condition.** If your system DOES NOT meet this condition, you have to change affected hardware or software or the whole system. **It is strongly recommended to use SSD (Solid State Disk) instead of HDD (Hard Disk Drive) because it will take less time when you are building the APS installation apk file.** Recommended is just recommended and it is not a mandatory. However, you may still use a HDD when you are building apk file but note that the building process can take a long time to complete, although once started, you can leave it running unattended. - -* * * - -### This article is divided into two parts. - -* In the overview part there is an explanation on what steps are necessary to build the APK file. -* In the step by step walkthrough part you will find the screenshots of a concrete installation. Because the versions of Android Studio - the software development environment which we will use to build the APK - will change very quickly this will be not identical to your installation but it should give you a good starting point. Android Studio also runs on Windows, Mac OS X and Linux and there might be small differences in some aspects between each platform. If you find that something important is wrong or missing, please inform the facebook group "AAPS users" or in the Discord chat [Android APS](https://discord.gg/4fQUWHZ4Mw) so that we can have a look at this. - -## Overview - -In general, the steps necessary to build the APK file: - -1. [Install git](../Installing-AndroidAPS/git-install.md) -2. [Install Android Studio](Building-APK-install-android-studio) -3. [Set git path in Android Studio preferences](Building-APK-set-git-path-in-preferences) -4. [Download AAPS code](Building-APK-download-AAPS-code) -5. [Download Android SDK](Building-APK-download-android-sdk) -6. [Build the app](Building-APK-generate-signed-apk) (generate signed apk) -7. [Transfer apk file to your phone](Building-APK-transfer-apk-to-smartphone) -8. [Identify receiver if using xDrip+](xdrip-identify-receiver) - -## Step by step walkthrough - -Detailed description of the steps necessary to build the APK file. - -## Install git (if you don't have it) - -Follow the manual on the [git installation page](../Installing-AndroidAPS/git-install.md). - -(Building-APK-install-android-studio)= - -## Install Android Studio - -The following screenshots have been taken from Android Studio Version Arctic Fox | 2020.3.1. Screens can change in future versions of Android Studio. But you should be able to find your way through. [Help from the community](../Where-To-Go-For-Help/Connect-with-other-users.md) is provided. - -One of the most important things when installing Android Studio: **Be patient!** During installation and setup Android Studio is downloading a lot of stuff which will take its time. - -Download [Android Studio from here](https://developer.android.com/studio/install.html) and install it on your computer. - -On first start you will find the setup wizard: - -Select "Do not import settings" as you have not used it before. - -![Do not import settings](../images/studioSetup/01_ImportSettings.png) - -Decide whether you want to share data with Google or not. - -![Share data with Google](../images/studioSetup/02_DataSharing.png) - -On the following screen click "Next". - -![Welcome screen](../images/studioSetup/03_Welcome.png) - -Select "Standard" installation and click "Next". - -![Standard installation](../images/studioSetup/04_InstallType.png) - -Select the theme for the user interface you like. (In this manual we used "Light".) Then click "Next". - -> ***Note:*** This is just the color scheme. You can select whatever you like (i.e. "Darcula" for dark mode). This selection has no influence on building the APK but the following screenshots might look different. - -![UI color scheme](../images/studioSetup/05_UITheme.png) - -Click "Next" on the "Verify Settings" dialog. - -![Verify settings](../images/studioSetup/06_Overview.png) - -Click on all three license agreement parts and select "Agree". When you have agreed to all, the "Finish" button will be enabled and you can "Finish". - - ![Agree license agreements](../images/studioSetup/07_LicenseAgreement.png) - - -Wait while Android Studio downloads additional components and be patient. Once everything is downloaded button "Finish" turns blue. Click the button now. - -![Downloading components](../images/studioSetup/08_Downloading.png) - -(Building-APK-download-AAPS-code)= - -## Download AAPS code - -* On the Android Studio welcome screen select "Projects" (1) on the left and then "Get from VCS" (2). - - ![Android Studio wizard](../images/studioSetup/20_ProjectVCS.png) - - * If you already opened Android Studio and do not see the welcome screen anymore select File (1) > New (2) > Project from Version Control... (3) - - ![Check out project from version control within Android Studio](../images/AndroidStudio_FileNew.PNG) - - * We will now tell Android Studio were to get the code from: - - * Make sure you have selected "Repository URL" on the left (1). - - * Check if "Git" is selected as version control (2). - * Copy and paste the URL ```https://github.com/nightscout/AndroidAPS``` to the main AAPS repository into the URL textbox (3). - * Choose the directory where you want to save the cloned code (4). - - ![Clone Git](../images/studioSetup/21_CloneURL.png) - -* Click button "Clone" (5). - - ![Clone repository](../images/studioSetup/22_Cloning.png) - -* Do not click "Background" while repository is cloned! - -* After the repository is cloned successfully, Android Studio will open the cloned project. - -* You will be asked whether you want to trust the project. Click on "Trust project"! - - ![Trust project](../images/studioSetup/23_TrustProject.png) - -* In the status bar at the bottom you will see the information that Android Studio is running background tasks. - - ![Background tasks](../images/studioSetup/24_GradleSyncRunning.png) - -* Windows only: Grant access if your firewall is asking for permission. - - ![Firewall permission java](../images/AndroidStudio361_18.png) - -* Once the background tasks are finished you will probably see an error saying that errors occurred (1) or (2) or (3). - - ![SDK licence](../images/studioSetup/25_SyncFailed.png) - - Don't worry, this will be solved soon! - -(Building-APK-set-git-path-in-preferences)= - -## Set git path in preferences - -Make sure [git is installed](../Installing-AndroidAPS/git-install.md) on your computer and you have restarted your computer since installing. - -On the Android Studio welcome screen click "Customize" (1) on the left and then select the link "All settings..." (2): - -![Android Studio settings from welcome screen](../images/studioSetup/10_WizardSettings.png) - -### Windows - -* As windows user, make sure you have restarted your computer after [installing Git](../Installing-AndroidAPS/git-install.md). - -* In the menu, go to File (1) > Settings (2) (or Android Studio > Preferences on Mac). - - ![Open settings](../images/studioSetup/30_Settings.png) - -* Double-click "Version Control" (1) to open the sub-menu. - -* Click Git (2). -* Make sure update method "Merge" (3) is selected. -* Check if Android Studio can locate path to git.exe automatically by clicking the button "Test" (4). - - ![Android Studio settings](../images/studioSetup/11_GitPath.png) - -* If automatic setting is successful git version will be displayed next to the path. - - ![Git version displayed](../images/studioSetup/12_GitVersion.png) - -* Eventually git.exe cannot be found automatically or the Test will result in an error (1): - - ![Git not found](../images/studioSetup/13_GitVersionError.png) - - In this case click on the folder icon (2). - -* Use [search function](https://www.tenforums.com/tutorials/94452-search-file-explorer-windows-10-a.html) in windows explorer to find "git.exe" if you are unsure where git has been installed. You are looking for a file named "git.exe", located in **\bin** folder. - -* Select path to git.exe and make sure you selected the one in ** \bin\ ** folder (3) and click "OK" (4). - - ![Select git manually](../images/studioSetup/14_GitManualSelection.png) - -* Check your selected git path again with the "Test" button as described above. - -* When the git version is displayed next to the path (see screenshot above), close settings window by clicking "OK" button (5). - -### Mac - -* Any git version should work. For example . -* Use homebrew to install git: ```$ brew install git```. -* For details on installing git see the [official git documentation](https://git-scm.com/book/en/v2/Getting-Started-Installing-Git). -* If you install git via homebrew there is no need to change any preferences. Just in case: They can be found here: Android Studio - Preferences. - -(Building-APK-download-android-sdk)= - -## Download Android SDK - -* In the menu, go to File (1) > Settings (2) (or Android Studio > Preferences on Mac). - - ![Open settings](../images/studioSetup/30_Settings.png) - -* Double-click on Languages & Frameworks to open its submenu (1). - -* Select Android SDK (2). -* Tick the box left of "Android 9.0 (Pie)" (3) (API Level 28). - - ![SDK settings](../images/studioSetup/31_AndroidSDK.png) - -* Confirm changes by clicking OK. - - ![Confirm SDK changes](../images/studioSetup/32_ConfirmSDK.png) - -* Wait until the SDK download and installation is finished. - - ![Wait during SDK installation](../images/studioSetup/34_DownloadSDK.png) - -* When SDK installation is completed the "Finish" button will turn blue. Click this button. - - ![Finish SDK installation](../images/studioSetup/35_DownloadSDKfinished.png) - -* Android Studio might recommend to update the gradle system. **Never update gradle!** This will lead to difficulties! - -* If you see an information on the lower right side of your Android Studio window that Android Gradle Plugin is ready to update click on the text "upgrade" (1). - - ![No gradle update](../images/studioSetup/36_GradleUpdateRequest.png) - -* In the dialog box the select "Don't remind me again for this project" (2). - - ![No gradle update](../images/studioSetup/37_GradleUpdateDeny.png) - -* Restart Android Studio before you continue. - -(Building-APK-generate-signed-apk)= - -## Generate signed APK - -Signing means that you indicate your app to be your own creation but in a digital way as a kind of digital fingerprint within the app itself. That is necessary because Android has a rule that it only accepts signed code to run for security reasons. For more information on this topic, follow [this link](https://developer.android.com/studio/publish/app-signing.html#generate-key). - -* After Android Studio is started, wait until all background tasks are finished. - - ![Wait for background tasks](../images/studioSetup/40_BackgroundTasks.png) - - * ***Warning:*** If errors occur, do not continue with the following steps. \ Consult the [troubleshooting section](../Installing-AndroidAPS/troubleshooting_androidstudio) for known problems! - - ![Gradle Sync Error](../images/studioSetup/41_GradleSyncError.png) - -* Click "Build" (1) in the menu bar and select "Generate Signed Bundle / APK..." (2). - - ![Build apk](../images/studioSetup/42_MenuBuild.png) - -* Select "APK" (1) instead of "Android App Bundle" and click "Next" (2). - - ![APK instead of bundle](../images/studioSetup/43_Apk.png) - -* Make sure that module is set to "AndroidAPS.app" (1). - -* Click "Create new..." (2) to start creating your key store. - - ***Note:*** A key store in this case is nothing more than a file in which the information for signing is stored. It is encrypted and the information is secured with passwords. - - ![Create key store](../images/studioSetup/44_KeystoreNew.png) - -* Click the folder symbol to select a path on your computer for your key store. - - ![Create key store](../images/studioSetup/45_KeystoreDialog.png) - -* Select the path where your key store shall be saved (1). - - ![Create key store](../images/studioSetup/46_KeystorePath.png) - - ***Warning: Do not save in same folder as project. You must use a different directory!*** A good location would be your home folder. - -* Type a file name for your key store (2) and confirm with "OK" (3). - -* Enter (2) and confirm (3) the password for your key store. ![Select key store path](../images/studioSetup/47_KeystoreDialog.png) - - ***Note:*** Passwords for key store and key do not have to be very sophisticated. Make sure to remember those or make a note in a safe place. In case you will not remember your passwords in the future, see [troubleshooting for lost key store](troubleshooting_androidstudio-lost-keystore). - -* Enter an alias (4) for your key. Choose whatever you like. - -* Enter (5) and confirm (6) the password for your key - -* Validity (7) is 25 years by default. You do not have to change the default value. - -* First and last name must be entered (8). All other information is optional. - -* Click "OK" (9) when you are done. - -* Make sure the box to remember passwords is checked (1). So you don't have to enter them again next time you build the apk (i.e. when updating to a new AAPS version). - -* Click "Next" (2). - - ![Remember passwords](../images/studioSetup/48_KeystoreSave.png) - -* Select build variant "fullRelease" (1) and press "Finish". - - ![Select build variant](../images/studioSetup/49_BuildVariant.png) - -* Android Studio will show "Gradle Build running" at the bottom. This takes some time, depending on your computer and internet connection. **Be patient!** - - ![Gradle Running](../images/studioSetup/50_GradleRunning.png) - -* Android Studio will display the information "Generate Signed APK" after build is finished. - - ![Build finished](../images/studioSetup/51_BuildFinished.png) - -* In case build was not successful refer to the [troubleshooting section](../Installing-AndroidAPS/troubleshooting_androidstudio). - -* Click on the notification to expand it. - -* Click on the link "locate". - - ![Locate build](../images/studioSetup/52_BuildLocate.png) - - * If the notification is gone, you can always open the "Event log" and select the same link there. ![Build successfully - event log](../images/studioSetup/53_EventLog.png) - -* Your file manager/explorer will open. Navigate to the directory "full" (1) > "release" (2). - - ![File location apk](../images/studioSetup/54_APKlocation.png) - -* "app-full-release.apk" (3) is the file you are looking for! - -(Building-APK-transfer-apk-to-smartphone)= - -## Transfer APK to smartphone - -Easiest way to transfer app-full-release.apk to your phone is via [USB cable or Google Drive](https://support.google.com/android/answer/9064445?hl=en). Please note that transfer by mail might cause difficulties and is not the preferred way. - -On your phone you have to allow installation from unknown sources. Manuals how to do this can be found on the internet (i.e. [here](https://www.expressvpn.com/de/support/vpn-setup/enable-apk-installs-android/) or [here](https://www.androidcentral.com/unknown-sources)). - -## Troubleshooting - -See separate page [troubleshooting Android Studio](../Installing-AndroidAPS/troubleshooting_androidstudio). \ No newline at end of file diff --git a/docs/CROWDIN/zh/Sandbox/sandbox2.md b/docs/CROWDIN/zh/Sandbox/sandbox2.md deleted file mode 100644 index 24314e223cc8..000000000000 --- a/docs/CROWDIN/zh/Sandbox/sandbox2.md +++ /dev/null @@ -1,43 +0,0 @@ -# 內部沙盒文件 2，用於測試 - -```{admonition} no need to translate this -:class: note - -不需要翻譯這個。 -``` - -這是供文檔團隊測試的內部沙盒文件 - -1. Markdown 語法和 - -1. 後台處理 - 1. CROWDIN 翻譯和 - 2. Read The Docs 部署。 - -您可以從這裡直接跳轉到 sandbox1.md 文件中的第一個標籤 - [「跳轉」](sandbox1-this-is-a-test)。 - -您可以從這裡直接跳轉到此文件中的第二個標籤 - [「跳轉」](sandbox1-this-is-another-test)。 - -這裡可以跳轉到第一個沙盒文件 - [「跳轉」](./sandbox1.md)。 - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua。 At vero eos et accusam et justo duo dolores et ea rebum。 Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet。 Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua。 At vero eos et accusam et justo duo dolores et ea rebum。 Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet。 - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua。 At vero eos et accusam et justo duo dolores et ea rebum。 Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet。 Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua。 At vero eos et accusam et justo duo dolores et ea rebum。 Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet。 - -Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua。 At vero eos et accusam et justo duo dolores et ea rebum。 Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet。 Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua。 At vero eos et accusam et justo duo dolores et ea rebum。 Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet。 - -(sandbox2-this-is-a-test)= -## 這是一個測試 - -這是一個測試，以檢查標籤是否必須唯一。 - -### 這是來自文檔的備用資訊 - -從索引中刪除： - -當您第一次開始 AAPS 之旅時，會設置一些「限制」。 這些安全限制是多年來觀察到的，因為新用戶在學習設置、構建並成功運作 AAPS 閉環系統時，最有可能犯錯，因為他們太過興奮以致於可能忘記花時間仔細閱讀本文檔中的資訊。 - - -### 從概述中刪除的備用訊息，以放入「準備」部分 - -由於要求與您以前設置的任何東西都不同，我們建議您在第一次構建應用程式時，逐步遵循說明，這樣您就能更清楚地了解當所有指示都完全按照要求執行時，應用構建過程應該如何進行。 請記住，慢慢來。 以後當您為新版本構建應用程式時，這個過程會變得非常迅速。 這樣您更有可能在問題出現之前就注意到是否有步驟出錯。 很重要的是將您的密鑰庫文件 (.jks 文件，用於簽署應用程式) 儲存在安全的地方，這樣每次您需要建立 AAPS 的新更新版本時，您都可以使用相同的密鑰庫文件和密碼。這樣可以確保每個新版本的應用程式能「記住」您在之前版本中提供的所有資訊，從而確保更新過程能順利進行。 通常，您可以預計每年會有一個新版本和 2-3 個必須的更新。 這個數字基於經驗，未來可能會發生變化。 但我們想至少提供一個預期的指導方針。 當您對構建更新的 AAPS 應用版本更有經驗時，完成所有必要的步驟平均只需 15-30 分鐘。 然而，對新用戶來說，這些步驟可能並不直觀，因此一開始可能會有相當大的學習曲線！ 因此，如果您發現自己感到非常沮喪，請不要氣餒，有時候在社群的幫助下，可能需要半天或整天才能完成更新過程。 如果您發現自己非常沮喪，請稍作休息，經常在周圍散步後，您會發現自己能更好地重新解決問題。 diff --git a/docs/CROWDIN/zh/Usage/Objectives.md b/docs/CROWDIN/zh/Usage/Objectives.md deleted file mode 100644 index c27b9c02a04c..000000000000 --- a/docs/CROWDIN/zh/Usage/Objectives.md +++ /dev/null @@ -1,184 +0,0 @@ -# Objectives - -AAPS has a series of Objectives that need to be completed to walk you through the features and settings of safe looping. They ensure you have configured everything detailed in the sections above correctly, and that you understand what your system is doing and why so you can trust it. - -If you are **upgrading phones** then you can [export your settings](../Usage/ExportImportSettings.md) to keep your progress through the objectives. Not only will your progress through the objectives be saved, but also your safety settings such as max bolus etc. If you do not export and import your settings then you will need to start the objectives from the beginning again. It is a good idea to [backup your settings](../Usage/ExportImportSettings.html) frequently just in case. - -If you want to go back in objectives see [explanation below](Objectives-go-back-in-objectives). - -## Objective 1: Setting up visualization and monitoring, analysing basals and ratios - -- Select the right blood glucose source for your setup. See [BG Source](../Configuration/BG-Source.md) for more information. -- Select the right Pump in ConfigBuilder (select Virtual Pump if you are using a pump model with no AAPS driver for looping) to ensure your pump status can communicate with AAPS. -- If using DanaR pump then ensure you have followed [DanaR Insulin Pump](../Configuration/DanaR-Insulin-Pump.md) instructions to ensure the link between pump and AAPS. -- You need to establish a data repository/reporting platform to complete this objective. That can be accomplished with either Nightscout or Tidepool (or both). Follow instructions at the [Nightscout](../Installing-AndroidAPS/Nightscout.md) or [Tidepool](../Installing-AndroidAPS/Tidepool.md) page for instructions. -- Note that URL in NSClient must be **WITHOUT /api/v1/** at the end - see [NSClient settings in Preferences](Preferences-nsclient). - -*You may need to wait for the next blood glucose reading to arrive before AAPS will recognise it.* - -## Objective 2: Learn how to control AAPS - -- Perform several actions in AAPS as described in this objective. - -- Click on the orange text "Not completed yet" to access the to-dos. - -- Links will be provided to guide you in case you are not familiar with a specific action yet. - - ```{image} ../images/Objective2_V2_5.png - :alt: Screenshot objective 2 - ``` - -(Objectives-objective-3-prove-your-knowledge)= - -## Objective 3: Prove your knowledge - -Objective 3 is a multiple choice test based on questions designed to test your theoretical knowledge of **AAPS**. - -Some users find Objective 3 to be the most difficult objective to complete. Please do read the AAPS documents in conjunction with the questions. If you are genuinely stuck after researching the **AAPS** documents, please search or ask for help on the Facebook or Discord group. These groups can provide friendly hints or redirect you to the relevant part of the **AAPS** documents. - -To proceed with Objective 3, click on the orange text “Not completed yet” to access the relevant question. Please read each question and select your answer(s). - - - -Within each question, a hyperlink to the **AAPS** documents will guide you to the relevant section of the document which you should read in order to locate the correct answer. - - -[Obj3_Screenshot 2023-12-05 223422](https://github.com/openaps/AndroidAPSdocs/assets/137224335/77347516-e24e-459d-98ab-acbb49a3d4e8)![image](https://github.com/openaps/AndroidAPSdocs/assets/137224335/ca756b8e-efbc-4427-b281-ac953ce16718) - - - -For each question, there may be more than one answer that is correct! If an incorrect answer is selected, the question will be time locked for a certain amount of time (60 minutes) before you can go back and answer the question. - - -After updating to a new version of **AAPS**, new questions may be added to cover a prevalent issue picked up by **AAPS** or alternatively to test your knowledge of a new feature of **AAPS** as released. - - -When **AAPS** is installed for the first time, you will have to complete Objective 3 entirely in order to move onto Objective 4. Each objective is required to be completed in sequential order. New features will gradually be unlocked as progress is made through the objectives. - -__What happens if new questions are added later to Objective 3?__ From time to time, new features are added to **AAPS** which may require a new question to be added to Objective 3. As a result, any new question added to Objective 3 will be marked as “incomplete” because **AAPS** will require you to action this. As each Objective is independent, you will not lose the existing functionality of **AAPS** providing the other objectives remain completed. - - -## Objective 4: Starting on an open loop - -- Select Open Loop either from Preferences, or by pressing and holding the Loop button in top left of the home screen. -- Work through the [Preferences](../Configuration/Preferences.md) to set up for you. -- Manually enact at least 20 of the temporary basal rate suggestions over a period of 7 days; input them to your pump and confirm in AAPS that you have accepted them. Ensure this data shows in AAPS and Nightscout. -- Enable [temp targets](../Usage/temptarget.md) if necessary. Use hypo temp targets to prevent that the system will correct too strong because of a raising blood glucose after a hypo. - -### Reduce number of notifications - -- To reduce the Number of decisions to be made while in Open Loop set wide target range like 90 - 150 mg/dl or 5,0 - 8,5 mmol/l. - -- You might even want to wider upper limit (or disable Open Loop) at night. - -- In Preferences you can set a minimum percentage for suggestion of basal rate change. - - ```{image} ../images/OpenLoop_MinimalRequestChange2.png - :alt: Open Loop minimal request change - ``` - -- Also, you do not need to act every 5 minutes on all suggestions... - -## Objective 5: Understanding your open loop, including its temp basal recommendations - -- Start to understand the thinking behind the temp basal recommendations by looking at the [determine basal logic](https://openaps.readthedocs.io/en/latest/docs/While%20You%20Wait%20For%20Gear/Understand-determine-basal.html) and both the [forecast line in AAPS homescreen](Screenshots-prediction-lines)/Nightscout and the summary of outputs from the calculations in your OpenAPS tab. - -You will want to set your target higher than usual until you are confident in the calculations and settings. System allows - -- a low target to be a minimum of 4 mmol (72 mg/dl) or maximum of 10 mmol (180 mg/dl) -- a high target to be a minimum of 5 mmol (90 mg/dl) and maximum of 15 mmol (225 mg/dl) -- a temporary target as a single value can be anywhere in the range of 4 mmol to 15 mmol (72 mg/dl to 225 mg/dl) - -The target is the value that calculations are based on, and not the same as where you aim to keep your blood glucose values within. If your target is very wide (say, 3 or more mmol \[50 mg/dl or more\] wide), you will often find little AAPS action. This is because blood glucose is eventually predicted to be somewhere in that wide range and therefore not many fluctuating temporary basal rates are suggested. - -You may want to experiment with adjusting your targets to be a closer together range (say, 1 or less mmol \[20 mg/dl or less\] wide) and observe how the behavior of your system changes as a result. - -You can view a wider range (green lines) on the graph for the values you aim to keep your blood glucose within by entering different values in [Preferences](../Configuration/Preferences.md) > Range for Visualisation. - -```{image} ../images/sign_stop.png -:alt: Stop sign -``` - -### Stop here if you are open looping with a virtual pump - do not click Verify at the end of this objective. - -```{image} ../images/blank.png -:alt: blank -``` - -(Objectives-objective-6-starting-to-close-the-loop-with-low-glucose-suspend)= -## Objective 6: Starting to close the loop with Low Glucose Suspend - -```{image} ../images/sign_warning.png -:alt: Warning sign -``` - -### Closed loop will not correct high BG values in objective 6 as it is limited to low glucose suspend. High BG values have to be corrected manually by you! - -- Prerequisite: You need a good profile (basal, ISF, IC) already working in AAPS to start with Loop in Low Glucose Suspend mode. Otherwise you can run in a hypo which you have to manually correct. This will help you a lot to avoid having to treat a low glucose over a period of 5 days. **If you are still having frequent or severe low glucose episodes then consider refining your DIA, basal, ISF and carb ratios and do NOT start objective 6 at this time.** -- You don't have to change your settings now. During objective 6, the maxIOB setting is internally set to zero automatically. **This override will be reversed when moving to objective 7.** -- The system will override your maxIOB settings to zero, which means if blood glucose is dropping it can reduce basal for you. If blood glucose is rising then it will only increase basal if the basal IOB is negative from a previous Low Glucose Suspend. Otherwise basal rates will remain the same as your selected profile. **That means that you have to manually handle high values with insulin corrections.** -- If your basal IOB is negative (see screenshot below) a TBR > 100% can be issued also in objective 6. - -```{image} ../images/Objective6_negIOB.png -:alt: Example negative IOB -``` - -- Set your target range slightly higher than you usually aim for, just to be safe and have a bit more scurity buffer. -- Enable 'Low Glucose Suspend' mode either by by pressing and holding the Loop icon at the top right corner of the home screen and selecting the Loop - LGS mode icon. -- Watch how temporary basals are active by viewing the blue basal text on the homescreen or the blue basal render on the homescreen graph. -- You may temporarily experience spikes following treated hypos without the ability to increase basal on the rebound. - -(Objectives-objective-7-tuning-the-closed-loop-raising-max-iob-above-0-and-gradually-lowering-bg-targets)= -## Objective 7: Tuning the closed loop, raising maxIOB above 0 and gradually lowering BG targets - -- Select 'Closed Loop' either from [Preferences](../Configuration/Preferences.md) or by pressing and holding the Loop icon at the top right corner of the home screen, over a period of 1 day. - -- Raise your 'Maximum total IOB OpenAPS can’t go over' (in OpenAPS called 'max-iob') above 0. The default recommendation is "average mealbolus + 3x max daily basal" (for the SMB algorithm) or "3x max daily basal" (for the older AMA algorithm) but you should slowly work up to this until you know your settings work for you (max daily basal = the maximum hourly value in any time segment of the day). - - This recommendation should be seen as a starting point. If you set to the 3x and you are seeing moves that push you too hard and fast then lower that number. If you are very resistant, raise it very little at a time. - - ```{image} ../images/MaxDailyBasal2.png - :alt: max daily basal - ``` - -- Once confident on how much IOB suits your looping patterns, then reduce your targets to your desired level. - -(Objectives-objective-8-adjust-basals-and-ratios-if-needed-and-then-enable-autosens)= -## Objective 8: Adjust basals and ratios if needed, and then enable autosens - -- You can use [autotune](https://openaps.readthedocs.io/en/latest/docs/Customize-Iterate/autotune.html) as a one off to check your basals remain accurate or do a traditional basal test. -- Enable [autosens](../Usage/Open-APS-features.md) over a period of 7 days and watch the white line on the homescreen graph show how your sensitivity to insulin may be rising or falling as a result of exercise or hormones etc. and keep an eye in the OpenAPS report tab how AAPS is adjusting the basals and/or targets accordingly. - -*Don’t forget to record your looping in* [this form](https://bit.ly/nowlooping) *logging AAPS as your type of DIY loop software, if you have not already done so.* - -(Objectives-objective-9-enabling-additional-oref1-features-for-daytime-use-such-as-super-micro-bolus-smb)= -## Objective 9: Enabling additional oref1 features for daytime use, such as super micro bolus (SMB) - -- You must read the [SMB chapter in this wiki](Open-APS-features-super-micro-bolus-smb) and [chapter oref1 in openAPSdocs](https://openaps.readthedocs.io/en/latest/docs/Customize-Iterate/oref1.html) to understand how SMB works, especially what's the idea behind zero-temping. -- Then you ought to [rise maxIOB](Open-APS-features-maximum-total-iob-openaps-cant-go-over-openaps-max-iob) to get SMBs working fine. maxIOB now includes all IOB, not just added basal. That is, if given a bolus of 8 U for a meal and maxIOB is 7 U, no SMBs will be delivered until IOB drops below 7 U. A good start is maxIOB = average mealbolus + 3x max daily basal (max daily basal = the maximum hourly value in any time segment of the day - see [objective 7](Objectives-objective-7-tuning-the-closed-loop-raising-max-iob-above-0-and-gradually-lowering-bg-targets) for an illustration) -- min_5m_carbimpact default in absorption settings has changed from 3 to 8 going from AMA to SMB. If you are upgrading from AMA to SMB, you have to change it manually. - -(Objectives-objective-10-automation)= -## Objective 10: Automation - -- You have to start objective 10 to be able to use [Automation](../Usage/Automation.md). -- Make sure you have completed all objectives including exam [Objectives-objective-3-prove-your-knowledge](Objectives#objective-3-prove-your-knowledge). -- Completing previous objectives will not effect other objectives you have already finished. You will keep all finished objectives! - -(Objectives-objective-11-DynamicISF)= -## Objective 11: Additional Features such as DynamicISF - -- You have to start objective 11 to be able to use [DynamicISF](../Usage/Open-APS-features.md) - -(Objectives-go-back-in-objectives)= -## Go back in objectives - -If you want to go back in objectives for whatever reason you can do so by clicking at "clear finished". - -```{image} ../images/Objective_ClearFinished.png -:alt: Go back in objectives -``` - -## Objectives in Android APS before version 3.0 - -One objective was removed when Android APS 3.0 was released. Users of Android APS version 2.8.2.1 who are on older Android software (i.e. earlier than version 9) will be using an older set of objectives which can be found [here](../Usage/Objectives_old.md). diff --git a/docs/CROWDIN/zh/Usage/Smoothing-Blood-Glucose-Data-in-xDrip.md b/docs/CROWDIN/zh/Usage/Smoothing-Blood-Glucose-Data-in-xDrip.md deleted file mode 100644 index 716234b04a15..000000000000 --- a/docs/CROWDIN/zh/Usage/Smoothing-Blood-Glucose-Data-in-xDrip.md +++ /dev/null @@ -1,33 +0,0 @@ -(Smoothing-Blood-Glucose-Data-in-xDrip-smoothing-blood-glucose-data)= - -# Smoothing blood glucose data - -If BG data is jumpy/noisy, AAPS may dose insulin incorrectly resulting in high or low BG. For this reason it’s important to disable the loop until the problem is resolved. Depending on your CGM such issues may be due to the CGM’s configuration or sensor problems/site issues. You may need to replace your CGM sensor to resolve this. - -Some CGM systems have internal algorithms to detect the noise level in the readings and AAPS can use this information to avoid giving SMBs if the BG data is too unreliable. However, some CGMs do not transmit this data and for these BG sources 'Enable SMB always' and 'Enable SMB after carbs' are disabled for safety reasons. - -## Dexcom sensors - -### Build Your Own Dexcom App - -When using [BYODA](DexcomG6-if-using-g6-with-build-your-own-dexcom-app) your BG data is smooth and consistent. Furthermore you can take advantage of Dexcom back-smoothing. There are no restrictions in using SMBs, because the noise-level data is shared with AAPS. - -### xDrip+ with Dexcom G6 or Dexcom ONE - -Noise-level data and smooth BG readings are only shared with AAPS if you use xDrip+ [native mode](https://navid200.github.io/xDrip/docs/Native-Algorithm). Using native mode, there are no restrictions in using SMBs. - -### Dexcom G6 or Dexcom ONE with xDrip+ Companion Mode - -The noise-level data is not shared with AAPS using this method. Therefore 'Enable SMB always' and 'Enable SMB after carbs' are disabled. - -## Freestyle Libre sensors - -### xDrip+ with FreeStyle Libre - -None of the FreeStyle Libre systems (FSL1, FSL2, or FSL3) broadcast any information about the level of noise detected in the readings, and therefore 'Enable SMB always' and 'Enable SMB after carbs' are disabled for all setups using the FreeStyle Libre. - -In addition, many people have reported the FreeStyle Libre often produces noisy data. In xDrip+ there are a few options to help with this: - -**Smooth Sensor Noise.** In xDrip+ Settings > xDrip+ Display Settings ensure that Smooth Sensor Noise is turned on. This attempts to apply smoothing to noisy data. - -**Smooth Sensor Noise (Ultrasensitive).** If you are still seeing noisy data in xDrip+ you can apply more aggressive smoothing using the Smooth Sensor Noise (Ultrasensitive) setting. This will attempt to apply smoothing even on very low levels of detected noise. To do this, first enable [engineering mode](Enabling-Engineering-Mode-in-xDrip.md) in xDrip+. Then navigate to Settings > xDrip+ Display Settings and turn on Smooth Sensor Noise (Ultrasensitive). \ No newline at end of file diff --git a/docs/CROWDIN/zh/Usage/making-sport-with-AAPS.md b/docs/CROWDIN/zh/Usage/making-sport-with-AAPS.md deleted file mode 100644 index 79d2f1c38223..000000000000 --- a/docs/CROWDIN/zh/Usage/making-sport-with-AAPS.md +++ /dev/null @@ -1,185 +0,0 @@ -# making sport with AAPS - -In this section we want to address the topic of sport with AAPS. - -The aim is to show you how AAPS can help you to continue doing your favorite sport more easily or even to start doing it. It is relatively common for new type 1 diabetics to ask whether exercise is still possible for them, even if the answer in the training courses is actually a clear yes. Exercise is not only good for healthy people, but also for type 1 diabetics and even moderate exercise can even help to stabilize the blood sugar curve overall. - -:::{admonition} consult with your diabetes team after reading - -::: - -The difficulty here is that the prerequisites that someone brings with them and the expectations of what sport means to them are very different. - -Since we can assume that experienced top athletes with T1D who use AAPS are unlikely to look it up here, we deliberately set the bar low for ourselves when writing and for you when reading and using it, so that as many people as possible can benefit from it. - -Since even sport as a category is far too imprecise, as the effects of endurance sports differ greatly from strength training, for example, we are trying to break it down by type of sport. - -To be concrete and give you something you can test yourself we arrange the explanaiton around a concrete example and explain to you they action, reactions and effects. - -:::{admonition} more examples wanted - -The focus should always be on how others can do sport and not on the top performance someone has achieved. - -It's really about the basics. Your experience, which you share here, can help others to pursue their beloved sport more quickly and successfully and is therefore important. -::: - -## Cycling - -:::{admonition} take a friend with you - at least on your first trials -:class: information -A gerneral very good idea can be to take a good friend with you on the first rides. -This is especially important if you are not experienced in T1D. -Always keep in mind please: arrival comes before speed! Safety for you and the others in road traffic is very, very important. -::: - -### Example - -Let's take about 60 minutes of cycling on a flat route with a moderate heart rate as an example. - -1. we take a flat route in order to have an even load for the first exercise. This is not about performance, but purely about learning how you should react to changes in blood glucose. -2. we take the heart rate as an indicator of the load, as it is easy to see whether you are under load or not. -3. we set ourselves the goal of doing a relaxed lap around the neighborhood and focus on staying within our target range during the lap. In my case, this would be 70 <= x <= 180 mg/dl. - -We **don't** take the speed, as this is heavily dependent on personal physical conditions as well as the bike and surface used. It is therefore not very meaningful. - -You should know from the diabetes training courses you have attended that during endurance sports cycling, the insulin active in the body works significantly better than during times without physical exertion. The insulin active in the body is referred to as insulin on board (IoB). It is our most important parameter when cycling with T1D. - -We try to keep the IoB as low as possible at the start and during exercise. IoB should be around 0 or even slightly negative. You can get it there by not eating 3-4 hours before exercise. In the beginning it can also be helpful to exercise in the morning before breakfast, as with the right profile you should always have around 0 for IoB in the morning. - -AAPS shows us the IoB value on the home screen on the left under the blood glucose value. - -![IoB](../images/cycling_20240104-174035.png) - -:::{admonition} ignoring the IoB rule increases the risk for roller coaster BG dramatically -:class: danger -If you ignore this rule, you can still go cycling, but it will be much more difficult to keep your blood sugar levels in balance, so it is better to save this for later tests after several successful simple tests. -::: - -As you should know from the diabetes training courses, you should reduce the basal rate during exercise. The factor is individual. I have found a value of 50% in tests to be suitable for me. - -In AAPS, you should therefore change your profile to 50% before exercise and keep it active until the end of exercise. Some people even do it a certain amount of time before, e.g. 1 hour. Unfortunately, the pre-run is also individual. We will come to the post-run later. - -You should use two carbohydrates during exercise. - -1. medium-fast carbohydrates for the insulin still in the body and -2. very fast carbohydrates to prevent slipping into a hypo. - -For medium-fast carbohydrates, I treat myself to cookies or a banana before exercise, for example. You can also use something else that is more suitable for you. -For very fast carbohydrates, I take 3 teaspoons of dissolved glucose per 100 ml of still water in a 500 ml water bottle on my bike. If I'm cycling longer distances, I take a larger bottle with me and, if necessary, packaged glucose to refill the bottle. I add a little lemon juice for flavor. You can also use something other than lemon juice for the taste. You shouldn't change anything about the dextrose, as dissolved dextrose raises blood sugar levels super quickly. If you only take it in sips, your blood sugar won't go super high either! You can also do this tip at home beforehand as a dry run and see how quickly the change shows up on the CGMS. - -Why do I place so much emphasis on fast carbohydrates? - -1. once you are in a slight hypo, you may get back into the normal range by drinking the dextrose solution. As a rule, however, the oscillation of the curve then begins, which leads to a rollercoaster ride of the blood sugar. You may even be able to keep this within your target range, but you must be constantly vigilant. Without a hypo it is simply the most stable. -2. if you even slip into a somewhat severe hypo (without the need for outside help, of course), you may even have to pause briefly to avoid getting stuck in the hypo. - With both hypos, there is a risk that you will be tempted to switch from drinking 2-3 sips at a time to larger quantities. Not too bad at first, until the oscillation sets in and pushes you into a hyper. You can correct this, but your blood sugar will most likely go on a rollercoaster ride. - -What else is helpful, but not absolutely necessary? -It is important to keep an eye on your blood sugar, as your blood sugar can change enormously (e.g. 30 - 50 mg/dl) within 15 minutes of riding and a little more IoB or a basal rate that is still too high. The best way to keep an eye on it is if it is visible on the handlebars or if it is also displayed on your watch. It is even possible to install an additional app on some Garmin GPS bike computers that displays the blood glucose from XDrip or Nightscout as a data field on the bike computer. The additional app was developed by Andreas May from the T1D community. It is available free of charge in the official connect IQ Store. Certainly an interesting option for riders interested in sports. - -[Link to Andreas May Data Field App on connect IQ store](https://apps.garmin.com/de-DE/apps/5a3e2cda-12f0-4afd-88ed-000e67a68d84) - -Here is a picture of my Garmin Edge 530 bike computer with map, blood sugar and heart rate. - -![Garmin Edge 530 with BG data field](../images/cycling_IMG_1087.jpeg) - -After you have eaten the medium fast carbohydrates (24 - 36 g I take) and the blood sugar is above 100 mg/dl but also below 160 mg/dl, I carry out the profile change to 50% and set the activity temp target. - -:::{admonition} disable SMBs during high temp targets if necessary -:class: danger -Attention: If you prefer not to receive SMBs during the sport, please disable the option "Enable SMB with hight temp targets" in the settings of SMB or DynIFS Plugin. -::: - -The following picture shows the start and end of the sport. The end was specified as the duration when the profile was changed at the start. - -The temporary profile change has the following effects - -1. for a period of 60 minutes -2. a reduction to 50% of the profile and -3. the target is raised by clicking on the Activity Target option, which may have the side effect of disabling the SMBs - see above. - -![profile switch with temp target](../images/cycling_20240104-174056.png) - -The second image shows that the start at IoB was started towards 0. - -![IoB around 0](../images/cycling_20240104-174111.png) - -If the blood sugar drops faster than 15 mg/dl in 5 minutes or if it is at 120 mg/dl and tends to fall, I drink 1-2 sips of dissolved glucose. Then I wait for the next value and proceed as described above. - -You can hardly see it here, but at the beginning I took 2 sips from the bottle several times when my blood sugar started to fall. When it stabilized, I didn't need any more glucose. - -Here is the picture that illustrates this. The chart is saved on the Garmin as a result of the activity. - -![BG chart Garmin](../images/cycling_20240104-174431.png) - -If you should suddenly break out upwards, i.e. above 180 mg/dl, you should consider whether you should make a correction bolus. Caution: Remember the factor and apply it to the correction, otherwise the correction will be too strong. - -If your blood sugar drops below 80 mg/dl, take a break and drink two sips until your blood sugar is back above 100 mg/dl. - -At the end of the ride, the profile change should be finished as the time is up. - -Since we only rode easy for 60 minutes, there shouldn't be a big muscle bulking effect continuing to pull carbohydrates from your blood sugar. However, if it felt strenuous to you, keep an eye on it. This is especially true if you then go straight to bed. It may be better to change your profile to e.g. 80% for sleep. You may come out of sleep slightly too high, but it's better than having a hypo at night. Over time, you will surely find out what happens to you. - -The following pictures show the low intensity of the sport. - -The elevation profile -![](../images/cycling_20240104-174314.png) - -Speed with average and maximum speed - -![](../images/cycling_20240104-174326.png) - -Note the pause at the level crossing, which is also reflected in the heart rate. - -The heart rate. -![](../images/cycling_20240104-174337.png) - -The training effect. -![](../images/cycling_20240104-174358.png) - -The time in the different heart rate training zones. -![](../images/cycling_20240104-174423.png) - -After succesfully mastering this simple example you could go for further targets by stretching - -1. the distance and time -2. the load during the ride -3. the elevation during the right which should make a big impact on the more necessary carbs or further reduction of IoB and percentage of profile switch. - -Based on my experiences I would not expect to come back 100% with time in range over the whole and every ride. - -### Tipps - -I already gave some tipps for during the ride above. - -Here are some further tipps what can go wrong and how you can act to prevent it or react to compensate it. - -#### sky rocket high after ride - -During the ride everything was fine but after siting down and relax the blood sugar go sky rocket high. - -**Possible reason:** This happens when you have drunk too much dissolved glucose. - -**Reaction:** Drink 500 ml water, go to the shower and then control again. Latest after 30 minutes think about giving a correction bolus but be careful when it is short for bed time. Therefore it can be very good to make the first try runs on weekend mornings. - -**Action:** Next time be a bit more cautious in drinking from the dissolved glucose. - -#### hypo during ride - -During the ride you are going into hypo and can't recover your blood sugar during cycling. - -**Possible reason:** Your body cannot absorb enough carbohydrates quickly enough during exercise. - -**Reaction:** Take a rest and corrrect your blood sugar with drinking dissolved glucose. Stay calm: arrival comes before speed. - -**Action:** Did you started with IoB near 0? Have you eaten a small amount of middle fast carbs? Can you increase this or are the not fast enough for your body? Is it possible to prevent going into hypo by reducing the factor for the profile switch? Have you disbaled SMBs during ride as explained above? - -#### sky rocket high during ride - -During the ride your blood sugar goes sky rocket high. - -**Possible reason:** You have got taken too much carbs for your IoB at that time. Beneath for sure the typical technical problems with your -insulin pump like leakage or blockage of the catheder! - -**Reaction:** If it is too high for you take a rest and correct with a bolus. Keep in mind that you must ride home and therefore make it carefully. Drink 500 ml pure water without carbs. Stay calm: arrival comes before speed. - -**Action:** Have you eaten too much? Especially have you drunk too much from the dissolved glucose during the ride? Is your percentage of reduction the profile during profile switch too low and you can increase this?