Names of fungal species with the same epithet applied to different morphs: how to treat them
Bibliographic record
Abstract
The abolition of the separate naming of different morphs of the same fungal species in 2011 will inevitably result in many name changes in some genera. The working practices commended here are intended to minimize one category of these changes, that which can arise as a consequence of an author using the epithet of an asexual morph when describing the sexual morph of the same species. We consider that name proposed for the sexual morph in such cases should be treated as a formal error for a new combination and not as a new species, and so be corrected. This is interpreted as applying even where the author indicated that a new species was being described and designated a type. We argue that those formalities were a result of the requirements of the rules then in force, as the author recognized that a morph of a named species was being described, and not a new hitherto unnamed species was being reported - but was barred from making a new combination so used the same epithet for the new morph name instead. Where a type with the sexual morph was designated for the sexual morph, under this interpretation that no longer has nomenclatural status, the type being that of the basionym. The material for the sexual morph indicated as a type, would be available for designation as an epitype, though a modern sequenced sample with both sexual and asexual morphs would be more informative as an epitype in many cases. A proposal to regularize the working practice commended here, and also the converse situation where the sexual morph typified name is the earlier, will be made to the 2017 Shenzhen Congress.
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.027 | 0.109 |
| Meta-epidemiology (narrow) | 0.002 | 0.002 |
| Meta-epidemiology (broad) | 0.002 | 0.002 |
| Bibliometrics | 0.007 | 0.005 |
| Science and technology studies | 0.008 | 0.017 |
| Scholarly communication | 0.012 | 0.025 |
| Open science | 0.005 | 0.006 |
| Research integrity | 0.006 | 0.013 |
| Insufficient payload (model declined to judge) | 0.009 | 0.023 |
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".