Across-Design Uncertainty in Short Pricing Panels: Inference and Identification

Sicherheitsmeldung mit Schweregrad noch nicht bewertet. Technische Details im Tab „Originaltext“; empfohlene Schritte in der Checkliste.

Originaltext der Quelle (nicht übersetzt) – die deutsche Zusammenfassung findest du im Tab „Kurzfassung".

arXiv:2608.21334v2 Announce Type: replace Abstract: Short observational pricing panels often contain many observations but few distinct price movements. We evaluate the inferential consequences of this sparsity in a synthetic data-generating process by separating estimation error into uncertainty conditional on a realized price trajectory and variation across alternative trajectories. In baseline simulations, this across-design component accounts for 97.6% of estimation error variance for a gradient-boosted specification, causing coverage shortfalls driven by design-specific centering error that standard within-panel resampling and cluster-robust procedures fail to capture. Three main results organize the analysis. First, across-design dispersion follows the empirical relation sigma_b approx 0.182 V^(-0.271), where V = n_moves * magnitude^2, with -0.271 treated as a simulation regularity. Second, adding regions sharing a common price path improves nuisance estimation but creates no independent price trajectories; only averaging across units with independent design errors reduces across-design standard deviation at the sqrt(k) rate. Third, a Paule-Mandel variance component estimated across independently priced units increases empirical coverage under homogeneity from 0.469 to 0.931. Broadly, improving inference in passive panels requires generating independent identifying variation, such as through controlled regional randomization. Finally, an application to scanner data (Dominick's Finer Foods, Soft Drinks) confirms these findings: nominal price zones and products …

Vollständiger Originalartikel ↗

• Betroffenheit im eigenen Stack prüfen: Versionen/Komponenten abgleichen.
• Originalquelle / Hersteller-Advisory lesen: https://arxiv.org/abs/2608.21334
• Verfügbaren Patch oder Workaround einspielen und dokumentieren.