Daily and seasonal spore dispersal by <i>Mycosphaerella pinodes</i> and development of mycosphaerella blight of field pea
Bibliographic record
Abstract
Daily and seasonal spore dispersal of Mycosphaerella pinodes (Berk & Bloxam) Vestergren and the relationship of spore dispersal to distance and disease severity were investigated in a pea field in western Canada during two consecutive years. Most ascospores were released in response to rain events, during the first 2327 d after the inoculum source area was infested with naturally diseased pea residue, whereas most pycnidiospores were trapped during the first 20 d. For both ascospores and pycnidiospores, the highest peaks of spore release occurred during the first 1420 d after infestation. Few spores were trapped after day 27 after infestation. Daily peaks of ascospore and pycnidiospore release occurred between 1700 and 0400 hours. Most ascospores were released 12 d after a rain event and the largest peak appeared the first day after rain. In contrast, most pycnidiospores were released on the same day as rain occurred or the following day. The release of both spore types was associated with rainfall events ≥2 mm during the first 27 d after infestation but not with rainfall events after 27 d. Ascospore density was negatively correlated with distance from the inoculum source (r ≤ 0.92) and positively related to the disease severity (r ≥ 0.92). Disease severity decreased with increasing distance from the inoculum source. The patterns of spore dispersal associated with rain events have practical applications in the disease forecasting and spraying of chemicals to control the disease.Key words: field pea, mycosphaerella blight, rainfall, spore release.
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.001 | 0.000 |
| Science and technology studies | 0.000 | 0.000 |
| Scholarly communication | 0.001 | 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".