https://docs.google.com/document/d/1mSJqlsYnl-EjavHP03HCkNgzMy9iSuQ000i3ecxfFgY/edit?usp=sharing

Simulation : Basic robot and environment modelling Simulation : Basic robot and environment modelling

Google Summer of Code Program 2020 Project Proposal Sachin shetty sachinsshetty.de@gmail.com sachinshetty

Project Abstract.
Design an editor/interface to add interactions with Robot and obstacles by integrating OpenRoberta with a game/physics engine like Godot or Phaser.js

Project Description.

Trial of JS engines like Phaser and Babylon js for environment creation with robot movement.

Create simple blocks with a path for the robot to traverse. These blocks can be drag and dropped to create a maze-like obstacle course. The blocks will have generated code for each robot movement and restriction.

Task Link : https://github.com/OpenRoberta/openroberta-lab/wiki/Simulation%3A-Basic-robot-and-environment-modelling

Personal Currently studying M.Sc Informatik at Uni-Bonn with interest in Autonomous Systems

Coursework Robotics : Probabilistic Robotics at Uni-Bonn. M.Sc. Germany Software Engineering : S/W Engg fundamentals class at BVBCET, India Computer graphics : OpenGL basics as part of project work at BVBCET, India Physics simulation : No coursework taken Experience Worked as a full stack developer for 4 years at Subex Ltd and EFI Ltd, Bengaluru Project : Prior work based on simulation like game (Dont Eat Me) : designed a simple game using Phaser.js game engines as part of Uni-bonn ‘CS Game jam 2019, game available at https://slabs.tech/tasty-assassin/ and github : https://github.com/slabstech/tasty-assassin Jekyll blog updated for no tracking and no cookies, maintained since 3+ years. github.com/gaganyatri.com Android app for automating undergraduate lab journal in 2012, saving more than 25000 pages per year, App has run for 8 years till 2019. Publications : Special Pedestrian and Head Pose Detection for Autonomous Vehicles, https://link.springer.com/book/10.1007/978-981-13-2553-3 Trace Transform Based Identifier for Speech Based Image Retrieval On Mobile Phones, https://ieeexplore.ieee.org/abstract/document/6637307/ Personal Website : https://gaganyatri.com https://slabs.tech

TODO =

Project Template sourced from Jenkins GSOC Template and Open Source Robotics

Project Deliverables Note: The dates in the GSoC Timeline takes precedence over this document GSoC Timeline: https://developers.google.com/open-source/gsoc/timeline May 4: Community bonding begins. Get to know your mentors, what will you need for your development environment? What aspects of the projecy objectives need to be clarified or expanded? What mailing list and other on-line communication means will you use and join? At the minimum, you will need to establish a github account and share it with your mentor, backup mentors, Jenkins organization administrator, and any other community members June 1 (coding begins) - What will you have to do to ensure that coding starts by this date? We expect you will have a development environment for OpenRoberta (core, plugin or other) working as part of the proposal effort.
June 29-July3 (Phase 1 Evaluation) - What will you have done by this point? Your mentor will use this to judge your progress and whether you pass or fail. July 27-31 (Phase 2 Evaluation) - What will you have done by this point? Your mentor will use this to judge your progress and whether you pass or fail. August 24-31 (Final Evaluation) - What will you have done at this point? What will you deliver? Your mentor will use this to judge your progress and whether you pass or fail. Sept 8 (Final Results Announced) - What will you have done at this point? You can use the period between Final Evaluation and here to do clean up, improve documentation, etc. Post GSOC - What will you do?

Proposed Schedule

During each phase, please make it clear whether code will be ready to be submitted for inclusion. Also ensure that your code will be available for review almost every day. Do not work long periods (more than 2-3 days) without submitting code to the git repository for your project. You should normally commit code to Github everyday or almost every day (except weekends).

March 16 - March 31 (Application Period)

What will you do during this period?

April 1 - May 4 (Acceptance Waiting Period)

What will you do during this period?

May 4 - June 1 (Community Bonding Period)

What will you do during this period?

June 1 - July 3 (Coding period 1)

What will you do during this period?

Remember that your coding phase 1 evaluation is at the end of this period (June 29 - July 3). You need to make deliverables for phase 1 before the evaluation period. Make sure you spend time on your presentation slides.

July 3 - July 31 (Coding period 2)

What will you do during this period?

Remember that your coding phase 2 evaluation is at the end of this period (July 27-31) before the evaluation period. You need to make deliverables for phase 2 before the evaluation period. Make sure you spend time to work on your presentation slides.

July 31 - Aug 24 (Coding period 3)

What will you do during this period?

Remember that your coding phase 3 FINAL evaluation is at the end of this period (Aug 24-31). You need to make deliverables for final milestones and prepare for writing documentation and code submission before this period ends. Make sure you spend time to work on your presentation slides.

Future Improvements

Here, some future improvements on this project are proposed. This would be done after the GSoC program timeline or as Bonus implementation during the program itself if things go better than expected.

Continued Involvement

How do you want to be involved with Jenkins in the future? What role do you see yourself growing into? Consider this like a career statement for your role in the Jenkins Project. Your mentors can help you achieve your goals.

Conflict of Interests or Commitment

State whether you may have any conflicts that may prevent you from working at full potential or may not allow you to contribute code you develop during GSoC. Possible reasons would include participating in a summer internship, or a scholarship/fellowship at your school that restricts your ability to claim a copyright on your work. Although working or being funded by your school can be OK with GSoC, we need to know about your other commitments, and also need to be certain that the code you write can be contributed by you to Jenkins without a claim by your employer or University.

Major Challenges foreseen

Discuss any of the challenges that you see could make your project difficult or issues you need to resolve.

References Links, books, etc that are relevant to your project