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-39796: Update task config defaults to LSST values #350

Merged
merged 9 commits into from Sep 21, 2023
Merged

Conversation

parejkoj
Copy link
Contributor

No description provided.

@@ -33,7 +33,7 @@ class FindCosmicRaysConfig(pexConfig.Config):
nCrPixelMax = pexConfig.Field(
dtype=int,
doc="maximum number of contaminated pixels",
default=10000,
default=1000000,
Copy link
Contributor

Choose a reason for hiding this comment

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

Can you explain this change? I see that this is the obs_subaru value, and that obs_decam also used a higher value, so I can see the underlying logic in relation to this ticket, but this value must be too large. For LSSTCam, this amounts to 1 CR pixel per 4x4 grid. HSC and DECam have double the contaminated area. I can't imagine any image with that level of contamination being scientifically useful. I'll dig through the obs_subaru git history to find the reason for the high value, but I just want to raise this issue.

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 large value was also set in obs_lsst, at the root-level characterizeImage override, so it's the defacto default now anyway (modulo the small DECam difference). I'd love to have some rationale for why it is what it is, and whether to make it something better. The goal of this ticket is to just make overrides that are defacto defaults into actual defaults.

Copy link
Contributor

Choose a reason for hiding this comment

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

I've added https://jira.lsstcorp.org/browse/DM-40586 as sorting out the correct value is out of scope here.

python/lsst/meas/algorithms/objectSizeStarSelector.py Outdated Show resolved Hide resolved
python/lsst/meas/algorithms/objectSizeStarSelector.py Outdated Show resolved Hide resolved
@@ -123,6 +123,7 @@ def test_significance(self):

schema = afwTable.SourceTable.makeMinimalSchema()
config = SourceDetectionTask.ConfigClass()
config.thresholdType = "stdev"
Copy link
Contributor

Choose a reason for hiding this comment

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

Note why you are overriding this for the test.

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 docstring for the test itself explains why.

tests/test_objectSizeStarSelector.py Outdated Show resolved Hide resolved
This was the override for multiple instruments, and is the behavior we
generally want by default.
Cleanup unnecessary test override defaults
This is the instFlux field most often used in characterize/calibrate, across
multiple instruments.
This was the override for multiple instruments.
This was overriden in obs_lsst for calibrate and characterize, but we
almost certainly want it everywhere.
The tests were written with the original stdev default in mind.
This has not been slow since circa 2015 (see DM-1128 and DM-2787), and
is the default for multiple instruments.
Also fix the docstring and remove redundant optional kwarg.
These were the defaults for lsst, subaru, and decam.
This isn't always the psfFlux; it depends on the configured flux field.
@parejkoj parejkoj merged commit 728939a into main Sep 21, 2023
2 checks passed
@parejkoj parejkoj deleted the tickets/DM-39796 branch September 21, 2023 23:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
4 participants