Network Analysis Reading Group
Switch branches/tags
Nothing to show
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
resources
LICENSE
README.md

README.md

Introduction

Welcome! This is the course page for the Network Analysis Reading Group (NARG), organized by Robert Shaffer and Zac McGee. You can find the course materials, syllabus, and other useful links and information here. We'll update this repository as needed throughout the semester, so be sure to check back regularly.

Philosophy

This reading group is participant-organized and taught, and it'll succeed (or fail) based on participant input and effort. As a result, we're expecting everyone to come prepared, to participate, and to complete the readings for each week. Some parts of the semester are busier than others, and if you can't make a meeting or two, it's not the end of the world. But, if you decide to participate, please view this reading group as a semester-long commitment!

Format

Each meeting will be led by one participant, who will begin with a lightning talk on their topic. Next, we'll discuss the week's papers as a group, and identify sources of confusion, potential applications, and critiques. Finally, the week's leader will present an applied example based on the week's topic. If course demand is high enough, two participants may split leadership duties.

Logistics

Meetings once per week, Thursdays 2-3pm. Most meetings will be in the Glickman Conference Center (CLA 1.302D), though a few meetings may need to be moved or rescheduled based on room availability. Based on demand and material, we may hold an optional half-hour mathematics section some weeks, in which more mathematically inclined participants can dive into the details of the week's concepts.

Duties

Leaders

  1. Select the week's applied paper and applied example.
  • Course organizers will suggest papers for each week, but the week's leader should feel free to select something different.
  • Leaders should send their materials to the organizers at least one week in advance, to give others time to look them over.
  1. Give a brief lightning talk on the week's topic.
  • Lightning talks should be about 5 minutes long, with no more than 5 slides.
  • The talk should introduce the topic, its significance, and the week's application.
  1. Walk the group through the week's applied example.
  • The application section should be about 10-15 minutes long, and should contain a live demonstration (e.g. R/Python code, standalone software environment).
  • Applications should be accompanied with documentation, so others can follow along.
  • We strongly encourage leaders to develop their own examples, rather than taking examples from elsewhere on the web. We'll all learn more by presenting and inspecting our own code!

Weekly leaders are not expected to be experts on their topic, but should be knowledgable about their assigned material and the applied example they prepare. Prepare for your week as session leader with the same level of care that you'd prepare for a seminar course meeting, and you'll be in good shape.

Participants

  1. Prepare
  • Show up each week.
  • Do the week's reading, and skim the week's applied example.
  • Try to look over a few of the supplementary resources.
  1. Participate
  • Speak up during the group meeting. We're all learning this material together, so if you're confused, others are likely confused as well.
  • If you know of any useful outside materials, suggest them to the organizers so we can add them to this repository!

Textbooks

For participants wishing to do some outside reading on their own, one or more of these textbooks may be helpful. Hyperlinks are included for texts that are available online.

List of topics

Weekly leaders and required readings are given in parentheticals following each topic heading. See each week's folder in the resources section for additional resources. Topic dates are approximate, and may be shifted depending on demand and scheduling.

Software

As a general rule, many software packages will work more easily with Unix-like operating systems (OSX; Linux) than with Windows. Check the documentation and requirements for each package carefully if you encounter issues!