December 2018 - Therion

Re: [Therion] Volume Calculation - Therion Digest, Vol 156, Issue 13
by Dave Clucas 16 Dec '18

16 Dec '18

In Loch export as a vtk file and open in Matlab. In Matlab you can get the volume of the model. Dave Clucas dave.clucas(a)icloud.com <mailto:daveclucas@icloud.com> Exploring the World - One cave at a time > On 16 Dec 2018, at 19: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. Lox model volume calculation (chris pennos) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Fri, 14 Dec 2018 16:10:02 +0000 > From: chris pennos <pennos4(a)hotmail.com> > To: "therion(a)speleo.sk" <therion(a)speleo.sk> > Subject: [Therion] Lox model volume calculation > Message-ID: > <AM0PR10MB2212DDD87B752C2ECF9FC9D8F2A10(a)AM0PR10MB2212.EURPRD10.PROD.OUTLOOK.COM> > > Content-Type: text/plain; charset="us-ascii" > > Anyone knows how to calculate the volume of a .lox model? > > Thanks in advance > > > ------------------------------ > > Subject: Digest Footer > > _______________________________________________ > Therion mailing list > Therion(a)speleo.sk > https://mailman.speleo.sk/listinfo/therion > > > ------------------------------ > > End of Therion Digest, Vol 156, Issue 13 > ****************************************

1 0

Lox model volume calculation
by chris pennos 16 Dec '18

16 Dec '18

Anyone knows how to calculate the volume of a .lox model? Thanks in advance

2 2

Therion Window gets smaler every time you compile
by Torsten Schnitter 10 Dec '18

10 Dec '18

Hi I'm using Therion 5.4.1+3bee73c on Windows 7. But also tested with 5.4.1+975063a and same.behaviour Every time when I click on "Compile" (or use F9 instead) the window from Therion get's a bit smaller in size (up down direction). Is there a fix for that? regards, Torsten

2 2

topodroid to therion
by Marco Corvi 04 Dec '18

04 Dec '18

Is there a workflow that is easy to use with ‘TopoDROID to Therion’ process, that also allows more than one scrap per survey trip file? With limited experimentation (and making assumption that TopoDROID ‘sketches’ might be approximately equivalent to Therion ‘scraps’), I have not yet found a way that is easy to implement and encourages a naming convention that eases tracing of scraps to their parent TopoDROID file. And breaking existing scraps into smaller scraps is a task I find unnecessarily tedious, when one could just have drawn smaller scraps in the first place. Am I missing something obvious? What are experienced Therion users who subsequently became proficient with TopoDROID as a data collector doing in this space? -------------------------- topodroid has many features requested by users that probably use other programs than therion to draft their cave maps, anyways, i use therion for my cave maps, and here is what i do. (0) a note3 with a stylus: reasonable compromise between the size of the android and that of the caves (lucky surveyors might go for a 7" tablet) (1) enable only drawing tools that are supported by therion, otherwise i must go for metapost code (2) each topodroid survey can have many sketches, and i usually draw several sketches, except for very simple surveys. (3) switch off fractional 'extend" (4) switch off loop closure compensation: better see potential blunders (5) i usually use "normal" line style, and the decimation button to simplify them (if need arises) (6) pre-exporting: check every sketch with joining sketches using the sketch outline feature, and make then fit nicely (7) it may happen that a sketch needs to be splitted in two, but this is rare as i'm used to draw small sketches. i never user sketch merge (8) i use automatic station points, even if, unfortunately, topodroid puts in all the stations in the convex hull of the sketch, and there can happen spurious ones. i do not remember if midline hide helps for this, however, midline hide is something i use only when the midline is very messy, i usually go over the station points and remove those that do not belong to the piece of midline of the skatch: this is easily done with a "good" text editor (9) i usually do not use "line continuation", but i fix the gaps between wall lines with point line editings (snap to point and merge with line). i sometimes use the feature that shifts a portion of a line, but i find often easier to redraw the line and erase the old one. (10) i have the feeling that outline is no longer very important to therion (it is however for csurvey, but this is ot on this list), thus i do not pay much attention that wall lines are properly oriented. anyways when i notice a line should be reversed i do it, as it's quick (11) automatic export because it's a nuisance to export each sketch (12) ... other things i do not recall at the moment marco

3 2

topodroid to therion
by Marco Corvi 04 Dec '18

04 Dec '18

*The meaning I meant to convey was; I don’t think I have seen a description of exactly the settings and workflow TopoDROID users should use if they want to export their data for Therion to process, in one place, and step by step. No doubt the detail is in the TopoDROID user manual, but it is scattered around, and interspersed with information that is not particularly useful for Therion users.* bruce, you are right. i misunderstood. a therion wiki page, a sort of "howto use topodroid for therion", is probably a good idea *And little indication of what settings will make life pleasant or unpleasant for Therion users. Many of the default settings seem to be Therion unfriendly, as evidenced by the examples posted on the Therion forum over the previous year or so, and my own subsequent experimentations.* this is probably because the default values of topodroid settings try to fit the average cave surveyor/cartographer, and only a minority of them uses therion. anyways, i think that the therion-relevant settings are only a few *I suspect what is missing is a user guide that describes what to do to ensure a pleasant Therion experience with data generated by TopoDROID. Your post from 3-4 December is the first time I recall seeing such a targeted user guide format, and I am wondering if a Therion wiki page based on your post might fill that gap. * however, i do not expect my way to be the best and the only one. i do not think there is a definitive way to work from topodroid to therion. the process depends also on the environment (=cave) and resources (=android device/distox). the wiki page might provide general rules and point to program features that are important for the drafting of maps with therion and cave project managing. * I am happy to create the outline of a wiki page and fit it into the Therion wiki structure somehow. If I start something, maybe someone else can fill in the gaps* as i said, i think it's a good idea. do it. and i hope other users add in their advices marco

1 0

topodroid to therion
by Bruce Mutton 04 Dec '18

04 Dec '18

Hi Marco Ah, so midline = the set of legs = centreline! >>That is a good description. I can see a wiki page developing from it. I don’t think I have seen similar information before? > that info is in the user manual, more or less The meaning I meant to convey was; I don’t think I have seen a description of exactly the settings and workflow TopoDROID users should use if they want to export their data for Therion to process, in one place, and step by step. No doubt the detail is in the TopoDROID user manual, but it is scattered around, and interspersed with information that is not particularly useful for Therion users. And little indication of what settings will make life pleasant or unpleasant for Therion users. Many of the default settings seem to be Therion unfriendly, as evidenced by the examples posted on the Therion forum over the previous year or so, and my own subsequent experimentations. I suspect what is missing is a user guide that describes what to do to ensure a pleasant Therion experience with data generated by TopoDROID. Your post from 3-4 December is the first time I recall seeing such a targeted user guide format, and I am wondering if a Therion wiki page based on your post might fill that gap. I am happy to create the outline of a wiki page and fit it into the Therion wiki structure somehow. If I start something, maybe someone else can fill in the gaps? Regards Bruce

1 0

topodroid to therion
by Marco Corvi 03 Dec '18

03 Dec '18

i apologize the cut-n-paste, but i get post in digest and i try to keep reply short. - - - - - - That is a good description. I can see a wiki page developing from it. I don’t think I have seen similar information before? that info is in the user manual, more or less It is a while since I played with TopoDROID. Is it the intention that one TopoDROID sketch produces, or is equivalent to, one matching pair of Therion scraps (plan and elevation)? yes, initially sketches were saved as th2 files. then i realized users were drawing huge sketches (well over 1 km), so i turned to a binary format (and a cache) to speed up opening (and saving) the sketches I am interested in the data naming conventions you use, to facilitate the tracing of parent and child object relationships (ie data files (TopoDROID and Therion) through to survey and scrap, for example). the survey name is the base name. sketches append their name to that of the survey, separated by a dash, and with suffix 'p' or 's' survey name and sketch names can be chosen by the user (topodroid suggest numbers for sketch names). cross-section names are chosen by topodroid (eg "xx1" etc; there are four patterns, if i'm not mistaken, for four different types of cross-section) scraps take the name from the file the xvi scale is almost 1:39.37 (the exact number is somewhere in therion sources) an exported data file (.th) contains input for all its sketches (.th2 files), and map commands. however these are all under comment. topodroid does not create the thconfig file And I should just check exactly what you mean by ‘mid-line’? I have always been guessing. Is it the survey shot line that goes from ‘from station’ to ‘to station’? midline = the set of legs marco

1 0

locating where scrap outline intersects itself, and understanding the metapost log
by Thorir Jonsson 03 Dec '18

03 Dec '18

Hi! I'm still having issues generating a pdf from my survey. Maybe it is because of the size of the scrap but I have not yet figured out how to work with multiple scraps so I hope I can make this work as a single scrap. The metapost log tells me that the scrap outline intersects itself, but does not give any indication of where this happens. How can I find out what is amiss? Right after the outline intersecting error I get the following: ! Value is too large (7219). <for(picture)> q:=pathpart(EXPR0);tmp:=length.q; s:=decimal(roundone(xpart.po... draw_downscrap->...te.s.to.clip_name;endfor;endfor ;write"closepath fill"to.b... l.14260 draw_downscrap ; I must confess I have no idea what this is trying to tell me. What value is too large? Why is the text formatted so strangely? Do the ellipses indicate where text has been clipped, and if so where can I find the full text? I'm running Therion on Fedora 27 if that matters. Here is the full text from the log: therion 5.4.1 (2017-04-18) initialization file: /etc/therion.ini reading ... done checking optional fonts csr10 csti10 csbx10 csss10 csssi10 ... NOT INSTALLED checking optional fonts cmcyr10 cmcti10 cmcbx10 cmcss10 cmcssi10 ... OK configuration file: thconfig.thc reading ... done reading source files ... done preprocessing database ... done output coordinate system: UTM28 meridian convergence (deg): 2.6969 geomag declinations (deg): 2016.1.1 -12.1246 2017.1.1 -11.8581 scanning centreline tree ... done searching for centerline loops ... done calculating station coordinates ... done calculating basic statistics ... done processing extended elevation ... done processing references ... done selecting export objects ... done processing projection plan ... done average distortion: 0.03% writing litrikur.pdf ... ####################### metapost log file ######################## This is MetaPost, version 1.9991 (TeX Live 2016) (kpathsea version 6.2.2) 3 DEC 2018 13:17 **data.mp (/usr/share/texlive/texmf-dist/metapost/base/mpost.mp (/usr/share/texlive/texmf-dist/metapost/base/plain.mp Preloading the plain mem file, version 1.005) ) (./data.mp [4001] [4002] [4003] [4004] [4005] [4006] [4007] [4008] [4009] [4010] [4011] [4012] [4013] [1] [Warning: scrap outline intersects itself in scrap Litrikur-1p@Litrikur] ! Value is too large (7219). <for(picture)> q:=pathpart(EXPR0);tmp:=length.q; s:=decimal(roundone(xpart.po... draw_downscrap->...te.s.to.clip_name;endfor;endfor ;write"closepath fill"to.b... l.14260 draw_downscrap ; The equation I just processed has given some variable a value outside of the safetyp range. Continue and I'll try to cope with that big value; but it might be dangerous. (Set warningcheck:=0 to suppress this message.) [2] [3] [4] (./mptextmp.mp) [5] ) Here is how much of MetaPost's memory you used: 138534 strings using 3746717 characters 6847656 bytes of node memory 1422 symbolic tokens 11i,81n,14p,226b,5f stack positions out of 16i,96n,17p,250b,6f 18 output files written: data.1 .. data.4013 #################### end of metapost log file #################### therion: error -- metapost exit code -- 512 writing xtherion file ... done

3 2

Line artifact on scrap
by Thorir Jonsson 02 Dec '18

02 Dec '18

I have a strange artifact on a scrap I am working on, that I can't seem to select or get rid of (see attached screenshot). It is always drawn in red and no matter what I do I can't select it or get rid of it. Any Ideas as to what might have caused this or how I can remove it? Cheers, Þórir Már

3 4

TopoDROID to Therion process with respect to scraps
by Bruce Mutton 02 Dec '18

02 Dec '18

If I may ask a question unrelated to Thorir’s original post topic … > try to make shorter scraps. There is no problem if you’ll create many short scraps. I agree with Martin’s statement above, however I wonder how to approach it if the survey data and drawing was created with TopoDROID, as it appears Thorir’s example was. Is there a workflow that is easy to use with ‘TopoDROID to Therion’ process, that also allows more than one scrap per survey trip file? With limited experimentation (and making assumption that TopoDROID ‘sketches’ might be approximately equivalent to Therion ‘scraps’), I have not yet found a way that is easy to implement and encourages a naming convention that eases tracing of scraps to their parent TopoDROID file. And breaking existing scraps into smaller scraps is a task I find unnecessarily tedious, when one could just have drawn smaller scraps in the first place. Am I missing something obvious? What are experienced Therion users who subsequently became proficient with TopoDROID as a data collector doing in this space? Bruce

1 0