<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Visualizing WPA expenditures</title>
	<atom:link href="http://crookedtimber.org/2009/01/03/visualizing-wpa-expenditures/feed/" rel="self" type="application/rss+xml" />
	<link>http://crookedtimber.org/2009/01/03/visualizing-wpa-expenditures/</link>
	<description>Out of the crooked timber of humanity, no straight thing was ever made</description>
	<lastBuildDate>Mon, 13 Feb 2012 09:29:41 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: michael e sullivan</title>
		<link>http://crookedtimber.org/2009/01/03/visualizing-wpa-expenditures/comment-page-1/#comment-262567</link>
		<dc:creator>michael e sullivan</dc:creator>
		<pubDate>Mon, 05 Jan 2009 22:02:54 +0000</pubDate>
		<guid isPermaLink="false">http://crookedtimber.org/?p=9048#comment-262567</guid>
		<description>&lt;i&gt;&quot;why not just a log scale?&quot;

That’s almost what it is. In the original discussion people were looking for a stronger way to remind the viewer about the scale changes in such a case.&lt;/i&gt;

I would say you&#039;ve made a weaker way.  It&#039;s not at all obvious that the scale is discontinuous visually -- you have to read the fine print. 

If you are going to graph it this way, I greatly prefer larger breaks between the categories plotted on different scales, both horizontally and vertically, also different colors used for the dot plots at different scales would also serve to alert the viewer that something is going on.  It&#039;s extremely difficult to visualize from your graph, the difference at the boundary of the scales.  

There appears to be a bigger difference between recreation and airports/airways, than between conservation and sewing, where the plots are right next to each other.  

That would be somewhat alleviated by more obvious visual breaks, but a simple log scale would avoid the problem completely while conveying at least as much visual information as this graph.   

I prefer the log scale.  or, as your last comment suggests, a table with full dollar amounts (or amounts in thousands/millions) which would make the arithmetical differences clearer without losing information.</description>
		<content:encoded><![CDATA[	<p><i>&#8220;why not just a log scale?&#8221;</i></p>

	<p>That&#8217;s almost what it is. In the original discussion people were looking for a stronger way to remind the viewer about the scale changes in such a case.</p>

	<p>I would say you&#8217;ve made a weaker way.  It&#8217;s not at all obvious that the scale is discontinuous visually&#8212;you have to read the fine print.</p>

	<p>If you are going to graph it this way, I greatly prefer larger breaks between the categories plotted on different scales, both horizontally and vertically, also different colors used for the dot plots at different scales would also serve to alert the viewer that something is going on.  It&#8217;s extremely difficult to visualize from your graph, the difference at the boundary of the scales.</p>

	<p>There appears to be a bigger difference between recreation and airports/airways, than between conservation and sewing, where the plots are right next to each other.</p>

	<p>That would be somewhat alleviated by more obvious visual breaks, but a simple log scale would avoid the problem completely while conveying at least as much visual information as this graph.</p>

	<p>I prefer the log scale.  or, as your last comment suggests, a table with full dollar amounts (or amounts in thousands/millions) which would make the arithmetical differences clearer without losing information.</p>
 ]]></content:encoded>
	</item>
	<item>
		<title>By: Kieran</title>
		<link>http://crookedtimber.org/2009/01/03/visualizing-wpa-expenditures/comment-page-1/#comment-262539</link>
		<dc:creator>Kieran</dc:creator>
		<pubDate>Mon, 05 Jan 2009 19:13:26 +0000</pubDate>
		<guid isPermaLink="false">http://crookedtimber.org/?p=9048#comment-262539</guid>
		<description>I take the point about the panel transitions being problematic. I think I&#039;m leaning back toward my original view that two separate graphs would be a better way to do it. In a way, a table with the full dollar amounts would work fine, as reading the extra zeros conveys the different magnitudes in the most compact way.</description>
		<content:encoded><![CDATA[	<p>I take the point about the panel transitions being problematic. I think I&#8217;m leaning back toward my original view that two separate graphs would be a better way to do it. In a way, a table with the full dollar amounts would work fine, as reading the extra zeros conveys the different magnitudes in the most compact way.</p>
 ]]></content:encoded>
	</item>
	<item>
		<title>By: lemuel pitkin</title>
		<link>http://crookedtimber.org/2009/01/03/visualizing-wpa-expenditures/comment-page-1/#comment-262517</link>
		<dc:creator>lemuel pitkin</dc:creator>
		<pubDate>Mon, 05 Jan 2009 15:49:33 +0000</pubDate>
		<guid isPermaLink="false">http://crookedtimber.org/?p=9048#comment-262517</guid>
		<description>Or to put it a little more shaprly -- by arbitrarily adjsuting the horizontal scale, you can give a curve like this whatever shape uyou want. But what does a graph tell you about the underlying data when its shape is simply imposed by hand?</description>
		<content:encoded><![CDATA[	<p>Or to put it a little more shaprly&#8212;by arbitrarily adjsuting the horizontal scale, you can give a curve like this whatever shape uyou want. But what does a graph tell you about the underlying data when its shape is simply imposed by hand?</p>
 ]]></content:encoded>
	</item>
	<item>
		<title>By: lemuel pitkin</title>
		<link>http://crookedtimber.org/2009/01/03/visualizing-wpa-expenditures/comment-page-1/#comment-262515</link>
		<dc:creator>lemuel pitkin</dc:creator>
		<pubDate>Mon, 05 Jan 2009 15:42:00 +0000</pubDate>
		<guid isPermaLink="false">http://crookedtimber.org/?p=9048#comment-262515</guid>
		<description>I have to agree with Zamfir and Andrew Cooke.  But I&#039;d like to hear Kieran&#039;s response.

My impression:

At first glance, the graph seems to say that there were spending categories distributed more or less evenly across the whole range of spending levels, with roads only a modest outlier. Second glance, you notice the key up top and think it&#039;s a straight line on a log scale. Naturally, you expect a horizontal increment under &quot;hundreds of millions&quot; to be ten times as much as one under &quot;tens of millions&quot;. But no, that&#039;s not the case either. Or is it that the items in the same panel are comparable in size, with each white space representing an order-of-magnitude break? But no, the middle break isn&#039;t really a break at all. 

As far as I can tell, the visual impression given by the graph -- the smooth slope of the points -- just has no relationship to the underlying data at all. So what&#039;s the advantage of this presentation over a simple table? or over Agnew&#039;s double graph?</description>
		<content:encoded><![CDATA[	<p>I have to agree with Zamfir and Andrew Cooke.  But I&#8217;d like to hear Kieran&#8217;s response.</p>

	<p>My impression:</p>

	<p>At first glance, the graph seems to say that there were spending categories distributed more or less evenly across the whole range of spending levels, with roads only a modest outlier. Second glance, you notice the key up top and think it&#8217;s a straight line on a log scale. Naturally, you expect a horizontal increment under &#8220;hundreds of millions&#8221; to be ten times as much as one under &#8220;tens of millions&#8221;. But no, that&#8217;s not the case either. Or is it that the items in the same panel are comparable in size, with each white space representing an order-of-magnitude break? But no, the middle break isn&#8217;t really a break at all.</p>

	<p>As far as I can tell, the visual impression given by the graph&#8212;the smooth slope of the points&#8212;just has no relationship to the underlying data at all. So what&#8217;s the advantage of this presentation over a simple table? or over Agnew&#8217;s double graph?</p>
 ]]></content:encoded>
	</item>
	<item>
		<title>By: Zamfir</title>
		<link>http://crookedtimber.org/2009/01/03/visualizing-wpa-expenditures/comment-page-1/#comment-262500</link>
		<dc:creator>Zamfir</dc:creator>
		<pubDate>Mon, 05 Jan 2009 10:51:27 +0000</pubDate>
		<guid isPermaLink="false">http://crookedtimber.org/?p=9048#comment-262500</guid>
		<description>Apologies for the double-post, I thought a bit more about it... The thing is, I am wondering whether a simple table with numbers would not be more effective than this particular graph. The advantages of a graph over table would be that you can visually compare magnitudes, and that patterns such as breaks are clearly visible. 

