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-35784: Update default truth match configuration #84

Merged
merged 4 commits into from Oct 4, 2023
Merged

Conversation

taranu
Copy link
Contributor

@taranu taranu commented Sep 25, 2023

No description provided.

@@ -69,7 +69,7 @@ tasks:
python: |
from lsst.pipe.tasks.diff_matched_tract_catalog import MatchedCatalogFluxesConfig
columns_flux = {}
for band in 'ugrizy':
for band in ("u", "g", "r", "i", "z", "y"):
Copy link
Contributor

Choose a reason for hiding this comment

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

If this is preferable, do you want to do it at lines 23 & 24 above?

        config.astromRefObjLoader.filterMap = {band: 'lsst_%s_smeared' % (band) for band in 'ugrizy'};
        config.photoRefObjLoader.filterMap = {band: 'lsst_%s_smeared' % (band) for band in 'ugrizy'};

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Better yet, I think I'll put the filterMap in parameters now that those can be referenced in python blocks.

'flux_i', 'flux_z', 'flux_y',
bands_match = ("u", "g", "r", "i", "z", "y")
# Bands to match aperture fluxes on as a fallback if cModel failed
bands_fallback = ("r", "i")
Copy link
Contributor

Choose a reason for hiding this comment

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

Why r & i?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I didn't want to include every band because then the aperture fluxes would be weighted as much as the CModel fluxes for matching (there is no way to weight each column differently as of yet). It seems unlikely there are many good detections with only u/g aperture fluxes. I suppose there could be z-band dropouts but this was meant to fix a problem with brighter stars.

Copy link
Contributor

Choose a reason for hiding this comment

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

Got it...a comment in the file would be nice.

config.match_tract_catalog.columns_target_copy = ['objectId']
config.match_tract_catalog.columns_ref_copy = ["id", "truth_type"]
config.match_tract_catalog.columns_ref_select_true = ["is_unique_truth_entry"]
config.match_tract_catalog.columns_target_copy = ["objectId"]
Copy link
Contributor

Choose a reason for hiding this comment

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

This file has a full-on mix-n-match of single vs. double quotes. Instead of updating these here, perhaps a separate commit to homogenize all those in the task overrides would be warranted?

@taranu taranu merged commit e62833c into main Oct 4, 2023
3 checks passed
@taranu taranu deleted the tickets/DM-35784 branch October 4, 2023 14:08
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