32
edits
ASTRA: Difference between revisions
Jump to navigation
Jump to search
no edit summary
(Update of references with documentation purposes) |
No edit summary |
||
| Line 4: | Line 4: | ||
Presently, the code is used for transport simulations of both [[Tokamak|tokamak]] and [[Stellarator|stellarator]] plasmas. If used for tokamak plasmas, the Grad-Shafranov equation can be solved to update the geometry as the plasma current density and pressure evolve. In the case of stellarators, the geometry can be taken from experimental files where the most relevant metric coefficients and magnitudes are defined. | Presently, the code is used for transport simulations of both [[Tokamak|tokamak]] and [[Stellarator|stellarator]] plasmas. If used for tokamak plasmas, the Grad-Shafranov equation can be solved to update the geometry as the plasma current density and pressure evolve. In the case of stellarators, the geometry can be taken from experimental files where the most relevant metric coefficients and magnitudes are defined. In this case, [https://servicios.mpr.es/VisorPublicaciones/visordocumentosicopo.aspx?NIPO=83220004X&SUBNIPO=0001&IDPUBLICACION=000183220 subroutines] can be added to update at will the metric coefficients depending on the plasma currents. Moreover, despite the one-dimensional nature of the transport equations, appropriate handling of the integration space permits also making calculations that include magnetic islands or ergodic plasma regions. | ||
ASTRA includes an extended library of physical modules, a graphic interface, plotting and post-run viewing facilities, etc. Along with the common libraries, every user can have his local libraries of different formulae and functions, experimental data and simulation results. The physics models are defined by the user through a high level programming language –ASTRA specific, but easy to learn– where the different formulae and functions can be directly included from the libraries. In addition, there is a set of subroutines that can be plugged into the models, thus allowing for complex evaluations of e.g. source terms. Subroutines can also be created by the user: every time ASTRA is run, it checks for modifications of the ASTRA environment (functions, formulae, subroutines... ) so the corresponding objects are compiled and included in the ASTRA framework for immediate use. Examples of how the ASTRA suit can be extended for particular needs can be found below for the case of the TJ-II Heliac at [ | |||
ASTRA includes an extended library of physical modules, a graphic interface, plotting and post-run viewing facilities, etc. Along with the common libraries, every user can have his local libraries of different formulae and functions, experimental data and simulation results. The physics models are defined by the user through a high level programming language –ASTRA specific, but easy to learn– where the different formulae and functions can be directly included from the libraries. In addition, there is a set of subroutines that can be plugged into the models, thus allowing for complex evaluations of e.g. source terms. Subroutines can also be created by the user: every time ASTRA is run, it checks for modifications of the ASTRA environment (functions, formulae, subroutines... ) so the corresponding objects are compiled and included in the ASTRA framework for immediate use. Examples of how the ASTRA suit can be extended for particular needs can be found below for the case of the TJ-II Heliac at [https://www.ciemat.es CIEMAT]. | |||
== Extensions of ASTRA for the TJ-II stellarator == | == Extensions of ASTRA for the TJ-II stellarator == | ||