Closed johann-wagner closed 9 months ago
If you’re doing something that isn’t exactly EDA, then use the report to describe and summarise what you’ve done. For example, if you write an R package then your report could summarise what it does and how it works.
It doesn’t matter if you don’t quite end up answering your original questions/aims. Science is hard, and if we knew the answer already it wouldn’t be research. Just tell us what you find that is interesting!
Your main report should contain R chunks interspersed with prose which summarise your work (e.g. your EDA, or your R package or Shiny App). We don’t have time to wade through 1000’s of plots and repetitive lines of code, though I appreciate that this is how EDA actually works! If you do want to record everything that you did, you are welcome to set up a separate .Rmd file for that. Please call this file EDA.Rmd.
Please use the template below for your final_project.Rmd file. You must retain all of the headings below. You are free to use whatever subheadings you like in the “Exploratory Data Analysis” section. After each heading I have briefly described what that section should contain. Please delete these descriptions in your report. If you choose to do something that is not exactly an Exploratory Data Analysis (e.g. build an R package), please change this heading (and only this heading) appropriately. The rest of the rules still apply.
Mostly finish addressing your questions
Detailed guidelines are in the final report instructions on wattle. But here are a few key things:
Your write-up is a summary of your work, not everything you did!
Word limit is 2000 words including code and references
You must count these with the word_count() function in provided in the instructions
Figure limit is 10 figures
Composite figures are OK, but consider the principles of data visualisation
If you go beyond the word/figure limit, we will stop reading/looking at when we hit the limit, all additional words/figures will be treated as if they weren’t there