VEuPathDB / VEuPathDB/study-wrangler
Check binWidth calculations on single-value columns and fix if needed
Nobody has claimed this yet.
- Dominant language
- R
- Stars
- 0
- Forks
- 0
- Avg merge
- 2d 1h
- Merged PRs (30d)
- 1
Description
I think if a column has all the same value (e.g. 1) the binWidth might be wrong and subsetting/distribution endpoint falls over in the EDA and notebooks. Need to test (UD), see what we used to do, and fix.
keywords: bin, findBinWidth
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
Search the repository for findBinWidth and binWidth, then trace how a single-valued column reaches the subsetting and distribution endpoints. Reproduce the failure in the EDA or notebooks, inspect the previous behavior, and add a regression test. Done means single-value columns no longer cause those endpoints to fail.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- r
- Domain
- data
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100