Looking at temperature curves before matching files to the trip list can hide gaps in coverage. Establish which trips are represented first, then determine what the measurements show.
Coverage first, temperature second
Compare the trip list with files; count files missing, unmatched or shorter than the trip separately. No file is not a measured normal temperature.
The order of work
Combine the trip list and file names in one table; leave source files unchanged.
Link each file to a container ID and trip ID; put unmatched files in a review queue.
Separate product regimes and use the evaluation method defined by the site.
Compare trip duration with recording start and end, marking uncovered intervals.
Once coverage is clear, review measured deviations with the applicable definition and raw record.
Curves and file lists
The monthly summary should show file status, container ID, covered interval and measured deviation separately for each trip. A gap in recording should not share a category with a normal measurement on a curve.
Why an average is not enough
A monthly average can hide an individual peak, duration and intervals without measurements. Keep raw curves and trip-level durations; use thresholds or decision methods from product specifications and the authorized quality process.
What the month should leave behind. List covered trips, missing or short files, unmatched records and separately verified measurement deviations. Send uncertainties for responsible review.
Time and month-to-month comparison
Keep raw device time, time zone and download time in separate fields. Use the same coverage and definitions for monthly comparisons; record the source of any clock conversion.
