Directory tree and GIT access#
Standard directory structure#
Each user should place (either physically or through symbolic links)
sdt.daily
xxx .sdtcheck patchupgrade
sdtcheck patchmkl
xxx / sdtdef problem if existclone by url https://github.com/SDTools-support/support
xxx clone_Support.png
For internal SDTools processes this is
sdt.cur
sdt.git
contains all the project directories. For examplesdt.git\support
should be a clone from https://github.com/SDTools-support/support
sdt.git/repo
should then contain the standard directoriessdt.git\repo\m
should contain.m
source files. Standard file names ared_*.m
correspond to demos and are never pcoded.t_*.m
correspond to test files.*(year).m
dev24.m
correspond to a project and the associated year.
sdt.git\repo\tex
should contain.tex
source files.sdt.git\repo\tex\plots
can contain.tex
source files but do not add binary figures (png/pdf/jpg) in the directory.sdt.git\repo\jup
should contain.md
or.rst
source files for documentation generation.
GitHub desktop as git interface#
GitHub desktop is an intuitive interface for Git access. It is the choice used by SDTools to explain git to users that are not familiar with this versioning system.