MétaCan
Menu
Back to cohort
Record W2134966567 · doi:10.1109/87.845871

Viable cascade control and application to a batch polymerization process

2000· article· en· W2134966567 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

VenueIEEE Transactions on Control Systems Technology · 2000
Typearticle
Languageen
FieldEngineering
TopicAdvanced Control Systems Optimization
Canadian institutionsQueen's University
Fundersnot available
KeywordsControl theory (sociology)CascadeController (irrigation)ComputationBoundary (topology)Nonlinear systemControl engineeringProcess (computing)Computer scienceAffine transformationSet (abstract data type)Process controlMathematicsControl (management)EngineeringAlgorithmPhysicsArtificial intelligence

Abstract

fetched live from OpenAlex

A hybrid model based on nonlinear control systems and on control affine systems is investigated. For both cases the defining dynamics (or vector fields) at a given time may undergo abrupt changes. Using the framework of viability theory, a controller is proposed that keeps the states within some user-specified region. This desired region is defined by constant bounds on individual states as well as by bounds on state-dependent functions. A viable cascade controller (VCC) is introduced which combines a typical (existing) controller (C) with a viable controller (VC). We assume that a design for C is given. The design of VC is based on computation of the velocity controlled regulation map which provides a set of control inputs that will both keep the states within the viable region as well as prevent these states from approaching the boundary of the viable region at high velocity. Theoretical background for the design of VCC is presented with a simple example which is used to demonstrate some of the computations. This approach is then applied to a batch polymerization process and simulation results are provided.

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: Simulation or modeling
GenreCandidate signal: Empirical · Consensus signal: none
Teacher disagreement score0.979
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.0010.001
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.002
GPT teacher head0.196
Teacher spread0.194 · 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