created a directory called appendix in the GitHub repo and added all the notebooks to it, organised into subdirs by chapter.
created a README.md for the appendix dir with a list of the notebooks and their names, this is automatically rendered into an appendix at the end of the pdf version (Example can be downloaded here, Appendix starts on page 219).
added in-text references to the appendix in the methods sections of each results chapter.
Once everything is totally finalised I will submit the whole repo, including the thesis & appendix, to Zenodo. I guess I should probably only do this after my viva & corrections, because - if I understand correctly - the Zenodo copy is not editable after submission. I will have to make the github repo public before my viva in case the examiners want to look at the code, though.
Does this sound like a good solution, @IanSudbery ?
as a means of adding a code appendix, I have:
appendixin the GitHub repo and added all the notebooks to it, organised into subdirs by chapter.README.mdfor the appendix dir with a list of the notebooks and their names, this is automatically rendered into an appendix at the end of the pdf version (Example can be downloaded here, Appendix starts on page 219).Once everything is totally finalised I will submit the whole repo, including the thesis & appendix, to Zenodo. I guess I should probably only do this after my viva & corrections, because - if I understand correctly - the Zenodo copy is not editable after submission. I will have to make the github repo public before my viva in case the examiners want to look at the code, though.
Does this sound like a good solution, @IanSudbery ?