You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Visualize Frustum GUI plugin (#2707) adds frustum visualization for logical camera sensors by subscribing to the logical camera sensor's frustum topic, e.g. /logical_cam_sensor/frustum (gazebosim/gz-sensors#491). One improvement is to extend the plugin to support visualization of other types of camera sensors, starting with a regular RGB camera sensor.
Desired behavior
The GUI plugin allows users to select other camera topics for visualizing frustums
Alternatives considered
Another option for enabling/disabling frustum visualization is to parse the //sensor/visualize sdf tag
Implementation suggestion
In the topic drop down list, we can also support gz.msgs.CameraInfo msg type which is published by many other types of camera sensors. On callback, we should be able to compute camera frustum info (near, far, hfov, etc) from the intrinsic params.
The text was updated successfully, but these errors were encountered:
Visualize Frustum GUI plugin (#2707) adds frustum visualization for logical camera sensors by subscribing to the logical camera sensor's frustum topic, e.g. /logical_cam_sensor/frustum (gazebosim/gz-sensors#491). One improvement is to extend the plugin to support visualization of other types of camera sensors, starting with a regular RGB camera sensor.
Desired behavior
The GUI plugin allows users to select other camera topics for visualizing frustums
Alternatives considered
Another option for enabling/disabling frustum visualization is to parse the //sensor/visualize sdf tag
Implementation suggestion
In the topic drop down list, we can also support gz.msgs.CameraInfo msg type which is published by many other types of camera sensors. On callback, we should be able to compute camera frustum info (near, far, hfov, etc) from the intrinsic params.
The text was updated successfully, but these errors were encountered: