August 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

Different map-level for different map items
by Tarquin Wilton-Jones 24 Aug '20

24 Aug '20

Hi, Just wondering if map-level can be dynamic or set differently for different map items. map mymap -projection plan eastcaves westcaves surfaceMP@surface #this has a title endmap map eastcaves cave1MP@cave1 #this has a title cave2MP@cave2 #this has a title endmap map westcaves cave3MP@cave3 #this has a title cave4MP@cave4 #this has a title endmap If I were making an atlas of "mymap" (using "select mymap@mycaves -map-level 2" and "export atlas"), I would want to use "-map-level 2" for the caves, but "-map-level 1" for the surface. Is there a way to make it use a different map-level for each item in mymap, or would I need to create a nested map to put surfaceMP@surface into, so that it would also have a map-level of 2? Cheers, Tarquin

1 0

Building Therion on Centos 8 (stream)
by Þórir Már Jónsson 20 Aug '20

20 Aug '20

I am building Therion for the first time and getting one Proj related error when running make: ------------------------------------------------------------------------------- projections: EPSG label -------------------------------------------------------------------------------utest-proj.cxx:77............................................................................... utest-proj.cxx:78: *FAILED:* CHECK( (epsg_labels.count(32634) > 0 && strcmp(epsg_labels[32634],"WGS 84 / UTM zone 34N") == 0) ) with expansion:* false* *====*=========================================================================== test cases: 18 | 17 passed | *1 failed* assertions: 44 | 43 passed | *1 failed* make: *** [Makefile:184: tests] Error 1 Is this an error I can ignore or something I need to fix? If so, do you have any pointers to how I might do that? Best regards, Þórir Már

4 9

Staion point should not go to the calculated lenght of the cave
by Markus Boldt 17 Aug '20

17 Aug '20

Hi, hopefully someone can give me an idea, what I have to do in therion, when I have a point station, which should not go to the calculated length of the cave. But this point station should shown in the In my sample there is a doline in the near of my cave entrance with a point station. Thanks! Best Markus

3 3

Difference between Therion and Survex when calibrating tape
by Tarquin Wilton-Jones 15 Aug '20

15 Aug '20

Hi folks, Think I may have uncovered a bug in Therion's parsing of the "calibrate tape" command. Survex: *calibrate tape 0 0.5 *calibrate tape 0 1 2 10 0 0 *calibrate tape 0 1 2 3 10 90 0 Therion: calibrate tape 0 0.5 calibrate tape 0 1 2 10 0 0 calibrate tape 0 1 2 3 10 90 0 In Survex, both legs are 10 m long. In Therion, the first leg is 5 m long and the second is 10 m long. Therion book: "The syntax is borrowed from Survex with minor modifications; the Survex manual may be useful as an additional reference for the user." Survex manual does not say what happens to the scale value when it is omitted, but it does say "By default, the zero error is 0.0 and the scale factor 1.0 for all quantities." This implies that the scale value should reset to 1 whenever it is omitted. Assuming Survex is "right" with this behaviour, does that mean Therion is wrong? Or is this one of those "minor differences"? Or if I just messed up, someone please shout at me ;) Cheers, Tarquin

3 4

Extended elevations - development snapshot (commit c7d41d9)
by Bruce Mutton 13 Aug '20

13 Aug '20

