| Topic | Excellent | Satisfactory | Needs Work |
|---|---|---|---|
| Coding style | |||
| Coding strategy | |||
| Coding documentation | |||
| Presentation: graphs | |||
| Presentation: tables | |||
| Achievement, creativity | |||
| Ease of access |
Remarks:
Coding style: This is the format of the code. Are there code chunks so it is easy to follow when a new command starts? Are there indents so you can follow what are commands and what are the parts of the command?
Coding strategy: Does the code flow in a linear fashion or is it just a random set of tries of different types of code?
Code documentaion: Is each code block documented with a description of what the code is doing and rationale for that choice? Is there documentation of what was tried and isn’t shown (perhaps it is in an older version, which should be noted)?
Presentation: graphs: Are the graphs logical and do they have legends that make sense? Can you locate the code that created the graphs?
Presentation: tables: Do the tables stand alone or can you only understand them by reading the report (which you probably won’t read)? Do they use consistent signficant figures? Is their a legend or caption? Are the tables good tables for this analysis/homework?
Achievement: Overall impression of the work.
Ease of access: Could you easily find the code files for the different elements or were you searching through a sea of files?