Challenges & Mitigation:<\/b><\/p>\n
This week, the biggest change was switching from using an API to web scraping for collecting environmental data. The API we planned to use was unreliable (down, buggy, outdated) and lacked important data. Paid backup APIs weren\u2019t an option, so we switched to scraping data from a website focused on houseplants. The challenge is that this site only covers houseplants, which may limit our scope. We\u2019ll either narrow our focus to houseplants or find another source.<\/span><\/p>\n We also switched from AWS to Replit due to the lack of AWS credits and other limitations. This change required us to adjust the web app code, which has already been done. We now need to explore different options for user notifications, such as Twilio, since we no longer have access to AWS services.<\/span><\/p>\n We\u2019re still facing challenges with getting enough plant data for the ML model. To solve this, we\u2019re collecting our own data and looking into data augmentation techniques. We\u2019re also prioritizing setting up sensors and cameras to collect data in the next few weeks.<\/span><\/p>\n <\/p>\n Progress:<\/b><\/p>\n <\/p>\n Next Steps:<\/b><\/p>\n Challenges & Mitigation: This week, the biggest change was switching from using an API to web scraping for collecting environmental data. The API we planned to use was unreliable (down, buggy, outdated) and lacked important data. Paid backup APIs weren\u2019t an option, so we switched to scraping data from a website focused on houseplants. The … <\/p>\n\n
\n