1 / 5

L-H threshold database: Status and Plans

L-H threshold database: Status and Plans. J.W. Hughes , J. Stillerman, MIT PSFC Y. Martin , CRPP-EPFL P. Gohil, GA D. McDonald, JET-EFDA ITPA Transport & Confinement Topical Group Meeting Naka, Japan 2 April 2009. L-H threshold database is changing hands, expanding.

charis
Download Presentation

L-H threshold database: Status and Plans

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. L-H threshold database: Status and Plans J.W. Hughes, J. Stillerman, MIT PSFC Y. Martin, CRPP-EPFL P. Gohil, GA D. McDonald, JET-EFDA ITPA Transport & Confinement Topical Group Meeting Naka, Japan 2 April 2009

  2. L-H threshold database is changing hands, expanding MIT will begin administering the L-H transition database in 2009 Server purchased and expected to be operational in May ‘09 Supported by PSFC computing personnel Accessible to ITPA participants Community usage, openness encouraged Reduced role of centralized administration Simple password authentication for ease of access Development of APIs to allow ease of data extraction, insertion for individual users Nightly backups plus version archiving following publications Two stage development envisioned Existing scalar power threshold database, on an SQL server Profile data, stored in standardized MDSplus tree structures (analogous to existing profile databases used by Pedestal, DIV/SOL groups) ITPA-TC. Naka, 2 April 2009 2

  3. Ideas for profile database development Participants in database effort should determine composition of profile DB Content driven by priorities, key goals of researchers (see next slide) Data sets should be sufficient to provide useful profiles, but not so extensive as to discourage participation A possible model is a tiered data set Tier 1. Global parameters: <ne>, BT, IP, etc. (plus d/dt of each) Tier 2. Essential profiles: ne,i, Te,i, vif, viq et al. Tier 3. Profiles requiring analysis: Poh, Paux, jBS et al. Tier 4. Advanced profile measurements: Prad, n0, flucts. et al. ITPA-TC. Naka, 2 April 2009 3

  4. A goal oriented threshold DB • Optimize effectiveness of DB effort with clear goals, determined by the participants • Profile data for model testing • Profile evolution across the L-H Transition • New dedicated DB or profile DB with cases labelling? • Participation of modellers in definition of set of variables • ITER requirements • Profile data for reducing the uncertainty in Pthresh prediction • Identification of important parameters in individual devices • Agreement on set of variables (depending on current JEX?), filling the DB and analysis ITPA-TC. Naka, 2 April 2009 4

  5. A goal oriented threshold DB (II) • Profile data for predictive capabilites (ITER) • Short term: 0D (and some 1D?) approach based on JEX results • Long term: simulations based on validated models • JEX to reduce the uncertainty • Comparison between devices of L-H trans. • Analysis of the targeted dependence • Reduction of the uncertainty by ‘inserting the parameter’ • Description of present knowledge and remaining issues • Paper to be initiated at the Princeton meeting • Preparation of the Princeton meeting • Strongly dedicated to L-H transitions? ITPA-TC. Naka, 2 April 2009 5

More Related