- Therion - speleo.sk

texts_es.tx
by Roman Muñoz 21 Jan '05

21 Jan '05

Hi, Here is the translated file. I observed there is no spanish translation in UIS symbols site, so I worked with some freedom, i,e on flute's case, which seems to be referred to 3 different things (marmitas (pits worked on rivers by pebbles), cupola (dome on the ceil) and channels For all those things about wiki, etc, please give me some time to get used with therion :) Cheers, Roman therion: point station:temporary es: estación topo temporal therion: point station:painted es: estación topo pintada therion: point station:natural es: estación topo natural therion: point station:fixed es: estación topo fija therion: line survey es: poligonal therion: point station-name es: nombre estacion topo therion: point entrance es: boca therion: line arrow es: flecha therion: line wall:bedrock es: pared therion: line wall:underlying es: pared subyacente therion: line wall:unsurveyed es: pared no topografiada therion: line wall:presumed es: pared supuesta therion: line wall:blocks es: bloques therion: line wall:debris es: derrubios therion: line wall:pebbles es: cantos rodados therion: line wall:sand es: arena therion: line wall:clay es: arcilla therion: line wall:ice es: hielo therion: point wall-altitude es: altura pared therion: point altitude es: altura therion: line section es: sección therion: point passage-height:unsigned es: altura therion: point passage-height:positive es: altura sobre nivel del mar therion: point passage-height:negative es: profundidad bajo nivel del mar therion: point passage-height:both es: altura y profundidad respecto nivel del mar therion: point air-draught es: corriente aire therion: point date es: fecha therion: point continuation es: continuación therion: point narrow-end es: final estrecho therion: point low-end es: final bajo therion: point flowstone-choke es: colmatado por concreción therion: point breakdown-choke es: colmatado por derrumbe therion: line floor-step es: resalte therion: line overhang es: extraplomo therion: line pit es: pozo therion: line ceiling-step es: resalte (techo) therion: line chimney es: chimenea therion: line gradient es: gradiente galería therion: point gradient es: gradiente galería therion: point height:unsigned es: altura resalte therion: point height:positive es: altura chimenea therion: point height:negative es: profundidad pozo therion: line contour es: contorno therion: line slope es: pendiente therion: line rock-border es: límite roca therion: line rock-edge es: arista therion: point bedrock es: roca madre therion: point blocks es: bloques therion: point debris es: derrubios therion: point sand es: arena therion: point clay es: arcilla therion: point water es: agua therion: point ice es: hielo therion: point pebbles es: cantos rodados therion: point raft es: calcita flotante therion: point guano es: guano therion: line border:visible es: límite therion: line border:temporary es: límite temporal therion: area water es: agua therion: area sump es: sifón therion: area debris es: derrubios therion: area sand es: arena therion: point waterflow:permanent es: curso agua therion: point waterflow:intermittent es: curso agua intermitente therion: point waterflow:paleo es: paleocurso agua therion: line waterflow:permanent es: curso agua therion: line waterflow:intermittent es: curso agua intermitente therion: line waterflow:conjectural es: curso agua supuesto therion: point spring es: surgencia therion: point sink es: sumidero therion: point flowstone es: concreción therion: line flowstone es: concreción therion: point moonmilk es: mondmilch therion: point stalactite es: estalactita therion: point stalagmite es: estalagmita therion: point pillar es: pilar therion: point curtain es: cortina therion: point soda-straw es: fistulosa therion: point popcorn es: coliflor therion: point cave-pearl es: perla de caverna therion: point disk es: disco therion: point helictite es: excéntrica therion: point aragonite es: aragonito therion: point crystal es: cristal therion: point wall-calcite es: calcita therion: point gypsum es: yeso therion: point gypsum-flower es: flor yeso therion: point rimstone-dam es: gour-presa therion: point rimstone-pool es: gour-poza therion: point anastomosis es: anastomosis therion: point karren es: lapiaz therion: point scallop es: golpes gubia therion: point flute es: canaleta therion: point raft-cone es: conos therion: point archeo-material es: yacimiento arq therion: point paleo-material es: yacimiento pal therion: point vegetable-debris es: detritus therion: point root es: raíz therion: point no-equipment es: sin equipar therion: point anchor es: anclaje therion: point rope es: cuerda therion: point rope-ladder es: escala therion: point fixed-ladder es: escala fija therion: point steps es: escalones therion: point traverse es: pasamanos therion: point bridge es: puente roca therion: point camp es: campamento therion: title legend es: Leyenda therion: title cave length es: Desarrollo therion: units m es: m therion: title cave depth es: Desnivel therion: title explo (plural) es: Exploración therion: title explo es: Exploración therion: title topo (plural) es: Espeleometría therion: title topo es: Espeleometría therion: title carto (plural) es: Espeleografía therion: title carto es: Espeleografía therion: title preview above es: Vista previa superior therion: title preview below es: Vista previa inferior therion: title surface bitmap es: Mapa superficie

1 0

model viewer?
by Roman Muñoz 19 Jan '05

19 Jan '05

Hi, I'm missing (in Linux) the model viewer available on windows Is this rigth? If yes, what coul I use to view models? Thanks, Roman

5 11

Adding sections error
by Andrew Atkinson 18 Jan '05

18 Jan '05

Just been trying to add sections to my plans, happily doing it until it decided to stop working, I cannot see what difference I have done. Whenever I try to put a point in to display sectB I get an error that starts off like the insert below. sectA, section1, section2, section3 seem to have worked fine, even discovered that you can use the scale points to rotate the sections, however this may not be the best method. START ERROR MESSAGE ! Inconsistent equation (off by 29.83728). <to be read again> ; <for(1)> ...z1,zz2])>0.1pt):zz5=whatever[zz1,zz2]; (zz3-zz5)=whatever*(zz1-zz... l_section->...z2--zz6;else:draw.zz1--zz2;fi;endfor ;for.pnt=(TEXT1):if.pnt=-1... l.3292 ),0,4) ; The equation I just read contradicts what was said before. But don't worry; continue and I'll just ignore it. ! Inconsistent equation (off by -22.96272). <to be read again> END THE ERROR MESSAGE While I am writing this email, I have a few clarification points pit-ent (not in this data set) seems to be displayed as a normal pit, not with the double line round it. The scaling of sections is very tedious, would there be anyway to make the default scale the same as the plan if it was in the same th2 file. The above error arose when adding sections, but I could not identify which one, the only thing I could do was to remove them all and then go back and add them one at a time until I found the mistake. As above is there a better way to rotate the sections if they have not been drawn on the original plan. Andrew

2 3

Section problem
by Andrew Atkinson 18 Jan '05

18 Jan '05

Sorry Typically, just after I sent the email I found the problem, on sectB I had the line type set to section instead of wall, fixed that and now it worked, although I still think that the error message with different information may have saved me a few hours Andrew

1 0

another set of inside-out pillars
by Wookey 18 Jan '05

18 Jan '05

I've added another km or so - the go-on series. No real problems except that all the pillars were inside-out. I split it into two scraps instead of one huge one, thereby determining in which half the problem lay, but after much staring at it and checking line types and looking at debug mode and fixing various problems, I still can't see why it's confused. The problem scrap is goon_s2 and it goes wrong on its own as well as when processed as part of the big plan. There are no therion errors about overlapping outlines, although there is one red metapost entry in the list (what do those mean?) The set of files is at http://trilogy-gw.aleph1.co.uk/~wookey/files/terikan.tgz (no pics). As ever, clues welcome. Wookey -- Aleph One Ltd, Bottisham, CAMBRIDGE, CB5 9BA, UK Tel +44 (0) 1223 811679 work: http://www.aleph1.co.uk/ play: http://www.chaos.org.uk/~wookey/

4 5

problem compiling on debian woody
by Roman Muñoz 18 Jan '05

18 Jan '05

