First Report of Ash Anthracnose Caused by <i>Discula fraxinea</i> in Oregon
Bibliographic record
Abstract
Anthracnose on ash trees has been observed on landscape trees in western Oregon, yet there has been no formal report of the disease or its causal fungus. Anthracnose symptoms are observed annually in May and become severe by July when defoliation starts to occur. From 1989 to now, samples have been received from Benton, Josephine, and Marion counties, suggesting that ash anthracnose has been present throughout western Oregon for some time. To identify the causal agent, a fungus was isolated from acervuli on necrotic lesions on leaves of cultivated white ash (Fraxinus americana L.) trees in Benton County in July 2003. The acervuli produced hyaline, nonseptate, ellipsoid conidia 5 to 11 × 3.5 to 6 µm in diameter. The fungus was identified as Discula fraxinea (Peck) Redlin & Stack (teleomorph Gnomoniella fraxini Redlin & Stack) (2). The sequences of the internal transcribed spacer (ITS) region (GenBank Accession No. AY455814) and large subunit (GenBank Accession No. AY455818) nrDNA agreed with those of D. fraxinea from Maryland, except for three single-base substitutions and three insertions/deletions in ITS1. Ash anthracnose has been reported from the central and eastern United States and California, the prairie provinces in Canada, and recently, from British Columbia (1). A specimen (U.S. National Fungus Collections BPI 843391) and culture (Centraal Bureau voor Schimmelcultures CBS 114053) of D. fraxinea from Oregon were deposited. References: (1) D. F. Farr et al. Fungal Databases. Systematic Botany and Mycology Laboratory. On-line publication. ARS USDA, 2003. (2) S. C. Redlin and R. W. Stack. Mycotaxon 32:175, 1988.
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.001 | 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.002 | 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".