Pest categorisation of Maconellicoccus hirsutus
Bibliographic record
Abstract
The EFSA Panel on Plant Health performed a pest categorisation of Maconellicoccus hirsutus (Hemiptera: Pseudococcidae), the pink hibiscus mealybug, for the EU. M. hirsutus is native to Southern Asia and has established in many countries in tropical and subtropical regions throughout the world. Within the EU, the pest has been reported from Cyprus and Greece (Rhodes). M. hirsutus is not listed in Annex II of Commission Implementing Regulation (EU) 2019/2072. It is highly polyphagous, feeding on plants assigned to 229 genera in 78 plant families, and shows some preference for hosts in the families Malvaceae, Fabaceae and Moraceae. Economically important crops in the EU such as cotton (Gossypium spp.), citrus (Citrus spp.), ornamentals (Hibiscus spp.), grapes (Vitis vinifera), soybean (Glycinae max), avocado (Persea americana) and mulberry trees (Morus alba) may be significantly affected by M. hirsutus. The lower and upper developmental temperature threshold of M. hirsutus on Hibiscus rosa-sinensis are 14.5 and 35.0°C, respectively, with optimal female development estimated to be at 29.0°C. There are about 10 generations a year in the subtropics but as many as 15 may occur under optimal conditions. Plants for planting, fruits, vegetables and cut flowers provide potential pathways for entry into the EU. Climatic conditions in EU member states around the Mediterranean Sea and host plant availability in those areas are conducive for establishment. The introduction of M. hirsutus is expected to have an economic impact in the EU through damage to various ornamental plants, as already observed in Cyprus and Greece, and reduction in yield and quality of many significant crops. Phytosanitary measures are available to reduce the likelihood of entry and further spread. Some uncertainties include the area of establishment, whether it could become a greenhouse pest, impact, and the influence of natural enemies. M. hirsutus meets the criteria that are within the remit of EFSA to assess for it to be regarded as a potential Union quarantine pest.
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.001 | 0.001 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.002 | 0.000 |
| Science and technology studies | 0.000 | 0.000 |
| Scholarly communication | 0.000 | 0.000 |
| Open science | 0.000 | 0.000 |
| Research integrity | 0.000 | 0.000 |
| Insufficient payload (model declined to judge) | 0.003 | 0.001 |
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".