defragster
Senior Member+
I'm going to try some ideas to handle these cases much better. Ideally, when the gaps are under 20%, it should become possible to automatically purge this bad data, and most of the lower quality data causing the variance error. But rejecting bad data is tricky
Tricky was my expectation. That why I went as far as "suggest starting a new calibration session". If you did the colorization of such odd 'solar flare' type data - and show the percentage of data that is being used to alter the current state of the 'calibration update'. Maybe when 'Send Calibration' is selected you could pop up a dialog: " xx% of the data in this sample session appears out of bounds - Yes to save, no to start a new session "
This time I neared the magnet on purpose - the other day it was inadvertent because I was staring at the screen I wasn't watching my hand - but then I also knew I got near something drastic - so I looked to see what was around me.
BTW: with it lying on my desk I pushed my Cortex powered 'BAND' around it and nothing odd happened this time.
ALSO: to multitask here - Frank updated his TeensyTransfer and it compiles for me - he fixed the one long name garbage - then I found another oddity I told him about.