MétaCan
Menu
Back to cohort
Record W2123833862 · doi:10.1109/icip.1995.529582

Object-oriented coding using successive motion field segmentation and estimation

2002· article· en· W2123833862 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

VenueProceedings - International Conference on Image Processing · 2002
Typearticle
Languageen
FieldComputer Science
TopicAdvanced Data Compression Techniques
Canadian institutionsUniversité Laval
Fundersnot available
KeywordsMotion estimationQuarter-pixel motionMotion fieldMotion compensationBlock-matching algorithmArtificial intelligenceComputer visionSegmentationComputer scienceMaximum a posteriori estimationData compressionImage segmentationBlock (permutation group theory)AlgorithmCoding (social sciences)Pattern recognition (psychology)MathematicsObject (grammar)Video trackingMaximum likelihood

Abstract

fetched live from OpenAlex

Block-based motion compensation assumes that all pixels within a block have the same translational motion. That hypothesis, however, results in inaccurate compensation of moving objects' boundaries. Object-oriented video compression algorithms typically segment each image in regions of uniform motion and estimates the motion of these regions to generate more accurate motion compensated images. We present a two-stage algorithm for motion field segmentation and estimation in an object-oriented coder. In the algorithm's first stage, a standard block-matching algorithm and a maximum a posteriori probability estimate are used to compute a translational motion field and its segmentation. This segmentation is then utilized in the second stage to estimate the parameters of complex motion models. The parameters of the complex motion models are only estimated in the algorithm's second stage which reduces the computational complexity of the proposed algorithm. Simulation results show that the proposed algorithm significantly reduces the bit rate needed to encode video sequences when compared to standard block-based algorithms.

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: none
GenreCandidate signal: Methods · Consensus signal: none
Teacher disagreement score0.888
Threshold uncertainty score0.956

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.0010.005
Open science0.0010.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.044
GPT teacher head0.331
Teacher spread0.287 · 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