Write-up feedback

[Gchism94]

Dear MineCrafters: 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	1.5
Justification of approach	6 (3/Question)	6
Code	6 (3/Question)	5
Visualization	8 (4/Question)	8
Discussion	8 (4/Question)	6
Total	30	26.5

Feedback: Introduction: your intro and abstract should be flipped. The abstract is much more informative. Code: you should have been able to suppress warnings and messages. They made the approach section very difficult to read. Discussion: the discussion should have also answered the question along with insight into why the approach worked and was appropriate.

[partha-pkp]

Hi Dr. Greg,

Thank you for the feedback!