NOTE: If you strongly prefer to use an alternate system (e.g., GIT) for your repository, you may do so, but you will have to manage the setup and access yourselves, and provide access to the repository to the instructional staff. David Brodbeck will provide a directory on the cluster.
You should lay out the repository along the following lines. Assuming
the group's directory is G1,
G1/trunk: main code
G1/branches: experiments
G1/tags: releases/deliverables
G1/tags/D1
G1/tags/D2
G1/tags/D3
G1/tags/D4
Each release should have following basic structure:
Dx/Dx.cmd: top-level Condor file (not needed for D1)
Dx/README: not needed for D1
Dx/src: source code
Dx/doc: reports, powerpoints, additional documentation
Dx/outputs: output files
Dx/results: evaluation results
This initial version should include the sections (headings and as little text as you'd like) below:
Please name your report D1.pdf.
The goal of this exercise is to ensure that, for the remainder of the course, you can concentrate on building working systems, rather than trying to figure out bibtex or arguing with your teammates about whether to use Word or latex.