Cognitronix

Overview The Cognitronix Hackathon is a 36-hour intensive innovation challenge designed to test participants on their ability to ideate, design, and implement solutions under strict time constraints. The event combines problem-solving, technical expertise, and teamwork in a high-pressure environment that simulates real-world engineering scenarios. Participants will work in teams to develop solutions to domain-specific problem statements. They are expected to: Build a functional prototype. Demonstrate consistent progress. Present a structured final solution to a panel of judges. Eligibility & Team Guidelines: Participation in the Cognitronix Hackathon is open to undergraduate B.Tech students, and the event emphasizes collaborative problem-solving and structured team execution. The following team guidelines must be followed: Each team must consist of 2 to 4 members. Each participant is allowed to be part of only one team. The hackathon will follow a hybrid participation model, where development is conducted online while key checkpoints require physical presence. It is mandatory for every team to include at least one student from an Electronics-related discipline (such as ECE, EEE, or equivalent). All teams are expected to maintain professionalism, communicate effectively, and collaborate fairly throughout the event. Event Duration: The hackathon will be conducted as a continuous 36-hour event, beginning immediately after the official inauguration and running uninterrupted until its conclusion. Participants are expected to manage their time efficiently across the following phases: Ideation Development Testing Final presentation Domains & Problem Statements: Problem statements will be revealed only at the time of inauguration to ensure fairness and spontaneity. The hackathon will include the following domains: AI/ML: 3 problem statements will be provided. Verilog: 2 problem statements will be provided. LT Spice: 1 problem statement will be provided. Teams will either select or be assigned a problem statement based on availability. Once a problem statement has been finalized, it cannot be changed. Teams are expected to clearly understand the problem and design a feasible and structured solution approach. Hackathon Structure: The event is structured to reflect a real-world development cycle so that both progress and execution can be evaluated effectively. The overall flow of the event will be as follows: The hackathon will begin with an inauguration and briefing session. Problem statements will then be released and allocated to teams. A continuous development phase of 36 hours will follow. A mid-evaluation will be conducted during the development phase. The event will conclude with a final evaluation and demonstration. Work Tracking & Submission Requirements: GitHub Activity Each team is required to maintain an active GitHub repository for their project. To ensure continuous development and transparency: At least one meaningful commit must be made every two hours. Progress Updates (Every 8 Hours): Teams must submit periodic updates in the form of a short presentation. Each update should clearly include: The work that has been completed so far. The challenges that have been encountered. The planned next steps. These updates must be submitted physically at the designated venue. Consistency in both updates and repository activity will play an important role in the evaluation. Evaluation Process: Mid Evaluation The mid evaluation focuses on assessing the team’s understanding of the problem, their approach, and their progress. During this stage, teams are expected to: Present their methodology. Demonstrate initial implementation. Justify the feasibility of their solution. Final Evaluation: The final evaluation focuses on the completeness and effectiveness of the solution. Teams are required to: Present a working prototype. Clearly explain their implementation and results. Demonstrate the overall impact of their solution. A live demonstration of the solution is mandatory. Judging Criteria: Teams will be evaluated on multiple aspects that reflect both technical depth and execution quality. The evaluation will be guided by the following criteria: Innovation and Approach: The originality of the idea and clarity in the problem-solving strategy will be assessed. Technical Implementation: The depth, correctness, and handling of complexity in the solution will be evaluated. Consistency and Progress: Regular GitHub activity and adherence to update timelines will be considered. Feasibility and Impact: The practical applicability and real-world relevance of the solution will be examined. Presentation and Communication: The clarity, structure, and effectiveness of the explanation will be judged. Final Prototype and Demonstration: The functionality, completeness, and quality of the final output will be evaluated. Venue & Logistics: All offline components of the hackathon will be conducted at the NAC Hall. Teams are required to be physically present during: Scheduled progress submissions (every 8 hours) Mid evaluation Final evaluation In case of high participation, evaluation slots may be assigned to ensure the smooth execution of the event. Rules & Code of Conduct: All participants are expected to maintain integrity and professionalism throughout the event. The following rules must be strictly followed: Any form of plagiarism or copying will result in immediate disqualification. Teams must strictly adhere to all timelines and submission requirements. Any form of unfair practice will lead to penalties. Participants must maintain respectful and professional behavior at all times. The decision of the judging panel will be final and binding.