essinit.md

@@ -135,21 +135,47 @@ Note that the channels that are purged/removed are: **NotEEG_chans + Fid_chans(s
 
 **merges**  
 This number indicates the number of files you wish to merge together. Entering a 1 into this field will prompt you for no merges, otherwise use the number of files you are combining. If you leave this feild empty ```''``` then you will get the following GUI prompt for a number.
-![nummerges](/uploads/9885d54325fd95c2c5bc144bbe24419c/nummerges.png)
+![nummerges](/uploads/9885d54325fd95c2c5bc144bbe24419c/nummerges.png)  
 
-**mergefiles**  
+***  
+
+**mergefiles**   
 This field can be left empty if you are not merging files. if you are nmergeing files leave this empty to prompt a browser to select the additional files you would like to merge to the loaded file. For example if  in the end I would like to combine 8 files. I use from above ```[merges],8``` and ```[mergefiles],''``` to browse for the other **7** files. Alternatively you can use swap strings to generate the names of the files and place them in a cell array. For example, ```[mergefiles],'[batch_dfn,_,-1]_m1.bdf' '[batch_dfn,_,-1]_m2.bdf'```
  
-![browsemerge](/uploads/64d029e9d32074d660a98fbc8cc3e885/browsemerge.png)
+![browsemerge](/uploads/64d029e9d32074d660a98fbc8cc3e885/browsemerge.png)  
 
+***  
 
-**change_srate**  
+**change_srate**    
 This item allows you to down sample your data's sampling rate. Use ```[change_srate],0``` or your current EEG.srate to leave the file as is. Type a new number to re sample to that frequency. If the field is left empty a GUI will prompt.
-![changesrate](/uploads/dc2c66e994f4d26e3abd695118edfb7d/changesrate.png)
+![changesrate](/uploads/dc2c66e994f4d26e3abd695118edfb7d/changesrate.png)  
 
-**erename**  
-This item is very similar to **NotEEG_chans** but is a list  of the indices of the fiducials. ESS capsules denote this information by specifying the channel *Type* as *FID* and will automatically use these when warping , but if you are using config you will have to specify these. For example our lab uses the first three channel locations as the LPA, NZ and RPA fiducials, using```[Fid_chans],[1 2 3]``` will set these as the landmarks for warping and then remove them from EEG.data afterwards. If you the leave config empty the following GUI will be displayed. Simply type in a indices of the channels, you do not have to do [  ] brackets in the GUI as it is already expecting a matrix. For example type```1 2 3```.
-![fids](/uploads/bc2b77cfce9682a2f667151421c71670/fids.png)
+***  
+
+**erename**    
+This variable stands for *Event-Rename* and can be used several different ways.
+
+**1. ESS**   
+This config field can be left blank, all you event codes will be renamed to their designated labels found in the study description.
+![esserename](/uploads/212adfb5d51dec8a5f2b6e8fcb229e94/esserename.png)
+
+**2. Manual**   
+Prompts a GUI where the user can see the old event names listed in a text editor. The list appears to be the event names all listed twice, but your job is to switch the second version of each of the names to the name you would like to use. This GUI will prompt for each of your merge files, in case you have the same events codes but wish to label them something different. If you do not wish to change the name then leave the second instance of the event code as is.
+![erenamegui](/uploads/294fc6f4e5e614a1d2de163e43bf3664/erenamegui.png)
+
+**3. Config File Reference**  
+If you would like to use the config to help rename your events you need to place the name of a event renaming file that matches the a specific design.
+Use  something like ```[erename],'Eyes_Erename.txt'``` in the config, and make sure your file is on the matlab path. :so: Store it in the *analysis/support/misc* folder so its on the path and you can use it later for reference.  
+
+The event renaming reference file should look like this:
+![erenamefile1](/uploads/281357a5d0cef623f1168f7d37bce061/erenamefile1.png)
+...
+
+![erenamefile2](/uploads/7779b6e1397d4638770f59364ce26c8a/erenamefile2.png)
+
+Where the first column is the file number, in reference to your merges, the second column is the existing event code, and the third column is the new event name. In the example above we were interested in the file one events only so they are renamed to understandable names. The events codes for the second file are left as is. You can add extra events that do not exist by accident, but make sure you do not leave one of your event codes out, as the name will be  set to empty. Separate the columns by spaces.
+
+:warning:  Note there are only 3 columns above! The first number in each row is my text editor displaying the line number! 
 
 ***