... | ... | @@ -12,13 +12,13 @@ Baseline initialization scripts and remote configuration scripts can be found at |
|
|
|
|
|
|**Filename**|**Explanation**|
|
|
|
|-------------|-------------|
|
|
|
|bids|See BIDS section below|
|
|
|
|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)|
|
|
|
|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
|
... | ... | @@ -33,9 +33,9 @@ Baseline initialization scripts and remote configuration scripts can be found at |
|
|
## bids/derivatives/lossless
|
|
|
|**Filename**|**Explanation**|
|
|
|
|-------------|-------------|
|
|
|
|code|stuff|
|
|
|
|log|stuff|
|
|
|
|sub-??|Subject folders containing the final output of the pipeline. Refer to config scripts to determine which .set file is which.|
|
|
|
|sub-??|Subject folders containing the final output of the pipeline. Refer to bash config scripts to determine which .set file is which.|
|
|
|
|log|Contains useful debugging information and necessary intermediate pipeline files. See below section for more details.|
|
|
|
|code|See section following the log section.|
|
|
|
|
|
|
## Log <a name="log"></a>
|
|
|
Log is automatically populated with scripts when you execute the pipeline. You will see a folder generated for every script identified by the script that was run followed by the date and time of the scripts execution. These folders contain:
|
... | ... | |