Files Affected:
fire_detection.py
gear_detection.py
r_zone.py
📌 Current Model Info
- Using
ultralytics.YOLO (default checkpoint).
- Confidence threshold:
0.85 (fire & gear), 0.45 (people).
- No optimization applied.
🐞 Problem
The current YOLO model is too heavy for real-time inference on edge devices (e.g., CPU-only machines, Raspberry Pi, Jetson Nano).
- On CPU: FPS drops below 10 FPS, making it unsuitable for live monitoring.
- High memory usage.
✅ Steps to Reproduce
- Run any detection script (
fire_detection.py, gear_detection.py, r_zone.py) on CPU with a live webcam feed.
- Measure FPS → performance is very low (<10).
💡 Suggested Improvement
-
Replace the current YOLO checkpoint with a lighter variant such as:
- YOLOv8n (nano)
- YOLOv9-tiny
- YOLO-Nano / MobileNet-based detectors
-
Add a config option so users can choose model size dynamically (n, s, m, l).
📊 Expected Outcome
- Improved FPS (15–30+) on CPU.
- Lower memory usage.
- Contributors can experiment with different models without modifying code.
Files Affected:
fire_detection.pygear_detection.pyr_zone.py📌 Current Model Info
ultralytics.YOLO(default checkpoint).0.85(fire & gear),0.45(people).🐞 Problem
The current YOLO model is too heavy for real-time inference on edge devices (e.g., CPU-only machines, Raspberry Pi, Jetson Nano).
✅ Steps to Reproduce
fire_detection.py,gear_detection.py,r_zone.py) on CPU with a live webcam feed.💡 Suggested Improvement
Replace the current YOLO checkpoint with a lighter variant such as:
Add a config option so users can choose model size dynamically (
n,s,m,l).📊 Expected Outcome