The ERO code – Manual

The ERO code – Manual

Contents

1. Introduction

2. Programme structure

3. Input parameter for ERO run: The interface JERO

4. Atomic and molecular data

5. Starting an ERO simulation

6. ERO output files

6.1. The graphical interface eropng

6.2. Description of the binary output files

6.3. Description of the ASCII output files

6.4. Temporary files

7. Installation of the ERO code

8. References

The ERO code – Manual

1. Introduction

The three-dimensional Monte Carlo code ERO simulates the transport of impurities through the edge plasma of fusion devices. Impurities are generated through plasma-wall interaction effects (physical sputtering or chemical erosion) but can also be externally injected through gas inlets. Normally the impurities start as neutrals from the surface. In dependent on the plasma parameters they are ionised or dissociated at a certain distance from the surface. The following movement is then determined by the Lorentz force, friction with the

background, thermal forces and diffusion. More details about the physics included in the code can be found in [NF2000].

ERO can be adapted to various experimental geometries (limiter machines like TEXTOR, pertor configurations like JET or ASDEX as well as linear plasma simulators such as PISCES). The “standard” ERO version handles various geometries for testlimiters such as roof or mushroom shaped tiles. In the simplest case the plasma background used for the simulations comes from measurements. However, especially for pertor configurations the 2D plasma in a poloidal cross section is taken from plasma simulations (e.g. B2-EIRENE) which themselves use experimental data as input.

2. Programme structure: flow charts

ERO is written in the programming language C. The main(..) -routine first calls readdata(..) to read the necessary input parameter from the input file for a specific simulation. Afterwards in the move-ctrl(..) routine the main part of the ERO simulation is started. Finally datapool1(..) writes the results into output files.

Read data from

input parameter file

Calculation of

erosion, deposition

and particle transport

Write output data

The following flow chart shows the (simplified) structure of move_ctrl(..). After some

preparation work (not explicitly included in flow chart) such as generating the surface grid and spectroscopy volume, defining possible markers on the surface, reading data from the previous time step and calculating the surface concentration of the different species in the interaction layer, the main physics part starts. The different plasma-wall-interaction

processes are executed consecutively inside a switch query. After having calculated the amount of eroded particles in each surface cell their transport through the plasma is

simulated via the test particle approximation (background plasma is not influenced by test particle) and using the Monte Carlo method. A loop over the number of test particles is executed. The transport of externally injected particles is calculated in the external source loop.

The ERO code – Manual

Calculation of amount of physically eroded particles in each surface cellCalculation of amount of chemically eroded particles in each surface cellCalculation of amount of deposited carbon from background plasmaCalculation of transport of externally injected particlesCalculation of transport of chemically eroded particlesCalculation of transport of physically eroded particles

3. Input parameter for ERO run: the interface JERO

The graphical interface JERO

Main aim of the window-based interface JERO is to provide a tool to create input files for ERO simulations and therefore to facilitate the handling of the multitude of input parameters. Existing input parameter files can be loaded by clicking OPEN after having clicked FILE. In the directory “jero_1.0.1/examples” (which is generated after installation of JERO) an

example file named “params.input” can be loaded into JERO. Opening it with a conventional text editor shows the structure of the ERO input file: In the line after a keyword, which describes the input parameter the corresponding value of the parameter is defined. E.g. following the keyword "pathtoresult" the next line should contain a string defining the starting letters of the output files. Comment lines (which are not read by ERO) start with a “#”. After having typed in values into the JERO windows for the input parameters a file with the correct (“ERO readable”) format can be generated by using the SAVE button. As stated above existing input parameter files can be loaded for editing. JERO is developed in JAVA and therefore flexible to use on different platforms (e.g. Windows or UNIX). In the following it is described how to install and start JERO on your local system.

The ERO code – Manual

=

SYSTEM PREQUISITES for JERO:

JERO is a Java application that requires Java Run Time Environment. Check if the Java Runtime Environment version 1.3 or higher is installed on your computer:

* On MS Windows: type “java –version” in a DOS box.

* On Unix: type “java –version” at the command line.

If the execution of the command fails or if you have a java version lower than 1.3, please go to the SUN web page to download and install JRE or SDK 1.4 on your local computer, following the instructions given there.

INSTALLATION of JERO:

1. After download of JERO (link) unzip and extract the file:

gzip -d c jero_1.0.1.tar.gz | tar xvf -

2. Initialise the environment variable JAVA_HOME …… 此处隐藏：17794字，全部文档内容请下载后查看。喜欢就下载吧 ……