-
Notifications
You must be signed in to change notification settings - Fork 99
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
How can the solution code learn the robot configuration? #600
Comments
You can communicate this type of information through the comms model. Alternatively, if you know the robots that you want to use ahead of time, then you can bake this information into the robot docker images. |
That is a bit awkward for us since the startup of our solution needs this information and comms is not available for us in that part of our code. As we learn in #270 we cannot do a single shot communication along the lines of calling
That is the point of my question - we would like to have a single docker image supporting multiple configuration since that works better for us - logistics-wise. Would it be possible to add some |
I just realized I cannot. The information is just not available so there is nothing to send through the comms model. Hard coding it is the only possible way right now. |
I see that we could parse @nkoenig Now that the information we need is available on simulation container according to #584 can we have same information available as rosparam on solution container? |
Is there some
rosparam
orrostopic
that would list this information? If not, can it be added?The text was updated successfully, but these errors were encountered: