Simulation/Output/Induction Loops Detectors (E1)

Instantiating within the Simulation
An induction loop is defined this way within an additional file like this:

" lane="" pos="" freq="" file="" [friendlyPos="true"] [splitByType="true"]/>

The " id " is any string by which you can name the detector. The attributes " lane " and " pos " describe on which lane and at which position on this lane the detector shall lay. The " freq "-attribute describes the period over which collected values shall be aggregated. The " file " attribute tells the simulation to which file the detector shall write his results into.

The attributes:

Generated Output
A single data line within the output of a simulated induction loop looks as following: " end="" id="" \ nVehContrib="" flow="" occupancy="" \ speed="" length="" nVehEntered=""/> ... further intervals ...

The values are described in the following table.

The detector computes the values by determining the times the vehicle enters and leaves the detector, first. This implicates, that a) some values are not available as long as the vehicle is on the detector, and b) some values can not be computed if the vehicle enters the detector by a lane change - as the vehicle did not pass the detector completely.

" nVehEntered " denotes how many vehicles were on the detector, but the values are collected for vehicles counted in " nVehContrib ".

Splitting by Type
If the output is split by vehicle types, then the values for all seen vehicle types are listed individually within the interval output:      " ...measures as above... />     ... further types ...   ... further intervals ...

Visualisation
Figure: A scenario with induction loops

Figure: A close-up view at an induction loop

Further Notes

 * Simulated induction loops can be accessed using TraCI
 * Please note that in split-mode ( splitByType="true" ) also a type line may be reported, but the values are empty. The reason is the internal implementation of the detectors, you have to take the numbers into account.
 * You can generate detector definitions automatically. See output tools for more information.