Skip to content

Changes

Page history
adlofts created page: pipeline scripts authored by Andrew Lofts's avatar Andrew Lofts
Hide whitespace changes
Inline Side-by-side
updates-and-git-version-control.md
View page @ c50a2044
...@@ -2,21 +2,35 @@ ...@@ -2,21 +2,35 @@
# Updates, Git and Version Control # Updates, Git and Version Control
**EEGLAB** **EEGLAB**
This pipeline uses the BUCANL [eeglab_asr_amica](https://git.sharcnet.ca/bucanl_eeglab/eeglab_asr_amica) version of EEGLAB. This pipeline uses the BUCANL [eeglab_asr_amica](https://git.sharcnet.ca/bucanl_eeglab/eeglab_asr_amica) version of EEGLAB.
You can determine if this version of EEGLAB is updated by checking through the website or by using git.
Even if your pipeline does not contain the most updated version of the associated BUCANL EEGLAB it should still work as designed, and also remember to use the recursive command when cloning the repository in order to get each of the sub modules.
# Git
Navigate to your project using the *cd* command. Using *git status* you will be able to see any new developments to sub modules in the untracked changes as **(modified content)**. Proceeding to the eeglab_asr_amica folder and preforming *git status* again will yield something like this:
![modifiedcontentineeglab](/uploads/a323772f360009055937a2eb64394f3c/modifiedcontentineeglab.png)
This shows the changes that have happened in the nested sub modules.
You can also see that the current **HEAD** is listed at the top. If you are on the most updated version this will instead say *master* and no HEAD branch will appear. See *git branch* on one of the sub modules:
![submodualisonahead](/uploads/e7127815607e1af9e1a4d08ba6b0eb20/submodualisonahead.png)
In order to update a specific sub module you can:
```matlab
cd /location/of/submodual
checkout master
git pull
```
or you can update all of the sub modules at once by preforming the following:
```matlab
cd /location/of/project
git submodule foreach git pull
```
# Website
In order to determine which BUCANL EEGLAB update you are using navigate to the eeglab directory in this **Pipeline** Project. In order to determine which BUCANL EEGLAB update you are using navigate to the eeglab directory in this **Pipeline** Project.
***
![versioncontroleeglab](/uploads/56d111a219ecd92ea202585fe6290cc4/versioncontroleeglab.png) ![versioncontroleeglab](/uploads/56d111a219ecd92ea202585fe6290cc4/versioncontroleeglab.png)
You should see a brief code such as *@2a691adf* proceeding the EEGLAB link which is the version identifier. You should see a brief code such as *@2a691adf* proceeding the EEGLAB link which is the version identifier.
Proceed to the network tab of **EEGLAB** project. You should see that the pipeline version code matches the start of the this EEGLAB version code. Proceed to the network tab of **EEGLAB** project. You should see that in this pipeline there is a version code that matches the start of the this EEGLAB version code. This is the commit that you are currently using.
***
![commitideeglab](/uploads/385ccace431176b8321a4e88d21a06c1/commitideeglab.png) ![commitideeglab](/uploads/385ccace431176b8321a4e88d21a06c1/commitideeglab.png)
Even if your pipeline does not contain the most updated version of the associated BUCANL EEGLAB it should still work as designed.
*** ***
[ :house: **Return to Main Page**](https://git.sharcnet.ca/bucanl_pipelines/eeg_pipe_asr_amica/wikis/home) [ :house: **Return to Main Page**](https://git.sharcnet.ca/bucanl_pipelines/eeg_pipe_asr_amica/wikis/home)
\ No newline at end of file