- Therion - speleo.sk

Re: [Therion] Trying to understand relation between select/unselect and export
by Martin Sluka 04 Mar '17

04 Mar '17

You are right, Rodrigo, "unselect" doesn't work in any way. Martin On Mar 03, 2017, at 12:59 PM, Rodrigo Severo via Therion <therion(a)speleo.sk> wrote: 2017-03-03 4:52 GMT-03:00 Benedikt Hallinger via Therion <therion(a)speleo.sk>: I do not think this is a bug. The way i understand (and use) is that with select/unselect you can define the data to export for one particular run of the compiler. So you can say "export all of this map, but exclude xyz". I understand your idea but can you present an working example of unselect actually unselecting a map? After Bruce called my attention to the fact that this issue has being dicussed before, I couldn't find an example of unselect making any difference in the final result. Rodrigo However, it would definitely be more comfortable to have it like discussed in this thread below. Am 2017-03-01 21:36, schrieb Rodrigo Severo via Therion: 2017-03-01 16:30 GMT-03:00 Bruce Mutton via Therion <therion(a)speleo.sk [8]>: There are many threads in this forum if you search for ‘unselect’. I have not researched it recently, and my lingering recollection is that it does not work as one might expect. Not sure I have ever managed a successful ‘unselect’. This 2013 post from Andrew Atkinson in response to Bertrand Hauser gives an explanation that seems plausible. https://www.mail-archive.com/therion@speleo.sk/msg04606.html [1] Yes Bruce. I believe you are right. I will try some little debugging on Therions code to see if I understand why thats happening. I dont think thats by design, it looks like a bug to me. Thanks Rodrigo FROM: Therion [mailto:therion-bounces@speleo.sk [3]] ON BEHALF OF Martin Sluka via Therion SENT: Thursday, 2 March 2017 8:11 AM TO: List for Therion users <therion(a)speleo.sk [4]> CC: Martin Sluka <martinsluka(a)mac.com [5]> SUBJECT: Re: [Therion] Trying to understand relation between select/unselect and export 1. 3. 2017 v 20:03, Rodrigo Severo via Therion <therion(a)speleo.sk [2]>: Its as if the first select mBartp@bart sticks and the unselect mBartp@bart later on doesnt change a thing. I always use # to comment selects I don’t want. It could be a bug. Martin _______________________________________________ Therion mailing list Therion(a)speleo.sk [6] https://mailman.speleo.sk/listinfo/therion [7] Links: ------ [1] https://www.mail-archive.com/therion@speleo.sk/msg04606.html [2] mailto:therion@speleo.sk [3] mailto:therion-bounces@speleo.sk [4] mailto:therion@speleo.sk [5] mailto:martinsluka@mac.com [6] mailto:Therion@speleo.sk [7] https://mailman.speleo.sk/listinfo/therion [8] mailto:therion@speleo.sk _______________________________________________ Therion mailing list Therion(a)speleo.sk https://mailman.speleo.sk/listinfo/therion _______________________________________________ Therion mailing list Therion(a)speleo.sk https://mailman.speleo.sk/listinfo/therion

2 2

Re: [Therion] Trying to understand relation between select/unselect and export
by Martin Sluka 03 Mar '17

03 Mar '17

select/unselect It doesn't work in this way too: source select_unselect.th select nacrt_12.map@select_unselect unselect scrap1@select_unselect export map -o select_unselect_1.pdf There is not any difference between compilation with line unselect or commented unselect. m.

1 0

Trying to understand relation between select/unselect and export
by Rodrigo Severo 03 Mar '17

03 Mar '17

Hi, I have a thconfig with the following exports: layout exploracao scale 1 200 base-scale 1 100 language pt code tex-map \framethickness=0.5mm sketches off legend on legend-width 21 cm legend-columns 3 statistics explo-length off endlayout layout aranha scale 1 200 base-scale 1 100 debug station-names language pt code tex-map \framethickness=0.5mm sketches off endlayout select mBartp@bart export map -projection plan -layout exploracao -layout extra_symbols -output Bart.pdf unselect mBartp@bart select mBartAranhap@bart export map -layout aranha -output Bart-centerline.pdf If I compile with the above settings I get the following 2 maps: Bart.pdf - https://goo.gl/zmnR3Y Bart-centerline.pdf - https://goo.gl/SaFF37 The first one is exactly what I expect but the second isn't as the second one should have only the centerline. If I comment the first 2 lines and run like this: #select mBartp@bart #export map -projection plan -layout exploracao -layout extra_symbols -output Bart.pdf unselect mBartp@bart select mBartAranhap@bart export map -layout aranha -output Bart-centerline.pdf I get the Bart-centerline.pdf as expected: https://goo.gl/dpZaEB Why is that? *unselect mBartp@bart* shouldn't remove mBartp@bart from the export? Rodrigo

