May 2018 - 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

TerrainTool
by Graham Mullan 28 Jun '19

28 Jun '19

Mike McCombe's TerrainTool has been fixed and is available again from http://www.ubss.org.uk/terraintool/terraintool.php Download and enjoy. It may not use the latest data but it remains the most straightforward way of adding topographic detail to Therion 3D models. Graham

8 30

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

Re: [Therion] Defining a user symbol that contains a short text string
by Dave Clucas 31 May '18

31 May '18

I think you may need to add the suffix to the label command. Eg. label.top (btex Gr etex, pos) rotated theta scaled sc aligned al Sorry, I can’t test it as I don’t have Therion installed. Sent from my iPhone > On 31 May 2018, at 10:20 AM, therion-request(a)speleo.sk wrote: > > Send Therion mailing list submissions to > therion(a)speleo.sk > > To subscribe or unsubscribe via the World Wide Web, visit > https://mailman.speleo.sk/listinfo/therion > or, via email, send a message with subject or body 'help' to > therion-request(a)speleo.sk > > You can reach the person managing the list at > therion-owner(a)speleo.sk > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Therion digest..." > > > Today's Topics: > > 1. Re: Defining a user symbol that contains a short text string, > Therion Digest, Vol 149, Issue 34 (Dave Clucas) > 2. Defining a user symbol that contains a short text string > (Bruce Mutton) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Wed, 30 May 2018 16:04:32 +0100 > From: Dave Clucas <dave.clucas(a)icloud.com> > To: therion(a)speleo.sk > Cc: Dave Clucas MY <dave.clucas(a)icloud.com> > Subject: Re: [Therion] Defining a user symbol that contains a short > text string, Therion Digest, Vol 149, Issue 34 > Message-ID: <5ACA36E2-6146-4525-8F3A-EC0CEA639FBC(a)icloud.com> > Content-Type: text/plain; charset="utf-8" > > Bruce, read this > > 3.6 Text > > You have already seen how the dotlabel command can be used to draw a dot and a label in the neighborhood of the dot. If you do not want the dot, simply use the label command: > > label.suffix(string expression, pair); > > It uses of the same suffices as the dotlabel command to position the label relative to the given pair. No suffix means that the label is printed at the specified location. The directives rt (right), urt (upper right), top (top), ulft (upper left), lft (left), llft (lower left), bot (bottom), lrt (lower right) can be used to specify the relative position of the label to the given pair. The distance from the pair to the label is set by the numeric variable labeloffset. > > The commands label and dotlabel both use a string expression for the label text and typeset it in the default font, which is likely to be "cmr10" and which can changed through the variables defaultfont and defaultscale. For example, > > defaultfont := "tir"; > defaultscale := 12pt/fontsize(defaultfont); > makes labels come out as Adobe Times-Roman at about 12 points. > > Until now the string expression in a text command has only been a string delimited by double quotes (optionally joined to another string via the concatenation operator &). But you can also bracket the text with btex and etex (do not put it in quotes this time) and pass it to TEX for typesetting. This allows you to use METAPOST in combination with TEX for building complex labels. Let us begin with a simple example: > > beginfig(1); > z0 = (0,0); z1 = (sqrt(3)*cm,0); > z2 = (sqrt(3)*cm,1cm); > draw z0--z1--z2--cycle; > label.bot(btex $\sqrt{3}$ etex, 1/2[z0,z1]); > label.rt(btex 1 etex, 1/2[z1,z2]); > label.top(btex 2 etex, 1/2[z0,z2]); > endfig; > end; > > Dave Clucas > dave.clucas(a)icloud.com <mailto:daveclucas@icloud.com> > > Exploring the World - One cave at a time > > >> On 30 May 2018, at 11:00, therion-request(a)speleo.sk wrote: >> >> Send Therion mailing list submissions to >> therion(a)speleo.sk >> >> To subscribe or unsubscribe via the World Wide Web, visit >> https://mailman.speleo.sk/listinfo/therion >> or, via email, send a message with subject or body 'help' to >> therion-request(a)speleo.sk >> >> You can reach the person managing the list at >> therion-owner(a)speleo.sk >> >> When replying, please edit your Subject line so it is more specific >> than "Re: Contents of Therion digest..." >> >> >> Today's Topics: >> >> 1. Defining a user symbol that contains a short text string >> (Bruce Mutton) >> >> >> ---------------------------------------------------------------------- >> >> Message: 1 >> Date: Tue, 29 May 2018 22:14:55 +1200 >> From: "Bruce Mutton" <bruce(a)tomo.co.nz> >> To: "'List for Therion users'" <therion(a)speleo.sk> >> Subject: [Therion] Defining a user symbol that contains a short text >> string >> Message-ID: <000401d3f735%24e5d86d90%24b18948b0%24(a)tomo.co.nz> >> Content-Type: text/plain; charset="utf-8" >> >> Good evening >> >> I'd like to make a user defined symbol that is simply an ascii text string. >> A quick and dirty adhoc symbol if you like. If I was going to be fancy, I >> would add a box around it like in the example of Dave Clucas that I have >> copied and modified below. >> >> >> >> So rather than defining the shape of the omega symbol using metapost, I'd >> like to hard code an ascii character, say "E". >> >> The yellow shaded text below needs to be replaced with some simple metapost, >> but I am too lazy to research and trial things. >> >> I notice that other examples tend to use a copy of the p_label definition, >> and modify that. I would rather not head down that route, as then my custom >> code would overwrite potential future improvements to Therion's source code. >> >> >> >> >> My plan is not really to create an alternative to the entrance symbol, but >> rather to create a template quick and dirty creation of single use or >> unusual symbols, that can be enumerated in the legend. >> >> >> >> Does anyone happen to know how to modify the code below to do what I >> describe? >> >> >> >> Thanks >> >> Bruce >> >> >> >> >> <https://therion.speleo.sk/wiki/_detail/metapost:entrancesymbol.png?id=metap >> ost> >> >> code metapost >> >> def p_u_ent (expr pos,theta,sc,al)= >> >> U:=(.2u,.5u); >> >> T:=identity aligned al rotated theta scaled sc shifted pos; >> >> path p; >> >> p = (-.3u,-.25u) -- (-.2u,-.25u){dir 135} .. (0u, .25u) .. {dir >> 225}(.2u,-.25u) -- (.3u,-.25u); % define omega shape >> >> thdraw p withpen PenA; % draw it with fat pen >> >> thdraw unitsquare scaled u shifted (-0.5u,-0.5u) rotated 45 withpen PenD; >> % diagonal box with thin pen >> >> enddef; >> >> >> >> initsymbol("p_u_ent") >> >> def p_u_ent_legend = >> p_u_ent( <I forget where to find code for point drawing in the >> legend> ) >> enddef; >> endcode >> text en "point u:ent" "E for entrance" #text to appear in legend >> >> >> >> >> >> >> >> >>

1 0

Defining a user symbol that contains a short text string
by Bruce Mutton 31 May '18

31 May '18

Thanks to Dave I did a little reading, and have come up with a partial solution. In the screenshot below, the top line shows that . point 0 0 u:graffiti -align b (or centre or t) works correctly. The second line shows that -scale xs, s, l and xl work OK for the circle and box, but not the label. Similar for -orientation (rotation) on the third line. For some reason the centre of the scale and rotation transformation is in the wrong place for the label. There is something I am doing wrong with the label part of the symbol definition. Any ideas? My code so far looks like. code metapost def p_u_graffiti (expr pos,theta,sc,al)= U:=(.2u,.5u); T:=identity aligned al rotated theta scaled sc shifted pos; %# pos and al work fine in label below, but theta and sc transformed about far off point??? label (btex Gr etex, pos) rotated theta scaled sc aligned al; % btex and etex are wrappers around code to be process by tex thdraw unitsquare scaled u shifted (-0.5u,-0.5u) rotated 45 withpen PenD; % diagonal box with thin pen thdraw fullcircle scaled u withpen PenD; enddef; initsymbol("p_u_graffiti") text en "point u:graffiti" "Historic graffiti" Bruce From: Bruce Mutton <bruce(a)tomo.co.nz> Sent: Tuesday, 29 May 2018 10:15 PM To: 'List for Therion users' <therion(a)speleo.sk> Subject: Defining a user symbol that contains a short text string Good evening I'd like to make a user defined symbol that is simply an ascii text string. A quick and dirty adhoc symbol if you like. If I was going to be fancy, I would add a box around it like in the example of Dave Clucas that I have copied and modified below. So rather than defining the shape of the omega symbol using metapost, I'd like to hard code an ascii character, say "E". The yellow shaded text below needs to be replaced with some simple metapost, but I am too lazy to research and trial things. I notice that other examples tend to use a copy of the p_label definition, and modify that. I would rather not head down that route, as then my custom code would overwrite potential future improvements to Therion's source code. My plan is not really to create an alternative to the entrance symbol, but rather to create a template quick and dirty creation of single use or unusual symbols, that can be enumerated in the legend. Does anyone happen to know how to modify the code below to do what I describe? Thanks Bruce <https://therion.speleo.sk/wiki/_detail/metapost:entrancesymbol.png?id=metap ost> code metapost def p_u_ent (expr pos,theta,sc,al)= U:=(.2u,.5u); T:=identity aligned al rotated theta scaled sc shifted pos; path p; p = (-.3u,-.25u) -- (-.2u,-.25u){dir 135} .. (0u, .25u) .. {dir 225}(.2u,-.25u) -- (.3u,-.25u); % define omega shape thdraw p withpen PenA; % draw it with fat pen thdraw unitsquare scaled u shifted (-0.5u,-0.5u) rotated 45 withpen PenD; % diagonal box with thin pen enddef; initsymbol("p_u_ent") def p_u_ent_legend = p_u_ent( <I forget where to find code for point drawing in the legend> ) enddef; endcode text en "point u:ent" "E for entrance" #text to appear in legend

1 0

Re: [Therion] Defining a user symbol that contains a short text string, Therion Digest, Vol 149, Issue 34
by Dave Clucas 30 May '18

30 May '18

Bruce, read this 3.6 Text You have already seen how the dotlabel command can be used to draw a dot and a label in the neighborhood of the dot. If you do not want the dot, simply use the label command: label.suffix(string expression, pair); It uses of the same suffices as the dotlabel command to position the label relative to the given pair. No suffix means that the label is printed at the specified location. The directives rt (right), urt (upper right), top (top), ulft (upper left), lft (left), llft (lower left), bot (bottom), lrt (lower right) can be used to specify the relative position of the label to the given pair. The distance from the pair to the label is set by the numeric variable labeloffset. The commands label and dotlabel both use a string expression for the label text and typeset it in the default font, which is likely to be "cmr10" and which can changed through the variables defaultfont and defaultscale. For example, defaultfont := "tir"; defaultscale := 12pt/fontsize(defaultfont); makes labels come out as Adobe Times-Roman at about 12 points. Until now the string expression in a text command has only been a string delimited by double quotes (optionally joined to another string via the concatenation operator &). But you can also bracket the text with btex and etex (do not put it in quotes this time) and pass it to TEX for typesetting. This allows you to use METAPOST in combination with TEX for building complex labels. Let us begin with a simple example: beginfig(1); z0 = (0,0); z1 = (sqrt(3)*cm,0); z2 = (sqrt(3)*cm,1cm); draw z0--z1--z2--cycle; label.bot(btex $\sqrt{3}$ etex, 1/2[z0,z1]); label.rt(btex 1 etex, 1/2[z1,z2]); label.top(btex 2 etex, 1/2[z0,z2]); endfig; end; Dave Clucas dave.clucas(a)icloud.com <mailto:daveclucas@icloud.com> Exploring the World - One cave at a time > On 30 May 2018, at 11:00, therion-request(a)speleo.sk wrote: > > Send Therion mailing list submissions to > therion(a)speleo.sk > > To subscribe or unsubscribe via the World Wide Web, visit > https://mailman.speleo.sk/listinfo/therion > or, via email, send a message with subject or body 'help' to > therion-request(a)speleo.sk > > You can reach the person managing the list at > therion-owner(a)speleo.sk > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Therion digest..." > > > Today's Topics: > > 1. Defining a user symbol that contains a short text string > (Bruce Mutton) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Tue, 29 May 2018 22:14:55 +1200 > From: "Bruce Mutton" <bruce(a)tomo.co.nz> > To: "'List for Therion users'" <therion(a)speleo.sk> > Subject: [Therion] Defining a user symbol that contains a short text > string > Message-ID: <000401d3f735%24e5d86d90%24b18948b0%24(a)tomo.co.nz> > Content-Type: text/plain; charset="utf-8" > > Good evening > > I'd like to make a user defined symbol that is simply an ascii text string. > A quick and dirty adhoc symbol if you like. If I was going to be fancy, I > would add a box around it like in the example of Dave Clucas that I have > copied and modified below. > > > > So rather than defining the shape of the omega symbol using metapost, I'd > like to hard code an ascii character, say "E". > > The yellow shaded text below needs to be replaced with some simple metapost, > but I am too lazy to research and trial things. > > I notice that other examples tend to use a copy of the p_label definition, > and modify that. I would rather not head down that route, as then my custom > code would overwrite potential future improvements to Therion's source code. > > > > > My plan is not really to create an alternative to the entrance symbol, but > rather to create a template quick and dirty creation of single use or > unusual symbols, that can be enumerated in the legend. > > > > Does anyone happen to know how to modify the code below to do what I > describe? > > > > Thanks > > Bruce > > > > > <https://therion.speleo.sk/wiki/_detail/metapost:entrancesymbol.png?id=metap > ost> > > code metapost > > def p_u_ent (expr pos,theta,sc,al)= > > U:=(.2u,.5u); > > T:=identity aligned al rotated theta scaled sc shifted pos; > > path p; > > p = (-.3u,-.25u) -- (-.2u,-.25u){dir 135} .. (0u, .25u) .. {dir > 225}(.2u,-.25u) -- (.3u,-.25u); % define omega shape > > thdraw p withpen PenA; % draw it with fat pen > > thdraw unitsquare scaled u shifted (-0.5u,-0.5u) rotated 45 withpen PenD; > % diagonal box with thin pen > > enddef; > > > > initsymbol("p_u_ent") > > def p_u_ent_legend = > p_u_ent( <I forget where to find code for point drawing in the > legend> ) > enddef; > endcode > text en "point u:ent" "E for entrance" #text to appear in legend > > > > > > > > >

