T-106.290 Ohjelmoinnin laboratoriotyöt

Deliverables for the Implementation Phase

The primary purpose of this deadline is to ensure you reserve enough time to run the tests. In some cases meaningful test runs may last for many days, and procrastinating with the implementation may leave too little time to run the tests. The same argument applies to processing the test results and writing the final report.

So, by the 16th of March you should have completed the implementation of programs that you run in order to generate benchmark results. This includes the following items:

• Algorithms or programs being tested, unless they are public software packages in which case it is sufficient to give the exact version number and/or URL for the software package.
• The input data or programs you generate input data with.
• Scripts and/or main routines that run the benchmarks, if any.

It is not necessary to include the programs you use to perform statistics or graphical presentations for the final report.

Note that this deadline should represent a code freeze of the code included in the deliverable. It is permitted to fix bugs or update public software packages to newer ones, but this will either have to be reported in the final report or a second, updated, submission of the implementation to be done in conjunction with the final report.

The procedure of submitting the deliverable is rather similar to electronics submission LaTeX-documents in previous deadlines:

1. Gather all the code of the deliverable in one directory, possibly organized into subdirectories.
2. If the purpose of a file is not self-evident by its name or comments in the beginning of the file, write a small README-file where you briefly describe the purpose of each file.
3. Include a Makefile, a compilation script, or write instructions of how to compile in the README-file.
4. Remove all object files and executables generated by the compiler in order to keep the deliverable as small as possible.
5. Go to the parent directory, and make a tar-file of the directory by issuing

   tar cf foo.tar foo

6. Copy the tar-file to a place where your assistant can download it from, and mail the URL to your assistant.

This deliverable will not be graded in any way, and it is quite possible that your assistant checks it only by skimming through it. The deliverable may, nevertheless, be subject to closer inspection if we suspect bugs that make the results incorrect or even worse, fabrication of benchmark results.