The no_information_rate function of the .632+ bootstrap consumes too much memory
Open
Nobody has claimed this yet.
Enhancement
New Feature
- Dominant language
- Python
- Stars
- 5.2k
- Forks
- 916
- Avg merge
- 17h 31m
- Merged PRs (30d)
- 4
Description
Currently, the no_information_rate function in bootstrap_point632.py consumes too much memory if the dataset is moderately large. Needs to be improved.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start in mlxtend/evaluate/bootstrap_point632.py and inspect the no_information_rate function's memory use on moderately large datasets. Determine which operation causes the excessive allocation and compare its behavior before and after the change. Done means the .632+ bootstrap calculation uses substantially less memory without changing its results.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- machine-learning, performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100