search

nightscout / cgm-remote-monitor

nightscout web monitor
GNU Affero General Public License v3.0
2.43k stars 71.82k forks source link

Delete CGM reading #7847

Open paddingtonil opened 1 year ago

paddingtonil commented 1 year ago

It is not unusual for CGM readings to be off on the first and last day, as well as when the transmitter battery is depleted. These discrepancies often exceed the 20%/20 rule, thus influencing statistics. It may be very useful to have the option of revoking noisy data in order to obtain more reliable statistics.

sulkaharo commented 1 year ago

The reporting section already does a filtering pass on CGM data to remove noise before variability metrics are reported. We could look into an additional feature to ignore the first day after sensor change? I don't think we'd want to implement actual deletion of data, as the database is a record of what has happened and deleting data doesn't change that fact - it's the role of reporting to provide the desired views into the data.

paddingtonil commented 1 year ago

CGM and BG discrepancies are random, with a high likelihood of occurring on the first day. There were sensors that were spot on from warmup and others that I had to calibrate a few times during the 10 day session. Ignoring one specific date, IMHO, while keeping the corrupted CGM readings will provide us with biased reports. There might be a better way to eliminate the problematic readings from NS reports while maintaining the inaccuracies.