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

Multiple roslisp nodes in a process #4

Open
130s opened this issue Jan 9, 2013 · 2 comments
Open

Multiple roslisp nodes in a process #4

130s opened this issue Jan 9, 2013 · 2 comments

Comments

@130s
Copy link
Member

130s commented Jan 9, 2013

Migrated from https://code.ros.org/trac/ros/ticket/2896
Reported by: bhaskara Owned by: bhaskara
Priority: major
Last modified ago: Jan 2011


This is a possible feature for diamondback or eastern box. See the discussion at http://www.ros.org/wiki/roslisp/Reviews/2010-07-16%20API%20Review.

@bhaskara bhaskara closed this as completed Apr 6, 2016
@bhaskara bhaskara reopened this Apr 6, 2016
@bhaskara bhaskara closed this as completed Apr 6, 2016
@bhaskara bhaskara reopened this Apr 6, 2016
@digikar99
Copy link

digikar99 commented Jul 26, 2020

Is this the same as nodelets - seems so to me; should I open a separate issue if not?

@gaya-
Copy link
Member

gaya- commented Jul 26, 2020

@digikar99 nodelets is not just for "running multiple ROS nodes in different threads in one process", which this issue is about. Nodelets also allow for efficient message passing between the different nodes of the same process. If you want efficient zero-copy message passing, open a new issue. If you only care about running multiple nodes in one REPL image, this issue is all you need.

...I personally am not going to put effort into implementing this. When I need multiple lisp nodes in my system, I just compile myself an executable (with add_lisp_executable) and run it in a terminal, in addition to my REPL image. One can also start two *inferior-lisp* processes in Emacs and have the other node run there. I've done that too, works pretty well. My lisp nodes usually publish with very low frequency, so I never bothered with the efficient message passing.

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

No branches or pull requests

4 participants