Allow variation of max basal rate when carbs are entered.

[tim2000s]

If people are using DCA to manage meals by setting a max basal rate to much higher than what one would consider to be safe for use without carbs present, encourage setting a true “safe” amount then allow loop to increase the max basal rate by a multiplier only when carbs are present and until a specific amount of carbs have been observed absorbed (maybe 65%).

This should leave the safety features that are built in in place for normal use.

[ps2]

This ticket is predicated by an 'if'. Could you give an example of someone "using DCA to manage meals by setting a max basal rate to much higher than what one would consider to be safe for use without carbs present"?

Loop's max basal rate is a safety valve that should be raised as the user gains confidence in the predictions. As settings are tuned and prediction performance improves, then max basal rate can be raised to gain more control. Having multiple settings for this adds complexity. Are you thinking predictions with carbs on board are less risky, and so loop should be able to act on them more strongly? This actually seems reversed from the truth. Predictions with carbs on board are inherently more difficult, and more likely to be off.

[Kdisimone]

Closing. No further requests for this feature have been received in the various forums. We can reopen if additional discussion is requested or warranted.