<p><div><div><div><div data-show-faces="false" data-height="21" data-width="100" data-layout="button_count" data-send="true" data-href="https://www.r-bloggers.com/a-tidytext-analysis-of-the-weinstein-effect/"></div></div><div></div></div><div></div></div>
<div>
(This article was first published on <strong><a href="https://www.gokhanciflikli.com/post/weinstein-effect/"> Computational Social Science</a></strong>, and kindly contributed to <a rel="nofollow" href="https://www.r-bloggers.com/">R-bloggers)</a> </div>
<div>
<h3>Quantifying He-Said, She-Said: Newspaper Reporting</h3>
<p>I have been meaning to get into quantitative text analysis for a while. I initially planned this post to feature a different package (that I wanted to showcase), however I ran into some problems with their .json parsing methods and currently waiting for the issue to be solved on their end. The great thing about doing data science with R is that there are multiple avenues leading you to the same destination, so let’s take advantage of that.</p>
<p>My initial inspiration came from David Robinson’s post on <a rel="nofollow" href="http://varianceexplained.org/r/tidytext-gender-plots/" target="_blank">gendered verbs</a>. I remember sending it around and thinking it was quite cool. Turns out he was building on Julia Silge’s earlier post on <a rel="nofollow" href="https://juliasilge.com/blog/gender-pronouns/" target="_blank">gender pronouns</a>. I see that post and I go, ‘what a gorgeous looking ggplot theme!’. <em>So. Neat.</em> Praise be the open source gods, the code is on GitHub. Let’s take advantage of that too.</p>
<p>I still needed a topic, and even though both the <a rel="nofollow" href="https://github.com/markriedl/WikiPlots" target="_blank">Wikipedia plots</a> and the <a rel="nofollow" href="https://cran.r-project.org/web/packages/janeaustenr/index.html" target="_blank">Jane Austen</a> datasets sound interesting to look at, I felt that there is another, obvious choice. It has a <a rel="nofollow" href="https://en.wikipedia.org/wiki/Weinstein_effect" target="_blank">Wikipedia page</a> and its own <a rel="nofollow" href="https://www.reddit.com/r/WeinsteinEffect/" target="_blank">subreddit</a>. Also, the title might have given it away. Let’s get to work.</p>
</div>
<div>
<h3>Getting Full Text News Articles</h3>
<div><img src="https://i2.wp.com/www.gokhanciflikli.com/img/guardian.png?w=456&ssl=1" data-recalc-dims="1"></div>
<p>My first instinct was to check out the <a rel="nofollow" href="http://developer.nytimes.com/" target="_blank">NYT APIs</a>—it made sense, given that they <a rel="nofollow" href="https://www.nytimes.com/2017/10/05/us/harvey-weinstein-harassment-allegations.html?_r=0" target="_blank">broke the news</a> (along with the <a rel="nofollow" href="https://www.newyorker.com/news/news-desk/from-aggressive-overtures-to-sexual-assault-harvey-weinsteins-accusers-tell-their-stories" target="_blank">New Yorker</a>). Everything seemed to be working out just fine, until I realised you cannot get the full text—only the lead. Staying true to my strict data scientist training, I googled ‘full text newspaper api r’ and there it was: <code>GuardianR</code>. Sorry NYC mates, we reckon we will have to cross the pond for this one.</p>
<p>Note that any one source will always be biased. If you are not familiar with the Guardian, it’s British and has a <a rel="nofollow" href="https://mediabiasfactcheck.com/the-guardian/" target="_blank">left-centre bias</a>. It might be prudent to pair it with a right-centre newspaper, however not all newspapers provide APIs (which in itself is another selection bias). Alas, we will move on just with the Guardian—insert idiom regarding salt. Finally, you will need to get a free API key from their <a rel="nofollow" href="http://open-platform.theguardian.com/" target="_blank">open source platform</a>. You still have to register, but you are only in danger if you vote Tory and stand on the left side of the escalator. Once you got it, install/load the package via CRAN:</p>
<pre><code>library(GuardianR)
ls(pos = &quot;package:GuardianR&quot;)</code></pre>
<pre><code>## [1] &quot;get_guardian&quot;     &quot;get_json&quot;         &quot;parse_json_to_df&quot;</code></pre>
<p>As you can see, the <code>GuardianR</code> package is a simple one: it contains only three (but powerful) functions. We only need the first one to get a hold of the full text articles, and the syntax is super simple:</p>
<pre><code>#not evaluated
articles &lt;- get_guardian(keywords = &quot;sexual+harassment&quot;,
                         section = &quot;world&quot;,
                         from.date = &quot;2012-11-30&quot;,
                         to.date = &quot;2017-11-30&quot;,
                         api.key = &quot;your-key-here&quot;)</code></pre>
