Reference Manual Cube Dynasim 6.11

7/26/2019 Reference Manual Cube Dynasim 6.11

1/481

Version 6


2/481


3/481

3 D Y N A S I M - RE F E R E N C E M A N U A L

WHATSNEWIN

VERSION6

Whats new in version 6

Whats new in CubeDynasim:

Changes in Files and directories, page 38.

The ability to share categories between different projects with the Categories database, page 52.

The Signal scenario graphic interface has been added.

The ability to establish a complete connection between the client and the Traffic Control System Uto-

pia, page 399.

Import text file for programing classic controller (see Import signal programing, page 316).

New types of flow scenarios:

Empty scenario, page 113,

Aggregate, page 149.

New types of counts:

Traffic count percentage, page 127,

Traffic count in a database, page 129.

New editing features for counts:

Splitting a traffic count, page 133,

Import the values of traffic counts from a text file, page 134.

Reduce computation time and minimize file size while compiling flow boxes based on bitmaps.

For assignment flow, or sub network assignment, it is possible to modify path flow estimation before

assignment.

Transit stops, page 272now have a randomized probability that the driver will stop.

New editing features for Timetable, page 284.

New panel for simulation scenario allowing to separate, for the same simulation scenario, the calcula-

tion of the demand from the replication, from the compilation of the reports. The same flow scenario

shared by different simulation scenarios will be computed only once. Moreover, the Simulation module

in Compute scenario mode, page 408allows multiple selection of scenarios to be computed in parallel


4/481


to the demands, the replications and the reports (in one click).

New keyboards shortcuts for displaying and editing simulations objects.

The functionalities of the Animation in the network edit area, page 24have been enhanced so that the

user can select an existing simulation scenario and directly display all types of error messages for this

scenario.

Parking simulation, the update lot can simulate drivers leaving the parking because they are tired oflooking for a free spot.

Rail simulation, new continuous sideways, allowing multiple hooking-unhooking maneuvers.


5/481


Whats new in version 6 . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Chapter 1 Presentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Projects and simulation models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Flow scenarios. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11Network scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Signal scenarios. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Public transport scenarios. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12

User interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Edit modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13

Menu bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Button bars. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Network edit area. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Status areas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Animation in the network edit area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .24

Module entry window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .27

Object entry windows. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .28

Name field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Integer numeric value field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

Color field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

Single-choice list field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .32

Multiple-choice list field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .33

Chapter 2 Managing projects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Project management window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

Files and directories. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

Installing CubeDynasim . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .38Creating a project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

Deleting a project. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .39

Modifying a project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

Adding a simulation scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

Deleting a simulation scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

Chapter 3 Vehicle categories. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Managing categories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

Graphic representations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

Editing 2D representations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44Editing 3D representations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Movement capacities. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

Categories database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

Saving a category. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .52

Import a category. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

Chapter 4 Background map. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Maps Management window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

Background map in DXF format. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

Background map in bitmap format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57Tiling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

Map Management window for bitmap files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58


6/481


Chapter 5 Layers and network scenarios . . . . . . . . . . . . . . . . . . . . 61

Using layers and network scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

Managing layers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

Network scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

Chapter 6 Network origins & destinations . . . . . . . . . . . . . . . . . . . . 67

Origins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

Stages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

Example of modeling a network origin. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

Destinations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

Zones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

Representation of a zone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

Creating a zone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

Chapter 7 Road network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79Vehicle network. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80

Handles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80

Trajectories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

Creating the vehicle network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

Editing the handles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

Editing trajectories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86

Speed distributions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92

Creating a Percentage distribution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

Creating a Maximum Speed distribution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

Creating a Category distribution. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .93

Pedestrian crossings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95Representation of a pedestrian crossing in the edit area. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

Creating a pedestrian crossing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .97

Editing and deleting a pedestrian crossing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99

Underpass object and 3D tile. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100

Underpasses. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .100

Representation of an underpass object in the edit area. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .100

Creating an underpass object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101

3D tile. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .102

Modeling the road network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104

Modeling weaving lanes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104

Modeling an increased/reduced number of lanes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105

Modeling a traffic circle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105

Chapter 8 Flow module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109

Flow scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110

Defining a flow scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110

Empty scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113

Generator scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114

The Generator scenario edit window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115

Subnetwork scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120

The links/nodes network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122

Export-Import scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124Edit a flow scenario of type Export-Import . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124

Format of the path-flow files to be imported . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125


7/481


Traffic counts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126

Traffic count direct entry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .126

Traffic count percentage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127

Traffic count in a database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129

Adding a traffic count . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131

Editing a traffic count . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132

Splitting a traffic count . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133Import the values of traffic counts from a text file. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134

