MétaCan
Menu
Back to cohort
Record W2790999378 · doi:10.1071/aseg2018abw10_3d

Multidimensional Topology Transforms

2018· article· en· W2790999378 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.

Bibliographic record

VenueASEG Extended Abstracts · 2018
Typearticle
Languageen
FieldComputer Science
TopicNeural Networks and Applications
Canadian institutionsLaurentian University
Fundersnot available
KeywordsTopology (electrical circuits)Computer scienceMathematicsCombinatorics

Abstract

fetched live from OpenAlex

Most currently constructed 3D geological models are to a first order the result of transformations of data with different dimensionality into 3D: 0D (e.g. outcrop data, at the regional scale),1D (e.g. drill hole data, at the mine scale),2D data (e.g. satellite data, at the regional scale) or3D data (e.g. seismic data, when high resolution 3D geophysical data are available, such as in basins),4D models (3D evolutions with time).The datasets used to project between dimensions vary according to the scenario, however they generally consist of a mixture of 0D observations and local temporal or spatial relationships (their topology). Modern software systems are able to use a sub-set of these relationships (fault-stratigraphy relationships for example) to build 3D geological models, however the relationships are not typically used as an independent constraint on how much of the 3D model is constrained by observations, and how much is generated by the end user (or the algorithms they use).This study explores the relationships between topological observations in 1, 2 and 3D in order to better understand how these may be used in the future as inputs to a revised 3D modelling workflow. We have investigated both synthetic cases, where we have full control, and natural examples, which permit alternate hypotheses. This approach has potential relevance to mine-scale and regional 3D models where the 3D topologies are poorly defined by the existing data, but 1D and 2D constraints are available.

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: Other design · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.617
Threshold uncertainty score0.750

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0000.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.000
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.001

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.014
GPT teacher head0.270
Teacher spread0.256 · 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