You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Phantom "meter reset" in the data-quality report. A CSV export taken mid-period pads its remaining slots with 0. Because the meter columns are cumulative counters, that padding read as one enormous drop, and the per-granularity check reported a meter reset that never happened. Those trailing rows are now recognised as padding and removed at import.
Your totals were never wrong — the rollup already skipped negative deltas. Only the data-quality finding was spurious.
Zeros between real readings are left alone: those are a meter dropout, already handled separately.
A row counts as padding only when every value column is absent or zero, so a genuine zero reading in one column (an empty battery's state of charge, for example) is never mistaken for it.
The number of rows dropped is logged on import.
📝 Docs
DESIGN_SPEC.md §3.3 now documents export padding at both ends of a file — the leading collapse-to-anchor and this new trailing removal — and why each is lossless.