Iām guessing thatās a āno.ā It was a reach.
Sorry. What is a no?
Yes. They are fully modular but I assume you are technical? You use what you want like a open pump with any sensor. Of course many people want to run closed instead of open loop.
Well, like, I guess Iām asking if I could piece a system together with just functionality to counteract lows from excessive basal, or just counteract post meal highs. Like, the systems tend to be so āall encompassingā that inevitably there is one piece of the functionality that doesnāt work well and the whole thing goes up in a ball of flames. Like, they arenāt as customizable/individualized as I imagined they would be. I suppose that is just the nature of the beast, or maybe just where we are at right now.
For example, when I was on Loop, the thing that really broke me was when they changed the algorithm for meal time insulin delivery. If I could have pulled that out, and replaced it with the original algorithm, I think I could have continued using it. But, everything was so tied up together, that would have broken all the functionality that accomidates new transmitter models. So, there was no effective way to pull an algorithm out or try on different algorithms with different rates of infusion at mealtime.
Does that make sense? I guess Iām asking if androidAPS is farther along in that way - like, could I pull out one algorithm for a specific piece of functionality and swap it out with a different algorithm? Or, am I pretty locked in?
Like, (I dont know) I donāt even think I would charectorize the problem as a āspaghetti codeā issue. More of like, the paradigm of how the system is constructed, where all these individual pieces are so dependent on one another than nothing actually operates independently. Thatās something that might not be able to be changed because of the nature of what is being built, but I would appreciate your feedback.