Re: [sumo-user] Bug in TraCI distance retrieval

[Jakob Erdmann <namdre.sumo@xxxxxxxxxxxxxx>]

If you send me the network and the route file of the problematic vehicle (either as a zip file or as a download line if it's too large) I will take a look.

regards,

Jakob

2017-11-22 17:31 GMT+01:00 Zhizhou Chen <Zhizhouchen@xxxxxxxxxxx>:

Hello Jakob,

I only use the TraCI movetoXY for ego-vehicle, which is related to reroute. And the routelist before and after the distance-jump is the same (with 118 edges) and the route index changes from 22 to 23.

Regards,

Zhizhou 

---

Von: Jakob Erdmann <namdre.sumo@xxxxxxxxxxxxxx>
Gesendet: Mittwoch, 22. November 2017 11:17

An: Zhizhou Chen
Cc: sumo-user@xxxxxxxxxxx
Betreff: Re: [sumo-user] Bug in TraCI distance retrieval

 

Actually, the settings in .sumocfg should not cause periodic rerouting (only routing on insertion).

Are you loading any <rerouter> definitions in your simulation?

Can you please check whether the value of vehicle.getRoute() is different before and after the jump in distance?

2017-11-22 11:50 GMT+01:00 Zhizhou Chen <Zhizhouchen@xxxxxxxxxxx>:

Hallo Jakob,

thanks for your reply. I think it's the same problem. The route of this bus is a "trip" with "from", "to" and "via" edges. The routing configuration in ".sumocfg" is set as below:

But in TraCI the routes besides ego-vehicle are not set. 

Regards,

Zhizhou

---

Von: Jakob Erdmann <namdre.sumo@xxxxxxxxxxxxxx>
Gesendet: Mittwoch, 22. November 2017 09:29
An: Zhizhou Chen
Cc: sumo-user@xxxxxxxxxxx
Betreff: Re: [sumo-user] Bug in TraCI distance retrieval

 

Hello,

it could be related to this known issue: https://github.com/DLR-TS/sumo/issues/2465

traci distance request is incorrect after rerouting (trac #2465) · Issue #2465 · DLR-TS/sumo github.com retrieving the already driven distance (0xa4 0x84) gives incorrect values (starting from the rerouting edge instead of the beginning) Migrated from http://sumo.dlr.de/ticket/2465 { "status": "a...

Does your simulation use rerouting (via TraCI or due to usage of --device.rerouting options)?

regards,

Jakob

2017-11-22 10:09 GMT+01:00 Zhizhou Chen <Zhizhouchen@xxxxxxxxxxx>:

Hallo Jakob,

thanks for your reply. I have just tried the simulation in curent SVN-Version "V0_31_0+1242-77877a78eb" but the Bug still appears nearly at the same time, from 950.4m(last step: 36955.0s) to 496.5m. Thanks for your help!

Regards,

Zhizhou

---

Von: sumo-user-bounces@xxxxxxxxxxx <sumo-user-bounces@xxxxxxxxxxx> im Auftrag von Jakob Erdmann <namdre.sumo@xxxxxxxxxxxxxx>
Gesendet: Dienstag, 21. November 2017 22:08
An: Sumo project User discussions
Betreff: Re: [sumo-user] Bug in TraCI distance retravel

 

Hello,

Try using the latest development version  (http://sumo.dlr.de/wiki/Downloads#SUMO_-_Latest_Development_Version) as it contains bug fixes related to driving distance calculation.

Downloads - Sumo

sumo.dlr.de

Here, you will find SUMO both as sources and as compiled binaries. Please contact us if you have any problems. If you want to report a bug, please open a GitHub issue.

regards,

Jakob

2017-11-21 16:21 GMT+01:00 Zhizhou Chen <Zhizhouchen@xxxxxxxxxxx>:

Hello all,

I use the TraCI plug-in subscription context (in C++ TraCI API) to retrieval the distance, which the vehicle has already driven (ID: 0X84). But in my simulation, the driving distance of the green truck below always suddenly reduces at this simulation step from 950.7m(last step: 36949.5s) to 496.8m. Is this a bug in TraCI or in route-planning? Thanks for your help!

Best wishes,

Zhizhou Chen

_______________________________________________
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