<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><br class=""><div><blockquote type="cite" class=""><div class="">10. 7. 2017 v 12:08, Bruce Mutton via Therion <<a href="mailto:therion@speleo.sk" class="">therion@speleo.sk</a>>:</div><br class="Apple-interchange-newline"><div class=""><div style="margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class="">Before I wiki-ise it, I’d like some feedback, or criticism, as appropriate! Is it helpful? (I think so)<o:p class=""></o:p></div><br class="Apple-interchange-newline"></div></blockquote><br class=""></div><div>Hi Bruce and all,</div><div><br class=""></div><div>after many years of experimenting I made a presentation of What is behind Therion. You may download it here: <a href="http://studiosluka.eu/therion/" class="">http://studiosluka.eu/therion/</a> The most difficult for me was to understand the principle of name spaces, what is normal way of thinking for authors of Therion. But at the end I did it, I hope.</div><div><br class=""></div><div>As you probably know, all Therion’s data could be only in one file, including centerline, comments, log, maps and layout. Examples of such files made by Stacho were in Sample folder of Therion source code in former versions. By command „input“ you may add to therion file any piece of plain text code. So it doesn’t matter, if you’ll have all your .th files in separate file and you add them all by simple "input index_th.thc“ command to survey in higher level, or you’ll list them all in that survey. The same with equates, joins, logs, maps, … </div><div><br class=""></div><div>You may organize in the same way smaller parts of cave system as: index_th_north_branch.thc, index_equate_north_branch.thc, index_join_north_branch.thc index_map_north_branch.thc, etc. and input them one by one.</div><div><br class=""></div><div>The same is possible to do with th2 files. The fastest way, how to work with Therion map editor is to have only one small scrap in one th2 file. And input all particular scrap to survey one by one.</div><div><br class=""></div><div>Everything, what is in particular survey used as „source“ in thconfig is available to compilation. But everything, what is outside that survey is not available.</div><div><br class=""></div><div>I started to use .scrap and .map „extensions in names of scraps and maps. Simply to be sure, what is what. It is more easy to add to scrap name from other surveyor „.scrap", then to correct his/her way to my scrap names convention. And I started to use really long names for scraps and maps, to be from first sight sure, what that piece of text means.</div><br class=""><div class="">Therion is able to collect all informations available in „source“ file and its name space. But not in all case it is what we want. So I prefer to use <span style="font-family: arial, sans-serif; font-size: 13px; white-space: nowrap; background-color: rgb(255, 255, 255);" class="">obligatory </span>„select“ command in thconfig and select only one map definition. (thanks, Martin Budaj)</div><div class=""><br class=""></div><div class="">Because of better description of what is particular thconfig for I prefer to use extension .thconfig for configuration files. So I’ll use north_branch.thconfig instead thconfig file in folder North_Branch.</div><div class=""><br class=""></div><div class="">I use base survey as really base survey, with all informations about that particular survey trip, if possible with commented each survey shot (ignore all) and better all shots (but is more or less theory). It includes map definition too, just to check of drawing. In this case I don’t need to use any additional commands in header of survey or scrap. I simply follow numbering of stations as in centerline. All connections of data in higher surveys are made in by Therion’s name space convention with @ syntax. I apologize to Survex developers, but it is for me more logical way, because it allows me to use extension for scraps, maps an to use original data from Toporobot or PocketTopo. In this base survey I may define several maps if necessary for each particular scrap and select only one of them. There could be a map definition for all scraps together too.</div><div class=""><br class=""></div><div class="">In this way I input only .th files from lover levels, because .th2 files are inputed in them yet and I don’t need to voodoo with names of stations.</div><div class=""><br class=""></div><div class="">My data structure is simple:</div><div class=""><br class=""></div><div class=""><font face="Courier" class="">my_cave</font></div><div class=""><font face="Courier" class=""> my_cave.thconfig</font></div><div class=""><font face="Courier" class=""> my_cave.th</font></div><div class=""><font face="Courier" class=""> data</font></div><div class=""><font face="Courier" class=""> north_branch — folder</font></div><div class=""><font face="Courier" class=""> north_branch_170321 — folder</font></div><div class=""><font face="Courier" class=""> north_branch.thconfig </font></div><div class=""><font face="Courier" class=""> north_branch_170321.th </font></div><div class=""><font face="Courier" class=""> north_branch_scrap1_170321.th2</font></div><div class=""><font face="Courier" class=""> north_branch_scrap2_170321.th2</font></div><div class=""><font face="Courier" class=""> north_branch_scrap3_170321.th2</font></div><div class=""><font face="Courier" class=""> ...</font></div><div class=""><font face="Courier" class=""> scans — folder</font></div><div class=""><font face="Courier" class=""> output — folder</font></div><div class=""><font face="Courier" class=""> north_branch_170514 — folder</font></div><div class=""><font face="Courier" class=""> ...</font></div><div class=""><font face="Courier" class=""><br class=""></font></div><div class=""><font face="Courier" class=""> south_branch — folder</font></div><div class=""><font face="Courier" class=""> ...</font></div><div class=""><font face="Courier" class=""><br class=""></font></div><div class=""><div class=""><font face="Courier" class=""> index — folder</font></div></div><div class=""><font face="Courier" class=""> output — folder</font></div><div class="">m.s.</div></body></html>