Quote:
Originally Posted by Ed Law
Ether,
Your republished numbers are very close to mine now. I also used double precision. My implementation is done in Excel using VBA. I do not actually put the 2053 X 2053 matrix inside the spreadsheet so it works in older version. The program read in the match results and assemble the matrix. It is just stored in the memory for the calculation. Solving the equations inside Excel using VBA is probably slower than outside in another app. Tom Line mentioned they are solving the equations using Excel built-in solver. I am curious what algorithm they use and how fast that would be.
How come you only have 2052 teams? I have 2053 teams in 2011.
|
Column " B" of the "Worldrank" tab of your
Team_2834 2011_Scouting_Database Championship v4b.xls spreadsheet has
has teams
1366 and
2627 which were not in
Phil's file. Phil's file has team
1702 which is not in your spreadsheet. So we still aren't using the same data. Do you have (or could you quickly generate) a single file in XLS, CSV, fixed-field, or whitespace-delimited format which has all the data you used
1?
Matrix factor time for double-precision 2052x2052 matrix elements with double-precision intermediate calculations (
instead of Intel extended precision 80-bit) is 12.4 seconds.
I didn't know that the Solver could be used by a macro to operate on a matrix in memory. I'll have to look into that. Even so, I'm surprised that they let you solve a 2052x2052 matrix using Solver. The Solver in Excel is a limited (but still quite capable) version of a commercial product from a third party named
Frontline.
1 with fields red1, red2, red3, blue1, blue2, blue3, red_alliance_score, blue_alliance_ score