2021-04-16

I'm bored of this one, time to move across

There's nothing particularly wrong with Blogger and I've got no real need to do this but...


Well, GitHub Pages + Jekyll turns blog management into a source-code management feast and it's possible to self-host for development / testing. In other words it's pointlessly harder to use, as far from WYSIWYG as you can get, and tremendous fun to muck around in.

Plus for the first time in about 15 years I can re-direct to a domain I own. Which is nice.

If you have any interest in anything I've written you might want to start looking at:

Things of Fleeting Interest: Bog-standard Nerd Self-Documentation


And, if you don't, my thanks for your attention so far and apologies for intruding on your day :-)

2020-08-10

Solar Power Is Great. At least as a toy....

 Everyone writes one rave post when they get a Solar Power System. Here's mine.

I've done my research and decided that where we live, and the way our house is oriented, means we were extremely unlikely to get any economic benefit from having a Solar system installed. We could marginally recoup value on a set of panels, but adding a storage system would never cost-in. So what would be the point?

tl;dr: Toys and Holier Than Thou Smugness!

In November 2019, I got made an offer....

So Tesla teamed up with Octopus to offer a special deal. Get a full solar system added, and one's rates would drop (considerably) as well as having parity on power exported. The big bonus here is when one is charging one's car a lot, this cuts the costs by nearly 50% just on the imported power rate. So I was interested.

We signed up to at least get a quote. And had a very professional survey done, and got the system on order in early January 2020. We were warned that the necessary regulatory approvals would take 6-8 weeks, which was fine - all being well the system should be in place for Spring and the return of sunny skies.

And then COVID happened. 

The system was finally installed in late-June 2020

If the world hadn't locked down, it looks like we'd have been ready to install based on approvals etc in early April. Instead it happened over a couple of days in late June. I want to add that it was a very impressive experience, our installers - Energize UK - were fantastic, very professional, very well organised and with a great eye for detail. And the support from the Tesla side was great too - with a good inspection/follow-up process to give lots of reassurance that the system's gone in successfully. 

The guys turned up at about 08:30 on the day of the install (the scaffolding having been erected the previous day), and by 14:00 I'd had my first entirely solar-powered cup of tea. Wonderful.

What we got: Hardware

We've got a 10 panel system, with nominal 3.15kW output,  a single SolarEdge Inverter with each panel connected single-string via an Optimiser. We've also got a Tesla Powerwall 2 (13.5kWh storage) and the whole system's held together with a Tesla Gateway 2 to manage it. 

As indicated above, we have a modest 4 bedroom house in the South of England. Our South-facing aspect is complicated by a gable over the main bedroom which limits the number of panels we can deploy. With the benefit of Energize's experience we determined that the west-facing aspect of the gable was unsuitable due to shadowing from next door and the chimney stack, leaving the south-facing main roof and east-facing gable as suitable. There's room for 3 panels on the East-facing aspect, and they managed to get 7 panels on the South-facing aspect, giving 10 in total:

Fig 1. The Solar array fitted to our roof. 7 panels face roughly South; 3 panels roughly East.

There's nothing in the Attic apart from cables from the panels being routed; it's possible to fit the Inverter up there but our insulation is on the attic floor, meaning it's not a temperature controlled space; I can verify from experience it gets flippin' cold in Winter and stinkin' hot in Summer, and while the Inverter's rated for those conditions it's not ideal for longevity or performance. So that and the rest of the system are all located together in the Garage instead:

Fig 2. (top-left) SolarEdge Inverter (bottom-left) Tesla Gateway 2 (bottom-right) Tesla Powerwall 2 during commissioning. It's a lot neater and tidier now!


There's a decent argument for keeping the Powerwall itself outside - mainly on safety grounds, as it's an energy store. In our case the passage between us and the neighbour is fairly narrow - sticking it there would get in the way of getting the bins in and out, and what I hadn't appreciated is that it's got a great big glowing green light on it which would draw attention. I've done some checking and the fire tests conducted show the overall risk to the house is fairly low so all in all, indoors in the (fire-isolated) garage is our best option. 

I should note that so far we've not had an upgrade to our electricity meter. We're on the list for a SMETS-2 smart meter but so far no news on when that might happen. As a result, nice hot sunny days have this effect once the battery's full and the immersion heater's warmed the water tank:



What we got: Software

Tesla App

Out of the box we have accounts with Tesla, so the App works great and shows what the system's doing and allows for customisation. Haven't felt much of a need to do much with it except set a 10% power buffer reserve for powercuts; they're rare and usually shortlived here so at normal loads that'll give me plenty of time to either wait out a short cut or (after say 15 minutes) if it's not back start doing an orderly shutdown of our household electrics. The nice thing about the Tesla app is the live view of status and where power's coming from and going to. 

Fig 3. Typical power routes
during the day
(the kettle's on for a cuppa)
Fig 4. Charging the Car still requires
some Grid power.


The Powerwall can supply 5kW (I've never seen it go over this although it's supposed to be able to do a 7kW surge), and that's enough for most uses. Although boiling the kettle while the oven is on and the washing machine's operating is over this limit, in practice the loads aren't continuous and it's rare to find household "spikes" of power that go above what the battery + solar (during the day) can provide, so our Grid usage during daylight hours has been minimal. 

The exception to this is shown in the 2nd screenshot, and that's when the car is charging. It's got a 32Amp (7kW) connection and it usually fires up outside peak solar hours (it's not been used much recently so it's mostly idle, but it does like to top-up by 1-2kWh every couple of days at least). So we do draw from the grid but the battery provides the bulk of the power for those small charges. One limitation at the minute is that there's no way of setting a priority for powerdraw - if I'm doing a big car charge I'd rather it all came from the grid and the Powerwall's energy was reserved for home use, but there's no way of telling the Gateway that. I suppose economically it makes no difference in our case but, hey, it'd be a nice to have. 

SolarEdge Monitoring

An unexpected but welcome bonus was that the SolarEdge inverter has it's own monitoring software, and our installer hooked us up with an account there. Whilst it only tells you about the generation side (up to and including the Inverter), it does have a degree more detail than the Tesla app about that. I quickly became addicted to the diagrammatic view which shows the performance of each panel over time. Here's what they've generated since install:

Fig 5. SolarEdge Energy Production in diagram form. Green box is the Inverter (and total),
each panel's production is shown in it's relative position on the roof. 1.1.9 currently in the lead
but it's the last to be shadowed as the sun drops in the West.


Ultimately, the SolarEdge stuff is less important for us - it'd be great if we were actually generating or exporting power, and it's valuable for giving feedback on how the system is performing (and I guess would be a good warning indicator of any panel issues, if their relative production started to drop off). But who doesn't love a good detailed statistic, eh?

Connectivity

Worth pointing out that both the SolarEdge and Tesla Gateway 2 need internet connectivity to show the data I've put above. The SolarEdge gateway has WiFi, Ethernet and (apparently) ZigBee connectivity options. The Tesla system is so dependent on connectivity it not only comes with WiFi and Ethernet but is also configured with a 4G SIM card for independent connectivity and monitoring. Shame we live in an area of poor signal, but it does work (intermittently). 

The Energize guys configured both to connect via our home WiFi network using a Powerline extender to the Garage. Subsequently I found that to be both redundant (I have a mesh WiFi system with good coverage there) and unreliable, so I reconfigured both to directly connect to the home network. That's worked great ever since although I noted the Tesla Gateway can throw a hissy fit when things change near it; hasn't happened a while but I did lose a couple of days of data early on before I discovered this propensity. 

The APIs

For me, the most interesting thing about the install is that there's both a remote and a local Gateway API. For the remote API one can query Tesla directly using one's account details and get configuration, health and performance data from the whole system. Of more immediate utility, though, the Gateway itself has a local REST endpoint that exposes much of the same data to local network sources...

So clearly I've been heavily using that and have a full time monitoring solution built using it to cover some of the (perceived) gaps in the Tesla App. To be fair, there's no way Tesla themselves could be expected to encapsulate the vast array of power billing mechanisms in use across the world - some of them so fiendishly complex it seems even the utility themselves don't understand them, so this isn't particularly a criticism just an area I wanted to address for my own needs. Having said that, it does somewhat erk me that there's no easy way to see what the battery is doing over time or to cross-reference that with the state of power use and consumption. So I wrote my own dashboard to provide all of that info instead:
Fig 6. Self-penned Dynamic Power Dashboard, bringing all the data into one page

(If you look closely at the "Power Today" chart you can see the car's had itself a little top-off already). I'm particularly pleased with the little status update top-left giving an estimate of when the battery will be full or empty. It's not clever - it just plots a straight line over the last 10 minutes - but it's surprisingly useful as an indicator.

At some point in the proceedings I realised that the rig up on the roof also effectively acts as it's own weather station - the amount of power being generated giving an indication of how cloudy it is, and the times of day when generating starts and finishes providing a proxy for the day length. Clearly, this is also graphable and dashboardable:

Fig 7. Rapidly disappearing up my own fundament, I present to you "Solar Array as Weather Station, The Dashboard"

The Economics

First major point to make is that we're about 6 weeks in to this setup, and that's over the hottest and sunniest days of the year. This is clearly not a good time to be assessing the economic worth of the system; I need at least a full year's worth of data before I can begin to do this sensibly. 

Second point is that I'm not going to give absolute costs. One, to preserve a fig-leaf of privacy and Two, your costs will differ, possibly greatly, in hardware, fitting and (most importantly) utility pricing. Do your own research before you make a decision.

With that out of the way, I'll make the following observations:
  • We get billed monthly for electricity. The last-but-one period was almost perfectly half before and half after the install, and as a result was almost exactly 50% of previous bills for the months before that
  • I've just submitted a reading for this month's bill. We drew a total of 3 kWh from the grid in that period. This is going to make our bill approximately 0.5% of it's normal monthly value.
    • (It's worth noting that I've been deliberately charging the car and running the immersion heater to avoid having to report negative numbers on the meter; I was aiming for zero but overshot yesterday as we did loads of washing and used the tumble-drier too)
  • The Battery is working well for us in the job it's supposed to do - run off the grid as much as possible. To a first approximation, the Solar Panels are generating enough during the day to both supply the house and charge the battery sufficiently to last overnight.
    • Actually the battery's proven it's big enough that, fully charged, it'll get us through an entire day of grotty weather. We only start drawing from the grid on the 2nd consecutive day of bad weather. 
  • Having the Battery act as a "soak" for our solar power means we're not exporting much excess. We seem to need 2 good days in a row to both charge the battery (...and top-off after overnight draws) and have enough left over to export. And we only  export in the afternoon despite generating most of our power in the morning.
    • If we were getting paid more to export, this would be a problem. At the moment, in this weather, it indicates we're well balanced between solar and battery.
    • Conversely, the rate we're now on we get the same for exporting power as we pay to import. Strictly speaking, this makes the entire Powerwall system redundant and valueless (as every kWh it "saves" from the grid we could export and import at net zero cost anyway)
  • According to the Tesla App, we've had two short "backup" events in the 6 weeks the system's been alive. These are times when the Gateway's detected the mains power has gone (or is about to go) out and has switched to entirely self-supported power. The first time we didn't notice anything at all. The second time some of the most sensitive electronics in the house rebooted which was noticeable. 
    • It's unlikely these were actual grid power outages - the Gateway's monitoring capabilities are necessarily paranoid to avoid brown-out scenarios, so it's more likely to go isolated at the slightest under-performance of the grid which nothing in the house would have noticed anyway. 
  • That worthless pointless weather-station dashboard above tells me we're already past peak power days for the year, with a long decline to winter ahead of us. We've had 4 continuous days of hot weather, yesterday was virtually cloudless, and we're down 20% on early-July's peak generation.

With all of the above noted, the most important figure economically is the time to break even on the install costs. Noting that we're a short time into ownership and that this is the best time of year for such a system, a simple calculation on monthly bill savings vs cost to install gives me a return on investment in a shade over 20 years. I expect once I can average this across a whole year it'll go up probably to 30 or so years.

Over that sort of period, there's too much variability in all factors - system lifespan, improvements in panel efficiencies, battery degradation and the changes in the utility market place - to have any confidence that the number is even meaningful let alone accurate. But I think it's clear that this is not an exercise that the thrifty and value-conscious should prioritise. 

I'll note that the battery system roughly doubled the cost of the installation, and as noted under the deal we've got it's actually adding zero economic value. So you could eliminate it and reduce time to break even by a half too. Having said that, we only got the utility deal because we've got the battery and current starting-from-scratch tariffs (post FITS-era) aren't normally anywhere near that generous as balanced import/export, so whether that would be practical in the real world is anyone's guess. 

Conclusions


Realistically: Too soon to say, but the omens aren't looking good for this being a great economic decision at the current time. 

Having said that, there are human and other non-economic factors in play that aren't accounted for by the account given so far:
  • I am far, far more aware of how much power we use around the house doing different things, and (by shouted osmosis) so is the rest of the family. This has already had the desired effect of making people think whether it's a good idea to leave lights on, or the TV, or whether that half-load of washing can wait. So we're slowly becoming a little bit more environmentally aware
  • The shear Smug sense of satisfaction one gets when we go an entire day without drawing a joule of energy from the grid without having to make any sacrifices in lifestyle is impossible to put a monetary value on, but should not be discounted. 
    • I am desperately trying to source a high-quality sticker I feel good about attaching to the car that says "Solar Powered - I'm Driving on Sunlight, not Dead Dinosaurs" or similar. I have achieved what proponents of electric vehicles have pointed out as one of the hidden benefits: My car emits less CO2 than when I got it, not more.
  • This system can only get smarter as we go. At the minute I'm manually switching the immersion heater on and off to "soak up" excess power and hopefully make an impact on our gas bill too; I'm well aware there are automated systems available to do this which I'm looking at, and the potential to make better use of smart switches throughout the house based on draw and capacity surely has some benefit. 

So: I'm very pleased and satisfied with the system we've got. Ideally I'd like more panels because MOAR POWER but unless and until we move house (....which we're not) that's not practical. Economically it's probably a white elephant but that's really not why we got the system in the first place. Insert your own Green Manifesto statements here if you like, I'm going to stick with the basics. We did this because we could, and because doing it feels like it's better for the wider environment than not doing it, over the lifetime of the system. You will come to different conclusions.


2020-03-28

OK, the world is shutting down.....

I think possibly the last update on this subject......

Here's an update up to 18:00 GMT Saturday 28th March. There's 4 weeks of data in this shot, with the very oldest (dotted) line showing A Time Before A Virus And An Airline Going Bust.

Flight detection rates really started dropping off from about Wednesday, with a steady decrease day-by-day down to about Tuesday (24th March). Rate since then has been fairly constant at about 25% - 20% (or: A quarter to a fifth if you prefer) of "normal" rates.



I think it would be pointless to speculate on if or when rates might return to normal at this point, so I won't.

We live in strange times...

2020-03-22

Air Traffic down by over a half

Yes, this is definitely a change in the real world.

You can argue that my first post was too soon on the topic given the data available, but look at the last 4 days and, yes, detected air traffic is down by well over a half compared to the previous week. 

...Really ought to do some work on classifying my detections by height - local, transit, landing etc....


2020-03-21

Yup. Traffic is definitely falling off

Quick follow-up to Thursday's post: Much clearer evidence of a fall-off in air traffic since then. Up to 50% today by the looks of it.

(And I hadn't realised what a spike there was on a "normal" Friday either, but yesterday was way down from those norms...)


ADS-B Aircraft Detection Rates, Thursday 19/03/2020 to 09:00 Saturday 21/03/2020

2020-03-19

The Skies Are Clearing.... Maybe?

So is Air Traffic decreasing in this COVID-19 world?

Background

As I write this, on March 19th 2020, we're about 3 full days into "properly" dealing with this damn COVID-19 business. By which I mean putting in place some self-isolation standards, not travelling unless we need to etc etc. And the news is full of stories of the impact of this, particularly on the travel industry and especially as it impacts Aviation. 

It's also (coincidentally?) about 2 weeks since our major domestic independent airline - flybe - went out of business (incidentally stranding me in Edinburgh but, hey, if you've got to be stranded somewhere, you can do a lot worse!). 

I wanted to test the hypothesis that if all of the above is real and active, we ought to be seeing a drop-off in air traffic.

Technology

I have a ADS-B receiver setup in my house. The summary of this is it's a radio that listens out for messages being broadcast from aircraft giving information on who they are and where they are - it's one of the more recent innovations in aviation safety and it's great. All commercial aircraft have it, and a lot of military and privately-owned aircraft do too. 

My rig (a Raspberry Pi Zero and an off-the-shelf SDR-capable USB radio stick) is part of the FlightAware global flight tracking network; all this data from feeds like mine is aggregated together and gives a pretty good global picture of what's in the sky at any given time. Since it's feeding that network, it's clearly capable of feeding other networks. So I've knocked up a bit of python to gather some summary stats on flight rates, shovel it all into an Influx time-series database, and then banged together some ugly but functional jqPlot code to spew out graphs showing me how many aircraft I've detected, hour by hour. There's a bit of cleverness to ensure that I'm getting a count of distinct "flights" rather than "sightings" but it's not rocket science. And most importantly it's nothing that I can't already get out of FlightAware's own dashboards already but, hey, why use something that's already there if you can build it yourself eh?

Location, Location, Location

All of the above needs a little summary: We live about 20 miles from Southampton Airport which is was a major hub for Flybe (approx 80% of flights into/out of the airport). Thanks to things like curvature of the earth, I can't directly "see" aircraft at the airport, my setup picks them up as they climb above about 1,500ft altitude heading North, and a bit more heading South (because my antenna is blocked by the house to the South). We're also about 20 miles south of Farnborough which is one of the major executive jet airports for the region (and, since that region includes London, the country) so the same conditions apply.

We're also within easy detection range of the major airways and routes going into and out of London (Gatwick and Heathrow) so, again, I can't see them on the ground but I've got decent sight of most traffic going there out to about 5-10 miles from the airport. And there's a couple of decent East-West airways, and at least one North-South, from the Americas to the Continent that normally picks up a decent amount of traffic heading to and from the European Mainland.

I'm trying to say that I'm well placed to get numbers that show indicative rates of movements into these locations, but I'm not confident that I'm absolutely picking up 100% of all traffic here and there. Basically: good enough to show changes over time, is what I'm hoping for.

The Data

Here's a chart showing the hourly sum of detected flights as three overlaid lines: This week (more accurately: the last 7 days), Last week, and the Week Before Last. I'd like to go back further in time - same week last year would be great, a month ago would be better - but I only got the data gathering sorted, er, 3 weeks ago so that's all we've got. It's just a massive coincidence I started gathering data the week before all of the action started happening, but one uses what one can get. Anyway:

Aircraft Detection Rates to 19/03/2020, by week.
Some features of interest:
  • Ignore that drop-to-zero at the far right; it's an artefact of how I report on the data I haven't bothered to fix (I should "ignore last hour" as the data's incomplete or unrecorded)
  • This Week (blue line) is significantly below previous weeks data, although not before about Tuesday (effects are less pronounced for Monday and back before - furthest right peak is today. Thursday, furthest left peak the tail end of last Thursday)
  • It's possible that there's a drop-off in traffic associated with FlyBE going bust around the time of the arrow. Tuesday's peaks 2 weeks ago are higher than last week; Wednesday of both weeks are about the same (FlyBE ceased operations effectively overnight between Tuesday and Wednesday at that time). If that's the case, about 10%ish of flights I was detecting were FlyBE related.

Interpretation

Honestly I don't know whether I'm over-interpreting insufficient data.

I'm more confident in saying that, in the last 48-72 hours there's been a significant (up to 30%) drop off in air traffic within our area compared to the same time last week. 

I've got some evidence that I was able to detect our regional airline going out of business by a 10% overnight drop-off of traffic that never recovered, but really I need more information than that.

Inspection of FlightAware's consoles - which plots "live" data like an air traffic control radar - shows that there's significantly fewer "small" aircraft (business jets, helicopters, private aircraft) than I'm used to seeing but it must be stressed that this is anecdotal observation, I don't have hard data to back that assertion up.

Further Work

What I haven't done is use the additional data available from look-up sources to categorise the data I've got. It might be useful to break down the data by aircraft type - commercial jet, business jet, helicopter, military etc - to work out which sectors (if any) are genuinely changing over time. Ah well, perhaps that's a project for another day.....

2019-01-07

ESP32 (more precisely: Heltec WiFi Kit 32 with onboard OLED display) WiFi WalkBy Signal Strength Plotter

Expanding on the previous post showing a restored out-of-the-box functionality, and inspired by the capabilities of the excellent u8g2 graphics library (all be it restricted by my limited imagination and capabilities), I have the pleasure to present Version 2 of the WiFi Scanner displayed onboard the ESP32.

This one only plots the top 3 WiFi Signals found (identified by router MAC address, not by name as you wouldn't believe the number of duplicate network names you'll find just walking around....) But, it stores "recent" signal strengths and uses that to plot a sort-of bar chart under the network of strength. I don't know how useful it is, but it's fairly nifty and I'm more proud than I ought to be about it.

Here's it running in a Generic Semi Public Location:

(image processed to disguise the terrible job I did of soldering on the pins)

Updated 2019-01-08 12:46: Changed the "replace with new network" code to zero-out stored and now invalid history for the old SSID.

2019-01-04

HELLO (esp32) WORLD - a re-creation of the code running on my ESP32 Board when I got it

Wasted a number of hours this evening in re-creating the WiFi scanning code that was running on the board when it arrived (and which I immediately blew away with my first upload). Mostly this was a learning experience in the U8g2 driver but there's a bit of Arduino IDE learning involved too....

Here's it running:


(It's not identical to the original, in particular the font I've used is almost certainly different. And it doesn't display the logo on boot, mainly because I've got no idea where that logo is defined and I've got no inclination to find or create a new one).

Note that I'm explicitly not claiming ownership of the code, I've noted where I've heavily borrowed from. Mostly this is for my own later use if I have to build another dev environment, if I'm honest.

The original WiFi scanner is a built-in sample of the ESP32 board samples (File -> Examples -> (ESP32) WiFi -> WiFi Scan). This version started from the example written by Robot Zero One available here, but I modified it to use the page-buffer because I wanted to have control over font sizes. I'm still not 100% sure I'm Doing It Right because pushing stuff to the display seems to be over-complicated, but it does have the virtue of, you know, working.....


2017-05-23

Portsmouth to Paris and Back - May 2017

This was written immediately on return, because I'm old and my memory is crap.  Note that this was an 11-man ride and I'm only 1 of them. Nothing I write should be taken for anyone else's experience. I will respect privacy by using only first names or initials to avoid confusion. And despite others having some cracking photos, I've not used them. Let me know if there's anything anyone objects to or wants taking down.


Portsmouth to Paris and back - May 2017

The Prologue

A good friend decided last year at fairly late-notice to ride from Portsmouth to Paris and back on 4 successive days to prove that age wasn't affecting him. With more notice I'd have loved to join them but instead watched enviously from afar as he and the 3 people with him managed it, unsupported, but decided it could be done in a much better way. Like with a support van to carry overnight gear, and probably better packing, and definitely without an arse-munching saddle.

So around Christmas time an invite was published and (I hope) a pleasantly large group of people responded positively. We're all middle-aged, spanning both ends of that range, and there were a few drop-outs and late-additions, but on Thursday 18th May 11 riders and 2 support drivers (and their hired van) appeared at the Ship and Castle for a couple of pre-ferry stiffeners.

I should mention, perhaps, that in marked contrast to last year a decent effort was put in by all concerned to prepare. I've been riding every week since Xmas, and twice a week (or more) since the clocks changed, mainly with Peter. We got up to 75 miles in training with no ill effects, so basic confidence was high.

Shout-Outs

Before continuing, all gratitude must be shown to the following:
  • Matt - his idea, his enthusiasm and his organisation. Without which none of this would have happened. I'm so very grateful.
  • Tim - Mr Organisation. Has a photographic memory for routes, and appears to know the location of all the good bars and restaurants in all towns and hamlets in the northern hemisphere, as well as being Kitty Holder extraordinaire. Thank you.
  • Xavier - Mr Local Knowledge. Made the trip along the coast line a joy, provided valuable translation skills, and a great source of entertainment despite the chronic pain. I wish I could display such fortitude under such conditions.

Day One - Ouistreham to Evreux

The morning began by exiting a packed ferry at 0700 local after the inevitable insufficient sleep. Xavier's foresight (and previous work experience) meant a proper french breakfast was laid on for us in the ferry terminal. Our ride started just before 0800, and with Local Knowledge available we took a side-road down to the bridges avoiding the footpath. Sadly this coincided with rush hour, and getting onto the main road (only to leave it shortly after) was about the worst traffic we encountered. A short while later, though, we left civilisation behind and started heading cross-country.

Two things became clear quite quickly: firstly, we had Tortoises and we had Hares. Secondly, the scenery was well worth looking at, the rolling countryside being a constant source of delight for the eyes all day. I was quite happy in my role as Tortoise, initially in a 3 out of 11 group but that was fairly fluid. We rolled on for a couple of hours, stopping for Coffee and Croissant  at Saint-Julien-le-Faucon, after 30 miles:

After this, we set off together but again quickly (after the first hill...) separated out. For the next few hours, Matt & I formed the "sweeper" group ensuring no-one got left behind whilst enjoying (genuinely, in my case) a delightful cross-country ride sweeping across enormous high plains, swooping down through ancient villages before a (usually) gentle climb out onto the next plain. It's worth noting we were incredibly lucky with the weather, arriving in towns to soaking pavement just after the rain, or riding along at the head of a following storm. We kept this up pretty much constantly (modulo an Orangina-and-Chocolate stop in Orbec) through to Beaumont-le-Roger at the 70 mile mark, where our 2-man Tortoise group arrived to find lunch of World's Biggest Pizza had already been ordered, and that the rain was about to pour down. Lunch was therefore very, very much appreciated sat indoors out of the weather watching an ancient episode of Columbo dubbed into French... his "..just one more question" still being instantly recognisable:


After lunch, with only about 25 miles to go I apparently had sufficient legs to keep up with the Hares, and we had another great couple of hours racing across more delightful countryside, with the added amusement factor of our resident Big Puppy Peter "The Red Baron" chasing all and sundry - including tractors - across the plains of Normandy.

And so it was we arrived at our hotel in Evreux just before 1700. Nearly everyone was happy with the 94.7 miles done in good time, in good conditions, and feeling fine. But there was one person who could very easily be goaded into making it a round 100 miler, so Pete and I hared off on a couple of "laps" of the town centre - at rush hour - to knock it over the limit. Stupid and Pointless, but a milestone nonetheless: A genuine Imperial Tonne ride:


The evening was spent in several delightful bars, and a perfectly serviceable restaurant in which many Calories were consumed. It was not a particularly late night...

Day Two - Evreux to Paris

Our ride started at the hotel at 0800, with a short diversion to Evreux's closest equivalent to a 'Spoons for more croissant and coffee before the departure proper. Getting out of towns at rush hour isn't much fun (even on a Saturday) but we managed it in short order, and again were very quickly out in the countryside. A couple of minor climbs notwithstanding, we pretty much kept in one group for the first hour or so, stopping for a second breakfast (need those calories) after 15 or so miles at Garennes-sur-Eure.

However, after this stop things went badly wrong for me. I'd picked up some right ankle pain on the first day, probably through over-tight shoes and/or bad cleat position. This came back in droves here, and allied itself with a massive dose of fatigue. So although the morning's ride wasn't particularly testing, I was hugely struggling to keep up with the back-markers and (I'm sorry to say it) really not enjoying the experience. I can't remember much about this part of the ride other than the suffering, even having looked back at it, except for the very end portion through Saulx-Marchais, the descent to Beynes and the (relatively easier than expected) ascent up to the airfield cafe at Beynes-Thiverval. Here was a most restoring 3-course lunch, sat in a tent watching gliders arriving and departing behind a motor-glider, with an old Mirage as gate-guardian:

(Peter's is in much better condition. And still has a Donk inside unlike this poor relic).

It took us a long time to get going again after lunch thanks to the size of the meal, our first tyre-change (self inflicted, apparently), and because we'd all got quite cold sitting in the breeze. A short ride up to and along the ridge saw another unscheduled pause to deal with our first genuine puncture, which we each handled in our own style:


From here we swept down off the ridge, through a couple of villages and onto my own first test - a deviation from the previous route after Chavenay to take us away from the Autoroutes. Initially, this went brilliantly: A short climb up a semi-busy road to take a farm route across country, which after the first up-and-down revealed, far in the distance but straight ahead of us, our next destination of Versailles Palace. My confidence and mood was high at this point, but it was premature. The route got less placid as we got closer, with a dark passage under a bridge through mud and gravel being particularly unpleasant. But then we got to Versailles Park only to find that all gates were locked as an anti-terrorism measure. Several probes were made to find a way in, with consensus being reached that the main road was our best option. Fortunately, this turned out to have a separated cycle-path, and at the head the Park (close to the palace grounds proper), an open entrance was found that allowed us into the park. We spent far longer than we really should have taking selfies and group-shots in front of the fountain and deciding how we could remedy the castle's under-statedness. 


After this, and a chaotic and spaced-out zoom around the north side of the grounds, it took us far too long to regroup at the front of the palace, and as a consequence it was nearly 1800 by the time we headed out on what I was sure would be our cycling highlight, the velo-route to Notre Dame. 

Things didn't start well, with a signpost apparently pointing through a forest really pointing at a path the wrong way down a slip road, a diversion past a railway station onto a river track that was honestly really on the Velo route despite being marked "no cycles" at several points, and a couple of obviously new sections that just flat-out weren't on the published route. But then it settled down into a properly-segregated track away from the roads. Sadly, though, this doesn't mean it wasn't a) quite up-and-down b) quite side-to-side c) frequently barriered to avoid zooming straight across roads and d) absolutely rammed full of Parisian families taking a leisurely Saturday evening constitutional. 

