Graphical User Interface (GUI)

Some recent improvements include:

You can now customize the vehicle's 3D view of an inside camera instead of relying on the 60o default view.

The system now remembers the data selected in the path assignment folder of the OD Matrix editor when opening another OD Matrix editor.

The Restore button in the Real Data Set editor updates the path of the Real Data reading file if it is in a different location from the one specified.

View Mode labels are now drawn on the side of the sections rather than the top.

When cutting in two a section before a turning closure, a forced turning or a rerouting, the affected traffic management actions are now linked to the end of the original section.

Dynamic simulators

We have improved memory cleanup after a replication run.

Actuated control: we have added 2 new parameters to actuated detectors to allow the detector call to either extend the current phase or add a call to the actuated phase.

You now have the option to deactivate messages in the log window to enable a faster simulation.

Microscopic simulator:

We have improved the way simulation vehicles are drawn in curved turning sections in both 2D and 3D Views, as well as in sections with altitude in 3D views. We have also rectified the problem of cars being drawn backwards in some circumstances.

In a microsimulation, there are now two attributes to distinguish a lost vehicle from a vehicle that has missed a turn.

Traffic management strategies can now involve public transport vehicles.

When gathering detection data in a microsimulation, for each detector that distinguishes by vehicle type, we can now generate the instant presence and speed of each vehicle type in addition to those for all vehicles.

Lane closure information is now propagated at incoming turnings.

Vehicles enter the model in a lane that is good for them in terms of the Look Ahead. If all the good lanes are reserved for a different vehicle type, then they enter the model using an adjacent lane that is not reserved but does not allow them to make their next turning.

Mesoscopic:

We have added turning and node statistics for mesoscopic simulation, which are available in the Aimsun database and time series.

Macroscopic:

Traversal operation is now permitted on a sub-network matrix.

Data analysis:

Improvements in the output comparison include easier access to the different options, the inclusion of relative and absolute differences and the comparison of averages and any pair of time series e.g., replication, average and static traffic assignment.

Scripting:

We have added functions for accessing pedestrian information for boarding and alighting at a public transport stop.

We have also added functions for accessing the micro simulator’s turning connections and conflicts.

Miscelaneous:

The Aimsun interface is now available in Portuguese.

We have corrected spelling errors in the templates as well as the manuals and exercises.

HASP drivers are now Linux-compatible.

Bugs fixed

Platform:

Aimsun file size no longer increases rapidly when gathering OD Pair outputs.

When creating a roundabout using the roundabout tool, the new sections now take the expected values from the road type.

When editing a Lane Closure traffic management action for a multi-segment section that affects only one segment, the specified segment is now stored correctly in the action.

When editing a public line time table, you can now store the Link Delay Time field.

Graphical object Z coordinates now update properly when loading Aimsun 6 networks into Aimsun 6.1

You can now record different parts of a microscopic simulation into the same video file.

You can now edit a dynamic bookmark created from the Bookmark Editor window.

We have eliminated erroneous warnings issued by the Check and Fix Network tool. If a section attractiveness rating is not 0, then no warning to that effect is issued. Also, no warnings are issued about supposed errors in the ICF and ICFVT functions when no such errors are present.

Micro:

We have improved the microscopic simulator models to avoid situations whereby 2 blocked vehicles would give way to each other.

Public transport vehicles no longer exit a compulsory public class lane unexpectedly.

If a public transport stop is located just before a lane closure or an incident, public transport vehicles now enter the stop as expected.

The Look Ahead model now functions properly in congested situations when a vehicle is in Zone 3.

Traffic management closed lane actions by segment no longer close the entire lane instead of the specified segment.

When storing statistics in a microscopic simulation for equipped vehicles crossing detectors, you can now store the idptline in the DETEQUIPVEH table correctly.

You can now allow for the vehicles circulating in the entire stream when calculating StreamIEM statistics.

Aimsun now includes in the replication outputs public transport vehicles ending in a terminal.

Aimsun now gives Minimum Dwell correct consideration in a pre-emption.

Simulation vehicles now have brake lights and indicator lights.

Vehicles no longer freeze at certain points, particularly on ramps.

Meso:

Detectors located in the narrowest part of a section with an off-ramp now allow for vehicles exiting from the off-ramps.

Lane selection model and look-ahead model have been improved.

Several public transport issues detected have been solved.

Actuated control plan is implemented as specified.

Path assignment result files bigger than 3Gb can be used as an input for a simulation.

Macro:

The paths from a macro experiment are now properly restored.

Matrix adjustment is now correctly calculated when there are detectors covering only a lateral lane and not the whole section.

The macro assignment results are now correctly restored from the database when using the 'Retrieve Static Assignment Results' option if the assignment affects a single vehicle type.

Legion for Aimsun:

Pedestrians now longer pass over a copied Pedestrian Polygon Obstacle.

Pedestrians now board articulated public transport vehicles in the correct location.

The actuated control plan now receives Legion Pedestrian crossing requests when the pedestrians come to a pedestrian crossing.

Pedestrians are now drawn in the 3D Views even if the name of a pedestrian type is not in ASCII format. Aimsun now also supports Unicode strings.

Importers/Exporters:

When exporting an Aimsun model to EMME the Network node number is now correctly exported.

The Paramics Import operation now converts the OD Matrices correctly.

Shapefiles Importer: CSV turning files are now correctly imported and centroid connections are also correctly created.

Microsimulator API:

We have added a new configuration in the Visual Studio AAPI project to build Aimsun APIs in 64 bits.

Scripting:

The following API functions are now error-free and available in Python:

AKIActionAddDetailedSpeedAction
GGetramModule.getCreateSimulator
Crash solutions

Platform:

Aimsun for Mac no longer crashes when loading an external image.

Aimsun no longer crashes when a centroid configuration is removed with Undo and another is created.

Opening the Experiment Editor when a strategy has no policy no longer causes a crash.

Meso:

Running a mesoscopic simulation with a traffic demand that includes Legion pedestrians no longer causes a crash during simulation.

Meso no longer crashes when applying a forced turning traffic management action with a sub-route or when creating incidents.

Macro:

The matrix adjustment in Windows 64 bits now works properly.

Aimsun console:

Aimsun no longer crashes when simulating a network collecting Instant Emission statistics from an Aimsun console.

Importers/exporters/interfaces:

Aimsun no longer crashes when opening a network created with 6.1.1 or previous versions that contained a TRL TRANSYT-Aimsun Link object.

Dynamic simulators
8523: Turning speed calculation problem
We have implemented a continuity equation for the turning speed ensuring a smooth transition between the straight and curved portions of turnings. This addresses a problem with turning speed calculations that occurred in previous versions.
7245: Add SRC initial and dynamic default cost functions to template file
The template file now contains the two default cost functions used by the stochastic route choice module.
7823: Select affected lanes in turning closure action
The traffic management action “Turning Closure” now allows the closure of a subset of origin lanes instead of the whole turning.
8419: Aimsun freezes when attempting to store outputs to SQLite
We have resolved a problem that prevented the storage of outputs of a dynamic simulation in an SQLite database.
8679: Crash when simulating with a simulation step of 0.1 seconds
We have resolved a precision problem that was causing Aimsun to crash when storing path information in a path assignment file.
8839: In a dynamic simulation, the initial k-shortest paths are not correctly calculated
The calculation of the initial k-shortest paths now correctly takes into account the volume-delay function defined in the section.
8807: Problem accessing “streams” tab
We have fixed a problem that occurred when defining the outputs to be gathered for a dynamic simulation that might have prevented the “statistical streams” tab folder from being activated as desired.
9337: Ramp meters not turning red in a dynamic simulation
We have resolved a problem that arose when the master control plan included several zones. In that case the ramp meters always used the control plan for the last zone defined. The ramps meters now use the appropriate control plan, that is, the one corresponding to the last zone whose type is not "Unspecified".

Micro
8843: Crash during microsimulation using DUE
We have fixed an initialisation problem that made Aimsun crash whenever a microscopic simulation with DUE was run.
8126: Problem in a yellow box that has a turning with one stop line and buffer
During microsimulation, when there was a turning with a stop line defined in a yellow box node, in some cases vehicles ignored the buffer and used the whole turning (as if it were not a yellow box). This problem is now resolved.
8155: Vehicles not entering intersection even though the conflict area is clear
Vehicles giving way at an intersection now take the destination lane of priority vehicles into account when deciding whether or not to enter the intersection.
8799: PT vehicles entering the network are not selecting the correct entrance lanes
Public transport vehicles now select the correct entrance lane as we have modified them to take into account their next turning or bus stop located inside the entrance section (when the entrance is inside zone 2 or 3).
9245: In a microsimulation some vehicles stop in certain sections for no apparent reason
A miscalculation caused some vehicles to stop in some parts of some sections when there was no congestion or any vehicle ahead. This issue arose mainly when a 2-segment curved section had a reserved lane with the first and last segment defined as not reserved (which resulted in the lane not being reserved at all) but has now been solved.
9264: Vehicles colliding in a microsimulation using Aimsun 6.1.1
We have modified the Gap Acceptance model in the microscopic simulator to avoid possible vehicle collisions; these were caused by recent changes that made it possible for a vehicle to change lanes too close to the beginning of the section ignoring any upstream vehicles located in the upstream node.
9064, 8619: In a microsimulation, a vehicle appears momentarily at the edge of a crossing
We have solved the graphical issue that caused some vehicles to appear very briefly in a different position from their actual location.
9037: Problem with turning closure actions for a specific vehicle class
In a microsimulation that used turning closure actions for a specific vehicle class, there was a problem that caused all the vehicle classes to consider the turning closed. We have resolved this issue and now only the specified vehicle class is prohibited from using the specified closed turning movement.
8998: Crash during microsimulation when using a traffic management action that closes a subset of lanes
The car-following model failed to deal with the scenario whereby all connections of a lane were closed by a traffic management action. This has now been addressed and the previously occurring crash resolved.
9253: Some vehicles still use a closed turning in a microsimulation
We have improved the treatment of vehicles that lose their pre-assigned turning, allowing them to choose from among those available, avoiding turning movements that have in the meantime been closed due to a traffic management action.
8157: Colour of ramp meters not updated in a microscopic simulation
In microscopic simulations working in English units, the ramp meterings are now coloured as expected.
8317: Section CO and NOx column missing
The calculated values for user-defined pollutants are no longer only stored in the last pollutant defined in Vehicle Type Pollutants Tab.
8875: Instant emission sensitivity of Aimsun model
We have changed the random generator used in the instant emission model during a microscopic simulation, so that we obtain the same results independently of gathering instant emission outputs or not.
8599: Instant emission statistics for public transport are not calculated
The instant emission model is now initialising the data for public transport vehicles correctly.
8902: IEM Outputs for an average are not correctly stored in a database
After gathering instantaneous emission outputs during a microscopic simulation, the vehicle types stored in the database are no longer incorrectly numbered 0, 10, 20 but rather 0, 1, 2, as they should be.
8085: ALINEA implementation updated in the light of more recent papers
The ALINEA ramp metering algorithm has been updated according to [Papageorgiou, 2008]. The new implementation uses the previously calculated ramp flow as the base flow for the next calculation instead of the measured ramp flow.
5408: Level of Service output must follow the Highway Capacity Manual
The Level of Service of a node was previously calculated considering only the delays of the turnings. Now it is calculated by additionally taking into account the delays of the incoming sections.
8398: Level of Service incorrectly displayed
The Level of Service is now always correctly displayed when before it was only displayed properly when the traffic demand was for more than one vehicle type.
8406: Aimsun-SSAM .trj does not contain all the information
The missing trajectory data has now been added to the trajectory file produced by the Aimsun-Surrogate Safety Assessment Model plug-in, which was previously created with just the headers.
8219: Empty video files
The microsimulator no longer produces empty videos as we have fixed a video recording bug introduced in 6.1.1.

