configuring-remote.md

-# Install
-The pipeline is designed to be used to defer computation to cluster of computers. We therefore need to have a copy of all files both locally and on the remote cluster.
-
-**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.
-
-**Practice Data Files**  
-For sample data to test your first execution of the pipeline see [this](sample-data) page.
-
-**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 `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`.
+# Configuring the Remote
+The pipeline is designed to be used to defer computation to clusters of computers. We therefore need to have synchronous copies of all files both locally and on the remote cluster.
 
-
-**Remote requirements**
+## Remote requirements
 
 The setup script will warn you if you are missing requirements but the basic requirements for remote setup are:
 * `ifort` (Intel C++ and Fortran Compiler)
 * `mpif90` (Open MPI 1.X)
 * `octave` GNU Octave Interpreter (Must be compiled with Java support)
 
+## Installation
+
+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`.
+
 **Setup Script**
 
 On the remote, through `ssh` run the script `./setup-remote.sh`
@@ -50,6 +42,12 @@ File name: [analysis/support/config/amica.sesinit]:
 
 Any problems with setup can be reported in [Issues](https://git.sharcnet.ca/bucanl_pipelines/bids_lossless_eeg/issues)
 
+**Data**
+
+Before setting up the remote cluster machine(s) you should consider uploading your 
+
+**Practice Data Files**  
+For sample data to test your first execution of the pipeline see [this](sample-data) page.
 
 [ :arrow_right: **Next Step**](running-your-first-job)
 [ :house: **Return to Main Page**](https://git.sharcnet.ca/bucanl_pipelines/bids_lossless_eeg/wikis/home)
\ No newline at end of file