AutoCATE: End-to-End, Automated Treatment Effect Estimation
— AutoML for causal effect estimation —
AutoCATE is an open-source Python package for automated, end-to-end estimation of Conditional Average Treatment Effects (CATE). Designed to simplify the complexities of causal inference, AutoCATE enables practitioners and researchers to quickly build robust ML pipelines for causal effect/heterogeneous treatment effect estimation in only four lines of code.
✨ Key Features
✔️ Automated ML Pipelines: Automatically builds pipelines and handles preprocessing, ML algorithm selection, hyperparameter optimization, and ensembling.
✔️ Custom Evaluation Protocols: Incorporates different risk measures (e.g., DR-risk, T-risk) and risk metrics (e.g., AUQC) tailored for causal inference.
✔️ Low-Code API: Effortlessly predict treatment effects with minimal setup.
📦 Installation
Install directly from PyPI:
pip install autocate
Requires Python ≥ 3.8.
🛠 Quick start
from autocate import AutoCATE
# Initialize AutoCATE
autocate = AutoCATE()
# Fit model on training data
autocate.fit(X_train, t_train, yf_train)
# Predict CATE for new data
cate_pred = autocate.predict(X_test)
⚙️ How It Works
AutoCATE operates in three stages:
1️⃣ Evaluation: Optimize the ML pipelines underlying the risk measure(s) (e.g., R-risk) for robust pipeline selection.
2️⃣ Estimation: Optimizing ML pipelines for CATE estimation, combining preprocessors, metalearners, and baselearners.
3️⃣ Ensembling: Combines the top-performing pipelines to create a final model.
❓ Why Choose AutoCATE?
Estimating causal effects requires dealing with unique challenges 🚨
❌ Evaluation is a challenge due to lack of ground truth CATE and covariate shift caused by confounding variables.
❌ Causal metalearners combine different ML algorithms and are complex to tune.
❌ No clear, established practices for preprocessing and ensembling.
AutoCATE eliminates these barriers by automating the entire process, making state-of-the-art CATE estimation accessible for everyone.
📄 License
This project is licensed under the MIT License.
Metadata
Release files for AutoCATE 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| autocate-0.1.0.tar.gz | 22.4 kB | Without provenance | Details for autocate-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| autocate-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for autocate-0.1.0-py3-none-any.whl |
Total release size: 46.2 kB
Release files / autocate-0.1.0.tar.gz
| Download URL | autocate-0.1.0.tar.gz |
|---|---|
| Size | 22.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f288b5d4443691dda6942a43ca8e603a88b2568847c04e7bd88883dcd12f7e75
|
|
BLAKE2b-256 checksum How to use checksums |
712093ce0ad3501b0a682cc4a2845db1121f81afa9665f5682835e6ef568a4ed
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.0.1 CPython/3.10.8
|
Release files / autocate-0.1.0-py3-none-any.whl
| Download URL | autocate-0.1.0-py3-none-any.whl |
|---|---|
| Size | 23.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
58c348976a03c3a06edebed9715af47c03ac58f69f3c040eb0c45a13efbcdb62
|
|
BLAKE2b-256 checksum How to use checksums |
2b80b9eea54921084d8d219666ebe27ffc9eeecf79825f7042cc4d1fd83549d0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.0.1 CPython/3.10.8
|
Security for AutoCATE 0.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.