Changes between Version 11 and Version 12 of ValidationIntro

Timestamp:

Sep 14, 2011, 2:21:13 PM (13 years ago)

Author:

davea

Comment:

--

ValidationIntro

@@ -21 +21 @@
     * The '''sample_trivial_validator''' accepts all results as valid.
 
-By default, a validator grants credit for valid results using the mechanism described [CreditNew here].
-You can change or disable this using command-line arguments.
+By default, a validator grants credit for valid results using a default mechanism (described [CreditNew here]).
+There are several [CreditAlt alternative ways of granting credit].
 
 === Command-line arguments ===
@@ -32 +32 @@
  [ --one_pass ]::       Make one pass through WU table, then exit
  [ --mod n i ]::        Process only WUs with (id mod n) == i. This option lets you run multiple instances of the validator for increased performance.
- [ --max_granted_credit X ]::   Grant no more than this amount of credit to a result.
+ [ --max_granted_credit X ]::   Grant no more than this amount of credit to a job.
  [ --update_credited_job ]:: For each valid result, create an entry in the credited_job database table.
   This lets you keep track of which user contributed to each WU, even if you use [DbPurge db_purge].
- [ --no_credit ]:: Don't grant credit (use this if you grant credit via trickle messages).
+ [ --no_credit ]:: Don't grant credit (use this if you [CreditAlt grant credit via trickle messages]).
  [ --credit_from_runtime ]:: Grant credit proportional to (runtime * CPU FLOPS).
   Use this if:
@@ -41 +41 @@
  * the app's jobs do different amounts of computation on different hosts,
    e.g. if they exit after a fixed amount of time.
+ * [CreditAlt Details].