Estimation scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136

Principle. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137

Examine the results of the estimation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138

Analyze the results of the flow calculation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .139

Assignment scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141

Principle. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142

Create an Assignment flow scenario.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143

Examine the result of the assignment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144

Subnetwork Assignment scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145

Principle. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146

Examine the result of the subnetwork assignment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148Aggregate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149

Paths: visualization and analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152

Flow box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .152

Paths on trajectory. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154

Scenario comparison . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155

Chapter 9 Paths . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157

Links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158

Speed link. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .159

Split link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160Split link by PCE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .165

Prohibitors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168

The different types of prohibitors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .168

Invalid paths. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168

Prohibitor field. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171

MP prohibitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173

Creating a MP prohibitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173

Editing a MP prohibitor. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173

Lane changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174

Insertion gaps. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175

Behavior associated with lane satisfaction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176

Lane change distance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182Creating a lane change distribution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182

Car-following rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184

Lane change distributions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185

Overview of lane change distributions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185

Lane Change Distributions window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189

Lane change marker . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190

MP Lane Change Marker . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192

The break continuity object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192

VMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .193

Chapter 10 Managing conflicting trajectories . . . . . . . . . . . . . . . . . 197Gap time distributions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199


8/481


Creating a gap time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .199

Editing gap time distribution parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200

Traffic circle insertion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .200

Left turn across a flow with priority . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201

Stop. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .201

Stop line. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202

Representation of the stop line in the edit area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .203Creating a stop line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .204

Editing a stop line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204

Adding a condition on a stop line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205

Yield . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206

The elements of a yield. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .206

Creating a yield . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .209

Editing a yield . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209

Use of the yield. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211

Yield-on-green. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214

Representation of a YOG in the edit area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214

Creating a YOG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215

Editing a YOG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215Stop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217

Representation of the stop in the edit area. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217

Creating a stop. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .218

Editing a stop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218

Strict stop. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219

Representation of a strict stop in the edit area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219

Creating a strict stop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220

Editing a strict stop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .220

Example of how to use a strict stop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221

Stop-if-stop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224

Representation of a stop-if-stop in the edit area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224

Creating a stop-if-stop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225Editing a stop-if-stop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .225

Example of how to use a stop-if-stop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226

Stop-on-red . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228

Representation of an SOR in the edit area. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .228

Creating an SOR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229

Editing an SOR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229

Example of how to use the SOR. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 230

Chapter 11 Data collectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233

What to measure, and how to measure it. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234

Flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236

Deficit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236

Number of vehicles present . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237

Delay . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237

Stop. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .238

Number of stops per vehicle. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238

Stop state duration per vehicle. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .239

Travel time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239

Travel speed. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240

Flow by lane. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .240

Queue. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240

Inter-vehicle times . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241

Occupancy rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241

Instant speed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242

Green signal duration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242


9/481


Red state duration for a signal. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .243

Signal line crossing duration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243

Vehicle scheduling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244

Storage of the values measured . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245

Data model. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245

SQL queries, optimization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .248

Installing an ODBC driver. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249

Extracting data using OpenOfficeTM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .252

Extracting data using ExcelTM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .254

Tables generated at the end of the simulation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 256

Representation of data collectors and editing them. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 262

Data collector representation and associated elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 262

Creating a data collector. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 264

Editing a data collectors geometry. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .264

The data collector entry window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265

Creating/Editing/Deleting a group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265

Editing/Deleting a data collector. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .267

Editing the criteria measured for a group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 269

Chapter 12 Public transport module . . . . . . . . . . . . . . . . . . . . . . . . 271

Stop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 272

Transit stops. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .272

Tolls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .274

Incidents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 275

Terminus. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .276

Public transport scenarios. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .277

Public transport module management window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279

Creating/Editing/Deleting a PT scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279

Creating/Editing/Deleting a PT line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .280Timetable. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 284

Creating a timetable. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 284

Edit the schedule of a timetable. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 285

Timetable assignment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 286

Creating a timetable assignment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .287

Chapter 13 Signals module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 289

Signals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 290

Signals with two states. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .290

Signals with three states . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 290

Creating and editing a signal. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 291

Representation of signals in the edit area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .292

Creating a signal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .293

Editing a signal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 294

Detectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 295

Multimarker detectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .295

Single-marker detectors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 299

Controllers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 305

Representation of controllers in the edit area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .305

Creating a controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .306

Editing a controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 306

Signal scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 308

Header . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .308

Programing controllers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 308

Editing signal scenarios in CubeDynasim. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .309


10/481


Classic Programing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 313

Edit states of the signals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 314

Rules between detectors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 317

Operations that modify the diagram during a simulation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .318

Edit actuated signal operation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 322

Examples of signal programs with CubeDynasim. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .326

Files generated. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 335

Chapter 14 Socket programming. . . . . . . . . . . . . . . . . . . . . . . . . . . 337

DynasimServer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 338

DynasimServer on the server side (external program) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .338

DynasimServer on the client side (micro simulator) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .341

Editing and naming objects in CubeDynasim . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .342

Defining the client in CubeDynasim. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .344

Simulation in client mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 344

The Socket library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 345

Prerequisites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .345General architecture of the program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 349

Compile and launch the server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 355

Managing scenarios. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .356

Generate a log file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 358

Classes and methods of the Socket library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 364

Controler . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .365

Phase . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .366

Capteur . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 367

QsOu_RegExpCapteur. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 368

QsEt_RegExpCapteur . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 369

QsXor_RegExpCapteur . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 370

QsNo_RegExpCapteur. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .370

QsAcquitte_RegExpCapteur . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 371

QsDAGeLt_RegExpCapteur . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 371

QsDALt_RegExpCapteur. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .372

QsDALe_RegExpCapteur . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 373

QsAttGEattMax_RegExpCapteur . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 373

QsDaMax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .374

NextPhase . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 375

NextPhaseAtTime . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 377

PointRepos . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 379

Adaptativ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .380

EscamotLigne. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 381

Switch. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .384

ChgeEtat . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 385PC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 386

Complete example of programming with the Socket library . . . . . . . . . . . . . . . . . . . . . . . . . . . .387

Utopia . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 399

Utopia controllers (CubeDynasim) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 399

Editing and naming objects in CubeDynasim . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .400

Defining the CubeDynasimUTOPIA client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .400

Simulation in client mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 401

Chapter 15 Simulation module . . . . . . . . . . . . . . . . . . . . . . . . . . . . 403

Simulation module in Edit scenario mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 405Add a simulation scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 406

Delete a simulation scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 407


11/481


Edit a simulation scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 407

Simulation module in Compute scenario mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 408

Compute the Flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .408

Calculate the simulation (in fact the replications). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 409

Generate report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .410

Stop the replications during the calculation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 411

Modify the autoblock conditions without replicating . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 411Export the simulation scenarios. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 411

Simulation module in Results mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 413

Comment a replication. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 414

Simulate a replication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 414

Delete an animation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .414

Animate a simulation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 414

Consult the messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 414

Simulation module in Draw mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 421

Chapter 16 Parking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 423

Model development and the simulation of parking. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 424

Parking Distribution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 427

Attractor. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 429

Create or edit an attractor. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 430

Aisle. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 431

The parking lot objects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 431

Create, edit a parking lot object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 433

Link an aisle to the road network. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 434

Clone an aisle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 436

Parking Lots . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 438

Parking Lot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 438

Assign Lot. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .440Update Lot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 443

Count display. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 447

Distribution of lane changing behavior in the parking lot. . . . . . . . . . . . . . . . . . . . . . . . . 448

Modify the appearance of the vehicles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 450

Vehicles present at the beginning of the simulation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 450

Vehicles parks at a certain parking lot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 450

Chapter 17 Animator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 451

Controller. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 453

Animation menu bar. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .453Controller Toolbar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 453

Animation cursor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 454

View. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 455

2D view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 455

3D view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 459

View of a controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .462

Saving the animator configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 464

Context. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 464

Markers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .464

Playing the animation as a continuous loop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 466


12/481


Chapter 18 DynasimViews . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 467

View scenarios window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 468

Scenario display area. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .468

Command area. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .468

View results window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 470

Group list area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 470Edit area. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .471

Command area. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .471

Graph . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 472

Chapter 19 License and transfer codes. . . . . . . . . . . . . . . . . . . . . . 475

License code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 477

Export code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 478


13/481


1

PRESENTATION

C H A P T E R

Presentation

CubeDynasim is a software application for modeling and simulating the operation of transportation infra-

structures including rail and waterways. CubeDynasimincludes a graphic editor, a simulation engineand

tools for viewing and analyzing simulation results. These three components are directly accessible via the

CubeDynasiminterface.

CubeDynasims graphic editor enables the user to define all aspects of a simulation model; with it, the user

can position objects on a background and define these objects using data entry windows.

Licenses and transfers can be managed via the License and transfer codes, page 475menu.

The simulation engine is microscopic, stochastic and event-driven. Microscopic simulation helps to con-

sider each moving vehicle according to its behavior and immediate environment. The simulation model is

stochastic because the parameter values (for example, a behavioral parameter) are obtained from statistical

distributions. During the simulated time period, an event (for example, a traffic signal change) can impact a

vehicles motion.

There are different tools for viewing and analyzing simulation results:

1. The animator, which reproduces vehicle movements calculated by the simulation engine as

graphic animations in two or three dimensions.

2. The grapher, which displays the statistical results as curves according to criteria measured during

the simulation, such as the travel time or the flow.

3. Standard tables, obtained from criteria measurements taken during the simulation. They give a

summary view of how the various simulated developments work.

4. Flow illustrations, obtained from the quantification of the demand.

5. Signal programs, obtained via the signals module.


14/481


This chapter breaks down into two parts:

Projects and simulation models, page 11which gives a definition of the terminology and method-

ology implemented to develop simulation models in the field of highway infrastructure operation,

User interface, page 13 which describes the main components of the CubeDynasim human-

machine interface, giving access to the simulators various functions.


15/481


P R O J E C T S A N D S I M U L A T I O N M O D E L S

PRESENTATION

Projects and simulation models

A simulation modelreproduces the operation of a development. This model is characterized by parameters

referenced in one of the following four categories: Flows, Networks, Signals and Public Transport (PT). The

different parameters are grouped into scenarios, whereby a scenario usually corresponds to a hypothesis to be

tested. A simulation scenariocomprises Flow scenarios, page 110, Network scenarios, page 65, pos-

sible Signal scenarios, page 308and Public transport module, page 271scenarios. A projectcom-

piles a set of simulation scenarios that "share" a certain number of parameters (see Projects and simulation

models, page 11).

Flow scenarios

Flow-type parameters quantify the demand of vehicles wanting to use the modeled development. The

CubeDynasimsimulator can distinguish three types of quantification in terms of the demand:

Quantification of OD-type vehicles:

origin-destination matrix, depending on the vehicle category and the time sample,

OR an estimation of the paths that satisfy a certain number of directional or ad hoc traffic counts,

OR an assignment of an origin-destination matrix resulting from an estimation on a new network,

OR a set of paths defined by a third party software solution,

Quantification by direct movement, applied to pedestrian crossings,

Quantification by frequency, applied to the definition of public transport lines.

In CubeDynasim, a flow basically refers to the quantification of the demand. You can define different

demand quantification hypotheses. A flow scenariocorresponds to each of these hypotheses. The flow sce-

nario-based approach makes it easier to study the operation of the simulated development at morning or eve-

ning peak times, or even future forecasts.

A simulation scenario necessarily includes a flow scenario (see Flow scenarios, page 110).

Network scenarios

Network scenarios contain all the simulation objects that describe the trajectories taken by the developments

users. This includes the sequence of trajectories, the management of trajectory conflicts, and the positioning

of regulation elements such as signals, detectors, etc.

CubeDynasimuses layersto share a subset of simulation objects among two network scenarios. Simula-

tion objects are thus compiled in layers, and layers are in turn compiled in network scenarios. This techniquemakes it possible to reuse portions of the road network common to two different network scenarios.

It must be noted that the networks entry and exit points are common to all the network scenarios in a project.

The entry and exit points serve to establish a connection between the network scenarios, the flow scenarios,

and the public transport (PT) scenarios for the simulation.

The network scenario can be edited/viewed in either logicalor geometricmodes.

Geometric modecorresponds to a description of the simulation objects determined by a dimension and/or

physical coordinates. The editing of trajectories, trajectory conflicts, the location of traffic signals and detec-

tors, and the definition of data collectors are done in geometric mode.

Simulation objects without dimensions, i.e., trajectory sequences (links) and entry/exit points on the net-

work, are edited in logical mode.


16/481

P R O J E C T S A N D S I M U L A T I O N M O D E L S


A simulation scenario necessarily includes a network (see Network scenarios, page 65).

Signal scenarios

Signal scenarios are used to simulate different signal timing strategies. This consists in defining - for the sim-

ulation - the diagram of signals times and, if necessary, the actuated signal control. As with network scenar-ios, the signal scenario compiles a set of layers defining the signals to be considered.

A simulation scenario does not necessarily incorporate a signal scenario. The set of layers in the signal sce-

nario must be included in the set of layers in the network scenario of a simulation scenario (see Signal sce-

narios, page 308).

Public transport scenarios

The public transport scenario is used to quantify the demand according to a line-based logic. For each line

simulated, you define the points of origin and destination in the network, and a stop frequency or stop times.

A simulation scenario does not necessarily incorporate a public transport scenario (see Public transport mod-ule, page 271).


17/481


U S E R I N T E R F A C E

PRESENTATION

User interface

Simulation models are mainly edited in the main window. The main window contains the "tools" used to edit

and view a projects various simulation models. These tools are accessible according to the edit mode in use.

The section describes the following :

Edit modes, page 13,

Menu bar, page 14,

Button bars, page 15,

Network edit area, page 19,

Status areas, page 24,

Module entry window, page 27,

Animation in the network edit area, page 24,

Object entry windows, page 28,

Name field, page 29,

Integer numeric value field, page 31,

Color field, page 31,

Single-choice list field, page 32,

Multiple-choice list field, page 33,

Views, page 33.

Edit modes

There are three edit modes that affect the main windows appearance:

1. Geometric modeis used to edit elements determined by geometric positioning (trajectories, pri-

ority rules, etc.), see the "Main CubeDynasim window in geometric mode" (see fig. 1, page 14).

2. Logical modeis used to name and identify the networks incoming and outgoing traffic, the con-

ditioned trajectory sequences, etc., see the "Main CubeDynasim window in logical mode" (see

fig. 2, page 14).

3. Rail modefor editing and model rail network.

The appearance of the main window in CubeDynasimis determined by the current mode. While the objects

differ from one mode to the other (simulation object bar), the general modules (tool bar and module bar) are

present in both modes.

Click the button on the tool bar to switch to logical mode. Click the button to switch CubeDynasim

to geometric mode.
http://-/?-http://-/?-http://-/?-http://-/?-


18/481



Menu bar

Located at the top of the CubeDynasimmain window, the main menu bar offers access to all the CubeDyna-

sim functions. Each menu contains commands and sub-menus. The menu bar has six menus : File, Edit,

Multilane,Distributions, Car-following rules,Report,Parking, ViewandHelp. Menus and their commands

do not change with the edit mode.

To select a menu command:

1. Click the desired menu to display its commands.

2. Click the desired command, or pressEscto quit select item mode.

Figure 1. Main CubeDynasimwindow in geometric mode

Figure 2. Main CubeDynasimwindow in logical mode

Modulebar

Menubar

Toolbar

Objectbar

Networkeditarea

Informationarea

Messagearea

Modulebar

Menubar

Toolbar

Objectbar

Networkeditarea

Informationarea

Messagearea
http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-


19/481



PRESENTATION

To select a sub-menu:

1. Select a command containing a sub-menu (indicated by a black arrow).

2. A sub-menu is displayed: click the desired sub-menu command, or press Esc to quit select sub-

menu mode.

Button bars

Button bars offer easy access to the commands used when editing the model. To display a tool-tip describing

the buttons function, rest the mouses cursor on the button.

The CubeDynasimmain window contains the following three button bars :

Toolbar, page 15,

Simulation object bar, page 17,

Module bar, page 18.

ToolbarThe "Toolbar" (see fig. 3, page 16)contains buttons used to modify the status of the Network edit area,

page 19, and to facilitate access to the functions used most frequently. The functions available are always the

same whatever the mode (logical or geometric) in use. They are activated by left-clicking the corresponding

button.
http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-


20/481



Quick selection to select and display Network scenarios, page 65

Quick selection to select the Flow scenarios, page 110.

Quick selectionto select one of the possible Signal scenarios, page 308.

Quick selection to select one of the possible Public transport scenarios,

page 277.

Button for shortcut simulation: Animation in the network edit area, page 24.

Switch to logical edit mode.

Switch to geometric edit mode.

Hide background map

The user can momentarily hide the background map to optimize the display rate, thus making it easier

to edit the model.

Edit mode(see Edit Object mode, page 20).

Pan mode (see Pan mode, page 24).

or Zoom mode(see Zoom mode, page 20).

Savethe model being edited. You can also save it via Menu bar, page 14, by selectingFile

> Save.

or Advanced zoom adjusts the zoom level to display all the elements in the network edit area.

There are three types of advanced zoom: Object zoom on all simulation objects ( ), Network

zoomon the simulation objects in the current network ( ), and Background Mapzoom on the ele-

ments in the background map ( ). These three types of advanced zoom must be distinguished in

order to solve the problem that occurs when updating a background map, which is defined in a new

marker. Here, the objects in the simulation model are no longer positioned on the background map.

You may have the impression that you have lost your changes, since the simulation model is no longerdisplayed. By switching from one advanced zoom mode to another, you will see that the position of

the objects in the simulation model and the background map no longer correspond.

By leaving the mouses cursor over the toolbars button for a few seconds, the advanced zoom

current status is displayed in a tool-tip.

To perform an advanced zoomdepending on this status, left-click the button.

To change the type of advanced zoom :

1. Left-click and hold the button.

2. When the sub-menu opens, move the mouses cursor to the appropriate sub-item.

Figure 3. Toolbar
http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-


21/481



PRESENTATION

Simulation object bar

The simulation object bar contains buttons to change the edit area toCreate Object mode, page 19. The

simulation object bars appearance changes depending on whether you are in logical or geometric mode see

The simulation object bar in geometric mode, page 17 and see Simulation object bar in logical mode,

page 17).

The object categories group together one or more types of simulation objects. For example, the Signals cate-

gory groups the simulation objects Controller, R11v, R12, R13b, R13c, R24, R25, SAC, PEC, vehicle signalsand pedestrian signals. A button on the simulation object bar corresponds to each simulation object category.

A specific icon is associated with each type of object.

To switch the Network edit area, page 19tocreate modeto create a type of simulation object whose icon

illustrates one of the buttons on the simulation object bar :

1. Move your cursor to the button in the simulation object bar.

2. Left-click. The button remains pressed in and the edit area changes to Create Object mode,

page 19.

Figure 4. The simulation object bar in geometric mode

Figure 5. Simulation object bar in logical mode

Signal

Measure

Pedestrian

Singlela

ne2.0

Underpass

Detector

Stop

Conflict

3DSt

ile

Simulationobjectcategorytitles

Barsinitialstate

Othertypes

ofsimulationobjectbycategory

Timetable

Trafficc

ount

VMS

Lanec

hange

Invalidp

ath

Measure

Barsinitialstate

Othertypesofsimulationobjectbycategory

Simulationobjectcategorytitles

Stages

Links

Origins

Dstns

Splitlink

s

Zones
http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-


22/481



For an object category that includes a number of different objects, to change the type of the simulation

object associated with the buttonon the simulation object bar:

1. Move your cursor to the button on the simulation object bar.

2. Keep the left mouse button pressed until the drop-down menu containing the various types of pos-

sible simulation objects for the associated category is displayed.

3. Keeping the left mouse button pressed, drag the mouse to the menu item corresponding to theappropriate simulation object.

4. Release the mouse button.

a the menu closes,

b. the new icon selected illustrates the button,

c. the button remains pressed in,

d. the edit area changes to Create Object mode, page 19.

Module bar

The module bar provides access to the module entry windows (see "Module bar", fig.6 p.18).

To open a modules entry window:

1. Click the appropriate module bar icon.

2. The Module entry window, page 27is displayed.

The contents of the module bar are not affected by the current mode, i.e., logical or geometric.

Search object

This command is used to find/delete an object in the simulation model.

The search can be performed by browsing the list of objects sortedby name, type, or the layer to which

they belong:

1. Click to open the "Search object window" (see fig. 7, page 19).

2. Click the header of the column corresponding to the appropriate sort key; the arrow displayed next

to the columns header represents the sort order. To invert the sort order, click this header again.

3. Browse the list using the scroll bar.

4. In the list of objects, left-click the object searched for to highlight it and zoom in the network edit

area.5. Click Quit to close the Search object window.

The search can be performed directly from the objects name:

1. Click to open the "Search object window" (see fig. 7, page 19).

2. In the Name Filter field, enter the name of the object or its first letters followed by the * wildcard

character to filter the list.

3. In the list of objects, click the object searched for to highlight it and zoom in the network edit area.

4. Click Quitto close the Search object window.

It is possible to reduce the number of objects displayed by applying a filter on their IDs. A filter is defined as

a set of characters and/or of meta-characters * replacing any set of characters. For example, the filterWE_*_1 will display objects named WE_1_1, WE_20ze_1 etc. The filter is defined using the field named

Name Filter of the "Search object window" (see fig. 7, page 19).

Figure 6. Module bar
http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-


23/481



PRESENTATION

The Search object window lists all the objects in the model, even those not included in the current scenario.

If you select an object that is not included in the current scenario, the edit window is zoomed, however the

object is not displayed since it does not exist in the current scenario.

Network edit area

The network edit area is used to visualize/edit all the projects simulation objects. The Background map,

page 53and the graphic representation of the simulation objects are displayed in the network edit area. Each

simulation object has a graphic representation according to the object category to which it belongs, its

parameters, and to the current mode - logical or geometric. The user determines the objects position.

The network edit area is displayed in one of five possible modes :

Create Object mode, page 19

Zoom mode, page 20

Continuous Zoom mode, page 20

Edit Object mode, page 20

Pan mode, page 24

The current mode also determines the shape of the pointer when located in the network edit area.

To modify the part of the network displayed in the network edit area, you can use the scroll boxes along the

borders of the display area. You can also use the mouse wheel to move the area displayed vertically, provided

the cursor is inside the scroll area.

Create Object mode

You switch to Create object mode after clicking one of the buttons on the Simulation object bar,

page 17.

Figure 7. Search object window

Listoffilteredobjects

Entrylinedisplayingtheselected

Validationbuttons