But this particular graph makes visual comparison impossible without looking up the actual numbers on the scale, and the breaks and their relative importance are only noticable if you study the graph really well. If you just printed the numbers, the larger number of digits would show the breaks at least as clear as this graph.</description>
		<content:encoded><![CDATA[	<p>Apologies for the double-post, I thought a bit more about it&#8230; The thing is, I am wondering whether a simple table with numbers would not be more effective than this particular graph. The advantages of a graph over table would be that you can visually compare magnitudes, and that patterns such as breaks are clearly visible.</p>

	<p>But this particular graph makes visual comparison impossible without looking up the actual numbers on the scale, and the breaks and their relative importance are only noticable if you study the graph really well. If you just printed the numbers, the larger number of digits would show the breaks at least as clear as this graph.</p>
 ]]></content:encoded>
	</item>
	<item>
		<title>By: Zamfir</title>
		<link>http://crookedtimber.org/2009/01/03/visualizing-wpa-expenditures/comment-page-1/#comment-262499</link>
		<dc:creator>Zamfir</dc:creator>
		<pubDate>Mon, 05 Jan 2009 10:29:31 +0000</pubDate>
		<guid isPermaLink="false">http://crookedtimber.org/?p=9048#comment-262499</guid>
		<description>I am afraid I have to agree with Andrew Cooke here, I think this solution introduces more problems than it solves. Your plot hides two jumps below 30 million and below 1 billion, suggesting a straight line that does not exist at all. Even more confusingly, the break at 100 million does not hide a jump to the same extent as the other breaks do.

As such, i think I like Agnew&#039;s solution more, also because it warns more clearly that it uses a &quot;non-standard&quot; way of plotting.  If you really want to do it in your way, I would make at most one break and make the white-space between them a lot larger.  Perhaps you can also introduce horizontal whitespace? 

My own solution to these kinds of situations is to use the small map/large map trick from newspapers: I make two graphs, and draw (in an external drawing program) a thick rectangle around the part of the billions-graph that goes on to be the millions-graph.</description>
		<content:encoded><![CDATA[	<p>I am afraid I have to agree with Andrew Cooke here, I think this solution introduces more problems than it solves. Your plot hides two jumps below 30 million and below 1 billion, suggesting a straight line that does not exist at all. Even more confusingly, the break at 100 million does not hide a jump to the same extent as the other breaks do.</p>

	<p>As such, i think I like Agnew&#8217;s solution more, also because it warns more clearly that it uses a &#8220;non-standard&#8221; way of plotting.  If you really want to do it in your way, I would make at most one break and make the white-space between them a lot larger.  Perhaps you can also introduce horizontal whitespace?</p>

	<p>My own solution to these kinds of situations is to use the small map/large map trick from newspapers: I make two graphs, and draw (in an external drawing program) a thick rectangle around the part of the billions-graph that goes on to be the millions-graph.</p>
 ]]></content:encoded>
	</item>
	<item>
		<title>By: salient</title>
		<link>http://crookedtimber.org/2009/01/03/visualizing-wpa-expenditures/comment-page-1/#comment-262465</link>
		<dc:creator>salient</dc:creator>
		<pubDate>Sun, 04 Jan 2009 18:27:43 +0000</pubDate>
		<guid isPermaLink="false">http://crookedtimber.org/?p=9048#comment-262465</guid>
		<description>&lt;i&gt;My irritation is with people who consider there to be such things as generic rules for communicative acts without regard to audience or context, despite all the evidence against such such things.&lt;/i&gt;

Says the person who is writing in grammatically appropriate sentences, which obey generic rules for the communicative act of writing. Or in a different context, would you have said rriiion aymt pswiht audnlascoa and expected to have gotten your point across all the more efficiently? Being a human being, communicating to other human beings who share a common language, implies enough context to start making at least rudimentary judgments about efficiency.

That having been said, the panel discontinuity of this graph is an excellent tweak. What a log scale tends to mask, this clarifies pretty well. I still get the immediate impression of what spending dwarfs what other spending, and I can compare two values relatively easily.

&lt;i&gt;that means that a first glance shows an almost flat rise when, in fact, there are different scales involved&lt;/i&gt;

...in general, for this kind of data, we&#039;re not trying to determine whether there&#039;s a linear or cubic or what-have-you relationship between points. We&#039;re comparing quantities that in some sense are not determined by one another. People who aren&#039;t scientists and don&#039;t work frequently with models themselves won&#039;t make the immediate association between an approximate-linear graph and the rather sophisticated notion of slope. You look at this graph and you see roads all by itself, in a block set aside all for itself: you get the idea that spending on roads dwarfs nearly everything else. It&#039;s not as skull-crushingly obvious &quot;at first glance&quot; as a basic log scale, but Kieran&#039;s striking a balance.

&lt;i&gt;It’s striking how complex even quite simple data can be to present effectively.&lt;/i&gt;

I&#039;d have preferred: 1, more room between each continuous block. 2, that billions be expressed as thousands of millions along the horizontal axis (the use of 1bn, 2bn, etc was a little ill-advised). Other than those minor aesthetic tweaks, this presentation seems very effective.</description>
		<content:encoded><![CDATA[	<p><i>My irritation is with people who consider there to be such things as generic rules for communicative acts without regard to audience or context, despite all the evidence against such such things.</i></p>

	<p>Says the person who is writing in grammatically appropriate sentences, which obey generic rules for the communicative act of writing. Or in a different context, would you have said rriiion aymt pswiht audnlascoa and expected to have gotten your point across all the more efficiently? Being a human being, communicating to other human beings who share a common language, implies enough context to start making at least rudimentary judgments about efficiency.</p>

	<p>That having been said, the panel discontinuity of this graph is an excellent tweak. What a log scale tends to mask, this clarifies pretty well. I still get the immediate impression of what spending dwarfs what other spending, and I can compare two values relatively easily.</p>

	<p><i>that means that a first glance shows an almost flat rise when, in fact, there are different scales involved</i></p>

	<p>&#8230;in general, for this kind of data, we&#8217;re not trying to determine whether there&#8217;s a linear or cubic or what-have-you relationship between points. We&#8217;re comparing quantities that in some sense are not determined by one another. People who aren&#8217;t scientists and don&#8217;t work frequently with models themselves won&#8217;t make the immediate association between an approximate-linear graph and the rather sophisticated notion of slope. You look at this graph and you see roads all by itself, in a block set aside all for itself: you get the idea that spending on roads dwarfs nearly everything else. It&#8217;s not as skull-crushingly obvious &#8220;at first glance&#8221; as a basic log scale, but Kieran&#8217;s striking a balance.</p>

	<p><i>It&#8217;s striking how complex even quite simple data can be to present effectively.</i></p>

	<p>I&#8217;d have preferred: 1, more room between each continuous block. 2, that billions be expressed as thousands of millions along the horizontal axis (the use of 1bn, 2bn, etc was a little ill-advised). Other than those minor aesthetic tweaks, this presentation seems very effective.</p>
 ]]></content:encoded>
	</item>
	<item>
		<title>By: andrew cooke</title>
		<link>http://crookedtimber.org/2009/01/03/visualizing-wpa-expenditures/comment-page-1/#comment-262453</link>
		<dc:creator>andrew cooke</dc:creator>
		<pubDate>Sun, 04 Jan 2009 11:44:47 +0000</pubDate>
		<guid isPermaLink="false">http://crookedtimber.org/?p=9048#comment-262453</guid>
		<description>i think it&#039;s a disaster, to be honest.

first, the scales have been chose so that the blue dots form a &quot;line&quot; across category boundaries.  that means that a first glance shows an almost flat rise when, in fact, there are different scales involved (agnew&#039;s plot shows the actual structure much more clearly).  in other words, structure in the data has been purposefully(!) hidden by the careful choice of scale boundaries (an apparently straight line across different scales &lt;em&gt;does&lt;/em&gt; smell - misleadingly - like a power law).

second (in a sense the same point repeated), there&#039;s no single zero point for the x axis.  there&#039;s no way of seeing that one point is worth twice another, even within the same scale, until you go look at the numbers.

i find it particularly depressing because it imitates tufte while ignoring the basic principles behind his work.  the point is not that something &lt;em&gt;look&lt;/em&gt; simple, but that it actually &lt;em&gt;is&lt;/em&gt; simple.  agnew&#039;s plot loses (slightly) on the &quot;style&quot; stakes, but more than makes up by being faithful to the original data.  clarity of presentation must emerge from clarity of thought; arranging things in an ad-hoc manner to make them look simple is - well, you must know, in your heart of hearts, that this sucks deeply?</description>
		<content:encoded><![CDATA[	<p>i think it&#8217;s a disaster, to be honest.</p>

	<p>first, the scales have been chose so that the blue dots form a &#8220;line&#8221; across category boundaries.  that means that a first glance shows an almost flat rise when, in fact, there are different scales involved (agnew&#8217;s plot shows the actual structure much more clearly).  in other words, structure in the data has been purposefully(!) hidden by the careful choice of scale boundaries (an apparently straight line across different scales <em>does</em> smell &#8211; misleadingly &#8211; like a power law).</p>

	<p>second (in a sense the same point repeated), there&#8217;s no single zero point for the x axis.  there&#8217;s no way of seeing that one point is worth twice another, even within the same scale, until you go look at the numbers.</p>

	<p>i find it particularly depressing because it imitates tufte while ignoring the basic principles behind his work.  the point is not that something <em>look</em> simple, but that it actually <em>is</em> simple.  agnew&#8217;s plot loses (slightly) on the &#8220;style&#8221; stakes, but more than makes up by being faithful to the original data.  clarity of presentation must emerge from clarity of thought; arranging things in an ad-hoc manner to make them look simple is &#8211; well, you must know, in your heart of hearts, that this sucks deeply?</p>
 ]]></content:encoded>
	</item>
	<item>
		<title>By: MQ</title>
		<link>http://crookedtimber.org/2009/01/03/visualizing-wpa-expenditures/comment-page-1/#comment-262451</link>
		<dc:creator>MQ</dc:creator>
		<pubDate>Sun, 04 Jan 2009 05:28:36 +0000</pubDate>
		<guid isPermaLink="false">http://crookedtimber.org/?p=9048#comment-262451</guid>
		<description>&quot;sewing&quot;?</description>
		<content:encoded><![CDATA[	<p>&#8220;sewing&#8221;?</p>
 ]]></content:encoded>
	</item>
	<item>
		<title>By: Kieran Healy</title>
		<link>http://crookedtimber.org/2009/01/03/visualizing-wpa-expenditures/comment-page-1/#comment-262449</link>
		<dc:creator>Kieran Healy</dc:creator>
		<pubDate>Sun, 04 Jan 2009 04:36:58 +0000</pubDate>
		<guid isPermaLink="false">http://crookedtimber.org/?p=9048#comment-262449</guid>
		<description>&lt;i&gt; But thinking about it more, it won’t work, because it would just reproduce the original plot with the billions dwarfing the smaller numbers.&lt;/i&gt;

Yes, I was just in the process of writing up a comment to that effect --- I should have realized it myself, as I&#039;d tried it already yesterday and that&#039;s exactly what happened.

&lt;i&gt;For this chart you could perhaps use geom_blank to add a dummy dataset and layer that pushed out the limits of the individual scales – that would ensure that you at least had consistent scales across the different orders of magnitude.&lt;/i&gt;

I&#039;ll check it out. 

&lt;i&gt;p.s. it’s really nice to see ggplot2 in the “wild” :)&lt;/i&gt;

