...just returned my last DDDT....

Sorry folks - I should have been posting this information. Here was the progress:

Workunits Left to Complete Processing

July 23 - 12:00 UTC: 64228
July 24 -  0:00 UTC: 60509
July 24 - 12:00 UTC: 52634
July 25 -  0:00 UTC: 44836
July 25 - 12:00 UTC: 37890
July 26 -  0:00 UTC: 32763
July 26 - 12:00 UTC: 28280
July 27 -  0:00 UTC: 24385  <- First 'overschedule'
July 27 - 12:00 UTC: 20809
July 28 -  0:00 UTC: 11254
July 28 - 12:00 UTC:  2757 <- Second 'overschedule'
July 29 -  0:00 UTC:   950
July 29 - 12:00 UTC:   308 <- Third and final 'overschedule'

I anticipate that we can release the new version in 24-36 hours from now.

Greetings again,

knreed is in the process of loading up new work on the grid for DDDT. This will be using the 6.06 version of the application. People should start seeing new work available within the next hour.

Thank you for your time and patience during this change.

-Uplinger

Many thanks !

Here is the details (pulled from the beta test)

Single validation is going to work in the following way:

Workunits are loaded into BOINC with a quorum size of 1. This means that 1 replica is created and it will only take 1 successfully run result in order for validation to be attempted on the result.

However, there are a few checks in place:

1) The server maintains a value that serves to inform us of how 'reliable' a given computer is. When a result is assigned to the computer for a workunit with a quorum of 1, then the reliable measurement is checked to make sure that the computer is sufficiently reliable. If it is, then all is good. If it isn't, then the workunit is changed to have a min_quorum of two and a second copy is sent.

2) When validation is attempted, the value for the host is checked again. If the value has fallen below the required level, then the result is marked INCONCLUSIVE and another result is sent.

3) Additionally, during validation, there is a certain random chance that the result will be flagged to be checked again. Any result picked in this case will be marked INCONCLUSIVE until the validation with the additional result occurs. All computers are subject to random checking.

4) We have also added some additional checks within the research apps to detect errant results. Part of this is a short run of the application that computes a known result (this was part of what we ran last week). This short run will be used to help ensure that the computation ran correctly as well as it will be used to determine the appropriate credit to award.