mirror of
https://expo.survex.com/repositories/expoweb/.git/
synced 2024-11-22 07:11:55 +00:00
90 lines
5.9 KiB
HTML
90 lines
5.9 KiB
HTML
<!DOCTYPE html>
|
|
<html>
|
|
<head>
|
|
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
|
|
<title>Handbook Troggle NOTES</title>
|
|
<link rel="stylesheet" type="text/css" href="/css/main2.css" />
|
|
</head>
|
|
<body>
|
|
<style>body { background: #fff url(/images/style/bg-system.png) repeat-x 0 0 }</style>
|
|
<h2 id="tophead">CUCC Expedition Handbook</h2>
|
|
<h1>Troggle - the users</h1>
|
|
<p>Troggle runs much of the the cave survey data management, presents the data on the website and manages the Expo Handbook.
|
|
|
|
<h2>Who needs to know What and When</h2>
|
|
|
|
<p>We have several quite different sorts of cavers who interact with troggle:
|
|
<img border="1" class="onright" width="150px" src='tricky-troggle.jpg' alt='git logo'/></a>
|
|
<ul>
|
|
<li>The youthful hard caver, who is trained in underground survey techniques but whose interest is limited to handing over the grubby
|
|
survey notes when she emerges into daylight. Is keen to know how many km of cave she surveyed each year and to see pretty drawn-up
|
|
surveys (done by someone else). Walks through walls.
|
|
<li>The surface walker who is happy to do route-finding over the plateau, takes lots of photos of cave entrances and cavers enjoying
|
|
sunshine and may sometimes be able to provide GPS tracks of where he has been. He needs a prospecting guide to find previously
|
|
identified entrances and be able to find photos of caves in past years. Writes up his explorations in execrable handwriting in the
|
|
logbook. Looks at walls.
|
|
<li>The diligent student who types up the survey notes into survex file format, transcribes sketch notes onto survex centre-lines, and
|
|
uses Therion to produce beautiful survey graphics of the caves he has digitised - but who is not a computer geek and whose brain oozes
|
|
out of his ears when Wookey explains what git is. Applies artistic graffiti to walls.
|
|
<li>The archivist who takes the survex files, the therion files, the GPS files, the scanned survex centrelines and files them in the
|
|
right places on the <em> expo laptop</em>, uses the troggle reports to help ensure that these are consistent and are filed correctly.
|
|
Uses troggle input forms to "create new cave" in the system and adds to the directory structures to match the recently discovered caves.
|
|
Is learning git. When transcribing bad handwriting in logbook (or struggling with git), climbs walls.
|
|
<li><em>Nerdus maximus</em>: talks python in his sleep and can rebase a hairy git branch without error after 7 bottles of Gosser.
|
|
Painfully averse to writing documentation. Overstressed, over-caffeinated and with a tendency to mutter that it's all obvious. Oblivious
|
|
to walls.
|
|
</ul>
|
|
<p>These are some of the "use cases" which troggle needs to be (re)designed to cope with.
|
|
|
|
<h2>Real example</h2>
|
|
<p>In March 2023, Radost analysed a lot of cave survey <a href="/years/2023/Fishface-SMK.html">and proposed</a> that there were 3 places
|
|
in 1623-204 Steinbrückenhöhle which were good candiates for linking in with 1623-290 Fischgesicht. So the task is to find the
|
|
records and find out how difficult those places are to get to, and what it looks like at the exploration limit. We want to find out
|
|
about Pretzel Passage.
|
|
|
|
<p>Start with the cave 1623-204 and read the cave
|
|
description. <ol><li>Start with the master caves list,
|
|
"Caves" on the left-hand menu on all handbook pages,
|
|
including this page you are reading now.
|
|
<li>Find 1623-204 and click on it. It goes to <a href=
|
|
"/1623/204/204.html">/1623/204/204.html</a>.
|
|
<li>204 has a cave description split up into multiple
|
|
pages, but there is "Glossary of Passage Names". So go to <a
|
|
href="/1623/204/atoz.html">/1623/204/atoz.html</a>
|
|
<li>Under 'P' we find no passage of that name. Bother. So
|
|
this is an obscre place not in the Cave Description.
|
|
<li>Next step is to look at all the survex files.
|
|
<li>Go back to the Cave Description page and find the
|
|
heading "Survex File(s)" and click on "All <a href=
|
|
"/survexfile/204">survexfiles</a> for this cave".
|
|
<li>Now do ctrl-F and search for "Pretzel"
|
|
<li>There are two surveys: pretzelpassage1 and <a href="/survexfile/caves-1623/204/midlevel/pretzelpassage2.svx">pretzelpassage2</a>.
|
|
Radost said it was pretzelpassage2.
|
|
<li>We can see already that it was Becka and Anthony Day who surveyed it on 27th Aug.2012, and that the raw data is in survey wallet <a
|
|
href="/survey_scans/2012%252345/">2012#45</a>.
|
|
<li>Click on <a href="/survexfile/caves-1623/204/midlevel/pretzelpassage2.svx">pretzelpassage2</a> to read the survex file.
|
|
<li>Bother, the survex file has no cave description in it, whcih is what we were hoping for.
|
|
<li>OK, look at the raw notes in the survey wallet <a href="/survey_scans/2012%252345/">2012#45</a>
|
|
<li>The wallet metadata tells us that the W tick-box is green, which means that either there was no cave description in the survex file
|
|
or that there was and it had been copied into the website cave description page: red means 'un-finished business'.
|
|
<li>We see a red box for "T" which means this trip has not been '"Tunneled" (or "Therioned"), or if it has, nobody has recorded it.
|
|
<li>We see that a Plan exists (green box) but no Elevation (red box).
|
|
<li>In the file list in the middle of the page we can see plan1.jpg and plan2.jpg. Click on them.
|
|
<li>Aha! "Stones rattle, sounds of water" that sounds like the lead we are looking for..
|
|
<li>Now we check through all the other data we have on things that happened on the same day. It is at the botoom of the page.
|
|
<li>Aha Again! A logbook entry <a href="/logbookentry/2012-08-27/2012-08-27a">" 204 - Survey Pretzl Passage below Big Boulder Chamber +
|
|
continue derig"</a>
|
|
<li>Click on it, and we at last find the passage description that we wanted. Which coupled with the hand-drawin plan sketches in the
|
|
wallet is all that we needed.
|
|
</ol>
|
|
|
|
|
|
<hr />
|
|
Go on to: <a href="trogarch.html">Troggle architecture</a><br />
|
|
Return to: <a href="trogintro.html">Troggle intro</a><br />
|
|
Troggle index:
|
|
<a href="trogindex.html">Index of all troggle documents</a><br />
|
|
|
|
<hr /></body>
|
|
</html>
|