Move differential expression analysis to separate package
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 345
- Forks
- 66
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 13
Description
Description of feature
After factoring out the differential expression visualizations into deres, I've been thinking if it would also make sense to make a separate package for the differential expression testing altogether.
It's useful in many contexts (e.g. differential spatial analysis) as we've seen during the hackathon and I would like to have that available to the scverse ecosystem without the hefty dependency tree pertpy brings with it.
The new package (e.g. demodels) could then become a dependency of pertpy and the corresponding class definitions could be re-rexported in the pertpy API such that there are no user-facing changes.
LMK what you think @Zethson.
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 by reviewing the existing differential expression testing classes in pertpy and the separate deres package mentioned in the issue, then trace pertpy's dependency tree and public API exports. Done means the testing functionality lives in a separate package, pertpy depends on it, and the corresponding classes remain available through pertpy without user-facing changes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- data
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100