Hello Jakob,
i already implement some Filtering from Client side. But we wanted to increase the performance. For this reason, we wanted
know how much speed we could gain, by using an implementation directly from server side. It’s the main reason, why we wanted to test this new Sumo Filtering functionality.
Can you give me maybe more hint about how I can do from my side this migration? I would try it once against. My first try
wouldn’t successful.
Br
Christian
Von: sumo-user-bounces@xxxxxxxxxxx <sumo-user-bounces@xxxxxxxxxxx>
Im Auftrag von Jakob Erdmann
Gesendet: Mittwoch, 13. Februar 2019 12:06
An: Sumo project User discussions <sumo-user@xxxxxxxxxxx>
Betreff: Re: [sumo-user] Question relativ to context subsciptions
you can always implement your own filltering on the client side (e.g. based on the angle of returned vehicles).
I cannot promise a fixed date by which the python client functionality will have been migrated to the C++ client.
Hello Jakob,
could we be able to use another Filter possibilities in the traci-Cpp source code for today.
Is on this part the tracic++ already extended. Because I faced some difficulties by trying to add these new subscription Filter.
Thank you
Br
Christian
Von:
sumo-user-bounces@xxxxxxxxxxx <sumo-user-bounces@xxxxxxxxxxx>
Im Auftrag von
Jakob Erdmann
Gesendet: Montag, 11. Februar 2019 18:58
An: Sumo project User discussions <sumo-user@xxxxxxxxxxx>
Betreff: Re: [sumo-user] Question relativ to context subsciptions
As I tried to explain in my previous mail, person.getSlope is missing on the server side.
It has just now been added to the server as well as the clients
Hello Jakob,
i think getAngle and getLength are already implemented. I think it was a mistake from my
side.
But for Slope it’s still strange. I extend the code and define the Slope in TraCIAPI.cpp
like this :
double
TraCIAPI::PersonScope::getSlope(const
std::string&
personID)
const
{
return
myParent.getDouble(CMD_GET_PERSON_VARIABLE,
VAR_SLOPE,
personID);
}
For sure in the header file i define it as well.
double
getSlope(const
std::string&
vehicleID)
const;
but I don’t know, what i forgot.
Thank you very much Jakob
Br
Christian
Von:
sumo-user-bounces@xxxxxxxxxxx <sumo-user-bounces@xxxxxxxxxxx>
Im Auftrag von Jakob Erdmann
Gesendet: Montag, 11. Februar 2019 15:37
An: Sumo project User discussions <sumo-user@xxxxxxxxxxx>
Betreff: Re: [sumo-user] Question relativ to context subsciptions
- PersonScope::getPosition3D is implemented (TraCIAPI.cpp, line 2971)
patches are welcome and should be much easier compared to subscription filtering
Hello Jakob,
thank you very much for your quick answer and for your help. I tried it but still facing
some strange behavior.
1-
It seem that these variable VAR_POSITION3D
, VAR_ANGLE ,
VAR_VEHICLECLASS , VAR_LENGTH
are not implemented yet for person in C++, although we can get all these value for person by using Traci function command.
2-
I also get this error bellow, when I use the variable Slope (VAR_SLOPE)
. Please Jakob can you give more hint ?
Thank you very much
Br
Christian
Von:
sumo-user-bounces@xxxxxxxxxxx <sumo-user-bounces@xxxxxxxxxxx>
Im Auftrag von Jakob Erdmann
Gesendet: Montag, 11. Februar 2019 10:59
An: Sumo project User discussions <sumo-user@xxxxxxxxxxx>
Betreff: Re: [sumo-user] Question relativ to context subsciptions
you need to use two subscribtions. one for vehicles and one for persons:
vehicle.subscribeContext(vehID, CMD_GET_VEHICLE_VARIABLE, range, vars, begin, end)
vehicle.subscribeContext(vehID, CMD_GET_PERSON_VARIABLE, range, persoVars, begin, end)
Hello everyone
I have a question relative to the context subscriptions of sumo.
I want to use the context subscription to filter every objects around the ego vehicle. But I’m facing the issue that the class person
is not handle as a vehicle class. The consequence is that by using vehicle.subscribeContext
pedestrian will not be considered. I wanted work around that by using
person.subscribeContext(vehID,
CMD_GET_VEHICLE_VARIABLE,
10000,
vars,
0,
3000);
but here the parameter vehID would be PedestrianID, and then in this case, I would take the person around a define PedestrianID. But want I want is to take pedestrian around a defined VehicleID (Ego Vehicle).
Can you help me on this part, how can I find here a suitable solution. There is a way to have this information by using context subscription ?
Thank you very much for your help.
Best regards
Christian Wabo
_______________________________________________
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
_______________________________________________
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
|