Thanks Stacho, fast work. The extend logging works, the scaled legs stand out nicely. My current project behaved exactly the same with c7d41d9 so I don’t think it broke anything. Moving the scaled legs from in-line with the survey data, out to a separate centreline using… extend <ratio> <from> <to> extend <ratio> <station> …also worked perfectly. I got a slight surprise in that ‘extend <ratio> <station>’ scales both the incoming and outgoing legs to and from that station, but then I realised that this is consistent with Therion’s treatment of other extend options ie as described in /wiki/extend <https://therion.speleo.sk/wiki/extend#summary_of_all_extend_options_for_sur…> ‘important note’ part way down the page. I have not tried extend ignore <3 station path> yet, but otherwise I think all the recent changes are sound. I only noticed one slight change in ‘breaking’ behaviour when checking a sample of old projects. It is an unfinished project, so it is not too late for me to tidy up the change. I may be out in a Therion desert for the next 10 days, but some time after that I should update the wiki extend page. Prod me if I forget. Bruce From: Therion <therion-bounces(a)speleo.sk> On Behalf Of Stacho Mudrak Sent: Thursday, 13 August 2020 08:50 To: List for Therion users <therion(a)speleo.sk> Subject: Re: [Therion] Extended elevations - development snapshot (commit 6860f82) Hi Bruce, thanks a lot for your feedback. I have added logging of extend ratio, when it is not 100%. Also I hope, I have enabled specification of ratio for given station/shot: extend <ratio> <from> <to> extend <ratio> <station> Allowing the form extend [left <ratio>] would be much more parsing. I have also changed the allowed range to 0 - 200%. Extend ratios are applied to splays also - but in this case - extend ratio of nearest shot is taken for splay. I think, this way it is OK. Could you please check whether it is working now as expected (commit c7d41d9 <https://github.com/therion/therion/commit/c7d41d96ebc47a652243711489813635e…> )? Thanks, S. On Wed, 12 Aug 2020 at 12:25, Bruce Mutton <bruce(a)tomo.co.nz <mailto:bruce@tomo.co.nz> > wrote: And it looks like the extend ratio is not reported when ‘log extend’ is set. It would be nice to have that if it is possible. Bruce From: Therion <therion-bounces(a)speleo.sk <mailto:therion-bounces@speleo.sk> > On Behalf Of Bruce Mutton Sent: Wednesday, 12 August 2020 22:18 To: 'List for Therion users' <therion(a)speleo.sk <mailto:therion@speleo.sk> > Subject: [Therion] Extended elevations - development snapshot (commit 6860f82) Stacho > there is a possibility to specify reduction ratio for extended elevation (0 = vertical, 100 = normal left/right) - just use "extend <number>" I have made this work, by placing ‘extend <number>’ statements in-line with the survey data, but that seems to be the only way it will work. Every combination I could think of with the extend controls in a separate centreline or block results in an error. For an example I have managed to make this extended centreline… …into this by using strategically placed ‘extend 50’, ‘extend 100’, and ‘extend 75’, as well as an ‘extend vertical’. It now matches more closely what one would expect by looking at the plan view. So it works very well, but the difficulty I have is that to make the extended elevation control manageable, it needs to be separated out (in one place) from the survey data, but now any control of the extend ratio must be in-line with the data. This makes it very confusing and difficult to manage. Is there any chance that the ratio could be controlled by statements in separate centrelines, as with left/right/vertical etc? Maybe by allowing the form ‘extend [left <ratio>] <station1> <station2>’ as an equivalent to the in-line statements ‘extend <ratio>’ and then ‘extend left’? (I am thinking of similar syntax to ‘export map -projection [elevation 290 deg]’ where the square brackets are required if the default is not what is wanted). The extend ratios are applied to splays as well as to legs, which is usually desirable, except sometimes where the ratio approaches zero. If the user is to control splay ratios separately to the legs, then I guess the only option is to put the extend ratio statements in-line. And one more thing. The range is limited from 0 to 100%. If we are going to allow distortion of the extended elevation, then I think the upper limit should be something like 150% or 200%. Bruce _______________________________________________ Therion mailing list Therion(a)speleo.sk <mailto:Therion@speleo.sk> https://mailman.speleo.sk/listinfo/therion

1 0

Extended elevations - development snapshot (commit 6860f82)
by Bruce Mutton 12 Aug '20

12 Aug '20

> there is a possibility to specify reduction ratio for extended elevation (0 = vertical, 100 = normal left/right) - just use "extend <number>" I have a project that is just perfect for this, but have not been able to make it work. I expect I have not understood how the syntax is intended to be used. The statements below relate to only a small part of the selected survey centreline, and cause this error ":\Program Files (x86)\Therion\therion.exe: error -- Extend-DwarfsDoorElevEXT.th [120] -- station doesn't exist - 1" If I remove the group endgroup pair, the project compiles just fine, however this branch (and the whole extended elevation) is compiled full size without the 85% reduction specified. The 'extend 85' statement is ignored. Also there seems to be a problem in that a group block is somehow cancelling the station-names specification (whether or not it is moved inside or outside of the group block). I have never really used group blocks, so am not familiar with their limitations. centreline group station-names []@D-K6 #DwarfsD-K6-Stream.th # now foreshorten this passage so station 13 appears near to station 2 (the red branch in the diagram below) # they could have been a loop, but the surveyor did not close to the same locations extend 85 extend left 1 endgroup endcentreline If I try extend 85 left 1 then I get the error "C:\Program Files (x86)\Therion\therion.exe: error -- Extend-DwarfsDoorElevEXT.th [120] -- unknown extend flag - 85" BTW I assume the reduction and the three-station path ignores will be reported when log extend is added to the thconfig? Bruce

3 5