Meso
7998: Cutting a section in two dramatically affects the results of the meso model run
Both the Lane Selection model and the Look Ahead model have been improved in order to deal with freeway configurations. In these configurations both models now try to anticipate future movements to ensure that the maximum throughput of a section remains realistic.
8781: Problem using a control plan with a mesoscopic simulation.
All junctions now employ the correct control plan when simulating a mesoscopic experiment where the master control plan has more than one zone.
8760: Running the same mesoscopic replication twice generates different outputs
The outputs for a mesoscopic simulation that includes traffic management actions are now consistent for every run of the same replication.
8146: In a mesoscopic simulation non-reserved vehicles are allowed to enter reserved lanes when they should not.
The Look Ahead model now takes the reserved lanes into account and therefore restricts the possible entry lanes appropriately.
6809: In a mesoscopic simulation no vehicles are generated if arrivals are ASAP
ASAP arrivals now function correctly and can be used in mesoscopic simulations as expected.
9034: Mesoscopic model - public transport vehicles are not generated
Public transport vehicles are now generated as expected when the timetable associated with the line is by intervals and the initial time of the timetable is earlier than the simulation start time.
9214: Crash when running Stochastic Route Choice with dynamic en route option
Running a mesoscopic simulation with the stochastic route choice DTA model using the “Change Destination” action together with the "Dynamic" option from the Route Choice parameters no longer causes a crash during the simulation.
8707: Meso crash at the end of the simulation
Mesoscopic simulations no longer crash at the end of the simulation when the “Store Path Statistics” option is active.
8685: Problem using traffic management actions with the mesoscopic simulator.
Trigger-activated traffic management actions now function correctly.
8264: Meso crashes with “Lane Closure” action
The “Lane Closure” action no longer causes the mesoscopic simulator to crash when all lanes in the section are selected to be closed.
8174: Mesoscopic simulations produce low lateral lane density
We have modified the computation of density statistics for lateral lanes to consider the real lateral lane length.
8878: Meso reaction time factor default value is incorrect for old networks
When loading an Aimsun network created with Aimsun 6, the reaction time factor defined in the sections for the mesoscopic model now takes the value defined in the section’s road type as the default value instead of erroneously setting the default value to 0.

Macro
8273: Traversal generation for a sub-sub-network is not available
We have added the possibility of generating a traversal O/D matrix for a sub-network contained within a larger sub-network.
8055: Furness execution problems
We have fixed two problems that prevented Furness from executing properly.
The first one occurred when displaying the O/D Matrix using the centroid names or external IDs instead of their Aimsun IDs. This meant that the edited totals could not be applied to the appropriate row or column.
The second problem occurred only if the user modified the O/D Matrix values just before executing Furness. In that case, because of an update problem, the computation used the original values of the number of trips, and not the modified values.
9071: Multiclass adjustment script provided in the template does not work
We have updated the multiclass adjustment script provided in the template to make it compliant with some recent changes made in Python classes.

Legion for Aimsun
7552: Legion outputs for pedestrian crossings
Checking the “Pedestrian Crossings” option in the scenario editor, Legion for Aimsun will calculate the following statistics for each pedestrian crossing:
1. Number of pedestrians that have crossed
2. Crossing Time: mean time that pedestrians positioned on both the crossing and in the waiting zone on either side of the crossing influence vehicles' progress.
3. Effective Crossing time: mean time that pedestrians take to cross the pedestrian crossing itself
4. Waiting Time: mean time that pedestrians wait before crossing
8110: Generate Legion for Aimsun log file
Legion Simulator extension allows the user to store output messages coming from the Legion simulator into a log file.
8894: Crash after calculating average
An incorrect memory reading has been rectified so that it no longer causes system crashes when calculating an average which includes pedestrian outputs.
8112: Incorrect shape of some generated obstacles
A precision problem when generating pedestrian obstacles from sections far away from the origin has been addressed.
8077: Incorrect percentage checking
There is no longer a problem with checking percentages in the Legion for Aimsun matrix editor.

