ASTRA: Difference between revisions

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 ==

Demanding calculations are conveniently done through system calls from the ASTRA subroutines.  One such possible extensions of the ASTRA is the coupling of the calculations to 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; or the coupling to ray-tracing calculations, including the access to distributed resources<ref>D. López-Bruna, J. M. Reynolds, A. Cappa, J. Martinell, J. García, and C. Gutiérrez-Tapia, “Programas periféricos de ASTRA para el TJ-II,” Informe Técnico Ciemat 1201, CIEMAT, March 2010, [https://documenta.ciemat.es/bitstream/123456789/114/1/40921_IC1201.pdf]</ref>.

== See also ==

* [https://w3.pppl.gov/~hammett/work/2009/Astra_ocr.pdf ASTRA online manual]

== References ==