<p><div><div><div><div data-width="100" data-show-faces="false" data-send="true" data-layout="button_count" data-height="21" data-href="https://www.r-bloggers.com/anova-in-r-afex-may-be-the-solution-you-are-looking-for/"></div></div><div></div></div><div></div></div>
<div>
(This article was first published on <strong><a href="http://singmann.org/anova-in-r-afex-may-be-the-solution-you-are-looking-for/"> Computational Psychology - Henrik Singmann</a></strong>, and kindly contributed to <a rel="nofollow" href="https://www.r-bloggers.com/">R-bloggers)</a> </div>
<p><strong>Prelude</strong>: When you start with <code>R</code> and try to estimate a standard ANOVA , which is relatively simple in commercial software like SPSS, <code>R</code> kind of sucks. Especially for unbalanced designs or designs with repeated-measures replicating the results from <a target="_blank" rel="nofollow" href="https://stats.stackexchange.com/a/14207/442">such software in base <code>R</code> may require considerable effort</a>. For a newcomer (and even an old timer) this can be somewhat off-putting. After I had gained experience developing <a target="_blank" rel="nofollow" href="https://cran.r-project.org/package=MPTinR">my first package</a> and was once again struggling with <code>R</code> and ANOVA I had enough and decided to develop <code>afex</code>. If you know this feeling, <code>afex</code> is also for you.</p>
<hr>
<p>A new version of <a target="_blank" rel="nofollow" href="https://cran.r-project.org/package=afex"><code>afex</code> (0.18-0) has been accepted on CRAN</a> a few days ago. This version only fixes a small bug that was introduced in the last version.  <code>aov_ez</code> did not work with more than one <code>covariate</code> (<a target="_blank" rel="nofollow" href="https://github.com/singmann/afex/issues/29">thanks to <code>tkerwin</code> for reporting this bug</a>).</p>
<p>I want to use this opportunity to introduce one of the main functionalities of <code>afex</code>. It provides a set of functions that make calculating ANOVAs easy. In the default settings, <code>afex</code> automatically uses appropriate orthogonal contrasts for factors, transforms numerical variables into factors, uses so-called Type III sums of squares, and allows for any number of factors including repeated-measures (or within-subjects) factors and mixed/split-plot designs. Together this guarantees that the ANOVA results correspond to the results obtained from commercial statistical packages such as <code>SPSS</code> or <code>SAS</code>. On top of this, the ANOVA object returned by afex (of class <code>afex_aov</code>) can be directly used for follow-up or post-hoc tests/contrasts using the <a target="_blank" rel="nofollow" href="https://cran.r-project.org/package=lsmeans"><code>lsmeans</code></a> package <span rel="{ 'api_user_id': '881472', 'pages': '', 'items': '{EID22BTQ}', 'format': '(%a%, %d%, %p%)', 'brackets': '', 'etal': '', 'separator': '', 'and': '' }"></span>.</p>
<h3>Example Data</h3>
<p>Let me illustrate how to calculate an ANOVA with a simple example. We use data courtesy of Andrew Heathcote and colleagues <span rel="{ 'api_user_id': '881472', 'pages': '', 'items': '{6ZTIZNX3}', 'format': '(%a%, %d%, %p%)', 'brackets': '', 'etal': '', 'separator': '', 'and': '' }"></span>. The data are lexical decision and word naming latencies for 300 words and 300 nonwords from 45 participants. Here we only look at three factors:</p>
<ul>
<li><code>task</code> is a between subjects (or independent-samples) factor: 25 participants worked on the lexical decision task (<code>lexdec</code>; i.e., participants had to make a binary decision whether or not the presented string is a word or nonword) and 20 participants on the naming task (<code>naming</code>; i.e., participant had to say the presented string out loud).</li>
<li><code>stimulus</code> is a repeated-measures or within-subjects factor that codes whether a presented string was a <code>word</code> or <code>nonword</code>.</li>
<li><code>length</code> is also a repeated-measures factor that gives the number of characters of the presented strings with three levels: 3, 4, and 5.</li>
</ul>
<p>The dependent variable is the response latency or response time for each presented string. More specifically, as is common in the literature we analyze the log of the response times, <code>log_rt</code>. After excluding erroneous responses each participants responded to between 135 and 150 words and between 124 and 150 nonwords. To use this data in an ANOVA one needs to aggregate the data such that only one observation per participant and cell of the design (i.e., combination of all factors) remains. As we will see, <code>afex</code> does this automatically for us (this is one of the features I blatantly stole from <a target="_blank" rel="nofollow" href="https://cran.r-project.org/package=ez"><code>ez</code></a>).</p>
<pre data-enlighter-language="null">library(afex)
data(&quot;fhch2010&quot;) # load data (comes with afex) 

