Sigmix User Manual

Sigmix User's Manual
Chen, Yen-Hsiang
December 5, 2017
2
alen3321@gmail.com
Greenwave Octopus Transport Solutions, Ltd.(Taiwan)
3
This manual is done via LATEX.

4
Contents
1 Overview 9
1.1 Sigmix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
1.2 Licensing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
1.3 Structure of Sigmix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
1.4 Quick Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
1.4.1 Fast Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
1.4.2 An Signalled Junction Example . . . . . . . . . . . . . . . . . . . . . . . . 12
2 The Main Window 21

2.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
2.2 Horizontal Buttons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
2.3 Vertical Buttons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
2.4 Menu Bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
2.4.1 File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
2.4.2 Facility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
2.4.3 Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
2.4.4 Library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
2.4.5 Bulk Property . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
2.4.6 Single Run . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
2.4.7 Optimisation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
2.4.8 Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
3 Topology and Its Object 29

3.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
3.2 Links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
3.2.1 Add a Link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
3.2.2 Topology Editing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
3.2.3 Edit Link Property-General . . . . . . . . . . . . . . . . . . . . . . . . . . 30
3.2.4 Edit Link Property-Signalled . . . . . . . . . . . . . . . . . . . . . . . . . 31
3.2.5 Delete Link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
3.2.6 Colouring of Link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
3.3 Connectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
3.3.1 Add a Connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
3.3.2 The Topology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
3.3.3 Edit Connector Property-General . . . . . . . . . . . . . . . . . . . . . . . 32
3.3.4 Edit Connector Property-Priority Relation . . . . . . . . . . . . . . . . . 32
3.3.5 Edit Opposed Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
3.3.6 The Superposition Principle . . . . . . . . . . . . . . . . . . . . . . . . . . 34
3.3.7 An opposed Turn Example . . . . . . . . . . . . . . . . . . . . . . . . . . 34
3.3.8 Delete Connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
3.4 Whirlpools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
3.4.1 Add a Whirlpool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
3.4.3 Edit Whirlpool Property . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
3.4.4 Time Dependent Demand (TDD) . . . . . . . . . . . . . . . . . . . . . . . 36
3.4.5 Delete Whirlpool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
3.5 Junctions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
3.5.1 Add a Junction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
3.5.3 Edit Junction Property . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
3.5.4 Delete Junction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
5
6 CONTENTS
3.6 Signalboxes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
3.6.1 Add a Signalbox . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
3.6.3 Edit Signalbox Property . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
3.6.4 Edit Signal Staging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
3.6.5 Edit Signal Timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
3.6.6 Delete Signalbox . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
4 Signalbox Settings 41
4.1 Signalbox Property . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
4.2 Signalbox Stage Editing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
4.2.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
4.2.2 Stream Compatibility (Tab 1) . . . . . . . . . . . . . . . . . . . . . . . . . 42
4.2.3 Intergreen (Tab 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
4.2.4 Signal Grouping (Tab 3) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
4.2.5 Signal Staging (Tab 4) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
4.2.6 Importing File Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
4.2.7 Compatibility Importing File Format . . . . . . . . . . . . . . . . . . . . . 45
4.2.8 Intergreen Importing File Format . . . . . . . . . . . . . . . . . . . . . . . 46
4.2.9 Signal Grouping Importing File Format -Type L . . . . . . . . . . . . . . 47
4.2.10 Signal Grouping Importing File Format -Type G . . . . . . . . . . . . . . 47
4.2.11 Signal Staging Importing File Format . . . . . . . . . . . . . . . . . . . . 48
4.2.12 An Example of Stage Editing: . . . . . . . . . . . . . . . . . . . . . . . . . 48
4.2.13 An Example with Import: . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
4.3 Signalbox Timing Editing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
4.3.1 Optimisation Timing Parameter (Tab 1) . . . . . . . . . . . . . . . . . . . 54
4.3.2 Customised Duration (Tab 2) . . . . . . . . . . . . . . . . . . . . . . . . . 55
4.3.3 An Example for Optimisation: . . . . . . . . . . . . . . . . . . . . . . . . 55
4.3.4 An Example for Single Run: . . . . . . . . . . . . . . . . . . . . . . . . . . 56
5 Single Run 57
5.1 A Single Run . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
5.2 Setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
5.3 Go - Single Run . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
5.4 The Result of Single Run . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
6 Optimisation 61
6.1 Theory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
6.2 Setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
6.3 Go - Optimise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
6.4 The Optimised Signal Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
6.5 Example: T-junction Continued . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
6.5.1 Stage 1 Ineciency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
6.5.2 Ecient Stage 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
7 Document Outputs 69
7.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
7.2 Output of Macroscopic Flow States . . . . . . . . . . . . . . . . . . . . . . . . . . 69
7.2.1 Example: Output of Monkok Case . . . . . . . . . . . . . . . . . . . . . . 69
7.3 Output of Artetial LOS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
7.3.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
7.3.2 The U.S. LOS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
7.3.3 Quick Export LOS Date . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
7.3.4 Customised LOS Output . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
7.3.5 Example of an One-way . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
7.3.6 Syntax Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
7.3.7 Example of Two-way Street . . . . . . . . . . . . . . . . . . . . . . . . . . 79
CONTENTS 7
8 Output as Microscopic 83
8.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
8.2 Microscopic Simulation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
8.3 Sumo . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
8.4 Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
8.5 Example: Isolated Junction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
8.6 Link Fusion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
8.6.1 Same Edge . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
8.6.2 Syntax of Link Fusion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
8.7 Example: Link Fusion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
8.8 Priority . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
8.8.1 Sumo Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
8.8.2 Merging Weight . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
8.9 Renement of the Previous Example . . . . . . . . . . . . . . . . . . . . . . . . . 93
8.10 Pedestrians and Pedal Cyclists . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
8.11 Miscellaneous . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
8.11.1 Details of Connector Priority . . . . . . . . . . . . . . . . . . . . . . . . . 95
8.11.2 Network Topology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
8.12 Support of Mixed Flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
8.12.1 Sublane Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
8.12.2 Lane Width . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
8.12.3 Hook Turn Zone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
8.12.4 Advanced Stop Zone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
9 Frequently Asked Questions 99

9.1 Conict Flow but Receives Green in the Same Stage . . . . . . . . . . . . . . . . 99
9.2 FAQ for Sumo . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
9.2.1 Could not Closed Error . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
9.2.2 Fail to Continue in Second Signal Cycle (mix ow) . . . . . . . . . . . . . 99
9.2.3 Oblique Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
9.2.4 Broken Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
9.2.5 Sumo Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
9.3 Others . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
8 CONTENTS
Chapter 1
Overview
1.1 Sigmix
Sigmix, Synchronising Inter-junction Greens that Minimise the Inauspicious of the linKS, is a
computer-aided tool for estimating performance of a road network and for optimising the green
times to derive a better performance.
1.2 Licensing
The 'Licensing Terms' are repeated here, but if the following is dierent from that claimed in the
elsewhere in the software (at the 'Help'>'About' on the main window or elsewhere), it should be
based on the newest one:
Greenwave Octopus Transport Solutions, Ltd. Terms of License
sigmix ('Software' hereinafter)
This term of license is a protocol between customer and Greenwave Octopus Transport Solu-
tions, Ltd. ('Greenwave Octopus' hereinafter). Please read the terms carefully before using the
'Software'. The customer is agreed with the terms once the 'Software' is used. If not agreed with
the terms, please do not use the 'Software'. The terms are also refer to the updated programming,
patched programming and supported services.
0. Denition: 0.1 Edition: The 'Software' the customer uses is categorised in one of the
following editions. Each edition has its own corresponding license term(s) if a paragraph elsewhere
stated in form of Roman numbers (I, II, III...): (I.) Full Edition: Edition that customer got
licensed from a supplier or retailer.(II.) Student Edition: Edition that customer as identity of
student got licensed from a supplier or retailer. (III.) Citizen Edition: Edition that customer
as a single person that represents him/herself downloaded from ocial website of Greenwave
Octopus.0.2 'Customer': Refers to you or legal entity that represents which has acquired legal
licensed. For example, your employer. 0.3 identity of 'student': A student refers to a full-time
student who is studying at an formal education organisation (limited to PhD. programme, master
programme, university, college or high school or below) that is recognised by education ocials.
If a person who is full-time in occupation other than student or is hired as formal faculty, he/she
is not identied as a student in this protocol.
1.Customer has the rights and obligations: I. Full Edition: (a)Right to install and use the
'Software'. (b)Behaviour that make use of the computing process or computing result to make
protable business. (c)Publicise the computing process or computing result at medium of third
party, including paper, electronic or on Internet. II. Student Edition (a)One who has identity of
full-time student that is recognised by government ocial of education has the right to install and
use the 'Software'. (b) Behaviour that make use of the computing process or computing result to
publicise the computing process or computing result at medium of third party, including paper,
electronic or on Internet. But making prot from it is not included. III. Citizen Edition (a) As
a single person not representing any organisation has the right to install and use the 'Software'.
If an organisation( no matter prot or non prot, academic or not) use the 'software' in the
purpose of evaluating whether to purchase, training or, demonstration, then the organisation has
the same right as those the abovementioned single person has. (b)For the purpose of promoting
public benets and fulling the curiosity over road trac or urban studies, customer is allowed
to make use of the computing process or computing result to publicise the computing process
or computing result at medium of third party, including paper, electronic or on Internet. But
making prot from it or submitting to a journal that is promoting one's scholar reputation are
not allowed.
10 CHAPTER 1. OVERVIEW
2. When installing, retrieving data from or using the 'Software', Greenwave Octopus has the
right to require the user to provide encrypted keys that are able to prove legal trade. Customer
is not allowed to share the encrypted keys with others.
3. If customer does not follow the instructions provided by Greenwave Octopus, either cus-
tomer is not able to use the 'Software', or the function of the software is restricted. Might
keep happening until the customer make remedial measure to start the programme, and may be
responsible for fees from Internet communication or telephone.
4. Scope of license. Customer is authorised to use the 'Software' once the 'Software' is
licensed, but not sold. Customer is only allowed to use the 'software' in the scope of permitted
behaviours written in the contract. This, customer must comply to use the 'Software' in certain
ways, and must not manipulate steps that are not written in User Manual, which is included in
the software package. Customer must not: (a)avoid the protection mechanism in the 'Software';
(b)make reverse engineering to the 'Software'; (c)detect the source code of the 'Software' or
decode the 'Software'; (d)extend the 'Software' or wrap the 'Software' up by another (automated
or not) procedure to manipulate the 'Software'; (e)see the 'Software' as a whole and detach part
of element in the 'Software'; (f)use the 'Software' in an illegal manner.
5. Quantity of license. Number of the 'Software' stalled by customer in storage devices(including
but not limited to hard disc, CD, memory card, USB...and other electronic devices etc.) must
not exceed the quantity being licensed. However, one additional copy is allowed but must not
be used during regular times except when original copy is out of use due to hardware failure and
this additional copy is aimed at reinstalling.
6. Terms prohibiting any form of transfer. The 'Software' and this contract must not
rent/sublease to third party, must not sell/resell to third party and must not provide third
party to use with or without charge (transfer or sublicense). Customer must not distribute to
third party to make copy (copies). 6.1(II.) Additional note on Student edition: If user(s) of
'Student Edition' submitted to journal for scholar reputation, then the number of article authors
must not exceed the number of student version being licensed. If the abovementioned article has
co-author that is not a student, then at least a full version must be licensed.
7. Limited damage responsibility.
7.1(For (I.) Full Edition and (II.) Student Edition) If customer encounters damage of devices
caused directly by using 'Software', the compensation would depend on seriousness of the damage,
and has a limit up to the trade price. Greenwave Octopus is not responsible for other indirect
damages using the 'Software', including prot loss,derivative loss or others. 7.2(For (III.) Citizen
Edition) For use of the 'Software', the customer has responsibility of its own risk.
8. Governing law. If controversy exists, the governing law is the law in Taiwan and over
where Taiwan Taipei District Court has jurisdiction.
9. Main Language of the term. The terms in English is translated from written Mandarin
in the form of Han-ji used by Taiwanese ocials. The translated words are kept precise from
the original language as possible but if there is controversy, customer and Greenwave Octopus
should follow the terms in original text.
1.3 Structure of Sigmix

See Figure 1.1, SIGMIX has a layered structure: with physical simulator that runs the macro-
scopic ow of vehicle dynamics. This layer itself can be applied as evaluation tool of trac that
performance index under certain trac signal settings can be derived. If the purpose is to opti-
mise the setting, additional layer is applied: the optimiser layer. The optimiser layer is able to
nd the optimal signal by generic algorithm (GA). The simulator simulates macroscopic trac
of the roads and it has the capability to model car (passenger car) trac. If the mixed ow with
motorbikes is the prevailing condition, mixMIX plug-in would be a good option to replace the
default simulator.
1.4 Quick Guide

1.4.1 Fast Steps
The quickest way to build a network is probably by the following steps:
1. Build all links. Press 'Add link' button. Click on the canvas for beginning of this link.
Click again for its destination.
2. Connect the links by 'Add connector'. Click on outgoing arrow of a link. Click again on
incoming arrow of another link to nish the creation of this connector.
1.4. QUICK GUIDE 11
Figure 1.1: Structure of Sigmix. It has a simulator at the bottom layer, a optimiser at the top
layer, and an interpreter ;ayer in between.
3. Create signalbox(es). Press 'Add signalbox' button, then click on the main canvas to create
signalbox. Number of signalbox should be the same as number of signalised junction.
4. Set the signalise link. Press 'Edit link' button, then select the link to edit. Right click to
call the menu. Select 'Edit link property' to edit. Change the 'Signal-Controlled' to 'yes',
'controlled by' to the signalbox to control. Then click on 'APPLY'.
5. Create whirlpools, where the demand of trac ow comes from and goes away. Press 'Add
whirlpool' button, then click on the main canvas to create whirlpool(s).
6. Press 'Edit whirlpool' button and then select the whirlpool to edit. Right click on the
whirlpool to call the menu. Select 'Edit whirlpool property' to edit. If this whirlpool is the
source of a link, select the link and then press '+' to add. Then click on 'APPLY'.
7. Set signal details. Press 'Edit signalbox' button, then select the signalbox to edit. Right
click to call the menu, then select 'Edit signal stage'. The 4 tabs are (a) stream compatibil-
ity, (b) intergreen between streams, (c) [optional] signal grouping, and (d) signal staging.
It is required to follow the order to edit.
(a) Stream compatibility: Press the table in the centre to select whether two movements
are compatible ('o'), semi-compatible('s'), or conict('x'). Select 'APPLY' to continue.
(b) Intergreen between streams: Edit the intergreen times. Select 'APPLY' to continue.
(c) [optional] Signal grouping: Group the stream(s) that is(are) enforced to have the same
signal staging. Select 'APPLY' to continue.
(d) Signal staging: Check the box for the stage(s) a group to receive green. If number of
stage is not enough, press '+' to add, else press '-' to delete stage. Select 'APPLY'
and 'DONE' to nish the setting.
8. Network settings: Select 'Settings' > 'Global Signal Settings' to set the cycle time.
9. Select 'Optimisation' on the overhead menu. Then, select 'Go' to optimise the signal timing.
Note that before pressing this you should at rst examine if the network has been done
setting. It takes time to optimise.
10. After the optimisation, a summary would be shown. They are the performance index (P.I.),
'Simulation Time', and 'Calculation Time of Performance'. Click 'Show Detail...' for more
information.
11. To save the work, select 'File'>'Save'. Note that the saved le does not include the result
of 'Single Run'/'Optimisation'. You have to export the result as a worksheet (*.csv le).
The layer of objects is not saved, either.
12. The detailed performance is shown in 3 tabs: 'Optimised Plan', 'Network State of particle',
and '[Network State of] outow':
(a) Optimised Plan shows the signal plan such that the P.I. is operated at its best;
(b) 'Network State of particle' shows the number of autos/ pedestrians/ pedal cyclists in
links and whirlpools during dierent simulation intervals. Select the interval to render,
and then select a link to render by 'Render Plot'. (The 'Render All' is not suggested
if the hardware is not capable of rendering large amount of plot at a time)
(c) '[Network State of] outow' is the outow of autos/ pedestrians/ pedal cyclists in a
links and whirlpools during dierent simulation intervals. It has same widgets as the
previous tab.
13. To export the detailed result, press more '...' button to export. To export it quickly (with-
out naming it with a lename), select 'Quick Export File', then 'report_for_optimisation.csv'
will be exported. You can also export the result by selecting 'Export Report to...'. You
can open it with any kind of worksheet reader.
Note that one does not need to conform to the above steps strictly. The skilled engineer can
follow his/her own recipe to nish the task.
1.4.2 An Signalled Junction Example

This example builds a junction start-from-scratch in fastest steps. It is a junction with two
crossing one-ways. It is demonstrated step-by-step:
1. Add Links. Press 'Add Link' button. Build the links from link1 to link4 by clicking on the
canvas.
2. Add Connectors. Press 'Add Connector' and connect the links from amber triangles to
blue triangles.
3. Create a signalbox to control this junction. Press the 'Add signalbox' button, then click
on the canvas at where you want it to be.
1.4. QUICK GUIDE 13
4. Set the links to be controlled as signalised links. Press the 'Edit link' button, then click on
the entering links (link1 and link3) one-by-one. They will be shown in bold in appearance
so that you can be sure that they are clicked. Then, right click to display the menu, which
has a selection 'Edit link property'.
5. Set them (link1 and link3) as signal controlled as in the 'Edit Link Property' dialogue:
Select 'yes' in 'Signal-Controlled'. Also, set 'Controlled by' as '1'-referring to 'signalbox
no. 1'. Press 'APPLY' to save.
6. Stop for a while to examine previous steps work (or not): Boarders of link1 and link3 should
now be yellow. Compare them with the boarders of link2 and link4, of which should be
purple.
7. Create whirlpools. Press the 'Add whirlpool' button, then click on the cordon lines of the
network - At
(a) upstream of link1;
(b) downstream of link2;
(c) upstream of link3; and
(d) downstream of link4. (Note that the above order is the suggested order. The model
still works with a dierent order )
8. Edit the whirlpool information. Press the 'Edit whirlpool' to begin editing. Click on
whirlpool 1. Right click to show the menu and click the 'Edit whirlpool property'. In the
popped dialogue 'Edit Whirlpool Property', in the window of 'Pitch to Candidate', click
on link1 and then click the add '+' button. Now you should see link1 changed its position
into the 'Pitch to Link' window. Click 'APPLY' to save settings. The same manner applies
to whirlpool 3.
9. Now, click on whirlpool 2, and this time we are editing 'Catch from'. Right click to show
the menu and click the 'Edit whirlpool property'. In the popped dialogue 'Edit Whirlpool
Property', in the window of 'Catch from Candidate', click on link2 and then click the add
'+' button. Now you should see link2 changed its position into the 'Catch from Link'
window. Click 'APPLY' to save settings. The same manner applies to whirlpool 4.
1.4. QUICK GUIDE 15
10. Now, examine the settings of whirlpools, you should see blue lines, meaning pitching re-
lation, connected from whirlpool 1 to link1 and from whirlpool 3 to link3. And there are
yellow lines, meaning catching relation, from whirlpool 2 to link2 and whirlpool 4 to link4.
11. Set the signal details. Click on the 'Edit signal' button, then click on signal no. 1. Right
click on it to display the menu and select 'Edit signal stage'. There should be two links
shown in the dialogue 'Edit signal stage'. Let us edit the 'Stream No.': Edit link 1 as
'Stream No.' 1 (Edit this by typing) and edit link3 as 'Stream No.' 2. Make this 'APPLY'.
12. Click the tab 2 named 'Intergreen Matrix'. Assume that after analysis1 , the intergreens
are both 6(sec), then set it by click and type. Press 'APPLY >>' to save and go on to the
next tab.
13. Edit the group: Set Stream 1 as Group 1 and Stream 2 as Group 2. (If it is already set,
skip this step by simply clicking 'APPLY>>') Note that since the two streams cannot be
in the same group, a transition group should be created by adding: Click add '+' button
to append a new group. Change Stream 1 to Group 3 by clicking on stream '1' and then
'Chng Group' button, then select 'Grp. 3' and 'Select'. Now Change Stream 2 to Group 2
by clicking on stream '2' and then 'Chng Group' button, then select 'Grp. 2' and 'Select'.
Finally, change Stream 1 to Group 1 by clicking on stream '1' and then 'Chng Group'
button, then select 'Grp. 1' and 'Select'. Delete Group 3 by clicking 'Grp. 3' and then
minus '-' button. Press 'APPLY>>' to save.
1 For example, with UK practice the analysis is the procedure in Trac Advisory Leaet 1/06 General Principles
of Trac Control by Light Signals.
1.4. QUICK GUIDE 17
14. Click the tab 'Staging' (tab 4) and edit the stage. Group 1 (grp.1) receives green on stage
1 while the other (grp.2) on stage 2. Press 'APPLY>>' and then 'DONE'.
15. Now, set the cycle time. In the main window, select 'Settings' in the menu bar, then 'Global
Signal Settings' to set the cycle time. Set it as 60(sec), then 'APPLY'.
16. Set the performance index type. Select 'Optimisation' in the main window, then 'Setting
for Run/Optimisation', set 'Objective function' to 'min Delay' and 'APPLY'.
17. Now, we are ready to nd the optimised signal scheme. In the main window, select 'Opti-
misation' in the menu bar, then 'Go - Optimise'. Wait for the results.
18. After optimisation (it may take time), the result would be shown in summary: The per-
formance index, 'Simulation time', 'Calculation Time of Performance'. The detail can be
seen by clicking 'Show Detail...'.
19. The dialogue 'Optimised Result' has 3 tabs: 'Optimised Plan', 'Network State of particle',
and '[Network State of] outow':
(a) 'Optimised Plan' shows the optimised trac signal settings. All the bars are displayed
(actual) green.
(b) 'Network State of particle' shows how many vehicles/ pedestrians/ pedal cyclists in a
auto/ pedestrian/ cycling link and whirlpools during dierent time intervals. Select the
'Rendering Interval' rst (for example, '3000 to 3300') then 'Render All'. (However,
it is suggested to render one plot at a time when there are huge amount of links since
the hardware may not be capable of dealing to much data in a short time)
1.4. QUICK GUIDE 19
(c) '[Network State of] outow' shows how much amount of outow during dierent time
intervals. Select the 'Rendering Interval' (for example, '3000 to 3300') rst, and then
click on 'Render Plot' beside 'link3' to see the outow of link3 in a plot.
20. To analyse in an worksheet elsewhere, export the le (in the form of *.csv) by clicking
more '...' button on the northeast, then press 'Quick Export Report', then a le named
'report_for_optimisation.csv' is generated. Open that le with your own worksheet editor.
Chapter 2
The Main Window

2.1 Introduction
The main window refers to the window that has one road network canvas, a menu bar, and main
function buttons. The network canvas is where the road network topology forms. By adding and
editing objects on the network canvas, it abstracts the core feature of the road. The functions on
the menu bar mostly covers those operations that are more complex and are less to be clicked;
the functions that are often being applied are listed in the buttons.
2.2 Horizontal Buttons

The buttons are 'Load', 'Save', and 'Save as' respectively. If not certain the function of the
subject button, move the cursor onto it and stay for a moment to see the balloon hint.
2.3 Vertical Buttons

The vertical buttons are summarised from left to right and from top to bottom.
22 CHAPTER 2. THE MAIN WINDOW
Adjust Scope
The background to accommodate the network might not be enough if large road network is built,
or vice versa. Adjust the scope by this button. Click 'Adjust Scope', then click anywhere on the
road network canvas. There are dierent functions:
1. 'Broaden [direction ] Scope': Extent the scope you can see on the specied direction.
2. 'Narrower [direction ] Scope': Shrink the scope you can see on the specied direction.
3. 'Adjust All Boundary to Fit the Current Network': As it named.
4. 'Adjust [direction ] Boundary to Fit the Current Network': As the previous function but
limited to t two directions only. This function is for those who is certain not to extend
the network on part of the direction but still building on the other sides.
5. 'Undo Scope Adjustment': The change in the scope adjustment can be undone if the le is
not closed.
Ordinary Mouse
Ordinary mouse provides a way not to accidentally click any of the object and change its property.
Click this before coee break.
Add Link
Links could be added on the network canvas after clicking the 'Add link' button.
Edit Link
Links could be edited on the network canvas after clicking the 'Edit link' button, and then left
click on the link to be edited. Finally, right click on it again to select further operation.
Add Connector
Connectors could be added on the network canvas after clicking the 'Add connector' button.
Edit Connector
Connectors could be edited on the network canvas after clicking the 'Edit connector' button, and
then left click on the connector to be edited. Finally, right click on it again to select further
operation.
Add Whirlpool
Whirlpools could be added on the network canvas after clicking the 'Add whirlpool' .
Edit Whirlpool
A whirlpool could be edited on the network canvas after clicking the 'Edit whirlpool' button,
and then left click on the whirlpool to be edited. Finally, right click on it again to select further
operation.
2.4. MENU BAR 23
Facility Type There are 3 kinds of facility types: 'Auto'/'Pedestrian'/'Pedeal Cycle'. If the
mode is 'Auto', the 'Add link' would refer to 'Add auto link', the 'Add connector' would refer to
'Add auto connector', and the 'Add whirlpool' would refer to 'Add auto whirlpool'. The same
manner applies to that of 'Pedestrian' and 'Pedal Cycle'.
Add Junction
Junctions could be added on the network canvas after clicking the 'Add junction' button. Note
that junctions are for displayed purpose only and will not aect the run/optimise results.
Edit Junction
Junction could be edited on the network canvas after clicking the 'Edit junction' button, and then
left click on the junction to be edited. Finally, right click on it again to select further operation.
Add Signalbox
Signalboxes could be added on the network canvas after clicking the 'Add signalbox' button.
Edit Signalbox
A signalbox could be edited on the network canvas after clicking the 'Edit signalbox' button,
and then left click on the signalbox to be edited. Finally, right click on it again to select further
operation.
2.4 Menu Bar
2.4.1 File
The operations here are all relevant to the le. The network are saved as network le (*.nwk)
and can be loaded again next time you need it.
New
New le is to create a completely new network.
Load
Load le is to open and reload the saved le.
Save
Save le is to preserve the current work on network canvas. If already named, the save will
update the existing le. If, however, unnamed (untitled), it will be asked to create a le name.
Save as
Save [le] as... is to preserve the current work on network canvas, but with a dierent name if
already named.
Note that (1) the position of the tags of links and (2) the layer of object (whether one object is
higher than the other) are not remembered. So reloaded le might not have the same appearance;
however, their P.I. is guaranteed to be the same.
Export Image
The network canvas can be exported. 'Quick' here means the network is exported directly
without further asking the le name and it is named 'roadnetwork.ps' automatically. 'Quick
(current view)' means the network is exported limiting to the view you currently see, and it is
named 'roadnetwork_part.ps' automatically.
Note that the image is exported as a postscript le (*.ps). This le format has no standard
for supporting Unicode. Thus if there are Unicode characters, it will not be displayed in the
exporting le.
Figure 2.1: Start-up Lost, End-of-Green Displacement and Eective Green
2.4.2 Facility
Facility allows you to change the layer of particular facility. Those facilities include: link/whirlpool/junction/signalbox.
You can raise them all or lower them all.
2.4.3 Settings
Global Trac Settings
Global trac settings refer to the global parameter of start-up lost and end-of-green displacement.
Note that if particular link does not conform to the global parameters, it can be set locally
elsewhere (in section 3.2.4).
Start-up lost is the time when signal turns to green, the road user might need a reaction time
to take action, to accelerate, to adopt speed. Figure 2.11 shows an ordinary departing capability
of a signalised link after the beginning displayed green. We can convert its saturation owrate
over time from curve (in solid line) into a rectangle (in dashed grey line) so that they still have
the same capability to discharge vehicles. The rectangle has the same area as the shouldered
solid curve of outow capacity over time. This means that we can treat the discharge in a way
that can be calculated with easier arithmetic. The begin of rectangle is the begin of eective
green and the end of rectangle is the end of eective green. The displayed green (actual green in
some literature) thus has some deviation to the eective green. Start-up lost is also literally the
dierence between the begin of eective green and the begin of displayed green, shown as d1.
End-of-green displacement has its reasoning in the similar manner: Once the signal is dis-
played from green to amber, the road users would not stop immediately. Rather, some of them
(perhaps they are in the so-called dilemma zone or they are aggressive users) do not stop within
a time range. On average, road users stop at least some time after signal changes from green to
amber. This is the parameter of end-of-green displacement, shown as d2.
A formula to transform: duration of eective green = duration of displayed green - start-up
lost (d1) + end-of-green displacement (d2).
1 Some jurisdictions do not require amber plus red, but turns from red to green directly. If the local regulation
does not have amber plus red, simply treat it as a part of red in the gure.
2.4. MENU BAR 25
Global Signal Settings

Global cycle time is applied globally in the road network. If it is desired to try dierent cycle times
in the optimisation process, set dierent times here and re-run ('Go-optimise') the optimisation.
Note that the cycle cannot be too short to create infeasibility of the green distribution. The
following formula must be followed:
For any signalled junction, sum of intergreen and sum of minimum green for all stages must
be smaller than cycle time.
If not true, there is no room to accommodate the intergreen and minimum green of all stages,
thus infeasible2 . If the above condition not fullled, error will be shown when editing cycle, when
editing signal timing of the unsatised signalbox, or when executing 'Single Run'/'Optimisation'.
2.4.4 Library
Some of the operations in creating road network are tedious and repetitive. To avoid such time-
consuming tasks, library is a place to nd reusable set of objects. There are 3 levels of library,
based on their scope.
Load Object Library

They are part of junction and may be applied twice (or above) in a junction.
Load Junction Library

Junction Library themselves form complete junction. They may be applied twice (or above) in
a network.
Load Network Library

They form a network themselves, but probably not the most useful type of library. But if one is
interested in modifying a complete network this is a good choice.
2.4.5 Bulk Property

[Facility ] Bulk Editor
Allows you to edit property of many links/ connectors/ whirlpools/ junctions/s ignalboxes in a
window with list. All the 'Edit' buttons have the same function as directly clicking that object.
2 This term comes from industrial engineering, or applied mathematics.

Flow Ratio Bulk Editor

Allows you to inspect the outow ratio to the downstream link(s) for all of the links. Subject
links are listed in 'from link' and its downstream links are listed in the 'to link' with turning
ratio. Note: if no ocial plug-in installed for bus or motorbike, the ratio of them will not be
eective.
2.4.6 Single Run

There are two dierent functions: 'Single Run' v.s. 'Optimisation'. Before executing, you must
be certain what purpose you are aim at. Evaluating or nding a potential better signal plan?
Evaluating is that once the network is built (by you on the network canvas), you can assign signal
plan (by editing signalboxes>Right click [on particular signalbox] >'Edit signal timing'>Check
the 'Customised duration'>Click on tab 2>Edit the duration>Click 'APPLY'.). A 'Single Run'
executes the proposed plan and returns a evaluated result (in specied performance index).
For example, you are investigating whether a proposed right-turning lane would alleviate
the congestion (in a signicant level or not), you should build two networks: The rst should
be the current network; the second would be the proposed scheme. After nishing the former,
'Single Run' ('Single Run'>'Go-Single Run') it, get the P.I., and save it, probably with le name
'current.nwk'. Then, save it as 'proposed.nwk' and add the proposed lane. 'Single Run'('Single
Run'>'Go-Single Run') it again, with another P.I. returned. Now you can compare the P.I. of
the two.
This software applies macroscopic simulation to do the evaluation. In the example of the
last paragraph, it can be also done by microscopic simulation [by other tools], which tracks all
the road user trajectories. But if you can do that in a faster manner-by this, via macroscopic
simulation3 , why not?
A complete chapter elsewhere shows the details of 'Single Run'.
2.4.7 Optimisation
In contrast to 'Single Run', the signal plan is not specied to be xed. In 'Optimisation'
('Optimisation'>'Go-Optimise'), all of the feasible plans that conforms global cycle time, in-
tergreen times, and constraints of minimum green time, could be possible to be the optimised
one. The executing of the optimisation is aim at nding the best performance, and its corre-
sponding signal plan. Following examples show when to use this function:
1. Newly built network: At/In a newly built junction/network, or with a newly installed
signal, a new signal plan must be set. Given the prediction of demand ow and turning
ratio, you might want to know what the best signal timing would be.
3 Actually , macroscopic simulation requires less parameter to calibrate, and thus should have better stablity in
the result. On the other hand, microscopic simulation requires many parameter to calibrate and may be sensitive
to one of the parameters.
2.4. MENU BAR 27
2. Modied network: During construction, lanes might be closed. Or, other new geometry is
created. The optimised plan is dierent from that of the original one. You might optimise
the signal according to the new scenario to provide a smooth ow to the road user.
3. Aged and reset: If there is no apparent change in geometry, signal timing still behaves not
as ecient as before. This is called aging of the signal timing and is due to the change in
demand (including demand ow and turning ratio). To cater new demands, the signal plan
of a network must be reformed once in 3-10 years. So you should input the demand with
recent investigation and optimise the signal timing.
Simply click 'Optimisation', then click 'Go-Optimise' to optimise. Detailed operations are in a
complete chapter elsewhere.
2.4.8 Help
User's Manual
The click of 'User's manual' should link to this document.
About
The version information, copyright claim and licensing terms are here. Note! You accept the
terms once using the software, if not, do not use.
Chapter 3
Topology and Its Object

3.1 Introduction
A valid network contains links, connectors, whirlpools [, optionally junctions] and signalboxes.
You must apply these objects to form a topology that abstracts the roads of a network.
3.2 Links
Links are those to transport road users, including motor vehicles, pedestrian, and pedal cyclists.
We now begin with a link that carries motorists.
3.2.1 Add a Link

Press 'Add link' button. Note the current 'Facility Type': If it is 'Auto', then you are building
a link for auto; if it is 'Pedestrian', then you are building a link for pedestrian, or a 'Pedestrian
Path'; else if it is 'Pedal Cycle', then you are building a link for pedal cyclists, or a 'Pedal Cycle
Path'. Click on the canvas for beginning of this link. Now an auxiliary line would appear to help
you on targeting, and then click again for its destination.
3.2.2 Topology Editing

You can rotate a link, or raise/lower its layer. Press 'Edit link' button, then click on the link you
want to edit. Right click again to select the function from menu, including: 'Rotate link', 'Raise
to top', and 'Lower to bottom'.
Rotate Link After selecting 'Rotate link', drag to rotate.
Raise to Top After selecting 'Raise to top', the link will be raised to the top if it is originally
covered by other object(s).
Lower to Bottom After selecting 'Lower to bottom', the link will be lowered to the bottom
if it is originally covering other object(s).
Change Position Press 'Edit link' button, then click on the link you want to edit. Drag it to
change position.
30 CHAPTER 3. TOPOLOGY AND ITS OBJECT
3.2.3 Edit Link Property-General

Parameters of a link must be edited in detail. These includes: 'Link Name', 'Link Length',
'Signal-Controlled' or not, 'Controlled by'(if necessary), 'Capacity', 'Freeow Speed', 'Number
of Lanes', 'Width', 'Merging Weight'.
Press 'Edit link' button, then click on the link you want to edit. Right click again to select
'Edit link property' from menu, then a dialogue titled 'Edit Link Property' would appear and
allow you to edit.
Link Name 'Link Name' is what you call this link. Do not give repeated names for dierent
links. It is recommended to start by alphabets and then by other numbers/letters. For example,
though '101x' is valid, it is still suggested to name it 'link 101x'. Starting with 'link' helps
reduce confusing when various object numberings come to you at once.
Link Length 'Link Length' is as it names and is measured in metres. Click on the arrows
to adjust the length. Note that if its length is adjusted and applied ('APPLY' is clicked), its
position of head (outgoing end) will not be changed whereas its tail (incoming end) will be
changed according to the newly assigned 'Link Length'.
Signal-Controlled 'Signal-Controlled?' is a true/false option. If 'yes', this link is signalled;

else it is not.
Controlled by If 'Signal-Controlled?' is 'yes', this link is signalled, and should be controlled

by one of the signalboxes. If the signalbox to control this link is not already established, then it
is not required to assign it immediately (just leave it as 'Select a signal'). It is allowed to assign
the controlling signalbox later, but before the 'Single Run'/'Optimisation'.
Capacity Capacity is the maximum ow this link can deal with. It is by default 2000(veh/hr),
which is the ordinary capacity of one lane. Note that when the link is signalised, the capacity
here refers to 'saturation owrate', having ordinary value of 2000(veh/hr per lane). If there is
more than one lane, assign it with higher value. (If you have not established this link in real
world with no historic data, and there is no suggested data in your jurisdiction, add up 2000
when adding up an additional lane, set in 'Number of Lane(s)')1
Freeow Speed Freeow Speed is that during the modest trac condition (the freeow) of
the subject link, what is the average speed of all vehicles.
Number of Lanes The number of lanes of this link. You should check that this value conforms
to the 'Capacity' specied.
Width Width is eective only when motorbikes are taken into account. Note that motorbikes
may appear only in plug-in modules. Without motorbike modelling, this option will not be
eective.
Merging Weight 'Merging Weight', defaulted by 10, is a parameter to specify when this link
and another link merges into the downstream link, if without priority control (and it is a simple
merge), what would be the weight of this link that can get into downstream if the downstream
link cannot accommodate all of the trac sending from subject link and the other link. For
example, link 45 and link 46 merges into link 47 and weighted 30 and 70 respectively. Link
45, 46 and 47 has capacity of 2100, 3100 and 4000, respectively. Demand of link 45 and link
46 is 1500, 2900 respectively. Obviously ow of 4400 (1500 + 2900) cannot be possibly pass
the link with capacity of 4000. Thus, only 1200 and 2800(veh/hr), can be discharged from link
45 and link 46 respectively. This comes from the fact that 1200 / 2800 is the ratio of 30 /
70. Thus, 'Merging Weight' must be calibrated well if it is expected to have merging points (or
any unsignalled junctions having queues likely) that is probable to fail to accommodate all its
upstream demands. If there is no such concern, merging weight will not be eective.
To save the edited parameter, press 'APPLY'.
1 If there is only single lane, the capatity should set as 2000; where there is 2 lanes, set it as 4000; where there
is 3 lanes, set it as 6000...etc... and so on.
3.3. CONNECTORS 31
3.2.4 Edit Link Property-Signalled

There is another tab titled 'Signalled'. This tab can be edited only if this link is a signalled
link. The parameters to set are: 'Apply global/local setting', 'Start-up lost', and 'End-of green
displacement'. Press 'Edit Link' button, and then click on the link you want to edit. Right click
again to select 'Edit signalled link property' from menu, and then a dialogue titled 'Edit Link
Property' would appear and allow you to edit the second tab.
Apply Global Setting Two mutually exclusive options exist: 'Apply global settings' or 'Apply
local settings'. If the 'Start-up lost' and 'End-of green displacement' parameters are both the
same to the settings globally (in the main window, select 'Settings' and then 'Global Trac
Settings'), check here, else check the 'Apply local settings'. (For global settings, refer to 2.4.3.)
Apply Local Setting If at least one of the parameters, which are 'Start-up lost' and 'End-of
green displacement', is dierent from the global settings (in the main window, select 'Settings'
and then 'Global Trac Settings'), then check this button.
Start-up lost Start-up lost is the dierence between the begin of eective green and the begin
of displayed(actual) green. Click arrows to edit. If not familiar with this parameter, refer to
2.4.3.
End-of-Green Displacement End-of-green displacement is the dierence between the end

of eective green and the end of displayed (actual) green. Click arrows to edit. To save the
parameters, press 'APPLY'.
3.2.5 Delete Link

To delete a link, press 'Edit Link' button, then click on the link you want to edit. Right click
again to select 'Delete this link' from menu.
Note that relevant relationships would be deleted at the mean time, including: the connector
connected to upstream and downstream, the signalbox behaviour if it was signalled (It is strongly
suggested to examine the relevant signalbox again, especially that the originally set signal stage
might be broken due to the link withdraw), and the downstream whirlpool (if it leads to a sink)
or the upstream whirlpool (if it is sent by a source).
3.2.6 Colouring of Link

The boarder of a link should be yellow if signalised; if not, it should have a purple boarder. The
colouring allows you to check its signalisation status in a quick glance.
3.3 Connectors
A connector connects two links. Thus, a connector must be started from the end of a link (shown
as amber triangle) to the beginning of another link (shown in blue triangle).
3.3.1 Add a Connector

Press 'Add connector' button. Note the current 'Facility Type': If it is 'Auto', then you are
building a connector for auto; if it is 'Pedestrian', then you are building a connector for pedestrian;
else if it is 'Pedal Cycle', then you are building a connector for pedal cyclists. Click on one of the
amber triangle for beginning of this connector, and then click again on the other blue triangle to
nish creating the connector.
3.3.2 The Topology

There is no way to directly edit the topology of the connector, since it should be dependent of its
host links. Thus, connector always follows the position of the relevant amber and blue triangles
if links are dragged, rotated, or reduced in length.
3.3.3 Edit Connector Property-General

Parameters of a connector must be edited in detail. These includes: 'Turning Ratio' and 'Priority
Relation'
Press 'Edit connector' button, and then click on the connector you want to edit. Right click
again to select 'Edit connector property' from menu, then a dialogue titled 'Edit Connector
Property' would appear and allow you to edit.
Note that connectors do not have their own names, thus in the dialogue it is mark with its
host links. (For example, 'From link16 to link13'. Or, 'From link1 to link2')
Turning Ratio Its default value is 10. 'Turning Ratio' is the ratio the outow of a link
would come via this connector to the downstream link. As an example, consider link 14 has 3
downstream links, which are link 15, 16 and 17 with 'Turning Ratio' 10, 24, and 18, respectively.
The outow of link 14 is 360(veh/hr), then the ow into link 15, 16 and 17 respectively are,
69.2(veh/hr), 166.1(veh/hr), and 124.6 (veh/hr), respectively since they are with ratio 10:24:18.
(Note that in this case it is assumed no jammed in any of the downstream links, otherwise the
answer would be smaller)
Note that the above discussion is about but not limited to 'Car ratio'- the 'Motorbike ratio'
and 'Bus ratio' also applies. Also note that the motorbike ratio and bus ratio are not eective
unless relevant plug-in is installed.
If you want to see a clear view of the ratio to other links from a designated link, it is suggested
to use the 'Bulk Property'. (In the main window, click 'Bulk Property', and then 'Flow ratio
bulk editor') They are all listed in single dialogue.
3.3.4 Edit Connector Property-Priority Relation

'Priority Relation' is designed for priority junctions, or opposed turns. Some terms must be
dened:
Opposed to Link 5 has priority over link 4, then it is said that link 4 is opposed to link 5.
Opposing Link 5 has priority over link 4, then it is said that link 5 is opposing link 4.
Merge with If link 4 and link 5 merges into the same downstream link via certain connector,
and they do not have clear priority relation, link 4 merges with link 5 and vice versa. Note that
this condition is automatically true in signalised links if two links never receive green in the same
time. If, however, there is any opposed turn, apply the other two conditions instead.
3.3. CONNECTORS 33
Now, with the terms dened, the operations in this dialogue are listed in the following:
Add Opposed to Press the add '+' button to add an opposed movement to relation. Select
another connector that has priority over this one, then press 'Select'. If the [other] link having
priority is a motor vehicle carriageway, then the governing 'Function' is 'f1'; if the [other] link
having priority is a pedestrian path (This link is thus opposed to that pedestrian path, probably
a pedestrian crossing), then the governing 'Function' is 'f2'; if the [other] link having priority is
a pedal cycling path, then the governing 'Function' is 'f3'.
Edit f1 Diagram To edit the 'f1' function, click 'Edit f1 Diagram', and see the next section
for its detail.
for its detail.
for its detail.
As an Opposing Stream Adding this connector directly as an opposing stream is not a valid
operation. Rather, you should edit the opposed stream and the opposing information would be
automatically shown in the 'Priority Relation' of the opposing stream.
3.3.5 Edit Opposed Diagram

The opposed diagram is based on the fact that the ow of opposing ow would aect that of
the opposed stream. If the opposing ow is zero, the opposed ow could operate at its best,
probably the same as its capacity. If the opposing ow is at its largest, the opposed ow could
be almost zero (but probably not zero, but a very low value, depending on local driving habits)
When opposing ow is in between, the resulting opposed ow should be in between. By the
above logic, a opposed diagram could be depicted. The opposing ow is in the horizontal axis,
whereas the opposed ow is in the vertical axis.
Several parameters are allowed to be tuned: 'q(max)', 'slope', and 'q(least)'.
q(max) 'q(max)' is the maximum possible ow of the opposed stream. Note that when the
opposing ow is zero, this still represents the maximum possible ow instead of a denite value
since the opposed outow is also depending on its demand. Click the arrows to edit.
slope 'slope' is the slope of the straight line of the opposed diagram. Click the arrows to edit.
q(least) 'q(least)' is the at-least capacity to discharge for the opposed stream.
If all the parameters are set, press 'APPLY'.
3.3.6 The Superposition Principle

An opposed stream is possible to be opposed by many opposing streams. For example, [in
right-keeping trac] a left turn operation is opposed both by the oncoming trac and by the
pedestrians [if the jurisdiction allows opposed turn with pesdetrian] At unsignalled T-junction,
the left turn vehicle must give way to both streams of the trunk road. Thus, for a stream it is
possible for it to have multiple opposing streams, no matter same mode (both are motor vehicles,
for example) or with multiple modes (opposed by pedestrian and autos, for example).
If multiple opposing streams, with at least two modes, exist, the diagramme is superpositioned
from the 'q(max)'.
Consider the subject connector is opposed by pedestrian stream p8, thus governed by f2 and
by pedal cycle c9, thus governed by f3, and they are:
f2:
q(subject) ≤ max(1700 − 2.0 × q(p8), 96)
f3:
q(subject) ≤ max(1700 − 2.4 × q(c9), 16)
If the ow of pedestrian stream p8 is 300(ped/hr) and the ow of pedal cycling stream is
200(pedal cycle/hr), then:
max(1700 − 2.0 × 300, 96) = 1100
max(1700 − 2.4 × 200, 16) = 1220
The reduced capacity due to opposing stream is (1700-1100)=600(veh/hr) and (1700-1220)=480(veh/hr),
respectively. According to the superposition principle, the reduced ow is 1080, thus the ow of
subject connector cannot exceed 620(veh/hr), which is computed from 1700-1080=620(veh/hr).
3.3.7 An opposed Turn Example

An example can be loaded from the library: In the main window, select 'Library', then 'Load
Junction Library'. Select 'Trunk Road and Secondary Road' to load. In this network, right
turning connector of link16 is opposed both by pedestrian and by pedal cycle.
3.3.8 Delete Connector

To delete a connector, press 'Edit connector' button, then click on the connector you want to
edit. Right click again to select 'Delete this connector' from menu.
3.4 Whirlpools
A whirlpool is an object that trac comes from and goes away into. It generates trac and
pitches to links; it is also able to catch trac from links that are leaving the network boarder.
3.4. WHIRLPOOLS 35
3.4.1 Add a Whirlpool

To add whirlpool, press 'Add Whirlpool' button, then click on the canvas. Note the current
'Facility Type': If it is 'Auto', then you are building a whirlpool for auto; if it is 'Pedestrian',
then you are building a whirlpool for pedestrian; else if it is 'Pedal Cycle', then you are building
a whirlpool for pedal cyclists.

You can change its position, or raise/lower its layer. Press 'Edit Whirlpool' button, and then
click on the whirlpool you want to edit. Right click again to select the function from menu,
including: 'Raise to Top', and 'Lower to Bottom'.
Raise to Top After selecting 'Raise to top', the whirlpool will be raised to the top if it is
originally covered by other object(s).
Lower to Bottom After selecting 'Lower to bottom', the whirlpool will be lowered to the
bottom if it is originally covering other object(s).
Change Position Press 'Edit Whirlpool' button, and then click on the whirlpool you want to
edit. Drag it to change position.
3.4.3 Edit Whirlpool Property

Parameters of a whirlpool may be edited in detail. These includes: 'Whirlpool ID', 'Link Pitch
To', 'Link Catch from', and 'Demand Flow'.
Press 'Edit Whirlpool' button, and then click on the whirlpool you want to edit. Right
click again to select 'Edit Whirlpool Property' from menu, then a dialogue titled 'Edit whirlpool
property' would appear and allow you to edit.
Whirlpool ID 'Whirlpool ID' is the identication of a whirlpool you can assign. It is integer
only and cannot be the same with the 'Whirlpool ID' of another whirlpool.
Link Pitch to Links in 'Link Pitch to' are links that generates the trac from the boarder of
the network and this whirlpool can assign the demand of them (in the 'Demand Flow' tab.).
Add a Link Pitch to To add a link into 'Link Pitch to', click the candidate in 'Link Candidate'
of 'Pitch to Candidate', then press add '+' button above it.
Delete a Link Pitch to To delete a link in 'Link Pitch to', click the 'Link' in the box, then
press minus '-' button above it to delete it.
Link Catch from Links in 'Link Catch from' are links that carries ow that are leaving the
road network. The whirlpools conrm this fact.
Add a Link Catch from To add a link into 'Link Catch from', click the candidate in 'Link
Candidate' of 'Catch from Candidate', then press add '+' button above it.
Delete a Link Catch from To delete a link in 'Link Catch from', click the 'Link' in the box,
then press minus '-' button above it to delete it.
Demand Flow The xed 'Demand Flow' can be edited by clicking the tab 'Demand Flow',
and then demand can be edited. Use arrows to edit the demand (in veh/hr). For time-dependent
demand settings, please see next subsection.
Press 'APPLY' to save all the parameter settings.
3.4.4 Time Dependent Demand (TDD)
Trac demand varies within rush hour itself. An hourly average of 166 (veh/h) might be a
combination of 300 (veh/hr) for the 1st 1000 (sec) and then 250 (veh/h) for the next 100(sec) (
from 1000 to1100 sec) and nally 110 (veh/h) for the last 2500(sec) (from 1100 to 3600 sec).
It should be however noted that the most trac investigations do not have such detailed
value. The previous example is mostly recorded as " 166(veh/h) and peak hour factor (PHF) of
0.37". But if an engineer has the time and resource to record such values in detail, then TDD
input is more suitable for reproducing this kind of detail.
Let us demonstrate how to format a TDD le, named myfirst.tdd, before we state the
syntax.
vehType:pc
#time__ flow__
#before demand
#------ ------
1000 : 300
1100 : 250
3600 : 110
vehType:mb
#time__ flow__
#before demand
#------ ------
1000 : 700
1100 : 459
3600 : 223
Press 'Edit Whirlpool' button, and then click on the whirlpool you want to edit. Right
click again to select 'Edit Whirlpool Property' from menu, then a dialogue titled 'Edit whirlpool
property' would appear and allow you to edit. The TDD can be imported by clicking the tab
'Demand Flow' >> check the 'Apply TDD' checkbox.
'Import' >> select myfirst.tdd (or another *.tdd le) >> 'OK'. Then, 'View' to conrm
the input. Now, you can view a graphical bar chart to conrm the import.
3.5. JUNCTIONS 37
Let us check the above graph: Before time point 1000 (sec), the demand ow is 300; before
time point 1100 (sec), the demand ow is 250(sec); before time point 3600 (sec0, the demand
ow is 110 (sec). If you are not sure if the imported TDD le is what you expected, always use
the 'View' to check.
After run/optimisation, it can be checked at '-outow' tab of 'Show detail...' Note that when
showing the states of run/opt result, the unit of ow is veh/sec.
Syntax of TDD
The syntax of TDD le (*.tdd) is:
[# <comments>]
vehType : <vehicle type>
[# <comments>]
<timeBefore1><demand1>
<timeBefore2><demand2>
[<timeBefore3><demand3>[...]]
[# <comments>]
<vehicle type> supports pc, mb. <comments> can be any characters, which are only for
user's personal notes. <timeBefore1> <demand1> states that the trac demand is demand1
(veh/hr) before simulation time point <timeBefore1> (sec). This implies the values of <time-
Before1> and <demand1> should be nonzero integer. It should be noted that if no values are
stated after the last time point, then the demand continues the last with the value of the last
statement. Hence, if zero demand is desired, zero should be explicitly expressed.
Note! Pedestrian and pedal cyclist trac are not suitable for TDD
Note that users are, in addition to import the demand of passenger cars, able to record the TDD
of motorbikes but these values are only eective when mixMIX plug-in is used.
3.4.5 Delete Whirlpool

To delete a whirlpool, press 'Edit whirlpool' button, then click on the whirlpool you want to
edit. Right click again to select 'Delete this whirlpool' from menu.
Note that relevant relationships would be deleted in the meantime, including: the connection
to the pitched links and to the catched links.
3.5 Junctions
A junction is an object that indicates the position of a junction. However, it is used as demon-
stration purpose. It will not be eective when applying 'Single Run'/'Optimisation'.
3.5.1 Add a Junction

To add a junction, press 'Add junction' button, then click on the canvas.

You can change its position, or raise/lower its layer. Press 'Edit Junction' button, then click
on the junction you want to edit. Right click again to select the function from menu, including:
'Raise to top', and 'Lower to bottom'.
Raise to Top After selecting 'Raise to top', the junction will be raised to the top if it is
Lower to Bottom After selecting 'Lower to bottom', the junction will be lowered to the
Change Position Press 'Edit junction' button, then click on the junction you want to edit.
Drag it to change position.
3.5.3 Edit Junction Property

Press 'Edit junction' button, then click on the junction you want to edit. Right click again to
select 'Edit junction property'. The 'Junction ID' can be assigned to be the identication of a
junction. Note that no two of the junctions are allowed to have the same ID.
3.5.4 Delete Junction

To delete a junction, press 'Edit junction' button, then click on the junction you want to edit.
Right click again to select 'Delete this junction' from menu.
3.6 Signalboxes
A signalbox is an object that controls the trac in certain links that are permitted to move or
not in a range of time. Links controlled by it are signalised links.
3.6.1 Add a Signalbox

To add a signalbox, press 'Add signalbox' button, then click on the canvas.

You can change its position, or raise/lower its layer. Press 'Edit signalbox' button, and then click
on the signalbox you want to edit. Right click again to select the function from menu, including:
'Raise to top', and 'Lower to bottom'.
Raise to Top After selecting 'Raise to top', the signalbox will be raised to the top if it is
Lower to Bottom After selecting 'Lower to bottom', the signalbox will be lowered to the
Change Position Press 'Edit signalbox' button, and then click on the whirlpool you want to
edit. Drag it to change position.
3.6. SIGNALBOXES 39
3.6.3 Edit Signalbox Property

Parameters of a signalbox must be edited in detail. Press 'Edit signalbox' button, and then click
on the signalbox you want to edit. Right click again to select 'Edit signalbox property' from
menu, then a dialogue titled 'Edit Signalbox Property' would appear and allow you to edit. The
detail of these parameters will be mentioned elsewhere (in section 4.1).
3.6.4 Edit Signal Staging

Signal staging of a signalbox must be edited in detail. Press 'Edit signalbox' button, then click
on the signalbox you want to edit. Right click again to select 'Edit signal stage' from menu, then
a dialogue titled 'Edit Signal Stages' would appear and allow you to edit. The detail of these
parameters will be mentioned elsewhere (in section 4.2).
3.6.5 Edit Signal Timing

Signal staging of a signalbox must be edited in detail. Press 'Edit signalbox' button, and then
click on the signalbox you want to edit. Right click again to select 'Edit signal timing' from
menu, then a dialogue titled 'Edit Signal Timing' would appear and allow you to edit. The detail
of these parameters will be mentioned elsewhere (in section 4.3).
3.6.6 Delete Signalbox

To delete a signalbox, press 'Edit signalbox' button, then click on the signalbox you want to edit.
Right click again to select 'Delete this signalbox' from menu.
Note that relevant relationships would be deleted at the mean time, that is, the controlling
links. These links should be reset of its signal behaviour by perhaps another signalbox if they
are still signal controlled.
Chapter 4
Signalbox Settings
4.1 Signalbox Property
To edit the general property of a signalbox, rst click the 'Edit signal' button, left click on the
subject signabox, and then right click to view the menu, click 'Edit Signalbox Property'. In the
'Edit signalbox property' dialogue, the 'SignalboxID' and 'Controlling Links' can be edited.
Signalnox ID 'Signalbox ID' is the identication of the signalbox that no two of them could
be the same.
Controlling Links 'Controlling Links' are links that are controlled by this signalbox. You
must select the candidate from the pool of 'Controlling Candidate', then press plus button '+'
to add. If a link you want to add into is not in the candidate pool, it might be either:
1. It is not selected as a 'Signalled Link'. Rather, it is an 'Unsignalled Link'; or
2. It is already selected as 'Controlling Link' by another signalbox.
To resolve, following are suggested measures according to the above condition, respectively:
1. Change the link to 'Signalled' link and do it again. In the main window, click 'Edit link'
button, left click on the subject link, and then right click to see the menu. Click 'Edit link
property' and change the 'Is signal controlled' to 'Yes', then 'APPLY'. Then you can try
to select it from candidate now.
2. Change signalbox controlling the subject link. Click 'Edit link' button, left click on the
subject link, and then right click to see the menu. Click 'Edit link property' and change
the 'Controlled by' directly to the signalbox you want to control it.
42 CHAPTER 4. SIGNALBOX SETTINGS
If you change your mind not to control certain link by this signalbox, press the link to retire in
'Controlling Links' and then press minus '-' button.
All the settings are saved only if 'APPLY' is pressed. Else the changes are not into force.
4.2 Signalbox Stage Editing

4.2.1 Introduction
Any signalised junction should be checked with 4 steps: (a) stream compatibility, (b) intergreen
between streams, (c) [optional] signal grouping, and (d) signal staging.
1. Stream compatibility: If two streams do not conict (their trajectory is absolutely no over-
lapping), then they are 'compatible'. If two movements have their swept path overlapped,
they are basically 'conict', except for cases that they are allowed to be green at the same
time, then they are 'semi-compatible'(or 'semi-conict' in other literatures).
2. Intergreen between streams: If two movements 'conict', the end of green of one stream
(that is losing right-of-way) must have a buer(in seconds) before allowing another one
(that is gaining right-of-way) to light the green up.
3. [optional] Signal grouping: signals in the same group have same signal stage at all times.
Note that this also means giving up the potential choice in pursuit for signal optimisation.
4. Signal staging: stage is a set of link that are green at the same time during the same interval
(stage duration). Stages are in timely order to create a signal staging. Thus, in this step,
the user determines how many stages for this signalbox and which of the group(s) are in
what stage.
4.2.2 Stream Compatibility (Tab 1)

To edit the signal stage, rst click the 'Edit signal' button, left click on the subject signabox, and
then right click to view the menu, click 'Edit signal stage'. In the 'Edit Signal Stages' dialogue,
the 1st tab should be the 'Compatibility Matrix'.
The 'Compatibility Matrix' here is link-based (stream-based). For example, a link allowing
left-turn and through movements is considered single unit (instead of two) that is named 'stream'.
Links are listed in the leftmost.
Change the Order The order of link can be changed (especially when you already have a draft
version on your hand, you might want the draft and the matrix here having the same order):
By clicking on subject link, and then press left arrow '<' to move up and right arrow '>' to the
other way.
Stream Number The 'Stream No.' is a number given to a link controlled by this signalbox.
The 'stream No.' cannot be repeated within this signalbox.
Compatibility Compatibility can be edited by directly clicking on the symbol of 'O', 'X',
's', which are 'compatible to', 'conict with', and 'semi-compatible to', respectively. Press 'AP-
PLY>>' to save the editing.
4.2. SIGNALBOX STAGE EDITING 43
Import If you want to import the already built compatibility matrix, click more '...' button,
then click the 'Import from...'. Select the compatibility le (*.cp1) you want to import.
Export Click more '...' button, then click the 'Export to' button to export. Select a lename,
ended with .cp1 ([lename].cp1). You can load it to another junction later if the number of
controlling links is the same and the link names are appropriately modied. You can also 'Quick
Export' the le, which is named 'exportedStageEditor.cp1' automatically.
4.2.3 Intergreen (Tab 2)

Note rst of all that this tab is not editable unless the previous tab is already applied ('APPLY'
is pressed). Press tab 2, titled 'Intergreen Matrix' to enter. Intergreen is counted from ::: the
time a link ends its
::::::::::::::::::::::
green(stream losing right-of-way) to the time the other link begins its
::::::::::::::::::::::::::::::::::
green
(stream gaining right-of-way). This is the minimal safety time interval and should constraint the
signal setting any time since set. Directly click on the integer to modify the time (in seconds) of
intergreen. Press 'APPLY>>' to save the editing.
Import If you want to import the already built intergreen matrix, click more '...' button, and
then click the 'Import from...'. Select the intergreen le (*.ig2) you want to import.
Export Click more '...' button, then click the 'Export to' button to export. Select a lename,
ended with .ig2 ([lename].ig2). You can load it to another junction later if the number of
controlling links is the same. You can also 'Quick Export' the le, which is named 'exported-
StageEditor.ig2' automatically.
4.2.4 Signal Grouping (Tab 3)

Note that this tab is not editable unless the previous tab is already applied ('APPLY' is pressed).
If grouped, streams in the same group have same signal stage at all times. However, as from
your knowledge of signal setting, this would constrain the exibility of staging and the overall
performance of a signal. Thus it is optional to group streams together, but not required.
A rule to follow is: At least one stream for a group. Or, a group cannot be logically empty.
No Group Bundle Even though grouping is not required, the rule should still be followed.
Thus, if not plan to group, a stream still belongs to one of the group: Press 'No Group Bundle'
to automatically set the grouping, which follows the rules and it follows the order of the links
controlled. Press 'APPLY>>' to save the editing.
Add a Group Click add '+' button to add a group.

Delete a Group Select the group to delete, then click on minus '-' button. Note that before
deleting the group the stream(s) in it should be all cleared, or this operation is not allowed.
Change Group To change the belonging group of a stream, rst click the stream no. directly,
then press 'Chng Group'. Note that within a group, all streams must be mutually compatible.1
Import If you want to import the already built grouping relations, click more '...' button, then
click the 'Import from...'. Select the grouping le (*.gp3) you want to import.
Export Click more '...' button, and then click the 'Export to' button to export. Select a
lename, ended with .gp3 ([lename].gp3). You can load it to another junction later if the
number of controlling links is the same. You can also 'Quick Export' the le, which is named
'exportedStageEditor.gp3' automatically.
4.2.5 Signal Staging (Tab 4)

Note that this tab is not editable unless the previous tab is already applied ('APPLY' is pressed).
Also, some rules should be noted, or else not applicable:
1. A group must be green in at least one of the stages.
2. A stage cannot be empty, without any groups in it.
Check the Stage If a group is green on some stages, then the box should be checked on those
stages.
Add Stage Click add '+' button to append a new stage in the end.
Delete Stage Click the stage to delete, then click minus '-' button to delete the stage. Note
that before deleting a stage, all box of that stage should be unchecked.
1 In literature, they are in a clique of a compatiblity graph.

Import If you want to import the already built staging relations, click more '...' button, then
click the 'Import from...'. Select the staging le (*.st4) you want to import.
Export Click more '...' button, and then click the 'Export to' button to export. Select a le-
name, ended with .st4 ([lename].st4). You can load it to another junction later if the number
of groups is the same. You can also 'Quick Export' the le, which is named 'exportedStageEdi-
tor.st4' automatically.
The Hint from the Staging

The checkboxes in the 'Staging' tab in fact provide mechanism to hint the possible feasible stage.
If you think you are done setting a stage, but there is still a box that can be checked (not shown
disabled), either:
1. A potentially group that can be green at this stage is forgotten to check (An example can
be seen in section 4.2.12). Check it;
2. The compatibility matrix is not well set. Examine the compatibility matrix again; or
3. There is no problem if it is desired to allow semi-compatible movements to receive green

simultaneously in one stage and only allow one of them in the other [stage].
4.2.6 Importing File Format

To import the compatibility, [stream] intergreen, grouping, and staging, formats must be strictly
followed otherwise the input data cannot be correctly identied. The formats are introduced in
following 4 sections.
4.2.7 Compatibility Importing File Format

The le can be edited by any kind of text editor, and you must save the lename in the form
of *.cp1, for example: 'junction1.cp1'. The le must contain Begin_compatibility to reveal
the beginning of the relevant content (This means that before this line you can contain other
customised message that will not be input but does not violate the format). Then, for every link
controlled by this signalbox, follow the grammar:
[link name]:[stream num.],[one line of compatibility matrix separated with comma]
Link Name Link name should be the same one of the links controlled by this signalbox, and
vice versa (every link controlled by this signalbox should appear in one of lines of the input le).
Otherwise the input format, missing some links or having unrecognised links, would not be valid.
Remember to add a colon (:) after the link name. Note that the links are ordered.
Stream Num. Stream num. (stream number) can be assigned freely by you if it is an integer
and any two links controlled by this signalbox do not have the same number. Remember to add
a comma (,) after the stream number.
One Line of Compatibility Matrix One line of compatibility matrix separated with comma
means that you should list all compatibility status in pairwise. For example, if there are 4 links,
then in a line you should list the compatibility status to all of 4 links, and separate them with
commas (,). If they are compatible, use capital alphabet-o(O); if they conict with each other,
use capital alphabet-x(X); if they are semi-compatible, use lowercase-s(s).
After all controlled links are listed, must end it with End_compatibility to reveal the end
of valid message.
A valid example is:
Begin_compatibility
link 45:1,O,O,X,O
link 46:2,O,O,O,O
Link 47:3,X,O,O,X
Link 48:4,O,O,X,O
End_compatibility
There are 4 links controlled by the signalbox and they are numbered from 1 to 4 as their
stream num. Compatibility should be self-explaining.
4.2.8 Intergreen Importing File Format

The intergreen le can be edited by any kind of text editor, and you must save the lename in the
form of *.ig2, for example: 'junction1.ig2'. The le must contain Begin_intergreen to reveal
the beginning of the relevant content (This means that before this line you can contain other
customised message that will not be input but does not violate the format). Then, for every link
controlled by this signalbox, follow the grammar:
[*link name]:[one line of intergreen matrix separated with comma]
Link Name Link name in this le is optional (mark with *) because its order are already
dened in previous section when we assigned the link in lines. Thus, if link name is not repeated
here, they can still be identied by their order.
One Line of Intergreen Matrix

One line of intergreen matrix separated with comma means that you should list all intergreen
values (in integer) in pairwise. Note that:
1. The matrix needs not to be symmetric. Since intergreen is calculated by relationship of

the trajectory of movement, enforced safety interval from end of green of link 45 to begin
of green of link 47 might have dierent value than that of from end of green of link 47 to
begin of green of link 45. This is a common sense in trac engineering, but it should be
reminded here again just in case.
2. If two streams are compatible, then its intergreen will not have any eect. A comma
practice is to show it in -255 to show that they are compatible.
In the end, End_intergreen must be shown.

A valid example is:
Begin_intergreen
link 45:5,2,1,5
link 46:4,3,2,4
Link 47:4,5,4,5
Link 48:4,5,5,3
End_intergreen
Note that if it is already shown compatible in the compatibility matrix (either by manually
set or by importing *.cp1 le) the intergreen stated here will not be eective. So, the 5,2, and 5
in the line of link 45 has no eect in real implemented intergreen. The previous example has
the same eect as:
Begin_intergreen
:-255,-255,1,-255
:-255,-255,-255,-255
:4,-255,-255,5
:-255,-255,5,-255
End_intergreen
4.2.9 Signal Grouping Importing File Format -Type L

The signal grouping le can be edited by any kind of text editor, and you must save the lename
in the form of *.gp3, for example: 'junction1.gp3'. There are two kinds of format that are
valid (type G and type L), and in this section only type L is introduced. The le must contain
Begin_grouping to reveal the beginning of the relevant content (This means that before this
line you can contain other customised message that will not be input but does not violate the
format). Another line must be added to declare the format of content is: link_format.
Then, for every link controlled by this signalbox, follow the grammar:
[*link name]:[group num.]
Link Name Link name in this le is optional (mark with *) because its order are already
dened in compatibility matrix. Thus, if link name is not repeated here, they still can be
identied by their order.
Group Num. Group numbers are able to identify links that are in the same group. If grouping
is not necessary in your case, just numbered them from 1 to 4.
Following rules must be applied:
1. Links in a group must be compatible with each other; otherwise this is an invalid claim.
2. Group Num. must be integers that can be counted from 1. For instance, if group 4 is
present then group 1, 2, and 3 are also present.
After the specifying data, End_grouping should appear in the le.

Here is a valid example:
Begin_grouping
link_format
link 45:2
link 46:2
Link 47:1
Link 48:3
End_grouping
Another example is here to show that if grouping is not the main concern:
Begin_grouping
link_format
:1
:2
:3
:4
End_grouping
4.2.10 Signal Grouping Importing File Format -Type G

Another format for signal grouping input, type G is introduced in this section. The le must
contain Begin_grouping to reveal the beginning of the relevant content (This means that before
this line you can contain other customised message that will not be input but does not violate
the format). Another line must be added to declare the format of content is: group_format.
Then, for every group, follow the grammar:
:[link name 1] ,[*link name 2] ,[*link name 3] ...
A group has at least one link, so the rst link in a line is compulsory. There may be many
links categorised in this group, so optional link name(s) can be further appended, as comma (,)
correctly separate them.
An example is:
Begin_grouping
group_format
:Link 47
:link 45 ,link 46
:Link 48
End_grouping
Figure 4.1: A signalised T-junction
4.2.11 Signal Staging Importing File Format

The signal grouping le can be edited by any kind of text editor, and you must save the le-
name in the form of *.st4, for example: 'junction1.st4'. To show the beginning of valid data,
Begin_staging must be shown.
The grammar is:
[*group num.]:[to show green or not in this stage],[to show green or not in this stage],[to
show green or not in this stage]...
Group Number Group Number in this le is optional (mark with *) because its order are
already dened in grouping.
Receiving Green The number of columns is the number of stages. If a group receives green
in this stage, then mark it as 1, else 0.
In the end, End_staging must be shown.
Here is an example:
Begin_staging
:0,1,0,1
:0,0,1,0
:1,0,0,0
End_staging
The example shows that there are 3 groups and 4 stages. The rst group receives green
twice, both in stage 2 and stage 4. The second and third group receives green in stage 3 and 1
respectively.
4.2.12 An Example of Stage Editing:

A signalised T-junction example is demonstrated. Consider a T-junction and its network mod-
elling as gure 4.1. There are pedestrian crossings in the south arm (correspond to northbound
vehicle) and east arm(correspond to westbound vehicle), and they are without design of stag-
gered phasing. Demand of whirlpool 11, 13, 14, 1, 2, 3, 4 are 900, 600, 900(veh/hr), 100, 100,
100, and 100(pedestrian/hr), respectively. Capacity is 2000(veh/hr per lane) for ahead stream or
through + right turn stream and is 1500(veh/hr per lane) for right turn stream. Assume all the
objects are well set except for the signal stage and its timing, as gure 4.2. Now, the step-by-step
demonstration is illustrated:
Figure 4.2: The signalised T-junction in modelled network
1. First analyse the compatibility.
(a) If two streams are allow to receive green at the same time, they are 'compatible';
(b) If two streams receiving green simultaneously is forbidden, then they are 'conict with'
each other;
(c) If two streams cannot proceed simultaneously when receiving green but are allowed
to receive green at the same time, they are 'semi-compatible'. Note that whether
the left turn is 'semi-compatible' with or 'conict with' oncoming trac depends
on jurisdiction or on scenario. Also note that whether the turning trac is 'semi-
compatible' with or 'conict with' pedestrian also depends on the jurisdiction. (For
example, in UK2 or Hong Kong, the practice is that turning vehicles and pedestrians
'conict with' each other whenever there is overlapping of trajectory).
2. The analysis of the compatibility setting is realised in the compatibility matrix.
2 But there are exceptions in UK: When special criteria are met and Walk with trac indication is addtionally
shown.
3. Secondly, the intergreen must be analysed. The intergreen requirement/suggestion may

vary among jurisdictions3 , check again the local requirement. Anyway, the procedure is
demonstrated for your reference. Intergreen between link 103 and link 104 is taken as
example. Other intergreens apply in the same manner.
(a) Draw the trajectory of the stream. Note that you need to conform to the trajectory of
the design vehicle, according to the local regulations. (Turn path rendering software
can be referred elsewhere)
(b) Identify the conict point of trajectories, see gure 4.3.
(c) Let us investigate the intergreen between termination of green of link 103 and begin
of green of link 104. The point 'ab' is the point that trajectories meet in advance.
Assume vehicle speed with lowest quarter of link103 takes 2.5(sec) from point 's103b'
to reach point 'ab' and has a end-of-green displacement of 1.8(sec); the vehicle speed
with highest quarter of link104 takes 0.8(sec) from point 's104b' to reach point 'ab'.
A safety buer interval must be created to avoid possible collision, and this value
assumed to be 2(sec)(Note this depends on local regulations and practices). Thus, the
intergreen should be 2.5 + 1.8 + 2.0 - 0.8 = 5.5, and rounding to the higher integer
is required. Hence, the intergreen is 6(sec).
(d) Now, investigate the intergreen between termination of green of link 104 and begin
of green of link 103. The point 'aa'4 is the point that trajectories meet in advance.
Assume vehicle speed with lowest quarter of link104 takes 1.1(sec) from point 's104a'
to reach point 'aa' and has a end-of-green displacement of 2.3(sec);the vehicle speed
with highest quarter of link103 takes 1.7(sec) from point 's103b' to reach point 'aa'.
A safety buer interval must be created to avoid possible collision, and this value
assumed to be 2(sec). Thus, the intergreen should be 1.1 + 2.3 + 2.0 - 1.7 = 3.7, and
rounding to the higher integer is required. Hence, the intergreen is 4(sec). It should be
reminded, though a basic knowledge among trac engineers, that intergreen matrix
does not have the general property of symmetry (unlike those symmetric property
appeared in compatible matrix). This is a good example.
4. With the previous analysis, place the calculated intergreen into the matrix. Note that the
value of (stream 3, stream 4) is 6(sec) and that of (stream 4, stream 3) is 4(sec). Other
grids in the matrix are calculated in the same manner. Click 'APPLY>>' and get to the
next tab.
3 For example, with UK practice the analysis is the procedure in Trac Advisory Leaet 1/06 General Principles
of Trac Control by Light Signals.
4 Point 'ac' is also probable. Make sure to check which is the critical one.
5. The grouping follows the stream numbers in this example. 'No Group Bundle' is adequate.
'APPLY' it and get to the next tab.
6. The staging follows the stage diagram as gure 4.4 (a). Obviously this scheme is not
working at most ecient level. As a senior engineer would observe that in stage 1, the
right turn of link 104 can be allowed without any conict. In tab4, it is provided a simple
examine mechanism that allows engineers (not limited to the senior ones) to be able to
identify the inecient without manually examined. The checkbox of group 4 (correspond
to link 104) in the rst stage, allowed to be checked but not checked, reveals that there is
room for improvement.
Figure 4.3: The trajectory and the point of conict
7. Thus, check the box of group 4 (correspond to link 104) in the rst stage, and the more
ecient stage diagram can be seen from the corresponding gure 4.4 (b).
8. Whenever there is forgotten stream in certain stage- to be specic, if adding this stream
does not break compatibility and semi-compatibility- the checkbox will shown in status
that can be checked (contrast to the dimmed box that is not editable). In this example,
there are various alternative stages could be implemented, the stages in gure 4.4 (c), for
instance.
Till now, all the stage settings mentioned are irrelevant to whether execute a single run or
optimisation. The stage settings are basic property of the signalled junction and should be
indierence to whether to single run or to optimise.
4.2.13 An Example with Import:

The previous example is repeated here, but with imported data.
Figure 4.4: Stage diagram (a) proposed but found out to be inecient (b) imporved version (c)
other possible combinations
Compatibility Matrix
Edit with a text editor as the following and save it as *.cp1 le. For example, name it with
'mynetwork.cp1'.
Begin_compatibility
link 101:1,O,O,O,O,X,X,O
link 121:2,O,O,X,O,X,X,X
link 103:3,O,X,O,X,X,X,X
link 104:4,O,O,X,O,O,X,X
link 124:5,X,X,X,O,O,O,X
ped190:6,X,X,X,X,O,O,O
ped191:7,O,X,X,X,X,O,O
End_compatibility
In the rst 'Compatibility Matrix' tab, click more '...' button and select 'Import' and choose
that le to import.
Intergreen Matrix
Edit with a text editor as the following and save it as *.ig2 le. For example, name it with
'mynetwork.ig2'.
Begin_intergreen
link 101:-255,-255,-255,-255,5,4,-255
link 121:-255,-255,6,-255,6,4,6
link 103:-255,6,-255,6,5,6,6
link 104:-255,-255,4,-255,-255,6,6
link 124:6,5,5,-255,-255,-255,6
ped190:6,6,6,5,-255,-255,-255
ped191:-255,6,5,6,6,-255,-255
End_intergreen
In the second 'Intergreen Matrix' tab, click more '...' button and select 'Import' and choose
that le to import.
Grouping
Edit with a text editor as the following and save it as *.gp3 le. For example, name it with
'mynetwork.gp3'.
Begin_grouping
group_format
grp1:1
grp2:2
grp3:3
grp4:4
grp5:5
grp6:6
grp7:7
End_grouping
In the third 'Grouping' tab, click more '...' button and select 'Import' and choose that le to
import.
Staging
Edit with a text editor as the following and save it as *.st4 le. For example, name it with
'mynetwork.st4'.
Begin_staging
grp.1:1,1,0,0
grp.2:1,0,0,0
grp.3:0,1,0,0
grp.4:0,0,1,0
grp.5:0,0,1,0
grp.6:0,0,0,1
grp.7:0,0,0,1
End_staging
To be more ecient:
Begin_staging
grp.1:1,1,0,0
grp.2:1,0,0,0
grp.3:0,1,0,0
grp.4:1,0,1,0
grp.5:0,0,1,0
grp.6:0,0,0,1
grp.7:0,0,0,1
End_staging
In the fourth 'Staging' tab, click more '...' button and select 'Import' and choose that le to
import.
The data from importing le has the same eect as those being input manually. If certain
signalbox has the same staging feature as before, it is advised to reuse its compatibility, intergreen,
grouping, and staging by exporting the data of the previous ones and import them in the subject
signalbox.
4.3 Signalbox Timing Editing

To edit the signal timing, rst click the 'Edit signal' button, left click on the subject signalbox,
and then right click to view the menu, click 'Edit signal timing'. In the 'Edit Signal Timing'
dialogue, the 1st tab should be the 'Optimisation Timing Parameter'.
4.3.1 Optimisation Timing Parameter (Tab 1)

The 'Minimum Green' is stream (link)-based, and its eect is valid for every stage. For example,
link 3 has minimum green of 7(sec) and receives green in stage 2 and stage 4, then both of the
stage has at least minimum green of 7(sec). Another example is that link 2 and link 4 receives
green in stage 3 and their minimum green is 4 and 5 (sec), respectively, then, stage 3 has minimum
green of 5(sec). In other words, stricter one applies.
Edit the 'Minimum Green' by clicking the up/down arrow, then press 'APPLY'.
If you are aim at optimisation, press 'DONE' and leave this dialogue. If, on the other hand,
you are trying to make single run, then check the 'Customised Green Duration' box to edit
specied green duration for each stage.
4.3. SIGNALBOX TIMING EDITING 55
4.3.2 Customised Duration (Tab 2)

To edit tab 2 or not is determined by your purpose: single run / optimisation. This module is
for single run only; any edit in this tab will not aect the result of optimisation. To edit in this
tab, you must check 'Customised Green Duration' in the previous tab.'
The customised green duration is that in a 'Single Run', the signal timing is xed and its
value is referred to here. There are parameters you can edit: 'Stage Duration' for each stage and
'Signalbox Oset'.
Stage Duration Stage duration is the duration of green for the subject stage. Click arrows to
change its value. There are constraints over its value:
1. The stage duration has a least value that is maximum over the minimum greens of links in
this stage. For example, if link2 and link4 belongs to this stage, and their minimum green
is 4 and 5 (sec), respectively, then, this stage has minimum green of 5(sec), and you can
specify the stage duration from 5 to higher values.
2. The sum of stage duration and intergreen for each stage should be equal to the cycle time.
(Note: If you want to change the cycle time, select 'Settings' in the main window and then
select 'Global Signal Settings') The stage intergreen is automatically calculated according
to the stream (link) intergreen.
Note that the above constraints are just reminders for you as clicking arrows to edit shall be
adequate since it does constraint the set value to satisfy the requirement.
Signalbox Oset The 'Signalbox Oset' is the deviation of start of green of the rst stage
from the simulation time zero. For example, if the oset value is 17(sec) and the cycle time is
70(sec), then the start of green of the rst stage would be at 17, 87, 157(sec)...and so on. Click
arrows to change its value. If all the values are set, click 'APPLY' to put them into eect. Press
'DONE' to nish this dialogue.
4.3.3 An Example for Optimisation:

If aim at nding the optimised plan, the function of 'Edit signal timing' is simple: edit the
minimum green and the parameter else in this dialogue will be dealt by the optimisation process.
The signalised T-junction example in 'Edit Signal Stage'(in section 4.2.12) is continued here:
Assume cycle time is 60(sec)(If not set, select 'Settings' from the main window, then select
'Global Signal Settings' to set cycle time), the minimum green for motorists is 5(sec) and that
of pedestrians is 6(sec). Set the minimum green of stream 1-5, representing motorists, to 5(sec),
and set the minimum green of stream 6 and 7, representing pedestrians, to 6(sec). Then press
'APPLY'. Note that the green bars here are for demonstration only. It represents only one of the
possible schemes. The optimised scheme (in section 6.5)can be seen only after the optimisation
process.
4.3.4 An Example for Single Run:

Note that if the purpose is to nd the optimised settings, then this section can be skipped. Before
doing the steps mentioned in this section, be sure that the purpose is to evaluate the performance
of specic scheme instead of trying to nd the optimised one.
Let us continue th T-junction example (in 4.2.12) Assume the cycle time is 60(sec)(If not set,
select 'Settings' from the main window, then select 'Global Signal Settings' to set cycle time).
Assume the intergreen requirements are same as the last section, then we go on with checking
the box 'Customised Green Duration' so that tab 2 is editable.
Click the 'Customised Duration' tab to specify the signal plan. Set the green duration as
12,9,9, and 6(sec), respectively. 'APPLY' it and the signal plan should be same as the gure.
Chapter 5
Single Run
5.1 A Single Run
The operation Single Run is not aim at optimising. Rather, It is aim at evaluating specic signal
timing. The signal timing are specied in each signalbox (by click 'Edit Signalbox' button and
right click on signalbox, then click 'Edit signal timing') either customised duration or [by default]
with equal green time on each stage.
5.2 Setting
To set the options, click 'Single Run' on the upper menu of the main window and then click
'Single Run Settings'. Choose the interval you want to simulate and the interval to calculate the
performance. There are various performance index (P.I.) you can choose: delay or total travel
time(TTT).
• Delay is the dierence between the time a driver desired to drive (correspond to freeow
speed) and the actual time he/she drives. In gure 5.1(a), the delay of single vehicle is
demonstrated: A vehicle enters the network at point a and nishes its journey in network
at point b, and it trajectory in time-space diagram is shown. The road user has a desired
speed (freeow speed has the averaged desired speed over all road users) of 50(kph), but
cannot achieve it due to trac conditions or the junction control. Thus, there is a dierence
in the time to nish journey at freeow and that of caused by other condition. The blue line
between two squares in the gure is the delay incur on that vehicle. During the calculation,
delays are sum up for all road users. The less delay, the better.
• Travel time (TT) is the time a road user spend in the network. In gure 5.1(b), the TT
of single vehicle is demonstrated: A vehicle enters the network at point a and nishes its
journey in network at point b, then the duration is the TT. During the calculation, TTT
sums up all TT over road users. The less TTT, the better.
Note that when selecting TTT as the objective function it favours the link with longer length. In
gure5.1(c), both links incur the same delay to the subject vehicle but the travel time is dierent.
Thus, if TTT is as the indicator, the road on the right hand has a worse performance. With this
property, cares must be taken when TTT is used.
Also note that P.I. is as an indicator to show the performance of the user-dened signal plan
(if the 'customised duration' box is checked for all signalboxes) and this plan is not the optimised
plan (unless it is coincidently the optimised one).
5.3 Go - Single Run

Click 'Single Run' on the upper menu (the menu bar of the main window) and then click 'Go-
Single Run'. Then the P.I. of the user-specied signal plan would be calculated. (Note again
that this is not the optimised one. It only runs the plan you just specied) If there is logical
error in the network, the reminding dialogue will show you how to x it (and try again).
5.4 The Result of Single Run

This will be shown after the calculation of single run. In addition to the plan, the corresponding
performance index (P.I.), the outow of each link of each time step, and the number of particles
58 CHAPTER 5. SINGLE RUN
Figure 5.1: Delay and Travel Time (a)Delay (b)Travel Time (c)A comparison of short and long
links
5.4. THE RESULT OF SINGLE RUN 59
of each link of each time step can also be looked up.

After running, the rst dialogue shows the P.I. Click on the button 'Show detail...', then the
timing would be shown. There are 3 tabs in the dialogue. The 2nd tab shows the number of
particles in links for various time steps. Select the time interval to render, then click 'Render' on
interested links or click 'Render All'. It is suggested to render the interested ones only because
a long render time it might be when rendering them all at once.
If not interested on graphical display, an alternative is to export into a csv (comma separated
value) le, which is readable by oce sheets. Deeper analysis can be based on these numerical
data. Click more '...' button on the northeast corner and then 'Export to...' to select the folder
to export. 'Quick export' can be clicked to generate 'report_for_single_run.csv'. Note that if
'report_for_single_run.csv' already exists it would be overwritten by newest operation.
It shall be mentioned again that this is the 'Run' of xed plan specied in each signalbox,
not the optimised one.
60 CHAPTER 5. SINGLE RUN
Chapter 6
Optimisation
6.1 Theory
The optimisation is based on genetic algorithm (GA). Genetic algorithm mimics the population
of species in the nature. It has mainly 4 stages: mutation, crossover, tness evaluation, and
selection. As we encode the signalised junction into gene representation (don't worry, this is
done and embedded in the software), we can do what GA can do over signalised network.
1. Mutation: gene in chromosome (a set of gene, represents an individual) mutates once in

a blue moon. But once mutated, the corresponding species has dierent ability to t the
environment. In signalised junction, signal plan are changed somewhere, correspond to the
mutated gene. For example: lengthen the duration of green for one of the controlled link
and shorten the green of other links.
2. Crossover: individuals exchange their gene when generating their children. Thus, crossover
mixes the genes of the two chromosome. But which of the parent passes certain gene depend
on chances. In signalised junction, signal plan are mixed to generate another feasible signal
plan.
3. Fitness evaluation: An individual ts the environment or not must be calculated. (In big
nature, taller giraes might survive well when leaves are in higher tree only but may be not
when there is starvation: they cannot feed themselves because the body is bigger than the
short ones) The plan is evaluated whether it has good performance or not. Performance
depends on user setting s(for example: lower delay or lower travel time).
4. Selection: Individual having better performance has higher chance to survive. But still note
that part of it depend on chances, not on deterministic. Better timing plans are survived,
meanwhile the bad timing are prone to be eliminated.
Generation after generation, the average performance will be better and we choose the best
individual after many generations. In signal optimisation, the best signal would come out in the
end.
6.2 Setting
To set the options, click 'optimisation' on the upper menu and then click 'Optimisation
Settings'. Choose the interval you want to simulate and the interval to calculate the performance.
There are various performance index (P.I.) you can choose: to minimise delay or to minimise
total travel time (TTT).
62 CHAPTER 6. OPTIMISATION
• Delay is the dierence between the time a driver desired to drive (correspond to freeow
speed) and the actual time he/she drives. Delay are sum up for all road users. The less
delay, the better.
• Travel time (TT) is the time a road user spends in the network. TTT sums up all TT. The
less TT, the better.
It is suggested to use delay minimisation scheme since TTT may be distorted when one of the
carriageway is extremely long, see section 5.2 for detail.
6.3 Go - Optimise
Click 'Optimisation' on the upper menu and then click 'Go-Optimise'. Then the best signal plan
would be calculated. If there is logical error in the network, the reminding dialogue will show you
how to x it (and try again later). Note that this function is perhaps the most time-consuming
operation.
6.4 The Optimised Signal Plan

The best signal plan in our signal plan pool will be shown to the user. In addition to the plan,
the corresponding performance index (P.I.), the outow of each link of each time step, and the
number of particles of each link of each time step can also be looked up.
After optimisation, the rst dialogue shows the P.I. Click on the button 'Show detail...', then
the best timing would be shown. There are 3 tabs in the dialogue. The 1st tab shows the signal
settings.
6.4. THE OPTIMISED SIGNAL PLAN 63
The 2nd tab shows the number of particles in links for various time. Select the time interval
to render, then click 'Render' on interested links or click 'Render All'. It is suggested to render
the interested ones only because a long render time it might be when rendering them all at once.
The 3rd tab shows the outow of links.

If not interested on graphical display, an alternative is to export into a csv (comma separated
value) le, which is readable by oce sheets. Deeper analysis can be based on these numerical
data. Click more '...' button on the northeast corner and then 'Export to...' to select the folder
to export. 'Quick export' can be clicked to generate 'report_for_optimisation.csv'. Note that if
'report_for_optimisation.csv' already exists it would be overwritten by newest operation.
6.5 Example: T-junction Continued

Let us continue the T-junction example, from 4.3.3.
6.5.1 Stage 1 Ineciency

As we already seen the forgotten stream to light up in stage 1. Let us still see its result, although
not ecient as expected.
The results are shown in gure 6.1(a)-(d). The performance index is 1,096 (thousand veh-
sec)(,which should be compared later). Some points should be noted from the optimised plan,
given the inecient plan, in gure 6.1(b):
1. Link 104 does not receive green in stage 1, which is the stream being forgotten. Thus, extra
waiting time is imposed on the vehicles in that stream.
2. The oset, is 36(sec)1 , so stage 1 begins at 36(sec).
3. Link 101 receives green in both stage 1 and stage 2, and since it should never conict to
itself, the green bar is of link 101 is connected automatically.
4. Interstage time between stage 2 and stage 3 is 6(sec)(End of stage 2 is at 4(sec) and begin
of stage 3 is at 10(sec)). Intergreen between link 101 and link 104 is 5(sec), less than the
interstage time, 6(sec), since the stricter intergreen of 6(sec) comes from the intergreen
between link 103 and link 104 of 6(sec), but not from the intergreen between link 101 and
others.
For the trac state correspond to optimised plan (given the inecient plan), refer to gure 6.1(c)
and (d). It can be seen that this scheme is able to deal with the given demand: By observing that
number of particles in every link and whirlpool exhibiting regular patterns instead of growing
without bound. This means that each object is able to discharge particles within a cycle.
6.5.2 Ecient Stage 1

If we follow the hints indicated when building signal stage, stage 1 would be more ecient as link
104 also receives green in the mean time. The result is shown in gure 6.2(a)-(d). In gure 6.2(a)
, it can be observed that the P.I. is now 1090(thousand veh-sec), which is 1.6 percent better. In
1 One may concern that there should be no oset for single junction. However, the oset 36(sec) is not reference
to any other junction but to the begin of simulation time.
6.5. EXAMPLE: T-JUNCTION CONTINUED 65
(a)
(b)
(c)
(d)
Figure 6.1: Optimised Result of T-Junction with Inecient Stage 1 (a)Summary (b) Optimised
Plan (c) Number of vehicle/pedestrian (d) Outow of vehicle/pedestrian
(a) (b)
(c) (d)
Figure 6.2: Optimised Result of T-Junction with Ecient Stage 1(a) Summary (b) Optimised
Plan (c) Number of vehicle/pedestrian (d) Outow of vehicle/pedestrian
Alt Staging Summary Perform. Index Improvem.

0 Inecient Stage 1 1,096,326 -
1 Ecient Stage 1 1,090,636 0.6%
2 Ecient Stage 1 and Stage 3, 4 Exchanged 994,465 9.3 %
3 Stage 1,2 Exchanged (stage 1 and 2 both ecient) 1,107,073 - 0.9 %
Table 6.1: Comparison of Performance of Alternative(Alt) 0-3
this case, the improvement is not so signicant since it is only one junction exist. Consider, if,
there is another junction (junction 2) downstream of link 101x, then the right turn green of link
104 has a higher probability to match the green of link 203, the link downstream of link 101x,
and the delay could be signicantly reduced.
From gure 6.2(b), one can observe that link 104 receives green in two stages (stage 1 and
stage 4) but not connected together, so would suspect if stage 3 and stage 4 are interchanged, the
green of link 104 would not suer the loss from making transition twice during its intergreen.2
Also note that exchanging stage 1 and 2 has the same function to connect the green bars3 , but
the detail is left for the reader to try out. The result of dierent settings are listed in table 6.1.
Note on the Inference and Result

There are some points to be discussed, and they are commonly encountered though only the
above case is focused on:
• It is inferred that alternative 0 is inecient and we make it ecient (to be alternative
1)by check the forgotten checkbox. However, the result is not as signicant as we thought.
2 Not only the performance loss, which can be evaluated by this software, but also the probable rear-end accident
it might cause, which should be evaluated by other tools.
3 But it also has the adverse eect: the spillback due to the waiting vehicles of link 121 does not occur before
exchanging
6.5. EXAMPLE: T-JUNCTION CONTINUED 67
The inference is correct, the result proved it correct, but its amplitude must be executing
optimisation again to examine.
• It is inferred that alternative 2 is better than alternative 1 because one of green bars are
connected to reduce wasted transition time. Still, its amplitude (improved 9.3%) is known
only after executing optimisation again.
• It is inferred that alternative 3 is better than alternative 1 because one of green bars are
connected to reduce wasted transition time. However, the inference is correct but the result
shows a contradiction: it deteriorates by 0.9%. This is because we have a limited view on
the global states: Here, alternative 3 has a spillback eect that is underestimated. Situation
like this is not uncommon: The saturation owrate seens perform better at stop line when
we calculated by hand (or by experience) but we are naive in estimating spillback/blockage
at upstream, resulting low pump into the stop line. Thus, the overall performance worsens.
We have a global view only after a complete execution of optimisation.
So, the value of computer-aided tool is now apparent that human calculation is limited to local
state but can be conrmed, be conrmed but with an oset by other hidden eects (in the above
example, it is spillback of alternative 3), or rejected if we have the global view from simulation
(including single run/optimisaiton).
Final Note on the Optimisation

In this example, the subject junction and the whole network undersaturated, but note that even
if under the best signal plan the oversaturation is not guaranteed to be dissolved! This is because
even the best timing cannot resolve the overwhelming demand if it is too large.4 Under such
condition the best signal scheme is only able to alleviate the problem but not remove it. Under
that circumstance, the authority is suggested to review the problem in higher perspective: the
transportation planning perspective5 .
4 If Y-value is greater than 1 no matter how grouping arrangements are made, then it is conrmed that this is
an oversaturated junction.
5 For example, evaluating commuter trains, trams, bus services, or road pricing to shift the demand of auto-
mobiles.
Chapter 7
Document Outputs
7.1 Overview
Finishing run/optimsation, there are three kinds of outputs:
1. Output of macroscopic ow states;
2. Output of Level of Service (LoS, LOS1 ); and
3. Microscopic network output
They are located at 'Show detail...' button and more '...' button after run/optimisation.
7.2 Output of Macroscopic Flow States

The states of macroscopic ow will be output as a csv le, which can be opened by spread sheet
software (for example, Excel of Microsoft, CSV buddy2 ...etc). The content of output includes:
Performance Index (TTT or delay), number of particles (vehicles/pedal cycles/pedestrians) in a
link, and ow of a link.
7.2.1 Example: Output of Monkok Case

1. From 'library', select case of 'Monkok'. Set the cycle time as 80(sec). Objective function
set as 'minimise delay' with calculation time of 900(sec). Do 'optimisation', then we can
obtain the optimal timing as:
1 To be consistent with language use in this literature, it should be 'LoS'. However, this concept comes from
U.S. standard, which use the 'LOS' version, so it is abbreviated 'LOS' instead of 'LoS' throughout this book.
2 Where there this book mentions 'CSV buddy', they are for introductory purpose only. See CSV buddy on its
ocial site at: code.jeanlalonde.ca/ahk/csvbuddy
70 CHAPTER 7. DOCUMENT OUTPUTS
2. Select more '...' on the upper right corner. Select 'Export Report to...'
3. Name a lename of the csv le, for instance 'Monkok01.csv' (If 'Quick Export Report'
is selected, then the le would be named automatically as 'for_single_run.csv' or 're-
port_for_opt.csv' and in the same folder as Sigmix.)
4. The exported can be opened with a spreadsheet:
5. The content of csv is: (i) number of particles (vehicles/pedestrians/pedal cyclists) in links
and (ii) ow of links. The values are recorded according to their evolution with time. This
provides transportation specialists to examine the result.
7.3. OUTPUT OF ARTETIAL LOS 71
Table 7.1: Type of Conclusion and its index

Index at Various Sites
Type Purpose
Site Index
P.I. Professional Use (unlimited) Total Delay
(unlimited) Total Travel Time (TTT)
LOS Quick Conclusion Isolated Intersection (Junction) Control Delay to rank A-F
Segment Travel Speed/FFS* to rank A-F
Urban Street Travel Speed/FFS* to rank A-F
Arterial (Primary Roads)** Travel Speed to rank A-F
*FFS: Free ow speed
** Dened in HCM 2000
7.3 Output of Artetial LOS
Note! This function is available only after version 1.0 of Sigmix. If your version is below 1.0, the
relevant function is not provided.
7.3.1 Overview
Authorities3 , no matter public sectors (delegating contractors for signal re-timing) or private sec-
tors (delegating contractors for trac impact analysis) may not be interested in trac operations,
but only do care about the conclusion. The conclusion can be categorised as 'for profession', that
is, performance index, or 'for decision maker', that is, LOS. Since trac engineers must demon-
strate the result in brevity to the politicians and the public, the 'lazy index' such as LOS exists.
LOS is developed in the U.S., so here the Highway Capacity Manual (HCM) of U.S. is quoted:
LOS is also considered a performance measure. It is computed for the automobile,

pedestrian, bicycle, and transit travel modes. It is useful for describing segment
performance to elected ocials, policy makers, administrators, or the public.
([2], page 17-3) So, a trac specialist is suggested to acknowlege his/her profession: For internal
evaluation between the specialists, total delay or total travel time should be used. On the
contrary, the LOS is aim to explain to non-professions, see Table 7.1. For total delay and total
travel time (TTT), refer to 5.2. In this section, output of LOS is discussed. First of all, how the
standard of LOS is dened is presented.
7.3.2 The U.S. LOS

The standards LOS in U.S. is based on HCM, which has newest version of HCM 2010[2], having
many big changes in it comparing to previous versions. If the research range is approximately
within a block, use the 'Segment'; if a primary road in urban street is to be investigated, apply
'Urban Street'. According to [2], summarise as below:
Segment: Approximately a size of a block. The road between two junctions (intersections).
Urban street: Analyse the performance of a street, connected by multiple segments of street.
Segment
The details rules4 :
1. A segment can be composed of a range between two signalised junctions (signalized inter-
sections).
2. If in the middle of segment, another junction is encountered, this junction must not be
signal-controlled.
3. If in the middle of segment, another junction is encountered, then the segment can be
regard as two segments (or not).
3 The European English is used throughout the book. However, the LOS is developed in the U.S., so in this
chapter some of the topics are styled in U.S.
4 Rearrange of sentence is implemented for ease of reading, so the texts and sentences are not completely same
as in HCM 2010.
Figure 7.1: Demonstration of 'segment'. The most west segment is named segment A; the range
between junction 1 and junction 2 forms segment B; the range between junction 2 and 4 forms
segment C; and the most east segment is segment D.
4. If it is a two-way (instead of one-way) street, then two of the directions must be in the
same segment.
To demonstrate these points, refer to Fig 7.1:
1. Signalised junction 1 and 2 forms segment B.
2. Junction 3 is uncontrolled for the subject primary road (no give-way or stop sign for it) so
the segment is not cut by junction 3. Thus, segment C is ranged between junction 2 and 4.
3. The trac specialist can also choose to cut segment into segments at junction 3 (if the
trac specialist considers that the ows in subject primary street is strongly inuenced by
the way-giving street)
4. Four segments in the gure (segment A-D) are enforced to take into account both directions
of the street. In HCM 2010, it is dened in this way because it recognises that: It is not
possible to enhance one direction of trac without harming the opposite way.
Urban Street
The functionality of urban street is to provide mobility. The ows in primary street should
be kept at higher (relative to the accessibility an alley would provide: The door-to-door nature,
including door of homes, door of stalls and doors of schools) speed and this speed is measured
in straight movements for at least certain length. The length considered into evaluation is the
length that across the town centre. The regulation in HCM 2010[2] is:
'An urban street facility is a length of roadway that is composed of contiguous urban street
segments and is typically functionally classied as an urban arterial or collector street.' ([2], page
16-5)
For example, in Fig 7.1, an urban street is composed of 4 segments, that is, segment A-D.
Level of Service
As segment and urban street are dened, HCM uses travel speed as measure of performance.
See Table 7.1, no matter the subject facility is segment or urban street, the free-ow speed
and travel speed must be obtained rst so that the ratio of it can be computed to derive LOS.
Note! New HCM 2010 is dierent from the previous version (HCM 2000): in the new version,
the streets no longer being categorised as class I, II, III, or IV, but they are calculated according
to FFS directly.
Note! If there is a v/c ratio in HCM 2010, it means demand to capacity ratio, instead of volume
capacity ratio ([2], p.17-6). This is due to the fact that the volume-to-capacity in congested and
in uncongested scenario might be the same, cause ambiguity. So it should demand capacity ratio
should be used to be clear.
Table 7.2: LOS of segment and urban street categorisation in HCM 2010 (Source: [2], p.16-8,
p.17-7)
Level of Service
Travel Speed as Percentile of Free Flow Speed (v/c)* ≤1.0 v/c >1.0
> 85 % A F
>67% - below (including) 85% B F
>50% - below (including) 67% C F
>40% - below (including) 50% D F
>30% - below (including) 40% E F
Below (including) 30% F F
*v/c: Demand to capacity ratio
Note! Demand capacity ratio is designed as a threshold value but not a index: If demand exceeds
capacity, i.e. demand capacity ratio >1.0, no matter what speed it might be, it is categorised as
LOS F without compromise.
Note: Regulation too Strict
Note! American standard might be too strict. In Asia, LOS A, B might mean overdesigned but
not servicing user at a good level. Level of Service C is already an excellent performance.
It should be noted that in Europe and Asia, the U.S. standard might not be directly suitable
since the American standard is too strict. Since land use in U.S. is rather slack, but the densely
populated Asia and Europe is not, leading to the standard unsuitable. (1) Consider a road
with free ow 55 (kph): Under the standard of HCM 2010, as the speed below 17 (kph), it
is categorised as LOS F; as the speed below 39 (kph), it is categorised as LOS C. However, in
urban area, if half of the time is spent in waiting the change of signal, on average, the speed is
roughly as low as 29 (kph), so LOS C is rather reasonable. (2) The capacity of roads with LOS
A, B is over-supplied with the ow actually on the roads under the prediction. (3) Singapore has
the best trac performance in Asia, but their average speed in town is 28.9 (kph)[4]. Therefore,
LOS C can be regarded as super performance. Thus, trac specialist must not be upset about
the performance of LOS C-F for the subject road network, because that kind of LOS is based on
too strict a standard from the U.S. If the public or politicians criticize for too low the LOS, the
specialist is advised compare the result to that of Singapore to persuade them the good result
from the hard work of we transportation specialists.
7.3.3 Quick Export LOS Date
Quick Export is for quick view. The exported format is based on links (instead of segments
or urban streets, which have standard denition in HCM). It reveals the link travel speed and
LOS based on HCM 2010. The output format can be seen in Fig 7.2. Note: this quick result is
prone to demonstrate local results. Since the calculation of quick result is based on links, which
probably having length as short as 5-200 (meter). Comparing to segments have length of a
block or arterials and urban streets have length of kilometre(s), links are so short that it may
generate local results which comes out extreme values- LOS A and F, see Fig 7.2. Thus, it is
suggested that the 'Quick Export' is for fast reference only. If a full report of Level of Service is
desired, customise the report format (by 'Customised LOS Output') and dene your segments
satisfying the denition in HCM 2010: Refer to Section 7.3.4.
Note! 'Quick Export LOS Data' has a local result of LOS for links, whose length might not full
the denition of segment in HCM 2010. Thus, the result might comes out with extreme values
(LOS A, LOS F). For full LOS analysis, use 'Customised LOS Output'.
Figure 7.2: 'Quick Export LOS Data'. (Since the format is link-based, it has the property of
strong locality, which generates extreme values, A and F, easily. It i suggested this function for
quick reference only)
In addtition, for pedestrians and pedal cyclists, their travel speed is provided, but not the
LOS.
Note! Sigmix provides LOS of motor vehicles. However, the counterpart of pedestrians and pedal
cyclists is not given since the index of measurement of their level of service has not reached a
consensus. Hence, only their travel speed is provided.
7.3.4 Customised LOS Output
'Customised LOS Output' supports links to be grouped as segment or urban street fol-
lowing the denition in HCM 2010.
Flow Chart - HCM

The ow chart of 'Customised LOS Output' can be depicted in 7.3. After the run/optimisation
in the main window, the 'Customised LOS Output' can be selected. When doing this, it is
required to dene which of the links form the self-dened segment and which of the segments
are grouped to be an urban street: These user-dened informations must be written in a
conguration le. With the above elements, it can be output as a LOS le- formatted as csv.
Syntax of Conguration File

The Syntax of conguration le is:
Begin_LOS
LOS_base:<HCM version>::
Segment_name:<segment naming>:is_composed_of:<link1>[,<link2>][,<link3>][......]
[...other denition of segment...]
[Street_name:<urban street naming>:is_composed_of:<segment1>[,<segment2>][,<segment3>][......]]
[...other denition of urban street]
End_LOS
When saving the le, the le extension must be .loscong
(For example, open the notepad, select the extension as '*all les', and type the lename
'abc.loscong')
Figure 7.3: Flow chart for exporting Level of Service

(Figure: Greenwave Octopus. File licensed under : Creative Commons Attribution Share Alike 3.0 Unported license.)
Maybe it would be easier to get the idea of the syntax if we look at some examples in the
next section rst, then review the above syntax.
7.3.5 Example of an One-way

Make a one-way by following the detailed steps:
1. From 'library', load the 'Monkok' Example. Cycle time set to 80 (sec). The map is:
2. Edit the LOS conguration le (*.loscong):
(a) Open the editing software, for example the 'notepad'.

(b) Refer to the network: from east to west is an urban primary road: link1, link2, link4,
link8, link10, and link13.
(c) (Whether link5 or link11, which are additional turning lanes, are categorised in the
abovementioned road depends on the judgement of trac specialists)
(d) Name these links as the segments of HCM 2010:
i. [Name as segA] Link1 must be in a segment composed of only link1 itself, since
rules in HCM 2010 said that signalised junction (signalized intersection) must be
boundary of segments.
ii. [Name as segB] Then, link2 and link4 must be in the same segment since the
road geometry at the connection of link2 and link4 is just a simple road widening
that a turning lane link5 begins. Thus, they should regard as a whole segment
until encountering another junction downstream.
iii. [Name as segC] In the same manner, link8 and link10 compose same segment.
iv. [Name as segD] Lastly, link13 exits the network. Since junction 3 separates it
from other part of the network, it cannot be in the same segment with other
links. So link13 must be in a segment composed of only link13 itself.
(e) Name the urban street as 'ArgyleSt' (This street really exists in Monkok, Hong
Kong): it consists of segA, segB, segC, and segD.
(f) Type the following message from the info described earlier:
Begin_LOS
LOS_base:HCM2010::
Segment_name:segA:is_composed_of:link1
Segment_name:segB:is_composed_of:link2,link4
Segment_name:segC:is_composed_of:link8,link10
Segment_name:segD:is_composed_of:link13
Street_name:ArgyleSt:is_composed_of:segA,segB,segC,segD
End_LOS
(g) Save as Ex1.loscong (or other lename instead of Ex1)
3. 'Go optimise' as other networks.
4. Obtain the following signal timing:
5. Select 'Show Detail ...', and click the more '...' button on the upper right corner.
6. Select 'Customised LOS Output'.

7. If not already selected a LOS conguration le (*.loscong), a dialogue window will remind
us to load. Click the 'Change', browse the les and select the *.loscong le we just edited.
8. Click 'APPLY and EXPORT', and a reminder of the lename will be shown:
9. Info about successfully exported le.
10. If the output csv is opened by spreadsheet software (By default, 'customised_ Level_of_Service_report.cs
the result would be:
11. Some properties can be observed:
(a) The level of service of the urban street (according to HCM 2010 in this example) is
LOS E, which looks bad. However, if examine the stats carefully, one would observe
it is not true to judge it an 'E' level: An average travel speed of 15 (kph) is in fact a
excellent value in any metropolitan area. The standard of North America is too strict.
(b) LOS of Segments is: LOS F, F, B, and A, respectively, showing diversity. Dening
urban street as a composite of those segments, the index is more accurate to reect
the overall performance of the signalised network condition for drivers driving from
segA to segD: travel speed of 15 (kph).
7.3.6 Syntax Details

We have seen how example works in previous subsection. Now we introduce a more detailed
syntax.
Typewriter, like this, means keywords must be completely matched. The unmatched words
will not be identied legal by Sigmix.
Italic-in-an-Angle-Brackets, <like this>, means enter words here by hint.
In-a-Bracket, [like this], means optional phrases that is not required, but can be entered if the
user considers it necessary.
Begin Mark
Begin_LOS
Must be shown for marking the beginning of the content of the conguration le. (It can
be interpreted as: You can comment on the le with any other information, which will not
considered by computer as eective input but will be information for human eyes, prior to the
this mark.)
Highway Capacity Manual Version

LOS_base:<HCM version>::
The supported versions of HCM are: HCM 2010 (American standard) and THCM 2011
(Taiwanese standard). Legal examples show in the following:
1. LOS_base:HCM2010::
2. LOS_base:THCM2011::
Two commas must be entered. This is the rule of LOS conguration le.
Dene a Segment
Segment_name:<Name the Segment Name>:is_composed_of:<Link Name 1> [,<Link Name
2>][,<Link Name 3>][,<Link Name 4>]
1. At least one link should be included (otherwise it is empty).
2. Name of link must be in one of the link name appears in main window (*.nwk) (otherwise
the subject link is not dened).
3. Name of segment is up to your choice.
4. Please make sure that the segment must full the denition in HCM 2010.
5. Depending on how many segments you are investigating, the syntax to dene segment
can be repeated many times to dene many segments. For example, segA, segB, segC,
and segD are segments to be investigated, and then the phrase must be repeated 4 times.
Dene a THCM Arterial

It is legal to dene a THCM[5] arterial. Please refer to the Mandarin version of this manual or
contact the author by email to derive further information.
Dene an Urban Street

[Street_name:<Name the Urban Street>:is_composed_of:<Segment Name 1>[,<Segment Name
2>][,<Segment Name 3>][,<Segment Name 4>...]...]
The whole phrase for urban street is optional: If the only subject is segments, then the
syntax here is unnecessary. If investigation of urban street is truly needed, then the rules would
be:
1. At least name one the segment name in this urban street.

2. The name of segment the must be dened previously in the denition of segment.
3. Name of urban street can be dened by user (you).
4. Please check the all the self-dened urban streets full the denition of urban street in
HCM 2010.
5. Depending on how many urban streets you are investigating, the syntax to dene urban
street can be repeated many times to dene many urban streets. For example, Main St.
and Fifth Ave. are urban streets to be investigated, then the phrase must be repeated 2
times.
End mark
End_LOS
Use this mark to end the denition of LOS conguration le.
7.3.7 Example of Two-way Street

Now an example of a two-way street is demonstrated. It can be loaded from 'library': (Since most
detailed steps are already demonstrated in the previous example, in this example only sketches
of steps are provided)
1. Load the case of '4 Junctions on Arterial'; set the cycle time as 90 (sec) and the simulation
time as 900 (sec). An outline of the road network can be seen in the gure:
2. Do 'Optimisation'. Here is the result:

3. We are eager to know the Level of Service of the primary road that has a west-east direction.
Set its conguration as:
Note! Rules in HCM 2010 regulates that to investigate a segment, if it is a two-way (instead of
one-way) road, then both directions of trac ow must be evaluated together.
Based on the above concept, link6 and link7 compose a segment called segA, and this
segment must includes link9, too. For segB, segC, segD, and segE, the same manner
applies.
Begin_LOS
LOS_base:HCM2010::
Segment_name:segA:is_composed_of:link6,link7,link9
Segment_name:segB:is_composed_of:link3,link16,link18,link1
Segment_name:segC:is_composed_of:link14,link25,link27,link12
Segment_name:segD:is_composed_of:link22,link35,link36,link20
Segment_name:segE:is_composed_of:link33,link30,link31
Street_name:MainSt:is_composed_of:segA,segB,segC,segD,segE
End_LOS
4. The Level of Service we obtained is LOS C. In fact, it's far above the average. The travel
speed is as high as 25.5 (kph). Since HCM regulates LOS too strict, the result seems not
so well in the appreance (LOS C) but it is as a matter of fact an excellent performance.
In Asia, the travel speed of urban street of 25.5(kph) should be considered a super
performance, just less than 28.9 (kph) of Singapore, which has most smooth trac
in Asia. Trac specialist must have this tip: to be condent with the result we
make by comparing with Singapore, but not to be confused with the too strict a
standard of HCM 2010, whose LOS is originally designed for non-specialists.
Chapter 8
Output as Microscopic
8.1 Overview
Sigmix networks can be output as microscopic networks as demonstrated in gure 8.1. Figure 8.1
(a) shows a Sigmix network, while (b) shows a Sumo (to be introduced later) network. Output
as microscopic model might be based on one of the following reasons:
1. For display purpose: Publics, government ocials, clients who are not trac specialist
regard simulation as a 'cool' tool, but might not be interested in accuracy. They want to
see some 'cars running on the screen'1 , then the module here fulls their need.
2. For microscopic validation: Trac specialists who are cautious would like to see microscopic
validation in addition to macroscopic computations. Hence, the module here provides the
functionality for specialists.
8.2 Microscopic Simulation

Trac ow simulation can be categorised as these two kinds (others including 'mesoscopic',
'cellular automata', ...etc. are not discussed here):
1. Macroscopic simulation: Models the bulk behaviour of vehicles. States include ow (or
ux), density, and average speed. Parameters include capacity, jammed density, and free-
ow speed, etc.
2. Microscopic simulation: Explicitly models the states of each vehicle. States includes vehicle
position, speed, etc. Parameters are ne details include desired speed, desired car-following
distance, gap acceptance at way-giving point, acceleration capability, brake capability, level
of consideration, etc.
Sigmix is itself software with macroscopic simulation and signal optimisation. When computing
the signal, in general software has to apply macroscopic simulator in it to create satised result
due to the computation speed. However, in some occasions as mentioned previously, trac
specialists do need microscopic simulation to see the dynamics of each vehicle. Select 'Export as
Microscopic Xml', then the exported les obey the format of Sumo.
8.3 Sumo
Sumo 2 is short for "Simulation of Urban MObility"[6], which is a freeware under GPL licensing.
Its network data consist of multiple Extensible Mark-up Language (XML) les. Sumo reads these
les and micro-simulate according to it. In addition to xed time signal, adaptive signals can be
simulated on Sumo.
1 Of course, specialists know that this is a redundant feature. Because some software that has accurate simu-
lation do not necessarily have graphical user interface (GUI).
2 At anywhere in this book, if 'Sumo' is mentioned, it is for purpose of introducing. It is developed by German
Space Centre (DLR, http://www.dlr.de/)
84 CHAPTER 8. OUTPUT AS MICROSCOPIC
(a)
(b)
Figure 8.1: Macroscopic and microscopic: (a) Sigmix, as an example using macroscopic modelling;
(b) Sumo, as microscopic counterpart.
8.4 Output
When exported, there would be multiple xml les:

<Filename>.edg.xml
<Filename>.nod.xml
<Filename>.sumocong
<Filename>.rou.xml
<Filename>.turns.xml
Note! This function is available only after version 1.1 of Sigmix. If your version is below 1.1, the
relevant function is not provided.
8.5 Example: Isolated Junction

A simple case is demonstrated here: Isolated signalised junction with two crossing one ways.
Capacity is 4000 veh/hr with 2 lanes for each link. The demand is 3000 (vph) for primary road
and 200 (vph) for secondary road. Turning ratios are all 50% for each O-D pair. The links
entering into junction are signal-controlled. Transform this network as a Sumo-readable le, and
its steps are as:
1. Preparation: Please make sure the Sumo is installed beforehand3 , the download link can
be found in http://sumo.dlr.de
2. Create the network topology as following gure:
3 Sorry, but the Sigmix software cannot include Sumo directly due to copyright reasons. Sumo is developed by
DLR with GPL licensing. Thus, Sigmix has no right to include Sumo in our package directly.
8.5. EXAMPLE: ISOLATED JUNCTION 85
3. 'Go - optimise' with objective function of minimising Delay ('min Delay') with calculation
time of 3600 (sec), then the result is:
4. Click 'Show detail...', the detailed result is:
5. Click more '...' button and select 'Export as Microscopic Xml'.
6. Now a dialogue jumps out. The conguration le and the name of output le can be
selected here. In this example, leave conguration le empty, and set the name of output
le. The default value of the name of the output le is 'sumoFile'. Click 'APPLY and
EXPORT'.
7. If successfully output, the following shows:
8. And the following dialogue shows ('Preparing Data'), and command line code is given as:
9. Please copy the code (Select all and press Ctrl+C) (Note! The message would be given
according to the settings of the example by user. It might be dierent from the following)
10. Open the 'Command Prompt'. In a Windows-based system, it is at 'Start' > 'All Pro-
grammes' > 'Accessories' > 'Command Prompt'. Right click on the Command Prompt
for paste. (Note! the information would show dierently according to the settings, so the
screen image might be dierent to the following gure. The example is assumed that the
Sigmix is installed under the folder D:\myPython\Canvas. )
8.5. EXAMPLE: ISOLATED JUNCTION 87
11. Make sure that the above steps are complete, then click 'DONE', then 'NEXT'.
12. Copy another line of code and paste it to command prompt again:
13. After pasting, the Sumo will initiate, meaning the export of the xmls works ne. (Otherwise
make sure the Sumo is properly installed)
14. In Sumo, it is suggested to adjust the 'Delay' of animation to 100 (ms), or the play speed
would be too fast to be seen by human eye. Press 'Play' to watch.
Figure 8.2: Link fusion: (a)Original junction; (b) macroscopic Sigmix with additional right
turning lane named link2 and straight lane link1; (c)Sigmix transformed into Sumo: should be
explicitly instruct it via s2s le that link2 and link1 should be combined as same street to become
a Sumo edge.
15. Vehicles can be seen in the network:
16. For the export of the microscopic performance of Sumo (After the simulation of Sumo is
complete), please see sumoFileAggregateResult.xml:
Following data can be observed:
<lane id="link1_0"... waitingTime="24524.00"...>
<lane id="link1_1" ... waitingTime="16120.00"...>
<lane id="link3_0" ...waitingTime="1759.00...>
<lane id="link3_1" ...waitingTime="2393.00"...>
The above data reveals that the delay of lane 0 (count from rightmost) of link1 is 24,524
(sec). That of lane 1 of link1 is 16,120. The delays of lane 0 and lane 1 are 1759 and 2393
(sec), respectively.
8.6 Link Fusion

Since the macroscopic and microscopic have dierent foundations of modelling topology, the
macroscopic Sigmix transforming to microscopic Sumo requires additional information when
encountering the situation for lane utilisation on same physical street.
8.6.1 Same Edge

As shown in gure 8.2(a), when entering a junction, there is a additional right turning lane. It
must be described as in 8.2(b) for Sigmix. However, in microscopic Sumo, we have to explicitly
instruct Sumo via s2s le that link2 and link1 should be combined as same street to become a
Sumo edge. The result in Sumo can be seen in 8.2(c).
8.7. EXAMPLE: LINK FUSION 89
Same Edge Declaration

For gure 8.2(b), the same edge declaration means to type in the following phrases in a *s2s le:
Begin_SIGMIX2SUMO
CombinedLinksAsEdgeFromKerbside:link2,link1
End_SIGMIX2SUMO
When typing in the links to fuse, they must follow the order of from right lane to left lane. In
this example, link2 is the right turn lane and link1 represents the straight-going lanes, so link2
has to be declared rst.
Note! When fusing the links as same edge, the order from rightmost to leftmost must be followed.
If not declaring in this way, the Sumo will show unexpected lane overlapping.
8.6.2 Syntax of Link Fusion

The syntax can be easily identied from last subsection, but is still listed here:
Begin Mark
Begin_SIGMIX2SUMO
Same Edge Declaration

CombinedLinksAsEdgeFromKerbside:<name of link in right most>,<name of link in 2nd right
most>[,name of link in 3rd right most>...]
...
End Mark
End_SIGMIX2SUMO
8.7 Example: Link Fusion

The example in this section is from 'library' load '4 junctions on arterial'. Since the detailed
steps are introduced earlier, the following steps are in outline:
1. Load from 'library':
2. Refer to the network topology, link1 is the straight-going and right-turning shared lane,
and link2 is the additional left-turn lane. link1 and link2 on the same street, and they
should be fused as a Sumo edge. Other 7 pairs including link7-link8 edge applies the
same manner. Open a text le, name it as 4junctionsOnAeterial.s2s (other lename is
possible), and type in the following text: (Remember that the links must be ordered from
rightmost to leftmost)
Begin_SIGMIX2SUMO
End_SIGMIX2SUMO
Note! Fusing the links as same edge, the order from rightmost to leftmost must be followed. If
not declaring in this way, the Sumo will show unexpected lane overlapping.
3. 'Go optimise' the trac signal ('min TTT' with simulation time of 3600(sec)). After the
result comes out, click 'Show Detail...'>> click more '...' and then 'Export as Microscopic
Xml'
4. Now, a dialogue titled 'Sigmix to Sumo settings...' comes out, select 'Change' to load the
s2s le we created previously.
(a) The dialogue that can select le to input (*.s2s) and the output lename:
(b) Select a *s2s le:
(c) After selecting the *s2s le:
5. Click 'APPLY EXPORT', and after the hint for successful output, then copy the following
code into the command prompt.
8.7. EXAMPLE: LINK FUSION 91
6. If 'success' appears in the command line, then do the next step. Else, press enter.
7. (You must be sure the last step is nished before doing this) Back to Sigmix, click the
'DONE pasting', and then 'NEXT'. To following code would appear:
8. Copy the above code, then paste it to command line:
9. Now, the Sumo has the network showing as:

10. In Sumo, the delay of play set to 100 (ms) so that it is not too fast for human eye not to
see. Press 'play' of animation:
11. After the microscopic simulation in Sumo is nished, the le 'sumoFileAggregateResult.xml'
can be opened to see the performance.
From the above case, one can make comparison of the result of 'Run' and 'Optimise' in micro
simulation prospective:
Result of 'Run' in Sumo: waiting time of link6 is 10,271(sec), of link30 is 1,311(sec).
Result of the optimised signal in Sumo: waiting time of link6 is 3,861(sec), of link30 is
573(sec)4
Renement of Macroscopic Model
The contents in this subsection do not aect the user operation of the software. For fully practical
purposes, this subsection can be skipped. This subsection deals with advanced problems for senior
engineers.
The previous two sections mention the microscopic Sumo is able to examine whether the
macroscopic Sigmix is delicate enough to model the case under investigation. Senior engineers
reading this book might nd that the trac in crossing streets should be modelled about its
opposed turn in Sigmix, or its performance would not be the same as in microscopic Sumo.
Later, the macroscopic model in Sigmix will be rened in section 8.9.
4 But the performance of crossing roads deteriorates due to (1) less demand to be considered comparing to
the main road in the overall optimisation; (2) modelling in Sigmix [in this case] does not take into account the
opposed turn during green for cross roads.
8.8. PRIORITY 93
8.8 Priority
8.8.1 Sumo Connection
Note the name dierence. In Sigmix, the connector connects the links;
In Sumo, the connection connects the edges. To reduce ambiguity, whenever the connection is
mentioned, it is shown as 'Sumo connection'.
The priority appears in two scenarios: (1) Pure priority control: the stops and give-way signs.
(2) Opposed turn in signalised junctions including giving way to the opposing trac and opposing
pedestrian. In these cases, the ows in the connectors of the opposed streams is dominated by
vehicles with higher priority of the opposing stream, as in subsection 3.3.5. When converting to
Sumo, the priority is set automatically as the priority in Sumo connection.
8.8.2 Merging Weight

When merge into the same link, in Sigmix there is a 'Merging Weight' parameter to describe the
weight of entrance for lane reduction or other merging situations. When converting to Sumo, the
priority is set automatically as the priority in Sumo edge.
8.9 Renement of the Previous Example

In section 8.7, it is mentioned that one of the additional functionality of microscopic Sumo is to
examine whether there is insucient modelling (or not) in Macroscopic Sigmix. We can rene
the case of '4 junctions on arterial' and to model the fact of 'left turns have lower priority and
must be aected by the oncoming cars' for crossing streets.
1. In the network topology, at wherever there is left turn vehicle required to give way to the
oncoming vehicle, create a short link (and relevant connector) branching out, and assign the
downstream connectors of these branching-out links to give way to the oncoming straight
movements. The topology is:
(a) Delete the connector at the downstream of link4, link10, link23, and link28:
i. Delete connector [link4->link9], connector [link4->link11], and connector [link4-
>link3].
ii. Delete connector [link10->link9], connector [link10->link5], and connector [link10-
>link3].
iii. Delete connector [link23->link22], connector [link23->link27], and connector [link23-
>link29].
iv. Delete connector [link28->link22], connector [link28->link27], and connector [link28-
>link24].
(b) At downstream of link4, insert two links: link38, link39 (for left turn).
(c) At downstream of link10, insert two links: link40 (for left turn), link41.
(d) At downstream of link23, insert two links: link42, link43 (for left turn).
(e) At downstream of link28, insert two links: link44 (for left turn), link45.
2. Create new connector; the turning ratios must be modied. To maintain the original
turning ratio (10:10:10 for left/straight/right, respectively), the new settings must be:
(a) The 'Turning Ratio' of connector [link4->link38] set as 20 (including ratio of straight
and right turn).
(b) The 'Turning Ratio' of connector [link10->link41] set as 20 (including ratio of straight
and right turn).
(c) The 'Turning Ratio' of connector [link23->link42] set as 20 (including ratio of straight
and right turn).
(d) The 'Turning Ratio' of connector [link28->link45] set as 20 (including ratio of straight
and right turn).
3. The priority (It is demonstrated how in subsection 3.3.5)
(a) Connector [link39->link3] (the left turn) is opposed by connector [link41->link5] (the
opposing oncoming trac).
(b) Connector [link40->link9] (the left turn) is opposed by connector [link38->link11] (the
opposing oncoming trac).
(c) Connector [link43->link22] (the left turn) is opposed by connector [link45->link24]
(the opposing oncoming trac).
(d) Connector [link44->link27] (the left turn) is opposed by connector [link42->link29]
(the opposing oncoming trac).
4. The 'Simulation Time' is set to 3600 (sec), and the optimal (of TTT) result is 180,025.
The optimal signal timing is:
8.10. PEDESTRIANS AND PEDAL CYCLISTS 95
5. According to this timing, run Sumo again, the answer is 190,782(sec). The answer from
Sumo is almost the same as the result from Sigmix. It is demonstrated that the macroscopic
Sigmix can be improved by rening the network via the help of microscopic Sumo, and then
the rened calculation of optimal signal timing can be achieved 5 .
6. Enjoy the animation in Sumo: See how progression works.
8.10 Pedestrians and Pedal Cyclists

Since Sumo is mainly for vehicle simulation instead of pedestrian, its support to pedestrian is
relatively low. Since pedestrian in Sumo cannot be transformed with the same performance under
same demand, the following principles are the alternative rules to follow:
Note! When converting to Sigmix from Sumo, the number of pedestrian does not full the Sigmix
settings.
1. The pedestrian demand is divided by 10. State in another way, pedestrian in Sumo =
(pedestrian in Sigmix / 10 )
2. Freeow of pedestrian is 2.5 times quicker. State in another way, pedestrian FF in Sumo
= (pedestrian FF in Sigmix x 2.5)
8.11 Miscellaneous
The contents in this section do not aect the user operation of the software. For fully practical
purposes, this section can be skipped. This section deals with advanced problems for senior
engineers.
Support of Unicode
Facts are:
• Sigmix supports Unicode. The Han character (Han-Zhi, Han-ji, Kanji, Hanza, Chinese
Characters), Japanese Characters, Greek Letters, Hebrew Letters, etc.
• Sumo does not support Unicode. Only 26 Latin letters (A-Z, a-z) and 10 number digits
(0-9) are supported. The blank cannot be appeared in naming.
• However, when transforming from Sigmix to Sumo, there is an automatic mechanism to
deal with it. Thus, the user (you) is not required to change namings manually.
The so-called mechanisms are: When transforming from Sigmix to Sumo,
• The Unicode character would become 'Unic<Unicode character>'
• The blank would become 'WHSP'
For example:
• The link named 'Grüne Str'(in German) in Sigmix would be transformed to 'GrUniC252neWHSPStr'.
The above transformations are done automatically, so need not to deal with it manually.
8.11.1 Details of Connector Priority

In sumo, it is dealt by label 'prohibition' of '.con.xml' le.
Ordinary Case
In Sigmix, a motor vehicle connector from link4 to link5. It should give way to the opposing
stream, which is the connector from link6 to link7. In *.con.xml of Sumo, it is converted into:
<prohibition prohibitor="link6->link7" prohibited="link4->link5"/>
5 In Sumo, the total travel time is dened in dierent way. So to calculate the 'Total Travel Time' we are
familiar with in Sumo, we must add 'traveltime=x ' (in Sumo) to 'waitingTime=y ' (in Sumo). In this case
they are 189,657 and 1,127, respectively.
Figure 8.3: Two network topologies that are legal in Sigmix, but they are dierently in Sumo.
(a) Sumo does not accept this kind of topology; (b) Sumo approves it.
Pedestrian Case
In Sigmix, a motor vehicle connector from link3 to link8. It should give way to the pedestrian,
which is a link named ped102. In *.con.xml of Sumo, it is converted into:
<prohibition prohibitor="ped102->ped102a" prohibited="link3->link8"/>
The priority parameter is same in order for Sumo and Sigmix. However, the result of ow due
to these priority settings might be dierent. If setting the resulting ow is one of the goals, then
other microscopic parameters in Sumo must be also tuned: acceleration of way-giving stream,
maximum deceleration of opposing stream, impatience of way-giving stream, and sight distance,
etc.
Acceleration of Way-Giving Stream

The larger this Sumo microscopic parameter, the larger the potential capacity of opposed ow,
since lower acceptance of gap is allowed. This parameter can be tuned in label accel of <vType>
in *.rou.xml le of Sumo.
Maximum Deceleration of Opposing Stream

since there is more room to prevent possible collision (Since in Sumo, the Krauss model is applied.
It is a model including description of collision-free). This parameter can be tuned in label decel
of <vType> in *.rou.xml le of Sumo.
Impatience of Way-Giving Stream

since the more aggressive behaviour of the drivers in opposed stream . This parameter can be
tuned in label 'impatience' of <vType> in *.rou.xml le of Sumo.
Others
In *.rou.xml, there are other microscopic parameters aecting the potential capacity. They are:
maxSpeed, speedDev, and minGap, etc.
8.11.2 Network Topology

In Sigmix, the topology is not restricted: If it has connection to pitching/catching whirlpools
(sources and sinks), you can create whatever the topology.
However, in Sumo they should be created with cautious. Consider a network in Sumo that
is able to run/optimise, see gure 8.3(a): Downstream of linkA is linkB, downstream of linkB is
linkC, but in Sumo it is not legal to let linkC as downstream of linkA. If the same topology to
be run in Sumo, it must be modied to 8.3(b): linkB cut into two links: linkBa and linkBb. The
reason is: A link (in this example, linkB) with upstream and downstream in the same junction
is considered incorrect topology in Sumo.
8.12. SUPPORT OF MIXED FLOW 97
Figure 8.4: Simulation of heterogeneous ow in Sumo
8.12 Support of Mixed Flow
Note! In this section, additional plug-in is required: mixMIX.

Mixed ow trac (heterogeneous ow/ mix ow) is trac ow with cars and motorbikes
(autobikes, scooters, etc.) According to sublane model[7] in Sumo, or cutting lanes into multiple
lateral sublanes to accomplish the microscopic simulation of two-wheelers.
After mixMIX installed, all the steps are same as before. The dierence is that when exporting
as a Sumo-readable le, it automatically generates the mix ow parameters for Sumo, as in gure
8.4.
8.12.1 Sublane Model

The so called 'sublane model' is a model based on characteristics of trac in some of the Asian
countries. Features are: sometimes cars drive in between lanes; vehicles (cars and motorbikes
alike) encroach into neighbouring lanes often; motorbikes pass other motorbike(s) within a lane.
To model these behaviours, the model cannot be simply based on conventional 'lane'. It should
be further cut the lane into 'sublanes' within a lane. Consider some phenomenon captured in
gure 8.4:
1. See the upper left in the gure, two cars drive shoulder-to-shoulder within a lane.
2. See the lower left in the gure, multiple motorbikes travel in a lane.
3. See lower part of the gure, a vehicle does not stay in its lane completely. Instead, it
encroaches into its neighbouring lane.
4. Continuing the last point, the same vehicle is travelling with another motorbike in the same
lane.
If there is a microscopic modelling software that is able to capture the phenomenon in het-
erogeneous ow that can be transformed from macroscopic mixMIX of Sigmix without lost of
dynamics, then it is Sumo.
8.12.2 Lane Width

In mixMIX, the lane width of link can be set. It is also an important parameter in Sumo since
interaction between vehicles (including cars and motorbikes) is aected by lane width. Note that
when exporting as Sumo, the lane width in Sigmix is evenly distributed to Sumo lanes in the
same edge. For example, link1 has lane width 3(m) and link2 has link width 4(m), and if the
lane fusion is taken, then they both become 3.5(m).
Note, when converting to Sumo from mixMIX, if average lane width is smaller than 3.0 (m),
technical problems in Sumo would occur.
8.12.3 Hook Turn Zone

Junctions with hook turn zone (HTZ) should follow the form in gure 8.3(b), but not 8.3(a). In
mixMIX library, there are versions marked with 'Sumo compatible' to full the topology logic
in Sumo. In lower part of gure 8.4, there is a HTZ. Eastbound (from west) to south and then
turn to north.
8.12.4 Advanced Stop Zone

Since microscopic Sumo does not support dierences in signal for various kind of vehicle type,
the advanced stop zone (ASZ) in mixMIX cannot be converted to counterpart in Sumo. Sumo
is software published by DLR, consult to http://www.dlr.de for latest update.
Chapter 9
Frequently Asked Questions

9.1 Conict Flow but Receives Green in the Same Stage
Q: For two conict streams of a junction, or the two streams are mark 'conict' in compati-
ble/conict matrices, it sometimes show simultaneous green in same signal stage, how come?
A: The corresponding signalbox is not edited at least once; the 'conict' you see might be the
afterwards (after the run/optimisation). Be sure all of the signalboxes are edited at least once:
Via 'Edit Signalbox' > Right click on the signalbox > select 'Edit Signal Stage'/'Edit Signal
Timing'.
9.2 FAQ for Sumo

9.2.1 Could not Closed Error
Q: Following the steps completely, but a line of 'The route starting at edge 'linkX' could no be
closed. Quitting (on error)' occurred on command line prompt, how to solve this?
A: If Sumo tells you that, it does not matter. It is not an error, but rather sort of a reminder.
9.2.2 Fail to Continue in Second Signal Cycle (mix ow)

Q: Under the mix ow setting, the Sumo behaves well at the beginning. However, it always fails
at the second cycle of trac signal, why?
A: The timing of failure seems to be related with trac signal, but it might be a result instead
of a cause. The root cause is the inadequate lane width. If the average lane width in a Sumo
edge is below 3.0(m), then Sumo fails to continue in the second signal cycle.
Solution methods: [method 1] In Sigmix, set the link width wider so that all of the lanes has
the width in the Sumo network exceeds 3.0(m) [method 2] (This method is more logical but may
be too advanced, you must be familiar with syntax in Sumo) In Sumo, set the car length smaller
than 3.0 (m). This requires your familiarity with Sumo xml syntax!
9.2.3 Oblique Network

Q: When converting from Sigmix to Sumo, the network always seems oblique.
A: Sumo uses the node to identify position, while the Sigmix uses the link as stick yards. The
dierent positioning basis in the topology causes the converted network to be oblique. However,
this will not aect the performance since the network you see is only the apparent position but
does not inuence the internal physics of trac.
If you really need a non-oblique network shown on Sumo, then modify Sumo Node position
in Sumo le *.nod.xml.
9.2.4 Broken Network

Q: Sometimes converting to Sumo network, it is broken in shape, why?
A: There is dierence in treating turns for Sigmix and Sumo. The macroscopic Sigmix does
not care about parameters like turning radius (If trac specialist is considering turning radius
to the simulation, then, say, set the capacity at straight-going with 2000(vph) and at sharp turns
1300(vph). The parameters in macroscopic model are able to be measured directly to trac
ow.); however, the microscopic Sumo do. When Sumo connection connects two Sumo edges,
100 CHAPTER 9. FREQUENTLY ASKED QUESTIONS
the turning radius is calculated. If the radius cannot be within a reasonable range, then the
connection goes around the corner to full the setting.
Solution to this kind of problem is to slightly modify the topology in Sigmix: drag the links
so that the turning would not be too sharp in Sumo. Simply dragging links in Sigmix would
not cause any performance dierence in Sigmix. When installing Sumo, there is an editor called
'NetGen' which allows directly modifying Sumo Xml les in GUI. But, be sure to be certain
that the network generated by Sumo is not changing any more, or you have to change the Sumo
network again due to new changes.
9.2.5 Sumo Editor

Q: Using Sigmix to generate Sumo cannot satisfy me; are there other graphical user interface
(GUI) editors for Sumo?
A: Yes. This is good question for advanced user. Since from Sigmix to Sumo there are a lot of
procedures that are automated. However, there are many details to be coped with, for example:
adjustment of microscopic parameters, topology, etc.
9.3 Others
If there is question other than the above FAQ, it is welcomed to contact us by email.
Bibliography
[1] Trac Advisory Leaet 1/06 General Principles of Trac Control by Light Signals, Depart-
ment of Transport, London, 2006
[2] Transportation Research Board, Highway Capacity Manual 2010 Vol.2 Interrupted Flow,
Washionton D.C., 2010
[3] American Association of State Highway and Transportation Ocials(AASHTO), A Policy on

Geometry Design of Highways and Streets (the Green Book), Washionton D.C., 2001
[4] Land Transport Authority (LTA), Singapore Land Transport Statistics in Brief 2015, Singa-
pore, 2016
[5] 2011 Highway Capacity Manual in Taiwan (in Traditional Mandarin), Ministry of Trans-
portation and Communications, Taipei, 2011
[6] Krajzewicz, D., Erdmann, J., Behrish, M., and Bieker, L., Recent Development and Ap-
plications of SUMO - Simulation of Urban MObility, International Journal On Advances in
Systems and Measurements no. 3 and 4, vol.5, pp.128-138, 2012
[7] Semrau, M., Eedmann, J., Friedrich, B., and Waldmann, R., Simulation framework for testing
ADAS in Chinese trac situations, SUMO 2016 Trac, Mobility, and Logistics, pp.103-134,
2016
101

Sigmix User Manual

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Sigmix User Manual

Uploaded by

Copyright:

Available Formats

Sigmix User's Manual

This manual is done via LATEX.

2 The Main Window 21

3 Topology and Its Object 29

9 Frequently Asked Questions 99

1.3 Structure of Sigmix

1.4 Quick Guide

1.4.2 An Signalled Junction Example

(a) upstream of link1;

(b) downstream of link2;

(c) upstream of link3; and

The Main Window

2.2 Horizontal Buttons

2.3 Vertical Buttons

2.4 Menu Bar

Figure 2.1: Start-up Lost, End-of-Green Displacement and Eective Green

Global Signal Settings

Load Object Library

Load Junction Library

Load Network Library

2.4.5 Bulk Property

2 This term comes from industrial engineering, or applied mathematics.

Flow Ratio Bulk Editor

2.4.6 Single Run

Topology and Its Object

3.2.1 Add a Link

3.2.2 Topology Editing

Rotate Link After selecting 'Rotate link', drag to rotate.

3.2.3 Edit Link Property-General

Signal-Controlled 'Signal-Controlled?' is a true/false option. If 'yes', this link is signalled;

Controlled by If 'Signal-Controlled?' is 'yes', this link is signalled, and should be controlled

3.2.4 Edit Link Property-Signalled

End-of-Green Displacement End-of-green displacement is the dierence between the end

3.2.5 Delete Link

3.2.6 Colouring of Link

3.3.1 Add a Connector

3.3.2 The Topology

3.3.3 Edit Connector Property-General

3.3.4 Edit Connector Property-Priority Relation

3.3.5 Edit Opposed Diagram

3.3.6 The Superposition Principle

3.3.7 An opposed Turn Example

3.3.8 Delete Connector

3.4.1 Add a Whirlpool

3.4.2 Topology Editing

3.4.3 Edit Whirlpool Property

3.4.4 Time Dependent Demand (TDD)

3.4.5 Delete Whirlpool

3.5.1 Add a Junction

3.5.2 Topology Editing

3.5.3 Edit Junction Property

3.5.4 Delete Junction

3.6.1 Add a Signalbox

3.6.2 Topology Editing

3.6.3 Edit Signalbox Property

3.6.4 Edit Signal Staging

3.6.5 Edit Signal Timing

3.6.6 Delete Signalbox

1. It is not selected as a 'Signalled Link'. Rather, it is an 'Unsignalled Link'; or

2. It is already selected as 'Controlling Link' by another signalbox.

4.2 Signalbox Stage Editing

4.2.2 Stream Compatibility (Tab 1)

4.2.3 Intergreen (Tab 2)

Figure 2.1: Start-up Lost, End-of-Green Displacement and Eective Green

End-of-Green Displacement End-of-green displacement is the dierence between the end

After the specifying data, End_grouping should appear in the le.

(b) Identify the conict point of trajectories, see gure 4.3.

Figure 4.3: The trajectory and the point of conict

The 3rd tab shows the outow of links.

6.5.1 Stage 1 Ineciency

2. The oset, is 36(sec)1 , so stage 1 begins at 36(sec).

6.5.2 Ecient Stage 1

1. Output of macroscopic ow states;

Syntax of Conguration File

2. Edit the LOS conguration le (*.loscong):

3. 'Go optimise' as other networks.

9. Info about successfully exported le.