Changes between Version 4 and Version 5 of ValidationIntro


Ignore:
Timestamp:
Apr 15, 2010, 9:42:41 AM (14 years ago)
Author:
davea
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • ValidationIntro

    v4 v5  
    11= Validation =
    22
    3 In BOINC, the process of validation does two things:
    4 
    5     * it compares redundant results and decides which ones are to be considered correct;
    6     * it decides how much credit to grant to each correct result.
     3In BOINC, a '''validator''' is a program that decides whether results are correct.
    74
    85A 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].
     
    2219A validator (either standard or custom) has the following command-line arguments:
    2320
    24  -app appname::         Name of the application
    25  [ -one_pass_N_WU N ]::         Validate at most N WUs, then exit
    26  [ -one_pass ]::        Make one pass through WU table, then exit
    27  [ -mod n i ]::         Process only WUs with (id mod n) == i. This option lets you run multiple instances of the validator for increased performance.
    28  [ -max_claimed_credit X ]::    If a result claims more credit than this, mark it as invalid.
    29  [ -max_granted_credit X ]::    Grant no more than this amount of credit to a result.
    30  [ -grant_claimed_credit ]::    If set, grant the claimed credit, regardless of what other results for this workunit claimed. This is useful for projects where different instances of the same job can do much different amounts of work.
    31  [ -credit_from_wu ]::  If set, credit is specified by the <credit> element in the WU.
     21 --app appname::        Name of the application
     22 [ --one_pass_N_WU N ]::        Validate at most N WUs, then exit
     23 [ ---one_pass ]::      Make one pass through WU table, then exit
     24 [ --mod n i ]::        Process only WUs with (id mod n) == i. This option lets you run multiple instances of the validator for increased performance.
     25 [ --max_claimed_credit X ]::   If a result claims more credit than this, mark it as invalid.
     26 [ --max_granted_credit X ]::   Grant no more than this amount of credit to a result.
     27 [ --grant_claimed_credit ]::   If set, grant the claimed credit, regardless of what other results for this workunit claimed. This is useful for projects where different instances of the same job can do much different amounts of work.
     28 [ --credit_from_wu ]::  If set, credit is specified by the <credit> element in the WU.
    3229This is needed only with the BOINC-supplied validators.
    33  [ -update_credited_job ]:: For each valid result, create an entry in the credited_job database table.
     30 [ --update_credited_job ]:: For each valid result, create an entry in the credited_job database table.
    3431This lets you keep track of which user contributed to each WU, even if you use [DbPurge db_purge].