erwanp / awesome-spectra

🌈 A collaborative list of awesome tools for spectroscopy. Also, check:

awesome-spectra

🌈 A collaborative list of awesome software for spectroscopy. Feel free to contribute

Contents

• Astrophysics & astronomy spectra
• Atmospheric spectra
• General purpose
• Import-Export
• Infrared spectroscopy
• MDS spectroscopy
• UV/VIS spectroscopy
• Spectral inference
• Post-processing
• Databases

Other ways to find spectroscopy software:

• Explore GitHub #spectroscopy packages tagged with "spectroscopy".
• FOSS for Spectroscopy overlaps with this list in part, but presents the options in a slightly different format.

---

Astrophysics & Astronomy Spectra

Generate or analyse astrophysics / astronomy spectra

• ChiantiPy : python package to calculate the radiative properties of astrophysical plasmas based on the CHIANTI atomic database

• HELIOS : GPU-Accelerated Radiative Transfer Code For Exoplanetary Atmospheres

• pyhdust : spectroscopic module of the pyhdust package for multi-technique astronomical data

• pyspeckit : a python spectroscopic toolkit for a wide variety of astronomical instruments.

• specutil : : a Python package for spectral analysis in astronomy

• radiospectra : radio spectra on solar physics from the sunpy package

• SpectroscoPyx : spectroscopy package of the PlasmaPy project

Atmospheric Spectra

Atmosphere spectra, with line of sight

• Py4CAtS (software) : Python code for Computational ATmospheric Spectroscopy (HITRAN, Geisa)

• BART : Bayesian Atmospheric Radiative Transfer fitting code

• GARLIC (software) : Fortran line by line code

• MODTRAN (software) : software for MODerate resolution atmospheric TRANsmission

• lowtran : LOWTRAN atmospheric absorption extinction, scatter and irradiance model--in Python and Matlab

• LBLRTM (software) : Line-by-line calculations of atmospheric fluxes and cooling rates

• libRadtran (software) : C / Fortran functions and programs for calculation of solar and thermal radiation in the Earth's atmosphere

• PyLBLRTM : Helper functions in reading/writing LBLRTM input/output files.

General purpose

General spectral processing or analysis packages

• pyspectra : Python package for working with (hyper)spectral data

• rampy : a Python package for spectral data processing (IR, Raman, XAS...)

• scikit-spectra : Python pandas-based toolkit for explorative spectroscopy (IR, IV-vis, ...).

• Spectragryph (software) : optical spectroscopy software for UV-VIS, NIR, FTIR, Raman, fluorescence, LIBS, XRF data.

• SpectroChemPy : Processing, analysing and modelling spectroscopic data (IR, NMR, UV-vis, ...).

Import-Export

Import/export of spectral data

• Bruker OPUS Reader : Reading the binary OPUS files generated by Bruker spectrometers.

• specio : Interface to read hypersectral data

• lightr : Import UV/VIS spectral data and related metadata in R

Infrared Spectroscopy

Generate or analyse infrared spectra for combustion / plasma physics applications #infrared

• HAPI : HITRAN Application Programming Interface

• HELIOS-K : Ultrafast opacity calculator for exoplanetary atmospheres.

• RADIS : a fast line-by-line code for high-resolution infrared molecular spectra

• SpectraPlot (website) : online interface to HITRAN / HITEMP / NIST data

• HITRAN on the web (website) : online interface to HITRAN data

• RadISpeC : Radiation Interface for Matlab Spectroscopy Calculations. Uses HITRAN and HITEMP

MDS Spectroscopy

• WrightTools (software) : a Python package for multidimensional spectroscopy

UV / Visible Spectroscopy

*Generate or analyse UV/VIS spectra (electronic states of atoms / molecules)

• SPECAIR (software) : software for calculation and fitting of UV/VIS plasma emission

• SPARTAN (software) : software for line-by-line radiative calculation of high-temperature, low pressure plasmas

• pavo : Perceptual Analysis, Visualization and Organization of Spectral Colour Data in R

Spectral inference

and fitting

• Starfish : Tools for Flexible Spectroscopic Inference

Post-processing

general spectral analysis packages

• fityk : curve fitting (peak fitting) software

Databases

Databases for atomic and molecular spectroscopy

• Chianti: atomic line database
• NIST: atomic line database
• EXOMOL: Molecular Line Lists for Exoplanet and Other Atmospheres
• GEISA: atmospheric spectroscopic database
• HITRAN: high-resolution transmission molecular absorption databases for gases of the atmosphere (infrared)
• HITEMP: high temperature molecular spectroscopic database (infrared)
• GASPAR: high-temperature plasma radiation modelling (uv/vis/infrared)

Visualization

Spectral visualizuation utilites

• react-emission-spectra set of react components for visualising atomic lines on the visible spectrum.

awesome-spectra's Issues

I made something and was wondering if it was relevant here

Hey I made a little js library for visual atomic emission spectra and was wondering if it was relevant here
https://github.com/Rested/react-emission-spectra

add to awesome list

The list I'm submitting complies with these requirements:

• Has been around for at least 30 days
  - That means 30 days from either the first real commit or when it was open-sourced. Whatever is most recent.
  - It's the result of hard work and the best I could possibly produce.
• Non-generated Markdown file in a GitHub repo.
• Includes a succinct description of the project/theme at the top of the readme. (Example)
• The repo should have awesome-list & awesome as GitHub topics. I encourage you to add more relevant topics.
• Not a duplicate.
• Only has awesome items. Awesome lists are curations of the best, not everything.
• Includes a project logo/illustration whenever possible.
  - Either fullwidth or placed at the top-right of the readme. (Example)
  - The image should link to the project website or any relevant website.
  - The image should be high-DPI. Set it to maximum half the width of the original image.
• Entries have a description, unless the title is descriptive enough by itself. It rarely is though.
• Includes the Awesome badge.
  - Should be placed on the right side of the readme heading.
  - Should link back to this list.
• Has a Table of Contents section.
  - Should be named Contents, not Table of Contents.
  - Should be the first section in the list.
  - Should only have one level of sub-lists, preferably none.
• Has an appropriate license.
  - That means something like CC0, not a code licence like MIT, BSD, Apache, etc.
  - WTFPL and Unlicense are not acceptable licenses.
  - If you use a license badge, it should be SVG, not PNG.
• Has contribution guidelines.
  - The file should be named contributing.md. Casing is up to you.
• Has consistent formatting and proper spelling/grammar.
  - The link and description are separated by a dash.
  - Example: - AVA - JavaScript test runner.
  - The description starts with an uppercase character and ends with a period.
  - Drop all the A / An prefixes in the descriptions.
  - Consistent and correct naming. For example, Node.js, not NodeJS or node.js.
• Doesn't include a Travis badge.
  - You can still use Travis for list linting, but the badge has no value in the readme.