1 0

Defining a user symbol that contains a short text string
by Bruce Mutton 29 May '18

29 May '18

Good evening I'd like to make a user defined symbol that is simply an ascii text string. A quick and dirty adhoc symbol if you like. If I was going to be fancy, I would add a box around it like in the example of Dave Clucas that I have copied and modified below. So rather than defining the shape of the omega symbol using metapost, I'd like to hard code an ascii character, say "E". The yellow shaded text below needs to be replaced with some simple metapost, but I am too lazy to research and trial things. I notice that other examples tend to use a copy of the p_label definition, and modify that. I would rather not head down that route, as then my custom code would overwrite potential future improvements to Therion's source code. My plan is not really to create an alternative to the entrance symbol, but rather to create a template quick and dirty creation of single use or unusual symbols, that can be enumerated in the legend. Does anyone happen to know how to modify the code below to do what I describe? Thanks Bruce <https://therion.speleo.sk/wiki/_detail/metapost:entrancesymbol.png?id=metap ost> code metapost def p_u_ent (expr pos,theta,sc,al)= U:=(.2u,.5u); T:=identity aligned al rotated theta scaled sc shifted pos; path p; p = (-.3u,-.25u) -- (-.2u,-.25u){dir 135} .. (0u, .25u) .. {dir 225}(.2u,-.25u) -- (.3u,-.25u); % define omega shape thdraw p withpen PenA; % draw it with fat pen thdraw unitsquare scaled u shifted (-0.5u,-0.5u) rotated 45 withpen PenD; % diagonal box with thin pen enddef; initsymbol("p_u_ent") def p_u_ent_legend = p_u_ent( <I forget where to find code for point drawing in the legend> ) enddef; endcode text en "point u:ent" "E for entrance" #text to appear in legend

1 0

Help With Huge Survey File
by Nick Bairstow 28 May '18

28 May '18

Somebody has sent me a project folder which contains one huge survey (6k+) made with Pocket Topo. It seems they had only partial knowledge on how to survey a cave of this size and only limited experience of Therion so the whole thing is a bit weird. I said I would attempt to sort it out. Andrew fixed one issue with the data which has moved us forward but my question now is how to proceed. If I compile I can get .3d and .lox output which seems to work fine but the pdf output fails with a load of complaints. Looks like a size thing to me but having never seen this before I'm not sure. To me the survey needs breaking up but again I am not sure of the best way to do this, can some of you clever chaps have a look and possibly offer advise please. Be warned the th2 is difficult to handle my machine takes 3-4 mins just to load it and 2mins to refresh if I adjust the zoom. The guys who collected the data spent an awful long time doing so and are obviously keen to use this data as redoing the survey is not an option. It is quite an interesting problem and a very good example of how not to do things. Any comments or involvement would be appreciated. Nick

5 11

Remove individual symbols from legend
by Bruce Mutton 28 May '18

28 May '18

It's winter here so I'm drawing maps. >From time to time I don't want particular symbols to turn up in the legend. Is it possible to turn off individual legend symbols, relatively easily with a layout statement? For example if I want border variants to be removed from the legend? And just on the off chance. has anyone come up with metapost for a line root (a root that travels along the floor)? Bruce

2 3

Wrong average calculation from compass/backcompass data
by Bruce Mutton 27 May '18

27 May '18

I agree to some extent with both sentiments below, however the software should not abort just because of backsight discrepancies. What about adding one more line to the Therion and or Survex log file; either "There are no backsights in the centreline", or "Maximum backsight discrepancy is xx [degrees|grads]", as approprite That way the user can be fully informed and make their own decision about whether to investigate further if the information is not what they expect. Bruce 17. 5. 2018 v 9:25, Evaristo Quiroga via Therion <therion(a)speleo.sk <mailto:therion@speleo.sk> >: In this case is not a problem with my formula, is a serious magnetic anomaly (100 degrees difference) and the program should to stop and to send a warning. Evaristo, Therion is a program to interprete your data, not to solve problems with your data. It is your responsibility what the data you import into Therion. Martin S.

2 1