Dear Gazebo community,
I am Jivan and I am a third year Computer Science undergrad at the CET Bhubaneswar in India. I am interested in contributing to Ignition through GSoC program 2020 and specially in the idea proposed as “Demos for Ignition knowledge base”.
I am well acquainted with version control and linux and my primary programming knowledge is python but by choosing this project I can improve my C++ skills as well. I would like to get some feedback so that I can start working on this project. Currenlty, I am going through the documentation of Ignition. @chapulina can give me some feedback on this maybe.
Dear Gazebo community,
Thank you for the interest in the project!
I’d recommend you go through some Ignition Gazebo tutorials to get familiar with the simulator. The goal of this project is to create several small demos showcasing other features, which may or may not be things like:
- Create a differential drive robot and teleoperate it with the keyboard
- Write your own plugin that spawns spheres into simulation
- Create a custom component and visualize it with a custom GUI plugin
The exact demos will be defined as the project is happening. The student will be responsible for writing the C++ plugin code, as well as necessary world and model files, and then creating documentation for it - all with the help of the mentors.
@marya, feel free to add anything.
I had read the documentation of Ignition Gazebo. Can you tell me what should I do next?
That’s great to hear!
One thing you could try now would be writing a short tutorial about a topic of your choice to get a feeling of how that would work.
One idea would be to write a demo / tutorial similar to this one. It’s about spawning spheres in simulation by pressing a custom GUI button.
Some helpful resources:
The tutorial would go here.
So, I have to write the tutorial using ignition gazebo that you’ve mentioned in the earlier message. I am working on it also, I am writing proposal for the same. If you can suggest some points then it will be great.
Sorry, that’s not what I meant. You’re not required to write a tutorial. Since you said you had already gone through the documentation, I recommended writing a tutorial in case you wanted to get a feeling about how the project would go. But that’s just a suggestion
Writing a tutorial is just one suggestion. Other ways to start getting a feeling for the project:
- Try writing your own plugin, even if you don’t contribute it back, to see how comfortable you’re with Ignition and get some ideas.
- Open a pull request fixing some issue you can find on the current documentation. That’s a great way to see how comfortable you are with the tutorials infrastructure.
- Open a pull request fixing some small bug on any Ignition library. This way you get a feeling for how the code contribution process goes.
This project is about creating demos and documentation for a project lacking both, so expect it to be tough to get started. So you’re encouraged to poke around as much as you can, because that’s what you’d be doing during the internship.