Models in Potato Pest Management (LateBlight)

1. Models in Potato Pest Management (LateBlight) Client: Professor William Fry Sharmin Azam Christopher Brickley Nathan Cormier Ledet Kinfu Cathryn Lao Ashwath Murthy Abhishek Sharma

2. Purpose • Give an update on what we have done so far • Run a demo of the latest build

3. Deployment Diagram

4. Component Diagram

5. Activity Diagram (for Full System)

6. Component: Profile Management

7. Update on Requirements… • Create user profile • Simplified form for the farmer to enter Farm Latitude, Farm Longitude, Sensor Height, Sensor Location and User Name. • Validate if the input is complete and in the right format. User will be asked to modify incorrect data.

8. Update on Requirements • Save validated data • New file is created and saved with the User Name. • Overwrites files with the same User Name. • Retrieve existing profile • Enter the name (User Name) of already saved profile to load it into the program.

9. Activity Diagram

10. Component: Treatment

11. Update on Requirements… • Input treatment information • Simplified form for the farmer to enter Emergence Date, Date when healthy plants were last seen, Date when late blight was first seen, Potato cultivar, Initial severity and Fungicide dose. • Validate if the input is in the correct range and format. User will be asked to modify incorrect data • Default Initial severity value is set to 0.8

12. Update on Requirements • Saving and processing the treatment data to make it ready to run the simulation. • Save and load the input treatment data. • Populate values related to the chosen potato cultivar: Variety, Lesion Growth Rate, Sporulation Rate, Latent Period

13. Activity Diagram

14. Component: Get Weather Forecast

15. Update on Requirements… • Download the weather xml file from National Weather Service. • A C# application that fetches the xml file is called within Polux. • Read the xml file • Rainfall data is given only for the first 72 hours. We have decided to populate the missing rainfall data (next 96 hours) by randomly selecting rainfall data from the given forecast and the farmer provided historical data.

16. Update on Requirements • Process the xml file • In order to simplify simulation concerns, we have also decided to make sure that the forecasted data ends with a FULL day of forecasts. • Output tab-delimited forecast.txt • This component concludes with an exporting of the forecast into a tab-delimited file which is then handled by the 'combine weather data' component.

17. Activity Diagram

18. Component: Combine Weather Data

19. Update on Requirements… • User loads historic data into Polux by importing the text file. • Data is checked if it’s in the right format. User will be asked to modify if there are errors. • Save validated data to a new file in tab-delimited format. • Instead of creating a new file we overwrite the file with new validated data.

20. Update on Requirements… • If there is missing data for the first day of the forecast, the farmer is asked to supply the information in 3-hour intervals. • Polux will calculate the daily average temperature (ºF), total daily rainfall(in), number of humid hours, and average temperature (ºF) when the weather was humid. • We have rainfall data in the forecast only for first 72 hours. So we have to extend to 168 hours using rainfall data historical data and forecast data for first 72 hours.

21. Update on Requirements… • The user will be presented with a screen asking for the required length of the simulation in days. This option allows the user to extend the provided weather data as far as the user requires. • The user can extend the simulation 90 days beyond the last forecast day. • The program will extend the weather data by the number of days specified by randomly selecting daily weather from the historical and forecasted data until it reaches the required number of days of the season.

22. Update on Requirements • The user can then provide overall adjustments to the weather (historical and forecasted) data for: mean daily temperature (ºF), total daily rainfall (inches) per day, total daily humid hours, and mean daily humid temperature via four sliding adjustments or text input fields. • We have added 3 different sliders for temperature, humid hours and humid temperatures respectively where users can change all the values in a column by moving respective sliders. The users can also change values in any particular cell by clicking and typing in the grid. • After the user is satisfied with the data the combined weather file is saved for simulation.

23. Activity Diagram (Combine Weather Data)

24. Activity Diagram (Combine Weather Data)

25. Activity Diagram (Combine Weather Data)

26. Notes on the Current Build • Not yet fully functional • Running the simulation and displaying the results • Acquiring weather data (problem on some systems/networks) • About the interface • Simple linear design • Few fields/buttons per page • Still needs some ‘polish’ before final version

27. Demo

28. Future Plans • Combine Weather Data • Add range validation for temperature, humid hours, humid temperature and rainfall • Complete • Usability testing with users familiar with the late blight disease but not with Polux. • System modifications after gathering enough feedback from the users and the client. • System testing • Documentation (User and Technical) • Code cleaning