Category | 5 | 4 | 3 | 2 | 1 |
---|---|---|---|---|---|
Progress (5 pts) | Excellent progress. Optimal use of lab time. The team was fully focused on getting the assignment done, and fully engaged. | Good progress. Good use of lab time. The team was focused on getting the assignment done, and engaged. | Moderate progress. Used some of the lab time well. There was some focus on getting the assignment done, but the team was occasionnally distracted. | Insufficient progress. Poor use of lab time. The team was generally distracted, and did not focus much on the assignment. | Minimal progress. The team did barely use lab time to make progress on the assignment, and was often distracted. |
Category | 5 | 4 | 3 | 2 | 1 |
---|---|---|---|---|---|
Planning of code and statistical analysis (2.5 pts) | Introductory comment describes overall strategy and gives evidence of preliminary planning. Thoughtful problem decomposition breaks the problem into independent pieces that can be solved easily. | Evidence of planning before coding, but some flaws in overall strategy. | More planning needed: overall strategy ok, but have missed some obvious ways of making the code simpler. | It all hangs together, but planning was absent or rushed. | No evidence of planning. Strategy deeply flawed. |
Programming execution and reproducibility of results (2.5 pts) | Mastery of Python/R vocabulary means that the absolute minimum amount of code is used to get the job done. Code free from duplication. Each function encapsulates a single task, and repeated tasks are performed by functions, not copy and paste | Workable, but not elegant. Common programming idioms used to reduce code. | The code works, but copy-paste used often. | Most of the code works, but some parts do not work. Copy-paste used very often | Functions used inapproriately, or existing functions reinvented. Extensive use of copy and paste. |
Programming Clarity (2.5 pts) | Code is a pleasure to read, and easy to understand. Code and comments form part of a seamless whole. | Comments used to discuss the why, and not how of code; to provide insight into complicated algorithms; and to indicate purpose of function (if not obvious from its name). Comment headings used to separate important sections of the code. | Generally easy to read, but some comments used inappropriately: either too many, or too few. Some variable names confusing. | Hard to understand. Poor choice of names and comments do not generally aid understanding. | Cannot understand code. The reader cannot understand why the code works. |
Communication (2.5 pts) | Findings very well organised. Clear headings demarcate separate sections. Excellent flow from one section to the next. The report is easy to scan. Tables and graphics carefully tuned and placed for desired purpose. | Findings well organised and sections clearly separated, but flow is lacking. Each section has clear purpose. Tables and graphics clear and well chosen | Generally well organised, but some sections muddled. Tables or graphics appropriate, but some are poorly presented - too many decimal places, poorly chosen aspect ratio etc. | Sections unclear and no attempt to flow from one topic to the next. Graphics and tables poorly chosen to support questions. Some have fundamental flaws. | It is hard to read your notebook. There are no headings, figures are far away from where they are referenced in the text. There is no summary or conclusion. |
Category | 5 | 4 | 3 | 2 | 1 |
---|---|---|---|---|---|
Depth of reflections (10 pts) | Response demonstrates an in-depth reflection on, and personalization of, the theories, concepts, and/or strategies presented in the course materials to date. Viewpoints and interpretations are insightful and well supported. Clear, detailed examples are provided, as applicable. | Response demonstrates a thoughtful reflection on, and personalization of, the theories, concepts, and/or strategies presented in the course materials to date. Viewpoints and interpretations are generally supported. Appropriate examples are genterally provided, as applicable. | Response demonstrates a limited reflection on, and personalization of, the theories, concepts, and/or strategies presented in the course materials to date. Viewpoints and interpretations are sometimes usupported. Appropriate examples are provided, as applicable. | Response demonstrates a minimal reflection on, and personalization of, the theories, concepts, and/or strategies presented in the course materials to date. Some viewpoints and interpretations are unsupported or supported with flawed arguments. Some examples, when applicable, are not provided or are irrelevant to the assignment. | Response demonstrates a lack of reflection on, or personalization of, the theories, concepts, and/or strategies presented in the course materials to date. Viewpoints and interpretations are missing, inappropriate, and/or unsupported. Examples, when applicable, are not provided. |
Writing quality (5 pts) | Writing is clear, concise, and well organized with excellent sentence/paragraph construction. Thoughts are expressed in a coherent and logical manner. There are no more than three spelling, grammar, or syntax errors. | Writing is mostly clear, concise, and well organized with good sentence/paragraph construction. Thoughts are expressed in a coherent and logical manner. There are no more than five spelling, grammar, or syntax errors. | Writing is sometimes unclear and/or disorganized. Thoughts are not always expressed in a logical manner. There are more than five spelling, grammar, or syntax errors. | Writing is unclear and/or disorganized. Thoughts are not expressed in a logical manner. There are more than five spelling, grammar, or syntax errors. | Writing is unclear and disorganized. Thoughts ramble and make little sense. There are numerous spelling, grammar, or syntax errors throughout the response. |