The Bar Code

Monday:
Purpose:  tapering, easy
Distance:  12.8 km
Time:  74' 53"
Rate:  5' 51"
Recovery: river as usual
Weather:  sunny, temp 22 degrees, humidity 22%, wind  west 20 kmph

Tuesday:
Purpose: tapering
Running distance:  nil
Bike riding:  about 25 kms
Recovery:  10 minutes in river
Weather:  sunny, temp 23 degrees, humidity 20%, wind west 10 kmph

Week:  12.8 km,  Jan & Year:  49.95 km

Very easy running on Monday after a no run Sunday. Just a little slow to get moving, but all Ok.
Very cool morning today to ride to work, taking in wind chill, about 5 degrees. But the wind dropped during the morning to a nice sunny day, so I rode home at lunch time via the river, and rode back afterwards. A good day during tapering week, and may be something I should do more often just to get a bit more cross training done.
Along with the 10 minutes in the river, a short gym session. Nothing too much.
For those interested in the bar code results system that the Parkrun uses, it's results system not a timing system. A stop watch is still needed to get the time although the downloading of the times are via a USB stick. That part is straightforward.
It's the other parts as far as a monthly handicap is concerned that may make it unsuitable. Questions raised so far include competitors changing events, the handicap nature of our races, loss of bar code during the event, soggy sweaty bar codes not laminated, will the system be compatible with existing club software, can a result be known within 15-30 minutes of the finish to allow for presentations, still have to have starters/timekeepers for each three events, still need a separate bar code swiper for each event.
Not sure it will work on a handicap system and given the off road nature of our events, how do we keep track of the number of competitors. It's easy for the Parkrun event, one race, same course, no bar code, no result, no winner's presentation, no medals, no points, no yearly awards.