Tomicus piniperda (Coleoptera: Scolytidae) Initial Flight and Shoot
Bibliographic record
Abstract
The exotic pine shoot beetle, Tomicus piniperda (L.) (Coleoptera: Scolytidae), established in the north central and northeastern United States (U.S.) and adjacent regions in Canada, is regulated by a federal quarantine that restricts movement of pine material during specific times of the year based on the beetle's life history. Although climatic variation occurs across T. piniperda's range, a single set of dates is used for timing the movement of pine logs. We monitored T. piniperda spring flight, fall shoot departure, and air and internal tree temperatures at three sites along a 300-km north-south gradient in Michigan and Indiana. We also estimated dates for initial spring flight (12oC threshold) and fall shoot departure (0oC threshold) across an 850-km gradient using historical temperature records (1901 to 1999). Average daily temperatures in fall 1997 (8 October to 12 December) and spring 1998 (20 February to 21 April) were 1.8 to 2.4oC colder, respectively, at the northern field site than at the southern field site. Fall shoot departure began at approximately the same time (day 289 to 290) at all three field sites, but complete shoot departure was extended by 3 wk at the southern site (day 336) compared with the northern site (day 317). T. piniperda adults were first captured in funnel traps on calendar day 86 at the northern site and on day 59 at the central and southern field sites. Peak flight occurred at approximately the same time (day 86) at all three sites. Within-shoot temperatures were very similar to air temperatures in the fall and aboveground inside-bark temperatures were similar to air temperatures in the spring. Average predicted dates based on historical temperature records varied by 31 d for initial shoot departure and 84 d for initial spring flight between northern Michigan and southern Indiana. Because considerable variation can occur in T. piniperda behavior across a broad geographic range, dates specified in the U.S. Federal quarantine should be adjusted according to local temperatures.
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.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".