expo/expoweb
1
0
Fork 0
mirror of https://expo.survex.com/repositories/expoweb/.git/ synced 2026-02-24 13:15:19 +00:00
Code Issues Packages Projects Releases Wiki Activity

Tidying and extending troggle documentation

Browse Source
This commit is contained in:
Philip Sargent
2020-07-10 02:51:53 +01:00
parent 63bc4103a7
commit d495e0f0d9
3 changed files with 36 additions and 24 deletions
Download Patch File Download Diff File Expand all files Collapse all files

34
handbook/troggle/trogdocm.html
View File

@@ -11,19 +11,31 @@
<h1>Troggle - Fixing things that break</h1>
<p>The guide to the parser-model-view architecture is in the architecture document.
<p><em>This page will describe the usual things that go wrong: the parsers that break when
faced with user-generated data and how to fix them. Common error messages. How to set up troggle on a new machine. Copies of the older material where that is illuminating.</em>
faced with user-generated data and how to fix them. Common error messages. </em>
<p>It concentrates on showing how to find and fix import errors so that the troggle-generated webpages are complete and not full of gaps.
<p>Intended audience: Ideally someone who is not a python programmer will be able to use this page to help them fix import errors.
<p>Also here we will explain the useful diagnostic pages such as <br>
<a href="http://expo.survex.com/experimental">experimental</a><br>
<a href="http://expo.survex.com/pathsreport">pathsreport</a><br>
<a href="http://expo.survex.com/survey_scans">survey_scans</a><br>
<a href="http://expo.survex.com//admin/core/dataissue/l">/admin/core/dataissue/</a><br>
<a href="http://expo.survex.com/tunneldata">tunneldata</a><br>
<a href="http://expo.survex.com/statistics">statistics</a><br>
<a href="http://expo.survex.com/people">people</a><br>
<p><b>Intended audience:</b> Ideally someone who is not a python programmer will be able to use this page to help them
fix import errors by re-editing the input files: survex, tunnel, or logbook.
<p>Here we will explain the useful diagnostic detailed data pages for finding mis-matched files:<br>
<img border="1" class="onright" width="150px" src='tricky-troggle.jpg' alt='git logo'/></a>
<var>These do not work until the server is updated in July 2020 to run the python3 version of troggle</var><br>
<a href="http://expo.survex.com/statistics">statistics</a> - survey legs and distances for each expo<br>
<a href="/survexfile/161">all data one cave</a> - all the survex data for one cave and who was on each trip<br>
<a href="/personexpedition/MartinGreen/2002">per-person caving</a> - list of logbook trips and surveys for one person<br>
<a href="/people">people</a> - who caved when and how much did they survey<br>
<a href="/logbookentry/2018-07-19/balkon-to-honeycomb-hangmans">logbook entry</a> - who, where and what<br>
<a href="/survey_scans">survey_scans</a> - all wallets of scanned surveys and corresponding survex files<br>
<a href="/survey_scans/2014%252347/">per-wallet links</a> - links to scan files and survex files from one wallet<br>
<a href="/tunneldata">tunneldata</a> - all the tunnel drawings and the wallets and scanned images they derive from<br>
<br>
<var>These do not work until the server is updated in July 2020 to run the python3 version of troggle</var><br>
<a href="/admin/core/dataissue/l">/admin/core/dataissue/</a> - where the data import errors and warnings are recorded<br>
<br>
Configuration aids when setting up on a new machine (move to main manual):<br>
<a href="/pathsreport">pathsreport</a> - debugging aid<br>
<em>How to set up troggle on a new machine. <br>
Copies of the older material where that is illuminating.</em>
<hr />
Go on to: <a href="trogarch.html">Troggle architecture</a><br />
Go on to: <a href="trognotes.html">Troggle notes to be restructured</a><br />
Return to: <a href="trogintro.html">Troggle intro</a><br />