<p>Running the above chunk with your own key will get you all articles published in the Guardian in the last five years tagged under the news section ‘world’ and containing the keywords ‘sexual harassment’ in the Guardian API. The keywords can be as simple or complicated as you want; just add more terms using the plus sign.</p>
<p>You might think the time frame is a bit skewed towards the ‘pre’ era—the news broke out on October 5, 2017. Going all the way back five full years, we are comparing 58 months worth of ‘pre’ to only 2 months of ‘post’ Weinstein. However, luckily for you blog posts are not written in real-time, meaning you get to see a (somewhat working) final result so just bear with me. And no, this is not at all like scientists running 514 regressions and failing to mention this tidbit in their publication. <a rel="nofollow" href="https://xkcd.com/882/" target="_blank">Relevant xkcd.</a></p>
<p>No, the reason is pure pragmatism. It’s not that running the code ‘live’ and getting the articles ‘real-time’ would not slow down this page—it’s not how it works. However, it is good practice to extract a tad bigger chunk than you think you will need, as you can always slice it up later to suit your needs better.</p>
<p>In any case, I am working with downloaded data so I will just load it up. Feel free to subset the data to see whether the results change if you use a different cut-off point. Also, if you go back the same amount of time (i.e. two months before October 5), that would lead to 183 articles for pre and 121 articles for the post time period—it is a reckoning, alright. Going back five years gets us 1224 articles in total; so we actually have 1103-pre and 121-post articles (89% to 11%). That’s more or less cross-validation ratio (well, a bit on the less side maybe), and we will roll with that for now.</p>
<pre><code>articles &lt;- read.csv(&quot;articles.csv&quot;, stringsAsFactors = FALSE)
dim(articles)</code></pre>
<pre><code>## [1] 1224   27</code></pre>
<pre><code>sum(articles$wordcount)</code></pre>
<pre><code>## [1] 1352717</code></pre>
<pre><code>colnames(articles)</code></pre>
<pre><code>##  [1] &quot;id&quot;                   &quot;sectionId&quot;            &quot;sectionName&quot;         
##  [4] &quot;webPublicationDate&quot;   &quot;webTitle&quot;             &quot;webUrl&quot;              
##  [7] &quot;apiUrl&quot;               &quot;newspaperPageNumber&quot;  &quot;trailText&quot;           
## [10] &quot;headline&quot;             &quot;showInRelatedContent&quot; &quot;lastModified&quot;        
## [13] &quot;hasStoryPackage&quot;      &quot;score&quot;                &quot;standfirst&quot;          
## [16] &quot;shortUrl&quot;             &quot;wordcount&quot;            &quot;commentable&quot;         
## [19] &quot;allowUgc&quot;             &quot;isPremoderated&quot;       &quot;byline&quot;              
## [22] &quot;publication&quot;          &quot;newspaperEditionDate&quot; &quot;shouldHideAdverts&quot;   
## [25] &quot;liveBloggingNow&quot;      &quot;commentCloseDate&quot;     &quot;body&quot;</code></pre>
<p>We get a bunch of variables (27) with that call, but we won’t be needing most of them for our analysis:</p>
<pre><code>#laziest subset for only two variables
want.var &lt;- c(&quot;webPublicationDate&quot;, &quot;body&quot;)
want &lt;- which(colnames(articles) %in% want.var)
articles &lt;- articles[, want]
articles$webPublicationDate &lt;- as.Date.factor(articles$webPublicationDate)</code></pre>
<p>The body contains the full-text, however it’s in HTML:</p>
<pre><code>dplyr::glimpse(articles$body[1])</code></pre>
<pre><code>##  chr &quot;</code><p>Numerous women have accused Don Burke of indecent assault, sexual harassment and bullying during the 1980s a&quot;| __truncated__</p></pre>
<p>At this point, I must admit I resorted to hacking a bit. I’m sure there is a more elegant solution here. I’ll go with this <a rel="nofollow" href="https://stackoverflow.com/a/17227415/6550364" target="_blank">SO answer</a> to extract text from HTML. Basically, the cleaning function removes the HTML using regex. Unfortunately, this does not clear up various apostrophes found in the text. For that, we switch the encoding from ASCII to byte:</p>
<pre><code>articles$body &lt;- iconv(articles$body, &quot;&quot;, &quot;ASCII&quot;, &quot;byte&quot;)</code></pre>
<pre><code>cleanFun &lt;- function(htmlString) {
  return(gsub(&quot;&lt;.*?>&quot;, &quot;&quot;, htmlString))
}

articles$body &lt;- cleanFun(articles$body)
dplyr::glimpse(articles$body[1])</code></pre>
<pre><code>##  chr &quot;Numerous women have accused Don Burke of indecent assault, sexual harassment and bullying during the 1980s and &quot;| __truncated__</code></pre>
<p>This will end up cutting some legitimate apostrophes (e.g. “hasn’t”, “didn’t” to “hasn”, “didn”) in some cases, but we will fix that later on.</p>
<p>Let’s split the data on date October 5, 2017 and get rid of the date column afterwards:</p>
<pre><code>#You can also use negative index for subsetting
articles.before &lt;- articles[articles$webPublicationDate &lt; &quot;2017-10-05&quot;, ]
articles.after &lt;- articles[articles$webPublicationDate >= &quot;2017-10-05&quot;, ]

full.text.before &lt;- articles.before[, 2]
full.text.before &lt;- as.data.frame(full.text.before)

full.text.after &lt;- articles.after[, 2]
full.text.after &lt;- as.data.frame(full.text.after)</code></pre>
</div>
<div>
<h3>N-Grams and Combinatorics</h3>
<p>To me, n-grams are what prisoner’s dilemma to college freshman—that ‘wow, so simple but so cool’ moment. As in, simple <em>after</em> the fact when someone has already figured it out and explained it to you. N-grams are essentially combinations of <em>n</em> words. For example, a bigram (2-gram). Using the <code>tidytext</code> package developed by David and Julia, we can create them in a flash with <code>unnest_tokens</code>. After that, we will separate the bigrams into two distinct words. Next, we will subset the bigrams so that the first word is either he or she. Finally, we will transform the words into frequency counts. I’m heavily recycling their code—no need to reinvent the wheel:</p>
<pre><code>library(tidytext)
library(tidyverse) #or just dplyr and tidyr if you are allergic

#Create bigrams
bigrams.before &lt;- full.text.before %>%
  unnest_tokens(bigram,
                full.text.before,
                token = &quot;ngrams&quot;,
                n = 2)
nrow(bigrams.before)</code></pre>
<pre><code>## [1] 1311051</code></pre>
<pre><code>head(bigrams.before)</code></pre>
<pre><code>##        bigram
## 1    the walk
## 1.1 walk from
## 1.2  from the
## 1.3  the gare
## 1.4   gare du
## 1.5   du nord</code></pre>
<pre><code>#Separate bigrams into two words
bigrams.separated.before &lt;- bigrams.before %>%
  separate(bigram, c(&quot;word1&quot;, &quot;word2&quot;), sep = &quot; &quot;)

head(bigrams.separated.before)</code></pre>
<pre><code>##     word1 word2
## 1     the  walk
## 1.1  walk  from
## 1.2  from   the
## 1.3   the  gare
## 1.4  gare    du
## 1.5    du  nord</code></pre>
<pre><code>#Subset he and she in word1
he.she.words.before &lt;- bigrams.separated.before %>%
  filter(word1 %in% c(&quot;he&quot;, &quot;she&quot;))

#Fix the missing t's after apostrophe
fix.apos &lt;- c(&quot;hasn&quot;, &quot;hadn&quot;, &quot;doesn&quot;, &quot;didn&quot;, &quot;isn&quot;, &quot;wasn&quot;, &quot;couldn&quot;, &quot;wouldn&quot;)
he.she.words.before &lt;- he.she.words.before %>%
  mutate(word2 = ifelse(word2 %in% fix.apos, paste0(word2, &quot;t&quot;), word2))
  
#10 random samples; the numbers are row numbers not counts
set.seed(1895)
dplyr::sample_n(he.she.words.before, 10)</code></pre>
<pre><code>##       word1  word2
## 4403    she doesnt
## 3732     he    was
## 5222    she  wasnt
## 11862   she   said
## 3972    she  wrote
## 3189     he   says
## 3952    she   sees
## 4878     he    was
## 9314     he   went
## 9408    she  noted</code></pre>
<pre><code>#Transform words into counts, add +1 for log transformation
he.she.counts.before &lt;- he.she.words.before %>%
  count(word1, word2) %>%
  spread(word1, n, fill = 0) %>%
  mutate(total = he + she,
         he = (he + 1) / sum(he + 1),
         she = (she + 1) / sum(she + 1),
         log.ratio = log2(she / he),
         abs.ratio = abs(log.ratio)) %>%
  arrange(desc(log.ratio))

#Top 5 words after she
head(he.she.counts.before)</code></pre>
<pre><code>## # A tibble: 6 x 6
##       word2           he          she total log.ratio abs.ratio
##       </code></pre>
<p>A couple of observations. First, n-grams overlap, resulting in 1.6M observations (and this is only the pre-period). However, we will only use the gendered subset, which is much more smaller in size. Second, as we define the log ratio as (she / he), the sign of the log ratio determines the direction (positive for she, negative for he), while the absolute value of the log ratio is just the effect size (without direction).</p>
<p>Good stuff, no? Wait until you see the visualisations.</p>
</div>
<div>
<h3>Let There Be GGraphs</h3>
<p>Both David and Julia utilise neat data visualisations to drive home their point. I especially like the roboto theme/font, so I will just go ahead and use it. You need to install the fonts separately, so if you are missing them you will get an error message.</p>
<pre><code>devtools::install_github(&quot;juliasilge/silgelib&quot;)
#Required Fonts
#https://fonts.google.com/specimen/Roboto+Condensed
#https://fonts.google.com/specimen/Roboto
library(ggplot2)
library(ggrepel)
library(scales)
library(silgelib) 
theme_set(theme_roboto())</code></pre>
<p>We are also loading several other libraries. In addition to the usual suspects, <code>ggrepel</code> will make sure we can plot overlapping labels in a bit nicer way. Let’s start by looking at the most gendered verbs in articles on sexual harassment. In other words, we are identifying which verbs are most skewed towards one gender. I maintain the original logarithmic scale, so the effect sizes are in magnitudes and easy to interpret. If you read the blog posts, you will notice that Julia reports a unidirectional magnitude (relative to she/he), so her scales go from</p>
<p><code>.25x   .5x   x   2x    4x</code></p>
<p>whereas David uses directions, i.e.</p>
<p><code>'more he'    4x    2x    x   2x    4x    'more she'</code></p>
<p>In both cases, x denotes the same frequency (equally likely) of usage. I don’t think one approach is necessarily better than the other, but I went with David’s approach. Finally, I filter out non-verbs plus ‘have’ and only plot verbs that occur at least five times. If you are serious about filtering out (or the opposite, filtering on) classes of words—say a certain sentiment or a set of adjectives—you should locate a dictionary from an NLP package and extract the relevant words from there. Here, I am doing it quite ad-hoc (and manually):</p>
<pre><code>he.she.counts.before %>%
  filter(!word2 %in% c(&quot;himself&quot;, &quot;herself&quot;, &quot;ever&quot;, &quot;quickly&quot;,
                       &quot;actually&quot;, &quot;sexually&quot;, &quot;allegedly&quot;, &quot;have&quot;),
         total >= 5) %>%
  group_by(direction = ifelse(log.ratio > 0, 'More &quot;she&quot;', &quot;More 'he'&quot;)) %>%
  top_n(15, abs.ratio) %>%
  ungroup() %>%
  mutate(word2 = reorder(word2, log.ratio)) %>%
  ggplot(aes(word2, log.ratio, fill = direction)) +
  geom_col() +
  coord_flip() +
  labs(x = &quot;&quot;,
       y = 'Relative appearance after &quot;she&quot; compared to &quot;he&quot;',
       fill = &quot;&quot;,
       title = &quot;Pre Weinstein: 2012-17 The Guardian Articles on Sexual Harassment&quot;,
       subtitle = &quot;Top 15 Most Gendered (Skewed) Verbs after he/she; at least 5 occurrences.&quot;) +
  scale_y_continuous(labels = c(&quot;8X&quot;, &quot;6X&quot;, &quot;4X&quot;, &quot;2X&quot;, &quot;Same&quot;, &quot;2X&quot;, &quot;4X&quot;, &quot;6X&quot;, &quot;8X&quot;),
                     breaks = seq(-4, 4)) +
  guides(fill = guide_legend(reverse = TRUE)) +
  expand_limits(y = c(-4, 4))</code></pre>
