Loop for iOS

Spike calibration guide: Spike calibration, https://cyoung1024.github.io/spike-guide/calibration/

- Do not use this branch with rechargeable transmitters for Dexcom & Spike
- Always have alarms enabled for both lows and highs (also fast drop & fast rise)
- Read and follow the Spike calibration guide for every calibration
- Disable automatic boluses until you are able to get a good calibration
- Calibrate properly and often check the values reported by Spike against values from a glucose meter

If you are using Dexcom rechargeable transmitters please use Spike in follower mode, with the Dexcom app as primary collector of data. This is because recently there have been cases of rechargeable transmitters providing inaccurate data. The Dexcom app has safety mechanisms built in, while Spike will report any data it reads from the sensor.

What are the problems with rechargeable transmitters?

• Multiple users reported noisy data.
• If the transmitter's battery nearly runs out it will read HIGH. It is extremely important to use the Dexcom app and Spike in follower mode to avoid this issue. If you're using Spike directly with the rechargeable transmitter, Loop will deliver large boluses due to the erroneously reported increase in levels.

You are on branch spike-autobolus

This branch is a merge of https://github.com/LoopKit/Loop/tree/automatic-bolus and https://github.com/Andrei0105/Loop/tree/dev-spike.

Last updated on Aug 23, 2020

Loop is an app template for building an automated insulin delivery system. It is a stone resting on the boulders of work done by many others.

Loop is built on top of LoopKit. LoopKit is a set of frameworks that provide data storage, retrieval, and calculation, as well as boilerplate view controllers used in Loop.

Please understand that this project:

• Is highly experimental
• Is not approved for therapy

Documentation

Please visit the Loop Docs for installation, algorithm, and other details.

For FAQs and other tips, refer to the Wiki

(Note: there is also a tab for the Wiki at the top of this page)

License and Code of Conduct

Please read the LICENSE and CODE_OF_CONDUCT