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

How can the solution code learn the robot configuration? #600

Open
zbynekwinkler opened this issue Sep 10, 2020 · 4 comments
Open

How can the solution code learn the robot configuration? #600

zbynekwinkler opened this issue Sep 10, 2020 · 4 comments
Labels
enhancement New feature or request

Comments

@zbynekwinkler
Copy link

Is there some rosparam or rostopic that would list this information? If not, can it be added?

@nkoenig
Copy link
Contributor

nkoenig commented Sep 11, 2020

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.

@zbynekwinkler
Copy link
Author

You can communicate this type of information through the comms model.

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 rosparam or rostopic so that further complicates things. We would have to get comms up and running before the rest of the system which is something we are not ready to do at this time.

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 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 rosparam-able or rostopic-able way to learn the robot configuration? Some kind of introspection.

@zbynekwinkler
Copy link
Author

You can communicate this type of information through the comms model.

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.

@AravindaDP
Copy link

AravindaDP commented Oct 30, 2020

I see that we could parse /<robot_name>/robot_description rosparam to get some information regarding robot configuration but I guess this could be a fragile approach. (Difficult to correctly identify exact sensor configuration of default robots X1 through X4) (Besides for some reason this ros param is not available when I use catkin_install launch command)

@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?

@nkoenig nkoenig added enhancement New feature or request and removed proposal labels Nov 18, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants