|
|
The best way to learn to use ActivityStudio is to first look at the video, which gets you a rough idea about what you can do
with the environment. You can then look at the user manual. The manual is
quite preliminary and incomplete so you might want to reference the video again while using the system.
video
activity sensing
ActivityStudio allows three kinds of "sensing" approaches.
- Users' self-reporting via a web interface generated by an Activity Server. The web interface should be accessed at "http://activityservername:8080/activitydesigner/reporter", where "activityservername" is the computer name (or IP address).
- Users' self-reporting using an ESM-based activity report tool
- Automatic activity detection with real sensors
ActivityStudio allows a "sensing" component to be easily added to its runtime environment. All the sensing components talk to an Activity Server via an HTTP protocol. To add your own sensing component, you only need to send
your sensing results to an ActivityServer based on this protocol. The following example reports event participant "user" did "Walking workout" with "significant other" on a "trail" for "25" minutes.
expid=mobilesession&pid=user&when=-1&duration=25&where are you?=trail=1&who are you with?=significant other=1&action=Walking workout=1
A request contains multiple pairs of attribute/value that are separated by an '&". There are several built-in attributes that each request must have: "expid" (experimental ID), "pid" (participant ID), and "when" (the event timestamp) and "duration" (in minutes, can have decimal fractions).
When "when" is "-1", the Activity Server will calculate the starting time of the event by subtracting its local time when the event reaches the server with the reported duration. Other attributes in a request denote activity properties/values defined in a design, e.g., for property "who are you with?", the value in the example
is "significant other=1". A value itself is a valueName-probability pair.
In addition, several other built-in parameters are supported in the protocol: debug, end_time_offset, source and timezone. The value of "debug" is saved in a log file that is unique to the session and participant of an event, i.e., activitydesigner_debug_eid_pid.log in the user home
directory on the Activity Server.
The value of "end_time_offset" will be used to calculate the starting time of an event. "source" and "timezone" will directly go to the Activity Server database. All these parameters are NOT case sensitive. The Activity Server ignores undefined parameters.
|
|