mean(!fhch2010$correct) # error rate
# [1] 0.01981546
fhch &lt;- droplevels(fhch2010[ fhch2010$correct,]) # remove errors

str(fhch2010) # structure of the data
# 'data.frame': 13222 obs. of  10 variables:
#  $ id       : Factor w/ 45 levels &quot;N1&quot;,&quot;N12&quot;,&quot;N13&quot;,..: 1 1 1 1 1 1 1 1 ...
#  $ task     : Factor w/ 2 levels &quot;naming&quot;,&quot;lexdec&quot;: 1 1 1 1 1 1 1 1 1 1 ...
#  $ stimulus : Factor w/ 2 levels &quot;word&quot;,&quot;nonword&quot;: 1 1 1 2 2 1 2 2 1 2 ...
#  $ density  : Factor w/ 2 levels &quot;low&quot;,&quot;high&quot;: 2 1 1 2 1 2 1 1 1 1 ...
#  $ frequency: Factor w/ 2 levels &quot;low&quot;,&quot;high&quot;: 1 2 2 2 2 2 1 2 1 2 ...
#  $ length   : Factor w/ 3 levels &quot;4&quot;,&quot;5&quot;,&quot;6&quot;: 3 3 2 2 1 1 3 2 1 3 ...
#  $ item     : Factor w/ 600 levels &quot;abide&quot;,&quot;acts&quot;,..: 363 121 ...
#  $ rt       : num  1.091 0.876 0.71 1.21 0.843 ...
#  $ log_rt   : num  0.0871 -0.1324 -0.3425 0.1906 -0.1708 ...
#  $ correct  : logi  TRUE TRUE TRUE TRUE TRUE TRUE ...
</pre>
<p>We first load the data and remove the roughly 2% errors. The structure of the <code>data.frame</code> (obtained via <code>str()</code>) shows us that the data has a few more factors than discussed here. To specify our ANOVA we first use function <code>aov_car()</code> which works very similar to base <code>R aov()</code>, but as all <code>afex</code> functions uses <code>car::Anova()</code> (read as function <code>Anova()</code> from package <code>car</code>) as the backend for calculating the ANOVA.</p>
<h3>Specifying an ANOVA</h3>
<pre data-enlighter-language="null">(a1 &lt;- aov_car(log_rt ~ task*length*stimulus + Error(id/(length*stimulus)), fhch))
# Contrasts set to contr.sum for the following variables: task
# Anova Table (Type 3 tests)
# 
# Response: log_rt
#                 Effect          df  MSE          F   ges p.value
# 1                 task       1, 43 0.23  13.38 ***   .22   .0007
# 2               length 1.83, 78.64 0.00  18.55 ***  .008  &lt;.0001
# 3          task:length 1.83, 78.64 0.00       1.02 .0004     .36
# 4             stimulus       1, 43 0.01 173.25 ***   .17  &lt;.0001
# 5        task:stimulus       1, 43 0.01  87.56 ***   .10  &lt;.0001
# 6      length:stimulus 1.70, 72.97 0.00       1.91 .0007     .16
# 7 task:length:stimulus 1.70, 72.97 0.00       1.21 .0005     .30
# ---
# Signif. codes:  0 ‘***’ 0.001 ‘**’ 0.01 ‘*’ 0.05 ‘+’ 0.1 ‘ ’ 1
# 
# Sphericity correction method: GG 
# Warning message:
# More than one observation per cell, aggregating the data using mean (i.e, fun_aggregate = mean)!</pre>
<p>The printed output is an ANOVA table that could basically be copied to a manuscript as is. One sees the terms in column <code>Effect</code>, the degrees of freedoms (<code>df</code>), the mean-squared error (<code>MSE</code>, I would probably remove this column in a manuscript), the <em>F</em>-value (<code>F</code>, which also contains the significance stars), and the <em>p</em>-value (<code>p.value</code>). The only somewhat uncommon column is <code>ges</code> which provides generalized eta-squared, ‘the recommended effect size statistics for repeated measure designs’  <span rel="{ 'api_user_id': '881472', 'pages': '', 'items': '{ZTKXF57D}', 'format': '(%a%, %d%, %p%)', 'brackets': '', 'etal': '', 'separator': '', 'and': '' }"></span>. The standard output also reports Greenhouse-Geisser (<code>GG</code>) corrected <em>df</em> for repeated-measures factors with more than two levels (<a target="_blank" rel="nofollow" href="http://homepages.gold.ac.uk/aphome/spheric.html">to account for possible violations of sphericity</a>). Note that these corrected <em>df</em> are not integers.</p>
<p>We can also see a warning notifying us that <code>afex</code> has detected that each participant and cell of the design provides more than one observation which are then automatically aggregated using <code>mean</code>. The warning serves the purpose to notify the user in case this was not intended (i.e., when there should be only one observation per participant and cell of the design). The warning can be suppressed via specifying <code>fun_aggregate = mean</code> explicitly in the call to <code>aov_car</code>.</p>
<p>The formula passed to <code>aov_car</code> basically needs to be the same as for standard <code>aov</code> with a few differences:</p>
<ul>
<li>It must have an <code>Error</code> term specifying the column containing the participant (or unit of observation) identifier (e.g., minimally <code>+Error(id)</code>). This is necessary to allow the automatic aggregation even in designs without repeated-measures factor.</li>
<li>Repeated-measures factors only need to be defined in the <code>Error</code> term and do not need to be enclosed by parentheses. Consequently, the following call produces the same ANOVA:
<pre data-enlighter-language="null">aov_car(log_rt ~ task + Error(id/length*stimulus), fhch)</pre>
<p> 

