Conversion API to other causal libraries' graph about pywhy-graphs HOT 7 CLOSED

I would also be happy to extend the API to ananke!

from pywhy-graphs.

I think based on today's discussion, this seems pretty high value. So I'ma start chipping away at this. Happy to review PR related to ananke.

Re all these packages btw, we'll only add them as soft dependencies for unit-testing purposes. This will go into the poetry group test in the pyproject.toml file

from pywhy-graphs.

Will get started on this later this week, on the ananke side I need to remove a hard dependency on graphviz and make sure that didn't break anything.

from pywhy-graphs.

Is there a rough sketch of how the api should look? Presumably we want to expose a set of functions that all look and behave roughly the same. One idea that comes to mind is the pandas export functionality, where df.to_<format>() is the pattern.

from pywhy-graphs.

Is there a rough sketch of how the api should look? Presumably we want to expose a set of functions that all look and behave roughly the same. One idea that comes to mind is the pandas export functionality, where df.to_<format>() is the pattern.

Currently, I have a functional API, which is just graph_to_<format> and <format>_to_graph. We can add more convenience once we have the working functions.

Will get started on this later this week, on the ananke side I need to remove a hard dependency on graphviz and make sure that didn't break anything.

You can keep it if you want, and just make ananke an optional dependency.

from pywhy-graphs.

Everything is done that is doable except Ananke now.

Note: some of the other packages which only supports DAGs, I did not handle or implement. I think those work fine w/ nx.DiGraph for now, so community can PR that if they want it.

from pywhy-graphs.

Example about tetrad conversion and other library conversion in examples script.

from pywhy-graphs.