rapids/config.yaml

# Valid database table names
SENSORS: [applications_crashes, applications_foreground, applications_notifications, battery, bluetooth, calls, fitbit_data, locations, messages, plugin_ambient_noise, plugin_device_usage, plugin_google_activity_recognition, screen]

# Participants to include in the analysis
# You must create a file for each participant
# named pXXX containing their device_id
PIDS: [p01, p02]

# Global var with common day segments
DAY_SEGMENTS: &day_segments
  [daily, morning, afternoon, evening, night]

# Global timezone
# Use codes from https://en.wikipedia.org/wiki/List_of_tz_database_time_zones
# Double check your code, for example EST is not US Eastern Time.
TIMEZONE: &timezone
  America/New_York

# Download data config
DOWNLOAD_DATASET:
  GROUP: AAPECS

# Readable datetime config
READABLE_DATETIME:
  FIXED_TIMEZONE: *timezone

# Communication SMS features config, TYPES and METRICS keys need to match
SMS:
  TYPES : [received, sent]
  METRICS: 
    received: [count, distinctcontacts, timefirstsms, timelastsms, countmostfrequentcontact]
    sent: [count, distinctcontacts, timefirstsms, timelastsms, countmostfrequentcontact]
  DAY_SEGMENTS: *day_segments  

# Communication call features config, TYPES and METRICS keys need to match
CALLS:
  TYPES: [missed, incoming, outgoing]
  METRICS:
    missed:  [count, distinctcontacts, timefirstcall, timelastcall, countmostfrequentcontact]
    incoming: [count, distinctcontacts, meanduration, sumduration, minduration, maxduration, stdduration, modeduration, hubermduration, varqnduration, entropyduration, timefirstcall, timelastcall, countmostfrequentcontact]
    outgoing: [count, distinctcontacts, meanduration, sumduration, minduration, maxduration, stdduration, modeduration, hubermduration, varqnduration, entropyduration, timefirstcall, timelastcall, countmostfrequentcontact]
  DAY_SEGMENTS: *day_segments

PHONE_VALID_SENSED_DAYS:
  BIN_SIZE: 5 # (in minutes)
  MIN_VALID_HOURS: 20 # (out of 24)
  MIN_BINS_PER_HOUR: 8 # (out of 60min/BIN_SIZE bins)

RESAMPLE_FUSED_LOCATION:
  CONSECUTIVE_THRESHOLD: 30 # minutes, only replicate location samples to the next sensed bin if the phone did not stop collecting data for more than this threshold
  TIME_SINCE_VALID_LOCATION: 12 # hours, only replicate location samples to consecutive sensed bins if they were logged within this threshold after a valid location row
  TIMEZONE: *timezone

BARNETT_LOCATION:
  LOCATIONS_TO_USE: ALL # ALL_EXCEPT_FUSED, RESAMPLE_FUSED
  ACCURACY_LIMIT: 51 # meters, drops location coordinates with an accuracy higher than this. This number means there's a 68% probability the true location is within this radius
  TIMEZONE: *timezone

BLUETOOTH:
  DAY_SEGMENTS: *day_segments
  METRICS: ["countscans", "uniquedevices", "countscansmostuniquedevice"]

GOOGLE_ACTIVITY_RECOGNITION:
  DAY_SEGMENTS: *day_segments
  METRICS: ['count','most_common_activity','number_unique_activities','activity_change_count']

BATTERY:
  DAY_SEGMENTS: *day_segments
  METRICS: ["countdischarge", "sumdurationdischarge", "countcharge", "sumdurationcharge", "avgconsumptionrate", "maxconsumptionrate"]

SCREEN:
  DAY_SEGMENTS: *day_segments
  METRICS_EVENTS: ["counton", "countunlock", "unlocksperminute"]
  METRICS_DELTAS: ["sumduration", "maxduration", "minduration", "avgduration", "stdduration"]
  EPISODES: ["unlock"]

LIGHT:
  DAY_SEGMENTS: *day_segments
  METRICS: ["count", "maxlux", "minlux", "avglux", "medianlux", "stdlux"]

ACCELEROMETER:
  DAY_SEGMENTS: *day_segments
  METRICS: ["maxmagnitude", "minmagnitude", "avgmagnitude", "medianmagnitude", "stdmagnitude", "ratioexertionalactivityepisodes", "sumexertionalactivityepisodes", "longestexertionalactivityepisode", "longestnonexertionalactivityepisode", "countexertionalactivityepisodes", "countnonexertionalactivityepisodes"]