Matt Watson : 2013

164.9 m surveyed this year.

Other years:  | 2013 | 2014 | 2015

Wallet status | 2013 | 2014 | 2015

Table of all trips and surveys aligned by date

July 27, 2013 Alex and Matt driving to Austria UNKNOWN
Aug. 1, 2013 justforalaugh3 27.1 m
Aug. 2, 2013 Prospecting N + W of Tunnocks UNKNOWN
Aug. 3, 2013 Ants In Pants UNKNOWN
Aug. 4, 2013 Tunnocks – Procrastination – bolting the climb ‘Bring on the Clowns’ UNKNOWN
Aug. 5, 2013 Antsinpantsschacht UNKNOWN
Aug. 6, 2013 Prospecting – Snow Pole and Dead Tree area to w-NW of Tunnocks UNKNOWN
Aug. 7, 2013 Tour of upper level Tunnocks + gear haul UNKNOWN
Aug. 11, 2013 Surface Prospecting - Drafty hole area Surface Prospecting 2004-10 51.1 m
Aug. 14, 2013 Tunnocks, Downgrade Window UNKNOWN
Aug. 15, 2013 Tunnocks, Downgraded window UNKNOWN
Aug. 16, 2013 window 86.7 m

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/
- the connection between the two is made in the URL resolver in troggle/

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