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.

Sign up for GitHub

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

Jump to bottom

Reduce dependencies on DESI software stack when using prospect with other data sets #47

Closed
weaverba137 opened this issue Aug 24, 2020 · 1 comment
Closed

Reduce dependencies on DESI software stack when using prospect with other data sets #47

weaverba137 opened this issue Aug 24, 2020 · 1 comment
Assignees
@weaverba137
Labels
enhancement New feature or request

Comments

@weaverba137
Copy link
Member

To make prospect more flexible in supporting data sets such as SDSS (e.g. #43 ), it may help with uptake if DESI software dependencies are optional. For example, specutils.py imports from desiutil and desispec, while plotspecutils.py imports from desitarget. Consider refactoring these modules so that these imports are optional. In particular it should be easy to drop the depenedency on desitarget, since DESI bitmasks are irrelevant to SDSS data.
@weaverba137 weaverba137 added the enhancement New feature or request label Aug 24, 2020
@weaverba137 weaverba137 self-assigned this Aug 24, 2020
@armengau armengau mentioned this issue Aug 28, 2020
Closed
@weaverba137
Copy link
Member Author

Closed by #50.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@weaverba137 weaverba137

Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@weaverba137