Posted on

Team Status Report for 2/27

This week, we focused on the refinement of our design so that we can get prepared for the design review presentation for next next week. As we focused on each of our parts, we hope to talk about our ideas on Monday/Wednesday to put them all together.

Hiroko worked on her hardware component, coming up with a block diagram and shopping list which helped us go over the scope of the project and organize what we really need.

Sarah has downloaded OpenCV and started to go through some tutorials and learn basic algorithms such as edge and color detection.  She will continue learning algorithms and OpenCV functionalities next week to get more specific ideas for the project.

Kanon has implemented OAuth to web application and will work more on the design and web development next week. She will also look into AWS database installation and pricing.

Next week, we will start ordering the parts we need and ask TA/Professor about borrowing Raspberry PI boards so that we can get started on building up hardware systems.

Posted on

Kanon’s Status Report for 2/27

This week, I mainly focused on the basic design of our web application. Currently, I’m thinking of having a single page layout of the website as it would be easier for the user to navigate through. Moreover, because the users will be using this web application on their phone, this single page layout will look like a normal iPhone/Android App. Therefore, there is no need to develop an actual smartphone application.

I heard that implementing Google OAuth with Django is a bit of hassle, so I also decided to implement Google OAuth login this week. It did turn out to be much harder than I expected it to be. There are many ways to implement Google OAuth but some information was outdated, so I had to go through all of them and gather knowledge to come up with the most optimal way to implement this API. Eventually I was able to make it work, but I did not have enough time to look into how to register with Google OAuth.

Lastly, I have set up AWS related accounts and got credits from Tamal. I have read through the basic documentation of DynamoDB and figured out it will cost every time when we try to write/read data to it. The rough calculation gave me $1 per month, which definitely is feasible under our budget. However, I will need to look into EC2 costing so that the total operation cost on AWS will be under $50.

Next week, I will start implementing CSS designs and refurbish registration +  login/logout functionality as it currently only supports Google OAuth login. The users should be able to register with email while also  being able to register with a Google account. I will further need to look into how the Django database is storing Google emails because we might use this information to send notifications/alerts to users.

Posted on

Team Status Report for 2/20

The significant risks that we face at this point in our project is to make the scope too large or too small, and to misjudge the requirements that we determine are necessary for our greenhouse to be effective. In order to manage these risks, we are doing as much research as we can, and making sure that we communicate with each other so that we are all on the same page about the envisionment of the final product. Also, we are planning to discuss and reflect the feedback that we get from our project proposal presentation to ensure that our scope, requirements, and overall future plans are on track.
This week, we came up with a more concrete design of our system with more quantitative requirements and testing metrics to add to the project proposal presentation. We also created a broad schedule to split up the work between each team member and into smaller tasks.