/usr/share/doc/stilts/sun256/CombinedMatchEngine.html is in stilts-doc 3.1.2-2.
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 | <html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<link rel="stylesheet" type="text/css" href="sun-style.css">
<title>Matcher Combinations</title>
</head>
<body>
<hr>
<a href="matchGroup.html">Next</a> <a href="sec7.1.11.html">Previous</a> <a href="MatchEngine.html">Up</a> <a href="index.html">Contents</a> <br> <b>Next: </b><a href="matchGroup.html">Multi-Object Matches</a><br>
<b>Up: </b><a href="MatchEngine.html">Match Criteria</a><br>
<b>Previous: </b><a href="sec7.1.11.html">Custom Matchers</a><br>
<hr>
<h4><a name="CombinedMatchEngine">7.1.12 Matcher Combinations</a></h4>
<p>In addition to the matching criteria listed in the previous subsections,
you can build your own by combining any of these.
To do this, take the two (or more)
matchers that you want to use, and separate their names with a
"<code>+</code>" character. The <code>values*</code> parameters
of the combined matcher should then hold the concatenation of the
<code>values*</code> entries of the constituent matchers, and the
same for the <code>params</code> parameter.
</p>
<p>So for instance the matcher "<code>sky+1d</code>" could be used
with the following syntax:
<pre>matcher=sky+1d values*='<ra/degrees> <dec/degrees> <x>'
params='<max-error/arcsec> <error>'
tuning='<healpix-k> <bin-factor>'</pre>
<blockquote>
<dl>
<dt><strong><code>values*</code>:</strong></dt>
<dd>
<ul>
<li><code>ra/degrees</code>: Right Ascension
</li>
<li><code>dec/degrees</code>: Declination
</li>
<li><code>x</code>: Cartesian co-ordinate #1
</li>
</ul>
</dd>
<dt><strong><code>params</code>:</strong></dt>
<dd>
<ul>
<li><code>max-error/arcsec</code>: Maximum separation along a great circle
</li>
<li><code>error</code>: Maximum Cartesian separation for match
</li>
</ul>
</dd>
<dt><strong><code>tuning</code>:</strong></dt>
<dd>
<ul>
<li><code>healpix-k</code>: Controls sky pixel size. Legal range 0 - 20. 0 is 60deg, 20 is 0.2".
</li>
<li><code>bin-factor</code>: Scaling factor to adjust bin size; larger values mean larger bins
</li>
</ul>
</dd>
</dl>
</blockquote>
This would compare positions on the sky with an additional scalar constraint.
Rows are considered to match if <em>both</em>
their <code>ra</code>, <code>dec</code> positions are within
<code>max-error</code> arcseconds of each other along a great circle
(as for <code>matcher=sky</code>)
<em>and</em>
their <code>x</code> values differ by no more than <code>error</code>
(as for <code>matcher=1d</code>).
</p>
<p>This example might be used for instance to identify objects from two
catalogues which are within a couple of arcseconds and also 0.5
blue magnitudes of each other.
Rolling your own matchers in this way can give you quite flexible match
constraints.
</p>
<p>When identifying the closest match
(e.g. <code>find=best1</code> in <code>tmatch2</code>)
the "distance" measure is obtained by
scaling the distances from each of the constituent matchers
and adding these scaled distances in quadrature,
so that each element of the matcher has approximately equal weight.
Scaling is generally done using the maximum permissible match
radius (or equivalent), so the distance measure looks something like
<i>d = sqrt([d<sub>A</sub>/max(d<sub>A</sub>)]<sup>2</sup>
+ [d<sub>B</sub>/max(d<sub>B</sub>)]<sup>2</sup>)</i>.
However the details are a bit dependent on which matchers you are combining.
</p>
<p><em>Note that in STILTS v3.0-9 and earlier,
a linear unscaled distance measure was used here instead,
which did not give very meaningful Best match results.</em>
</p>
<hr><a href="matchGroup.html">Next</a> <a href="sec7.1.11.html">Previous</a> <a href="MatchEngine.html">Up</a> <a href="index.html">Contents</a> <br> <b>Next: </b><a href="matchGroup.html">Multi-Object Matches</a><br>
<b>Up: </b><a href="MatchEngine.html">Match Criteria</a><br>
<b>Previous: </b><a href="sec7.1.11.html">Custom Matchers</a><br>
<hr><i>STILTS - Starlink Tables Infrastructure Library Tool Set<br>Starlink User Note256<br>STILTS web page:
<a href="http://www.starlink.ac.uk/stilts/">http://www.starlink.ac.uk/stilts/</a><br>Author email:
<a href="mailto:m.b.taylor@bristol.ac.uk">m.b.taylor@bristol.ac.uk</a><br>Mailing list:
<a href="mailto:topcat-user@jiscmail.ac.uk">topcat-user@jiscmail.ac.uk</a><br></i></body>
</html>
|