Changes between Version 5 and Version 6 of RemoteJob
- Timestamp:
- Sep 9, 2010, 9:23:02 AM (14 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
RemoteJob
v5 v6 6 6 from a convenient command-line interface. 7 7 8 In the following, we will use the ''scientist'' term to denote the individual who submits and administers the workunits on their workstation through the RBoinc 'client tools'. RBoinc client tools are not to be confused with BOINC clients (i.e. the slaves of the distributed computing architecture); for utmost clarity, we shall prefer the term ''scientist'' and ''scientist workstation'' to indicate the user of the RBoinc client and their machine. 8 In the following, we will use the ''scientist'' term 9 to denote the individual who submits and administers the workunits 10 on their workstation through the RBoinc 'client tools'. 11 RBoinc client tools are not to be confused with BOINC clients 12 (i.e. the slaves of the distributed computing architecture); 13 for utmost clarity, we shall prefer the term ''scientist'' and ''scientist workstation'' 14 to indicate the user of the RBoinc client and their machine. 9 15 10 16 The system (Perl-based) is in boinc/rboinc/. … … 42 48 == Annotating the WU template files == 43 49 44 Workunit template files should be marked as RBoinc-enabled at the top. This marks the template as RBoinc-enabled and thus ''scientist-visible'' as an application. This is achieved prepending the following tag to the relevant workunit template: 50 Workunit template files should be marked as RBoinc-enabled at the top. 51 This marks the template as RBoinc-enabled 52 and thus ''scientist-visible'' as an application. 53 This is achieved prepending the following tag 54 to the relevant workunit template: 45 55 46 56 {{{ … … 49 59 }}} 50 60 51 The ''application'' attribute will be the user-visible name of the application (which may or may not coincide with BOINC application names). The scientist will identify this template through the {{{-app }}} command line switch. 61 The ''application'' attribute will be the user-visible name of the application 62 (which may or may not coincide with BOINC application names). 63 The scientist will identify this template 64 through the {{{-app }}} command line switch. 52 65 53 66 54 Additionally, input files in the workunit template are augmented with RBoinc-related settings. In the WU template, each {{{file_ref}}} element should have a child ''rboinc'' element as follows: 67 Additionally, input files in the workunit template are augmented with RBoinc-related settings. 68 In the WU template, each {{{file_ref}}} element should have a child ''rboinc'' element as follows: 55 69 56 70 {{{ … … 67 81 }}} 68 82 69 The ''parameter_name'' attribute is the command line parameter that will be required by the ''boinc_submit'' command for that file. The argument passed by the scientist on the command line to that parameter will be interpreted as a local file, transferred to the BOINC server, and associated to the given BOINC-handled file (in this case, number 3, with BOINC open name "input.vel"). 83 The ''parameter_name'' attribute is the command line parameter 84 that will be required by the ''boinc_submit'' command for that file. 85 The argument passed by the scientist 86 on the command line to that parameter 87 will be interpreted as a local file, 88 transferred to the BOINC server, 89 and associated to the given BOINC-handled file 90 (in this case, number 3, with BOINC open name "input.vel"). 70 91 71 The ''parameter_description'' is a descriptive text returned by the command line client when the scientist requests help for the attributes supported by the given application. 92 The ''parameter_description'' is a descriptive text 93 returned by the command line client 94 when the scientist requests help for the attributes 95 supported by the given application. 72 96 73 The optional ''optional'' flag specifies whether supplying the given file upon submission is mandatory or not. If not, it will be replaced by a (server-supplied) default file. 97 The optional ''optional'' flag specifies 98 whether supplying the given file upon submission is mandatory or not. 99 If not, it will be replaced by a (server-supplied) default file. 74 100 75 101 … … 77 103 == Annotating the result template files == 78 104 79 Results template files are annotated with RBoinc-specific tags which identify which results should be transferred back to the scientist's workstation. The same tags can be used to build output-input ''chains'', i.e. to automatically submit new workunits as continuations of successfully-completed ones. 105 Results template files are annotated with RBoinc-specific tags 106 which identify which results should be transferred back to the scientist's workstation. 107 The same tags can be used to build output-input ''chains'', 108 i.e. to automatically submit new workunits 109 as continuations of successfully-completed ones. 80 110 81 111 The syntax for the results template is as follows: … … 94 124 }}} 95 125 96 The optional ''chain'' attribute indicates that, upon successful WU completion, that output file should be used as a third input file for the next step in the chain. The ''aliases'' attribute (currently unimplemented) allows automatic renaming upon retrieval. 126 The optional ''chain'' attribute indicates that, 127 upon successful WU completion, 128 that output file should be used as a third input file 129 for the next step in the chain. 130 The ''aliases'' attribute (currently unimplemented) 131 allows automatic renaming upon retrieval. 97 132 98 133 For details on the chaining mechanism, please see the paper T. Giorgino, M. J. Harvey and G. De Fabritiis, ''Distributed computing as a virtual supercomputer: Tools to run and manage large-scale BOINC simulations'', Comp. Phys. Commun. 181, 1402 (2010). [[http://boinc.berkeley.edu/rboinc.pdf pdf]]
