Training Log Archive: slow-twitchIn the 1 days ending Dec 18, 2023: |
| « | » |
| » now | ||||
| Mo |
Monday Dec 18, 2023 #
Note
WARNING: PHILOSOPHICAL MUSING AHEAD
While I had been staying at home (mostly just precautionary) with illness since Tuesday night, I had time to reflect a bit on the sprint weekend, especially as the mistakes I was making weren't really typical for me - more about race management than navigation or whatever:
* missing an entire loop of one of the head-to-head races
* missing a control in the 'standard' sprint
* starting on the wrong part of the course after the map flip in the 'standard' sprint, then almost reading the wrong leg several more times
I still think course/map presentation contributed to the first and last of those but I think another element was inexperience running with SIAC (only other time was with the Lonely Mountain and STB sprints way back just Before Covid Epidemic [as we know, any date BCE is back in the murky distant past]). I suspect even in a sprint race, with normal punching I'm probably making more use of the micropauses while punching than I consciously realise, to take in little bits of information. Even if it's only enough to reinforce what control number I'm up to that might have prevented these process errors. More consciously I was aware at the time that I certainly wasn't using the control descriptions as much as I normally would. Maybe a bullshit theory, but something to be aware of if I ever decide that yes I do deserve a SIAC of my own. And maybe also something to consider when thinking about the high MP rate of some of our younger top runners who may have pretty much only run with 'touch free'. How to make sure they have an ingrained process of tracking where they are in the control sequence, expected control code etc?
I'm pretty happy with how everything else went - even running speed (when I'm sensible about who to compare myself against)
While I had been staying at home (mostly just precautionary) with illness since Tuesday night, I had time to reflect a bit on the sprint weekend, especially as the mistakes I was making weren't really typical for me - more about race management than navigation or whatever:
* missing an entire loop of one of the head-to-head races
* missing a control in the 'standard' sprint
* starting on the wrong part of the course after the map flip in the 'standard' sprint, then almost reading the wrong leg several more times
I still think course/map presentation contributed to the first and last of those but I think another element was inexperience running with SIAC (only other time was with the Lonely Mountain and STB sprints way back just Before Covid Epidemic [as we know, any date BCE is back in the murky distant past]). I suspect even in a sprint race, with normal punching I'm probably making more use of the micropauses while punching than I consciously realise, to take in little bits of information. Even if it's only enough to reinforce what control number I'm up to that might have prevented these process errors. More consciously I was aware at the time that I certainly wasn't using the control descriptions as much as I normally would. Maybe a bullshit theory, but something to be aware of if I ever decide that yes I do deserve a SIAC of my own. And maybe also something to consider when thinking about the high MP rate of some of our younger top runners who may have pretty much only run with 'touch free'. How to make sure they have an ingrained process of tracking where they are in the control sequence, expected control code etc?
I'm pretty happy with how everything else went - even running speed (when I'm sensible about who to compare myself against)