RosettaCommons / RosettaCommons/PyRosetta.notebooks

ncAA-protein mutageneis scoring

Open
#109 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Jupyter Notebook
Stars
709
Forks
173
Avg merge
5m
Merged PRs (30d)
2

Description

When quantifying the binding energy of a ncAA-protein complex, we observe varying energies for each trial (noise spikes of -0.3 to 0.7 REUs for binding energy & 13 to 21 REUs for folding energy) at a given residue after mutagenesis which doesn’t seem correct given our system.

Our workflow is as follows: we separate a protein-cAA chain, “score” the constituents, mutate the AA to an ncAA & “re-score.” Do you know why we could be experiencing such fluctuations in REUs given the same complex/interface residues? In addition, is there a distinct difference between 2 & 3 or 10 & 20 REUs (same order of magnitude) or can the difference between these be considered negligible where the “trend” is most important given a residue with varying scores when mutated.

Image

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

The issue names no file, test, or notebook entry point. Begin by reviewing the separation, scoring, and mutation workflow described in the report and determine how repeated scores vary. A useful resolution would explain the fluctuation source and clarify whether the reported REU differences are meaningful or expected.

Written by the indexing model from the issue text.

Assessment

Tech stack
jupyter-notebook
Domain
bioinformatics
Issue type
Bug
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.