From PublicWiki
Revision as of 21:53, 9 November 2006 by Bdferris (talk | contribs) (Tools)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

University of Washington Activity Recognition (UWAR) Group


Brian Ferris:

  • Currently working on Wifi localization and SLAM.
  • Using sensor board + wifi + hand annotation on iPAQ.

Julie Letchner:

  • Currently working on relational motion models (for people, indoors).
  • Using wifi (iPAQ-collected data set).

Gaetano Borriello:

  • Currently working on using personal sensors to infer activity
  • Applications in personal fitness and assistance with cognitive disorders

Henry Kautz:

  • Currently working on activity recognition for prompting and guidance
  • Goal this quarter: initial user study of indoor navigation aid

Danny Wyatt:

  • Currently working on sensing and modelling human social behavior
  • Using sensor board (mainly audio) + wifi + gps
  • Goals this quarter: detect multi-person conversations and infer number of participants, detect conversation types (eg. social vs. work)

Alan Liu:

  • Currently working on integrating IRS' Place Lab WiFi fingerprint localization into Brian's Wizard of Oz framework for the ACCESS studies
  • Goals this quarter: support user studies on indoor navigation and activity+location+GIS

Harlan Hile:

  • Working on ACCESS project, indoor navigation assistance. currently doing wizard-of-oz studies.
  • Working on ESM support for study with obesity research center. working with Jon Froehlich's ESM package from intel.
  • Python support for UWAR streams

Yaw Anokwa:

  • Working on processing MSB data on the iMote2 and providing context information to the MS SPOT watch.

Getting Started

The goal of the UWAR group is to provide a common set of tools for use in projects and research. We've broken these tools down into a set of common activities:

Data Collection

Tools for collecting raw data from sensor streams.

  • TraceWriterPrime - An iPAQ application for collecting data from the MSB, GPS, and Wifi. Can write UWAR data to disk or to a network socket. See the tutorial on usage at UWAR:Tutorial:TraceWriterPrime.

Data Processing

Tools for working with UWAR traces.


All software should reside in the UWAR CVS repository. The cvs root is out in NFS space at:


C++ projects targeted at Windows Mobile (aka iPAQ aka PocketPC aka WinCE) are typically maintained with some Microsoft Visual C++-esque tool (see UbiComp:Hacking:PocketPC). Java projects are typically Eclipse projects (see http://eclipse.org/).


  • Windows Mobile
    • TraceWriterLibraryCE - provides ability to read data from sensor hardware (MSB,Wifi,GPS,etc) for output to a UWAR:DataFormat stream [C++ DLL]
    • TraceWriterPrime - provides a UI front end to TraceWriterLibraryCE [C++ application]
    • Mobile Packages - provides a collection of pre-built packages for the iPAQ, including most of the tools mentioned here.
  • Java
    • uwar.patterns - a collection of utility classes used by other projects
    • uwar.io - provides support for reading, writing, and processing UWAR:DataFormat streams in Java
    • uwar.maps - provides mapping visualization widgets in Swing and SWT
    • uwar.jtracewriter - provides a Java wrapper around TraceWriterLibrary
    • edu.washington.cs.uwar.annotation - provides a Java application for collecting trace data with a configurable annotation tool

Java Notes:

  • To easily check out and setup the Java proejcts in Eclipse, use the CVS Repository browser. When you've browsed to the above projects, right-click on the project's module and select 'Check out as project...'. Keep the module name as the project name, as we expect projects to have specific names for inter-project dependencies.
  • In Eclipse, you may get an error concerning an unsatisfied User Library named 'swt'. SWT is a Java gui toolkit (think replacement for Swing) that builds on native OS widgets for display. Because it uses native widgets, you must select a SWT library appropriate for your OS (Win,Mac,Linux,etc). As such, we don't hardcode the reference to SWT in our projects, but instead specify a 'swt' placeholder, which you should go in and specify for your platform: Window -> Preferences -> Java -> Build Path -> User Librares, New..., Name: swt, Add your specific SWT jars (usually found in your eclipse/plugins directory. If you get an UnsatisfiedLinkError when running a program, you will need to find the swt dll file and put it in your jre/bin directory.