Backend
Multiply Robust Causal Mediation Analysis with Continuous Treatments
arXiv stat.ML0 views
arXiv:2105.09254v5 Announce Type: replace-cross Abstract: In many applications, researchers are interested in the direct and indirect causal effects of a treatment or exposure on an outcome of interest. Mediation analysis offers a rigorous framework for identifying and estimating these causal effects. For binary treatments, efficient estimators for the direct and indirect effects are presented by Tchetgen Tchetgen and Shpitser (2012) based on the influence function of the parameter of interest. These estimators possess desirable properties such as multiple-robustness and asymptotic normality while allowing for slower than root-n rates of convergence for the nuisance parameters. However, in settings involving continuous treatments, these influence function-based estimators are not readily applicable without making strong parametric assumptions. In this work, utilizing a kernel smoothing approach, we propose an estimator suitable for settings with continuous treatments inspired by the influence function-based estimation strategy. Our proposed approach employs cross-fitting, relaxing the smoothness requirements on the nuisance functions and allowing them to be estimated at slower rates than the target parameter. Additionally, similar to influence function-based estimators, our proposed estimator is multiply robust and asymptotically normal, allowing for inference in settings where parametric assumptions may not be justified.
Source:https://arxiv.org/abs/2105.09254PreviousFormalizing the Intrinsic Dimension of Objective Landscapes by a Generalized Notion of Co-dimensionNextAlgorithmic Insurance
Related posts
The build check that keeps my anonymous site anonymous
0dev.to

How to pick AWS storage (without reading every doc)
0dev.to
Day 12: Auto-Scaling AI Inference — Using Horizontal Pod Autoscalers for Spiky API Traffic
0dev.to
I pinned every image by digest. That froze 97 vulnerabilities in place.
0dev.to
Case study (hypothetical): the provider disabled our webhook endpoint after a weekend of 500s, and nobody noticed for 9 days
0dev.to
How to fix 'too many missed start times' in Kubernetes CronJobs (and why your job silently stopped running)
0dev.to