Namefilter

object
http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-


24/481



The mouse pointer changes to in the network edit area.

The subsequent operations to perform for creating network objects are described in the chapter dealing with

the type of simulation object.

Zoom mode

To increase or decrease the scale at which the background map and the simulation objects are displayed :

1. Switch to zoommode by clicking the button on the toolbar. The mouse pointer changes to

in the network edit area.

2. In the edit area, position the pointer at the center of the area you wish to zoom in on.

3. Left-click to zoom in and right-click to zoom out.

4. The edit area remains centered on the selected point.

Continuous Zoom mode

Switch to continuous zoom mode by clicking the button on the Toolbar, page 15.

The mouse pointer changes to in the network edit area.

To continuously zoom in or zoom out :

1. Position the mouse cursor in the edit area away from any network objects.

2. Click and drag up or down to zoom in or out, or use the mouse-wheel to the same effect, whatever

the pointers status.3. The scale is modified continuously until the left mouse button is released.

The zoom windowfunction is accessible in continuous zoom mode. The window is delimited by a rectangle,

defined by two opposite corners, either from left to right or from right to left, regardless. The zoom factor is

defined by the minimum height or width ratios between the rectangle and the edit window.

1. Right-click to define the first corner of the selection rectangle.

2. Drag the mouse to define the rectangle.

3. Right-click again to complete the rectangle that defines the selection window.

Edit Object mode

You enter edit object modeby clicking the button on the Toolbar, page 15.

The mouse pointer changes to in the edit area.

In Create object mode, you can use the following functions:

1. Pan mode, page 24, using the middle mouse button instead of the left button.

2. Continuous Zoom mode, page 20, using the mouse wheel.

In continuous zoom mode, you can use the Pan mode, page 24, function using the middle mouse

button instead of the left button.


25/481



PRESENTATION

In edit object mode, you can:

deleteor modifya simulation object, or place it in the backgroundor foreground

1. Switch to edit object mode.

2. Position the pointer on the simulation object to modify. Right-click to display a drop-down menu

containingModify, Foreground, Background, Delete.

3. Drag to the appropriate menu item keeping the right button pressed.4. Release, for example, on Modify to display the simulation object entry window.

movea simulation object on the background map


2. Position the pointer on the object to move.

3. Left-click and hold to move the object.

4. Release at the desired location.

selecta simulation object


2. Position the pointer on the object to select.

3. Left-click to select the object.

deselectan object or multiselection


2. Left-click in the edit area away from any object.

perform a multiselection


2. Keeping theShiftkey pressed, left-click the objects displayed in the edit area that you wish to add

to the selection.

perform amultiselection in a rectangle


2. Keeping the CTRLkey pressed, right-click at the point where you want to start your selection

rectangle.

3. Release the mouse button, then drag the mouse to the opposite corner of the selection rectangle.

4. Right-click again once you reach the opposite corner. All objects that are not part of a frozen layer,

and that are completely or partially situated inside the rectangle, are selected (see Using layers

and network scenarios, page 62).

perform amultiselection by path

This consists in selecting a sequence of paths that a vehicle can take during the simulation.


2. Position the pointer at the start support of the path to select.

3. Right-click to display the drop-down menu associated with the support. Keeping the button

pressed, drag the mouse to the "Select path" menu item.

4. The selection is extended up to the next fork, or to the end of the network. For a fork, a dialog boxis displayed in which you can choose to either stop the selection, or extend it by selecting one or

other of the forks corresponding paths.


26/481



Figure 8. Multiselection by path

Selectedtrajectory

Clickedhandle


27/481



PRESENTATION

move a set of objects

1. Make a multiselection, a rectangle multiselection, or a multiselection by path on the objects to

move.

2. Position the pointer on one of the objects selected (it is highlighted).

3. Keeping the left button pressed, move the mouse as appropriate.

4. Release the button to complete the operation.

modify a set of objects : change the layer, switch to the foreground/background, delete, change the

speed limit.

1. Make a multiselection or a rectangle multiselection on the objects to modify.

2. Position the pointer on one of the objects selected.

3. Right-click and drag the mouse to select the appropriate operation.

rotate a set of objects

1. Make a multiselection, a rectangle multiselection, or a multiselection by path on the objects to

move.

2. Right-click and select Rotate in the menu.

3. Left-click and hold, then move the mouse to define the angle of rotation.

clone a set of objects

1. Make a multiselection or a rectangle multiselection on the objects to clone.

2. Position the pointer on one of the objects selected.

3. Right-click and drag the mouse to select the Clonemenu item and open the corresponding win-

dow.

4. Define the naming rule applied to the cloned objects by filling in the fields according to the fol-

