40
Practical issues with DTA CE 392D DTA in practice

Practical issues with DTA · DTA in practice Preparing Input Data. Deciding which streets to include in the network is a balance of accuracy and computation time/data collection requirements

  • Upload
    others

  • View
    1

  • Download
    0

Embed Size (px)

Citation preview

Page 1: Practical issues with DTA · DTA in practice Preparing Input Data. Deciding which streets to include in the network is a balance of accuracy and computation time/data collection requirements

Practical issues with DTA

CE 392D

DTA in practice

Page 2: Practical issues with DTA · DTA in practice Preparing Input Data. Deciding which streets to include in the network is a balance of accuracy and computation time/data collection requirements

PREPARING INPUT DATA

Page 3: Practical issues with DTA · DTA in practice Preparing Input Data. Deciding which streets to include in the network is a balance of accuracy and computation time/data collection requirements

What do you need to run the basic traffic assignment model?

The network itself

Parameters for link models (capacities, free-flow speeds, etc.)

OD matrix

The extensions of TAP require additional information, such as demand func-tions, destination attractiveness, logit parameters, value of time, etc.

DTA in practice Preparing Input Data

Page 4: Practical issues with DTA · DTA in practice Preparing Input Data. Deciding which streets to include in the network is a balance of accuracy and computation time/data collection requirements

Deciding which streets to include in the network is a balance of accuracyand computation time/data collection requirements.

In practice, regional models typically include minor arterials and largerroads; neighborhood streets are typically abstracted into centroidconnectors:

Neighborhood streets are typically uncongested, so there isn’t a need tomodel them in great detail. (Or is there?)

DTA in practice Preparing Input Data

Page 5: Practical issues with DTA · DTA in practice Preparing Input Data. Deciding which streets to include in the network is a balance of accuracy and computation time/data collection requirements

Ideally, fundamental diagrams are obtained through regression of fielddata. What are the complications?

DTA in practice Preparing Input Data

Page 6: Practical issues with DTA · DTA in practice Preparing Input Data. Deciding which streets to include in the network is a balance of accuracy and computation time/data collection requirements

