FISSION-PRODUCT RELEASES FROM A PHWR TERMINAL DEBRIS BED
Bibliographic record
Abstract
During an unmitigated severe accident in a pressurized heavy water reactor (PHWR) with horizontal fuel channels, the core may disassemble and relocate to the bottom of the calandria vessel. The resulting heterogeneous in-vessel terminal debris bed (TDB) would likely be quenched by any remaining moderator, and some of the decay heat would be conducted through the calandria vessel shell to the surrounding reactor vault or shield tank water. As the moderator boiled off, the solid debris bed would transform into a more homogeneous molten corium pool located between top and bottom crusts. Until recently, the severe accident code MAAP-CANDU assumed that unreleased volatile and semi-volatile fission products remained in the TDB until after calandria vessel failure, due to low diffusivity through the top crust and the lack of gases or steam to flush released fission products from the debris. However, national and international experimental results indicate this assumption is unlikely; instead, high- and medium-volatility fission products would be released from a molten debris pool, and their volatility and transport should be taken into account in TDB modelling. The resulting change in the distribution of fission products within the reactor and containment, and the associated decay heat, can have significant effects upon the progression of the accident and fission-product releases to the environment. This article describes a postulated PHWR severe accident progression to generate a TDB and the effects of fission-product releases from the terminal debris, using the simple release model in the MAAP-CANDU severe accident code. It also provides insights from various experimental programs related to fission-product releases from core debris, and their applicability to the MAAP-CANDU TDB model.
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.000 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.000 | 0.000 |
| Science and technology studies | 0.001 | 0.000 |
| Scholarly communication | 0.001 | 0.000 |
| Open science | 0.000 | 0.001 |
| Research integrity | 0.001 | 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".