Normal service is now resumed - apologies for any inconvenience caused
For those of you who have ever written code before, you will recognise this phenomenon: I couldn't resist looking at the code when I got home yesterday evening. I had a hunch the problem was dealing with the slightly crazy way the CTC sometimes numbers events (they skip event numbers sometimes for no obvious reason and of course the code breaks because it expects some kind of logical progression). This is made more complex by McNally happening in February and "stealing" March's event number. I couldn't quite get a fix working last night and went to bed. I awoke with the answer in my head. It is amazing how often coding issues are fixed while you are asleep. The brain is an amazing thing (sometimes!).
Anyway, this is working for now and the January scores are back where they should be, instead of being inflated because the tool thought we were looking at the McNally challenge.
A lot of this will need to be rewritten when the CTC switches to their new site. Hopefully it won't be too difficult.
Back to work for me now....yes I know it's a Sunday
