Early detection and management of crop diseases and pest infestations

The receipts 🧾

Every red flag on this statement, in full. These are the four places it bites.

1. Exhibit A

   This is the most reproduced student machine learning project there is, so a leaf classifier alone is indistinguishable from dozens of prior submissions

2. It gets worse

   Models trained on PlantVillage's uniform laboratory backgrounds degrade severely on real field photographs with mixed foliage and variable light, and an agriculture judge will hand you a real photo to test it

3. Still reading?

   Misdiagnosis leads to wrong pesticide application, which the description itself names as a harm, so confidence handling and referral to an expert are requirements rather than extras

4. And the finisher

   The description asks for detection, forecasting, mapping, validation and advisory, and teams routinely build only the classifier

The damage report 📉

Every score this statement earned, and what each one actually costs you.

• Feasibility

  5/5

  Actually buildable, which on this slate is rarer than it sounds. Do not squander it on scope.

  PlantVillage and several successor datasets provide tens of thousands of labelled crop disease images, weather APIs are free, and the whole stack is ordinary application work — this is among the most data-rich problems in the entire set.

• Innovation scope

  2/5

  Nothing here is new. Your only edge is execution — and execution is also everyone else's only edge.

  Image-based crop disease classification is one of the most solved and most reproduced applications in machine learning, and the description prescribes the surrounding features, leaving room only in the risk forecasting and the feedback loop.

• Clarity

  3/5

  Clear enough to start, vague enough to drift. Write the scope down and stop reinterpreting it weekly.

  The expected capabilities are listed clearly but no crops, diseases or region are specified, so you must choose the scope and no acceptance bar is given for diagnostic accuracy.

• Acceptance potential

  2/5

  The numbers do not like you. Bring something the numbers cannot see.

  Crop disease detection from leaf images is possibly the single most cloned student ML project in existence — a judge will have seen it many times, PlantVillage-trained models notoriously collapse on real field photographs, and the differentiating features are exactly the ones teams skip.

• Effort

  Heavy

  Heavy. Somebody on this team is not sleeping in week three. Pick who, on purpose.

  The classifier is quick given public data, but the risk forecasting, hotspot aggregation, expert validation loop and multilingual advisory layer together make a substantial application.

• Demo-ability

  Easy

  Easy to demo — and so is everyone else's. Working is the floor here, not the achievement.

  Photographing a leaf and receiving an instant diagnosis is a tactile, self-explanatory demo that works with a real infected plant brought into the room.

• Data

  None supplied

  No dataset comes with this one, so every accuracy figure you quote is a number about labels you invented.

  Nothing is provided with the statement. You are sourcing, cleaning and labelling it yourself, and that work is invisible in the demo but very visible in the questions.

The demo they will have already seen 🪞

Somewhere around 480–500 teams are heading here, and the description is doing the choosing for most of them. They will read the same brief, reach the same architecture, and build a version of the same demo you are planning. Being correct is the floor. If your five minutes could be swapped with the team before you and nobody in the room would notice, you have not picked badly — you have built predictably, which costs exactly the same and hurts more.

What survives 🛡️

The ground worth standing on when the questions start.

• Public labelled disease image datasets are enormous, so the classifier is working within hours and your time goes to the differentiating features
• Weather-driven risk forecasting using degree-day and humidity thresholds is established agronomy and is the part almost nobody builds
• The expert validation loop turning extension officer confirmations into training data is a genuinely good idea that addresses the field-accuracy problem head-on