Brian Derby : 1984

321.8 m surveyed this year.

Other years:  | 1984 | 1985

Wallet status | 1984 | 1985

Table of all trips and surveys aligned by date

DateTripsSurveys
July 22, 1984 travel - Team advance party - Orange Fiesta travel
July 23, 1984 144 - Day 1 142/41 -> 144 144
July 24, 1984 142 - 142/41 142
July 25, 1984 Wolfhöhle - The Rescue (or the day Wadders almost had to go caving) Wolfhöhle
July 30, 1984 142 142
Aug. 1, 1984 147 - 1st August Prospecting Steinschlagschacht to Wolfhöhle 147
-- Wolfhöhle Wolfhöhle
Aug. 4, 1984 Wolfhöhle - Surveying Wolfhöhle part4 321.8 m
Aug. 8, 1984 143 - Derigging 143 143

Horrible bug here but only when there is more than one survex block per day, or is there ?!

WHat we thought was the bug: e.g. see Wookey 1999 where there are 3 eiscream survex blocks on 5th August. it duplicates the entry but gets it wrong. The length from the first block is displayed twice but there should be 3 rows: eiscream, eiscream2, eiscream3.

The interaction of django database query idioms with django HTML templating language is a bit impenetrable here. I blame Aaron Curtis who was too fond of being clever with the Django templating system instead or writing it in python anyone could understand.
- The template is in troggle/templates/personexpedition.html
- The code is in function personexpedition() which calls get_person_chronology() in troggle/core/views/logbooks.py
- the connection between the two is made in the URL resolver in troggle/urls.py

To be fixed!

What we now know

The eiscream.svx file does indeed record 3 blocks: eiscream, eiscream2 & eiscream3. But (more) careful inspection shows that eiscream2 and eiscream3 are in the year 2000, not in 1999. So they absolutely should not be shown here. So maybe everything is correct after all. (Well, apart from the duplication.)