1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
|
Reference/API
=============
**Background estimation & source detection**
.. autosummary::
:toctree: api
sep.Background
sep.extract
**Aperture photometry**
.. autosummary::
:toctree: api
sep.sum_circle
sep.sum_circann
sep.sum_ellipse
sep.sum_ellipann
**Aperture utilities**
.. autosummary::
:toctree: api
sep.kron_radius
sep.flux_radius
sep.winpos
sep.mask_ellipse
sep.ellipse_axes
sep.ellipse_coeffs
**Low-level utilities**
.. autosummary::
:toctree: api
sep.get_extract_pixstack
sep.set_extract_pixstack
sep.get_sub_object_limit
sep.set_sub_object_limit
**Flags**
======================== ===========================================
Flag Description
======================== ===========================================
``sep.OBJ_MERGED`` object is result of deblending
``sep.OBJ_TRUNC`` object is truncated at image boundary
``sep.OBJ_SINGU`` x, y fully correlated in object
``sep.APER_TRUNC`` aperture truncated at image boundary
``sep.APER_HASMASKED`` aperture contains one or more masked pixels
``sep.APER_ALLMASKED`` aperture contains only masked pixels
``sep.APER_NONPOSITIVE`` aperture sum is negative in ``kron_radius``
======================== ===========================================
To see if a given flag is set in ``flags``::
is_merged = (flags & sep.OBJ_MERGED) != 0
.. note::
The coordinate convention in SEP is that (0, 0) corresponds to the
center of the first element of the data array. This agrees with the
0-based indexing in Python and C. However, note that
this differs from the FITS convention where the center of the first
element is at coordinates (1, 1). As Source Extractor deals with
FITS files, its outputs follow the FITS convention. Thus, the
coordinates from SEP will be offset from Source Extractor
coordinates by -1 in x and y.
|
