If you have not come to this page from the sequence starting at Starting a New Cave" then go and read that first.
[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.]
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
/home/expo/loser/caves-1623/264/mongolrally.svxand tell someone nerdy when you have finished and they will ensure that it is saved, committed, and pushed appropriately.
If you have several parts of the cave surveyed on one trip, create several distinct .svx files.
Once you have created the .svx file you will run survex to generate a centre line, transcribe your sketches onto that paper, scan it again and then digitise into tunnel or therion.
[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 which is why we are only telling them to use the expo laptop.]
To be written.
to be documented
to be documented See drawing up the sketches.
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: /home/expo/expofiles/surveyscans/2018/2018#19/
to be documented
Tunnel only produces plan surveys, but they are very pretty.
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 drawings,
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.
to be documented
Write a passage descriptions by copying and extending the descriptions given in all the component .svx files.
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.
In written descriptions, underline passage names the first time they are mentioned, or when they are "defined".
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 troggle system.
to be documented
Complementing the passage description in vertical bits is a Rigging Guide. 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.
to be completed