Update README.md
Browse files
README.md
CHANGED
@@ -1,8 +1,7 @@
|
|
1 |
---
|
2 |
license: gpl-3.0
|
3 |
---
|
4 |
-
|
5 |
-
# Potato and Tomato Disease Classification Web Application
|
6 |
---
|
7 |
|
8 |
## Overview
|
@@ -36,32 +35,32 @@ Dropout layers to prevent overfitting.
|
|
36 |
|
37 |
2. Tomato Disease Classification Model
|
38 |
- Classes:
|
39 |
-
Tomato Early Blight
|
40 |
-
Tomato Late Blight
|
41 |
-
Tomato Healthy
|
42 |
- Techniques Used:
|
43 |
-
Similar architecture to the potato model with appropriate adjustments for tomato disease classification.
|
44 |
-
Batch normalization, max pooling, and dropout layers are also used here.
|
45 |
|
46 |
## Web Application
|
47 |
- Backend
|
48 |
The backend of the application is powered by Flask. It loads the trained models, handles image uploads, processes images, and returns predictions to the frontend.
|
49 |
|
50 |
-
|
51 |
-
|
52 |
-
|
53 |
|
54 |
- Frontend
|
55 |
The frontend is developed using HTML and CSS, with Bootstrap for responsive design.
|
56 |
|
57 |
-
|
58 |
-
|
59 |
-
|
60 |
|
61 |
## Outcome
|
62 |
- Performance
|
63 |
-
|
64 |
-
|
65 |
- Benefits
|
66 |
-
|
67 |
-
|
|
|
1 |
---
|
2 |
license: gpl-3.0
|
3 |
---
|
4 |
+
# Potato and Tomato Disease Classification Web Application
|
|
|
5 |
---
|
6 |
|
7 |
## Overview
|
|
|
35 |
|
36 |
2. Tomato Disease Classification Model
|
37 |
- Classes:
|
38 |
+
Tomato Early Blight
|
39 |
+
Tomato Late Blight
|
40 |
+
Tomato Healthy
|
41 |
- Techniques Used:
|
42 |
+
Similar architecture to the potato model with appropriate adjustments for tomato disease classification.
|
43 |
+
Batch normalization, max pooling, and dropout layers are also used here.
|
44 |
|
45 |
## Web Application
|
46 |
- Backend
|
47 |
The backend of the application is powered by Flask. It loads the trained models, handles image uploads, processes images, and returns predictions to the frontend.
|
48 |
|
49 |
+
- Model Loading: Both models (potato and tomato) are loaded at the start of the application to minimize latency during prediction.
|
50 |
+
- Prediction Logic: Depending on the selected plant type (potato or tomato), the corresponding model is used to predict the disease class.
|
51 |
+
- Dynamic Background: The background image on the frontend changes based on the selected plant type, enhancing user experience.
|
52 |
|
53 |
- Frontend
|
54 |
The frontend is developed using HTML and CSS, with Bootstrap for responsive design.
|
55 |
|
56 |
+
- File Upload Interface: Users can upload an image of a leaf.
|
57 |
+
- Prediction Display: After processing, the application displays the predicted disease class and the associated probability.
|
58 |
+
- Dynamic Background: The background image changes depending on whether the user is predicting for potato or tomato.
|
59 |
|
60 |
## Outcome
|
61 |
- Performance
|
62 |
+
- Potato Model: Achieved an accuracy of 95% on the validation set, with strong performance in classifying Early Blight, Late Blight, and Healthy leaves.
|
63 |
+
- Tomato Model: Achieved an accuracy of 93% on the validation set, effectively distinguishing between Early Blight, Late Blight, and Healthy leaves.
|
64 |
- Benefits
|
65 |
+
- Disease Detection: Helps farmers and agriculturists detect diseases in potato and tomato plants early, potentially preventing crop losses.
|
66 |
+
- User-Friendly Interface: The web application provides a simple interface for non-technical users to diagnose plant diseases.
|