-
Notifications
You must be signed in to change notification settings - Fork 5
PeerReviewQuestions
e-lo edited this page Mar 17, 2015
·
1 revision
- Are the strategies that we've already employed appropriate?
- Are there any tricks or strategies that we should be trying that we haven't yet?
- How should we prioritize our effort for calibration moving forward?
- Does our data collection methodology and associated results make sense?
- Are there other observed data that we should be trying to collect?
- We have a generalized cost function that we've basically inferred, but how do we get a better one both now, and after we get observed routes from 2012 California Household Travel Survey
- Do the DTA settings that we have chosen make sense?
- How sensitive should the model be to these settings?
- What others should we test out and why?
- Are there any validation standards for a large-scale DTA? When is ‘enough’?
- How should we measure the "stability" of the results? What should we be looking at other than relative gap?
- Similarly, how should we test the model's sensitivity to changes in: network geometry; signal operations; other?
- How does one validate to conflicting data?
- Is there a way to deal with movement-specific yellow time in signal phases where there is another movement that has continuing green time?
- Transit lanes that allow specific movements in them (i.e. right turns)
- How should we prioritize the strategies listed in the integration memo both for "Demand Information for DTA" and "DTA Information for Demand"
- What thoughts or cautions would you give to simultaniously pursuing person-based dynamic transit assignment a la FastTrips?
- What (if anything) about this process/project would be useful for other agencies to learn and hear about? In what format?
- What parts of the code base that we have developed (if any) would be useful to operationalize for others?
- Are there any research or application questions that it seems like we should be able to answer with this project?