source: git/doc/TODO.htm @ e63994c

RELEASE/1.2debug-cidebug-ci-sanitisersstereowalls-datawalls-data-hanging-as-warning
Last change on this file since e63994c was b22123e, checked in by Olly Betts <olly@…>, 8 years ago

Remove already done item from todo list

  • Property mode set to 100644
File size: 9.5 KB
Line 
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
10<H2>3d format</H2>
11
12<ul>
13
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!
16
17<li>store equated stations in some way
18
19<li>store legs by end stations rather than repeating coordinates over and
20over?
21
22</ul>
23
24<H2>Aven</H2>
25
26<ul>
27
28<li>Compare HPGL export with what printhpgl used to give.
29
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.
31
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).
34
35<li>Fix depth clipping on grid
36
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).
40
41<li>Clean up export.cc and allow line width, etc to be specified
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
53<li>Round the measuring line coords so the ring is a nice shape?  Or just
54antialias the ring, "there" blob and line?
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
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...
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
69<li>File-&gt;Extended Elevation - provide a way to specify a spec file?  Or
70better a UI to control the extending.
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
80<li>print to an image file?
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).
104
105<li>check on monochrome, 16, and 256 colour displays - especially that depth
106colouring looks OK
107
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?
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
120</ul>
121
122<H2>Documentation</H2>
123
124<ul>
125
126<li>Platform specific versions of docs?
127
128<li>Put more terms in terminology in docs ? trip, instrument, ...
129
130<li>Finish off manual loose ends.
131
132<li>Document dump3d
133
134<li>Look at rewording extend.sgml (AndyA comments)
135
136</ul>
137
138<H2>Internationalisation and Localisation</H2>
139
140<ul>
141
142<li>Update translations.
143
144<li>length units in .err file?
145
146</ul>
147
148<H2>Test Suite</H2>
149
150<ul>
151
152<li>test diving data with compass omitted (plumbed)
153
154<li>more tests for direction
155
156<li>improve 3d torture test and try to automate its use if possible.
157
158<li>Compass .mak and .plt and CMAP .xyz in test suite?
159
160<li>img.c: explicitly test routines in test suite?
161
162</ul>
163
164<H2>Miscellaneous</H2>
165
166<ul>
167
168<li>resolve FIXMEs in code
169
170<li>diffpos: compare connectivity (i.e legs as well as stations) - e.g.
171
172<pre>
173foo.1 moved by (0.02, 0.10, -0.06)
174leg between foo.1 and bar.2 removed
175...
176bar.2 moved by (-0.02, -0.05, 0.03)
177</pre>
178
179</ul>
180
181<H2>Cavern</H2>
182
183<ul>
184
185<li>This gives "*** Singular!!!" warning with DEBUG_INVALID on:
186<pre>
1871 2 50000 0 -
1881 2 5 0 -30
189</pre>
190
191<li>Default variance for topofil counter? (currently same as that of tape)
192
193<li>Rather than forming a linked list of components, solve each as it is
194identified?  Beware of issues like those that revcomplist test checks.
195
196<li>Don't split other traverses at articulating traverses when reporting error
197stats.
198
199<li>sort out title which goes in .3d file for this (if no *includes in ...
200it gets the title of the leafname of this .svx file, otherwise it's the
201leafnames of the *include-d files, comma-separated):
202
203<pre>
204*begin mycave
205*title "My Cave"
206...
207*end mycave
208</pre>
209
210<li>look at solution by QR factorisation in matrix.c more
211
212<li>consider disabling the more expensive asserts - turning them all off
213speeds up cavern by about 10%.
214
215<li>
216Warn bearings not 3 digits, gradient not &lt;sign&gt;&lt;digit&gt;&lt;digit&gt;
217
218<li>Sort out gross error detection code
219
220<li>For warnings such as "Suspicious compass reading", report the reading
221in question in the error message (in the text form given in the file).
222Also report values when warning about problems with processed readings.
223
224<li>legs: implied flags: inloop/plumb
225
226<li>legs: "dubious" for "tapeless" legs - bearing along continuation...
227
228<li>station flags: "important" - e.g. top camp "fixed" point /
229junction,deadend (implied by order) /
230articulation pt (know for nodes I think a station is if at least one
231of its nodes is)
232
233<li>Maybe station lists should know how long they are?
234
235<li>Articulation point code: ideally the articulation point code should allow
236further network reductions to happen after splitting at articulation
237points?
238
239</ul>
240
241<H2>Survex file format</H2>
242
243<ul>
244
245<li>*data chamber ...
246
247<li>*data nsew ... for pitches (bearings rather than having to be NSEW)
248
249<li>Allow angles as deg/min/sec (for theodolite data) (060&deg;10'15" as 060 10
25015, or 060.1005 (crap notation))
251
252<li>Add support for bearings of form N20E (ie [NS][0-9]+[EW])?
253
254<li>should % after a clino reading work?
255
256<li>Fixing a point by triangulation?
257
258<li>multiple readings:
259<p>
260average bearings specially - they don't average like normal numbers
261<p>
262%age gradients should probably average the same as angle gradients
263<p>
264Document - works like so:
265<pre>
266*set open {
267*set close }
268*calibrate compass {000.5 001.0 001.25}
2691 2 10.23 {000 001} -02
2702 3 {10.16 10.17} 127 {+06 +05}
2713 4 11.98 007 {+03 +03}
272</pre>
273Implement as extension to number format so any suitable numeric value to be
274repeated?
275<li>Theodolite + level:
276<ul>
277  <li>delta(bearing (relative to 0 at start)
278  <li>delta(horizontal)
279  <li>delta(vertical) / maybe "clino" instead
280</ul>
281
282<li>Theodolite only:
283<ul>
284  <li>delta(bearing (relative to 0 at start)
285  <li>delta(horizontal)
286  <li>infinite sd for z
287</ul>
288
289<li>Infinite sds so we can fix in x and y only (or z only)?
290
291<li>legs: "commented out" flag?  syntax check data but otherwise ignore
292
293<li>legs: hydrology - fossil/active/not recorded/static water/underwater
294(sump) [diving underwater by default? except style can mean altimeter
295too...]
296
297<li>legs: floor type - mud/sand/breakdown/flowstone/etc and can then used
298LRUD to draw crude survey...
299
300<li>Allow valid range for an instrument to be specified.  Tie in with
301*instrument.  *units date - ranges for dates - e.g. "1990-" or
302"jun-aug"...
303
304<li>cope with any combination of readings which gives enough info ???
305
306<li>leg and station "comments":
307
308<pre>*data passage station left right up down comment
309
3101 1.0 - 50+ 0.5 "large cairn"
311
3122 ...
313
314*data normal station l r u d comment newline tape compass clino
315
3161 1.0 - 50+ 0.5 "large cairn"
317
318  10.78 123 -03
319
3202 ...
321</pre>
322
323comment can be omitted "-" or not present if at end of line...?
324commentall?
325
326<li>Allow covariances to be specified in cartesian style?
327
328<li>flag legs as "skeletal" or something? (i.e. not in the cave passage) -
329e.g. a radiolocation leg from one passage to another isn't surface,
330but it isn't in the cave itself either (it's through rock).  You could
331just call it surface but maybe later we want to use the surface
332flag to produce points for a surface triangulation...
333
334<li>?outlaw prefixes on stations in data legs (as Todd has lobbied for)
335and then the prefix of a leg == prefix of each end...?
336
337<li>comma separated dates in *date?
338
339<li>Find a solution to Thilo's "." problem.
340
341<li>Units in *fix (currently metres)
342
343</ul>
344
345<H2>img library</H2>
346
347<ul>
348
349<li>eliminate duplicate img_LABELs when reading .PLT files.
350
351<li>img should return img_XSECT from Compass PLT files.
352
353<li>make img more modular (convert to C++?)
354
355<li>add support for .KST?  Gary says documentation is out of date, and recent
356releases of winkarst have broken .KST export/import...
357
358<li>resolve documentation/examples mismatch for station based XYZ files and
359implement reading of legs from them.
360
361</ul>
362
363</BODY></HTML>
Note: See TracBrowser for help on using the repository browser.