Population dynamics of foxes during restricted-area culling in Britain: Advancing understanding through state-space modelling of culling records
Bibliographic record
Abstract
Lethal control is widely employed to suppress the numbers of target wildlife species within restricted management areas. The success of such measures is expected to vary with local circumstances affecting rates of removal and replacement. There is a need both to evaluate success in individual cases and to understand variability and its causes. In Britain, red fox (Vulpes vulpes) populations are culled within the confines of shooting estates to benefit game and wildlife prey species. We developed a Bayesian state-space model for within-year fox population dynamics within such restricted areas and fitted it to data on culling effort and success obtained from gamekeepers on 22 shooting estates of 2 to 36 km2. We used informative priors for key population processes-immigration, cub recruitment and non-culling mortality-that could not be quantified in the field. Using simulated datasets we showed that the model reliably estimated fox density and demographic parameters, and we showed that conclusions drawn from real data were robust to alternative model assumptions. All estates achieved suppression of the fox population, with pre-breeding fox density on average 47% (range 20%-90%) of estimated carrying capacity. As expected, the number of foxes killed was a poor indicator of effectiveness. Estimated rates of immigration were variable among estates, but in most cases indicated rapid replacement of culled foxes so that intensive culling efforts were required to maintain low fox densities. Due to this short-term impact, control effort focussed on the spring and summer period may be essential to achieve management goals for prey species. During the critical March-July breeding period, mean fox densities on all estates were suppressed below carrying capacity, and some maintained consistently low fox densities throughout this period. A similar model will be useful in other situations to quantify the effectiveness of lethal control on restricted areas.
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.005 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.001 | 0.001 |
| Bibliometrics | 0.000 | 0.000 |
| Science and technology studies | 0.000 | 0.001 |
| Scholarly communication | 0.001 | 0.001 |
| Open science | 0.001 | 0.001 |
| Research integrity | 0.001 | 0.001 |
| Insufficient payload (model declined to judge) | 0.001 | 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".