Drought sensitive maize inbred shows more oxidative damage and higher ROS scavenging enzymes, but not glyoxalases than a tolerant one at seedling stage
Bibliographic record
Abstract
This study was undertaken to unveil the oxidative stress tolerance mechanism in maize seedlings under drought.The level of oxidative stress and involvement of antioxidant and glyoxalase systems were investigated in seedlings of two maize inbreds: P134, a relatively drought tolerant, and P142, a drought susceptible inbred subjected to water deficit for 7 days and then rewatered to reveal the mechanism of oxidative stress tolerance under drought.Water content, chlorophyll (Chl), reactive oxygen species (ROS), lipid peroxidation, methylglyoxal (MG), lipoxygenase (LOX) activity, enzymatic and non-enzymatic antioxidants and glyoxalases status were investigated in the uppermost fully expanded leaves.The superoxide (O 2•-) generation rate, hydrogen peroxide (H 2 O 2 ), lipid peroxidation and MG as well as LOX activity were higher in P142 throughout the drought period .Conversely, relative water content (RWC), Chl, carotenoid (Car) and proline contents were remarkably higher in P134.However, in rewatering, recovery of Chl and Car were higher in P142.The reduced glutathione (GSH), ascorbic acid (ASA) and their redox homeostasis indicated more oxidative damage in P142.The ROS scavenging enzymes like superoxide dismutase (SOD), peroxidase (POD), ascorbate peroxidase (APX) and dehydroascorbate reductase (DHAR) activities were comparatively higher in P142 under drought, while catalase (CAT), monodehydroasacorbate reductase (MDHAR) and glutathione reductase (GR) activities were higher in P134.Though the activity of GST increased in both inbreds, activities of glyoxalase-I (Gly-I) and glyoxalse-II (Gly-II) increased only in P134.In rewatering, activities of most of the enzymes decreased in both inbreds.Taken together, the non-enzymatic antioxidant system was stronger in P134, but the higher SOD, POD, APX, GPX and DHAR activities in P142 suggesting that these enzymes might involve in cellular protection through reducing oxidative damage.
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.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".