Another part of it was that the Flying 200 felt awful. Really bad. I did it on 92", which didn't quite feel right, but mostly because I just wasn't focussed on it - and so my jump, my form, and my ability to push the whole way just weren't there. So I didn't feel I was going to get much of a training effect out of the evening. Because, well, I'm a sprinter; there's no point going out there at 60%. And as Craig Colduck said:
If you don't make the target times or loads on the first effort or set, you warm down and go home. You aren't fresh enough to train at a level that will make you improve.
I didn't check my time after the Flying 200, but I knew in myself that I wasn't on. My goal had been a sub-13 second. I felt like I'd just scraped in a sub-30 second!
Interestingly, I was right in a technical sense - I hadn't made my target. It may be argued that aiming for a 0.4second PB shouldn't be an initial training target in this sense, but no need to quibble. It turned out I rode 13.34 seconds - which is precisely (where 'precisely' in this, hand-timed, context means 'within 0.2s or so') what I rode at the come-n-try day 10 weeks or so ago. So I actually qualified to go home on the other half of Craig's advice:
If you do a PB, you warm down and go home.So even if I'd wanted to, I couldn't possibly have stayed!
One interesting thing to note from the stats is that I started my jump for the F200 from ~42.4km/hr, hit the 200m line at about 54.7, hit my top of 57.1 (@131RPM) some 20m later, and then dribbled all the way back down to 54.9 over the next 60m, popped back up to 55.7 and held there for another 60m or so, and then plummeted away after coming out of the bend (in fact, I almost sat up in the straight) to cross the line at about 52.7km/hr. This is all slightly approximate, of course, as I'm inferring from the graph rather than correlating with a GPS plot, but it's probably about right.