MétaCan
Menu
Back to cohort
Record W2164146430 · doi:10.1080/0143116031000139845

Detection of lines, line junctions and line terminations

2004· article· en· W2164146430 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

VenueInternational Journal of Remote Sensing · 2004
Typearticle
Languageen
FieldComputer Science
TopicImage and Object Detection Techniques
Canadian institutionsUniversité de Sherbrooke
Fundersnot available
KeywordsDetectorLine (geometry)Computer scienceEdge detectionCanny edge detectorFilter (signal processing)CurvatureAlgorithmInfinite impulse responseArtificial intelligenceComputer visionMeasure (data warehouse)Topology (electrical circuits)MathematicsImage (mathematics)Image processingDigital filterGeometryTelecommunicationsData mining

Abstract

fetched live from OpenAlex

Abstract This paper describes an optimal line detector for the one-dimensional case which is derived from Canny's criteria, and an efficient approach for the detection of line junctions and line terminations. The line detector is extended to the two-dimensional case by operating separately in the x and y directions. An efficient implementation using an infinite impulse response (IIR) filter is provided. This implementation has the additional advantage that increasing the filter scale affects neither temporal nor spatial complexity. The detection algorithm for junctions and terminations is divided into two steps. First, given the lines extracted from the original image, a local measure of line curvature is estimated using the mean of the dot products of orientation vectors within a given neighbourhood. The second step involves the localization of junctions and terminations. Experimental results using several synthetic and real images demonstrate the validity of the two methods. Notes 1In this paper, edge detection is performed only by using a filtering operation; thus the terms filter and detector as used are synonymous.

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: Bench or experimental · Consensus signal: none
GenreCandidate signal: Methods · Consensus signal: none
Teacher disagreement score0.898
Threshold uncertainty score0.288

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.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.012
GPT teacher head0.274
Teacher spread0.262 · 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