-
Notifications
You must be signed in to change notification settings - Fork 19
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
ROS version? #3
Comments
Sounds great. Porting for ROS compatibility seems pretty feasible. I'd be happy to discuss ways that it could be merged into master so that you don't need to maintain a separate fork, but whatever works for you. |
I'm glad to see this program has been ported to C++, this would make the porting to ROS easier for me. I'll have a look at the code from this repository and let you know what I think it's best. Inevitably, the new repository would depend on catkin and roscpp/rospy. |
A small FYI, we have created a ROS version of Procman. It's fully functional in the previous manner of lcm-procman we have made minimal modifications so far. However we may need to modify the communications further to support the situation of PCs become disconnected from the sheriff. So it seems it might be difficult to keep it compatible with this repo. FYI: @heuristicus |
Hi @ashuang ,
We use procman on our bots here in Oxford. But have shifted to ROS otherwise.
We are planning to rewrite the communications part of procman to use ROS.
Do you envisage any major problems with shifting to ROS? (Beyond the roscore being detected)
Ideally it could be an "official" fork, as procman is pretty feature complete.
(FYI @mcamurri)
The text was updated successfully, but these errors were encountered: