Difference between revisions of "BusyBear"

From ESE205 Wiki
Jump to navigation Jump to search
Line 35: Line 35:
! Item  !! Description !! Cost !! Link
! Item  !! Description !! Cost !! Link
| Example || Example || Example ||
| AWS || Website Hosting || Depends || https://aws.amazon.com/pricing/?nc2=h_ql_pr
| Example || Example || Example ||
| Total Cost||  || $ ||
| Total Cost||  || $ ||

Revision as of 23:34, 30 January 2019


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


[View Project Log]

Team Members

Thomas Emerson
Tom Goon
Allison Todd
David Tekien, TA
Jim Feher, Instructor


  • 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


  • 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

Link to No Where


Item Description Cost Link
AWS Website Hosting Depends https://aws.amazon.com/pricing/?nc2=h_ql_pr
Total Cost $


Past Projects: