BEGIN:VCALENDAR VERSION:2.0 PRODID:IEEE vTools.Events//EN CALSCALE:GREGORIAN BEGIN:VTIMEZONE TZID:Asia/Kolkata BEGIN:STANDARD DTSTART:19451014T230000 TZOFFSETFROM:+0630 TZOFFSETTO:+0530 TZNAME:IST END:STANDARD END:VTIMEZONE BEGIN:VEVENT DTSTAMP:20241012T190520Z UID:CB9191CD-DD8B-4EAF-A600-A1F9FF9AD11E DTSTART;TZID=Asia/Kolkata:20241009T160000 DTEND;TZID=Asia/Kolkata:20241009T180000 DESCRIPTION:The event\, Codeager: A Narrative Coding Challenge\, began at\n 4:30 PM in rooms M509 and M510. It was a coding competition\nwhere partici pants showcased their skills in solving coding\nproblems within a set time frame.\n The event provided a platform for participants to demonstrate \ntheir technical expertise and problem-solving abilities in the field\nof competitive programming.\n The challenge was a team-based competition\ , with each team\nconsisting of two members. Participants were tasked with solving\n8 coding problems within 105 minutes.\n Each team received a unique team ID and entered the\ncompetition area\, where they worked colla boratively to solve\ncoding problems. The event tested participants' codin g skills\,\ncritical thinking\, and problem-solving abilities under time\n pressure.\n The challenge involved various tasks\, including downloadin g\ninput files for specific problems and saving them on their\ndesktops to work on. Each team was allowed to use up to three\nhints throughout the e vent\, but only one hint per question.\n Participants had the flexibili ty to use any IDE and programming\nlanguage of their choice. However\, the y were required to switch\ntheir search engines to Yahoo and using AI assi stants or code\ngeneration tools such as ChatGPT\, Copilots\, Blackbox.AI\ , or\nGemini was strictly prohibited.\n The organizing team ensured tha t rules were followed\,\nprohibiting communication between members of diff erent teams\nduring the competition.\n Teams progressed through the cod ing problems\, with volunteers\nmonitoring their progress and ensuring the smooth running of\nthe event. Volunteers only intervened when necessary t o keep the\ncompetition fair and on schedule.\n The team that solved th e most questions in the least amount of\ntime would be declared the winner . In the event of a tie\, the team\nthat completed the tasks in the shorte st time would win. Teams\nhad to solve at least four questions to be eligi ble for prizes.\n The results were announced later on the official hand les of\nCodeager \, followed by a group photo with participants\,\nvolunte ers\, and organizers\n\nCo-sponsored by: IEEE-VIT Student Branch\n\nRoom: M509 & M510\, VIDYALANKAR INSTITUTE OF TECHNOLOGY\, Sangam Nagar\,\, Mumba i\, Maharashtra 400037\, Mumbai\, Maharashtra\, India\, 400037 LOCATION:Room: M509 & M510\, VIDYALANKAR INSTITUTE OF TECHNOLOGY\, Sangam N agar\,\, Mumbai\, Maharashtra 400037\, Mumbai\, Maharashtra\, India\, 4000 37 ORGANIZER:vidyalankarieee@gmail.com SEQUENCE:0 SUMMARY:IEEE Fest: Codeger URL;VALUE=URI:https://events.vtools.ieee.org/m/439650 X-ALT-DESC:Description: <br /><p>The event\, Codeager: A Narrative Coding C hallenge\, began at<br>4:30 PM in rooms M509 and M510. It was a coding com petition<br>where participants showcased their skills in solving coding<br >problems within a set time frame.<br> The event provided a platform fo r participants to demonstrate<br>their technical expertise and problem-sol ving abilities in the field<br>of competitive programming.<br> The chal lenge was a team-based competition\, with each team<br>consisting of two m embers. Participants were tasked with solving<br>8 coding problems within 105 minutes.<br> Each team received a unique team ID and entered the<br >competition area\, where they worked collaboratively to solve<br>coding p roblems. The event tested participants' coding skills\,<br>critical thinki ng\, and problem-solving abilities under time<br>pressure.<br> The chal lenge involved various tasks\, including downloading<br>input files for sp ecific problems and saving them on their<br>desktops to work on. Each team was allowed to use up to three<br>hints throughout the event\, but only o ne hint per question.<br> Participants had the flexibility to use any I DE and programming<br>language of their choice. However\, they were requir ed to switch<br>their search engines to Yahoo and using AI assistants or c ode<br>generation tools such as ChatGPT\, Copilots\, Blackbox.AI\, or<br>G emini was strictly prohibited.<br> The organizing team ensured that rul es were followed\,<br>prohibiting communication between members of differe nt teams<br>during the competition.<br> Teams progressed through the co ding problems\, with volunteers<br>monitoring their progress and ensuring the smooth running of<br>the event. Volunteers only intervened when necess ary to keep the<br>competition fair and on schedule.<br> The team that solved the most questions in the least amount of<br>time would be declared the winner. In the event of a tie\, the team<br>that completed the tasks in the shortest time would win. Teams<br>had to solve at least four questi ons to be eligible for prizes.<br> The results were announced later on the official handles of<br>Codeager \, followed by a group photo with part icipants\,<br>volunteers\, and organizers</p> END:VEVENT END:VCALENDAR