source: git/doc/TODO.htm @ dcb33cb

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

Add File->Extended Elevation menu item

Provides a way to generate extended elevations for simple cases
without having to use the command line. Suggested by Fleur
Loveridge.

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