There has been was a few issues with the FF1GP points.
The 1st was Jaime Alguersuari was missing his 13th place finish. I must have been looking at the girls in the pit lane when I was recording the results. That one was fixed within 10 mins of the results going live. That was about Monday at around 17:00 Thanks to the users who emailed me very quickly to tell me about this mistake.
The 2nd problem is related to your 2nd driver in your team, and if you correctly predicted a DNF for that driver. It seems you are missing 4 vital points.
Update 20:36 16 Match 2010
Right, I’ve identified the problem and checked a few more bits of code. If you want the technical bits on what went wrong, you can read a bit more below.
All the results have been updated, and anyone who predicted their 2nd driver in their team to not finish, like any of the Hispania drivers, was not being awarded their DNF points.
A big thanks to the users who did email me about the problems.
However, I’m going to mark these results as provisional for the next few days. just in case there are any other issues. I’m hoping there isn’t, any more issues, and I’ll be updating this blog with any more changes and randomly checking results.
If you think you have an issue with any of the results please email me at admin@ff1gp.com
Finally, I can only apologise for the issues you had this race. The next race in Australia should be a lot smoother affair, and also I hope a better race as well!
Update 08:00 19 Match 2010
Right, there have been no more protests or queries against the FF1GP results. I’m happy with the results, so the Bahrain results are sorted. (Short of any F1 scandal between now and Australia.)
The results have not been changed since the last update.
So what went wrong…
The first I heard was when got a few emails about the problem, it was clear that many FF1GP teams was not getting their DNF points for their drivers. A quick scan at the calculation code quickly revealed where the problem was, but as I have my daytime job as well, I had to leave for work.
Why did the code went wrong, when it’s almost the same code as last years code? Currently I’m migrating 8 years of legacy data to my own to a new code base. The data migration has to be done in phases, and currently about 50% of the database is done. This does mean that some of the old code has to talk to the new database. When I updated the old calculation code I made a slight typo that stopped that 2nd driver from being picked up when the user had predicted a DNF.
The fix was simple, and I wanted to get it done at lunchtime today. However when I got home to apply the fixes, my PC (Which I call Sedna) and Windows 7 which I use for the development was refusing to see my home network.
Now my PC has been having a few problems lately. Back in December the SATA controller on the motherboard packed up, but I was able to get going again with a new controller. In January the onboard network interface died, but this was replaced with an new PCI network card that was Windows 7 64 bit compatible. Something was obviously going wrong here, it looks like the Southbridge on the motherboard was on its way out. At the weekend I had a problem with Windows crashing, but a reboot was fine after that.
Well today, when I most needed a working PC, it failed. Windows 7 was Blue Screen of Deathing all over the place, and Ubuntu as my backup OS was just freezing. Then the hard disk on the IDE controller disappeared, and no swapping of hardware with spare bits made the problems go away. I’m now on a spare PC typing this, and doing hot-fixes on the server to get the FF1GP results up and running.
So sadly I have to say RIP Sedna, and now I need to spend a little money on buying the parts for the new PC aka Sedna 2.0.
I’m off to have a pint, thanks for your patience.
