/usr/share/doc/stilts/sun256/tcatn.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 | <html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<link rel="stylesheet" type="text/css" href="sun-style.css">
<title>tcatn: Concatenates multiple tables</title>
</head>
<body>
<hr>
<a href="tcatn-usage.html">Next</a> <a href="secB.24.2.html">Previous</a> <a href="cmdUsage.html">Up</a> <a href="index.html">Contents</a> <br> <b>Next: </b><a href="tcatn-usage.html">Usage</a><br>
<b>Up: </b><a href="cmdUsage.html">Command Reference</a><br>
<b>Previous: </b><a href="secB.24.2.html">Examples</a><br>
<hr>
<hr>
<h2><a name="tcatn">B.25 <code>tcatn</code>: Concatenates multiple tables</a></h2>
<p><code>tcatn</code> is a tool for concatenating a number of tables
one after the other. Each table can be manipulated separately
prior to the concatenatation.
If you have two tables T1 and T2 which contain similar columns, and you
want to treat them as a single table, you can use <code>tcatn</code>
to produce a new table whose metadata (row headings etc) comes from T1
and whose data consists of all the rows of T1 followed by all the rows of T2.
</p>
<p>For this concatenation to make sense, each column of T1 must be
compatible with the corresponding column of T2 - they must have
compatible types and, presumably, meanings.
If this is not the case for the tables that you wish to concatenate,
for instance the columns are in different orders, or the units
differ between a column in T1 and its opposite number in T2,
you can use the <code>icmd1</code> and/or <code>icmd2</code>
parameters to manipulate the input tables so that the
column sequences are compatible. See <a href="tcatn-examples.html">Appendix B.25.2</a> for
some examples.
</p>
<p>If the tables are similar to each other
(same format, same columns, same preprocessing stages required if any),
you may find it easier to use <code><a href="tcat.html">tcat</a></code> instead.
</p>
<ul>
<li><a href="tcatn-usage.html">B.25.1 Usage</a></li>
<li><a href="tcatn-examples.html">B.25.2 Examples</a></li>
</ul>
<hr><a href="tcatn-usage.html">Next</a> <a href="secB.24.2.html">Previous</a> <a href="cmdUsage.html">Up</a> <a href="index.html">Contents</a> <br> <b>Next: </b><a href="tcatn-usage.html">Usage</a><br>
<b>Up: </b><a href="cmdUsage.html">Command Reference</a><br>
<b>Previous: </b><a href="secB.24.2.html">Examples</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>
|