MétaCan
Menu
Back to cohort
Record W2116746070 · doi:10.5565/rev/elcvia.508

Comprehensive Analysis of High-Performance Computing Methods for Filtered Back-Projection

2013· article· en· W2116746070 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.
fundA Canadian funder is recorded on the work.

Bibliographic record

VenueELCVIA Electronic Letters on Computer Vision and Image Analysis · 2013
Typearticle
Languageen
FieldMedicine
TopicMedical Imaging Techniques and Applications
Canadian institutionsUniversity of Alberta
FundersNatural Sciences and Engineering Research Council of CanadaServierTechnische Universität MünchenUniversity of Alberta
KeywordsComputer scienceCUDADirectXOpenGLPipeline (software)Computer graphics (images)Projection (relational algebra)Graphics processing unitImaging phantomGraphicsGraphics pipelineComputational scienceParallel computingArtificial intelligence3D computer graphicsAlgorithmVisualization

Abstract

fetched live from OpenAlex

This paper provides an extensive analysis concerning runtime, accuracy and noise of High-Performance Computing (HPC) frameworks for Computed Tomography (CT) reconstruction tasks: "conventional" multi-core, multi threaded CPUs, the Compute Unified Device Architecture (CUDA) on GPUs, and the graphics pipeline of GPUs as facilitated by the DirectX or OpenGL programming interfaces, exploiting various built-in hardwired features like rasterization and texture filtering. We compare implementations of the Filtered Back-Projection (FBP) algorithm with fan-beam geometry on all these HPC frameworks. Specifically, an ACR-accredited phantom is reconstructed from the raw attenuation data acquired by a clinical CT scanner. Our analysis shows that a single GPU can run the FBP algorithm for reconstructing a 1024 x 1024 image considerably faster than a 64-core, multi-threaded CPU machine. Moreover, employing the graphics pipeline further increases performance as compared to CUDA, albeit with slightly lower accuracy due to "fast math" operations.

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: Empirical · Consensus signal: none
Teacher disagreement score0.947
Threshold uncertainty score0.714

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0000.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0010.000
Bibliometrics0.0010.002
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.013
GPT teacher head0.345
Teacher spread0.332 · 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