Project Info
Inspiration
Our inspiration came from a series of different methods to detect traffic signs, cars, and scenerios on the rode. Our main usages are BLIP, CLIP, a RoboFlow model using LISA data, and YOLO8n model for car detection models to detect scenarios, cars, and traffic signs. We also have seen the power of LLM like chatGPT, so we used this model to do so. The project name was inspired by the fact that the model would be responding to traffic related scenarios, acting like an arrogant backseat driver, (by giving advice). Hopefully it proves helpful!
What it does
Our project uses pre-trained models to extract from videos different traffic related data, building a scenario into text in which then we feed to a chatGPT api in order to determine a related question. Videos and multiple choice questions are given to us by Tesla.
How we built it
We build our project on NVIDIA VMs, for that extra compute power on the cloud and in order to run some of our models like YOLO and BLIP. We used BLIP, CLIP, a LISA based model, and YOLO8n image model in order to extract what exists and what is going on in a driving scenario. Each model extracts different things, like a description of what is going on, specific traffic signs, object detection, or object movement. We harness each model's strength, by taking a video and frame by frame (8 frames per 5 sec video approximately), and running these models on each one. Afterwards we aggregate this data per video and feed it into chatGPT's API. Additionally we give it a multiple choice question and with that data, and prompting it will make an answer. Afterwards the answer is taken an converted into a csv file, which we use to submit.
Challenges we ran into
So many dependency issues, too many installations and conflicts! Training models is time consuming! We opted to use pre-trained ones to save time, but training them ourselves would have allowed for on device models paired with NVIDIA VMs, thus faster compute.
Accomplishments we're proud of
We were able to build a VLM while making use of several models! We also learned to use new tools like chatGPT and RoboFlow APIs and NVIDIA VMs!
What we learned
We learned to use new tools like chatGPT and RoboFlow APIs and NVIDIA VMs!
What's next
We hope to put many of the models we call via API onto actual device plus tune them with more data.
Team:
Luis Arizmendi and Miggy Silva
Sources:
RoboFlow with LISA data set for detecting signs: https://universe.roboflow.com/kaggle-road-sign-dataset/lisa-bjgh5/model/2
Tesla Challenge dataset: https://www.kaggle.com/competitions/tesla-real-world-video-q-a/leaderboard
#Inspiration:
LISA: https://www.kaggle.com/datasets/mbornoe/lisa-traffic-light-dataset/data
Analysis
View
Metric
- 14
- 1
Figures cover GitHub contributors during the hackathon window. A co-authored commit counts in full for each author, so per-member totals add up to more than the whole-team figures.
Technology
- PythonIn code
1 of 1 appear in the indexed code.
AI coding agents
No AI coding agent signals were found in this repository.
Detected from committed agent config files and commit authorship. Absence of a signal is not proof an agent was unused.
Codebase size
Source size
10 KB
Source files
11
Counts recognized source files only; vendored directories, binaries and lockfiles are excluded, so this is smaller than the repository on disk.
Repository
arizmendi-luis/TreeHacks2025
4,000 files · 325.5 MB · @ df1765d
Structure
Application logic
8 files · 0%Domain rules, services and shared utilities.
Supporting
Layers are inferred from where files sit in the tree, not from reading the code. A project that names its directories unconventionally will read oddly here — open the file browser to check anything the diagram implies.
Languages
- YAML100%
Share of indexed source by file size. Binary and vendored files are excluded.
This repository has more files than are indexed here, so the diagram and browser show a partial tree. Open it on GitHub for the complete structure.
This project’s features have not been analysed yet.
Export this project's context (description, README, evidence, key source files) to chat with an AI agent elsewhere.