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
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
|
<!DOCTYPE html>
<html lang="en" data-content_root="./">
<head>
<meta charset="utf-8" />
<meta name="viewport" content="width=device-width, initial-scale=1.0" /><meta name="viewport" content="width=device-width, initial-scale=1" />
<title>Larry Fish’s Compass — Survex 1.4.17 documentation</title>
<link rel="stylesheet" type="text/css" href="_static/pygments.css?v=d1102ebc" />
<link rel="stylesheet" type="text/css" href="_static/alabaster.css?v=12dfc556" />
<script src="_static/documentation_options.js?v=91e0adf2"></script>
<script src="_static/doctools.js?v=9bcbadda"></script>
<script src="_static/sphinx_highlight.js?v=dc90522c"></script>
<link rel="index" title="Index" href="genindex.htm" />
<link rel="search" title="Search" href="search.htm" />
<link rel="next" title="David McKenzie’s Walls" href="walls.htm" />
<link rel="prev" title="General: How do I?" href="genhowto.htm" />
<link rel="stylesheet" href="_static/custom.css" type="text/css" />
</head><body>
<div class="document">
<div class="documentwrapper">
<div class="bodywrapper">
<div class="body" role="main">
<section id="larry-fish-s-compass">
<h1>Larry Fish’s Compass<a class="headerlink" href="#larry-fish-s-compass" title="Link to this heading">¶</a></h1>
<p>Survex can read Compass survey data - it supports survey data files
and project files (<code class="docutils literal notranslate"><span class="pre">.DAT</span></code> and <code class="docutils literal notranslate"><span class="pre">.MAK</span> <span class="pre">files</span></code>), closed data files (<code class="docutils literal notranslate"><span class="pre">.CLP</span></code>),
and processed survey data (<code class="docutils literal notranslate"><span class="pre">.PLT</span></code> and <code class="docutils literal notranslate"><span class="pre">.PLF</span></code> files). Survex 1.4.6 made
significant improvements to this support so we recommend using this
version or newer if you’re working with Compass data.</p>
<section id="compass-mak-support">
<h2>Compass .MAK support<a class="headerlink" href="#compass-mak-support" title="Link to this heading">¶</a></h2>
<p>A Compass <code class="docutils literal notranslate"><span class="pre">.MAK</span></code> file defines a survey project to process, and
specifies one or more <code class="docutils literal notranslate"><span class="pre">.DAT</span></code> files to process, along with coordinate
systems and fixed points. You can process a <code class="docutils literal notranslate"><span class="pre">.MAK</span></code> file with cavern
or aven as if it were a <code class="docutils literal notranslate"><span class="pre">.svx</span></code> file.</p>
<p>Survex understands most MAK file features. Known current
limitations and assumptions:</p>
<ul>
<li><p>Survex handles the UTM zone and datum provided the combination
can be expressed as an EPSG code (lack of any EPSG codes for a
datum suggests it’s obsolete; lack of a code for a particular
datum+zone combination suggests the zone is outside of the
defined area of use of the datum). Example Compass files we’ve
seen use “North American 1927” outside of where it’s defined
for use, presumably because some users fail to change the datum
from Compass’ default. To enable reading such files we return a
PROJ4 string of the form “+proj=utm …” for “North American
1927” and “North American 1983” for UTM zones which don’t have
an EPSG code. Please let us know if support for additional
cases which aren’t currently supported would be useful to you.</p></li>
<li><p>The <code class="docutils literal notranslate"><span class="pre">@</span></code> command which specifies a base location to calculate
magnetic declinations at is handled, provided the datum and UTM
zone are supported (see previous bullet point). The UTM
convergence angle specified as part of this command is ignored
as Survex knows how to calculate it.</p></li>
<li><p>Link stations are ignored. These have two uses in Compass. They
were a way to allow processing large surveys on computers from
last century which had limited memory. Survex can easily handle
even the largest surveys on current hardware and ignoring them
is not a problem in this case.</p>
<p>The other use is they provide a way to process surveys together
which use the same station names for different stations. In
this case we recommend writing a <code class="docutils literal notranslate"><span class="pre">.svx</span></code> file to replace the MAK
file which wraps the <code class="docutils literal notranslate"><span class="pre">*include</span></code> of each DAT file in
<code class="docutils literal notranslate"><span class="pre">*begin</span> <span class="pre">survey1</span></code>/<code class="docutils literal notranslate"><span class="pre">*end</span> <span class="pre">survey1</span></code>, etc so that stations
have unique qualified names. Then the link stations can be
implemented using e.g. <code class="docutils literal notranslate"><span class="pre">*equate</span> <span class="pre">survey1.XX1</span> <span class="pre">survey2.XX1</span></code>.
This example from the Compass documentation:</p>
<div class="highlight-none notranslate"><div class="highlight"><pre><span></span>#FILE1.DAT; /no links
#FILE2.DAT,A22,A16;
#FILE3.DAT,A16,B14;
</pre></div>
</div>
<p>would look like this:</p>
<div class="highlight-none notranslate"><div class="highlight"><pre><span></span>*begin file1
*include FILE1.DAT
*end file1
*begin file2
*include FILE2.DAT
*end file2
*equate file1.A22 file2.A22
*begin file3
*include FILE3.DAT
*end file3
*equate file1.A16 file3.A16
*equate file2.B14 file3.B14
</pre></div>
</div>
<p>Note that the <code class="docutils literal notranslate"><span class="pre">.svx</span></code> version is able to more precisely represent
what’s actually required here - in the MAK version “you must
carry <code class="docutils literal notranslate"><span class="pre">A16</span></code> into <code class="docutils literal notranslate"><span class="pre">FILE2</span></code> even though <code class="docutils literal notranslate"><span class="pre">FILE2</span></code> doesn’t need it for its
own processing”. If you want the exact analog of the MAK
version you can change the <code class="docutils literal notranslate"><span class="pre">A16</span></code> equate to:</p>
<div class="highlight-none notranslate"><div class="highlight"><pre><span></span>*equate file1.A16 file2.A16 file3.A16
</pre></div>
</div>
</li>
<li><p>The following commands (and any other unknown commands) are
currently ignored: <code class="docutils literal notranslate"><span class="pre">%</span></code> (Convergence angle (file-level)), <code class="docutils literal notranslate"><span class="pre">*</span></code>
(Convergence angle (non file-level)), <code class="docutils literal notranslate"><span class="pre">!</span></code> (Project parameters)</p></li>
</ul>
</section>
<section id="compass-dat-support">
<h2>Compass .DAT support<a class="headerlink" href="#compass-dat-support" title="Link to this heading">¶</a></h2>
<p>A Compass <code class="docutils literal notranslate"><span class="pre">.DAT</span></code> file contains unprocessed survey data. You can process a
<code class="docutils literal notranslate"><span class="pre">.DAT</span></code> file with cavern or aven as if it were a <code class="docutils literal notranslate"><span class="pre">.svx</span></code> file.</p>
<p>You can even use <code class="docutils literal notranslate"><span class="pre">*include</span> <span class="pre">compassfile.dat</span></code> or <code class="docutils literal notranslate"><span class="pre">*include</span>
<span class="pre">compassproject.mak</span></code> in a <code class="docutils literal notranslate"><span class="pre">.svx</span></code> file and it’ll work, which allows combining
separate cave survey projects maintained in Survex and Compass.</p>
<p>One point to note when doing so (this tripped us up!) is that
station names in Compass are case sensitive and so Survex reads
<code class="docutils literal notranslate"><span class="pre">.DAT</span></code> files with the equivalent of <code class="docutils literal notranslate"><span class="pre">*case</span> <span class="pre">preserve</span></code>. The default
in <code class="docutils literal notranslate"><span class="pre">.svx</span></code> files is <code class="docutils literal notranslate"><span class="pre">*case</span> <span class="pre">lower</span></code> so this won’t work</p>
<div class="highlight-none notranslate"><div class="highlight"><pre><span></span>*fix CE1 0 0 0
*include datfilewhichusesCE1.dat
</pre></div>
</div>
<p>because <code class="docutils literal notranslate"><span class="pre">CE1</span></code> in the <code class="docutils literal notranslate"><span class="pre">*fix</span></code> is actually interpreted as <code class="docutils literal notranslate"><span class="pre">ce1</span></code>. The
solution is to turn on preserving of case while you fix the point
like so:</p>
<div class="highlight-none notranslate"><div class="highlight"><pre><span></span>*begin
*case preserve
*fix CE1 0 0 0
*end
*include datfilewhichusesCE1.dat
</pre></div>
</div>
<p>If you want to be able to refer to the fixed point from Survex data too then
you can add in a <code class="docutils literal notranslate"><span class="pre">*equate</span></code> to a lower-case name to achieve that:</p>
<div class="highlight-none notranslate"><div class="highlight"><pre><span></span>*begin
*case preserve
*fix CE1 0 0 0
*equate CE1 ce1
*end
*include datfilewhichusesCE1.dat
*include svxfilewhichusesce1.svx
</pre></div>
</div>
<p>Or if you’re just wanting to link a Compass survey to a Survex one, you can use
a <code class="docutils literal notranslate"><span class="pre">*equate</span></code> with <code class="docutils literal notranslate"><span class="pre">*case</span> <span class="pre">preserve</span> <span class="pre">on</span></code>:</p>
<div class="highlight-none notranslate"><div class="highlight"><pre><span></span>*begin
*case preserve
*equate CE1 ce1
*end
*include datfilewhichusesCE1.dat
*include svxfilewhichusesce1.svx
</pre></div>
</div>
<p>Survex understands most DAT file features. Known current limitations and
assumptions:</p>
<ul class="simple">
<li><p>The cave name, survey short name, survey comment and survey
team information are currently ignored (because this
information isn’t currently saved in the <code class="docutils literal notranslate"><span class="pre">.3d</span></code> file even for <code class="docutils literal notranslate"><span class="pre">.svx</span></code>
files).</p></li>
<li><p>Survey date January 1st 1901 is treated as “no date specified”,
since this is the date Compass stores in this situation, and it
seems very unlikely to occur in real data.</p></li>
<li><p>Passage dimensions are currently ignored.</p></li>
<li><p>Shot flag <code class="docutils literal notranslate"><span class="pre">C</span></code> in Compass causes flagged legs to not be subject to
loop closure. Survex currently sets the SDs of such legs to 1mm,
so flagged legs can still move slightly during loop closure.
(Since 1.4.16; earlier versions ignored this flag entirely.)</p></li>
<li><p>Shot flag <code class="docutils literal notranslate"><span class="pre">L</span></code> is mapped to Survex’s “duplicate” leg flag.</p></li>
<li><p>Shot flag <code class="docutils literal notranslate"><span class="pre">P</span></code> is mapped to Survex’s “surface” leg flag. The
Compass documentation describes shot flag <code class="docutils literal notranslate"><span class="pre">P</span></code> as “Exclude this
shot from plotting”, but the suggested use for it is for
surface data, and shots flagged <code class="docutils literal notranslate"><span class="pre">P</span></code> “[do] not support passage
modeling”. Even if it’s actually being used for a different
purpose, Survex programs don’t show surface legs by default so
the end effect is at least to not plot as intended.</p></li>
<li><p>Shot flag <code class="docutils literal notranslate"><span class="pre">S</span></code> is mapped to Survex’s “splay” leg flag.</p></li>
<li><p>Surveys which indicate a depth gauge was used for azimuth
readings are marked as <code class="docutils literal notranslate"><span class="pre">STYLE_DIVING</span></code> in the <code class="docutils literal notranslate"><span class="pre">.3d</span></code> file.</p></li>
<li><p>Compass seems to quietly ignore a shot with the same “from” and “to”
station. This seems likely to be a mistake in the data so Survex 1.4.12
and later warn about this in a Compass DAT file (in native Survex data
this is treated as an error, which is how older Survex versions treat
it in Compass DAT files).</p></li>
</ul>
</section>
<section id="compass-clp-support">
<h2>Compass .CLP support<a class="headerlink" href="#compass-clp-support" title="Link to this heading">¶</a></h2>
<p>A Compass .CLP file contains raw survey data after adjusting for
loop closure. The actual format is otherwise identical to a
Compass <code class="docutils literal notranslate"><span class="pre">.DAT</span></code> file, and Survex 1.4.6 and later support processing a
.CLP file with cavern or aven as if it were a <code class="docutils literal notranslate"><span class="pre">.svx</span></code> file (the extra
support is to recognise the <code class="docutils literal notranslate"><span class="pre">.CLP</span></code> extension, and to not apply the
instrument corrections a second time).</p>
<p>You can even use <code class="docutils literal notranslate"><span class="pre">*include</span> <span class="pre">compassfile.clp</span></code> in a <code class="docutils literal notranslate"><span class="pre">.svx</span></code> file
and it’ll work, which allows combining separate cave survey
projects maintained in Survex and Compass.</p>
<p>Usually it is preferable to process the survey data without loop
closure adjustments (i.e. <code class="docutils literal notranslate"><span class="pre">.DAT</span></code>) so that when new data is added
errors get distributed appropriately across old and new data, but
it might be useful to use the <code class="docutils literal notranslate"><span class="pre">.CLP</span></code> file if you want to keep
existing stations at the same adjusted positions, for example to
be able to draw extensions on an existing drawn-up survey which
was processed with Compass.</p>
<p>Another possible reason to use the data from a <code class="docutils literal notranslate"><span class="pre">.CLP</span></code> file is if
that’s all you have because the original <code class="docutils literal notranslate"><span class="pre">.DAT</span></code> file has been lost!</p>
</section>
<section id="compass-plf-plt-support">
<h2>Compass .PLF/.PLT support<a class="headerlink" href="#compass-plf-plt-support" title="Link to this heading">¶</a></h2>
<p>A Compass <code class="docutils literal notranslate"><span class="pre">.PLT</span></code> file contains processed survey data. The extension
<code class="docutils literal notranslate"><span class="pre">.PLF</span></code> is also used for “special feature files” which have
essentially the same format.</p>
<p>Survex supports both reading and writing these files, each of which
are documented in separate sections below.</p>
<section id="reading-compass-plf-plt">
<h3>Reading Compass .PLF/.PLT<a class="headerlink" href="#reading-compass-plf-plt" title="Link to this heading">¶</a></h3>
<p>You can load these files with <code class="docutils literal notranslate"><span class="pre">aven</span></code> as if they were .3d files, and
similarly for other Survex tools which expect a .3d file such as
<code class="docutils literal notranslate"><span class="pre">survexport</span></code>, <code class="docutils literal notranslate"><span class="pre">extend</span></code>, <code class="docutils literal notranslate"><span class="pre">diffpos</span></code>, <code class="docutils literal notranslate"><span class="pre">3dtopos</span></code> and <code class="docutils literal notranslate"><span class="pre">dump3d</span></code>.
(This support is actually provided by Survex’s img library, so other
programs which use this library should also be able to read Compass
<code class="docutils literal notranslate"><span class="pre">.PLT</span></code> files without much extra work.)</p>
<p>Survex understands most PLT file features. Known current
limitations and assumptions:</p>
<ul class="simple">
<li><p>Survey date January 1st 1901 is treated as “no date specified”,
since this is the date Compass stores in this situation, and it
seems very unlikely to occur in real data.</p></li>
<li><p>Passage dimensions are translated to passage tubes, but Survex
may interpret them differently from Compass.</p></li>
<li><p>Shot flag <code class="docutils literal notranslate"><span class="pre">C</span></code> is ignored. It only seems to be useful in unprocessed survey
data.</p></li>
<li><p>Shot flag <code class="docutils literal notranslate"><span class="pre">L</span></code> is mapped to Survex’s “duplicate” leg flag.</p></li>
<li><p>Shot flag <code class="docutils literal notranslate"><span class="pre">P</span></code> and plot command <code class="docutils literal notranslate"><span class="pre">d</span></code> are mapped to Survex’s “surface”
leg flag. The Compass documentation describes shot flag <code class="docutils literal notranslate"><span class="pre">P</span></code> as
“Exclude this shot from plotting”, but the suggested use for it
is for surface data, and shots flagged <code class="docutils literal notranslate"><span class="pre">P</span></code> “[do] not support
passage modeling”. Even if it’s actually being used for a
different purpose, Survex programs don’t show surface legs by
default so the end effect is at least to not plot as intended.
Stations are flagged as surface and/or underground based on
whether they are at the ends of legs flagged surface or
non-surface (a station at the boundary can be flagged as both).</p></li>
<li><p>Shot flag <code class="docutils literal notranslate"><span class="pre">S</span></code> is mapped to Survex’s “splay” leg flag. A station
at the far end of a shot flagged <code class="docutils literal notranslate"><span class="pre">S</span></code> gets the “station on wall”
flag set since the Compass PLT format specification says: “The
shot is a “splay” shot, which is a shot from a station to the
wall to define the passage shape.”</p></li>
<li><p>Stations with “distance from entrance” of zero are flagged as
entrances.</p></li>
<li><p>Stations which are present in multiple surveys are flagged as
exported (like when <code class="docutils literal notranslate"><span class="pre">*infer</span> <span class="pre">exports</span> <span class="pre">on</span></code> is in effect in <code class="docutils literal notranslate"><span class="pre">.svx</span></code>
files).</p></li>
<li><p>Stations listed as fixed points are flagged as fixed points.</p></li>
<li><p>If a PLT file only uses one datum and UTM zone combination and
it is supported (the same combinations are supported as for MAK
files) then they are converted to the appropriate EPSG code or
PROJ4 string and this is reported as the coordinate system.
Please let us know if support for additional cases which aren’t
currently supported would be useful to you. Files with multiple
datums could be handled too, but we’d need to convert
coordinates to a common coordinate system in the img library,
which would need it to depend on PROJ. Please let us know if
support for mixed datums would be useful to you.</p></li>
</ul>
</section>
<section id="exporting-compass-plt">
<h3>Exporting Compass .PLT<a class="headerlink" href="#exporting-compass-plt" title="Link to this heading">¶</a></h3>
<p>Survex can also create PLT files via <code class="docutils literal notranslate"><span class="pre">aven</span></code>’s File->Export feature, and also
from the command line via <code class="docutils literal notranslate"><span class="pre">survexport</span> <span class="pre">--plt</span></code>.</p>
<p>This export was originally added to allow importing data from Survex into
Carto. The principal author of Carto has sadly died and it seems Carto is no
longer actively developed, but we’ve left this support in place in case it is
useful - the generated files can be used with Compass itself for example,
though they are currently rather crudely structured. Here are some notes on
this support:</p>
<ul class="simple">
<li><p>The whole Survex survey tree is exported as a single survey.</p></li>
<li><p>Compass station names can’t contain spaces, so any spaces (and also ASCII
control characters) are in station names are replaced by <code class="docutils literal notranslate"><span class="pre">%</span></code> follow by two
lowercase hex digits giving the byte value (like the escaping used in URLs).
<code class="docutils literal notranslate"><span class="pre">%</span></code> itself is also escaped as <code class="docutils literal notranslate"><span class="pre">%25</span></code>.</p></li>
<li><p>The full Survex station name include survey prefixes is used - no attempt is
currently made to shorten station names to fit within the 12 character limit
documented for the Compass PLT format. If you export a single survey the
names should be short enough, but exporting the whole of a complex survey
project will likely give names longer than 12 characters.</p></li>
<li><p>Anonymous stations are given a name <code class="docutils literal notranslate"><span class="pre">%:</span></code> followed by a number starting from
one and incrementing for each anonymous station (Compass doesn’t allow empty
station names, and these invented names can’t collide with actual station
names). Since Survex 1.4.10 (1.4.6 implemented support for exporting
anonymous stations to PLT, but with names which typically exceeded the
documented 12 character limit of the format).</p></li>
<li><p>Passage data is not included in the export (each exported leg has dummy LRUD
readings of all <code class="docutils literal notranslate"><span class="pre">-9</span></code> which is needed to avoid a bug in some versions of
Compass which don’t cope with legs without LRUD).</p></li>
<li><p>Survex’s “surface” leg flag is mapped to Compass shot flag <code class="docutils literal notranslate"><span class="pre">P</span></code>.
The Compass documentation describes shot flag <code class="docutils literal notranslate"><span class="pre">P</span></code> as “Exclude this shot
from plotting”, but the suggested use for it is for surface data, and shots
flagged <code class="docutils literal notranslate"><span class="pre">P</span></code> “[do] not support passage modeling”. Since Survex 1.4.10.</p></li>
<li><p>Survex’s “splay” leg flag is mapped to Compass shot flag <code class="docutils literal notranslate"><span class="pre">S</span></code>. Since Survex
1.4.10.</p></li>
<li><p>Survex’s “duplicate” leg flag is mapped to Compass shot flag <code class="docutils literal notranslate"><span class="pre">L</span></code>. Since
Survex 1.4.10.</p></li>
<li><p>The Datum and UTM zone information is not currently set in exported PLT
files.</p></li>
</ul>
</section>
</section>
</section>
</div>
</div>
</div>
<div class="sphinxsidebar" role="navigation" aria-label="Main">
<div class="sphinxsidebarwrapper">
<h1 class="logo"><a href="index.htm">Survex</a></h1>
<h3>Navigation</h3>
<ul class="current">
<li class="toctree-l1"><a class="reference internal" href="intro.htm">Introduction</a></li>
<li class="toctree-l1"><a class="reference internal" href="getstart.htm">Getting Started</a></li>
<li class="toctree-l1"><a class="reference internal" href="cmdline.htm">Survex Programs</a></li>
<li class="toctree-l1"><a class="reference internal" href="datafile.htm">Survex data files</a></li>
<li class="toctree-l1"><a class="reference internal" href="svxhowto.htm"><code class="docutils literal notranslate"><span class="pre">.svx</span></code> Cookbook</a></li>
<li class="toctree-l1"><a class="reference internal" href="genhowto.htm">General: How do I?</a></li>
<li class="toctree-l1 current"><a class="current reference internal" href="#">Larry Fish’s Compass</a><ul>
<li class="toctree-l2"><a class="reference internal" href="#compass-mak-support">Compass .MAK support</a></li>
<li class="toctree-l2"><a class="reference internal" href="#compass-dat-support">Compass .DAT support</a></li>
<li class="toctree-l2"><a class="reference internal" href="#compass-clp-support">Compass .CLP support</a></li>
<li class="toctree-l2"><a class="reference internal" href="#compass-plf-plt-support">Compass .PLF/.PLT support</a><ul>
<li class="toctree-l3"><a class="reference internal" href="#reading-compass-plf-plt">Reading Compass .PLF/.PLT</a></li>
<li class="toctree-l3"><a class="reference internal" href="#exporting-compass-plt">Exporting Compass .PLT</a></li>
</ul>
</li>
</ul>
</li>
<li class="toctree-l1"><a class="reference internal" href="walls.htm">David McKenzie’s Walls</a></li>
<li class="toctree-l1"><a class="reference internal" href="cmap.htm">Bob Thrun’s CMAP</a></li>
<li class="toctree-l1"><a class="reference internal" href="img.htm">Using the img library</a></li>
<li class="toctree-l1"><a class="reference internal" href="maillist.htm">Mailing List</a></li>
<li class="toctree-l1"><a class="reference internal" href="future.htm">Future Developments</a></li>
</ul>
<div class="relations">
<h3>Related Topics</h3>
<ul>
<li><a href="index.htm">Documentation overview</a><ul>
<li>Previous: <a href="genhowto.htm" title="previous chapter">General: How do I?</a></li>
<li>Next: <a href="walls.htm" title="next chapter">David McKenzie’s Walls</a></li>
</ul></li>
</ul>
</div>
<search id="searchbox" style="display: none" role="search">
<h3 id="searchlabel">Quick search</h3>
<div class="searchformwrapper">
<form class="search" action="search.htm" method="get">
<input type="text" name="q" aria-labelledby="searchlabel" autocomplete="off" autocorrect="off" autocapitalize="off" spellcheck="false"/>
<input type="submit" value="Go" />
</form>
</div>
</search>
<script>document.getElementById('searchbox').style.display = "block"</script>
</div>
</div>
<div class="clearer"></div>
</div>
<div class="footer">
©1998-2025.
|
Powered by <a href="https://www.sphinx-doc.org/">Sphinx 8.1.3</a>
& <a href="https://alabaster.readthedocs.io">Alabaster 0.7.16</a>
</div>
</body>
</html>
|
