Closed behrisch closed 3 years ago
Is this still up to date? The detectors would probably want to output the timeloss suffered during the vehicle's stay on the detector? So the proposal is to equip the vehicle with a method to query its rate of time loss?
- TraCI (vehicle, edge, lane)
- edgeData
- E2Detector
- E3Detector
it's probably best to extend SUMOVehicle with a getTimeLoss() function
to:
- TraCI (vehicle, edge, lane)
- edgeData
E2Detector- E3Detector
it's probably best to extend SUMOVehicle with a getTimeLoss() function
@namdre commented:
Replying to [comment:1 leo]:
Is this still up to date? The detectors would probably want to output the timeloss suffered during the vehicle's stay on the detector? So the proposal is to equip the vehicle with a method to query its rate of time loss?
No. The proposal was to implement MSVehicle::getTimeLoss() which has already been done. This is to compare the time loss at the point of entering with the time loss at the time of leaving.
timeLoss retrieval for edge/lane should be handle via #9242
edgelaneit's probably best to extend SUMOVehicle with a getTimeLoss() function
Migrated from http://sumo.dlr.de/ticket/1396