MétaCan
Menu
Back to cohort
Record W1966364820 · doi:10.1109/tia.2015.2417834

Design Considerations of 2-D Magnetizers for High Flux Density Measurements

2015· article· en· W1966364820 on OpenAlex
John Wanjiku, Pragasen Pillay

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

VenueIEEE Transactions on Industry Applications · 2015
Typearticle
Languageen
FieldMaterials Science
TopicMagnetic Properties and Applications
Canadian institutionsConcordia University
FundersNatural Sciences and Engineering Research Council of Canada
KeywordsMagnetic fluxMagnetizationFlux (metallurgy)Magnetic flux leakageEddy currentMagnetYoke (aeronautics)Electromagnetic coilMaterials scienceMechanicsRange (aeronautics)Magnetic fieldElectrical engineeringMechanical engineeringPhysicsEngineeringComputational physicsComposite material

Abstract

fetched live from OpenAlex

A 2-D magnetizer introduces variation in the flux density (B) across the sample under rotational magnetization. This variation requires additional energy requirements that limits the attainable aspect ratios, flux density levels and stresses the supply. A numerical methodology that accounts for the flux leakage and the eddy currents is proposed to analyze uniformity and variation in B in four 2-D magnetizers. The analysis was done beyond the knee of the magnetization curve. Numerical results will show that round magnetizers can mitigate the variation of the square magnetizer by over 92%, by making the MMF more sinusoidal and equalizing the reluctance along the airgap. In addition, deeper yokes minimized the variation by about 50% in the square and the Halbach testers. The results of this analysis was a design that mitigates the variation in B by a combination of sinusoidally distributed windings, and a deep yoke. The proposed magnetizer achieved very high flux densities over a relatively wide frequency range, which were 2.04 and 1.69 T at 60 Hz and 1 kHz, respectively.

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: Bench or experimental · Consensus signal: Bench or experimental
GenreCandidate signal: Methods · Consensus signal: none
Teacher disagreement score0.914
Threshold uncertainty score0.955

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.0010.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.134
GPT teacher head0.286
Teacher spread0.152 · 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