search

spacetelescope / jwst

Python library for science observations from the James Webb Space Telescope
https://jwst-pipeline.readthedocs.io/en/latest/
Other
560 stars 167 forks source link

determine best parameters for setting is_extended flag in the image source catalog step #6020

Open stscijgbot-jp opened 3 years ago

stscijgbot-jp commented 3 years ago

Issue JP-2077 was created on JIRA by Anton Koekemoer:

The source catalog step determines whether or not sources are classified as extended (and indicates this by setting the "is_extended" boolean flag), using an algorithm that is based on concentration index values, derived from the ratios of fluxes in different sized apertures. The value of the "is_extended" flag is determined by whether an object falls inside or outside a region that is defined by thresholds for these concentration index values.

Since this algorithm is being applied to catalogs generated from images obtained with a variety of instruments and pixel sizes (NIRCam, NIRISS, MIRI) and filters covering a wide range of wavelengths (from 0.6 to 25 micron), it is expected that the specific concentration index threshold values may need to be different for various instrument/filter combinations, and will be read from a parameter reference file.

This ticket is aimed at tracking (/ facilitating) discussion in the Photometry WG (lead Matteo Correnti) for determining the best settings to use for the concentration index threshold values, initially based on simulations, and potentially updated once real in-flight data becomes available.

 

stscijgbot-jp commented 1 year ago

Comment by Alicia Canipe on JIRA:

Reassigning to Anton Koekemoer since it was previously assigned to Matteo Correnti 

stscijgbot-jp commented 10 months ago

Comment by Misty Cracraft on JIRA:

This is listed as a MIRI critical ticket (not assigned this by the MIRI team), and has not been touched in awhile. If this is truly critical, I would assume someone would be working on it (in a working group?) and there would be updates. Can we re-assess this issue and either move it along or downgrade it?

stscijgbot-jp commented 10 months ago

Comment by Anton Koekemoer on JIRA:

Thanks Misty, and yes the "critical" rating very likely came from some time ago before the more recent "Criticality" number rating scheme - so indeed if MIRI re-evaluates this, then please set values for both the "Impact" and "Urgency" numbers, and set the new "INS Team Criticality" to a different value, to reflect the MIRI team's new (/current) assessment of the priority of this. Thanks!

stscijgbot-jp commented 6 months ago

Comment by David Law on JIRA:

I don't see any development on this, and it is pending input on how to make this determination.  Setting to On Hold.