<p>In addition to <code>aov_car</code>, <code>afex</code> provides two further function for calculating ANOVAs. These function produce the same output but differ in the way how to specify the ANOVA.</p>
<ul>
<li><code>aov_ez</code> allows the ANOVA specification not via a <code>formula</code> but via <code>character</code> vectors (and is similar to <code>ez::ezANOVA()</code>):
<pre data-enlighter-language="null">aov_ez(id = &quot;id&quot;, dv = &quot;log_rt&quot;, fhch, between = &quot;task&quot;, within = c(&quot;length&quot;, &quot;stimulus&quot;))</pre>
</li>
<li><code>aov_4</code> requires a formula for which the <code>id</code> and repeated-measures factors need to be specified as in <code>lme4::lmer()</code> (with the same simplification that repeated-measures factors only need to be specified in the random part):
<pre data-enlighter-language="null">aov_4(log_rt ~ task + (length*stimulus|id), fhch)
aov_4(log_rt ~ task*length*stimulus + (length*stimulus|id), fhch)
</pre>
</li>
</ul>
<h3>Follow-up Tests</h3>
<p>A common requirement after the omnibus test provided by the ANOVA is some-sort of follow-up analysis. For this purpose, <code>afex</code> is fully integrated with <code>lsmeans</code> <span rel="{ 'api_user_id': '881472', 'pages': '', 'items': '{EID22BTQ}', 'format': '(%a%, %d%, %p%)', 'brackets': '', 'etal': '', 'separator': '', 'and': '' }"></span>.</p>
<p>For example, assume we are interested in the significant <code>task:stimulus</code> interaction. As a first step we might want to investigate the marginal means of these two factors:</p>
<pre data-enlighter-language="null">lsmeans(a1, c(&quot;stimulus&quot;,&quot;task&quot;))
# NOTE: Results may be misleading due to involvement in interactions
#  stimulus task        lsmean         SE    df    lower.CL    upper.CL
#  word     naming -0.34111656 0.04250050 48.46 -0.42654877 -0.25568435
#  nonword  naming -0.02687619 0.04250050 48.46 -0.11230839  0.05855602
#  word     lexdec  0.00331642 0.04224522 47.37 -0.08165241  0.08828525
#  nonword  lexdec  0.05640801 0.04224522 47.37 -0.02856083  0.14137684
# 
# Results are averaged over the levels of: length 
# Confidence level used: 0.95 
</pre>
<p>From this we can see naming trials seems to be generally slower (as a reminder, the dv is log-transformed RT in seconds, so values below 0 correspond to RTs bewteen 0 and 1), It also appears that the difference between <code>word</code> and <code>nonword</code> trials is larger in the <code>naming</code> task then in the <code>lexdec</code> task. We test this with the following code using a few different <code>lsmeans</code> function. We first use <code>lsmeans</code> again, but this time using <code>task</code> as the conditioning variable specified in <code>by</code>. Then we use <code>pairs()</code> for obtaining all pairwise comparisons within each conditioning strata (i.e., level of <code>task</code>). This provides us already with the correct tests, but does not control for the family-wise error rate across both tests. To get those, we simply <code>update()</code> the returned results and remove the conditioning by setting <code>by=NULL</code>. In the call to update we can already specify the method for error control and we specify <code>'holm'</code>,  because it is uniformly more powerful than Bonferroni.</p>
<pre data-enlighter-language="null"># set up conditional marginal means:
(ls1 &lt;- lsmeans(a1, c(&quot;stimulus&quot;), by=&quot;task&quot;))
# task = naming:
#  stimulus      lsmean         SE    df    lower.CL    upper.CL
#  word     -0.34111656 0.04250050 48.46 -0.42654877 -0.25568435
#  nonword  -0.02687619 0.04250050 48.46 -0.11230839  0.05855602
# 
# task = lexdec:
#  stimulus      lsmean         SE    df    lower.CL    upper.CL
#  word      0.00331642 0.04224522 47.37 -0.08165241  0.08828525
#  nonword   0.05640801 0.04224522 47.37 -0.02856083  0.14137684
# 
# Results are averaged over the levels of: length 
# Confidence level used: 0.95 
update(pairs(ls1), by=NULL, adjust = &quot;holm&quot;)
#  contrast       task      estimate         SE df t.ratio p.value
#  word - nonword naming -0.31424037 0.02080113 43 -15.107  &lt;.0001
#  word - nonword lexdec -0.05309159 0.01860509 43  -2.854  0.0066
# 
# Results are averaged over the levels of: length 
# P value adjustment: holm method for 2 tests</pre>
<p>Hmm. These results show that the <code>stimulus</code> effects in both <code>task</code> conditions are independently significant. Obviously, the difference between them must also be significant then, or?</p>
<pre data-enlighter-language="null">pairs(update(pairs(ls1), by=NULL))
# contrast                              estimate         SE df t.ratio p.value
# wrd-nnwrd,naming - wrd-nnwrd,lexdec -0.2611488 0.02790764 43  -9.358  &lt;.0001</pre>
<p>They obviously are. As a reminder, the interaction is testing exactly this, the difference of the difference. And we can actually recover the <em>F</em>-value of the interaction using <code>lsmeans</code> alone by invoking yet another of its functions, <code>test(..., joint=TRUE)</code>.</p>
<pre data-enlighter-language="null">test(pairs(update(pairs(ls1), by=NULL)), joint=TRUE)
# df1 df2      F p.value
#   1  43 87.565  &lt;.0001</pre>
<p>These last two example were perhaps not particularly interesting from a statistical point of view, but show an important ability of <code>lsmeans</code>. Any set of estimated marginal means produced by <code>lsmeans</code>, including any sort of (custom) contrasts, can be used again for further tests or calculating new sets of marginal means. And with <code>test()</code> we can even obtain joint <em>F</em>-tests over several parameters using <code>joint=TRUE</code>. <code>lsmeans</code> is extremely powerful and one of my most frequently used packages that basically performs all tests following an omnibus test (and in its latest version it directly interfaces with <code>rstanarm</code> so it can now also be used for a lot of Bayesian stuff, but this is the topic of another blog post).</p>
<p>Finally, <code>lsmeans</code> can also be used directly for plotting by envoking <code>lsmip</code>:</p>
<pre data-enlighter-language="null">lsmip(a1, task ~ stimulus)</pre>
<p><img sizes="(max-width: 490px) 100vw, 490px" data-image-description="" data-orig-file="https://i2.wp.com/singmann.org/wp-content/uploads/2017/06/lmsip_example1.png?fit=1181%2C826" data-orig-size="1181,826" data-image-title="lmsip_example1" class="wp-image-526" data-comments-opened="1" data-recalc-dims="1" data-attachment-id="526" data-permalink="http://singmann.org/anova-in-r-afex-may-be-the-solution-you-are-looking-for/lmsip_example1/" alt="" data-medium-file="https://i2.wp.com/singmann.org/wp-content/uploads/2017/06/lmsip_example1.png?fit=300%2C210" data-large-file="https://i2.wp.com/singmann.org/wp-content/uploads/2017/06/lmsip_example1.png?fit=490%2C343" data-image-meta="{" src="https://i2.wp.com/singmann.org/wp-content/uploads/2017/06/lmsip_example1.png?resize=490%2C343"></p>
<p>Note that <code>lsmip</code> does not add error bars to the estimated marginal means, but only plots the point estimates. There are mainly two reasons for this. First, as soon as repeated-measures factors are involved, it is difficult to decide which error bars to plot. Standard error bars based on the standard error of the mean are not appropriate for within-subjects comparisons. For those, one would need to use a within-subject intervals <span rel="{ 'api_user_id': '881472', 'pages': '', 'items': '{8SUWFIRC},{4U9N89AU},{CS2R6JNU}', 'format': '(%a%, %d%, %p%)', 'brackets': '', 'etal': '', 'separator': '', 'and': '' }"></span> (see also <a target="_blank" rel="nofollow" href="http://www.mypolyuweb.hk/~sjpolit/confidenceintervals.html">here</a> or <a target="_blank" rel="nofollow" href="https://motorbehaviour.wordpress.com/2014/10/31/confidence-intervals-in-within-participant-design-a-tutorial-on-the-cousineau-morey-method/">here</a>). Especially for plots as the current one with both independent-samples and repeated-measures factors (i.e., mixed within-between designs or split-plot designs) no error bar will allow comparisons across both dimensions. Second, only ‘if the SE [i.e., standard error] of the mean is exactly 1/2 the SE of the difference of two means — which is almost never the case — it would be appropriate to use overlapping confidence intervals to test comparisons of means’ (<a target="_blank" rel="nofollow" href="https://stat.ethz.ch/pipermail/r-sig-mixed-models/2017q2/025699.html">lsmeans author Russel Lenth</a>, the link provides an alternative).</p>
<p>We can also use <code>lsmeans</code> in combination with <code>lattice</code> to plot the results on the unconstrained scale (i.e., after back-transforming tha data from the log scale to the original scale of response time in seconds). The plot is not shown here.</p>
<pre data-enlighter-language="null">lsm1 &lt;- summary(lsmeans(a1, c(&quot;stimulus&quot;,&quot;task&quot;)))
lsm1$lsmean &lt;- exp(lsm1$lsmean)
require(lattice)
xyplot(lsmean ~ stimulus, lsm1, group = task, type = &quot;b&quot;, 
       auto.key = list(space = &quot;right&quot;))
