MétaCan
Menu
Back to cohort
Record W2942426424

JET DT Scenario Extrapolation and Optimization with METIS

2017· article· en· W2942426424 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.

aboutThe title or abstract carries a Canadian signal from the geographic lexicon.
no affNo Canadian affiliation: this work is invisible to an affiliation-only frame.
No Canadian affiliation. An affiliation-only frame, the usual design, would never have seen this work. It is one of the works that make the case for inverting the frame.

Bibliographic record

VenueASEP · 2017
Typearticle
Languageen
FieldEngineering
TopicSuperconducting Materials and Applications
Canadian institutionsnot available
Fundersnot available
KeywordsMetisExtrapolationJet (fluid)PhysicsComputer scienceMechanicsMathematicsStatisticsWorld Wide Web
DOInot available

Abstract

fetched live from OpenAlex

Bayesian optimization is applied to tokamak scenario optimizations. The key advantages are 1) a reduced number of objective function evaluations, 2) no need for derivatives, and 3) the possibility to include a prior knowledge. This is of a great value for optimizing tokamak scenarios, where several (competing) objectives with often unknown magnitudes exist and the number of parameters is large (>10). The first two properties imply that Bayesian optimization is well suited for heavy, complex objective functions. Reusing previous iterations as priors for next optimization steps effectively enables interactive, multiobjective optimizations, regardless of whether a human decision maker is included or not. We show that these features make Bayesian optimization an outstanding tool for optimizing tokamak scenarios. Objective functions and constraints, targeting, e.g., fusion gain, flux consumption, coils currents limits or q-profile, can be assembled interactively. The optimized parameter vector may include actuators like plasma current or heating waveforms. We demonstrate the capabilities on optimizing ITER and DEMO-like scenarios, simulated by the METIS code

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: Empirical
Teacher disagreement score0.210
Threshold uncertainty score0.148

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.017
GPT teacher head0.222
Teacher spread0.205 · 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