On Spot Prelims: 13th February | 14:00-15:00 Hrs | CLC Lecture Halls 05, 06

Finals: 14th February | 13:00-18:00 Hrs | Ice Dept. Lab

---

Peek-a-Boo

Are you a person intrigued by robotics? Does the feel of a robot titillate you? Do you believe you have the required skills but need a platform to put them to test? Well my pal you have come to the precise place. Take a walk into the labyrinth of robotics and explore the challenges within in this brand new robot debugging event of Pragyan. Debug the robot faster than the crowd and walk away with the cash prize and the bot of course. The only pre-requisites – basic robotics skills and a keen eye for finding and killing bugs!

Target

As it is well known, debugging a malfunctioning robot, is one of the most challenging and interesting aspect of robotics. The event evaluates how quickly the teams grasp the idea of a new robot and implement its working mechanism. It tests skills in electrical, electronics, mechanics and algorithm. So the event will be looking at itching those grey cells of bot geeks from around the country.

---

Online prelims will be held from 29-31 January

Registrations closed.

Fix the Android Prelims completed. Results out.

Prologue

Fix the Android is an on the spot robot debugging event. After prelims, 10 teams are chosen for the main event, where they are given pre-made robots. Blueprints and data sheets about the bot and its components are made available to the teams for their scrutiny. Each of these bots uniformly has 10 errors in their build up. These errors range from malfunctioning and missing components to erroneous connections. Teams armed with multimeters and other necessary equipments, try and dig out each one of these faults, make their bot bug-free and get the bots running on the test track. The fastest team to bring the bot to life wins.

Problem Statement

All teams are provided with a faulty robot. These robots have a number of bugs and errors in circuitry and algorithm, causing them to malfunction. Teams are required to debug these robots in the shortest possible time. Blueprint of robot and data sheet of ICs used would be provided to the teams. Teams are required to bring their own tools namely multimeters, nose pliers and wire cutter for debugging. Winners will be decided based on the total time taken to debug and successfully run the bot in the arena provided. Judge's decision shall be final and binding.

Prelims

• Teams of 3 are required to register themselves on the pragyan website.
• The participants will be taking the test on-line and will be required to answer the questions in the given time.
• The test would assess algorithms, circuits, coding and debugging.
• Short-listing for the finals will be based on the relative performance of the competitors.
• A maximum of 10 teams would be selected for the finals.
• Online prelims will be held from 29-31 January

Eligibility

All students with a valid identity card from their respective educational institutes are eligible to participate.

Rules and Regulations

• Nature and function of the robot will be intimated to the teams on the spot.
• All teams would be provided with uniform prototypes of the defective robot, having the same set of faults.
• Teams are required to bring their own hardware for debugging namely wire cutter, nose plier and multimeter.
• The event is designed to test debugging skills and not designing skills. So the central structure, function and circuitry of robot should not be altered during the debugging.
• Each team is given a maximum of 180 min for successfully debugging their respective bots and test run them on the standard arena.
• Teams are allowed multiple chances to test their bot in the testing arena anytime within the prescribed 180 min.
• In order to prevent crowding of teams at the testing arena, each team is given only 5 min at a time to test their bots, after which the next team is given a turn.
• If no team successfully debugs the bot, the number of individual faults identified and their elegant rectification would be the sole judging criteria.
• It is also the sole responsibility of the each team to ensure that they do not introduce further faults while debugging their bots. These added faults will not be evaluated as debugged errors as the case may be.
• Judge's decision shall be final and binding!
• The organizers reserve the right to change any or all of the above rules as they consider necessary. The changes will be marked in red. Please check the website consistently for updates.

Judging Criteria

• Winners will be decided based on the total time taken to debug and successfully run the bot in the arena provided.
• If no team successfully debugs the bot, the number of individual faults identified and their elegant rectification would be the sole judging criteria.

Team Composition

• Each team must consist of 3 members
• Teams are required to register themselves online
• Maximum of ten teams will be short-listed for the finals
• No person shall be a member of two teams

Certificate Details

• Certificate of Excellence will be given to the top 3 teams emerging from this competition.
• Certificates of Participation will be given to all the teams who make it to the final.

• What kind of robot would be given to us for debugging?
  Since it is an on the spot event complex bots like micromouse would not be given to the teams for debugging. However one can expect a bot at a difficulty level close to that of a photovore or a line follower. The actual bot will be known to teams only at the time of the event.
• Because the bot is completely new to us, on what basis are we supposed to debug it?
  Before the start of the finals, all selected finalists will have an introductory session where the nature and function of bot would be told to the teams. Besides this blueprint of the robot, data sheets of ICs used and other necessary support material would be provided to the teams to familiarize them with the bot before the start of the actual event.
• Would all teams be given the same type of bot with the same bugs?
  All 10 teams would get similar prototypes of the SAME faulty robot. The errors in the bots are also uniform so as to ensure equal difficulty level in debugging.
• Does the event involve software debugging i.e. correcting a erroneous program burned onto a microcontroller?
  The event is completely a hardware based affair. The event expects the participants to debug the given robot consisting of various electronic, electrical and mechanical components which might not be working properly, have faulty connections etc. There will be no software debugging included. So don't expect to see any programmable micro-controllers involved in the circuitry.
• What are we supposed to bring for the event?
  Because we provide you with the faulty bot, you only have to bring the necessary tools for debugging it namely multimeter, nose plier, wire cutter and a fully throttling brain.
• Do we get to take the debugged robot after the event?
  Unfortunately no. The above privilege is exclusively reserved for the event winner who gets the cash prize, certificate and the debugged robot.
• We have some more queries that are not given in this list. What should we do?
  You may contact any us via email or phone or post your queries on the forum.

Gautham Ram  +91 99406 85245

Akshay Agrawal  +91 99623 53125