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

Frames and Entities #289

Closed
mxgrey opened this issue Dec 16, 2014 · 1 comment
Closed

Frames and Entities #289

mxgrey opened this issue Dec 16, 2014 · 1 comment
Assignees
Labels
priority: high should be resolved right now tag: feature request Indicates new feature requests
Milestone

Comments

@mxgrey
Copy link
Member

mxgrey commented Dec 16, 2014

As we've discussed, I intend to implement a Frame class that would serve as a base class for things like BodyNodes and EndEffectors. The Frame class would establish a well-defined kinematic tree structure within the DART API that offers new semantics to the user for interacting with data that exists in reference frames.

I was thinking about the concept of an Entity class proposed by JS, and I think it would be a good complement to the Frame class. The Entity class would be a base class for objects that exist within some Frame. It would keep track of what its reference frame is, and it would receive notifications when properties of its reference frame (such as pose, velocity, and acceleration) are changed. The Frame class would inherit the Entity class, since every Frame exists within a reference frame (besides the World Frame, but that's a special case).

I think the Entity class should also encapsulate rendering information, that way the user would be able to easily add renderable objects by creating their own Entities and plugging them into the kinematic tree by giving it a reference frame. Then rendering can be handled by simply traversing the kinematic tree and passing through each Entity.

@mxgrey mxgrey added priority: high should be resolved right now tag: feature request Indicates new feature requests Comp: API labels Dec 16, 2014
@mxgrey mxgrey self-assigned this Dec 16, 2014
@mxgrey
Copy link
Member Author

mxgrey commented Feb 24, 2015

This is now finished in #319

@mxgrey mxgrey closed this as completed Feb 24, 2015
@jslee02 jslee02 added this to the Release DART 5.0 milestone Feb 24, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority: high should be resolved right now tag: feature request Indicates new feature requests
Projects
None yet
Development

No branches or pull requests

2 participants