Importers/Exporters
8198: Capacity can be defined per lane for GIS importer
An enhancement to the GIS importer allows the definition of the capacity from a GIS file to be per lane or per section.
8332: Value zero for lane width in GIS defaults to 3.3527 feet
When importing sections from a GIS file with a lane-width value of zero, the GIS importer assigned a width of 3.3527 feet to these sections instead of assigning the correct width for that section's road type. This has now been corrected.
8660: GIS node value not copying to name on import
The assigned attribute for the GIS node name is now copying correctly.
8202: The GIS importer sometimes fails to distinguish between nodes and centroids
When a GIS file contains both centroids and nodes, the importer was sometimes creating centroids instead of nodes. Now it correctly distinguishes between nodes and centroids.
8991: Centroids and connectors are not properly created when importing a CUBE network
Centroids and connectors were being incorrectly created and/or positioned when importing a CUBE network.
8612: Aimsun VS-PLUS interface issue
Aimsun no longer crashes after running a simulation using VS-Plus controllers.
8270: Emme Import: read up1, up2, up3 and assign turning penalty functions
When importing an Emme network, up1, up2 and up3 are read into a turning's User Defined Cost, Second User Defined Cost and Third User Defined Cost, respectively. Also, the turning penalty function fp is assigned to the turning.
8176: Emme exporter: export Aimsun section ID
When exporting networks to Emme, the Emme link extra attribute @nsect will contain Aimsun's section ID.
7893: Aimsun crashes during attempts to import a Paramics network with link files
The Paramics importer was not finding the link files. It now searches for link files whose extension might be ".1", ".2", etc.

Programming
8757: API function alerts user when a route choice cycle is about to begin
The Aimsun Microsimulator API has a new high-level function (AAPIPreRouteChoiceCalculation) that allows the user to carry out any desired checks and modifications before a new route choice cycle begins.
8765: New function added to the Aimsun Microsimulator API for checking the last simulation instruction
The newly added function ANGSetSimulationOrder now allows users to check the last simulation instruction sent to the simulation using the API.
8756: Microsimulator API functions to obtain and modify the values of the section attributes affecting route choice calculation
New functions that read and modify the section parameters used in route choice calculation have been added. These functions are:
• int AKISetSectionCapacity(int idsection, double capacity);
• double AKIGetSectionCapacity(int idsection);
• int AKISetSectionUserDefinedCost(int idsection, double userdefinedcost);
• double AKIGetSectionUserDefinedCost(int idsection);
• int AKISetSectionUserDefinedCost2;
• double AKIGetSectionUserDefinedCost2;
• int AKISetSectionUserDefinedCost3;
• double AKIGetSectionUserDefinedCost3;
8718: Aimsun Microsimulator API: New functions added for accessing actuated control parameters
New functions for reading and modifying the actuation parameters of a control plan have been added. These functions are:
• int ECIGetActuatedParamsPassageTime
• int ECISetActuatedParamsPassageTime
• int ECIGetActuatedParamsMinimumGreen
• int ECISetActuatedParamsMinimumGreen
• double ECIGetActuatedParamsMaxGreen
• int ECISetActuatedParamsMaxGreen
6981: New API function to specify the amount of time in a yellow phase that the vehicles behave as if the light were green
We have added the function ECIChangeSignalGroupStateToYellow to the microscopic simulator API to specify the amount of time that vehicles will behave as if the traffic light were green when it changes to yellow.

8863: Aimsun API: Incorrect documentation of the function for reading the turning information assigned to a signal group
We have updated the microsimulator API manual to prevent a possible misunderstanding of the parameter limits when using the function: ECIGetFromToofTurningofSignalGroup.
8808, 8768: Error in AKIActionAddNextSubPathResultAction and AKIActionAddNextSubPathODAction
Calling up the AKIActionAddNextSubPathResultAction or AKIActionAddNextSubPathODAction functions within an Aimsun API no longer causes a crash.
7590: Malfunction with the ECIChangeDirectPhaseWithInterphaseTransition
When the function ECIChangeDirectPhaseWithInterphaseTransition was used in an actuated control plan it did not behave as expected. This has now been addressed.

GUI
9000: Shape 3D Object Editor doesn't show any attributes
Shape 3D object editor now shows additional attributes.
8128: The spots on view modes are always drawn in black
When applying a view mode that defined coloured spots, sometimes the spots could not be drawn in the defined colour and always came out in black. This could happen, for example, when visualizing the GEH statistic. It is now fixed.
7610: U-turns
U-turns no longer cause an incorrect interpretation of the direction of the turning when drawing the sign on the road.
7385: Curved turning coordinates are not maintained properly when moving their origin and destination sections
After translating a group of sections and their origin and destination nodes, they are now accompanied by their corresponding turnings.
6907: Problems drawing detectors placed on curves
Detectors placed on a curve are no longer causing drawing issues.
8421: Matrix Demand Summary is not working when a variable factor is used
When a variable factor is used in the Matrix Demand, the Matrix Demand Summary will consider it to be 100% by default.
8343: Real Data Sets for turnings are not read where section identifiers are not unique
When using the origin and destination sections' name or external ID for identifying turnings, the real data is now properly imported even if more than one section shares the same name or external ID.
7408: Functions should admit variables
It is now possible to employ user-defined variables in cost functions. The value of these variables must be set at the experiment or scenario that uses such functions.
Note that it is common to use a $ symbol as the prefix of a variable's name. This symbol cannot be used in a function expression. Please add the variable to the scenario of the experiment with the $ symbol ($Cost, for example) but not the expression (Cost).
When using variables, Aimsun reports warnings for undefined variables even if they are correctly defined in the scenario or experiment. This is due to executing some syntax checks without the related scenario or experiment when the network is loaded.
If a variable is not defined at the time of use (when carrying out a simulation for example), Aimsun will print an error in the Log Window.
8615: Arithmetic operators FLOOR and ROUND added
The Functions operators list has been extended with operator FLOOR (returning the nearest lower integer to a) and ROUND (returning the closest integer to a).
8242: Missing connection after turnings definition modification
We have addressed some connection problems that were occurring when modifying the turnings definition, which were making Aimsun crash during simulation.
8142: Graphical Timetable cannot show PT lines with loops
When selecting two or more PT lines in the graphical timetable, Aimsun no longer hangs if any of the selected PT lines have loops in their route.
9194: It is not possible to select a centroid label
Dynamic labels associated with centroids can now be selected or moved away from the centroid centre.
9195: The default values of a dynamic label are incorrect
When defining a new dynamic label, the editor now accepts the default size value and there is no longer an error message.
9242: The roundabout tool creates a node that is not drawn in the open Views
When there is no active layer and a roundabout is created using the roundabout tool, the node created is now drawn in the 2D Views.

