Indoor tracking systems will be an essential part of the home of the future, enabling location-aware and individually-tailored services. However, today there are no tracking solutions that are practical for "every day" use in the home. In this paper, we introduce the Doorjamb tracking system that uses ultrasonic range finders mounted above each doorway, pointed downward to sense people as they walk through the doorway. The system differentiates people by measuring their heights, infers their walking direction using signal processing, and identifies their room locations based on the sequence of doorways through which they pass. Doorjamb provides room-level tracking without requiring any user participation, wearable devices, privacy-intrusive sensors, or high-cost sensors. We create a proof-of-concept implementation and empirically evaluate Doorjamb with experiments that include over 3000 manually-recorded doorway crossings. Results indicate that the system can perform room-level tracking with 90% accuracy on average.

Homes are rich with information about people's energy consumption, medical health, and personal or family functions. In this paper, we present our experiences deploying large-scale residential sensing systems in over 20 homes. Deploying small-scale systems in homes can be deceptively easy, but in our deployments we encountered a phase transition in which deployment effort increases dramatically as residential deployments scale up in terms of 1) the number of nodes, 2) the length of time, and 3) the number of houses. In this paper, we distill our experiences down to a set of guidelines and design principles to help future deployments avoid the potential pitfalls of large-scale sensing in homes.

Macroprogramming abstractions provide abstract distributed data structures to simplify the programming of wireless embedded networks. However, none of the current macroprogramming systems provide debugging support for application development. We have developed MDB, a GDB-like post-mortem debugger for the MacroLab macroprogramming abstraction. In this demonstration, we show how MDB enables application development and debugging at a single level of abstraction. MDB eliminates the need for a programmer to reason about low-level event traces and message passing protocols, instead allowing debugging in terms of abstract data types. We expect MDB to fill a crucial link in the development cycle as a macroprogram progresses from the drawing board to real deployment.

Creating and debugging programs for wireless embedded networks (WENs) is notoriously difficult. Macroprogramming is an emerging technology that aims to address this problem by providing high-level programming abstractions. We present MDB, the first system to support the debugging of macroprograms. MDB allows the user to set break-points and step through a macroprogram using a source-level debugging interface similar to GDB, a process we call macrodebugging. A key challenge of MDB is to step through a macroprogram in sequential order even though it executes on the network in a distributed, asynchronous manner. Besides allowing the user to view distributed state, MDB also provides the ability to search for bugs over the entire history of distributed states. Finally, MDB allows the user to make hypothetical changes to a macroprogram and to see the effect on distributed state without the need to redeploy, execute, and test the new code. We show that macrodebugging is both easy and efficient: MDB consumes few system resources and requires few user commands to find the cause of bugs. We also provide a lightweight version of MDB called MDB Lite that can be used during the deployment phase to reduce resource consumption while still eliminating the possibility of heisenbugs: changes in the manifestation of bugs caused by enabling or disabling the debugger.

We present a macroprogramming framework called MacroLab that offers a vector programming abstraction similar to Matlab for Cyber-Physical Systems (CPSs). The user writes a single program for the entire network using Matlab-like operations such as addition, find, and max. The framework executes these operations across the network in a distributed fashion, a centralized fashion, or something between the two - whichever is most efficient for the target deployment. We call this approach deployment-specific code decomposition (DSCD). MacroLab programs can be executed on mote-class hardware such as the Telos [24] motes. Our results indicate that MacroLab introduces almost no additional overhead in terms of message cost, power consumption, memory footprint, or CPU cycles over TinyOS

We demonstrate MacroLab, which is a macroprogramming framework that offers a vector programming abstraction similar to Matlab for cyber-physical systems (CPSs). The user writes a single program for an entire network using Matlab like operations such as addition, find, and max. The framework executes these operations across the network in a distributed fashion, a centralized fashion, or something between the two - whichever is most efficient for the target deployment. We call this approach deployment-specific code decomposition (DSCD). The MacroLab programming framework will facilitate the easy development of applications for CPSs by domain experts such as scientists and engineers with almost no additional overhead to the nodes in terms of message cost, power consumption, memory footprint, or CPU cycles over TinyOS programs.