distributed.net Faq-O-Matic : Project: OGR (Optimal Golomb Rulers) : What is the total number of stubs/nodes in each OGR contest? | |
OGR-28Stubspace 1: 115,676 stubsStubspace 2: 5,823,649 stubs Stubspace 3: 518,152,118 stubs
OGR-27OGR-27.1 -- 2,526 stubs (3-diff)OGR-27.2 -- 179,120 stubs (4-diff) OGR-27.3 -- 6,457,815 stubs (5-diff) OGR-27.4 -- 295,982,125 stubs (6-diff) 27.1: Min: 87.61 Gnodes (27/61-2-62) Max: 706.83 Gnodes (27/2-18-104) Avg: 391.80 Gnodes (in 2526 stubs) Tot: 989,678.00 Gnodes 27.2: Min: 30.61 Gnodes (27/61-11-51-3) Max: 747.49 Gnodes (27/2-18-24-82) Avg: 219.90 Gnodes (in 179120 stubs) Tot: 39,388,136.47 Gnodes 27.3: Min: 1.91 Gnodes (27/61-11-51-2-1) Max: 884.72 Gnodes (27/2-16-17-21-60) Avg: 123.88 Gnodes (in 6457815 stubs) Tot: 800,008,962.55 Gnodes 27.4: Min: 0.00 Gnodes (27/61-4-7-2-1-5) Max: 1566.62 Gnodes (27/1-4-18-12-20-39) Avg: 73.86 Gnodes (in 295982125 stubs) Tot: 21,862,526,768.38 Gnodes Total for OGR-27: 22,701,923,867 Gnodes 56,754,810 seconds (656.88 days) for one pass (at a common rate near the end of the project of 400Gn/sec)
OGR-26ogrng-26.1 -- 714 stubsogrng-26.2 -- 44,866 stubs ogrng-26.3 -- 9,921,953 stubs 26.1: Min: 128.14 Gnodes (26/12-55-37) Max: 312.57 Gnodes (26/2-18-84) Avg: 222.89 Gnodes (in 714 stubs) 26.2: Min: 16.78 Gnodes (26/12-55-36-1) Max: 446.99 Gnodes (26/2-18-24-53) Avg: 159.36 Gnodes (in 44,866 stubs) 26.3: Min: 0.12 Gnodes (26/4-7-2-1-5) Max: 553.95 Gnodes (26/1-6-13-4-18) Avg: 53.70 Gnodes (in 9,921,953 stubs)
OGR-25Stubspace 1: 48,979,672 stubsStubspace 2: 42,196,852 stubs Stubspace 3: 47,775,232 stubs Stubspace 4: 46,417,392 stubs Stubspace 5: 36,267,180 stubs Stubspace 6: 38,361,468 stubs Stubspace 7: 38,106,790 stubs Stubspace 8: 6,515,212 stubs Stubspace 9: 237,944 stubs
OGR-24For OGR-24 phase 1, there are approximately 6,000,000 "5-stubs" per pass (two complete passes are done for verification purposes). Each of these stubs has a variable number of nodes, ranging from fewer than 900,000 nodes to more than 150,000,000,000 nodes per stub.Keep in mind that the number of nodes within a given stub has absolutely no relation to the "shortness" or "optimality" of the ruler that the project is looking for. The node count merely represents the number of golomb ruler possibilities that were checked within that stub's prefix, of which any single one has a chance of being a golomb ruler that is more optimal than what is currently known.
You may want to also check out:
Tell me about the total project percentage complete and Phase 1 and Phase 2 for OGR-24/25?
|
|
© Copyright distributed.net 1997-2013 - All rights reserved