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

DM-35771: Remove gen2 #20

Merged
merged 15 commits into from Aug 4, 2022
Merged

DM-35771: Remove gen2 #20

merged 15 commits into from Aug 4, 2022

Conversation

timj
Copy link
Member

@timj timj commented Jul 29, 2022

No description provided.

@timj
Copy link
Member Author

timj commented Jul 29, 2022

@mfisherlevine I'm assuming that NightStellarSpectra is not used any where since it's entirely gen2 butler? Should I delete it or try to port it to gen3?

@timj
Copy link
Member Author

timj commented Jul 30, 2022

There is also the makeFakeFlats.py script that is using gen2. Should that be deleted or ported?

Does require that the extraction file is retrievable from
a butler. It no longer attempts to find a filename to read
explicitly.
python/lsst/atmospec/utils.py Outdated Show resolved Hide resolved
python/lsst/atmospec/nightAnalysis.py Outdated Show resolved Hide resolved
python/lsst/atmospec/nightAnalysis.py Show resolved Hide resolved
python/lsst/atmospec/nightAnalysis.py Outdated Show resolved Hide resolved
python/lsst/atmospec/nightAnalysis.py Show resolved Hide resolved
python/lsst/atmospec/nightAnalysis.py Outdated Show resolved Hide resolved
python/lsst/atmospec/nightAnalysis.py Outdated Show resolved Hide resolved
python/lsst/atmospec/nightAnalysis.py Outdated Show resolved Hide resolved
python/lsst/atmospec/nightAnalysis.py Outdated Show resolved Hide resolved
python/lsst/atmospec/nightAnalysis.py Outdated Show resolved Hide resolved
Does need daf_butler and does not need the library path env vars.
The metadata translator already knows how to deal with
different header variants for LATISS data.
Storing things that do match seems easier than storing things
that don't match and then having to filter them out the list
later.
This leaves the ordering up to the caller rather than
trying to decide whether the self.seqNums will always
be sorted.
Jim Bosch advises we be defensive and remove them just in
case queryDimensionRecords changes how it works in the future.
@timj timj merged commit 1335b44 into main Aug 4, 2022
@timj timj deleted the tickets/DM-35771 branch August 4, 2022 04:29
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

Successfully merging this pull request may close these issues.

None yet

2 participants