The initial completion check: Each project will specify a set of items that you must complete approximately one week prior to the official due date. This is to ensure that your tools work, to minimize the burden of last minute questions, and to give you time to focus on writing your report. Unless otherwise approved, these completion checks must be performed during your lab session, and it is your responsibility to meet with the TA to have her/him check your code. Failure to have your project checked during lab will result in a 10% grade reduction on your project.

Turning things in: Before 5:00 pm on the date indicated, you must upload two files to Canvas:

  1. All Matlab functions and scripts, as separate ”.m” files, as well as input files or requested plots or output files, must be combined into a single ”.tgz” or ”.zip” file to so that they can be run when grading. For portions of the project performed interactively, turn in Matlab diaries containing all commands you used.
  2. A technical report, consisting of a single ”.pdf” file. This should:
    • Use complete sentences and paragraphs – this is a report, not an itemized list of responses.
    • Explain the problems to be solved, and the mathematical approaches used on them.
    • Describe your codes, including a discussion on any unique decisions that you had to make.
    • Discuss all of your computed results. In this portion, you should include any relevant plots, as well as any relevant output from running your codes.
    • Answer all questions posed in this project.
    • In your own words, explain why you found the results that you did, justifying them mathematically if applicable.
    • Include all of your Matlab functions, scripts, and diaries as attachments to the report (in the same file).

The uploaded code and all results in your writeup must match – always turn in output from the final version of your program. Otherwise points will be deducted, and we will not know whether the results came from your program or somebody else’s (so you may be suspected of violating the Honor Code).

We will run your codes, so do not forget any of the files needed to run your code!

You must obey the SMU Honor Code on all projects (all work must represent your own individual effort).

Example Project

The following project was turned in by a student from a previous year. It is a good example of the level of detail and the kind of work that is expected in the project reports in this class.

Project 1: Nonlinear Solvers

(assigned 3/6, progress check 3/26, due 4/5)

Project 2: Numerical Integration

(assigned 4/3, progress check 4/23, due 5/3)