January 2008 - Therion

Editing svg therion results
by Xavier Pennec 22 Mar '08

22 Mar '08

Hi One of the things that I would like to do with the maps generated by Therion is embedding plans and elevations in a single document, especially for small caves, and rework on subparts of the plans and elevations to put some specific features into evidence for figures in a text explaining things about the cave (or in this case the mine). I thought that it would be easy with any svg editor, but apparently this is not the case at all. I can open and visualize the svg files produced by therion using inkscape, but I cannot degroup the drawing in order to edit some of the parts and, more importantly, importing the plan and the elevation in a single document lead to an incorrect result (see NaduelRD5_fuse.svg). It seems that there is a namespace problem: as both drawing refer to elements that have the same name, so that the definition of one of the drawing overwrite the definitions of the other. Does anybody have an idea of how to overcome that? Is there any other svg editor that behaves better (and which is not too expensive!)? By the way, it would be interesting to have a north arrow symbol that we can place wherever we want in a plan and not only a north arrow generated in the legend. That way, we could avoid using legends when needed (e.g. to fuse maps outside therion). Thanks Xavier

4 6

Re: [Therion] therion notes
by Ladislav Blazek 18 Mar '08

18 Mar '08

http://search.cpan.org/dist/HTML-WikiConverter-DokuWiki/ HTML::WikiConverter::DokuWiki adds the DokuWiki dialect to HTML::WikiConverter allowing the conversion of HTML to DokuWiki markup. Usage: html2wiki --dialect DokuWiki input.html > output.wiki L. marco napsal(a): >> really nice documentation. What about migrate this to therion wiki > pages? > > i would like to have a wiki output filter, > but i never had enough motivations to put my head to it. > do you c++ ? > > marco > > -- Ladislav Blazek

8 15

Concatinate map-comment?
by Bruce Mutton 07 Feb '08

07 Feb '08

I'd like to add some 'standardised' blocks of text to my finished cave maps, and a convenient way seems to be to use the map-comment command to add the text to the title block. As far as it goes the following works fine. FILE THCONFIG- GreenlinkAnnotationLayout layout GreenlinkAnnotationLayout map-comment "REFERENCES:\ Discovery and early exploration of Greenlink cave\ NZSS Bulletin Vol 7 No 100 p500-510\ \ Original Maps of Greenlink cave\ NZSS Bulletin Vol X No XXX pXXX-XXX" endlayout GreenlinkAnnotationLayout END FILE I'd then like to be able to concatenate similar blocks of text at compilation time. Trouble is if multiple map-comments are used, then the last one executed overwrites the other. Why concatenate them? For example; The thconfig file(s) producing output files for a particular cave all refer to the above layout for that particular cave. This works fine. I have three caves, each with their own files. Now I'd like to reuse the data at the next level up, without maintaining duplicate copies. The data for these three caves is contained in a directory with a master thconfig that produces output files for the whole system of three caves. Rather than having duplicate copies of the map-comment layouts containing the text above, I'd like to refer to the same layout each time, ie concatenate the text along the lines of. layout. copy GreenlinkAnnotationLayout copy MiddleEAnnotationLayout copy SwissMAnnotationLayout .endlayout Trouble is each one overwrites the previous. Can I concatenate the map-comment field? Is there a better way to do this? Thanks Bruce

2 2

Output map Scale
by Bruce Mutton 07 Feb '08

07 Feb '08

