ASTRA: Difference between revisions

Jump to navigation Jump to search
21 bytes added ,  17 July 2014
no edit summary
No edit summary
No edit summary
 
Line 6: Line 6:
Presently, the code is used for transport simulations of [[Tokamak|tokamak]] and [[Stellarator|stellarator]] plasmas. If used for tokamak plasmas, the Grad-Shafranov equation can be used 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 [[Tokamak|tokamak]] and [[Stellarator|stellarator]] plasmas. If used for tokamak plasmas, the Grad-Shafranov equation can be used 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.


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. An example of how the ASTRA suit can be extended for particular needs can be found [http://www.iaea.org/inis/collection/NCLCollectionStore/_Public/41/046/41046471.pdf here] (In Spanish), where subroutines have been developed to couple the set of transport equations with [http://fusionwiki.ciemat.es/wiki/EIRENE Eirene] and Fafner to obtain respectively recycling and [http://fusionwiki.ciemat.es/wiki/TJ-II:Neutral_Beam_Injection neutral beam injection] sources for the [http://fusionwiki.ciemat.es/wiki/TJ-II TJ-II] device.
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. An example of how the ASTRA suit can be extended for particular needs can be found [http://www.iaea.org/inis/collection/NCLCollectionStore/_Public/41/046/41046471.pdf here] (In Spanish), where subroutines have been developed to couple the set of transport equations with the Montecarlo codes [http://fusionwiki.ciemat.es/wiki/EIRENE Eirene] and Fafner to obtain respectively recycling and [http://fusionwiki.ciemat.es/wiki/TJ-II:Neutral_Beam_Injection neutral beam injection] sources for the [http://fusionwiki.ciemat.es/wiki/TJ-II TJ-II] device.
    
    
== See also ==
== See also ==

Navigation menu