-
Notifications
You must be signed in to change notification settings - Fork 204
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
New ball shooter plugin for the "Scan and Dock and Deliver" task #311
Conversation
Signed-off-by: Carlos Agüero <[email protected]>
Signed-off-by: Carlos Agüero <[email protected]>
Signed-off-by: Carlos Agüero <[email protected]>
Signed-off-by: Carlos Agüero <[email protected]>
The gazebo 7 test is failing. Since this is very old now, I've changed the merge requirements to make it optional and added the gazebo 11 test to the list of required checks. I'm also updating the test images just to make sure they are correct. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this looks great! Thanks for putting it together. I added one suggestion about putting the shot_force explicitly in the ball_shooter.xacro, if you agree that could make things easier for users.
A couple other notes:
- I tested varying the shot force and number of shots. These seemed to be working as expected.
- I see what you mean about re-using the same ball. I think this is fine. I guess it's possible that teams will want to use a strategy of shooting a bunch of shots in rapid succession if they are running out of time, and this might be OK to allow if we decide to limit the number of shots (say, to 3 or whatever would reasonably fit). I think we can adjust this later if needed though.
/// | ||
/// * Optional parameters: | ||
/// <num_shots> - Number of shots allowed. Default to UINT_MAX. | ||
/// <shot_force> - Force (N) applied to the projectile. Default to 250 N. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What do you think about including this tag explicitly in the example and also the .xacro file we are providing ? Out of all the parameters, it seems like the one that users are most likely to want to adjust. Even if it is redundantly set to 250 it might make it easier to quickly pick up how to use this plugin.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good idea! Added in 07609f6.
<frame>wamv/ball_shooter_link</frame> | ||
<pose>0.2 0 0 0 0 0</pose> | ||
</projectile> | ||
<topic>${namespace}/${shooter_namespace}${name}/fire</topic> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is where I was thinking we could change to something like:
<shot_force>250</shot_force>
<topic>${namespace}/${shooter_namespace}${name}/fire</topic>
One more note: after updating the test images this is still not building on Gazebo 7. I'm not sure whether we should try to fix this or not. Thoughts? |
Signed-off-by: Carlos Agüero <[email protected]>
Signed-off-by: Carlos Agüero <[email protected]>
I needed to add a few |
See issue #280.
How to test it:
Terminal 1:
Terminal 2:
You should observe how the blue ball is fired.
Feel free to play with the plugin parameters in
ball_shooter.xacro
for testing.Note about the ball shooter model: For now, the model is just a box. This will be replaced in the future when a nicer model is ready. It shouldn't be any functional difference in any case.