Also, if you were shipped a "beta" unit, under the advanced methods, those have to be "post-beta" inspected, to make sure that the code is correct, and works likes it's supposed to.
The point totals are higher, but there is a built-in delay, while the completed workunits are tested and compared.
After all, it's not the "amount" of work that is the most important to Stanford, but the "quality" of work. If the work units they ship out are rock solid, that's that much less manual intervention they have to do, and a lot less work in documentation.
Again, the log is the only way we can tell what might possibly have happened.
I don't think there's a way to get the beta-core (QMD) stuff through the standard configuration - I think you have to add the command-line flag by hand, meaning that most folks here probably aren't set up for it. Probably for a reason - they're not kidding about the system requirements for these things. I have a QMD unit going now, and it's chewing up almost 330MB of memory all by itself.