lowing rules :a if possible, replace the old prefixeswith the new prefixes, or else concatenate the new prefix and the

original object name,

b. if the name of the cloned object already exists, add the "CL !" prefix.

5. The multiselection now applies to the cloned objects, which cover the old objects. You must move

the selected objects in order to distinguish the original ones from their clones (see move a set of

objects, page 23).

paste the parameters of one path to a set of paths (see Copying/Pasting trajectory properties,

page 91).

You must select an object to change a subset of its geometric characteristics.

For a multiselection, you can move, delete or modify the order in which the selected objects are displayed,and assign them a common layer.

Multiselection or rectangle multiselection operations invert the selected/deselected states of the

objects.

In other words, for a multiselection by rectangle, all the objects inside the rectangle that are in the

selected state change to the deselected state; the other objects in the rectangle switch from the

deselected state to the selected state.
http://-/?-http://-/?-http://-/?-http://-/?-


28/481



Pan mode

To enter pan mode, click the button on the Toolbar, page 15.

The pointer changes to in the network edit area.

To Pan in edit mode:1. Switch to pan mode.

2. Position the pointer in the edit area away from any objects.

3. Left-click and drag the mouse.

4. Release when you have finished panning.

Status areas

The two status areas are located at the bottom of the "Main CubeDynasim window in geometric mode" (see

fig. 1, page 14).

Theinformation areadisplays parameters specific to the simulation object the mouse is pointing to regard-

less of the mode of the Network edit area, page 19. Moreover, when pointing to Handles, page 80,

Trajectories, page 81, or Links, page 158, the object will be highlighted in the Network edit area,

page 19.

The message area offers guidance about the appropriate actions and their consequences depending on

CubeDynasims current mode. When creating a simulation object, the message area reminds you of the pos-

sible commands.

Animation in the network edit area

CubeDynasimcan be used to define, simulate and animate a simulation scenario in the interface. This fea-

ture allows you to quickly analyze a situation without having to start a number of replications.

In Create Object mode, page 19, Continuous Zoom mode, page 20, and Edit Object mode,

page 20 pan mode is accessible by following the same procedure using the middle mouse button

instead of the left button.


29/481



PRESENTATION

Define a simulation scenario

To define a simulation scenario in the editor, use the quick selects in the Toolbar, page 15to select the

network and flow scenarios and, optionally, the signal and PT scenarios to define a simulation scenario.

Select a simulation scenario

To select an existing simulation scenario, click on

Click on one of the displayed simulation scenarios. The quick selections of the Toolbar, page 15are auto-

matically updated.

Figure 9. Animation in the edit area
http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-


30/481



Calculate a simulation scenario

Once the scenario has been defined, its status is indicated by a circular indicator to the right of the list of

quick selections.

The indicator specifies that the scenario has never been simulated and that the animation is therefore

not available.

Click this button to add the scenario to the simulation scenarios in the Simulation module, page 403

and start the scenarios calculation.

The indicator specifies that the scenario is being calculated and that the animation can already be

displayed in this state.

The indicator specifies that the scenario has been simulated and is up to date. The animation is avail-

able.

The indicator specifies that the scenario exists and has been simulated in the past, but that its anima-

tion, even if it is available, no longer matches the model.

Click this button to start the simulation and get an updated animation.

Uppercase + left click on the indicator opens the "Messages window" (see fig. 213, page 415).

Animate a scenario in the edit area

The CubeDynasimanimator integrated in the edit area has three modes:

the animation for the active scenario, defined by the statuses of the quick selection lists, is not

available.

This mode corresponds to thegraysimulation indicator.

the animation for the active scenario is available; click this button to access the animation control

buttons.

the animation for the active scenario is in progress in the models edit area; click this button to close

the animation and go back to the model in edit mode.

To animate a scenario in the models edit area, click the button if available. Integrated animator bar,

page 26is subsequently displayed.

Restart: restarts the animation from the simulation start time.

Previous: rewinds the animation in 5-minute increments.

Step: forwards the animation by one quarter of the value of the animation speed.

Play/Pause: plays or pauses the animation.

Next: fast forwards the animation in 5-minute increments (provided the simulation at t + 5 min was ani-

mated beforehand).

Time field: this editable text field shows the current time of the animation. You can edit this field to move

to a given moment in time (provided the simulation calculation has finished or is sufficiently complete.)

To change the animation time, click on the hour, minute or second in the field and enter the correspond-

ing value. After a few moments, the animation in the edit area moves to the instant entered.

Speed field: the vehicle animation speed can be modified either via the numeric field (where 1 corre-

sponds to real time, 2 to twice the speed of real time, etc.), or via the speed slider that you can

Documents

Reference Manual Cube Dynasim 6.11