Data Tools - RunScribe

Data Analysis Tools

RunScribe Data Tool Support

Please note – RawData was designed as a debugging tool, so any/all RawData access is on a DIY basis, as the system isn’t designed to properly record/analyze RawData in addition to the onboard metrics.

Per-Step Metrics - CSV Export

Click here for CSV Export Instructions …

Raw Data Collection - Configuration

You can request RawData access by emailing support@runscribe.com – letting me know what email address is associated with your account along with your intended use. Once RawData has been enabled for your account, you’ll need to enable it via the RS mobile app.

RawData is collected at 500Hz, resulting in file sizes that are far beyond what is typical for the consumer metrics. On-board flash memory will typically fill within 20min, and uploads can take upwards of an hour for ever 10min of collection.

Raw Data Download - FIT Files

Raw Data Conversion - FIT to CSV

Raw Data - Scaling Factors

Once you’ve downloaded the RawData in CSV format, you’ll need to do a little scaling:

# Time in (1/4) msec
Motion.Time <<- as.numeric(CSV_MotionData[,5]) / 4.0

Motion.Accel.X <<- as.numeric(CSV_MotionData[,8]) / (256*8.0) ;
Motion.Accel.Y <<- as.numeric(CSV_MotionData[,11]) / (256*8.0) ;
Motion.Accel.Z <<- as.numeric(CSV_MotionData[,14]) / (256*8.0) ;

Motion.Gyro.X <<- as.numeric(CSV_MotionData[,17]) / 16.384;
Motion.Gyro.Y <<- as.numeric(CSV_MotionData[,20]) / 16.384;
Motion.Gyro.Z <<- as.numeric(CSV_MotionData[,23]) / 16.384;

Motion.Mag.X <<- as.numeric(CSV_MotionData[,26]) / 32;
Motion.Mag.Y <<- as.numeric(CSV_MotionData[,29]) / 32;
Motion.Mag.Z <<- as.numeric(CSV_MotionData[,32]) / 32;

Motion.Quat.Q0 <<- as.numeric(CSV_MotionData[,35]) / 16384.0 ;
Motion.Quat.Q1 <<- as.numeric(CSV_MotionData[,38]) / 16384.0 ;
Motion.Quat.Q2 <<- as.numeric(CSV_MotionData[,41]) / 16384.0 ;
Motion.Quat.Q3 <<- as.numeric(CSV_MotionData[,44]) / 16384.0 ;