Systematics of Andean gladiator frogs of the Hypsiboas pulchellus species group (Anura, Hylidae)
Bibliographic record
Abstract
Köhler, J., Koscinski, D., Padial, J. M., Chaparro, J. C., Handford, P., Lougheed, S. C. & De la Riva, I. (2010). Systematics of Andean gladiator frogs of the Hypsiboas pulchellus species group (Anura, Hylidae). —Zoologica Scripta, 39, 572–590. We revisit the taxonomic status of Andean species and populations of frogs of the Hypsiboas pulchellus group using multiple lines of evidence potentially indicative of evolutionary lineage divergence in anurans: differences in qualitative morphological or bioacoustic character states, no overlap in quantitative characters of advertisement calls, and monophyly of gene genealogies. We found qualitative and quantitative morphological characters to be extremely variable among species and populations of the group and thus of very limited use in assessing lineage divergence. In contrast, phylogenetic analyses based on 16S rRNA and cytochrome b sequences resolved highly supported clades that are in concordance with bioacoustic differences. The results support the specific distinctness of most nominal species recognized in the group, including the Bolivian Hypsiboas balzani and Hypsiboas callipleura, two species that were considered to be synonymous, and revealed the presence of an undescribed species from southern Peru, which is here described as Hypsiboas gladiator sp. n. In contrast, Hypsiboas andinus and Hypsiboas riojanus were mutually paraphyletic, and showed no differences in morphology and acoustic characters. Consequently, we regard the former as a junior synonym of the latter. However, we discovered that populations of H. riojanus from central Bolivia exhibit some degree of genetic differentiation and advertisement call differences with respect to Argentine populations, but sampling of these Bolivian populations is too sparse to draw taxonomic conclusions. Our phylogenetic results support the hypothesis that ancestral lineages of the Andean H. pulchellus group experienced successive splitting events along a latitudinal gradient from north to south.
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.002 | 0.001 |
| Science and technology studies | 0.001 | 0.001 |
| Scholarly communication | 0.000 | 0.000 |
| Open science | 0.000 | 0.001 |
| 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".