Traffic Table
Contains information about the vehicle passes, including start and end times for each load event, gear configuration, applied loads (actual), and wander position.
|
Traffic_ID
|
Unique number assigned to a traffic event. An event is defined as a movement of the vehicle with loads.
|
|
Track_ID
|
Track number defining the lateral position of the vehicle during event EventNo. There are 9 track numbers ranging from [-4, 4] as defined in the Track table.
|
|
Wander Pattern
|
Two different wander patterns were used to traffic CC-3. The standard wander pattern was used for all but one day of trafficking. An alternate MWHGL wander pattern was utilized for the single day of trafficking. The Wander Pattern page provides further information about the two wander patterns. |
|
EventStartTime
|
Date and time of the start of a traffic event. Dates are given in the format MM/DD/YYYY. Time is local time (New Jersey, USA).
|
|
EventEndTime
|
Date and time of the end of a traffic event. Dates are given in the format MM/DD/YYYY. Time is local time (New Jersey, USA).
|
|
AvgModuleLoadsLB
|
Average module loads corresponding to traffic event EventNo (lbs.). Values are given as a string of 6 space-delineated values as follows: Carriage 1 Module 1, Carriage 1 Module2, Carriage 1 Module 3, Carriage 2 Module 1, Carriage 2 Module 2, and Carriage 2 Module 3. |
|
LFC1
|
Flexible pavement section 1. A value of ‘0’ indicates LFC1 was not trafficked during the event, while a value of ‘1’ indicates it was trafficked.
|
|
LFC2
|
Flexible pavement section 2. A value of ‘0’ indicates LFC2 was not trafficked during the event, while a value of ‘1’ indicates it was trafficked.
|
|
LFC3
|
Flexible pavement section 3. A value of ‘0’ indicates LFC3 was not trafficked during the event, while a value of ‘1’ indicates it was trafficked.
|
|
LFC4
|
Flexible pavement section 4. A value of ‘0’ indicates LFC4 was not trafficked during the event, while a value of ‘1’ indicates it was trafficked.
|
| Gear_ID |
Gear configuration for event EventNo. Refer to table Gear.
|
|
Wander_ID
|
Indicates individual passes of the test vehicle for completion of the wander pattern. The standard CC-3 wander pattern utilized a 66 pass sequence. The MWHGL wander pattern utilized a 30 pass sequence.
|
|
Comment
|
Comments
|
CC3 Summary of Daily Trafficking
|
Date
|
Number of Wanders
|
Number of Runs
|
Note
|
|
09/03/02
|
1 (1)
|
66 (66)
|
Start of CC3 traffic tests from 14:13 on LFC-1, 2, 3, &4. 2 mph test speed. 55 kip wheel loads.
|
|
09/04/02
|
3 (4)
|
198 (264)
|
Continue trafficking of LFC-1, 2, 3, & 4. 90 runs LFC-1 north declared failed. (Unloaded from 91st run). 132 runs LFC-1 south declared failed. (Unloaded from 133rd run).
|
|
09/05/02
|
5 (9)
|
330 (594)
|
Continue trafficking of LFC-2, 3, & 4.
|
|
09/06/02
|
6 (15)
|
396 (990)
|
Continue trafficking of LFC-2, 3, & 4.
|
|
09/07/02
|
6 (21)
|
396 (1386)
|
Continue trafficking of LFC-2, 3, & 4.
|
|
09/08/02
|
3 (24)
|
198 (1584)
|
Continue trafficking of LFC-2, 3, & 4.
|
|
09/09/02
|
5 (29)
|
330 (1914)
|
Continue trafficking of LFC-2, 3, & 4. No loading on LFC-2 north from 1593rd run due to concerns of vehicle reaction to pavement damage.
|
|
09/10/02
|
7 (36)
|
462 (2376)
|
Continue trafficking of LFC-2 south and LFC-3 & 4.
|
|
09/11/02
|
5(41)
|
330(2706)
|
Continue trafficking of LFC-2 south and LFC-3 & 4.
|
|
09/12/02
|
7(48)
|
462(3168)
|
Continue trafficking of LFC-2 south and LFC-3 & 4. Finished on LFC-2 south at 3,168 runs.
|
|
09/13/02
|
0
|
0
|
Test pit in LFC-2.
|
|
09/14/02
|
0
|
0
|
Weekend.
|
|
09/15/02
|
0
|
0
|
Weekend.
|
|
09/16/02
|
0
|
0
|
Test pit in LFC-2.
|
|
09/17/02
|
12*(12*)+12runs
|
372(3540)
|
Continue trafficking of LFC-3 & 4. *Modeled on MWHGL (30 steps). 55 kip wheel loads.
|
|
09/18/02
|
9*(21*)+4(52)
|
534(4074)
|
Continue trafficking of LFC-3 & 4. *Modeled on MWHGL. Changed wheel loads to 65 kip & old wander pattern (66 runs) after 13:01.
|
|
9/19/02
|
12(64)+18 runs
|
810(4884)
|
Continue trafficking of LFC-3 & 4.
|
|
9/20/02
|
10(74)
|
660(5544)
|
Continue trafficking of LFC-3 & 4.
|
|
9/21/02
|
14(88)
|
924(6468)
|
Continue trafficking of LFC-3 & 4.
|
|
9/22/02
|
15(103)
|
990(7458)
|
Continue trafficking of LFC-3 & 4.
|
|
9/23/02
|
14(117)
|
924(8382)
|
Continue trafficking of LFC-3 & 4.
|
|
9/24/02
|
15(132)
|
990(9372)
|
Continue trafficking of LFC-3 & 4.
|
|
9/25/02
|
16(148)
|
1056(10428)
|
Continue trafficking of LFC-3 & 4.
|
|
9/26/02
|
13(161)+39 runs
|
897(11325)
|
Continue trafficking of LFC-3 & 4. Tire on C1M2 north failed at the end of east run. Changed next day.
|
|
9/27/02
|
11(172)+27 runs
|
753(12078)
|
Continue trafficking of LFC-3 & 4.
|
|
9/28/02
|
16(189)
|
1056(13134)
|
Continue trafficking of LFC-3 & 4.
|
|
9/29/02
|
18(207)
|
1188(14322)
|
Continue trafficking of LFC-3 & 4.
|
|
9/30/02
|
11(218)
|
726(15048)
|
Continue trafficking of LFC-3 & 4.
|
|
10/01/02
|
10(228)
|
660(15708)
|
Continue trafficking of LFC-3 & 4.
|
|
10/02/02
|
14(242)
|
924(16632)
|
Continue trafficking of LFC-3 & 4.
|
|
10/03/02
|
10(252)
|
660(17292)
|
Continue trafficking of LFC-3 & 4.
|
|
10/04/02
|
12(264)
|
792(18084)
|
Continue trafficking of LFC-3 & 4.
|
|
10/05/02
|
8(272)
|
528(18612)
|
Continue trafficking of LFC-3 & 4.
|
|
10/06/02
|
16(288)
|
1056(19668)
|
Continue trafficking of LFC-3 & 4.
|
|
10/07/02
|
7(295)
|
462(20130)
|
Continue trafficking of LFC-3 & 4.
|
|
10/08/02
|
7(302)
|
462(20592)
|
Continue trafficking of LFC-3 & 4.
|
|
10/09/02
|
7(309)
|
462(21054)
|
Continue trafficking of LFC-3 & 4.
|
|
10/10/02
|
7(316)
|
462(21516)
|
Continue trafficking of LFC-3 & 4.
|
|
10/11/02
|
6(322)+52 runs
|
448(21964)
|
Continue trafficking of LFC-3 & 4.
|
|
10/15/02
|
8(330)+14 runs
|
542(22506)
|
Continue trafficking of LFC-3 & 4.
|
|
10/16/02
|
6(337)
|
396(22902)
|
Continue trafficking of LFC-3 & 4.
|
|
10/17/02
|
8(345)
|
528(23430)
|
Continue trafficking of LFC-3 & 4.
|
|
10/18/02
|
6(351)
|
396(23826)
|
Continue trafficking of LFC-3 & 4. Finished trafficking of LFC-3 & 4 @ 23,826 runs.
|