9280: Extend the maximum vehicle length allowed for a vehicle type
The maximum length allowed for a vehicle type has been changed from 1000 to 10000 metres.
8487: The check-and-fix-network shows an incorrect Attractiveness rating
There was a problem in the check-and-fix-network informing of a problem in the Attractiveness of a section when the section had the same node as origin and destination.
7757: Add check-and-fix tool for detection of overlapping bus stops
The check-and-fix tool now verifies that there are no overlapping public transport stops.
9056: Dongles using a FLEXlm licence for a network in Windows 7 lose the licence
With a network licence, when the server computer was running Windows 7, the licence was sometimes lost when the computer was in sleep mode. This issue has been resolved by updating the Imgrd tool to a newer version.

Aimsun: 6.1.1 Release notes

Dynamic simulators

7447: Aimsun crashes using paths from a macro assignment

When attempting to run a simulation that used paths produced by a macro assignment, there was a crash if the model contained centroids with a user-defined distribution of vehicles to entrance sections. Now the problem has been addressed.

7476: Cannot load path assignment files with extensión *.apa

In Aimsun 6.1, we changed the path assignment file extension from *.asp to *.apa. The change introduced an error that prevented Aimsun from being able to load an *.apa file as a starting point of a simulation. This has now been fixed: both *.asp and *.apa files can be loaded successfully.

7905: Aimsun crashes when storing simulation statistics in the database if the "Keep in Memory" option is off.

This crash has been fixed. It is now posible to save outputs from a simulation to a database without the need to keep them in memory.

7861, 7992: Problems with turning connections when converting from version 6.0 to version 6.1

In Aimsun 6.1, when loading a network saved using a previous version, Aimsun recalculated the turning connections ignoring possible changes the user might have made. This issue has been addressed: now only new connections are created automatically.

We also fixed a problem whereby stored turning connections from older networks were being modified during the conversion process. This happened when there were reserved lanes involved in the turning movement.

Microscopic simulator

7387: Queue length statistics not shown for unused sections

Previous versions did not display any queue length data in the time series editor if a section had not been used at all. This has now been addressed: unused sections show queue lengths of 0.

7389: Global value of statistics not computed when pollutant statistics are gathered

Running a micro-simulation with the instantaneous emissions model selected, would sometimes disable the computation of the global value for all simulation outputs. This issue has been addressed.

7607: Aimsun crashes when starting a microsimulation with the instantaneous emissions model activated

This crash was caused by an initialisation problem that has now been fixed.

7316: Instantaneous pollutant emissions by vehicle

We have added the ability to check the instantaneous pollutant emissions of a single vehicle during a micro-simulation. The corresponding data can be accessed through the vehicle editor. Currently this feature is only available for the recently implemented instantaneous pollutant emission model by Panis et al [2006].

7771: In a microscopic simulation, objects in hidden layers are suddenly being shown

Due to a bug, simulated vehicles changed the status of previously hidden layers to ¨visible” as they travelled in sections or nodes that belonged to those layers. This is no longer the case.

7452: Cannot collect statistics for all O/D pairs

In previous versions, to avoid potentially excessive memory consumption, it was not possible to collect statistics for all O/D Pairs by setting Origin=”All” and Destination =”All”. We have now enabled this option. We caution users to consider the size of the model and available memory before selecting “All/All”.

7794: Global count of a detector time series is an average value

The global count of a detector time series is now the sum total of the vehicles counted by that detector throughout a simulation.

6781: Table DETEQUIPVEH missing in Aimsun 6.1

We have added back to the database the table DETEQUIPVEH. It contains the following information for equipped vehicles: replication id, detector id, time detection, vehicle id, vehicle type, public line id, speed and headway.

8062: Microscopic simulation crashes when activating a traffic management strategy in a sub-network

Applying forced turning actions in a sub-network when the demand for the microscopic simulation was defined using traffic states could make Aimsun crash when the action affected all vehicles in a section. This issue has been addressed.

7993: In yellow box intersections without a warning sign, turning stop lines are ignored

In a microscopic simulation, the buffer areas that can be defined in a turning movement, were only being considered by vehicles if the turning had a giveway or a stop sign. Now, they are also considered when the intersection is a yellow box and the turning movement has priority

Mesoscopic simulator

