Changes between Version 1 and Version 2 of ValidationIntro

Timestamp:

Apr 24, 2007, 11:06:41 AM (18 years ago)

Author:

KSMarksPsych

Comment:

Updated links to point to wiki pages. HomogeneousRedundancy needs to be created.

ValidationIntro

@@ -6 +6 @@
     * it decides how much credit to grant to each correct result. 
 
-A validator is a daemon program. You must supply a validator for each application in your project, and include it in the <daemons> section of your [http://boinc.berkeley.edu/configuration.php project configuration file].
+A validator is a daemon program. You must supply a validator for each application in your project, and include it in the <daemons> section of your [ProjectConfigFile project configuration file].
 
 Depending on various factors, you may be able to use a standard validator that comes with BOINC, or you may have to develop a custom validator.
 
-    * If your application generates exactly matching results (either because it does no floating-point arithmetic, or because you use [http://boinc.berkeley.edu/homogeneous_redundancy.php homogeneous redundancy]) then you can use the 'sample bitwise validator' (see below).
+    * If your application generates exactly matching results (either because it does no floating-point arithmetic, or because you use [HomogeneousRedundancy homogeneous redundancy]) then you can use the 'sample bitwise validator' (see below).
     * If you are using BOINC for 'desktop grid' computing (i.e. you trust all the participating hosts) then you can use the 'sample trivial validator' (see below).
     * Otherwise, you'll need to develop a custom validator for your application. BOINC supplies a [ValidationSimple simple validator framework] in which you plug in a few short application-specific functions. This is sufficient for most projects. If you need more control over the validation process, you can use BOINC's [ValidationLowLevel low-level validator framework].