Original dataset

Inside data/original folder you will find a list of .csv files, all the files have similar filename pattern, used to distinguish different sessions, sensor location and dataset type.

[session name]_[sensor location].[dataset_type].csv

For example, file session1_DAK.raw.csv represents the raw 3-axis accelerometer data file for session 1 on dominant ankle. And file session2.annotation.csv represents the annotation file for session 2.

Note that there is only one annotation file for each session so sensor_location is omitted.

There are four raw accelerometer data files for each session at four sensor locations,

  • dominant wrist (DW)

  • dominant ankle (DAK)

  • nondominant wrist (NDW)

  • dominant arm (DAR)

Note that for the experiments run in the paper, only wrist accelerometers are used, please refer to the paper for detailed explanation.

Raw sensor data format

The accelerometer we used is Actigraph GT3X, which has a dynamic range of ±4g and stores value using 10 bits, it’s a 3-axis linear accelerometer. It stores in csv format, with the first column being the unix timestamp, and column 2 to 4 for x, y and z axis.

1319714602650,0.15625,-0.4375,-0.109375

There is no header row. Data has already been converted to -4g to +4g from voltage.

Annotation file format

Annotation file has standard csv format with header describes the meaning of each column.

Column name

Meaning

STARTTIME

start time of current annotation

ENDTIME

end time of current annotation

COLOR

unused

posture

annotation for body posture, could be walking, sitting, standing, lying

activity

annotation for subject activity

smoking

annotation for smoking status, could be either smoking or not-smoking

puffing

annotation for puffing status, could be no-puff, left-puff or right-puff

puff index

the index (start from 0) of current puff, if two annotation has the same puff index, that means they actually belong to the same puff. If it’s a no-puff annotation, the index will be -1.

prototypical?

A binary value (0 or 1) indicates whether this puff is prototypical puff. If it’s no-puff, the value will be -1.

potential error?

A binary value indicates whether this annotation might be wrong due to human error

note

additional comments on this annotation

link

filename of the corresponding puff example plot in the supplies/puffing_example_plots folder

Last updated

Was this helpful?