/usr/share/doc/gmt/html/man/x_update.html is in gmt-doc 4.5.11-1build1.
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 | <!-- Creator : groff version 1.19.2 -->
<!-- CreationDate: Tue Nov 5 09:45:54 2013 -->
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd">
<html>
<head>
<meta name="generator" content="groff -Thtml, see www.gnu.org">
<meta http-equiv="Content-Type" content="text/html; charset=US-ASCII">
<meta name="Content-Style" content="text/css">
<style type="text/css">
p { margin-top: 0; margin-bottom: 0; }
pre { margin-top: 0; margin-bottom: 0; }
table { margin-top: 0; margin-bottom: 0; }
</style>
<title>X_UPDATE</title>
</head>
<body bgcolor="#ffffff">
<h1 align=center>X_UPDATE</h1>
<a href="#NAME">NAME</a><br>
<a href="#SYNOPSIS">SYNOPSIS</a><br>
<a href="#DESCRIPTION">DESCRIPTION</a><br>
<a href="#BEWARE">BEWARE</a><br>
<a href="#SEE ALSO">SEE ALSO</a><br>
<a href="#REFERENCES">REFERENCES</a><br>
<hr>
<a name="NAME"></a>
<h2>NAME</h2>
<p style="margin-left:11%; margin-top: 1em"><b>x_update</b>
− Archiving of Cross-Over Information</p>
<a name="SYNOPSIS"></a>
<h2>SYNOPSIS</h2>
<p style="margin-left:11%; margin-top: 1em"><b>x_update</b>
<i>cross-overfile</i> [ <b>−X</b><i>xbase</i> ] [
<b>−L</b><i>legbase</i> ] [ <b>−V</b> ] [
<b>−W</b><i>max</i> ]</p>
<a name="DESCRIPTION"></a>
<h2>DESCRIPTION</h2>
<p style="margin-left:11%; margin-top: 1em"><b>x_update</b>
reads the ASCII file produced by <b><A HREF="x_over.html">x_over</A></b> and writes
the information to the database files <i>xx_base.b</i> and
<i>xx_legs.b</i> (unless other filenames are specified on
the command line) using a compact, binary format. The
options recognized are:</p>
<table width="100%" border=0 rules="none" frame="void"
cellspacing="0" cellpadding="0">
<tr valign="top" align="left">
<td width="11%"></td>
<td width="3%">
<p style="margin-top: 1em" valign="top"><b>−X</b></p> </td>
<td width="8%"></td>
<td width="78%">
<p style="margin-top: 1em" valign="top">Indicate alternate
<i>xx_base.b</i> file.</p></td>
<tr valign="top" align="left">
<td width="11%"></td>
<td width="3%">
<p style="margin-top: 1em" valign="top"><b>−L</b></p> </td>
<td width="8%"></td>
<td width="78%">
<p style="margin-top: 1em" valign="top">Indicate alternate
<i>xx_legs.b</i> file.</p></td>
<tr valign="top" align="left">
<td width="11%"></td>
<td width="3%">
<p style="margin-top: 1em" valign="top"><b>−V</b></p> </td>
<td width="8%"></td>
<td width="78%">
<p style="margin-top: 1em" valign="top">Selects verbose
mode, which will send progress reports to stderr [Default
runs "silently"]. Reports the pair currently being
processed.</p> </td>
<tr valign="top" align="left">
<td width="11%"></td>
<td width="3%">
<p style="margin-top: 1em" valign="top"><b>−W</b></p> </td>
<td width="8%"></td>
<td width="78%">
<p style="margin-top: 1em" valign="top">Prints a warning if
the number of COEs generated by any pair of legs exceed
<i>max</i>.</p> </td>
</table>
<a name="BEWARE"></a>
<h2>BEWARE</h2>
<p style="margin-left:11%; margin-top: 1em">For security
reasons the <i>xx_legs.b</i> are first renamed to
<i>xx_legs.b_old</i>, to prevent loss of information if a
black-out or system crash should occur during writing of the
new <i>xx_legs.b</i> file. It is recommended that the old
file is left on the disk in case of other disasters. Note
that <b>x_update</b> does not check if a pair of legs
already exist in the <i>xx_base.b</i> file. It is the
user’s responsibility to ensure that duplication of
information does not occur. Should some pairs already in the
database need to be re-examined, then run <b><A HREF="x_remove.html">x_remove</A></b>
which will wipe out all traces of the specified cruises from
the x_system data base files. Now we can pass the pairs that
need to be redone through <b>x_over/x_update</b> again.</p>
<a name="SEE ALSO"></a>
<h2>SEE ALSO</h2>
<p style="margin-left:11%; margin-top: 1em"><i><A HREF="GMT.html">GMT</A></i>(1),
<i><A HREF="x_system.html">x_system</A></i>(1)</p>
<a name="REFERENCES"></a>
<h2>REFERENCES</h2>
<p style="margin-left:11%; margin-top: 1em">Wessel, P.
XOVER: A Cross-over Error Detector for Track Data,
<i>Computers & Geosciences, 15</i>, 333-346.</p>
<hr>
</body>
</html>
|