griffithlab / griffithlab/pVACtools
Should anchor position be a criteria in the aggregate reprot for class II predictions?
Open
Nobody has claimed this yet.
grant
- Dominant language
- Python
- Stars
- 188
- Forks
- 81
- Avg merge
- 9d 17h
- Merged PRs (30d)
- 6
Description
The default [1, 2, n-1, n] positions might not be appropriate for class II and no allele-specific anchor positions are available for class II alleles. Are the default positions also applicable to long class I peptides (12mers and above)?
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
The issue names no files, tests, or entry points. Start by locating the aggregate report logic and the handling of class II predictions, then compare how anchor positions are selected for class I and class II peptides, including long class I peptides; done requires an agreed criterion and corresponding validation.
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