This repository provides a straightforward and standalone implementation for computing coronal densities.
Two small example notebooks that can be used to infer FE XIII coronal densities using a CHIANTI calculation look-up table. Target lines are the infrared Fe XIII 1074.7nm and 1079.8nm pair.
- NSO's DKIST Cryo-NIRSP or DL-NIRSP slit and imaging spectro-polarimeters
- HAO's MLSO CoMP/uCoMP imaging full-disk polarimetric coronagraph
Some sample data that can be downloaded and unarchived directly into your repository clone will enable running the example notebooks can be found here.
uCoMP/CoMP data can be downloaded from MLSO.
Cryo-NIRSP or DL-NIRSP data can be downloaded from the DKIST Datacenter.
- This implementation is a standalone coronal density calculations that are implemented and available through the CLEDB coronal inversion.
- Spatio-temporal matching observations in both Fe XIII infrared lines are required.
- The LOS integration assumption exists. Users should be very careful when interpreting their coronal signals as they get integrated along the LOS. This approach is valid only in spaces where a dominant coherent structure exists. A superposition of structures along the LOS is not adequately represented in terms of density computed via this method.
- Examples offer a parallel/multithread cpu implementation, making calculations reasonably fast.
- Options for processing either peak line emission or integrated line emission exist for all instruments.
- Accurate header and pointing information from the data providers are required.
- Currently, a high-resolution look-up table is provided in this repository. The table is created using CHIANTI V10.1 through a PyCELP implementation.
- A PyCELP generated look-up table generator notebook is also provided. Users should not generate new look-up tables unless a specific need exists. The provided tables are flexible enough to suit most needs.
- A lower parameter space resolution deprecated look-up table created via a SSWIDL CHIANTI implementation still exists, but this is deprecated and should only be used for cross-validating calculations, and not for production runs.
This implementation benefits and uses published results from: