Sage said:
ahh, okay. Actually, I'm planning on just having a few systems that fit into "ancient" "low-end" "mid-range" "high-end" and "workstation" categories. And I'm going to be testing just "graphics cards" like you would buy out of the box. I plan on trying to get every card (not brand, of course) into the database. It's a mighty-big task, but I think it will be well-worth it.
of course, resolution and AA/AF would also be considered "dimensions" yes? Also, there is the issue of driver versions... well, I have given it some thought and I think I'll only have one driver version posted. I'll do tests and keep records of other driver versions, but only use the ones that give the best scores and pass my quality requirements (no cheats!
) and then show which ones you're seeing the results for.
oh, and no I haven't taken probability. I haven't even graduated high school
much less taken any college.... and probably never will graduate
That'd probably work pretty well just segmenting the different systems into different age catagories. As far as demensionality goes, it's really up to you how detailed you want it to be. A really simple set of dimensions could be:
1) Computer Type (Ancient, Low-end, mid-range, High-end, workstation)
2) Video Card (9700pro, ti4600, etc)
3) Resolution (etc)
4) Quality Settings (High, medium, Llow)
5) Benchmark (3DMark03, Quake3, etc)
So in this case you might be able to get by with 5 dimensions. This doesn't tell you a lot about how a card plays with AA and with Anisotropic filtering though, so you could split up Quality Settings into AA, Texture Filtering, and any other attributes you may want (perhaps texture compression or something). You could also break up videocard into the GPU, the GPU speed, the video memory speed, etc.
I decided to go for a more intimate look at the data and ended up with 14 attributes:
CPU Type (PIII, PIV, Athlon, etc)
CPU Speed (in Mhz)
RAM Speed (in MB/s)
Chipset (nForce2, i850E, etc)
GPU Type (NV30, R300, etc)
GPU Speed (in MHz)
VRAM Speed (in MB/s)
Driver (Cat4.6, etc)
Resolution (1024x768, etc)
AA (2x, 4x, etc)
Aniso (2x, 4x, etc)
Filtering (Bi, bri, tri, etc)
Map (Antalus, Cathedral, etc)
Benchmark (Quake3, SS:SE, etc)
Note that a number of these could probably be combined. There isn't much reason for having map and benchmark seperate (except that in some cases I have the same game listed under two benchmarks, UT2003_Botmatch and UT2003_Flyby for example).
With this many attributes, there are a *lot* of possible combinations of hardware and software to test.
Btw, it's not a big deal that you arn't out of highschool. I did a lot of raytracing back then, you have more free time now than you'll probably have again for a long time, so make good use of it!
If you are interested in picking up some basic statistics, find a copy of "The Basic Practice of Statistics" by David S. Moore. It's non-calculus based, so if you haven't had calc yet it's not too big of a deal. You'll want to understand the binomial theorem, and the concepts behind statistical significance and how you find it. This way you can let people know if the results you get are meaningful.
Nite_Hawk