warning/option for integer perturbation covariate keys
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Python
- Stars
- 159
- Forks
- 27
- PR merge metrics
- No merged PRs in 30d
Description
Description of feature
now integer perturbation covariate keys in .obs are treated as concentrations and cannot be keys for .uns. we should add a warning and write that clearly in documentation or add an explicit option to have integer keys
Contributor guide
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
No file or test is named. Start by locating the code that interprets integer perturbation covariate keys in .obs and writes or reads keys in .uns; then determine whether the expected result is a warning, documentation clarification, or explicit option, with tests covering the chosen 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