Skip to content
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

Rbs se3 viz #153

Open
wants to merge 5 commits into
base: master
Choose a base branch
from
Open

Rbs se3 viz #153

wants to merge 5 commits into from

Conversation

mmaurus
Copy link

@mmaurus mmaurus commented Jan 26, 2021

Added vizkit3d plugin for Wrenches and new RigidBodyStateSE3

Comment on lines 44 to 45
pluginNames->push_back("RigidBodyStateSE3Visualization");
pluginNames->push_back("WrenchVisualization");
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Wrong indentation (happens elswhere in the patch).

Rock style guide is 4 space indent, no tabs. I'm guessing that you are using tabs.

Comment on lines 28 to 30



Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please avoid unecessary leading/trailing lines.

// update transform
osg::Vec3d force(wrench.force.x(), wrench.force.y(), wrench.force.z());
Q.makeRotate(osg::Vec3d(0,0,1), force);
//force_node->setScale(osg::Vec3f(resolution, resolution, resolution*force.length()));
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Don't commit commented-out code. If it is commented out, it's not part of the implementation and just adds noise.

@doudou
Copy link
Member

doudou commented Jan 27, 2021

Not a requirement, but we've started to create a while ago "interactive" unit tests for visualization, that are in test/viz/. They basically work by showing some data and asking the user/tester whether some stuff appear as expected.

Would you consider creating those for these two visualizers ? It would really help.

${OPTIONAL_HPP}
DEPS base-types
LIBS ${Boost_SYSTEM_LIBRARY}
DEPS_PKGCONFIG base-logging
DEPS_PKGCONFIG base-logging PrimitivesFactory osgViz
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I really believe we should consider other alternatives before adding osgViz as a "hard" dependency in base/types.

This is also breaking rock-core's build.

@doudou

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In practice, base/types already depends on gui/vizkit3d which depends on osgViz. The (optional) dependency should definitely be explicitly added to the manifest, though.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, that will be a problem in constrained environments (i.e embedded computers running iodrivers_base based drivers). Can we please don't do that?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The keyword was optional ;-). The dependency on osgViz that this PR adds is also optional as the whole viz/ folder is disabled by the Rock CMake macros if vizkit3d is not available or if ROCK_VIZ_ENABLED is set to OFF.

base/types already depends optionally on gui/vizkit3d. In constrained environments, you usually exclude gui/.* which removes that particular dependency

Copy link
Contributor

@g-arjones g-arjones Feb 9, 2021

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

the whole viz/ folder is disabled by the Rock CMake macros if vizkit3d is not available or if ROCK_VIZ_ENABLED is set to OFF

I missed that, sorry. I guess I was misled by the breaking build (which is probably breaking for some other reason I didn't look into). Did this pass on your CI?

Copy link
Contributor

@g-arjones g-arjones Feb 9, 2021

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

-- Checking for module 'PrimitivesFactory'
--   No package 'PrimitivesFactory' found
CMake Error at /usr/share/cmake-3.10/Modules/FindPkgConfig.cmake:415 (message):
  A required package was not found
Call Stack (most recent call first):
  /usr/share/cmake-3.10/Modules/FindPkgConfig.cmake:593 (_pkg_check_modules_internal)
  /buildbot/squidbot-build/build/install/base/cmake/share/rock/cmake/Rock.cmake:288 (pkg_check_modules)
  /buildbot/squidbot-build/build/install/base/cmake/share/rock/cmake/Rock.cmake:383 (rock_find_pkgconfig)
  /buildbot/squidbot-build/build/install/base/cmake/share/rock/cmake/Rock.cmake:649 (rock_target_definition)
  /buildbot/squidbot-build/build/install/base/cmake/share/rock/cmake/Rock.cmake:811 (rock_library_common)
  viz/CMakeLists.txt:11 (rock_vizkit_plugin)

This is when building base/types

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't know what PrimitivesFactory is or where it comes from. I was looking at osgViz since it was what you mentioned in your comment.

Didn't check CI yet.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

PrimitivesFactory is a module in osgViz

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants