| title | nav |
|---|---|
Step 5 - Version Control |
true |
Are you keeping track of any versions or logs made by the software in use?
Make sure you have a copy of every step you have completed and if possible, version numbers for the program you are using and any libraries. Programs change over time and this can alter your results if someone asks to replicate your work post publication.
Instead, make a copy of the raw data files and keep them somewhere safe (like Research Vault). That way, if you need to redo your work or you find an error earlier in your workflow, you have an original baseline to start from.
Write down the versions of analysis software (like SPSS or NVIVO etc) AND hardware (MRI machines etc). Your documentation is a great place for this, but even just in your lab notebook will work.
If you are using random numbers in your research, save your random seed generator number as part of your working data. This way, you can later reproduce your results.
If you are using a workflow program (Galaxy, KNIME, a virtual lab like EcoCloud or TINKER Humanities,Arts and Social Science Virtual Lab), you can copy your workflow and save it as part of your documentation. Write the date that you ran the workflow if versions of the software are not available.
If you are writing scripts (R/Python/Matlab etc), use Git.
Note:
Griffith has a gitlab version you can use for private repositories. Also record the version of R/Python/Matlab, the operating system you are using and the version numbers of any library you are using.
If you are using the HPC, also record the version of any modules you used there.
If you’ve heard of Docker or Singularity and you are interested, come talk to hacky hour/eResearch Services
NB if you are going to publish any Git repos, please talk to Antony Ley, our IP specialist for a copyright licence
- Workshops on how to use git are available through Hacky Hour as Software Carpentry Griffith