Why `clonotype_imbalance` is deprecated?
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 265
- Forks
- 50
- Avg merge
- 9d 9h
- Merged PRs (30d)
- 4
Description
Hi @grst,
I was wondering why clonotype_imbalance is deprecated because of clonotype_modularity?
clonotype_imbalance seems to me still a very useful tool if one wants to compare how the clonal compositions differ between two populations of interest, whereas clonotype_modularity reveals how similar cells belonging to the same clone_id are in terms of their gene expression profiles.
Am I missing something?
Thanks very much,
Yuan
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
Start with the clonotype_imbalance and clonotype_modularity entry points and their documentation; the issue names no files or tests. Determine whether the deprecation rationale is documented, and consider the issue resolved when the distinction and deprecation decision are clearly explained.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- bioinformatics
- Issue type
- Documentation
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100