Aurora

Allow explicit source only as a function of time in forward modeling, for use in OMFIT ImpRad module.

Generalization to read files produced by adas_208, removing initial labels.

Small release to allow for time-dept neutral D atomic density to permit forward modeling using time-dept measured n0 in DIII-D. Update also parsing of SOLPS variables to include latest addition of a new variable.

Small release to solve issues with parsing of unknown variables in SOLPS fort.44.

Created an OMFIT to allow simple interaction with the OMFIT GUI and loading of Aurora ion transport simulations in the form of sorted dictionaries.

Also, included some new features in the SOLPS processing module.

Modification of routines dealing with ADAS files, attempting to prevent issues related to copying to locations without write permissions.

Miscellaneous other updates.

Feature necessary for flexible use of Aurora in OMFIT. @odstrcilt

This release also includes some corrections to KN1D modeling.

The Aurora-SOLPS submodule has gone through a significant update; it can now read SOLPS "full" output from files including b2fstate, b2fgmtry, fort.44, fort.46, fort.33, fort.34, and fort.35. 2D plotting is handled via patches and polygons, showing now end-of-grid discrepancies. Midplane profiles and flux surface averages should be easily handled from a wide range of 2D SOLPS outputs.

The radial grid of Aurora simulations of ion transport has been updated to match old ones produced in fortran, similar to those created by the STRAHL code. This update makes it easier to compare the two codes, e.g. in OMFIT.

Solved issue with PyPI installation with extra directories for ADAS data from the web, now should work well also on Iris with OMFIT and similar situations where users don't have root permissions.

This release begins using the omfit_classes package (https://pypi.org/project/omfit-classes/) rather than previous individual packages for each OMFIT set of classes. Functionality is mostly unchanged, although a few updates related to processing of PEC files from ADAS and plotting of synthetic spectra is included. Better treatment of interpolation of ADAS ADF15 files allows for greater accuracy at low Te values.

This is a small update to better handle atomic data files for users who do not have write-permissions on the device (e.g. a cluster) where they are running Aurora.
@jmcclena

Addition of capability to run and process results from KN1D, a 1D kinetic neutral code originally developed by B. LaBombard (MIT).

The new aurora.solps module also adds capabilities to read and process SOLPS-ITER results. This is still evolving, but already allows useful functionality.

This release offers additional capabilities, especially for radiation modeling and neutrals. The interfaces to ADAS data now allow simple downloading of atomic data from OPEN-ADAS, but users are always able to overrun the defaults for each file. ADF15-reading methods handle better cases with excitation, recombination and charge exchange components, as well as metastable states. A first interface to SOLPS-ITER output has been added to facilitate analysis that involves impurities, neutrals and radiation at the same time. Methods to analyze spectroscopic experimental signals (e.g. from Ly-a diagnostics) have been added. The code can run across multiple computer mounts and is more easily integrated within wider frameworks.

First release of Aurora, still in testing phase.

Aurora is a package to simulate heavy-ion transport and radiation in magnetically-confined plasmas. It offers a 1.5D impurity transport forward model inheriting from the historical STRAHL code, with which it has been thoroughly benchmarked. Routines to analyze neutral states of hydrogen isotopes, both from the edge of fusion plasmas and from neutral beam injection, allow integration of impurity and neutral transport analysis. Aurora’s code is mostly written in Python 3 and Fortran 90, with a Julia interface also recently added. The package enables radiation calculations using ADAS atomic rates, which can easily be applied to the output of Aurora’s own forward model, or coupled with other 1D, 2D or 3D transport codes.