Modeling of the bacterial luciferase‐flavin mononucleotide complex combining flexible docking with structure‐activity data
Bibliographic record
Abstract
Although the crystal structure of Vibrio harveyi luciferase has been elucidated, the binding sites for the flavin mononucleotide and fatty aldehyde substrates are still unknown. The determined location of the phosphate-binding site close to Arg 107 on the alpha subunit of luciferase is supported here by point mutagenesis. This information, together with previous structure-activity data for the length of the linker connecting the phosphate group to the isoalloxazine ring represent important characteristics of the luciferase-bound conformation of the flavin mononucleotide. A model of the luciferase-flavin complex is developed here using flexible docking supplemented by these structural constraints. The location of the phosphate moiety was used as the anchor in a flexible docking procedure performed by conformation search by using the Monte Carlo minimization approach. The resulting databases of energy-ranked feasible conformations of the luciferase complexes with flavin mononucleotide, omega-phosphopentylflavin, omega-phosphobutylflavin, and omega-phosphopropylflavin were filtered according to the structure-activity profile of these analogs. A unique model was sought not only on energetic criteria but also on the geometric requirement that the isoalloxazine ring of the active flavin analogs must assume a common orientation in the luciferase-binding site, an orientation that is also inaccessible to the inactive flavin analog. The resulting model of the bacterial luciferase-flavin mononucleotide complex is consistent with the experimental data available in the literature. Specifically, the isoalloxazine ring of the flavin mononucleotide interacts with the Ala 74-Ala 75 cis-peptide bond as well as with the Cys 106 side chain in the alpha subunit of luciferase. The model of the binary complex reveals a distinct cavity suitable for aldehyde binding adjacent to the isoalloxazine ring and flanked by other key residues (His 44 and Trp 250) implicated in the active site.
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.001 | 0.000 |
| Meta-epidemiology (broad) | 0.001 | 0.001 |
| Bibliometrics | 0.000 | 0.001 |
| 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.002 | 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".