IRC League 10



IRC INTERNATIONALS
MIDDLE LEVEL PROBLEM STATEMENT


Problem Statement

To build one Autonomous and one Manual Robot that can carry out the Bot-Kart Race.

Real World Inspiration

A Bot-Kart Race is run on a track in which the driver drives their karts at a pre-set distance while avoiding various hurdles in their path.

Actual Task Description

Robots are tasked to collect the hurdle props to reach to the finish area and create a predefined structure. Hurdle props are nothing but 3D printed cubes, that can be stacked to form the structure in the minimum possible time to achieve bonus score.

Bot Information

Name of the bot Start Area Maximum Size Task
Bot 1 - Name of Bot need to be decided by the participantsStart Area 1Length: 9.5 Inches
Width: 9.5 Inches
Height: No limit
Bot 1 will be the automated bot and needs to follow the given path and move the hurdles placed in its path to the designated area adjacent to the line and finally reach the finish area.
Bot 2 - Name of Bot need to be decided by the participantsStart Area 2Length: 9.5 Inches
Width: 9.5 Inches
Height: No limit
Bot 2 will be the manual controlled and needs to collect all the hurdles one by one and take them to the collection area and make a stack (Final Stack) at the end in the respective form given in the image.

Other Information

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.
Track
Track is the area on which robot needs to move removing the hurdles from its path.
Hurdle area
Hurdle area is the area where hurdle is kept. Further defined by numbers as Hurdle area 1, Hurdle area 2 and so on.
Drop area
Drop area is the area where Bot 1 has to keep all the hurdles so that Bot 2 will collect it and take it to the collection area.
Collection area
This is the area where all the hurdles need to be kept by Bot 2 to finish the task.
Finish Area
This is the area where Bot 1 should reach to end the race.

Arena

Arena Length :123 Inches(Including Boundary)117 Inches(Working Area)
Arena Width :99 Inches(Including Boundary)93 Inches(Working Area)
Arena Boundary :Height - 6 InchesHeight - 6 Inches

Arena Details

Prop Details


Black CubeBlue CubeOrange CubePurple CubeGolden Cube

Props Description

Prop name Colors 3-D Printing Details
CubesBlack, Blue, Golden, Purple & Orange Layer Height: 0.3mm
Shell Thickness: 1.2mm
Infill type: Hexagon
Infill Density: 8%
Print Speed: 60mm/s
3-D File:   STL GX GCODE

Final Stack


Final Stack

Arena Tasks


Tasks of Bot 1:

  • Bot needs to follow the given track of black line at center with white surroundings
  • Bot has to reach at Hurdle area 1 and move the hurdle to its designated location i.e. Drop area 1
  • Bot has to reach at Hurdle area 2 and move the hurdle to its designated location i.e. Drop area 2
  • Bot has to reach at Hurdle area 3 and move the hurdle to its designated location i.e. Drop area 3
  • Bot has to reach at Hurdle area 4 and move the hurdle to its designated location i.e. Drop area 4
  • Bot has to reach at Hurdle area 5 and move the hurdle to its designated location i.e. Drop area 5
  • Bot has to reach to the Finish Area to end the task

Tasks of Bot 2:

  • Collect the Hurdle from Drop area 1 and place it at Collection area
  • Collect the Hurdle from Drop area 2 and place it at Collection area
  • Collect the Hurdle from Drop area 3 and place it at Collection area
  • Collect the Hurdle from Drop area 4 and place it at Collection area
  • Collect the Hurdle from Drop area 5 and place it at Collection area


Note: Hurdles should be placed in the sequence as shown in the image below(Final Stack). Formation will be judged from the bottom most cube(Black) of the stack. Scores will be awarded for individual cubes in case if some part of the stack is not according to the images given or formed partially.
For Example: If Black, Blue and Purple cube is in order and position of Golden and orange is reversed than scores will be awarded only for 3 correct placed cube or only 3 cubes were kept till the end of 6 minutes time.

