MétaCan
Menu
Back to cohort
Record W2091447749 · doi:10.13182/nt13-1

Deployment Strategies for Wireless Sensor Networks in Nuclear Power Plants

2014· article· en· W2091447749 on OpenAlex

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

VenueNuclear Technology · 2014
Typearticle
Languageen
FieldEngineering
TopicNuclear and radioactivity studies
Canadian institutionsWestern University
FundersNatural Sciences and Engineering Research Council of CanadaUniversity Network of Excellence in Nuclear Engineering
KeywordsWorkaroundWireless sensor networkWirelessComputer scienceSoftware deploymentContainment (computer programming)Nuclear powerWireless networkKey distribution in wireless sensor networksNuclear power plantTransmission (telecommunications)Computer networkTelecommunications

Abstract

fetched live from OpenAlex

Applications of wireless technologies in nuclear power plants (NPPs), in particular for monitoring purposes, have been gaining popularity recently. It has been shown that wireless technologies can offer several advantages over wired solutions. However, many challenges need to be overcome before widespread adoption of wireless systems in nuclear industries. This paper has extended the existing work in this area and has developed a systematic procedure to deploy a wireless sensor network within a NPP containment. The developed scheme deals with the following challenges explicitly: (a) restrictions on the peak transmission power of the wireless sensor modules, (b) workaround of large concrete and metal structures, and (c) avoidance of locations with high radiation levels. Starting from the sensor locations dictated by the variables to be measured, the scheme determines the positions of the wireless relaying modules in a three-dimensional containment space to ensure reliable data communication. The results from case studies under realistic NPP containment conditions demonstrate the practical value of the proposed solution.

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: Not applicable · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.478
Threshold uncertainty score0.738

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.000
Science and technology studies0.0000.000
Scholarly communication0.0000.000
Open science0.0000.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.006
GPT teacher head0.199
Teacher spread0.193 · 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