Residual-Based Causal Discovery via Pretrained In-Context Quantile Regression
Residual-based causal discovery assumes that each variable is generated from its parents and an independent noise source.
ProofPaper ↗
Key points
- It estimates this noise and tests its independence from candidate causes.
- For identifiable functions such as additive-noise models (ANMs) and the broader class of location-scale noise models (LSNMs), this principle identifies the causal direction, as only the causal model admits this independence.
- In contrast, the RESIT-framework allows for nonparametric estimation of residuals to iteratively identify sink nodes, but was proposed for ANMs. To close this gap, we propose Loscar, an extension of RESIT to LSNMs that estimates the conditional mean and scale via quantile regression, enabling pretrained tabular foundation models as plug-in estimators.
- Across bivariate and multivariate causal-discovery benchmarks, in-context quantile regression substantially outperforms FGLS with flexible function classes, particularly for multivariate causes.
Sources (1)
- [1]Residual-Based Causal Discovery via Pretrained In-Context Quantile RegressionarXiv (AI, ML, NLP, CV, robotics, multi-agent) · Oct 21, 10:19 AM
Residual-based causal discovery assumes that each variable is generated from its parents and an independent noise source.
It estimates this noise and tests its independence from candidate causes.
Extractive summary: sentences quoted from the sources.
Before this
- Oct 21, 2026Multimodal Embodied Agents: A Unified Capability-centric Perspective from Computer-Use to Robot-Use
- Oct 21, 2026Evolving with Open Worlds: Towards Recursive Self-Improvement for Future Forecasting
- Oct 20, 2026Human-Robot Interaction via Meta-Learning Based Mode Recognition and Adaptive Control
- Oct 20, 2026Quantum-JEPA: Quantum Born Priors for Latent-Action JEPA World Models
- Oct 20, 2026LaLa-World: Scaling Latent World Models with Natural Language Actions
- Oct 20, 2026Runtime Control for AI Agents: Closing the Evaluation--Execution Gap in Operational Workflows