Interim rigging guide
-The logbook is the place where we record the rigging of caves as we discover them. -
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 measured, 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.
+Initial rigging guide
+The logbook is the place where we record the rigging of caves as we discover them. You will manually copy the notes you made underground into the logbook. +
Writing up this and the final rigging guide is an important part of the Expo cave exploration process and is documented in a specific "rigging" section the survey handbook. +
The online logbook file
If you are at basecamp, then it is an excellent idea to type the text of your logbook trip report instead of writing it by hand - see below. But still do lots of drawings in the paper logbook. -
The contents of both the topcamp logbook and the basecamp logbook are typed into the same "logbook.html" file for future use in tracking down leads and surveys. The drawings are scanned and stored in the same place, and hand-edited into the logbook.html file after expo finished. The typed notes are uploaded into the expo server database and correlated with survey data done on the same day or by the same people. - -
Recent logbooks:
- 2018
@@ -75,6 +66,9 @@ which is then synchronised the version control system.
The result is a webpage reporting who did what and what was done by whom on expo, e.g. see the 2018 expo report. +
Typing your trip report - in the UK Caving Blog
+In recent years we have seen an admirable increase in the number of people writing up their trips and experiences on social media and in particular on the UK Caving blog, see 2019 Blog. But please, please also make a handwritten entry in the logbook saying you have done this so that the text and pictures can be transcribed later. It is too easy to lose these: in 2018 there were two blogs in operation and most people didn't know that. +
Typing just your trip report (at the Expo Laptop)
As handwriting can be very bad, please try to type the text, print it and stick it in the logbook, adding any sketches by hand. This will save someone (probably you) deciphering your handwriting and typing it up later. @@ -144,7 +138,7 @@ idea to type up just your trip(s) in a separate file, e.g. "logbook-mynew <div class="timeug">T/U 10 mins</div>
Note: the ID's must be unique, so are generated from 't' plus the trip date plus a,b,c etc. when there is more than one trip on a day.
-Note: T/U stands for "Time Underground" in hours (6 minutes would be "0.1 hours"). +
Note: T/U stands for "Time Underground" in minutes and/or hours. (We do not parse or collate this information so the format and units don't matter.)
Note: the <hr /> is significant and used in parsing, it is not just prettiness.
Note this special format "Top Camp - " in the triptitle line: @@ -152,7 +146,7 @@ when there is more than one trip on a day.
It denotes the cave or area the trip or activity happened in. It is a word or two separated from the rest of the triptitle with " - " (space-dash-space). Usual values for this are "Plateau", "Base camp", "264", "Balkon", "Tunnocks", "Travel" etc. -Note this special format "<u>Jenny Black</u>" in the trippeople line: +
Note this special format "<u>Jenny Black</u>" in the trip-people line:
guides are drawn for any new rigging or rerigging each year so that we can add rigging guides to the online cave descriptions.<div class="trippeople"><u>Jenny Black</u>, Olly Betts</div>This write-up should be done by the person who did the rigging at the first available moment: usually this will be in the top-camp logbook. -
See the making a rigging guide part of the survey preparation process for where and when to do the initial and the final rigging guides for a new cave you have discovered. +
See the New Rigging Guide part of the survey preparation process for where and when to do the initial and the final rigging guides for a new cave you have discovered. + +Instructions for the first, immediate rigging guide are in the Logbook write-up part of the survey handbook.
It's also essential for future years to record any gear left in situ, so that we can keep the
Interim rigging guide
-The logbook is the place where we record the rigging of caves as we discover them. For a particularly fine example of rigging guides in a logbook see the 2005 logbook. -+The logbook is the place where we record the rigging of caves as soon as possible after we discover them. For a particularly fine example of rigging guides in a logbook, scroll through the 2005 logbook. +
SAFETY: Sketched rigging guides are most intensively used during the few days after the pitch is first rigged, and this is also the time when accidents are most likely, so this is an occasion where hours count. Sketch the rigging in the logbook as soon as possible and make sure a copy is at both base camp and top camp. +
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 measured, 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. So please do this during the initial exploration and write it down in your survey notes.
-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 measured, 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. - - -Final rigging guide
- -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. +
Preparation of rigging notes
You will already have an "Interim rigging guide" in the logbook entries of the trips, and also sketches on waterproof paper which were made underground which were stored in the survey wallet and scanned to produce "notes-XXX.jpg" files in the online survey wallet for your trip. For small caves the logbook entry may be all you need. -
Collect together your notes for the rigging guide now, including all the pitch lengths. It is a good idea to copy these notes now and put them in the plastic survey wallet or to photograph them and put the files in the online survey wallets. The next step can take some time so get the rigging data in order now. -
You will enter the final rigging guide as part of the +
Collect together your notes for the rigging guide now, including all the pitch lengths. It is a good idea to copy these notes now and put them in the plastic survey wallet or to photograph them and put the files in the online survey wallets. The next step of doing the survey can take some time so get the rigging data in order now so that it doesn't get forgotten. + +
Final rigging guide
+ +A Rigging Guide of the vertical sections is published with the cave survey and the cave passage descriptions in the cave guide after surveying is complete. + +This is usually easiest to do as a sketch, but must include notes to +ensure that all bolts can be found again and any deviations and natural belays recognised for re-rigging in future. + +
You will enter the final rigging guide sketch as a scanned drawing within the cave description when you edit the HTML pages for the online cave documentation. This is done using the "New Cave" online form. -
You should also produce a separate rigging guide document which will live in - expofiles/rigging_topos/ e.g. see - expofiles/rigging_topos/264/entrance_topo_2016.pdf - but also /expofiles/rigging_topos/264/entrance_topo2_2016.jpeg +
Your initial rigging guide might be needed with some urgency during expo while exploration continues, so this is the place to put it.
See also the part of the bolting & rigging handbook which discusses writing up your rigging attempts. +
Filing and Finding rigging guides
+There are three different activities for rigging topos: +
-
+
- drawing them up (either scanning or re-drawing scrappy images out of logbooks), +
- making them findable/appear in cave descriptions, +
- (optionally) making prettier versions for important caves which have complex rigging. +
The simple and nicest-looking way to make them findable is to add them to the HTML inline in cave descriptions. For a finished example see the rigging topo for the "Merry Go Round" pitches in the Swings and Roundabouts area in 204. + +Creating a new cave in the online system is how you create the inline HTML. It is the next step in this Survey Handbook sequence of pages.
[To Do - improve documentatiton for how to add in image files in cave descriptions] + +You should produce a separate rigging guide file for each connected set of pitches which will live in
+ expofiles/rigging_topos/ e.g. see
+ expofiles/rigging_topos/264/entrance_topo_2016.pdf
+ but also (to demonstrate that something is always better than nothing):
+ expofiles/rigging_topos/264/entrance_topo2_2016.jpeg + +The format is important. Please don't use PDF: if you are scanning a hand-drawn sketch then JPEG is best for our purposes as it is compact and we reuse it easily elsewhere in the system. +
If you are using a drawing package then produce the file in SVG format. +Inkscape is what most cavers use as it's free and stable. This will make it possible to edit and update your topo in future. + +
Discussions on Expo Slack after the 2019 expo resulting in us consolidating rigging topo files into expofiles/rigging_topos/ when previously they had had a number of different homes. So if you remember putting them somewhere else int he past, don't do that now. Put them in expofiles/rigging_topos/. + +
[ We could dream up some fancy scheme for indexing the rigging for every pitch in the system and add that +into troggle but frankly we don't think it's worth the effort.] +
Back to the previous page in this sequence Drawing up your survey.
Now go the the next page in this sequence Creating a new cave in the online system. diff --git a/handbook/troggle/trogindex.html b/handbook/troggle/trogindex.html index b269e9ad1..eebf62870 100644 --- a/handbook/troggle/trogindex.html +++ b/handbook/troggle/trogindex.html @@ -10,15 +10,15 @@Handbook Troggle - Index
The number of different webpages describing troggle, configuring the server troggle runs on, maintaining the underlying Django system, current documentation, future design issues and historical decisions is all getting a bit voluminous. So we need a complete index: -
-Troggle Introduction - what it is
+
+Troggle - Introduction - what it is
Troggle - the users - Who needs to know What and When
Troggle - Fixing things - users' manuals for data import
-Troggle Data Import - reset and import data
-Troggle Maintenance - list of maintenance tasks
-Troggle Architecture - diagrams, files, structure
-Troggle Data Model - syntax-coloured list of Classes, instance variables and foregin keys
-Troggle Design Decisions for the Future - open issues being worked on
+Troggle - Data Import - reset and import data
+Troggle - Maintenance - list of maintenance tasks
+Troggle - Architecture - diagrams, files, structure
+Troggle - Data Model - syntax-coloured list of classes, instance variables and foreign keys
+Troggle - Design Decisions for the Future - open issues being worked on:
- Troggle - a kinder simpler troggle? - Radost's proposals (critiqued)
- Troggle Architecture Speculations - as in April 2020
@@ -27,7 +27,7 @@ - Troggle Menu Design - options for replacing the menuing system
-Troggle Unit Tests - test suite for programmers
+Troggle unit tests - test suite for programmers
Troggle & Expo Systems - status update - where we are now
diff --git a/handbook/troggle/trogmanual.html b/handbook/troggle/trogmanual.html index 6a24104fa..a3ca24796 100644 --- a/handbook/troggle/trogmanual.html +++ b/handbook/troggle/trogmanual.html @@ -31,6 +31,8 @@
Go on to: Troggle architecture
Return to: Troggle intro
+Troggle index: +Index of all troggle documents
