MétaCan
Menu
Back to cohort
Record W2026246025 · doi:10.1115/1.2039114

Predicting Thermal Contact Resistance Between Molten Metal Droplets and a Solid Surface

2005· article· en· W2026246025 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

VenueJournal of Heat Transfer · 2005
Typearticle
Languageen
FieldEngineering
TopicAdhesion, Friction, and Surface Interactions
Canadian institutionsUniversity of Toronto
Fundersnot available
KeywordsMaterials scienceThermal contact conductanceComposite materialBrassThermal conductionContact resistanceSurface roughnessThermal resistanceSurface finishContact areaSubstrate (aquarium)Interfacial thermal resistanceWettingAluminiumThermalContact angleMetallurgyThermodynamicsCopper

Abstract

fetched live from OpenAlex

Thermal contact resistance between molten metal droplets (aluminum alloy 380 and bismuth) and solid plates (steel and brass) was measured experimentally. The diameter of the droplets was 4mm, and droplet impact velocity ranged between 1 and 3m∕s. Substrate temperature was varied from 25to300°C and roughness from 0.06to5.0μm. Substrate temperature variation under impacting droplets was measured using fast temperature sensors that had a response time of 40ns and recorded substrate temperatures at five different radial locations under each droplet. Thermal contact resistance during the first few milliseconds of impact was obtained by matching measured surface temperature variation with an analytical solution of the one-dimensional transient heat conduction equation. An analytical model of the deformation of a free liquid surface in contact with a rough solid was used to calculate the true area of contact between them and, thereby, the thermal contact resistance. Test results agreed well with predictions from the analytical model. Thermal contact resistance values ranged from 10−7to3×10−6m2K∕W, increasing with surface roughness and decreasing with rising impact velocity.

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: Empirical · Consensus signal: Empirical
Teacher disagreement score0.408
Threshold uncertainty score0.490

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.001
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.011
GPT teacher head0.232
Teacher spread0.222 · 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