Development of an integrated framework to implement the nuclear safety goals with various safety criteria
Bibliographic record
Abstract
The question “How safe is safe enough?” has been raised since the start of nuclear power plant (NPP) operations in the 1950s, and to address this issue, the Nuclear Regulatory Commission (NRC) of the United States (U.S.) introduced the concept of safety goals in the mid-1980s. In the U.S., the safety goal is called the 0.1 % rule because it requires that the additional risk imposed on individuals and society by the operation of a new NPP should not exceed one-tenth of one percent (0.1 %) of the total risk resulting from other factors to which members of the U.S. population are generally exposed. Nordic countries Sweden and Finland have taken a different approach to setting safety goals for NPPs than the U.S. by introducing requirements for the amount and frequency of cesium-137 (Cs-137) releases. In the case of the Republic of Korea, the regulatory body introduced nuclear safety goals following amendments to the Nuclear Safety Act in 2016. Korea adopted the same safety goal of the 0.1 % rule of the U.S. and simultaneously introduced the Cs-137-related safety goal, which requires that the total frequency of NPP accidents in which the release of Cs-137 exceeds 100 TBq is less than or equal to 1.0E-6 per year. The latter was introduced as a safety goal to protect the environment. Furthermore, while Canada, which has also formally adopted the Cs-137-related safety goal, and Finland require this goal to be applied only to new NPPs, the Korean regulatory body requires the Cs-137-related safety goal to be applied to both operating and new NPPs. Thus, various safety criteria are used in the Korean nuclear safety goals. The use of various safety criteria as in the Korean nuclear safety goals might cause several issues in the practical application of those safety criteria. In this paper, I examine these issues from three main perspectives: (1) consistency, (2) assessment framework, and (3) practical application. I propose several methods to resolve these issues, and also recommend a new integrated framework to implement the safety goals with various safety criteria based on the proposed methods.
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.018 | 0.015 |
| Meta-epidemiology (narrow) | 0.002 | 0.001 |
| Meta-epidemiology (broad) | 0.001 | 0.003 |
| Bibliometrics | 0.005 | 0.002 |
| Science and technology studies | 0.002 | 0.003 |
| Scholarly communication | 0.008 | 0.011 |
| Open science | 0.006 | 0.008 |
| Research integrity | 0.004 | 0.004 |
| Insufficient payload (model declined to judge) | 0.007 | 0.004 |
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".