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
DM-34919: Remove gen2 support #402
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
How are ccdExposureIds handled in gen3? Those and detector names are the removals here, so I hope we're testing the modern interface for that somewhere?
instrument.makeDefaultRawIngestRunName(), | ||
instrument.makeCalibrationCollectionName()] | ||
cls._butler = lsst.daf.butler.Butler(cls.data_dir, collections=collections, | ||
instrument=instrument.getName()) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
All of the above is instrument agnostic, so it could go into obs_base:butler_tests.setup_*
, I think?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Only if the obs_base tests are dropping gen2 and we think any of these tests are worth keeping.
ccdExposureId is not anything to do with butler so the test is no longer relevant. detector names are all handled transparently by the detector dimension record in butler (which comes from the ObservationInfo) so there is no specialist parsing involved, unlike gen2. The tests asking for a dataset by raft and name_in_raft show that it works. |
The gen2 tests now all fail.
These are small enough that in the future we should consider creating them dynamically. This would prevent us hard-coding a camera geometry into the test but would require an explicit step for the calibration files to ingest them with a dataId and associate them with a validity range.
No description provided.