Neil Pacey : 2010

502.5 m surveyed this year.

Other years:  | 1999 | 2010 | 2011 | 2014

Wallet status | 1999 | 2010 | 2011 | 2014

Table of all trips and surveys aligned by date

Aug. 2, 2010 Tunnocks Rigging UNKNOWN
Aug. 4, 2010 Tunnocks - Checking horizontal leads Tunnocks
Aug. 5, 2010 Tunnocks - Stringfellows chamber and connecting to Usual Suspects Tunnocks
Aug. 6, 2010 Tunnocks - Stringfellows Tunnocks konigsbergpassage 170.2 m
Aug. 9, 2010 konigsberg2 70.2 m
Aug. 10, 2010 konigsberg3 95.3 m
Aug. 13, 2010 Tunnocks UNKNOWN konigsberg4 82.7 m
-- konigsberg5 84.0 m
Aug. 14, 2010   UNKNOWN
Aug. 15, 2010 Tunnocks UNKNOWN
Aug. 16, 2010 Ice Flow Tunnocks UNKNOWN
Aug. 17, 2010 Usual Suspects - Rampart Usual Suspects

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