griffithlab / griffithlab/pVACtools

Add support for screening of end modifications to long peptides to accommodate manufacture/solubility issues

Open
#880 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

grant
Dominant language
Python
Stars
188
Forks
81
Avg merge
9d 17h
Merged PRs (30d)
6

Description

Conceptually similar in some ways to what happens in pVACvector. In working with peptide manufacturers, there is sometimes a case where the manufacturer wishes to add a few (e.g. 1-3) amino acids to the N- or C-terminus of the proposed long peptide.

It might be desirable to have a tool that would help facilitate the process of screening these altered peptides to see if any predicted strong binding peptides arise that include the altered (non-self and non-tumor) peptides.

Example of what input might look like:

Proposed-long-peptide       N-terminal-additions       C-terminal-additions 
RKNEQFEQEAVAVDSNLRVREKK     RKN                        KK

When pVACbind is run for each given peptide length selected we want to predict binding for those peptides that contain at least one altered amino acid at the end (RKN or KK in this case).

Contributor guide

No contributing guide indexed for this repository

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

Start by comparing the proposed workflow with pVACvector and the existing pVACbind inputs and peptide-length handling. Define how N-terminal and C-terminal additions are represented, then ensure predictions include only peptides containing at least one altered terminal amino acid. The example input provides the expected three-column shape and screening goal.

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
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.