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

[ros2] World plugin with get/set entity state services #839

Merged
merged 1 commit into from
Feb 14, 2019

Conversation

chapulina
Copy link
Contributor

This is part of breaking gazebo_ros_api into several plugins, see #779 and #838.

See the migration documentation: ROS 2 Migration: Entity states.

Try the demo world added in this PR (see the world file for more detailed instructions):

gazebo gazebo_ros/worlds/gazebo_ros_state_demo.world

FYI @mkhansen-intel.

@chapulina chapulina changed the title [ros2] World plugin to get/set entity state services [ros2] World plugin with get/set entity state services Nov 16, 2018
Copy link
Member

@tfoote tfoote left a comment

Choose a reason for hiding this comment

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

Overall it looks good. Adding the status_message is a little odd. In general I think that that sort of output is better to go out on the console logging. Which looking at the implementation is already being done. Because the only thing that we can programmatically do with that information is display it to the user. I'm not entirely against it but it seems to be pushing the limit of what should go back in the message versus go out to console.

# * header.frame_id Filled with the relative_frame.
gazebo_msgs/EntityState state # Contains pose and twist.
bool success # Return true if get was successful. If false, the state contains garbage.
string status_message # Comments if available.
Copy link
Member

Choose a reason for hiding this comment

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

What sort of "comments" might go here?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I was just keeping it because it was in ROS 1, but I agree it doesn't serve any good purpose, so removed in 6387f4a.

@chapulina chapulina added the ros2 label Nov 29, 2018
@chapulina
Copy link
Contributor Author

@ros-pull-request-builder retest this please

1 similar comment
@chapulina
Copy link
Contributor Author

@ros-pull-request-builder retest this please

@chapulina chapulina force-pushed the ros2_state branch 2 times, most recently from de5ce8e to d98f584 Compare December 12, 2018 18:10
@chapulina
Copy link
Contributor Author

TODO(@chapulina) : rebase against new crystal branch

@chapulina chapulina changed the base branch from ros2 to crystal February 14, 2019 21:24
@chapulina
Copy link
Contributor Author

@nzlz's team has been using this branch (see #838 (comment)) and I've already addressed @tfoote's review comment, so I'm merging this.

@chapulina chapulina merged commit f9a7798 into crystal Feb 14, 2019
@chapulina chapulina deleted the ros2_state branch February 14, 2019 22:32
shiveshkhaitan pushed a commit to shiveshkhaitan/gazebo_ros_pkgs that referenced this pull request Jun 4, 2019
@mkhansenbot
Copy link

@chapulina - I don't see the gazebo_ros_state files in the 'ros2' branch, is that expected? I see they were merged to the 'crystal' branch, but not 'ros2'. I'd like to use this feature in dashing, has it been replaced somehow?

@chapulina
Copy link
Contributor Author

@mkhansen-intel , see #933. I'm still reviewing it. I was having some difficulties using it which I'm not sure were local problems in my setup.

chapulina pushed a commit that referenced this pull request Jun 5, 2019
* [ros2] World plugin to get/set entity state services (#839)

remove status_message

* [ros2] Port time commands (pause / reset) (#866)

* relative -> reference
@mkhansenbot
Copy link

I see it's merged now, thanks for the quick follow up

chapulina pushed a commit that referenced this pull request Aug 21, 2019
* [ros2] World plugin to get/set entity state services (#839)

remove status_message

* [ros2] Port time commands (pause / reset) (#866)

* [ros2] Migration of get/set world, model, joint, link, light properties

* Trying to pass CI test, try n1.

* clean up some linter warnings

* Requested changes in review, unfinished

* Fix uncrustify

* Address reviews

* more tests, joint types

Signed-off-by: Louise Poubel <louise@openrobotics.org>

* Revert changes to GetModelProperties message

Document gazebo_ros_properties header

* Convert msgs pose to math pose and use it on SetCoG

Signed-off-by: Louise Poubel <louise@openrobotics.org>
@JWSLAM
Copy link

JWSLAM commented Mar 25, 2021

@mkhansenbot @chapulina
I am using dashing,also want to use setModelState service. Which commit or branch should I check out. Waiting for reply, Thanks.

@i1Cps
Copy link

i1Cps commented May 7, 2023

I'm using foxy, and also want to user a service where i can set the state of a model. Have any similar services been migrated to Ros2 yet?

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

Successfully merging this pull request may close these issues.

5 participants