Update README.md
Browse files
README.md
CHANGED
@@ -46,21 +46,21 @@ Dropout layers to prevent overfitting.
|
|
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.
|
|
|
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.
|