py-why / py-why/causal-learn

Different results with Tetrad and causal-learn implementations.

Open
#175 9 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
1.7k
Forks
274
PR merge metrics
No merged PRs in 30d

Description

Dear developers,

I have been trying to use causal learn models with fMRI data. I used both the Tetrad implementation (using pyTetrad and JPype) and the causal-learn implementations.

What surprises me is that I'm getting quite different results from these implementations. Using the PC algorithms in a 100 variables graph (4950 potential undirected edges) the algorithms' results differ in 155 edges.

Also, the GES algorithm in causal-learn is orders of magnitude (hours vs seconds) slower than the Tetrad implementation.

Kind regards

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue names no files, tests, dataset, or algorithm settings. Start by reproducing the PC and GES comparisons using the same inputs and options in causal-learn and the Tetrad implementation via pyTetrad and JPype. Done means identifying and documenting the source of the differing edges and performance, or narrowing it to a specific implementation discrepancy.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
machine-learning
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.