August 2013 - Therion

Compiling Therion projects from Notepad++
by Footleg 08 Jan '15

08 Jan '15

I find having multiple thconfig files open so I can compile different parts of my large cave system project very useful. So I was investgating how to run Therion from Notepad++ (my preferred text editor). This is how I got it working: I wrote a 2 line batch file containing these commands: cd %1 "C:\Program Files (x86)\Therion\therion.exe" %2 Saved to somewhere on disk, and then call it from Notepad++ using the Run command, as follows: On the Run menu in Notepad++, Select the 'Run' item, and enter the command as follows: "C:\Personal\Caving\Therion\compileTherion.bat" "$(CURRENT_DIRECTORY)" "$(FILE_NAME)" (But using the path to where you saved your batch file). Save the command (I called it 'Compile Therion' and gave it the shortcut CTRL+T). Now with any thconfig file open in a tab in Notepad++, I can compile that project by pressing CTRL+T, or by selecting 'Compile Therion' from the Run menu. You can create multiple thconfig files in the same folder on Windows, by giving them any filename you want with the extension .thc or give them no extension at all. That way all the files will be listed in the 'Open File' dialog from the compile tab in xTherion. Next I'll see if I can get my batch file to open the output PDF automatically in Foxit Reader :) But that will be less general because I need to pick a PDF filename which can vary between my thconfig files. Footleg

3 6

5.3.11
by Stacho Mudrak 06 Oct '13

06 Oct '13

Hello everybody, I have just uploaded version 5.3.11. Here is the list of changes: therion: * added -survey option for map for setting survey associated with map. For example all surveying statistics from this survey will be used, when this map is selected for output. * added sketch-colors <number-of-colors> option to thconfig file, to reduce size of sketch bitmap images in maps * hide symbol from legend, if it has explicitly empty translation * survey-level works for point station-name labels, if station name is automatically determined (no -text is specified) * symbol-show|hide group text for point label, remark, date and line label * grid-angle <value> <units> - can be used in centerline to specify magnetic grid angle (declination against grid north). * -cs output specification works for export cave-list (including lat-long) * dates are shown using OS locale settings in map export * layout statistics explo/topo-length on/hide/off -- if it is off, team members are sorted alphabetically * KML export format supported for cave-list and continuation-list * bugs fixed: - PLT export in output coordinate system - context point air-draught not working - instrument position in centerline does not work - debug scrap-names crashes if empty scraps - counter not working in centerline data diving - revise not working outside of survey context - wrong length/depth and other statistics calculation for map output - sketch bitmaps inserted multiple times in PDF files xtherion: * bugs fixed: - new file in xtherion works, even if file is already open Merry Christmas :) S.

5 9

image missing and import error
by Andrew Atkinson 13 Sep '13

13 Sep '13

Hello I have just upgraded to debian jessie which comes with Therion 5.3.10 When opening a th2 file I find that all my background images are not visable, also not listed in the background images on the right hand side So in a new file I try importing a jpg, one I have done before, it gives an error, the log of which is attached, as is the th2 file it produces, which looks okay at a quick glance. I also tried a .top text file import, again that I have successfully done before, with the same result, the xvi is produced. Trying importing an xvi it looks like the same error Suspect this is a debian bug, as no one else has complained so will file a report after this thanks Andrew

3 5

Export Full Backbearings from PocketTopo to Therion
by John Stevens 08 Sep '13

08 Sep '13

