-
-
Notifications
You must be signed in to change notification settings - Fork 3.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
PythonAPI sensor actor cleanup "no stream available" #1821
Comments
It could be very handy having this callback, I think we can add a list of destroyed actors in the world observer's message, that'd make very easy adding callbacks in the client-side. This would be also very handy for the pedestrian navigation. Meanwhile a workaround could be checking periodically if the actor is still alive if world.get_snapshot().find(actor_id) is None:
# actor was destroyed. |
At the moment there are two tick()-callbacks registered in CARLA ROS bridge:
Therefore the error-message is only seen for max 1s. So ideally, we would have two callbacks:
|
@fpasch Is this still a relevant issue? |
Yes. |
Would it be fine to just keep a list with the deleted actors and offer that information to the client? |
This issue has two aspects:
For 1.), although it would be convenient to have a callback on actor-deletion, there is the workaround to compare the actor lists between ticks (see ros-bridge). So this has a low priority. |
Added to the task board. |
There seems to be an issue within the cleanup of the sensor actors, which results in the following error messages:
This was seen within the CARLA ROS bridge. It seems to happen whenever a sensor, that has a registered callback (
self.carla_actor.listen(self._callback_sensor_data)
) goes away.To my knowledge there is no API available to handle that issue from within Python. (e.g. a callback whenever the actor goes away).
So I believe that we need to handle it within the CARLA PythonAPI code.
The text was updated successfully, but these errors were encountered: