To build two Manual Robot that can carry out the game of Hurdle race in Bot-Olympics.

A Hurdle Race is a track and field event in which athletes run a pre-set distance while avoiding various hurdles in their path. For IRC purpose, this game is twisted a bit to perform stacking as well.

Robots are tasked to collect/pick/drag the hurdle props into the Finish area and create a predefined structure. Hurdle props are nothing but 3D printed Cubes, that can be stacked to form the structure.

Start areas
Start area 1 is the start area for the first runner bot and Start area 2 is the start area for the second runner bot. These are also the spots where the bots will be kept at the start of the run.

Start Area 1

Start Area 2

Track
The Track (Including white area) is the area on which robot needs to move and remove/drag/pick/place the hurdles, untill all the props are in the collection area.

Track

Hurdle Area
Hurdle area is the area where hurdles are kept. Which is further defined by numbers as Hurdle area 1, Hurdle area 2 and so on

Hurdle Area 1

Hurdle Area 2

Hurdle Area 3

Hurdle Area 4

Hurdle Area 5

Crossover Line
Crossover Line is the area which is the borderline for both bots and where Bot 1 has to pass all the collected hurdles to Bot 2 so that the hurdle will be taken to the Collection area.

Crossover Line

Crossover Gate
Crossover gate is the structure that is placed on Crossover Line. The Hurdle (Cube) prop need to pass through this gate opening for it to be considered handed over.

Crossover Gate

Collection Area
This is the area where all the Hurdles need to be kept and design a stack with the hurdles.

Collection Area

• Start Position: Start Area 1
• Bot needs to follow the given track of coloured lines with white surroundings
• Bot has to reach at Hurdle area 1 by taking along the hurdle to the crossover line and make sure hurdle is passed on the other side of the crossover line through the crossover gate.
• Bot has to reach at Hurdle area 2 by taking along the hurdle to the crossover line and make sure hurdle is passed on the other side of the crossover line through the crossover gate.
• Bot has to reach at Hurdle area 3 by taking along the hurdle to the crossover line and make sure hurdle is passed on the other side of the crossover line through the crossover gate.
• Bot has to reach it's Start Area to end the task .
• End Position: Start Area 1

• Start Position: Start Area 2
• Bot needs to follow the given track of coloured lines with white surroundings
• Bot has to reach at Hurdle area 4 and take the hurdle to the collection area
• Bot has to reach at Hurdle area 5 and take the hurdle to the collection area
• Bot has to bring hurdles 1, 2 and 3 (being dropped by Bot 1 across the crossover line) to collection area
• Form the stack as indicated by the structure shown in Figure 1
• End Position: Any where within Arena

Deviation: When any of the bots moves out of the track (completely i.e.no part of the robot in contact with the Track, before bringing all the props in the collection area), a Deviation will be marked. Even a single Deviation by any bot will result in end of the game for the team and scores achieved so far will become the final scores.

• It is the responsibility of the team to make sure they call DONE, when the structure is ready and well within the designated areas.
• "Calling out DONE" doesn't necessarily mean to call out the word done, it means that the team should indicate to the referee in any way that the team is done with the run and would want to get the scores.
• If the base of the stack is not within the designated area, no score will be awarded (irrespective of any formation on top).
• Bonus points will be awarded only when all the tasks (for both the bots) of the run are completed fully. This also means that the second run will not be provided.

Bot 1 and Bot 2 need to make sure they stay on the designated track and don't leave the track. However, if all the props are collected, only the Bot no. 2 can leave the track.

• END-OF-MATCH SCORING - Most of your score depends on the conditions/design of props/arena exactly at the end of the match. Following are important reference points for this kind of scoring:
  
  
  • The arena/props are the evidence of most of your score. When the run ends, PLEASE DON’T TOUCH ANYTHING! The referee first needs time to record the condition of the arena on a score sheet and come to an agreement with you (participating team members only) about what points were scored or missed and why.
  • Points aren’t given for results the robot produces during the run and are disturbed before the end of the run. For example, you might have kept a prop at a designated location during the run, but in a bid to complete other tasks, if that prop is disturbed and stays in that situation at the end of the match, no scores will be rewarded.


• MID-MATCH SCORING - If a team’s score is permanently determined during the match, instead of at the end:
  
  
  • EXAMPLE: When a mission is required to be achieved through a specific method but is achieved by some other method, it is marked scoreless. Please don’t try to show the video to the referees.
  • EXAMPLE: If the robot puts Model A into a scoring condition by destroying Model B, the Model B mission is marked scoreless and vice versa.
  • EXAMPLE: If the robot is required to drive over something in the middle of the match, the referee will mark the score for that when it happens, since no lingering evidence will be visible.