Hi, this is my first post I'm trying to compile in debian woody with Tcl/Tk8.4 from www.backports.org. BWidget is 1.3 from woody. Tkimg is compiled from source. This is what I am getting: tatel@ganbo:~/src/therion$ make g++ -c -Wall -DTHLINUX -O2 -o thdate.o thdate.cxx g++ -c -Wall -DTHLINUX -O2 -o thexception.o thexception.cxx g++ -c -Wall -DTHLINUX -O2 -o thbuffer.o thbuffer.cxx g++ -c -Wall -DTHLINUX -O2 -o thmbuffer.o thmbuffer.cxx g++ -c -Wall -DTHLINUX -O2 -o thlogfile.o thlogfile.cxx g++ -c -Wall -DTHLINUX -O2 -o thtmpdir.o thtmpdir.cxx g++ -c -Wall -DTHLINUX -O2 -o thparse.o thparse.cxx thparse.cxx: In function `void thparse_image(char *, double &, double &, double &)': thparse.cxx:756: implicit declaration of function `int round(...)' make: *** [thparse.o] Error 1 What should I do? Thanks, Roman

2 2

arranging files for big systems
by Wookey 17 Jan '05

17 Jan '05

OK - now that I have a few non-trivial chunks of therion data to bring together I have re-arranged everything in a big-cave way. This has of course caused some problems. I am documenting them here. What I want to be able to do is produce a whole area map as well as smaller maps of each cave in the area, and maybe parts of a cave, and keep related data together,but only have it appear in one place. I know how to do this in survex, using a directory for each major cave or area. That contains an 'overview file' that is something like: *survey terikan *equate elevator.pt3.18b evening.25 *include elevator.svx *equate river.40 goon.0 *inculde goon.svx ... *end terikan so connections between surveys are here, but not connections within surveys (they are inside each .svx sub-file), and also connections (equates) are grouped together with the relevant files. So, I have an overall file for terikan in therion form but if I try to use the above structure - i.e like this: survey terikan map <scraplist> endmap input elevator.th2 input goon.th2 ... join <whwatever> centreline equate 0@goon 40@river input goon.th equate 25@evening 18b(a)pt3.elevator input elevator.th endcentreline endsurvey terikan then I get an error: therion: error -- terikan/terikan.th [72] -- not enough data readings at the first line that is an 'input <something>.th' The only way I can get it to work is by moving all the equates into one block, wrapped in a centreline/endcentreline command But for a big system this gives you a huge list of equates in one place and ahuge list of inputs below - it'smuch nicer to have the equates in the file next to the relevant inputs IMHO. So questions: 1) is my preferred arrangement possible/permitted in therion? How do would one do it? 2) Why do I get the error 'not enough data readings'? That seems to have very little to do with the actual problem - it took me some time to work out how to make it go away. I have more questions about arranging scraps and submaps too, but those can wait till another mail. Wookey -- Aleph One Ltd, Bottisham, CAMBRIDGE, CB5 9BA, UK Tel +44 (0) 1223 811679 work: http://www.aleph1.co.uk/ play: http://www.chaos.org.uk/~wookey/

5 14

survex to therion conversion script
by Wookey 12 Jan '05

12 Jan '05

A couple of people asked about this, so here it is under a sensible title so people can find it in the archives. Below is a perl script which does a reasonable job of converting .svx files to .th files. Written by Olly. I have noticed a few problems, which I might as well document here as as good a place as any: (I was going to tidy them up and send them to Ol as I was given said script for 'testing'). *calibrate declination comes out wrong. It should be: *calibrate declination n -> declination n degrees therion doesn't understand 'ignoreall' - needs commenting out Doesn't try to deal with different 'team' syntax - but could be fixed to get most of them right ((lower case them all), 'pics'->'pictures', 'disto'->'length #disto' etc) Only significant problem was with 'overview' files which include a number of others. * All the equates need enclosing in 'centreline'/'endcentreline' * The converter reads in any 'included' files and inserts them. It stopped after doing two of these and truncated the file. It should probably just convert '*include foo' to 'input foo.th' It once inserted a top-level 'dummy' survey where one wasn't needed. This is a feature of converting files individually rather than as a coherent dataset, I suspect. It could probably do a better job if it 'spidered' the dataset from a top-level overview file, but that's a lot more work :-) I found one case where the ';' remained for the comment char instead of it getting converted to '#'. I need to look at that or send ol the offending file. Then you can do this to convert a whole directory: for FILE in ls *.svx; do FILE=echo $FILE | sed "s/.svx//"; echo "Converting $FILE.svx"; svx2th $FILE.svx > $FILE.th; done #!/usr/bin/perl -w use strict; # svx2th v0.1 # Copyright (C) Olly Betts 2004 sub convert_file($); my $in_survey = 0; my $had_fix = 0; print "encoding iso8859-1\n"; for my $filename (@ARGV) { convert_file($filename); } if ($in_survey) { print "endsurvey dummy\n"; } sub convert_file($) { my $filename = shift; open F, "<", $filename or die "$filename: $!\n"; my @lines = <F>; close F; my $in_centre_line = 0; my $lineno = 0; my $dummy_survey = -1; foreach $_ (@lines) { ++$lineno; # Replace ; with # as comment separator. # FIXME won't cope with ; in a filename or *title s/;/#/; # Comment out "*export" and "*entrance" as there seems to be no # equivalent of either. if (/^\s*\*\s*(?:export|entrance)\b/i) { print "#$_"; next; } if ($in_centre_line) { if (/^\s*\*/ && !/^\s*\*\s*(?:date|calibrate|fix|equate|data|instrument|units|sd|infer|flags|team)\b/i) { print "endcentreline\n"; $in_centre_line = 0; } } else { if (/^\s*[^\s*#]/ || /^\s*\*\s*(?:date|calibrate|fix|equate|data|instrument|units|sd|infer|flags|team)\b/) { if (!$in_survey) { # Therion can't handle these outside a centreline which # must be inside a survey, so we have to add a dummy # top-level survey. print "survey dummy -title \"Therion is crap\"\n"; ++$in_survey; } print "centreline\n"; $in_centre_line = 1; } } # *begin <survey> -> survey <survey> if (s/^(\s*)\*(\s*)begin\b(\s*)(\S+)/$1$2survey$3$4 -title "$4" /i) { ++$in_survey; print $_; next; } # *begin -> <nothing> # The *begin will cause an endcentreline / centreline pair to be # output which hopefully prevents settings from escaping. However # this doesn't restore the old settings, just undoes any new ones. # FIXME: Need to address this somehow... if (/^(\s*)\*(\s*)begin\b[ \t]*$/i) { ++$in_survey; if ($dummy_survey != 0) { # FIXME: doesn't coped with nested *begin with no arguments... die "This convertor doesn't currently handle nested *begin with no arguments\n"; } $dummy_survey = $in_survey; print "#$_"; next; } # *end [<survey>] -> endsurvey [<survey>] if (s/^(\s*)\*(\s*)end\b/$1$2endsurvey/i) { if ($dummy_survey == $in_survey) { $_ = "#$_"; $dummy_survey = -1; } --$in_survey; if ($in_centre_line) { print "endcentreline\n"; $in_centre_line = 0; } print $_; next; } # *title <title> -> # -title <title> # FIXME: just comment out for now - should really convert to -title on # the "survey" line. if (s/^(\s*)\*\s*title\b\s*/$1# -title /i) { print $_; next; } # *team and *instrument format is unspecified in Survex, and they're # just informational so comment them out for now... # NB therion seems to be case sensitive so "Compass" isn't a valid role # ("compass" is)... # NB in *team pics -> pictures if (s/^(\s*)\*(\s*(?:team|instrument))\b/#$1$2/i) { print $_; next; } # *include -> literal text inclusion. # Note that the *include means an implicit *begin, but the output # may not reflect this correctly (since we can't handle *begin # with no survey name anyway...) if (/^\s*\*\s*include\s*"?([^"\s]*)/i) { # Use Unix path separators (/ not \) - Survex understands either on # either platform. my $filename = $1; $filename =~ s!\\!/!g; $filename .= '.svx' unless $filename =~ /\.svx$/i; convert_file($filename); next; } # survey.subsurvey.12 -> 12(a)subsurvey.survey if (s/^(\s*)\*(\s*equate)\b/$1$2/i) { # Ensure that a comment separator doesn't get eaten by station name. s/(\S)#/$1 #/; s/(\S+)\.(\S+)/"$2\@".join(".",reverse split m!\.!, $1)/ge; print $_; next; } if (/^\s*\*\s*fix\b/i) { $had_fix = 1; } s/^(\s*)\*/$1/; print; } } Wookey -- Aleph One Ltd, Bottisham, CAMBRIDGE, CB5 9BA, UK Tel +44 (0) 1223 811679 work: http://www.aleph1.co.uk/ play: http://www.chaos.org.uk/~wookey/

5 7

change to flags and subtypes (was Re: rock-border cannot be presumed)
by Andrew Atkinson 11 Jan '05

11 Jan '05

Wookey wrote >>> > >>> > OK - changing therion this way would be easy - but converting existing >>> > data is difficult. I would be very happy if I could remove > >> subtypes, but > >>> > it would be quite substantial change... > >> >> It it really that difficult to write some perl conversion that >> would usually >> do the right thing? >> >> I think you are right that this was a design error and we should fix it if >> at all possible. There are not that many datasets now - in the >> future it will >> only get harder... >> >> I think we should say that this will change in 0.4 or something. If we can >> add the new functionality now/soon so that people can create new >> data in the >> new style, then that will make it easier to convert (because >> there will be a >> version that can cope with old and new data for people to use until they >> have converted). >> >> I don't want to break my dataset any more than necessary, but if >> changes are >> necessary for long-term growth, and we can design a reasonable transition, >> then it is probably worth doing. >> The difference and different ways to get the same thing confused me, I think that although it would break my data, it would be better to change it now so that the program can be developed coherently in the future. Andrew PS On a related topic, how does Therion now fit with survex, I have to say that I am finding data set conversion a little tedious, and I have not tried to for a big cave yet.

2 1

rock-border cannot be presumed
by Wookey 10 Jan '05

10 Jan '05

I have a rock-border that is presumed, but this is not a permitted subtype. How should should a thing be drawn in therion? Wookey -- Aleph One Ltd, Bottisham, CAMBRIDGE, CB5 9BA, UK Tel +44 (0) 1223 811679 work: http://www.aleph1.co.uk/ play: http://www.chaos.org.uk/~wookey/

2 4