<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/how-to-interpret-correspondence-analysis-plots-it-probably-isnt-the-way-you-think/"></div></div><div></div></div><div></div></div>
<div>
(This article was first published on <strong><a href="https://www.displayr.com/interpret-correspondence-analysis-plots-probably-isnt-way-think/"> R – Displayr</a></strong>, and kindly contributed to <a rel="nofollow" href="https://www.r-bloggers.com/">R-bloggers)</a> </div>
<p><img sizes="(max-width: 300px) 100vw, 300px" src="https://i0.wp.com/www.displayr.com/wp-content/uploads/2017/05/correspondence-analysis-movements-300x185.png?resize=300%2C185&ssl=1" alt="correspondence analysis movements" class="webfeedsFeaturedVisual wp-post-image" data-recalc-dims="1">
<p><img sizes="(max-width: 780px) 100vw, 780px" src="https://i1.wp.com/www.displayr.com/wp-content/uploads/2017/05/correspondence-analysis-movements.png?w=450&ssl=1" alt="correspondence analysis movements" class="wp-image-1767" data-recalc-dims="1"></p>
<p>Correspondence analysis is a popular data science technique. <a rel="nofollow" href="https://www.displayr.com/correspondence-analysis-to-find-patterns-in-tables" target="_blank">It takes a large table, and turns it into a seemingly easy-to-read visualization.</a> Unfortunately, it is not quite as easy to read as most people assume.</p>
<p>In <a rel="nofollow" href="https://www.displayr.com/how-correspondence-analysis-works" target="_blank">How correspondence analysis works (a simple explanation)</a>, I provide a basic explanation of how to interpret correspondence analysis, so if you are completely new to the field, please read that post first. In this post I provide lots of examples to illustrate some of the more complex issues.</p>
<h1>1. Check conclusions using the raw data</h1>
<p>The key to correctly interpreting correspondence analysis is to check any important conclusions by referring back to the original data. In this post I list 9 other things to think about when interpreting correspondence analysis. But, so long as you always remember this first rule, you will not go wrong.</p>
<p>The reason for this rule is illustrated in the example below. It shows 24 months of <a rel="nofollow" href="http://www.abs.gov.au/ausstats/meisubs.NSF/log?openagent&850101.xls&8501.0&Time%20Series%20Spreadsheet&C058C1FF0CE37E69CA25811B00140BFB&0&Mar%202017&09.05.2017&Latest" target="_blank">sales data</a> by different retail categories. The visualization shows that Department stores are associated with December (i.e., Christmas, Dec-15 and Dec-16). We can see that Food retailing is on the opposite side of the map, which most people would interpret as meaning that Food retailing sales are lower in December.</p>
<p><iframe width="450" src="https://embedded.azureedge.net/75668/212794/a831b954-a548-4b1c-ac26-390846b19228.html?v=34784-1890703863"></iframe></p>
<p>Now, take a look at the actual data, shown below. Even though Food retailing is a long way from December on the map:</p>
<ol>
<li>Food retailing has the highest sales in December of any of the categories.</li>
<li>Food retailing’s biggest month is December.</li>
</ol>
<p>How can this be? The data seems to say the exact opposite of visualization? If you have read <a rel="nofollow" href="https://www.displayr.com/how-correspondence-analysis-works" target="_blank">How correspondence analysis works (a simple explanation)</a>, you should understand that this is because correspondence analysis is all about the relativities. If we dig deeper into the data we can see that the map above does make sense, once you know how to read it.</p>
<p>While Food retailing does peak at Christmas, its sales are only 19% above its average monthly sales. By contrast, Department store sales spike to 85% above average in December. This is what correspondence analysis is trying to show us. Correspondence analysis does not show us which rows have the highest numbers, nor which columns have the highest numbers. It instead shows us the relativities. If your interest is instead on which categories sell the most, or how sales change over time, you are better off plotting the raw data than using correspondence analysis.<br>
<iframe width="450" src="https://embedded.azureedge.net/75668/212794/37073809-597c-4970-9b6b-5a030bd4cdca.html?v=34784924264970"></iframe></p>
<p> </p>
<h1>2. The further things are from the origin, the more discriminating they are</h1>
<p>The correspondence analysis plot below is from a big table consisting of 42 rows, each representing a different brand, and 15 columns. You can see the original data <a rel="nofollow" href="https://www.displayr.com/correspondence-analysis-to-find-patterns-in-tables" target="_blank">here</a>. Correspondence analysis has greatly simplified the story in the data. As you hopefully remember from school, the <em>origin </em>is where the <em>x- </em>and <em>y-</em>axes are both at 0. It is shown below as the intersection of two dashed lines. The further labels are from the origin, the more discriminating they are. Thus, Lee Jeans (at the top) is highly differentiated. Similarly, Outdoorsy is a highly discriminating attribute.</p>
<p><iframe width="450" src="https://embedded.azureedge.net/75668/181389/48f00930-aaf1-4bac-ac46-7efbec5a652f.html?v=34784-1860738801"></iframe></p>
<h1>3. The closer things are to origin, the less distinct they <em>probably</em> are</h1>
<p>In the map above, we see that Qantas is bang smack in the middle of the visualization. Thus, the conclusion <em>probably </em>is that it is not differentiated based on any of the data in the study. I explain the use of the weasel-word “probably” in the next section.</p>
<p>Here is another example. In the center of the map we have Wallaby and Lucky. Does this mean wallabies are lucky animals? No. They get hit by cars a lot. If you follow rugby, you will know that 99 times out of 100 a Wallaby is no match for even a Kiwi. If you look at the table below, you can see that the Wallaby is pretty average on all the variables being measured. As it has nothing that differentiates it, the result is that it is in the middle of the map (i.e., near the origin). Similarly, Lucky does not differentiate, so it is also near the center. That they are both in the center tells us that they are both indistinct, and that is all that they have in common (in the data).</p>
<p><iframe width="450" src="https://embedded.azureedge.net/75668/212975/bb5ae02d-c682-4095-90c5-97778878e9fd.html?v=34784-853901435"></iframe></p>
<p><iframe width="450" src="https://embedded.azureedge.net/75668/212975/4e51c9a6-ca77-4c1e-afc9-83df87a47432.html?v=347841715188761"></iframe></p>
<h1>4. The more variance explained, the fewer insights will be missed</h1>
<p>I have reproduced the correspondence analysis of the brand personality data below. You will hopefully recall my mentioning that Qantas being in the middle meant that it was probably not differentiated based on the data. Why did I write “probably”? If you sum up the proportion of variance explained by horizontal and vertical dimensions (shown in the axis labels), we see that visualization displays 57% of the variance in the data. And, remember, this is only 57% of the variance in the relativities. So, a lot of the data has been left out of the summary. Perhaps Qantas is highly differentiated on some dimension that is irrelevant for most of the brands; the only way to know for sure is to check the data.</p>
<p><iframe width="450" src="https://embedded.azureedge.net/75668/181389/48f00930-aaf1-4bac-ac46-7efbec5a652f.html?v=34784-1860738801"></iframe></p>
<p>Now, in fairness to correspondence analysis, it is important to appreciate that it is actually a great achievement for the map to explain 57% of the variation with such a large input table. To represent all of the relativities of this table requires 14 dimensions, but we have only plotted two. Correspondence analysis is not the problem. The problem is the quantity of the data. The more data, the greater the chance that any good summary will miss out important details.</p>
<h1>5. Proximity between row labels probably indicates similarity (if properly normalized)</h1>
<p>As discussed in some detail in <a rel="nofollow" href="https://www.displayr.com/how-correspondence-analysis-works" target="_blank">How correspondence analysis works (a simple explanation)</a>, we <em>should</em> be able to gauge the similarity of row labels based on their distance on the map (i.e., their <i>proximity</i>).  “Should” is another weasel word! Why? Three things are required in order for this to be true:</p>
<ol>
<li>We need to be explaining a high proportion of variance in the data. If we are not, there is always the risk that the two row labels are highly distinct, but are still shown on the map as if not distinct.</li>
<li>The <em>normalization, </em>which is a technical option in correspondence analysis software, needs to have been set to either <em>principal </em>or <em>row principal. </em>I return to this in the next section.</li>
<li>The <em>aspect ratio</em> of the map needs to be fixed at 1. That is, the horizontal and vertical coordinates of the map need to match each other. If your maps are in Excel or, as in the example below, PowerPoint, you may well have a problem. In the chart below, the really big pattern is that there is an enormous gap between the pro-Trump camp, on the far left, and the pro-Clinton camp on the far right. If you have even a passing understanding of American politics, this will make sense. However, if you look at the scale of the labels on the <em>x- </em>and <em>y- </em>axes you will see a problem. A distance of 0.2 on the horizontal is equivalent to a distance of 0.6 on the vertical. The map below this has the aspect ratio set to 1, and it tells a different story. Yes, the pro- and anti-Trump camps are well apart, but the disenfranchised youth are now much more prominent.</li>
</ol>
<p><img sizes="(max-width: 1024px) 100vw, 1024px" src="https://i0.wp.com/www.displayr.com/wp-content/uploads/2017/05/MCAinPPT-1024x425.png?w=450&ssl=1" alt="" class="wp-image-1717" data-recalc-dims="1"></p>
<p><iframe width="450" src="https://embedded.azureedge.net/75668/212197/1130eba2-0a5f-4248-a4da-c958e7ff3123.html?v=34784-1710143916"></iframe></p>
<h1>6. Proximity between column labels indicates similarity (if properly normalized)</h1>
<p>This is a repeat of the previous point, but applying to columns. Here, the normalization needs to be either <em>principal </em>or <em>column principal. </em>You may recall me writing in the previous point that to compare between rows, we need to be using either <em>principal </em>or <em>row principal </em>normalization. So, setting the normalization to <em>principal </em>seems the obvious solution. But, before jumping to this conclusion, which has its own problems (as discussed in the next section), I will illustrate what these different normalization settings look like. The visualization below is based on the principal normalization. <em>Principal </em>is the default in some apps, such as Displayr, Q, and the R package <span>flipDimensionReduction</span>. However, it is <em>not </em>the default in SPSS, which means that comparing the distances between rows labels in a map created by SPSS with defaults is dangerous.</p>
<p><iframe width="450" src="https://embedded.azureedge.net/75668/208717/4b00fa07-18c3-4453-990b-7a08408b45e2.html?v=34784226864495"></iframe></p>
<p>The plot below uses the column principal normalization. If you look very carefully, you will see that the positions of the column points are unchanged (although the map has been zoomed out). But, the positions of the row labels, representing the brands, have changed. There are two ways that the row labels positions have changed. First, they have been stretched out to be further form the origin. Second, the degree of stretching has been greater vertically. With the <em>principal </em>plot shown above, the horizontal differences for the row labels are, in relative terms, bigger. With the column principal shown below, the vertical differences are bigger. So, to repeat the point made a bit earlier: the distances between the column points are valid for both <em>principal </em>and <em>column principal, </em>but the distances between the row points are not correct in the column principal shown below.</p>
<p><iframe width="450" src="https://embedded.azureedge.net/75668/208717/aa2bea14-1740-4dd2-8139-2b534a255bf8.html?v=34784-527730899"></iframe></p>
<p>The visualization below shows the row principal normalization. Now the distances between the row labels are meaningful and consistent with those shown in the principal normalization, but the differences between the column coordinates are now misleading.</p>
<p><iframe width="450" src="https://embedded.azureedge.net/75668/208717/2d443e94-e084-4682-9387-da8d28dcb3ed.html?v=34784-75598853"></iframe></p>
<p> </p>
<h1>7. If there is a small angle connecting a row and column label to the origin, they are probably associated</h1>
<p>Take a look at the plot above. Would you say Lift is more strongly associated with Cheers you up or Relax? If you have said Relax, you are interpreting the map correctly. As discussed in <a rel="nofollow" href="https://www.displayr.com/how-correspondence-analysis-works" target="_blank">How correspondence analysis works (a simple explanation)</a> it is wrong to look at the distance between row labels and column labels. Instead, we should imagine a line connecting the row and column labels with the origin. The sharper the angle, the stronger the relationship. Thus, there is a strong relationship between Relax and Lift (although, if you look at the data shown below, you will see that Lift is very small, so it does not in any sense “own” Relax).</p>
<p><iframe width="450" src="https://embedded.azureedge.net/75668/208717/e27ef5b6-72aa-49c6-82b3-b9afd90e7962.html?v=34784-106146620"></iframe></p>
<p>If you have not yet had your coffee for the day, go get it now. We are at the hard bit. In the plot above, the angles are informative. However, interpreting the angles is only strictly valid when you have either <em>row principal, column principal, </em>or <em>symmetrical (1/2) </em>normalization. So, if wanting to make inferences about the relationships between the rows and columns (e.g., brands and attributes in the examples above), we are better off not using the default principal normalization. This is really the yuckiest aspect of correspondence analysis. No one normalization is appropriate for everything. Or, stated from a glass half full perspective, our choice of normalization is really a choice of how we want to mislead the viewer!</p>
<p>Additional complexity is added to this problem by the tendency of people not to report the normalization. Fortunately, we can make an educated guess based on the dispersion of the points (if the rows points are all near the origin we probably have row principal, and vice versa for columns).</p>
<p>Depending on the day of the week I have two ways of dealing with this issue. Most of the time, my preference is to use the <em>principal </em>normalization, and remind viewers to check everything in the raw data. Sometimes though, where my interest is principally in the rows of a table, I use <em>row principal </em>and a <em>moon plot. </em>Distances between the brands are plotted inside of a circle and these distances are meaningful. The column labels are shown on the outside of the circle. They have the same angles as on the plot above. But, now the font size represents what was previously indicated by the distance between the column labels and the origin. The beauty of this representation is that we can now compare distances between column labels and points, so the plot is much harder to misread, and we have no need to educate the reader about the whole reading of angles. The information regarding the relativities of the column labels is harder to gauge, but, this is arguably beneficial, as the construction of the plot makes it clear that the focuses is on the rows (brands).</p>
<p><iframe src="https://embedded.azureedge.net/75668/208717/a0cae2f4-0582-46e0-bfa6-901a7399fa97.html?v=34784-74583043" data-mce-fragment="1" width="450"></iframe></p>
<h1>8. A row and column label are probably not associated if their angle to the origin is 90 degrees</h1>
<p>In the moonplot above, if you draw a line connecting Red Bull to the Origin, and back out to Kids, you will see that it is roughly a right-angle (90 degrees). This tells us that there is no association between Kids and Red Bull. Again, I have written “probably”. If you look at the data, shown in the table above, there is clearly a negative association. Remember, always look at the data!</p>
<h1>9. A row and column label are probably negatively associated if they are on opposite sides of the origin</h1>
<p>The plot below shows the traits that people want in an American president by age. What do the 25 to 34 year old yearn for? The is a strong association with Entertaining. What is the next strongest association? You may think it would be concern about global warming and minorities. This is not the case. The next strongest associations are negative ones: the 25 to 34 year olds are less keen on a Christian President, one who has been successful in business, and one who is plain-speaking. We can see this because these traits are on the opposite side of the origin, and are a long way from the origin, whereas the traits relating to global warming and welfare of minorities are all closer to the origin, and thus are less discriminating.<br>
<iframe width="450" src="https://embedded.azureedge.net/75668/212197/28b82a63-4ca0-4d85-adbd-85dd648c1e27.html?v=34784-354804799"></iframe></p>
<p><iframe width="450" src="https://embedded.azureedge.net/75668/212197/91616317-d6eb-4b09-8662-547e0f75f8a9.html?v=347841747426615"></iframe></p>
<p>Here’s another example. The correct way to read this visualization is that Yahoo is, in relative terms, stronger than Google on Fun. However, if you look at the raw data it shows that Google is much more fun than Yahoo (54% versus 28%). The reason that Yahoo has stronger association with Fun is that it is its second best performing attribute (with 29% for Easy-to-use). By contrast, while Google is twice as fun as Yahoo, it scores three times as high on High quality, and High performance, which are on the opposite side of the map, and this is what drags Google away from Yahoo.</p>
<p><iframe width="450" src="https://embedded.azureedge.net/75668/208717/47ecba2c-6b85-4459-b4a1-344cd3e71604.html?v=34784967232688"></iframe></p>
<p><iframe width="450" src="https://embedded.azureedge.net/75668/212975/3c1bac4c-0b32-4d83-910c-b192a728dbf1.html?v=347841193223848"></iframe></p>
<h1>10. The further a point from the origin, the stronger their positive or negative association</h1>
<p>The visualization below shows movement of Yahoo’s perceptions from 2012 to 2017, with the arrow head showing 2017 and the base of the arrow showing 2012. The obvious way to read this is that Yahoo has become more fun, more innovative, and easier-to-use. However, such a conclusion would be misplaced.</p>
<p>A better interpretation is:</p>
<ul>
<li>In 2012, the angle formed by connecting the base of Yahoo to the origin and back to Fun is very small, which tells us that they are associated.</li>
<li>As Fun is relatively far from the origin we know that Fun is a relatively good discriminator between the brands.</li>
<li>As Yahoo was very far from the origin, and associated with Fun, we can conclude that Yahoo and Fun were closely associated in 2012 (remember, correspondence analysis focuses on relativities; in 2012 Yahoo’s Fun score was half of Google’s).</li>
<li>From 2012 to 2017, Yahoo moved much closer to the origin, which tells us that Yahoo’s relative strengths in terms of Fun, Easy-to-Use, and Innovative, have likely declined (and, in reality, they have declined sharply; Google is now more than four times as fun).<br>
<iframe width="450" src="https://embedded.azureedge.net/75668/208918/1e941368-a72d-4283-9373-a959fd7f17f6.html?v=34784-969767681"></iframe></li>
</ul>
<h1>Summary</h1>
<p>It is really, really, important to always check key conclusions from correspondence analysis by inspecting the raw data.</p>
<h1>Software</h1>
<p>Hopefully you like the look of the plots in this post! They can all be created in R using the <span>Displayr/flipDimensionReduction</span> package, or in Displayr and Q via the menus. More detail about the various plots shown in this post, and R code, can be found in the other correspondence analysis posts on this blog.</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.displayr.com/interpret-correspondence-analysis-plots-probably-isnt-way-think/"> R – Displayr</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/Z_JoVx7zxxw" height="1"></a></div>