-
Notifications
You must be signed in to change notification settings - Fork 3
/
index.Rmd
114 lines (73 loc) · 9.35 KB
/
index.Rmd
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
---
output:
html_document:
toc: true
toc_depth: 3
---
<div class="container">
<div class="jumbotron" style="margin-left:-15px">
<h1 class="title">POIR 613</h1>
<h2 class="subtitle">Computational Social Science</h2>
<p>University of Southern California, Fall 2022</p>
</div>
</div>
Citizens across the globe spend an increasing proportion of their daily lives online. Their activities leave behind granular, time-stamped footprints of human behavior and personal interactions that represent a new and exciting source of data to study standing questions about political and social behavior. At the same time, the volume and heterogeneity of digital data present unprecedented methodological challenges. The goal of this course is to introduce students to new computational social science methods and tools required to explore and harness the potential of digital trace data using the R programming language.
The course will follow a "learning-by-doing" approach and will place emphasis on gaining experience in analyzing data using R. Students are expected to do the required readings and coding exercises for each week. The lectures will build upon the content of the readings with a series of data challenges that will introduce new statistical and programming concepts, which will then be applied to the analysis of data from published research papers or common tasks in computational social science. Most of the applications will be related to Political Science and International Relations questions, but the course should be of interest to social science students more generally.
# Instructor
<table class = "table table-striped">
<tr>
<td><a href="http://www.pablobarbera.com"><strong>Pablo Barberá</strong></a></td>
<td><a href="mailto:[email protected]">[email protected]</a></td>
<td><a href="https://www.twitter.com/p_barbera">@p_barbera</a></td>
</tr>
</table>
# Schedule
<table class = "table table-striped table-hover">
<tr>
<td><b>Class meetings</b></td>
<td>Wednesdays</td>
<td> 5:00–7:50 pm </td>
<td><a href="http://classes.usc.edu/maps/?b=CPA">CPA 256</a></td>
</tr>
<tr>
<td><b>Office hours</b></td>
<td>Mondays</td>
<td>4:00–5:00 pm</td>
<td><a href="https://calendar.google.com/calendar/selfsched?sstoken=UUIwOW9ET0d1c2xFfGRlZmF1bHR8MTg5MDlhYWJiNmZhZTU4MDhhY2MyNWZkOWM0MDZlZmE">Zoom - sign up here</a></td>
</tr>
<tr>
<td></td>
<td>Fridays</td>
<td>9:00–10:00 am</td>
<td><a href="https://calendar.google.com/calendar/selfsched?sstoken=UUIwOW9ET0d1c2xFfGRlZmF1bHR8MTg5MDlhYWJiNmZhZTU4MDhhY2MyNWZkOWM0MDZlZmE">Zoom - sign up here</a></td>
</tr>
</table>
Other times by appointment.
# Prerequisites
The course assumes prior knowledge of probability theory, hypothesis testing, regression analysis at the level of POIR 611 or equivalent, research design at the level of POIR 610 or equivalent, and familiarity with the R programming language. The exercises and problem sets will assume that you know how to read datasets in R, work with vectors and data frames, write simple functions and loops, and run basic statistical analyses, such as a t-test or a linear regression. More advance knowledge of maximum likelihood, causal inference, and Bayesian statistics is helpful but not required.
Students are expected to bring a laptop to class and follow along the coding section of each session. The USC Computing Center offers a <a href="https://itservices.usc.edu/spaces/laptoploaner/">Laptop Loaner Program</a> for students who may not have access to one.
# Course structure
Each session will be divided into three blocks: an introduction to a computational social science tool or method, a discussion of recent research that uses that method, and a lab component that will demonstrate how to use it with R.
The first block, led by the instructor, will be based on a set of readings from textbooks and introductory manuals. This part will assume that all students have done the readings and thus we will move quickly and focus on the most complex aspects, how these methods are embedded in the broader computational social science literature, and strengths and weaknesses that perhaps were not obvious from the readings.
The second block will feature a critical discussion of recent publications or working papers that apply these methods. Two students will prepare a two-page referee report (due the night before the class) and a 12-minute presentation during which they will discuss their assessment of the paper. All students in the class are expected to at least have skimmed the papers and be ready to ask questions or engage in the discussion.
The third part of each class will be applied. The instructor will provide code and data that illustrate the application of a specific computational social science method, followed by a "coding challenge" where students will need to apply what they have learned to a new dataset. The code and output (pdf or html file) of their coding challenge needs to be submitted via GitHub classroom before the beginning of the following class.
# Course requirements and grading
## Class participation (10%)
Students are expected to attend every session, and do the assigned readings before each session. You should come to class with questions and ready to engage in a discussion about that week's topic.
## Referee report and student presentation (20%)
Each student is expected to write TWO referee reports and present them to the rest of the class. The report should be 800-1000 words long and provide a critical evaluation of the strengths and weakness of the paper, with a particular emphasis on its methodological aspects. For some suggestions on how to write a good report, see for example this <a href="https://thepoliticalmethodologist.files.wordpress.com/2016/02/tpm_v23_n1.pdf">Special Issue on Peer Review</a> in The Political Methodologist. The presentation in class should summarize the main points in the referee report, but also go beyond its content by e.g. suggesting follow-up studies or other methods that could have been applied. The use of slides is recommended but not required. Each presentation should last no longer than 12 minutes, not including questions.
Note: The referee report will be due by <b>8pm the day before the class</b> where it will be discussed via email.
## Coding challenges (20%)
At the end of each class, the instructor will share a short problem set based on the content of that class. There will be some time during class to start working on this exercise, and to address any question, but most of it should be completed after class. Each of these coding challenges will be due before the beginning of the following class, when the solutions (or a sketch of the solution) will be posted. They will not be graded, but submitting at least FIVE of them is compulsory. A complete submission should be done via GitHub and include both the R script with the code written by the student (and comments with interpretation of the results, answering the questions) as well as a pdf/html file showing the output of compiling the code.
Late submissions will not be accepted.
## Research project (50%)
Students are required to submit an original research paper that employs any of the methods introduced in the course. The goal of this exercise is to demonstrate that you have the ability to conduct research in computational social science. This research paper can be an individual or group project (up to 3 people). For more information and deadlines for each component of the project, go to the [Project](/research_project.html) page.
# Software
This course will use [R](https://www.r-project.org/), which is a free and open-source programming language primarily used for statistics and data analysis. We will also use [RStudio](https://www.rstudio.com/), which is an easy-to-use interface to R. Make sure you install R and RStudio before the first day of class.
# License and credit
Science should be open, and this course builds up other open licensed material, so unless otherwise noted, all materials for this class are licensed under a <a rel="license" href="https://creativecommons.org/licenses/by/4.0/">Creative Commons Attribution 4.0 International License</a>.
More specifically, some of the content of this course is based on materials kindly shared by [Dan Cervone](http://dcervone.com/), [Alex Hanna](http://alex-hanna.com), [Ken Benoit](http://www.kenbenoit.net/), [Paul Nulty](https://github.com/pnulty), [Kevin Munger](https://github.com/kmunger), [Arthur Spirling](http://www.nyu.edu/projects/spirling/), [Katya Ognyanova](http://kateto.net/), [Rochelle Terman](http://rochelleterman.com/), [Justin Grimmer](http://www.justingrimmer.org/), [Karsten Donnay](http://www.karstendonnay.net/), [Zoltan Fazekas](https://zfazekas.github.io/), [Jonathan Kastellec](http://www.princeton.edu/~jkastell/), and is probably inspired by many others who have publicly released their teaching materials. I have tried to give credit to the original author of each script, but if I forgot anyone, please feel free to reach out.
The layout for this website was designed by [Jeffrey Arnold](http://www.jrnold.me/) (thanks!).
The source for the materials of this course is on GitHub at <a href="https://github.com/pablobarbera/POIR613">pablobarbera/POIR613</a>
# Feedback
If you have any feedback on the course or find any typos or errors in this website go to [issues](https://github.com/pablobarbera/POIR613/issues), click on the "New Issue" button to create a new issue, and add your suggestion or describe the problem.