Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Spectrum1D #21

Closed
PAHdb opened this issue Nov 21, 2018 · 3 comments
Closed

Spectrum1D #21

PAHdb opened this issue Nov 21, 2018 · 3 comments

Comments

@PAHdb
Copy link
Owner

PAHdb commented Nov 21, 2018

Have a look at https://specutils.readthedocs.io/en/latest/ for possible using specutils from astropy.

@PAHdb
Copy link
Owner Author

PAHdb commented Dec 7, 2018

The specutils package is quite powerful and already makes use of Units, therefore also addressing #23. Replacing Spectrum with specutils.Spectrum1D has now been implemented.

@PAHdb PAHdb closed this as completed Dec 7, 2018
@PAHdb PAHdb mentioned this issue Dec 7, 2018
@PAHdb
Copy link
Owner Author

PAHdb commented Jan 19, 2019

I'm reopening this issue as it turns out that specutils can also readily handle reading/parsing/writing spectral data saved in FITS-files. When #24 is fixed, specutils is likely to parse our example FITS-files directly. In addition, it can use custom loaders to handle other formats (https://specutils.readthedocs.io/en/latest/custom_loading.html).

@PAHdb PAHdb reopened this Jan 19, 2019
@PAHdb
Copy link
Owner Author

PAHdb commented Feb 26, 2019

After some checking it turns out that specutils currently doesn't read our FITS-files. Furthermore, while we can write a custom loader, they need to sit in the ~/.specutils-directory; something we don't really want ... closing.

@PAHdb PAHdb closed this as completed Feb 26, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant