DM-51841: Compute effective time from magnitude limit#1147
Open
DM-51841: Compute effective time from magnitude limit#1147
Conversation
f2e2d2b to
846d367
Compare
ehneilsen
approved these changes
Mar 16, 2026
Contributor
Author
|
Jenkins run 8435. |
846d367 to
6d1161a
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This ticket is for updating the effective time calculation to use the magnitude limit and fiducial magnitude limit in accordance with DMTN-296. The result will be a proper incorporation of the readout noise into the effective time, which will primarily change the effective time values for the u and g bands.