Re: [Therion] Detecting errors

2019-09-07 Thread Tarquin Wilton-Jones via Therion
This is one of the reasons that for legs like that (where the Disto will be parallel to a wall not perpendicular to it during the next shot), we aim the laser not for the station itself, but for the middle of a small block that is a similar size to the Disto, held on the station. The easiest

Re: [Therion] Detecting errors

2019-09-07 Thread Martin Sluka via Therion
> 7. 9. 2019 v 13:33, Ben Cooper : > > I think I see what you mean now, the following drawing portrays the issue > with a Disto sitting on top of one station, and pointing to another. That is the reason to use extension. Martin ___ Therion mailing

Re: [Therion] Detecting errors

2019-09-07 Thread Ben Cooper
>Took your advice to heart and calibrated without helmet. Much better! My non-surveyor assistants are usually dismayed when I ask them to remove everything! Apologies, I misunderstood what you meant by display to the left and right. I think I see what you mean now, the following drawing

Re: [Therion] Detecting errors

2019-09-06 Thread MD
On 6. Sep 2019, at 08:01, Ben Cooper wrote: > > In my experience poor calibration is usually down to either just inaccurate > calibration shots, or local magnetic anomalies: take off watch, step counter, > metal belt buckle, jewellery, glasses, helmet, lights, steel toe caps, etc!! Took your

Re: [Therion] Detecting errors

2019-09-06 Thread MD
On 6. Sep 2019, at 18:31, Wookey wrote: > > What SD numbers do you use for this? > > I agree they should be different, but I've not seen much research > evidence on what the correct numbers are. Pre-Disto we used https://de.wikipedia.org/wiki/H%C3%A4ngezeug which should result in about the

Re: [Therion] Detecting errors

2019-09-06 Thread Wookey
On 2019-08-15 11:50 +0200, Benedikt Hallinger wrote: > To expand a little in this, you could also use the standard „grade“ to tell > theriob which centerline data has which quality. We use this to mark the > centerlines we have surveyed with distox and traditional way and therion uses > this to

Re: [Therion] Detecting errors

2019-09-06 Thread Martin Sluka via Therion
You are the wizard, but for as normal people the physical laws are valid. ;) Martin Odesláno z iPhonu 6. 9. 2019 v 10:39, Pavel Herich : > Martin, > I´ve never used this back extention, but before every "topo day" I use to > calibrate DistoX, which brings me errors under 0,5 % permanetly,

Re: [Therion] Detecting errors

2019-09-06 Thread Pavel Herich
Martin, I´ve never used this back extention, but before every "topo day" I use to calibrate DistoX, which brings me errors under 0,5 % permanetly, very rarely between 0,5 - 1 %. Pavel Dňa 2019-09-06 10:00 Martin Sluka via Therion napísal(a): 5. 9. 2019 v 13:10, Max D : So I know that if

Re: [Therion] Detecting errors

2019-09-06 Thread Markus Boldt
: Re: [Therion] Detecting errors 5. 9. 2019 v 13:10, Max D : So I know that if the display is to the right the Disto tends to reassure an Azimuth 2 degrees to high and if the display is to the left. And when the display is to the left it tends to give an Azimuth 1 degree to low

Re: [Therion] Detecting errors

2019-09-06 Thread Ben Cooper
An error of 3 degrees in clino does indicate a device out of calibration. I would expect it to be within 0.5 degrees for a well calibrated device, and would not tolerate more than 1 degree. In my experience poor calibration is usually down to either just inaccurate calibration shots, or local

Re: [Therion] Detecting errors

2019-09-05 Thread Benedikt Hallinger
You could also indicate the misalignment with instrument correction commands, but i dont know the exact command at the moment. I think that would not with different orientations of the same device... > Am 05.09.2019 um 13:10 schrieb Max D : > > > >> On 5. Sep 2019, at 08:28, Olly Betts

Re: [Therion] Detecting errors

2019-09-05 Thread Max D
> On 5. Sep 2019, at 08:28, Olly Betts wrote: > >> On Fri, Aug 16, 2019 at 05:11:22AM +0200, MD wrote: >> We also then to measure the same small loop at the beginning of each trip: >> A-B in four device orientations >> B-A in four device orientations >> A-C in four device orientations >> C-A

Re: [Therion] Detecting errors

2019-09-05 Thread Olly Betts
On Fri, Aug 16, 2019 at 05:11:22AM +0200, MD wrote: > We also then to measure the same small loop at the beginning of each trip: > A-B in four device orientations > B-A in four device orientations > A-C in four device orientations > C-A in four device orientations > C-B once > > So I could

Re: [Therion] Detecting errors

2019-09-04 Thread Olly Betts
On Thu, Aug 15, 2019 at 10:06:05PM +0100, Olly Betts wrote: > The colour scale is fixed such that blue is "good" and anything else > is suspect. You probably want to look at the worst first. > > Once you have a suspect traverse identified, you can look it up in the > .err file which is produced

Re: [Therion] Detecting errors

2019-08-20 Thread Max D
> On 20. Aug 2019, at 11:21, Max D wrote: > >> >> On 20. Aug 2019, at 11:15, Bruce Mutton wrote: >> >> Survex loop closure seems to be fed arbitrary station names > > Maybe be we can ask Therion to dump a mapping between svx station names and > it's own names. We can! 1. Ensure that

Re: [Therion] Detecting errors

2019-08-20 Thread Max D
> On 20. Aug 2019, at 11:15, Bruce Mutton wrote: > > Survex loop closure seems to be fed arbitrary station names Maybe be we can ask Therion to dump a mapping between svx station names and it's own names. Something like this but for all stations: therion.log … ###

Re: [Therion] Detecting errors

2019-08-19 Thread Olly Betts
On Fri, Aug 16, 2019 at 02:23:20PM +1200, Bruce Mutton wrote: > I'm a Therion user (not Survex), although I use survex loop closure. > That gives some additional statistics in the Therion log file, but not > the loop error standard deviations. I wonder if Therion (or Cavern) > could incorporate

Re: [Therion] Detecting errors

2019-08-15 Thread MD
Thanks for all the suggestions. Especial the „Aven colored by error“ is a superb starting point. We do not always practice paperless caving but Disto X1/X2 devices are used for everything. So we get a SD from Calibrating - although to my understanding this value is something different then

Re: [Therion] Detecting errors

2019-08-15 Thread Bruce Mutton
be made to list them? The graphical presentation in Aven is of course the best, but sometimes a written list is useful as well. Bruce -Original Message- From: Therion On Behalf Of Olly Betts Sent: Friday, 16 August 2019 09:06 To: MD Cc: therion@speleo.sk Subject: Re: [Therion] Detecting

Re: [Therion] Detecting errors

2019-08-15 Thread Olly Betts
On Thu, Aug 15, 2019 at 10:17:00AM +0200, MD wrote: > I wonder what people use to find errors. For example im I have too > loops L1 and L2 and L1 is “good” (0.1% error) while L2 is “bad” (4% > error) i can assume that the error is in the stations/shots which are > part of L2 but not L1. Is there

Re: [Therion] Detecting errors

2019-08-15 Thread Benedikt Hallinger
... forgot to mention, survex can display the errors visually, when generated from therion this way. When you marked the surveys accordingly you can see which loops are bad and which ones are good in the polylines. This greatly aids in finding problematic or faulty measurements. For

Re: [Therion] Detecting errors

2019-08-15 Thread Benedikt Hallinger
To expand a little in this, you could also use the standard „grade“ to tell theriob which centerline data has which quality. We use this to mark the centerlines we have surveyed with distox and traditional way and therion uses this to put more of the errors towards the more bad survey. See

Re: [Therion] Detecting errors

2019-08-15 Thread Martin Sluka via Therion
Somebody else could answer you more detailed. > 15. 8. 2019 v 10:17, MD : > > Our current project is nearing 2000 Stations in a labyrinth and things start > to get cumbersome. We have more than 100 Loops detected by therion. > > I wonder what people use to find errors. For example im I have