Object dynamic state #234
Merged
Object dynamic state #234
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
AbdelrhmanBassiouny
force-pushed
the
object_dynamic_state
branch
from
ceb34e3 to
b546276
Compare
AbdelrhmanBassiouny
force-pushed
the
object_dynamic_state
branch
from
784f43c to
838ef77
Compare
… ability for the used to specift the state id.
… pycram objects, closing and opening gripper works.
… giskard. Updated robot_description usage from old version to new version in Giskard. Added options for disabling monitors and allowing gripper collision in achieve_cartesian_goal in Giskard and added these options to the configurations of the world. Added a globale variable that indicates if robokudo was found or not to avoid using real detection processs module if Robokudo was not found.
… is not synced correctly. Fixed Goal Validator. robot_state_updater.py also updates states of objects. no need for original pose anymore to move mobile robot in multiverse.
…make a feedback loop on gripper closing.
…e kept while navigating.
Added mutex for multiverse writer client
…nged world methods.
…e kept while navigating.
…nged world methods.
…f prospection objects.
…entities except for world.
…ocation. Check for continuous joint when clipping. Fixed multiverse demo. Don't set link_state as it is not settable/needed.
AbdelrhmanBassiouny
force-pushed
the
object_dynamic_state
branch
from
716a6c4 to
5068e12
Compare
Tigul
reviewed
Dec 17, 2024
demos/pycram_multiverse_demo/demo_euROBIN_industrial_robotics.py
Outdated
Show resolved
Hide resolved
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This depends on #227
Created a super class for Object and Link called PhysicalBody, this hast common attributes for any physical body like pose, velocity, contact points.
Also changed ContactPoint to use bodies instead of links as datatype for returned bodies.
Also Everything now is a WorldEntity including PhysicalBody, and Wolrd, this unified the methods eq and hash so they are only implemented in WorldEntity except for World which overwrites them.
Also every WorldEntity has a parent_entity, so Link has parent as Object and Object has parent as world, while World has None.
In addition the ontology_concept class variable was moved from Object class to PhysicalBody class because now it makes more sense there since any PhysicalBody is a PhysicalObject by Default.
Added attributes for PhysicalBody like velocity, is_translating, is_rotating, is_moving but currently they are not set by anything, one way could be through querying the simulation but one could also set them by performing their own calculation and according to their own thresholds for that, they just are helpful to be inside physical body if someone is interested in its dynamic state.
Also Added a PhysicalBodyState that includes pose, velocity, is_translating, and is_rotating.