... | ... | @@ -41,7 +41,7 @@ The pipeline is designed to be used to defer computation to cluster of computers |
|
|
|
|
|
**Data**
|
|
|
|
|
|
Before setting up the remote cluster machine(s) you should copy your .set or .ess data to your `<project root>/analysis/data/1_init` directory
|
|
|
Before setting up the remote cluster machine(s) you should copy your .set or .ess data to your `<project root>/analysis/data/1_init` directory.
|
|
|
|
|
|
**Practice Data Files**
|
|
|
There are 10 practice data files that can be downloaded from the following owncloud link if you wish to practice before you obtain your own data:
|
... | ... | @@ -52,8 +52,27 @@ The eeg_pipeline_asr_amica requires a setup on the server side in order to be ab |
|
|
|
|
|
**Synchronize**
|
|
|
|
|
|
Synchronize your data/pipeline project directory with the remote cluster using `scp` or another method supported by your remote cluster administrators. Secure copy (`scp`) will copy all files over the existing files and therefore wastes time transferring files that already exist on the remote. Systems that support `scp`/`ssh` usually will support `rsync` as well which only sends the differences between your files and the remote files speeding up your transfer. You may also use a visual diff program like `meld` over
|
|
|
Synchronize your data/pipeline project directory with the remote cluster using `scp` or another method supported by your remote cluster administrators. Secure copy (`scp`) will copy all files over the existing files and therefore wastes time transferring files that already exist on the remote. Systems that support `scp`/`ssh` usually will support `rsync` as well which only sends the differences between your files and the remote files speeding up your transfer. You may also use a visual diff program like `meld` over `sshfs` which is "secure shell file system." For Windows a suitable program for `scp` is [MobaXterm](http://mobaxterm.mobatek.net/). For Unix/Linux & MacOS users you will already have `scp` and you likely will also have `rsync`.
|
|
|
|
|
|
***scp example***
|
|
|
```bash
|
|
|
# Change to your project directory locally in terminal
|
|
|
cd /scratch/user_name/project_dir
|
|
|
# -r specifies recursive directory copy
|
|
|
# dot specifies this directory
|
|
|
# scp -r . <you_username>@<your remote cluster>:<remote path>
|
|
|
scp -r . brad@graham.computecanada.ca:/scratch/brad/
|
|
|
```
|
|
|
***rsync example***
|
|
|
```bash
|
|
|
# Change to your project directory locally in terminal
|
|
|
cd /scratch/user_name/project_dir
|
|
|
# -a specifies archive options
|
|
|
# dot slash (./) specifies this directory should be synced with the remote directory
|
|
|
# note the ending slashes
|
|
|
# rsync -av ./ <you_username>@<your remote cluster>:<remote path>
|
|
|
rsync -av ./ brad@graham.computecanada.ca:/scratch/brad/
|
|
|
```
|
|
|
**Remote requirements**
|
|
|
|
|
|
The setup script will warn you if you are missing requirements but the basic requirements for remote setup are:
|
... | ... | @@ -66,7 +85,7 @@ The setup script will warn you if you are missing requirements but the basic req |
|
|
On the remote, through `ssh` run the script `./setup-remote.sh`
|
|
|
|
|
|
*on remote server*
|
|
|
```
|
|
|
```bash
|
|
|
cd /path/to/root/of/project
|
|
|
./setup-remote.sh
|
|
|
```
|
... | ... | @@ -74,5 +93,5 @@ cd /path/to/root/of/project |
|
|
Any problems with setup can be reported in [Issues](https://git.sharcnet.ca/bucanl_pipelines/eeg_pipe_asr_amica/issues)
|
|
|
|
|
|
***
|
|
|
|
|
|
[ :arrow_right: **Next Step**](configuring-context-config)
|
|
|
[ :house: **Return to Main Page**](https://git.sharcnet.ca/bucanl_pipelines/eeg_pipe_asr_amica/wikis/home) |
|
|
\ No newline at end of file |