public documents.sextractor_doc

[/] [crossid.tex] - Blame information for rev 29

Go to most recent revision | Details | Compare with Previous | View Log

Line No. Rev Author Line
1 19 gam
\chapter{Cross-identification within {\sc SExtractor}}
2 29 bertin
{\sc SExtractor} allows one to perform on-the-fly \index{cross-identification} cross-identification of
3
detections with an {\tt ASCII} list provided by the user. \index{cross-identification} cross-identification
4
can be done both in pixel and world coordinates. Configuration parameters related
5
to \index{cross-identification} cross-identification are prefixed with {\tt ASSOC}.
6 19 gam
 
7
\section{The {\tt ASSOC} list}
8
The {\tt ASSOC} process is initiated by requesting in the parameter
9
file at least one of the {\tt ASSOC} catalogue parameters: {\tt
10
VECTOR\_ASSOC} and {\tt NUMBER\_ASSOC}. Then {\sc SExtractor} looks
11
for an {\tt ASCII} file (let's call it the {\tt ASSOC} list) whose
12
file name has to be specified by the {\tt ASSOC\_NAME} configuration
13
keyword. The {\tt ASSOC} list must contain columns of numbers
14
separated by spaces or tabs. Each line describes a source that will
15 25 gam
enter the \index{cross-identification} cross-identification process. Lines with zero characters, or
16
beginning with ``{\tt \#}'' (for comments) are ignored. This \index{mean} means you
17 19 gam
may use any {\tt ASCII} catalogue generated by a previous {\sc
18
SExtractor} run as an {\tt ASSOC} list.
19
 
20 25 gam
To perform the \index{cross-identification} cross-identification, {\sc SExtractor} needs to know
21 19 gam
which are the columns that contain the $x$ and $y$
22
coordinates\footnote{The $x$ and $y$ coordinates must comply with the
23
FITS (and {\sc SExtractor}) convention: by definition, the center of
24 25 gam
the first pixel in the \index{image} image array has pixel-coordinates (1.0,1.0).}
25 19 gam
in the {\tt ASSOC} list. These shall be specified using the {\tt
26 25 gam
ASSOC\_PARAMS} configuration parameter. The \index{syntax} syntax is: ``{\tt
27 19 gam
ASSOC\_PARAMS}~$c_x$,$c_y[$,$c_Z]$'', where $c_x$ and $c_y$ are the
28
positions of the columns containing the $x$ and $y$ coordinates (the
29
first column has position 1). $c_Z$ (optional) specifies an extra
30
column containing some ``$Z$'' parameter that may be used for
31
controlling or weighting the {\tt ASSOC} process. $Z$ will typically
32
be a flux estimate. $c_Z$ is required if {\tt ASSOC\_TYPE} is {\tt
33
MIN}, {\tt MAX}, {\tt MEAN} or {\tt MAG\_MEAN} (see \S\ref{assoc} below).
34
 
35
\section{Controlling the {\tt ASSOC} process}
36
\label{assoc}
37
Two configuration parameters control the {\tt ASSOC} process. The
38
first one, {\tt ASSOC\_RADIUS}, accepts a decimal number which
39
represents the maximum distance (in pixels) one should have between
40 25 gam
the \index{barycenter} barycenter \gam{{\tt X}, {\tt Y} or {\tt XWIN}, {\tt YWIN}?}
41 19 gam
of the current {\sc SExtractor} detection and an {\tt
42
ASSOC}-list member to consider a match. This number must of course
43
account for positional uncertainties in both catalogues. In most cases,
44
a value of a few pixels will do just fine. The second configuration
45
parameter, {\tt ASSOC\_TYPE}, accepts a keyword as argument and
46
selects the kind of identification procedure one wants to operate:
47
\begin{itemize}
48
\item {\tt FIRST}: this is the simplest way of performing a
49 25 gam
\index{cross-identification} cross-identification. It does not require the $c_Z$ column in {\tt
50 19 gam
ASSOC\_PARAMS}. The first geometrical match encountered while scanning
51
the {\tt ASSOC} list is retained as the actual match. This can used
52
for catalogues with low spatial density.
53
\item {\tt NEAREST}: this option does not require the $c_Z$ column in
54
{\tt ASSOC\_PARAMS}. The match is performed with the {\tt ASSOC}-list
55
member the closest (in position) to the current detection, provided
56
that it lies within the {\tt ASSOC\_RADIUS}.
57
\item {\tt SUM}: all parameters issued from {\tt ASSOC}-list members
58
which geometrically match the current detection are summed. $c_Z$ is
59
not required.
60
\item {\tt MAG\_SUM}: all parameters $c_i$ issued from {\tt
61
ASSOC}-list members which geometrically match the current detection
62
are combined using the following law: $-2.5\log(\sum_i 10^{-0.4c_i})$.
63
This option allows one to sum flux contributions from magnitude data.
64
$c_Z$ is not required.
65
\item {\tt MIN}: among all geometrical matches, retains the {\tt
66
ASSOC}-list member which has the smallest $Z$ parameter.
67
\item {\tt MAX}: among all geometrical matches, retains the {\tt
68
ASSOC}-list member which has the largest $Z$ parameter.
69
\item {\tt MEAN}: all parameters issued from {\tt ASSOC}-list members
70
which geometrically match the current detection are weighted-averaged,
71
using the $Z$ parameter as the weight.
72
\item {\tt MAG\_MEAN}: all parameters issued from {\tt ASSOC}-list
73
members which geometrically match the current detection are
74
weighted-averaged, using $10^{-0.4Z}$ as the weight. This option is
75
useful for weighting catalogue sources with magnitudes.
76
\end{itemize}
77
 
78
\section{Output from {\tt ASSOC}}
79 25 gam
Now that we have described the \index{cross-identification} cross-identification process, let's see
80 19 gam
how informations coming from the matching with the {\tt ASSOC} list
81
are propagated to the output {\sc SExtractor} catalogue.
82
 
83
The output of {\tt ASSOC} data in {\sc SExtractor} catalogue is done
84
through the {\tt VECTOR\_ASSOC()} catalogue parameter. {\tt
85
VECTOR\_ASSOC()} is a vector, each element of which refers to a column
86
from the input {\tt ASSOC} list. {\tt VECTOR\_ASSOC()} contains either
87
{\tt ASSOC}-list member data from the best match (if {\tt ASSOC\_TYPE}
88
is {\tt FIRST}, {\tt NEAREST}, {\tt MIN} or {\tt MAX}), or a
89
combination of {\tt ASSOC}-list member data (if {\tt ASSOC\_TYPE} is
90
{\tt MEAN}, {\tt MAG\_MEAN}, {\tt SUM} or {\tt MAG\_SUM}). If no match
91
has been found, it just contains zeros. The {\tt NUMBER\_ASSOC}
92
contains the number of {\tt ASSOC}-list members that geometrically
93
match the current {\sc SExtractor} detection, and obviously, if
94
different from zero, indicates that {\tt VECTOR\_ASSOC()} has a
95 25 gam
\index{mean} meaningful content.
96 19 gam
 
97
The {\tt ASSOC\_DATA} configuration parameter is used to tell {\sc
98
SExtractor} to which column refers each element of {\tt
99 25 gam
VECTOR\_ASSOC()}. The \index{syntax} syntax of {\tt ASSOC\_DATA} is similar to that
100 19 gam
of {\tt ASSOC\_PARAMS}: ``{\tt ASSOC\_DATA} $c_1$,$c_2$,$c_3$,...''
101
where the $c_i$ are the column positions in the {\tt ASSOC} list. The
102
special case ``{\tt ASSOC\_DATA} 0'' tells {\sc SExtractor} to
103
propagate all columns from the {\tt ASSOC} file to the output catalogue.
104
 
105
There are situations where it might be desirable to keep in the output
106
{\sc SExtractor} catalogue only those detections that were matched with
107
some {\tt ASSOC}-list member. Such a feature is controlled by the {\tt
108
ASSOCSELEC\_TYPE} configuration parameter, which accepts one of the
109
three following keywords:
110
\begin{itemize}
111
\item {\tt ALL}: keep all {\sc SExtractor} detections, regardless of
112
matching. This is the default.
113
\item {\tt MATCHED}: keep only {\sc SExtractor} detections that were
114
matched with at least one {\tt ASSOC}-list member.
115
\item {\tt -MATCHED}: keep only {\sc SExtractor} detections that were
116
not matched with any {\tt ASSOC}-list member.
117
\end{itemize}
118