Data frame daily - StatisticalReinforcementLearningLab/HeartstepsV1Code GitHub Wiki
Table with one row per user-day combination (day in study)
| Variable Name | Description |
|---|---|
| user | user id |
| study.date | calendar date (for each user, should have a date for each day the user was in the study) |
| ema.utime | UTC timestamp for the EMA context (either the notification context, if available, or the context at the first engagement record). If no context is available, ema.utime is the time of intended/selected EMA notification. |
| user.index | user number counting from 1 to the number included in the analysis (38). User ID may be different. |
| intake.date | user intake date |
| intake.utime | intake datetime in UTC |
| intake.tz | |
| intake.gmtoff | |
| intake.hour | |
| intake.min | |
| intake.slot | |
| travel.start | |
| travel.end | |
| exit.date | |
| dropout.date | |
| last.date | |
| last.utime | |
| last.tz | |
| last.gmtoff | |
| last.hour | |
| last.min | |
| last.slot | |
| own.phone | |
| travel | |
| study.day | Day in study, starting from 0 |
| study.day.nogap | Day in study, starting from 0, excluding travel days |
| ema.hours | The user's selected time of EMA notification in units of hours after midnight |
| date.updated | Date when user changed EMA notification time |
| ema.tz | |
| ema.gmtoff | offset between local time and UTC |
| ltime | local datetime |
| tz | |
| gmtoff | |
| notify | Indicator of whether the context information comes from the notification record or the first engagement record. |
| context.date | |
| context.utime | |
| context.year | |
| context.mon | |
| context.yday | |
| context.mday | |
| context.wday | |
| context.hour | |
| context.min | |
| context.sec | |
| planning.today | Type of planning, populated using EMA_Context_Notified. Not the same as daily$planning. |
| recognized.activity | |
| front.end.application | |
| calendar | |
| gps.coordinate | |
| home | |
| work | |
| city | |
| location.exact | |
| location.category | |
| weather.condition | |
| temperature | |
| windspeed | |
| precipitation.chance | |
| snow | |
| ema.set.length | |
| hectic | |
| stressful | |
| typical | |
| active.cardio | |
| active.strength | |
| active.flex | |
| active.housework | |
| active.none | |
| follow | |
| down.motivate | |
| down.action | |
| down.difficult | |
| down.doable | |
| down.time | |
| down.active | |
| down.other | |
| down.msg | |
| up.motivate | |
| up.easy | |
| up.doable | |
| up.interest | |
| up.feel | |
| up.other | |
| up.msg | |
| barrier.weather | |
| barrier.busy | |
| barrier.place | |
| barrier.ill | |
| barrier.sore | |
| barrier.social | |
| barrier.traffic | |
| barrier.personal | |
| barrier.none | |
| barrier.other | |
| enabler.joined | |
| enabler.encourage | |
| enabler.weather | |
| enabler.scheduled | |
| enabler.facilities | |
| enabler.location | |
| enabler.none | |
| enabler.other | |
| energetic | |
| urge | |
| interaction.count | Populated from engage by summing interaction.count for each user-ema.date combination. Interpretation is suspect. |
| planning | Type of planning, populated using responses to planning questions. Possible values: disconnected, no_planning, structured, unstructured |
| response | Response to planning question |
| device.utime | UTC timestamp of the latest time an app was opened before ema.utime |
| start.utime | identical to device.utime |
| device.since | Hours between ema.utime and most recent phone usage (device.utime) |
| respond | Indicator of whether the user responded to at least one EMA/planning question. |
| view | TRUE if the user responded to at least one EMA/planning question or there is a non-missing interaction.count. |
| connect | Equal to (daily$notify OR daily$view OR daily$respond). FALSE indicates that there are 0 EMA_Context_Notified records, 0 planning responses, 0 EMA_Response records, and 0 EMA_Context_Engaged records |
| jbsteps | Number of jawbone steps for this user on this day. |
| gfsteps | Number of google fit steps for this user on this day. |