# DoWhy

**DoWhy is a Python Library for Causal Inference from Microsoft, developed by** [Amit Sharma](https://www.microsoft.com/en-us/research/people/amshar/), [Emre Kiciman](https://www.microsoft.com/en-us/research/people/emrek/). Its name is inspired by Judea Pearl’s do-calculus for causal inference.

![](/files/-MFIPHnSVE6_K-7agXmC)

## **About**

DoWhy is a Python library for causal inference that supports explicit modeling and testing of causal assumptions. DoWhy is based on a unified language for causal inference, combining causal graphical models and potential outcomes frameworks. DoWhy stresses on Interpretability of the output. At any point in the analysis, you can inspect the untested assumptions.

DoWhy uses the Bayesian graphical Model framework where one can specify all the assumptions about the data generating process.

DoWhy is a very effective and helpful library for **implementing Causal Inference**. The library implements causality by **first making the underlying assumptions explicit**, for example, by explicitly representing identified estimands. **Secondly by making sensitivity analysis and other robustness checks** on these explicit assumptions, for example, by introducing a confounder or by replacing the intervention with placebo. The goal here is to enable people to focus their efforts on identifying assumptions for causal inference, rather than on details of estimation.

**DoWhy examples**: [Github](https://github.com/microsoft/dowhy/tree/master/docs/source/example_notebooks/)

## **Resource:**

1. <https://github.com/Microsoft/dowhy>&#x20;
2. <https://microsoft.github.io/dowhy/>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://akm5630.gitbook.io/understanding-causal-inference/tools-and-libraries/dowhy.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.