7450: Add vehicle trajectory data for a mesoscopic simulation

In mesoscopic simulations, we have added the ability to save vehicle trajectory statistics to the database. The data is saved in two tables:

Summary table: vehicle id, entrance time, exit time, total travel time, total delay time.

Details table: section id, section index in vehicle's path, entrance section time, exit section time, section's travel time, section's delay time.

7860: Problem in mesoscopic simulations with bus bays on on-ramps

In previous versions, bus bays located on on/off-ramps were treated like normal bus stops. Now the problem has been addressed.

7378, 7699: Crash when trying to run mesoscopic simulation with public transport

Running a mesoscopic simulation that included public transport whereby two bus stops were located in the same place or overlapped would result in a crash. This has now been fixed.

7391: Public transport statistics are not gathered in a meso simulation

Because of an error, when the scheduled start time of a public transport line occurred earlier than the simulation start time, the operation of that particular line was not taken into account in the simulation. This is no longer the case.

7392: Some public transport not simulated mesoscopically within a sub-network

Public transport lines with routes going outside a sub-network produced an error and were not simulated in the mesoscopic simulation. Now the problem has been addressed.

7797: Vehicles failing to observe reserved lanes in entrance sections during a mesoscopic simulation

In a mesoscopic simulation, vehicles entering the network through a section that contained a reserved lane would erroneously use the reserved lane. This is no longer the case.

7243: “Close turning” action causes a crash during a mesoscopic simulation

Under some cirmcumstances, a ”close turning” action would give rise to a crash when running a mesoscopic simulation. The crash has been fixed in this version.

7400: Meso DUE results are not viewable when the “past costs” option is activated

Activating the “past costs” option during a mesoscopic simulation using traffic assignement by Dynamic User Equilibrium had the effect that no results were viewable. This has now been addressed: the option is ignored under meso-DUE and the rest of the results are computed and displayed correctly.

7795: Detector outputs by lane in mesoscopic simulations

Older versions of Aimsun produced detector outputs by section. It is now possible to collect mesoscopic simulation outputs by lane.

8087: Define Look-ahead as a distance in the mesoscopic simulator

The Look-ahead model in the mesoscopic simulator now takes into account a maximum Look-ahead distance and a local Look-ahead distance. The maximum Look-ahead distance can be set in the experiment editor and the local Look-ahead distance in the section editor. More details with the Look-ahead model can be found in the "Microsimulator and Mesosimulator Aimsun 6.1 User’s Manual"

Macroscopic tools

3139: Add macroscopic outputs as time series

Macroscopic outputs for sections and turnings are now available in the time series tab of the corresponding object editors.

6975: Traversal generation with "Do Not Assign Percentages" option ticked actually assigns percentages

During a traversal calculation the option "Do not assign percentages" had no effect. Percentages are no longer assigned when this option is selected.

7793: Erroneous connector percentages when calculating traversal matrix for exising subarea

When calculating a traversal matrix for a subarea with an already existing centroid configuration, the resulting connector percentages were computed incorrectly. This has now been addressed.

7953: Static traffic assignment may crash at the end

The crash would occur if the user selected the option of not storing statistics and at the same time specified that assignment convergence data should be stored. It has not been fixed.

8064: Assignment data for multiple vehicle types not displayed correctly in macro validation

When validating a static traffic assignment that involved several vehicle types and real data was available for each one of the vehicle types, the assignment output for a particular vehicle type was not validated against the real data corresponding to it. This now works as expected.

Legion for Aimsun

7551: Legion outputs for entrances and exits

There are new Legion outputs for each selected Origin-Destination pair, namely: number of pedestrians, speed, travel time, walking time, mean stop time, max stop time and number of stops.

7490: Legion for Aimsun output: store .res file

The Legion for Aimsun plugin is able to generate Legion results file (.res) which can be loaded in the Legion Analyser.

Note that this option is only available in the Lite and Extra editions of the Legion for Aimsun plugin.

7449: Show current PT vehicle load and max capacity

When the Legion for Aimsun plugin is active, the Public Transport vehicle editor shows the vehicle’s current number of passengers and maximum capacity.

7866: It is not possible to delete pedestrian types

In Aimsun 6.1.0, deleting pedestrian types resulted in a crash. The problem has been fixed in this version.

7404: Crash while pedestrian obstacles are being generated

Legion for Aimsun could crash while trying to build an obstacle from a centroid. This has now been addressed.

7424: Pedestrians fail to observe red lights in simulations with multiple control plans

When a simulation included multiple traffic control plans, Legion for Aimsun errorneously disregarded some of those plans with the result that some pedestrians ignored red lights. This has now been addressed.

7436: Problem when attempting to access an obsolete .xml file of Legion pedestrian positions

Aimsun now issues a warning whenever a user attempts to run a simulation using Legion pedestrian positions saved to an .xml file which has been subsequently moved or deleted. In previous versions, this was not the case resulting in an apparent inability to display pedestrian trajectories read from a file.

7988: Set initial pedestrians load on pt vehicles

At the first stop inside a pedestrian area, Public Transport vehicles will drop the minimum number of people between the maximum vehicle capacity and the defined number of people to alight the public transport line.

7989: Alight/Board pedestrians depending on stop curb side

The side where Legion Pedestrians alight or board public transport vehicles is calculated as follows: 
if the section has only one lane, then the rule of the road will be taken into account, otherwise, it will depend on the public transport stop side.

