Talk:Review Algorithm/1.4.4/@comment-9088222-20130504190243/@comment-9088222-20130506000644

I will try to look into it. Most of the time that I thought the excel sheet was wrong though, I checked again and it was because either I had someone new on my crew(thus it would go through the first pass), I put less than 20% time allocation on a >=0.9 design area, or I messed up the technical expertise modifer by accident. Although, I noticed that some scores were not consistent also with my most recent career.

I will see what I can find out though :)

Edit: So far I have found that my b value in the spreadsheet is not limited to 0.2*Top Score(Although it it near impossible to even reach this limit anyway). I will try to correct that and check for any further mistakes.

Edit 2: I fixed the b value problem. If games rated was >=3, I was checking the values with 0.1*(Top Score + 2 * Y) instead of 0.1*(Top Score + previous b value * Y). Looking for more problems.

Edit 3: I couldn't find any other errors with the code of the document. I have made quite a few changes though(added a few more rows needing input to make the calculated q require no assumptions, added an MMO? row, and made it look a bit better. I will continue looking to try to find mistakes(if anyone else finds any, please let me know!).