-
Notifications
You must be signed in to change notification settings - Fork 8
Gamma support #2
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
base: master
Are you sure you want to change the base?
Conversation
LucaGemma87
commented
Dec 21, 2015
- Debugging and checking the joint state publisher.
- Hardware interface
now all seems work well !
modified: README.md deleted: config/force_torque_sensor_control.yaml modified: launch/display_simulation.launch modified: model/ft_sensor.gazebo.xacro modified: model/ft_sensor.urdf.xacro config/ launch/control_sensor_simulation.launch model/ft_sensor.trasmission.xacro
README.md
Outdated
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.
👍
55069f4 to
5441e9e
Compare
only warning message to be solved
Only warning message to resolve
Deleted unused files.
add ft_simulation_display.launch
add ft_simulation_display.launch
|
|
||
| 1) on first terminal for nano17 ft sensor type: | ||
|
|
||
| roslaunch force_torque_sensor ft_simulation_display.launch use_gamma:=false |
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.
Is there a way to pass a string instead of a true/false arg?
Would be nice to have something like:
roslaunch force_torque_sensor ft_simulation_display.launch use_model:=gamma
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.
Not found
|
Review done. Let me know about the suggestion above... and thanks! |
|
Thanks @LucaGemma87 . One last thing before merging, you moved this file from the model to the robot folder: Is there a reason for that? If not, I'd prefer that files implementing macros remain in the model folder, and their uses in the robot folder. Other than that, ok for the rest |