B CSV files - StatisticalReinforcementLearningLab/HeartstepsV1Code GitHub Wiki

Here we list all of the CSV files for data from the intake/exit interviews, HeartSteps, Jawbone and Google Fit. The files are loaded into data frames, which are saved in the R workspace csv.RData. These data require considerable processing before it can be reasonably analyzed, so only the analysis data frames should be used. Tables that played a role in constructing the analysis data frames are documented further on individual wiki pages, linked from the table name.

The descriptions also give limitations or complications of the data available from each file for analysis. Underlying reasons for these issues are documented on the data issues wiki page. We emphasize "available" because essentially every app-based source is subject to missingness; this topic is covered in the data issues page and the data summary.

Interviews

These CSV files are primarily exported manually from Excel spreadsheets, which are maintained by the study coordinators.

Table	Data frame	Description
HeartSteps Participant Directory	participants	User names, identifiers, intake and exit dates, and notes on study participation (e.g. study dropout, international travel, technical issues).
Survey_Intake	intake	User answers to the intake interview questions.
Survey_Exit	exit	User answers to the exit interview questions; these re-administer the activity choice index, self-efficacy for physical activity and the IPAQ. See Survey_Intake for the variable format.
TestX_AppUsageData	tracker	The exit interview also involved downloading data from an app usage tracker, which is installed on the phone at intake. This file records the time and duration of use for any application installed on the user's phone.

HeartSteps

These CSV files generally contain data captured by the HeartSteps app. Files are exported using Google App Engine tools, following the steps documented on the exporting data wiki page.

Table	Data frame	Description
EMA_Completed	complete	EMA completion status and time, but does not always reflect the data in EMA_Response; EMA_Completed thus is used only for time zone information.
EMA_Context_Engaged	engage	Context in which the user engaged with the EMA. What constitutes an engagement is not clear, but generally corresponds to interactions with the EMA questions after the initial interaction via the EMA notification.
EMA_Context_Notified	notify	Context at the time of EMA notification and administered planning/EMA questions. The latter are recorded under a race condition; we instead infer from EMA_Response, Structured_Planning_Response and Unstructured_Planning_Response.
EMA_Response	ema	Answers to each EMA question. Time stamps for each answer have no time zone.
Heartsteps_Usage_History	usage	Interaction with the 4 main pages of the HeartSteps app interface.
Momentary_Decision	decision	Context and decision result for the decision on whether or not an activity suggestion is provided.
Motivational_Message		Motivational messages the user entered into the home page of the HeartSteps app.
Response	response	Context and interaction result (thumbs up/down, snooze, timed out) of the activity suggestion notification.
Reviewed_Heartsteps_Messages	messages	Unique suggestion messages with all relevant tags. Used for post-hoc tagging, since the messages and the tags relevant to the context were not captured by HeartSteps.
Snooze_FromInApp	snooze	Times at which the user enabled snooze from the HeartSteps app (as opposed to interaction with an activity suggestion).
Structured_Planning_Response	plan	Structured planning options selected by the user.
Unstructured_Planning_Response	plan	Text the user entered when prompted to complete unstructured planning.
User_Addresses	address	Addresses for home and work, provided by the user through the HeartSteps app settings. Time stamps have no time zone.
User_Calendars	calendar	Google calendar accounts, provided by the user through the HeartSteps app settings. Data for the calendar accounts were not retrieved due to privacy issues.
User_Data		User name, identifier and time of HeartSteps account creation.
User_Decision_Times	timeslot	Time slots for suggestion and EMA notifications chosen by the user, apart from some constraints imposed by the app settings menu.
Weather_History	weather	Morning temperature, high temperature and total preciptation for each city represented in the users' GPS coordinates encounted in each day. Time stamps do not have time zone.

Physical activity tracking

These CSV files are exported from a web interface, following the steps documented on the exporting data wiki page.

Table	Data frame	Description
google_fit_data	googlefit	Cumulative step counts per bout of physical activity. What defines a "bout" is not apparent from the Google Fit API.
jawbone_step_count_data	jawbone	Cumulative step counts per minute in each bout of physical activity. Here a bout is defined differently from Google Fit, but the exact definition is similarly unclear from the Jawbone API.