Aaron Curtis : 2007

494.6 m surveyed this year.

Other years:  | 2006 | 2007 | 2008

Wallet status | 2006 | 2007 | 2008

Table of all trips and surveys aligned by date

July 15, 2007 204 - 204e Crowning Glory exploration 204
July 16, 2007 Top Camp - On obtaining alcohol at top camp - password protect Top Camp
July 19, 2007 Surface Prospecting - Surface messing Surface Prospecting
Aug. 3, 2007 204 - John Billing's account of Razor Dance derigging trip 204
Aug. 4, 2007 'Lead 03-75A' UNKNOWN hollow 35.3 m
Aug. 5, 2007 Chocolate Salty Balls UNKNOWN
-- CSB Thermistor & Treeumphant UNKNOWN
Aug. 7, 2007 Anemometer related quick useless trip UNKNOWN
Aug. 8, 2007 Tunnockschacht UNKNOWN
Aug. 11, 2007 Gaffered -> The Wares + Derig UNKNOWN whereoware 214.1 m
Aug. 12, 2007 Gaffered derig + Thermistors UNKNOWN stonemonkey 129.7 m
-- Tunnockschacht -> Stone Monkey UNKNOWN
Aug. 13, 2007 South Tunnocks (Pantin Sales Pitch) UNKNOWN flyinghigh2 21.7 m
-- pantinsales 93.8 m
Aug. 14, 2007 Final CSB thermistor trip UNKNOWN
Aug. 15, 2007 Packing Steinbruckenhoehle Bivvy UNKNOWN

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.)