We will have these presently. The weekly milestones are still being produced from the old stats, and D2OL was never gotten running there. I need to make some adjustments to start extracting them from teamstats code.
The problem is the floating time base, weekly posted milestones must neither miss anyone, nor list them twice. Both can happen when weekly time frames do not match perfectly. Some code will have to be added to separately cache the timeblocks used for each successive weekly milestone.
The D2OL milestone list is running on teamstats, and they look like this:
50 K ... 100 K ... 250 K ... 500 K ... 1 M ... etc.
The first milestone was set from Shaktai's original D2OL benchmarks, normalized to a G4 350 crunching at least a month to reach it.
Any comments? Have I done anyone a great injustice?
The problem is the floating time base, weekly posted milestones must neither miss anyone, nor list them twice. Both can happen when weekly time frames do not match perfectly. Some code will have to be added to separately cache the timeblocks used for each successive weekly milestone.
The D2OL milestone list is running on teamstats, and they look like this:
50 K ... 100 K ... 250 K ... 500 K ... 1 M ... etc.
The first milestone was set from Shaktai's original D2OL benchmarks, normalized to a G4 350 crunching at least a month to reach it.
Any comments? Have I done anyone a great injustice?