Re: [Therion] Hiding centreline within a scrap, while showing it for surveys
> On 7. Dec 2019, at 09:53, Tarquin Wilton-Jones via Therion > wrote: > > I want to hide the centreline within bar@baz, So qux has data for bar@baz? I generally have one piece of centerline per scrap and include only the centerline data when there’s no scrap. —max ___ Therion mailing list Therion@speleo.sk https://mailman.speleo.sk/listinfo/therion
Re: [Therion] Bounding Box to big in Loch but fine in Aven
> On 23. Sep 2019, at 15:13, Tarquin Wilton-Jones via Therion > wrote: > >> On 23/09/2019 09:06, Max D wrote: >> >> >>> On 22. Sep 2019, at 23:28, Max D wrote: >>> >>> So I'm still searching. >> >> Found it. Inside a th2 file there was a big scrap and a small one . >> The small one contained no stations. Adding Stations fixed the lox bounding >> box. > > > When you try to render this as PDF, Metapost says it cannot render > something that large It did not show tat error in my case - probably because the scrap was nowhere referenced. —max ___ Therion mailing list Therion@speleo.sk https://mailman.speleo.sk/listinfo/therion
Re: [Therion] Detecting errors
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 advice to heart and calibrated without helmet. Much better! Thanks! —max ___ Therion mailing list Therion@speleo.sk https://mailman.speleo.sk/listinfo/therion
Re: [Therion] Detecting errors
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 same SD as an Disto. I toyed with taking the Callibration SD but I‘m not sure this makes sense. > Also SDs are about expected errors and do not cover blunder > probability I think this is an important point. They tend to mess up things much worse than anything else. —max___ Therion mailing list Therion@speleo.sk https://mailman.speleo.sk/listinfo/therion
Re: [Therion] Detecting errors
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 the survey sd. 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 calculate an SD based on that. For sone Devices errors seem to be bound very much to orientation. In the data saved by TopoDroid you can see the device orientation and so we could set a sd based on the direction in which the shot was taken. I have nit investigated this further so far. Also because we have this data only for about 20% of the cave. TopoDroid also is able to flag an “magnetic anomaly” - i’m not totally sure how but this als could be used in setting a per shot SD. i have not looked much into this. Regards —max ___ Therion mailing list Therion@speleo.sk https://mailman.speleo.sk/listinfo/therion
[Therion] Detecting errors
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 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 an automated approach for that? When I add a new loop and the overall error goes up it is likely, that this loop is faulty. Any way to automatically check that? I also read the “Error Detection in Compass” page and couldn’t understand much mire than “we just try out”. We have Disto X (no transcription errors possible) and traditional (transcription errors likely) surveys. How to handle that? Any suggestions besides loads of manual work? ___ Therion mailing list Therion@speleo.sk https://mailman.speleo.sk/listinfo/therion
Re: [Therion] merge lines in xtherion
> On 26. Jul 2019, at 10:37, Benedikt Hallinger wrote: > > What exactly is the problem with two separate lines in this case? > Just curious For example my TopoDroid exports tend to have half a dozen separate lines, where One would be enough. Changing styles etc is a pain this way. Also „convert to curve“ gets better results with a single line. —max ___ Therion mailing list Therion@speleo.sk https://mailman.speleo.sk/listinfo/therion
