December 2020 - Therion

Re: [Therion] Point altitude/deph, Help !
by Xavier Robert 28 Jun '22

28 Jun '22

Hi all, I think I have found a trick. The other Xavier led me to the right tracks, thanks a lot ! Finally, this is quite simple with the point altitude, and no need to change anything inside the : - If we use the point altitude only with the option -align, we get the altitude - If we use the point altitude with the options -align and -value [-1004 m] where 1004 is the altitude of the main entrance, we print the depth only for that point (Do not forget the " - " before the altitude of the main entrance), and thus, we do not erase the classic point altitude. The only (small) limits are : * If the main entrance changes, we need to manually update ALL the points that print the depth. But that should not be be everyday, and not a big issue to do that. * the symbology of the two points is the same. I will have a look for a way to modify that and let you know if I find a trick (If I copy the code of the point Altitude, and call it p_u_depth(expr pos, R, S, A), it crashes...). Cheers, Xav

4 4

How to calculate the volume of a cave
by Bill Gee 31 Jan '22

31 Jan '22

Hello everyone - What tools can be used to calculate the volume of a cave based on center line and LRUD data? I found an email from Martin Sluka from about 4 years ago describing how to use Loch to export a .lox file in other formats, then run that file through CloudCompare or ParaView. The process looks very complex to me, and besides - Loch does not run on my computers, so there is no way for me to generate an export. As far as I can tell, Survex does not have a way to calculate volume. Could it be done with a KML file and Google Earth? -- Bill Gee

8 11

"\legendbox" "\loadpicture" and absolute paths
by rowena 14 Mar '21

14 Mar '21

Hello, I am using the "\loadpicture" capability in "\legendbox" constructs to include map sections, elevations, etc. It all works nicely on my PC where I am using relative paths to the pdf files. My club has a desire to archive the map data for posterity - ie if my pc dies or I go walkabout, the map data should still be available so that others can add to the maps as they are extended. I would prefer to have the images included using relative pathnames, rather than absolute pathnames, so that future explorers can download the map data and extend it, without having to duplicate my file hierarchy. How can I include relative paths in the \loadpicture functionality? Thanks, Rowena

4 5

texts_rs and a remark about karren vs anastomosis
by ivana miskovic 09 Feb '21

09 Feb '21

Hello, Here I put the translation file of map outputs in Serbian language. It would be great if texts_rs.txt were compiled in next Therion release. Also, unrelated to the translation itself, during translation I found some confusion in point symbols for karren and for anastomosis. It seems like they are inverted. Karren are generally sharp limestone formations on the floor, and anastomosis are usually remain like rounded rock formations in the cave ceiling. Unfortunately, in the UIS official symbol list, karren and anastomoses were put on the same picture. Thanx and c u in next surveyes, Ivana

3 4

new Therion 5.5.6
by Therion 13 Jan '21

13 Jan '21

Hi, there is a new release 5.5.6 of Therion. Release notes: v5.5.6 Therion 5.5.6 (2020-12-27): therion: * fixed map statistics bug introduced in 5.5.5 Best regards, Therion team

7 8

Therion 5.5.5 + 5a614ef testing - colour map-fg hierarchy
by Bruce Mutton 26 Dec '20

26 Dec '20

Stacho Most of my datasets checked so far look OK, but there is one that is suspicious, and I am not sure of the proper hierarchy or what it has been in the preceding versions, so it may be OK. What seems to be happening for colour map-fg hierarchy is: 1. ‘lookup’ colours defined in layout override all other map-fg colour specifications 2. ‘Selected’ map colours specified in thconfig override unless there is a matching lookup 3. Explicitly specified map-fg colours are ignored if either of the above are present. I was expecting that number 2 to be top of the list, always, and then the other two dependent on the order called. But it seems never to be the case if there is a lookup, the hierarchy is always as above I think. It might always have been this way, but it seems inconsistent that; a. Selected map colours in thconfig do not always override those defined in layouts (lookups and explicitly specified map-fg), and b. Lookup and explicitly specified map-fg colours do not take their precedence based on order of appearance in layouts. A limited example…. In thconfig: select MegamaniaBeyondWordsPlanMap -color [100 0 0] #ie colour red should override for whole map In layout: colour map-fg map, with a ‘lookup map’ defined Output: Is greyscale as set in a map lookup Change layout to: colour map-fg [97 86 38] # yellow brown Output: Is red as expected, with the select map colour overriding If it has always been this way, then it is not a problem to consider for the Debian release, but maybe later on. Bruce From: Therion <therion-bounces(a)speleo.sk> On Behalf Of Stacho Mudrak Sent: Thursday, 24 December 2020 09:44 To: List for Therion users <therion(a)speleo.sk> Subject: Re: [Therion] Therion 5.5.5 bug - statistics missing from header If you will find some bugs or some suspicious behavior, please let us know. And if someone could test the latest version on some larger datasets, it would be great. We would like to have the most stable version of therion in Debian 11 release and there are still some days left until freeze happens. Thanks, S. On Wed, 23 Dec 2020 at 15:07, Benedikt Hallinger <beni(a)hallinger.org <mailto:beni@hallinger.org> > wrote: Ok wookey, will check that regarding the glx Patch issue then. > Am 23.12.2020 um 14:26 schrieb Wookey <wookey(a)wookware.org <mailto:wookey@wookware.org> >: > > On 2020-12-23 10:42 +0100, Stacho Mudrak wrote: >> I am sorry, one bug fixed, another introduced :/ >> It should be OK in 5a614ef. Windows binaries should be automatically built >> within half an hour. > > And the Debian packages are now built in unstable. They should move into testing in 5 days time. > > > Wookey > -- > Principal hats: Linaro, Debian, Wookware, ARM > http://wookware.org/ > _______________________________________________ > Therion mailing list > Therion(a)speleo.sk <mailto:Therion@speleo.sk> > https://mailman.speleo.sk/listinfo/therion _______________________________________________ Therion mailing list Therion(a)speleo.sk <mailto:Therion@speleo.sk> https://mailman.speleo.sk/listinfo/therion