7742: Pedestrian Area doesn't generate any obstacle from sections that cross the whole area

The object Pedestrian Area wasn't able to create obstacles from sections that crossed the whole area if the automatic obstacle generation option was used. This issue has now been addressed.

7906: Pedestrians don't alight public transport vehicles on certain conditions

Pedestrian obstacles built from sections with public transport stops must fit the section shape. Otherwise, pedestrians won't alight the PT vehicle as they cannot find a way to to reach their destination.

Misc / UI

7120: Bus pre-emption editing improvement

We have added the option of selecting multiple public transport lines and adding them in one operation to a bus preemption control plan.

7354: Pan to the object clicked in a trigger window

We have improved the Trigger editor. When a section or detector is selected in the editor, the 2D view automatically pans to the selected object.

7826: Space Time Diagram: change the colour scale from green-red to red-green depending on the attribute

The colour progression in space-time diagrams changes automatically to red-green when the selected time series is speed. Previously, all time series had a green-red colour progression.

7812: Add the posibility to control the limits and the colour of Space Time Diagrams

In the Settings tabs, for each type of measure (Count, Density, Headway, Occupancy and Speed) we have added the possibility to customise the value ranges that correspond to each colour.

7408 User-defined variables in cost functions

We have added the ability to include user-defined variables in cost functions. The value of these variables must be set within the experiment or scenario that uses the cost functions.

When using the $ symbol as a prefix in the name of a variable ($Cost for example), that the full name can be used to associate the variable with a scenario or experiment. However, when when defining the cost function, please use the name without the leading “$”(Cost).

Finally, when including user-defined variables in cost functions, Aimsun may issue a warnings about undefined variables even if the variables are actually correctly defined in the scenario or experiment. This is because some syntax checks are carried out without knowledge of that. If a variable is not defined at use time (when running a simulation, for example), Aimsun will print an error in the Log Window.

7894: Aimsun crashes when deleting a centroid connection

Under certain circumstances, using the centroid editor to delete a centroid connection would result in a crash. This issue has now been addressed.

7756: It is difficult to view the text specified in a View Style when there are colours and bandwidths involved

The texts defined in a View Style are now always drawn in black to improve their visibility when shown in 2D.

7702: 'New Network' option, from File Menu, creates an Aimsun network without using a template

The 'New Network' option, from File menu, now uses the first available template to create a new network.

7924: Crash when editing the 3D shapes of a vehicle

This occurred when a vehicle had a 3D shape assigned whose corresponding 3ds file had been deleted: Aimsun would crash when trying to delete the assignment of the 3D shape. This problem has been fixed.

7330: Warnings added for null traffic demand factors and null compliance levels associated with traffic managament actions

In previous versions null values in traffic demand factors or traffic management action compliance levels were interpreted as zeros leading to ambiguity. Aimsun now issues warnings if those variables are null/undefined.

7332: Section length not available in Table View window

The length attribute for sections, turnings and polylines can now be displayed in the Table View.

7394: Turnings Attributes are not displayed

Fixed an issue that prevented additional turning attributes to be displayed in the Node editor.

7445: Error loading textures from stored .3ds files

We have resolved some problems that caused textures from .3ds objects not to load properly.

7426: Buildings (extruded polygons) created using a shapefile are not saved

Previous versions of Aimsun incorrectly identified polygons imported from shapefiles and then extruded as temporary objects. This has now been addressed

7419: Lane closure applied to All lanes is not saved correctly when the section contains lateral lanes

When a lane closure action was defined as applying to all lanes in a section and the section had a lateral lane, it could happen that when reopening the Aimsun network, the definition of the lane closure changed from all lanes to a single lane. This problem has been addressed.

7808: The Time Series dialog doesn't keep the lane number setting

When displaying the outputs related to a section's lane in the time series tab of the section's editor, the lane displayed was not kept properly and outputs for subsequent sections did not display the appropriate lane.

7834: Minimum Gap value set in Gap Reduction dialog is not saved

When editing an actuated control with gap reduction, the minimum gap value entered was not saved, now this problem has been addressed.

7417: Check and Fix Network add check for PCUs=0

If a network contains vehicles with 0 PCUs then a warning is displayed when they are not used in any matrix demand and an error when they are.

7434: In the sections, the 'distance zone 1' parameter should be always higher than the 'distance zone 2' one

While editing a section, if the distance zone 1 parameter is lower that the distance zone 2, a new message appears informing the user about it to redefine them.

7859: Check and fix network is not able to find some errors.

Check and Fix tool is able to detect wrong turning definitions when they have conflicts on section destination lanes.

7841: Check and Fix Network Raises Error for Section with not turning at entrance where warning might be more appropriate

When checking an Aimsun network using the check and fix tool, the messages about a section without any intersection at the entrance have changed to be a warning which is more appropriate than an error.

7177: Check and fix network only lists the first unconnected O/D Pair when checking the demand

All the unreachable O/D pairs for the specified traffic demand, when using the check and fix network tool, are now listed instead of just listing the first one as before.

7954: Check and Fix Network was giving warnings that should not have been listed

Where no demand was specified in the Check and Fix Network tool, warnings about floating sections were being generated even for sections that were actually connected to centroids. Now, when no demand is chosen, all centroid configurations are considered and sections connected to a centroid are not listed as a floating section warning.

8061: Check and Fix Network should detect wrong values for section's meso parameter

