G
GuestThere was a problem with some people getting their projections multiplied by 10. So if you said BYU would throw for 300 yards, it was saved as 3,000.
I went through and with the obvious offenders was able to divide those by 10 and restore them in the database.
You may want to check your predictions and make sure nothing is too crazy in there.
The explanation as to how this happen follows for those of you who are nerds..
As some of you know this summer I updated the prediction game. The reason for it was that I was using two different code bases (one for football and one for basketball). The problem was they were very similar and when I fixed a bug in one, I'd invariably have to fix it in the other, and sometimes I would get distracted and not update one.
So over the summer I consolidated them into one set of code that handles both. There was only one problem with this. The basketball game asks about percentages, which I was storing in the database as whole numbers for accuracy (so 33.8% stored in the database as 338). I was doing this by multiplying the input answer by 10 (the reason is that databases aren't very precise when dealing with decimal places so 33.8 could really be 33.79999999999999 or 33.8000000000001 which makes it tough to deal with anyway...)
Thanks to Sno for noticing this and pointing it out to me this afternoon.
I went through and with the obvious offenders was able to divide those by 10 and restore them in the database.
You may want to check your predictions and make sure nothing is too crazy in there.
The explanation as to how this happen follows for those of you who are nerds..
As some of you know this summer I updated the prediction game. The reason for it was that I was using two different code bases (one for football and one for basketball). The problem was they were very similar and when I fixed a bug in one, I'd invariably have to fix it in the other, and sometimes I would get distracted and not update one.
So over the summer I consolidated them into one set of code that handles both. There was only one problem with this. The basketball game asks about percentages, which I was storing in the database as whole numbers for accuracy (so 33.8% stored in the database as 338). I was doing this by multiplying the input answer by 10 (the reason is that databases aren't very precise when dealing with decimal places so 33.8 could really be 33.79999999999999 or 33.8000000000001 which makes it tough to deal with anyway...)
Thanks to Sno for noticing this and pointing it out to me this afternoon.

