[Debian Wiki] Update of "BOINC/ServerGuide" by SteffenMoeller

[Debian Wiki]

Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Debian Wiki" for change notification.

The "BOINC/ServerGuide" page has been changed by SteffenMoeller:
http://wiki.debian.org/BOINC/ServerGuide?action=diff&rev1=95&rev2=96

Comment:
Worked on the results section.

  
  === Access on result files ===
  
- The previously described output template describes what files are expected to be created. Those are shipped back and can then be prepared for subsequent scrutiny. This is explained neatly on http://boinc.berkeley.edu/trac/wiki/AssimilateIntro . For projects that have only results that are successfully validated and that have only one file per workunit, the action to be performed is basically "none". Well, One moves the right file of the many (for complicated projects) into some result area that is then archived. For our purpose, the assimilator could just be "mv", the file mover. But there is also some special communciation with the server, so 
+ The previously described output template describes what files are expected to be created. Those are shipped back and can then be prepared for subsequent scrutiny. This is explained neatly on http://boinc.berkeley.edu/trac/wiki/AssimilateIntro . For projects that have only results that are successfully validated and that have only one file per workunit, the action to be performed is basically "none". Well, One moves the right file of the many (for complicated projects) into some result area that is then archived. For our purpose, the assimilator could just be "mv", the file mover. But there is also some special communication with the server, so one takes the ''sample_assimilator'', which gets the files from their original location {{{
- 
- Result files are at {{{
  $ find $installroot/$fileprojectname/upload/
  upload/
  upload/ba
@@ -367, +365 @@

  $ cat upload/ba/test_0_0 
  TEST STRING
  }}}
- 
+ into a new directory. From the upload directory they will otherwise be removed by the file_deleter daemon. With some deeper insights one can decide to do additional things. To mind come to ring a bell for exceptionally nice results, or to immediately remove a result rather than copying it when it is too bad to be true. The sample_assimilator names the files after their workunit name, basically to bring relief to the programmer to think about a unique namespace. Again, one specifies a daemon section. In complete analogy to the verification: {{{
+ $ /usr/lib/boinc-server/bin/sample_assimilator --app upper_case --one_pass -d 4
+ 2011-08-10 02:43:07.3138  Starting
+ query: select * from app where name='upper_case'
+ query: select * from workunit where appid=11 and assimilate_state=1  limit 1000
+ 2011-08-10 02:43:07.3234 [debug] [test] assimilating WU 1; state=1
+ query: select * from result where workunitid=1
+ query: update workunit set assimilate_state=2, transition_time=1312936987 where id=1
+ query: COMMIT
+ 2011-08-10 02:43:07.3502  Assimilated 1 workunits.
+ }}}
+ The entry for the config.xml is {{{
+     <daemon>
+       <cmd>
+          sample_assimilator --app upper_case --sleep_interval 610 -d 3     
+       </cmd>
+     </daemon>
+ }}}
+ and the completed workunits are then found in {{{
+ $ find sample_results -type f
+ sample_results/test
+ }}}
+ and indeed {{{
+ $ cat sample_results/test 
+ TEST STRING
+ }}}
+ where "test" is indeed the name of the workunit as can be seen in the table above. Please make better workunit names than shown here. Those should have a meaning of some sort. Files in here will not be touched by the system since the workunit will be completed. Anyway - make backups.
  
  == Add your own application ==