-
Notifications
You must be signed in to change notification settings - Fork 88
Loaders: spectrum cube importers #3748
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
base: main
Are you sure you want to change the base?
Conversation
5c8ccad to
95d1891
Compare
430ee60 to
aaed7f0
Compare
|
removed the |
|
this is now sending s2d files that used to go through fits to now go through specutils, losing the ability to select an extension. Any idea why? Seems this isn't causing a test failure though, so I can try to add a test that fails and enforces the previous/preferred behavior. |
This reverts commit bc26f3e.
* Use environment option `MEMORY_PROFILE=1` to run (caution, takes a very long time!)
030e785 to
fdf63b9
Compare
|
Memory report for loading in the Manga cube in In
in
Total: ~2000 MB |

Description
This pull request adds a "3D Spectrum" importer, partially updates cubeviz plugins to work within deconfigged (more follow-up work will be needed, but they don't prevent data from loading),
and temporarily redirects load_data through load to test what failures exist with current CI.To test locally - set
app.state.dev_loaders = True. Note that tests were run with that enabled and as of the last effort here, there were 20 remaining failures that will need to be addressed before removing the dev-flag.This PR will need to be rebased back to main once #3739 is merged.Note: this work brings up the question - do we want to keep flux, uncertainty, and mask as separate data-collection entries? This PR maintains the current behavior/support.... but should we deprecate this in favor of a single data collection entry? Or do we want to keep this behavior to allow multiple masks? Right now, how do you re-assemble the input spectrum from multiple DC cubes?
Change log entry
CHANGES.rst? If you want to avoid merge conflicts,list the proposed change log here for review and add to
CHANGES.rstbefore merge. If no, maintainershould add a
no-changelog-entry-neededlabel.Checklist for package maintainer(s)
This checklist is meant to remind the package maintainer(s) who will review this pull request of some common things to look for. This list is not exhaustive.
triviallabel.cache-download.ymlworkflow?