Comments (3)
In my view time complexity isn't the right way to think about drawing the diagram. It can be done in seconds. What takes time is understanding the data and systems the diagram represents, discussing alternative diagrams with stakeholders, and adapting to the limitations of the available or obtainable data (e.g. some variables cannot be observed). This part takes time.
Given the above, multiple causal diagrams can exist, and may be equally valid if the underlying system is not fully understood.
If the causal diagram is incorrect, any statistical analysis based on it might be invalidated.
However, not drawing a causal diagram doesn't help you. Your statistical analyses may be just as invalid, but without the diagram it's difficult to know either way: Your assumptions are not explicit! This is why I would advocate for always drawing causal diagrams when exploring causal questions with observational data (and in other experiment designs).
We have written an article about this here: https://causalwizard.app/inference/article/causal-diagram
from dowhy.
This issue is stale because it has been open for 14 days with no activity.
from dowhy.
This issue was closed because it has been inactive for 7 days since being marked as stale.
from dowhy.
Related Issues (20)
- Support polars data frames HOT 2
- What is the purpose of providing observation data in gcm.conventional_samples()?
- Python 3.12 support HOT 9
- Clarify the differences among refute methods HOT 11
- Feature relevance/Influence HOT 26
- Graphviz installation : --include-path not recognized anymore HOT 4
- Does this package support non-English languages? HOT 3
- Question about Dummy Outcome Refuter HOT 2
- Inconsistency in the placebo_treatment_refuter when using estimate_effect of IV HOT 1
- numpy.dual is dropped but it still occurs in dowhy HOT 2
- NetworkXError: graph should be directed acyclic HOT 4
- Refutation & Overlap Error ("data_subset_refuter", "add_unobserved_common_cause", assess_support_and_overlap_overrule) HOT 2
- No Backdoor Path Available
- Clarification on how to use gcm properly for confounders adjustment HOT 5
- Can you provide code demo for each function? HOT 2
- How is propensity score matching implemented? HOT 2
- Interpreting mean while using logistic regression to estimate causal effect. HOT 1
- model.estimate_effect and model.refute_astimate throws 'A column-vector y was passed ...' error
- RuntimeWarning: divide by zero encountered in divide when using evaluate_causal_model HOT 3
- Auto assign_causal_mechanisms is taking so much time in gcm HOT 11
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from dowhy.