> I demonstrated Therion to our local caving club a couple of days ago...
>Fantastic! I've been thinking of doing the same thing with my club. If >you don't mind my asking, how exactly did you give your presentation? >Did you just show how it's used, or did you go more in depth? >-Jonny ^v^ Started with showing a bunch of outputs for the cave system I've been working on; -Loch model with 3 caves, terrain model & surface image -SQL and 'continuations' outputs -A bunch of pdf map and atlases including surveyed caves, old scanned cave map and surface image. Then went very broadly and briefly through the process demo-ing the actual input files for the above outputs, 'scan data format', xvi-draw or print_atlas-sketch-scan-trace_scraps drawing alternatives, drew a new bit of passage, had a compile error I couldn't solve on the fly, INDEX files to link it all together and thconfig files to obtain output, and answered questions. A couple of people have taken away my data for the cave system, and hope to use it as a template to draw up some projects they have... which brings me to the single biggest hurdle that continues to dog me with Therion - how to arrange ones data? I realise there's probably about 50 good ways to do this, depending on ones needs and expectations, and some are described very vaguely in the documentation. I think I'm heading towards a reasonable strategy that's scalable from single caves to 60km systems with numerous small surficial caves nearby. When I've got the bugs ironed out I'll see if I can get something into the Wiki. Probably in the form of some actual data, suitably scrambled so that it does not reflect a real cave, and with commonly used statements pre-entered and commented and well documented. If anyone has already documented a Therion data management system I would be most interested. There was nothing specific enough on the Wiki when I looked a few months ago - may be better now, I notice there is some nice content on surfaces added recently. Bruce
