Simulation/Output/Instantaneous Induction Loops Detectors

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

" lane="" pos="" file="" [friendlyPos="x"]/>

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 "file" attribute tells the simulation to which file the detector shall write his results into. The file will be generated, does not have to exist earlier and will be overwritten if existing without any warning. The folder the output file shall be generated in must exist.

The attributes:

Generated Output
An instantaneous induction loop is writing a value to the output as soon as a vehicle was detected. This detector differs between different states:
 * "enter": a vehicle has entered the detector in this simulation step
 * "stay": a vehicle which entered the detector in a prior step is still on the detector
 * "leave": a vehicle has left the detector in this simulation step

The following values are reported in all cases:

If state is "enter", then the following value is generated additionally:

If state is "leave", then the following value is generated additionally:

Visualisation
Figure: A scenario with induction loops

Figure: A close-up view at an induction loop

Further Notes

 * Instantaneous induct loops are not directly supported by TraCI. As Simulated induction loops can be accessed using TraCI allows a per-second value retrieval from plain induction loops, you can nonetheless monitor vehicle entering and leaving times using the "last step vehicle data" variable.