Mitigation of pollen limitation in the lowbush blueberry agroecosystem: effect of augmenting natural pollinators
Bibliographic record
Abstract
Growers of small fruit crops often supplement the natural pollinator community by introducing pollinators into commercial orchards and fields, but there are relatively few studies that test the extent to which such interventions increase fruit yield. To test whether plants are limited by pollen availability, inflorescences in 78 commercial lowbush blueberry fields during three years were hand‐pollinated either with supplemental outcross pollen, or marked and left as controls (open‐pollination). Maximum fruit set with supplemental pollination was in the range 50–65%, whereas with open‐pollination, it was slightly, but significantly lower, in the range of 47–57%, suggesting that pollen limitation can affect fruit set. In a two‐year experiment, we augmented native pollinators with introduced honey bees, bumble bees, and leaf cutter bees and all combinations in 48 fields. Stigmatic pollen loads were influenced by the total numbers of managed bees in a field in 2010 but not 2011. The presence of leaf cutter bees had a small but positive effect on seed set in 2010, and honey bees had a small but negative influence on seed set in 2011. There was a strong correlation between fruit set reproductive output of supplementally pollinated and open‐pollinated plants, suggesting that plant health or plant resources influence reproductive success. Temperature variation among regional groupings of fields was minimal and is unlikely to have accounted for differences among fields in fruit set. We propose several reasons why, despite pollen‐limitation of fruit and seed set of blueberry plants, augmentation of the pollinator community of lowbush blueberry did not significantly increase reproduction. These include pollinator‐mediated transfer of self‐pollen followed by subsequent fruit abortion due to inbreeding depression and resource limitation for fruit maturation. Management practices that focus on increasing outcross pollen receipt, or plant resources for fruit set may have greater overall benefit than pollinator augmentation alone.
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.000 | 0.000 |
| Science and technology studies | 0.000 | 0.000 |
| Scholarly communication | 0.000 | 0.000 |
| Open science | 0.001 | 0.000 |
| Research integrity | 0.000 | 0.000 |
| 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".