| Your team name | To review 1 | To review 2 |
|---|---|---|
| Section 1 - M 10:15 - 11:30 am | ||
| Alpha equals one | Seven | Sealteam6 |
| 2cool4school | Alpha equals one | Seven |
| ggplot3 | 2cool4school | Alpha equals one |
| Cuatro | ggplot3 | 2cool4school |
| Cinco | Cuatro | ggplot3 |
| Sealteam6 | Cinco | Cuatro |
| Seven | Sealteam6 | Cinco |
| Section 2 - M 1:45 - 3:00 pm | ||
| Blue Squirrels | Who's your data? | Suffer |
| Stats R Us | Blue Squirrels | Who's your data? |
| Team300 | Stats R Us | Blue Squirrels |
| geom_slay | Team300 | Stats R Us |
| Suffer | geom_slay | Team300 |
| Who's your data? | Suffer | geom_slay |
| Section 3 - M 3:30 - 4:45 pm | ||
| Cool Kids | Seven Wonders | Mine's Minions |
| Meteors | Cool Kids | Seven Wonders |
| Green Team | Meteors | Cool Kids |
| Fantastic Four | Green Team | Meteors |
| Theta-Five | Fantastic Four | Green Team |
| Mine's Minions | Theta-Five | Fantastic Four |
| Seven Wonders | Mine's Minions | Theta-Five |
| Section 4 - M 5:15 - 6:30 pm | ||
| Merge Conflicts | group_by(6) | Git Freaky |
| Quart2 | Merge Conflicts | group_by(6) |
| Git Real | Quart2 | Merge Conflicts |
| Kameron Krazies | Git Real | Quart2 |
| Git Freaky | Kameron Krazies | Git Real |
| group_by(6) | Git Freaky | Kameron Krazies |
| Section 5 - M 12:00 - 1:15 pm | ||
| Women in Tech | Split Ends | Super Raspberries |
| Stats Sisters | Women in Tech | Split Ends |
| The Outliers | Stats Sisters | Women in Tech |
| Duke Data Devils | The Outliers | Stats Sisters |
| Super Raspberries | Duke Data Devils | The Outliers |
| Split Ends | Super Raspberries | Duke Data Devils |
Lab - Project peer review
Lab
Important
The project peer review is due at the end of your lab section on Monday, Nov 28. No submission on Gradescope needed, just post issues on GitHub by this time.
Learning goals
In this lab, you will…
- Review others’ project drafts as a team and provide feedback
- Post issues on GitHub using an issue template
- Learn from others’ projects and improve your own project based on their strengths and weaknesses
Project peer review
Each team will review two other teams’ project. As a team you should spend ~30 minutes on each team’s project.
Find the names of the teams whose projects you’re reviewing below. You should already have access to this team's repo.
Each team member should go to the repo of the team you’re reviewing.
Then,
1-2 team members clone the team’s project and renders it to check for reproducibility.
1-2 team members open the team’s project in their browser and starts reading through the project draft.
1 team member opens an issue on the team’s repo using the peer review template.
All team members discuss the project based on the prompts on the issue template and one team member records the feedback and submits the issue.
To open an issue in the repo you’re reviewing, click on New issue, and click on Get started for the Peer review issue. Fill out this issue, answering the following questions:
Peer review by: [NAME OF TEAM DOING THE REVIEW]
Names of team members that participated in this review: [FULL NAMES OF TEAM MEMBERS DOING THE REVIEW]
Describe the goal of the project.
Describe the data used or collected, if any. If the proposal does not include the use of a specific dataset, comment on whether the project would be strengthened by the inclusion of a dataset.
Describe the approaches, tools, and methods that will be used.
Provide constructive feedback on how the team might be able to improve their project. Make sure your feedback includes at least one comment on the statistical reasoning aspect of the project, but do feel free to comment on aspects beyond the reasoning as well.
What aspect of this project are you most interested in and would like to see highlighted in the presentation.
Were you able to reproduce the project by clicking on Render Website once you cloned it? Were there any issues with reproducibility?
Provide constructive feedback on any issues with file and/or code organization.
What have you learned from this team’s project that you are considering implementing in your own project?
(Optional) Any further comments or feedback?
Review pairings
Grading
Peer reviews will be graded on the extent to which it comprehensively and constructively addresses the components of the reviewee’s team’s report.
Only the team members participating in the review during the lab session are eligible for points for the peer review. If you’re unable to make it to lab in person, you should arrange to virtually connect with your team during your lab session.
0 points: No peer review
1 point: Only one peer review issue open, feedback provided is not constructive or actionable
2 points: Both peer review issues open, feedback provided is not constructive or actionable
3 points: Both peer review issues open, feedback provided is not sufficiently thorough
4 points: Both peer review issues open, one of the reviews is not sufficiently thorough
5 points: Both peer review issues open, both reviews are constructive, actionable, and sufficiently thorough
Note
The feedback issue will come from one team member on GitHub since you can’t collectively edit an issue. However it must represent the opinions of the entire team. It is not a single team member’s responsibility to provide feedback, they’re just the record keeper for the team.