Home

IRC International Junior Problem Statement
IRC League 11


IRC LEAGUE (INTERNATIONALS - DUBAI)
JUNIOR LEVEL PROBLEM STATEMENT


Problem Statement:

To build a pair of wired/wireless robots that can setup Air Base for strengthening our defences.

Problem Description:

There is an emergency situation and the Air Force is asked to create a temporary Air Base to help Army with their operations. Your team in the Air Force, is tasked to develop two robots (called Dare Bot and Savot Bot) that will be used for Setting up of Air Base for strengthening our defences.

Bot Information:

The Dare Bot and Savot Bot are small, flexible manageable cranes and robotic machines" that can be used to lift and move prefabricated blocks at the Air Base Setup Site.

Both the bots would have to carry out myriad of tasks on the Air Base site ranging from identifying different prefabricated construction blocks to picking/ dropping or pushing/dragging these blocks and finally assembling them to become meaningful structures like Hangar, Control Tower, Radar Tower, Runway and Fuel Unit. All these tasks would involve different kinds of mechanisms and it is best to select specific mechanisms for each of the bots.

Dare Bot
Dare Bot is the first robot that has been tasked to ensure that it grips, pulls or drag and drops various material used in Air Base Setup. The base of robot should not exceed the 23 cm X 23 cm.

Savot Bot
Savot Bot is the second robot that has been tasked to ensure that it grips, pushes and drops the material used in Air Base Setup. The base of robot should not exceed the 23 cm x 23 cm.
Note: The above mechanisms are mostly suggestive, you can choose to create a design that you deem fit. However, the robot should be able to fit inside the verification prop with length and width of 23 cm X 23 cm

Arena

  • The length & width of the arena is 8 feet x 8 feet.
  • The Arena is placed on the ground within a frame (made out of EVA sheet).
  • All the props are described in detail next to the arena design.
  • All the props are of the suggestive shapes made either out of Avishkaar kits, MDF or EVA sheets only. Props size is suggestive. Tolerance should be only 5%.
  • Both the robots can do all the tasks simultaneously. If in case any robot breaks down then another robot completes all of the remaining tasks.
  • Task, once started, must be completed before starting up another task. If any of the robots pick/move the any of the props that don’t belong to the current tasks then your run should stop at that time and scores obtained at that time become the final scores.
  • Both robots should be identifiable preferably by a sticker.
  • Dare Bot will start from Start Area 1 and Savot Bot will start from Start Area 2.
  • Design of any thing like Hangar, Control Tower, Radar Tower etc should be at the designated location.
  • Only 1 prop is allowed to be carried at one time by one Robot.

Arena Details

Note: Refer the arena image for the initial positions of blocks

Actual Arena
Junior Arena
Detailed Arena
Junior Arena

Arena Tasks:

(Can be executed by any of the Robots)
Construction of Hangar : Hangar unit is a critical building where planes are parked. For this,base levels need to be built and covered with a roof. Any robot can construct this structure. Structure should be designed inside the designated area including roof of the Hangar.For complete design of hangar please see below.

Hangar-Base Hangar-Base Hangar-Base Hangar-Base

Construction of Control Tower: A control tower is a building at an airport from which instructions are given to aircraft when they are taking off or landing. For this, three levels need to be built. Any robot can construct this structure. Structure should be designed(Part in contact with ground i.e. Caster wheels) inside the designated area.For complete design of control tower please see below.

Hangar-Base Hangar-Base Hangar-Base Hangar-Base

Construction of Radar Tower: Radar towers are used for detection of unidentified flying elements approaching our territory. For this, two levels need to be built. Any robot can construct this structure. Structure should be designed (Part in contact with ground) inside the designated area. For complete design of Radar tower please see below.

Hangar-Base Hangar-Base Hangar-Base

Construction of Fuel Unit: Any robot can construct the Fuel Unit. This structure is for fulfilling the fuel needs of the fleet. This is a single storey structure. For complete design of Fuel Unit please see below.

Hangar-Base

Construction of a Runway: Any robot can construct the Fuel Unit. This structure is for fulfilling the fuel needs of the fleet. This is a single storey structure. For complete design of Fuel Unit please see below.

Hangar-Base Hangar-Base

Scoring

Task DescriptionScore
Control Tower:
Successfully dragged the base chamber of Control Tower from the Material collection area to designated location 30
Successfully placed Mapping unit into the base chamber of Control tower150
Successfully placed ATC antenna on the Mapping unit. Note: ATC antenna is only placed when mapping unit into the base chamber of control tower50
Radar Tower:
Successfully placed Radar base Tower in designated location100
Successfully placed Radar antenna into Radar base Tower130
Fuel Unit:
Successfully able to place fuel unit to designated location70
Hanger:
Successfully constructed the level 1 of Hangar. (Note: 60 for each Piece.) and block should be placed in horizontal direction120
Successfully constructed the roof of the hanger into the base of the hangar. Note: The distance between two blocks doesn’t matter . 200
Runway:
Successfully constructed the Runway (Note 30 For each piece)150

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 , not on the line.
  • Only Avishkaar kits are allowed to build these robots.
  • A power source of 7.5 Volts and 2200 MAH current is allowed in the bots.
  • Participants can touch the Robots only when they are in the start areas and nowhere else. They can repair their robots at start area in case of damage in the robot.
  • 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 for them.
  • If a team is able to finish all its tasks before time, all the props will be refurbished on the arena and the team can start scoring points again. The timer would stop when the refurbishing is taking place.

Interpretation

  • Problem statement text means exactly and only what it says, so take it literally whenever possible.
  • Do not interpret text based on your assumption about intent, or on how a situation might be in “real life”.
  • If a 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, and then realize the many FREEDOMS that are left.

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.
  • 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 varies. You are being warned here. Consider this while designing.
  • Two important building techniques you can use to limit the effects of variability are:

    1. Use Caster wheels while building your Robot to avoid bumps in Arena.
    2. Cover your sensors from surrounding light.

Explanation on 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
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.

meared-motor-88-rpm
Geared Motor(88 rpm)
meared-motor-126-rpm
Geared Motor(126 rpm)
encoded-motors
Encoded Motor



Reference for the placement of props

meared-motor-88-rpm

The Scoring Process

  • END-OF-MATCH SCORING - Most of your score depends on the conditions at the exact time the match ends.
  • The Arena/Props is 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 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 trashes before the end.
  • If you agree with the score, you 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.
  • After a short discussion, if the referee is not sure about the score, the head referee makes the final decision.
  • MID-MATCH SCORING - Sometimes part of your 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 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.
    - 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.

Verification of Robots

verification-robot robot-verification-prop jnior-level-props