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-19329: Add comCam support to obs_lsst #118
Conversation
Without this it is possible for a subclass to pick up the detector mappings from a parent translator.
python: lsst.daf.base.PropertyList | ||
storage: FitsStorage | ||
tables: raw | ||
template: raw/%(run)s/%(raftName)s/%(visit)08d-%(raftName)s-%(detectorName)s-det%(detector)03d-%(snap)03d.fits[0] |
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.
Do we still have the concept of run
s for ComCam? Maybe we do. I'm not even sure where this is supposed to support data from, so perhaps this is fine, but I think this was really only a TS8 and TS3 concept. If the data is there in the headers then it's fine though. If not, then here and throughout this file run
will need addressing.
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.
This is a generic obs_lsst gen2 question. lsstCam supports run so surely comCam should to. It gets set to "unknown". If we remove it we should have the broader discussion on lsstCam as well.
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.
I'm surprise it's needed on lsstCam as well, but if it is, then yes, I agree to leave it.
This reverts commit f487f44. The test data directory includes butler and fits files so we can not ignore all of them.
No butler gen 2 tests yet.