CE 474 Traffic Systems Design Fall 2001

Lab Assignment #4: Highway Capacity Software Calibration

and Validation
Background
The purpose of this assignment is to test how well the Highway Capacity Manual model, for
computing the capacity and level of service of a signalized intersection, replicates the operation of
the intersection that you have just studied. You will work with other members of your team to
predict the average delay per vehicle and v/c ratio based on the data that have been collected in the
field. You will make modifications to the model (i.e., “calibrate” the model) so that the model
predictions more closely reflect field observations of the delay and cycle failures. Then you validate
the model using independent data.

Scope of Work
Before we begin the formal steps to this lab, we need to combine the data collected at the different
approaches. While we are doing this we need to make sure that the data is reasonable and that the
information extracted from the data is correct. Each group should have a copy of the data collection
report for each approach. Based on what you observed while at the intersection, review the material
and determine whether it is satisfactory and if you can get the information that you need from it. If
additional information is needed, ask the individuals responsible for the data.

Perform the steps outlined below in your respective teams.

Step 1. The Highway Capacity Software (HCS 2000) requires the following input data:

Intersection lane usage a

Traffic flow rates for each movement a

Peak hour factors (use 1.0 for this lab because we are already using 15 minute flow rates)

Right turns on red b

Initial unmet demand a

Unit extension c

Extension of effective green b

Intergreen times c

Phasing pattern a

Phase length and cycle length a

Proportion of heavy vehicles a

Lane widths a

Presence or absence of parking a

Parking maneuvers per hour b
a. see field data
b. use default value
c. given in lab

Four teams comprised of two groups (A and B) will perform the data input and intersection analysis.
The A groups and B groups will perform the analysis for the first and second time period of data

Page 1 of 3
CE 474 Traffic Systems Design Fall 2001

collected in the previous lab, respectively. The above data should be entered in a new signal analysis
file, of the operations type, in HCS 2000.

Step 2. Perform this step in your respective groups (A and B). Using all of the default values
provided as part of HCS 2000, use the model to predict the values for the capacity, degree of
saturation, and delay for each lane group for the time period you were assigned. Record the
estimated degree of saturation and delay values.

Calibration
Perform steps 3 through 6 two times so that the estimated delay and v/c ratios, by lane group, have
been adjusted as closely as possible to what was observed in the field.

Step 3. Identify the differences between your measured values for delay and the values predicted by
HCS 2000. Do the v/c ratios seem reasonable based on what was observed in the field (i.e., cycle
failures)? Is the estimated delay sufficiently close to what was observed (i.e., +/- 10%)? What are
the possible (and alternative) reasons for these differences?

Step 4. Discuss the questions posed in step 3 with the other group in your team.

Step 5. As a team, prepare a list of possible changes that you can make to the HCS model default
input values that would improve your predicted values (i.e., delay and degree of saturation).

Step 6. Implement the changes in your respective groups (A and B) and record the new predicted
values of delay and degree of saturation. Document the changes that you have made as part of your
calibration process.

Step 7. Record your predicted values of delay and your observed values in a table together with the
v/c ratios by lane group. Organize your data by calibration run (1 and 2).

Validation
Step 8. Finally, run the model using the data for the last two time periods of data collection. Groups
A and B will use data from time periods 3 and 4, respectively. This will allow you to determine how
well the model works using an independent set of data, without being able to make additional
modifications to the input parameters. This is a measure of how well the model will work when you
are evaluating different design alternatives.

Deliverable
Document your input values that were collected from the field, limited to a table for volume and a
table for signal timing data. Document your calibration process, including the results of your
calibration, the modifications that you made to the HCS default values, and the results of your
validation. As a team, organize your lab results into three tables, one table describing the
modifications made for each calibration run, one table for the calibration results for each run, and
another table for the validation results. The individual groups (A and B) then need to assess the
adequacy of HCS 2000 as a predicting and analysis tool based on the results of the validation tests
and prepare a formal four page report (including tables). Make sure that your report is neat, correct,
thorough, efficient, proofread, and demonstrates that you understand.

Page 2 of 3
CE 474 Traffic Systems Design Fall 2001

Deadline
The report summarizing your analysis (one report per group) will be due at the beginning of class on
Monday, October 8.

Teams and Groups

Table 1 Team and Group Assignments.
Team Group Students
Ravi
A
Cindy
1
Gary
B
Sharat
Kumar
A
JR
2
Jeff
B
Jens
Raju
A
Rahim
3
Craig
B
Sajeev
Kevin
A
Vijay
4
Melissa
B
Chunyu

Page 3 of 3