You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
|[14](weeks/week-14.html)| 11-24 | Model Building + Mediation |[Chapter 15.8 - 15.10 - LSR](https://learningstatisticswithr.com/book/){target="_blank"} |[💻 Model Building](/slides/lec-14.html)| Continue Working on Final! |
|15 | 12-01 | Making R Work for You |[Chapter 17 & 18 - ST](https://statsthinking21.github.io/statsthinking21-core-site/){target="_blank"} |||
75
+
|[15](weeks/week-14.html)| 12-01 | Making R Work for You |[Chapter 17 & 18 - ST](https://statsthinking21.github.io/statsthinking21-core-site/){target="_blank"} ||Finish your Final Project|
|**Functionality & Organization**| Code runs immediately upon download without error on a fresh environment. Uses relative paths or `here()` correctly. | Code runs but requires minor troubleshooting (e.g., installing a missing package, fixing a hard-coded path like `C:/Users/...`). | Code breaks significantly, references local hard drives, or necessary files are missing from the folder. |
246
+
247
+
#### Data Preparation (20 Points)
248
+
249
+
*Focus: Did you prepare the data correctly before analyzing?*
|**Cleaning & Sampling**| Random subset (N=400) created correctly (if applicable). Cleaning steps (handling NAs, recoding variables) are justified and executed efficiently. | Subset created but method is unclear/not reproducible. Minor errors in data cleaning (e.g., missed an obvious outlier). | No subsetting performed on large data. Data is "dirty" (e.g., typos in factor levels) affecting the analysis results. |
255
+
256
+
#### Statistical Rigor (50 Points)
257
+
258
+
*Focus: Does the logic follow and build a cohesive statistical
|**Analysis Selection**| Chosen analyses (must include regression) are perfectly aligned with the research question and data type. | Analyses are generally appropriate, but a better model existed (e.g., used standard linear regression on a binary outcome). | Analysis does not address the hypothesis or is statistically invalid for the data type. |
265
+
|**Assumption Checks**| All relevant assumptions (normality, linearity, homoscedasticity, etc.) are explicitly tested, reported, and handled if violated. | Assumptions are mentioned but not thoroughly tested, or violations are noted but ignored in the final model. | Assumptions are completely ignored or misunderstood. |
266
+
|**Interpretation**| Interpretation of coefficients, p-values, confidence intervals, and effect sizes is accurate and nuanced. | Interpretation is generally correct but relies too heavily on "significance" (p<.05) rather than effect size or practical significance. | Fundamental misunderstanding of statistical output (e.g., interpreting p>.05 as "proof" of no effect). |
267
+
268
+
#### Presentation (30 Points)
269
+
270
+
*Focus: Can you synthesize the project in a concise way to an audience?*
|**Communication**| Engaging, clear, and well-paced (within 7 min). Speaker demonstrates mastery of the material during Q&A. | Clear but relies heavily on reading notes. Slightly over or under the time limit. | Reading directly from slides (wall of text). Unable to answer basic questions about their own study. |
276
+
|**Visual Aids**| Slides are visual-heavy and support the narrative. Graphs are clean, large, and legible. | Slides are text-heavy. Graphs are present but small, pixelated, or unformatted default outputs. | Slides are disorganized, confusing, or missing. |
277
+
278
+
#### Written Report Content (60 Points)
279
+
280
+
*Focus: Can you communicate the findings in a written format?*
|**Introduction & Logic**| Clear narrative arc from problem identification to hypothesis. Citations (3+) are highly relevant and integrated well. | Hypothesis is stated, but the background justification is weak, disjointed, or citations are loosely related. | Hypothesis is missing or unclear. Introduction is disorganized or lacks citations. |
286
+
|**Formatting (APA)**| Tables and Figures are perfect APA style. **No raw code output** (e.g., R console text) in the document. Prose is professional and academic. | Minor APA errors in tables/figures. Some raw software output included in the text. | Major formatting errors. Figures are unreadable, missing labels, or screen-capped from software. |
287
+
|**Discussion**| Deeply contextualizes results within the field. Discusses limitations honestly and provides insightful future directions. | Summarizes results well but lacks depth in "implications." Limitations are generic (e.g., "sample size could be bigger"). | Discussion just repeats the results section in words. No limitations mentioned. |
title: "Week 15 - Having R Work for You: wRapping up"
3
+
editor: visual
4
+
---
5
+
6
+
We are almost at the end of the course! This week, we will be focusing on some random things related to R that could make things easier. Plus, there will be time for working on your final project, helping your peers and "office hours".
7
+
8
+
## Data for Today
9
+
10
+
We may have a demo of a workflow. In that case, we will be able to pick some data from this website below. I think the DASS (Depression, Anxiety and Stress Scale) dataset would be a good candidate.
0 commit comments