Difference between revisions of "BusyBear"
Jump to navigation
Jump to search
Line 23: | Line 23: | ||
==Challenges== | ==Challenges== | ||
− | * | + | * Limited experience with working with WiFi receivers or anything to do with MAC Addresses |
+ | * Limited knowledge of Python and Raspberry Pi | ||
+ | * Connecting our data with a database, AWS, and a website | ||
==Gantt Chart== | ==Gantt Chart== |
Revision as of 23:33, 30 January 2019
Contents
Overview
It always seems like an impossible task to find an open table to work or a quick line for food across the WashU campus. BusyBear's goal is to create a database that is accessible to WashU students. The goal of our project is to measure busyness in high traffic areas on campus like Lopata Hall
Links
Team Members
Thomas Emerson
Tom Goon
Allison Todd
David Tekien, TA
Jim Feher, Instructor
Objectives
- Setup a Raspberry Pi and be able to control it through a virtual machine and/or Putty
- Learn and be able to code in Python as related to the Pi
- Implement detection of devices through WiFi (MAC Addresses)
- Be able to monitor busyness fairly accurately by filtering detected devices
- Compare busyness at different times of day and between buildings
- Host a website displaying useful and relevant data through Amazon Web Services (AWS)
- Create a database to store data and use through AWS
Challenges
- Limited experience with working with WiFi receivers or anything to do with MAC Addresses
- Limited knowledge of Python and Raspberry Pi
- Connecting our data with a database, AWS, and a website
Gantt Chart
Budget
Item | Description | Cost | Link |
---|---|---|---|
Example | Example | Example | |
Example | Example | Example | |
Total Cost | $ |
Resources
Past Projects: