[7bb8184] | 1 | <refmeta> |
---|
| 2 | <refentrytitle>cavern</refentrytitle> |
---|
| 3 | <manvolnum>1</manvolnum> |
---|
| 4 | </refmeta> |
---|
| 5 | |
---|
| 6 | <refnamediv> |
---|
| 7 | <refname>cavern</refname> |
---|
| 8 | <refpurpose>process raw survey data |
---|
| 9 | </refpurpose> |
---|
| 10 | </refnamediv> |
---|
| 11 | |
---|
| 12 | <refsynopsisdiv> |
---|
| 13 | <cmdsynopsis> |
---|
| 14 | <command>cavern</command> |
---|
| 15 | <arg choice="opt">options</arg> |
---|
| 16 | <arg choice="req" rep="repeat">survex data file</arg> <!--FIXME--> |
---|
| 17 | </cmdsynopsis> |
---|
| 18 | </refsynopsisdiv> |
---|
| 19 | |
---|
| 20 | <refsect1><title>Description</title> |
---|
| 21 | |
---|
| 22 | <Para>Cavern is the &survexsuite; data processing engine.</Para> |
---|
| 23 | |
---|
| 24 | <Para>If multiple survey data files are listed on the command line, |
---|
| 25 | they are processed in order from left to right. Settings are reset to |
---|
| 26 | their defaults before processing each file. |
---|
| 27 | </Para> |
---|
| 28 | |
---|
| 29 | </refsect1> |
---|
| 30 | |
---|
| 31 | <refsect1><Title>Options</Title> |
---|
| 32 | |
---|
| 33 | <VariableList> |
---|
| 34 | <VarListEntry> |
---|
| 35 | <Term>-p, --percentage</Term> |
---|
| 36 | <ListItem> |
---|
| 37 | <Para>You can get cavern to display the percentage progress through the |
---|
| 38 | current file. As of &survexsuite; 0.90 this is disabled by default, but you |
---|
| 39 | can enable it if you want. Because the value given is for the |
---|
| 40 | <emphasis/current/ file, the values jump around for a multi-file survey |
---|
| 41 | project. Also note that displaying this information slows down processing |
---|
| 42 | a little. |
---|
| 43 | <!-- FIXME: on a slow machine you'd probably rather it ran faster, and on a |
---|
| 44 | fast machine you can't follow the change percentages.--> |
---|
| 45 | </Para> |
---|
| 46 | </ListItem> |
---|
| 47 | </VarListEntry> |
---|
| 48 | |
---|
| 49 | <VarListEntry> |
---|
| 50 | <Term>-o, --output=OUTPUT</Term> |
---|
| 51 | <ListItem> |
---|
| 52 | <Para>Sets location for output files. |
---|
| 53 | <!--FIXME elaborate this and other option descriptions.--> |
---|
| 54 | </Para> |
---|
| 55 | </ListItem> |
---|
| 56 | </VarListEntry> |
---|
| 57 | |
---|
| 58 | <VarListEntry> |
---|
| 59 | <Term>-q, --quiet</Term> |
---|
| 60 | <ListItem> |
---|
| 61 | <Para>Only show a brief summary (--quiet --quiet or -qq will display |
---|
| 62 | warnings and errors only). |
---|
| 63 | </Para> |
---|
| 64 | </ListItem> |
---|
| 65 | </VarListEntry> |
---|
| 66 | |
---|
| 67 | <VarListEntry> |
---|
| 68 | <Term>-s, --no-auxiliary-files</Term> |
---|
| 69 | <ListItem> |
---|
| 70 | <Para>do not create .err file. |
---|
| 71 | </Para> |
---|
| 72 | </ListItem> |
---|
| 73 | </VarListEntry> |
---|
| 74 | |
---|
| 75 | <VarListEntry> |
---|
| 76 | <Term>-w, --warnings-are-errors</Term> |
---|
| 77 | <ListItem> |
---|
| 78 | <Para>turn warnings into errors. |
---|
| 79 | </Para> |
---|
| 80 | </ListItem> |
---|
| 81 | </VarListEntry> |
---|
| 82 | |
---|
| 83 | <VarListEntry> |
---|
| 84 | <Term>--log</Term> |
---|
| 85 | <ListItem> |
---|
| 86 | <Para>Send screen output to a .log file. |
---|
| 87 | </Para> |
---|
| 88 | </ListItem> |
---|
| 89 | </VarListEntry> |
---|
| 90 | |
---|
| 91 | </VariableList> |
---|
| 92 | |
---|
| 93 | </refsect1> |
---|
| 94 | |
---|
| 95 | <refsect1><Title>Output</Title> |
---|
| 96 | |
---|
| 97 | <Para>Cavern reads in text files containing the survey data |
---|
| 98 | &svx;) and outputs two files, with the extensions |
---|
| 99 | &x3d; and &err;. |
---|
| 100 | By default these files are put in the current directory, |
---|
| 101 | with the same base filename as the first &svx; file read, |
---|
| 102 | but a different extension. |
---|
| 103 | You can change the directory and/or base filename using the --output |
---|
| 104 | command line option. |
---|
| 105 | <!-- FIXME: link --> |
---|
| 106 | </Para> |
---|
| 107 | |
---|
| 108 | <Para>E.g. if you process the data file <filename>entrance.svx</filename> |
---|
| 109 | with the command <userinput>cavern entrance</userinput> then the files |
---|
| 110 | <filename>entrance.3d</filename> and <filename>entrance.err</filename> |
---|
| 111 | will be created. |
---|
| 112 | </Para> |
---|
| 113 | |
---|
| 114 | <!-- mention .log FIXME --> |
---|
| 115 | |
---|
| 116 | <Para> |
---|
| 117 | Cavern also gives a range of statistics at the end of a successful run: |
---|
| 118 | </Para> |
---|
| 119 | |
---|
| 120 | <itemizedlist> |
---|
| 121 | <listitem><para>The highest and lowest stations and the height difference |
---|
| 122 | between them |
---|
| 123 | </para></listitem> |
---|
| 124 | |
---|
| 125 | <listitem><para>The total length of the survey (before and after |
---|
| 126 | adjustment). This total excludes survey legs flagged as SURFACE, |
---|
| 127 | DUPLICATE, or SPLAY. |
---|
| 128 | </para></listitem> |
---|
| 129 | |
---|
| 130 | <listitem><para>The number of stations and legs. Note that a *EQUATE |
---|
| 131 | is counted as a leg in this statistic. |
---|
| 132 | </para></listitem> |
---|
| 133 | |
---|
| 134 | <!-- FIXME loops, components, anything else --> |
---|
| 135 | |
---|
| 136 | <listitem><para>The East-West and North-South ranges, and the North-most, |
---|
| 137 | South-most, East-most, and West-most stations. |
---|
| 138 | </para></listitem> |
---|
| 139 | |
---|
| 140 | <listitem><para>The number of each size of node in the network (where size |
---|
| 141 | is number of connections to a station) i.e. a one node is the end of a |
---|
| 142 | dead-end traverse, a two-node is a typical station in the middle of a |
---|
| 143 | traverse, a three-node is a T-junction etc. |
---|
| 144 | </para></listitem> |
---|
| 145 | |
---|
| 146 | <listitem><para>How long the processing took and how much CPU time was |
---|
| 147 | used. |
---|
| 148 | </para></listitem> |
---|
| 149 | </itemizedlist> |
---|
| 150 | |
---|
| 151 | <refsect2><Title>&x3d; - data describing the loop-closed centre line</Title> |
---|
| 152 | |
---|
| 153 | <Para>This file contains details of the stations and legs, and any |
---|
| 154 | flags associated with them. |
---|
| 155 | </Para> |
---|
| 156 | |
---|
| 157 | </refsect2> |
---|
| 158 | |
---|
| 159 | <refsect2><Title>&err; - loop closure statistics (%age errors, etc)</Title> |
---|
| 160 | |
---|
| 161 | <Para>This file contains statistics about each traverse in the survey |
---|
| 162 | which is part of a loop. It includes various statistics for each |
---|
| 163 | traverse, such as the percentage error per leg. |
---|
| 164 | You should study this information to determine if any parts of the survey |
---|
| 165 | are of lower quality or contain gross errors. |
---|
| 166 | |
---|
| 167 | <!-- FIXME explain the various statistics --> |
---|
| 168 | </Para> |
---|
| 169 | |
---|
| 170 | </refsect2> |
---|
| 171 | |
---|
| 172 | </refsect1> |
---|
| 173 | |
---|
| 174 | <refsect1><Title>Error Messages</Title> |
---|
| 175 | |
---|
| 176 | <Para> |
---|
| 177 | There are a number of error messages that you may get when processing |
---|
| 178 | data. Most of these are self explanatory, and will be caused by such |
---|
| 179 | problems as typing mistakes, or by your survey data not being attached |
---|
| 180 | to fixed points (in this situation, &survexsuite; will |
---|
| 181 | list some of the stations that are not connected). |
---|
| 182 | </Para> |
---|
| 183 | |
---|
| 184 | <Para> |
---|
| 185 | Along with the error message, the filename and line number of the offending |
---|
| 186 | line will be printed (or the filename for errors such as `file not |
---|
| 187 | found'). The format of the filename and line number is that used by |
---|
| 188 | gcc, so if your editor can parse errors from gcc, you should be able to |
---|
| 189 | set it to allow you to jump to the file and line of each error. |
---|
| 190 | </Para> |
---|
| 191 | |
---|
| 192 | <Para> |
---|
| 193 | Cavern will stop after more than 50 errors. This usually indicates |
---|
| 194 | something like the incorrect data order being specified. Deluging |
---|
| 195 | the user with error messages makes the actual problem less clear. |
---|
| 196 | </Para> |
---|
| 197 | |
---|
| 198 | </refsect1> |
---|