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

ROS version? #3

Open
mauricefallon opened this issue Feb 4, 2020 · 3 comments
Open

ROS version? #3

mauricefallon opened this issue Feb 4, 2020 · 3 comments

Comments

@mauricefallon
Copy link

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)

@ashuang
Copy link
Owner

ashuang commented Feb 13, 2020

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.

@mcamurri
Copy link

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.

@mauricefallon
Copy link
Author

A small FYI, we have created a ROS version of Procman. It's fully functional in the previous manner of lcm-procman
https://github.com/ori-drs/procman_ros

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

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

No branches or pull requests

3 participants