Add option to visualize <link> reference frame axis. visualize <collision> and <visual> frame axis. - Githubissues

gazebosim / gazebo-classic

Gazebo classic. For the latest version, see https://github.com/gazebosim/gz-sim

http://classic.gazebosim.org/

Other

1.19k stars 480 forks source link

Add option to visualize <link> reference frame axis. visualize <collision> and <visual> frame axis. #853

Open osrf-migration opened 11 years ago

osrf-migration commented 11 years ago

Original report (archived issue) by John Hsu (Bitbucket: hsu, GitHub: hsu).

osrf-migration commented 9 years ago

Original comment by Andrei Haidu (Bitbucket: ahaidu).

bump

A frame visualization mode, something similar to: Right Click -> View -> Frames , I think would be very useful

osrf-migration commented 9 years ago

Original comment by Nate Koenig (Bitbucket: Nathan Koenig).

set assignee_account_id to "557058:095b1e12-74ed-4e20-b44f-2f0745b616e0"
set assignee to "nkoenig (Bitbucket: nkoenig, GitHub: nkoenig)"

osrf-migration commented 9 years ago

Original comment by John Hsu (Bitbucket: hsu, GitHub: hsu).

actually this topic just came up in haptix as well, wanted to visualize imu sensor frames as well...

osrf-migration commented 9 years ago

Original comment by Louise Poubel (Bitbucket: chapulina, GitHub: chapulina).

I'm also working on some frame visualization for the Apply Force GUI, and it is needed on the Model Editor as well.

I think we should decide on a standard way of representing frames across all tools.
This will be probably tricky, but it would be great to visually tell if it's a model frame, or a link frame, collision, visual...
This is the current state of the Force GUI, the thin lines represent the link frame.
- Pros: It stretches outside of the link, no need to view transparent.
- Cons: Might become too cluttered; No direction.

I have an old implementation of frame visuals for the model editor here (2ee18d8203dbe65d175f7d7914f6e19b55d52a0e), I'll share a screen shot when I can, but it basically looks like the joint visuals, just smaller and without arrow heads.
- Pros: More compact, shows direction.
- Cons: Very similar to joint visuals, disappears inside model.

osrf-migration commented 9 years ago

Original comment by Steve Peters (Bitbucket: Steven Peters, GitHub: scpeters).

set component to "gui"

osrf-migration commented 9 years ago

Original comment by Louise Poubel (Bitbucket: chapulina, GitHub: chapulina).

Since my last comment:

It was decided not to add link frame / CoM visuals to the apply force dialog, so the screenshot above was never merged.
A line-style origin visual for the world was added in pull request #1700

Pull request #1762 adds small visuals for the link frames - no model, collision or visual frames yet.

osrf-migration commented 9 years ago

Original comment by Louise Poubel (Bitbucket: chapulina, GitHub: chapulina).

There is a question about sensor frames.

osrf-migration commented 9 years ago

Original comment by Louise Poubel (Bitbucket: chapulina, GitHub: chapulina).

@spaepcke

So for visuals and collisions, make frame visuals similar to the ones for links but with a V or a C floating next to it.

osrf-migration commented 8 years ago

Original comment by Nate Koenig (Bitbucket: Nathan Koenig).

set version to "all"