<p><img src="https://i1.wp.com/www.gokhanciflikli.com/post/2017-12-02-weinstein-effect_files/figure-html/unnamed-chunk-11-1.png?w=450&ssl=1" data-recalc-dims="1"></p>
<p>Several immediate and depressing trends emerge from the data. The top active verbs for women cluster on bringing charges: ‘testified’, ‘filed’; whereas male verbs seem to react to those with ‘argued’, ‘faces’, ‘acknowledges’, and ‘apologized’. Women ‘awoke’ and ‘woke’, matching the more violent male verbs such as ‘drugged’, ‘assaulted’, ‘punched’, and ‘raped’. ‘Alleged’ occurs four times more after she relative to he, and there is no mention of denial (e.g. ‘denied’, ‘denies’) after he. A note on word variations: in some cases, it might be better to combine conjugations into a single category using a wildcard (such as expect* in the graph above). However, I thought the tense can also contribute to a quantitative story, so I left them as they are.</p>
<p>Another way of visualising the gendered differences is to plot their magnitude in addition to their frequency. This time, we are not limited to just verbs; however we still filter out some uninteresting words. There are additional <code>ggplot</code> and <code>ggrepel</code> arguments in this plot. First, I added two reference lines: a red y-intercept with <code>geom_hline</code> to act as a baseline and an invisible x-intercept using <code>geom_vline</code> to give the labels more space on the left-hand side. Do you not love tidy grammar? Last but not least, I insert <code>geom_text_repel</code> to give us more readability: <code>segment.alpha</code> controls the line transparency, while the <code>force</code> argument governs the aggressiveness of the jittering algorithm. We could supply it with a <code>fill</code> argument that corresponds to a factor variable to highlight a certain characteristic (say, total occurrence), however there is not much meaningful variation there in our case.</p>
<pre><code>he.she.counts.before %>%
  filter(!word2 %in% c(&quot;himself&quot;, &quot;herself&quot;, &quot;she&quot;, &quot;too&quot;, &quot;later&quot;, &quot;apos&quot;, &quot;just&quot;, &quot;says&quot;),
         total >= 10) %>%
  top_n(100, abs.ratio) %>%
  ggplot(aes(total, log.ratio)) +
  geom_point() +
  geom_vline(xintercept = 5, color = &quot;NA&quot;) +
  geom_hline(yintercept = 0, color = &quot;red&quot;) +
  scale_x_log10(breaks = c(10, 100, 1000)) +
  geom_text_repel(aes(label = word2), segment.alpha = .1, force = 2) +
  scale_y_continuous(breaks = seq(-4, 4),
                     labels = c('8X &quot;he&quot;', '6X &quot;he&quot;', '4X &quot;he&quot;', '2X &quot;he&quot;', &quot;Same&quot;,
                                '2X &quot;she&quot;', '4X &quot;she&quot;', '6X &quot;she&quot;', '8X &quot;she&quot;')) +
  labs(x = 'Total uses after &quot;he&quot; or &quot;she&quot; (Logarithmic scale)',
       y = 'Relative uses after &quot;she&quot; to after &quot;he&quot;',
       title = &quot;Gendered Reporting: Pre Weinstein, The Guardian&quot;,
       subtitle = &quot;Words occurring at least 10 times after he/she:
                  160 unique words (100 displayed) | 11,013 occurrences in total&quot;) +
  expand_limits(y = c(4, -4))</code></pre>
<p><img src="https://i1.wp.com/www.gokhanciflikli.com/post/2017-12-02-weinstein-effect_files/figure-html/unnamed-chunk-12-1.png?w=450&ssl=1" data-recalc-dims="1"></p>
<p>Plotting frequencies complement the first plot quite nicely. We can infer reported characteristics more easily when there is a tangible baseline. Words around the red line occur after she or he more or less equally: the y-axis determines the relational effect size (with regards to gender), and the x-axis displays the total amount of occurrences. Some additional insights: we see that ‘sexually’ and ‘allegedly’ popping up after he quite frequently. There is also the verb ‘admitted’, as well as ‘denies’ (even though visually it is located above the red line, if you follow the grey segment, it’s located around 1X ‘he’). For women, more morbid words like ‘suffered’, ‘died’ are added to the mix. There are also nuances regarding the tense; ‘claims’ follows she twice more than he, while ‘claimed’ is twice likely to come after he.</p>
<p>Moving on to the post-Weinstein period (‘the effect’), I quietly run the same code, and plot the equivalent graphics below. Some caveats: with the smaller sample size, I lowered the inclusion threshold from 5 to 2. Additionally, although it is top 15 most skewed verbs per gender, because of frequent ties, it ends up having more than that at the end.</p>
<p><img src="https://i2.wp.com/www.gokhanciflikli.com/post/2017-12-02-weinstein-effect_files/figure-html/unnamed-chunk-14-1.png?w=450&ssl=1" data-recalc-dims="1"></p>
<p>After the scandal broke, we see that women are reported to have ‘complained’, ‘hoped’, and ‘became’. On the other hand, men are vehemently denying the accusations, with ‘denies’ and ‘denied’ being the most skewed verbs following he. Random point: in the pre-period, it’s ‘apologized’, in the post-period, it’s ‘apologised’. Maybe Brexit can manifest in mysterious ways.</p>
<p><img src="https://i1.wp.com/www.gokhanciflikli.com/post/2017-12-02-weinstein-effect_files/figure-html/unnamed-chunk-15-1.png?w=450&ssl=1" data-recalc-dims="1"></p>
<p>Again we turn to the frequency plot to infer more. In addition to denial, men are also reported to use words such as ‘categorically’ and ‘utterly’. Both ‘claims’ and ‘claimed’ occur more after she, not repeating the earlier dynamic regarding the tense. In addition, we don’t see ‘alleged’ or ‘allegedly’ featured in the plot at all. How much of this change can we attribute to the effect? At a glance, we definitely see a difference. For example, verbs display a good variation for both genders. The post-frequency plot features less violent words than the pre-frequency plot. There is a lot more ‘denying’ and not much ‘alleging’ in the post-Weinstein period.</p>
<p>Some are definitely data artefacts. The post-frequency plot is ‘cleaner’—in addition to (and directly caused by) the smaller <em>n</em>—because the cut-off point is set to ‘more than once’: if we remove the filter, all the violence and harassment terms are back in. Some are probably reporter/reporting biases plus the prevalent gendered thinking (that occurs both on a conscious level and below). And perhaps some are genuine effects—true signal. It is still too early to pass judgement on whether the Weinstein effect will result in tangible, positive change. Currently, all we can get is a short, limited glimpse at the available data.</p>
<p>Hopefully you managed to enjoy this rather depressing data undertaking using the <code>tidytext</code> package. As usual, the underlying code is available on <a rel="nofollow" href="https://github.com/ciflikli/website/tree/master/content/post/2017-12-02-weinstein-effect.Rmd" target="_blank">GitHub</a>. N-grams are powerful. Imagine the possibilities: assume you have access to a rich dataset (say, minimum 100K very long articles/essays). You can construct n-grams sequentially; i.e. 2-grams; 3-grams, 4-grams etc., separate the words, and subset for gendered pronouns. This would give you access to structures like “he” + “word” + “her” (direct action) and “she” + “word” + “word” + “him” (allowing for adjective + verb). Then it would be possible to look for all kinds of interactions, revealing their underlying structure. I will be reporting more on this front, until I move onto image processing (looking at you, <code>keras</code>).</p>
</div>
<p><strong><a rel="nofollow" href="https://blockads.fivefilters.org/" target="_blank">Let’s block ads!</a></strong> <a rel="nofollow" href="https://blockads.fivefilters.org/acceptable.html" target="_blank">(Why?)</a></p>
	<p>
