Development of an integrated framework to implement the nuclear safety goals with various safety criteria
Pourquoi ce travail est dans la base
Une base qui oublie comment elle a trouvé un travail ne peut pas être vérifiée. Voici les voies qui ont admis celui-ci.
Notice bibliographique
Résumé
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.
Récupéré en direct depuis OpenAlex et désinversé. Les résumés ne sont pas conservés dans cette base de données : les index inversés représentent 8,6 Go des 9,3 Go de texte de la base, et le serveur dispose de 13 Go libres.
Prédiction distillée sur la base complète
Imitation des enseignantsNi prévalence calibrée, ni vérité terrain. Validation humaine à venir. Apprise à partir de 10 348 étiquettes directes de Codex et de 10 348 étiquettes directes de Gemma. Le mode candidate est l'union des têtes enseignantes seuillées; le consensus est leur intersection. Ces sorties portent le statut machine_predicted_unvalidated et ne sont ni des étiquettes humaines ni des étiquettes directes de modèles de pointe.
Scores Codex et Gemma par catégorie
| Catégorie | Codex | Gemma |
|---|---|---|
| Métarecherche | 0,000 | 0,000 |
| Méta-épidémiologie (sens strict) | 0,000 | 0,000 |
| Méta-épidémiologie (sens large) | 0,000 | 0,000 |
| Bibliométrie | 0,000 | 0,001 |
| Études des sciences et des technologies | 0,000 | 0,000 |
| Communication savante | 0,000 | 0,000 |
| Science ouverte | 0,000 | 0,000 |
| Intégrité de la recherche | 0,000 | 0,000 |
| Charge utile insuffisante (le modèle a refusé de juger) | 0,000 | 0,000 |
Scores machine (provisoires)
Les deux têtes enseignantes du modèle étudiant, lues sur ce travail. Un score ordonne la base pour la relecture; il n'affirme jamais une catégorie, et le statut de validation accompagne chaque rangée tel quel.
Scores de référence d'un modèle non mature (critères de maturité non atteints, 7 itérations). Un score ordonne; il n'affirme jamais une catégorie.
score_only:v0-immature-baseline · tel quel depuis la passe de notation : score_only signifie que le nombre peut ordonner les travaux, et qu'aucune étiquette de catégorie n'en découle