Stripe rust of winter wheat in western Canada mitigated with spring- but not fall-applied foliar fungicide
Bibliographic record
Abstract
Winter wheat production in Canada is approximately 5% of all the wheat seeded in Canada; however, it has important economic and agronomic benefits for growers. Stripe rust of wheat, caused by Puccinia striiformis f. sp. tritici Eriks. occurs across western Canada in many years; as a result, it is prudent to evaluate strategies to control stripe rust in winter wheat. The objective of this project was to evaluate the effects of fall and spring fungicide application (metconazole and pyraclostrobin) on stripe rust, as well as leaf spot severity, and impact on yield and quality of winter wheat (Triticum aestivum L.). The effect of fungicide application in the fall, in the spring, or both, on four winter wheat cultivars varying in resistance to these diseases was evaluated at 11 site-years in Alberta and Saskatchewan for four growing seasons from 2013 to 2017. Stripe rust severity on the susceptible cultivars, ‘AC Bellatrix’ and ‘CDC Osprey’, and leaf spot severity on these cultivars and ‘Radiant’, was reduced by single spring or dual (fall and spring) applications, but not by fall application alone when disease severity was high. Single spring and dual fungicide applications to ‘AC Bellatrix’ maintained yield potential by 16.9–229.5% compared to the unsprayed treatment. Grain quality was also maintained by the same treatments at some site-years. During the study, virulence of the natural Pst population on ‘Radiant’ with the Yr10 resistance gene was differentially expressed among sites and therefore yield response to fungicide varied. The stripe rust resistant cultivar ‘Moats’ did not benefit from fungicide application at any timing. Single fall fungicide application had no effect on disease severity of any of the cultivars at any site-years, although it had minor effects on yield or grain quality of ‘AC Bellatrix’ at a few site-years. Multiple fungicide applications, in fall and again in spring, did not offer additional benefits to a single spring application.
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.001 | 0.000 |
| Scholarly communication | 0.001 | 0.000 |
| Open science | 0.001 | 0.000 |
| Research integrity | 0.000 | 0.001 |
| 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".