<div>
<div>To <strong>leave a comment</strong> for the author, please follow the link and comment on their blog: <strong><a href="https://www.gokhanciflikli.com/post/weinstein-effect/"> Computational Social Science</a></strong>.</div>
<hr>
<a rel="nofollow" href="https://www.r-bloggers.com/">R-bloggers.com</a> offers <strong><a rel="nofollow" href="https://feedburner.google.com/fb/a/mailverify?uri=RBloggers">daily e-mail updates</a></strong> about <a rel="nofollow" href="https://www.r-project.org/" title="The R Project for Statistical Computing">R</a> news and <a rel="nofollow" href="https://www.r-bloggers.com/search/tutorial" title="R tutorials">tutorials</a> on topics such as: <a rel="nofollow" href="https://www.r-bloggers.com/search/data%20science" title="Data science">Data science</a>, <a rel="nofollow" href="https://www.r-bloggers.com/search/Big%20Data" title="Big Data">Big Data, <a rel="nofollow" href="https://www.r-users.com/" title="R jobs">R jobs</a>, visualization (<a rel="nofollow" href="https://www.r-bloggers.com/search/ggplot2" title="ggplot and ggplot2 tutorials">ggplot2</a>, <a rel="nofollow" href="https://www.r-bloggers.com/search/boxplot" title="Boxplots using lattice and ggplot2 tutorials">Boxplots</a>, <a rel="nofollow" href="https://www.r-bloggers.com/search/map" title="Maps and gis">maps</a>, <a rel="nofollow" href="https://www.r-bloggers.com/search/animation" title="Animation in R">animation</a>), programming (<a rel="nofollow" href="https://www.r-bloggers.com/search/RStudio" title="RStudio IDE for R">RStudio</a>, <a rel="nofollow" href="https://www.r-bloggers.com/search/sweave" title="Sweave and literate programming">Sweave</a>, <a rel="nofollow" href="https://www.r-bloggers.com/search/LaTeX" title="LaTeX in R">LaTeX</a>, <a rel="nofollow" href="https://www.r-bloggers.com/search/SQL" title="SQL and databases">SQL</a>, <a rel="nofollow" href="https://www.r-bloggers.com/search/eclipse" title="Eclipse IDE for R">Eclipse</a>, <a rel="nofollow" href="https://www.r-bloggers.com/search/git" title="git and github, Version Control System">git</a>, <a rel="nofollow" href="https://www.r-bloggers.com/search/hadoop" title="Large data in R using Hadoop">hadoop</a>, <a rel="nofollow" href="https://www.r-bloggers.com/search/Web+Scraping" title="Web Scraping of google, facebook, yahoo, twitter and more using R">Web Scraping</a>) statistics (<a rel="nofollow" href="https://www.r-bloggers.com/search/regression" title="Regressions and ANOVA analysis tutorials">regression</a>, <a rel="nofollow" href="https://www.r-bloggers.com/search/PCA" title="principal component analysis tutorial">PCA</a>, <a rel="nofollow" href="https://www.r-bloggers.com/search/time+series" title="Time series">time series</a>, <a rel="nofollow" href="https://www.r-bloggers.com/search/trading" title="finance trading">trading</a>) and more...
<img width="1" alt="" src="http://feeds.feedburner.com/~r/RBloggers/~4/oiNmNObaAA8" height="1"></a></div>