Project Presentation Notes

1. Project Presentation Notes • Problem Statement: • High level statement • Sub-problems • Existing solutions, drawbacks, challenges • Approach, promising new ideas (contributions) • Design rationale, comparing/contrasting alternatives and tradeoffs • Details of protocols & services • Evaluation details (as applicable) • Math analysis – simulations – implementation • Initial results and findings (if applicable)

2. Project-related note: Scanning, sensing efficiency • On monitoring of sensors (e.g., accelerometers, or others, location, bluetooth,…): • 1- continuous monitoring is wasteful and may not be needed always • 2- a constant rate of sampling may not be needed, and an adaptive/adjustable rate may be better (how to adjust and which rates/thresholds to use is a challenge and could be a design element in your project) • [check the efficient scanning mode in iTrust and the paper to see how Udayan approached it... but that's not the only way to do it] • 3- one can employ a hierarchical sampling approach, where you start with coarse grained sensing, and if/once you sense something 'potentially' interesting, then you turn on a finer (higher fidelity) sampling • 4- one can use the state of the user/patient and make use of high level constraints and domain-specific knowledge to guide the sampling to be efficient yet effective (e.g., getting location estimates without new GPS or other scanning by estimating speed, using a finite state machine for the activity of the patient,... etc.). • 5- one can employ a learning algorithm to adjust the parameter settings based on the patients feedback and or information.