-
Notifications
You must be signed in to change notification settings - Fork 12
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
Implementation of multi_image_photometry()
code in photometry.py
#145
Implementation of multi_image_photometry()
code in photometry.py
#145
Conversation
…ctions to end of file and adding definition of multi_image_photometry.
…S solution BEFORE filtering sources. Disabled nan for saturated pixels as it crashes fwhm fit.
…nstead of just rolling original, allows for more realistic situation.
…age_photometry().
…ntion is to stop all program execution.
… messages are sufficient.
…s for `multi_image_photometry()`
…() to avoid wasting time.
… letter file extension limit).
I think using the |
…oid Windows test failures.
Just submitted a commit to add the |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There are a couple of minor changes inline.
More broadly, I've opened issues for:
- Figuring out how to better handle messages. We need some way to opt out of (or opt into) t verbose messaging. We might want to implement it using python logging. Logging in the photometry functions #148
- Simplifying the function signatures. Function signatures for photometry functions #149
- Seeing if we can simplify the test image classes a bit. Not a real high priority.
CHANGES.rst
Outdated
+ Creation of new data classes for handling aperture, photometry, and catalog data in a more consistent way by enforcing validation and certain column names. [#125] | ||
+ Development of new data classes for handling source list, photometry, and catalog data which include data format validation. [#125] | ||
+ Aperture photometry streamlined into single_image_photometry() and multi_image_photometry() functions that use the new data classes. [#141] | ||
+ multi_image_photometry() now is a wrapper for single_image_photometry() instead of a completely separate function. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you add the PR number to this?
+ multi_image_photometry() now is a wrapper for single_image_photometry() instead of a completely separate function. | |
+ ``multi_image_photometry`` now is a wrapper for ``single_image_photometry`` instead of a completely separate function. |
All issues addressed. |
So this is the next big update, I wrote a function
multi_image_photometry()
that is essentially a wrapper ofsingle_image_photometry()
. This will replacephotometry_on_directory()
.Some changes of note since the last PR:
single_image_photometry()
toNone, None
if it fails but it's OK to proceed to the next time. Exceptions are now only used when we really need to stop execution.compute_fwhm()
and just return a summary of the number of failed fits to the screen.compute_fwhm()
(really the 2D Gaussian fitter it calls) to handle NaN, which allows us to use NaN for high pixels. (Fixing issuecompute_fwhm()
throws exception on images with NaN #142)When run on a file in a directory, the output looks something like:
I am hoping this is much cleaner and easier to follow without all the warning messages.