CUCC Expedition Handbook

Troggle - Fixing things that break

The guide to the parser-model-view architecture is in the architecture document.

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.

It concentrates on showing how to find and fix import errors so that the troggle-generated webpages are complete and not full of gaps.

Intended audience: 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.

Here we will explain the useful diagnostic detailed data pages for finding mis-matched files:
statistics - survey legs and distances for each expo
all data one cave - all the survex data for one cave and who was on each trip
per-person caving - list of logbook trips and surveys for one person
people - who caved when and how much did they survey
logbook entry - who, where and what
survey_scans - all wallets of scanned surveys and corresponding survex files
per-wallet links - links to scan files and survex files from one wallet
tunneldata - all the tunnel drawings and the wallets and scanned images they derive from

/admin/core/dataissue/ - where the data import errors and warnings are recorded

Configuration aids when setting up on a new machine (move to main manual):
pathsreport - debugging aid
How to set up troggle on a new machine.
Copies of the older material where that is illuminating.
...needs more work...