Leader: D.
Coster
Deputy: V.
Basiuk, D. Kalupin,
V. Parail , G. Pereverzev
-
To
provide the computational basis for a modular transport code,
taking account of the core, the pedestal and the scrape-off layer
-
Ultimately,
to enable the simulation of complete tokamak
scenarios, e.g. for ITER
-
Implement a
systematic verification and experimental validation
procedure for the transport modeling activities
-
Implement
systematic documentation on the transport modeling tools
-
Implement
systematic reporting of the transport modeling results
As the number
of codes analyzing the transport in the plasma core
(ASTRA, CRONOS, JETTO and RITM) and at the edge and SOL regions
(EDGE2D, TECXY
etc.) is already used by EU modelers, the fastest and practical way to
construct the ITM transport code is to assemble it from existing
modules. Thus
the main task of the project
will
be identification and implementation of
existing modules, where the standardized interface should be developed
together
with ISIP group. It also will be required to validate and verify, as
well as to
document each of the module before it gets the ITM label on it. It does
not
mean that we are going to choose the single module for each component
of the ITM
transport code, it can be several of modules doing basically the same
physics
and the users will be free to choose one of them. The task of the IMP3
project
is to bring all of these modules to the stage when they will be
approved to be
used as ITM tools and can be linked to other ITM modules through the
standardized interfaces. The project is divided for six tasks
representing
different components of the transport simulations:
MHD
equilibrium and stability modules
Tasks:
-
identification
of existing
equilibrium modules (in conjunction with IMP1);
-
preparation
of
standardized interfaces (in conjunction with IMP1 and ISIP);
-
preparation
of equilibrium
modules by extraction from existing codes (in conjunction with IMP1);
-
implementation
of prepared
equilibrium modules (in conjunction with IMP1);
-
documentation
/
verification / validation /benchmarking (in conjunction with IMP1).
Non-linear
modules (saw-teeth, ELMs,
NTMs)
Tasks:
-
identification
of existing
non-linear modules (in conjunction with IMP2);
-
preparation
of
standardized interfaces (in conjunction with IMP2 and ISIP);
-
preparation
of non-linear
modules by extraction from existing codes (in conjunction with IMP2);
-
implementation
of prepared
non-linear modules (in conjunction with IMP2);
-
documentation
/
verification / validation /benchmarking (in conjunction with IMP2).
Transport
models
Tasks:
-
identification
of existing
transport modules (in conjunction with IMP4);
-
preparation
of transport
modules by extraction from existing codes;
-
preparation
of
standardized interfaces (in conjunction with IMP4 and ISIP);
-
documentation
/
verification / validation /benchmarking (in conjunction with IMP4);
-
implementation
of prepared
transport modules (in conjunction with IMP4 and ISIP).
Sources
and Sinks
Tasks:
-
identification
of existing
source modules (in conjunction with IMP5);
-
preparation
of
standardized interfaces (in conjunction with IMP5 and ISIP);
-
preparation
of source
modules by extraction from existing codes (in conjunction with IMP5);
-
implementation
of prepared
source modules (in conjunction with IMP5)
-
documentation
/
verification / validation /benchmarking (in conjunction with IMP5)
Interfaces
to boundaries
Tasks:
-
identification
of existing
edge codes (in conjunction with IMP5);
-
preparation
of
standardized core-edge interfaces (in conjunction with ISIP and other
IMP3 tasks);
-
preparation
of edge
modules by extraction from existing codes;
-
implementation
of prepared
edge modules (in conjunction with ISIP and other IMP3 tasks);
-
documentation
/
verification / validation /benchmarking (in conjunction with other IMP3
tasks).
Whole
device modeling
Tasks:
-
identification
of existing
device modeling tools;
-
preparation
of
standardized interfaces (in conjunction with ISIP);
-
preparation
of the first
(simple) tool for Whole Device Modelling and outlining the resources
required
for the development of more comprehensive tools;
-
implementation
of prepared
modules (in conjunction with ISIP and other IMP3 tasks);
-
documentation
/
verification / validation /benchmarking (in conjunction with ISIP and
other
IMP3 tasks ).
IMP3
is the central ITM project aimed to provide users with a tool for the
transport
simulations, available from the plasma axis until the wall. It is
subdivided
for six tasks, from to
,
addressing different transport modeling issues, which should
develop the modular components for the
future tokamak simulator. There is a strong overlap of each particular
task
within the ITM-IMP3 project to other IMPs and ISIP, which includes
development,
implementation and validation&verification activity for each
task.
|
|
PLANNED IMP3
ACTIVITY |
|
JANUARY |
Participation
to the TFT meeting at JET Participation
to the IMP4 meeting at JET |
FEBRUARY |
|
|
MARCH |
Benchmarking of
core transport codes using JAMS platform at JET |
|
APRIL |
|
|
MAY |
|
|
JUNE |
|
|
JULY |
|
|
AUGUST |
|
|
SEPTEMBER |
General ITM
meeting (preliminary) |
|
OCTOBER |
|
|
NOEMBER |
|
|
DECEMBER |
|