Log quality characteristics of mountain pine beetle killed lodgepole pine trees from southern interior British Columbia for board processing.
Bibliographic record
Abstract
The mountain pine beetle (MPB) (Dendroctonus ponderosae Hopkins) epidemic has ravaged lodgepole pine (Pinus contorta var. latifolia) forests throughout British Columbia (BC). The research focused on the effects of three stages of MPB trees, green, red, and grey attack from southern interior BC on the MPB-induced variables of log moisture content (MC), blue stain, and checking and how these relate to log quality from an end product perspective. The objectives were to determine if: 1) the percentage of blue stain calculated from the log end surface at diameter breast height (DBH) correlates to the percentage of blue stained boards 2) the quantity and size of checks present in a disk removed at DBH correlates to the percentage of checked boards 3) the sapwood moisture content from a cross sectional disc at DBH correlates to the percentage of MPB-induced degrades (checking, wood borers, and decay fungi). Three sections of each MPB log (bottom, middle, and top), were examined for the MPB-induced degrades blue stain, checking, and the losses due to wood borers and decay fungi. The results support the findings of previous MPB research where reduced moisture content, blue stain, and checking significantly reduce log quality. However, this study is unique since it relates these findings to the effects that they have on the board products. The percentage of blue stain from a disc cut at DBH is correlated to the percentage of blue stained boards from that tree for green, red, and grey attack. As blue stain increases in the disc cut at DBH by attack stage, the amount of blue stained boards also increases by attack stage. When the check depth is >3 cm and the check depth to width ratio in a disk cut at DBH is >4, there is a positive correlation to the percentage of checked boards for that tree. If the check depth to width ratio is less, these shallow checks are removed by the canter chipping heads during primary breakdown. As MC decreases below the fibre saturation point, there is a linear relationship between MC and MPB-
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.001 | 0.001 |
| Science and technology studies | 0.001 | 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".