Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fire detection project #12879

Closed
1 task done
Cho-Hong-Seok opened this issue Apr 3, 2024 · 2 comments
Closed
1 task done

Fire detection project #12879

Cho-Hong-Seok opened this issue Apr 3, 2024 · 2 comments
Labels
question Further information is requested Stale

Comments

@Cho-Hong-Seok
Copy link

Search before asking

Question

@glenn-jocher
I am working on a project to detect fire using YOLOv5&YOLOv8 models. The project model I would like to implement is a program that detects the initial fire with a lightweight model like YOLOv8s, and then uses a more accurate model like YOLOv8x to track -> segment and finally alarm as the fire and smoke grows. I was wondering if anyone could advise me on any libraries, frameworks, equipment, etc. to implement this?

The first picture below is a crude representation of the sort of process I'd like to implement.
The second picture is an image captured from roboflow youtube and it shows an implementation using the gradio library to switch to bbox->segmentation when a boundary is crossed using the YOLO-World + EfficientSAM model. My goal is to implement something similar to this for the fire object.

Thanks as always!

Additional

YOLOv8 project
YOLO-World + SAM

@Cho-Hong-Seok Cho-Hong-Seok added the question Further information is requested label Apr 3, 2024
@glenn-jocher
Copy link
Member

@Cho-Hong-Seok hello! 🚀 Your fire detection project sounds quite innovative, and using YOLOv5 and YOLOv8 for initial detection and then tracking to segmentation and alarm as the fire grows is a smart approach. For implementing this multi-stage process, you would want to consider a few aspects:

  1. Libraries/Frameworks: For integration and switching between models (like YOLOv8s for initial detection and YOLOv8x for detailed tracking), consider using a deep learning framework like PyTorch which YOLO is based on. It offers flexibility in model management and deployment. For segmentation, you might look into segmentation models available in PyTorch or libraries like Detectron2 which are compatible with YOLO outputs.

  2. Equipment: Depending on the deployment environment (real-time detection, offline processing, etc.), ensure you have the necessary computational resources. GPUs are highly recommended for model training and inference, especially for the more accurate (thus computationally intensive) models like YOLOv8x.

  3. Application logic: For the application logic that switches between detection and tracking/segmentation based on certain criteria, you may need to implement custom code that monitors detection confidence, object size, or other metrics that signal when to transition from one model to another.

Remember that any usage of Ultralytics models, architectures, or code in your project at any stage requires an Ultralytics Enterprise License or fully open-sourcing your entire project under AGPL-3.0.

I hope these suggestions are helpful! 😊 For further details and documentation on Ultralytics YOLOv5, please visit the Ultralytics Docs. Best of luck with your fire detection project!

Copy link
Contributor

github-actions bot commented May 4, 2024

👋 Hello there! We wanted to give you a friendly reminder that this issue has not had any recent activity and may be closed soon, but don't worry - you can always reopen it if needed. If you still have any questions or concerns, please feel free to let us know how we can help.

For additional resources and information, please see the links below:

Feel free to inform us of any other issues you discover or feature requests that come to mind in the future. Pull Requests (PRs) are also always welcomed!

Thank you for your contributions to YOLO 🚀 and Vision AI ⭐

@github-actions github-actions bot added the Stale label May 4, 2024
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale May 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested Stale
Projects
None yet
Development

No branches or pull requests

2 participants