MétaCan
Menu
Back to cohort

Diamondback Moth Ecology and Management: Problems, Progress, and Prospects

2012· review· en· W2151148027 on OpenAlex

Why this work is in the frame

A frame that forgets how it found something cannot be audited. These are the routes that admitted this work.

affAt least one author lists a Canadian institution in the pinned OpenAlex snapshot.

Bibliographic record

VenueAnnual Review of Entomology · 2012
Typereview
Languageen
FieldAgricultural and Biological Sciences
TopicInsect-Plant Interactions and Control
Canadian institutionsUniversity of Alberta
Fundersnot available
KeywordsBiologyDiamondback mothEcologyLepidoptera genitaliaPlutella

Abstract

fetched live from OpenAlex

Agricultural intensification and greater production of Brassica vegetable and oilseed crops over the past two decades have increased the pest status of the diamondback moth (DBM), Plutella xylostella L., and it is now estimated to cost the world economy US$4-5 billion annually. Our understanding of some fundamental aspects of DBM biology and ecology, particularly host plant relationships, tritrophic interactions, and migration, has improved considerably but knowledge of other aspects, e.g., its global distribution and relative abundance, remains surprisingly limited. Biological control still focuses almost exclusively on a few species of hymenopteran parasitoids. Although these can be remarkably effective, insecticides continue to form the basis of management; their inappropriate use disrupts parasitoids and has resulted in field resistance to all available products. Improved ecological understanding and the availability of a series of highly effective selective insecticides throughout the 1990s provided the basis for sustainable and economically viable integrated pest management (IPM) approaches. However, repeated reversion to scheduled insecticide applications has resulted in resistance to these and more recently introduced compounds and the breakdown of IPM programs. Proven technologies for the sustainable management of DBM currently exist, but overcoming the barriers to their sustained adoption remains an enormous challenge.

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.

Full frame distilled prediction

Teacher imitation

Not calibrated prevalence, not ground truth. Human validation pending. Learned from the 10,348 direct Codex labels and 10,348 direct Gemma labels. Candidate is the union of thresholded teacher heads; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels or direct frontier model labels.

metaresearch head score (Codex)0.000
metaresearch head score (Gemma)0.000
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Not applicable · Consensus signal: none
GenreCandidate signal: Review · Consensus signal: Review
Teacher disagreement score0.979
Threshold uncertainty score0.478

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0000.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0010.000
Bibliometrics0.0000.000
Science and technology studies0.0000.000
Scholarly communication0.0000.000
Open science0.0000.000
Research integrity0.0000.000
Insufficient payload (model declined to judge)0.0000.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.

Opus teacher head0.021
GPT teacher head0.285
Teacher spread0.264 · how far apart the two teachers sit on this one work
Validation statusscore_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from it