February 2017 - Therion

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

Scale dependant error when using area fills
by Tom Foord 20 Jan '19

20 Jan '19

Hi all I'm having some problems compiling a project which includes debris area fills. Depending on the exact symbol fill that I use, I am getting strange scale-dependant errors which seem to cause the compiler to loop endlessly until I force it to stop. I originally noticed the problem when using a custom area fill that I made by modifying the standard a_debris_AUT symbol fill. I've attached my modified metapost definition in the attached text file 'a_debris_WUG.txt'. The error occurs for any scale between 1:2000 and 1:4483 (outside of this range the project compiles fine). See attached output log 'Output log - a_debris_WUG.txt'. As you can see, the file seems to loop over and over again. Initially I thought this problem was specific to my custom fill, but then I noticed that I also get a similar error when using the standard a_debris_AUT fill, however this time the error only occurs when the scale is set to exactly 1:2000 (any other scale seems to be fine). See attached output log 'Output log - a_debris_AUT.txt'. Can anyone help with this problem? Thanks Tom

9 21

Import a scrap into another scrap (or th2-file)
by torstein finnesand 11 Oct '17

11 Oct '17

Hi fellows, Sometimes I realize that two scraps should have been one (for instance scrap A in A.th2 should have been a part of scrap B in B.th2), in particular when it's difficult to join them. It's easy to insert the xvi file into the scrap B file. But I have to draw it again. Is there any workaround here? Torstein Finnesand Norway

8 14

Question/Problem with customizing text labels
by Torsten Schnitter 21 May '17

21 May '17

Hi all I have a question concerning customizing text labels. Drawing a map with scale 1:250 is ok. Just some points a very small on the map. Therefore I would like to resize these points and make them bigger. For example: "point x y passage-height -value [- 10 m]" generates the wanted symbol, a number with a frame around. But it's to small (attached picture passage-height-1.jpg). I add the option "-scale xl". Now it's a little bit bigger but still to small (attached picture passage-height-2.jpg). Finally I use within the layout command: code metapost fonts_setup(6,8,10,14,36); endcode Now the number is looking good in size but the frame around is not correct anymore (attached picture passage-height-3.jpg). Is there a solution for this problem? Or is there any other option to resize single points or lines (like "point passage-heigt" or "line label" ...)? I'm looking forward for any help. Thanks, Torsten

6 12

linux and distoX
by cawa.sorix＠gmail.com 06 Apr '17

06 Apr '17

Hello, I look for a software to use a distoX on linux, I found for windows, android, but nothing on linux. Do you know if a linux soft exist ? Thanks C.S.

3 3

Aven colour by loop error
by Bruce Mutton 05 Apr '17

05 Apr '17

Following on from this thread <https://www.mail-archive.com/therion@speleo.sk/msg04871.html> 2.5 yrs ago where I was asking about Therion support of Aven features. Therion files exported to .3d format now display 'colour by' depth, survey date, gradient and leg length when viewed with Aven. But not colour by loop error. Is 'colour by loop error' something that could readily be added to the Therion export? Bruce

6 17

Necessary packages to compile Therion on a Ubuntu machine
by Rodrigo Severo 06 Mar '17

06 Mar '17

Hi, Here is a list of packages necessary for compiling Therion on a Ubuntu 16.04 machine: apt install libvtk6-dev libwxgtk3.0 libfreetype6-dev build-essential wx3.0-headers libwxbase3.0-dev libglu1-mesa-dev mesa-common-dev bwidget feynmf libtk-img texlive-metapost It might save someone sometime. Regards, Rodrigo

8 14

Error visualisation data, drawing pdf
by Bruce Mutton 27 Feb '17

27 Feb '17