Can Therion output the scale of the map as drawn, in text? (I'd like to display this as say 1:1000, as well as the scalebar) Thanks Bruce

2 4

instalation of therion on MacOS X
by Martin Sluka 28 Jan '08

28 Jan '08

It looks that on system 10.4 Tiger or 10.5 Panther one must install only: 1. XCode Tools (from installation DVD of MacOS X) 2. MacTeX - http://www.tug.org/mactex/ 3. Survex – http://www.survex.com and therion: Download the therion source, expand it by doubleclick and copy the therion folder to Application folder. Than from terminal: 0. cd /Application/therion 1. make config macosx 2. make 3. sudo make install All other bits are installed in system yet or in XCode Tools. There is a bug in therion if you install therion on new installed MacOS X system the folder /usr/local/etc is not created. The installation script of therion doesn't mkdir etc, so one must to do it manually. Only remaining problem is with VTK and with Loch. m.

1 0

Cavewhere Experiment
by Philip Schuchardt 27 Jan '08

27 Jan '08

Help evaluate the next generation of cave visualization and mapping software with the VT-CAVE! Requirements for participating: Basic knowledge of caves and cave features such as domes, pits, multi- level passages, and drainage paths. You must be over 18 years old to participate and must NOT have extensive preexisting knowledge of Omega (24.5mi / 39km), the longest and deepest cave in Virginia. If you have any questions about the requirements, email me. Benefits: You will be able to use new technology for visualizing cave data. You may gain a better knowledge of the structure of Omega. Session Length: 1 hour When: Contact me for scheduling your session. Schedule early because session slots fill up fast. Open Sessions -- January 28, 2008 to February 15, 2008 Monday 10AM to 11PM Tuesday 4PM to 11PM Wednesday 10AM to 11PM Thursday 4PM to 11PM Friday 10AM to 5PM Where: Torgerson 3050 – The VT CAVE, Virginia Tech, Blacksburg, VA Thanks, Philip Schuchardt

3 5

Problem in 3D model
by Gilbert Fernandes (mailinglist) 24 Jan '08

24 Jan '08

Hello, I notice a bug in the 3D modeling. In this short exemple you can reproduce the error. The main problem is when you have a pit, ans so a vertical survey ( compas = 90 or -90 ), the up and down value in survey data is used in the 3D model (.lox file) for the with of the pit and not for the hight (or down) of the galery. So pits are always as fat as they are hight. Look the .th file and try to change the up and down value as comment in the exemple, look the effect in the 3D view. Thanks, Gilbert encoding utf-8 source pinee1.th export model -o pinee_3D.lox

2 1

Calculating Magnetic Declination
by David A. Riggs 24 Jan '08

24 Jan '08

I just spent far too long trying to get automatic calculation of magnetic declination to work, and I'm posting my findings so that others don't make the same mistake, and so that therion (an already great piece of software) can be improved accordingly. I've found that... Specifying the fixed coordinate before the coordinate system causes therion to silently fail to apply declination. In other words, this is wrong: date 2007.06.31 fix A0 626333 4320333 2620 cs UTM17 Specifying the coordinate system before the fixed coordinate causes therion to properly calculate magnetic declination. This is correct: date 2007.06.31 cs UTM17 fix A0 626333 4320333 2620 Therion 0.5.1 does this completely silently, with no notification that declination has been applied at all. Therion 0.5.0 prints the following (rather confusing) message in therion.log: output coordinate system: EPSG:32617 meridian convergence (deg): -0.9190 geomag declinations (deg): 2007.1.1 -8.9944 2008.1.1 -9.0224 My recommendations are that therion should: - Ignore the order of 'cs' and 'fix', apply declination as long as both are included - Explicitly state that declination has or has not been applied, regardless of configuration, so users are aware of this - Emit a warning if partially or incorrectly configured for magnetic declination calculation Thanks very much! Dave Riggs Morgantown, WV -- David A. Riggs <david.a.riggs(a)gmail.com>

2 1

long lines
by Wolfgang Zillig 14 Jan '08

14 Jan '08

Hi, what is the limit in line length? My elevation model hits that limit (it was just a test with interpolated data, so nothing that really bothers me). The question is out of interest only. C:\Program Files\Therion\therion.exe: error -- AHS.th [12] -- line too long Regards Wolfgang

2 1

therion 0.5.1 uploaded to Debian
by Wookey 04 Jan '08

04 Jan '08

I finally got round to uploading the work I did in January to Debian proper. So there is now a current Therion in unstable as well as experimental, and the various long-standing bugs are fixed. The new packages use texlive instead of tetex, as Debian has transitioned to these, and the wiki docs are included in the therion-docs package (that's currently the wiki docs as of about a year ago. I'll update those too shortly). The package now appears in Applications/Science/Geoscience in line with current menu policy (I'll do an update of Survex with this property too soon). You can see current package status here: http://packages.qa.debian.org/t/therion.html and build logs here: http://buildd.debian.org/pkg.cgi?pkg=therion Please try them out if you can and report any problems. I've included the current debian diff below in case Stacho wishes to include any of it upstream (I'm afraid I've trampled all over your nice multiplatform build stuff stacho, but a few bits of the diff are probably worth incorporating upstream). This has raised a few issues worthy of note. 1) 64-bit loch Wolfgang Zillig reported in April that he couldn't get loch to work on his AMD64 box. It doesn't work on mine either. I'll post more details in that thread. 2) gcc warnings The therion code generates hundreds of warnings if you do a build with default gcc4.2.2 like this: thdataleg.h:141: warning: deprecated conversion from string constant to 'char*' thdataleg.h:141: warning: deprecated conversion from string constant to 'char*' thdataleg.h:141: warning: deprecated conversion from string constant to 'char*' I've worked around that for now using -Wno-write-strings but I think the correct fix is to use const in the function prototypes to match the declarations. You can see a log of the full set of whinges here if someone wants to go through them: http://buildd.debian.org/fetch.cgi?pkg=therion;ver=0.5.0-2;arch=ia64;stamp=… The gcc docs suggest that -Wno-deprecated should also stop these warnings, but that doesn;t seem to work. Not sure if I was just having finger trouble/too much beer over xmas there, but it really didn't seem to stop them all. 3) New sample data I had a bit of trouble building this, so it's not in the current package, but I've worked it out now (paths and dependencies was the issue) and so will integrate it into the docs package on the next upload. It's a nice piece of work. Is this intended to replace the wiki docs eventually? 4) tcl version. Does Therion care if tcl 8.4 or 8.5 is used? I've left it defaulting 8.4 for now, but I guess 8.5 would work and would be preferred? A quick test suggests that it works fine. 5) library linkages: The shared-library analyser points out that we link to all the wxgtk libs but only actually use some of them. This is wrong. dpkg-shlibdeps: warning: debian/therion-viewer/usr/bin/loch shouldn't be linked with libwx_gtk2u_xrc-2.6.so.0 (it uses none of its symbols). dpkg-shlibdeps: warning: debian/therion-viewer/usr/bin/loch shouldn't be linked with libwx_gtk2u_qa-2.6.so.0 (it uses none of its symbols). dpkg-shlibdeps: warning: debian/therion-viewer/usr/bin/loch shouldn't be linked with libwx_gtk2u_adv-2.6.so.0 (it uses none of its symbols). dpkg-shlibdeps: warning: debian/therion-viewer/usr/bin/loch shouldn't be linked with libwx_baseu_xml-2.6.so.0 (it uses none of its symbols). dpkg-shlibdeps: warning: debian/therion-viewer/usr/bin/loch shouldn't be linked with libwx_baseu_net-2.6.so.0 (it uses none of its symbols). dpkg-shlibdeps: warning: debian/therion-viewer/usr/bin/loch shouldn't be linked with libvtkImaging.so.5.0 (it uses none of its symbols). dpkg-shlibdeps: warning: debian/therion-viewer/usr/bin/loch shouldn't be linked with libvtkIO.so.5.0 (it uses none of its symbols). dpkg-shlibdeps: warning: debian/therion-viewer/usr/bin/loch shouldn't be linked with libz.so.1 (it uses none of its symbols). I think the reason is that the build uses: $(shell wx-config --libs --gl-libs) to list the wx libs so gets all of them. I haven't fixed this yet as I'm not sure what the best fix is. Should we just list the libs that actually are used, or is there a way to use wx-config to DTRT? 6) No desktop files Therion doesn't appear to have any desktop files so it doesn't appear in the main menus of xfce/gnome/kde. Anyone done any, or care to do some? Wookey -- Principal hats: Balloonz - Toby Churchill - Aleph One - Debian http://wookware.org/

3 7