Mangled 3d file

[Bill Gee]

Hi Olly -

Wow, that is interesting!  I set the SD because otherwise cavern issues a 
warning on every set of readings that do not match exactly.  I don't want to 
see 200 warnings for readings that are within the tolerance we chose.

I set it for only the forward readings because I assumed cavern would apply it 
to the backward reading as well.  It is, after all, looking at BOTH readings 
to determine whether a warning should be issued.

I added backcompass and backclino to the *sd lines and ran cavern again.  Now 
everything looks good.

Thanks - Bill Gee



On Tuesday, March 03, 2015 22:10:56 Olly Betts wrote:
> On Tue, Mar 03, 2015 at 02:21:18PM -0600, Bill Gee wrote:
> > I attached the SVX file and resulting 3D file.  The cave runs mostly
> > straight north, but the .3d file shows it as a spaghetti mess.  It looks
> > OK up to station A10 except for a splay shot that goes off the wrong side
> > of the passage.  After A10 it is just a mess.
> 
> This issue seems to be due to only setting the SD for the compass and
> clino, not for the backcompass and backclino - if I change the *sd
> commands to these, the processed data looks much better:
> 
> *sd clino backclino 1.0 degrees
> *sd compass backcompass 1.0 degrees
> 
> It looks like there's a bug with handling the case where the instrument
> and back instrument have different SDs, which is probably not common in
> reality (having different instruments for each sighting direction is
> reasonably, so the calibrations may well be different, but I doubt many
> people use a significantly less accurate instrument for sighting in one
> direction).
> 
> I'll try to fix the bug, but making sure that you set the same SDs for
> both directions should avoid the problem.
> 
> Cheers,
>     Olly