pywhy-graphs
pywhy-graphs copied to clipboard
py-why
[Experimental] Causal graphs that are networkx-compliant for the py-why ecosystem.
https://github.com/py-why/pywhy-graphs/blob/20661f1eadf64bf359a88afc09a8e5fed29123c5/pywhy_graphs/viz/draw.py#L118-L121
Towards #65 Changes proposed in this pull request: - Creates a new directed/undirected graph class `DiUnGraph` - Refactors CPDAG to be a subclass of DiUnGraph - Create a new graph...
**Is your feature request related to a problem? Please describe.** At the moment there is a graph class `pywhy_graphs.CPDAG` that handles graphs with directed and undirected edges. However, such graphs...
**Is your feature request related to a problem? Please describe.** Whenever a PAG is constructed, it is not necessary a valid PAG in the sense of the definition. I.e. it...
What happens if a user has `graph_type="dag"` instead here? Will this function detect that there are `o->` edges and prevent that? Clearly the imported file does not represent a DAG...
**Is your feature request related to a problem? Please describe.** They should be under `pywhy_graphs.generators.*`, where each function corresponds to some graph that is generated. **Describe the solution you'd like**...
**Is your feature request related to a problem? Please describe.** In causal estimation tasks, one is interested in typically using covariate adjustment to estimate the total causal effects given a...
**Is your feature request related to a problem? Please describe.** In causal estimation tasks, one is interested in typically using front door adjustment to estimate the total causal effects given...
**Is your feature request related to a problem? Please describe.** Given some representation of a set of DAGs, we want to reduce this to one DAG. For example, given a...
A lot of the `mixedEdgeGraph` internals was essentially copied over from networkx. I think with the assumption that "maybe" we could've kept similar internal data structures like `_adj`, `_nodes`, etc....