This file is indexed.

/usr/share/doc/munipack/man_cross.html is in munipack-doc 0.5.10-1.

This file is owned by root:root, with mode 0o644.

The actual contents of the file can be viewed below.

  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
 73
 74
 75
 76
 77
 78
 79
 80
 81
 82
 83
 84
 85
 86
 87
 88
 89
 90
 91
 92
 93
 94
 95
 96
 97
 98
 99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
<!DOCTYPE HTML>
<html lang="en">
<head>
<!-- meta -->
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<meta name="description" content="A general astronomical image processing software">
<meta name="author" content="Filip Hroch">
<link href="news_feed.xml" type="application/atom+xml" rel="alternate" title="Sitewide ATOM Feed" />
<link type="text/css" rel="stylesheet" href="munipack.css">
<link rel="shortcut icon" href="favicon.ico">
<title>Munipack ‒ Cross-Match</title>
</head>
<body>
<header>
<a href="munipack.html"><img src="title_logo.png" alt="Munipack's logo" class="head"></a>
<div class="headhead">
<div class="headtitle">
<a class="headtitle" href="munipack.html">Munipack</a>
<a class="headsubtitle" href="munipack.html">A general astronomical image processing software</a>
</div>
<ul class="menu">
  <li class="menu"><a href="docs.html" class="menu">Documents</a></li>
  <li class="menu"><a href="guide.html" class="menu">User guide</a></li>
</ul>
</div>
</header>

<h1>Cross-Match</h1>

<p class="abstract">
The cross-match is procedure which is looking for the equivalent objects 
in two tables. The equivalence is assigned on base of a metric 
(spherical distance). An index of equivalent rows of the tables is generated.
</p>

<h2>Command</h2>

<code>
munipack cross [..] file
</code>

<h2>Description</h2>
<p>
The cross-match is the procedure which searches tables
for the equivalent objects on base of minimal spherical
distance and optionally, on similar fluxes. Purpose of the
match is looking for the objects in different catalogues,
detected object on frame or two frames.
</p>

<p>
This utility cross-match implementation is follows the criteria
for successful match:
</p>
<ul>
<li>Spherical distance needs to be minimal and under a tolerance.</li>
<li>Optionally, relative calibrated fluxes needs to be similar. 
    (partially implemented)</li>
<li>Optionally, the mutual correspondence is one to one. (not implemented yet)</li>
</ul>

<p>
For the first criterion, one computes the distance along great circle 
of spherical coordinates
(<a href="http://en.wikipedia.org/wiki/Great-circle_distance">)
</a>
which must be equal under given tolerance.
The tolerance is a parameters and must be provided. The method looks plain,
but is very powerful and in sparse star fields works very well.
</p>

<p>
Visual double stars (stars are angular near) has rare occurrence
but can confuse the distance criterion, especially when theirs
coordinates are load down by statistical errors. In this case,
the comparison of fluxes can be helpful.
</p>

<!--
<p>
Passing of the previsous criretii, the twices (or groups) of
near and the same brightness stars can be. In this case one
row of one table can corresponds to more rows of other table.
We can check the situation and we can look for the most probable
candidates on base of ...
</p>
-->

<p>
The algorithm compares coordinates computed at the same epoch
(the same time) which can be differ from catalogue positions
by proper motion of the objects. The algorithm is used:
</p>
<ul>
<li>For known epoch (time), the coordinates are computed.</li>
<li>The epoch is determined from EPOCH parameter of the catalogue
    (FITS keyword), when is not provided, one is set to 2000.00 year.</li>
<li>When proper motions are not set, the coordinates are used directly.</li>
</ul>
<p>
The proper motion of stars is usually small and one is often omitted. 
But sometimes, one can be important for heavy crowded
star fields or fast stars.
</p>

<p>
This utility is just public interface to internal procedures for
cross-match. The same code is used internally for all catalogue to frame
matching.
</p>

<h2>Parameters</h2>

<dl>
<dt><samp>--tol</samp></dt><dd>tolerance of uncertainty of coordinates of objects
                               in degrees</dd>
<dt><samp>--ftol</samp></dt><dd>relative errors for flux ratios, default = 1</dd>
<dt><samp>--col-ra</samp></dt><dd>Right Ascension column in catalogue</dd>
<dt><samp>--col-dec</samp></dt><dd>Declination column in catalogue</dd>
<dt><samp>--col-pm-ra</samp></dt><dd>Proper motion in Right Ascension column in catalogue</dd>
<dt><samp>--col-pm-dec</samp></dt><dd>Proper motion in Declination column in catalogue</dd>
<dt><samp>--col-mag</samp></dt><dd>Magnitude-like column in catalogue</dd>
</dl>

<p>
The parameter <samp>--tol</samp> is default set to machine precision 
(which will be not too useful). Therefore the parameter is practically mandatory.
</p>

<p>
The parameters <samp>--col-ra,--col-dec</samp> are mandatory. When any from
<samp>--col-pm-ra,--col-pm-dec,--col-pm-mag</samp> missing, the corresponding
criterion is not used. 
</p>

<p>
See <a href="man_com.html">Common options</a> for 
input/output file names.
</p>


<h2>Data Format</h2>

<p>
Results of cross-matching are stored in a FITS table with two
columns only. Every column represents the index of object in 
corresponding file. In the first column, indexes of second
files are stored. In second column, the indexes of first objects
are stored. Zero value means no correspondence has been found.
Number of rows is maximum of both tables.
</p>

<p>
Keywords FILE1,FILE2 in FITS header points to filenames of input tables.
</p>


<h2>Examples</h2>

<p>
Lets have already calibrated frame <samp>T_Phe_000003.fits</samp>
and we are doing cross-match with a catalogue:
</p>
<pre>
$ munipack cross --tol 5e-4 --col-ra RA,RAJ2000 --col-dec DEC,DEJ2000 \
       T_Phe_000003.fits cone.fits
</pre>

<h2>See Also</h2>
<p><a href="man_com.html">Common options</a></p>

<footer>
<div style="float:left; margin-left:2em;">
Copyright &copy; 1997 – 2018
Filip Hroch (<a style="text-decoration: none" href="mailto:hroch@physics.muni.cz?Subject=Munipack" title="Author's Email"></a>), license <a href="http://www.gnu.org/licenses/gpl.html">GPLv3</a>.
</div>
<div style="float:right; margin-right:2em; margin-top:-0.2em;">
<a href="http://monteboo.blogspot.com/search/label/Munipack" title="Munipack on MonteBoo Blog"><img src="favicon-blogger.png" alt="Blogger"></a>
<a href="http://www.muni.cz/?lang=en" title="Masaryk University in Brno, Czech Republic"><img src="mu-logo.png" alt="Masaryk University"></a>
<a href="news_feed.xml" title="Munipack's Releases in Atom Syndication Format"><img src="Feed-icon.png" alt="Atom Feed"></a>
</div>
</footer>
</body>
</html>