Important Points during the run

  • It is the responsibility of the team to make sure they call DONE, when all the structures are 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.
  • Bonus points will be awarded only when all the tasks of the run are completed fully. This also means that the second run will not be provided.

Scoring

Type of Scoring - Mid match / End of match

Task description Score for each prop Total Score
Successfully able to move Hurdle to its respective Drop area (Points will be awarded to each hurdle)
Scoring Method: Mid Match
70 350
Successfully able to collect Hurdle from the Drop area (Points will be awarded to each hurdle)
Scoring Method: Mid Match
50 250
Successfully able to take Hurdle to Collection area and place in form of stack (Points will be awarded to each hurdle but only when it is placed according to the color pattern shown in the image below)
Scoring Method: End of Match
80 400

The Scoring Methods

There are two ways in which scoring can happen for a run:

  • END-OF-MATCH SCORING - Most of your score depends on the conditions 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 (students only) about what points were scored or missed and why.
    • Points aren’t given for results the robot produces during the match but then disturbs before the end. For example, you might have kept a prop at designated location during the run, but in a bid to other tasks if that prop is disturbed and stays in that situation at the end of the match, no scores will be rewarded.
    • If a team agrees with the score, the team’s leader needs to sign the sheet, and the score is considered as final.
    • If you don’t agree, tell the referee nicely. Referees can be wrong, and when they are, they want to know.
    • If there is still a conflict, you need to tell the referee about the conflict and follow the Conflict Raising process.
    • After a short discussion, if the referee is not sure about the score, the head referee makes the final decision.

  • 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 as scoreless. Please don’t try to show 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 as scoreless.
    • 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.

Bonus Score

If a team is able to finish the task before time so a score of 5 points will be added for every 5 seconds of the time left.
For example: From total time of 6 minutes, if the task was completed at 5 minutes 30 seconds mark, so 30 points will be added to the final score. If the task was completed at 5 minutes 35 seconds mark, so 25 points will be added to the final score.

Middle Level Rules and Regulations

  • The duration of the run will be 6 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 into the drop area, not partially, not on the line.
  • Deviation: If a robot deviates from the line, the deviated robot will be kept at the respective start area.
  • A total of 4 deviations (4 runs) are allowed during the whole arena run of 6 minutes. Remember this count (4) is for both the bots. In such a situation, the run need to start again and referee would bring the deviated bot to its respective start area.
  • No time will be paused in case the robot deviates from its path.
  • 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 the Start areas (Over ruling this can lead to disqualification) and nowhere else. They can repair their robots at start area in case of damage in the robot.
  • If robots got stuck with each other or toppled over, only the referee will keep the robot at the respective start area/areas.
  • If any of the robot 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 got damaged then 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 a sticker.
  • It is mandatory to mention Name and Number on your bots. (For example: Ronaldo - 7)

Interpretation

  • Problem statement text should be taken literally without any scope of interpretation.
  • Do not interpret text based on your assumption about intent, or on how a situation might be in “real life”.
  • If 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.

Examples

  • If a task requirement is to collect the prop. 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. It 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.

Variability

As you build and program the bots, 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.

Explanation of the parts that can be used

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

CP Lite Brain

CP Lite Brain

Intro Brain

E-Series Intro Brain

Lite Brain

E-Series Lite Brain

Full 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.

Grey Motor

Geared Motor

Blue Motor

Encoded Motor

Black Motor

Geared Motor


Reference for the placement of props/Robots


Robot Start New Area Props Placement Props Placement

Verification of Robots

Note: The design shown in the image is a graphical image and no design reference must be drawn from this. For your design, please refer to the exact size details of the verification prop.
Note: Bot should sit comfortably on the floor during verification. Any part of the bot in air would be liable for rejection.
Verification Image 1Verification Image 2Verification Image 3Verification Image 4

Middle Level Hint Video