| Re: [sumo-user] E2 detector: nVehSeen is negative? |
Hi Jan,
this is definitely a bug. You are right about the lane change but in an interval of 1s you cannot have 11 lane changes if the detector is short. Can you send the scenario?
Best regards,
Michael____________________________________________________________Hello,
I have a puzzling problem: When simulating a network equipped with E2
detectors, at least one of those detectors gives me negative
"nVehSeen" values:
[...]
<interval maxVehicleNumber="0" meanVehicleNumber="0.00"
startedHalts="0.00" intervalHaltingDurationSum="0.00"
maxIntervalHaltingDuration="0.00" meanIntervalHaltingDuration="0 .00"
haltingDurationSum="0.00" maxHaltingDuration="0.00"
meanHaltingDuration="0.00" jamLengthInMetersSum="0.00"
jamLengthInVehiclesSum="0" maxJamLengthInMeters="0.00"
maxJamLengthInVehicles="0" meanMaxJamLengthInMeters="0.00"
meanMaxJamLengthInVehicles="0.00" maxOccupancy="0.00"
meanOccupancy="0.00" meanTimeLoss="-0.00" meanSpeed="-1.00" nVehSeen="-
11" nVehLeft="1" nVehEntered="0" sampledSeconds="0.00" id="701057"
end="100.00" begin="99.00"/>[...]
and in fact the cumulative nVehEntered value is lower than the nVehLeft
count for the whole simulation (low traffic, only 159 vs. 173 vehicles).
My first explanation was that some vehicles are only partially hitting
the detector due to lane change, but the detector is relatively short so
this phenomenon is rather unlikely.
Is this a bug or an E2 feature?
Jan
_________________
sumo-user mailing list
sumo-user@xxxxxxxxxxx
To change your delivery options, retrieve your password, or
unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/sumo-user
_________________
sumo-user mailing list
sumo-user@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/sumo-user