Contribution of rubredoxin:oxygen oxidoreductases and hybrid cluster proteins of <i> <scp>D</scp> esulfovibrio vulgaris </i> <scp>H</scp> ildenborough to survival under oxygen and nitrite stress
Bibliographic record
Abstract
A genomic island (GEI) of the sulfate-reducing bacterium Desulfovibrio vulgaris Hildenborough, found to be able to migrate between two tRNA-Met loci of the genome, contains genes for rubredoxin:oxygen oxidoreductase-1 (roo1) and hybrid cluster protein-1 (hcp1) with additional copies for these genes (roo2 and hcp2) being found elsewhere on the chromosome. A suite of mutants was created in which roo2 and/or hcp2 and/or the GEI were either present or missing. The GEI and roo2 increased survival under microaerobic conditions and allowed growth in closer proximity to the air-water interface of soft agar tubes, two properties which appeared to be closely linked. When Hcp2(+) GEI(+) or Hcp2(-) GEI(+) cells, harbouring cytochrome c nitrite reductase (NrfHA) and growing on lactate and sulfate, were amended with 10 mM nitrite at mid-log phase (8-10 mM sulfide), all nitrite was reduced within 30 h with a rate of 3.0 mmol (g biomass)(-1) h(-1) after which sulfate reduction resumed. However, Hcp2(+) GEI(-) or Hcp2(-) GEI(-) cells were unable to use lactate, causing sulfide to be used as electron donor for nitrite reduction at a sixfold lower rate. Complementation studies indicated that hcp1, not roo1, enhanced the rate of nitrite reduction under these conditions. Hcp2 enhanced the rate of nitrite reduction when, in addition to lactate, hydrogen was also present as an electron donor. These results indicate a critical role of Hcps in alleviating nitrite stress in D. vulgaris Hildenborough by maintaining the integrity of electron transport chains from lactate or H(2) to NrfHA through removal of reactive nitrogen species. It thus appears that the GEI contributes considerably to the fitness of the organism, allowing improved growth in microaerobic environments found in sulfide-oxygen gradients and in environments, containing both sulfide and nitrite, through the action of Roo1 and Hcp1 respectively.
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.000 |
| Insufficient payload (model declined to judge) | 0.000 | 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".