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

Versatile Robot Configurations #293

Closed
osrf-migration opened this issue Dec 11, 2019 · 4 comments
Closed

Versatile Robot Configurations #293

osrf-migration opened this issue Dec 11, 2019 · 4 comments

Comments

@osrf-migration
Copy link

Original report (archived issue) by Martin Dlouhy (Bitbucket: robotikacz).


Today is the deadline for the user model submission via pull-request for Urban Circuit, so this post is rather proposal for the next challenge.

The process adding new configuration is rather complex - here I would like to thank Arthur Schang (Arthur Schang) for his help with our ("robotika") pull request (it is not over yet). Actually all we wanted to do is to replace original HD camera in X2 config 4 (with lidar 30m) by RGBD in order to see small obstacles in front of the robot and distinguish ramps from obstacles. The PR is mainly copy & paste of parts we do not really understand (unfortunately there was no working example to start with, but this will surely change for Cave Circuit). Also we should not really get the attribution (#284), unless you count this process 😉. Note, we gave up to repeat this process for X1 which could be more suitable for the subway environment (rails).

So that was the motivation - question is if this can be simplified? In particular if you are building configuration only from existing
components (robot and sensors) and you only "mount" them together. The complex process can be reserved for new/non-existing robots and sensors. The configuration would be then like "shopping list" where you could choose from sensors and only specify placement. There could be even just few "mounting positions" like front, left, rear ... or just (x y z yaw pitch roll). There is no need to copy materials, worlds, models etc. This list would be input for “generator” which could create the complex configuration if that is the only way - or it could create it “on demand” during start of the simulation. Is this feasible?

@osrf-migration
Copy link
Author

Original comment by Neil Johnson (Bitbucket: realdealneil1980).


Martin, you took the words right out of my mouth. I agree with what you mentioned. It would certainly be nice if we could develop vehicles similar to X1-X4 with relatively minor changes to sensors without having to build out a whole new package for the vehicle. So, if we wanted to use the X2 config 2 but with a nicer IMU, we could just choose that and accept whatever cost penalty was associated with that decision. So, I second this proposal.

@osrf-migration
Copy link
Author

Original comment by Angela Maio (Bitbucket: Angela Maio).


Since this proposal is related to competition design, please post on the DARPA Subterranean Challenge Community Forum.

@osrf-migration
Copy link
Author

Original comment by Angela Maio (Bitbucket: Angela Maio).


  • changed state from "new" to "on hold"

@nkoenig
Copy link
Contributor

nkoenig commented Aug 11, 2020

Please use the DARPA Subterranean Challenge Community Forum.

@nkoenig nkoenig closed this as completed Aug 11, 2020
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

2 participants