Welcome to EUROfusion Integrated Modelling workflow’s documentation!
Contents
- 1. Introduction to the EUROfusion Project Code Development for integrated modelling
- 2. Infrastructure
- 2.1. Kepler
- 2.1.1. Introduction to Kepler - basics
- 2.1.2. Kepler IMAS actors
- 2.1.3. IMAS Kepler based configuration
- 2.1.4. FC2K - Embedding user codes into Kepler
- 2.1.4.1. FC2K basics
- 2.1.4.1.1. What FC2K actually does?
- 2.1.4.1.2. FC2K main window
- 2.1.4.1.3. Actor description
- 2.1.4.1.4. Environment
- 2.1.4.1.5. “Arguments” tab explained
- 2.1.4.1.6. “Parameters” tab explained
- 2.1.4.1.7. “Source” tab explained
- 2.1.4.1.8. “Settings” tab explained
- 2.1.4.1.9. “Documentation” tab explained
- 2.1.4.1.10. “Interface” tab explained
- 2.1.4.2. Incorporating user codes into Kepler using FC2K - exercises
- 2.1.4.1. FC2K basics
- 2.1.5. FC2K - developer guidelines
- 2.1.6. FC2K - Example 1 - Embedding Fortran codes into Kepler (no CPOs)
- 2.1.6.1. Get familiar with codes that will be incorporated into Kepler
- 2.1.6.2. Build the code by issuing
- 2.1.6.3. Prepare environment for FC2K
- 2.1.6.4. Start FC2K application
- 2.1.6.5. Open a nocpo_example_1 project
- 2.1.6.6. Project settings
- 2.1.6.7. After all the settings are correct, you can generate actor
- 2.1.6.8. Confirm Kepler compilation
- 2.1.6.9. You can now start Kepler and use generated actor
- 2.1.6.10. Launch the workflow
- 2.1.7. FC2K - Example 2 - Embedding Fortran code into Kepler (CPOs)
- 2.1.7.1. Get familiar with codes that will be incorporated into Kepler
- 2.1.7.2. Build the code
- 2.1.7.3. Prepare environment for FC2K
- 2.1.7.4. Start FC2K application
- 2.1.7.5. Open project cposlice2cposlicef_fc2k
- 2.1.7.6. Project settings
- 2.1.7.7. After all the settings are correct, you can generate actor
- 2.1.7.8. Confirm Kepler compilation
- 2.1.7.9. You can now start Kepler and use generated actor
- 2.1.7.10. Launch the workflow
- 2.1.8. FC2K - Example 3 - Embedding C++ code within Kepler (no CPOs)
- 2.1.8.1. Get familiar with codes that will be incorporated into Kepler
- 2.1.8.2. Build the code by issuing
- 2.1.8.3. Prepare environment for FC2K
- 2.1.8.4. Start FC2K application
- 2.1.8.5. Open project simplecppactor_nocpo
- 2.1.8.6. Project settings
- 2.1.8.7. Actor generation
- 2.1.8.8. Confirm Kepler compilation
- 2.1.8.9. You can now start Kepler and use generated actor
- 2.1.8.10. Launch the workflow
- 2.1.9. FC2K - Example 4 - Embedding C++ code within Kepler (CPOs)
- 2.1.9.1. Get familiar with codes that will be incorporated into Kepler
- 2.1.9.2. Build the code by issuing
- 2.1.9.3. Prepare environment for FC2K
- 2.1.9.4. Start FC2K application
- 2.1.9.5. Open project simplecppactor
- 2.1.9.6. Project settings
- 2.1.9.7. Actor generation
- 2.1.9.8. Confirm Kepler compilation
- 2.1.9.9. You can now start Kepler and use generated actor
- 2.1.10. IMAS Kepler 2.1.3 (default release)
- 2.1.11. IMAS Kepler 2.1.5 (release candidate)
- 2.1.12. Installation based on README file
- 2.2. General Grid Description and Grid Service Library
- 2.1. Kepler
- 3. European Transport Simulator (ETS)
- 3.1. ETS Documentation
- 3.2. ETS workflows in KEPLER
- 3.2.1. Configuring the ETS run
- 3.2.1.1. Workflow parameters
- 3.2.1.2. Ion, Impurity and Neutral Composition
- 3.2.1.3. Equations to be solved and boundary conditions
- 3.2.1.4. Convergence loop
- 3.2.1.5. Equilibrium
- 3.2.1.6. Transport
- 3.2.1.7. MHD
- 3.2.1.8. Sources and impurity
- 3.2.1.9. Instantaneous events & Actuators
- 3.2.1.10. Scenario output
- 3.2.1.11. Visualization during the run
- 3.2.2. List of Actors
- 3.2.1. Configuring the ETS run
- 3.3. Turbulent Flux Quantities in Transport Models
- 3.4. Running Exponential Average
- 4. Equilibrium and MHD Stability workflow (EQSTABIL)
- 5. The EQRECONSTRUCT workflow
- 6. Turbulence with synthetic diagnostics workflows
- 7. Codes
- 7.1. IMASviz
- 7.2. IMASgo!
- 7.3. How to turn a C++ code into a Kepler actor
- 7.4. Plasma equilibrium and MHD list of codes
- 7.5. Heating, current drive (H&CD) and fast particles list of codes
- 7.5.1. Electron heating codes
- 7.5.1.1. EC wave codes
- 7.5.1.2. Combined electron Fokker-Planck codes
- 7.5.1.3. Wave codes for ion cyclotron heating
- 7.5.1.4. Fokker-Planck codes for ion cyclotron heating
- 7.5.1.5. NBI sources for Fokker-Planck codes
- 7.5.1.6. Nuclear sources (input for Fokker-Planck codes)
- 7.5.1.7. NBI Fokker-Planck codes
- 7.5.1.8. Runaway electrons
- 7.5.1.9. Advanced codes
- 7.5.1.10. Codes for fast ion-MHD interactions
- 7.5.1. Electron heating codes
- 7.6. Transport list of codes
- 8. Conventions
- 8.1. Standard Machine Names
- 8.2. Physics Conventions
- 8.2.1. Coordinate System
- 8.2.2. Representation of the Magnetic Field and Current
- 8.2.3. Poloidal and Toroidal Fluxes
- 8.2.4. Safety Factor
- 8.2.5. Signs
- 8.2.6. COCOS - toroidal coordinate conventions
- 8.2.7. The Flux Surface Average
- 8.2.8. The Toroidal Flux Radius as the Radial Coordinate
- 8.2.9. Toroidal and Parallel Current
- 8.2.10. Straight Field Line Coordinates
- 8.2.11. Plasma Betas
- 8.2.12. Internal Inductance
- 8.2.13. Poloidal Angle Dimension in Equilibrium CPO
- 8.3. Numerical and computational conventions
- 9. AMNS
- 9.1. Scientific Rationale and Main Objectives
- 9.2. EU-IM contact person
- 9.3. AMNS tasks
- 9.4. AMNS Documentation
- 9.4.1. AMNS User Interface
- 9.4.2. C AMNS User Interface
- 9.4.3. Python AMNS User Interface
- 10. Additional resources
Using the WPCD workflows
Use of the WPCD workflows is available via the EUROfusion Gateway, the JET analysis cluster (FREIA) and the ITER IO HPC
The WPCD documentation and workflow concepts are copyright of the EUROfusion consortium.