•  Each week submit in your assignment in the form of an ``executive summary''. Imagine this to be the document you would give to your manager, if you were in an industrial setting, or to your advisor if you were in graduate school. Make your report succinct and focused on what you did. Don't bother copying much from the text (I wrote it), but do try to express the point of the work using your own words.

•  To save you time in the long run, do it right. Before you begin working on your assignment or running code, write down (and save this as part of your report):

                1.   the equations you are to solve or simulate (the math)
                2.   the numerical method being used (the algorithm)
                3.   the code listing (the modified code that you ran)

•  For an A grade, answer all parts of the assigned problem including these 5 items:

                1. the equations you are to solve or simulate
                2. the numerical method being used
                3. the code listing
                4. edited results (just the edited good stuff): graphs, short tables, or something visual
                5. critical analysis: what did you learn, are you convinced, how could we do this better.

• No credit will be given for just running a code we give you; you should be modifying, extending, applying, or rewriting it as part of understanding the problem.

• You may discuss your projects with other people, but the report you submit must reflect your own work. If you submit it, you have agreed that you are prepared to explain it to the instructor.
   

Partial support for this work was provided by the National Science Foundation, NPACI, and EPICS.
©Rubin H Landau, Oregon State University, Corvallis, Oregon 2011