It&#039;s a great package -- thanks for writing it. An earlier effort in the same vein as this one is &lt;a href=&quot;http://crookedtimber.org/2008/11/19/make-work/&quot; rel=&quot;nofollow&quot;&gt;here&lt;/a&gt;. I&#039;m much more used to the lattice framework, so it&#039;s taken me a bit of time to get used to the ggplot approach (which is also one of the reasons I mess around with this sort of data -- to learn the syntax). The new version of the book is very helpful, btw.</description>
		<content:encoded><![CDATA[	<p><i> But thinking about it more, it won&#8217;t work, because it would just reproduce the original plot with the billions dwarfing the smaller numbers.</i></p>

	<p>Yes, I was just in the process of writing up a comment to that effect&#8212;- I should have realized it myself, as I&#8217;d tried it already yesterday and that&#8217;s exactly what happened.</p>

	<p><i>For this chart you could perhaps use geom_blank to add a dummy dataset and layer that pushed out the limits of the individual scales &#8211; that would ensure that you at least had consistent scales across the different orders of magnitude.</i></p>

	<p>I&#8217;ll check it out.</p>

	<p><i>p.s. it&#8217;s really nice to see ggplot2 in the &#8220;wild&#8221; :)</i></p>

	<p>It&#8217;s a great package&#8212;thanks for writing it. An earlier effort in the same vein as this one is <a href="http://crookedtimber.org/2008/11/19/make-work/" rel="nofollow">here</a>. I&#8217;m much more used to the lattice framework, so it&#8217;s taken me a bit of time to get used to the ggplot approach (which is also one of the reasons I mess around with this sort of data&#8212;to learn the syntax). The new version of the book is very helpful, btw.</p>
 ]]></content:encoded>
	</item>
	<item>
		<title>By: Hadley</title>
		<link>http://crookedtimber.org/2009/01/03/visualizing-wpa-expenditures/comment-page-1/#comment-262448</link>
		<dc:creator>Hadley</dc:creator>
		<pubDate>Sun, 04 Jan 2009 04:28:02 +0000</pubDate>
		<guid isPermaLink="false">http://crookedtimber.org/?p=9048#comment-262448</guid>
		<description>p.s. it&#039;s really nice to see ggplot2 in the &quot;wild&quot; :)</description>
		<content:encoded><![CDATA[	<p>p.s. it&#8217;s really nice to see ggplot2 in the &#8220;wild&#8221; :)</p>
 ]]></content:encoded>
	</item>
	<item>
		<title>By: Hadley</title>
		<link>http://crookedtimber.org/2009/01/03/visualizing-wpa-expenditures/comment-page-1/#comment-262447</link>
		<dc:creator>Hadley</dc:creator>
		<pubDate>Sun, 04 Jan 2009 04:24:44 +0000</pubDate>
		<guid isPermaLink="false">http://crookedtimber.org/?p=9048#comment-262447</guid>
		<description>You&#039;d think I&#039;d be able to remember the arguments to my own code - it&#039;s space not shape.       But thinking about it more, it won&#039;t work, because it would just reproduce the original plot with the billions dwarfing the smaller numbers.  There probably should be some way to specify per facet labels, breaks and limits, but I haven&#039;t come up with a clean way of doing it yet.     

For this chart you could perhaps use &lt;code&gt;geom_blank&lt;/code&gt; to add a dummy dataset and layer that pushed out the limits of the individual scales - that would ensure that you at least had consistent scales across the different orders of magnitude.</description>
		<content:encoded><![CDATA[	<p>You&#8217;d think I&#8217;d be able to remember the arguments to my own code &#8211; it&#8217;s space not shape.       But thinking about it more, it won&#8217;t work, because it would just reproduce the original plot with the billions dwarfing the smaller numbers.  There probably should be some way to specify per facet labels, breaks and limits, but I haven&#8217;t come up with a clean way of doing it yet.</p>

	<p>For this chart you could perhaps use <code>geom_blank</code> to add a dummy dataset and layer that pushed out the limits of the individual scales &#8211; that would ensure that you at least had consistent scales across the different orders of magnitude.</p>
 ]]></content:encoded>
	</item>
	<item>
		<title>By: Kieran Healy</title>
		<link>http://crookedtimber.org/2009/01/03/visualizing-wpa-expenditures/comment-page-1/#comment-262444</link>
		<dc:creator>Kieran Healy</dc:creator>
		<pubDate>Sun, 04 Jan 2009 02:11:18 +0000</pubDate>
		<guid isPermaLink="false">http://crookedtimber.org/?p=9048#comment-262444</guid>
		<description>Hi Hadley, 

&lt;i&gt;Maybe you want facet_grid(…, shape = “free”)?&lt;/i&gt;

The basic plot is an object with custom breaks which is then built up first with geom_point() and then facet_grid(. ~ Order, scale=&quot;free&quot;), where Order is the factor that distinguishes the panels (&quot;Millions&quot;, &quot;Tens of Millions&quot; etc). If I substitute shape=&quot;free&quot; instead, I get an error:

&lt;i&gt;Error in get(&quot;new&quot;, env = FacetGrid, inherits = TRUE)(FacetGrid, ...) : 
  unused argument(s) (shape = &quot;free&quot;)&lt;/i&gt;

The full code is:

&lt;i&gt;
llabs &lt; -c(&quot;1&quot;,&quot;2&quot;,&quot;3&quot;,&quot;4&quot;,&quot;30&quot;,&quot;40&quot;,&quot;50&quot;,&quot;60&quot;,
          &quot;80&quot;,&quot;100&quot;,&quot;200&quot;,&quot;300&quot;,&quot;400&quot;,&quot;500&quot;,&quot;1bn&quot;,&quot;2bn&quot;,&quot;3bn&quot;,&quot;4bn&quot;, &quot;5bn&quot;)

p &lt;- ggplot(data, aes(Spending, reorder(Category,Spending))) +
  scale_y_discrete(name=&quot; &quot;) + scale_x_continuous(name=&quot;Millions of Nominal Dollars&quot;, breaks=c(1,2,3,4,30,40,50,60,80,100,200,300,400,500,1000,2000,3000,4000,5000),labels=llabs) + geom_point(colour=&quot;blue&quot;,size=2.5)

p + facet_grid(. ~ Order, scalee=&quot;free&quot;) + opts(axis.text.y=theme_text(colour=&quot;#000000&quot;,hjust=1),
                            axis.text.x=theme_text(colour=&quot;#000000&quot;,vjust=1)) + opts(title=&quot;Scale and Allocation of Total Expenditure from WPA and Sponsors&#039; Funds, through March 1943\n&quot;)
&lt;/i&gt;

Without the custom breaks (which aren&#039;t ideal) I found some ticks being repeated on adjacent panels. Is there a a way to control the width of separate panels, or would that entail constructing completely different objects one at a time?

(For the rest of you following along, &lt;a href=&quot;http://had.co.nz/&quot; rel=&quot;nofollow&quot;&gt;Hadley&lt;/a&gt; is the author of the R package that does all the heavy lifting in this graph.)&lt;/i&gt;</description>
		<content:encoded><![CDATA[	<p>Hi Hadley,</p>

	<p><i>Maybe you want facet_grid(&#8230;, shape = &#8220;free&#8221;)?</i></p>

	<p>The basic plot is an object with custom breaks which is then built up first with geom_point() and then facet_grid(. ~ Order, scale=&#8221;free&#8221;), where Order is the factor that distinguishes the panels (&#8220;Millions&#8221;, &#8220;Tens of Millions&#8221; etc). If I substitute shape=&#8221;free&#8221; instead, I get an error:</p>

	<p><i>Error in get(&#8220;new&#8221;, env = FacetGrid, inherits = <span class="caps">TRUE</span>)(FacetGrid, &#8230;) :<br />
unused argument(s) (shape = &#8220;free&#8221;)</i></p>

	<p>The full code is:</p>

	<p><i><br />
llabs < -c(&#8220;1&#8221;,&#8221;2&#8221;,&#8221;3&#8221;,&#8221;4&#8221;,&#8221;30&#8221;,&#8221;40&#8221;,&#8221;50&#8221;,&#8221;60&#8221;,<br />
&#8220;80&#8221;,&#8221;100&#8221;,&#8221;200&#8221;,&#8221;300&#8221;,&#8221;400&#8221;,&#8221;500&#8221;,&#8221;1bn&#8221;,&#8221;2bn&#8221;,&#8221;3bn&#8221;,&#8221;4bn&#8221;, &#8220;5bn&#8221;)</i></p>

	<p>p < - ggplot(data, aes(Spending, reorder(Category,Spending))) +<br />
scale_y_discrete(name=&#8221; &#8220;) + scale_x_continuous(name=&#8221;Millions of Nominal Dollars&#8221;, breaks=c(1,2,3,4,30,40,50,60,80,100,200,300,400,500,1000,2000,3000,4000,5000),labels=llabs) + geom_point(colour=&#8221;blue&#8221;,size=2.5)</p>

	<p>p + facet_grid(. ~ Order, scalee=&#8221;free&#8221;) + opts(axis.text.y=theme_text(colour=&#8221;#000000&#8221;,hjust=1),<br />
axis.text.x=theme_text(colour=&#8221;#000000&#8221;,vjust=1)) + opts(title=&#8221;Scale and Allocation of Total Expenditure from <span class="caps">WPA</span> and Sponsors&#8217; Funds, through March 1943n&#8221;)<br />
</p>

	<p>Without the custom breaks (which aren&#8217;t ideal) I found some ticks being repeated on adjacent panels. Is there a a way to control the width of separate panels, or would that entail constructing completely different objects one at a time?</p>

	<p>(For the rest of you following along, <a href="http://had.co.nz/" rel="nofollow">Hadley</a> is the author of the R package that does all the heavy lifting in this graph.)</p>
 ]]></content:encoded>
	</item>
	<item>
		<title>By: Charles S</title>
		<link>http://crookedtimber.org/2009/01/03/visualizing-wpa-expenditures/comment-page-1/#comment-262442</link>
		<dc:creator>Charles S</dc:creator>
		<pubDate>Sun, 04 Jan 2009 00:34:02 +0000</pubDate>
		<guid isPermaLink="false">http://crookedtimber.org/?p=9048#comment-262442</guid>
		<description>I think it would be better without the discontinuity in the upper hundred millions. I don&#039;t think that there is anyone who will correctly read your chart to say that sewing had twice the expenditure as conservation, and that the discontinuity between recreation and airports is only half the size of the discontinuity between sewing and conservation.  I do like the idea of breaking the graph up into linear sections based on orders of magnitude (instead of a log scale), particularly for a non-science audience, but I think that introducing discontinuities at the shifts in scale creates more confusion rather than simplicity.  

Even after noticing the discontinuity at Sewing, I had almost finished this comment and was just looking at the chart again when I noticed that writing (just below $30 million, and arbitrarily at the bottom of the tens of millions category) received more than 5 times what Household workers training received (just over $4 million and arbitrarily at the top of the millions category), even though the two dots are very close together.

The idea of adding headers naming each order of magnitude is very nice, and would work well with a true log scale as well.</description>
		<content:encoded><![CDATA[	<p>I think it would be better without the discontinuity in the upper hundred millions. I don&#8217;t think that there is anyone who will correctly read your chart to say that sewing had twice the expenditure as conservation, and that the discontinuity between recreation and airports is only half the size of the discontinuity between sewing and conservation.  I do like the idea of breaking the graph up into linear sections based on orders of magnitude (instead of a log scale), particularly for a non-science audience, but I think that introducing discontinuities at the shifts in scale creates more confusion rather than simplicity.</p>

	<p>Even after noticing the discontinuity at Sewing, I had almost finished this comment and was just looking at the chart again when I noticed that writing (just below $30 million, and arbitrarily at the bottom of the tens of millions category) received more than 5 times what Household workers training received (just over $4 million and arbitrarily at the top of the millions category), even though the two dots are very close together.</p>

	<p>The idea of adding headers naming each order of magnitude is very nice, and would work well with a true log scale as well.</p>
 ]]></content:encoded>
	</item>
	<item>
		<title>By: Hadley</title>
		<link>http://crookedtimber.org/2009/01/03/visualizing-wpa-expenditures/comment-page-1/#comment-262441</link>
		<dc:creator>Hadley</dc:creator>
		<pubDate>Sat, 03 Jan 2009 23:05:46 +0000</pubDate>
		<guid isPermaLink="false">http://crookedtimber.org/?p=9048#comment-262441</guid>
		<description>Maybe you want facet_grid(..., shape = &quot;free&quot;)? I&#039;m guessing you&#039;re using a custom breaks and labels argument for the x axis, rather than modifying it afterwards.  (It looks like you missed 70)</description>
		<content:encoded><![CDATA[	<p>Maybe you want facet_grid(&#8230;, shape = &#8220;free&#8221;)? I&#8217;m guessing you&#8217;re using a custom breaks and labels argument for the x axis, rather than modifying it afterwards.  (It looks like you missed 70)</p>
 ]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Minified using disk: basic
Page Caching using disk: enhanced

Served from: crookedtimber.org @ 2012-02-13 09:35:31 -->