2 1

Therion 5.5.5 bug - statistics missing from header
by Bruce Mutton 26 Dec '20

26 Dec '20

Not sure if this is of my making due to my customisations, or a bug introduced recently. I suspect a bug. Therion 5.5.5 and 5.5.4+4e3623 produce map headers without explorers, surveyors, cartographers or copyrights. Without making any change other than installing 5.5.4+647dcea the explorers, surveyors, cartographers and copyrights are correctly exported. Bruce

6 10

Re: [Therion] Cartesian STD for individual legs
by Marcelo Taylor 23 Dec '20

23 Dec '20

*Hi Marcelo,* Hi Tarquin, thanks for your kind answer. > These surveys only > use tape and clinometer, surveying triangles, starting from two > coordinates known stations. *That's ... both cool and insane at the same time.* I believe that a typical speleological topographer thing: being a little bit ingenious and a lot insane... *Pretty sure a Total Station can cope with this magnetic rock situation.Perhaps someone else on this list can offer advice...* For sure, but total stations are expensive, cumbersome and time consuming. Our idea is to provide a cheap fast way to deal with magnetic anomalous caves.. > Is there a way to specify specific standard deviations for each leg in > Therion? *As far as I know, SD affects all legs specified after it, until another* *sd command changes it. Similar to the "calibrate" command or "units"* *command.* *sd compass 0.3 degrees* *1 2 12.5 315 17* *sd compass 0.5 degrees* *2 3 7.2 220 33* *It is a Survex command (most things inside a Therion centreline block* *are a direct copy of their Survex equivalents, and can be passed through* *to Survex for processing; group/endgroup is an exception, which is* *begin/end in Survex syntax).* *I tested it with a loop where every leg is set to sd 0.1, but one single* *leg set to 200. Therion gave that single leg most of the error.* Thanks for the suggestion, I will try it for sure. Nevertheless I will prefer to use cartesian data and dX, dY and dZ notations. It is because transversal and longitudinal expected errors are very different in trilateration methodology and I have been able to estimate it in cartesian coordinates. I am a little worried if it will also work in "leap-frogging" legs, but I will check it, for sure. *If that doesn't work for you, you can use:* *group* *sd compass 0.3 degrees* *1 2 12.5 315 17* *endgroup* *group* *sd compass 0.5 degrees* *2 3 7.2 220 33* *endgroup* *It's quite verbose, but that is explicitly stated as being possible in* *the Therion book.* I will try this option too. Right now, that calculations have been done in an Excell spreadsheet,it is verbose, for sure. But the idea is to include in our TOPGRU software package (https://see.ufop.br/topgru) in the future. So, after coding, it will only lead to larger lines centerline blocks, that can be copied directly into Therion. TOPGRU right now is only in portuguese and have a more educational characteristics, but one of our 2021 goals is to release an english version and maybe moving it to GNU compliant. *Hope this helps.* It helped a lot, Tarquin. Many thanks. Marcelo Taylor Cel: +55 21 9 9344 5196 marcelo.taylor(a)gmail.com

2 1

Cartesian STD for individual legs
by Marcelo Taylor 22 Dec '20

22 Dec '20

Dear all, I am a brazilian cave topographer and I am developing a methodology of planimetric trilateration for magnetic influenced caves (Brazil has thousands of caves in iron formation rocks). These surveys only use tape and clinometer, surveying triangles, starting from two coordinates known stations. I have been able to calculate coordinates for all the stations and predict specific cartesian standard deviations for each leg, and prepared both normal and cartesian output that can be read by Therion (I suppose that by Survex too, although I am not a Survex user). Is there a way to specify specific standard deviations for each leg in Therion? I understood that the SD command is only for surveys, isn´t it? Because of trilateration a complex triangle network is created in this kind of survey and it will be very useful to close them in a least Squares algorithm, such as Therion´s. I am sorry if this is a too basic question, but I got stuck in this. Regards, Marcelo Taylor Cel: +55 21 9 9344 5196 marcelo.taylor(a)gmail.com

2 1

new Therion 5.5.5
by Therion 22 Dec '20

22 Dec '20

Hi, there is a new release 5.5.5 of Therion. Release notes: v5.5.5 Therion 5.5.5 (2020-12-22): therion: * updated Italian translation [#308] * fixed bug with statistic explo/topo/carto/copyright <number> * fixed bugs related to an undefined Area of Use, which should be used in Proj transformations Best regards, Therion team

1 0