././@PaxHeader 0000000 0000000 0000000 00000000033 00000000000 011451 x ustar 00 0000000 0000000 27 mtime=1643306919.748087
specutils-1.6.0/ 0000755 0005037 0002007 00000000000 00000000000 015604 5 ustar 00rosteen STSCI\science 0000000 0000000 ././@PaxHeader 0000000 0000000 0000000 00000000034 00000000000 011452 x ustar 00 0000000 0000000 28 mtime=1643306919.7003136
specutils-1.6.0/.github/ 0000755 0005037 0002007 00000000000 00000000000 017144 5 ustar 00rosteen STSCI\science 0000000 0000000 ././@PaxHeader 0000000 0000000 0000000 00000000034 00000000000 011452 x ustar 00 0000000 0000000 28 mtime=1643306919.7058005
specutils-1.6.0/.github/workflows/ 0000755 0005037 0002007 00000000000 00000000000 021201 5 ustar 00rosteen STSCI\science 0000000 0000000 ././@PaxHeader 0000000 0000000 0000000 00000000026 00000000000 011453 x ustar 00 0000000 0000000 22 mtime=1643302783.0
specutils-1.6.0/.github/workflows/ci_cron_weekly.yml 0000644 0005037 0002007 00000003505 00000000000 024723 0 ustar 00rosteen STSCI\science 0000000 0000000 name: Weekly cron
on:
schedule:
# run every Monday at 6am UTC
- cron: '0 6 * * 1'
jobs:
tests:
name: ${{ matrix.name }}
runs-on: ${{ matrix.os }}
if: github.repository == 'astropy/specutils'
strategy:
fail-fast: false
matrix:
include:
# We check numpy-dev also in a job that only runs from cron, so that
# we can spot issues sooner. We do not use remote data here, since
# that gives too many false positives due to URL timeouts. We also
# install all dependencies via pip here so we pick up the latest
# releases.
- name: Python 3.7 with dev version of key dependencies
os: ubuntu-latest
python: 3.8
toxenv: py38-test-devdeps
- name: Documentation link check
os: ubuntu-latest
python: 3.7
toxenv: linkcheck
# TODO: Uncomment when 3.10 is more mature. Should we use devdeps?
# Test against Python dev in cron job.
#- name: Python dev with basic dependencies
# os: ubuntu-latest
# python: 3.10-dev
# toxenv: pydev-test
steps:
- name: Checkout code
uses: actions/checkout@v2
with:
fetch-depth: 0
- name: Set up Python
uses: actions/setup-python@v2
with:
python-version: ${{ matrix.python }}
- name: Install language-pack-de and tzdata
if: ${{ matrix.os == 'ubuntu-latest' }}
run: sudo apt-get install language-pack-de tzdata
- name: Install graphviz
if: ${{ matrix.toxenv == 'linkcheck' }}
run: sudo apt-get install graphviz
- name: Install Python dependencies
run: python -m pip install --upgrade tox
- name: Run tests
run: tox ${{ matrix.toxargs}} -e ${{ matrix.toxenv}} -- ${{ matrix.toxposargs}}
././@PaxHeader 0000000 0000000 0000000 00000000026 00000000000 011453 x ustar 00 0000000 0000000 22 mtime=1643302783.0
specutils-1.6.0/.github/workflows/ci_workflows.yml 0000644 0005037 0002007 00000007072 00000000000 024442 0 ustar 00rosteen STSCI\science 0000000 0000000 name: CI
on:
push:
pull_request:
jobs:
tests:
name: ${{ matrix.name }}
runs-on: ${{ matrix.os }}
strategy:
fail-fast: false
matrix:
include:
- name: Code style checks
os: ubuntu-latest
python: 3.x
toxenv: codestyle
- name: Python 3.7 with minimal dependencies
os: ubuntu-latest
python: 3.7
toxenv: py37-test
- name: Python 3.8 with all optional dependencies
os: ubuntu-latest
python: 3.8
toxenv: py38-test-alldeps
toxargs: -v --develop
toxposargs: --open-files
# NOTE: In the build below we also check that tests do not open and
# leave open any files. This has a performance impact on running the
# tests, hence why it is not enabled by default.
- name: Python 3.7 with oldest supported version of all dependencies
os: ubuntu-18.04
python: 3.7
toxenv: py37-test-oldestdeps
- name: Python 3.7 with numpy 1.17 and full coverage
os: ubuntu-latest
python: 3.7
toxenv: py37-test-alldeps-numpy117-cov
toxposargs: --remote-data=astropy
- name: Python 3.8 with all optional dependencies (Windows)
os: windows-latest
python: 3.8
toxenv: py38-test-alldeps
toxposargs: --durations=50
- name: Python 3.7 with all optional dependencies (MacOS X)
os: macos-latest
python: 3.7
toxenv: py37-test-alldeps
toxposargs: --durations=50
- name: Python 3.7 doc build
os: ubuntu-latest
python: 3.7
toxenv: build_docs
steps:
- name: Checkout code
uses: actions/checkout@v2
with:
fetch-depth: 0
- name: Set up Python
uses: actions/setup-python@v2
with:
python-version: ${{ matrix.python }}
- name: Install language-pack-de and tzdata
if: startsWith(matrix.os, 'ubuntu')
run: |
sudo apt-get update
sudo apt-get install language-pack-de tzdata graphviz
- name: Install Python dependencies
run: python -m pip install --upgrade tox codecov
- name: Run tests
run: tox ${{ matrix.toxargs }} -e ${{ matrix.toxenv }} -- ${{ matrix.toxposargs }}
# TODO: Do we need --gcov-glob "*cextern*" ?
- name: Upload coverage to codecov
if: ${{ contains(matrix.toxenv,'-cov') }}
uses: codecov/codecov-action@v2
with:
file: ./coverage.xml
allowed_failures:
name: ${{ matrix.name }}
runs-on: ${{ matrix.os }}
strategy:
fail-fast: false
matrix:
include:
- name: (Allowed Failure) Python 3.8 with remote data and dev version of key dependencies
os: ubuntu-latest
python: 3.8
toxenv: py38-test-devdeps
toxposargs: --remote-data=any
steps:
- name: Checkout code
uses: actions/checkout@v2
with:
fetch-depth: 0
- name: Set up Python
uses: actions/setup-python@v2
with:
python-version: ${{ matrix.python }}
- name: Install language-pack-de and tzdata
if: startsWith(matrix.os, 'ubuntu')
run: |
sudo apt-get update
sudo apt-get install language-pack-de tzdata
- name: Install Python dependencies
run: python -m pip install --upgrade tox codecov
- name: Run tests
run: tox ${{ matrix.toxargs }} -e ${{ matrix.toxenv }} -- ${{ matrix.toxposargs }}
././@PaxHeader 0000000 0000000 0000000 00000000026 00000000000 011453 x ustar 00 0000000 0000000 22 mtime=1643302783.0
specutils-1.6.0/.gitignore 0000644 0005037 0002007 00000001427 00000000000 017600 0 ustar 00rosteen STSCI\science 0000000 0000000 # Compiled files
*.py[cod]
*.a
*.o
*.so
__pycache__
# Ignore .c files by default to avoid including generated code. If you want to
# add a non-generated .c extension, use `git add -f filename.c`.
*.c
# Other generated files
*/version.py
*/cython_version.py
htmlcov
.coverage
MANIFEST
.ipynb_checkpoints
# Sphinx
docs/api
docs/_build
# Eclipse editor project files
.project
.pydevproject
.settings
# Pycharm editor project files
.idea
# Floobits project files
.floo
.flooignore
# Visual Studio Code project files
.vscode
# Packages/installer info
*.egg
*.egg-info
dist
build
eggs
.eggs
parts
bin
var
sdist
develop-eggs
.installed.cfg
distribute-*.tar.gz
# Other
.cache
.tox
.*.sw[op]
*~
.project
.pydevproject
.settings
pip-wheel-metadata/
# Mac OSX
.DS_Store
.vscode
.pytest_cache
././@PaxHeader 0000000 0000000 0000000 00000000026 00000000000 011453 x ustar 00 0000000 0000000 22 mtime=1643302783.0
specutils-1.6.0/.readthedocs.yml 0000644 0005037 0002007 00000000303 00000000000 020666 0 ustar 00rosteen STSCI\science 0000000 0000000 version: 2
build:
image: latest
python:
version: 3.8
system_packages: false
install:
- method: pip
path: .
extra_requirements:
- docs
- all
formats: []
././@PaxHeader 0000000 0000000 0000000 00000000026 00000000000 011453 x ustar 00 0000000 0000000 22 mtime=1643302783.0
specutils-1.6.0/CHANGES.rst 0000644 0005037 0002007 00000030674 00000000000 017420 0 ustar 00rosteen STSCI\science 0000000 0000000 1.6.0 (2022-01-27)
------------------
New Features
^^^^^^^^^^^^
- Add collapse methods to Spectrum1D. [#904, #906]
- SpectralRegion and Spectrum1D now allow descending (in wavelength space) as
well as ascending spectral values. [#911]
1.5.0
-----
New Features
^^^^^^^^^^^^
- Convolution-based smoothing will now apply a 1D kernel to multi-dimensional fluxes
by convolving along the spectral axis only, rather than raising an error. [#885]
- ``template_comparison`` now handles ``astropy.nddata.Variance`` and
``astropy.nddata.InverseVariance`` uncertainties instead of assuming
the uncertainty is standard deviation. [#899]
Bug Fixes
^^^^^^^^^
- Speed up JWST s3d loader and reduce memory usage. [#874]
- ``SpectralRegion`` can now handle pixels. [#886]
- Fix bug where ``template_comparison`` would return the wrong chi2 value. [#872]
Other Changes and Additions
^^^^^^^^^^^^^^^^^^^^^^^^^^^
- ``fit_lines`` now makes use of unit support in ``astropy.modeling``. [#891]
- ``Spectrum1D.with_spectral_units`` now attempts to fall back on the ``spectral_axis``
units if units could not be retrieved from the WCS. [#892]
- ``ndcube`` package pin updated to released version (2.0). [#897]
- Minor changes for astropy 5.0 compatibility. [#895]
1.4.1
-----
Bug Fixes
^^^^^^^^^
- Fix JWST s3d loader. [#866]
1.4
---
New Features
^^^^^^^^^^^^
- Allow overriding existing astropy registry elements. [#861]
- ``Spectrum1D`` will now swap the spectral axis with the last axis on initialization
if it can be identified from the WCS and is not last, rather than erroring. [#654, #822]
Bug Fixes
^^^^^^^^^
- Change loader priorities so survey loaders always override generic ones. [#860]
- Handle "FLUX_ERROR" header keyword in addition to "ERROR" in JWST loader. [#856]
Other Changes and Additions
^^^^^^^^^^^^^^^^^^^^^^^^^^^
- ``Spectrum1D`` now subclasses ``NDCube`` instead of ``NDDataRef``. [#754, #822, #850]
1.3.1
-----
New Features
^^^^^^^^^^^^
- Add ``SpectrumList`` loader for set of JWST _x1d files. [#838]
Bug Fixes
^^^^^^^^^
- Handle new ``astropy.units.PhysicalType`` class added in astropy 4.3. [#833]
- Handle case of WCS with None values in ``world_axis_physical_types`` when
initializing Spectrum1D. [#839]
- Fix bug in apStar loader. [#839]
Other Changes and Additions
^^^^^^^^^^^^^^^^^^^^^^^^^^^
- Improve continuum flux calculation in ``equivalent_width``. [#843]
1.3
---
New Features
^^^^^^^^^^^^
- Added ability to slice ``Spectrum1D`` with spectral axis values. [#790]
- Added ability to replace a section of a spectrum with a spline or model fit. [#782]
Bug Fixes
^^^^^^^^^
- Fix infinite recursion when unpickling a ``QuantityModel``. [#823]
- Changed positional to keyword arguments in ``fit_continuum``. [#806]
Other Changes and Additions
^^^^^^^^^^^^^^^^^^^^^^^^^^^
- Fix inaccuracy about custom loading in docs. [#819]
- Use non-root logger to prevent duplicate messages. [#810]
- Removed unused astropy config code. [#805]
1.2
---
New Features
^^^^^^^^^^^^
- Add support for reading IRAF MULTISPEC format with non-linear 2D WCS into
``SpectrumCollection`` to default_loaders. [#708]
- ``SpectralRegion`` objects can now be created from the ``QTable``
object returned from the line finding rountines. [#759]
- Include new 6dFGS loaders. [#734]
- Include new OzDES loaders. [#764]
- Include new GAMA survey loaders. [#765]
- Include new GALAH loaders. [#766]
- Include new WiggleZ loaders. [#767]
- Include new 2dF/AAOmega loaders. [#768]
- Add loader to handle IRAF MULTISPEC non-linear 2D WCS. [#708]
- Add ability to extract minimum bounding regions of ``SpectralRegion`` objects. [#755]
- Implement new moment analysis function for specutils objects. [#758]
- Add new spectral slab extraction functionality. [#753]
- Include new loaders for AAT and other Australian surveys. [#719]
- Improve docstrings and intialization of ``SpectralRegion`` objects. [#770]
Bug Fixes
^^^^^^^^^
- Fix ``extract_region`` behavior and slicing for ``Spectrum1D`` objects
that have multi-dimensional flux arrays. Extracting a region that extends
beyond the limits of the data no longer drops the last data point in the
returned spectrum. [#724]
- Fixes to the jwst loaders. [#759]
- Fix handling of ``SpectralCollection`` objects in moment calculations. [#781]
- Fix issue with non-loadable x1d files. [#775]
- Fix WCS handling in SDSS loaders. [#738]
- Fix the property setters for radial velocity and redshift. [#722]
- Fix line test errors and include python 3.9 in tests. [#751]
- Fix smoothing functionality dropping spectrum meta information. [#732]
- Fix region extraction for ``Spectrum1D`` objects with multi-dimensional fluxes. [#724]
Documentation
^^^^^^^^^^^^^
- Update SDSS spectrum documentation examples. [#778]
- Include new documentation on working with ``SpectralCube`` objects. [#726, #784]
- Add documentation on spectral cube related functionality. [#783]
Other Changes and Additions
^^^^^^^^^^^^^^^^^^^^^^^^^^^
- Improved error messages when creating ``SpectralRegion`` objects. [#759]
- Update documentation favicons and ensure color consistency. [#780]
- Remove fallback ``SpectralCoord`` code and rely on upstream. [#786]
- Move remaining loaders to use utility functions for parsing files. [#718]
- Remove unnecessary data reshaping in tabular fits writer. [#730]
- Remove astropy helpers and CI helpers dependencies. [#562]
1.1
---
New Features
^^^^^^^^^^^^
- Added writer to ``wcs1d-fits`` and support for multi-D flux arrays with
1D WCS (identical ``spectral_axis`` scale). [#632]
- Implement ``SpectralCoord`` for ``SpectrumCollection`` objects. [#619]
- Default loaders work with fits file-like objects. [#637]
- Implement bin edge support on ``SpectralCoord`` objects using
``SpectralAxis`` subclass. [#645]
- Implement new 6dFGS loader. [#608]
- Implement uncertainty handling for ``line_flux``. [#669]
- Implement new 2SLAQ-LRG loader. [#633]
- Implement new 2dFGRS loader. [#695]
- Default loaders now include WCS 1D (with multi-dimensional flux handling) writer. [#632]
- Allow continuum fitting over multiple windows. [#698]
- Have NaN-masked inputs automatically update the ``mask`` appropriately. [#699]
Bug Fixes
^^^^^^^^^
- Fixed ``tabular-fits`` handling of 1D+2D spectra without WCS;
identification and parsing of metadata and units for ``apogee``
and ``muscles`` improved; enabled loading from file-like objects. [#573]
- Fix ASDF handling of ``SpectralCoord``. [#642]
- Preserve flux unit in ``resample1d`` for older versions of numpy. [#649]
- Fix setting the doppler values on ``SpectralCoord`` instances. [#657]
- Properly handle malformed distances in ``SkyCoord`` instances. [#663]
- Restrict spectral equivalencies to contexts where it is required. [#573]
- Fix ``from_center`` descending spectral axis handling. [#656]
- Fix factor of two error in ``from_center`` method of ``SpectralRegion`` object. [#710]
- Fix handling of multi-dimensional mask slicing. [#704]
- Fix identifier for JWST 1D loader. [#715]
Documentation
^^^^^^^^^^^^^
- Display supported loaders in specutils documentation. [#675]
- Clarify inter-relation of specutils objects in relevant docstrings. [#654]
Other Changes and Additions
^^^^^^^^^^^^^^^^^^^^^^^^^^^
- Remove pytest runtime dependency. [#603]
- Change implementation of ``.quantity`` to ``.view`` in ``SpectralCoord``. [#614]
- Ensure underlying references point to ``SpectralCoord`` object. [#640]
- Deprecate ``spectral_axis_unit`` property. [#618]
- Backport ``SpectralCoord`` from astropy core for versions <4.1. [#674]
- Improve SDSS loaders and improve handling of extensions. [#667]
- Remove spectral cube testing utilities. [#683]
- Change local specutils directory creation behavior. [#691]
- Ensure existing manipulation and analysis functions use ``mask`` attribute. [#670]
- Improve mask handling in analysis functions. [#701]
1.0
---
New Features
^^^^^^^^^^^^
- Implement ``SpectralCoord`` object. [#524]
- Implement cross-correlation for finding redshift/radial velocity. [#544]
- Improve FITS file identification in default_loaders. [#545]
- Support ``len()`` for ``SpectrumCollection`` objects. [#575]
- Improved 1D JWST loader and allow parsing into an ``SpectrumCollection`` object. [#579]
- Implemented 2D and 3D data loaders for JWST products. [#595]
- Include documentation on how to use dust_extinction in specutils. [#594]
- Include example of spectrum shifting in docs. [#600]
- Add new default excise_regions exciser function and improve subregion handling. [#609]
- Implement use of ``SpectralCoord`` in ``Spectrum1D`` objects. [#610]
Bug Fixes
^^^^^^^^^
- Fix stacking and unit treatment in ``SpectrumCollection.from_spectra``. [#578]
- Fix spectral axis unit retrieval. [#581]
- Fix bug in subspectrum fitting. [#586]
- Fix uncertainty to weight conversion to match astropy assumptions. [#594]
- Fix warnings and log messages from ASDF serialization tests. [#597]
Other Changes and Additions
^^^^^^^^^^^^^^^^^^^^^^^^^^^
- Remove spectral_resolution stub from Spectrum1D. [#606]
0.7
---
New Features
^^^^^^^^^^^^
- Make specutils compatible with Astropy 4.0 (breaking change). [#462]
- Remove all wcs adapter code and rely on APE14 implementation. [#462]
Bug Fixes
^^^^^^^^^
- Address ``MexicanHat1D`` name change in documentation. [#564]
0.6.1
-----
API Changes
^^^^^^^^^^^
- Resamplers now include ``extrapolation_treatment`` argument. [#537]
- Template fitting now returns an array of chi squared values for each template. [#551]
New Features
^^^^^^^^^^^^
- Masks now supported in fitting operations. [#519]
- Resamplers now support resamping beyond the edge of a spectrum using. [#537]
- New template fitting for redshift finding. [#527]
- New continuum checker to discern whether continuum is normalized or subtracted. [#538]
- Include documentation on how to achieve splicing using specutils. [#536]
- Include function to calculate masks based on S/N thresholding. [#509]
Bug Fixes
^^^^^^^^^
- Include new regions regression tests. [#345]
- Fix fitting documentation code block test. [#478]
- Fix Apogee loader to incorporate spectral axis keyword argument. [#560]
- Fix tabular fits writer and include new regression test. [#539]
- Fix dispersion attribute bug in ``Spectrum1D`` objects. [#530]
- Correctly label regression tests that require remote data. [#525]
Other Changes and Additions
^^^^^^^^^^^^^^^^^^^^^^^^^^^
- Switch to using ``gaussian_sigma_width`` for ``Gaussian1D`` fitting estimator. [#434]
- Update documentation side bar to include page listing. [#556]
- New documentation on ``spectrum_mixin``. [#532]
- Model names are now preserved in the ``fit_lines`` operation. [#526]
- Clearer error messages for incompatible units in line fitting. [#520]
- Include travis stages in test matrix. [#515]
0.6
---
New Features
^^^^^^^^^^^^
- New redshift and radial velocity storage on `Spectrum1D` object.
- Spectral template matching including resampling.
- Error propagation in convolution smoothing.
- Sub-pixel precision for fwhm calculations.
- New spectral resampling functions.
- New IRAF data loaders.
- New FWZI calculation.
Bug Fixes
^^^^^^^^^
- Stricter intiailizer for ``Spectrum1D``.
- Correct handling of weights in line fitting.
- Array size checking in `Spectrum1D` objects.
- Fix for continuum fitting on pixel-axis dispersions.
Other Changes and Additions
^^^^^^^^^^^^^^^^^^^^^^^^^^^
0.5.3
-----
Bug Fixes
^^^^^^^^^
- Fix comparison of FITSWCS objects in arithmetic operations.
- Fix example documentation when run in python interpreter.
0.5.2 (2019-02-06)
----------------
Bug Fixes
^^^^^^^^^
- Bugfixes for astropy helpers, pep8 syntax checking, and plotting in docs [#416,#417,#419]
- All automatically generated ``SpectrumList`` loaders now have identifiers. [#440]
- ``SpectralRange.from_center`` parameters corrected after change to SpectralRange interface. [#433]
Other Changes and Additions
^^^^^^^^^^^^^^^^^^^^^^^^^^^
- Improve explanation on creating spectrum continua. [#420]
- Wrap IO identifier functions to ensure they always return True or False and log any errors. [#404]
0.5.1 (2018-11-29)
------------------
Bug Fixes
^^^^^^^^^
- Fixed a bug in using spectral regions that have been inverted. [#403]
- Use the pytest-remotedata plugin to control tests that require access to remote data. [#401,#408]
0.5 (2018-11-21)
----------------
This was the first release of specutils executing the
[APE14](https://github.com/astropy/astropy-APEs/blob/main/APE14.rst)
plan (i.e. the "new" specutils) and therefore intended for broad use.
././@PaxHeader 0000000 0000000 0000000 00000000026 00000000000 011453 x ustar 00 0000000 0000000 22 mtime=1583343826.0
specutils-1.6.0/CITATION 0000644 0005037 0002007 00000000723 00000000000 016743 0 ustar 00rosteen STSCI\science 0000000 0000000 If you use Specutils for work/research presented in a publication (whether
directly, or as a dependency to another package), please cite the Zenodo DOI
for the appopriate version of Specutils. The versions (and their BibTeX
entries) can be found at:
https://doi.org/10.5281/zenodo.1421356
We also encourage the acknowledgement of Astropy, which is a dependency of
Specutils. See http://www.astropy.org/acknowledging.html for more on the
recommendations for this.
././@PaxHeader 0000000 0000000 0000000 00000000026 00000000000 011453 x ustar 00 0000000 0000000 22 mtime=1643302783.0
specutils-1.6.0/MANIFEST.in 0000644 0005037 0002007 00000000427 00000000000 017345 0 ustar 00rosteen STSCI\science 0000000 0000000 include README.rst
include CHANGES.rst
include setup.cfg
include pyproject.toml
recursive-include specutils *.pyx *.c *.pxd
recursive-include docs *
recursive-include licenses *
recursive-include scripts *
prune build
prune docs/_build
prune docs/api
global-exclude *.pyc *.o
././@PaxHeader 0000000 0000000 0000000 00000000033 00000000000 011451 x ustar 00 0000000 0000000 27 mtime=1643306919.748239
specutils-1.6.0/PKG-INFO 0000644 0005037 0002007 00000012024 00000000000 016700 0 ustar 00rosteen STSCI\science 0000000 0000000 Metadata-Version: 2.1
Name: specutils
Version: 1.6.0
Summary: Package for spectroscopic astronomical data
Home-page: https://specutils.readthedocs.io/
Author: Specutils Developers
Author-email: coordinators@astropy.org
License: BSD 3-Clause
Platform: UNKNOWN
Requires-Python: >=3.7
Description-Content-Type: text/x-rst
Provides-Extra: test
Provides-Extra: docs
License-File: licenses/LICENSE.rst
Specutils
=========
.. image:: https://github.com/astropy/specutils/workflows/CI/badge.svg
:target: https://github.com/astropy/specutils/actions
:alt: GitHub Actions CI Status
.. image:: https://readthedocs.org/projects/specutils/badge/?version=latest
:target: http://specutils.readthedocs.io/en/latest/?badge=latest
:alt: Documentation Status
.. image:: http://img.shields.io/badge/powered%20by-AstroPy-orange.svg?style=flat
:target: http://www.astropy.org/
Specutils is an `Astropy affiliated package `_
with the goal of providing a shared set of Python representations of
astronomical spectra and basic tools to operate on these spectra. The effort is
also meant to be a "hub", helping to unite the Python astronomical spectroscopy
community around shared effort, much as Astropy is meant to for the wider
astronomy Python ecosystem. This broader effort is outlined in the
`APE13 document `_.
Note that Specutils is not intended to meet all possible spectroscopic analysis or
reduction needs. While it provides some standard analysis functionality
(following the Python philosophy of "batteries included"), it is best thought
of as a "tool box" that provides pieces of functionality that can be used to
build a particular scientific workflow or higher-level analysis tool. To that
end, it is also meant to facilitate connecting together disparate reduction
pipelines and analysis tools through shared Python representations of
spectroscopic data.
Getting Started with Specutils
------------------------------
For details on installing and using Specutils, see the
`specutils documentation `_.
Note that Specutils now only supports Python 3. While some functionality may
continue to work on Python 2, it is not tested and support cannot be guaranteed
(due to the sunsetting of Python 2 support by the Python and Astropy development
teams).
License
-------
This project is Copyright (c) Specutils Developers and licensed under
the terms of the BSD 3-Clause license. This package is based upon
the `Astropy package template `_
which is licensed under the BSD 3-clause license. See the ``licenses`` folder for
more information.
Contributing
------------
We love contributions! specutils is open source,
built on open source, and we'd love to have you hang out in our community.
**Imposter syndrome disclaimer**: We want your help. No, really.
There may be a little voice inside your head that is telling you that you're not
ready to be an open source contributor; that your skills aren't nearly good
enough to contribute. What could you possibly offer a project like this one?
We assure you - the little voice in your head is wrong. If you can write code at
all, you can contribute code to open source. Contributing to open source
projects is a fantastic way to advance one's coding skills. Writing perfect code
isn't the measure of a good developer (that would disqualify all of us!); it's
trying to create something, making mistakes, and learning from those
mistakes. That's how we all improve, and we are happy to help others learn.
Being an open source contributor doesn't just mean writing code, either. You can
help out by writing documentation, tests, or even giving feedback about the
project (and yes - that includes giving feedback about the contribution
process). Some of these contributions may be the most valuable to the project as
a whole, because you're coming to the project with fresh eyes, so you can see
the errors and assumptions that seasoned contributors have glossed over.
Note: This disclaimer was originally written by
`Adrienne Lowe `_ for a
`PyCon talk `_, and was adapted by
specutils based on its use in the README file for the
`MetPy project `_.
If you locally cloned this repo before 22 Mar 2021
--------------------------------------------------
The primary branch for this repo has been transitioned from ``master`` to ``main``. If you have a local clone of this repository and want to keep your local branch in sync with this repo, you'll need to do the following in your local clone from your terminal::
git fetch --all --prune
# you can stop here if you don't use your local "master"/"main" branch
git branch -m master main
git branch -u origin/main main
If you are using a GUI to manage your repos you'll have to find the equivalent commands as it's different for different programs. Alternatively, you can just delete your local clone and re-clone!
././@PaxHeader 0000000 0000000 0000000 00000000026 00000000000 011453 x ustar 00 0000000 0000000 22 mtime=1643302783.0
specutils-1.6.0/README.rst 0000644 0005037 0002007 00000011205 00000000000 017272 0 ustar 00rosteen STSCI\science 0000000 0000000 Specutils
=========
.. image:: https://github.com/astropy/specutils/workflows/CI/badge.svg
:target: https://github.com/astropy/specutils/actions
:alt: GitHub Actions CI Status
.. image:: https://readthedocs.org/projects/specutils/badge/?version=latest
:target: http://specutils.readthedocs.io/en/latest/?badge=latest
:alt: Documentation Status
.. image:: http://img.shields.io/badge/powered%20by-AstroPy-orange.svg?style=flat
:target: http://www.astropy.org/
Specutils is an `Astropy affiliated package `_
with the goal of providing a shared set of Python representations of
astronomical spectra and basic tools to operate on these spectra. The effort is
also meant to be a "hub", helping to unite the Python astronomical spectroscopy
community around shared effort, much as Astropy is meant to for the wider
astronomy Python ecosystem. This broader effort is outlined in the
`APE13 document `_.
Note that Specutils is not intended to meet all possible spectroscopic analysis or
reduction needs. While it provides some standard analysis functionality
(following the Python philosophy of "batteries included"), it is best thought
of as a "tool box" that provides pieces of functionality that can be used to
build a particular scientific workflow or higher-level analysis tool. To that
end, it is also meant to facilitate connecting together disparate reduction
pipelines and analysis tools through shared Python representations of
spectroscopic data.
Getting Started with Specutils
------------------------------
For details on installing and using Specutils, see the
`specutils documentation `_.
Note that Specutils now only supports Python 3. While some functionality may
continue to work on Python 2, it is not tested and support cannot be guaranteed
(due to the sunsetting of Python 2 support by the Python and Astropy development
teams).
License
-------
This project is Copyright (c) Specutils Developers and licensed under
the terms of the BSD 3-Clause license. This package is based upon
the `Astropy package template `_
which is licensed under the BSD 3-clause license. See the ``licenses`` folder for
more information.
Contributing
------------
We love contributions! specutils is open source,
built on open source, and we'd love to have you hang out in our community.
**Imposter syndrome disclaimer**: We want your help. No, really.
There may be a little voice inside your head that is telling you that you're not
ready to be an open source contributor; that your skills aren't nearly good
enough to contribute. What could you possibly offer a project like this one?
We assure you - the little voice in your head is wrong. If you can write code at
all, you can contribute code to open source. Contributing to open source
projects is a fantastic way to advance one's coding skills. Writing perfect code
isn't the measure of a good developer (that would disqualify all of us!); it's
trying to create something, making mistakes, and learning from those
mistakes. That's how we all improve, and we are happy to help others learn.
Being an open source contributor doesn't just mean writing code, either. You can
help out by writing documentation, tests, or even giving feedback about the
project (and yes - that includes giving feedback about the contribution
process). Some of these contributions may be the most valuable to the project as
a whole, because you're coming to the project with fresh eyes, so you can see
the errors and assumptions that seasoned contributors have glossed over.
Note: This disclaimer was originally written by
`Adrienne Lowe `_ for a
`PyCon talk `_, and was adapted by
specutils based on its use in the README file for the
`MetPy project `_.
If you locally cloned this repo before 22 Mar 2021
--------------------------------------------------
The primary branch for this repo has been transitioned from ``master`` to ``main``. If you have a local clone of this repository and want to keep your local branch in sync with this repo, you'll need to do the following in your local clone from your terminal::
git fetch --all --prune
# you can stop here if you don't use your local "master"/"main" branch
git branch -m master main
git branch -u origin/main main
If you are using a GUI to manage your repos you'll have to find the equivalent commands as it's different for different programs. Alternatively, you can just delete your local clone and re-clone!
././@PaxHeader 0000000 0000000 0000000 00000000026 00000000000 011453 x ustar 00 0000000 0000000 22 mtime=1643302783.0
specutils-1.6.0/conftest.py 0000644 0005037 0002007 00000000471 00000000000 020005 0 ustar 00rosteen STSCI\science 0000000 0000000 from importlib.util import find_spec
import pkg_resources
entry_points = []
for entry_point in pkg_resources.iter_entry_points('pytest11'):
entry_points.append(entry_point.name)
if "asdf_schema_tester" not in entry_points and find_spec('asdf') is not None:
pytest_plugins = ['asdf.tests.schema_tester']
././@PaxHeader 0000000 0000000 0000000 00000000033 00000000000 011451 x ustar 00 0000000 0000000 27 mtime=1643306919.714216
specutils-1.6.0/docs/ 0000755 0005037 0002007 00000000000 00000000000 016534 5 ustar 00rosteen STSCI\science 0000000 0000000 ././@PaxHeader 0000000 0000000 0000000 00000000026 00000000000 011453 x ustar 00 0000000 0000000 22 mtime=1583343826.0
specutils-1.6.0/docs/Makefile 0000644 0005037 0002007 00000010745 00000000000 020203 0 ustar 00rosteen STSCI\science 0000000 0000000 # Makefile for Sphinx documentation
#
# You can set these variables from the command line.
SPHINXOPTS =
SPHINXBUILD = sphinx-build
PAPER =
BUILDDIR = _build
# Internal variables.
PAPEROPT_a4 = -D latex_paper_size=a4
PAPEROPT_letter = -D latex_paper_size=letter
ALLSPHINXOPTS = -d $(BUILDDIR)/doctrees $(PAPEROPT_$(PAPER)) $(SPHINXOPTS) .
.PHONY: help clean html dirhtml singlehtml pickle json htmlhelp qthelp devhelp epub latex latexpdf text man changes linkcheck doctest
#This is needed with git because git doesn't create a dir if it's empty
$(shell [ -d "_static" ] || mkdir -p _static)
help:
@echo "Please use \`make ' where is one of"
@echo " html to make standalone HTML files"
@echo " dirhtml to make HTML files named index.html in directories"
@echo " singlehtml to make a single large HTML file"
@echo " pickle to make pickle files"
@echo " json to make JSON files"
@echo " htmlhelp to make HTML files and a HTML help project"
@echo " qthelp to make HTML files and a qthelp project"
@echo " devhelp to make HTML files and a Devhelp project"
@echo " epub to make an epub"
@echo " latex to make LaTeX files, you can set PAPER=a4 or PAPER=letter"
@echo " latexpdf to make LaTeX files and run them through pdflatex"
@echo " text to make text files"
@echo " man to make manual pages"
@echo " changes to make an overview of all changed/added/deprecated items"
@echo " linkcheck to check all external links for integrity"
clean:
-rm -rf $(BUILDDIR)
-rm -rf api
-rm -rf generated
html:
$(SPHINXBUILD) -b html $(ALLSPHINXOPTS) $(BUILDDIR)/html
@echo
@echo "Build finished. The HTML pages are in $(BUILDDIR)/html."
dirhtml:
$(SPHINXBUILD) -b dirhtml $(ALLSPHINXOPTS) $(BUILDDIR)/dirhtml
@echo
@echo "Build finished. The HTML pages are in $(BUILDDIR)/dirhtml."
singlehtml:
$(SPHINXBUILD) -b singlehtml $(ALLSPHINXOPTS) $(BUILDDIR)/singlehtml
@echo
@echo "Build finished. The HTML page is in $(BUILDDIR)/singlehtml."
pickle:
$(SPHINXBUILD) -b pickle $(ALLSPHINXOPTS) $(BUILDDIR)/pickle
@echo
@echo "Build finished; now you can process the pickle files."
json:
$(SPHINXBUILD) -b json $(ALLSPHINXOPTS) $(BUILDDIR)/json
@echo
@echo "Build finished; now you can process the JSON files."
htmlhelp:
$(SPHINXBUILD) -b htmlhelp $(ALLSPHINXOPTS) $(BUILDDIR)/htmlhelp
@echo
@echo "Build finished; now you can run HTML Help Workshop with the" \
".hhp project file in $(BUILDDIR)/htmlhelp."
qthelp:
$(SPHINXBUILD) -b qthelp $(ALLSPHINXOPTS) $(BUILDDIR)/qthelp
@echo
@echo "Build finished; now you can run "qcollectiongenerator" with the" \
".qhcp project file in $(BUILDDIR)/qthelp, like this:"
@echo "# qcollectiongenerator $(BUILDDIR)/qthelp/Astropy.qhcp"
@echo "To view the help file:"
@echo "# assistant -collectionFile $(BUILDDIR)/qthelp/Astropy.qhc"
devhelp:
$(SPHINXBUILD) -b devhelp $(ALLSPHINXOPTS) $(BUILDDIR)/devhelp
@echo
@echo "Build finished."
@echo "To view the help file:"
@echo "# mkdir -p $$HOME/.local/share/devhelp/Astropy"
@echo "# ln -s $(BUILDDIR)/devhelp $$HOME/.local/share/devhelp/Astropy"
@echo "# devhelp"
epub:
$(SPHINXBUILD) -b epub $(ALLSPHINXOPTS) $(BUILDDIR)/epub
@echo
@echo "Build finished. The epub file is in $(BUILDDIR)/epub."
latex:
$(SPHINXBUILD) -b latex $(ALLSPHINXOPTS) $(BUILDDIR)/latex
@echo
@echo "Build finished; the LaTeX files are in $(BUILDDIR)/latex."
@echo "Run \`make' in that directory to run these through (pdf)latex" \
"(use \`make latexpdf' here to do that automatically)."
latexpdf:
$(SPHINXBUILD) -b latex $(ALLSPHINXOPTS) $(BUILDDIR)/latex
@echo "Running LaTeX files through pdflatex..."
make -C $(BUILDDIR)/latex all-pdf
@echo "pdflatex finished; the PDF files are in $(BUILDDIR)/latex."
text:
$(SPHINXBUILD) -b text $(ALLSPHINXOPTS) $(BUILDDIR)/text
@echo
@echo "Build finished. The text files are in $(BUILDDIR)/text."
man:
$(SPHINXBUILD) -b man $(ALLSPHINXOPTS) $(BUILDDIR)/man
@echo
@echo "Build finished. The manual pages are in $(BUILDDIR)/man."
changes:
$(SPHINXBUILD) -b changes $(ALLSPHINXOPTS) $(BUILDDIR)/changes
@echo
@echo "The overview file is in $(BUILDDIR)/changes."
linkcheck:
$(SPHINXBUILD) -b linkcheck $(ALLSPHINXOPTS) $(BUILDDIR)/linkcheck
@echo
@echo "Link check complete; look for any errors in the above output " \
"or in $(BUILDDIR)/linkcheck/output.txt."
doctest:
@echo "Run 'python setup.py test' in the root directory to run doctests " \
@echo "in the documentation."
././@PaxHeader 0000000 0000000 0000000 00000000034 00000000000 011452 x ustar 00 0000000 0000000 28 mtime=1643306919.7152724
specutils-1.6.0/docs/_static/ 0000755 0005037 0002007 00000000000 00000000000 020162 5 ustar 00rosteen STSCI\science 0000000 0000000 ././@PaxHeader 0000000 0000000 0000000 00000000026 00000000000 011453 x ustar 00 0000000 0000000 22 mtime=1643302783.0
specutils-1.6.0/docs/_static/logo.png 0000644 0005037 0002007 00000340677 00000000000 021651 0 ustar 00rosteen STSCI\science 0000000 0000000 PNG
IHDR cP sRGB pHYs .# .#x?v YiTXtXML:com.adobe.xmp
1
L'Y @ IDATx%Uu_uAը@O5"FofD̠F =GC_y̍~Po11ʌ
3ӧkծUk^8}yj{OwS' t@ mӭkǝ|`{W|Ѣpޠc;/O56- [cFAo}?7/z?gaz #=gx 8}ɳKǏfgsudᑴ4ewEyooדT(1Ǐ ^{6}oyN@ @ @ @ @ @ @ @ @{@` XwcƢv4|jFj{eAM|)i`S9%