Dear @lestrada: Below is the score breakdown for your write-up. Details of things that should be updated/revised are provided in separate issues. As you address them, you should close the individual issues.
You can do this in one of two ways:
On GitHub, by clicking on Close issue
Via a commit that directly addresses the issue.
Please use the second method wherever a fix can be tied to a commit. If you preface your commit messages with "Fixes", "Fixed", "Fix", "Closed", or "Close", the issue will be closed when you push the changes to your repo. For example, suppose you want to close issue #2 which, hypothetically, suggested that you add a new line to the README, your commit message can say something like Add a new line to the README, closes #2.
Once you've closed all of the other issues, close this one as well, so that going into the presentation you have no open issues remaining.
Write-up
Available
Earned
Introduction
2
2
Justification of approach
6 (3/Question)
4
Code
6 (3/Question)
6
Visualization
8 (4/Question)
6
Discussion
8 (4/Question)
6
Total
30
25
Feedback:
Justification of approach: I am missing the "why" in your project. Why is it important to know these patterns.
Visualization: I found the unordered bar chart difficult to determine patterns from. It would make more sense to order everything by favorite. Also, there was redundancy from having both the legend and the y-axis (remember this from hw-01). You also did not create unique titles for this chart, which I expected even from exploratory plots.
Discussion: The discussion did not give me insights into greater implications of the results.
Dear @lestrada: Below is the score breakdown for your write-up. Details of things that should be updated/revised are provided in separate issues. As you address them, you should close the individual issues.
You can do this in one of two ways:
Please use the second method wherever a fix can be tied to a commit. If you preface your commit messages with "Fixes", "Fixed", "Fix", "Closed", or "Close", the issue will be closed when you push the changes to your repo. For example, suppose you want to close issue
#2which, hypothetically, suggested that you add a new line to the README, your commit message can say something likeAdd a new line to the README, closes #2.Once you've closed all of the other issues, close this one as well, so that going into the presentation you have no open issues remaining.
Write-up
Feedback: Justification of approach: I am missing the "why" in your project. Why is it important to know these patterns. Visualization: I found the unordered bar chart difficult to determine patterns from. It would make more sense to order everything by favorite. Also, there was redundancy from having both the legend and the y-axis (remember this from hw-01). You also did not create unique titles for this chart, which I expected even from exploratory plots. Discussion: The discussion did not give me insights into greater implications of the results.