</pre>
<p> </p>
<h3>Summary</h3>
<ul>
<li><code>afex</code> provides a set of functions that make specifying standard ANOVAs for an arbitrary number of between-subjects (i.e., independent-sample) or within-subjects (i.e., repeated-measures) factors easy: <code>aov_car()</code>, <code>aov_ez()</code>, and <code>aov_4()</code>.</li>
<li>In its default settings, the <code>afex</code> ANOVA functions replicate the results of commercial statistical packages such as SPSS or SAS (using orthogonal contrasts and Type III sums of squares).</li>
<li>Fitted ANOVA models can be passed to <code>lsmeans</code> for follow-up tests, custom contrast tests, and plotting.</li>
<li>For specific questions visit the new afex support forum: <a target="_blank" rel="nofollow" href="http://afex.singmann.science/">afex.singmann.science</a> (I think we just need someone to ask the first ANOVA question to get the ball rolling).</li>
<li>For more examples see <a target="_blank" rel="nofollow" href="https://cran.r-project.org/web/packages/afex/vignettes/afex_anova_example.html">the vignette</a> or <a target="_blank" rel="nofollow" href="https://www.psychologie.uni-heidelberg.de/ae/meth/team/mertens/blog/anova_in_r_made_easy.nb.html">here (blog post by Ulf Mertens)</a> or download the <a target="_blank" rel="nofollow" href="http://singmann.org/download/teaching/r/blog_example.R">full example R script used here</a>.</li>
</ul>
<p>As a caveat, let me end this post with some cautionary remarks from Douglas Bates (<code>fortunes::fortune(184)</code>) who explains why ANOVA in <code>R</code> is supposed to not be the same as in other software packages (i.e., he justifies why it ‘sucks’):</p>
<blockquote><p>You must realize that R is written by experts in statistics and statistical computing who, despite popular opinion, do not believe that everything in SAS and SPSS is worth copying. Some things done in such packages, which trace their roots back to the days of punched cards and magnetic tape when fitting a single linear model may take several days because your first 5 attempts failed due to syntax errors in the JCL or the SAS code, still reflect the approach of “give me every possible statistic that could be calculated from this model, whether or not it makes sense”. The approach taken in R is different. The underlying assumption is that the useR is thinking about the analysis while doing it.<br>
— Douglas Bates (in reply to the suggestion to include type III sums of squares and lsmeans in base R to make it more similar to SAS or SPSS)<br>
R-help (March 2007)</p>
</blockquote>
<p><a target="_blank" rel="nofollow" href="https://youtu.be/HMqZ2PPOLik">Maybe he is right, but maybe what I have described here is useful to some degree</a>.</p>
<h3>References</h3>
<div>
<span>881472</span><br>
<span>{EID22BTQ};{6ZTIZNX3};{ZTKXF57D};{EID22BTQ};{8SUWFIRC},{4U9N89AU},{CS2R6JNU}</span><br>
<span>apa</span><br>
<span>default</span><br>
<span>ASC</span><br>
<span>no</span><br>
<span></span><br>
<span></span><br>
<span></span><br>
<span></span><br>
<span></span><br>
<span></span><br>
<span></span><br>
<span></span><br>
<span></span><br>
<span></span><br>
<span>485</span><br>
<span>http://singmann.org/wp-content/plugins/zotpress/</span>
<div></div>
<p></div>
<p></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="http://singmann.org/anova-in-r-afex-may-be-the-solution-you-are-looking-for/"> Computational Psychology - Henrik Singmann</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 title="The R Project for Statistical Computing" rel="nofollow" href="https://www.r-project.org/">R</a> news and <a title="R tutorials" rel="nofollow" href="https://www.r-bloggers.com/search/tutorial">tutorials</a> on topics such as: <a title="Data science" rel="nofollow" href="https://www.r-bloggers.com/search/data%20science">Data science</a>, <a title="Big Data" rel="nofollow" href="https://www.r-bloggers.com/search/Big%20Data">Big Data, <a title="R jobs" rel="nofollow" href="https://www.r-users.com/">R jobs</a>, visualization (<a title="ggplot and ggplot2 tutorials" rel="nofollow" href="https://www.r-bloggers.com/search/ggplot2">ggplot2</a>, <a title="Boxplots using lattice and ggplot2 tutorials" rel="nofollow" href="https://www.r-bloggers.com/search/boxplot">Boxplots</a>, <a title="Maps and gis" rel="nofollow" href="https://www.r-bloggers.com/search/map">maps</a>, <a title="Animation in R" rel="nofollow" href="https://www.r-bloggers.com/search/animation">animation</a>), programming (<a title="RStudio IDE for R" rel="nofollow" href="https://www.r-bloggers.com/search/RStudio">RStudio</a>, <a title="Sweave and literate programming" rel="nofollow" href="https://www.r-bloggers.com/search/sweave">Sweave</a>, <a title="LaTeX in R" rel="nofollow" href="https://www.r-bloggers.com/search/LaTeX">LaTeX</a>, <a title="SQL and databases" rel="nofollow" href="https://www.r-bloggers.com/search/SQL">SQL</a>, <a title="Eclipse IDE for R" rel="nofollow" href="https://www.r-bloggers.com/search/eclipse">Eclipse</a>, <a title="git and github, Version Control System" rel="nofollow" href="https://www.r-bloggers.com/search/git">git</a>, <a title="Large data in R using Hadoop" rel="nofollow" href="https://www.r-bloggers.com/search/hadoop">hadoop</a>, <a title="Web Scraping of google, facebook, yahoo, twitter and more using R" rel="nofollow" href="https://www.r-bloggers.com/search/Web+Scraping">Web Scraping</a>) statistics (<a title="Regressions and ANOVA analysis tutorials" rel="nofollow" href="https://www.r-bloggers.com/search/regression">regression</a>, <a title="principal component analysis tutorial" rel="nofollow" href="https://www.r-bloggers.com/search/PCA">PCA</a>, <a title="Time series" rel="nofollow" href="https://www.r-bloggers.com/search/time+series">time series</a>, <a title="finance trading" rel="nofollow" href="https://www.r-bloggers.com/search/trading">trading</a>) and more...

	<img height="1" alt="" width="1" src="http://feeds.feedburner.com/~r/RBloggers/~4/oKkxIDZfl_4"></a></div></ul>