[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [sumo-user] vehicle scope data after calling moveToXY
|
Hi Jakob, our actual setup is a little hard to send over, but I tried to pack something together quickly that exhibits the behavior. If you call the “moveToXY” command every step (i.e. set the variable MoveEveryXSteps to 1), you will always retrieve (1073741824, 1073741824) as a result from “getLaneChangeState”. However, if you only move every other step (i.e. set the variable MoveEveryXSteps to 2), you will receive alternating values of (1073741824, 1073741824) after moving and a set of plausible values after simulating without moving. We were hoping to be able to move the vehicle (every time step) and still receive meaningful lanechange values (and others such as leader, etc.) All the best
Jakob
Von: sumo-user-bounces@xxxxxxxxxxx <sumo-user-bounces@xxxxxxxxxxx> Im Auftrag von Jakob Erdmann
Gesendet: Freitag, 1. März 2019 17:35
An: Sumo project User discussions <sumo-user@xxxxxxxxxxx>
Betreff: Re: [sumo-user] vehicle scope data after calling moveToXY Since my own test does not show this problem, it would be great if you could prepare a minimal error scenario and send it my way (traci script, net.xml, etc). Thanks for your response, I tried again the recent available snapshot. However when accessing the getLaneChangeState I always get the bitset integer 1073741824 I actually specified a valid route when calling vehicleScope.add(*) by specifying the route_id The route_id seems to be available when asking for traci->vehicle.getRoute(veh_name). Is there anything else we need to account for? Just as a hint: When calling simulationStep twice, i.e. when letting sumo to control the vehicle at least for one step, the lane change state seems to be correct. Best regards, Benedikt Von: sumo-user-bounces@xxxxxxxxxxx [mailto:sumo-user-bounces@xxxxxxxxxxx] Im Auftrag von Jakob Erdmann
Gesendet: Freitag, 1. März 2019 10:04
An: Sumo project User discussions
Betreff: Re: [sumo-user] vehicle scope data after calling moveToXY - the functions getLeader (if the leader is on another edge), getNextTLS and getLaneChangeState require knowledge about upcoming route edges for proper functioning. If you only move the vehicle with moveToXY and never set a route, these functions cannot work because the route then only consists of the current edge Dear SUMO users, I am trying to get vehicle scope data for objects that I move with moveToXY command via the C++ TraCIAPI. The used procedure is as following 1. Determine new xy positioning for vehicle with name name 2. Call moveToXY for traffic object with name name 3. Perform SUMO simulation step 4. Access the following variables from vehicleScope for the moved traffic object a. vehicle_scope.getLaneChangeState(name, 1) and vehicle_scope.getLaneChangeState(name, -1) b. vehicle_scope.getAcceleration(name) c. vehicle_scope.getLeader(name) d. vehicle_scope.getNextTLS(name) However, the values seem to be not valid after calling moveToXY. Is it possible to access these values for moved traffic objects or would it be possible to provide this functionality in the next time? Kind regards, Benedikt Schott _______________________________________________
sumo-user mailing list
sumo-user@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.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://www.eclipse.org/mailman/listinfo/sumo-user
|
Attachment:
TestLaneChangeRetrieval.zip
Description: Zip compressed data
