gz-sensors icon indicating copy to clipboard operation
gz-sensors copied to clipboard

Using gz_frame_id emits a warning; should be part of the SDFormat spec

Open azeey opened this issue 2 years ago • 4 comments

Environment

  • OS Version: any
  • Source or binary build? any

Description

  • Expected behavior: No warnings when using gz_frame_id to set a custom frame id for a sensor in gz-sim.
  • Actual behavior: The following error is emitted warning that the element gz_frame_id is not part of the SDFormat spec.
Warning [Utils.cc:130] [/sdf/world[@name="imu_sensor"]/model[@name="imu_model"]/link[@name="link"]/sensor[@name="imu_sensor"]/gz_frame_id:/home/addisu/ws/garden/src/gz-sim/test/worlds/imu.sdf:L75]: XML Element[gz_frame_id], child of element[sensor], not defined in SDF. Copying[gz_frame_id] as children of [sensor].

I think we'd want this tag in SDFormat. I would also say we could just use frame_id instead of gz_frame_id.

Steps to reproduce

  1. Modify gz-sim/test/worlds/imu.sdf to use gz_frame_id
  2. Run the world in gz sim.

azeey avatar Jan 06 '23 18:01 azeey

There's also an optical_frame_id in SDFormat. Probably should consolidate all frame id info into the frame_id tag targeting Harmonic.

azeey avatar Jan 09 '23 19:01 azeey

@ahcorde is this something we can do for Harmonic?

azeey avatar Aug 04 '23 21:08 azeey

Hi all, as of today is there a way to change the frame_id of a sensor? I am using a gpu_lidar but I cannot manage to change the frame_id attached to the message. Thanks

muttistefano avatar Jan 05 '24 11:01 muttistefano

Hi all, as of today is there a way to change the frame_id of a sensor? I am using a gpu_lidar but I cannot manage to change the frame_id attached to the message. Thanks

Yes, you should be able to use gz_frame_id. In Fortress, you can use ign_frame_id (discouraged) or gz_frame_id.

azeey avatar Apr 04 '24 19:04 azeey

Hello everyone, I am facing the same problem. gz_frame_id tag is not changing the frame_id of the lidar_sensor. Rather, the lidar_sensor is publishing messages with frame_id of the format: ROBOT_NAME/base_footprint/NAME_OF_THE_SENSOR. is there any new fix for this?

Also, optical_frame_id is issuing the same warning.

faizurrahman1998 avatar Jun 30 '24 06:06 faizurrahman1998

included frame id fix for lidar sensor in https://github.com/gazebosim/gz-sensors/pull/444. I'll backport to gz-sensors8 (harmonic) and make it compatible with <gz_frame_id> once that PR is merged.

iche033 avatar Jul 03 '24 23:07 iche033

backported fix in #446

iche033 avatar Jul 10 '24 16:07 iche033