py-why / pywhy-stats Goto Github PK

          We should have an example demonstrating how to leverage different kernels. We can ideally show how different kernels are useful too on a small simulated data.

Originally posted by @adam2392 in #15 (comment)

Implement https://papers.nips.cc/paper/2009/hash/9246444d94f081e3549803b928260f56-Abstract.html
or
https://jmlr.org/papers/v13/gretton12a.html

Is your feature request related to a problem? Please describe.
Similar to numpy, scipy and scikit-learn and many other performant libraries, we should implement an ASV benchmarking suite that will then allow us to gauge how to improve the runtime and memory performance of the CI test suite. This will then map to significant improvements downstream in dowhy, dodiscover, etc.

Describe the solution you'd like
Add asv benchmarks. See scikit-learn repo for some boilerplate.

Additional context
We need to figure out where to host the resulting plots and add a CI pipeline to handle this. Not sure exactly on details related to this yet tho...

Migrate over basic documentation and poetry setup from dodiscover

Systematically migrate independence test, documentation and unit tests one at a time.

Is your feature request related to a problem? Please describe.
Hey I just wanted to let you know the links for the documentation are broken in the readme. Also the "installation page" link

Describe the solution you'd like
The documentation if it is done, or some kind of flag like WIP if it is undone or it doesn't exist

As brought up in #19, the power_divergence should just take the stance that categorical features can be str

Checklist

• I have verified that the issue exists against the main branch.
• I have read the relevant section in the contribution guide on reporting bugs.
• I have checked the issues list for similar or identical bug reports.
• I have checked the pull requests list for existing proposed fixes.
• I have checked the CHANGELOG and the commit log to find out if the bug was already fixed in the main branch.
• I have included in the "Description" section below a traceback from any exceptions related to this bug.
• I have included in the "Related issues or possible duplicates" section beloew all related issues and possible duplicate issues (If there are none, check this box anyway).
• I have included in the "Environment" section below the name of the operating system and Python version that I was using when I discovered this bug.
• I have included in the "Environment" section below the output of pip freeze.
• I have included in the "Steps to reproduce" section below a minimally reproducible example.

Description

Related issues or possible duplicates

• None

Environment

OS:

Python version:

Steps to reproduce

See: larsoner/circleci-artifacts-redirector-action#40

TODO:

• dodiscover
• pywhy-graphs

Checklist

• I have verified that the issue exists against the main branch.
• I have read the relevant section in the contribution guide on reporting bugs.
• I have checked the issues list for similar or identical bug reports.
• I have checked the pull requests list for existing proposed fixes.
• I have checked the CHANGELOG and the commit log to find out if the bug was already fixed in the main branch.
• I have included in the "Description" section below a traceback from any exceptions related to this bug.
• I have included in the "Related issues or possible duplicates" section beloew all related issues and possible duplicate issues (If there are none, check this box anyway).
• I have included in the "Environment" section below the name of the operating system and Python version that I was using when I discovered this bug.
• I have included in the "Environment" section below the output of pip freeze.
• I have included in the "Steps to reproduce" section below a minimally reproducible example.

Description

Related issues or possible duplicates

• None

Environment

OS:

Python version:

Steps to reproduce