MétaCan
Menu
Back to cohort
Record W2116765515 · doi:10.1093/ijlct/ctr001

Exergy analysis of heat exchangers in the copper-chlorine thermochemical cycle to enhance thermal effectiveness and cycle efficiency

2011· article· en· W2116765515 on OpenAlex
Mehmet F. Orhan, İbrahim Dinçer, Marc A. Rosen

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

VenueInternational Journal of Low-Carbon Technologies · 2011
Typearticle
Languageen
FieldEngineering
TopicChemical Looping and Thermochemical Processes
Canadian institutionsOntario Tech University
FundersNatural Sciences and Engineering Research Council of Canada
KeywordsThermochemical cycleExergyHeat exchangerNuclear engineeringExergy efficiencyThermodynamic cycleThermal efficiencyHeat transferCopperThermodynamicsProcess engineeringHeat recovery ventilationEnvironmental scienceMaterials scienceWaste managementChemistryHydrogen productionHydrogenEngineeringMetallurgy

Abstract

fetched live from OpenAlex

Most existing nuclear power plants in North America are typically water-cooled and operate at 250–500°C. For this temperature level, the copper–chlorine (Cu–Cl) cycle is one of the most promising cycles that can be integrated with nuclear reactors for hydrogen production by decomposing water into its constituents. In this study, we analyze the heat exchangers in the Cu–Cl thermochemical cycle so as to enhance heat transfer effectiveness and thereby improve the cycle efficiency. The thermal management options for internal and external heat transfer are studied and heat recovery opportunities are investigated and compared. Each heat exchanger in the cycle is examined individually based on the chemical/physical behavior of the process, and the most appropriate options are recommended. A thermodynamic analysis and associated parametric studies are performed for various configurations to contrast their efficiencies and effectivenesses.

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: Bench or experimental
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.016
Threshold uncertainty score0.371

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.001
Science and technology studies0.0000.000
Scholarly communication0.0000.000
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.008
GPT teacher head0.243
Teacher spread0.235 · 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