The Coupling of Nuclear Heat and Hydrogen Production Thermochemical Cycles
Bibliographic record
Abstract
The technology to use nuclear heat to thermally split water into hydrogen and oxygen attracts more and more attentions at present. This paper discusses some challenges to couple nuclear heat with thermochemical hydrogen production cycles. The challenges include matching the maximum heat grade of thermal chemical cycles and nuclear reactors, and extracting heat from nuclear reactors. Sulfur-iodine and copper-chlorine cycles are taken as typical examples for analysis and discussion. The heat grade and quantity required by each step of the cycles are discussed. The maximum heat grade of sulfur-iodine cycle is higher than 800°C which cannot be easily coupled by GenIV nuclear reactor and other sources of heat must be provided. In comparison, the maximum heat grade of copper-chlorine cycle is 530°C which can be coupled by more nuclear reactors such as advance Gen-III and future Gen-IV nuclear reactor. It is concluded that thermochemical cycles with lower temperature requirement are easier to couple with present and future generations of reactors. Low temperature thermochemical cycles such as copper-chlorine cycles are recommended to match the heat grade of most nuclear reactors. Some methods are proposed to couple heat between a thermochemical cycle and nuclear power generating station. Several heat extraction methods such as using working fluid of nuclear reactor to provide heat to thermochemical cycles are proposed in this paper.
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.
How this classification was reachedexpand
Full frame machine prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.
Distilled classifier scores by category (both heads)
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.000 | 0.001 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.000 | 0.000 |
| Science and technology studies | 0.000 | 0.000 |
| Scholarly communication | 0.000 | 0.001 |
| Open science | 0.000 | 0.001 |
| Research integrity | 0.000 | 0.001 |
| Insufficient payload (model declined to judge) | 0.002 | 0.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.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from itClassification
machine, unvalidatedMachine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.
How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".