expo/expoweb
1
0
Fork 0
mirror of https://expo.survex.com/repositories/expoweb/.git/ synced 2024-11-26 01:01:58 +00:00
Code Issues Packages Projects Releases Wiki Activity

Removed half-baked to do scripting

Browse Source
This commit is contained in:
Philip Sargent 2022-06-25 23:00:48 +03:00
parent e4b92a8209
commit 5c3e7d39d8
4 changed files with 467 additions and 680 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

758
handbook/computing/todo-data.html
View File

@ -6,403 +6,117 @@
<meta name="keywords" content="NOEDIT">
</head>
<body>
<script src="todo.js" defer></script>
<link rel="stylesheet" type="text/css" href="todo-styles.css" />
<h1>Data Updating To-Do List</h1>
<button onclick="window.location.href = 'todo-data.html_edit';">Edit this to-do list</button>
<!--
<button onclick="window.location.href = 'todo.html_edit';">Update this to-do list</button>
-->
<!--
<label for="toggle-1">Toggle visibility of all sub-items</label>
<input type="checkbox" id="toggle-1">
-->
<!-- ------------------- Don't touch anything above this line --------------------------->
<style>
li.todo {
font: 18px Calibri, sanserif;
font-weight: normal;
color: 6083BF;
list-style-type: None;
line-height: 1.0;
margin-left: 1.0em;
}
li.todo:before {
content: "» ";
font-weight: normal;
color: 6083BF;
}
</style>
<h1>Data Updating To-Do List</h1>
<h2>How this works</h2>
<p><b>Click twice on a sub-heading to reveal</b> the individual to-do items. Click again to hide.<br />
If a heading is in italics, then there are hidden items.
<p><b>Click on the main "How this works" heading</b> to toggle reveal/hide <b>everything.</b>
<p>Printing this page uses a much smaller font. Complain to <a href="mailto:expo-tech@lists.wookware.org">the nerd list</a> if you don't like this behaviour.
<p>Edit this page by clicking on the big blue button. It uses the same "Edit this page" function that you may have used before. Just be careful not to touch the code at the top of the page.
<p>Edit this page by clicking on the "Edit this page" menu item.
It uses the same "Edit this page" function that you may have used before.
<p>We were working on a more capable and easier-to-use system which would mimic
how <a href="https://github.com/CaveSurveying/CUCCexposurveyissues/issues">GitHub Issues</a> do this sort of thing,
but now we are just going to use standard HTML5 tags. This page is only partly converted to use HTML5 tags instead of javascript. Sorry.
but now we are just going to use standard HTML5 tags.
<h2>Cave Data Updating</h2>
<p>To see the "handbook updating" and "troggle/system" to-do lists, go to <a href="todo.html">the other TO-DO list</a>
<details><summary><!-- date ? -->Update Cave Number <=> Kataster list</summary>
<li>:expoweb:/noinfo/cave-number-index last updated in 2016
<li class="todo">:expoweb:/noinfo/cave-number-index last updated in 2016
</details>
<details><summary><!-- date ? -->:expoweb:/noinfo/katasterable-or-not needs updating. PENDING - 2015, 2000</summary>
<li>Check that the list from :expoweb:/pending/2015/katasterable has been done.
<li class="todo">Check that the list from :expoweb:/pending/2015/katasterable has been done.
[Last Updated 8th Feb. 2016 by Wookey] latest kept in noinfo/cave-number-index (?). Wookey to confirm and delete older copy in pending/2015/
<li>Check that the 4 lists in :expoweb:/pending/2000/ have been done. Anything not done to be moved into this to-do list.
<li class="todo">Check that the 4 lists in :expoweb:/pending/2000/ have been done. Anything not done to be moved into this to-do list.
</details>
<h3>Cave photos needed, especially entrances</h3>
<details><summary><!--2020-04-30 becka-->New katastered caves need photos</summary>
<li>1626/359 Homecoming Cave Heimkehrh&ouml;hle 2018-dm-07
<li>1623/290 Fish Face Cave Fischgesicht-H&ouml;hle 2017_cucc_28
<li>1623/291 Happy Butterfly Cave Gl&uuml;ckliche-Schmetterlingsh&ouml;hle
<li>1623/285 Knackered Tacklesack Cave Geknackter-Packsackh&ouml;hle 2006-08
<li>1623/288 Purple Lupin Cave Lila Lupinenh&ouml;hle 2015-mf-06
<li>2015_cucc_24
<li>1623/295 No Watermelon Cave Keine-Wassermelone-H&ouml;hle cucc-2017-23
<li>1623/293 Blocked Air Cave Blocklufth&ouml;hle 2010-03
<li>1623/296 Double Gemse Cave Doppel-Gemse-H&ouml;hle 2012-70
<li class="todo">1626/359 Homecoming Cave Heimkehrh&ouml;hle 2018-dm-07
<li class="todo">1623/290 Fish Face Cave Fischgesicht-H&ouml;hle 2017_cucc_28
<li class="todo">1623/291 Happy Butterfly Cave Gl&uuml;ckliche-Schmetterlingsh&ouml;hle
<li class="todo">1623/285 Knackered Tacklesack Cave Geknackter-Packsackh&ouml;hle 2006-08
<li class="todo">1623/288 Purple Lupin Cave Lila Lupinenh&ouml;hle 2015-mf-06
<li class="todo">2015_cucc_24
<li class="todo">1623/295 No Watermelon Cave Keine-Wassermelone-H&ouml;hle cucc-2017-23
<li class="todo">1623/293 Blocked Air Cave Blocklufth&ouml;hle 2010-03
<li class="todo">1623/296 Double Gemse Cave Doppel-Gemse-H&ouml;hle 2012-70
</details>
<h3>Logbook fettling</h3>
<details><summary>2019 Logbook</summary>
<li> transcribe the rest of those UKcaving blog entries into expoweb/years/2019/logbook.html
<li><!--2020-04-03 psargent-->
<li class="todo"> transcribe the rest of those UKcaving blog entries into expoweb/years/2019/logbook.html
<li class="todo"><!--2020-04-03 psargent-->
copy the photos from the UKCaving blog into expofiles/photos/2019/<MyName>/ -- in fact many of those photos are already there
<li><!--2020-04-03 psargent-->edit in the links to those photos in the right place in 2019/logbook.html
<li class="todo"><!--2020-04-03 psargent-->edit in the links to those photos in the right place in 2019/logbook.html
</details>
<details><summary>Garlic cave</summary>
<li> edit logbook entries 2018, 2019 to link to extensive photos of Garlic cave area {Withnall 2018} , {Becka 2019}
<li class="todo"> edit logbook entries 2018, 2019 to link to extensive photos of Garlic cave area {Withnall 2018} , {Becka 2019}
</details>
<details><summary>Add missing images to logbooks</summary>
<li><!--2020-04-30 psargent-->
<li class="todo"><!--2020-04-30 psargent-->
2018, 2009, 2008, 2001 , 2000, 1992, 1989,..2011? List here: <a href="../../pubs.htm">pubs.htm</a> Previous years HTML logbooks are missing images extracted from scanned PDF copies of the logbooks. </dd>
<li>2018 logbook:
<li class="todo">2018 logbook:
<!--2020-05-10 psargent--> RENAME files of photos /2018/BlogPostPhotos/* from .JPG to .jpg as the generated .xml files get confused.
<li>2011 logbook:
<li class="todo">2011 logbook:
type up via-ferrate & bolt-testing writeups (In paper book, not in scan or HTML)
<li><!--2020-07-24 psargent-->1982 Logbook - no diagrams.
<li class="todo"><!--2020-07-24 psargent-->1982 Logbook - no diagrams.
It has been typed but there are no diagrams. Scanned PDF recently acquired.
<li>200? logbook:
<li class="todo">200? logbook:
Type up "list of GPS locations still to type"
</details>
<h3>Wallets/Scan fettling</font></h3>
<details><summary>2018 surveyscans & wallets</summary>
<li><!--2020-05-10 psargent--> merge /copies/ subfolder in 2018#10 & 2018#22 - there should be no subfolders. Are they just duplicates?
<li>wallets and SVX file *refs.
<li class="todo"><!--2020-05-10 psargent--> merge /copies/ subfolder in 2018#10 & 2018#22 - there should be no subfolders. Are they just duplicates?
<li class="todo">wallets and SVX file *refs.
<!--2020-05-10 psargent--> Look at <a href="../../svxvalid.html">svxvalid.html</a> and resolve all the MISMATCH errors in *ref and .json 'survexfile' links
</dl>
</details>
<h3>Tunneling to do</font></h3>
<dl>
<dt><!--2020-04-12 wookey-->1623/251</dt>
<dd>Put in tunnel plan instead of scan of drawn-up notes.</dd>
<dd>Draw up elevation (therion)</dd>
<details><summary><!--2020-04-12 wookey-->1623/251</summary>
<li class="todo">Put in tunnel plan instead of scan of drawn-up notes.</li>
<li class="todo">Draw up elevation (therion)</li>
</details>
<h3><font color="fuchsia">Tackle Store Records</font></h3>
<dl>
<dt>No authoritative list of where the expo paper records are!
<dd><!--2020-04-03 psargent-->NO expo paperwork at all prior to 2008 in Tackle Store - where is it ?
<dd><!--2020-04-03 psargent-->FIND where all the wallet binders are, and the logbooks.
< <dd><!--2020-04-03 psargent--> BUY A4 plastic boxes for filing cabinet for logbooks getting damp there.
<dd>2017, 2018, 2019 wallet binders are in Philip S.'s house.
</dl>
<h3><!--2020-04-17 psargent-->:expoweb:/1623/264/cavedescription2016<br><br> (All moved verbatim, original to-do file now empty.)</h3>
<dl>
<dt>
tightyorkshireman
<dd>
person size phreatic tube, left passage emerges at pitch head, right passage becomes too tight.
<dt>
rabbitwarrens
<dd>
Sandy crabwalk turning into a tube parallel to main passage connecting to ein und zwanzig
<dt>
noserock2
<dd>
Pitch dropped round the corner from the pitch in noserock. Lots of
break-down and pitch ended in a choked chamber floor.
<dt>
northhole
<dd>
;Small grotty hole in the floor of eis koek aven, which connects through to the nearby large hole down to a circular ice floor.
<dt>
northhole2
<dd>
; continuing north from northhole, there is a series of freeclimbable avens going upward, the final survey station is at an awkward but not impassable squeeze. A handline would be very helpful in coming back down. There are also two connections to the frozen north, one is a tube at head height and the other is a small crawl at the start of the choss slope leading to the first aven climb.
<dt>
icecockLC1
<dd>
;linking icecock aven to the ice pit in north hole.
<dt>
icecock3
<dd>
;small sandy floored tube connecting the icecock bypass to the northhole passage
<dt>
gosserwager2
<dd>
linking the bottom of the pitch (name?) to the rift above gosser wager and the pitch down to it, continuing to a boulder choke.
<dt>
gosserwager3
<dd>
Rift passage heading South, with a 15m pitch at head. Clean walls, rubble floor. Leads to short down climb before more rift and another pitch series.
<dt>
frozennorth
<dd>
climb up between wall and block, aided by two bolts, to enter ice lake
chamber. Ahead is a large aven with snow slope entering. Just before
this is a small passage on the right. Climb up into this and follow
ice inlet until breaks out into large aven and trench area at station
12. To the south is/was unexplored, but later connected to rest of
cave. To left is small sanding tube to view into same trench system.
<dt>
frozennorth4
<dd>
left juction in frozennorth where there are sandy crawls, comes out on
a precarious ledge above a big hole. Traversing around this leads to a
medium sized sandy crawl sloping downwards to a huge chamber with a
pitch suspected to be the north end of lead 93B from the start of
expo2015 in turtlehead.
<dt>
frozennorth3:
<dd>
A rift passage that loops round and links 2 chambers, with possible leads at the end at station 5.
<dt>
darkartsiv:
<dd>
continuing A lead at south end of dark arts, went in then surveyed out but didn't make it all the way to connect up the surveys.
<dt>
cathedralLC2:
<dd>
Linking avalancheexperience to cathedralchasm without having to use the dodgy data in chamber90b survey
<dt>
cathedralchasm:
<dd>
really fucking huge chamber with many good leads. turns out it was already surveyed as chamber90b be Julian.
<dt>
catherdralchasm2
<dd>
Coming fdrom Cathedral Kazam a wet traverse across a pitch David
dropped a setter down. Passage continues to chamber with a loop coming
off to the left up and emerging at top of chamber en route. from
cahmber a rift goes off up right with main passgae continueing
straight. Also a small lead to left leads round to two small 5m pitchs
containg crystal formations. A traverse continues on with another
pitch. Taking the main route from the chamber a sandy passage leads
past three bat skeletons before becoming a crawl, eventually reaching
a junction. the larger passge to the left links back to the passge
near trident junction/ gear dump. This bypass is now the recommended
wat to reach cathedral kazam.
<dt>
bipedal:
<dd>
heading south out of amalgamation you arrive at a large long hole in the floor. Partial completion of traverse over hole, plus exploratin of two small side leads. Left over small rock bridge ends in blind pot. Right hand small passage soon becomes too tight.
<dt>
bipedalpassage5
<dd>
short pitch down to large aven chamber with vedose rift in floorway.
<dt>
hiltigalactica
<dd>
After dropping initial pitch (Deep Space 9) approx 25m in hilt-a-plenty.
After dropping initial pitch (Deep Space 9) approx 25m in hilt-a-plenty.
Long rocky chamber from bottom of pitch to next unexplored pitch.
Slope near end up left ends after short distance. Small side passage near
start on right continues to small sandy chamber with several leads.
From here archway leads onto bouldery ledge in side of very large chamber
to be explored.
</dl>
<h3><!--2020-04-19 psargent-->/expofiles/surveyscans/2017/2017notes.txt<br><br> (All moved verbatim, original to-do file now empty.)</h3>
<dl>
<dt>258
<dd>
<pre>
import other 258 files:
pawpaw
notthebeast
To draw up!!!
258/whatwouldyourmothersay.svx needs drawing up from notes in 2016#27 (we missed it out)
</pre>
<dt>264
<dd>
<pre>264/doublescoop from notes in 2016#34
nothingtosee3: 264/wallet 2017#52 needs printing out and drawing up
dogendseries: 2017#42 notesplan
Need to find the snow symbol
How to make the jar file work again (and then update all copies in svn)
nothingtosee --> imported
sloppyseconds2 --> imported
naturecalls --> imported
created 264post2017b
created sloppysecondspart
Sync 2016#19 snowhole back to expo computer (as well as whole of 2017)
Rescan notes for 2017#50 (cropped)
queries:
2017#12. 264/nothingtosee ULSA distoX. Length calibration -0.05 ('tape too long'). Is that right?
2017#15 not_the_best elevation drawn, but not beastsideleads? Plans for bth
======================
To get the files here:
rsync -av expo@expo.survex.com:expofiles/surveyscans/2017/ /home/julian/data/expodata/expofiles/surveyscans/2017/
To copy a rendered survey up:
scp /home/julian/data/expodata/tunneldata/2017-09-28incomplete1.png expo@expo.survex.com:expofiles/surveys/
======================
tunnocks high level
not_the_beast 2017#15
rigormortis 2017#43
</pre>
<dt>tunnocks deep stuff
<dd>
<pre>
mastercave 2017#16 drawnin
gryke of the earth 2017#17
loserlido 2017#44
snakecharmer 2017#06
slackerstidyup 2017#05 background
raisinhell 2017#04
therestherub 2017#02 drawn
snakecharmer2 2017#31
snakecharmer3 2017#32
hipsterreturn 2017#35
lowersnakebite 2017#40
beckoningsilence 2017#41 drawnin
bahama 2017#45
</pre>
<dt>cathedralchasm offshoots
<dd>
<pre>
the_mendips 2017#18 !!!Missing folder!!! no drawing
mysterious_schlag 2017#19 is a pitch in cathedralchasm
pointless_dig 2017#20
naturecalls 2017#47 not tied in from bottom of Ash's pitch in cathedral chasm bit (have faked it)
</pre>
<dt>galactica area fuckups
<dd>
<pre>
sloppyseconds1 2017#01
galactica 2017#03
sloppyseconds2 2017#07
sloppyseconds 2017#42 dogendseries
secondhand 2017#49
missing bit 2017#52
nothingtosee 2017#12
nothing2see ??? lost wallet #24 centreline typed
nothingtosee3 2017#52 recovered
hilti_nts_bones_pitch 2017#21 -linked in now
hilti_nts_near_bats 2017#22 -linked in now
hilti_nts_near_start 2017#23
nothingtosee 2017#39
</pre>
<dt>surface crap
<dd>
<pre>
prospecting 2017#08
prospecting 2017#09
prospecting 2017#10
prospecting 2017#11
prospecting 2017#24 !!! not nothing2see as documented
watermelon 2017#28
kitten-helicopter 2017#33
prospecting 2017#34
</pre>
<dt>Fish Gesicht (2017-cucc-28)
<dd>
<pre>
fishface 2017#38
fishface 2017#46
windytube 2017#37
icytube 2017#48
fgh 2017#50
blitzen 2017#53
</pre>
<dt>GSH
<dd>
<pre>
gsh entrance 2017#25
gsh 2017#26
coulda 2017#27
gsh 2017#29
riftpiece 2017#30
</pre>
<dt>Bad Forecast (2017-pw-01)
<dd>
<pre>
gardeningshoots 2017#13
thirdentrance 2017#14
badforecast 2017#51
</pre>
</dl>
<h3><!--2020-04-17 psargent-->:expoweb:/1623/264/trident_to_little_boy.txt<br><br> (All moved verbatim, original to-do file now empty.)</h3>
<dl>
<dt>
Cave: Balcony (Far Side to Deep Balcony)
<dd>
Trident is a four way junction- take the left fork to an alcove on the left with an obscure mud floored crawl. This is followed for 10m, improving to walking height. Follow past two bat skeletons then right turn to another bat; continue ~20m. A mud floored junction, turn right to the head of a traverse then pitch after 10m. Straight on would have led you to a noteworthy drippy pitch (Kathedral Chasm).
<dt>
----Honeycomb----
<dd>
The traverse to pitch is the beginning of Honeycomb (50m of pitches). This swings to a window, following the rope to a ledge 10m above the floor. From here there's a narrow popcorn-lined climb to the head of a 7m pitch. At the bottom, climb the slope and follow obvious continuation (draught) to the head of 12m pitch. This pitch lands at the top of Hangman (p30), on account of the huge hanging boulder. (The near side of the boulder descends to the way on to the top of Mongol Rally, whereas the far side of the boulder is rigged to swing into a window half way down, Myopia. This is a passage heading north, traversing around a large pit, leading to another pitch which could be traversed around, ?a.)
<dt>
----Nature Calls----
<dd>
At the bottom, follow the traverse round to a mudslope. At the top of the mudslope there is an awkward crawl for 10m, soon improves to walking. Follow this passage for 30m. There's a p5, follow the rope to the head of the Mongol Rally (p200).
<dt>
----Mongol Rally and Little Boy----
<dd>
Descending this rope lands into a roomy boulder chamber. Walking down the slope between boulders (distinguished path in the mud), leads to a blind pit and big aven. A right turn takes you to stooping height passage, for 50m to the head of Little Boy pitch (20m). There is a significant draught here; follow this. The camp is currently at the base of the pitch (August 2018).
<dt>
----Water collection----
<dd>
There are three exits to the chamber. <br>
1. a short crawl <br>
2. a climb down on the far side. <br>
Both lead to the same place and draught.
<br><br>
Leave on the far side of the chamber, via a climb down and turn right, climbing down a boulder into pleasent walking passage, very straight and heading north. The floor is soft wet mud. After ~100m a stream trench enters on the right, followed round a corner into a drippy aven. Collect water here, scoop (mug) advisable.
<br>
(Currently unconnected from Grand Prix)
<dt>
----One direction----
<dd>
A little further on from the right turn towards the water cllection, is a muddy ledge on the left hand side (1m from ground). Low crawl continues for 100m in straight line, over three puddles. Stal, but largely unnoteworthy. Ends at the Tsection into clean washed tall rift with sounds of water. Downhill leads to promising a lead, in clean washed rock, sketchy c6, requires rope, heads into rifty stuff. Uphill, includes split (meander) to scoopy loopy junction.
<dt>
----Scoopy Loopy----
<dd>
Scoop it until you loop it. Junction has small a lead on right hand wall, to sound of wet rift. Obvious way on cuts left, walking passage heading upwards until low crawl into breakdown chamber. A climb on the right links into Grand Prix.
<dt>
----Nothing to do with you traverse---- (ntdwyt)
<dd>
The passage towards the water collection is followed, beyond the turning for water. This leads to a pitch down (Indy Rally) or a traverse left. The traverse left goes ~10m, before muddy walking passage ~30m until it chokes.
<dt>
----Little boy beneath the boulders----
<dd>
A short 2m climb through a boulder choke leads to break down chamber directly below grand prix. Qmc at station 8, p10, probably drops level with station 6 (lbbeneaththeboulders).
<dt>
----Little boy bolt climbs----
<dd>
From the grand prix, left from little boy beneath the boulders is a large hanging boulder. Traverse along massive choked boulder on left hand side of grand prix. Not derigged. Climbs up steep mud slope into rift that shortly forks (station 4). P15 qmc down from here, leads probably to lbbeneaththeboulders. Sketchy rift climb qmc from here, dispute about seeing a human sized passage beyond here.
</dl>
<details>
<summary>No authoritative list of where the expo paper records are!</summary>
<li class="todo"><!--2020-04-03 psargent-->NO expo paperwork at all prior to 2008 in Tackle Store - where is it ?
<li class="todo"><!--2020-04-03 psargent-->FIND where all the wallet binders are, and the logbooks.
< <li class="todo"><!--2020-04-03 psargent--> BUY A4 plastic boxes for filing cabinet for logbooks getting damp there.
<li class="todo">2017, 2018, 2019 wallet binders are in Philip S.'s house.
</details>
<h3>Generic things to check that they are all OK</h3>
<dl>
<dt><!-- psargent 2020-05-08 -->All these svx files have commented-out *include statements. Are they all OK? SHould some of these files be deleted ?
<dd><pre>
<details>
<summary><!-- psargent 2020-05-08 -->All these svx files have commented-out *include statements. Are they all OK? SHould some of these files be deleted ?</summary>
<li class="todo"><pre>
In the :loser: repository
1623-and-1626-with-terrain.svx: ;*include surface/terrain/tdm.svx
@ -447,11 +161,12 @@ surface/1623/allnr41.svx: ;*include BunttoP0
surface/1623/allsurface.svx: ;*include 258to264
surface/1623/allsurface.svx: ;*include butterfly_to_fish
</pre>
</dl>
</details>
<h3>List of jobs in :loser:/docs/Questions.txt</h3>
<dl>
<dt>Jan 2015, Dec 2013, Apr 2013. 2012
<dd>
<details>
<summary>Jan 2015, Dec 2013, Apr 2013. 2012</summary>
<li class="todo">
<pre>
Jan 2015
Arge dataset merge:
@ -528,65 +243,362 @@ where did 143/krone.svx go? Just superceded?
41 merged:
germanrt split out of e41 survey
</pre>
115: b9 duplicate survey - keep or remove?
<li class="todo">115: b9 duplicate survey - keep or remove?
CUCC surveys all moved into cucc subdir. Old SU conversions replaced
with newer ones. Akte surveys renamed. Stream split in surveys.
Juttahoehle: 'jutta.svx'. This is 1984 data from Franz Lindenmayr. Has
<li class="todo">Juttahoehle: 'jutta.svx'. This is 1984 data from Franz Lindenmayr. Has
been under '40' since 2000. Now moved to Juttahoehle dir. Is it really
a separate cave?
We don't have entrance locations for: E08, E16, E18, Nachbarschacht
<li class="todo">We don't have entrance locations for: E08, E16, E18, Nachbarschacht
(in 233 dir), gruenstein. Does data exist?
------------
-- 233. Robert Seebacher's kataster spreadsheet has 233 = Betthupferle, and the length and depth match the svx file betthupferle.svx. I have thus renamed betthupferle.svx to 233/233.svx and copied the ent coords out of RS's file. But Blaubeerschacht also claims to be no. 233. I have put blaubeerschacht in but not linked it, as we don't have an entrance fix.
<li class="todo"> 233. Robert Seebacher's kataster spreadsheet has 233 = Betthupferle, and the length and depth match the svx file betthupferle.svx. I have thus renamed betthupferle.svx to 233/233.svx and copied the ent coords out of RS's file. But Blaubeerschacht also claims to be no. 233. I have put blaubeerschacht in but not linked it, as we don't have an entrance fix.
-- Which points of Griesskogelschacht are entrances?
<li class="todo"> Which points of Griesskogelschacht are entrances?
-- File "neu.svx". What is the deal with this? Does the cave have a name or a number?
<li class="todo"> File "neu.svx". What is the deal with this? Does the cave have a name or a number?
Example data file for 'new survey'?
-- 41/entlink.svx -- what does this do?
<li class="todo"> 41/entlink.svx <li class="todo"> what does this do?
-- The 1987 extension in 87. This doesn't match anything in the ARGE data,
<li class="todo"> The 1987 extension in 87. This doesn't match anything in the ARGE data,
whereas the original 1980 survey data looks like the ARGE data rotated
somewhat. I have left this unlinked. Perhaps best to ask Robert Winkler.
-- 87 location fix and the 115 connection. The entrance fix for 87 in ARGE's file is over 50m different from the entrance fix from our surface survey. Bizarrely, CUCC's ent fix gives a smaller misclosure than ARGE's when you tie into 115.
<li class="todo"> 87 location fix and the 115 connection. The entrance fix for 87 in ARGE's file is over 50m different from the entrance fix from our surface survey. Bizarrely, CUCC's ent fix gives a smaller misclosure than ARGE's when you tie into 115.
-- 113. ARGE's data and CUCC's data cover different bits of the cave and don't really match very well.
<li class="todo"> 113. ARGE's data and CUCC's data cover different bits of the cave and don't really match very well.
-- 145. I have combined CUCC's data and ARGE's for the upper level resurvey. Any comments?
<li class="todo"> 145. I have combined CUCC's data and ARGE's for the upper level resurvey. Any comments?
-- 41-144 connection. Is the line
*equate 144.144verb.58 41.entlueft.9_10
<li class="todo"> 41-144 connection. Is the line <br>
*equate 144.144verb.58 41.entlueft.9_10<br>
correct? It appears in some of the ARGE index files and not others!
113 cucc replaced by ARGE
<li class="todo">113 cucc replaced by ARGE
<li class="todo">
2012:
why is e142 survey inside 41? 142 is separate cave. We have an
antrance location for it. Is it in fact used in any of the surveys?
<li class="todo">
152 (bananahoehle) is connected to 113 (sonnetrahlhoehle). but p152=Q3
on stogersteig. No GPS or fixed point in ents file. Why not?
<li class="todo">
136 cannot be processed on its own due to 136d not being connected.
<li class="todo">
Need to get better info on errors with/without surface and GPS and old
and new. And decide wht to do about caves that can't be processed
alone. Put fixes into all cave files? How do we do updates then?
</details>
<h3><!--2020-04-17 psargent-->:expoweb:/1623/264/cavedescription2016</h3>
<p>(All moved verbatim, original to-do file now empty.)
<details>
<summary>tightyorkshireman</summary>
<li class="todo">
person size phreatic tube, left passage emerges at pitch head, right passage becomes too tight.
<summary>rabbitwarrens</summary>
<li class="todo">
Sandy crabwalk turning into a tube parallel to main passage connecting to ein und zwanzig
<summary>noserock2</summary>
<li class="todo">
Pitch dropped round the corner from the pitch in noserock. Lots of
break-down and pitch ended in a choked chamber floor.
<summary>northhole</summary>
<li class="todo">
;Small grotty hole in the floor of eis koek aven, which connects through to the nearby large hole down to a circular ice floor.
<summary>northhole2</summary>
<li class="todo">
; continuing north from northhole, there is a series of freeclimbable avens going upward, the final survey station is at an awkward but not impassable squeeze. A handline would be very helpful in coming back down. There are also two connections to the frozen north, one is a tube at head height and the other is a small crawl at the start of the choss slope leading to the first aven climb.
<summary>vicecockLC1</summary>
<li class="todo">
;linking icecock aven to the ice pit in north hole.
<summary>icecock3</summary>
<li class="todo">
;small sandy floored tube connecting the icecock bypass to the northhole passage
<summary>vgosserwager2</summary>
<li class="todo">
linking the bottom of the pitch (name?) to the rift above gosser wager and the pitch down to it, continuing to a boulder choke.
<summary>gosserwager3</summary>
<li class="todo">
Rift passage heading South, with a 15m pitch at head. Clean walls, rubble floor. Leads to short down climb before more rift and another pitch series.
<summary>frozennorth</summary>
<li class="todo">
climb up between wall and block, aided by two bolts, to enter ice lake
chamber. Ahead is a large aven with snow slope entering. Just before
this is a small passage on the right. Climb up into this and follow
ice inlet until breaks out into large aven and trench area at station
12. To the south is/was unexplored, but later connected to rest of
cave. To left is small sanding tube to view into same trench system.
<summary>frozennorth4</summary>
<li class="todo">
left juction in frozennorth where there are sandy crawls, comes out on
a precarious ledge above a big hole. Traversing around this leads to a
medium sized sandy crawl sloping downwards to a huge chamber with a
pitch suspected to be the north end of lead 93B from the start of
expo2015 in turtlehead.
<summary>frozennorth3:</summary>
<li class="todo">
A rift passage that loops round and links 2 chambers, with possible leads at the end at station 5.
<summary>darkartsiv:</summary>
<li class="todo">
continuing A lead at south end of dark arts, went in then surveyed out but didn't make it all the way to connect up the surveys.
<summary>cathedralLC2:</summary>
<li class="todo">
Linking avalancheexperience to cathedralchasm without having to use the dodgy data in chamber90b survey
<summary>cathedralchasm:</summary>
<li class="todo">
really fucking huge chamber with many good leads. turns out it was already surveyed as chamber90b be Julian.
<summary>catherdralchasm2</summary>
<li class="todo">
Coming fdrom Cathedral Kazam a wet traverse across a pitch David
dropped a setter down. Passage continues to chamber with a loop coming
off to the left up and emerging at top of chamber en route. from
cahmber a rift goes off up right with main passgae continueing
straight. Also a small lead to left leads round to two small 5m pitchs
containg crystal formations. A traverse continues on with another
pitch. Taking the main route from the chamber a sandy passage leads
past three bat skeletons before becoming a crawl, eventually reaching
a junction. the larger passge to the left links back to the passge
near trident junction/ gear dump. This bypass is now the recommended
wat to reach cathedral kazam.
<summary>bipedal:</summary>
<li class="todo">
heading south out of amalgamation you arrive at a large long hole in the floor. Partial completion of traverse over hole, plus exploratin of two small side leads. Left over small rock bridge ends in blind pot. Right hand small passage soon becomes too tight.
<summary>bipedalpassage5</summary>
<li class="todo">
short pitch down to large aven chamber with vedose rift in floorway.
<summary>hiltigalactica</summary>
<li class="todo">
After dropping initial pitch (Deep Space 9) approx 25m in hilt-a-plenty.
After dropping initial pitch (Deep Space 9) approx 25m in hilt-a-plenty.
Long rocky chamber from bottom of pitch to next unexplored pitch.
Slope near end up left ends after short distance. Small side passage near
start on right continues to small sandy chamber with several leads.
From here archway leads onto bouldery ledge in side of very large chamber
to be explored.
</details>
<h3><!--2020-04-19 psargent-->/expofiles/surveyscans/2017/2017notes.txt</h3>
<p>(All moved verbatim, original to-do file now empty.)
<details>
<summary>258</summary>
<li class="todo">
<pre>
import other 258 files:
pawpaw
notthebeast
To draw up!!!
258/whatwouldyourmothersay.svx needs drawing up from notes in 2016#27 (we missed it out)
</pre>
</details>
<details>
<summary>264</summary>
<li class="todo">
<pre>264/doublescoop from notes in 2016#34
nothingtosee3: 264/wallet 2017#52 needs printing out and drawing up
dogendseries: 2017#42 notesplan
Need to find the snow symbol
How to make the jar file work again (and then update all copies in svn)
nothingtosee --> imported
sloppyseconds2 --> imported
naturecalls --> imported
created 264post2017b
created sloppysecondspart
Sync 2016#19 snowhole back to expo computer (as well as whole of 2017)
Rescan notes for 2017#50 (cropped)
queries:
2017#12. 264/nothingtosee ULSA distoX. Length calibration -0.05 ('tape too long'). Is that right?
2017#15 not_the_best elevation drawn, but not beastsideleads? Plans for bth
======================
To get the files here:
rsync -av expo@expo.survex.com:expofiles/surveyscans/2017/ /home/julian/data/expodata/expofiles/surveyscans/2017/
To copy a rendered survey up:
scp /home/julian/data/expodata/tunneldata/2017-09-28incomplete1.png expo@expo.survex.com:expofiles/surveys/
======================
</details>
<details>
<summary>tunnocks high level</summary>
<li class="todo">
not_the_beast 2017#15
rigormortis 2017#43
</pre>
<summary>tunnocks deep stuff</summary>
<li class="todo">
<pre>
mastercave 2017#16 drawnin
gryke of the earth 2017#17
loserlido 2017#44
snakecharmer 2017#06
slackerstidyup 2017#05 background
raisinhell 2017#04
therestherub 2017#02 drawn
snakecharmer2 2017#31
snakecharmer3 2017#32
hipsterreturn 2017#35
lowersnakebite 2017#40
beckoningsilence 2017#41 drawnin
bahama 2017#45
</pre>
<summary>cathedralchasm offshoots</summary>
<li class="todo">
<pre>
the_mendips 2017#18 !!!Missing folder!!! no drawing
mysterious_schlag 2017#19 is a pitch in cathedralchasm
pointless_dig 2017#20
naturecalls 2017#47 not tied in from bottom of Ash's pitch in cathedral chasm bit (have faked it)
</pre>
<summary>galactica area fuckups</summary>
<li class="todo">
<pre>
sloppyseconds1 2017#01
galactica 2017#03
sloppyseconds2 2017#07
sloppyseconds 2017#42 dogendseries
secondhand 2017#49
missing bit 2017#52
nothingtosee 2017#12
nothing2see ??? lost wallet #24 centreline typed
nothingtosee3 2017#52 recovered
hilti_nts_bones_pitch 2017#21 -linked in now
hilti_nts_near_bats 2017#22 -linked in now
hilti_nts_near_start 2017#23
nothingtosee 2017#39
</pre>
<summary>surface crap</summary>
<li class="todo">
<pre>
prospecting 2017#08
prospecting 2017#09
prospecting 2017#10
prospecting 2017#11
prospecting 2017#24 !!! not nothing2see as documented
watermelon 2017#28
kitten-helicopter 2017#33
prospecting 2017#34
</pre>
<summary>Fish Gesicht (2017-cucc-28)</summary>
<li class="todo">
<pre>
fishface 2017#38
fishface 2017#46
windytube 2017#37
icytube 2017#48
fgh 2017#50
blitzen 2017#53
</pre>
</dl>
<!-- ------------------- Do not touch anything below here either ------------------------>
<!--2020-03-26 Testing.. -->
<div id="demo">Demonstration text as initially read from disc</div>
<summary>GSH</summary>
<li class="todo">
<pre>
gsh entrance 2017#25
gsh 2017#26
coulda 2017#27
gsh 2017#29
riftpiece 2017#30
</pre>
<summary>Bad Forecast (2017-pw-01)</summary>
<li class="todo">
<pre>
gardeningshoots 2017#13
thirdentrance 2017#14
badforecast 2017#51
</pre>
</details>
<h3><!--2020-04-17 psargent-->:expoweb:/1623/264/trident_to_little_boy.txt</h3>
<p>(All moved verbatim, original to-do file now empty.)
<details>
<summary>
Cave: Balcony (Far Side to Deep Balcony)</summary>
<li class="todo">
Trident is a four way junction- take the left fork to an alcove on the left with an obscure mud floored crawl. This is followed for 10m, improving to walking height. Follow past two bat skeletons then right turn to another bat; continue ~20m. A mud floored junction, turn right to the head of a traverse then pitch after 10m. Straight on would have led you to a noteworthy drippy pitch (Kathedral Chasm).
</details<details></summary>Honeycomb</summary>
<li class="todo">
The traverse to pitch is the beginning of Honeycomb (50m of pitches). This swings to a window, following the rope to a ledge 10m above the floor. From here there's a narrow popcorn-lined climb to the head of a 7m pitch. At the bottom, climb the slope and follow obvious continuation (draught) to the head of 12m pitch. This pitch lands at the top of Hangman (p30), on account of the huge hanging boulder. (The near side of the boulder descends to the way on to the top of Mongol Rally, whereas the far side of the boulder is rigged to swing into a window half way down, Myopia. This is a passage heading north, traversing around a large pit, leading to another pitch which could be traversed around, ?a.)
</details<details></summary>Nature Calls</summary>
<li class="todo">
At the bottom, follow the traverse round to a mudslope. At the top of the mudslope there is an awkward crawl for 10m, soon improves to walking. Follow this passage for 30m. There's a p5, follow the rope to the head of the Mongol Rally (p200).
</details<details></summary>Mongol Rally and Little Boy</summary>
<li class="todo">
Descending this rope lands into a roomy boulder chamber. Walking down the slope between boulders (distinguished path in the mud), leads to a blind pit and big aven. A right turn takes you to stooping height passage, for 50m to the head of Little Boy pitch (20m). There is a significant draught here; follow this. The camp is currently at the base of the pitch (August 2018).
</details<details></summary>Water collection</summary>
<li class="todo">
There are three exits to the chamber. <br>
1. a short crawl <br>
2. a climb down on the far side. <br>
Both lead to the same place and draught.
<br><br>
Leave on the far side of the chamber, via a climb down and turn right, climbing down a boulder into pleasent walking passage, very straight and heading north. The floor is soft wet mud. After ~100m a stream trench enters on the right, followed round a corner into a drippy aven. Collect water here, scoop (mug) advisable.
<br>
(Currently unconnected from Grand Prix)
</details><details></summary>One direction</summary>
<li class="todo">
A little further on from the right turn towards the water cllection, is a muddy ledge on the left hand side (1m from ground). Low crawl continues for 100m in straight line, over three puddles. Stal, but largely unnoteworthy. Ends at the Tsection into clean washed tall rift with sounds of water. Downhill leads to promising a lead, in clean washed rock, sketchy c6, requires rope, heads into rifty stuff. Uphill, includes split (meander) to scoopy loopy junction.
</details<details></summary>Scoopy Loopy</summary>
<li class="todo">
Scoop it until you loop it. Junction has small a lead on right hand wall, to sound of wet rift. Obvious way on cuts left, walking passage heading upwards until low crawl into breakdown chamber. A climb on the right links into Grand Prix.
</details<details></summary>Nothing to do with you traverse---- (ntdwyt)
<li class="todo">
The passage towards the water collection is followed, beyond the turning for water. This leads to a pitch down (Indy Rally) or a traverse left. The traverse left goes ~10m, before muddy walking passage ~30m until it chokes.
</details<details></summary>Little boy beneath the boulders</summary>
<li class="todo">
A short 2m climb through a boulder choke leads to break down chamber directly below grand prix. Qmc at station 8, p10, probably drops level with station 6 (lbbeneaththeboulders).
</details<details></summary>Little boy bolt climbs</summary>
<li class="todo">
From the grand prix, left from little boy beneath the boulders is a large hanging boulder. Traverse along massive choked boulder on left hand side of grand prix. Not derigged. Climbs up steep mud slope into rift that shortly forks (station 4). P15 qmc down from here, leads probably to lbbeneaththeboulders. Sketchy rift climb qmc from here, dispute about seeing a human sized passage beyond here.
</details>
<hr>
See also <a href="todo.html">System Maintenance to-do list</a><br />
Back to <a href="manual.html">Data Maintenance manual</a>

124
handbook/computing/todo-styles.css
View File

@ -1,124 +0,0 @@
button {
color: #ffffff;
font: 18px Georgia, "Times New Roman", Times, serif;
letter-spacing: 1px;
text-shadow: 0 1px 1px #000000;
#display: block;
float:right;
margin: auto;
font-size: 1.2em;
line-height: 1.25em;
padding: 7px 25px;
cursor: pointer;
position: static;
background: #bf3700;
border: 1px solid #60AABF;
-moz-border-radius: 20px;
-webkit-border-radius: 20px;
-khtml-border-radius: 20px;
border-radius: 20px;
/*
-webkit-box-shadow: rgba(0, 0, 0, .25) 0 1px 1px;
-moz-box-shadow: rgba(0, 0, 0, .25) 0 1px 1px;
-o-box-shadow: rgba(0, 0, 0, .25) 0 1px 1px;
box-shadow: rgba(0, 0, 0, .25) 0 1px 1px;
*/
background: #39b2e5;
background: -webkit-gradient(linear, left top, left bottom, from(#39b2e5), to(#6083BF));
background: -moz-linear-gradient(top, #39b2e5, #6083BF);
background: -o-linear-gradient(top, #39b2e5, #6083BF);
background: linear-gradient(top, #39b2e5, #6083BF);
}
button:hover,
button:focus {
cursor: pointer;
border-color: blue;
-webkit-box-shadow: aqua 0 0 8px;
-moz-box-shadow: aqua 0 0 8px;
-o-box-shadow: aqua 0 0 8px;
box-shadow: aqua 0 0 8px;
}
button:active {
background: #39b2e5;
background: -webkit-gradient(linear, left bottom, left top, from(#39b2e5), to(#6083BF));
background: -moz-linear-gradient(bottom, #39b2e5, #6083BF);
background: -o-linear-gradient(bottom, #39b2e5, #6083BF);
background: linear-gradient(bottom, #39b2e5, #6083BF);
}
h2, h3, h4 {
color: #39b2e5;
margin-bottom: 0;
line-height: 0.6;
}
dd {
font: 18px Calibri, sanserif;
font-weight: normal;
color: 6083BF;
display: none;
#list-style-type: disc;
line-height: 1.3;
margin-left: 1.0em;
}
li {
font: 18px Calibri, sanserif;
font-weight: normal;
color: 6083BF;
list-style-type: None;
line-height: 1.3;
margin-left: 1.0em;
}
li:before, dd:before {
content: "» ";
font-weight: bold;
color: red;
}
/* Default State */
summary, dt {
font: 20px Calibri, sanserif;
font-weight: bold;
color: 6083BF;
margin-top: 0.2em;
margin-left: 1.0em;
margin-right: 5em;
#list-style-type: none;
line-height: 1.4;
font-style: italic;
}
/* Toggled State */
input[type=checkbox] ~ dl dd {
display: block;
}
input[type=checkbox]:checked ~ dl dd {
display: none;
}
@media only print, print)
{
b {
font-size: 10pt;
}
p {
font-size: 10pt;
}
dt{
font: 1.0em Calibri, sanserif;
font-weight: bold;
}
dd {
font: 0.8em Calibri, sanserif;
}
}

194
handbook/computing/todo.html
View File

@ -3,7 +3,6 @@
<head>
<title>Expo Systems - To-Do List</title>
<meta charset="utf-8">
<meta name="keywords" content="NOEDIT">
</head>
<body>
@ -14,11 +13,8 @@ body {
/* Use grey for system/programming/nerd pages as a visual reminder */
</style>
<!-- only use some of these styles. Pending tidying after the other todo list is changed to use <details>
overwrite the ones we don't want here-->
<link rel="stylesheet" type="text/css" href="todo-styles.css" />
<style>
li {
li.todo {
font: 18px Calibri, sanserif;
font-weight: normal;
color: 6083BF;
@ -26,17 +22,13 @@ li {
line-height: 1.0;
margin-left: 1.0em;
}
li:before {
li.todo:before {
content: "» ";
font-weight: normal;
color: 6083BF;
}
</style>
<h1>Expo Systems To-Do List</h1>
<button onclick="window.location.href = 'todo.html_edit';">Edit this to-do list</button>
<!-- ------------------- Don't touch anything above this line --------------------------->
<h2>How this works</h2>
@ -44,255 +36,233 @@ li:before {
<p>Printing this page uses a much smaller font. Complain to <a href="mailto:expo-tech@lists.wookware.org">the nerd list</a> if you don't like this behaviour.
<p>Edit this page by clicking on the big blue button. It uses the same "Edit this page" function that you may have used before. Just be careful not to touch the code at the top and bottom of the page. (The "Edit this page" prompt is still there too.)
<p>Edit this page by using the same "Edit this page" function that you may have used before.
<p>We were working on a more capable and easier-to-use system which would mimic
how <a href="https://github.com/CaveSurveying/CUCCexposurveyissues/issues">GitHub Issues</a> do this sort of thing,
but now we are just going to use standard HTML5 tags.
<p>To see the "data maintenance" and "survey data-entry" to-do lists, go to <a href="todo-data.html">the other TO-DO list</a>
<h3>Module to-do texts</h3>
<p>These are extracted directly from the <var>todo = &apos;&apos;&apos;Thing to do &apos;&apos;&apos;</var> string at the top of each file of troggle code:</p>
<hr>
<a href="/todo/anything"><div>
<embed type='text/html' height='200px' width='800px' src="/todo/anything"><br>
Click here if no todo list appears here (because 'frames' have been disabled).</div></a>
<embed type='text/html' height='100px' width='800px' src="/todo/anything"><br>
Click here if no todo list appears here (because 'frames' have been disabled).</div></a> This list is generated directly from the troggle python code files.
<hr>
<h3>Other coding To Do things</h3>
<p>See also these long-running issues which have their own 'to do' implications:
<ol>
<li><a href="/handbook/troggle/trogdesign.html">What Troggle Does Badly - Design Decisions</a>
<li><a href="/handbook/troggle/menudesign.html">New Menu System</a>
<li><a href="/handbook/troggle/trog2030.html">Troggle in 2025-2030</a>
<li class="todo"><a href="/handbook/troggle/trogdesign.html">What Troggle Does Badly - Design Decisions</a>
<li class="todo"><a href="/handbook/troggle/menudesign.html">New Menu System</a>
<li class="todo"><a href="/handbook/troggle/trog2030.html">Troggle in 2025-2030</a>
</ol>
<h3>Process Documentation</h3>
<details><summary><!--2020-03-26 psargent-->Wallets and new-cave</summary>
<li><!--2020-03-26 psargent-->Explain how to link a new cave into the other caves in
<li class="todo"><!--2020-03-26 psargent-->Explain how to link a new cave into the other caves in
troggle filesystem
<li><!--2020-03-26 psargent-->Explain how to add photos with the correct URL format to sub-HTML files attached to New Caves
<li>explain how to put stuff in the wallet folder and how to look at expofiles/photos/xml/
<li class="todo"><!--2020-03-26 psargent-->Explain how to add photos with the correct URL format to sub-HTML files attached to New Caves
<li class="todo">explain how to put stuff in the wallet folder and how to look at expofiles/photos/xml/
</details>
<details><summary><!--2021-10-31 psargent-->Scans and Drawings Uploads</summary>
<li>Add to user data manual how to upload to expofiles - in the "survey manual"
<li>Add in description of *where* to put the drawings files
<li class="todo">Add to user data manual how to upload to expofiles - in the "survey manual"
<li class="todo">Add in description of *where* to put the drawings files
</details>
<details><summary><!--2020-04-13 psargent-->svx check</summary>
<li>explain command line to run on newly typed survex file to check for format errors '$cavern xxxx.svx'
<li>explain when to use svxtrace.py <a href="troggle/scriptscurrent.html">current scripts</a>
<li>Making an svx - explain how to make link to *ref to wallet folder
<li class="todo">explain command line to run on newly typed survex file to check for format errors '$cavern xxxx.svx'
<li class="todo">explain when to use svxtrace.py <a href="troggle/scriptscurrent.html">current scripts</a>
<li class="todo">Making an svx - explain how to make link to *ref to wallet folder
</details>
<h3>Wallets re-programming</h3>
<details><summary><!--2021-05-21 psargent-->Things wallets.py might do in future </summary>
<li>- integrate into troggle, remove as a distinct script
<li>- relates to conversion of the XRF shell script into python/troggle too
<li>- checking the cave number specified matches the folder for the .svx file,
<li>- checking that the *ref: filed in the survex file is the same as the wallet nameS
<li>- detecting whether there is a description or a list of QMs in the survex file,
<li>- accepting a list of .svx files and not just one (a very common thing),
<li>- checking the name of the cave against the cave number,
<li>- checking whether the website page even exists for this cave,
<li>- being more intelligent about .topo files and thus the lack of scan files,
<li>- checking the date is in the recent past etc.
<li class="todo">- integrate into troggle, remove as a distinct script
<li class="todo">- relates to conversion of the XRF shell script into python/troggle too
<li class="todo">- checking the cave number specified matches the folder for the .svx file,
<li class="todo">- checking that the *ref: filed in the survex file is the same as the wallet nameS
<li class="todo">- detecting whether there is a description or a list of QMs in the survex file,
<li class="todo">- accepting a list of .svx files and not just one (a very common thing),
<li class="todo">- checking the name of the cave against the cave number,
<li class="todo">- checking whether the website page even exists for this cave,
<li class="todo">- being more intelligent about .topo files and thus the lack of scan files,
<li class="todo">- checking the date is in the recent past etc.
</details>
<h3>Surveys data entry documentation</h3>
<details><summary>Write code to automatically extract ref info about wallets from tunnel xml files</summary>
<li><!--2020-04-03 psargent-->This will replace :drawings:chk-xml.txt as used by :drawings:check-xml.sh
<li><!--2020-04-03 psargent-->Do similar for Therion files when people start using #REF comments
<li class="todo"><!--2020-04-03 psargent-->This will replace :drawings:chk-xml.txt as used by :drawings:check-xml.sh
<li class="todo"><!--2020-04-03 psargent-->Do similar for Therion files when people start using #REF comments
</details>
<details><summary><!--2020-03-26 psargent-->2019 surveyscans</summary>
<li><!--2020-03-26 psargent-->edit all the content.json files
<li><!--2020-03-26 psargent-->try to autocomplete the content.json by parsing .svx files
<li><!--2020-03-26 psargent-->Put personal names into canonical form
<li class="todo"><!--2020-03-26 psargent-->edit all the content.json files
<li class="todo"><!--2020-03-26 psargent-->try to autocomplete the content.json by parsing .svx files
<li class="todo"><!--2020-03-26 psargent-->Put personal names into canonical form
</details>
<details><summary>2014 contents.json</summary>
<li><!--2020-04-03 psargent-->parse all the svx files to extract people, dates & svx references
<li class="todo"><!--2020-04-03 psargent-->parse all the svx files to extract people, dates & svx references
</details>
<h3>Handbook</h3>
<details><summary><!--2020-04-11 psargent-->Navigation - Context, Situational Awareness</summary>
<li><!--2020-04-11 psargent-->No overall view of what there is: need a user-friendly diagrammatic overview <a href="https://en.wikipedia.org/wiki/Site_map">sitemap</a>. There are 4,869 files in :expoweb:
<li><!--2020-04-11 psargent-->Not fixed by menus - breadcrumbs needed?
<li><!--2020-04-11 psargent-->Diagrams of major sections: survey handbook, rigging handbook, computing handbook, Areas, cave data..
<li><!--2020-04-11 psargent-->Chase Airoa to help fix <a href="../troggle/menudesign.html">the menus for phones</a>
<li><!--2020-04-11 psargent-->Look at <a href="https://www.gov.uk/guidance/government-design-principles">gov.uk guidelines</a> for inspiration</details>
<li class="todo"><!--2020-04-11 psargent-->No overall view of what there is: need a user-friendly diagrammatic overview <a href="https://en.wikipedia.org/wiki/Site_map">sitemap</a>. There are 4,869 files in :expoweb:
<li class="todo"><!--2020-04-11 psargent-->Not fixed by menus - breadcrumbs needed?
<li class="todo"><!--2020-04-11 psargent-->Diagrams of major sections: survey handbook, rigging handbook, computing handbook, Areas, cave data..
<li class="todo"><!--2020-04-11 psargent-->Chase Airoa to help fix <a href="../troggle/menudesign.html">the menus for phones</a>
<li class="todo"><!--2020-04-11 psargent-->Look at <a href="https://www.gov.uk/guidance/government-design-principles">gov.uk guidelines</a> for inspiration</details>
<h3>Areas and prospecting guides</h3>
<details><summary>Areas (these are the sub-areas)</summary>
<li><!--2020-05-01 psargent-->Downgrade the "areas" aspect of the documentation as we don't use these now
<li class="todo"><!--2020-05-01 psargent-->Downgrade the "areas" aspect of the documentation as we don't use these now
</details>
<h3>Photos</h3>
<details><summary><!--2020-04-03 psargent-->Fix the BINS package (Wookey is looking for replacement)</summary>
<li><!--2020-04-03 psargent-->set up git on the BINS software? Fix base url sautret.org
<li><!--2020-04-03 psargent-->set up a cron / Makefile job to run BINS
<li><!--2020-04-03 psargent-->why is 'updatephotos' script in expofiles?
<li>Document the ~expo/webphotos/ directory and how it works
<li>Why does expofiles/photos/xml/ get created containing all the generated xml files? Fix this.
<li class="todo"><!--2020-04-03 psargent-->set up git on the BINS software? Fix base url sautret.org
<li class="todo"><!--2020-04-03 psargent-->set up a cron / Makefile job to run BINS
<li class="todo"><!--2020-04-03 psargent-->why is 'updatephotos' script in expofiles?
<li class="todo">Document the ~expo/webphotos/ directory and how it works
<li class="todo">Why does expofiles/photos/xml/ get created containing all the generated xml files? Fix this.
</details>
<details><summary>galley thumbs etc.</summary>
<li>:expoweb:/galley/0.htm thumbnails not loading
<li class="todo">:expoweb:/galley/0.htm thumbnails not loading
</details>
<h3>Laptop config.</h3>
<details><summary><!-- 2020-04-11 psargent --> imagemagick convert</summary>
<li><!--2020-04-03 psargent-->Not working for PDFs on current version of xubuntu ! Fix & document. Also not working on WSL ubuntu. Needed to work with logbook images easily & to extract PDFs, JPEGs. Need to edit /etc/ImageMagick-6/policy.xml
<li class="todo"><!--2020-04-03 psargent-->Not working for PDFs on current version of xubuntu ! Fix & document. Also not working on WSL ubuntu. Needed to work with logbook images easily & to extract PDFs, JPEGs. Need to edit /etc/ImageMagick-6/policy.xml
<a href="https://cromwell-intl.com/open-source/pdf-not-authorized.html">cromwell-intl.com/open-source/pdf-not-authorized.html</a>
</details>
<h3>System Documentation</h3>
<details><summary><!--2020-04-11 psargent-->Document how we generate the SMK overall lengths and stats</summary>
<li><!--2020-04-20 psargent-->scripts and manual actions in cavern
<li>smklengths.sh script
<li>smklengsths.odt
<li class="todo"><!--2020-04-20 psargent-->scripts and manual actions in cavern
<li class="todo">smklengths.sh script
<li class="todo">smklengsths.odt
</details>
<details><summary><!--2020-04-20 psargent-->:loser:/docs/ files</summary>
<li>Questions.txt
<li>SMKlog.txt
<li class="todo">Questions.txt
<li class="todo">SMKlog.txt
</details>
<details><summary><!--2020-03-26 psargent-->Troggle architecture</summary>
<li><!--2020-04-10 psargent-->Regenerate the diagram of the tables in the database & document
<li><!--2020-04-10 psargent-->Describe the parsing/import procedures so non-nerds can do it
<li class="todo"><!--2020-04-10 psargent-->Regenerate the diagram of the tables in the database & document
<li class="todo"><!--2020-04-10 psargent-->Describe the parsing/import procedures so non-nerds can do it
</details>
<details><summary><!--2020-03-26 psargent-->Surveyscans</summary>
<li><!--2020-03-26 psargent-->explain where the image files are referenced from: svx, tunnel/therion, and
<li>Be exhaustive in checking all the broken links between svx & wallets
<li class="todo"><!--2020-03-26 psargent-->explain where the image files are referenced from: svx, tunnel/therion, and
<li class="todo">Be exhaustive in checking all the broken links between svx & wallets
</details>
<details><summary>Makefile</summary>
<li>Get it working ! How many of <a href="../troggle/scriptsother.html">other scripts</a> should be in it ? Should we do data imports to schedule too ?
<li class="todo">Get it working ! How many of <a href="../troggle/scriptsother.html">other scripts</a> should be in it ? Should we do data imports to schedule too ?
</details>
<h3>Troggle</h3>
<details><summary><!--2022-06-23 psargent--> Testing git status</summary>
<li>add settings.SURVEX_DATA when loser is gitified. In test_imports.py
<li class="todo">add settings.SURVEX_DATA when loser is gitified. In test_imports.py
</details>
<details><summary><!--2022-02-15 psargent--> Expo log parsing</summary>
<li>Parsing broken on several old expo logs, excluded in the source code
<li class="todo">Parsing broken on several old expo logs, excluded in the source code
</details>
<details><summary><!--2021-11-06 psargent--> CaveView fixing</summary>
<li>re-enable CaveView
<li class="todo">re-enable CaveView
</details>
<details><summary><!--2021-11-04 psargent--> non-server, non-Apache links to Cave HTML i/t/l pages ALL BROKEN</summary>
<li>http://expo.survex.com/1623/others/l/113day.htm works but, and
<li>http://localhost:8000/1623/others/l/113day.htm works but
<li>http://localhost:8000/cave/others/l/purple.htm is a 404 as troggle urls.py doesn't do it at all
<li>Ah it is because of the 'cave' page being at /cave/ instead of sent to /1623/ which is the problem..
<li class="todo">http://expo.survex.com/1623/others/l/113day.htm works but, and
<li class="todo">http://localhost:8000/1623/others/l/113day.htm works but
<li class="todo">http://localhost:8000/cave/others/l/purple.htm is a 404 as troggle urls.py doesn't do it at all
<li class="todo">Ah it is because of the 'cave' page being at /cave/ instead of sent to /1623/ which is the problem..
</details>
<details><summary><!--2020-07-27 psargent--> QM links in cave descriptions ALL BROKEN</summary>
<li><!--2020-07-24 psargent-->There are HREF links to individual QMs in the cave description in e.g. 204
<li class="todo"><!--2020-07-24 psargent-->There are HREF links to individual QMs in the cave description in e.g. 204
<a href="1623/204/swings.html">Swings and Roundabouts</a> such as "At the bottom there is a climb down over boulders <a href="1623/204/qm.html#C2001-204-45">[C2001-204-45 C]</a>." where the troggle URL fails completely.
</details>
<details><summary><!-- 2020-04-11 psargent -->Troggle parser/viewer </summary>
<li>Explain how expopages (formerly flatpages) work. refer to computing/hbmanual1.html
<li class="todo">Explain how expopages (formerly flatpages) work. refer to computing/hbmanual1.html
</details>
<details><summary><!--2020-07-24 psargent--> Completely new design of QM management needed</summary>
<li><!--2020-07-24 psargent-->see <a href="../troggle/scriptsqms.html">QM status and redesign needed document</a>
<li class="todo"><!--2020-07-24 psargent-->see <a href="../troggle/scriptsqms.html">QM status and redesign needed document</a>
</details>
<h3>Troggle Refactoring</h3>
<details><summary><!--2022-02-15 psargent-->MIME types and filename extensions</summary>
<li>We should use standard <a href="https://docs.python.org/3/library/mimetypes.html">https://docs.python.org/3/library/mimetypes.html</a>
<li class="todo">We should use standard <a href="https://docs.python.org/3/library/mimetypes.html">https://docs.python.org/3/library/mimetypes.html</a>
to convert between mimetypes and filenames, not our own hacks
<li>We should not be relying on filenames to accurately describe the format of the files. This is not robus and may also be a bit insecure.
<li class="todo">We should not be relying on filenames to accurately describe the format of the files. This is not robus and may also be a bit insecure.
We should use <a href="https://github.com/ahupp/python-magic">python-magic</a> or some other wrapper around Linux libmagic1 C library.
But note that there are TWO packages called python-magic, see https://stackoverflow.com/questions/436220/how-to-determine-the-encoding-of-text/16203777#16203777
</details>
<details><summary><!--2020-07-24 psargent-->Make parsers use generators to yield one line at a time</summary>
<li><!--2020-07-24 psargent-->Both recursive load and linear load parsers/survex could do this.
<li><!--2020-07-24 psargent-->In the logbooks parsing and cache loading.
<li class="todo"><!--2020-07-24 psargent-->Both recursive load and linear load parsers/survex could do this.
<li class="todo"><!--2020-07-24 psargent-->In the logbooks parsing and cache loading.
</details>
<details><summary><!--2020-07-24 psargent-->Enhance some exceptions with dataIssue [NOTIFICATION pattern], not just in parsers</summary>
<li><!--2020-07-24 psargent-->https://martinfowler.com/articles/replaceThrowWithNotification.html
<li class="todo"><!--2020-07-24 psargent-->https://martinfowler.com/articles/replaceThrowWithNotification.html
</details>
<details><summary><!--2020-07-24 psargent-->Python documentation: Django's use of modern unobvious idioms</summary>
<li><!--2020-07-24 psargent-->[DECORATOR] pattern used for login-required pages
<li><!--2020-07-24 psargent-->Get all trogglistas to read https://ebookscart.com/effective-python-by-brett-slatkin-pdf-download/ - downloded to /expofiles/
<li><!--2020-07-24 psargent-->Get all trogglistas to read https://martinfowler.com/tags/refactoring.html
<li class="todo"><!--2020-07-24 psargent-->[DECORATOR] pattern used for login-required pages
<li class="todo"><!--2020-07-24 psargent-->Get all trogglistas to read https://ebookscart.com/effective-python-by-brett-slatkin-pdf-download/ - downloded to /expofiles/
<li class="todo"><!--2020-07-24 psargent-->Get all trogglistas to read https://martinfowler.com/tags/refactoring.html
</details>
<details><summary><!--2020-07-24 psargent-->expopages is used to deliver CSS and JS for django admin pages,</summary>
</details>
<details><summary><!--2022-02-19 psargent-->gardening our main model files for unused things</summary>
<li>get rid of 'expeditionday' as a concept everywhere ?
<li class="todo">get rid of 'expeditionday' as a concept everywhere ?
</details>
<details><summary><!--2022-02-19 psargent-->Make QM a first-class 'thing' and manage them explicitly in troggle</summary>
<li>after fixing the display of QMs from the existing hodge-podge
<li class="todo">after fixing the display of QMs from the existing hodge-podge
</details>
<h3>Expo Server</h3>
<details><summary><!--2020-07-24 psargent--> document cgit installation and config</summary>
<li><!--2020-07-24 psargent-->as per Wookey on Debian 10
<li class="todo"><!--2020-07-24 psargent-->as per Wookey on Debian 10
</details>
<details><summary>MySQL configuration </summary>
<li><!--2022-02-18 psargent-->robots.txt completely missing from /home/expo/static or troggle:/media
<li class="todo"><!--2022-02-18 psargent-->robots.txt completely missing from /home/expo/static or troggle:/media
<li><!--2020-05-14 psargent-->Document "anacron" / cron system on server
<li class="todo"><!--2020-05-14 psargent-->Document "anacron" / cron system on server
</details>
<h3>
<font color="fuchsia">This to-do-list gadget itself</font>
</h3>
<details><summary>Status</summary>
<li>This one now uses just HTML5 with no JS. But the other todo page still uses JS
</details>
<details><summary><!--2020-03-26 psargent-->Eventual aim</summary>
<li><!--2020-03-26 psargent-->to replace GitHub <a href="https://github.com/CaveSurveying/CUCCexposurveyissues/issues">
CUCCexposurveyissues</a> for non-tunnel, non-GIS issues.
<li><!--2020-03-26 psargent-->if using tinymcs, use the INLINE mode.
<li><!--2020-03-26 psargent-->Implement comments on an issue, mimicking GitHub issues wiki
<li><!--2020-03-26 psargent-->Use javascript to skip over the _edit page and submit changes
direct to server when updating. Needs direct POST and include the javascript in the posted content.
<li><!--2020-03-26 psargent-->checkboxes so that items can be ticked (which also does strike-through)
<li><!--2020-04-03 psargent-->promotion/demotion options?
<li><!--2020-03-26 psargent-->bin icon to delete an item? Better to have an archive process.
</details>
<!-- ------------------- Do not touch anything below here either ------------------------>
<!--2020-03-26--> Testing area..
<div id="demo">Demonstation text as initially read from disc</div>
<h3>The To Do pages</h3>
<p>We were working on a more capable and easier-to-use to-do system which would mimic
how <a href="https://github.com/CaveSurveying/CUCCexposurveyissues/issues">GitHub Issues</a> do this sort of thing,
but now we are just going to use standard HTML5 tags.
<hr>
See also <a href="todo-data.html">Data maintenance to-do list</a><br />

71
handbook/computing/todo.js
View File

@ -1,71 +0,0 @@
document.getElementById("demo").innerHTML = "<span style='color: lime'>Script working CONFIRMED</span>";
// TO DO - make the <dt> italic when any of the <dd> following it are hidden.
// Set up the click handlers:
var itemlist = document.getElementsByTagName('dd');
for (i = 0; i < itemlist.length; i++) {
itemlist[i].onclick = hideable;
}
var itemlist = document.getElementsByTagName('dt');
for (i = 0; i < itemlist.length; i++) {
itemlist[i].onclick = showable;
}
var itemlist = document.getElementsByTagName('h2');
for (i = 0; i < itemlist.length; i++) {
itemlist[i].onclick = h2toggle;
}
function showable () {
// When clicking on a <dt> item, show or not all the following <dd> elements
if (this.style.fontStyle != "italic") {
this.style.fontStyle = "italic";
} else {
this.style.fontStyle = "normal";
}
var ddO = this.nextElementSibling;
while((ddO !== null) && (ddO.nodeName.toLowerCase() == 'dd')){
if (this.style.fontStyle != "normal") {
ddO.style.display = 'none';
} else {
ddO.style.display = 'block';
}
ddO = ddO.nextElementSibling;
}
}
function hideable () {
// When clicking on a <dd> item, show or not itself
var x = this;
if (x.style.display != "block") {
x.style.display = "block";
} else {
x.style.display = "none";
}
}
function h2toggle () {
// When clicking on a <h2> item, toggle the display of absolutely everything
var itemlist = document.getElementsByTagName('dd');
for (i = 0; i < itemlist.length; i++) {
x = itemlist[i]
if (x.style.display != "block") {
x.style.display = "block";
} else {
x.style.display = "none";
}
}
var dtlist = document.getElementsByTagName('dt');
for (i = 0; i < dtlist.length; i++) {
x = dtlist[i]
if (x.style.fontStyle != "normal") {
x.style.fontStyle = "normal";
} else {
x.style.fontStyle = "italic";
}
}
}