Using the Input-Output Diagram to Determine the Spatial
Download
Report
Transcript Using the Input-Output Diagram to Determine the Spatial
Using the Input-Output Diagram
to Determine the Spatial and
Temporal Extents of a Queue
Upstream of a Bottleneck
Tim W. Lawson
David J. Lovell
Carlos F. Daganzo
University of California at Berkeley
1
Outline
Background
Bottleneck with constant departure rate
“Conventional” (time-space) Approach
Proposed (input-output) Approach
Extensions to Approach
Purpose and objective
Automation, varying capacity, traffic signal
Conclusions
2
Background
Concepts of “Delay” and “Time in Queue”
Delay = actual time - free flow time
Time in Queue = Delay for “point” queues
Time in Queue > Delay for traffic queues
Concepts confused in the literature
Evaluation and MOEs
Value of time
Energy and emissions
3
Motivation
Time-Space Diagram Approach
clear distinction: Delay & Time in Queue
(often) well understood
difficult to construct
Objective
clear up some of the confusion
provide a simple approach based on
familiar tools (input-output diagram)
4
Assumptions
Constant free-flow speed, vf
Congested speed, vm
speed is constant, regardless of flow
speed is dependent on bottleneck capacity
Typical time-space diagram assumptions
e.g., instantaneous speed changes
5
“Conventional” Approach
6
Conventional Approach
7
Lessons From t-x Diagram
1
1
w = v - v dQ
m
f
w
dQ = 1
1
v
v
m
tQ =
f
w
vm
1- v
f
8
Basic Input-Output Diagram
9
Proposed Approach
10
Interpretation
11
Interpretation
12
Other Applications
Automation on a spreadsheet
Bottleneck whose capacity changes once
required: upstream arrival times, m, vf, vm
provides same measures
simple extension to above approach
Undersaturated Traffic Signal
“limiting” case
13
Conclusions
Simplicity
modifies widely used and understood tool
much less tedious than t-x; automation
14
Conclusions
Simplicity
modifies widely used and understood tool
much less tedious than t-x; automation
Utility
estimates of wait times, etc.; impacts
queue lengths; time of maximum queue
15
Conclusions
Simplicity
Utility
modifies widely used and understood tool
much less tedious than t-x; automation
estimates of wait times, etc.; impacts
queue lengths; time of maximum queue
Superiority
corrects significant misunderstanding
16