ROSCon 2018 will be happening in Madrid in September. The call for proposals has been posted. The deadline is on July 2nd, now just under a month away! Our first submissions have started coming in. If you’d like to propose a talk but aren’t sure what to talk about this thread is for you.
Talking at ROSCon can be very rewarding way to share your expertise and knowledge with the greater community. However, putting in a proposal to ROSCon can sometimes be intimidating because you don’t know if there are people in the community who are interested in what you’re doing.
To that end I’d like to kick off a brainstorming thread here on topics that people would like to see presented at ROSCon. Even if you won’t be able to make it to ROSCon feel free to suggest a topic: we record all videos and post them online. All of the previous years talks are linked to from the programs (2017, 2016, 2015, 2014, 2013, 2012). With people sharing topics that they would like to learn more about I hope their posts here will inspire more people to submit talks. We have a large and diverse community and want everyone to consider sharing what they’re working on.
Note that this thread is meant to be inspiration for submissions and will not be part of the Program Committee’s review process.
Please reply to this thread to share the sort of talk that you’d like to see someone present at ROSCon this September.
Guidelines:
This is a brainstorming session.
Be positive.
There are no wrong answers. Please don’t critique others’ responses, but build upon them.
I’d like to see a short talk from Open Robotics about the development process for ROS (in particular ROS 2) as a way to introduce people to how to participate in development, whether that be through commenting on design discussions, making bug reports, fixing bugs, or adding features.
I want to know
1.how to localize robot indoor accurately except UWB
2.how to monitor the network normally avoid robot is out of online , and out of control
3.robot hardware is so boring , if there any simple way to construct a robot
What does it take to convert it from a quick-and-dirty prototype to an actual ROS package expected to be used by all the community? (correct installation, roslaunch, examples, tests…).
From my dirty script in my home folder to a released ROS package in multiple ros distros.
I’d be interested in seeing an MVP demo of a real application in ROS2 (more than basic pub/sub), and explaining some of the preconfigured options available or what’s coming in the near future.
Then explaining areas where help is requested so we can know what areas people are looking for outside contributors to help with specifically.
Many companies creating autonomous robots for unstructured environments are realizing that its impossible to deal with all the edge cases upfront, so they are opting to create remote operating centers where the robot asks for help, and a remote operator then remotes in to deal with the edge case. I’d be very interested on a talk on how this can be done with ROS.
Another suggestion: deployment approaches for ROS applications in commercial and research settings that are a little bigger than one or two robots. Containerisation, network management, runtime testing, internal buildfarms, quality assurance processes, telemetry, etc.
How about of art, many modern artists want to make autonomous system or robot to show what they thought. Talking about experiences co-working with them might be a interesting story and unique.
I’d like to hear an overview about testing: how to quick-start, what options are available, tips etc. - AFAI googled there has been no dedicated talk about testing in previous ROSCon occurrences. This kind of talk will help esp. new hires and people with less experience in testing in ROS and/or general development.
Some topics I can think of off the top of my skull. Some of these may be based on my misunderstanding / lack of understanding (I myself need the overview :))
Re-visit test-{first/driven} approach. There is a slide shared back in 2014. The content is not integrated into ros.org (i.e. the content in this slide might be forgotten sadly).
I would like to here more about ROS-Control concept in detail. Especially the basic concepts of it and how for example create standard control system from Sensor, Controller and Actor.
Currently are Sensors and Actors always part of the RobotHW which is in some cases very cumbersome to use. This is just a point I thought about a lot lately and did get to any sensible solution.
P.S. I am even eagar to research it myself until the presentation, but as of today my knowledge does not go deep enough.
I would be interested in continuous integration/deployment (including testing) based on kubernetes and its infrastructure (helm, keel, kontinuous, etc.)
This is perhaps a little last minute, but I’ve been back and forth between submitting a proposal for a few weeks now.
I’ve been working with testing in ROS, and have been tinkering with creating a new package to abstract unit and integration tests a bit further. In my mind, the package would allow you to simply define subs/pubs and test a given set of nodes to verify their output. Take for example a simple node that does filtering on command input data, you would provide example input to the node, and check for expected output. It would theoretically also be able to take rosbags as an input.
Would a talk briefing over the state of testing, and then going over this sort of package be valuable? I know I can get something working by then, but whether it’s a full on package or work in progress would to be seen.
I have been writing a lot of rostests and gtests lately and would be very interested in this project/proposal. Also please keep me informed about the project, I would love to contribute if it makes sense.
@vmayoral: I just released TensorSwarm which is a reinforcement learning framework for mobile robot swarms. If I am lucky you will get a presentation of the tool at Roscon.
Continuing the testing and debugging theme, here’s the demo video in my proposed talk:
The talk is about using Mozilla rr for reversible debugging, coupled with some tricks to make debugging ROS nodes easier by republishing messages from inside the replayed process.
