History

rubberhead 81262392e0 Added table		2024-03-11 21:02:07 +00:00
..
draft	I THOUGHT BACKGROUND WRITING WOULD BE EASY	2023-10-11 22:34:21 +01:00
misc	Added table	2024-03-11 21:02:07 +00:00
.gitignore	Initial commit -- w4 status report	2023-10-09 00:25:28 +01:00
eushield-normal.pdf	Initial commit -- w4 status report	2023-10-09 00:25:28 +01:00
eushield.sty	Initial commit -- w4 status report	2023-10-09 00:25:28 +01:00
infthesis.cls	Initial commit -- w4 status report	2023-10-09 00:25:28 +01:00
main.bib	Can't remember... whatever rollback is possible anyways	2023-12-06 02:20:03 +00:00
mybibfile.bib	Initial commit -- w4 status report	2023-10-09 00:25:28 +01:00
README.md	Initial commit -- w4 status report	2023-10-09 00:25:28 +01:00
skeleton.pdf	Initial commit -- w4 status report	2023-10-09 00:25:28 +01:00
skeleton.tex	Maintenance	2023-11-25 16:05:51 +00:00
ugcheck.sty	Initial commit -- w4 status report	2023-10-09 00:25:28 +01:00

README.md

Template for Informatics UG final-year projects

Please base your project report on skeleton.tex, reading the instructions in that example file carefully.

To compile the skeleton.pdf report, with all cross-references resolved:

pdflatex skeleton.tex
bibtex skeleton.aux
pdflatex skeleton.tex
pdflatex skeleton.tex

Many TeX distributions have (or can install) a latexmk command that will automatically compile everything that is needed:

latexmk -pdf skeleton.tex

If the logo causes compilation problems (errors related to eushield), it isn't necessary, you may remove the logo option from the first line of code. Although check first that you are using pdflatex or the -pdf option above. As directed in skeleton.tex do not change other template or layout options.

Occassionally latex gets really confused by errors, and intermediate files need to be deleted before the report will compile again. We strongly recommend that you keep your files in version control so that you can unpick any problems. Remember also to keep off-site backups.