
<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Alina Matei, M. Giovanna Ranalli, &#8211; SIS-Graspa</title>
	<atom:link href="https://graspa.org/tag/alina-matei-m-giovanna-ranalli/feed/" rel="self" type="application/rss+xml" />
	<link>https://graspa.org</link>
	<description>The official site of the Graspa SIS group</description>
	<lastBuildDate>Wed, 16 Jan 2019 12:11:29 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	

<image>
	<url>https://graspa.org/wp-content/uploads/2025/09/cropped-07-Graspa-verticale-ridotto-32x32.png</url>
	<title>Alina Matei, M. Giovanna Ranalli, &#8211; SIS-Graspa</title>
	<link>https://graspa.org</link>
	<width>32</width>
	<height>32</height>
</image> 
	<item>
		<title>Dealing with nonresponse in survey sampling: a latent modeling approach</title>
		<link>https://graspa.org/my-page-96/</link>
		
		<dc:creator><![CDATA[SteamAdm]]></dc:creator>
		<pubDate>Wed, 16 Jan 2019 12:11:29 +0000</pubDate>
				<category><![CDATA[2012]]></category>
		<category><![CDATA[Alina Matei, M. Giovanna Ranalli,]]></category>
		<guid isPermaLink="false">https://graspa.org/my-page-96/</guid>

					<description><![CDATA[Nonresponse is present in almost all surveys and can severely bias estimates. It is usually distinguished between unit and item nonresponse: in the former, we completely fail to have information from a unit selected in the sample, while in the latter, we observe only part of the information on the selected unit. Unit nonresponse is&#8230;&#160;<a href="https://graspa.org/my-page-96/" class="" rel="bookmark">Read More &#187;<span class="screen-reader-text">Dealing with nonresponse in survey sampling: a latent modeling approach</span></a>]]></description>
										<content:encoded><![CDATA[<p>  Nonresponse is present in almost all surveys and can severely bias estimates.<br />
It is usually distinguished between unit and item nonresponse: in the former,<br />
we completely fail to have information from a unit selected in the sample,<br />
while in the latter, we observe only part of the information on the selected<br />
unit. Unit nonresponse is usually dealt with by reweighting: each unit selected<br />
in the sample has associated a sampling weight and an unknown response<br />
probability; the initial sampling weight is multiplied by the inverse of<br />
estimated response probability. Item nonresponse is usually dealt with by<br />
imputation. By noting that for a particular survey variable, we just have<br />
observed and unobserved values, in this work we exploit the connection between<br />
unit and item nonresponse. In particular, we assume that the factors that drive<br />
unit response are the same as those that drive item response on selected<br />
variables of interest. Response probabilities are then estimated by using a<br />
logistic regression with a latent covariate that measures such will to respond<br />
and that can explain part of the unknown behavior of a unit to participate in<br />
the survey. The latent covariate is estimated using latent trait models. Such<br />
approach is particularly relevant for sensitive items and, therefore, can<br />
handle non-ignorable nonresponse. Auxiliary information known for both<br />
respondents and nonrespondents can be included either in the latent variable<br />
model or in the logistic model. The approach can be also used when auxiliary<br />
information is not available, and we focus here on this case. The theoretical<br />
properties of the proposed estimators are sketched and simulations studies are<br />
conducted to illustrate their finite size sample performance.</p>
]]></content:encoded>
					
		
		
			</item>
	</channel>
</rss>
