scikit-learn / scikit-learn/scikit-learn

making mutual_info_regression more verbose

Open
#26,775 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

New Feature
Dominant language
Python
Stars
67.3k
Forks
27.4k
Avg merge
1d 15h
Merged PRs (30d)
58

Description

Describe the workflow you want to enable

Hi,

Thanks for coding up mutual_info_regression, I use it for novel space science research and it's super helpful for me.

I'm currently using it to analyse quite large amounts of data, and understandably this can be quite slow. I'm wondering if it would be possible to implement an optional flag in mutual_info_regression to make the code verbose while it's running. For example, printing out something to the terminal when it is 10%, 20%, 30% (etc) done.

Just an idea - hopefully I have raised this in the correct way!

Thanks,
Alexandra Fogg

Describe your proposed solution

Implementation of an optional flag in mutual_info_regression to make the function verbose, where it prints out statements at certain stages of the process, e.g. 10% done or saying that a certain stage is completed, etc.

Describe alternatives you've considered, if relevant

No response

Additional context

No response

Contributor guide

Open the contributing guide

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

Start by locating the mutual_info_regression entry point and inspect how its current computation progresses. Check nearby tests and existing API conventions for optional runtime reporting. Done means an optional verbosity setting reports useful progress during large runs without changing default behavior, with tests covering the new behavior.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
machine-learning
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.