MétaCan
Menu
Back to cohort
Record W1762397077 · doi:10.1139/cjce-2012-0462

Analysis of ground penetrating radar data using hierarchical Markov Chain Monte Carlo simulation

2013· article· en· W1762397077 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.

venuePublished in a venue whose home country is Canada.
no affNo Canadian affiliation: this work is invisible to an affiliation-only frame.
No Canadian affiliation. An affiliation-only frame, the usual design, would never have seen this work. It is one of the works that make the case for inverting the frame.

Bibliographic record

VenueCanadian Journal of Civil Engineering · 2013
Typearticle
Languageen
FieldEngineering
TopicGeophysical Methods and Applications
Canadian institutionsnot available
Fundersnot available
KeywordsGround-penetrating radarMarkov chain Monte CarloMonte Carlo methodRadarRemote sensingComputer scienceGeologyStatisticsMathematics

Abstract

fetched live from OpenAlex

Ground penetrating radar (GPR) is a geophysical method used in highway maintenance to determine subsurface conditions within the right-of-way. GPR operates by using short-pulse radiation of radio-frequency electromagnetic energy to record dissimilarities in electrical properties of subsurface materials. As such, GPR results are susceptible to the transmission frequency used and the inherent properties of different subsurface materials. Uncertainty due to these susceptibilities can lead to ambiguity in the interpretation of GPR data. To distinguish heterogeneity from uncertainty, this paper modeled GPR data on pavement layer thickness using Markov Chain Monte Carlo (MCMC) simulation. MCMC is able to model heterogeneity within a given dataset and was employed to estimate and predict layer thicknesses obtained from GPR data. Simulated results were consistent with field data and provided statistical estimates of missing values in the original dataset. This analysis will aid relevant stakeholders to verify and determine consistency in field GPR data.

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.000
metaresearch head score (Gemma)0.000
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Simulation or modeling · Consensus signal: Simulation or modeling
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.140
Threshold uncertainty score0.624

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0000.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0010.001
Science and technology studies0.0000.000
Scholarly communication0.0000.000
Open science0.0000.000
Research integrity0.0000.000
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.026
GPT teacher head0.251
Teacher spread0.225 · 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