MétaCan
Menu
Back to cohort
Record W4312068629 · doi:10.1080/14942119.2022.2142367

Planning methods and decision support systems in vehicle routing problems for timber transportation: a review

2022· review· en· W4312068629 on OpenAlex

Why this work is in the frame

A frame that forgets how it found something cannot be audited. These are the routes that admitted this work.

affAt least one author lists a Canadian institution in the pinned OpenAlex snapshot.
fundA Canadian funder is recorded on the work.

Bibliographic record

VenueInternational Journal of Forest Engineering · 2022
Typereview
Languageen
FieldEngineering
TopicVehicle Routing Optimization Methods
Canadian institutionsUniversité LavalUniversité du Québec à Trois-Rivières
FundersNatural Sciences and Engineering Research Council of Canada
KeywordsVehicle routing problemSoftware deploymentRouting (electronic design automation)Context (archaeology)Transport engineeringTransportation planningDecision support systemOperations researchComputer scienceEngineering

Abstract

fetched live from OpenAlex

In the forest industry, transportation accounts for a significant part of the operational costs. Reducing transportation costs through advanced planning and improved efficiency has motivated considerable research efforts. A substantial part of the research has been devoted to planning methodology and decision support systems development to solve large complex vehicle routing problems in forest timber or roundwood transportation. This paper reviews the scientific contributions to timber transportation vehicle routing planning methodologies and decision support systems used in case studies found in the literature. The challenges of their deployment are discussed and future research opportunities are presented. Vehicle routing problems in timber transportation differ from general vehicle routing problems in many aspects. This paper also describes the industrial context, in which various timber transportation vehicle routing problems (TTVRPs) are intrinsic. Several attributes are identified that characterize the TTVRPs, for which various planning and solution methodologies have been implemented.

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.

Full frame distilled prediction

Teacher imitation

Not calibrated prevalence, not ground truth. Human validation pending. Learned from the 10,348 direct Codex labels and 10,348 direct Gemma labels. Candidate is the union of thresholded teacher heads; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels or direct frontier model labels.

metaresearch head score (Codex)0.003
metaresearch head score (Gemma)0.000
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesMeta-epidemiology (narrow)
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Simulation or modeling · Consensus signal: none
GenreCandidate signal: Review · Consensus signal: Review
Teacher disagreement score0.675
Threshold uncertainty score1.000

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0030.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0010.000
Bibliometrics0.0010.000
Science and technology studies0.0000.000
Scholarly communication0.0000.000
Open science0.0000.000
Research integrity0.0000.001
Insufficient payload (model declined to judge)0.0000.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.

Opus teacher head0.051
GPT teacher head0.384
Teacher spread0.333 · how far apart the two teachers sit on this one work
Validation statusscore_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from it