In silico based re-engineering of a computationally designed biosensor with altered signalling mode and improved dynamic range
Bibliographic record
Abstract
A current challenge in the rational design of biomolecular sensors is the ability to custom design binding affinities and detection mode in silico. To this end, we re-engineered a previously reported computationally-designed fluorescent maltooligosaccharide (MOS)-detecting biosensor to both alter its ligand-binding affinity and to analyse the underlying sensing mechanism. The dynamic range of the biosensor was expanded through the computer aided introduction of a series of amino acid substitutions in the starting protein scaffold (MalX from Streptococcus pneumoniae), which generated a biosensor set with binding affinities spanning over five orders of magnitude. The impact of the introduced substitutions on the underlying mode of signal generation was assessed in silico using our previously reported Computational Identification of Non-disruptive Conjugation sites (CINC) pipeline. CINC utilizes molecular dynamics simulations and an in-house developed algorithm to examine and exploit the structural dynamics of a protein at amino acid-level resolution. Using CINC, we demonstrate that re-engineering of the MOS-detecting biosensor set resulted in sensors with two distinct output modes which differed based on local conformational changes at the fluorescently modified reporter position. These output modes were classified as "ligand-sensing"-type biosensors (readout based on the tool sensing a unique conformation in the ligand-bound state), and "apo-sensing"-type biosensors (readout based on the tool sensing a unique conformation in the apo state). Together, these results demonstrate that structural dynamics at the individual amino acid residue level can be used as an engineer-able feature to rationally alter the fluorescence reporting properties of a biosensing device. Moving forward, the CINC workflow can also be adapted for the rational design of protein dynamic properties maximizing its utility as an in silico design platform for custom biomolecular tools.
Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.
How this classification was reachedexpand
Full frame machine prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.
Distilled classifier scores by category (both heads)
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.000 | 0.001 |
| Meta-epidemiology (narrow) | 0.001 | 0.000 |
| Meta-epidemiology (broad) | 0.001 | 0.000 |
| Bibliometrics | 0.000 | 0.000 |
| Science and technology studies | 0.000 | 0.000 |
| Scholarly communication | 0.001 | 0.000 |
| Open science | 0.001 | 0.000 |
| Research integrity | 0.001 | 0.001 |
| Insufficient payload (model declined to judge) | 0.001 | 0.000 |
Machine scores (provisional)
The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.
Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from itClassification
machine, unvalidatedMachine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.
How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".