More time to fly: with a warming climate the Western honey bee (<i>Apis mellifera</i>, Linnaeus) now has more temperature-eligible flight hours than 40 years ago
Bibliographic record
Abstract
There have been official NOAA and EPA reports of measurable changes in temperature across the United States over the last several decades with average temperatures increasing in most areas and decreasing in a few others. In order to fly, honey bees need optimal temperatures ranging from 13 °C (55 °F) to 38 °C (100 °F), sunlight, low wind, and no rain. This study looks at changes in temperature-eligible flight times of honey bees across the US and Canada. Four decades of weather data from 60 locations in the US and Canada for the period 1980 through 2019 were analyzed. We discovered that honey bee flight hours are increasing almost everywhere, but most dramatically in the northern regions of Canada and Alaska, and also in a few locations in the US south of the border with Canada. Warming temperatures (ignoring all other factors), may lead to more flight time for honey bees; may affect plant bloom times and species distributions; and may change the exposure of honey bee colonies to pests, parasites, and pathogens. Therefore, beekeepers must be prepared to modify management practices to accommodate possible plant–pollinator mismatches and timings for seasonal and pest management. This study highlights that a warming climate will increase temperature-eligible flight hours for honey bees. Further research is needed to consider how other climate change factors, in combination with temperature, will affect actual honey bee flight opportunities and behavior, as well as, overall colony management.
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.001 |
| Science and technology studies | 0.000 | 0.000 |
| Scholarly communication | 0.001 | 0.000 |
| Open science | 0.000 | 0.000 |
| 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".