sift:documentation:directory_structure_for_input_data
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| sift:documentation:directory_structure_for_input_data [2024/06/18 13:26] – sgranger | sift:documentation:directory_structure_for_input_data [2024/07/17 15:44] (current) – created sgranger | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| + | ====== Directory Structure for Input Data ====== | ||
| + | |||
| There is a basic directory structure for Sift's input data that aligns with some useful concepts from the experiments that produced the data. This directory structure organizes the [[Visual3D: | There is a basic directory structure for Sift's input data that aligns with some useful concepts from the experiments that produced the data. This directory structure organizes the [[Visual3D: | ||
| Line 7: | Line 9: | ||
| - Trial | - Trial | ||
| - | ===== Study ===== | + | ==== Study ==== |
| Although the name of this directory level suggests that the data it contains is only used for one study, this is not necessary. As a top-level concept this is the largest, most general database that is stored in on location. This could be specific to a study, or it could be specific to a project, researcher, lab, or consortium. In these latter cases it is possible to define [[Sift: | Although the name of this directory level suggests that the data it contains is only used for one study, this is not necessary. As a top-level concept this is the largest, most general database that is stored in on location. This could be specific to a study, or it could be specific to a project, researcher, lab, or consortium. In these latter cases it is possible to define [[Sift: | ||
| - | ===== Group ===== | + | ==== Group ==== |
| This level of the directory structure is optional, but it allows the researcher to divide c3d files according to desired parameters, e.g., Women - Men, Old - Young. If this level is omitted from the structure then individual C3D files can be [[Visual3D: | This level of the directory structure is optional, but it allows the researcher to divide c3d files according to desired parameters, e.g., Women - Men, Old - Young. If this level is omitted from the structure then individual C3D files can be [[Visual3D: | ||
| - | ===== Session | + | ==== Session ==== |
| This directory level can be conceived as a single day (or a single effort) of data collection within the database. This is the most important level as this is where the [[Visual3D: | This directory level can be conceived as a single day (or a single effort) of data collection within the database. This is the most important level as this is where the [[Visual3D: | ||
| - | ===== Task ===== | + | ==== Task ==== |
| This level of the directory allows the researcher to divide c3d files according to the desired activity, e.g., walking, running, jumping, etc. As with group-level parameters, C3D files can be coded with these different tasks by using [[Visual3D: | This level of the directory allows the researcher to divide c3d files according to the desired activity, e.g., walking, running, jumping, etc. As with group-level parameters, C3D files can be coded with these different tasks by using [[Visual3D: | ||
| - | ===== Trial ===== | + | ==== Trial ==== |
| At this level of the directory structure we have individual trials. This means that we have the individual C3D files that are recorded by the motion capture system. | At this level of the directory structure we have individual trials. This means that we have the individual C3D files that are recorded by the motion capture system. | ||
sift/documentation/directory_structure_for_input_data.1718717171.txt.gz · Last modified: 2024/06/18 13:26 by sgranger