You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Dear colleagues,
Aperture magnitudes are calculated in circular apertures, whereas galaxies often appear elongated on the sky (due to the presence of a disk for the vast majority, which can be seen with various inclinations).
Being able to calculate apertude magnitudes in elliptical apertures, defined either by the isophotal elongation, or better, with a predefined elongation per source would be a significant plus.
Thanks a lot in advance for your opinion on such a feature.
Best regards
The text was updated successfully, but these errors were encountered:
Hi, I'm trying to evaluate the work that would be needed for this request and it's not entirely clear to me.
Currently we have the AutoPhotometry property that uses an elliptical aperture based on the shape property derived from the detection pixels.
The AperturePhotometry uses a list of circular (in the detection coordinates) apertures defined in the Python configuration. Those aperture radii are user defined, would the idea be to be able to define some as being semi-major axis instead and have the angle and elongation automatically derived from the shape property?
By predefined elongation do you mean having them come from the Assoc catalog? Angles and sizes as well? Maybe this could be a different property that allows that?
Dear colleagues,
Aperture magnitudes are calculated in circular apertures, whereas galaxies often appear elongated on the sky (due to the presence of a disk for the vast majority, which can be seen with various inclinations).
Being able to calculate apertude magnitudes in elliptical apertures, defined either by the isophotal elongation, or better, with a predefined elongation per source would be a significant plus.
Thanks a lot in advance for your opinion on such a feature.
Best regards
The text was updated successfully, but these errors were encountered: