Sorry guys, I should have replied to this a long time ago. Got distracted and didn't register.
Welcome to our stats engine, you are in good company with a lot of other great teams.
Chew, the MHz rating is an estimation based on average weekly crunch rate. The rate is normalized to my own G4 350, and will be wrong for many processors. Processors with lower power-per-MHz (604, G3, PI/PII/P4, K5/K6) will estimate below actual MHz. New processors with higher power-per-MHz will estimate too high (G5, AthlonXP, Opteron, Athlon64). System architecture will also play a role. There is no easy way to fix this, so use it as a ballpark estimate.
Future Shock, what did you mean about the page still needing cleanup around the edges? If you mean HTML, the page code has been arranged to render readably in all browsers. It's incredibly hard to make it render perfectly in all browsers, I spent many hours trying. Rather than declare a preferred browser and put up harrassing dialogs to get others to switch, we went with acceptable rendering for everyone. Probably a good thing, the preferred browser would have been my own iCab, which most people have never heard of.
Anyone trying to access the stats over the past week may have found outdated data. We had a HD crash last weekend, the stats database was affected. After looking it over, I decided to do a more general cleanup of the data rather than a quick fix. There was a lot of duplicate data accumulated (momentary glitches on the project-server side usually cause this), the DB size had been driven above 9 GB. This slows processing and web access, so I reset nearly all teams (50+) to a few months back for corrected processing. It took a few days for the server to catch back up to the present, but it was well worth it - DB size fell to 7.5 GB.
If data repairs are in progress, you can spot it by checking the time reference for that page. Check the bottom of the colored QuickStats bar, it gives the origin time "time ref" for the data presented. If the time reference gets "stuck" for a few days, please email us or post in our forum. The stats engine can repair most types of data problems on it's own, but some things require manual attention - such as D2OL making changes to their page HTML.
While I didn't get back here right away, we did get a matching thread up for you guys. Feel free to drop in and give us a bad time ... er, say hello. We've found that reasonable cross-team taunting has a nice effect on member activity and production. BTW, congratulations on your recent production, you're really moving along there.