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

Feature request-Cotton Disease Prediciton-Deep Learning #782

Closed
Shy029 opened this issue Nov 6, 2024 · 2 comments · Fixed by #793
Closed

Feature request-Cotton Disease Prediciton-Deep Learning #782

Shy029 opened this issue Nov 6, 2024 · 2 comments · Fixed by #793

Comments

@Shy029
Copy link
Contributor

Shy029 commented Nov 6, 2024

I propose adding a "Cotton Disease Prediction" feature to ML Nexus using transfer learning to classify diseases in cotton crops from leaf images. Leveraging pre-trained models with transfer learning, this tool will efficiently and accurately diagnose common diseases, enabling farmers to take timely action to protect their crops. By integrating this feature, ML Nexus can offer a practical, agriculture-focused solution that demonstrates the project’s adaptability and real-world impact. I am excited to contribute to this impactful feature, enhancing ML Nexus’s relevance in agricultural applications.

Please assign this to me.

@Shy029 Shy029 added the enhancement New feature or request label Nov 6, 2024
Copy link

github-actions bot commented Nov 6, 2024

Thanks for creating the issue in ML-Nexus!🎉
Before you start working on your PR, please make sure to:

  • ⭐ Star the repository if you haven't already.
  • Pull the latest changes to avoid any merge conflicts.
  • Attach before & after screenshots in your PR for clarity.
  • Include the issue number in your PR description for better tracking.
    Don't forget to follow @UppuluriKalyani – Project Admin – for more updates!
    Tag @Neilblaze,@SaiNivedh26 for assigning the issue to you.
    Happy open-source contributing!☺️

Copy link

github-actions bot commented Nov 6, 2024

Hello @Shy029! Your issue #782 has been closed. Thank you for your contribution!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants