MétaCan
Menu
Back to cohort
Record W2149987644 · doi:10.1109/ias.2004.1348813

A maximum torque per ampere vector control strategy for synchronous reluctance motors considering saturation and iron losses

2004· article· en· W2149987644 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.

Bibliographic record

VenueConference Record of the 2004 IEEE Industry Applications Conference, 2004. 39th IAS Annual Meeting. · 2004
Typearticle
Languageen
FieldEngineering
TopicElectric Motor Design and Analysis
Canadian institutionsMemorial University of Newfoundland
Fundersnot available
KeywordsAmpereControl theory (sociology)TorqueDirect torque controlMagnetic reluctanceVector controlSwitched reluctance motorSaturation (graph theory)Synchronous motorComputer scienceEngineeringControl (management)MagnetMathematicsCurrent (fluid)Induction motorPhysicsVoltageElectrical engineering

Abstract

fetched live from OpenAlex

In recent years, the synchronous reluctance (SyncRel) motor received much attention for many applications due to its simple and robust construction. When using the principle of vector control, it is possible to achieve optimal operation of SyncRel motors for all loads and speeds. A suitable control strategy can be implemented to achieve maximum torque per ampere, high efficiency and maximum power factor. However, the control of a SyncRel motor is highly affected by both magnetic saturation and high iron losses. A new strategy to achieve maximum torque per ampere (MTPA) is proposed in this paper. The motor behavior under vector control is analyzed considering both saturation and iron losses. A simple relationship between the developed torque and d-axis current has been obtained for MTPA conditions. After experimental check, the obtained relation has been implemented in a vector control algorithm. The proposed control strategy has been successfully implemented with the aid of an experimental setup.

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 categoriesMeta-epidemiology (narrow)
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Simulation or modeling · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.437
Threshold uncertainty score1.000

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0000.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0010.000
Bibliometrics0.0000.000
Science and technology studies0.0000.000
Scholarly communication0.0000.000
Open science0.0010.000
Research integrity0.0010.001
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.016
GPT teacher head0.234
Teacher spread0.218 · 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