Changes between Version 4 and Version 5 of ValidationSummary
- Timestamp:
- 06/10/08 09:33:32 (1 year ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
ValidationSummary
v4 v5 1 1 = Validation, credit, and replication = 2 2 3 A computational result consists of:3 The execution of a job produces: 4 4 5 * The result itself (the output files)5 * The output files; 6 6 * The amount of CPU time used; this may be used to determine how much credit to grant for the result. 7 7 8 In general, neither of these can be trusted :8 In general, neither of these can be trusted, because: 9 9 10 * Some hosts have hardware problems (consistent or sporadic) that cause errors (usually in floating-point computation).11 * Some volunteers may maliciously return wrong results; they may even reverse-engineer your application, deciphering and defeating any sort of internal validation mechanism you might include in it.10 * Some hosts have consistent or sporadic hardware problems, typically causing errors in floating-point computation. 11 * Some volunteers may maliciously return wrong results; they may even reverse-engineer your application, deciphering and defeating any internal validation mechanism it might contain. 12 12 * Some volunteers may return correct results but falsify the CPU time. 13 13 14 14 BOINC offers several mechanisms for validating results and credit. 15 15 However, there is no "one size fits all" solution. 16 The choice depends on your requirements, 17 and on the nature of your applications 16 The choice depends on your requirements, and on the nature of your applications 18 17 (you can use different mechanisms for different applications). 19 18 22 21 * A "validator", which decides whether results are correct; 23 22 * An "assimilator", which handles validated results 24 25 PICTURE: different validator/assim for different apps26 23 27 24 BOINC provides examples of each of these,
