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
Only calculate the area of the aperture for valid pixels. This means that, if some pixels in the image are masked or out of the image, the real aperture area used by SEP is different than the calculated from the radius. This calculated area is also not exposed to user. Is there any way that this value can be exposed to user?
Problems: if we include area1 variable in the return of the sep.sum_* functions, we change the API, that is very bad.
Workaround: obtain the sum (without background extraction) of a image filled with ones.
The text was updated successfully, but these errors were encountered:
It would be possible to return the area without breaking the API by adding a keyword argument return_area defaulting to False. Similar to numpy.unique() and it's return_counts keyword argument, for example.
I think I didn't do this originally because I didn't think many people would really have a use for the area. (The flags do already tell you if all or no pixels were masked) More often I think people might want a "correct masked" option. Related issue about masked pixels: #60
This is a little suggestion to think, not a bug.
Only calculate the area of the aperture for valid pixels. This means that, if some pixels in the image are masked or out of the image, the real aperture area used by SEP is different than the calculated from the radius. This calculated area is also not exposed to user. Is there any way that this value can be exposed to user?
Problems: if we include
area1
variable in the return of thesep.sum_*
functions, we change the API, that is very bad.Workaround: obtain the sum (without background extraction) of a image filled with ones.
The text was updated successfully, but these errors were encountered: