Dear @INFO523-S24/datadetectives : 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)
6
Code
6 (3/Question)
6
Visualization
8 (4/Question)
7
Discussion
8 (4/Question)
8
Total
30
29
Feedback:
Your Time Series plots had to be scrolled.
Dear @INFO523-S24/datadetectives : 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: Your Time Series plots had to be scrolled.