The thread 'Aven colour by loop error' resolved my initial query (I understand a solution has been pushed to the repo <https://www.mail-archive.com/therion@speleo.sk/msg06282.html> ), and then got a bit off topic and discussed centreline and drawing distortions as shown with 'debug', which seems to be not quite the same thing, so I have started a new topic here. I have used debug to troubleshoot gross drawing errors for one or two scraps at a time, but I have never considered that it might be useful to look at centrelines or whole drawing projects. It might not be, but I want to explore that here, because I don't understand it well. Maybe it would be good to come up with a layout that facilitates emphasising the debug information. I have added lots of links to this mail, so if your mail client has stripped the links, you will have to view it from the wiki start page or the mail archive https://www.mail-archive.com/therion@speleo.sk/ Therion's debug features are described in the wiki here <https://therion.speleo.sk/wiki/tbe:wiki5?s%5b%5d=debug#debug> a bit more fully than in the Therion Book. A clarification I would add to that description, is that there are black and yellow point pairs for each scrap (and centreline??) But there are some questions I have, like; What is the difference between debug on and debug all? (nothing that I have noticed) Why is there a debug off, and how would one use it? (unless one wants to be sure that the default 'off' is enforced, which is a good enough reason) Is it possible have debug all, but without the red first and blue second transformations? (I have partially achieved that I think, but my solution is not as good as Martin's) Orange points are described as points with maximal change in distance - I don't seem to have any orange dots, just lots of red dots located at every symbol. Are there really orange dots with the current Therion version? Is there one orange dot per scrap, or only one for the entire exported map? What are the meanings that can be gained from the yellow and black dot configurations? What I have deduced is; * Yellow dots over top of black dots indicates no distortion ie perfect. A small distance between yellow and black is good. * Length of parallel yellow and black lines has no meaning. Very short lines and very long lines can both occur where there is almost no distortion, and long lines can occur where there is distortion as well. * Yellow and black lines forming triangles, squares or other polygons typically means a significant distortion. To recap on the previous thread. Martin Sluka has provided some useful output examples. By the way, is it possible to create a Therion debug with the black, yellow and orange debug features, without the <https://www.mail-archive.com/therion@speleo.sk/msg06287.html> 'first', 'second' and 'scrap-names'? The question of removing the 'first' and 'second' morphing transformations is not answered, but reducing the text size by adjusting scales and base-scales is a good idea. Martin clarified that it would find typos like 1.23m, in place of 12.3m, although where there is no sketch and no loop, I cannot work out how Therion would know that. He posted 4 pairs of useful pdf examples showing errors with centrelines, although for some reason I cannot find the message in the mail-archive, so I have attached them to this message and copied Martin's example sketch and th file. survey error_visualization input nacrt.th2 centerline data normal from to tape compass clino ignoreall 1 2 11 45 -10 2 3 10.5 95 +10 no error #2 3 10.5 275 +10 backsight #2 3 1.05 95 +10 typo #2 3 10.5 65 +10 misreading 3 4 12 100 0 endcenterline endsurvey outputs without walls and with walls: Although the attached files appear to show pairs of outputs with only the centreline and 'centreline plus scrap' for comparison, they all have the label 'scrap 1' so the scraps are clearly present in the compilation for all examples, it's just that the walls are hidden somehow. I have tried to replicate this with one of my larger projects, and find the following anomalies. When I use the layout below, which essentially just hides the walls (or not), the yellow and black dots are positioned identically for each run, whereas Martins examples clearly show a distinction between 'centreline only' behaviour and ' centreline + scrap' behaviour. How have you hidden your walls Martin, such that they are ignored by the debug dots when hidden? Here is the layout I have used, and below that, screen grabs of pdf outputs; layout LayoutDistortion ## Hides most features and emphasises ??centreline and maximal ??drawing errors (but not ??loop errors) ## If used with or after other layouts then behaviour may not be consistent with this layout when used alone! ## Yellow/black spots indicate maximal distortion of scrap, regardless of whether line wall (scrap) is 'shown' below ## Enforce white background and passage infill to reduce colour confusion colour map-bg 100 #white colour map-fg 100 #white symbol-colour group all 1 #black symbols opacity 10 #mostly transparent debug all #turns on all debug options, for visible entities only ## Options to control text size ## Use scale base-scale pair to control text size ratios 2:1 to 10:1 OK scale 1 1000 base-scale 1 200 #set base-scale to smaller number to reduce text size (but increases relative yellow/black dot size) ## OR Use fonts_setup to control text size for xs s m l xl respectively # code metapost # fonts_setup(0.01,0.01,2,3,5); ## Hide features we don't want to see symbol-hide group all #hides ALL except passage infill colour, and preview-above, below symbol-show group cave-centreline symbol-show group surface-centreline symbol-show line map-connection symbol-hide group text ## If all rows below commented out, only these entities visible; ## - part centreline and yellow/black spots ## - scrap names ## - full centrelines and all station names for centrelines included in a map definition # symbol-show line wall #this adds scrap outlines and red/blue morphing lines to output # symbol-show point cave-station #optional, sets up for showing cave only # symbol-show point surface-station #optional, sets up for showing surface only # symbol-show point station #shows and labels all stations and red debug spots # symbol-show point station:fixed #shows and labels fixed stations only and red debug spots endlayout LayoutDistortion Thanks for reading this far! I would appreciate any corrections, clarifications, improvements or insights you may have. Bruce

2 4

xtherion: "Edit line" contextual menu for line points doesn't work
by Rodrigo Severo 27 Feb '17

27 Feb '17

Hi, I can't make any of xtherion's "Edit line" contextual menu options to work. When I right click on a line point and choose some of the "Edit line" submenu options nothing happens: no error, no change on the line, just the menu disappears. I have being trying to debug this for a while now. It's true that I spent more time learning Tcl/Tk than actually debuging but that's not that relevant ;) If I use the "Edit line" button menu on the right pane everything works as expected. I already found out that this menu's definition starts at me.tcl line 2102 and that it's attached to the contextual menu at me_cmds.tcl line 3414. I also found out that the actual command defined for each of "Edit line" menu isn't called at all when activated through the contextual menu. They are called just fine when they are activated from the side panel button menu. Any help? Suggestions? Pointers? Thanks in advance, Rodrigo

8 15

Re: [Therion] Aven colour by loop error
by Martin Sluka 23 Feb '17

23 Feb '17

By the way, is it possible to create a Therion debug with the black, yellow and orange debug features, without the ‘first’, ‘second’ and ‘scrap-names’? You may change it by scale and base-scale m

1 0