MétaCan
Menu
Back to cohort
Record W2136560859 · doi:10.1109/ccece.1999.804949

Conditions for removing intersample ripples in multirate control

2003· article· en· W2136560859 on OpenAlexaff
Arun K. Tangirala, Sirish L. Shah, Tongwen Chen

Bibliographic record

Venuenot available
Typearticle
Languageen
FieldEngineering
TopicAdvanced Control Systems Optimization
Canadian institutionsUniversity of Alberta
Fundersnot available
KeywordsControl theory (sociology)Curse of dimensionalityComputer scienceController (irrigation)Control systemSampling (signal processing)Control (management)Control engineeringEngineeringFilter (signal processing)Artificial intelligence

Abstract

fetched live from OpenAlex

Multirate systems arise when signals of interest are sampled at different rates. Measurements from chemical processes are typically available at different sampling rates. For example, composition estimates in a distillation column are available at a much slower rate than flow, temperature and pressure measurements. Multirate systems pose a challenging problem due to several reasons such as increased complexity design, time-varying nature, etc. Systems consisting of fast-rate control moves and slow-sampled outputs are a common scenario in chemical processes and of practical interest. Traditionally, inferential techniques based on secondary measurements have been used to design the fast-rate input moves. Lifting techniques conveniently transform multirate systems to single-rate lifted systems with increased dimensionality. Controllers designed using lifting techniques require that certain causality constraints are satisfied. We show firstly, that intersample ripples can arise in the closed-loop output of a multirate system as a result of non-uniform gains of the discrete lifted system and inverse lifting. Secondly, we present conditions on the controller gains to avoid intersample ripples.

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.

How this classification was reachedexpand

Full frame machine prediction

Teacher imitation

Not calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.

metaresearch head score (Codex)0.004
metaresearch head score (Gemma)0.019
Version: metacan-v3-hybrid-931329e0061cValidation 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.004
Threshold uncertainty score0.024

Distilled classifier scores by category (both heads)

CategoryCodexGemma
Metaresearch0.0040.019
Meta-epidemiology (narrow)0.0020.001
Meta-epidemiology (broad)0.0020.001
Bibliometrics0.0010.001
Science and technology studies0.0010.002
Scholarly communication0.0020.002
Open science0.0010.002
Research integrity0.0020.002
Insufficient payload (model declined to judge)0.0040.001

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.007
GPT teacher head0.220
Teacher spread0.213 · 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

Classification

machine, unvalidated

Machine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.

The models applied no category: nothing in the taxonomy fit this work.
Study designSimulation or modeling
Domainnot available
GenreEmpirical

How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".

Quick stats

Citations3
Published2003
Admission routes1
Has abstractyes

Explore more

Same topicAdvanced Control Systems OptimizationFrench-language works237,207