WEBVTT

1
00:00:00.400 --> 00:00:02.950
A summary can contain plausible counts and

2
00:00:02.960 --> 00:00:05.030
still have the wrong number of bins.

3
00:00:05.200 --> 00:00:07.830
The key question is which completed header

4
00:00:08.080 --> 00:00:11.190
defines that summary record. The mixed-file parser

5
00:00:11.200 --> 00:00:14.630
tracks header blocks. Definitions collected between H

6
00:00:14.640 --> 00:00:17.000
zero and H nine become active when

7
00:00:17.000 --> 00:00:19.350
the header closes, and the next completed

8
00:00:19.360 --> 00:00:21.680
header can change the context. For a

9
00:00:21.680 --> 00:00:24.790
type twenty example, the implemented check expects

10
00:00:24.800 --> 00:00:27.510
the configured bin count plus ten fields.

11
00:00:27.840 --> 00:00:31.510
Three configured bins therefore require thirteen fields;

12
00:00:31.520 --> 00:00:34.470
twelve fields produce a count mismatch. Summary

13
00:00:34.480 --> 00:00:37.590
configuration checks also inspect the applicable class

14
00:00:37.600 --> 00:00:40.310
or bin definitions. These checks address the

15
00:00:40.440 --> 00:00:43.430
record structure and configuration, not an assurance

16
00:00:43.440 --> 00:00:45.670
that the traffic counts are physically correct.

17
00:00:46.080 --> 00:00:48.870
Separate checks examine timestamp order and daily

18
00:00:48.880 --> 00:00:51.830
coverage in the mixed-file route. A complete-looking

19
00:00:51.840 --> 00:00:53.510
row is not enough to prove a

20
00:00:53.520 --> 00:00:56.790
complete observation period. Use the complete source

21
00:00:56.800 --> 00:01:00.390
file when reviewing header-dependent findings. A standalone

22
00:01:00.400 --> 00:01:03.110
summary lacks the active-header evidence needed for

23
00:01:03.120 --> 00:01:05.910
this comparison. Correct the relevant definition or

24
00:01:06.080 --> 00:01:09.430
record and rerun, retaining the original context.