Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

how does it compare to causalinference library #7

Closed
kirk86 opened this issue Aug 22, 2018 · 2 comments
Closed

how does it compare to causalinference library #7

kirk86 opened this issue Aug 22, 2018 · 2 comments

Comments

@kirk86
Copy link

kirk86 commented Aug 22, 2018

Hi, hank you for releasing this work and all the effort put in to it.
I was curious to understand what are the primary differences compared to this library? Are there any pros and cons?

Best,
k.

@amit-sharma
Copy link
Member

Thanks for your interest. The library laurencium/causalinferece also implements causal inference methods, but it focuses only on one step in causal analysis: estimation. In building DoWhy, therefore, we decided to have support for all the steps required for a causal analysis:

  • model (make assumptions),
  • identify (find what to estimate given the assumptions),
  • estimate
  • refute (sensitivity and robustness checks).

I think the biggest difference is the last step: DoWhy provides refute methods to test underlying causal assumptions. This is often missed in causal inference libraries that only deal with estimation, as the user is expected to know beforehand what is the right causal target estimand, and which covariates to include. DoWhy also allows the user to specify your asssumptions explicitly in code, so that they can be reasoned about and tested if possible.

Finally, in terms of estimation methods, DoWhy supports both backdoor-based and instrumental variable methods, while laurencium/causalinference library supports only backdoor-based methods.

@kirk86 kirk86 changed the title how does it comparet to causalinference library how does it compare to causalinference library Aug 24, 2018
@kirk86
Copy link
Author

kirk86 commented Aug 24, 2018

@amit-sharma Sounds awesome! Thank you for taking time to answer my question. I'll definitely delve more into the inner workings in the next couple of days. I'm closing this issue in hope to keep things clean since your answer is really thorough.

@kirk86 kirk86 closed this as completed Aug 24, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants