ETC5521 Assignment 1

Team name: quoll

Team members:

• Jinhao Luo
• Yawen Zhang
• Brendi Ang
• Putu Saputra

Steps

3. Add your names to the README.md file on the repo.

4. You should create a new issue on the repo, that maps out how the report will be improved. Both members need to comment on the plan. There are various ways you might think about to improve the first analysis: you can brainstorm new questions to answer, different plots or calculations to answer the original questions, or even remove parts that were not effective in the previous report. Think about how elements of topics covered in weeks 4-6 might be used. Also think about what would be needed to do to finish the analysis, to be able to make some conclusions about what was learned from the analysis about the topic of the data.

5. Each team member needs to add one new question to be answered with the data, that will broaden the scope of the existing report. Write this into the revised report.

6. Finish your report, which should be structured as follows

• Introduction and motivation: Refine the original version (if necessary) to give the bigger picture of the topic of the data, and inspire the reader to learn more about the problem by reading your analysis.
• Data description, details given in 4-5.
• Analysis and Findings, refined and expanded from the original, which includes at least one plot or numerical summary for each of your questions, that helps the reader arrive at an answer. You should also write paragraphs describing the methods, summaries and findings.
• Conclusions - this is an entirely new section that summarises what was learned about the topic of the data.
• References

7. Write a brief overview of how you have improved on the original report. This needs to be done by adding a new issue to the GitHub repo, containing the summary.

8. Provide peer feedback on assigned report. You will be randomly assigned another team’s report, and be expected to reproduce their analysis, and provide constructive input on the analysis. The purpose of peer feedback is to learn how other analysts approach problems, and to help improve other analysts analyses.

• Contributed steps 1-5 to the team github repo due 11th Sep
• Final report available on repo due 18th Sep
• Peer feedback provided as an issue on your assigned group's repo due 25th Sep