Export oddities from PocketTopo to Therion A while back, I noted that if you do a full back bearing of three readings straight after you have done to forward leg, PocketTopo recognises this as the same leg and numbers it accordingly. I have not found any documentation about this useful feature though. 2.10 1.139 64.25 -33.70 [1] 2.10 1.288 53.85 -61.89 [1] 2.10 2.243 304.70 -50.40 [1] "fissure in floor with sound of water flowing " 2.10 2.11 3.574 49.25 -15.19 [1] 2.10 2.11 3.574 49.06 -15.19 [1] 2.10 2.11 3.577 49.27 -15.23 [1] 2.11 2.10 3.576 229.26 14.68 [1] 2.11 2.10 3.575 229.37 14.68 [1] 2.11 2.10 3.577 229.60 14.80 [1] 2.11 0.599 96.53 74.98 [1] 2.11 0.201 156.69 -50.20 [1] If the back bearing was outside the automatic parameters, then it can always be forced and sorted later. i.e. make a note, station may be too close to iron work or buried iron in spoil/deads. PocketTopo and TopParser deal with these in different ways when it is imported into Therion PocketTopo averages all 6 readings for the output file but it also adds a blank line 2.10 64.25 -33.68 1.140 > 2.10 53.85 -61.89 1.288 > 2.10 304.69 -50.39 2.243 > 2.10 2.11 49.30 -14.96 3.575 > 2.11 2.10 0.00 0.00 0.000 > 2.11 96.67 75.01 0.599 > 2.11 156.63 -50.15 0.201 > This second line then has to be commented out or deleted once in Therion. Other than that all other outputs act as expected. TopParser on the other hand outputs both sets of readings as separate legs. This has an advantage but a couple of disadvantages. 2.10 - 1.139 64.25 -33.7 2.10 - 1.288 53.85 -61.89 2.10 - 2.243 304.7 -50.4 fissure in floor with sound of water flowing #2.10 2.11 3.574 49.25 -15.19 #2.10 2.11 3.574 49.06 -15.19 #2.10 2.11 3.577 49.27 -15.23 2.10 2.11 3.575 49.15 -15.2 Calculated leg from 3 above #2.11 2.10 3.576 229.26 14.68 #2.11 2.10 3.575 229.37 14.68 #2.11 2.10 3.577 229.6 14.8 2.11 2.10 3.576 229.31 14.72 Calculated leg from 3 above 2.11 - 0.599 96.53 74.98 2.11 - 0.201 156.69 -50.2 If I use this output, the length of the cave is doubled for the leg but I do get some nice 2 leg loop closure errors. The distance can be adjusted but adding flags duplicate and flags not duplicate lines around the duplicate leg. These loop closures then give me good feed back into where magnetic influences are within the cave/mine. 5.70% 0.4m 7.7m 2 -0.2m 0.4m -0.0m [2.7 - 2.8 - 2.7] 3.86% 0.2m 5.1m 2 -0.1m -0.2m -0.0m [2.8 - 2.9 - 2.8] 2.70% 0.2m 8.7m 2 -0.2m 0.2m -0.0m [2.11 - 2.12 - 2.11] 1.18% 0.1m 11.0m 2 -0.1m -0.1m 0.0m [2.9 - 2.10 - 2.9] 0.50% 0.0m 3.9m 2 -0.0m -0.0m 0.0m [2.12 - 2.2 - 2.12] 0.44% 0.0m 7.2m 2 -0.0m 0.0m -0.0m [2.10 - 2.11 - 2.10] 0.33% 0.0m 10.8m 2 0.0m 0.0m -0.0m [2.2 - 2.7 - 2.2] >From these it is easy to see which passage had a large iron pipe running down it, even those we kept a good distance from it. This now allows me to set that passage survey grade as lower for the loop closures. But with all these subloops, Therion does not like calculating the main loop error. The other main problem with the TopParser output is for the extended section. Here it plots both legs so the centreline and splays are in the wrong place for the drawings. So that output is totally useless and I have to go back and use the PocketTopo output for extended sections. So bit more work on TopParser and PocketTopo to make them both fully implement this useful function.

4 3

Error 768
by Andrew Atkinson 06 Sep '13

06 Sep '13

Hello Debian wheezy. Therion 5.3.9 and 5.3.10 First some history. I was using 5.3.9, but last weekend I was running a course in Wales so needed the OSGB:SN which is added to 5.3.10. So to achieve this built 5.3.10 from source as 5.3.10 is not in wheezy due to the freeze. So when producing a pdf I get the Error 768, log attached, everything else I do seems to work as normal Wookey was there to help, so also tried installing 5.3.10 from .deb and then 5.3.9 from the .deb, both with the same error. Now in the error there is the bit that says ! Unable to make mpx file. l.2 btex \mainfont 0 etex The two files given above are one of your source files and an auxiliary file I need to read to find out what your btex..etex blocks mean. If you don't know why I had trouble, try running it manually through MPtoTeX, TeX, and DVItoMP played around with this, but really do not know what I am doing, but it might help me trace the problem. 5.3.10 worked on Wookeys Wheezy machine, so the w/e training could continue, at least. This was generated when running the thconfig file in http://www.cave-registry.org.uk/svn/CheddarCatchment/Reservoir/ Thanks Andrew

3 6

samples processing failing
by Wookey 05 Sep '13

05 Sep '13

When doing the build the samples processing gets as far as the 'survex' folder and things go wrong: therion 5.3.11 initialization file: /etc/therion.ini reading ... done configuration file: thconfig.1 reading ... done reading source files ... done preprocessing database ... therion: error -- file import -- cave1.th [11] -- unable to open file cave1.th definitely exists. why would 'source cave1.th' fail? ownership and permissions are OK running therion thconfig.1 again produces the above output. similarly in the survex/use dir: therion 5.3.11 initialization file: /etc/therion.ini reading ... done configuration file: thconfig.1 reading ... done reading source files ... done preprocessing database ... therion: error -- file import -- cave1.th [11] -- unable to open file source foo.th has just worked fine in q-marks and pocket-topo and morphing/sample1 etc. I am perplexed. Wookey -- Principal hats: Linaro, Emdebian, Wookware, Balloonboard, ARM http://wookware.org/

2 5

Surface profile in elevation maps
by Steve Clark 01 Sep '13

01 Sep '13

[re-sent due to email address error] I am looking for some advice on the best way to add the profile of the ground surface to a cave elevation (for pdf export). Apologies if this is in the book and I've missed it. Currently, I have the background colour as a light grey, with cave the foreground in white. This works well, is easy to read and looks good. Sample section here : https://dl.dropboxusercontent.com/u/4064739/draft_section_18may2013.pdf Assuming I can draw the ground profile, is there a simple way to change the colour above the ground (i.e. the sky) to white too? If not, and it's better to make everything white, what is the most consistent way to draw the ground profile as a line in a scrap? Should I be using a 'walls' line but inside-out or is there a better/correct way to do this? Any help much appreciated, Steve

3 2

Re: [Therion] Annoying joins
by Graham Mullan 19 Aug '13

19 Aug '13

Thanks guys, I guess that advice translates as "RTFM!" However, I note that the specific ID seems to relate to a line rather than to a single line point. When I add these in and write my joins accordingly, the problem is not resolved, the output merely becomes differently wrong. Experience would suggest that a line, somewhere is the wrong way round, but I've checked them all, to no avail. Is there a way of attributing an ID to a line point rather than a whole line? Or am I still missing something basic. Graham -- graham.mullan(a)coly.org.uk In the UK 0117 9502556 or 07887 637064 France from the UK 0844 2327803 In France 05 53 51 19 15 or 06 02 53 37 81

3 4

Strange top file causes pain for therion
by Bruce 19 Aug '13

19 Aug '13

This may be one for Therion authors, Beat (PocketTopo) and Andrew (TopParser) A strange spurious value in the attached top file causes therion to hang when trying to load the xvi file produced by topparser (have not tried the workflow where we import txt files produced by PocketTopo, although I have attached those txtx files). Not sure how the bad value got into the top file? -bad disto? Seems reasonable as we occasionally get spurious numbers from our disto -PocketTopo glitch? Seems possible based on what I recall of the workflow in the cave as we were collecting data. -user error due to accidentally deleting the distance in the data table? Quite likely, I am fairly blind in a cave when it comes to close work. Anyway, sending these just in case it helps with more graceful error handling with similar bad data in future, and maybe will help users who have similar troubles. You can see how it manifests in PocketTopo in the screenshot attached and below. It is handled gracefully, but not much clue as to where the problem is. The offending entry in the data table view appears to be normal-ish, maybe a zero missing. I think I had just performed the 'continue here' function. The bad line is highlighted blue. You can see what seems to be the cause here in the exported 'therion data file. Maybe it is a bad value in top file causing this, or maybe this is what the export function in Xtherion and the conversion in topparser do with a null distance in the top file? File 56-ConsciousTHERION.txt produced by Therion line 214 56.4 180.00 0.00 2147483.648 > File 56-ConsciousTEXT.txt produced by Therion line 272 56.4 0.00 0.00 [1] File 56-Conscious.th produced by TopParser line 335 56.4 - 2147483.648 0.0 0.0 I think topparser produces Therion files faithfully, but Therion drawing window hangs when trying to load the xvi produced. Anyway, when I added a 0.0 value to the missing distance in the PocketTopo file and reprocessed everything, all is now as it should be and the world is a better place. How to make it easier in the future? PockeTopo to warn on export if there appears to be bad or missing data? Therion and TopParser to replace null values with zero?? Bruce

2 1

Annoying joins
by Graham Mullan 18 Aug '13

18 Aug '13

Thanks to a way that a survey was carried out, I have a junction between a scarp in one survey and two scraps in another. No matter which way i try to sort the joins, nonsense results. Is there a more specific way of joining lines that just specifying scraps? Graham -- graham.mullan(a)coly.org.uk In the UK 0117 9502556 or 07887 637064 France from the UK 0844 2327803 In France 05 53 51 19 15 or 06 02 53 37 81

3 4