Looking for "less than current" only makes sense if user can do multiple iso UF sessions in a treatment. And if that's the case, we should be looking at how much time we've already spent doing iso UF instead of how much time we've spent in the HD or HDF treatment.
can you help explain what this method does exactly? This takes a very long time. Can we simply just test the min and max with arrows then min and max with slider. This seems to go back and forth for each item.
All these are more of debug related overrides (acid and bicarb P & I gain). you can keep them in one function, when the implementation is complete, you may remove these. The init function is too big, group them and split in the functions and call here.
ive noticed this common method being used in other test cases. If its a general method that is used throughout please move outside in a shared file and call from there. Please update other repositories that use this as well.
when running I am stuck here for 10 min which and does not hit this condition... I think we are missing the global vitalsrequest at the top of this block
Since this is being used everywhere, I would recommend defining a global variable(s) so that we can later be flexible to adjust that for all the mouse clicks or watforobject functions
