1 / 10

Lynton Appel Representing…..

This work discusses the practical implementation of Unified Automation Language (UAL) with the EFIT code, funded by UK Engineering and Physical Research Council and EURATOM. It explores the challenges and advantages of integrating UAL with the ITM structure, providing a possible approach for efficient implementation. The implementation process for MAST data has been successfully achieved, and future plans include complete implementation for JET data and the replacement of the quasi-ITM structure with the complete ITM structure.

myedinak
Download Presentation

Lynton Appel Representing…..

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. Practical Experience of a UAL with EFIT Lynton Appel Representing….. David Muir, David Taylor, Vladimir Drozdov, Emelia Solano This work was jointly funded by the UK Engineering and Physical Research Council and EURATOM

  2. Background • 2004: EFIT code re-written for MAST “EFIT-f90” • (50k 12k lines); FORTRAN77 FORTRAN95; all machine specific info placed in a single module; input/output to ASCII files, FORTRAN unformatted files, and IDA-3 files) • Sept 2005: JET decide to replace their existing version of EFIT code with “EFIT-f90”. • Nov 2005: EFIT code interfaced to UAL with IDAM for MAST, JET…..

  3. Possible approach to UAL implementation • Ideal world - ITM makes structures, these are adequate for all, everyone uses them in harmony • Issues: • Codes may require data from many parts of the ITM structure. • Code developments must be linked to modifications/additions in ITM structure. • Code interface to ITM • can be messy (multiple calls for data) • require downloading of massive amounts of unwanted data • Codes require a second method of data entry for day-to-day running.

  4. A practical approaches to UAL implementation • There exists an ITM structure and a code structure; The UAL maps between the two structures. • Advantages: • Input/output code structure can be designed to optimise clarity. • code structure contains only the data required. • Code structure under the control of the code RO. • Straightforward to make temporary modifications. • Can use the same code structure for day-to-day running. • Straightforward for users to construct/modify code structure. • Implementation allows the use of Web services. • Disadvantage: efficiency non-optimal?

  5. Schematic of UAL JET MAST ITM ?? User-files UAL IDAM Quasi-ITM structure • Run modes: EFIT_IN structure constructed from • Quasi-ITM structure • User-files • Quasi-ITM structure with local modifications EFIT_OUT Structure EFIT_IN Structure Equilibrium solver

  6. Quasi-ITM structure • Contains cut-down full ITM structure. Will be replaced by fulI ITM structure • Each Instance is described in IDAM by an XML file • Static data is stored directly in XML • For measurement data XML stores location of data. Flux_loops Magnetic_probes Pfcircuits Pfcoils Pfsupplies Toroidal_field Plasma_current pfpassive Quasi ITM

  7. EFIT-IN structure • Contains Input fields required by EFIT for a single time • All input fields should be derivable from full ITM structure. M  W R Z  Magnetic probes constraints grid(:,:,:) fcoil(:,:,:) greens grid grid(:,:,:) fcoil(:,:) grid magnetic probes EFIT_IN limiter current fitdz numerical pp_base ff_base ww_base Bvac_r

  8. Construction of the EFIT-IN structure • At present code implementation is very inelegant! • Immediate issue: cannot easily transfer IDAM structure from C to FORTRAN. Problem solved with FORTRAN2003. • In future, possible to automate if EFIT_IN and ITM structures have XML descriptions.

  9. Structure of Driver routine • Neat short code • Concept of UAL is complicated by get_ITM occurring outside time-loop. initialize ITM_extract_single_time read i/p namelist Fill_EFITIN_with_ITM get_ITM(device,shot) Modify_EFITIN_structure Create EFIT_IN structure Call EFIT (Loop over time)

  10. Implementation • Have successfully implemented scheme for MAST data to run EFIT via IDAM. • For JET data have created a quasi-ITM structure via IDAM • Future plans • Complete JET implementation • Replace quasi-ITM structure with complete ITM strucutre (!) • Construct EFIT_OUT structure and “ITM_put”

More Related