DoWhy 0.9 includes some exciting new extensions and features, including better sensitivity analyses, new identification algorithms, and more. I'm particularly excited to see so many new contributors joining in on this release!
@PatrickBloebaum and @kailashbuki improve the GCM module with a new API for unit change attribution, support for modeling FCMs with auto-gluon, and more!
Egor Kraev added support for EconML's multi-treatment estimators; and @amt_shrma added support for estimating direct effects (previously had been total effect)
Plus, many expensive refutations now run in parallel, making them much faster (Thanks Andreas Stöffelbauer and Amey Verhade!) and as of DoWhy 0.9.1, DoWhy has cleaned up dependencies and supports python 3.10
If you want to see your favorite algorithm or feature in the next version of DoWhy, we have a contributor's guide (thanks to Michael Marien!) github.com/py-why/dowhy/b…
Open for discussions at our Discord and in GitHub issues
And a strong agree with @amt_shrma's comment here that an LLM capturing domain knowledge can be a useful tool for bootstrapping, brainstorming, or supporting the creation of causal graphs
For example, we are not limited to asking about whether A causes B. We can ask directly about potential confounders, to help data scientists or others interrogate their own thinking, while remaining vigilant against overreliance on the LLM alone.