This page contains an overview of all measure types available in sampling packages; both packages that are are built-in to the carp_mobile_sensing framework, as well as the external ones. This list is constantly evolving as we release more and more support.

Measure type format

The dataType property of a Measure specify what type of data to collect. The string version is typically a namespace + name. CAMS-native measure types have the namespace dk.cachet.carp and the name is the measure type:
The cachet part of the namespace is a legacy. The original vision and design of CARP was done as part of the Copenhagen Center for Health Technology (CACHET) and the namespace dk.cachet.carp was adopted back then. Now, CACHET has closed and the maintenance of CARP is now done by the Section of Digital Health at the Department of Health Technology at the Technical University of Denmark.For now we keep the old namespace for backward compatibility. This will, however, be changed to carp.dk in the future.
The different types is specified in the tables below.

Event-based vs. one-time measures

Most measures are event-based (EB), i.e., once triggered and started, they continuously sample data from their sensor until explicitly stopped. For example, collecting a step event every time a step is detected on the phone. However, some measures are one-time (OT), i.e., sampling one piece of data when triggered. For example, collecting weather data from the Open Weather API. It is important to know the type (EB vs. OT) of a measure since an event-based measure can be started and run until stopped, whereas a one-time measure needs to be triggered to sample data. This can, for example, be done periodically using appropriate triggers, like the PeriodicTrigger. The difference when specifying the study protocol is illustrated below. The first task added to the protocol contains a one-time measure (device info), which is triggered only once. The second task contains a set of event-based measures that are triggered to start immediately and keep sampling data based on events. The third task collects weather (one-time measure) periodically every 5 minutes.
Each SamplingPackage provides a list of what types of measures it supports using the dataTypes property. Each sampling package also comes with a default sampling schema for each of its measure types.

Available measure types

CAMS comes with a large set of predefined measure types, each available in different sampling packages. Some measures are part of CAMS, others are available in separate sampling packages, and some are part of device-specific sampling packages. The tables below describe, for each measure:
  • Type Name - all type names are of the format dk.cachet.carp.<type>, where type is listed below
  • Availability on Android and/or iOS
  • The sampling package containing the measure
  • A description
Measures marked with * are one-time measures.

Built-in sampling packages

External sampling packages

Wearable device sampling packages

Each of these device measures has sub-types, such as dk.cachet.carp.movisens.hr for heart rate (HR) measures from the Movisens device.