Genera specific distribution of DEAD-box RNA helicases in cyanobacteria
Bibliographic record
Abstract
Although RNA helicases are essentially ubiquitous and perform roles in all stages of RNA metabolism, phylogenetic analysis of the DEAD (Asp-Glu-Ala-Asp)-box RNA helicase family in a single phylum has not been performed. Here, we performed a phylogenetic analysis on DEAD-box helicases from all currently available cyanobacterial genomes, comprising a total of 362 helicase protein sequences from 280 strains. DEAD-box helicases belonging to three distinct clades were observed. Two clades, the CsdA (cold shock DEAD-box A)-like and RhlE (RNA helicase E)-like helicases, cluster with the homologous proteins from Escherichia coli . The third clade, the CrhR (cyanobacterial RNA helicase Redox)-like helicases, is unique to cyanobacteria and characterized by a conserved sequence motif in the C-terminal extension. Restricted distribution is observed across cyanobacterial diversity with respect to both helicase type and strain. CrhR-like and CsdA-like helicases essentially never occur together, while RhlE always occurs with either a CrhR-like or CsdA-like helicase. CrhR-like and RhlE-like proteins occurred in filamentous cyanobacteria of the orders Nostocales , Oscillatoriales and Synechococcales . Similarly, CsdA- and RhlE-like proteins are restricted to unicellular cyanobacteria of the genera Cyanobium and Synechococcus . In addition, the unexpected occurrence of RhlE in two Synechococcus strains suggests recent acquisition and evolutionary divergence. This study, therefore, raises physiological and evolutionary questions as to why DEAD-box RNA helicases encoded in cyanobacterial lineages display restricted distributions, suggesting niches that require either CrhR or CsdA RNA helicase activity but not both. Extensive conservation of gene synteny surrounding the previously described rimO–crhR operon is also observed, indicating a role in the maintenance of photosynthesis. The analysis provides insights into the evolution, origin and dissemination of sequences within a single gene family to yield divergent functional roles.
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.000 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.002 | 0.001 |
| Science and technology studies | 0.000 | 0.000 |
| Scholarly communication | 0.001 | 0.000 |
| Open science | 0.000 | 0.001 |
| Research integrity | 0.000 | 0.000 |
| 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".