is the shipping tray supposed to be listed as a model in the logical camera?

[dan]

In 2018, the shipping box showed up as a model (along with all the parts in the box) when it appeared under a logical camera. In the current code, the shipping tray does not show up as a model, only the parts on the tray are listed. Is that correct?

[Shane Loretz]

I would expect only the parts to show up in the logical camera. pull request #117 adds tf frames kit_tray_1 and kit_tray_2 for the trays. Run this to see the transform from world to one of the tray frames.

rosrun tf tf_echo kit_tray_1 world

[Shane Loretz]

Question answered and pull request #117 merged

[dan]

I just updated ariac3 but this frame is not showing up, either in tf view_frames or in tf_echo kit_tray_1 world. I tried both kit_tray1 and kit_tray1_frame (which would be consistent with the other names, such as bin1_frame) as well as kit_tray_1 and kit_tray_1_frame.

Not surprising that the tf_echo fails, since none of those frames show up in the tf tree visualized by tf view_frames

[Shane Loretz]

I see both frames using the latest prerelease.

Would you mind posting the output of this command?

apt list --installed | grep -e ignition -e sdformat -e gazebo

[dan]

''' apt list --installed | grep -e ignition -e sdformat -e gazebo

WARNING: apt does not have a stable CLI interface. Use with caution in scripts.

gazebo9/unknown,now 9.7.0-1~bionic amd64 [installed,automatic]

gazebo9-common/unknown,unknown,now 9.7.0-1~bionic all [installed,automatic]

gazebo9-plugin-base/unknown,now 9.7.0-1~bionic amd64 [installed,automatic]

libgazebo9/unknown,now 9.7.0-1~bionic amd64 [installed,automatic]

libgazebo9-dev/unknown,now 9.7.0-1~bionic amd64 [installed,automatic]

libignition-cmake-dev/unknown,now 0.6.1-1~bionic amd64 [installed,automatic]

libignition-common/unknown,now 1.1.1-1~bionic amd64 [installed,automatic]

libignition-common-dev/unknown,now 1.1.1-1~bionic amd64 [installed,automatic]

libignition-fuel-tools1-1/unknown,now 1.2.0-1~bionic amd64 [installed,automatic]

libignition-fuel-tools1-dev/unknown,now 1.2.0-1~bionic amd64 [installed,automatic]

libignition-math2/bionic,now 2.9.0+dfsg1-1 amd64 [installed]

libignition-math4/bionic,now 4.0.0+dfsg1-4 amd64 [installed,automatic]

libignition-math4-dev/bionic,now 4.0.0+dfsg1-4 amd64 [installed,automatic]

libignition-msgs/bionic,now 1.0.0+dfsg1-5 amd64 [installed,automatic]

libignition-msgs-dev/bionic,now 1.0.0+dfsg1-5 amd64 [installed,automatic]

libignition-transport4/bionic,now 4.0.0+dfsg-4 amd64 [installed,automatic]

libignition-transport4-dev/bionic,now 4.0.0+dfsg-4 amd64 [installed,automatic]

libsdformat6/unknown,now 6.2.0-1~bionic amd64 [installed,automatic]

libsdformat6-dev/unknown,now 6.2.0-1~bionic amd64 [installed,automatic]

ros-melodic-gazebo-dev/bionic,now 2.8.4-0bionic.20180706.234303 amd64 [installed,automatic]

ros-melodic-gazebo-msgs/bionic,now 2.8.4-0bionic.20181112.202939 amd64 [installed,automatic]

ros-melodic-gazebo-plugins/bionic,now 2.8.4-0bionic.20181117.185301 amd64 [installed,automatic]

ros-melodic-gazebo-ros/bionic,now 2.8.4-0bionic.20181117.190127 amd64 [installed,automatic]

ros-melodic-gazebo-ros-control/bionic,now 2.8.4-0bionic.20190221.010412 amd64 [installed,automatic]

ros-melodic-gazebo-ros-pkgs/bionic,now 2.8.4-0bionic.20181117.193954 amd64 [installed,automatic]

sdformat-sdf/unknown,unknown,now 8.0.0~pre4-1~bionic all [installed,automatic]

'''

[dan]

This is what I used to update: sudo apt-get update && sudo apt-get install ariac3

[Shane Loretz]

Mind running one more command?

apt list --installed | grep -e ariac

[dan]

apt list --installed | grep -e ariac

WARNING: apt does not have a stable CLI interface. Use with caution in scripts.

ariac3/unknown,now 3.0.0~pre4+git20190318r66ba65fe22124a5eebe2e27ca540efc86e971917-0~bionic amd64 [installed]

Here is the response to sudo apt-get install ariac3

ariac3 is already the newest version (3.0.0~pre4+git20190318r66ba65fe22124a5eebe2e27ca540efc86e971917-0~bionic).

[Shane Loretz]

That version does publish the tf_frames. I can't reproduce this issue on a fresh docker container with just the prerelease installed.

Is it possible there is an out-of-date from source build on this machine that's being run instead? In the same terminal you start ARIAC from, what's the output of catkin_find osrf_gear?

[Shane Loretz]

Opening until it's known whether the missing tf frame issue is a gear bug or a machine issue

[dan]

catkin_find osrf_gear

/opt/ros/melodic/include/osrf_gear

/opt/ros/melodic/lib/osrf_gear

/opt/ros/melodic/share/osrf_gear

I resolved it by doing a static publisher for those frames. If nobody else is having this issue, then it must be machine specific here, as you say.