Skip to content

ActiPASS project folder structure

Pasan Hettiarachchi edited this page Apr 6, 2023 · 34 revisions

ActiPASS project folder structure

Project-folder-structure

1) BatchOut

This folder is where you shall start to look for your results. This folder contains the results and visualizations in separate folders, for each batch. In each batch folder the diaries, quality check logs and visualizations (.png files) for each individual is stored.

Tips! -You can easily perform the quality check of your data by quickly browsing the visualization (.png files) in the BatchOut folders by using the preview function in your file explorer

In the file "ActiPASS_BatchQC" information that may be valuable when you perform the quality check of your batch is stored.

There is also one important file "ActiPASS_BatchSettings" with information about all settings and parameters that was used for the actual batch. If you have forgot what settings that you have used when you processed the data you can find that in this file

There is also one file "ActiPASS_BatchLog" with information about the batch processing.

2) CrashLogs

Here you can find crash logs with information that may be useful for the developer if something went wrong when running ActiPASS.

3) IndividualOut

Here the results is stored in separate folders for each individual. If you have chosen to create "full" visualizations there are individual weekly histograms and pie-charts visualizations as well as weekly activity visualizations that can be used for feedback to the participants.

There is also more specific information from the sleep algorithm and individual files for the daily activities that are available here.

In this folder there is also a matlab data table with the activities second by second for each individual, and warnings that may have been generated during the processing of the individual data.

4) QC_Distributions

Here you find the distributions in histograms (*.png files) for each activity types. These distributions is valuable to use when you perform you quality check and shall find eventual outliers in your data. In the excel files the participants ID is shown.

Tips!- by opening the SubjectID_ Distributions.xls file in excel you can zoom out in excel and then you can visualize an upside down histogram with the participant ID's.

5) ActiPASS_QC_MasterFile.xlsx

This file contains merged data which is useful for the quality check. It contains information such as start/stop times of the measurement, start/stop times of the wear period, orientation, automatic individual calibration (reference positions), device calibration, outlier flags and other error flags.

6) ActiPASS_Daily_LongFormat_MasterFile.csv

This is the main result file which contains merged data from one or several batches seperated into calendar days. The file contains all default variables which are needed for most types of analysis. This is a long-format (i.e. multiple rows for each day for each participant) table and contain data for both valid and invalid (not enough wear-time and other exclusions) days. It also contains columns of quality-check information for each day. For more information about the variable definitions we refer to ActiPASS variable dictionary. The file is created after the stat generation step in ActiPASS.

7) ProPASS_WideFormat_MasterFile.csv

This file also contains calendar day based variables from all batches (similar to the above) suitable for ProPASS projects. This is a wide-format table (i.e. there is only row for each participant). However this table only contains data for only first valid 7 days (ProPASS criteria). For more information about the variable definitions please refer ActiPASS variable dictionary. This file is created after stat generation step in ActiPASS.

8) ActiPASS_Events_LongFormat_MasterFile.csv

This is the results of an events (stats-domains) based stats generation. This is generated only when ActiPASS output table format is changed from defult "daily" format to one of the "Events" formats in advanced settings. Unlike 'days', 'events' are not automatically quality checked for validity, and this table contains all events sequentialy as a long format table.