It took us forever to get to Montparnasse station, and it was notable how short words being spoken were by the time we got there. We all took a quick diversion to get a group shot with the Eiffel Tower behind us - my own effort not coping with the contrast differences. It's behind me, honest!:

At this point we split again into 2 groups, one going for a proper Eiffel Tower shot, the other (with self navigating) going "directly" to the hotel. Thanks to at least 1 navigational error (obvious, now I see the map), some awful shared-with-pedestrian sections in which we really needed Angus's icebreaker to clear our way, and a couple of re-grouping stops we ended up getting to the hotel after the Tower party despite their longer distance. Events such as these provide all of the material needed to fuel the evening's bar discussions, a true and accurate representation of which is shown:


Day Three - Paris to Rouen

This was the day I'd been training for: I reckoned it'd be the hardest, 2 down, 1 more to go, and one of the longer, hillier routes. You can imagine how I felt after the poor showing the previous day; it was 50/50 whether I'd get on the bike or not. I'm glad I did.

After the disappointment of finding the only Boulangerie in Paris with an inadequate supply of Croissant, we zoomed out of Paris following a decent route mainly of Tim's devising that took us through some of the less touristic parts of the city in an effort to get to countryside quicker. Our arrival at green fields was celebrated in proper middle-aged style with a comfort break. I decided Paris hadn't seen enough of me and took the opportunity to apply a second coating of Chamois Cream. Much to the delight of my co-riders, naturally.

We spent a decent chunk of the morning following the Seine, sometimes very closely indeed, with some glorious riding. A few minor climbs, a couple of thrilling descents, and one quick lung-burster away from the river at Andresy. It wasn't easy riding (for me) but it was manageable and we stayed in one group pretty much all the way to Meulan-en-Yvelines where we paused for Second Breakfast (and suncream) by the river.

After this we left the Seine and headed cross-country. Time was against us a bit - we needed to find lunch before everywhere closed, so there was some pressure to keep the speed up. The climbs weren't steep, but they were long, and we inevitably spaced out again (I tended towards the rear here, and as a general point it's a lot easier to keep up with people than it is to catch up with them).  Our one scenic stop on the hills above Moisson was short and a bit arbitrary, but the descent into Gommecourt was spectacular enough to make up for it. After this, the valley route through Limetz-Villez, past Monet's gardens at Giverny and on was spoiled a little by the time pressure. As a result of which we took an unscheduled detour into Vernon where plenty of options were available for lunch: Most had kebab but I went classy with a chicken burger and chips outside the fantastic church there:


After this refreshing pause, it was back out onto Route des Andelys to continue. Frankly I was tired enough that it took me a good 10 miles to realise I was nursing a puncture; a roadside stop just outside Port Mort was required to address this, with Marcus, Matt and myself cementing ourselves here firmly as the back-markers with this. I must give Mad Props here to Marcus for his assistance and sharp eyes with the tyre change - I'll give the Schwalbe Marathons a pass as the shark-tooth grit he dug out at the edge of the tread wasn't well covered by the puncture resistant strip and was sharp enough to penetrate. On the plus side: those tyres ride quite well even when flat (I'd been bumbling along at 17mph for miles before I noticed).

Our 3-man peloton pressed on to re-group with the fast riders at the really rather spectacular Le Petit Andely, where they'd enjoyed a coffee break that we skipped. After this we carried on but with the addition of Pete to our gang of Tortoises for the last stretch. After more Seine-side work, with Parascenders above us on the cliff tops, we left again at Muids for a quick up-and-over to Herqueville to rejoin (where we found we were overtaking the working traffic on the Seinne, a minor but needed boost to the ego), before leaving finally at Pitres.

After this came the fairly well advertised "Last Big Climb of the Day" which, despite the fear, was quite pleasant; the road had been resurfaced, the worst of the ascent was done in a shaded forest section, and it brought us up to another of France's Big Sky plains with the advantage of real Planes from the local airport buzzing around us as we circumnavigated it. From here it was a bit of suburb-hopping to get to the day's finale, the spectacular descent into Rouen proper, a mile or so's fast descent made all the better by being "free" - cyclists know that what goes down must usually go back up, so to have this long, long drop knowing the hotel was at the bottom was a real joy. We were diverted from our destination by the imposition in front of us of another Belgian Bar, where all stopped to enjoy the early evening sun and a couple of pints of local anaesthetic:


Sadly, while we were enjoying this some local scrotes were helping themselves to Pete's bike despite it being only 5m away and within sight. This really put the downers on the mood; the evening was great (Rouen is a beautiful city) but it was understandably overshadowed.

Day Four - Rouen to Ouistreham

So while I'd been dreading Day 3 for the riding, the final day was my Bete Noire because I'd done the route for it (no alternate being available). It wasn't difficult - find small roads in the right direction that stay away from crappy places and cliffs where possible - but it was time-consuming and hazard prone (the routes we'd inherited were meticulously hand-researched and ground tested over years. I had Google Earth). It was a mixed bag but people seemed to enjoy it...

Departing Rouen was a bit easier than I feared as the riverside cycle path went just as far as we needed it. The ascent out of the city wasn't dreadful, but it was long and on a busy road (we left just after rush-hour but that just swaps cars for lorries). Fortunately at the peak we turned off onto a country road that was an absolute blinder: a decent 8 mile gentle descent through forest and fields that kept our Fast Boys happy in their sprinting and the rest of us really enjoyed the low-effort / high-speed cycling for a good distance.

It was just a shame that the ferry we needed at the bottom of the descent was broken, that's all. Five miles back around the shoreline took us to the next nearest ferry though, and luckily the exit point here was almost exactly on my backup "crap short route" plan out of Rouen. A 10-mile diversion / addition to the day, but not a total disaster:


