MétaCan
Menu
Back to cohort

Machine Learning-based Trajectory Planning for Single-loop Flatness-based Control of PMSMs

2025· article· en· W4407803133 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

Venuenot available
Typearticle
Languageen
FieldEngineering
TopicIndustrial Technology and Control Systems
Canadian institutionsMcMaster University
Fundersnot available
KeywordsFlatness (cosmology)Computer scienceTrajectoryControl theory (sociology)Loop (graph theory)Control (management)Artificial intelligencePhysicsMathematics

Abstract

fetched live from OpenAlex

Permanent magnet synchronous motors (PMSMs) are among the most widely used motors in modern industry. Over the past few decades, extensive research has been conducted on various control methods, while field-oriented control (FOC) being one of the most well-known approaches. Additionally, flatness-based (FB) control has been introduced in the literature as a solution for addressing the nonlinear characteristics inherent in PMSM drive systems. Traditional FB control methods typically has a cascaded structure and employ second-order functions as trajectory functions to maintain the flatness property of the drive system. However, this cascaded structure presents certain limitations, particularly in applications requiring high-dynamic performance. To overcome these drawbacks, the concept of single-loop FB control has been proposed in recent studies. One significant challenge in single-loop FB control systems is ignoring controller limits, such as overcurrent protection. To address this issue, this paper proposes a novel trajectory planning method for single-loop FB control of PMSMs, using machine learning. The proposed method effectively tackles the challenge of current protection while maintaining the system’s flatness property. The effectiveness of the proposed approach has been validated through simulation studies, demonstrating its potential for enhancing the performance of PMSM drives.

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: Simulation or modeling · Consensus signal: Simulation or modeling
GenreCandidate signal: Empirical · Consensus signal: none
Teacher disagreement score0.967
Threshold uncertainty score0.656

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.015
GPT teacher head0.229
Teacher spread0.214 · 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