Eco Sort Ai
Our users are waste management companies, recycling facilities (MRFs), municipalities, and large businesses such as supermarkets, logistics centers, and food and beverage plants. They rely on manual sorting, which is slow, costly, and inconsistent. Workers must make repetitive visual decisions at high speed, so accuracy drops with fatigue. Mixed streams end up contaminated and recyclable material goes to landfill. Soft, deformable items such as plastic film, bags, and textiles are especially hard to handle. EcoSort AI moves sorting from manual labor to accurate, data-driven sorting. It analyzes a photo or camera feed of waste in real time, detects each item, classifies the material, shows a confidence score, and decides which bin the item goes to. Low-confidence items go to a “reject” bin for human review, so people move from repetitive picking to supervision and quality control. ReflexGrip is the robotic layer for soft objects. It adjusts grip force from feedback, so the item is held without being crushed or dropped. Better sorting gives cleaner recyclable fractions and less material sent to landfill. This can lower the carbon footprint of waste handling, because more material is recycled and less is landfilled or incinerated. We treat this as a potential environmental benefit to be measured in pilots, not a proven result.
Preliminary score
- Value for the user17.5 / 25
A specific problem and a clear outcome from solving it.
- Prototype and use of AI20.5 / 30
A working core scenario, and what AI actually contributes to the result.
- Quality testing12.5 / 20
Tests, examples of failures, and comparison with the current approach.
- Feasibility8.5 / 15
Data requirements, running costs and a clear next step.
- Originality5.0 / 10
A meaningful difference from common solutions.
What the judges wrote
- GPT-6 AstraPreliminary66/100
- Strengths
- Your documented image-to-classification-to-review workflow gives AI a meaningful role in a concrete waste-sorting task. Your README clearly separates inference from simulated robot actions and describes useful safeguards, including uncertainty rejection, operator corrections, and fail-closed object checks. Your acknowledgment of dataset leakage, label conflicts, and camera limitations shows valuable attention to reliability.
- To improve
- Publish actual evaluation results with sample counts, clean camera-session holdouts, failure examples, and accepted-item accuracy versus rejection rate, alongside a manual-sorting baseline. Reconcile the submission’s YOLO/Next.js description with the README’s MobileNetV2/Python and COCO-SSD implementation, and provide a traceable input-to-routing example. Focus the next pilot on one facility workflow, with throughput and contamination targets, measured inference latency, and per-item running costs; validate soft-grip benefits separately on hardware.
- Claude Opus 5.5Preliminary62/100
- Strengths
- Your classifier routes uncertain items to human review rather than forcing a wrong sort. That is backed by explicit rules: a confidence of at least 75%, a top-two margin of 15 points, three-frame burst agreement, and a fail-closed COCO-SSD guard that blocks non-waste objects like phones and people. Your README is unusually honest. It states that the robot, sensors and multi-object detection are simulated or manual, that thresholds are uncalibrated, and that duplicates across train/test splits may inflate results. You also back the quality work with code: a dataset audit tool, a clean-split preparation script, an evaluation script with a confusion matrix and per-class F1, and pytest/Node test suites. The operator-correction history with JSON/CSV export and the EPA WARM-based carbon estimate add practical value for an MRF workflow.
- To improve
- Your submission text and README disagree on the model: the submission says YOLO with an 'other/reject' class, while the README describes a five-class MobileNetV2 and says explicitly it is not YOLO. Align these so judges and users trust your claims. Put the actual test numbers (accuracy, macro F1, the main confusion pairs) in your written submission, and compare them with manual sorting accuracy or throughput at a real facility. The track asks for an adoption metric, so name one, such as contamination rate or picks per hour, and include rough running costs per camera or line. Finally, collect even a small held-out set of real conveyor-style or local photos, which would show whether the Kaggle-trained model transfers.
The team
Elcan Məmmədov
developer
Rauf Fəthi Qovaşin
developer
Namət Nağıyev
developer
Nərmin Əlizadə
developer
Alican MikayılovLead
developer