CS 6364_4364 Lab 10
-
Lab 10 is due by Thursday, 12/05 at 11:59 PM (EST)
Announcements
-
Class participation, Google Folder.
Goals
Goals for this Lab Assignment:
-
Double Blind peer review
-
Learn and Apply Best Practices
1. Double-Blind Peer Review Instructions
-
Review the Same Five Submissions as the Midterm
-
Continue reviewing the same five submissions you were assigned for the midterm, ensuring consistency in your evaluation.
-
-
Evaluate Both Code and Final Paper Draft
-
Review both the code implementation and the draft of the final paper. Assess how well the code aligns with the project goals and how effectively the paper communicates the findings.
-
-
Provide Constructive Feedback
-
Be supportive and specific when writing comments. Clearly define actionable tasks for improvement, focusing on areas that can enhance both the quality of the code and the clarity of the paper.
-
-
Generate a Final Score
-
Assign a score to each submission, considering both the code and paper draft. Ensure your scoring reflects the quality of the work and provides a basis for improvement.
-
2. Write Your Own Review
-
Task: Review FIVE final project draft from your assigned set.
-
Review FIVE final project drafts from your assigned set. You are required to review the same five submissions as the midterm. Please adhere to the guidelines for double-blind reviewing as outlined on the Reviewer Guidelines page.
-
-
How to Write Your Review:
-
Your review should follow the Reviewer Guide and Review Examples. Be thorough, constructive, and respectful in your feedback. Below is the structure your review should follow, including both the paper and code review.
-
Summary and contributions: Provide a summary of both the paper and the code. Include the paper’s innovation, how it connects to the topic, and its potential impact. Briefly assess the functionality and implementation of the code, particularly how well it aligns with the project goals. Write at least five sentences.
-
Strengths: Highlight the strengths of both the paper and the code. For the paper, focus on the quality of the writing, novelty of the approach, and research contribution. For the code, discuss aspects like efficiency, readability, and how well it accomplishes the intended task. Write at least five sentences.
-
Weaknesses: Provide constructive feedback on weaknesses in both the paper and code. For the paper, focus on areas such as unclear explanations, missing citations, or lack of depth. For the code, comment on possible issues with implementation, bugs, or inefficiencies. Be specific, and provide examples to help the authors improve.
-
Clarity: Comment on the clarity of the paper. Provide examples of sections that could benefit from revision for improved clarity. If the code is hard to follow, mention any areas that need clearer documentation or better structure.
-
Relation to prior work: Assess how the work relates to prior research. The related work section should not just list references but explain how the proposed work differs from existing literature. Additionally, discuss whether the code builds on any prior implementation or open-source tools.
-
Overall score: Provide an overall score for both the paper and code. Use the EEGEyeNet rubric (7-7-10) as a reference. I expect most reviews to fall around 6 out of 10 or lower. Remember, this score is for helping your peers improve and is NOT tied to their final project grades.
-
Questions: (Optional) If applicable, include any additional questions for the authors to clarify their work or improve their approach.
-
-
3. Submission Guide
-
Each student team only submits one file, lab_10_lastname1_lastname2.zip, including
-
Five review PDF files in HCII format, name your review files such as submission_1st_reviewer_A7D5.PDF, submission_5th_reviewer_A7D5.PDF
-
Keep the review process double-blind, your team will be assigned a team number and a reviewer code.
-
4. Notes
-
Email the zip file for Lab 10 to x.qu@gwu.edu.
-
Lab assignments are typically released on Fridays and are due the following Thursday.
-
Lab 10 is due by Thursday, 12/05 at 11:59 PM (EST)