IRC League 10



IRC INTERNATIONALS
JUNIOR LEVEL PROBLEM STATEMENT


Problem Statement

To design two manually controlled robots that can carry out the game of stacking in Bot-Olympics.

Real World Inspiration

Stacking is a sport where the team needs to stack different objects in a defined scheme and complete the task in given time.

Actual Task Description

Robots are tasked to make stacks of different designs and formations in the designated area to complete the task in the minimum possible time to achieve the 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
Both the Bots need to work with each other to form the stacks at their designed areas either by dragging, picking up, lifting etc keeping in mind that it does not damage the Arena while taking pieces of stacks from the collection 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

Arena Information

Start areas
Start area 1 is the start area for the first stacker bot and Start area 2 is the start area for the second stacker bot. These are also the spots where robots will be kept at the start of the run.
Stack areas
Stack area is the area where the required structures need to be built. Required structures in Figures 1 to 4 need to be created at Stack Area 1 to 4 respectively.
Collection area
This is the area where all the pieces to make stack need to be kept by the referee at the start of the run.

Arena & Props

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 CubeBlack RingBlue RingGolden RingOrange RingPurple Ring

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
RingsBlack, 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

Stacks: Figures


Stacks: FiguresStacks: FiguresStacks: FiguresStacks: Figures

Arena Tasks

  • Both the bots will start from their respective areas.
  • They need to take pieces from the collection area and move them to form the defined structures at the designated places [Stack Areas].
  • There is no sequence that needs to be followed.
  • If you complete all the stack formations within time, announce it by saying DONE. The referee will take note and will take up the scores based on the state of the stack formations.

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.
  • 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 of the run are completed fully. This also means that the second run will not be provided.
  • Materials used for art and crafts can be used to decorate robots, for example: Papers, Tapes etc. This is limited to mostly passive things. Any other motors, batteries or other electronics or metal/plastics can’t be attached. Decision of Verification team in this regard will be final.
  • Placement of stack pieces at the collection area will be random. This means, at different times and different arenas, the arrangement may vary.
    Note: No conflict against this will be considered and/or entertained.


Bot 1 and Bot 2 are tasked to form 4 different types of stacks as shown in the images below while taking/collecting pieces of stacks from the collection area. The total task is against time.

Scoring

Type of Scoring - Mid match / End of match

Task description Score for each prop Total Score
Successfully able to make Stack of the pyramid (Figure 1) in Stack Area 1 (Points will be awarded for each piece only when it is placed according to the placement in the images)
Scoring Method: End of Match
40 200
Successfully able to make Stack of rings (Figure 2) in Stack Area 2 (Points will be awarded for each piece only when it is placed according to the placement in the images)
Scoring Method: End of Match
40 200
Successfully able to make Stack of the bigger triangle (Figure 3) in Stack Area 3 (Points will be awarded for each piece only when it is placed according to the placement in the images)
Scoring Method: End of Match
45 450
Successfully able to make Stack of the small triangle (Figure 4) in Stack Area 4 (Points will be awarded for each piece only when it is placed according to the placement in the images)
Scoring Method: End of Match
50 150

The Scoring Methods

There are two ways scoring can happen for a run:

  • 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 (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 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.
    • 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 then follow the Conflict Raising process.
    • After a short discussion, if the referee is not sure about the score, the Chief Referee will make 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 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.

Bonus Score

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

Junior 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 ,i.e. not on the line.
  • 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 (Overruling this can lead to disqualification) and nowhere else. They can repair their robots at the start area in case of damage in the robot.
  • 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 remaining 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)

Interpretation

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

Examples

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

Variability

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.

Explanation of the parts that can be used

Brains: 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 wheel of the bot which is in air would be liable for rejection.
Verification Image 1Verification Image 2