4 11

test of data of old survey
by Martin Sluka 01 Mar '17

01 Mar '17

In attached PDF file is map for only polygon from data and map from year 1959. It is clear that there are problems in several shots (in green circles). m.s.

1 0

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

Colors and thickness for new symbols
by thomasschilter＠bluewin.ch 22 Feb '17

22 Feb '17

Dear Therion-Community I try to change some symbols on my layout. This works with most symbols. With two symbols I can not go any further. 1. With the symbol "Absatz Lehm" I can not transfer the color to the whole symbol. The symbol is similar to the line floorstep (Fig .: Legend_Linecolor). The base line takes the color brown, with the right-angled lines I have no idea that works: code metapost def l_u_absatz_lehm (expr P) = T:=identity; cas := 0; dlzka := arclength P; mojkrok:=adjust_step(dlzka, .5u); % Schraffurabstand eingeben pickup PenD; draw p withcolor (0.75,0.2,0.12); % not works!!! forever: t := arctime cas of P; mark_ (P,t,0.9u); cas := cas + mojkrok; exitif cas > dlzka + (mojkrok /3); % for rounding errors endfor; pickup PenC; thdraw P withcolor (0.75,0.2,0.12); % works enddef; initsymbol("l_u_absatz_lehm") def l_u_absatz_lehm_legend = l_u_absatz_lehm(((-.3,0.5) .. (.3,.3) .. (.7,.7) .. (1.3,.5)) inscale) enddef; endcode text de "line u:absatz_lehm" "Absatz Lehm" 2. The second symbol “phreatische Fliessrichtung” is only one line. However, I would like to place the symbol with the outline in the legend box. Compare with the figure Legend_Color_Pen. The outside lines should be gray and slightly thicker than the line in the middle. code metapost def l_u_phreatisch (expr P) = T:=identity; pickup PenC; thdraw P; enddef; initsymbol("l_u_phreatisch") def l_u_phreatisch_legend = l_u_phreatisch(((.25,.5){dir 300} .. (.65,.5)) inscale); l_u_phreatisch(((.4,1.0) .. (.2,.5){dir 270} .. (.1,0.0)) inscale) % must be grey (0.86, 0.86, 0.86) and PenA l_u_phreatisch(((.8,1.0) .. (.7,.5){dir 270} .. (.6,0.0)) inscale) % must be grey (0.86, 0.86, 0.86) and PenA enddef; endcode text de "line u:phreatisch" "phreatische Fliessrichtung" Does anyone know a solution? Thank you and best regards Thomas

1 0

Clino question
by Torsten Schnitter 22 Feb '17

22 Feb '17

Hi I get a strange problem with survey data and clino numbers. I can't figure out the error and therefore need any help or advice. I have to stations with this data: survey line_25 centreline -id "line_25" date 2014.09.23 cs lat-long walls on units compass degree data normal from to left right up down tape compass backcompass clino backclino .... IMO113 IMO114 0.0 0.0 0.0 0.0 58.7 132 309 0.5 -2.0 .... endcentreline endsurvey The output is shown in attached picture "Clino-Problem.jpg" which is elevation view of course. The problem is that this survey shot (grey line) is going much to high on the right side. The difference in height from left point to right point should be less than 1m (squares in background of image are 1m). I checked this with: sin(1.25°) x 58,7m = 1,28m. So the difference in height should be 1,28m. (The calculated average of clino should be 1,25°, shouldn't it!?) But the picture shows a difference of close to 5m related to the squares. To show this strange problem more easy I changed the clino and backclino numbers to 0 and expected a horizontal shot: survey line_25 centreline -id "line_25" date 2014.09.23 cs lat-long walls on units compass degree data normal from to left right up down tape compass backcompass clino backclino .... IMO113 IMO114 0.0 0.0 0.0 0.0 58.7 132 309 0.0 0.0 .... endcentreline endsurvey The output is shown in attached picture "Clino-Zero.jpg" and as you can see the shot is not horizontal. The difference in height is around 4m. But: sin(0°) x 58,7m = 0m. So the difference in height should be zero. So what I'm missing or doing wrong? Thanks for you help, Torsten

2 2

Translation doubt: what's a "clay-tree" point?
by Rodrigo Severo 22 Feb '17

22 Feb '17

Hi, I'm making a small revision on the translations I did yesterday. I'm not entirely satisfied with some of them. What's a "clay-tree" point? I couldn't find out even searching Google. Rodrigo

8 10