Conditional space evaluation of progress variable definitions for Cambridge/Sandia swirl flames
Bibliographic record
Abstract
Data from all spatial locations of nine turbulent flames in the Cambridge/Sandia swirl database are combined to study how the choice of scalar variables in conditional moment closure (CMC) type approaches affect the conditional spatial fluctuations of reactive scalars. In order to investigate the influence of swirl and stratification, two additional data-sets have been constructed. Principal component analysis (PCA) is applied to help identify the number of scalar variables and the most appropriate choices to describe the composition space. Two PCA scaling methods have been adopted, namely Pareto and Auto-scaling. Regardless of the data-set investigated and the scaling method used, the results suggest that a single principal component correlated with temperature accounted for the largest variance. For the first moment hypothesis, four progress variable, c, definitions identified by PCA are selected as conditioning variables to investigate the conditional fluctuations and normalised RMS of various species and temperature from all three databases at all axial locations. The results indicate that two control variables based on mixture fraction, Z, and progress variable significantly reduce the conditional fluctuations of scalars compared to a single variable. The selection of progress variables had minimal effects on the RMS of conditional fluctuations for all tested conditions, although a slight reduction of conditional fluctuations was found for the temperature-based progress variable, which can potentially help the further extension of CMC-based models in different flame configurations. The present study also shows that using Z and c (regardless of its definition) as two conditioning scalars enables the detachment of the thermo-chemical state from space, swirl and stratification effects. This suggests that adopting a doubly conditioned source term estimation (DCSE) approach might successfully predict the considered set of flames, assuming that ensembles are divided along the axial direction.
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.003 | 0.005 |
| Meta-epidemiology (narrow) | 0.001 | 0.000 |
| Meta-epidemiology (broad) | 0.001 | 0.001 |
| Bibliometrics | 0.003 | 0.001 |
| Science and technology studies | 0.000 | 0.000 |
| Scholarly communication | 0.001 | 0.001 |
| Open science | 0.001 | 0.001 |
| Research integrity | 0.000 | 0.001 |
| Insufficient payload (model declined to judge) | 0.001 | 0.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.
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".