| ... | ... | @@ -10,20 +10,6 @@ The goal of this page is to provide a working understanding of how the *pipeline |
|
|
|
## Main Pipeline Directory
|
|
|
|
Baseline initialization scripts and remote configuration scripts can be found at the highest level directory.
|
|
|
|
|
|
|
|
|**Filename**|**Explanation**|
|
|
|
|
|-------------|-------------|
|
|
|
|
|bids|See BIDS section below.|
|
|
|
|
|remote_archive|Mounting point for software to transfer data|
|
|
|
|
|remote_work|Secondary mounting point for software to transfer data.|
|
|
|
|
|bids_init_path.m|Matlab path configuration script.|
|
|
|
|
|eeg_init_path.m|Matlab path configuration script.|
|
|
|
|
|lossless_path.m|Matlab script to check if necessary dependencies are present and if so, adds them to the Matlab path.|
|
|
|
|
|setup-remote.m|Configuration script for building dependencies on remote clusters. See [here](configuring-remote).|
|
|
|
|
*Note: Excluded files at this level are git repository specific and have no actual effect on the pipeline*
|
|
|
|
|
|
|
|
## bids
|
|
|
|
**Note:** From this directory level on, all file structure are fully bids compliant.
|
|
|
|
|
|
|
|
|**Filename**|**Explanation**|
|
|
|
|
|-------------|-------------|
|
|
|
|
|code| BIDS Definition: This folder should contain the source code of scripts that prepared the dataset for running on the pipeline.
|
| ... | ... | |
