Wavelet Transform Based Methodology for Detection and Characterization of Multiple Oscillations in Nonstationary Variables
Bibliographic record
Abstract
Diagnosing the root cause of a propagated oscillation in the operation requires detection of all process variables that are oscillating with similar frequencies followed by application of an appropriate root cause diagnosis procedure. Oscillations in chemical processes are usually caused by controller tuning, valve problems, or external oscillatory disturbances. There are several methods proposed in literature for root cause diagnosis of oscillations within the system. However, most of the methodologies can only work for a specific type of oscillation. For example, the methodologies based on quantifying the nonlinearity of variables can help with root cause diagnosis of a valve-induced oscillation but cannot help if the oscillation actually has occurred due to aggressive controller tuning or due to an external oscillatory disturbance. Therefore, before trying to find out which loop within the system has caused the oscillation, it is important to categorize the oscillation meaning to learn if the oscillation is caused by a nonlinear valve within the system, controller tuning or an external disturbance to choose an appropriate diagnostic procedure. The different characteristics of these three oscillation types are studied in the literature with methodologies to distinguish them from each other. However, the proposed methodologies can work reliably when there is only one oscillatory component present in the variables and cannot help in cases of multiple oscillations. Also, nonstationary trends and noise within variables are yet a challenging issue in detection and diagnosis of oscillations. This paper presents a comprehensive oscillation detection and characterization procedure based on wavelet transform. The methodology is capable of both detection and independent characterization of multiple oscillation frequencies in variables as well as implementing automatic noise and nonstationary trend removal algorithms. Advantages of the proposed method are illustrated through analysis of data sampled from an industrial process as well as simulations.
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 imitationNot 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.
Distilled classifier scores by category (both heads)
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.001 | 0.003 |
| Meta-epidemiology (narrow) | 0.001 | 0.000 |
| Meta-epidemiology (broad) | 0.001 | 0.001 |
| Bibliometrics | 0.002 | 0.002 |
| Science and technology studies | 0.000 | 0.001 |
| Scholarly communication | 0.001 | 0.001 |
| Open science | 0.001 | 0.001 |
| Research integrity | 0.001 | 0.001 |
| Insufficient payload (model declined to judge) | 0.001 | 0.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.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from itClassification
machine, unvalidatedMachine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.
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".