If a team is able to finish the task before time, a score of 5 points will be added for every 5 seconds of the time left.
For example: From the total time of 4 minutes, if the task was completed at 3 minutes 30 seconds mark (between 3 minutes 26 seconds to 3 minutes 30 seconds), 30 points will be added to the final score.
If task was completed at 3 minutes 34 seconds , 25 points will be added to the final score.

• If a team agrees with the score, the team’s leader needs to sign the sheet, and the score is final.
• If you don’t agree, tell the referee nicely. Referees can be wrong, and when they are, they want to know.
• If still there is a conflict, you need to tell the referee and follow the Conflict Raising process.
• In such situation, the case will be referred to Chief Referee. Chief Referee’s decision would be final and binding.

• The duration of the run will be 4 minutes and there won't be any trial time provided for the run on the event day.
• Scores will be given only if the props are dropped completely inside the collection area, not partially ,i.e. not on the line. Final score also will be provided if stack is created within boundary and in the same sequence.
• Deviation need to be understood properly. It does mean Bots should not leave the designated track. In a situation where during the play (and before bringing all props in the collection area) any prop is out of reach of Bot and Bot has to leave the track to get it back, that situation will also be considered a Deviation.
• This deviation rule is applicable untill all the props are brought into the collection area. Once all 5 props are collected and brought in the collection area, the bots can leave the track and go any where else within the arena. The bots need to be at their end positions to completely end the run.
• If a deviation happens, the run will be stopped and scores earned till the time of deviation would become the final score of the team.
• Only Avishkaar kits are allowed to build these robots.
• A power source of 7.4 Volts and 2200 mAh current is allowed in the bots.
• Participants can touch the robots only when they are in their start areas and nowhere else. Overruling this can lead to disqualification.
• Participants can repair their bots at the start area in case of any issues. Run timer will continue and will not be paused in such a case.
• If robots got stuck with each other or are toppled over, only the referee will keep the robot at the respective start area/areas.
• If any of the robots goes out of the arena, the referee would bring it back to the respective start area and the arena props (if they were attached to the robot in some manner) to their respective start locations and no points would be awarded to the team.
• During the arena run if by any means the arena/props get damaged, then the referee can disqualify the team.
• If a team is able to finish all its tasks before time, bonus of 5 points per 5 seconds will be added to their final score.
• Both robots should be identifiable preferably by their name and number sticker.
• You are not allowed to interact with any part of the field that’s not COMPLETELY in designated area.
• Due to any reason, if already created structure is damaged then participants need to reconstruct it to get scores.For example: If robot has created any of the structure and it got damaged by robot while creating another structure or by toppling then participants need to reconstruct it to get scores.
• It is mandatory to mention Name and Number on your bots. (For example: Ronaldo - 7)

• Problem statement text means exactly and only what it says, so take it literally.
• Do not interpret text based on your assumption about intent, or on how a situation might be in “real life”.
• If any particular detail isn’t mentioned, then it doesn’t matter.
• There are no hidden requirements or restrictions. If you’ve read everything, then you know everything.

• If a task requirement is to collect the prop, then that means the prop should be in control and attached with the robot.
• If a mission requirement is to place the prop at the designated location, this means the prop should be completely inside the designated area. It will not be considered if it is partially inside or on the line.
• You’re encouraged to think this way - please learn the requirements and constraints very well, tasks need to be done as explained in the task description only.

As you build and program, keep in mind that our suppliers, mentors, and volunteers try very hard to make all arena and props as per the specifications mentioned, but you should always expect some variability (i.e. tolerance of 5%) due to machine/manual process and transportation. Consider this as a warning and incorporate them into your robot design. The variabilities can be defined as:

• Flaws in the arrangement of border walls i.e. boundary mats.
• Variety in lighting conditions, from hour to hour, and/or arena to arena.
• Texture/bumps under the mat, due to imperfections, seams, or props.
• Presence or absence of tape at the edges of the arena and props.
• Waviness in the arena itself - at many competitions, it’s impossible for the arena to be rolled out in time to lose their waviness. Location and severity of waviness vary. You are being warned here. Consider this while designing.
• Two important building techniques you can use to limit the effects of variability are:
  • Use caster wheels while building your robot to avoid bumps in the arena.
  • Cover your sensors from surrounding light.

Brains: There is no limitation on the number of brains used per robot. Choose from the Avishkaar-manufactured ones shown here.

CP Lite Brain

E-Series Intro Brain

E-Series Lite Brain

E-Series Full Brain

Motors: There is no limitation on the number of motors used per robot. Choose among the Avishkaar-manufactured ones shown here. No other motors are allowed.

Geared Motor

Encoded Motor

Geared Motor