It's not my fault. . . the machine ate the project

[LuvToGame]

Hi,

After a rocky start with some marginal pc equipment that continually returned EUE's, lost wifi connections to the network, and in various other ways failed to complete the assigned projects. I'm worried that I might have fallen under the >=80% requirement for bonus point collection--I know the shame . Anyway, is there a way for a donor to check his status at any one moment in time? Furthermore, it would be of great benefit to be able to see the jobs that have been--or havent' been--submitted to the servers over the course of several weeks? I understand that it is possible to track projects under third party programs; however, those apps don't run under v7 as I understand it. And while everyone (the machines) are behaving I really just don't want to rock the boat so to speak by switch to another client right now.

So basically, where can I check my stats in some detail beyond just the sum total of all submissions and points?

Thanks for the help and suggestions,

bpcouncil

[P5-133XL]

At this point there isn't a good way. With v7 you can get some information such as what WU's were completed successfully or failed but that just gives very limited tracking data. Eventually, there will be better 3rd party tools but one must give the significant developers time for their v6 applications don't port well at all so they have to start from scratch.

[bruce]

V6 reuses the 10 positions in the local queue, so it's possible to recover what happened to the last 9 WUs. V7 does not keep a history at all. Of course if you've still got log files, you can search through them either manually or with the help of some software. At least one 3rd party developer has been working on a log-file-parsing-program which is not ready to release, but you're welcome to try it. (Stanford recommends against writing code that parses the logs since they may make changes at any time that break that code. Instead, they have provided a stable interface that will continue to be supported but that requires some major changes from the code that 3rd parties have developed for V6 and earlier.)

The Stanford website used to keep a history, too, but supporting it forced the servers to spend a huge amount of time updating the database so it was discontinued.

AFAIK, all of the 3rd party tools for v6 that keep a history do so by watching the client and recording key information when WUs start and finish. If the program isn't running while FAH is running, data cannot be reconstructed.