Kernel Density Estimation - Statistics Graduate Level
- If the original bandwidth is , which bandwidth and density relationship make the kernel density estimator exactly equivariant under this transformation? Answer: Use , giving Whenever you see a question about kernel density estimation (KDE) under linear transformations, anchor your thinking to two requirements simultaneously: how the bandwidth must scale, and how the density value must transform to preserve proper probability mass. For a linear transformation with , the KDE achieves exact equivariance — meaning it behaves like the true density under the transformation — when the bandwidth scales as . Here, , so . This makes intuitive sense: stretching the data by a factor of 3 spreads observations apart, so the smoothing window must widen proportionally to maintain the same relative smoothing. For the density relationship, recall that if , then the change-of-variables formula requires . The factor ensures the density integrates to 1 after stretching. Combining both requirements confirms C is correct. A uses the wrong bandwidth ( instead of ) but accidentally gets the density formula right — it's a half-correct answer that fails equivariance because the bandwidth doesn't account for the scale change. B has the correct bandwidth but inverts the density scaling factor, writing instead of . This would produce a density that doesn't integrate to 1 — a fundamental violation. D shrinks the bandwidth () when it should expand, and omits the necessary normalizing factor entirely. A reliable memory aid: for , bandwidth multiplies by and the density divides by . These two adjustments always move in opposite directions.
- For observations , consider the kernel density estimator where and What is ? Answer: Kernel density estimation questions test your ability to mechanically apply the KDE formula, which requires careful bookkeeping of which kernels actually "activate" at your target point. At with and , the estimator is: The Epanechnikov kernel is zero when . Check each observation: - : , so — kernel is zero. - : , so . - : , so — kernel is zero. Only contributes, giving: That confirms A. Choice B, , is the trap of forgetting to multiply by the prefactor — you evaluated the kernel but skipped the normalization. Choice D, , doubles instead of multiplying by . Choice C, , uses as the prefactor instead of , confusing with . Always compute the standardized argument first to identify which observations fall within the kernel's support before evaluating anything else.
- Which approximation to the expectation of the kernel density estimator at is correct? Answer: reflecting downward smoothing bias at a local maximum. Whenever you see a question about kernel density estimation bias, your first instinct should be to recall the standard bias expansion. For a symmetric kernel at an interior point, the bias formula is: This result comes from a Taylor expansion of inside the convolution integral; the symmetry of the kernel kills the odd-order terms, leaving the leading bias proportional to . Plugging in the given values — , , and — you get: So , which is answer B. The negative sign makes intuitive sense: a point where is a local maximum, and smoothing pulls estimates downward toward neighboring lower values — a classic downward bias. A gets the sign wrong. Upward bias would require (a local minimum), not a local maximum. C omits the crucial factor and uses directly — a common algebraic error that forgets the coefficient in the Taylor expansion. D claims the bias is linear in , which contradicts the theory; the leading bias is always of order for symmetric kernels. The key memory anchor: bias . Never drop the , and always check the sign of to determine the direction of smoothing bias.
- Which statement about the resulting estimator is necessarily correct? Answer: It integrates to one but can be negative at some points, so it need not be a genuine density. When you encounter a question about higher-order or signed kernels, the key is carefully separating two properties that a genuine probability density must satisfy: nonnegativity everywhere, and integrating to one. These two properties are logically independent, and signed kernels break them asymmetrically. The condition is preserved under the estimator's construction. Since , integrating over all gives regardless of the sample. So the estimator always integrates to one. However, where , the estimator can take negative values for certain , violating nonnegativity. This makes C correct: the estimator integrates to one but is not guaranteed to be a valid density. Answer A is wrong because the estimator is not necessarily nonnegative — negative kernel lobes directly produce negative estimates. It also incorrectly claims the integral deviates from one, which contradicts the linearity argument above. Answer B is wrong for the same integral reason: the integral is always exactly one, not "less than one," because each kernel shift integrates to one regardless of where observations fall. Answer D is wrong because no sample size, however large, eliminates the possibility of negative values at specific points — that is a structural feature of the signed kernel, not a finite-sample artifact. Your takeaway: for signed kernels, the normalization condition travels through linearity cleanly, but nonnegativity does not. Always ask "which density property does linearity preserve?" — the answer is integration to one, never pointwise positivity.
- What is the probability limit of the estimator evaluated exactly at the left endpoint, ? Answer: It converges to because only one half of the symmetric kernel mass overlaps the support. Kernel density estimation at boundary points is a classic source of asymptotic bias, and recognizing why requires you to think carefully about how mass integrates over a truncated region. The kernel density estimator is Its pointwise probability limit equals its limiting expected value (by the law of large numbers under standard bandwidth conditions). At any interior point, because the full kernel integrates to 1 over the support. But at , the situation changes: the kernel is centered at the boundary, and since the data live only on , only the right half of the symmetric kernel actually overlaps the support. Formally, Because on , the limit is , confirming answer B. Choice A is wrong because contributions from nearby positive observations do not vanish — they simply get cut in half. Choice C applies interior consistency results where boundary effects are absent; consistency fails at the boundary precisely because the estimator carries systematic bias toward zero. Choice D invents a renormalization that a standard kernel estimator never performs — that would describe a boundary-corrected estimator. As a study tip: whenever a boundary is present, immediately check which fraction of kernel mass lies inside the support. Symmetric kernels lose exactly half their mass at a hard boundary, so the limiting bias factor is always .
- How does the kernel density estimate at change after adding the observation? Answer: It becomes because only the normalization changes at . Whenever you see a question about kernel density estimation, anchor yourself to the formula: Every observation contributes a scaled kernel bump, but only observations within bandwidth of contribute nonzero values when the kernel has compact support . Here's the key insight: the new observation is farther than from , so . Its numerator contribution is exactly zero. However, the denominator still grows — the sample size increases from to . The updated estimate becomes: So the estimate at is diluted by the factor , making D correct. A is tempting but incomplete — yes, the new observation contributes zero kernel mass, but you cannot ignore how the normalization constant changes. B is wrong because it assumes the new observation contributes a full bump, which requires , impossible when the observation falls outside the kernel's support. C inverts the logic entirely — a larger sample size dilutes the existing contributions rather than inflating them. The study tip: always track both the numerator (kernel evaluations) and the denominator () separately. In KDE, adding a remote observation affects only the denominator, quietly shrinking every existing estimate.
- Which bandwidth order and resulting optimized error order follow from balancing these terms? Answer: and reflecting the two-dimensional variance term. Whenever you see a kernel density estimation question involving AMISE balancing, your job is to treat bias and variance as two terms in an equation and find the bandwidth that minimizes their sum — then substitute back to find the optimal error rate. Here, the AMISE has two terms: a bias-squared term and a variance term . To find the optimal , set them equal in order of magnitude: Multiply both sides by : Substituting back, the bias term gives , and the variance term gives . Both terms are , confirming . This is answer D. A is the classic univariate result, where the variance term is . In 2D with a product kernel, the variance inflates to because the effective local bin volume scales as , not . Plugging in univariate logic here gives the wrong exponent. B arrives at the right AMISE rate but the wrong bandwidth. It appears to account for the squared bandwidth in the variance but mis-solves the balance equation — setting does not yield . C incorrectly supposes that adding a second coordinate changes the bias order, but the bias remains per dimension with a squared-kernel product, keeping the squared bias at . Study tip: In dimensions, the product-kernel variance term is , so the optimal bandwidth scales as and AMISE as . For : and . Memorizing this general formula saves time on any dimensionality question.
- Why is the ordinary in-sample criterion unsuitable for bandwidth selection in this setting? Answer: It tends to favor extremely small bandwidths because each observation contributes a large kernel value to its own fitted density. When choosing a bandwidth for kernel density estimation, you need a criterion that genuinely measures how well your estimated density generalizes — not just how well it memorizes the data. The in-sample log-likelihood is fatally flawed because each observation participates in its own estimated density value . With a Gaussian kernel, the contribution of observation to its own density estimate is which grows without bound as . As the bandwidth shrinks, each point's self-contribution dominates and inflates the log-likelihood artificially. The optimizer therefore drives toward zero, producing degenerate "spike" estimates — one sharp Gaussian centered at each data point — rather than a smooth, meaningful density. This confirms that A is correct. B is wrong because it describes the leave-one-out criterion, not the in-sample one. In leave-one-out cross-validation, is deliberately excluded from , which is exactly why that approach avoids the collapse-to-zero problem. C is wrong because the criterion absolutely depends on . While each Gaussian kernel integrates to one (a property ensuring is a valid density), the pointwise evaluation at each changes with — the two concepts should not be conflated. D is wrong because the in-sample criterion is not an unbiased estimator of predictive log-likelihood; it is systematically upward-biased due to the self-evaluation problem described above. As a study tip: whenever a selection criterion evaluates a model on the same data used to fit it, ask whether any observation is "cheating" by inflating its own fit — this self-evaluation trap appears frequently in density estimation and model selection questions.
- For a twice-differentiable density and a symmetric second-order kernel, suppose the leading asymptotic mean integrated squared error has the form where and are positive constants. Restrict attention to bandwidths of the form Which choice yields the fastest decay of the displayed AMISE while also satisfying the usual consistency conditions? Answer: because it balances the integrated squared-bias and variance terms. Kernel density estimation questions hinge on the bias-variance tradeoff baked into the AMISE. When you see a form like , your instinct should be: minimize over , then check what power of that optimal bandwidth takes. Taking the derivative with respect to and setting it to zero gives which yields So the optimal bandwidth has the form with Plugging back in, both terms contribute equally and AMISE decays at rate — the fastest possible for this setup. Consistency also requires and , both satisfied since means and . That confirms B is correct. Choice A () fixes as a constant, so and the bias never vanishes — the estimator is inconsistent. Choice C () makes shrink faster than optimal, so the variance term dominates and AMISE decays only at rate , which is slower than . It's consistent but suboptimal. Choice D () shrinks too aggressively: , so and the variance explodes — another inconsistent choice. Study tip: Always verify two things for KDE bandwidth sequences: the AMISE-minimizing rate (set derivative to zero) and the consistency conditions (, ). Forgetting the second step is the most common trap on these questions.
- Which comparison is correct to leading asymptotic order? Answer: has the same leading bias and a smaller leading variance than . Kernel density estimation questions like this one test whether you understand which kernel properties govern bias versus variance in the asymptotic MSE decomposition. For a kernel estimator with bandwidth , the leading bias at an interior point depends on — the second moment of the kernel — through the expression . The leading variance depends on through . These two quantities are entirely separate: bias is controlled by the second moment, variance by the roughness functional . The passage tells you that and share the same second moment but differ in roughness, with . Since both kernels are symmetric, integrate to one, and have identical second moments, their leading bias terms are identical. However, because , produces a strictly smaller leading variance. This confirms A as correct. Choice B is wrong because it claims has a smaller bias — but bias depends only on the second moment, which is equal for both kernels. Choice C compounds this error by also claiming a larger bias for , which contradicts the identical second moments. Choice D gets the variance comparison exactly backwards: smaller means smaller variance, so 's advantage is lower variance, not higher. A useful rule to memorize: bias tracks the second moment; variance tracks . These are independent kernel properties, so a question changing one while fixing the other affects only one component of MSE.