Changes

Jump to: navigation, search

Peapod

578 bytes added, 13:25, 10 April 2016
Software
* Forward the collected data at regular intervales (30 minutes?) via a WiFi connection to a server
The AP signal strength information is sufficient to determine the physical location of the device during the conference; this may be aided by additional access points added at strategic locations. Rather than perform the location determination on the Peapod (consuming energy), this analysis will be done on the server side. Various projects report that 2-3m accuracy is possible, but in our case, room-level accuracy is sufficient.
This information will enable:
* Immediate feedback on the presentations and workshops (via the button-presses), correlated with location and time information to determine which presentation/workshop is being rated
In addition, it is proposed that the raw collected data be made available in real-time to the attendees, and that a contest be held for the most interesting use of that data by the end of the conference(such as: mapping attendee travels; heat-mapping sessions; doing fine-grained user location to determine who interacted with who at the conference; determining how many people left in the middle of each session; calculating the number of trips to non-session areas such as the break room, Tim Horton's, the registration desk, or washrooms; mapping when people gave feedback on a presentation; calculating tardiness; figuring out which presentations ran overtime; etc...)
== Peapod after FSOSS ==

Navigation menu