~/talk

Getting started with R when analysing Github events

Talkat Voxxed Days Vienna 2016 · 2016-03-16..03-18· [data-science]
links:none on file
slides:none on file

Uses R to parse GitHub Archive hourly JSON with readLines + jsonlite, converts each line to an event, then filters for only pull_request contains language. Analyzes one hour (about 11k events → ~500 pull_requests), finds language present in ~5% as empty/missing for several entries, deduplicates by repository id before counting, and produces a sorted frequency table and barplot. Notes sapply versus lapply type pitfalls and that the first working pipeline took about six hours to assemble.

AI-written summary · about

  1. 0:00Introduction and setup
  2. 1:58About the R ecosystem
  3. 5:16Basic R syntax and types
  4. 16:07Data structures in R
  5. 21:53Reading and processing GitHub data
  6. 26:54Handling missing values and nested data
  7. 30:47Filtering and deduplicating data
  8. 33:51Counting language distribution
  9. 36:39Summary and Q&A
~/search
type to search 6,249 conferences, 138,987 speakers and 185,172 talks
~/help
cmdctrl k
search every conference, speaker and series
/
focus the filter search
h
home
c
conferences
s
speakers
e
series
t
light / dark — the status bar button does the same
?
this help
esc
close this, then clear every filter — or just the search, while you are typing in it

Ignored while you are typing. Pages without a filter rail have no search to focus.