Commit
·
720ed94
1
Parent(s):
3dc7ef0
Add initial project structure with event details for Coherence 2025 hackathon, including .gitignore, documentation files, and Docker setup.
Browse files- .gitignore +69 -0
- Dockerfile +25 -0
- comb.md +154 -0
- comb.txt +155 -0
- data_1.txt +80 -0
- data_2.txt +68 -0
- data_3.txt +33 -0
- data_4.txt +94 -0
- main.py +124 -0
- requirements.txt +121 -0
.gitignore
ADDED
|
@@ -0,0 +1,69 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
# Environment variables
|
| 2 |
+
.env
|
| 3 |
+
|
| 4 |
+
# Python
|
| 5 |
+
__pycache__/
|
| 6 |
+
*.py[cod]
|
| 7 |
+
*$py.class
|
| 8 |
+
*.so
|
| 9 |
+
.Python
|
| 10 |
+
build/
|
| 11 |
+
develop-eggs/
|
| 12 |
+
dist/
|
| 13 |
+
downloads/
|
| 14 |
+
eggs/
|
| 15 |
+
.eggs/
|
| 16 |
+
lib/
|
| 17 |
+
lib64/
|
| 18 |
+
parts/
|
| 19 |
+
sdist/
|
| 20 |
+
var/
|
| 21 |
+
wheels/
|
| 22 |
+
*.egg-info/
|
| 23 |
+
.installed.cfg
|
| 24 |
+
*.egg
|
| 25 |
+
|
| 26 |
+
# Virtual Environment
|
| 27 |
+
venv/
|
| 28 |
+
env/
|
| 29 |
+
ENV/
|
| 30 |
+
.venv/
|
| 31 |
+
.env/
|
| 32 |
+
|
| 33 |
+
# IDE specific files
|
| 34 |
+
.idea/
|
| 35 |
+
.vscode/
|
| 36 |
+
*.swp
|
| 37 |
+
*.swo
|
| 38 |
+
.DS_Store
|
| 39 |
+
|
| 40 |
+
# Logs
|
| 41 |
+
*.log
|
| 42 |
+
logs/
|
| 43 |
+
|
| 44 |
+
# Local development
|
| 45 |
+
*.db
|
| 46 |
+
*.sqlite3
|
| 47 |
+
.coverage
|
| 48 |
+
htmlcov/
|
| 49 |
+
.pytest_cache/
|
| 50 |
+
.tox/
|
| 51 |
+
.nox/
|
| 52 |
+
.coverage.*
|
| 53 |
+
.cache
|
| 54 |
+
nosetests.xml
|
| 55 |
+
coverage.xml
|
| 56 |
+
*.cover
|
| 57 |
+
*.py,cover
|
| 58 |
+
.hypothesis/
|
| 59 |
+
.pytest_cache/
|
| 60 |
+
cover/
|
| 61 |
+
|
| 62 |
+
# Data files
|
| 63 |
+
*.csv
|
| 64 |
+
*.json
|
| 65 |
+
*.txt
|
| 66 |
+
!requirements.txt
|
| 67 |
+
!comb.txt
|
| 68 |
+
!comb.md
|
| 69 |
+
!data_*.txt
|
Dockerfile
ADDED
|
@@ -0,0 +1,25 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
# Use Python 3.10 as base image
|
| 2 |
+
FROM python:3.10-slim
|
| 3 |
+
|
| 4 |
+
# Set working directory
|
| 5 |
+
WORKDIR /app
|
| 6 |
+
|
| 7 |
+
# Install system dependencies
|
| 8 |
+
RUN apt-get update && apt-get install -y \
|
| 9 |
+
build-essential \
|
| 10 |
+
&& rm -rf /var/lib/apt/lists/*
|
| 11 |
+
|
| 12 |
+
# Copy requirements first to leverage Docker cache
|
| 13 |
+
COPY requirements.txt .
|
| 14 |
+
|
| 15 |
+
# Install Python dependencies
|
| 16 |
+
RUN pip install --no-cache-dir -r requirements.txt
|
| 17 |
+
|
| 18 |
+
# Create necessary directories for data files
|
| 19 |
+
RUN mkdir -p data
|
| 20 |
+
|
| 21 |
+
# Expose the port the app runs on
|
| 22 |
+
EXPOSE 7860
|
| 23 |
+
|
| 24 |
+
# Command to run the application
|
| 25 |
+
CMD ["uvicorn", "main:app", "--host", "0.0.0.0", "--port", "7860"]
|
comb.md
ADDED
|
@@ -0,0 +1,154 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
# Coherence '25 Hackathon
|
| 2 |
+
|
| 3 |
+
## 📌 Event Overview
|
| 4 |
+
**Coherence 2025** is a **24-hour offline hackathon** designed to bring together brilliant minds, fostering innovation and creativity.
|
| 5 |
+
|
| 6 |
+
📍 **Venue**: Vidyavardhini's College of Engineering and Technology, Vasai-Virar, Maharashtra
|
| 7 |
+
📅 **Final Hackathon Dates**: March 28-29, 2025
|
| 8 |
+
👥 **Team Size**: 2-4 members
|
| 9 |
+
🎯 **Domains**:
|
| 10 |
+
- **Web/App Development**: Build responsive websites and cross-platform mobile apps.
|
| 11 |
+
- **Blockchain**: Develop decentralized solutions and blockchain applications.
|
| 12 |
+
- **AI/ML**: Solve complex problems using artificial intelligence and machine learning.
|
| 13 |
+
|
| 14 |
+
---
|
| 15 |
+
|
| 16 |
+
## 🛠️ Hackathon Structure
|
| 17 |
+
|
| 18 |
+
### 🔹 Initial Judging Round (Free Entry)
|
| 19 |
+
- Teams will be **evaluated** based on a **submitted PPT and demo video**.
|
| 20 |
+
- **Submission Deadline**: March 16, 2025, 11:59 PM (Late submissions will not be considered).
|
| 21 |
+
- **No registration fee** for this round.
|
| 22 |
+
|
| 23 |
+
### 🔹 Grand Finale Participation Fee
|
| 24 |
+
- **₹500 per team** for teams that qualify for the Grand Finale.
|
| 25 |
+
- Payment details and deadlines will be shared with shortlisted teams.
|
| 26 |
+
|
| 27 |
+
### 🔹 Problem Statements
|
| 28 |
+
- **Different** problem statements for **selection round** and **Grand Finale**.
|
| 29 |
+
- The **final round problem statement** will be released **on March 25, 2025**.
|
| 30 |
+
|
| 31 |
+
### 🔹 Final Code Submission
|
| 32 |
+
- Teams must submit a **GitHub repository link** with **proper documentation**.
|
| 33 |
+
- Submission must include:
|
| 34 |
+
- ✅ **Source Code**
|
| 35 |
+
- ✅ **Demo Video**
|
| 36 |
+
- ✅ **PPT Presentation**
|
| 37 |
+
|
| 38 |
+
### 🔹 Original Work Only
|
| 39 |
+
- All projects **must be built from scratch** during the hackathon.
|
| 40 |
+
- **No pre-existing code or plagiarism** allowed. Violations will lead to **disqualification**.
|
| 41 |
+
|
| 42 |
+
### 🔹 Team Conduct
|
| 43 |
+
- No external assistance except from assigned mentors.
|
| 44 |
+
- Maintain **professional conduct** at all times.
|
| 45 |
+
|
| 46 |
+
---
|
| 47 |
+
|
| 48 |
+
## 📊 Judging Criteria
|
| 49 |
+
- **Innovation & Creativity** – Uniqueness of the solution.
|
| 50 |
+
- **Technical Implementation** – Code quality and feasibility.
|
| 51 |
+
- **Impact & Use Case** – Practicality and real-world application.
|
| 52 |
+
- **Presentation & Demo** – Clarity, execution, and engagement.
|
| 53 |
+
|
| 54 |
+
### 🔹 Final Decision
|
| 55 |
+
- The **judges' decision is final** and binding. **No appeals** will be entertained.
|
| 56 |
+
|
| 57 |
+
---
|
| 58 |
+
|
| 59 |
+
## 📅 Stages and Timelines
|
| 60 |
+
|
| 61 |
+
### **1️⃣ Submission Round (via Unstop)**
|
| 62 |
+
📅 **March 6 - March 16, 2025**
|
| 63 |
+
- Teams must choose a **problem statement**.
|
| 64 |
+
- **Submission requirements**:
|
| 65 |
+
- PPT
|
| 66 |
+
- **2-3 min video** explaining the solution.
|
| 67 |
+
- Video should cover **methodology, concepts, tech stack** and be uploaded to **YouTube/Google Drive** with a shareable link.
|
| 68 |
+
|
| 69 |
+
⏳ **Start**: March 6, 2025, 09:35 AM IST
|
| 70 |
+
⏳ **End**: March 16, 2025, 11:59 PM IST
|
| 71 |
+
|
| 72 |
+
### **2️⃣ Grand Finale (24-Hour Hackathon)**
|
| 73 |
+
📅 **March 28-29, 2025**
|
| 74 |
+
|
| 75 |
+
#### 🏆 **Day 1 – March 28**
|
| 76 |
+
- **12:00 PM**: Reporting time and registration.
|
| 77 |
+
- **1:00 PM**: Inauguration Ceremony + Problem statement release.
|
| 78 |
+
- **2:00 PM**: Coding begins.
|
| 79 |
+
- **4:30 PM**: Mentoring Round 1.
|
| 80 |
+
- **5:00 PM**: Evening snacks.
|
| 81 |
+
- **8:00 PM**: Mentoring Round 2.
|
| 82 |
+
- **9:00 PM**: Dinner break.
|
| 83 |
+
- **12:00 AM (Midnight)**: Midnight snack.
|
| 84 |
+
|
| 85 |
+
#### 🏆 **Day 2 – March 29**
|
| 86 |
+
- **8:00 AM**: Breakfast.
|
| 87 |
+
- **12:00 PM**: Lunch.
|
| 88 |
+
- **2:00 PM**: Coding ends.
|
| 89 |
+
- **3:00 PM**: Final presentations.
|
| 90 |
+
- **5:00 PM**: Results announcement + Prize distribution.
|
| 91 |
+
- **6:00 PM**: Event concludes.
|
| 92 |
+
|
| 93 |
+
---
|
| 94 |
+
|
| 95 |
+
## 🏆 Prizes Up for Grabs!
|
| 96 |
+
🥇 **Winner**: ₹15,000 + Internship Opportunity + Certificate + Goodies
|
| 97 |
+
🥈 **1st Runner-up**: ₹7,500 + Internship Opportunity + Certificate + Goodies
|
| 98 |
+
|
| 99 |
+
---
|
| 100 |
+
|
| 101 |
+
## ❓ Frequently Asked Questions
|
| 102 |
+
|
| 103 |
+
🔹 **How do I register?**
|
| 104 |
+
Register via **[Unstop](https://unstop.com/o/flano7B?lb=VKuEY8zM&utm_medium=Share&utm_source=shortUrl)**.
|
| 105 |
+
|
| 106 |
+
🔹 **What is the allowed team size?**
|
| 107 |
+
**2-4 members** per team.
|
| 108 |
+
|
| 109 |
+
🔹 **What is the registration cost?**
|
| 110 |
+
₹500 per team (Grand Finale only).
|
| 111 |
+
|
| 112 |
+
🔹 **When will the problem statements be released?**
|
| 113 |
+
Final problem statements will be released on **March 25, 2025**.
|
| 114 |
+
|
| 115 |
+
🔹 **Are travel expenses covered?**
|
| 116 |
+
No, participants must cover their **own travel expenses**.
|
| 117 |
+
|
| 118 |
+
🔹 **Is this an online or offline event?**
|
| 119 |
+
Coherence 2025 is **fully offline**.
|
| 120 |
+
|
| 121 |
+
🔹 **Can I participate as an individual?**
|
| 122 |
+
No, **team participation is required** (minimum 2 members).
|
| 123 |
+
|
| 124 |
+
🔹 **Can a member be part of two teams?**
|
| 125 |
+
No, each participant can be part of **only one team**.
|
| 126 |
+
|
| 127 |
+
---
|
| 128 |
+
|
| 129 |
+
## 📢 Communication & Updates
|
| 130 |
+
📲 **Join our official WhatsApp group** for updates: **[Join Here](https://chat.whatsapp.com/KsUFdyRNAiqLSJukLPQIg2)**.
|
| 131 |
+
|
| 132 |
+
---
|
| 133 |
+
|
| 134 |
+
## 📍 Event Venue
|
| 135 |
+
📍 **Vidyavardhini's College of Engineering and Technology**
|
| 136 |
+
K.T. Marg, Vartak College Campus, Vasai Road, Vasai-Virar, Maharashtra 401202
|
| 137 |
+
|
| 138 |
+
---
|
| 139 |
+
|
| 140 |
+
## 📞 Contact Organizers
|
| 141 |
+
📧 **Email**: mlsc@vcet.edu.in
|
| 142 |
+
📞 **Paarth Baradia (Club Lead)**: +91 84519 24342
|
| 143 |
+
📞 **Vishal Mane (Associate Club Lead)**: +91 87936 18982
|
| 144 |
+
📞 **Amey Chaudhari**: +91 96534 92872
|
| 145 |
+
📞 **Shreya Wankhede**: +91 96195 08298
|
| 146 |
+
📞 **Shagun Upadhyay**: +91 96193 42859
|
| 147 |
+
|
| 148 |
+
---
|
| 149 |
+
|
| 150 |
+
## 🔥 Summary
|
| 151 |
+
Coherence 2025 is a **24-hour offline hackathon** that brings together developers, designers, and innovators to push boundaries in **Web/App Development, Blockchain, and AI/ML**. It provides a platform to **build, learn, and compete** with exciting **prizes and internship opportunities**!
|
| 152 |
+
|
| 153 |
+
🚀 **Get ready to innovate, code, and win!**
|
| 154 |
+
|
comb.txt
ADDED
|
@@ -0,0 +1,155 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
All that you need to know about the event Coherence '25
|
| 2 |
+
Hackathon Rules – Coherence ‘25 - A 24 hr Offline Hackathon
|
| 3 |
+
Initial Judging Round (Free Entry):
|
| 4 |
+
|
| 5 |
+
Teams will first be evaluated based on their submitted PPT and demo video.
|
| 6 |
+
Submission Deadline: March 16, 2025, 11:59 PM. Late submissions will not be considered.
|
| 7 |
+
No registration fee for this round.
|
| 8 |
+
|
| 9 |
+
Grand Finale Participation Fee:
|
| 10 |
+
Teams that qualify for the Grand Finale (24-hour hackathon) will be required to pay a participation fee of ₹500 per team.
|
| 11 |
+
Payment details and deadlines will be shared with the shortlisted teams.
|
| 12 |
+
|
| 13 |
+
Problem Statements:
|
| 14 |
+
The problem statements for the selection round and the Grand Finale will be different.
|
| 15 |
+
The problem statement for the final round will be declared to the shortlisted teams on March 25, 2025.
|
| 16 |
+
|
| 17 |
+
Final Code Submission:
|
| 18 |
+
Teams must submit their GitHub repository link with properly documented code.
|
| 19 |
+
Submission must include: Source Code, Demo Video, and PPT Presentation.
|
| 20 |
+
|
| 21 |
+
Original Work Only:
|
| 22 |
+
All projects must be built from scratch during the hackathon.
|
| 23 |
+
No pre-existing code or plagiarism allowed—violations will lead to disqualification.
|
| 24 |
+
|
| 25 |
+
Team Conduct:
|
| 26 |
+
No external assistance outside of assigned mentors.
|
| 27 |
+
Professional conduct must be maintained at all times.
|
| 28 |
+
Judging Criteria:
|
| 29 |
+
|
| 30 |
+
Innovation and Creativity – Uniqueness of the solution.
|
| 31 |
+
Technical Implementation – Code quality and feasibility.
|
| 32 |
+
Impact and Use Case – Practicality and real-world application.
|
| 33 |
+
Presentation and Demo – Clarity, execution, and engagement.
|
| 34 |
+
|
| 35 |
+
Final Decision:
|
| 36 |
+
The judges' decision is final and binding. No appeals will be entertained.
|
| 37 |
+
|
| 38 |
+
Communication & Updates:
|
| 39 |
+
All participating teams must join the official WhatsApp group for important updates: Join Here (https://chat.whatsapp.com/KsUFdyRNAiqLSJukLPQIg2)
|
| 40 |
+
|
| 41 |
+
---*---*---*---*---*---
|
| 42 |
+
Contact the organisers
|
| 43 |
+
Paarth Baradia - Club Lead
|
| 44 |
+
paarth.psb@gmail.com
|
| 45 |
+
+918451924342
|
| 46 |
+
|
| 47 |
+
Vishal Mane - Associate Club Lead
|
| 48 |
+
vishalmane0611@gmail.com
|
| 49 |
+
+918793618982
|
| 50 |
+
---*---*---*---*---*---
|
| 51 |
+
|
| 52 |
+
Stages and Timelines:
|
| 53 |
+
1. Submission Round (via Unstop)
|
| 54 |
+
16 Mar 25
|
| 55 |
+
Teams must choose one problem statement from the given options. Submissions require a PPT and a 2-3 minute video explaining the solution. The video should clearly present the methodology, concepts, and tech stack used, along with a detailed explanation of the project. Teams must screen-record their PPT while explaining the solution. The video should be uploaded to YouTube or Google Drive, with a shareable link provided for evaluation.
|
| 56 |
+
Start: 06 Mar 25, 09:35 AM IST
|
| 57 |
+
End: 16 Mar 25, 11:59 PM IST
|
| 58 |
+
|
| 59 |
+
2. Final Round
|
| 60 |
+
28 Mar 25
|
| 61 |
+
Grand Finale -- 24-Hour Hackathon Timeline: --
|
| 62 |
+
|
| 63 |
+
Day 1 - 28th March:
|
| 64 |
+
12:00 PM: Reporting time and registration.
|
| 65 |
+
1:00 PM: Inauguration Ceremony.
|
| 66 |
+
Overview of the event and release of problem statements.
|
| 67 |
+
2:00 PM: Coding begins.
|
| 68 |
+
4:30 PM: Mentoring Round 1 starts.
|
| 69 |
+
5:00 PM: Evening snacks.
|
| 70 |
+
8:00 PM: Mentoring Round 2 starts.
|
| 71 |
+
9:00 PM: Dinner break.
|
| 72 |
+
12:00 AM (Midnight): Midnight snack.
|
| 73 |
+
|
| 74 |
+
Day 2 - 29th March:
|
| 75 |
+
8:00 AM: Breakfast.
|
| 76 |
+
12:00 PM: Lunch.
|
| 77 |
+
2:00 PM: Coding ends.
|
| 78 |
+
3:00 PM: Final presentations.
|
| 79 |
+
5:00 PM: Results announcement and distribution of prizes.
|
| 80 |
+
6:00 PM: Event concludes and dispersal.
|
| 81 |
+
|
| 82 |
+
---*---*---*---*---*---
|
| 83 |
+
About the event: Coherence 2025
|
| 84 |
+
Welcome to Coherence 2025, where innovation knows no bounds! In the heart of our 24-hour hackathon, we unite brilliant minds, fueling a symphony of creativity. Join us on a relentless quest to redefine possibilities and amplify the pulse of tech brilliance!
|
| 85 |
+
---*---*---*---*---*---
|
| 86 |
+
Domains are
|
| 87 |
+
1. Web/App Development: Craft responsive websites and cross-platform mobile apps with the latest technologies.
|
| 88 |
+
2. Blockchain: Empower decentralized solutions and building blockchain applications for the future.
|
| 89 |
+
3. AI/ML: Explore artificial intelligence and machine learning to solve complex problems.
|
| 90 |
+
---*---*---*---*---*---
|
| 91 |
+
|
| 92 |
+
General Guidelines
|
| 93 |
+
All participants are requested to get their identities verified beforehand at the Registration desks.
|
| 94 |
+
Problem Statements will be released on the day of hackathon i.e on 28rd March.
|
| 95 |
+
Each team should comprise a minimum of 2 and a maximum of 4 members, including the team leader. Team members can be from different colleges.
|
| 96 |
+
Participant should be enrolled in a full-time undergraduate degree.
|
| 97 |
+
Teams will be shortlisted based on Round 1.
|
| 98 |
+
The hackathon format includes 24 hours of coding. After that, teams may present their solutions to the judges.
|
| 99 |
+
Results of this round will be announced after all presentations are reviewed by the judges.
|
| 100 |
+
The participating teams must select any one problem statement to work on and should develop a viable software solution for the same.
|
| 101 |
+
Teams can freely use available servers or their own servers for developing and presenting their product.
|
| 102 |
+
---*---*---*---*---*---
|
| 103 |
+
Prizes up for grabs!
|
| 104 |
+
Winner
|
| 105 |
+
₹ 15,000 + Certificate +
|
| 106 |
+
Internship Opportunity + Goodies
|
| 107 |
+
1st Runner-up
|
| 108 |
+
₹ 7,500 + Certificate +
|
| 109 |
+
Internship Opportunity
|
| 110 |
+
+ Goodies
|
| 111 |
+
---*---*---*---*---*---
|
| 112 |
+
Frequently Asked Questions
|
| 113 |
+
How do I register for the hackathon?
|
| 114 |
+
You can register by visiting our registration page (https://unstop.com/o/flano7B?lb=VKuEY8zM&utm_medium=Share&utm_source=shortUrl
|
| 115 |
+
) and following the instructions.
|
| 116 |
+
|
| 117 |
+
What is the allowed Team size?
|
| 118 |
+
1-4 Members in a single team
|
| 119 |
+
|
| 120 |
+
What is the registration cost?
|
| 121 |
+
Only ₹500 per team.
|
| 122 |
+
|
| 123 |
+
When will the problem statements be released?
|
| 124 |
+
All the problem statements will be released a day before the event.
|
| 125 |
+
|
| 126 |
+
Are travel expenses included too?
|
| 127 |
+
No, the participants are responsible for covering their travel expenses.
|
| 128 |
+
|
| 129 |
+
Is it an Online or an Offline Hackathon?
|
| 130 |
+
Coherence 25 is being hosted Offline only.
|
| 131 |
+
|
| 132 |
+
What are the eligibility criteria?
|
| 133 |
+
The hackathon is open to all participants.
|
| 134 |
+
|
| 135 |
+
Can I participate as an individual or do I need a team?
|
| 136 |
+
Team participation is required. Individual participation is not allowed.
|
| 137 |
+
|
| 138 |
+
Can a member be a part of two teams?
|
| 139 |
+
No, every member should be part of a single team.
|
| 140 |
+
---*---*---*---*---*---
|
| 141 |
+
Reach Us at Location Venue
|
| 142 |
+
Vidyavardhini's College of Engineering and Technology, K.T. Marg, Vartak College Campus, Vasai Road, Vasai-Virar, Maharashtra 401202
|
| 143 |
+
---*---*---*---*---*---
|
| 144 |
+
For Enquiries Contact:
|
| 145 |
+
Amey Chaudhari: +91 96534 92872
|
| 146 |
+
Shreya Wankkhede: +91 96195 08298
|
| 147 |
+
Shagun Upadhyay: +91 96193 42859
|
| 148 |
+
Email: mlsc@vcet.edu.in
|
| 149 |
+
|
| 150 |
+
---*---*---*---*---*---
|
| 151 |
+
What is the event about (Coherence 2025)?
|
| 152 |
+
Coherence 2025 is a 24-hour offline hackathon where innovation knows no bounds. It unites brilliant minds, fueling a symphony of creativity on a relentless quest to redefine possibilities and amplify the pulse of tech brilliance.
|
| 153 |
+
|
| 154 |
+
Where is Coherence 2025 being held?
|
| 155 |
+
Coherence 2025 is being held at Vidyavardhini's College of Engineering and Technology, K.T. Marg, Vartak College Campus, Vasai Road, Vasai-Virar, Maharashtra 401202.
|
data_1.txt
ADDED
|
@@ -0,0 +1,80 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
All that you need to know about the event Coherence '25
|
| 2 |
+
Hackathon Rules – Coherence ‘25 - A 24 hr Offline Hackathon
|
| 3 |
+
Initial Judging Round (Free Entry):
|
| 4 |
+
|
| 5 |
+
Teams will first be evaluated based on their submitted PPT and demo video.
|
| 6 |
+
Submission Deadline: March 16, 2025, 11:59 PM. Late submissions will not be considered.
|
| 7 |
+
No registration fee for this round.
|
| 8 |
+
|
| 9 |
+
Grand Finale Participation Fee:
|
| 10 |
+
Teams that qualify for the Grand Finale (24-hour hackathon) will be required to pay a participation fee of ₹500 per team.
|
| 11 |
+
Payment details and deadlines will be shared with the shortlisted teams.
|
| 12 |
+
|
| 13 |
+
Problem Statements:
|
| 14 |
+
The problem statements for the selection round and the Grand Finale will be different.
|
| 15 |
+
The problem statement for the final round will be declared to the shortlisted teams on March 25, 2025.
|
| 16 |
+
|
| 17 |
+
Final Code Submission:
|
| 18 |
+
Teams must submit their GitHub repository link with properly documented code.
|
| 19 |
+
Submission must include: Source Code, Demo Video, and PPT Presentation.
|
| 20 |
+
|
| 21 |
+
Original Work Only:
|
| 22 |
+
All projects must be built from scratch during the hackathon.
|
| 23 |
+
No pre-existing code or plagiarism allowed—violations will lead to disqualification.
|
| 24 |
+
|
| 25 |
+
Team Conduct:
|
| 26 |
+
No external assistance outside of assigned mentors.
|
| 27 |
+
Professional conduct must be maintained at all times.
|
| 28 |
+
Judging Criteria:
|
| 29 |
+
|
| 30 |
+
Innovation and Creativity – Uniqueness of the solution.
|
| 31 |
+
Technical Implementation – Code quality and feasibility.
|
| 32 |
+
Impact and Use Case – Practicality and real-world application.
|
| 33 |
+
Presentation and Demo – Clarity, execution, and engagement.
|
| 34 |
+
|
| 35 |
+
Final Decision:
|
| 36 |
+
The judges' decision is final and binding. No appeals will be entertained.
|
| 37 |
+
|
| 38 |
+
Communication & Updates:
|
| 39 |
+
All participating teams must join the official WhatsApp group for important updates: Join Here (https://chat.whatsapp.com/KsUFdyRNAiqLSJukLPQIg2)
|
| 40 |
+
|
| 41 |
+
---*---*---*---*---*---
|
| 42 |
+
Contact the organisers
|
| 43 |
+
Paarth Baradia - Club Lead
|
| 44 |
+
paarth.psb@gmail.com
|
| 45 |
+
+918451924342
|
| 46 |
+
|
| 47 |
+
Vishal Mane - Associate Club Lead
|
| 48 |
+
vishalmane0611@gmail.com
|
| 49 |
+
+918793618982
|
| 50 |
+
---*---*---*---*---*---
|
| 51 |
+
|
| 52 |
+
Stages and Timelines:
|
| 53 |
+
1. Submission Round (via Unstop)
|
| 54 |
+
16 Mar 25
|
| 55 |
+
Teams must choose one problem statement from the given options. Submissions require a PPT and a 2-3 minute video explaining the solution. The video should clearly present the methodology, concepts, and tech stack used, along with a detailed explanation of the project. Teams must screen-record their PPT while explaining the solution. The video should be uploaded to YouTube or Google Drive, with a shareable link provided for evaluation.
|
| 56 |
+
Start: 06 Mar 25, 09:35 AM IST
|
| 57 |
+
End: 16 Mar 25, 11:59 PM IST
|
| 58 |
+
|
| 59 |
+
2. Final Round
|
| 60 |
+
28 Mar 25
|
| 61 |
+
Grand Finale -- 24-Hour Hackathon Timeline: --
|
| 62 |
+
|
| 63 |
+
Day 1 - 28th March:
|
| 64 |
+
12:00 PM: Reporting time and registration.
|
| 65 |
+
1:00 PM: Inauguration Ceremony.
|
| 66 |
+
Overview of the event and release of problem statements.
|
| 67 |
+
2:00 PM: Coding begins.
|
| 68 |
+
4:30 PM: Mentoring Round 1 starts.
|
| 69 |
+
5:00 PM: Evening snacks.
|
| 70 |
+
8:00 PM: Mentoring Round 2 starts.
|
| 71 |
+
9:00 PM: Dinner break.
|
| 72 |
+
12:00 AM (Midnight): Midnight snack.
|
| 73 |
+
|
| 74 |
+
Day 2 - 29th March:
|
| 75 |
+
8:00 AM: Breakfast.
|
| 76 |
+
12:00 PM: Lunch.
|
| 77 |
+
2:00 PM: Coding ends.
|
| 78 |
+
3:00 PM: Final presentations.
|
| 79 |
+
5:00 PM: Results announcement and distribution of prizes.
|
| 80 |
+
6:00 PM: Event concludes and dispersal.
|
data_2.txt
ADDED
|
@@ -0,0 +1,68 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
About Coherence 2025
|
| 2 |
+
Welcome to Coherence 2025, where innovation knows no bounds! In the heart of our 24-hour hackathon, we unite brilliant minds, fueling a symphony of creativity. Join us on a relentless quest to redefine possibilities and amplify the pulse of tech brilliance!
|
| 3 |
+
---*---*---*---*---*---
|
| 4 |
+
Domains are
|
| 5 |
+
1. Web/App Development: Craft responsive websites and cross-platform mobile apps with the latest technologies.
|
| 6 |
+
2. Blockchain: Empower decentralized solutions and building blockchain applications for the future.
|
| 7 |
+
3. AI/ML: Explore artificial intelligence and machine learning to solve complex problems.
|
| 8 |
+
---*---*---*---*---*---
|
| 9 |
+
|
| 10 |
+
General Guidelines
|
| 11 |
+
All participants are requested to get their identities verified beforehand at the Registration desks.
|
| 12 |
+
Problem Statements will be released on the day of hackathon i.e on 28rd March.
|
| 13 |
+
Each team should comprise a minimum of 2 and a maximum of 4 members, including the team leader. Team members can be from different colleges.
|
| 14 |
+
Participant should be enrolled in a full-time undergraduate degree.
|
| 15 |
+
Teams will be shortlisted based on Round 1.
|
| 16 |
+
The hackathon format includes 24 hours of coding. After that, teams may present their solutions to the judges.
|
| 17 |
+
Results of this round will be announced after all presentations are reviewed by the judges.
|
| 18 |
+
The participating teams must select any one problem statement to work on and should develop a viable software solution for the same.
|
| 19 |
+
Teams can freely use available servers or their own servers for developing and presenting their product.
|
| 20 |
+
---*---*---*---*---*---
|
| 21 |
+
Prizes up for grabs!
|
| 22 |
+
Winner
|
| 23 |
+
₹ 15,000 + Certificate +
|
| 24 |
+
Internship Opportunity + Goodies
|
| 25 |
+
1st Runner-up
|
| 26 |
+
₹ 7,500 + Certificate +
|
| 27 |
+
Internship Opportunity
|
| 28 |
+
+ Goodies
|
| 29 |
+
---*---*---*---*---*---
|
| 30 |
+
Frequently Asked Questions
|
| 31 |
+
How do I register for the hackathon?
|
| 32 |
+
You can register by visiting our registration page (https://unstop.com/o/flano7B?lb=VKuEY8zM&utm_medium=Share&utm_source=shortUrl
|
| 33 |
+
) and following the instructions.
|
| 34 |
+
|
| 35 |
+
What is the allowed Team size?
|
| 36 |
+
1-4 Members in a single team
|
| 37 |
+
|
| 38 |
+
What is the registration cost?
|
| 39 |
+
Only ₹500 per team.
|
| 40 |
+
|
| 41 |
+
When will the problem statements be released?
|
| 42 |
+
All the problem statements will be released a day before the event.
|
| 43 |
+
|
| 44 |
+
Are travel expenses included too?
|
| 45 |
+
No, the participants are responsible for covering their travel expenses.
|
| 46 |
+
|
| 47 |
+
Is it an Online or an Offline Hackathon?
|
| 48 |
+
Coherence 25 is being hosted Offline only.
|
| 49 |
+
|
| 50 |
+
What are the eligibility criteria?
|
| 51 |
+
The hackathon is open to all participants.
|
| 52 |
+
|
| 53 |
+
Can I participate as an individual or do I need a team?
|
| 54 |
+
Team participation is required. Individual participation is not allowed.
|
| 55 |
+
|
| 56 |
+
Can a member be a part of two teams?
|
| 57 |
+
No, every member should be part of a single team.
|
| 58 |
+
---*---*---*---*---*---
|
| 59 |
+
Reach Us at Location/Venue
|
| 60 |
+
Vidyavardhini's College of Engineering and Technology
|
| 61 |
+
K.T. Marg, Vartak College Campus, Vasai Road,
|
| 62 |
+
Vasai-Virar, Maharashtra 401202
|
| 63 |
+
---*---*---*---*---*---
|
| 64 |
+
For Enquiries Contact:
|
| 65 |
+
Amey Chaudhari: +91 96534 92872
|
| 66 |
+
Shreya Wankkhede: +91 96195 08298
|
| 67 |
+
Shagun Upadhyay: +91 96193 42859
|
| 68 |
+
Email: mlsc@vcet.edu.in
|
data_3.txt
ADDED
|
@@ -0,0 +1,33 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
-- Registration Process: --
|
| 2 |
+
|
| 3 |
+
6th March: Registration goes live on Unstop.
|
| 4 |
+
16th March (11:59 PM): Unstop registration deadline.
|
| 5 |
+
20th - 21st March: Shortlisted teams announcement.
|
| 6 |
+
28th - 29th March: Offline Hackathon event dates.
|
| 7 |
+
|
| 8 |
+
|
| 9 |
+
-- 24-Hour Hackathon Timeline: --
|
| 10 |
+
|
| 11 |
+
Day 1 - 28th March:
|
| 12 |
+
12:00 PM: Reporting time and registration.
|
| 13 |
+
1:00 PM: Inauguration Ceremony.
|
| 14 |
+
Overview of the event and release of problem statements.
|
| 15 |
+
2:00 PM: Coding begins.
|
| 16 |
+
4:30 PM: Mentoring Round 1 starts.
|
| 17 |
+
5:00 PM: Evening snacks.
|
| 18 |
+
8:00 PM: Mentoring Round 2 starts.
|
| 19 |
+
9:00 PM: Dinner break.
|
| 20 |
+
12:00 AM (Midnight): Midnight snack.
|
| 21 |
+
|
| 22 |
+
Day 2 - 29th March:
|
| 23 |
+
8:00 AM: Breakfast.
|
| 24 |
+
12:00 PM: Lunch.
|
| 25 |
+
2:00 PM: Coding ends.
|
| 26 |
+
3:00 PM: Final presentations.
|
| 27 |
+
5:00 PM: Results announcement and distribution of prizes.
|
| 28 |
+
6:00 PM: Event concludes and dispersal.
|
| 29 |
+
|
| 30 |
+
|
| 31 |
+
|
| 32 |
+
|
| 33 |
+
|
data_4.txt
ADDED
|
@@ -0,0 +1,94 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
Q1: What is Coherence 2025?
|
| 2 |
+
A1: Coherence 2025 is a 24-hour offline hackathon where innovation knows no bounds. It unites brilliant minds, fueling a symphony of creativity on a relentless quest to redefine possibilities and amplify the pulse of tech brilliance.
|
| 3 |
+
|
| 4 |
+
Q2: Where is Coherence 2025 being held?
|
| 5 |
+
A2: Coherence 2025 is being held at Vidyavardhini's College of Engineering and Technology, K.T. Marg, Vartak College Campus, Vasai Road, Vasai-Virar, Maharashtra 401202.
|
| 6 |
+
|
| 7 |
+
Q3: What are the domains for the hackathon?
|
| 8 |
+
A3: The hackathon covers three domains:
|
| 9 |
+
|
| 10 |
+
Web/App Development – Craft responsive websites and cross-platform mobile apps with the latest technologies.
|
| 11 |
+
Blockchain – Empower decentralized solutions and build blockchain applications for the future.
|
| 12 |
+
AI/ML – Explore artificial intelligence and machine learning to solve complex problems.
|
| 13 |
+
Q4: What is the schedule for Day 1 (March 28)?
|
| 14 |
+
A4:
|
| 15 |
+
|
| 16 |
+
12:00 PM – Reporting and Registration
|
| 17 |
+
2:00 PM – Opening Ceremony
|
| 18 |
+
3:00 PM – Hacking Begins
|
| 19 |
+
8:00 PM – Dinner Break
|
| 20 |
+
Q5: What is the schedule for Day 2 (March 29)?
|
| 21 |
+
A5:
|
| 22 |
+
|
| 23 |
+
8:00 AM – Breakfast
|
| 24 |
+
10:00 AM – Hacking Resumes
|
| 25 |
+
12:00 PM – Judging Begins
|
| 26 |
+
2:00 PM – Closing Ceremony
|
| 27 |
+
Q6: Who can participate in Coherence 2025?
|
| 28 |
+
A6: Coherence 2025 is open to undergraduate and postgraduate students from all backgrounds.
|
| 29 |
+
|
| 30 |
+
Q7: How many members are allowed in a team?
|
| 31 |
+
A7: Teams can consist of 2 to 4 members.
|
| 32 |
+
|
| 33 |
+
Q8: How do I register for the hackathon?
|
| 34 |
+
A8: You can register on the official Coherence 2025 website by filling out the registration form.
|
| 35 |
+
|
| 36 |
+
Q9: Is there a registration fee?
|
| 37 |
+
A9: No, participation in Coherence 2025 is completely free.
|
| 38 |
+
|
| 39 |
+
Q10: What is the selection process for the hackathon?
|
| 40 |
+
A10: Teams will be selected based on the innovation, feasibility, and impact of their project ideas.
|
| 41 |
+
|
| 42 |
+
Q11: Can I participate alone?
|
| 43 |
+
A11: No, you need to form a team of at least two members.
|
| 44 |
+
|
| 45 |
+
Q12: Will food and accommodation be provided?
|
| 46 |
+
A12: Yes, food and basic accommodation will be provided for all participants.
|
| 47 |
+
|
| 48 |
+
Q13: What should I bring to the hackathon?
|
| 49 |
+
A13: Bring your laptop, charger, valid ID, and any other hardware you may need.
|
| 50 |
+
|
| 51 |
+
Q14: Are there any prizes for winners?
|
| 52 |
+
A14: Yes, winners will receive exciting cash prizes, trophies, and other rewards.
|
| 53 |
+
|
| 54 |
+
Q15: How will the projects be judged?
|
| 55 |
+
A15: Projects will be judged based on innovation, technical execution, and presentation.
|
| 56 |
+
|
| 57 |
+
Q16: Will there be any mentorship during the hackathon?
|
| 58 |
+
A16: Yes, experienced mentors will be available to provide guidance and support.
|
| 59 |
+
|
| 60 |
+
Q17: Can we use third-party libraries and APIs?
|
| 61 |
+
A17: Yes, you are allowed to use third-party libraries and APIs as long as they are open-source or properly licensed.
|
| 62 |
+
|
| 63 |
+
Q18: Can I work on a pre-existing project?
|
| 64 |
+
A18: No, all projects must be started from scratch at the hackathon.
|
| 65 |
+
|
| 66 |
+
Q19: Can I submit multiple projects?
|
| 67 |
+
A19: No, each team is allowed to submit only one project.
|
| 68 |
+
|
| 69 |
+
Q20: Is internet access available at the venue?
|
| 70 |
+
A20: Yes, high-speed internet will be available for all participants.
|
| 71 |
+
|
| 72 |
+
Q21: Are there any hardware restrictions?
|
| 73 |
+
A21: No specific restrictions, but teams are encouraged to use hardware provided by the organizers when available.
|
| 74 |
+
|
| 75 |
+
Q22: Can I switch teams after registration?
|
| 76 |
+
A22: No, team compositions are final after registration closes.
|
| 77 |
+
|
| 78 |
+
Q23: What happens if a team member drops out?
|
| 79 |
+
A23: The team can continue with the remaining members if the minimum requirement of 2 members is maintained.
|
| 80 |
+
|
| 81 |
+
Q24: How can I contact the organizers for support?
|
| 82 |
+
A24: You can reach out to the support team via the official website or through the provided email.
|
| 83 |
+
|
| 84 |
+
Q25: Are there any rules for coding languages?
|
| 85 |
+
A25: No, you can use any programming language you prefer.
|
| 86 |
+
|
| 87 |
+
Q26: What if my project requires special hardware?
|
| 88 |
+
A26: You need to inform the organizers in advance if you require special hardware.
|
| 89 |
+
|
| 90 |
+
Q27: Are participants allowed to sleep at the venue?
|
| 91 |
+
A27: Yes, sleeping arrangements will be provided.
|
| 92 |
+
|
| 93 |
+
Q28: Will there be networking opportunities with industry professionals?
|
| 94 |
+
A28: Yes, there will be dedicated networking sessions with industry experts and professionals.
|
main.py
ADDED
|
@@ -0,0 +1,124 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
import os
|
| 2 |
+
import getpass
|
| 3 |
+
from groq import Groq
|
| 4 |
+
from langchain.chat_models import init_chat_model
|
| 5 |
+
from langchain_core.messages import HumanMessage, SystemMessage
|
| 6 |
+
from langchain_core.vectorstores import InMemoryVectorStore
|
| 7 |
+
from langchain_core.documents import Document
|
| 8 |
+
from langchain_text_splitters import RecursiveCharacterTextSplitter
|
| 9 |
+
from langchain_community.document_loaders import UnstructuredMarkdownLoader
|
| 10 |
+
from langchain_community.embeddings import HuggingFaceInferenceAPIEmbeddings
|
| 11 |
+
from langchain import hub
|
| 12 |
+
from langgraph.graph import START, StateGraph
|
| 13 |
+
from pydantic.main import BaseModel
|
| 14 |
+
from typing_extensions import List, TypedDict
|
| 15 |
+
|
| 16 |
+
from langchain_cohere import CohereEmbeddings
|
| 17 |
+
|
| 18 |
+
import re
|
| 19 |
+
from dotenv import load_dotenv
|
| 20 |
+
from fastapi import FastAPI
|
| 21 |
+
from fastapi.middleware.cors import CORSMiddleware
|
| 22 |
+
from fastapi.responses import JSONResponse
|
| 23 |
+
|
| 24 |
+
'''
|
| 25 |
+
if not os.environ.get("GROQ_API_KEY"):
|
| 26 |
+
os.environ["GROQ_API_KEY"] = getpass.getpass("Enter API key for Groq: ")
|
| 27 |
+
'''
|
| 28 |
+
|
| 29 |
+
load_dotenv()
|
| 30 |
+
|
| 31 |
+
print(f"GROQ_API_KEY: {os.getenv('GROQ_API_KEY')}")
|
| 32 |
+
print(f"HUGGING_FACE_API_KEY: {os.getenv('HUGGING_FACE_API_KEY')}")
|
| 33 |
+
|
| 34 |
+
|
| 35 |
+
llm = init_chat_model("deepseek-r1-distill-llama-70b", model_provider="groq", api_key=os.getenv("GROQ_API_KEY"))
|
| 36 |
+
'''
|
| 37 |
+
embeddings = HuggingFaceInferenceAPIEmbeddings(
|
| 38 |
+
api_key = os.getenv('HUGGING_FACE_API_KEY'),
|
| 39 |
+
model_name="sentence-transformers/all-MiniLM-L6-v2"
|
| 40 |
+
)
|
| 41 |
+
|
| 42 |
+
embeddings = HuggingFaceInferenceAPIEmbeddings(
|
| 43 |
+
api_key=os.getenv('HUGGING_FACE_API_KEY'), model_name="sentence-transformers/all-MiniLM-L6-v2"
|
| 44 |
+
)'''
|
| 45 |
+
|
| 46 |
+
embeddings = CohereEmbeddings(
|
| 47 |
+
cohere_api_key=os.getenv('COHERE'),
|
| 48 |
+
model="embed-english-v3.0", # Added this line
|
| 49 |
+
user_agent="langchain-cohere-embeddings"
|
| 50 |
+
)
|
| 51 |
+
|
| 52 |
+
vector_store = InMemoryVectorStore(embedding=embeddings)
|
| 53 |
+
|
| 54 |
+
# Data - 1 and Data - 2
|
| 55 |
+
data_1 = open(r'data_1.txt', 'r').read()
|
| 56 |
+
data_2 = open(r'data_2.txt', 'r').read()
|
| 57 |
+
data_3 = open(r'data_3.txt', 'r').read()
|
| 58 |
+
data_4 = open(r'data_4.txt', 'r').read()
|
| 59 |
+
|
| 60 |
+
comb = open(r'comb.txt', 'r').read()
|
| 61 |
+
|
| 62 |
+
md_loader = UnstructuredMarkdownLoader('comb.md')
|
| 63 |
+
|
| 64 |
+
text_splitter = RecursiveCharacterTextSplitter(chunk_size=500, chunk_overlap=100)
|
| 65 |
+
# all_splits = text_splitter.split_text(data_1 + "\n\n" + data_2 + "\n\n" + data_3 + "\n\n" + data_4)
|
| 66 |
+
# all_splits = text_splitter.split_text(comb)
|
| 67 |
+
all_splits = text_splitter.split_documents(md_loader.load())
|
| 68 |
+
|
| 69 |
+
# docs = [Document(page_content=text) for text in all_splits]
|
| 70 |
+
docs = [Document(page_content=text.page_content, metadata=text.metadata) for text in all_splits]
|
| 71 |
+
_ = vector_store.add_documents(documents=docs)
|
| 72 |
+
|
| 73 |
+
|
| 74 |
+
prompt = hub.pull("rlm/rag-prompt")
|
| 75 |
+
|
| 76 |
+
class State(TypedDict):
|
| 77 |
+
question: str
|
| 78 |
+
context: List[Document]
|
| 79 |
+
answer: str
|
| 80 |
+
|
| 81 |
+
def retrieve(state: State):
|
| 82 |
+
retrieved_docs = vector_store.similarity_search(state["question"])
|
| 83 |
+
return {"context": retrieved_docs}
|
| 84 |
+
|
| 85 |
+
def generate(state: State):
|
| 86 |
+
docs_content = "\n\n".join(doc.page_content for doc in state["context"])
|
| 87 |
+
messages = prompt.invoke({"question": state["question"], "context": docs_content})
|
| 88 |
+
response = llm.invoke(messages)
|
| 89 |
+
return {"answer": response.content}
|
| 90 |
+
|
| 91 |
+
graph_builder = StateGraph(State).add_sequence([retrieve, generate])
|
| 92 |
+
graph_builder.add_edge(START, "retrieve")
|
| 93 |
+
graph = graph_builder.compile()
|
| 94 |
+
'''
|
| 95 |
+
response = graph.invoke({"question": "Who should i contact for help ?"})
|
| 96 |
+
print(response["answer"])
|
| 97 |
+
'''
|
| 98 |
+
|
| 99 |
+
app = FastAPI()
|
| 100 |
+
|
| 101 |
+
origins = ["*"]
|
| 102 |
+
|
| 103 |
+
app.add_middleware(
|
| 104 |
+
CORSMiddleware,
|
| 105 |
+
allow_origins=origins,
|
| 106 |
+
allow_credentials=True,
|
| 107 |
+
allow_methods=["GET", "POST", "PUT", "DELETE"],
|
| 108 |
+
allow_headers=["*"],
|
| 109 |
+
)
|
| 110 |
+
|
| 111 |
+
@app.get("/ping")
|
| 112 |
+
async def ping():
|
| 113 |
+
return "Pong!"
|
| 114 |
+
|
| 115 |
+
class Query(BaseModel):
|
| 116 |
+
question: str
|
| 117 |
+
|
| 118 |
+
@app.get("/chat")
|
| 119 |
+
async def chat(request: Query):
|
| 120 |
+
response = graph.invoke({"question": request.question})
|
| 121 |
+
response = response["answer"]
|
| 122 |
+
response = re.sub(r'<think>.*?</think>', '', response, flags=re.DOTALL)
|
| 123 |
+
# response = response[4:]
|
| 124 |
+
return {"response": response}
|
requirements.txt
ADDED
|
@@ -0,0 +1,121 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
aiofiles==24.1.0
|
| 2 |
+
aiohappyeyeballs==2.5.0
|
| 3 |
+
aiohttp==3.11.13
|
| 4 |
+
aiosignal==1.3.2
|
| 5 |
+
annotated-types==0.7.0
|
| 6 |
+
anyio==4.8.0
|
| 7 |
+
attrs==25.1.0
|
| 8 |
+
backoff==2.2.1
|
| 9 |
+
beautifulsoup4==4.13.3
|
| 10 |
+
certifi==2025.1.31
|
| 11 |
+
cffi==1.17.1
|
| 12 |
+
chardet==5.2.0
|
| 13 |
+
charset-normalizer==3.4.1
|
| 14 |
+
click==8.1.8
|
| 15 |
+
cohere==5.14.0
|
| 16 |
+
cryptography==44.0.2
|
| 17 |
+
dataclasses-json==0.6.7
|
| 18 |
+
distro==1.9.0
|
| 19 |
+
dnspython==2.7.0
|
| 20 |
+
email_validator==2.2.0
|
| 21 |
+
emoji==2.14.1
|
| 22 |
+
eval_type_backport==0.2.2
|
| 23 |
+
fastapi==0.115.11
|
| 24 |
+
fastapi-cli==0.0.7
|
| 25 |
+
fastavro==1.10.0
|
| 26 |
+
filelock==3.18.0
|
| 27 |
+
filetype==1.2.0
|
| 28 |
+
frozenlist==1.5.0
|
| 29 |
+
fsspec==2025.3.0
|
| 30 |
+
greenlet==3.1.1
|
| 31 |
+
groq==0.18.0
|
| 32 |
+
h11==0.14.0
|
| 33 |
+
html5lib==1.1
|
| 34 |
+
httpcore==1.0.7
|
| 35 |
+
httptools==0.6.4
|
| 36 |
+
httpx==0.28.1
|
| 37 |
+
httpx-sse==0.4.0
|
| 38 |
+
huggingface-hub==0.29.3
|
| 39 |
+
idna==3.10
|
| 40 |
+
Jinja2==3.1.6
|
| 41 |
+
jiter==0.9.0
|
| 42 |
+
joblib==1.4.2
|
| 43 |
+
jsonpatch==1.33
|
| 44 |
+
jsonpointer==3.0.0
|
| 45 |
+
langchain==0.3.20
|
| 46 |
+
langchain-cohere==0.4.3
|
| 47 |
+
langchain-community==0.3.19
|
| 48 |
+
langchain-core==0.3.43
|
| 49 |
+
langchain-groq==0.2.5
|
| 50 |
+
langchain-openai==0.3.8
|
| 51 |
+
langchain-text-splitters==0.3.6
|
| 52 |
+
langdetect==1.0.9
|
| 53 |
+
langgraph==0.3.5
|
| 54 |
+
langgraph-checkpoint==2.0.18
|
| 55 |
+
langgraph-prebuilt==0.1.2
|
| 56 |
+
langgraph-sdk==0.1.55
|
| 57 |
+
langsmith==0.3.13
|
| 58 |
+
lxml==5.3.1
|
| 59 |
+
Markdown==3.7
|
| 60 |
+
markdown-it-py==3.0.0
|
| 61 |
+
MarkupSafe==3.0.2
|
| 62 |
+
marshmallow==3.26.1
|
| 63 |
+
mdurl==0.1.2
|
| 64 |
+
msgpack==1.1.0
|
| 65 |
+
multidict==6.1.0
|
| 66 |
+
mypy-extensions==1.0.0
|
| 67 |
+
nest-asyncio==1.6.0
|
| 68 |
+
nltk==3.9.1
|
| 69 |
+
numpy==1.26.4
|
| 70 |
+
olefile==0.47
|
| 71 |
+
openai==1.65.5
|
| 72 |
+
orjson==3.10.15
|
| 73 |
+
packaging==24.2
|
| 74 |
+
propcache==0.3.0
|
| 75 |
+
psutil==7.0.0
|
| 76 |
+
pycparser==2.22
|
| 77 |
+
pydantic==2.10.6
|
| 78 |
+
pydantic-settings==2.8.1
|
| 79 |
+
pydantic_core==2.27.2
|
| 80 |
+
Pygments==2.19.1
|
| 81 |
+
pypdf==5.3.1
|
| 82 |
+
python-dateutil==2.9.0.post0
|
| 83 |
+
python-dotenv==1.0.1
|
| 84 |
+
python-iso639==2025.2.18
|
| 85 |
+
python-magic==0.4.27
|
| 86 |
+
python-multipart==0.0.20
|
| 87 |
+
python-oxmsg==0.0.2
|
| 88 |
+
PyYAML==6.0.2
|
| 89 |
+
RapidFuzz==3.12.2
|
| 90 |
+
regex==2024.11.6
|
| 91 |
+
requests==2.32.3
|
| 92 |
+
requests-toolbelt==1.0.0
|
| 93 |
+
rich==13.9.4
|
| 94 |
+
rich-toolkit==0.13.2
|
| 95 |
+
shellingham==1.5.4
|
| 96 |
+
six==1.17.0
|
| 97 |
+
sniffio==1.3.1
|
| 98 |
+
soupsieve==2.6
|
| 99 |
+
SQLAlchemy==2.0.38
|
| 100 |
+
starlette==0.46.1
|
| 101 |
+
tenacity==9.0.0
|
| 102 |
+
tiktoken==0.9.0
|
| 103 |
+
tokenizers==0.21.1
|
| 104 |
+
tqdm==4.67.1
|
| 105 |
+
typer==0.15.2
|
| 106 |
+
types-PyYAML==6.0.12.20241230
|
| 107 |
+
types-requests==2.32.0.20250306
|
| 108 |
+
typing-inspect==0.9.0
|
| 109 |
+
typing-inspection==0.4.0
|
| 110 |
+
typing_extensions==4.12.2
|
| 111 |
+
unstructured==0.17.0
|
| 112 |
+
unstructured-client==0.31.1
|
| 113 |
+
urllib3==2.3.0
|
| 114 |
+
uvicorn==0.34.0
|
| 115 |
+
uvloop==0.21.0
|
| 116 |
+
watchfiles==1.0.4
|
| 117 |
+
webencodings==0.5.1
|
| 118 |
+
websockets==15.0.1
|
| 119 |
+
wrapt==1.17.2
|
| 120 |
+
yarl==1.18.3
|
| 121 |
+
zstandard==0.23.0
|