Custom Query (95 matches)

Pockettopo measures 3 versions of each leg, and if you feed such data into cavern it treats each version as a separate leg, producing a very loopy network which takes a while to solve.

Ideally we want to average the repeat readings in this case, and then solve the network treating each set of such readings as one leg. That would also make the leg count saner.

Not sure if we just always do this when we have multiple readings between two points, or if we only consider consecutive readings. The later is probably easier to implement if nothing else.

comments on Mac version...

• processing a .svx file does not produce a log file - so unable to get length/depth details of survey

• clicking on a station in Aven view most times resets the view to some random angle or size/magnification....sometimes flipping the survey 180º !

On cavern runs the warnings say 'WARNING' but the errors (which prevent a 3d file being output) do not say 'ERROR', so it can be very hard to find the actual offending issue in the output, especially when there is a lot of it.

This is noticeable in a project with backbearings for example, where a lot of 'mismatched backbearing' warnings can obscure the important ERROR lines.

Can we please just mark errors explicitly with something greppable? (probably 'ERROR:')

This could be described as an enhancement or a bug, but I'm going to file it as a bug as it seems wrong, given the WARNING output.