MétaCan
Menu
Back to cohort
Record W2760409432 · doi:10.1109/rbme.2017.2757013

Are Current Advances of Compression Algorithms for Capsule Endoscopy Enough? A Technical Review

2017· review· en· W2760409432 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

VenueIEEE Reviews in Biomedical Engineering · 2017
Typereview
Languageen
FieldMedicine
TopicGastrointestinal Bleeding Diagnosis and Treatment
Canadian institutionsUniversity of Saskatchewan
Fundersnot available
KeywordsComputer scienceCapsule endoscopyData compressionRisk analysis (engineering)Bandwidth (computing)Image compressionStrengths and weaknessesAlgorithmImage processingArtificial intelligenceTelecommunicationsMedicineImage (mathematics)

Abstract

fetched live from OpenAlex

The recent technological advances in capsule endoscopy system have revolutionized the healthcare system by introducing new techniques and functionalities to diagnose gastrointestinal tract. These techniques improve diagnostic accuracy and reduce the risk of hospitalization. Although many benefits of capsule endoscopy are known, there are still limitations including lower battery life, higher bandwidth, poor image quality and lower frame rate, which have restricted its wide use. In order to solve these limitations, the importance of a low-cost compression algorithm, that produces higher frame rate with better image quality and yet consumes lower bandwidth and transmission power, is paramount. While several review papers have been published describing the capability of capsule endoscope in terms of its functionality and emerging features, an extensive review on the compression algorithms from past and for future applications is still of great interest. Hence, in this review, we aim to address the issue by exploring the characteristics of endoscopic images, analyzing the strengths and weaknesses of useful compression techniques, and making suggestions for possible future adaptation.

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.001
metaresearch head score (Gemma)0.002
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesMeta-epidemiology (narrow)
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Systematic review · Consensus signal: none
GenreCandidate signal: Review · Consensus signal: Review
Teacher disagreement score0.687
Threshold uncertainty score1.000

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0010.002
Meta-epidemiology (narrow)0.0010.000
Meta-epidemiology (broad)0.0060.001
Bibliometrics0.0000.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.189
GPT teacher head0.464
Teacher spread0.275 · 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