Skip to content

DM-49364: Switch LATISS/bestEffortIsr to IsrTaskLSST#167

Open
mfisherlevine wants to merge 13 commits intomainfrom
tickets/DM-49364
Open

DM-49364: Switch LATISS/bestEffortIsr to IsrTaskLSST#167
mfisherlevine wants to merge 13 commits intomainfrom
tickets/DM-49364

Conversation

@mfisherlevine
Copy link
Contributor

No description provided.

Copy link

@czwa czwa left a comment

Choose a reason for hiding this comment

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

I'm not going to make the change request mandatory, but unless there's a compelling reason not to doApplyGains=True, I think that will improve things.

config.brighterFatterMaxIter = 2 # Uncomment this to remove test warning
config.doDeferredCharge = False # no calib for this yet
config.doBootstrap = False
config.doApplyGains = False
Copy link

Choose a reason for hiding this comment

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

Unless you expect to never have a PTC, I would strongly suggest this be set to doApplyGains=True. The new ISR defaults largely assume that everything has had gains applied so units are in electrons. We also should have CTI calibrations in the next set, but that correction is far less likely to have visual impact on the images than doApplyGains (which should help remove amp offsets).

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Oh, for sure - totally agreed! This is all ancient stuff that used to be necessary years ago, I'm up for any/all changes like that 👍.

mfisherlevine and others added 9 commits January 26, 2026 12:20
Replace detectObjectsInExp with direct detection using Threshold.VALUE
and np.std() to avoid STDEVCLIP returning 0 for some guider images.
Add starMaskThreshold parameter to exclude bright pixels when computing
background standard deviation.
Add a uniform [0, 1) random dither per stamp before computing the
median coadd. This breaks integer quantization that causes the pixel
distribution to be so narrow that STDEVCLIP returns 0 on some guider
images. Fix suggested by Robert Lupton. (DM-54263)
Replace the manual sigma68-only background estimation with STDEVCLIP
from lsst.afw.math, falling back to sigma68 if STDEVCLIP returns 0.
The dithered coadds (previous commit) prevent STDEVCLIP from failing,
but the fallback provides a safety net. Also adds a configurable
nPixMin parameter for footprint detection. (DM-54263)
Address review feedback from Merlin: use explicit assertion
instead of mypy ignore comment.

(DM-54263)
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.

3 participants