From here we followed the "crap route" through some unremarkable suburbs, and onto the long ascent up to Saint-Ouen-de-Thouberville. Here's where we made our own little bit of news - before the town there's a choice of Peage or green-route to Caen, and clearly there's a lot of heavy traffic aiming to avoid the tolls. But the road's quite narrow, and the French are very very good to cyclists either giving plenty of room when passing or, as here, just not passing. The 10 minutes or so it took us to get from the roundabout into the town, with a very patient Artic behind us, meant that when we paused for more pastries and a coffee there was a genuine Waze/Google traffic alert on the section we'd been on. All our fault!.

This road wasn't much fun, but we needed to follow it for a few more miles to Bourg-Achard before turning off towards Bouquetot, which turned the route from heavy-traffic purgatory back into our favoured delightful back-road rolling countryside. Although we again split into Tortoise and Hare here (more Tortoises today, although still not a strict majority), there really was only a difference on the few steeper climbs; we were all rolling along the countryside at good clip (17-18 MPH on the flat) aided by great weather as we had been all weekend. After Bouquelon we descended from our side of the Valley on one of the faster descents through some lovely turns and switch-backs, only (for us Tortoises) to be met at the bottom by a reversing car and the smokiest diesel in the world coming the other way. Good job the brakes work!

From here after an only-slightly-dodgy traverse of the D6178 at Foulbec, we climbed up to Conteville to get our first sight of the sea (or more accurately: Estuary). As a 4-main train we chugged on through some rolling, twisting routes up the floodplain and around the shield hills towards our planned lunch at Honfleur. Pete was clearly holding back behind me, so with only 6km to go I confidently told him even an idiot would find it from there, just follow the signs and off he went. Not 1/2 K later was a roundabout with the (signed) main road leading right, but the planned (and shorter, as well as quieter) route going straight over. And no sight of Pete. I spent the remainder of the 5km to the quayside kicking myself for being so confident in my pronouncements. But luckily when we got there he had just arrived himself, and we were only 5 mins behind the Hares on a 25 mile section.

Lunch was, again, welcome if a bit late (with thanks to the Restraunter that Xavier persuaded to stay open for us, and who willingly refilled water-bottles afterwards even throwing in Ice with a smile). At this point we'd made up our deficit in miles, and had only 30ish to go, so despite leaving late (closer to 16:00 than 15:00...), and with the addition of our Local Knowledge rider Xavier back to the fold after a day or so off with injury, the mood was high for our last stretch.

There was a climb out of Honfleur, but it didn't amount to much. It did, once again, separate the groups but there was more spread amongst the Tortoises than before. Or more accurately: I got caught on my own in the middle, with 6 fast guys ahead and 3 slower ones before. This wasn't a problem - a beautiful sunny day, lots of water, a fully-charged Garmin with route loaded - and if I'm honest I appreciated an hour or so to myself to enjoy the scenery and ride, but I really ought to have stayed with one or the other of the groups. As it was, by strictly sticking to the published route (and not having the benefit of local rider Xavier's knowledge on which was the best route), I came through the centre of Deuville (over the cobbles, chasing a vintage car) and popped out at the seafront just in time to see the Hare Peloton pass in front of me. They didn't see me, but I gave chase and was soon dropped again. However, by sticking to (my!) published route which inadvertently went the wrong way down a 1-way street, and by them stopping for photos, I again popped out near La Garenne behind them. The imposition of a small but relatively steep hill ensured I once again dropped behind here, though.

So I was left to my own devices along the coast at Blonville-sur-Mer, chasing an Audi R8 through the 30kmh zone (and keeping up!), and stopped at the end of Villers-sur-Mer for a Mars Bar and water break hoping the remaining Tortoises would catch me. Since they didn't, I did the final Big Climb Of The Day on my own up to Alberville and, as warned it was a doozy of a climb. Proper 2nd gear slog for a good mile or more, with several "I'm sure the top's just around this corner" moments before the final sting at the top. However, from here it was a delightful cross-country then long swooping descent into Houlgate, promising myself (loudly, at the top of my voice, to the empty skies) that no matter what I was stopping here for an Ice Cream. And then, as I popped out onto the seafront I was again caught and overtaken by the Hare Peloton who'd both come a different (longer) way and stopped for an ice cream themselves.

Fortunately, the saint and martre that is Peter decided to show me where the ice cream shop was and perhaps even partake himself. I am very grateful to him for this kindness and my ice-cream leaping out of the cone as I hit the curb coming into the car park was no-one's fault but my own. And I'm not ashamed of scooping (most of) it back up and finishing it. IT WAS MY HOLIDAY ICE-CREAM GOD DAMN IT. Here we all regrouped, we happy few, and a passing brit was kind enough to take our group shot:


If we look happy, it's because we know we're done with climbing, we've got plenty of time to get to the Ferry, and most of us have had an ice-cream. From here we went on to Cabourg, where a seafront Beer was obligatory if ruinously expensive:


...After which, we had a cheeky little 12 miles to go, which we seemed to need to take at top-speed. Alan, to this point an absolutely dedicated Hare, decided after a close call that a more measured response was called for and deigned to take me in tow for a good portion of this ride. I've never been more relieved for someone to call "water stop" than I was when he did so only a mile from the bridge; he may have been taking it easy but he was still at my top-speed.  From here we went over Pegasus Bridge where we were lucky enough to intercept our support drivers for the first time since Honfleur:


..and from there, it was up the canal path to Ouistreham, where we declared "Finished" at the seafront and went for dinner. I had a Savoury Crepe that was delicious although it didn't have Frites. And then a Citron Crepe for pudding because I reckon I could.

From there it was the usual phaff to get onto the ferry, one last drink in the bar with a bit of post-match analysis, bed, then up at the crack of dawn to stumble off the Ferry, through Passport Control and across Portsmouth to get the train home. And now here I am and that's the end of my 1/2 day holiday so I'd better get to work.

2016-01-15

In Praise of the BBC and it's Education Mission

Or: I love Stargazing Live and I'm not too proud to admit it.

One of the things the BBC does best is Educate. More so than the other 2 legs of it's charter (Inform - news - and Entertain - everything else), it's really the only organisation in the country that has the freedom to do so. 

Nowhere does it demonstrate this better than the annual StarGazing Live extravaganza which normally runs over 3 nights in January. Over the last 5 or so years, they've managed to use this show to bring Astronomy and all things Space to the public in a way that's clearly a success. That's demonstrated ably by this year's Special Guest Victim, comedian John Bishop who's spent the last 3 nights being flung around in centrifuges, undergoing (voluntary!) hypoxia and conducting simulated EVAs in ESA's training tank, all in the name of showing the sorts of things Astronauts have to do for training. On the first night he admitted he'd not been particularly interested in the stars until he'd sat down with his kids to watch Stargazing a few years back; the moment of heartwarming when he gave a shout-out to Tim O'Brian for giving his wife advice on what telescope to get him for his birthday shows exactly the sort of atmosphere we're dealing with: a bunch of nice, relatable, smart people doing their best to present on topics they've got an interest and passion for, for the benefit of the nation.

From poor old Prof. Lucie Green, forever stuck in a muddy field doing her best to let us know what we could see in the night sky if only it wasn't raining again, to Liz Bonin who does an excellent job both in explaining whatever torture John Bishop's going though and acting as the nation's worried Mum for his health throughout it, to the aforementioned Tim O'Brian, the genial, knowledgable and very tolerant host of the event as director of Jodrell Bank, to the two presenters - Professor Brian Cox, the nation's National Treasure scientist and his "straight man" Dara O'Briain, forever tasked with the job of keeping things on-track for the 60 minutes. There isn't a single one of them who doesn't communicate their excitement, enthusiasm and knowledge and make the show work.

