The Open FUSION Toolkit 1.0.0-8905cc5
Modeling tools for plasma and fusion research and engineering
|
In this example we show how to generate a mesh for the ITER device using TokaMakers built in mesh generation.
pip
or other standard methods.To load the TokaMaker python module we need to tell python where to the module is located. This can be done either through the PYTHONPATH
environment variable or using within a script using sys.path.append()
as below, where we look for the environement variable OFT_ROOTPATH
to provide the path to where the OpenFUSIONToolkit is installed (/Applications/OFT
on macOS).
For meshing we will use the gs_Domain class to build a 2D triangular grid suitable for Grad-Shafranov equilibria. This class uses the triangle code through a simple internal python wrapper within OFT.
First we define some target sizes to set the resolution in out grid. These variables will be used later and represent the target edge size within a given region, where units are in meters. In this case we are using a fairly coarse resolution of 15 cm in the plasma region and 60 cm in the vacuum region. Note that when setting up a new machine these values will need to scale with the overall size of the device/domain. Additionally, one should perform a convergence study, by increasing resolution (decreasing target size) by at least a factor of two in all regions to ensure the results are not sensitive to your choice of grid size.
The geometry information (eg. bounding curves for vacuum vessels) are now loaded from a JSON file. For simple geometries, testing, or generative usage this can be created directly in the code. However, it is often helpful to separate this information into a fixed datafile as here. This JSON file contains the following:
limiter
: A contour of R,Z points defining the limiter (PFC) surfaceinner_vv
: Two contours of R,Z points defining the inner and outer boundary of the inner vacuum vesselouter_vv
: Two contours of R,Z points defining the inner and outer boundary of the outer vacuum vesselcoils
: A dictionary of R,Z,W,H values defining the PF coils as rectangles in the poloidal cross-sectionWe now create and define the various logical mesh regions. In the ITER case we have 6 regions:
air
: The region outside the vacuum vessel, which is not actually air in a complex device like ITER but we use this terminology for commonality with present research devicesplasma
: The region inside the limiter where the plasma will existvacuum1
: The region between the inner vacuum vessel and the limitervacuum2
: The region between the inner and outer vacuum vesselsvv1
: The inner vacuum vesselvv2
: The outer vacuum vesselPF1,...
: Each of the 14 coils in ITER (6 CS, 6 PF, 2 VS)In ITER all coils are independent except for the vertical stability coil (VS
), which is single coil set composed of two counter-wound coils. To treat this set as a single coil we use the coil_set
and nTurns
argument to define_region() to join the coils in a single VS
coil set with opposing polarities.
nTurns
can also be used to define the number of turns in a given coil region. At the moment we are not including # of turns in this model so we keep the amplitude for each coil as 1.0 and only adjust the polarity.For each region you can provide a target size and one of four region types:
plasma
: The region where the plasma can exist and the classic Grad-Shafranov equation with \(F*F'\) and \(P'\) are allowed. There can only be one region of this typevacuum
: A region where not current can flow and \(\nabla^* \psi = 0\) is solvedboundary
: A special case of the vacuum
region, which forms the outer boundary of the computational domain. A region of this type is required if more than one region is specifiedconductor
: A region where toroidal current can flow passively (no externally applied voltage). For this type of region the resistivity should be specified with the argument eta
in units of \(\omega \mathrm{-m}\).coil
: A region where toroidal current can flow with specified amplitude through set_coil_currents() or via shape optimization set_coil_reg() and set_isoflux()Once the region types and properties are defined we now define the geometry of the mesh using shapes and references to the defined regions.
plasma
as the region enclosed by the contour and vacuum1
as the region outside the contour.vacuum1
as the region enclosed by the annulus, vv1
as the annular region itself, and vacuum2
as the region outside the annulus.vacuum2
as the region enclosed by the annulus, vv2
as the annular region itself, and air
as the region outside the annulus.air
as the region outside the rectangle for the CS and PF coils and vacuum1
for the VS coils.Warning: sliver (angle=45.0) detected at point 31 (5.565, -4.5559)
After defining the logical and physical topology we can now plot the curves within the definitions to double check everything is in the right place. In cases where curves appear to cross eachother (as with the VS coil and inner VV) one should zoom in to ensure no crossings exist. In this case we had to move the upper VS coil down by 1 cm to avoid an intersection with the geometry available for this example.
Now we generate the actual mesh using the build_mesh() method. Additionally, if coil
and/or conductor
regions are defined the get_coils() and get_conductors() methods should also be called to get descriptive dictionaries for later use in TokaMaker. This step may take a few moments as triangle generates the mesh.
Note that, as is common with unstructured meshes, the mesh is stored a list of points mesh_pts
of size (np,2), a list of cells formed from three points each mesh_lc
of size (nc,3), and an array providing a region id number for each cell mesh_reg
of size (nc,), which is mapped to the names above using the coil_dict
and cond_dict
dictionaries.
Assembling regions: # of unique points = 885 # of unique segments = 74 Generating mesh: # of points = 4757 # of cells = 9400 # of regions = 20
We now plot the mesh by region to inspect proper generation.
As generation of the mesh often takes comparable, or longer, time compare to runs in TokaMaker it is useful to separate generation of the mesh into a different script as demonstrated here. The method save_gs_mesh() can be used to save the resulting information for later use. This is done using and an HDF5 file through the h5py library.