Open diogoalmeida opened 6 years ago
Proposed solution:
optodaq_sensors
through a hardware interface which can be configured by a user. I propose that the hardware interface support should be generic and on this repo, and a concrete yumi with force torque sensors would then instantiate a particular ft sensor by adding the required configuration/description files in a separate repository.@rtkg, @diogoalmeida Thank you for your input. I think those are good directives, and we are set on the right path.
Later today I'll create the "core" branch. I propose the following order of things:
I'd name the branch "kinetic" to be coherent with the conventions used in ROS repos.
As for your points:
@diogoalmeida thank you for the feedback.
Then for the new branch I'll focus on:
Sounds good! Can you make separate issues for those features and track them under the "Setup core yumi package" milestone? This will make it easier to track progress.
@diogoalmeida @YoshuaNava: regarding point 1 it might be an idea to have a short chat / discussion? There have been some recent discussions about ros-i urdfs that might be good to take into account.
I also have some other things I'd like to discuss with you, so perhaps we could combine that with a short discussion about the robot support package.
@gavanderhoorn, that sounds great. I am out of office until Friday, and next week my availability starts on Wednesday. So, Friday at some point in time or later next week works for me!
@rtkg @diogoalmeida @gavanderhoorn: This week I'm very busy. Could it be next week after Wednesday?
On a different note, should we arrange the details of the meeting via mail?
@YoshuaNava wrote:
should we arrange the details of the meeting via mail?
yes, let's do that.
Could you send me a message on my tu address? It's used in just about any commit on any of the repositories I've committed to.
We currently have a 'main' brainch,
egm_modifications
with code for our EGM-compatible yumis. Then we have branches likeoptodaq_sensors
for the optoforce-equipped Yumi.This does not make sense, as everytime we update
egm_modifications
, those changes should be made available to the optoforce Yumi. Furthermore, we might want to change other Yumis in the future. This repo should contain base code for all the Yumis, and we should have a way to keep the feature/Yumi-specific files away from this repo.