But a special mention must be made for Chris Lintott, the whole Sky at Night team (who very clearly support and back-up the production), and the Universe Zoo project which has absolutely and rightly latched-on to the interest in the show to achieve wonders of crowd-sourced science every year. Starting with a proper leap-in-the-dark (again: who else but the BBC could support this?) on the first series, the success and engagement shown by the general public has challenged them to come up with new and interesting projects to showcase every year, a sign that they're really hitting their stride with this has been that there's actual published scientific papers now flowing out on a regular basis. I repeat: A prime-time live show on a public channel has a side-effect of generating real scientific discoveries. And the joy shown on their faces when they can announce the findings (this year: a Pulsar discovered "somewhere in Cygnus" that's showing evidence of orbiting something close by) can't be beaten. Getting (one) of the families who'd done the work to find it in the data on Skype in the background to show their excitement over what they found (and name the Pulsar after their Guinea Pig pets) was also a masterclass in making science relevant and interesting.

And we must not ignore the guests. From (relatively!) obscure scientists, to probe mission leads, to interested amateur celebrities, through to veteran and current Astronauts, the guests have been superbly chosen to compliment and extend the show. Nowhere is this better shown than in the companion "Back to Earth" programme shown immediately after the main show which takes a less structured "fireside chat" approach to extending on the night's topics. 

A defining moment of the programme was (I think) in the second year when, having secured a veteran Apollo Astronaut (Walter Cunningham), current superstar Astronaut Chris Hadfield, and grand dame of the outer planets Carolyn Porco, the producers wisely ditched the "filler" entertainment pieces (questions from K9 as I recall) to give more time to the three guests. How rare, how delightful, how enlightened of the production team to re-plan, live, to get the most out of the opportunity. It's an attitude they've carried on with and it's marvellous. This year they've gone all-out, adding (with little prior warning) a 4th show tonight with Chris Hadfield to talk through Tim Peake's spacewalk and I have to say I can't wait. 

So: If you want to know what a "socialist", nationalised, publicly-funded broadcasting organisation can do that commercial entities can't? Look no further. Having the ability to go all-in on a niche scientific subject, put huge commitment and resources into it, and make it a stunning success.

Now if you'll excuse me I must go find a livestream for NASA TV to watch this spacewalk...


2014-09-08

HPV Vaccines Not Proven To Be Unsafe, Or, In praise of the Wise Sages Goldacre and Harford...

We were passed the following link and asked for thoughts. We have a child who is of age to join the NHS HPV Vaccination programme:


Summary of Objection

If we take what's asserted in this link, and combine it with the important numbers it doesn't provide to give total population information, the numbers given in this link suggest your child might be 10 times safer after taking the vaccine than she would be if she didn't. 

This evidence is in direct conflict with the conclusion the link itself wishes to portray of a drug of questionable efficacy and safety.

Background to the Objection


Thanks to years of reading popular science writings, and in particular thanks to Ben Goldacre's Bad Science and Tim Harford's work on the Radio 4 show More or Less, I am no longer able to read such links without at least a cursorial attempt to work out what's not being said.

I could tackle the material in a visceral, emotional way, based on what we know of the context of the link and it's material, especially in reaction to the source country's known political and anti-vaccination movements. But in a poor imitation of the two Sages I venerate above, let's try some Science and Statistics instead...

Analysis of the article's assertions


The core arguments made to support the (simplified) conclusion "Gardasil is Bad, M'Kay?" in the article are:
  • 30,000 adverse effects reported for takers of the vaccine in about 7 years, of which:
  • 1600 were serious or life-threatening, 
  • 136 people who took the vaccine subsequently died.

These are scary numbers. BUT we're missing vital context:
  • How many people were vaccinated with the drug?
  • What is the chance of someone dying during the appropriate period anyway?
Because the source link came from the US, I'm going to assume for the rest of this work that all figures will apply to the US only. I'm not convinced my source materials (I'll embed links) are entirely consistent in this, but I'm fairly happy that my numbers will be in the right order-of-magnitude, and I'll try and prove that this is Good Enough to come to some supportable conclusions.


Let's start by answering the "background radiation" question: Given this Vaccine is aimed at girls between about 12 and 20, what's the chance of a girl of this age-group dying of any cause?

  • This link suggests a "background rate" of 11 deaths per 100,000 for under-20s in the US. But that's boys and girls. Let's say the rate is about 5 girls per 100,000, per year.
  • The US census estimate an average teenage population of 42 Million (boys and girls) between the ages of 10 to 20 
We can then multiply the two together:
  •  (21,000,000 / 100,000) * 5 = about 2,160 female deaths per year.
And, just to be clear, we'll call this the "background rate" - it's deaths from all causes, averaged out across the whole US (interestingly, go look it up, most of these will be from car accidents even though they massively favour testosterone=infused boys. Why aren't we making a fuss about Our Precious Children driving these lethal steel boxes? But I digress).

This doesn't make the 136 deaths linked to Gardasil over 7 years doesn't sound too bad after all, when compared to the expected 15,000 females killed from all causes over that time-span. But let's be rigorous, as we don't yet know the percentage female population given the drug. We can put a lower-boundary on this, though, in order to decide when to start worrying:
  • 136/7 = ~20 deaths per year linked to the vaccine
  • 20/2160 = 0.9% of annual deaths
...So, even without tackling the central problem with the statement "20 people per year taking Gardasil die" (which is, to be clear,  that no-one's attempting to prove whether those deaths have anything to do with the drug), we can be fairly confident that if we discover that Gardasil is given to more than about 1% of the female target population, the death rate is unaffected by the drug. So we need more numbers.


 Wikipedia says 57 million doses were given in roughly the same timescale as the adverse reports, which gives a reasonable upper bound on the number of girls affected. We need to add to this that the standard drug regime has been 3 administered doses per person over a 12-24 month period, so we can estimate that:
  • 57,000,000 / 7 / 3   = ~2,700,000 girls given the drug per year
I should be clear that this number is not geographically-bounded, and it's not absolutely clear whether those doses were all administered, vs just manufactured and/or distributed. But it's what we've got to work on. 

At any given time, the female target population aged 10-20 in the US is about 20,000,000 so we can estimate that about 13% of the female population has been being (fully) vaccinated (note: the Wikipedia link referenced above states that about 33% of girls in the US are currently receiving at least 1 dose, so we've immediately got a conflict of information). 

All of a sudden, this turns the study on it's head. Let's do the sums:
  • We know the chance of an average girl dying in the US, per year, is about 1 in 20,000
We can now calculate the chance of a girl taking the vaccine dying as:
  • 1 / (20 / 2,700,000) = about 1 in 135,000
Or, in other words, according to the material given in the link itself, my child is around 10 times less likely to die after being given the vaccine than she would otherwise.

But my analysis is flawed, because without evidence I've asserted all doses administered to US Girls.  Let's assume only half the doses went into the arms of US girls. This doesn't change matters much: it only means my beautiful daughter is 5 times less likely to die with the vaccine than not. If only 10% of the doses were administered to US girls, then without anything else changing we can still say the drug's not affected the chance of your child being killed this year.

And that in itself is a very simplistic view, because it's based on an assumption that 90% of the doses of the drug went either unused or into the arms of girls from other parts of the world who we've implicitly assumed have a 0% death rate, which is patently false. And we've already got information that suggests the number of vaccinated kids in the US is much higher than my 13% figure so the error could very well go the other way making my kid even safer than I've calculated...

All of which is to say that my analysis is, I am happy to confirm, wrong. But it's probably not more than an order-of-magnitude wrong, and even if that's the case my central refutation of the source material stands.

Conclusions


At this point, I've done enough Science and Statistics to stop worrying about what the article's trying to tell me, because it's clearly not being backed up by sufficient facts to make it's argument robust. I probably ought to tackle the "incapacity rate" number (1,600 over 7 years) to strengthen my case, but I just can't be bothered: The central thesis of the link is that I should be scared of giving my daughter this vaccine because it might do her harm, but the "facts" it quotes to support that thesis suggest the exact opposite. I see no reason to believe it's assertions over serious harm are just as flawed.

But let me be absolutely clear: I'm not suggesting that the HPV Vaccines are some sort of wonder-drug that magically improve your kid's chances of survival, and I'm not going to make any assertions of the efficacy or safety of the drugs concerned. All I've sought to do is to tackle the fundamental gaps present in the information presented by the source link and see if they can be supported by available evidence, and my conclusion is that they can't, and that the authority of the assertions made and conclusions drawn by that article are therefore, at best, questionable.

All I'm trying to suggest is that you should take the claims made in the source link with a VERY large pinch of salt and back them up with a decent review of other materials when making your decisions. 

2014-07-14

London to Brighton Night Ride 2014 - Trip Report

Anyone who's been tracking the Twitter and Facebook updates I've been making probably has most of this, but I thought I'd put it all down in one place for my own reference purposes...


Motivation

Since Patricia did the L2B day ride in 2011, we've had a bit of a family thing going for supporting the BHF London 2 Brighton rides. I did the day ride in 2012 (and wrote it up here), we both did the day ride in 2013 with friends (and didn't really enjoy it due to the traffic), and I did the Night Ride last year with a friend and really enjoyed it. 

So I was keen to do it again - so keen, in fact, that I signed up last September, although that was after a couple of beers and enthusiastic blather in a hotel bar with friends and colleagues. Take it as a sign of my enthusiasm and not poor judgement.

I was initially hopeful to get a crowd doing it this year, but for various reasons that never happened. This wasn't really a spirit damper but it did change the character of the ride for me.

Preparation

I've got two modes of preparation for bike rides: Just Sufficient (2012) and Far Too Much (2013). This year fell somewhere in the middle, due to the nasty weather at the start of the year, some minor illness and one or two bouts of laziness on my part. But for the last couple of months I've been out at least once a week, I've done a couple of 50-mile rides to prepare (never quite satisfactorily; they were very tiring and at the limits of my endurance), and thanks to a good friend's encouragement I've even done some off-road cross training. 

I've also gotten off the fence and made a couple of investments in the bike. The first was to get some SPD clip-on pedals. These things are fantastic - just as everyone has been telling me for years - and if you've never tried a ride without tying your feet to the bike you don't know what you're missing. Hills become easier and faster to climb, power can be put down more evenly around the pedal stroke, and you run the risk of collapsing in a heap every time you come to a stop thanks to forgetting to unclip. They're great!

The second change was to get some better lights. I've dithered between the light-of-a-thousand-suns offroad type and just something sensible and long-lived. Since I've done and hope to do a bit more commuting on the bike, being sensible won out and I got a nice set of LED USB-rechargeable lights that throw out a decent beam at the front and blink forever on the back. 

Finally, as a bit of a last-minute change, I bought a new seat for the bike last Tuesday. I've had trouble with my seat for years, it's not so much the ho-ho-ho razor-blade-not-saddle effect as that the geometry caused cramp and numbness in various parts of my thighs and...other areas... after a long ride. I dithered in the bike shop for quite a while wondering whether to go big on a hi-fallutin' gel seat, but in the absence of any advice or ability to try out, I went for another cheapo seat with a noticeably thinner profile on the grounds that a *change* is as good as an *improvement*.

Pre-Start

Gary the Gerbil smiles for the camera
One of the things that I find hard to grapple with is that you've got a whole normal day before you start your preparation for the ride. So I took youngest swimming (as normal), then we all went out to see her perform in the local Dance School's show, then I came back and had a bit of a lie down, we played with the gerbils a bit, all had dinner, then they went out to a party and I got on with packing my stuff. I didn't leave home until 21:00, which frankly is about the time I'd be looking for a bit of telly before bed on most nights.





This year's pre-departure shot
I got the train up to Waterloo, as before, with the bike and as before I was joined at Woking by another couple heading to the start line. It was their first time at it and they seemed nervous. We didn't talk a huge amount but we shared some concerns about the weather forecast and wished each other well.

I was also astonished and delighted to find I'd gotten some responses to my initial tweets from the train from my old friend John who couldn't ride this year but was spending the weekend in London, with a bike. He offered to see me at the start line - south side of Tower Bridge, an offer I couldn't and wouldn't want to refuse.


Start-Line Selfies
The ride from Waterloo to Tower Bridge was as odd as I expected, although there was more (vehicular) traffic than I was hoping for. I'm not a fan of city riding and at night it's not a favourite thing to do. I have respect (some) for those that do it regularly but even on that short 2.5Mile trip I came across red-light jumpers, and one memorable girl on a bike with no helmet and no lights weaving between the buses and taxis. We don't do ourselves any favours on the roads with this sort of thing, do we?


John at the Start Line




Got to Tower Bridge OK and eventually rendezvoused with John. Fantastic to see him and have a catch up - we last met at Xmas and he's had a lot going on in his life. Even better to have someone to distract me from the pre-start nerves. It's not that it's a particularly sporting or high-tension event, but there's always an element of excitement and no matter how well organised there's always going to be some confusion and chaos at the start line. Having someone to share it with was a big help and I'm very grateful.

First Section

John snuck around the side of the start line as I crossed it at about 23:45 and met me on the main road, so we cycled together north over Tower Bridge and across to Southwick Bridge. We said goodbye there and he headed off to Islington, while we went over the bridge and headed south. 

This whole section was new to the ride this year - last year we started at Clapham Common - and I have to say I thought it was a mixed success. It's a much nicer start and gives a grand sense of occasion - how much closer to central London could you get? and riding over Tower Bridge was an experience, but they don't stop the traffic so (for my part) it was spoilt a bit by dicing with buses heading up to Tower Gateway and beyond. It was also here that I realised what everyone else knows about clips - you'll spend a hell of a lot of time getting your feet into and out of them in traffic, sometimes in a hurry. 

Once we turned South the navigation settled down a bit but the traffic didn't, and the section between Southwick Bridge and Clapham Common was too full of riders and traffic, with each slowing the other down, to be too much fun. At the Common, though, we picked up last year's route which took us off the main road and down some quieter residential areas which provided some relief. By the time we rejoined the bigger roads we'd spread out some and weren't interfering with traffic so much which made the ride much more relaxing. When it's pub chucking out time in London Town this is a blessing. And the cheers - some no doubt heartfelt - from revellers heading home after a good night out was at least entertaining.

There's not a lot to say about the first section beyond this, although I've only really described the first 1/2 of it (to about 10 miles). The second part is through suburbia and is well lit on roads getting quieter as the night progresses. There's a bit of a sting near the end, as the last 3-4 miles are fairly constantly uphill. As with previous events I'm amazed how quickly people start getting off and pushing even at this fairly early stage. There's nothing steep that requires a Granny Gear, but having spent a bit of time recently looking at bike options and gearing I'm beginning to see it's possible for a fairly average person to be persuaded into purchasing something only a fully-enhanced Lance Armstrong could get up a serious hill, so my previous scorn for such sights is abating a bit. Anyway, be that as it may, there ought to be some satisfaction in knowing that by the time the first rest stop is reached at the 20 mile point you've climbed to the highest point on the route and, logically, it's all downhill from here....


The weather had held out so far, but as I put in a 20-minute water, coffee and (why not?) hot dog stop the drizzle started to fall. It was hard to tell the effects at first, because I'm a prolific sweater and it was also quite humid, but my clear specs misted up very quickly on the stop and everything got too damp to use for cleaning. 

Luckily, after only 90 minutes or so riding, I was fairly fresh (as fresh as one can be at 01:30), so instead of sticking it out and getting cold, I cut my losses and pressed on. Plenty of other people had the same idea so we headed out to the second section in a bit of a peloton.

Second Section

The second section's the part of the ride where bits are put between teeth, knuckles are down, and Serious Business is engaged. In theory it's an easy drag without many hills, but in practice it's where England's Green and Pleasant Rolling Countryside starts to show. This year, however, it was totally overshadowed by a nasty accident at the bottom of a hill. I can only speculate on cause, but at the bottom a long descent to a T-junction where we needed to turn right, someone had had a very nasty fall, and when I got there the Ambulance and Police were in attendance. I caught the second half of a 30-minute road closure while they scraped the chap off the road. It's an odd and slightly de-humanising feeling: along with 2-300 other riders, you're feeling sorry for the fellow while at the same time wondering whether they're going to get a move on so we can get riding again. It's not a nice thing. 

It also changed the character of the section completely, because when they re-opened the road it was like a second mass start, and the rest of the section was spent in crowded company with a bunch of riders all trying to re-group with their friends, break free from the masses in a sprint, or just generally remain oblivious to all that's going on around them and act like a rolling road-block. It would be great to say this mass riding represents the best of cycling - common spirit and purpose, all united in a single goal - but as on other rides I've done it's quite the opposite; it seems to bring out the worst in everyone. I did manage to keep my mouth shut and not express these Grumpy Old Man feelings, but it had an effect.

Still, the advantage of this section is that the roads are as quiet as they'll ever get, and meeting traffic in either direction is a rarity and not a hazard. This together with the constant pacing effect of other riders meant progress to the second stop at 35 miles felt fairly rapid. I got there at about 03:10, which was roughly as expected once the stoppage is taken into account.

Last year's ride was saved, for me, at this point by John's bringing out of some pre-made sandwiches.
Second Service Area - Cheese & Marmite Sandwiches can do this to a man...
It's the worst time of the night - it's been dark forever and there's no sign of morning, you're only just over 1/2 way, and fatigue's kicking in. So this year I prepared by making myself some sandwiches to bring, and had the John Ford Memorial Cheese & Marmite Sandwich of Hope washed down with another large gulp of water and some flapjack. I also got chatting to some fellow riders - one chap had just left a group of 4 who'd spent an hour correcting a navigational mistake which saw them get as far as Redhill before finding a friendly taxi-driver to put them back on the right track (that'll count big on the total mileage front but won't help their finish time!), and I had a very fun chat with a lady who'd only agreed to do the ride again to help out her friends who were practicing for the Ride London 100 and, at the time of our meeting, were no-where to be seen somewhere behind her clearly not quite as prepared as they'd thought...

She also said something quite insightful which I'd only unconsciously noticed - the riders this year (although there appeared to be far more of them) seemed more serious, and there was a distinct absence of novelty bikes like we've seen on previous rides. Maybe it was the weather (which, once again, decided to wait until I'd stopped before starting to rain), maybe the start-venue change, but the ride had a more serious character than before.

Third Section

The lady also vocalised what I was feeling, which was that the 3rd section ahead of us is the worst of the night, what with the timing, the fatigue and the fact that there's so many miles still to go. But it was clear that we'd never manage it stood around at a rest stop so I packed up my things and decided better behind me than in front...

In terms of height profile, there's only one half-decent hill on this section and it's reasonably close to the start when one ought to be freshest (for locals: it's the hill heading out of Crawley towards Balcombe past the M23). At that time of day it takes more epic proportions, though, and there were a fair number of walkers. I could tell I was feeling it too, because I hit bottom gear for part of it, and there's no way that hill is less than a 3rd gear climb on a normal day. 

The rest of the section features more of that lovely Rolling English Countryside posh southern poets love to write about; they should try riding it in the pre-dawn dampness of a sunday morning after 40-odd miles of roads before they wax so lyrical is all I want to say, as the constant shifting up and down gears to slog up one slight rise whilst taking maximum advantage of the downslope on the other side gets very waring. Just once I'd like to do a ride that's *actually* flat for a good distance, rather than just appearing to be so on a profile map in relation to everything else on the journey...

Thanks to the 6-7 miles added to the front of the ride, this was also the point in the ride where I started to feel a bit down about progress. Last year, John & I got to the final service area at 04:00 just as it was starting to get light. This time around, I was out on the roads as this happened and it ought to have been joyful to ride into daylight but I couldn't help feeling I was letting the side down by being slow. Rational thought was hard to come by, partly because I knew what was coming ahead of me and wasn't feeling up to the challenge, and partly because it'd become wet enough to warrant removal of my clear glasses which really weren't helping with seeing anything.
Still another 17 miles to go, and fairly knackered

I rolled in to the 3rd Service Area outside Burgess Hill at the 50-mile point at about 04:40 to find a large crowd of people all looking like I felt, and there's some consolation to be taken in shared misery! A cup of hot coffee, a sit-down, a mars-bar, some flapjack and a good long ponder of the world passing me by helped recover my body and spirits somewhat.

Final Section

However, we all knew what was coming either by reputation (for the first-timers) or from bitter experience for those of us who'd done it before. So after a good 1/2 hour break, back onto the bike to join a noticeably slower-moving, more tired group heading onto the final section. I was a bit disconcerted at this point, because I'd worked out the ride distance as 60 miles, meaning we should have had 10 to go, but the marshals were cheerily shouting "Only 17 miles to go!" at us. Time would prove they were right and I was wrong, so serves me right for reading straight-line distances off a Garmin route as definitive, I suppose.

Dawn's joys were dampened by the weather. I'd been hoping for an earlier start, reasoning that if I'd got away at 22:30 I'd arrive at the hill either while it was still dark (and I wouldn't see it), or I'd catch sunrise at the summit. In the event, I could barely see where I was going thanks to the mist and rain so I guess I got part of my wish.

I should probably explain better. The (day) London to Brighton ride is (in)famous for being fairly easy for the first 50 miles, then throwing everyone over a long, steep hill (Ditching Beacon) only 10 miles from the end when you're nice and tired. It's a proper Nemesis of a hill, the highest point of *that* ride, and a genuine excuse for a slow walk and push of the bike up for about 1/2 the riders of that event. 

The Night Ride doesn't go up Ditchling Beacon (it'd be an accident blackspot if the road's aren't closed to other traffic like they are on the day ride), instead it finds another way over the South Downs about 5 miles further west, up a peak called the Devil's Dyke. It's not as high as Ditchling (as I've mentioned: peak altitude for the night ride actually comes at the 20 mile mark, over the North Downs well inside the M25), but it's a lot longer and a lot sneakier, coming in 3 distinct sections with a bit of downhill between each. Last year I knew nothing of this, so put my all into each of them thinking their sub-peaks were the heights. It's not helped by the fact that there's about a mile of descent (about 1/3 of the total so far climbed) between the 2nd and 3rd sections, and the final climb back up to the peak is the steepest bit.

It was nice in the run-up to the hill to find that there were people out already to support; the bell-ringers and shouts of encouragement from the sparsely-spread cars were really appreciated. But they didn't help with my mental state, which (this time around) knew what was coming. As with last year, it was around the 3rd stop that we also started to see the first returners - those for whom a night-ride TO Brighton isn't enough and who are now well into their return journey. I respect and admire these people for their stamina and spirit, but I wish they'd chose a different route back for their effect on my morale.

So I arrived at the hill with legs of lead, a bum on fire, and dripping wet. Not the best mental state to be in. Resigned as I was to my fate, I couldn't get upset with those passing me on the right even though I envied every one of them their legs. For my part, I passed but one rider on the hill, and plenty of walkers. As mentioned, I'd say 50% of day riders walk Ditchling Beacon but either the hill's easier (and I'm making a scene of it) or the riders are hardier on the night ride and the proportion is much lower - no more than 20% of people were pushing up the hill (although plenty stopped for a break at each mini-summit). Some of these look at you - as I would - with pity or envy in their eyes as I huffed, puffed, dribbled and swore my way past them, but most smile and offer words or shouts of encouragement and represent all that is good in people. Thus I reached the bottom of the 3rd climb in no good state, and with my head firmly DOWN to avoid seeing what was ahead of me. I reached bottom gear in the quickest time I've ever managed, and plugged at it. I really, truly, felt I couldn't make it despite being shouted at not only by those walkers I past but also by the riders passing me, and I was making more noise panting for breath than the Flying Scotsman made on it's record-breaking run. But, bit by bit, I got up the hill. I can distinctly remember looking up ahead of me at my lowest point, thinking perhaps to find a spot I could dis-engage feet and dismount, to find I was at least 3/4 of the way up and in sight of the summit, uttering an unprintable stream of self-encouragement and vowing to make it. And I did, and it was glorious. I'll win no prizes for my ascent, not even "most shabby rider to make it" as I'm mediocre in all things, but a funny thing happened to me immediately I recognised I'd made it to the top.

The summit of Devil's Dyke is at the 60-mile marker on the ride, and my GPS tells me I got there at 06:20. Last year's ride was about 60 miles total, and John & I finished at 06:11 after starting at 23:55. So this needs to be the definitive reckoning: I was slower this year than last. But my Strava Trace of the event shows a slightly different picture, as I was faster over the first half of the event and tapering off badly towards the end. This matches my feeling of the event; I was struggling quite hard towards the end and much closer to being out of reserves than I remember feeling last year. Having said that, Strava tells me I was only 39 seconds slower up the hill than last year, which is a surprise; I'd have expected minutes.

It probably also explains my behaviour from the summit on the long, long winding descent to the finish, where waves of relief and emotion kept washing over me, causing the disturbing sight (to anyone close by) of a middle-aged man riding a bike at 20MPH down residential streets whilst intermittently bawling and sobbing uncontrollably. It persisted past the finish line, and accounts for my appearance in the obligatory finish-line selfie:
Bit of a mess at the finish line

Apres-Ride

There was a cracking spirit at the finish line - I've got nothing but respect for the DJ who'd been at it for hours and yet whose encouragement made every last one of the finishers feel great about what they'd done. And there was a surprisingly big turn out - at 06:45 - of people there to wave and cheer. That, too, was appreciated by everyone cycling along Madeira Drive. 

I had a brief chat with a lass heading back to the train station. She'd found it tough going and she'd previously been a sporting rider winning events. Mind you, she admitted she'd done little preparation and was relying on previous experience and fitness to get through it. I could have told her from my 2012 experience that this wouldn't be good enough, but we all learn these lessons the hard way.

Plan A for the post-ride had been to crash out on the beach for an hour or two, perhaps a little snooze to recharge the batteries, and then leisurely ride home. Plan A was toast, and I'm going to blame the weather which was wet and surprisingly windy. So instead I opted for a sit-down at a cafe, a full English, and a re-think. I've never enjoyed a meal more and it disappeared far too quickly. Unfortunately, in my post-bacon daze I'd failed to consider that I was sheltered from the worst of the elements and so I made the decision to try a little ride to Worthing and see how I felt.

So, an hour after finishing the night ride, I saddled up and started to head west. And, as it turned out, straight back into the wind which I'd not noticed had provided a big boost to the final sprint along the seafront towards the finish-line. So while I quite enjoyed the first few miles into wind - smiling and waving and enjoying the disbelieving can't-believe-I've-done-it looks on the faces of the riders still heading towards the finish - I can tell you that in that state a full english breakfast with tea wears off at Shoreham-by-Sea, pretty much going past the airport. Any thoughts of making it further home than that disappeared at that point, and I must have looked a strange sight to those bikers who were just getting out for their sunday constitutionals as I rather slowly made heavy work of a seafront ride to Worthing.

I got the train from there, and ended up sharing a carriage with 3 other riders of the event who'd done it for the first time and were heading back to Portsmouth. I greatly enjoyed sharing the experience and swapping tales with them, and getting a second insight into the event. They hadn't done a BHF ride before but had plenty of experience on other rides, and the tales of organisation and relative enjoyment of the various organisers gave me much to think about. 

After a very long wait at Havant for a connecting train, which tested my abilities to remain conscious, I finally rolled up to my front door just after 10:00. To find a normal common-or-garden Sunday under way; youngest lounging about reading the Beano in her pyjamas, eldest still in bed, and my Dearly Beloved slowly going out of her mind trying to herd the offspring into doing *anything* with the day. I didn't help - I dismounted, discharged the contents of my various pockets and rucksack, disrobed and collapsed in bed for a couple hours longer than I'd planned. I'd like to say that sorted me out, but frankly the rest of the day was a wash-out, for which I'd like to apologise to my long-suffering family.


Thanks

And on that note, it only remains to say thank-you to everyone who's sponsored me, to everyone who's commented or sent their kind words of support, and to my friends and family who once again have put up with my distraction and obsession with preparing for and riding in this event.

The sponsorship page for the ride will remain open for a little longer, so try Clicking Here if you'd like to see it.