-
Notifications
You must be signed in to change notification settings - Fork 0
/
big_picture.qmd
128 lines (86 loc) · 4.64 KB
/
big_picture.qmd
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
---
title: "Big Picture"
description: "A 538/Upshot style article about the data."
toc: true
draft: FALSE
format:
html:
resources:
- shinylive-sw.js
filters:
- shinylive
---
This comes from the file `big_picture.Rmd`.
Think of this page as your 538/Upshot style article. This means that you should try to tell a story through the data and your analysis. Read articles from those sites and similar sites to get a feeling for what they are like. Try to write in the style of a news or popular article. Importantly, this page should be geared towards the general public. You shouldn't assume the reader understands how to interpret a linear regression or a complicated plot. Focus on interpretation and visualizations.
---
### Interactive
You will also be required to make an interactive dashboard like [this one](/flex/flex.html).
Your Big Data page should also include a small interactive dashboard. The dashboard should be created either using Shinylive, as below. This interactive component should in some way support your thesis from your big picture page. Good interactives often provide both high-level understanding of the data while allowing a user to investigate specific scenarios, observations, subgroups, etc.
```{shinylive-r}
#| standalone: true
#| viewerHeight: 640 # You will have to adjust this to fit everything
library(shiny)
library(tidyverse)
options("readr.edition" = 1) # keep this to ensure you can download the data
# Define UI for app that draws a histogram ----
ui <- fluidPage(
# App title ----
titlePanel("Hello Shiny!"),
# Sidebar layout with input and output definitions ----
verticalLayout(
# Input: Slider for the number of bins ----
sliderInput(inputId = "bins",
label = "Number of bins:",
min = 1,
max = 50,
value = 30),
# Output: Histogram ----
plotOutput(outputId = "distPlot")
)
)
# Define server logic required to draw a histogram ----
server <- function(input, output) {
# The URL below has to point to a dataset on your github pages website
# I recommend creating a small-ish rds file that has only the data relevant to
# the interactive.
data <- read_rds("https://sussmanbu.github.io/ma4615-final-project-quarto/dataset/loan_refusal_clean.rds")
output$distPlot <- renderPlot({
ggplot(data, aes(x = refusal_rate)) +
geom_histogram(bins = input$bins + 1)
})
}
# Create Shiny app ----
shinyApp(ui = ui, server = server)
```
---
## Rubric: On this page
You will
* Title
* Your big picture page should have a creative/click-bait-y title/headline that provides a hint about your thesis.
* Clarity of Explanation
* You should have a clear thesis/goal for this page. What are you trying to show? Make sure that you explain your analysis in detail but don't go into top much mathematics or statistics. The audience for this page is the general public (to the extent possible). Your thesis should be a statement, not a question.
* Each figure should be very polished and also not too complicated. There should be a clear interpretation of the figure so the figure has a clear purpose. Even something like a histogram can be difficult to interpret for non-experts.
* Creativity
* Do your best to make things interesting. Think of a story. Think of how each part of your analysis supports the previous part or provides a different perspective.
* Interactive component
* Quality and ease of use of the interactive components.
Is it clear what can be explored using your interactive components?
Does it enhance and reinforce your conclusions?
* This page should be self-contained.
**Note**: This page should have no code visible, i.e. use `#| echo: FALSE`.
## Rubric: Other components
### Video Recording
Make a video recording (probably using Zoom) demonstrating your interactive components.
You should provide a quick explanation of your data and demonstrate some of the conclusions from your EDA.
This video should be no longer than 4 minutes.
Include a link to your video (and password if needed) in your README.md file on your Github repository. You are not required to provide a link on the website.
This can be presented by any subset of the team members.
### Rest of the Site
Finally, here are important things to keep in mind for the rest of the site.
The main title of your page is informative.
Each post has an author/description/informative title.
All lab required posts are present.
Each page (including the home page) has a nice featured image associated with it.
Your about page is up to date and clean.
You have removed the generic posts from the initial site template.