DOI: 10.5281/zenodo.2671650
title: Data: Influence of Arm Swing on Cost of Transport during Walking

description: Data and code for De Graaf et al. (2019): Influence of Arm Swing on Cost of Transport during Walking (https://doi.org/10.1101/426775).

The ArmSwingData folder contains two subfolders. One with the raw data and one with the necessary scripts to run the analyses. The analysis can be run from the <strong>Main.m</strong> script located in the top folder. <strong>Start.m</strong>  initializes the program, and saves some important variables in <strong>infovar.mat</strong> so most programs can be ran separately, without being called from Main.m. If you change the name of the ArmSwingData folder, make sure to change the name for the directory in this script.

Data is ordered in the subfolder ‘Data’. For each participant (PP01, PP02, …, PP12) three folders exist:


	<strong>Cosmed</strong>: contains excel files with the metabolic (cosmed) data, as well as age/height/weight information of the participant
	<strong>ForcePlate</strong>: contains .afp and .afp2 files with kinetic data for forceplate 1 and 2 respectively. You can find which file corresponds to what condition in the file ‘Main_Forceplate.m’ stored in the software subfolder. Heelstrike information for the forceplate data has already been stored in the variable PP**_HS.mat, but can also be recalculated and checked from within the software. To do this open ‘Main_Forceplate.m’ and uncomment line 23 that runs ‘Forceplate_HeelStrike.m’ .
	<strong>Xsens</strong>: contains .mvnx for all conditions. You can find which file corresponds to what condition in the file ‘Main_Xsens.m’ stored in the software subfolder. Heelstrike information for the xsens data has already been stored in the variable PPXX_HS.mat, but can also be recalculated and checked from within the software. To do this open ‘Main_Xsens.m’ and uncomment line 23 that runs ‘Xsens_HeelStrike.m’ .


All scripts (except for start-up files Main.m and Start.m) are located in the software folder:


	<strong>=VU 3D Model=</strong>: the somewhat under documented VU 3D model, several functions of which are being used;
	<strong>Cosmed</strong>:  All scripts belonging to the cosmed analysis. These can be all run from Main_Cosmed.m
	<strong>ForcePlate</strong>: All scripts belonging to the kinetic analysis. These can be all run from Main_ForcePlate.m
	<strong>Xsens</strong>: All scripts belonging to the kinematic analysis. These can be all run from Main_Xsens.m
	<strong>Plotting</strong>: All scripts necessary for creating the figures featured. These can be all run from Plots.m


All the Main_*.m files can in turn be ran from Main.m. The Main_*.m files also contain brief descriptions of the files.  All files first check if the product they create already exist. If so they will not run. If you want to run them anyways, simply inverse the if ~exist statement by removing the tilde, the program will then be executed and the existing product will be overwritten.

N.B. For Xsens_Align, checking if it’s product exists takes a long time, so it could be wise to not run this program again after the first time (set run=false at the start of the program, or simply comment the line in Main_Xsens)