<?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 for Source-Filter</title>
	<atom:link href="http://www.nhsilbert.net/source/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.nhsilbert.net/source</link>
	<description>Statistics, Models, Language, Cognition, and Assorted Whatnots</description>
	<lastBuildDate>Sat, 18 May 2013 03:21:39 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.5.1</generator>
	<item>
		<title>Comment on A bad graph by Noah Motion</title>
		<link>http://www.nhsilbert.net/source/2013/05/a-bad-graph/#comment-1996</link>
		<dc:creator>Noah Motion</dc:creator>
		<pubDate>Sat, 18 May 2013 03:21:39 +0000</pubDate>
		<guid isPermaLink="false">http://www.nhsilbert.net/source/?p=1465#comment-1996</guid>
		<description><![CDATA[I think you hit the nail on the head. The error in the graph seems much more likely to be due to a combination of sloppiness and a bad choice of graph type than malice. Not to mention that it&#039;s not at all obvious that the graph is off by a factor of 1.8 when you just look at it (and don&#039;t measure it). Areas like these don&#039;t seem particularly easy to compare, at least not across factors of ~200.

It also occurred to me while writing the post that the figure could easily have been someone else&#039;s idea entirely. The prose I quote appears directly above the graph, which makes it seem extremely silly in situ.]]></description>
		<content:encoded><![CDATA[<p>I think you hit the nail on the head. The error in the graph seems much more likely to be due to a combination of sloppiness and a bad choice of graph type than malice. Not to mention that it&#8217;s not at all obvious that the graph is off by a factor of 1.8 when you just look at it (and don&#8217;t measure it). Areas like these don&#8217;t seem particularly easy to compare, at least not across factors of ~200.</p>
<p>It also occurred to me while writing the post that the figure could easily have been someone else&#8217;s idea entirely. The prose I quote appears directly above the graph, which makes it seem extremely silly in situ.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on A bad graph by Christian DiCanio</title>
		<link>http://www.nhsilbert.net/source/2013/05/a-bad-graph/#comment-1995</link>
		<dc:creator>Christian DiCanio</dc:creator>
		<pubDate>Sat, 18 May 2013 02:16:31 +0000</pubDate>
		<guid isPermaLink="false">http://www.nhsilbert.net/source/?p=1465#comment-1995</guid>
		<description><![CDATA[You could state your observed differences in terms of what Tufte calls the &quot;Lie factor.&quot; So, 233/132.25 = 1.76. This isn&#039;t actually too terrible of a lie factor, but it is still lying. In Silver&#039;s defense, he has no reason to lie about something that would only help show his point if properly depicted. So, I don&#039;t think this is necessarily intentional, just perhaps lazy.

As for whether a figure is necessary, I completely agree with you; it&#039;s not. I imagine that an editor may have decided, just as many do, that too much text without figures is inherently boring. However, it seems that the editor underestimates the audience here. Those who are reading Nate Silver&#039;s book probably don&#039;t need pictures every third page to hold their attention.]]></description>
		<content:encoded><![CDATA[<p>You could state your observed differences in terms of what Tufte calls the &#8220;Lie factor.&#8221; So, 233/132.25 = 1.76. This isn&#8217;t actually too terrible of a lie factor, but it is still lying. In Silver&#8217;s defense, he has no reason to lie about something that would only help show his point if properly depicted. So, I don&#8217;t think this is necessarily intentional, just perhaps lazy.</p>
<p>As for whether a figure is necessary, I completely agree with you; it&#8217;s not. I imagine that an editor may have decided, just as many do, that too much text without figures is inherently boring. However, it seems that the editor underestimates the audience here. Those who are reading Nate Silver&#8217;s book probably don&#8217;t need pictures every third page to hold their attention.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Font size and orientation in dendrograms in R by Noah Motion</title>
		<link>http://www.nhsilbert.net/source/2013/04/font-size-and-orientation-in-dendrograms-in-r/#comment-1974</link>
		<dc:creator>Noah Motion</dc:creator>
		<pubDate>Tue, 30 Apr 2013 14:05:51 +0000</pubDate>
		<guid isPermaLink="false">http://www.nhsilbert.net/source/?p=1410#comment-1974</guid>
		<description><![CDATA[Why didn&#039;t I think of that?!

If one is not careful, Power Point can rock one&#039;s socks off.]]></description>
		<content:encoded><![CDATA[<p>Why didn&#8217;t I think of that?!</p>
<p>If one is not careful, Power Point can rock one&#8217;s socks off.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Font size and orientation in dendrograms in R by Brian Marks</title>
		<link>http://www.nhsilbert.net/source/2013/04/font-size-and-orientation-in-dendrograms-in-r/#comment-1947</link>
		<dc:creator>Brian Marks</dc:creator>
		<pubDate>Thu, 18 Apr 2013 12:22:21 +0000</pubDate>
		<guid isPermaLink="false">http://www.nhsilbert.net/source/?p=1410#comment-1947</guid>
		<description><![CDATA[Why don&#039;t you just load the figure into PowerPoint and then put the labels wherever you want?  Point and click, and voila!  PowerPoint rocks!]]></description>
		<content:encoded><![CDATA[<p>Why don&#8217;t you just load the figure into PowerPoint and then put the labels wherever you want?  Point and click, and voila!  PowerPoint rocks!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Font size and orientation in dendrograms in R by Mark VanDam</title>
		<link>http://www.nhsilbert.net/source/2013/04/font-size-and-orientation-in-dendrograms-in-r/#comment-1946</link>
		<dc:creator>Mark VanDam</dc:creator>
		<pubDate>Wed, 17 Apr 2013 22:23:30 +0000</pubDate>
		<guid isPermaLink="false">http://www.nhsilbert.net/source/?p=1410#comment-1946</guid>
		<description><![CDATA[This is nice.  I&#039;ve done very similar things with MATLAB, for example, getting multiple rows or angled labels into figures.  Since this is a space to be pedantic, however, I think you need a different font for these characters.  I see you used the unicode, but it&#039;s my impression that IPA fonts are serif fonts, not the sans-serif fonts that appear in your dendogram.  I&#039;ll leave it up to you how to accomplish that.]]></description>
		<content:encoded><![CDATA[<p>This is nice.  I&#8217;ve done very similar things with MATLAB, for example, getting multiple rows or angled labels into figures.  Since this is a space to be pedantic, however, I think you need a different font for these characters.  I see you used the unicode, but it&#8217;s my impression that IPA fonts are serif fonts, not the sans-serif fonts that appear in your dendogram.  I&#8217;ll leave it up to you how to accomplish that.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Semantic analysis by Noah Motion</title>
		<link>http://www.nhsilbert.net/source/2013/02/semantic-analysis/#comment-1419</link>
		<dc:creator>Noah Motion</dc:creator>
		<pubDate>Mon, 04 Feb 2013 04:16:42 +0000</pubDate>
		<guid isPermaLink="false">http://www.nhsilbert.net/source/?p=1368#comment-1419</guid>
		<description><![CDATA[Google says the synonym is &#039;elk&#039;, but Solly told me later in the day that it&#039;s &#039;mooses&#039;.]]></description>
		<content:encoded><![CDATA[<p>Google says the synonym is &#8216;elk&#8217;, but Solly told me later in the day that it&#8217;s &#8216;mooses&#8217;.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Semantic analysis by Mike Reynolds</title>
		<link>http://www.nhsilbert.net/source/2013/02/semantic-analysis/#comment-1418</link>
		<dc:creator>Mike Reynolds</dc:creator>
		<pubDate>Sun, 03 Feb 2013 23:17:21 +0000</pubDate>
		<guid isPermaLink="false">http://www.nhsilbert.net/source/?p=1368#comment-1418</guid>
		<description><![CDATA[a) The &#039;Popso&#039; name was forming when I was overstaying my welcome at your house 10 years ago this summer.  I didn&#039;t realize that it had stuck through so many years and kids.
b) 10 years! The time, how she flies.
c) So what&#039;s the synonym for moose?  I&#039;m dying to know.
Love,
Mike]]></description>
		<content:encoded><![CDATA[<p>a) The &#8216;Popso&#8217; name was forming when I was overstaying my welcome at your house 10 years ago this summer.  I didn&#8217;t realize that it had stuck through so many years and kids.<br />
b) 10 years! The time, how she flies.<br />
c) So what&#8217;s the synonym for moose?  I&#8217;m dying to know.<br />
Love,<br />
Mike</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on When is a parameter not a parameter? by Noah Motion</title>
		<link>http://www.nhsilbert.net/source/2013/01/when-is-a-parameter-not-a-parameter/#comment-1324</link>
		<dc:creator>Noah Motion</dc:creator>
		<pubDate>Mon, 21 Jan 2013 19:43:55 +0000</pubDate>
		<guid isPermaLink="false">http://www.nhsilbert.net/source/?p=1350#comment-1324</guid>
		<description><![CDATA[The more I think about it, the more I&#039;m with Gelman on this (see, e.g., &lt;a href=&quot;http://www.stat.columbia.edu/~gelman/research/published/AOS259.pdf&quot; rel=&quot;nofollow&quot;&gt;section 6 of this paper&lt;/a&gt; and pp. 262-265 of &lt;a href=&quot;http://www.stat.columbia.edu/~gelman/arm/&quot; rel=&quot;nofollow&quot;&gt;Gelman &amp; Hill&#039;s book&lt;/a&gt;). The section 6 bit addresses fixed vs. random effects terminology in general (arguing that it&#039;s more useful to talk about constant vs. varying parameters), and the book section illustrates how there are a number of mathematically equivalent ways of writing &#039;mixed effects&#039; models, a number of which make it pretty clear that the &#039;random effects&#039; bits are parameters, too.

The fact that the random effects are estimated differently than are the parameters governing them doesn&#039;t make the former something other than parameters. The key difference between fixed effects and random effects here is that random effects are modeled (i.e., there are variances and covariances governing them [as well as means, namely the associated fixed effects]) whereas the fixed effects aren&#039;t. Yet there is still uncertainty about the fixed effects, else why have standard errors and confidence intervals and all the associated statistical testing machinery?

Bates says (on p. 2 of lrgprt.pdf) that &quot;random effects are unobserved random variables.&quot; Well, the fixed effects aren&#039;t observed either, and the fact that nobody disputes that there is uncertainty about them (again, CIs, SEs, etc...) suggests that, whether we&#039;re modeling them or not (i.e., whether we are willing to make particular distributional assumptions about them or not), there is an element of randomness smack dab in the middle of fixed effect estimation, too.

Ultimately, I can&#039;t figure out what exactly Bates and others mean by &#039;parameter&#039; that includes fixed effects and variances/covariances while excluding random effects.

This distinction, whatever it is, seems at odds with a lot of other statistical modeling, too. For example, in CFA and SEM, there are potentially huge numbers of latent variables, all of which are parameters in those models. Pretty much all of the cognitive/math psych modeling I know about has analogous structure - latent variables like the spatial location, dimension weights, and bias parameters in &lt;a href=&quot;http://www.cogs.indiana.edu/nosofsky/pubs/1986_rmn_jep-g_attention.pdf&quot; rel=&quot;nofollow&quot;&gt;Generalized Context Model&lt;/a&gt; or the means and correlations in the perceptual distributions in &lt;a href=&quot;http://www.perceptionweb.com/abstract.cgi?id=p261101&quot; rel=&quot;nofollow&quot;&gt;GRT&lt;/a&gt;. I link to those two papers specifically because they illustrate maximum likelihood estimation and not Bayesian estimation (i.e., the unobserved parameters aren&#039;t explicitly probabilistically modeled).

The fact that the variance of the estimated random effects can be different from the estimated variance doesn&#039;t do much work here either. For any given step in an MCMC chain in a Bayesianly-estimated model, the actual variance of a set of &#039;random effects&#039; parameters may or may not match the variance parameter governing them exactly. In fact, given that there&#039;s exactly one way for the two numbers to match exactly and approximately infinitely many ways for them to fail to match, I would expect the latter to occur far more often.]]></description>
		<content:encoded><![CDATA[<p>The more I think about it, the more I&#8217;m with Gelman on this (see, e.g., <a href="http://www.stat.columbia.edu/~gelman/research/published/AOS259.pdf" rel="nofollow">section 6 of this paper</a> and pp. 262-265 of <a href="http://www.stat.columbia.edu/~gelman/arm/" rel="nofollow">Gelman &#038; Hill&#8217;s book</a>). The section 6 bit addresses fixed vs. random effects terminology in general (arguing that it&#8217;s more useful to talk about constant vs. varying parameters), and the book section illustrates how there are a number of mathematically equivalent ways of writing &#8216;mixed effects&#8217; models, a number of which make it pretty clear that the &#8216;random effects&#8217; bits are parameters, too.</p>
<p>The fact that the random effects are estimated differently than are the parameters governing them doesn&#8217;t make the former something other than parameters. The key difference between fixed effects and random effects here is that random effects are modeled (i.e., there are variances and covariances governing them [as well as means, namely the associated fixed effects]) whereas the fixed effects aren&#8217;t. Yet there is still uncertainty about the fixed effects, else why have standard errors and confidence intervals and all the associated statistical testing machinery?</p>
<p>Bates says (on p. 2 of lrgprt.pdf) that &#8220;random effects are unobserved random variables.&#8221; Well, the fixed effects aren&#8217;t observed either, and the fact that nobody disputes that there is uncertainty about them (again, CIs, SEs, etc&#8230;) suggests that, whether we&#8217;re modeling them or not (i.e., whether we are willing to make particular distributional assumptions about them or not), there is an element of randomness smack dab in the middle of fixed effect estimation, too.</p>
<p>Ultimately, I can&#8217;t figure out what exactly Bates and others mean by &#8216;parameter&#8217; that includes fixed effects and variances/covariances while excluding random effects.</p>
<p>This distinction, whatever it is, seems at odds with a lot of other statistical modeling, too. For example, in CFA and SEM, there are potentially huge numbers of latent variables, all of which are parameters in those models. Pretty much all of the cognitive/math psych modeling I know about has analogous structure &#8211; latent variables like the spatial location, dimension weights, and bias parameters in <a href="http://www.cogs.indiana.edu/nosofsky/pubs/1986_rmn_jep-g_attention.pdf" rel="nofollow">Generalized Context Model</a> or the means and correlations in the perceptual distributions in <a href="http://www.perceptionweb.com/abstract.cgi?id=p261101" rel="nofollow">GRT</a>. I link to those two papers specifically because they illustrate maximum likelihood estimation and not Bayesian estimation (i.e., the unobserved parameters aren&#8217;t explicitly probabilistically modeled).</p>
<p>The fact that the variance of the estimated random effects can be different from the estimated variance doesn&#8217;t do much work here either. For any given step in an MCMC chain in a Bayesianly-estimated model, the actual variance of a set of &#8216;random effects&#8217; parameters may or may not match the variance parameter governing them exactly. In fact, given that there&#8217;s exactly one way for the two numbers to match exactly and approximately infinitely many ways for them to fail to match, I would expect the latter to occur far more often.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on When is a parameter not a parameter? by Scott J</title>
		<link>http://www.nhsilbert.net/source/2013/01/when-is-a-parameter-not-a-parameter/#comment-1313</link>
		<dc:creator>Scott J</dc:creator>
		<pubDate>Mon, 21 Jan 2013 04:07:39 +0000</pubDate>
		<guid isPermaLink="false">http://www.nhsilbert.net/source/?p=1350#comment-1313</guid>
		<description><![CDATA[Actually, I think this &quot;non-parameter&quot; thing is more accurate than you might think.  I&#039;ve been digging more into these things recently. In short, unlike a Bayesian or other type analysis where there is no real distinction between the parameters of by-subject intercepts (or slopes) and other parameters, the way lme4 (and I think other mixed-effects-fitting software) works is exactly as described in your post.  The variance of the random effect is a parameter of the model, but the actual by-subject intercepts are not &quot;estimated&quot; in the same way the fixed effects are estimated.  One illustration of this is that if you do var() on the output of ranefs(), you don&#039;t get exactly the same number as the estimated variance of the random effect in the model.

Maybe the best place for you to look (and I mean that, because you will understand the math better than I do) is one of the drafts of Bates&#039; long-in-progress book on lme4.  If you go to this site:
http://lme4.r-forge.r-project.org/
And find a doc called &quot;lrgprt.pdf&quot;, you will find a relevant discussion in section 1.6 (at least, in the version at the time of this posting). Here&#039;s a paragraph of it:

&lt;blockquote cite=&quot;&quot;&gt;These values [talking about BLUPs] are often considered as some sort of “estimates” of the random effects. It can be helpful to think of them this way but it can also be misleading. As we have stated, the random effects are not, strictly speaking, parameters—they are unobserved random variables. We don’t estimate the random effects in the same sense that we estimate parameters. Instead, we consider the conditional distribution of B given the observed data, (B&#124;Y = y).
&lt;/blockquote&gt;]]></description>
		<content:encoded><![CDATA[<p>Actually, I think this &#8220;non-parameter&#8221; thing is more accurate than you might think.  I&#8217;ve been digging more into these things recently. In short, unlike a Bayesian or other type analysis where there is no real distinction between the parameters of by-subject intercepts (or slopes) and other parameters, the way lme4 (and I think other mixed-effects-fitting software) works is exactly as described in your post.  The variance of the random effect is a parameter of the model, but the actual by-subject intercepts are not &#8220;estimated&#8221; in the same way the fixed effects are estimated.  One illustration of this is that if you do var() on the output of ranefs(), you don&#8217;t get exactly the same number as the estimated variance of the random effect in the model.</p>
<p>Maybe the best place for you to look (and I mean that, because you will understand the math better than I do) is one of the drafts of Bates&#8217; long-in-progress book on lme4.  If you go to this site:<br />
<a href="http://lme4.r-forge.r-project.org/" rel="nofollow">http://lme4.r-forge.r-project.org/</a><br />
And find a doc called &#8220;lrgprt.pdf&#8221;, you will find a relevant discussion in section 1.6 (at least, in the version at the time of this posting). Here&#8217;s a paragraph of it:</p>
<blockquote cite=""><p>These values [talking about BLUPs] are often considered as some sort of “estimates” of the random effects. It can be helpful to think of them this way but it can also be misleading. As we have stated, the random effects are not, strictly speaking, parameters—they are unobserved random variables. We don’t estimate the random effects in the same sense that we estimate parameters. Instead, we consider the conditional distribution of B given the observed data, (B|Y = y).
</p></blockquote>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Induction redux by Noah Motion</title>
		<link>http://www.nhsilbert.net/source/2013/01/induction-redux/#comment-1198</link>
		<dc:creator>Noah Motion</dc:creator>
		<pubDate>Wed, 09 Jan 2013 14:38:49 +0000</pubDate>
		<guid isPermaLink="false">http://www.nhsilbert.net/source/?p=1341#comment-1198</guid>
		<description><![CDATA[I think I had it say &quot;a special case of hasty generalization&quot; at one point, but I changed it to say that they&#039;re equivalent. But, yeah, the more I think about it, the more I agree that the toupee fallacy is more narrow in scope than the general problem of (plebian) induction.]]></description>
		<content:encoded><![CDATA[<p>I think I had it say &#8220;a special case of hasty generalization&#8221; at one point, but I changed it to say that they&#8217;re equivalent. But, yeah, the more I think about it, the more I agree that the toupee fallacy is more narrow in scope than the general problem of (plebian) induction.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
