source: git/doc/TODO.htm @ faf83bee

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

doc/manual.sgml,src/commands.c,tests/cmd_dummy.svx,
tests/doubleinc.out: Add *ref command to allow specifying an external
reference.

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