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-9004: Check uses of darktime for NAN #48

Merged
merged 2 commits into from Jan 16, 2017
Merged

Conversation

PaulPrice
Copy link
Contributor

No description provided.

It's not recorded in the header, so set it to the exposureTime.
Unfortunately, that's the best we can do. It needs to be set
explicitly, or it will be NAN.
Copy link
Contributor

@r-owen r-owen left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks fine.

@@ -192,7 +192,7 @@ def std_raw(self, item, dataId):

def std_dark(self, item, dataId):
exposure = self._standardizeExposure(self.calibrations['dark'], item, dataId, trimmed=False)
visitInfo = afwImage.makeVisitInfo(exposureTime=1.0)
visitInfo = afwImage.makeVisitInfo(exposureTime=1.0, darkTime=1.0)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This looks fine. However, I am curious why darks don't already have correct exposure time (at least), a question that is out of scope, but left over from when I first added VisitInfo support to obs_subaru.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The dark construction script has never set the dark time. I'll address that in DM-8913.

@PaulPrice PaulPrice merged commit 167c7ef into master Jan 16, 2017
@ktlim ktlim deleted the tickets/DM-9004 branch August 25, 2018 06:45
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