MétaCan
Menu
Back to cohort
Record W2901313711 · doi:10.25071/10315/35287

Particle Image Velocimetry Data Processing On A Gpu Cluster

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

VenueProgress in Canadian Mechanical Engineering · 2018
Typearticle
Languageen
FieldEngineering
TopicFluid Dynamics and Turbulent Flows
Canadian institutionsUniversity of Toronto
Fundersnot available
KeywordsParticle image velocimetryComputer scienceCluster (spacecraft)Particle tracking velocimetryImage processingVelocimetryComputer graphics (images)Artificial intelligenceImage (mathematics)PhysicsOptics

Abstract

fetched live from OpenAlex

Particle image velocimetry (PIV) data processing is a computationally expensive process. The immense time taken to analyze data can limit the maximum dataset size. Using graphics processing units (GPUs) has been shown to drastically decrease the processing time for PIV image pairs. The open-source PIV data processing software OpenPIV has been ported to run on a GPU to boost speed and efficiency and has outperformed the CPU version of the software. A multipass method is being implemented in OpenPIV to improve both speed and accuracy. The completed algorithm will be tested on an embedder CPU-GPU device, a desktop computer, and the SOSCIP GPU-accelerated supercomputing cluster. Ultimately, OpenPIV will run on a wide variety of computer platforms an enable larger datasets to be collects, leading to better statistics on the resulting velocity fields.

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: Empirical
Teacher disagreement score0.796
Threshold uncertainty score0.917

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.238
Teacher spread0.226 · 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