(Aside: recent research is looking at changes-of-variables which produce abetter fit to data.

These use Lagrangian coordinates (n, t) or (n, x), instead of Euleriancoordinates (t, x).

DTA in practice Preparing Input Data

Page 7: Practical issues with DTA · DTA in practice Preparing Input Data. Deciding which streets to include in the network is a balance of accuracy and computation time/data collection requirements

The OD matrix is often the most challenging input data to calibrate, forseveral reasons:

There are many more OD matrix entries than links.

The OD matrix can’t be observed directly (unlike link speeds andflows).

Can we use direct observations (say, link flows) to try to estimate the ODmatrix?

DTA in practice Preparing Input Data

Page 8: Practical issues with DTA · DTA in practice Preparing Input Data. Deciding which streets to include in the network is a balance of accuracy and computation time/data collection requirements

This is surprisingly difficult!

Because there are more OD matrix entries than links, the problem is highlyunderdetermined; the problem is not finding an OD matrix that matchesthe

B D E

C

150

100

250

A50

One trivial solution is for all trips to go from one node to a neighboringnode.

DTA in practice Preparing Input Data

Page 9: Practical issues with DTA · DTA in practice Preparing Input Data. Deciding which streets to include in the network is a balance of accuracy and computation time/data collection requirements

(As an aside, the distinction between a good regression fit and a goodmodel is absolutely critical here.)

DTA in practice Preparing Input Data

Page 10: Practical issues with DTA · DTA in practice Preparing Input Data. Deciding which streets to include in the network is a balance of accuracy and computation time/data collection requirements

We often have an OD matrix available from other parts of the planningprocess, say, a gravity model. Can we use this “target” OD matrix as astarting point which can be adjusted to conform to link flows?

OD Matrices Link flows

Observed flows

Target matrix

DTA in practice Preparing Input Data

Page 11: Practical issues with DTA · DTA in practice Preparing Input Data. Deciding which streets to include in the network is a balance of accuracy and computation time/data collection requirements

We can try a least-squares approach where we try to match both thetarget OD matrix and the link flows:

mind,x

λ∑rs

(d rs − d

rs)2

+ (1− λ)∑ij

(xij − x ij)2

where λ reflects the importance put on matching the OD matrix relativeto the link flows; the proper balance is a matter of judgment and dependson the level of trust in the accuracy of d and x.

We have two constraints: nonnegativity of OD matrix entries d rs ≥ 0, andthat the link flows x must be a user equilibrium solution given the ODmatrix d.

DTA in practice Preparing Input Data

Page 12: Practical issues with DTA · DTA in practice Preparing Input Data. Deciding which streets to include in the network is a balance of accuracy and computation time/data collection requirements

Because field data contains some noise and error, however, all solutionswhich satisfy link flows exactly may have short trips:

B D E

C

148

101

250

A50

DTA in practice Preparing Input Data

Page 13: Practical issues with DTA · DTA in practice Preparing Input Data. Deciding which streets to include in the network is a balance of accuracy and computation time/data collection requirements

A quasi-dynamic approach can help match the number of decisionvariables and observations.

Divide the analysis period into “sub-periods”; assume that within eachsub-period, the distribution of trips between origins and destinations isfixed.

DTA in practice Preparing Input Data

Page 14: Practical issues with DTA · DTA in practice Preparing Input Data. Deciding which streets to include in the network is a balance of accuracy and computation time/data collection requirements

If we have counts available on nlc links, and there are nθ time steps in theanalysis period, then we have nlcnθ observations we can use.

If there are nod OD pairs, then there are nodnθ entries in the dynamic ODmatrices; generally nod � nlc , so we have many more unknowns thanequations.

With the approach of Cascetta et al., let no be the number of origins, andnτ the number of “sub-periods” of the analysis peirod. Then the numberof unkowns is:

nθno values, giving total departures from each origin at each timestep.

nτ (nod − no) values, giving the proportion of the demand from eachorigin to each destination during time period τ .

DTA in practice Preparing Input Data

Page 15: Practical issues with DTA · DTA in practice Preparing Input Data. Deciding which streets to include in the network is a balance of accuracy and computation time/data collection requirements

By adjusting the length of the “sub-periods” and timestep, we can bringbalance to the number of unknowns and equations.

The ratio is approximately 1 if nlc ≈ no + nτnθ

(nod − no)

DTA in practice Preparing Input Data

Page 16: Practical issues with DTA · DTA in practice Preparing Input Data. Deciding which streets to include in the network is a balance of accuracy and computation time/data collection requirements

The mθ′θodl parameters are key: they reflect the fraction of flow that

departred OD pair od at time θ′ which is on link l at time θ. This can beobtained from network loading; but if the OD matrix changessubstantially from the seed, we need to do another loading.

DTA in practice Preparing Input Data

Page 17: Practical issues with DTA · DTA in practice Preparing Input Data. Deciding which streets to include in the network is a balance of accuracy and computation time/data collection requirements

An alternative formulation: use departure time choice to automatically“profile” the demand.

Advantage: Departure time profiles are endogenous; determinedbehaviorally rather than statistically

Disadvantage: Parameters in schedule delay equations may vary overthe population and with time.

For more details, see:Levin, M. W., S. D. Boyles, and J. Duthie. (2016) Demand profiling fordynamic traffic assignment by integrating departure time choice and tripdistribution. Computer-Aided Civil and Infrastructure Engineering 31, 86–99

DTA in practice Preparing Input Data

Page 18: Practical issues with DTA · DTA in practice Preparing Input Data. Deciding which streets to include in the network is a balance of accuracy and computation time/data collection requirements

Uniform preferred arrival time

DTA in practice Preparing Input Data

Page 19: Practical issues with DTA · DTA in practice Preparing Input Data. Deciding which streets to include in the network is a balance of accuracy and computation time/data collection requirements

DTA in practice Preparing Input Data

Page 20: Practical issues with DTA · DTA in practice Preparing Input Data. Deciding which streets to include in the network is a balance of accuracy and computation time/data collection requirements

Normally distributed preferred arrival time

DTA in practice Preparing Input Data

Page 21: Practical issues with DTA · DTA in practice Preparing Input Data. Deciding which streets to include in the network is a balance of accuracy and computation time/data collection requirements

MULTISCALE MODELING

Page 22: Practical issues with DTA · DTA in practice Preparing Input Data. Deciding which streets to include in the network is a balance of accuracy and computation time/data collection requirements

Multiscale modeling aims to get the “best of both world,” so to speak.

A microsimulator provides detailed results on a small area; a regional modelgives more aggregate results on a larger area.

DTA in practice Multiscale modeling

Page 23: Practical issues with DTA · DTA in practice Preparing Input Data. Deciding which streets to include in the network is a balance of accuracy and computation time/data collection requirements

But how do two models communicate with each other?

DTA in practice Multiscale modeling

Page 24: Practical issues with DTA · DTA in practice Preparing Input Data. Deciding which streets to include in the network is a balance of accuracy and computation time/data collection requirements

In principle, information can flow from either model to the other.

A consistent solution to both models respects both directions.

DTA in practice Multiscale modeling

Page 25: Practical issues with DTA · DTA in practice Preparing Input Data. Deciding which streets to include in the network is a balance of accuracy and computation time/data collection requirements

The main focus is usually on the boundary conditions, translating onemodels outputs to anothers inputs.

Solve for equilibrium on the regional model; see which vehicles enter thesubarea, and use those as the path flows for microsimulation.

DTA in practice Multiscale modeling

Page 26: Practical issues with DTA · DTA in practice Preparing Input Data. Deciding which streets to include in the network is a balance of accuracy and computation time/data collection requirements

In practice, this usually involves an ad hoc fitting-together and sequentialsolution.

Can we do better?

DTA in practice Multiscale modeling

Page 27: Practical issues with DTA · DTA in practice Preparing Input Data. Deciding which streets to include in the network is a balance of accuracy and computation time/data collection requirements

How large should the subarea be?This question was studied for two “nested” DTA models in the Austin area.

(Bringardner, Gemar, Machemehl, Boyles, 2014–15)DTA in practice Multiscale modeling

Page 28: Practical issues with DTA · DTA in practice Preparing Input Data. Deciding which streets to include in the network is a balance of accuracy and computation time/data collection requirements

These analyses gave recommendations about the subarea “radius” in termsof the number of affected links, and the severity of the capacity reduction.

DTA in practice Multiscale modeling

Page 29: Practical issues with DTA · DTA in practice Preparing Input Data. Deciding which streets to include in the network is a balance of accuracy and computation time/data collection requirements

Or is the “how large” question a red herring?

Downtown subnetwork

The real question is where the interactions lie, and how large they are.

DTA in practice Multiscale modeling

Page 30: Practical issues with DTA · DTA in practice Preparing Input Data. Deciding which streets to include in the network is a balance of accuracy and computation time/data collection requirements

An emerging alternative is the use of “soft” boundaries, which blur thedistinction between the models.

10 12

6 75

213

8

4

9 13

14

11

1 4

10 12

6 7

11

The subarea model retains a simplified version of the regional network,rather than eliminating it entirely. Route choice and diversion can be mod-eled naturally.

DTA in practice Multiscale modeling

Page 31: Practical issues with DTA · DTA in practice Preparing Input Data. Deciding which streets to include in the network is a balance of accuracy and computation time/data collection requirements

ACCURACY ANDSTABILITY

Page 32: Practical issues with DTA · DTA in practice Preparing Input Data. Deciding which streets to include in the network is a balance of accuracy and computation time/data collection requirements

Multiscale models highlight the question of model stability: how do modeloutputs change with inputs. Ideally, a model is not overly sensitive tohaving exactly the right input parameters.

In reality, this has been relevant all along!

DTA in practice Accuracy and stability

Page 33: Practical issues with DTA · DTA in practice Preparing Input Data. Deciding which streets to include in the network is a balance of accuracy and computation time/data collection requirements

I’m starting with a simpler setting, with two equally-tractable networkloading models. The objective is to predict the steady-state flow rates onlinks in one of two ways:

Spillback: If a link’s outflow is restricted, its steady-state inflow will besimilarly restricted.

No spillback: Restrictions to a link’s outflow are not transmitted to itsinflow.

Clearly, the spillback model is more realistic, and will be treated as“ground truth.” However, spillback can introduce discontinuities into flowmodels, so small input errors can potentially propagate into much largeroutput errors.

DTA in practice Accuracy and stability

Page 34: Practical issues with DTA · DTA in practice Preparing Input Data. Deciding which streets to include in the network is a balance of accuracy and computation time/data collection requirements

Q11

Q2

p

p and Q2 are model parameters, the objective is to estimate the flow Q1.

DTA in practice Accuracy and stability

Page 35: Practical issues with DTA · DTA in practice Preparing Input Data. Deciding which streets to include in the network is a balance of accuracy and computation time/data collection requirements

Standard merge and diverge equations apply

At the merge, in highly congested conditions flow is allocatedproportionate to capacity, if the sending flow from an approach is less thanthis the other approach can increase its flow.

The diverge respects the first-in, first-out principle, flows waiting to exitthe freweay will obstruct thru traffic.

In a spillback model, the steady-state inflow rate to the onramp cannotexceeds its outflow rate.

DTA in practice Accuracy and stability

Page 36: Practical issues with DTA · DTA in practice Preparing Input Data. Deciding which streets to include in the network is a balance of accuracy and computation time/data collection requirements

This example is small enough that it can be solved exactly.

1/2

1 - p

10

1

p

Q2 No spillback

0

p

Q2 Spillback

1/2 1

1/2

2/3

11/3

1 - p(1-p)/(2p)

(1-p)/3p (*)

(1-p)/(2p)(1-p)(1-Q2)/p (*)

If we don’t know p and Q2 exactly, which model gives better results?

DTA in practice Accuracy and stability

Page 37: Practical issues with DTA · DTA in practice Preparing Input Data. Deciding which streets to include in the network is a balance of accuracy and computation time/data collection requirements

For a given “true” value of of p and Q2, perform the following:

Generate n sampled values of Q2 and p, using independent normaldistributions, with means p̂ and Q̂2, and given standard deviation.

For each sample, εNS and εS are the absolute errors of theno-spillback and spillback models.

Calculate the additional expected error in the no-spillback model:δ = E [εNS − εS ], and its standard deviation s.

Calculate the t score: t = δ/(s/√n)

DTA in practice Accuracy and stability

Page 38: Practical issues with DTA · DTA in practice Preparing Input Data. Deciding which streets to include in the network is a balance of accuracy and computation time/data collection requirements

If t is greater than a positive critical value, we can conclude theno-spillback model has higher error.

If t is less than a negative critical value, the spillback model has highererror.

Otherwise that there is no significant difference between the models interms of error.

DTA in practice Accuracy and stability

Page 39: Practical issues with DTA · DTA in practice Preparing Input Data. Deciding which streets to include in the network is a balance of accuracy and computation time/data collection requirements

400 true values were chosen, uniformly distributed in [0, 1]2.

2500 samples were run for each case.

DTA in practice Accuracy and stability

Page 40: Practical issues with DTA · DTA in practice Preparing Input Data. Deciding which streets to include in the network is a balance of accuracy and computation time/data collection requirements

10

1

p

Q2 Low error (sd = 0.01)

S S S S S S = S S S S S S S S S S S S SS S S S S S = S S S S S S S S S S S S SS S S S S S = S S S S S S S S S S S S SS S S S S S = S S S S S S S S S S S S SS S S S S S = S S S S S S S S S S S S SS S S S S S = S S S S S S S S S S S S SS S S S S S = S S S S S S S S S S S S SS S S S S S = N S S S S S S S S S S S SS S S S S S S = N S S S S S S S S S S SS S S S S S S S = N S S S S S S S S S SS S S S S S S S S = N N N N N N N N = SS S S S S S S S S S S S S S S S S S S SS S S S S S S S S S S S S S S S S S S SS S S S S S S S S S S S S S S S S S S SS S S S S S S S S S S S S S S S S S S SS S S S S S S S S S S S S S S S S S S SS S S S S S S S S S S S S S S S S S S SS S S S S S S S S S S S S S S S S S S SS S S S S S S S S S S S S S S S S S S SS S S S S S S S S S S S S S S S S S S S

10

1

p

Q2 Moderate error (sd = 0.1)

= = N N N N N N N S S S S S S S S S S S= = N N N N N N N S S S S S S S S S S S= = N N N N N N N S S S S S S S S S S S= = N N N N N N N S S S S S S S S S S S= = N N N N N N N S S S S S S S S S S S= = N N N N N N N S S S S S S S S S S S= = N N N N N N N S S S S S S S S S S S= = N N N N N N N S S S S S S S S S S S= = = N N N N N N N = S S S S S S S S S= = = N N N N N N N N = S S S S S S S S= = = N N N N N N N N N N = S S S S S S= = = = N N N N N N N N = = S S S S S S= = = = = N N N N N N N = = S S S S S SS = = = = N N N N N N N = = = S S S S SS S = = = = = N N N N N = = = = = S S SS S S = = = = = N N N N = = = = = = = =S S S S S S S S = = = = = = = = = = = =S S S S S S S S S S = = = = = = = = = =S S S S S S S S S S S S S S S S S S S SS S S S S S S S S S S S S S S S S S S S

10

p

Q2 Large error (sd = 0.25)

N N N N N N N N N N S S S S S S S S S SN N N N N N N N N N S S S S S S S S S SN N N N N N N N N N S S S S S S S S S SN N N N N N N N N N S S S S S S S S S SN N N N N N N N N N S S S S S S S S S SN N N N N N N N N N S S S S S S S S S SN N N N N N N N N N S S S S S S S S S SN N N N N N N N N N S S S S S S S S S SN N N N N N N N N N N S S S S S S S S SN N N N N N N N N N N N S S S S S S S SN N N N N N N N N N N N = S S S S S S SN N N N N N N N N N N N = S S S S S S SN N N N N N N N N N N N = S S S S S S SN N N N N N N N N N N N = S S S S S S SN N N N N N N N N N N N = S S S S S S SN N N N N N N N N N N N = S S S S S S SN N N N N N N N N N N N = S S S S S S SN N N N N N N N N N N N = = S S S S S SN N N N N N N N N N N N = = S S S S S S= N N N N N N N N N N N N = = S S S S S

Average positive t score: +87.4, average negative t score: −13.9.

DTA in practice Accuracy and stability