June 2019 - 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

"\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

extend
by Marco Corvi 02 Jun '20

02 Jun '20

i think that extend should take values in the interval [-1,1], ie also fractional values, plus some special value such as "ignore" to open loops, and "undefined" to let the program choose, because it's a nuisance to enter a decimal number for every shot (legs + splays). therion uses the left/right normal/reverse etc. solution, and users should be allowed to set extend also for splays, if they need to. for now, let's use left/right/vert, and ignore only to open loops btw, are vertical extend considered in the computation of the cave length by therion ? marco

5 6

World Magnetic Model
by kevin dixon 28 Feb '20

28 Feb '20

The last Therion release 5.4.3 is dated 01 Feb 2019. There has in recent years been a significant change of the Magnetic North Pole location, less so for the Geomagnetic South Pole: https://ngdc.noaa.gov/geomag/GeomagneticPoles.shtml Given the above, an out of cycle World Geomagnetic Model WMM2015v2 was released 04 Feb 2019. When will this update appear in Survex and Therion ? Thanks, Kevin Dixon

4 4

maps on off feature characteristics
by Bruce Mutton 08 Oct '19

08 Oct '19

I've just been playing with the new maps on/off feature a little more. These are just some observations. There seems to be a bug regarding map altitudes in all cases, and scrap altitudes where the scraps are empty. On the other hand it is a good way to highlight the existence of empty scraps! The notes below may not be particularly coherent, but together with the attached log files, you should be able to figure out what is going on. Setting maps to off quadruples compile time and increases pdf size by 15 times (not sure why that should be). Maps off On running a project with 614 scraps reported; This log entry was caused by an empty scrap definition, regardless of whether the empty scrap appears in a map definition S -899999999999999990000000000000000000000000000000000000000000000000000000000 0000000000000000000000000.00 04-BangAndBeyondPlan-s2@BlackSabbath () ie scrap 04-BangAndBeyondPlan-s2 -projection plan -scale [0 0 787.4 787.4 0 0 10 10 m] endscrap It seems I have 16 empty scraps in that project, a legacy of using topparser, and not always using all of the scrap definitions that it creates. Maps on On running same project with 254 scraps/maps reported; 1. Empty Scrap causes map that contains it not to appear in log, sometimes 04-BangAndBeyondPlan-s2@BlackSabbath is empty and for some reason the following map is not reported in the log file at all. map 04-BangAndBeyondPlan -title "04 beyond the capped rock - black sabbath plan" -projection plan 04-BangAndBeyondPlan-s1 04-BangAndBeyondPlan-s2 endmap 2. All maps are reported with elevation of; M -899999999999999990000000000000000000000000000000000000000000000000000000000 0000000000000000000000000.00 3. Unexplained empty 'scrap' reported at high altitude. Looking at my data, I cannot explain why this might happen. In the 254 lines, there are only two of these. M -899999999999999990000000000000000000000000000000000000000000000000000000000 0000000000000000000000000.00 61-AngelicaPlan@MiddleEarth (61 Angelica plan) S 473.40 61-AngelicaPlan-s1@MiddleEarth () S 489.54 61-AngelicaPlan-s2@MiddleEarth () S 1219.69 @ () map 61-AngelicaPlan -title "61 Angelica plan" -projection plan 61-AngelicaPlan-s1 #9C start surveying up pitch 61-AngelicaPlan-s2 # to base of 20C endmap 4. Similar things happen with projected elevation outputs, but there are many more of empty report lines, as in 3. above, and the altitudes reported seem somewhat random and just wrong. I wonder if the altitudes are really some measure of distance into or out of the 'page'? Behaviours seem to be the same whether maps or atlas are exported. Very nice for disabling passage offsets and previews. Bruce

5 12

Re: [Therion] Therion 5.4.2. potential bug
by Martin Budaj 31 Jul '19

31 Jul '19

