TSSC Simulation Subcommittee Meeting July 22, 2007 San Jose, CA

Subcommittee Goal Select topics that are of interest to members and share them Let’s do braining storming to define “vision” and “objectives”

Past Presentations Hardware in the loop simulation (HILS)  Status of CID  Success stories Software in the loop simulation (HILS)  VISSIM + ASC/3C Simulation model calibration & validation  Handbook  Workshop material CICAS Evaluation Test-Bed

Suggested Activities Guidance on how to use simulation Driving behavior using NGSIM data Online resources (server from TSSC website) Development of better user interface Animation of internal controller logics API documentation Oversaturated conditions

Suggested Activities (Cont’d) Driving simulator + Microscopic simulation HCQS, NCHRP 3-85 working papers on HCM limitations and use of simulation Contact controller vendors for SILS capabilities

Subcommittee Activities: Volunteers Updated HILS bibliographies (Aleksandar Stevanovic) Simulation Guidance Document (Hong Li, Lin Zhang & Md. S. Chowdhury ) Driving behavior using NGSIM data (Md. S. Chowdhury & Lin Zhang) Traffic Simulation Modeling Archives

Traffic Simulation Modeling Archive

VISSIM API: COM v. DLL Both COM and DLL provide application programming interface (API) Evaluated impacts in simulation run times  Use runContinuous() to start VISSIM and use embedded DLL (e.g., driver module)  Use runSingleStep() to implement any special logics while VISSIM pauses  The method of getting the vehicles (COM vs. DLL)  Whether VISSIM visualization is enabled.

Simulation Speed by Getting Vehicle Info.

COM v. DLL COM with External Driver Module is general faster than COM only option 100 cars in the system, about 8.5 times faster 500 cars, about 3.2 times faster 1000 cars, about 2.3 times faster cars, about 1.3 times faster

Impact of Visualization during Simulation About 2.5 faster without visualizations