Replies: 6 comments
-
Internal tracking ticket: FG-3725 |
Beta Was this translation helpful? Give feedback.
-
Hi @kevswims, can you describe what you mean by "an actual frame of reference parameter"? This frame_id corresponds with the 3D panel's Transforms feature: https://foxglove.dev/docs/studio/panels/3d#transforms Is there something you're trying to accomplish that the current feature set does not support? |
Beta Was this translation helpful? Give feedback.
-
@jtbandes do you have an example somewhere that sets the I'm not quite understanding how the frame of reference is supposed to be stored as a string. |
Beta Was this translation helpful? Give feedback.
-
You can see some example code in nuscenes2mcap which is used to make our sample dataset: The image is positioned in 3D space based on the FrameTransform messages with the corresponding I confirmed that Studio actually doesn't use the image's |
Beta Was this translation helpful? Give feedback.
-
Thanks @jtbandes , that makes much more sense now. Once I try this out I'll see if I can put up a PR that cleans up the documentation comment on the frame_id. |
Beta Was this translation helpful? Give feedback.
-
Closing this out as it seems answered. |
Beta Was this translation helpful? Give feedback.
-
Description
In the RawImage.proto file here https://github.com/foxglove/schemas/blob/f8d19d032541f8241b5e1576dd833fa09545bf40/schemas/proto/foxglove/RawImage.proto#LL14C1-L14C196 there is a comment that indicates a frame of reference but the parameter is just a
string frame_id
. I'm not sure which of these is supposed to be there but we would like to have an actual frame of reference parameter on images.Beta Was this translation helpful? Give feedback.
All reactions