310 likes | 453 Views
MN IDS Project Progress Update. MN IDS Update. Progress to date Test Intersection Sensor evaluation results Benefit:cost efforts progress Human Factors (Max) Rural Intersection Pooled Fund Study (Max) Upcoming work Intersection on line Simulator Studies MUTCD approval
E N D
MN IDS Update Progress to date • Test Intersection • Sensor evaluation results • Benefit:cost efforts progress • Human Factors (Max) • Rural Intersection Pooled Fund Study (Max) Upcoming work • Intersection on line • Simulator Studies • MUTCD approval • Benefit:cost analyses
MN IDS Test Intersection • Design Completed 15 Jan 2004 • Design review with Mn/DOT traffic, geometric, district, and ESS engineers • Good advice • Recommendations for sensor mounts • Nothing in the median lasts • Revised cross-roads surveillance • Laser sensors to Visible Light/IR Cameras • Explored opportunity to cooperate on construction • Month of negotiations, didn’t work out. • ROC 52 • ESS
Present Instrumentation • Mainline • Vehicle speed, position, lane of travel (Radar) • 2000 foot coverage before Xroads (Radar) • 800 foot coverage beyond (Radar) • 53’x36’ coverage at camera (IR/Visible) • Hardwired and Wireless Communication • Cost and performance trade-off analyses • Crossroads • Vehicle type (Radar and laser based) • Vehicle approach speed (adapt VA technology at a later date?) • Trajectory leaving minor road • Right turn (camera + radar) • Straight through (camera) • Left turn (camera + radar)
MN Test Intersection-Mainline Sensors Camera Suite (for evaluation) Radar to track vehicles past crossroads (primarily for minor road trajectory recording) Radar Camera FOV 53’x36’
Mainline Highlights • Camera / mast provides independent means to verify • Radar performance • Camera performance • Gap tracker performance • Emerging technologies • May or may not be part of final system • Benefit:cost analysis • Poor weather capability of vision based systems
Laser / Radar Sensor Mount • Approved by Mn/DOT Right-of-Way Engineer • 350 Crash worthy • Will include break-away conduit and connector • Will include reflector at top of 3# U channel
C4 FOV C3 FOV Intersection Crossroads-Vehicle Trajectory Cameras at intersection corners capture the trajectory of vehicles entering intersection from minor roads. Mn/DOT advised that median-based sensors won’t live. (Crashed out).
Camera Based Validation Tracking on this side No tracking on this side
Classification Capable T-300 Radar Horizontal Laser Scanner Classification Capable T-300 Radar Vertical Laser Scanner Intersection Crossroads – Vehicle Classification
R/WIS Data from Intersection Mn/DOT updates at 10 Minute intervals. Data collected every 10 minutes
Information Available from Intersection • Distribution of gaps accepted by drivers • for right turns • for left turns • for crossing intersection (see next page) Cross-correlated with • Vehicle type / size • Driver age (macroscopic level, limited basis initially) • Driver gender (limited basis initially) • Weather effects (R/WIS 0.9 Mile away), with in-road sensors (collecting data already)
Information Available from Intersection (cont’d) • Maneuvers executed by drivers from minor road • Left turn in one stage or two? • Variation in left and right gaps accepted for each maneuver type • Cross-correlation with vehicle type • Crossing intersection in one stage or two? • Variation in left and right gaps accepted for each maneuver type • Cross-correlation with vehicle type
Information Available from Intersection (cont’d) • Response of mainline traffic • Speed adjustment if stationary vehicle on minor road • Do mainline drivers adjust speed if a vehicle is spotted on minor road? • Will mainline drivers move to left lane (when possible) to provide a lane for the minor road traffic? • Reaction of drivers on major road if too small gap is accepted • Braking? • Lane change? • Other?
Intersection Build Details • Hardware • Cameras, radar, lasers, camera masts, radar stations, etc., ordered or out on bid. • iDAQ (intersection Data AcQuisition) computers built • Software • Camera based vehicle tracking software under continued development (20 FPS vs. existing 5 FPS for improved tracking and robustness) • Wireless system integrity software scaled from Demo 2003 version
Intersection Build Details • Construction • Bid to purchasing 12 March 2004 • UMN VP signature expected 16 March 2004 • Bids due back 2 weeks after bid is published. • 04 June 2004 end date specified • Cold cold winter, need to avoid frozen ground trenching costs.
MUTCD Approval Process • Howard Preston contract, phase II executed. • Task Highlights which follow Mn/MUTCD Section 1A.10 • Documentation of the design process, from crash analysis to simulator study results • Patent search • Development of acceptable research plan for the ensuing FOT • Data collection • MOE’s • Semi-annual progress reports to FHWA Office of Transportation Operations
Benefit Cost Analysis: Framework NPV: Net Present Value
Work complete/in progress Subtask C1: Identify relevant technologies, Review of Literature. Subtask C2: Develop Benefit Cost Framework. Subtask C3: Estimate Lifespan of Technology. Subtask C4: Estimate Costs of technology. Subtask C5: Estimate Benefits of Countermeasures. Subtask C6: Lifecycle Analysis. Work yet to be undertaken Subtask C7: Recommend Countermeasures. Subtask C8: Analyze Inter-technology Effects. Subtask C9: Determine Performance Metrics. Subtask C10: Develop cost:performance models. Subtask 11: Analyze Synergies. Subtask 12: Optimize Counter-measure Combination. Benefit Cost Analysis: Status
Schedule Adherence TODAY Intersection Brought On-line Human Factors Simulator DII Testing Begins Final Report Preparation Begins