On Sat, Jan 12, 2019 at 10:51 AM Michael <knollesimage(a)t-online.de> wrote: > I have now attached a minimal cave sample produced with 5.4.1. and one > produced with 5.4.2. to demonstrate the displacement. > Hi, the problem is that EPSG:31467 projection uses the "potsdam" datum and the PROJ library used by Therion changed the way how to transform potsdam datum to the standard WGS84 datum – it switched from a simple string parameter (towgs84) to using external grid file (see https://proj4.org/resource_files.html#transformation-grids for examples). No grid files are currently included in the windows Therion distribution, so the transformation is not correct in 5.4.2. Therion needs to be modified to include and use those files – hopefully soon. Best regards Martin

5 8

Page Size
by Markus Boldt 31 Jul '19

31 Jul '19

Hello, how is it possible to "say" Therion to make a PDF-File with for example a Size of DIN A4 (21 x 29,7 cm)? I have tried Page-setup 21 29.7 20 29 0.1 0.1 cm it doesn`t work I have tried Size 21 29.7 cm It doesn`t, too The command is ignored. Greetings Markus

4 5

Loch fails on Fedora 30
by Bill Gee 17 Jul '19

17 Jul '19

Hello everyone - I just noticed that Loch no longer works on Fedora 30. I use the version that is packaged by JM Begley. Launching from a KDE menu spins an hourglass for about 2 seconds and then goes away. When launched from a command shell, the only output is "Error: glXCreateContext failed". This happens on both my laptop and desktop, which have two different display drivers. It also happens on a VirtualBox guest. Is there a way to get a more detailed log file? Thanks! -- Bill Gee

3 4

Re: [Therion] maps on off feature characteristics
by Bruce Mutton 30 Jun '19

30 Jun '19

After a bit more experimentation with a smaller project. I think this situation arises from a map made from two survey centrelines (no scraps or maps in the map definition). With maps on M -899999999999999990000000000000000000000000000000000000000000000000000000000 0000000000000000000000000.00 DwarfsDoorElev290Map@ (Dwarfs Door<br>Elevation looking 290 deg) S 749.01 @ () S 732.25 @ () With maps off S -899999999999999990000000000000000000000000000000000000000000000000000000000 0000000000000000000000000.00 @ () So the code needs to test for and either filter out centrelines and maps comprised only of centrelines, or better, correctly determine their name and namespace. Bruce

1 0

maps on off feature characteristics
by Bruce Mutton 29 Jun '19

29 Jun '19

In case anyone is interested, I have updated my standard commentary in my thconfig template, to account for the new 'maps' switch, as below. And I have some more observations on 'maps' behaviour below that. ##SELECT SURVEY AND OR MAP OBJECTS to prepare for output #======================================================= # Default (nothing) selects all surveys/maps in 'sources'. # If a unique survey or map title can be inferred, map header includes the 'title' # List the specific surveys and or map objects that you wish to export # If no surveys are selected, then 'survey type exports' will include ALL surveys in 'sources' # If no map objects are selected, then 'map object type exports' will include ALL map objects in 'sources' # Surveys and map object selections are independent, the selections and outputs of one type have NO EFFECT on the other # For this reason, unless all surveys and all maps are (drawn and) selected, or # unless selected map(s) are defined with an associated 'survey <id>' option, # reported statistics for the different outputs almost always differ from each other. # select NameOfCavePlan # select NameOfCaveElevEXT maps on # [on] off ## Setting maps to off disables all previews and offsets, and only scraps from the selected maps are output. Survey centrelines included as part of a map definition are not output. # As at Jun2019, maps off significantly increases compile time and pdf file size To demonstrate those last points, here is a work in progress including a selected map that includes a survey centreline with 'maps on'. Here is the same selected map including the same selected centreline with 'maps off'. The centreline component of the map definition is not output, which is consistent with the stated behaviour in the Therion Book that only scraps are output, but not necessarily what I was expecting. It is a good behaviour though, as the general combination of effects is to simplify the output. Still not sure why an output that contains less (no previews, no map-connections, less centreline) should be 15x bigger in file size. Interesting that the colouring differs between the two examples, as they are coloured by altitude, and nothing else has changed between compiles. Here are log file excerpts that show that the scrap altitudes are unchanged, although Therion has reordered them. With 'maps off' they appear in order of altitude, and with 'maps on' they are in the order that they appear in the map definition (or is that a coincidence?). Maps Off Maps On I have not shown the map lines for the 'maps on' case here, but it is interesting that the maps comprised of centrelines only do not even appear in any of the log files. It looks to me like the maps are listed in order of average altitude (highest at top) when 'maps on' is set, but it is hard to tell, because at present they all report the altitude as -8999 etc. Bruce

1 0