Things you should turn in for Programming Lab #3

Document your work in a well-written, 10 to 15 page report, including plots. This report is worth 70% of the grade for the assignment. The most important part of your report is an analysis of your results, that should offer insight into your design decisions and their relationship to your understanding of the application and the hardware testbed. Your report should thoroughly explain your results, relating them to how you designed the code. Discuss the decisions you made to improve performance, including any negative results.

Present a clear evaluation of the design of your code, including bottlenecks of the implementation. If you improved performance of your code in a sequence of steps, document the process. If you like, summarize the information in a list or a table in your report. If necessary, provide pseudo code to illustrate the concepts. Do not include full code listings in your writeup as these will be in your turnin.

If you are running out of time, put more effort into the writeup and your analysis rather than trying yet another performance enhancement. It can take time to collect, tabulate and plot results, as well as offer a reasonable explanation. We prefer a deeper analysis involving a few program optimizations over a shallower analysis over a larger number of optimizations. Spend more time discussing the optimizations that made a difference and less on those that made less of a difference. Negative results are also especially valued if you carefully document them, with the underlying causes, or best guesses if the causes are unclear.

Take care in how you plot your data, only plotting what's necessary to get your points across, and choosing log and linear plots carefully. You must also include any plotted data in tabular form. Tabular data may be included electronically (in your turnin) as a spreadsheet or other document called, e.g. Data.xlsx, Data.txt.

Cite any written works or software as appropriate in the text of the report. Citations should include any software you used that was written by someone else, or that was written by you for purposes other than this class. In such cases you must talk with us prior to get our approval.
Hard copy of your report. Hand in a hard copy by the deadline, placing it in Jing' student mailbox on the 2nd floor of EBU3B. The paper and electronic versions of the report should be identical. When there are any questions about turnin time, the latest timestamp of all files in your turnin establishes the turnin time. We won't collect files included in your repository after the deadline.
When you write your report, please put the following header on the front page:
```
CSE 260 Programming Lab 3
Date
Authors
Group ID's
Authors AID numbers
```
Files. Our tester will check out your code from your private Turnin repository, using the latest versions that were created not later than the deadline. Be sure that your svn repository is up to date. If you get stuck at the end, we can always roll back your code when grading it, though this may delay the grading of your assignment and result in a small penalty.
In addition to source code files, your electronic turnin should include a Makefile if you modified the provided version. We'll need this to build and test your code.

Your turnin must also include the following three important documents. These documents are required as the grading process which not complete without them. Empty forms, or forms not properly filled out, will result in a 10% penalty being assessed, in addition to holding up the grading process.
1. A PDF file containing the text of your report. The name of the file should contain the Group ID and Authors' AID number as follows:
```
A3-report-GROUP-ID-Student AID's.pdf
```
  GROUP-ID is the name of your group. If your group ID was G-123-456, and your AID numbers are 12345678 and 12345679, then file name of your report should be
```
A3-report-123-456_12345678-12345679.pdf
```
  If you working alone, then a legal file name would be, for example,
```
A3-report-123_12345678.pdf
```
2. A completed team self-evaluation called teameval.txt, that discusses the division of labor and other aspects of how you worked together as a team. A copy of the form is included in the provided code.
3. A file named DECLARATION, that you sign electronically, stating that the work was your own, and that you did not violate the Academic Integrity policies in effect for the course. The DECLARATION file is also included with the provided code. Make changes to your login ID(s) and the date only. Don't change anything else. Be sure that the date you entered falls in between the dates 2/13/2014-3/14/2014.

Scott B. Baden Fri [Mon Feb 10 08:42:33 PST 2014]