source: git/doc/TODO.htm @ 6b71b92

RELEASE/1.2debug-cidebug-ci-sanitisersfaster-cavernloglog-selectstereostereo-2025walls-datawalls-data-hanging-as-warningwarn-only-for-hanging-survey
Last change on this file since 6b71b92 was 2a9c909, checked in by Olly Betts <olly@…>, 9 years ago

Use docbook2man instead of docbook-to-man

The latter seems to be no longer actively maintained, and docbook2man
now does a similarly good job. It is also available in homebrew, which
docbook-to-man isn't.

  • Property mode set to 100644
File size: 9.5 KB
RevLine 
[0e26b3a]1<HTML><HEAD>
2<TITLE>Survex To-Do List</TITLE>
3<STYLE type="text/css"><!--
4BODY, TD, CENTER, UL, OL {font-family: sans-serif;}
5-->
6</STYLE>
7</HEAD><BODY BGCOLOR=white TEXT=black>
8<H1>Survex To-Do List</H1>
9
[df26b81]10<H2>3d format</H2>
[f39a2e8]11
[df26b81]12<ul>
[f39a2e8]13
[df26b81]14<li>sort out XSECT - I'm sure I meant there to be 1 and 2 byte forms, not 2
15and 4 - 4 byte is only useful if a passage dimension is &gt; 327.67m!
[f39a2e8]16
[df26b81]17<li>store equated stations in some way
[f39a2e8]18
[df26b81]19<li>store legs by end stations rather than repeating coordinates over and
20over?
[ac3f376]21
[df26b81]22</ul>
[f39a2e8]23
[df26b81]24<H2>Aven</H2>
[ac3f376]25
[df26b81]26<ul>
[f39a2e8]27
[ce77e4f]28<li>Compare HPGL export with what printhpgl used to give.
29
[df26b81]30<li>loading a .3d file with no survey data (or which has a valid header but is broken later) with a survey already loaded doesn't work well.
[f39a2e8]31
[df26b81]32<li>After keyboard controlled movement, the measuring line/circle doesn't
33reappear until the mouse is moved (e.g. plan/elevation transition with P/L).
[f39a2e8]34
[df26b81]35<li>Fix depth clipping on grid
[f39a2e8]36
[ac3f376]37<li>Does anyone use Controls-&gt;"Reverse Sense"?  It made some sense with
38caverot but now seeing the mouse pointer makes people expect the default
39motions (for right button drag particularly).
[f39a2e8]40
[ce77e4f]41<li>Clean up export.cc and allow line width, etc to be specified
[f39a2e8]42
43<li>Better handling of missing LRUD values
44
45<li>Smooth wrinkles in presentation code (stop pres on Open or
46New, changing focus on listctrl as presentation plays doesn't really work
47properly)
48
49<li>Draw the measuring line directly onto the front buffer, so we can remove it
50with a copy from the back buffer and redraw it in the new position without a
51re-render.
52
[ac3f376]53<li>Round the measuring line coords so the ring is a nice shape?  Or just
54antialias the ring, "there" blob and line?
[f39a2e8]55
56<li>Process all pending input before rerendering to improve responsiveness.
57
58<li>Check timing code - we need to glFinish to ensure it's all drawn, and that
59may be needed to get meaningful timing info.
60
[85ed935]61<li>Add "colour by survey" - colour by cave (and more generally by sub-prefix):
62maybe "aven --survey 161 --colour-by-sub-prefix all.3d" would result in
63lhroute, rhroute, adrian, etc all getting different colours...
[f39a2e8]64
65<li>Implement "Skip blank pages" in aven printing
66
67<li>different keyboard layouts mean that some key choices don't make much sense...
68
[ef041e1]69<li>Easy way to "print extended elevation" - e.g. button in aven for extended elevation (ask for .spec file?)
[f39a2e8]70
71<li>Optional lazy label redraw during drags?  Or turn on at some redraw time
72threshold...
73
74<li>Some way to view older/newer version of survey
75
76<li>Label lengths aren't considered when working out image size when
77printing so a long label can spill off the edge of the printout
78
[df26b81]79<li>print to an image file?
[f39a2e8]80
81<li>grid on printouts
82<ul>
83<li>grid crosses option (only draw cross at intersections, not a full grid).
84<li>[(x,y) of a point to go through (easting, northing)
85<li>x spacing, y spacing (default to x spacing)
86<li>orientation (bearing of y-axis?) (defaults to 0)]
87</ul>
88
89<li>Profile aven further (for both speed and memory usage)
90
91<li>by default put crosses on those points with no legs attached (unused
92fixed points)?
93
94<li>label junctions/dead ends?
95
96<li>section colouring/selective labelling
97
98<li>clipping - want to select a clip sphere (or maybe cube) centred on
99centre on rotation I think.
100
101<li>Some way to display all the names of an equated station (e.g. in pop-up
102window or the info panel).
[e03199f]103
[27b8b59]104<li>check on monochrome, 16, and 256 colour displays - especially that depth
105colouring looks OK
[0e26b3a]106
[a8e9fde]107<li>Feed back redraw time to key based movement as in caverot?  Or perhaps best
108not to?  It depends on whether we expect people to hold down keys or not...
109Perhaps something smart where the first press is a fixed size, then after that
110it depends on the redraw?
[df26b81]111
112<li>improve .plt export to include less crude survey structure.
113
114<li>If multiple methods for drawing crosses and/or blobs pass the
115visual fidelity check, check which is fastest.
116
117<li>Lots of aven things need documenting.
118
[0e26b3a]119</ul>
120
121<H2>Documentation</H2>
122
123<ul>
124
[ce77e4f]125<li>Document averaging of repeated legs
126
[0e26b3a]127<li>Platform specific versions of docs?
128
129<li>Put more terms in terminology in docs ? trip, instrument, ...
130
[2e53e55]131<li>Finish off manual loose ends.
132
[91f6661]133<li>Document dump3d
134
[df26b81]135<li>Look at rewording extend.sgml (AndyA comments)
[b462168]136
[0e26b3a]137</ul>
138
[65ad692]139<H2>Internationalisation and Localisation</H2>
[0e26b3a]140
141<ul>
142
[df26b81]143<li>Update translations.
[0e26b3a]144
[85c0078]145<li>length units in .err file?
[65ad692]146
147</ul>
148
149<H2>Test Suite</H2>
150
151<ul>
152
153<li>test diving data with compass omitted (plumbed)
154
155<li>more tests for direction
156
157<li>improve 3d torture test and try to automate its use if possible.
158
[b462168]159<li>Compass .mak and .plt and CMAP .xyz in test suite?
[65ad692]160
[df26b81]161<li>img.c: explicitly test routines in test suite?
[65ad692]162
[0e26b3a]163</ul>
164
165<H2>Miscellaneous</H2>
166
167<ul>
168
[ac3f376]169<li>resolve FIXMEs in code
[0e26b3a]170
[df26b81]171<li>diffpos: compare connectivity (i.e legs as well as stations) - e.g.
172
173<pre>
174foo.1 moved by (0.02, 0.10, -0.06)
175leg between foo.1 and bar.2 removed
176...
177bar.2 moved by (-0.02, -0.05, 0.03)
178</pre>
179
180</ul>
181
182<H2>Cavern</H2>
183
184<ul>
185
186<li>This gives "*** Singular!!!" warning with DEBUG_INVALID on:
187<pre>
1881 2 50000 0 -
1891 2 5 0 -30
190</pre>
191
[0e26b3a]192<li>Default variance for topofil counter? (currently same as that of tape)
193
194<li>Rather than forming a linked list of components, solve each as it is
195identified?  Beware of issues like those that revcomplist test checks.
196
197<li>Don't split other traverses at articulating traverses when reporting error
198stats.
199
[4c5c5f3]200<li>sort out title which goes in .3d file for this (if no *includes in ...
201it gets the title of the leafname of this .svx file, otherwise it's the
202leafnames of the *include-d files, comma-separated):
203
204<pre>
205*begin mycave
206*title "My Cave"
207...
208*end mycave
209</pre>
[3ede867]210
[df26b81]211<li>look at solution by QR factorisation in matrix.c more
[3ede867]212
[df26b81]213<li>consider disabling the more expensive asserts - turning them all off
214speeds up cavern by about 10%.
[3ede867]215
[df26b81]216<li>
217Warn bearings not 3 digits, gradient not &lt;sign&gt;&lt;digit&gt;&lt;digit&gt;
[3ede867]218
[df26b81]219<li>Sort out gross error detection code
220
221<li>For warnings such as "Suspicious compass reading", report the reading
222in question in the error message (in the text form given in the file).
223Also report values when warning about problems with processed readings.
224
225<li>legs: implied flags: inloop/plumb
226
227<li>legs: "dubious" for "tapeless" legs - bearing along continuation...
[3ede867]228
[df26b81]229<li>station flags: "important" - e.g. top camp "fixed" point /
230junction,deadend (implied by order) /
231articulation pt (know for nodes I think a station is if at least one
232of its nodes is)
233
234<li>Maybe station lists should know how long they are?
235
236<li>Articulation point code: ideally the articulation point code should allow
237further network reductions to happen after splitting at articulation
238points?
239
240</ul>
241
242<H2>Survex file format</H2>
243
244<ul>
245
246<li>*data chamber ...
247
248<li>*data nsew ... for pitches (bearings rather than having to be NSEW)
249
250<li>Allow angles as deg/min/sec (for theodolite data) (060&deg;10'15" as 060 10
25115, or 060.1005 (crap notation))
252
253<li>Add support for bearings of form N20E (ie [NS][0-9]+[EW])?
254
255<li>should % after a clino reading work?
256
257<li>Fixing a point by triangulation?
258
259<li>multiple readings:
260<p>
261average bearings specially - they don't average like normal numbers
262<p>
263%age gradients should probably average the same as angle gradients
264<p>
265Document - works like so:
[3ede867]266<pre>
[df26b81]267*set open {
268*set close }
269*calibrate compass {000.5 001.0 001.25}
2701 2 10.23 {000 001} -02
2712 3 {10.16 10.17} 127 {+06 +05}
2723 4 11.98 007 {+03 +03}
[3ede867]273</pre>
[df26b81]274Implement as extension to number format so any suitable numeric value to be
275repeated?
276<li>Theodolite + level:
277<ul>
278  <li>delta(bearing (relative to 0 at start)
279  <li>delta(horizontal)
280  <li>delta(vertical) / maybe "clino" instead
281</ul>
[3ede867]282
[df26b81]283<li>Theodolite only:
284<ul>
285  <li>delta(bearing (relative to 0 at start)
286  <li>delta(horizontal)
287  <li>infinite sd for z
288</ul>
[3ede867]289
[df26b81]290<li>Infinite sds so we can fix in x and y only (or z only)?
[7c663ef]291
[df26b81]292<li>legs: "commented out" flag?  syntax check data but otherwise ignore
[6cd4aab]293
[df26b81]294<li>legs: hydrology - fossil/active/not recorded/static water/underwater
295(sump) [diving underwater by default? except style can mean altimeter
296too...]
297
298<li>legs: floor type - mud/sand/breakdown/flowstone/etc and can then used
299LRUD to draw crude survey...
300
301<li>Allow valid range for an instrument to be specified.  Tie in with
302*instrument.  *units date - ranges for dates - e.g. "1990-" or
303"jun-aug"...
304
305<li>cope with any combination of readings which gives enough info ???
306
307<li>leg and station "comments":
308
309<pre>*data passage station left right up down comment
310
3111 1.0 - 50+ 0.5 "large cairn"
312
3132 ...
314
315*data normal station l r u d comment newline tape compass clino
316
3171 1.0 - 50+ 0.5 "large cairn"
318
319  10.78 123 -03
320
3212 ...
322</pre>
323
324comment can be omitted "-" or not present if at end of line...?
325commentall?
326
327<li>Allow covariances to be specified in cartesian style?
328
329<li>flag legs as "skeletal" or something? (i.e. not in the cave passage) -
330e.g. a radiolocation leg from one passage to another isn't surface,
331but it isn't in the cave itself either (it's through rock).  You could
332just call it surface but maybe later we want to use the surface
333flag to produce points for a surface triangulation...
334
335<li>?outlaw prefixes on stations in data legs (as Todd has lobbied for)
336and then the prefix of a leg == prefix of each end...?
337
338<li>comma separated dates in *date?
339
340<li>Find a solution to Thilo's "." problem.
341
342<li>Units in *fix (currently metres)
343
344</ul>
345
346<H2>img library</H2>
347
348<ul>
349
350<li>eliminate duplicate img_LABELs when reading .PLT files.
351
352<li>img should return img_XSECT from Compass PLT files.
353
354<li>make img more modular (convert to C++?)
355
356<li>add support for .KST?  Gary says documentation is out of date, and recent
357releases of winkarst have broken .KST export/import...
358
359<li>resolve documentation/examples mismatch for station based XYZ files and
360implement reading of legs from them.
[a775268]361
[0e26b3a]362</ul>
363
364</BODY></HTML>
Note: See TracBrowser for help on using the repository browser.