Status of the Humboldt Penguin in Peru, 1999-2000
Bibliographic record
Abstract
The status of the Humboldt Penguin (Spheniscus humboldti) was investigated in Peru after the 1997-98 El Niño event, the strongest of the last century. Penguin numbers along the southern and central coast of Peru (97% of the total) did not differ significantly between 1999 and 2000; the average number was 4,425 individuals. In 1999, the proportion of juveniles (one-year-old birds) was only 0.2% compared with 7% in 2000, probably as a result of the 1997-98 El Niño. Penguins were found from La Foca Island (512’S) to Punta Coles (1742’S). However, the majority (78%) were clustered in five localities, Punta San Juan (36%), San Juanito Islet (11%), Hornillos Island (10%), Pachacamac Island (12%) and Tres Puertas (9%). The size and distribution of penguin colonies have changed over the last 15 years. Penguins have abandoned sites at Punta Corio, Sombrerillo and Morro Sama, and have decreased significantly in numbers in Punta San Fernando and Punta La Chira, where human disturbance has increased, mainly due to local fisheries activities. Penguins have increased at Punta San Juan, San Juanito Islet and San Gallan Island, all of which are partially protected. Half of the penguins were located in guano bird reserves, primarily at Punta San Juan. Guano bird reserves provide some protection against terrestrial predators and human disturbance; however, periodical guano extraction decreases their breeding success. Most penguin sites were found in inaccessible and marginal areas, which were vulnerable to occasional and unpredictable flooding from ocean swells. The methodology recommended by the Population and Habitat Viability Assessment workshop for a consistent census of penguins in Peru and Chile during the molting period was validated at the Punta San Juan Reserve. Continued monitoring of Humboldt Penguin numbers is recommended in order to more fully understand patterns of fluctuation and to be able to detect changes of conservation concern as early as possible. Collaborative efforts between local authorities and conservation biologists are needed to monitor and protect this vulnerable species.
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.001 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.001 | 0.001 |
| Science and technology studies | 0.001 | 0.000 |
| Scholarly communication | 0.001 | 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".