Computing the percentage complete depends on re-collating all of the completed stubs and accounting for the distribution of stubs that count against the secondary verification pass, and requires entirely reprocessing several hundreds of megabytes of compressed completion data. It also depends on whether you are attempting to compute the overall percentage complete, or just the percentage of phase 1 or phase 2 of the project.

While the projects were running, the percentage complete for OGR-24 and OGR-25 were available at:

  OGR-24 -- http://stats.distributed.net/projects.php?project_id=24

  OGR-25 -- http://stats.distributed.net/projects.php?project_id=25

Phase 2 for OGR-24 started on 16-May-2004, and was completed on 1-Nov-2004.
Phase 2 of OGR-25 started on 16-May-2004, and was completed on 28-Oct-2008.

OGRNG (ie: OGR-26 and beyond) are expected to on only require one phase, however there will still be "sub-phases".

Although we try to present the OGR progress as just two percentages (one for phase 1 and one for phase 2), it is actually a little more complex.

For OGR-24, there was a phase 1, and then two sub-phases in phase 2:

• Phase 1 (aka "OGR24 classic"): 5-diffs stubs (len <= 70) belong to the OGR contest. Completed!
• Phase 2 (aka "OGRp2-24" sub-phase 1): 4-diffs stubs (the client places the 6th mark at a position > 70). Stub len < 80. Total 1131772 stubs. Completed!
• Phase 2 (aka "OGRp2-24" sub-phase 2): 3-diffs stubs (the client places the 5th mark at a position >= 80). Total 95748 stubs. Completed!

Similarly for OGR-25, there was a phase 1, and then there are nine sub-phases in phase 2.

• Phase 1 (aka "OGR25 classic"): 6-diffs stubs (len <= 70) belong to the OGR contest. Completed!
• Phase 2 (aka "OGRp2-25" sub-phases 1 thru 5): 6-diffs stubs (70 < len <= 95). Extension to the OGR contest. Subdivided into five chunks for manageability:
  • 48979672 6-diffs stubs : 70 < stub-length <= 81 Completed!
  • 42196852 6-diffs stubs : 81 < stub-length <= 86 Completed!
  • 47775232 6-diffs stubs : 86 < stub-length <= 90 Completed!
  • 46417392 6-diffs stubs : 90 < stub-length <= 93 Completed!
  • 36267180 6-diffs stubs : 93 < stub-length <= 95 Completed!
  (Total : 221636328 6-diffs stubs.)
• Phase 2 (aka "OGRp2-25" sub-phases 6 thru 7): 5-diffs stubs (len < 112, the client places the 7th mark at a position > 95). Subdivided into two chunks for manageability:
  • 38361468 5-diffs stubs : 0 < stub-length <= 98 Completed!
  • 38106790 5-diffs stubs : 98 < stub-length <= 111 Completed!
  (Total : 76468258 5-diffs stubs.)
• Phase 2 (aka "OGRp2-25" sub-phase 8): 4-diffs stubs (len < 122, the client places the 6th mark at a position >= 112). Completed!
(Total : 6515212 4-diff stubs.)
• Phase 2 (aka "OGRp2-25" sub-phase 9): 3-diffs stubs (the client places the 5th mark at a position >= 122). Completed!
(Total : 237944 3-diffs stubs.)

The higher-diff stubs overlap with the smaller-diff stubs from later sub-phases, so there is less work (fewer average nodes per stub) left for the later sub-phases. This makes the overall project percentage for Phase 2 (which is measured in stubs not nodes) seem to progress more slowly in the early sub-phases, than the later sub-phases.

Additionally, each stub is distributed at least two times in order to get the necessary validation by two different computers.