scverse / scverse/scirpy

Public and private epitopes

Open
#27 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

new-feature
Dominant language
Python
Stars
265
Forks
50
Avg merge
9d 9h
Merged PRs (30d)
4

Description

In GitLab by @szabogtamas on Feb 19, 2020, 14:04

In publications, people commonly refer to CDR3s shared by most individuals in a group (patients) as a public chain. We should also consider if we want to offer a function to detect public CDRs and if this should just return a list or try to visualize something.
Another consideration is whether or not we should creat a metric that tells us how public is a CDR3 (maybe the diversity of the grouping variable among the cells having tat specific CDR3).

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue names no files, tests, or entry points. Begin by clarifying whether the goal is public-CDR3 detection, visualization, a publicness metric, or all three, and define the grouping variable and expected outputs from the cited publication context. Done should include an agreed scope and measurable behavior before implementation starts.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
bioinformatics
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.