expoweb/handbook/survey/newcave.html

263 lines
13 KiB
HTML

<html>
<head>
<title>Handbook - Doing a new cave</title>
<link rel="stylesheet" type="text/css" href="../../css/main2.css" />
</head>
<body>
<h2 id="tophead">CUCC Expedition Handbook - New Cave</h2>
<h1>Creating a new cave in the online system</h1>
<h2>Great, I have discovered a new cave...</h2>
<p>So, you have staggered off the plateau with a fist-full of notes and surveys,
and you want to let the world know of your massive discovery.
<ul>
<li>If you have not yet learned how to record your prospecting and survey
your leads, read the <a href="../look4.htm">prospecting introduction</a> and
<a href="../survey/index.htm">survey handbook</a> which tells you how to record
survey information in your waterproof notebook. But first you should read the
<a href="/expofiles/presentations/cave_surveying_20130626.pdf">
Cave Surveying training course slidepack</a>.
<li>This page outlines the rest of the process. Each part of it is documented separately.
</ul>
<h2>Process</h2>
<p>After 40 years or so, we have a well-defined process which you will need to learn.
Read <em>all</em> this list first, then follow
the instructions section by section which tell you how to
actually do these things.
<ul>
<li>Write up your trip in the <a href="../logbooks.html">logbook</a><br><br>
<li>Put notes in a new wallet
<li>Scan the notes (see <a href="#onlinew">below</a> for the filenames to use and <a href="#scan">how to use the scanner</a>)
<li>Type in survey data (in the right place in the file system) in <a href="#survexformat">survex format</a>.<br>
(This includes passage descriptions and open leads known as QMs: Question Marks).
<li>Run survex to create a centre-line printout
<li>Transcribe your sketches onto centre-line paper
<li>Scan your centre-lined sketches
<li>Use tunnel to digitise your centre-line sketches
</ul>
<p>and either later or at the same time, you will be doing these other tasks
<ul>
<li>Create a new folder in the file system for the wallet data
<li>Create a new folder in the file system for the survex data
<li>Create a "new cave entry" for the guidebook description
<li>Write the <b>full cave description</b> into the correct html files. <br>
(This will mean copying the passage descriptions from the survex files.)
<li>Update the index tick boxes on paper: as your wallet progresses through this process
<li>Update the online record of those tick boxes
<li>Regenerate the <a href="http://expo.survex.com/expofiles/surveyscans/2018/">list of outstanding survey tasks</a> for everyone
</ul>
<p>This documentation assumes that you have recorded your survey data in
a waterproof paper notebook. If instead you are using a PDA to record the survey readings
digitally for your first cave, don't. Use the paper process first, then when you are familiar
the overall process, look at the <a href="pdanotes.html">PDA additional notes</a>.
<h3 id="newwallet">Starting a new wallet</h3>
<ol>
<li>Put all your written notes into the next empty "wallet":
(a transparent folder/envelope) in this year's lever-arch file labelled
e.g. "Expo Survey 2018" in the potato hut*.
<li>The wallet has a paper sticky label on it with the wallet-identifier,
e.g. <b>2018#22</b>, already printed on the label.
<li>Write the date and the names of the people on the trip on the label.
<li>Tick whether your trip was a surface or a cave trip.
<li>Write the name of the cave (with number if you know it), e.g. "264 Balkon"
<li>Write the area in the cave you did your surveying, e.g. "mongol rally"<br>
<li>Now turn to the index sheets at the front of the folder,
and fill in the line (e.g. 2018#22) for your wallet
<ul>
<li>"264 mongol rally"
<li>date of trip
<li>people who were on it
<li>then there are a lot of tick boxes. The explanations for these will come later.
</ul>
<li>Now, if you have not done it immediately after you left the cave,
photograph all the pages of survey notes with your phone.
Get one or more of the people also on the trip to do this too.
</ol>
<p>* As people spend longer and longer at top camp, we may establish
a wallet file at top camp
too, with pre-allocated numbers.
<p>The original notes and sketches should be filed in the clearly marked
wallet. Rip them out of the notebook, don't take them caving again and <em>don't leave them lying around to
be "G&ouml;ssered"!</em></p>
<p>The notes (all of them, including dates, personnel, calibration, LRUD,
station details, etc.) should be filed away in the wallet in the current year's
surveys file. You should include a transcription on a sheet of paper if they are illegible
(to other people; if you can't read them yourself, go back and do the survey
again!). Even if you do this, never throw away the original notes.</p>
<!-- Original text: ...copied onto a fresh page of the Survey Book
while everyone's memory is still fresh (this helps if something is only
marginally legible). This should be proof checked by someone else. Current
survey books are divided into "Kaninchenh&ouml;hle" (usually referred to as
"KH Survey book") and "surface stuff and other caves" (usually referred to as
"notKH survey book"). There should be an index page at the front, which you
should also fill in so that people can find your survey again.</p>-->
<h3 id="onlinew">Scan the notes into the online wallet</h3>
<p>Each wallet has a corresponding folder in the online system where a record is kept
of what information is in the wallet and where the corresponding survey data is filed:
<pre>
/expofiles/surveyscans/2018/2018#22/
</pre>
<p>This is where the scanned (or photographed) copies of the survey notes are kept.
<p id="scan">To use the scanner attached to the <em>expo laptop</em>, select the "Simple Scan"
icon from the vertical menu of icons which you get by clicking on
"Activities" in the top lefthand corner of the screen.
<p style="margin-left:20px">[ Normal people should skip this, <br>&nbsp;
but nerds need to look here
for the <a href="onlinewallet.html">online wallet maintenance process</a> ].
<p>If your initial backup photos of your notes were poor quality, use the
scanner in the potato hut to make better copies. Scan to JPEG format as .jpg files.
<p>Name the scanned pages "<em>notes-1.jpg</em>, or perferably <em>notes-cavepassagename.jpg</em>" etc. This is important as a script detects whether these files exist
(with names beginning "notes.." and "elev..") and if you name them something else it will hassle you unnecessarily.
<p>[ Note to maintainers: do not rename these files even if they have been created with the wrong names.
They are permanently referred to by the tunnel/therion/troggle system !]
<p>Scanned survey notes are voluminous and so are not kept in the version control system. Instead it is all kept
in the file bucket "expofiles" on the expo server in Cambridge.
<p>You will be using the expo laptop to do the scanning
and you will put all the scan files in the folder for your wallet, e.g. for 2018#19 it is:
<pre>
/home/expo/expofiles/surveyscans/2018/2018#19/
</pre>
and tell someone nerdy when you have finished and they will
ensure that it is copied to the expo server.
[ If you want to do this yourself, or are using your own laptop, then learn how to use Filezilla
- as <a href="../uploading.html">documented for uploading your expo photographs</a>. The correct folder
on the expo server is the same as that on the expo laptop- because we set up the expo laptop to be like that.
But <em>only copy files to the server that you created yourself and which live in your own wallet folder</em> ]
<h3 id="runsurvex">Storing your electronic survey files</h3>
<p>If you used a PDA instead of making notes on paper, you need to store your .topo files in the right place.
<p>If you using the expo laptop you can put the .topo files in a special "X" folder for your virtual
wallet, as there is no physical wallet,
e.g. for 2018#X16 it would be:
<pre>
/home/expo/expofiles/surveyscans/2018/2018#X16/
</pre>
and tell someone nerdy when you have finished and they will
ensure that it is copied from the <em>expo laptop</em> to the expo server.
<p>[ If all else fails, use the "Upload your photos" documented process and store
the .topo files where you would have stored your .jpg photo files. Otherwise you can email all the .topo files
to a friendly nerd who will put them in the right place. ]
<p><em>to be further documented - probably in a separate page</em>
<h3 id="survexformat">Typing in the survey data in survex format</h3>
<p>[This has been described in several places and we are in the process of consolidating
the documentation and getting rid of out of date notes.]
<p>The survey data typed up must include all the notes, including station details and passage
names. Make a backup copy to another machine or USB stick as soon as you have typed it in.
New users will be using the expo laptop to create the .svx file and
you will put it in the folder
<pre>
/home/expo/loser/caves-1623/264/mongolrally.svx
</pre>
and tell someone nerdy when you have finished and they will
ensure that it is <em>saved, committed, </em>and<em> pushed</em> appropriately.
<p>If you have several parts of the cave surveyed on one trip, create several distinct .svx files.
<ul>
<li><a href="how_to_make_a_survex_file.pdf">How to make a survex file</a> - PDF
<li><a href="getin.htm">From muddy book to survex plot</a> - the survex file format (to be revised)
<li><a href="drawup.htm">Drawing up your survey</a> - incomplete and a bit out of date
<li><a href="athome.htm">Back in the UK</a> - not really part of the process
<li><a href="/expofiles/presentations/cave_surveying_20130626.pdf">Cave Surveying - training course slidepack</a>
</ul>
<p>[Nerds: survex cave data belongs in the repository "loser", e.g.
loser "caves-1623/264/mongolrally.svx". We are assuming that normal users have never
worked with an distributed version control system at this point whcih is why we are only
telling them to use the <em>expo laptop</em>.]
<h3 id="runsurvex">Running survex to create a centre-line</h3>
<p><em>to be documented</em>
<h3>Transcribing and re-scanning your sketches</h3>
<p><em>to be documented</em> See <a href="drawup.htm">drawing up the sketches</a>.
<p>The files of your scanned and re-scanned sketches should be stored in the same folder
as the scanned notes, i.e. (for wallet #19) you would put them in:
<pre>
/home/expo/expofiles/surveyscans/2018/2018#19/
</pre>
<h3>Using tunnel (or therion) for final survey production</h3>
<p><em>to be documented</em>
<ul>
<li><a href="/expofiles/tunnelwiki/wiki/pages/Tunnel.html">Tunnel tutorial</a> - a wiki of examples and tutorials
</ul>
<p>Tunnel only produces plan surveys, but they are very pretty.
<p>The tunnel (or therion) files should NOT stored in the same folder as the scanned notes. They should
be uploaded to the version control repository //tunneldata//.
<h3>Interim rigging guide</h3>
<p>The logbook is the place where we record the rigging of caves as we discover them.
<p>When a cave is derigged,
a good way of getting the rope lengths for your rigging guide is to
leave the knots in ropes removed so they can
be <b>measured</b>, but these days our caves are a bit deep
and complicated for this to be feasible.
Although a good survey and details of the belays
can be used to estimate the length of rope needed, this is no substitute for
measuring how much rope it actually took to rig.</p>
<h3>Guidebook description and final rigging guide</h3>
<p>This is the last thing to do - typically after all exploration has been finished for the summer.
The rigging guide sections will have been written into the logbook, and the passage descriptions will
have been written into the survex files, with more lyrical descriptions written into the logbook for each trip.
<p><em>to be documented</em>
<p>Write a <b>passage descriptions</b> by copying and extending the descriptions
given in all the component .svx files.
<p>This should be detailed enough to be
followed by someone in the cave who hasn't been there before, and should
include all passage names, lengths of pitches and climbs, compass directions
when this makes left/right/ahead clearer. If your passage is a connection
it is worth while writing descriptions from both directions.
<p>In
written descriptions, underline passage names the first time they are
mentioned, or when they are "defined".</p>
<p>
You will type this description, and pass it on to someone more nerdy who
will file it in the right place. This will involve "creating a new cave" using the <a href="../troggle-ish.html">troggle</a> system.
<p><em>to be documented</em>
<p>Complementing the passage description in vertical bits is a <b>Rigging
Guide</b>. This is usually easiest to do as a sketch, but include notes to
ensure that all bolts can be found again and any deviations and natural belays recognised.
<p><em>to be completed</em>
<hr />
<ul id="links">
<li><a href="../index.htm">Expedition Handbook</a>
<li><a href="index.htm">Survey Handbook</a>
</ul>
</body>
</html>