Pengaturan Perilaku Berkendara dengan PTV Vissim - Part 5: Signal Control dan Driving Behavior

Summary

The video demonstrates how to configure traffic signals and driving behavior in a PTV Vissim simulation, then check that the model runs and resembles observed local traffic.

Run and Inspect the Simulation

• Start the simulation with the Play control.
• Switch between 2D and 3D views to inspect the network and vehicle movements.
• Use the animation to check signal colors and vehicle behavior.
• If the simulation fails, inspect the signal control configuration and error log. The instructor identifies incorrect signal-control settings as a common cause.
• Check the network geometry as well. Disconnected or incorrectly positioned links can cause visual or modeling problems.

Configure Signal Control

The instructor uses signal timing data from a field survey to create signal groups, intergreen periods, and signal programs.

Four-Approach Intersection

• Create four signal groups and assign the relevant signal heads to them.
• Set each group’s sequence to red, green, amber.
• Enter the surveyed green times: 35, 40, 30, and 45 seconds.
• Use 5-second intergreen periods between stages.
• The stated cycle is 170 seconds, based on 150 seconds of green time plus 20 seconds of intergreen time.
• Enter the stages in the signal program using cumulative times, then check that the signal heads are assigned to the intended groups.

Three-Stage Intersection

• Configure the three required signal groups and remove any unnecessary group.
• Use a 100-second cycle, with green times of 40, 25, and 20 seconds and 5-second intergreen periods.
• Assign the signal heads to the correct groups and test the program in the simulation.

These examples emphasize translating surveyed timings into Vissim’s signal program and verifying the result by running the model.

Create and Assign a Local Driving-Behavior Profile

Rather than changing Vissim’s default behavior settings, the instructor recommends creating a separate profile—named “Metropolitan” in the demonstration—and assigning it to the relevant links.

The demonstrated adjustments, based on a journal used as a reference, include:

• Free-flow lateral position: Change from staying in the middle of the lane to allowing vehicles to travel at any lateral position.
• Overtaking: Enable overtaking on the left and right. The default setting shown had overtaking disabled.
• Stopped following distance: Reduce the distance at 0 km/h from 1 m to 0.2 m.
• Distance while moving: Reduce the distance at 50 km/h from 1 m to 0.4 m.
• Following-model parameters: Adjust the average standstill distance and safety-distance parameters. The instructor gives values around 0.6 m for some settings and says to change a multiplier from 3 to 1. These values should be checked against the reference settings because parts of the subtitles are unclear.
• Look-ahead distance: The example discusses reducing the default 250 m to 100 m as a possible overtaking-related adjustment.
• Waiting time before a vehicle is removed from a blocked connector: The example mentions 60 seconds and says this can be increased if needed.

The instructor associates Wiedemann 74 with urban driving and Wiedemann 99 with driving on routes outside urban areas.

Assign the Profile

1. Add a new driving-behavior entry in the database and name it.
2. Edit the new profile’s parameters rather than changing the default profile.
3. Add the profile as a link behavior type.
4. Select the intended links—using Shift-selection for a range of links if appropriate—and assign the new profile.
5. Save and rerun the simulation to confirm that the behavior has changed.

Calibrate and Validate Against Local Conditions

The instructor stresses that the journal settings are a starting reference, not a universal set of values. Driving behavior varies by location, so parameters should be calibrated and validated against field observations. Compare the model’s output with survey results and adjust parameters where the results do not match.

The lecture also highlights two network-setup checks:

• Scale and distance: Confirm that the network reflects real-world distances. One example had a link of about 83 m where the intended distance was around 400 m.
• Overtaking geometry: Check that links and lanes are positioned and connected correctly. In the demonstrated case, the instructor suggests adjusting lateral offsets to roughly 2 m, then recalculating the network geometry.

Speakers and Sources

• Instructor: The subtitle opening appears to identify the speaker as Des Mertiasari, though the name is not fully clear in the auto-generated text.
• Participants named in the subtitles: Berliana, Pangeran Langit, Muhammad Wipterian, Saifullah, and Humairah. Other names are mentioned during the session, but it is unclear whether they speak.
• Reference source discussed: A journal on microsimulation of mixed traffic at a signalized intersection, used as a benchmark for driving-behavior settings. The instructor also refers to the Wiedemann 1974 and 1999 models.