Home

EvolveTraffic - User Manual v0.94

1. The display colour for the road line markings 17 AINE LESS PBS 0 255 D bo 55 2 Ea NUMBER TYPE integer integer integer 76 UCD LCPC 2008 EvolveTraffic v1 0 4 User Manual Version 0 94 VALUE OPE Niew Colours a cie The display UNITS RGB NUMBER TYPE VALUE uetus ff P IWrew OOoloufs lU a CE ELE The display UNITS RGB NUMBER TYPE VALUE Oy 050 Vien Colours ne a The display UNITS RGB NUMBER TYPE VALUE 000 Ta LIN Lew Colours Fer I The displ y UNITS RGB NUMBER TYPE VALUE 255 2515 0 i 7 J7View Colours jer The display UNITS RGB NUMBER TYPE VALUE 0 22 5 5I Niew Colours a cie The display UNITS RGB NUMBER TYPE VALUE Oi Oy o P IVrew Ocolourfs lU MEE EE The display UNITS RGB NUMBER TYPE VALUE DD ty JAN ew Colours DrawElements CLR RULER LINES DrawElements CLR RULER TEXT DrawElements CLR LEGEND TEXT DrawElements CLR DET OUTPUT DrawElements CLR DET FLOWDENSITY DrawElements CLR DET HEADWAY DrawElements CLR DET COMPOSITION DrawElements CLR FEAT SPEEDLIMIT RGB 005 0 17 Colour for the ruler sick Lines OBO 230 VTO aaay 0 06 255 integer integer integer RGB CO 00 COlOUr For ne EULSE text D E92 gue O WO Zoey EG 5 intege
2. EvolveTraffic v1 0 4 User Manual Version 0 94 Important EvolveTraffic does not check the file format prior to reading the file Therefore setting the wrong file format here will result in a program crash Number of Lanes Specify the number of lanes of traffic in each direction as contained in the traffic file Important EvolveTraffic does not check the number of lanes in the traffic file prior to reading the file Therefore setting the wrong numbers here may result in a program crash In particular e Setting more lanes than there are on the traffic file does not affect the program execution e Setting fewer lanes than there are in the traffic file results in a program crash Simulation Details Simulation Step The time step in milliseconds that the simulation progresses against Vehicle driving properties are only updated once per time step Too small a time step is inefficient too large may result in inaccuracies For the IDM Treiber uses 250 ms typically stating that smaller time steps do not exhibit significantly different results 3 4 Simulation Road Details Road Length The length of the road in metres that the vehicles are to be driven along All lanes are this length Drive on the Choose the drive side for the vehicles European or British Irish This setting only affects the graphical display of the road and vehicles 29 UCD LCPC 2008 EvolveTraffic v1 0 4 User Manual Version 0 94
3. IHis number must be greater than zero since every vehicle should want to make progress UNITS ms NUMBER TYPE real VALUE 13 UCD LCPC 2008 User Manual Version 0 94 EvolveTraffic v1 0 4 User Manual Version 0 94 Road RoadFeatures Gradient IDM Modifiers VO SLOPE NO me This specifies how the IDM parameter VO the desired velocity varies with gradient It is measured in the gradient per 1 km h reduction in the desired velocity The desired velocity is reduced for downhill gradients and not modified for uphill gradiente FR DNITSS NUMBER TYPE integer VALUE Since we usually consider there to be 5 working days per week for 50 weeks per year which allows for holidays we have 250 days per year We thus consider there to be 10 working months per year of 25 working days each A vehicle with a time stamp of 3 500 000 seconds thus is written Fr Que EO BLE ass 0702 0808 1293220 The number of days per simulation month UNITS N A NUMBER TYPE integer VALUE The number of simulation months per year UNITS N A NUMBER TYPE integer VALUE The program defines 5 types of vehicles and these parameters govern the vehicle class assigned to a vehicle NehicleID CRANE AVERAGE SPACING 2 5 The average spacing of a crane s axles UNITS m NUMBER TYPE real IK VALUE J VehicleID CRANE MAX SPACIN
4. This means only a single EvolveTraffic file can be opened at any one time similar to the way NotePad in Windows operates The menu and toolbar commands whilst being specific to the program are operated in the same way as standard Windows programs Of note for ease of use there is extensive support for keyboard shortcuts in EvolveTraffic This makes it much quicker and easier to use the program features during a simulation whilst in Visible Mode 17 UCD LCPC 2008 EvolveTraffic v1 0 4 User Manual Version 0 94 4 2 Menu File File gt New Opens a new etr file with some default settings File gt Open Displays the Open File dialog for choosing an existing etr file File gt Save Saves the current file File gt Save As Allows the current file to be saved as a different name File gt Save Image Saves the view currently visible to a bmp file specified in the Save dialog This feature is useful for including configurations in reports presentations etc and replaces the need for using the Windows Print Screen command File gt Print Prints the current view this feature 1s not supported as may be seen from the Print Preview command File gt Print Preview Displays a preview of the output that may be sent to the printer File gt Print Setup Specify the setup to be used when printing File gt Recently Used Files A list of recently used files for ease of access File g
5. e 5 CH p LX 4 J OPP EDD PDD d 1000 m 65 UCD LCPC 2008 EvolveTraffic v1 0 4 User Manual Version 0 94 8 FAQs and TroubleShooting 8 1 FAQs Since this is the first release of this program there are no frequently asked questions 66 UCD LCPC 2008 EvolveTraffic v1 0 4 User Manual Version 0 94 8 2 TroubleShooting As this is the first release of this program there bound to be some bugs and inconsistent behavior Please check below for some possible solutions If the problem persists please send a copy of the etr and input traffic file that causes the problem to colin caprani ucd ie explaining the steps required to reproduce the problem It is envisaged that this section of the document will be updated frequently as the program matures Problems The program crashes e Please check this document for the Important labels and confirm that you have adhered to these requirements e Restore the default configuration file values if you have changed any The driving is not realistic e Check the IDM parameters for realism e Use Treiber s IDM parameters 1 3 with a small traffic file to verify realism e Slowly build the extra complexity into the IDM parameters verifying the realism at each stage 67 UCD LCPC 2008 EvolveTraffic v1 0 4 User Manual Version 0 94 9 Appendices 9 1 Appendix 1 CASTOR and SAFT File Formats CASTOR File Format In the table
6. Lane Changes Allowed Choose whether to allow lane changes or not Output Cars To File Specifies whether or not cars are to be output to the output traffic file This is useful for creating truck only traffic files which are of chief interest in bridge loading calculations Number of Lanes Specify the number of lanes in each direction on the simulation road up to a maximum of 4 If there is only one direction choose 0 lanes for the Direction 2 choosing zero lanes for Direction 1 means the program will swap Direction I and Direction 2 single direction roads always run in the positive x direction Note that the user cannot set fewer lanes in the simulation road than there are in the input traffic file since the vehicles cannot arrive to non existent lanes Road Location of Detectors for Output To File Specify the position of the Output Detectors which upon a vehicle s arrival write the vehicle to file along with its new time of arrival 30 UCD LCPC 2008 EvolveTraffic v1 0 4 User Manual Version 0 94 5 3 Traffic Model Configuration This dialog configures the IDM parameters that govern the driving behaviour for each of the 5 classes of vehicle that the program considers IDM Traffic Model Configuration IDM Parameters for Vehicle Class Class Cars x Copy from lt lt bi Distribution Location Scale Shape 4 Safe time headway T 5 Normal 1 20 Maximum acceleration mfs 2 Normal 1 0
7. drop down box 4 Input the locations of the start and end of the speed limit section as measured from the start of the road in the positive x direction 5 Type the Value of the speed limit that is the actual speed limit in km h Though up to two decimal places is allowed this is only enabled for defining gradients speed limits should be integer valued Non integer speed limits will be rounded by the program Notes e EvolveTraffic will exchange the start and end values if it needs to Koad Features Contipuration Feature 1 overlaps with Feature 4 change start and end points dd Feature Delete Last Feature Type Direction Start m End fm Feature 1 Speed Limit Positive x id 500 1 000 Feature 2 Speed Limit Positive x 1 000 2 O00 Feature 3 Gradient Positive x foul 1 200 Feature 4 Speed Limit Positive x Bd zoo O 400 h Cancel 36 UCD LCPC 2008 EvolveTraffic v1 0 4 User Manual Version 0 94 e There cannot be two speed limits for the same section of road and so EvolveTraffic checks for and prevents the user defining overlapping speed limit sections as shown below where the Feature 4 speed limit overlaps with the Feature 1 and Feature 2 speed limits as shown above e To prevent unrealistic speed limits the program checks that the speed limits defined are between 10 and 150 km h Effect of a Speed Limit on a Vehicle When a vehicle enters a speed limit region the progr
8. 000 4 000 2 200 2 500 200 To add or delete a detector follow the same steps as for adding or deleting a Road Feature explained in Section 5 4 For all types of detector the following parameters are the same e Type the type of detector e Direction the road direction the detector covers e Vehicle Types the types of vehicles that the detector examines The types of detectors available and their properties are 39 UCD LCPC 2008 EvolveTraffic v1 0 4 User Manual Version 0 94 Flow amp Density This detector extracts the flow and density of the traffic as follows e The flow is determined by counting the number of vehicles of the selected type passing during the time interval This figure is then changed to the standard vehicles per hour measure e The density is determined from the flow per hour previously found divided by the average velocity of the vehicles during the time interval That 1s EvolveTraffic uses the relation Flow Average Velocity x Density The time interval directly affects the calculation of the above properties and so is of importance in the results Thus the last two parameters are e Time Interval the interval in simulation time between the detector outputs e Location Step this value specifies the location of the detector Refer to Section 7 3 for information on the data output by this detector 40 UCD LCPC 2008 EvolveTraffic v1 0 4 Us
9. 2 00 Lane change threshold delta th mis Constant Cancel Ee I Ec E KOE KOE 0 30 34 UCD LCPC 2008 EvolveTraffic v1 0 4 User Manual Version 0 94 5 4 Road Features Configuration This dialog allows the user to define the features that a road may have the so called Road Features Currently speed limit and gradient sections of road are available Koad Features Configuration Add Feature Delete Last Feature Type Direction Start m End m Feature 1 Speed Limit Positive X ont 1 000 Feature 2 Speed Limit v Positive X 1 000 Or Feature 3 Gradient _x Positive X H 750 1 200 OF Cancel Adding and Deleting Road Features To add a Road Feature press the Add Feature button and then edit the details of the newly added feature Currently only the Road Feature that is last in the list can be deleted Pressing the Delete Last Feature button deletes this last feature 35 UCD LCPC 2008 EvolveTraffic v1 0 4 User Manual Version 0 94 The Speed Limit Road Feature To include a speed limit section of road do the following 1 Add a Road Feature as above 2 Choose Speed Limit from the Type drop down menu 3 Choose the direction that the speed limit is to be applied to from the Direction
10. 4 Shortcut Keys Extensive support for shortcut keys is included in EvolveTraffic Some commands are only accessible through the keyboard Commands only accessibly through the keyboard Left Arrow Moves the portion of the road being viewed one tenth the length of the road to the left Right Arrow Moves the viewport one tenth of the road length to the right Home Moves the viewport to the start of the road End Moves the viewport to the end of the road In addition to the standard Windows keyboard selection of menu commands EvolveTraffic provides the following keyboard shortcuts to menu commands Ctri N File gt New Ctrl 0 File gt Open Ctrl File gt Save Ctrl I File gt Save Image Ctrl P File gt Print Alt S Configuration gt Simulation Alt T Configuration gt Traffic Model Alt R Configuration gt Road Features Alt M Configuration gt Traffic Flow Metrics F5 Run gt Visible Shift F5 Run gt As Invisible F10 Tools gt Zoom In F11 Tools gt Zoom Out F6 Tools gt Speed Up 22 UCD LCPC 2008 EvolveTraffic v1 0 4 User Manual Version 0 94 e F7 Tools gt Slow Down e F9 Tools gt Pause Resume e F12 Tools gt Stop e Alt P Tools gt Preferences 23 UCD LCPC 2008 EvolveTraffic v1 0 4 User Manual Version 0 94 4 5 Other Interface Elements DataTips All of the relevant information about a vehicle can be obtain through the DataTips
11. ENE SE P4 The display Colour for a small truck Fe UNE ESS RGB UO 255 0s Ge 255 O Bo 255 NUMBER TYPE integer integer integer VALUE 0707255 View Colours Vehicles VEH COLOR LARGETRUCK RGB 255 0 0 7 The display colour for large truck Fr ANT LISS URGE eu EC PSE 0 EO 255 OTEO 255 A NUMBER TYPE integer integer integer VALUE 2957070 View Colours Vehicles VEH COLOR CRANE RGB 0 255 0 The display colour for a crane e NT ESS RGB U To 255 O bo 2554 0 Er 255 NUMBER TYPE integer integer integer VALUE 025520 View Colours Vehicles VEH COLOR LOWLOADER RGB 100 100 100 The display colour for a low loader PA gNIISSIBRBOBT OS Do 259 O to 299 To 259 3 NUMBER TYPE integer integer integer VALUE L00 T0000 Niew Colours DrawElements CLR BACKGRND RGB 255 255 255 The display colour for the background usually white F UNITS SREB U Eco 255 X E0255 0 EO 255 NUMBER TYPE integer integer integer VALUE 750 25562055 d Niew Colours DrawElements CLR ROAD SURFACE RGB 200 200 200 fl The display colour for the road surface Fe UNTSO RGB O bo 255 10 255 0 BO 255 NUMBER TYPE integer integer integer VALUE 2007200 200 EG View Colours DrawElements CLR ROAD LINES RGB 0 0 0
12. Manual Version 0 94 5 2 Simulation Configuration This dialog configures the simulation parameters The various sections of the dialog as shown are explained as follows Simulation Configuration Traffic File Details Simulation Road Details Input Traffic File DA Researchs Codes C TralficFlowGe ws Road Length 2000 m Drive on the Right Output Traffic File D ResearchiCodelC TrafficFlowGe I Lane changes allowed w Output cars to file Metrics Directory DA Research Code C 4TrafficFlowGe v Mumber of Lanes Traffic File Format CASTOR C SAFT Single lane data only Direction 1 Positive x direction 1 Humber of Lanes Direction 2 Negative direction 1 Direction 1 1 Direction 2 I Road Location of Detectors for Output to File Direction 1 Positive direction 2000 m Simulation Details Direction 2 Negative x direction 1 m Simulation Time Step 300 SE Neg DE Cancel Traffic File Details e Input Traffic File The file from which the traffic to be placed on the road is read e Output Traffic File The file to which the traffic 1s written as it passes the output detector e Metrics Directory The directory to which the metrics detectors output files if any will be written e Traffic File Format the format of the file to be read in and written out Note that only CASTOR supports multiple lane traffic The SAFT format is for single lane traffic 28 UCD LCPC 2008
13. Pu E m NOB B qo qo rare OR x vi PM PS aou om EUN E m e Dm b ule Dm Dm at D ha Dm zo M x SV Es ali aia Mm eoe LU E at es at P PS ve ae PS PS UE MA DU c are n a T S a Pu S S a a Ls P on EI ay pe ai A s CE ce ae eee ee eee at nos 0 mE S ER HK RO a NL ML C C X eke a ee te tates zs 2 gt Lee mm mM oe ME es a G fy S E x es ES es A hay UN ER UN E zo S oe d oe n RN etd Es eps xw ge ze a Eu es don ll e 7 rx EE d PS S ae me Mu Qs a See a ete RUE RR RR ae Shee RC C O8 OG Pee Maye x o x mut ci oe p D mr ce mE P E ore SF DEE EG en HOR Eee DE A D a X m alia m EX di HM oce KN XS Ex as a a Show Legend set this value to zero to turn off any other value turns it on the display of the legend at the top of the screen Car Output Detector speed limit section Small Truck FlowDensity Detector Large Truck Headway Detector Crane ee Composition Detector EMH Gradient section Low loader LC Lane Change Detector Tick Length the length of the ruler ticks e Tick Interval the interval between ruler ticks and distance displays 48 UCD LCPC 2008 EvolveTraffic v1 0 4 User Manual Ve
14. To use these 1 A simulation must be running in Visible Mode 2 The simulation must be paused 3 Clicking on the vehicle of interest with the left mouse button displays the DataTip for that vehicle The DataTip contains all of the relevant data for that vehicle as shown vehicle Data Direction Positive Lane 1 Position 157 6m Velocity 54 8 km h Acceleration 0 15 m s 2 Desired Vel 60 5 km h 1 07 mis 2 02 mis 0 93 m 19 65 m 22 4 ms IDM Delta 4 0 IDM Polite OZ IDM Bias GNI IDM DelkaGth 0 3 Ho of Axles Axle 1 54 9 kM 3 5 m Axle 2 121 6 kM 5 4 m Axle 3 66 7 kN 1 2m Axle 4 66 7 kN 1 2m Axle 5 66 7 kM 24 UCD LCPC 2008 EvolveTraffic v1 0 4 User Manual Version 0 94 Progress Bar The progress bar gives an indication of the amount of simulation complete and remaining At the start of the simulation EvolveTraffic counts the number of vehicles in the input traffic file At each time step the number of vehicles already read from the file is compared to the total number of vehicles to give an estimate of the simulation duration as shown ET CF 5000 Test etr Evolve Traffic File Configuration Run Tools View Help Deh hyl rie gt Sim Time Day 0 0 02 16 52 Real Time Day 0 0 00 00 86 ae PE o Car Small Truck Large Truck Crane Low loader Output Detector Flow Density Detector Headway Detector Composition Detector Lane Change Detector
15. by reducing the desired velocity 1 5 only EvolveTraffic allows the Developer User to change more IDM parameters than this though care must be taken Please refer to the comments in the configuration file for further information on how a gradient can affect vehicles 38 UCD LCPC 2008 EvolveTraffic v1 0 4 User Manual Version 0 94 5 5 Traffic Flow Metrics Configuration This dialog allows the user to define locations on the road where information regarding the traffic flow is abstracted Macroscopic Traffic Flow Metrics Detectors Detector 1 Detector 2 Detector 3 Detector 4 Detector 5 Detector 6 Detector Detector 8 Detector 9 Detector 10 Detector 11 Type Flow amp Density Flow amp Density Flow amp Density Flow amp Density Headway Headway Headway Headway Composition Composition Lane Changes Add Detector Direction Positive x l Positive x xl Negative x l Negative x Positive x Positive x Negative x Negative x Positive x ha Negative x l Negative x Delete Last D etector vehicle Types All Vehicles l al Vehicles All vehicles l All vehicles All vehicles p All vehicles E All Vehicles xl All Vehicles l All vehicles l al Vehicles All vehicles Time Interval s EE ES Ee E EG Ee Ec s 60 60 60 60 B 60 B 60 60 60 60 Location Step m 2 000 4 000 2 000 4 000 2 DO 4 000 2
16. o a Te s es 3 1 Fix AM 2 is TEN ee RES APP S a S d ER Pies te Kminoo 50000000 Speed limit section Note that once the last vehicle has entered the road the progress bar will display 100 since all vehicles have been read but the simulation is not complete until the last vehicle has left the road 25 UCD LCPC 2008 EvolveTraffic v1 0 4 User Manual Version 0 94 Clocks For simulations run in both the Visible and Invisible Modes two clocks are maintained e A simulation clock which represents time as observed by the vehicles e A real clock representing the elapsed actual time since the start of the simulation Bm CF 5000 Test etr Evolve Traffic Fil Configuration Run Tools View Help r d o5 7 HN ka ml A em sim Time Day ll D 27 51 52 Car Output Detector e o so Real Time Day 0 0 00 15 76 small Truck Flow Density Detector 22022n20000000000099 EN Large Truck Headway Detector EN Crane Composition Detector Me Lowloader LC Lane Change Detector In Visible Mode when paused the real clock 1s also paused This means that at the end of the simulation an estimate of the average time warp ratio of simulation to real time 1s easily got In Invisible Mode only the final simulation and real times are shown upon completion of the simulation This enables the time warp to be calculated Calculation of the time warp can prove useful to examine t
17. output files using a csv file viewer such as MS Excel The user preferences and configuration preferences required for the program are explained next 44 UCD LCPC 2008 EvolveTraffic v1 0 4 User Manual Version 0 94 6 2 Simulation Modes Introduction Two modes of running the simulations are provided to meet the aims of the program Visible Mode In this mode the user can interact with the program at any stage of the simulation and change visualisation parameters via the User Preferences dialog box Section 6 3 This mode displays the vehicles as they progress along the road The animation can be paused or stopped at any time Whilst paused information on vehicles can be got though the DataTips Section 4 5 Also at any point during the simulation a screenshot of the simulation may be taken using the File gt Save Image command or the Ctrl I keyboard shortcut These features make the Visible Mode an interactive environment for the calibration of a traffic model The features described for Visible Mode above come at the expense of execution time Both rendering the simulation to the screen at 20 frames per second and interrupting the simulation every time the user interacts with the program mean that results cannot be obtained as fast as possible Further this mode requires that the program sleep for a period during each simulation step in order that the animation of vehicles is done at a slow enough s
18. the simulation and these are written out to file and will be the same as those read in The arrival time at the Output Detector is output to this file as the vehicle s new time stamp It is this time stamp that is the reason behind EvolveTraffic since it represents the driving behaviour as the vehicle moves along the road The output traffic file is in the same format as the input traffic file Section 5 2 For reference the CASTOR and SAFT file formats are given The output traffic file is saved with the name extension and location as specified by the user in the Simulation Configuration dialog Section 5 2 54 UCD LCPC 2008 EvolveTraffic v1 0 4 User Manual Version 0 94 7 3 Flow amp Density File The output for a Flow Density Detector is made to the following file EFD A A dadd OUO CSV Where e FD means Flow Density detector file e vvv the vehicle type for which the output is made it can be O O O O O O O All for All Vehicles output Trucks For all trucks output Car for Car only output ST for Small Truck only output LT for Large Truck only output Crane for Crane only output LL for Low loader only output e ddd the direction identifier O O Pos for the positive x direction Neg for the negative x direction e xxxxx a number representing the location of the detector in metres 55 UCD LCPC 2008 Evol
19. 0 Comfortable decceleration bim s gt 2 Normal 2 00 Minimum jam distance s0 m Normal 1 00 Elastic jam distance 51 m Normal 10 00 Desired velocity vO km h Narmal 110 00 Acceleration exponent delta Constant 4 00 Lane change politeness Factor p Constant 1 20 Outside lane bias Factor delta4bias Constant 1 00 E ES E ES Ed Ed E B3 Lane change threshold delEa amp th mis Constant 0 30 Cancel For an explanation of the parameters refer to Treiber s work 1 3 Classes of Vehicle The program considers 5 classes of vehicle 1 Class 0 Cars any vehicle under 3 5 tonnes 2 Class 1 Small Trucks any vehicle with less than 4 axles 1 e 2 and 3 axle vehicles over 3 5 tonnes 3 Class 2 Large Trucks any vehicle that is not a car small truck crane or low loader 4 Class 3 Crane any vehicle that is not a car and has a maximum axle spacing of 4 5 m and an average axle spacing less than 2 5 m 31 UCD LCPC 2008 EvolveTraffic v1 0 4 User Manual Version 0 94 5 Class 4 Low loader any vehicle that is not a car and has a maximum axle spacing not less than 7 5 m EvolveTraffic considers these particular classes of vehicles due to their importance in highway bridge traffic loading Parameter Values For a particular class of vehicle there are 10 parameters to be set for the IDM and MOBIL lane changing models 1 3 In all of Treiber s work to date the
20. 00 4500 LT I I c Oo Oo oo Sos soso So oo oo OO 00 000000000000 oQ 000000000000 00000000 eo Note that in this example the columns referring to Steps 1600 m to 4400 m have been hidden From this example it is apparent that there is significant lane changing at 1000 m This is caused by a speed limit section that starts at this point in the road By keeping the Lane Change Detector time interval the same as that of the Flow Density Detector the lane change rates and density at a particular point on the road can be plotted together As explained in the MOBIL paper 3 this curve should display low rates of lane changing at low flows high rates at medium flows and low rates at fully congested flows 63 UCD LCPC 2008 EvolveTraffic v1 0 4 User Manual Version 0 94 The LC_ST File This file outputs the time and position of each lane change event for both Left to Right changes and for Right to Left changes for the direction that the detector is applied to An example 1s A E D 1 LANE CHANGE SPACE TIME OF EVENTS 2 Left To Right Right To Lett 3 Time s Location m Time s Location rn 56 02 1009 bb S 1015 b bb S 1023 7 bo S JO De 54 SE E 90 52 dn 10 119 02 1609 11 118 52 1679 12 127 02 915 13 136 52 3h53 14 144 52 1996 15 147 52 446 AL 154 52 1012 EG 162 02 2124 The plot that results from a large amount of such data can be very in
21. 19 1108 1260 139 619 Note that the 1 4IND means that no number is present 1 e no vehicles passed the detector during the time interval considered This can be clearly seen from the Flow information since it 1s zero 56 UCD LCPC 2008 EvolveTraffic v1 0 4 User Manual Version 0 94 7 4 Headway File The output for a Headway Detector is made to the following file Head vvv ddd xxxx CSV In which vvv ddd and xxxx have the same meanings as for the Flow Density Detector file Section 7 3 Output A B At each time interval EvolveTraffic outputs the vectors 1 Headways s 2 Lane1 Lane2 of headways in seconds for the vehicle types considered for ES 541 373 4 329436 552235 each lane for the direction which the detector covers An 5 434141 E 15 4491 804202 example is shown to the left p 9 09299 EE 13 8558 9 21 529 GO 16 6086 Note from the example that the first vehicles have large EST headways since there is no vehicle in front Also notice that 13 21393 1245 Lane 1 is more heavily trafficked than Lane 2 14 16 2595 15 15 4452 161 17 4007 17 27 895 40 4083 18 15 0831 19 18 8952 20 110103 1 362 57 UCD LCPC 2008 EvolveTraffic v1 0 4 User Manual Version 0 94 7 5 Composition File The output for a Composition Detector is made to the following file Comp vvv ddd XXXxx cesv In which vvv ddd and xxxx have the same meanings a
22. G 4 5 74 UCD LCPC 2008 EvolveTraffic v1 0 4 User Manual Version 0 94 The maximum single axle spacing possible for a vehicle to still be considered a crane UNITS m NUMBER TYPE real VALUE VehicleID LOWLOADER MIN MAX SPACING 7 5 If a vehicle has a maximum axle spacing greater than this value and has more than 2 axles it is considered a low loader UNITS m NUMBER TYPE real VALUE VehicleID SMALL TRUCK NO AXLES 3 The maximum Number Or axles a small truck can De considered to have UNITS N A NUMBER TYPE integer VALUE A vehicle with a weight less than this value is a car otherwise ite 1S cw Were ke UNITS kg 100 NUMBER TYPE integer VALUE The minimum value the user can zoom out to Setting this value too low will result in the program crashing UNITS N A NUMBER TYPE real VALUE The time in seconds that the vehicle datatip stays visible after the user clicks on a vehicle in pause mode Must be greater than zero or program will crash UNTTSE N A NUMBER TYPE real VALUE 0 75 UCD LCPC 2008 EvolveTraffic v1 0 4 User Manual Version 0 94 View Colours Vehicles VEH COLOR CAR RGB 0 0 0 ji The display colour for car L4 UNIT S RGB U 00255 X Eo 255 0 50 255 I NUMBER TYPE integer integer integer VALUE 0 0 0 gs I Niew Colours Vehicles VEH COLOR SMALGTRUCK REBI 0 0 255 ENERSEN GE GONE
23. Time Dra U OSC U EN Car Ouian Detector en at EN Small Truck Flow Density Detector ESS EE Lage Truck Headway Detector umi Crane Composition Delector Low laander LE Lane Change Detector ARRAS RS eee ion sonne n em re eres ENE eae i S EE Eerme Sion il king KE EEE EEE PLL ee iss ate Om 500 m 1000 m 1500 m 2000 m 2500 m 3000 m 3600 m Lane change detectors are specified for both directions In this file congestion can be seen to start occurring in each direction at the first Road Feature the vehicles arrive at High levels of lane changes occur at this point as may be observed in the Lane Change Detector Output 51 UCD LCPC 2008 EvolveTraffic v1 0 4 User Manual Version 0 94 Example 2 Ex 2 etr This example illustrates a free flowing truck only traffic file run on the same road as Example 1 Various detectors are specified along the length of the positive direction TLELI IIIS PP a SS RE BR SS Settee eee eee eee eee See eee eee eee eee eee 1000 m 1500 m 2000 m 2500 m DOO 6 CO OC COGO RTE TA TA Example 3 Ex 3 etr This file illustrates a SAFT input file from the RN4 in France A speed limit section of 50 km h is specified for 500 m along the 3 km road 500 m 1000 m i 1500 m 52 UCD LCPC 2008 EvolveTraffic v1 0 4 User Manual Version 0 94 7 EvolveTraffic Output 7 1 Introduction EvolveTraffic
24. Tr 8 142 52 4021 3 Lett smallTr E 170 02 4036 4 3 Left smallTr 10 177 52 3993 3 Lett smallTr 11 190 02 1025 3 Lett smallTr 12 200 02 1887 3 Left LargeTr Eile 207 52 1992 3 Lett Largelr The columns are explained as 59 UCD LCPC 2008 EvolveTraffic v1 0 4 User Manual Version 0 94 e Time the time at which the lane change vene took place e Position the location as measured from the start of the road of the lane change e From Lane the lane number that the vehicle moved from e To Lane the lane number that the vehicle moved to e Right Left whether the vehicle moved left or right e Type the vehicle type that changed lane Note that lanes are numbered from the outside lane of the positive x direction to the outside lane of the negative x direction So for a European road Lane 4 L amp Lane 3 Direction of travel Lane 2 gt L Lane I ss s Om 500 m And for a left hand drive roads Lane I L Lane 2 p Direction of travel Lane 3 4 L Lane 4 P TTE Om 500 m 60 UCD LCPC 2008 EvolveTraffic v1 0 4 Use
25. User Manual Version 0 94 EvolveTraffic v1 0 4 EvolveTraffic lation Model for Bridge Loading crosimu I A Traffic M Version 1 0 4 tT CF 5000 Test etr Evolve Traffic im A v Dc Ed Gavi gt gt Ie it section imi Speed Output Detector EB Car 21 52 12 36 0 0 04 Sim Time Day Flow Density Detector Headway Detector EH Small Truck EH Large Truck EN Crane 0 0 00 Real Time Day Gradient sect lon Composition Detector Lane Change Detector LC EN Low loader XS XX C Ke e KK FG OO pq e x OO E D 5 complete BEBEEBE User Manual Version 0 94 University College Dublin Ireland Laboratoire Central des Ponts et Chausees France UCD LCPC 2008 EvolveTraffic v1 0 4 User Manual Version 0 94 Acknowledgements This program was developed at the School of Architecture Landscape and Civil Engineering University College Dublin Ireland in liaison with Laboratoire Central des Ponts et Chaus es France Its development was funded as part of the HeavyRoute Project http heavyroute fehrl org At University College Dublin Project Supervisor Prof Eugene OBrien eugene obrien 2 ucd ie Project Leader Dr Colin Caprani colin caprani ucd ie Programmer Mr Cillian Murphy Calibration Mr Alberto Bordallo Ruiz For Laboratoire Central des Ponts et Chaus es Project Supervisor Dr Hocine Imine hocine imi
26. along a road consider 5 classes of vehicle cars small trucks large trucks cranes and low loaders especially chosen for their relevance to bridge loading model roads of up to 8 lanes in width 4 per direction model one or two directions at the same time each of up to 4 lanes take account of speed limit sections of road take account of gradient sections of road consider overlapping gradient and speed limit sections of road output vehicles to file along with their arrival times at the output detector output Flow amp Density information for specified locations on the road at specified time intervals for specified classes of vehicles output Headway information for specified locations on the road at specified time intervals for specified classes of vehicles output traffic Composition information for specified locations on the road at specified time intervals output Lane Change information by direction at specified time intervals for specified classes of vehicles 14 UCD LCPC 2008 EvolveTraffic v1 0 4 User Manual Version 0 94 Limitations EvolveTraffic s not able to determine the number of lanes or directions of traffic in the specified input traffic file in advance of the simulation determine the input traffic file format whether CASTOR or SAFT calculate load effects on bridges model on ramps curves in the road or lane closures model different lengths of lanes or directions Cars o
27. am carries out the following Steps 1 Checks to see if the speed limit is less than the vehicle s desired velocity if it is it proceeds to the next step 2 Stores the desired velocity of the vehicle before it entered the speed limit region 3 Sets the vehicle a new desired velocity by keeping the ratio of desired velocity to speed limit the same as the initial desired velocity to average desired velocity i e the Location value of the IDM parameter VO distribution This last step means that vehicles going faster than the average for their class remain faster when in the speed limit region and similarly for slower vehicles When a vehicle leaves a speed limit region of road its initial desired velocity is restored Note that a vehicle can enter multiple speed limit regions and still have its initial desired velocity restored 37 UCD LCPC 2008 EvolveTraffic v1 0 4 User Manual Version 0 94 The Gradient Road Feature To specify a section of road with gradient follow the steps as per the Speed Limit Road Feature The Value of a Gradient Road Feature is the slope of the road measured as a percentage EvolveTraffic checks that gradient sections of road do not overlap and that the maximum slope of 15 is not exceeded Effect of a Gradient on a Vehicle The EvolveTraffic configuration file has several parameters that specify how a gradient affects a vehicle In Treiber s work he models the effect of a gradient
28. am crash Parameters that may be changed in the EvolveTraffic ini configuration file are coloured in green as 3 5 tonnes Values in this text are default values and may be changed by a Developer User 7 UCD LCPC 2008 EvolveTraffic v1 0 4 User Manual Version 0 94 Glossary Detector IDM Invisible Mode MOBIL Output Detector Visible Mode Road Feature SDI Treiber A virtual loop detector a location on the road where information on the traffic flow passing that point 1s abstracted Intelligent Driver Model the microsimulation model used in the current version of the program A simulation is run with no output to screen except for the progress bar indicator and no user interaction allowed Minimize Overall Braking Induced by Lane changes the lane change model developed by Treiber When a vehicle passes this form of detector it 1s written to file along with its arrival time Every road and direction must have these detectors since they are the reason for the program s development A simulation is run so that the vehicles are animated on the screen and user interaction with the program can occur Any feature of the road currently only speed limit sections of road and sections of road with gradient are considered single Document Interface the program operates on one EvolveTraffic file at a time similar to the way NotePad in Windows operates Dr Martin Treiber Technisc
29. below the Format column gives the storage type of the data IX refers to an integer of X number of digits including leading or trailing zeros Head I4 Day I2 Month I2 Year I2 Hour I2 Minute I2 Second I2 Second 100 I2 Speed dm s I3 Gross Vehicle Weight GVW kg 100 I4 Length dm I3 Number of Axles I Direction I1 Lane I1 Transverse Location In Lane dm I3 Weight Axle 1 kg 100 I3 Spacing Axle 1 Axle 2 dm 2 Weight Axle 2 kg 100 I3 Spacing Axle 2 Axle 3 dm I2 spacing Axle 8 Axle 9 dm I2 Weight Axle 9 kg 100 I3 68 UCD LCPC 2008 EvolveTraffic v1 0 4 User Manual Version 0 94 SAFT File Format As for the CASTOR table the Format column gives the storage type of the data IX refers to an integer of X number of digits including leading or trailing zeros Note that since the SAFT format does not contain direction or lane identifiers this format is suitable for single lane traffic only Vehicle order 20000 unused number I5 Day I2 Second I2 Second 100 I2 Speed I3 Gross Vehicle Weight GVW I4 Length I3 Number of Axles I1 Weight Axle 1 I3 Spacing Axle 1 Axle 2 I2 Spacing Axle 8 Axle 9 I3 Weight Axle 9 I2 69 UCD LCPC 2008 EvolveTraffic v1 0 4 User Manual Version 0 94 9 2 Appendix 2 Further Documentation The source code documentation gives further detailed information on the algorithms used in the program along with explanations of the source code structur
30. ber does not do this but basic physics suggests that a vehicles acceleration ability is lessened This ability is not modified for downhill gradients UNITS N A NUMBER TYPE boolean use I or 0 VALUE The minimum acceleration ability that any vehicle can have after having its ability modified to take account of a gradient it may be on This number must be greater than zero The program will crash due to a divide by zero or a square root of a negative number if it is not UNITS N A NUMBER TYPE real VALUE This flag specifies if a vehicles braking ability is to be be modified to account for the gradient it is on Included because Treiber does not do this but basic physics suggests that a vehicle can brake easier going uphill This ability is not modified for downhill gradients UNITS N A NUMBER TYPE boolean use I or 0 VALUE Road RoadFeatures Gradient IDM Modifiers T SLOPE C This specifies how the IDM parameter T the safe time headway changes according to the gradient the vehicle is on This value is the number of percent of gradient per second increase in the safe time headway It is increased for the gradient whether uphill or downhill UNITS 7s NUMBER TYPE real VALUE 0 Road RoadFeatures Gradient IDM Modifiers VO MIN 3 0 This specifies the minimum desired velocity any vehicle can have after its desired velocity has been modified to account for the gradient the vehicle is on
31. bsequent lane change can only occur once the specified time delay has been passed T4 ONS 5 NUMBER TYPE real VALUE This is the distance that the front vehicle in any lane considers as being clear road no vehicles in front of them even as it approaches the end of the defined road length This means that vehicles approach the end of the road realistically UNITS m NUMBER TYPE integer VALUE 1000 Road RoadFeatures SpeedLimit SPEEDLIMIT_MIN 10 RS a a eS a See eae ee This is the minimum permissible speed limit that the user can specify Included to keep things more realistic This must be greater than zero UNITS km h NUMBER TYPE integer VALUE 10 Road RoadFeatures SpeedLimit SPEEDLIMIT MAX 200 je aS a ee EEE This is the maximum permissible speed limit that the user can I4 SPSCITYy Included to keep things more realistic UNITS km h NUMBER TYPE integer VALUE 200 This is the maximum permissible slope of gradient that the user can specify Included to keep things more realistic and to conform better with the assumptions made in modifying the vehicles driver f model JP UNITS NUMBER TYPE integer 12 UCD LCPC 2008 EvolveTraffic v1 0 4 VALUE This flag specifies if a vehicles acceleration ability is to be be modified to account for the gradient it is on Included because Trei
32. d This new configuration of traffic 1s useful for bridge loading because it essentially extends measured data which is expensive to obtain 5 UCD LCPC 2008 EvolveTraffic v1 0 4 User Manual Version 0 94 1 2 The User Manual Purpose This User Manual has been written to explain the use of the EvolveTraffic program and to explain its capabilities and limitations It explains the user interface the required input information and the output information This manual does not explain the Intelligent Driver Model IDM used for the traffic microsimulation in the program Further it does not explain how the input data is to be prepared or how the program output 1s to be used Conventions Menus Menu commands are written as Configuration gt Simulation And mean the user should select Simulation from the Configuration menu as shown t CF 5000 Test etr Evolve Traffic File Permie Run Tools View Help Simulation Traffic Model Alt T EL Road Features AlE F Traffic Flow Metrics Alt Mm 700 00 Fear Time vay v uuu Keyboard The use of shortcut keys is indicated as Ctrl I And means that the user should press the Control and TI keys simultaneously 6 UCD LCPC 2008 EvolveTraffic v1 0 4 User Manual Version 0 94 Notices Points of significant importance are denoted as Important Typically failure to adhere to these points will result in unexpected behaviour or a progr
33. e An example output below illustrates the Detector Classes hierarchy The source code documentation is included in the installation package To open In the program s installation folder open the Documents htm1 folder and double click on the index html file Alternatively you can view a PDF of the documentation in the Documents folder SourceDoc pdf Detector Class Reference amp m DetectarType m_RoadLength amp m DirFos Mm Localan m_Nolanes amp m vehicleType amp m CurentTime amp m Totall ne amp m Timelsteral m_Interealhlo m s vehicles m_MetncsDir getDirPas Dstecton Deedar EndOutpuit add ehiclef CheckFotluipuiTime getLocation gelDetectorlyped amp IntOuiputF ilesi amp dolntervalCuipuid Reiniti amp MapDirTostingf MapDetvekType ToStingi amp FindDetectorAarival Timer ana lhangeDetactor m vChangeEvents m CutFile verbose m_OuiF ile_Compossion m Arge m OuiF ile Spacelime T 1 lutF ilg m GuiF ile Rate m vehicle ypes m NoLaneChangeSvents m velocities m Distance ntens m wHeadways m NoDisilntervals m TimeCfLasidrrival m xLustancaelntereal Ti whovenmcles m vDistlrt LCECount FlnHanrllnr m hatrirsDirz pa so aati m plilsHandler HUEINC SUE ect Zu LaneChanageDletecrem EndOutputi er eee isa LeneChangeDetectar addehiclat ser ndier i Ega NEUF ag FWritevebirlasTaF ila addE verit dolma
34. eft button on the cell to edit and type in the value 2 Use the Tab and the arrow buttons to move between cells When the appropriate cell is selected typing a value places that value in the cell Copying Parameter Sets Between Vehicle Classes Since it is likely that most parameter values will be the same between classes the dialog allows the user to copy parameters sets between vehicle classes For example to copy the parameter set from vehicle Class 2 Large Truck to Class 3 Crane 1 Be currently defining parameters for vehicle Class 3 Crane vehicle by choosing the Vehicle Class from the drop down box labelled IDM Parameters for Vehicle Class 2 In the second right drop down box select Class 2 Large Truck 3 Press the lt lt Copy From lt lt button where the arrows indicate the direction in which the copying 1s taking place This is as shown below IDM Traffic Model Configuration IDM Parameters for Vehicle Class Class 3 Crane lt lt Copy er ad Class 2 Large Truck Distribution Location Scale 4 Safe time headway T 5 Mormal 1 50 Maximum acceleration a ris Normal 1 00 Comfortable decceleration bim s 2 Normal 2 00 Minimum jam distance s0 m Normal 1 00 Elastic jam distance 1 m Mormal 20 00 Desired velocity vO km h Normal 78 00 Acceleration exponent delta Constant 4 00 Lane change politeness Factor p Constant 0 20 Outside lane bias Factor delkadbias Constant
35. er Manual Version 0 94 Headway This detector assembles the headway data for the chosen vehicle type s EvolveTraffic considers headway to be the time between two successive vehicles in the same lane arriving at the detector Since EvolveTraffic is run in discrete simulation steps the time of arrival at the detector is based on an interpolation which is based on constant velocity over the simulation time step The program records headways calculated in this manner for each lane of the specified direction and for the specified vehicle types The last two parameters are e Time Interval the interval in simulation time between the detector outputs of the recorded data This value can be reasonably large to avoid the slow process of accessing the hard drive e Location Step this value specifies the location of the detector Refer to Section 7 4 for information on the data output by this detector 4 UCD LCPC 2008 EvolveTraffic v1 0 4 User Manual Version 0 94 Composition This detector assembles the composition of the traffic stream at the detector location Since this statistic only makes sense if a range of vehicle types is accounted for it only performs output if the user selects All Vehicles or All Tucks in the Vehicle Type drop down box The program outputs the number of each type of vehicle to pass the detector during the previous time interval Thus the last two parameters are e Time Interva
36. formative 6000 5000 su E E 4000 D gn E H c S 3000 m 7 E a 2000 j gw Left To Right g e Right To Left 1000 0 A 0 1000 2000 3000 4000 5000 6000 7000 Time s 64 UCD LCPC 2008 EvolveTraffic v1 0 4 User Manual Version 0 94 Noting that each change is represented by a point this plot shows that a large number of lane change events occur at about 1000 m and as time progresses this point moves backwards towards the start of the road at 0 m This is explained by the presence of the speed limit region previously mentioned and as shown below that causes congestion that progresses backwards necessitating earlier lane changes Further along the road beyond say 2000 m there are a number of vehicles returning to the outside lane and very few overtaking events Sim Time Day 0 0 21 59 52 Real Time Day 0 0 00 17 59 Om Car Small Truck Large Truck Crane Low loader THES E B B S Output Detector Flow Density Detector Headway Detector Composition Detector Lane Change Detector 500 m ii B S 14 8 ERES B KKK Bs ate e d nat SX e CRY rer erste x vet c LM Dx xe Bau i x GJ tt tt 0000006 0000006 0000000066 0000060666 RR RR ORTA RA tallet ga a a 767A a ae es WA S Sd e Bete ose PER Soo PS e e ER Ko X uS oe Ex Los RS Ses wok ot
37. has the ability to produce large amounts of output especially for long or heavily congested traffic files The program accesses the hard drive at every time interval specified for each detector Section 5 5 and this can significantly slow the program s execution Therefore it 1s recommended that statistical detector output is only used when required for calibrating the IDM traffic parameters For execution of the program for the sole purpose of obtaining another randomized traffic file based on calibrated IDM parameters it is better to have no detector output For calibration purposes the statistical detectors output 1s comprehensive and should be sufficient to obtain good matches between measured and simulated traffic This process is not trivial only macroscopic statistics can be used as the basis for comparison of measured against simulated traffic Besides the output traffic file all detector output files are in Comma Separated Values csv file format which can be read by any spreadsheet viewer such as MS Excel They are output to the directory as specified by the user in the Simulation Configuration dialog Section 5 2 53 UCD LCPC 2008 EvolveTraffic v1 0 4 User Manual Version 0 94 7 2 Traffic File For every simulation run each vehicle is output to file at the time it hits the location of the Output Detector Section 5 2 for its direction The physical properties of the vehicle are maintained through
38. he Universt t Dresden developer of the IDM traffic microsimulation model 2 8 UCD LCPC 2008 EvolveTraffic v1 0 4 User Manual Version 0 94 1 3 Release History EvolveTraffic Program Version Date Description 1 0 22 8 08 e Initial release 1 0 1 1 9 08 e Bug fix SAFT file format removed unnecessary GVW kN to kg 100 conversion 1 0 2 10 9 08 e Bug fix Cars were being identified as small trucks fixed e Bug fix background to legend entities were coloured when no road features were to be drawn fixed e Bug fix the lane number of Direction 2 vehicles was incorrect for CASTOR output fixed e Bug fix a base year of 2005 was assumed in reading the traffic file This is changed to 2000 e Bug fix SAFT file format now padded with zeros for POLLUX to read e Disabled for release Added option to output cars to output traffic file or not useful when only truck loading is of interest Note this requires the etr file structure to change and this change is not backward compatible 1 0 3 14 9 08 e Bug fix text for road features in single lane roads was off centre fixed e Added support for All Trucks output in the detectors dialog and throughout program Distributions in IDM parameter box re ordered Gap information added to vehicle information tooltip e Revised calculation of flow and density output to use the space mean velocity e Bug fix simulation does not end due to D
39. he effect of including various detector output or even just the detector s time intervals Section 5 5 26 UCD LCPC 2008 EvolveTraffic v1 0 4 User Manual Version 0 94 5 EvolveTraffic Input 5 1 Introduction The output from EvolveTraffic 1s only of use if the input data is representative of the traffic stream of interest Use of the program is therefore an iterative process the Developer User must run the program to get results that may be compared to measured traffic statistics and macroscopic properties Depending on the comparison the Developer User must then change some of the traffic configuration properties as appropriate and re run to check on the revised comparison This process may take many iterations To minimise effort all the input data for the program can be saved into EvolveTraffic files file of type etr Once a traffic stream has been calibrated that traffic may be run over many different road configurations lengths speed limits and gradients Again a different etr file may come in useful at this point Note however that since the IDM properties may be probabilistic Section 5 3 running the same traffic over the same road configuration can result in slightly different traffic output files All of the above aspects mean that the a calibrated site may be used as the basis for many hundreds of different traffic configurations 21 UCD LCPC 2008 EvolveTraffic v1 0 4 User
40. ing D 2007 General lane changing model MOBIL for car following models Transportation Research Record Journal of the Transportation Research Board No 1999 Transportation Research Board of the National Academies Washington D C pp 8694 Treiber M and Helbing D 1999 Explanation of observed features of self organization in traffic flow preprint cond mat 9901239 arXiv cond mat 9901239v1 Treiber M and Helbing D 2001 Microsimulations of freeway traffic including control measures Automatisierungstechnik 49 pp 478 484 http www arxiv org abs cond mat 0210096 79 UCD LCPC 2008
41. irNegEmpty set to false when only one direction fixed 1 0 4 6 8 09 9 UCD LCPC 2008 EvolveTraffic v1 0 4 User Manual Version 0 94 EvolveTraffic Manual Version Date Description 0 9 0 91 0 92 0 93 0 94 22 8 08 1 9 08 10 9 08 14 9 08 6 8 09 Initial release e Updated EvolveTraffic version number e Added manual and program release histories Updated manual for v1 0 2 Updated manual for v1 0 3 Updated manual for v1 0 4 10 UCD LCPC 2008 EvolveTraffic v1 0 4 User Manual Version 0 94 2 Installing the Program 2 1 System Requirements The program has been tested on Windows XP It is expected to run on Windows Vista and on Windows 2000 also The program is a single threaded application and so cannot take advantage of multi core processors Therefore for maximum speed prefer a computer with a fast single processor over a computer with a multi core slower processor The program does not require much memory because e the input file is read in line by line as required with a buffer of default 10 vehicles being held e the memory a vehicle uses is released when the vehicle leaves the road e memory used for the storage of the metrics detectors data is released upon writing to file which occurs at user specified intervals usually about 60 seconds of simulation time For long roads with a large output time interval a computer with I GB of RAM is recommended so
42. k Length m Tick Interval im Border Top m Border Bottom m Border Left m Border Right m Value 0 20 10 00 1 00 4 00 3 00 2 00 1 00 1 00 1 00 ann n 20 00 40 00 20 00 100 00 Cancel e Overall Scale the current scale of the drawing e Widths Scale the exaggeration applied to the road and vehicle widths so that it is easier to visualize the vehicles e Time Warp Factor the ratio between simulation time and real time e Lane Width the width of a lane as drawn prior to application of the Widths Scale factor e Vehicle Width the width of a vehicle as drawn prior to application of the widths scale factor 47 UCD LCPC 2008 EvolveTraffic v1 0 4 User Manual Version 0 94 e Vehicle Length Scale a factor that allows the length of a vehicle to be exaggerated in order that a more reasonable aspect ration is kept once the Widths Scale factor has been applied Note that when this 1s not unity it can appear that vehicles overlap on the road when very close bumper to bumper traffic set this to unity to observe that this is not the case Note also that the vehicle length is exaggerated from the front of the vehicle that is the extra length is applied to the back of the vehicle always Show Velocities set this value to zero to turn off any other value turns it on the display of the velocities of each vehicle shown as a text output overlaid alia E E E Ee Es Ee
43. l the interval in simulation time between the detector outputs e Location Step the location of the detector Refer to Section 7 5 for information on the data output by this detector 42 UCD LCPC 2008 EvolveTraffic v1 0 4 User Manual Version 0 94 Lane Changes This detector assembles Lane Change statistics A Lane Change Detector takes account of lane changes that occur anywhere in the specified road direction and so it is only necessary to specify one Lane Change Detector per direction Specifying more Lane Change Detectors will only slow the program s execution The last two parameters are e Time Interval the interval in simulation time between the detector outputs e Location Step for a Lane Change Detector the Step is the spatial discretization required for outputting the lane change rate as defined by Trieber 3 This value should not be more than 1000 m Refer to Section 7 6 for information on the data output by this detector 43 UCD LCPC 2008 EvolveTraffic v1 0 4 User Manual Version 0 94 6 Running EvolveTraffic 6 1 Introduction The usual procedure followed when using the program 1s 1 Define the input data either by using the dialogs Section 5 or by opening an etr file Section 5 1 2 Run the program in Visible Mode Section 6 2 to view the behaviour of the traffic Section 4 and to obtain intermediate information Section 4 5 3 Examine the various detector
44. mand changes to Resume and resumes the simulation when clicked Tools gt Stop Stops the current simulation Tools gt Preferences Displays the Preferences dialog see Section 6 3 View gt Toolbar Choose whether or not to display the toolbar View gt Status bar Choose whether or not to display the status bar at the bottom of the screen which contains the progress bar during the simulation Help gt About This shows information about the copyright developers and version of the program running 20 UCD LCPC 2008 EvolveTraffic v1 0 4 User Manual Version 0 94 4 3 Toolbar Re pe n Hp lb mle i Ze A Le ohms sk pl php de The buttons indicated provide a shortcut to the menu commands as follows e New File gt New e Open File gt Open e Save File gt Save e Print File gt Print e Simulation Configuration gt Simulation e Traffic Configuration gt Traffic Model e Road Features Configuration gt Road Features e Metrics Configuration gt Traffic Flow Metrics e Run Visible Run gt As Visible e Pause Tools gt Pause Resume e Stop Tools gt Stop e Run Invisible Run gt As Invisible e Zoom In Tools gt Zoom In e Zoom Out Tools gt Zoom Out e Speed Up Tools gt Speed Up e Slow Down Tools gt Slow Down e Preferences Tools gt Preferences e About Help gt About 21 UCD LCPC 2008 EvolveTraffic v1 0 4 User Manual Version 0 94 4
45. n a format particular to EvolveTraffic and is not d in standard ini format 71 Do NOT alter the sequence of the variables the program assumes Fy the sequence as given below FF Please refer to Treiber s references for more information on these parameters IDM LANECHANGE MIN GAP 2 0 LL The minimum gap toe the rear of the vehlcle in front in the target lane or from the front of the rear vehicle in the target lane to fi the rear or the current vehicle A lane change is not considered if both these gaps are not larger than this parameter specifies Lf UNITS om NUMBER TYPE real VALUE The minimum clear space in front of the next vehicle to enter the road before it is allowed onto the road 17 UNITS M NUMBER TYPE real Ly VALUE Zoe The maximum permissible deceleration any vehicle can undergo This number provides a check on the realism of the random braking ability generated according to the user defined IDM parameters LJ UNITS m s 2 71 UCD LCPC 2008 EvolveTraffic v1 0 4 User Manual Version 0 94 NUMBER TYPE real always negative VALUE cal loge IDM T_DELAY 1 6 This specifies the time gap between consideration of lane change events for a particular vehicle Once a lane change event has ll occurred for this vehicle the timer is reset and su
46. ne cpc fr Traffic Data Dr Manel Hannachi hannachi Icpc fr Development Dr Bernard Jacob For further information please contact colin caprani ucd ie Dr Colin Caprani August 2008 2 UCD LCPC 2008 EvolveTraffic v1 0 4 User Manual Version 0 94 Contents dnfrodictUOllos incite E 5 TO ON NNN 5 MENN 6 ES RMN 9 2 dustallme the Program 5e diese nest EN NER ENSE NAUES IEEE eee 11 21 SERENA a one one 11 Z2 Aae 12 3 JAbOULEVOIVeTErdftfiQO uinecatoie is Peu ve PERI Ee vi RETE ee 13 SM MEN TOC 0 0 ORRE a de TEE 13 3 2 EvolveTraffic Capabilities and Limitations eeeuussl 14 3 gt VERN ETE 16 4 Th EvolveTraffic User Interface sucsisiaissisccinsecsaccosesscoceannnncdsvessssondexewevcsss 17 BD LDH OS AC VE PRE NE EN EE a uA 17 2 Messer 18 G3 TOODA a ete oU DU DRESD AN OU EP UE Uds 2 24 Sboreu IK CY Sor RITE TET Um 22 15 Other Intertace PN ie eco 24 S jEvolveTrafrtio Iinpu l aoscecue e rx IE SEP EE E RE ETE VEIT 27 DL Moda 0 EE imas at dd on ar 27 2 2 s inulation CONTE 8 ON RE 28 2 9 F R Model CT ON esaa nd ne 31 23 4 Road Fers CoS 35 55 Trae Plow Metrics Conte UEaUOT disce Seb are 39 6 RUNING Evolve PEAT ssns NEA a 44 DSL 8 0 0 1 618 0 d eer eer Teen EE aa ele et ce oni tua ELA ete 44 02 SUN NOT rene a ad en de staan sited 45 OS od ROSSA ANT ee Rado ho GE Re ee ee ere cee na eR ee nt eee 47 3 UCD LCPC 2008 EvolveTraffic v1 0 4 User Man
47. nly lanes cannot yet be modelled 15 UCD LCPC 2008 EvolveTraffic v1 0 4 User Manual Version 0 94 3 3 User Levels There will be two main types of user of EvolveTraffic Ordinary User This type of user is typically interested in running the program to generate new traffic configurations They will be using a set of IDM parameters previously calibrated but may be considering different road layouts Usually they will not require the traffic metrics detectors output Indeed once the road layout has been developed this user will probably run the program in Invisible Mode to get the output traffic file as quickly as possible Developer User This user is using the program to calibrate it against measured real traffic This user will be using the traffic flow metrics detectors in order to compare measured traffic properties against the program s output in order to develop a set of IDM parameters that model the measured traffic This user may also need to change some of the program configuration settings in the EvolveTraffic ini file in order to achieve this goal This user will mostly work in the Visible Mode for visual verification of the traffic behaviour and to use the DataTips to see vehicle information during the simulation 16 UCD LCPC 2008 EvolveTraffic v1 0 4 User Manual Version 0 94 4 The EvolveTraffic User Interface 4 1 Introduction The EvolveTraffic program has a Single Document Interface SDI
48. of number of lane changes per hour per kilometre 1 hr km Taking At 1 min and Ax 200 m a single lane change Is equivalent to a lane change rate of 1 1 60 200 1000 300 hr km Therefore the lane change rate values in the file will tend to be round numbers due ot the above calculations Further this metric is calculated for each time interval at each step along the road leading to a large matrix of lane change rates An example Is 62 UCD LCPC 2008 EvolveTraffic v1 0 4 User Manual Version 0 94 A E 2 Time s B 5 120 6 180 RE 240 300 E 360 10 420 11 450 12 540 13 BOU 14 D 15 20 16 fou 17 B40 18 900 18 960 20 1020 21 1080 22 1140 23 1200 24 1260 25 1320 OD 0o O 0DO O O O 0O O O 0O O O 0O O Oo O Oo Oo a a Oo O r3 uma c pcoDmumomi EoIS3SO BIjaalijjgmjgsjgoojojomuejco IR CI CI pomiou iiiliiiiDDomauauijIB yA Ijeurm XoagaeJ yoccojo o c LANE CHANGE RATES BY LOCATION AND TIME Location m T m c pcoDU Iioomiom oDOouliiiliiimosoeojo cocojjo T COL 000 000000000000 oQ o 150 1000 ani 1200 ani 1500 ani BD 2100 1200 1200 1500 BD 1500 1500 BOO 1800 1800 ani ant aur 300 0 1200 300 GOD 300 RE n00000520000002020 05 e c ceo oo 1400 m a E m G G a DE aa G A am G D a D D a OO D ue DS aa DE mue DE a DS mue DE mue DE mue DE mn DE mue DE qu 46
49. peed for human eyes to perceive Invisible Mode rectifies these issues as it is optimised for speed of execution 45 UCD LCPC 2008 EvolveTraffic v1 0 4 User Manual Version 0 94 Invisible Mode When a simulation 1s run in invisible mode the program only does two things 1 Runs the simulation as fast as possible 2 Updates the progress bar The progress bar is therefore the only indication the user has that the program is running This mode can run very fast with simulation time to real ratios of over 5000 easily achieved When running in Invisible Mode the program will require the full use of the processor it is being run on Users with multi core processors will be able to run other programs as EvolveTraffic runs in the background However users with single core processers will not be able to use other programs and the computer will appear frozen until the simulation is complete For such users to optimise simulation times it is advised that no other programs be running at the same time 46 UCD LCPC 2008 EvolveTraffic v1 0 4 6 3 Program Preferences Ordinary User Preferences User Manual Version 0 94 User preferences can be specified though the User Preferences dialog shown here The parameters are Setting Overall scale meters pixel Graphics Preferences Widths Scale Time warp Factor Lane width im Vehicle width m vehicle Length Scale Show Velocities Show Legend Tic
50. r integer integer RGB 007073 colour for the legend text DES Zoo 16 250 edo Zao 3 integer integer integer REB 252000 colour for the output detectors VES 206 GE bu cU To co integer integer integer REB 0 255 0 4 colour for the flow density detectors Or BO 255 UE 255 0 uto 59 integer integer integer RGB OFU 255 4 colour for the headway detectors 20255 00 00 2585 0 uo 120550 integer integer integer RGB 0 0 09 colour for tratiuc i low Composition detectors VEG gue UL CO owe DEG 5 integer integer integer RGB 2598y 0 0 UCD LCPC 2008 EvolveTraffic v1 0 4 User Manual Version 0 94 LI The display Colour for the Speed Limit r gions fe UNITS ROB 0 to 255 0 TO 255 0 820255 NUMBER TYPE integer integer integer VALUE 75000 View Colours DrawElements CLR FEAT GRADIENT RGB 0 255 0 FI The display Colour for the gradient regions fo NEES CBGBCUS CBO 2554 0 co 255 D to 255 3 NUMBER TYPE integer integer integer 78 UCD LCPC 2008 EvolveTraffic v1 0 4 User Manual Version 0 94 9 4 1 2 3 4 5 Appendix 4 References Treiber M Hennecke A and Helbing D 2000 Microscopic Simulation of Congested Traffic in Traffic and Granular Flow 99 Eds D Helbing H J Herrmann M Schreckenberg and D E Wolf Springer Berlin pp 365 376 http www mtreiber de Kesting A Treiber M Helb
51. r Manual Version 0 94 The LC Comp File This file gives information pertaining to the composition of lane change events by vehicle type Since this output only makes sense if the vehicle type for this detector is All Vehicles no output is performed for other vehicle types An example of this file s output for a traffic stream with no cars 1s A E E E F LANE CHANGE COMPOSITION OF EVENTS 2 Time Interval Car Changes Smalllr Changes LargeTr Changes Crane Changes LowLoad Changes 3 B 1 1 1 1 120 3 0 0 0 25 180 4 1 1 1 b 240 1 5 1 1 7 300 4 2 0 0 8 360 1 B 4 1 1 E 420 4 3 1 1 10 AO 0 7 1 1 0 14 540 10 1 1 1 EE pog 5 1 1 1 13 D fi 1 1 The number of lane changes that occurred in the previous time interval of each vehicle type is as indicated 61 UCD LCPC 2008 EvolveTraffic v1 0 4 User Manual Version 0 94 The LC Rate File This file contains the lane change rate for each time interval for each Step see Section 5 5 along the road length This metric is as defined in the paper on the lane change model MOBIL 3 The lane change rate 1s Mic Hn AL Ax In which e r p x t is the lane change rate and is a function of both time distance and traffic density e n is the number of lane changes that occurred in the time interval At e At and Ax are the temporal and spatial discretizations The lane change rate is measure in units
52. rralQut putt FAR PEN EE IniCiurgulbFiles elit i inde si Ber enn Sc REI TN add ahiclaf daintemalCiutaut InitCompositionF ilet part Relrz InitHeadwayFilefl CEU SR InitarbosaeFilar fnitFlowDeansit Filet Indtarmposdsonkiled Jataornposihonrtubaultfi InASaaceTimeFiled daHeadwvean Out puti Int steFilei doFlowDiensity Output dovarboseDutputi AddCurerivahic ad doCompostdonQutpu mitverctorsi do aace Niredbutpuld at ostringi doRateDutputij AdeCurrentEveriz 70 UCD LCPC 2008 EvolveTraffic v1 0 4 User Manual Version 0 94 9 3 Appendix 3 EvolveTraffic ini Configuration File M EVOLVETRAFFIC PROGRAM CONFIGURATION FILE nnn Notes 1 This file is used by EvolveTraffic to set environment variables that may be altered by the user 2 Before altering this file make a back up copy even though the Z default values for each parameter are given in the description ff d The User dan insert their own Comments in this tilep once they p are preceded by 19 As No checking of the validity of this file is done by the program If after a change to this file the program does not run or ee exhibits strange behaviour please use your back up 5 You can email colin caprani ucd ie with any questions or for copy OL the default file to save reinstallation 6 This file is i
53. rsion 0 94 e Border Top the border between the top of the screen and the legend and clocks e Border Bottom currently obsolete e Border Left the border between the start of the road and the edge of the window e Border Right the border between the end of the road and the edge of the window 49 UCD LCPC 2008 EvolveTraffic v1 0 4 User Manual Version 0 94 Developer User Preferences These are as specified in the EvolveTraffic ini configuration file found in the program folder Refer to Appendix 9 1 for the default version of this file and for the extensive explanatory comments Note that the user can add their own comments similar to C style single line comments to this file by preceding the line with two forward slashes Some of the configuration parameters may be brought into the main interface in future versions for ease of use 50 UCD LCPC 2008 EvolveTraffic v1 0 4 User Manual Version 0 94 6 4 Examples Included with the installation are three example applications of EvolveTraffic in the Examples folder of the program installation folder Open the relevant etr file and run in Visible Mode to see the examples or in Invisible Mode to get straight to the detector output Example 1 Ex 1 etr This example represents a congested truck only traffic file run on a road of 5 km length with several speed limit and gradient regions Sim Time Day 0 1 00 00 00 Heal
54. s for the Flow Density Detector file Section 7 3 Output The output for each time interval 1s simply the count of the number of vehicles of the vehicle type that passed the detector during the previous time interval Each time interval writes to a row and each vehicle type has a column All best seen in the example output taken from a traffic file without cars E E E 1 No Cars No Small Trucks No Large Trucks No Cranes No Low Loaders 2 0 0 1 3 1 d 0 5 4 Be 0 3 12 1 5 1 12 0 nee 1 5 12 1 5 11 0 E n 2 4 D 10 1 1 z 1 1 11 1 1 1 12 1 5 Ha 1 1 14 1 3 1 BE 1 5 58 UCD LCPC 2008 EvolveTraffic v1 0 4 User Manual Version 0 94 7 6 Lane Changes File The output for a Lane Change Detector is made up of the following files Il LC All vvv ddd csv LC Comp vvv dddad cesv LC Rate vvv ddd csv p qe LL Tyv AU In which vvv and ddd have the same meanings as for the Flow Density Detector file Section 7 3 The LC All File This file outputs the raw information relating to lane change events The format of the file 1s best seen by example iis E D NE 1 LANE CHANGE VERBOSE OUTPUT OF EVENTS 2 ime Position From Lane To Lane Right Left Type Be 02 52 4051 3 Lett smallTr 5 95 02 40272 3 Lett smallTr b 115 02 1072 3 Left cmallTr Fi 134 52 4056 3 Lett small
55. se parameters have had the same value of each vehicle class he considers EvolveTraffic extends this by allowing vehicles within a class to have varying parameters that is the program allows probabilistic parameters However the program retains the ability to specify deterministic or constant parameter values Each parameter can be distributed according to a number of distributions Since distributions require different numbers of parameters the most general parameter set of location scale and shape is available However setting a parameter consider shape for example for a distribution that does not require it consider the Normal distribution for example has no effect It is up to the user to decide upon the distribution that best suits the parameter being modelled The supported distributions with parameters and some comments are 1 Exponential Location and Scale parameters may be useful for some parameters such as Safe Time Headway Not suitable for most parameters for example Desired Velocity 2 Log Normal Location and Scale parameters 3 Gamma Location and Scale parameters 4 Gumbel Location and Scale parameters 32 UCD LCPC 2008 EvolveTraffic v1 0 4 User Manual Version 0 94 5 Poisson Location and Scale parameters provides a continuous approximation to the discrete distribution only valid when the location parameter is greater than 10 6 GEV Location Scale and Shape parameters al
56. t Exit Closes the program 18 UCD LCPC 2008 EvolveTraffic v1 0 4 User Manual Version 0 94 Configuration Run Tools Configuration gt Simulation Brings up the Simulation Configuration dialog box see Section 5 Configuration gt Traffic Model Brings up the Traffic Model Configuration dialog box see Section 5 3 Configuration gt Road Features Brings up the Road Features Configuration dialog box see Section 5 4 Configuration gt Traffic Flow Metrics Brings up the Traffic Flow Metrics Configuration dialog box see Section 5 5 Run gt As Visible Starts the simulation in the Visible Mode see Section 6 2 If the simulation is currently paused this restarts the simulation as per Tools gt Pause Resume Run gt As Invisible Starts the simulation in the Invisible Mode see Section 6 2 Tools gt Zoom In Zooms into the road making the road and vehicles larger on the screen Tools gt Zoom Out Zooms out from the road making the road and vehicles smaller on the screen Tools gt Speed Up Speeds the simulation up the ratio of simulation time to real time increases Tools gt Slow Down Slows the simulation the ratio of simulation time to real time reduces Tools gt Pause Resume 19 UCD LCPC 2008 EvolveTraffic v1 0 4 User Manual Version 0 94 View Help Once a simulation is running this pauses it If a simulation is paused this com
57. that other programs can continue to operate successfully 11 UCD LCPC 2008 EvolveTraffic v1 0 4 User Manual Version 0 94 2 2 Installation To install the program carry out the following steps 1 Extract the zip archive to a folder 2 In that folder double click on the file Setup exe 3 Follow the on screen instructions to install the program 12 UCD LCPC 2008 EvolveTraffic v1 0 4 User Manual Version 0 94 3 About EvolveTraffic 3 1 Introduction EvolveTraffic broadly performs the following steps 4 3 6 A file containing a record of vehicles 1s opened and linked to the traffic file The simulation commences Vehicles are read from the traffic file and enter the road at the time indicated 1n the traffic file The vehicles proceed along the road with the driving behaviour simulated user a traffic microsimulation model When a vehicle arrives at an Output Detector it is written to the output traffic file with the time of arrival at the Output Detector The simulation progresses until all vehicles have been read from the traffic file and have exited the road 13 UCD LCPC 2008 EvolveTraffic v1 0 4 User Manual Version 0 94 3 2 EvolveTraffic Capabilities and Limitations Capabilities EvolveTraffic is able to Read data from CASTOR or SAFT format vehicle files manipulate vehicles according to the IDM traffic microsimulation model as they progress
58. though strictly an extreme value distribution its flexibility due to its three parameters allows many phenomena to be modelled accurately 7 Normal Location and Scale the standard Gaussian distribution of parameters mean and standard deviation 8 Constant Location this is the deterministic option as no random numbers are generated and the parameter takes the value Location for all vehicles in the class Important EvolveTraffic does not check the validity of the distribution values entered It 1s up to the user to verify that the values and distribution chosen are realistic and appropriate both to the distribution and the parameter Choosing inappropriate values or distributions will have unexpected consequences which may include the program crashing For calibration purposes it is recommended to use Constant parameters initially and then use appropriate distributions with increasing values of Scale This allows the impact of the probabilistic parameter values to be assessed In any case since most parameters cannot be directly measured the Scale or Shape parameters must be based upon judgement and the effect upon the macroscopic traffic statistics Defining a Parameter Set Choose the Vehicle Class from the drop down box labelled IDM Parameters for Vehicle Class There are two methods of entering data se UCD LCPC 2008 EvolveTraffic v1 0 4 User Manual Version 0 94 1 Using the mouse double click the l
59. ual Version 0 94 Ou PvP 51 Te EvolveTrraffic OUQU E iuo rrt fr rre ENS REPE ERE I e IER e EE TENES ER UNS TEES 53 ride ET 53 TSN 54 TD OVDS PP 55 DU N S EN SON P 57 To svare 58 ODA CARS ENE E ne 59 8 FAQs and TroubleShooting ssssssersesvrsessssvnsennessnsennennnsenneneneennnssnsennesenvsnsenenese 66 SE FAOS mr 66 52 Troubles 6160 8 161 earm A T E A ee 67 9 APPeNdICES PE D D EI EU 68 9 1 Appendix I CASTOR and SAFT File Formats 68 9 2 Appendix 2 Further Documentation 70 9 3 Appendix 3 EvolveTraffic ini Configuration File 71 Od JAppendbe4 RCICIENCES in A TOE 79 4 UCD LCPC 2008 EvolveTraffic v1 0 4 User Manual Version 0 94 1 Introduction 1 1 TheEvolveTraffic Program EvolveTraffic 1s a program that simulates driving behaviour for the purpose of estimating highway bridge loading Vehicles are read into the program and they are simulated driving along a road which may have speed limit sections and gradient sections The vehicles interact with one another and may perform lane changes Various statistics of the traffic can be output at various points along the road When the vehicles pass the Output Detector they are written to the output file The output traffic file contains the same vehicles as the input traffic file but represents a different configuration or order of the traffic one that depends on the features the user has specified for the traffic and roa
60. veTraffic v1 0 4 User Manual Version 0 94 Output The format of the Flow Density output is e The first column contains an index representing the time interval for which the output was made Next for each lane in the direction that the detector considers for the particular time interval considered we have three columns e Density veh km the measured traffic density of the vehicles considered e Flow veh hr the flow of the vehicles considered e Ave Vel km h the average velocity of the vehicles considered Finally for the direction as a whole we have the three columns of Density Flow and Ave Vel as before An example output for a two lane direction 1s A B D E F G H J 4 Lane 1 Lane 2 Totals 2 Interval No Density tveh km Flow wehh Avg Vel km h Density vek km Flow wehh Avg Vel km h Density veh km Flow veh hr Avg Vel km h 3 1 1 4ND D 1 AND 1 AND 0 1 AND 1 AND D 1 AND 4 2 4 55358 360 79 067 0 673806 BO 03 0464 5 24745 420 168 103 LE B 11 0702 roi 70 4591 2 18971 180 B2 2028 13 26 960 152 662 6 4 14 3979 aen bb b 53 3 10109 240 7 3921 17 499 1200 144 066 5 14 6639 aen 65 467 3 65787 300 22 0149 18 3218 1260 147 482 5 14 8338 S60 64 691 3 76076 300 79771 16 6005 1260 144 462 E 7 14 0666 ann 53 8813 5 60274 420 74 9533 19 6694 1320 138 945 10 B 15 1851 aeu 63 2197 3 05794 300 77 7618 19 0431 1260 140 982 11 g 15 1838 EZ 53 2248 3 92699 300 76 3944

EvolveTraffic - User Manual v0.94

Contents

Download Pdf Manuals

Related Search

Related Contents