Deletion of a terminal residue disrupts oligomerization of a transmembrane α-helixThis paper is one of a selection of papers published in this special issue entitled “Canadian Society of Biochemistry, Molecular & Cellular Biology 52nd Annual Meeting — Protein Folding: Principles and Diseases” and has undergone the Journal's usual peer review process.
Bibliographic record
Abstract
In studies of the structural biology of membrane proteins, the success of strategies based on the "divide and conquer" approach, where peptides are used to model the individual transmembrane (TM) alpha-helices of membrane proteins, depends on the correct identification of the membrane-embedded TM alpha-helix amino acid sequence within the full-length protein. In the present work, we examine the effects of excluding or including TM boundary residues on the intrinsic properties of a Lys-tagged TM2 alpha-helix of myelin proteolipid protein (PLP), of parent sequence KKKK-66AFQYVIYGTASFFFLYGALLLAEG89-KKKK along with analogs containing an additional wild type Phe-90, Phe-90 and Tyr-91, and of a hydrophobic mutant Leu-90. Using protein gel electrophoresis, circular dichroism, and fluorescence resonance energy transfer in the membrane-mimetic detergent sodium dodecylsulfate (SDS), we demonstrate that the removal of a single amino acid from the C-terminus of this TM segment is enough to change its intrinsic properties, with TM2 66-89 displaying only a monomeric form, but with dimers arising for the other 3 peptides. A novel use of trifluoroethanol (TFE) as a maximal helix-supporting solvent demonstrated that peptides containing residues at positions 90 and (or) 90-91 displayed significantly increased helical content vs. the TM2 parent peptide. The findings suggest that deletion of critical C-terminal residue(s) tends to reposition the helix terminus toward the membrane-aqueous interface. Our overall results emphasize the potential influence of boundary residues on TM properties when using peptides as models for TM alpha-helices, and may implicate a role for these residues in membrane protein folding and assembly.
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.000 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.000 | 0.000 |
| Science and technology studies | 0.000 | 0.000 |
| Scholarly communication | 0.000 | 0.000 |
| Open science | 0.000 | 0.000 |
| Research integrity | 0.000 | 0.001 |
| Insufficient payload (model declined to judge) | 0.001 | 0.001 |
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".