CS 4364 Lab 10

  • Lab 10 is due by Monday, 04/27 at 11:59 PM (EST)

Announcements

Goals

Goals for this Lab Assignment:

  • Practice double-blind code review

  • Learn from other teams’ code and implementation choices

  • Evaluate code quality, readability, reproducibility, and technical progress

  • Prepare for the final project by reflecting on good coding practices

1. Double-Blind Code Review Instructions

  • Review All Submitted Lab 09 Code Submissions

    • Each student must individually review all Lab 09 team submissions.

  • Focus on Code, Not the Paper

    • This lab focuses on reviewing the code submission materials from Lab 09, not the final paper draft.

    • You should review the code folder, README file, and short results summary or comparison table submitted by each team.

  • Provide Constructive Feedback

    • Your feedback should be clear, specific, respectful, and useful for improvement.

    • Please point out both strengths and areas to improve.

  • Keep the Review Double-Blind

    • Do not include your real name inside the review files.

    • Use only your assigned reviewer code in the file names and inside the review documents.

2. Write Your Own Review

  • Task: Review ALL submitted Lab 09 team code submissions individually.

    • Each student must complete their own reviews. This is an individual lab assignment, not a team submission.

    • You should carefully inspect each team’s submitted code materials and write one review for each submission.

  • How to Write Your Review:

    • Your review should be simple, clear, and constructive. Focus on the code and supporting materials. For each submission, include the following parts:

      1. Summary: Briefly describe what the code appears to do, what model or method is implemented, and what the team is trying to compare or demonstrate. Write at least three sentences.

      2. Strengths: Point out one or more strengths of the submission. For example, you may comment on code organization, comments, naming, README quality, or clear experimental structure. Write at least three sentences.

      3. Weaknesses / Areas to Improve: Provide constructive suggestions for improvement. For example, unclear code structure, missing instructions, weak documentation, reproducibility issues, or confusing results presentation. Be specific and helpful.

      4. Code Clarity and Organization: Comment on whether the file structure, variable names, comments, and implementation are reasonably easy to understand.

      5. Reproducibility and Technical Progress: Comment on whether the README and code make it reasonably clear how to run the project, and whether the submission shows meaningful technical progress.

      6. Overall Score: Give one overall score for the code submission on a 10-point scale. Please use the score mainly as feedback for improvement, not as a judgment of the team’s final project grade.

      7. Questions: (Optional) If anything is unclear, you may include one or two short questions for the authors.

3. What to Focus On

  • Please focus mainly on the following:

    • Code clarity and organization

    • README quality and ease of understanding

    • Whether the code seems reasonably correct

    • Reproducibility and ease of running the code

    • Whether the results summary or comparison is understandable

    • Signs of real technical progress

  • Model performance matters, but it is not the main focus of this lab.

  • This is a code review lab, not a paper review lab.

4. Submission Guide

  • Each student submits one file, lab_10_lastname.zip, including

    1. One review PDF file for each Lab 09 team submission

    2. One short overall reflection file, such as overall_reflection.pdf or overall_reflection.txt

    3. Keep the review process double-blind. Use only your reviewer code in the review file names and inside the review documents.

  • Name your review files like submission_1_reviewer_A7D5.pdf, submission_2_reviewer_A7D5.pdf, and so on.

  • In your overall reflection, briefly summarize what you learned from reviewing other teams’ code, common strengths you noticed, and common issues you noticed.

5. Notes

  • Submit the zip file for Lab 10 to Blackboard.

  • Lab 10 is due by Monday, 04/27/2026 at 11:59 PM (EST).

  • This is the last day of classes, so please start early and keep your reviews concise, thoughtful, and professional.