GrapesAfonsoGithub

My point is that there is no "quantitative fashion" that can help us here because the context of hypoglycaemia is, sometimes, caused by quantitative inputs that are wrong but the...

Adrian, let me answer in pieces [adrian]This is still the wrong repo to discuss the base algorithm of OpenAPS. [Miguel] i disagree. My point is NOT to change the algorithm....

Let me simplify things please. All i am suggesting is a safety feature, optional to the user, of "with BG

Team, i dont want to get into the details of openAPS as i dont see the algorithm needs to be fixed. Nor would i be an expert to sugest any...

Just to make developers lifes easier, i add here another idea from the FB discussion which could be a low hanging fruit for everyone ---- Dan Evans One other reflection...

this is not a proposal of algorithm change or fork. It is an incremental safety feature. When you say scott, that it may drive future highs: maybe. But the point...

testing it is way beyond my technical skills, unfortunately. Regarding the change: the app already has a ton of safety features, this is just another one (not saying it is...

Here you have a fresh example of why this safety feature is needed. Context: hipoglicemia with a temp target of 150. The BG moves from 54 to 59 and the...

This is my daughter's app. I don't user her as a guinea pig. And no, she was not rising. After that 59 it came down again. So ofcourse i gave...

Scott, sorry, what you say is medically and factually incorrect. 1 - cutting insulin in the context of hypoglycemia (especially a severe one as a 59) is one of the...