The Check and Fix Network tool now detects values of jam density and reaction time factor that are outside the corresponding permissible range and replaced them with the appropriate default values.

7515: Analyser Dynamic Label problems

Dynamic Analyser Labels didn't consider the font size to draw the label. It has now been addressed.

7747: Node polygons drawn incorrectly

We have improved the rendering of node polygons to account for some special cases whereby the node surface did not correctly represent the connectivity between lanes. Specifically, under some additional conditions, if one lane from the origin section was connecting to all lanes in the destination section, then the node surface could misleadingly suggest that the origin lane was only connected to the middle lane of the target section. This is no longer the case.

7971: Undoing "Change road type" command makes program crash

We fixed an application crash which occurred when undoing the "Change road type" operation.

Programming tools

7574: Microsimulator API for Linux and Mac versions

This version of Aimsun introduces full support for Microsimulator API programming, both in C++ and Python, in Mac and Linux.

7888: Changes done to the Scenario Date in the Scenario Editor are not considered

The scenario editor was changing the scenario's date only if a real data set was selected in order to match the date from the real data set. Manual changes made to the scenario date were ignored.

7786: Allow a simple section cut operation via scripting

We have added a new Python script method that allows you to cut a section. Here's some sample code:

cutCmd = section.getCutCmd( point, point2, True )
cutCmd.doit()

7474: Optimal detector location functions now available through scripting

We have added functions related to the optimal detector location module to the Aimsun scripting libraries.

GIS

7950: Add functional class support to sections

Functional Class: the classification of the road according to the character of service they are intended to provide.

Aimsun will use this information to hide low functional class sections when the zoom level is very high, revealing more details as the user zooms in. 



There are several possible classifications

The Federal Highway Administration defines three: 1 for Arterial, 2 for Collector and 3 for Local roads.


Navteq defines five: 1 for high volume and maximum speed roads to 5 for low volume roads.

7473: Support Navteq functional class attribute

Now is possible to assign the functional class as found in Navteq links to the corresponding Road Type.

If the Road Type has no funcional class information or if its information is different from the one specified by Navteq, it will be updated according.

7565: Save GIS network importer settings for later re-use

After importing a GIS file as a network, Aimsun will generate an xml file with the settings used by the user to do the translation. This file has the same name as the shp input file with the .xml extension added.

If the user imports again the same .shp file, Aimsun will fill the importer dialogue with the previous settings.

7835: Missing turns after importing certain GIS files

In previous versions of Aimsun, the GIS importer failed to create turns when the lanes involved were more than 10m apart. Now all turns are created as expected.

7475: GIS network importer doesnt't import the correct number of lanes for inverted links in single direction

In previous versions the LANES_BA attribute was only used for bidirectional links. Now it is also used for single direction links when those are inverted.

7472: GIS import: sections from single inversed direction links not added to node

From-node and to-node information, required to create the network topology, where not inverted for single links in inverted direction, only for dual links. Now we interchange from and to node information for single links too.

Importers/Exporters

7874: Emme import: centroids with 6-character IDs were not correctly imported

When reading the nodes&links file, previous versions of Aimsun did not handle correctly centroids whose ID contained more than 5 characters, for example 123456. This has now been addressed.

8042: Aimsun-Emme interface does not translate AND operator importing vdfs into Aimsun

Emme Import: When importing VDFs, the logical AND operator (&&) was not correctly translated into Aimsun (&). This problem has now been fixed.

7511: Problem with bus stops in S-Paramics Importer

The S-Paramics importer was not reading properly the "busstops" file. Now, it has been addressed.

7568: Paramics importer creates banned turns

The Paramics importer was creating banned turns at signalised intersections. Now, it creates turns that are allowed in any phase of the control plan.
The bug has been addressed.

7714: Import Paramics vehicle types

Paramics Importer creates Aimsun vehicle types setting car default values except the following parameters:
length, width, maximum speed, maximum aceleration and maximum deceleration

8025: Paramics Importer doesn't load some matrices

Non-square matrices defined in "matrix" file were not imported. This issue has now been addressed.

8026: Paramics Importer: control plan offset not set properly

In certain conditions, the offset was not initialised properly. As a result, the imported control plan was populated with incorrect values.This problem has now been resolved.

7716: Paramics importer: Turn Lanes are not imported properly

The Paramics importer was not calculating turning origin and destination lanes when translating turning geometry. This issue has now been addressed.

7718: Paramics Importer: Sias doesn't have stop priority

Paramics Importer was setting Stop priority to all MINOR turnings. This is wrong as Paramics doesn't have Stop priorities. It has now been addressed

7713: S-Paramics importer doesn't load demand profiles

S-Paramics importer now supports the corresponding demand file format.

7715: Paramics Importer loads banned turnings

Paramics importer was adding banned turnings to control plans. It has now been addressed.

7717: Paramics importer: signal timing is ignoring amber times

Paramics importer now adds "signals green to red time" - "signal movement stop delay" seconds to normal phases and it adds "signal movement stop delay" seconds to interphases.

7440: CONTRAM Importer: import results

We have improved the CONTRAM importer: it is now able to load Contram simulation results by creating associated real data sets. This feature makes it possible to compare CONTRAM and Aimsun results.

We have also added the abilty for O/D Routes to be assigned to O/D Matrices according to the percentage use produced by CONTRAM.

7752: UTOPIA status messages in log file

The UTOPIA output file now also contains log entries when the spot status changes either to CENTRALIZED or LOCAL.