Changes between Version 15 and Version 16 of RemoteJob


Ignore:
Timestamp:
Feb 3, 2011, 11:04:29 AM (13 years ago)
Author:
tonig
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • RemoteJob

    v15 v16  
    189189== Frequently asked questions ==
    190190
    191 It seems that in BOINC, if you have 2 WU with different input but
    192 having the same name (like "environment.dat"), there will be a problem
     191
     192=== File naming ===
     193
     194In BOINC you can't have 2 WU with different input but
     195with the same name (say, "environment.dat"),
    193196because it will already be in the folder "download" on your
    194197project. So you would have to rename the file or set manually the file
     
    196199overwritten ?
    197200
    198 
    199     That should be handled correctly: file names in download are
     201    No, it will be handled correctly: file names are made
    200202    unique (in fact, equal to the file's md5), even though the
    201203    submitter used the same name for different contents. (It's fairly
     
    204206
    205207
    206 
    207 I understood that with RBoinc, user didn't have to worry about
     208I understood that with RBoinc, user doesn't have to worry about
    208209uploading separately files used and that it was automatic. So is it
    209210important to ensure all input files (for different WUs) will have a
     
    216217
    217218
     219Will there be a problem if a user send simultaneously 1000 jobs by a
     220script (as I saw you used temp folders which were deleted at the end
     221of 1 submission) ?
     222
     223    It's perfectly fine (quite common indeed).
     224
     225=== Retrieve ===
     226
    218227How does the manual retrieve operation affect workunits once a job has
    219 been performed ?
     228been performed?
    220229
    221230    Retrieve will free up space taken on the server by the results of
    222231    the completed WUs. Currently running, scheduled, and future WUs
    223     will be otherwise unaffected (e.g., "step1" may depend on "step0"
     232    will be otherwise unaffected (e.g., ''step1'' may depend on ''step0''
    224233    through the chaining mechanism).
    225234
    226     Note, however, that a "boinc_retrieve -stop ..."  command will
    227     stop the chaining machinery, ie. the generation of new WUs.
     235    Note, however, that a {{{boinc_retrieve -stop ...}}}  command will
     236    stop the chaining machinery, ie. the generation of new WUs. This is
     237    a ''stop'' operation, which should not be confused with a ''retrieve''.
    228238
    229239
     
    237247What is the relationship between RBoinc and the assimilator?
    238248
    239     Let me clarify:
     249    This important point should be clarified:
    240250
    241251      1. a client ("volunteer") computes a WU
     
    252262    The "retrieve" operation is completely independent of the above
    253263    process: a "retrieve" can be requested at any time, and it will
    254     download any results in workflow_results/GROUPNAME
    255 
    256 
    257 
    258 
    259 Will there be a problem if a user send simultaneously 1000 jobs by a
    260 script (as I saw you used temp folders which were deleted at the end
    261 of 1 submission) ?
    262 
    263     It's perfectly fine (quite common indeed).
    264 
     264    download any results stored in workflow_results/GROUPNAME.
     265
     266
     267The scientist may request the output at any time.  Is it also possible
     268to retrieve automatically the output in a predefined folder when a job is
     269performed?
     270
     271    Yes, scientists may request the outputs of successfully-completed WUs
     272    at any time (even if they are part of a still-ongoing chain of
     273    WUs). Automatic retrieval on the issuing scientist's machine via
     274    cron jobs is convenient.
     275
     276
     277
     278
     279=== Portability and server coexistence ===
    265280
    266281Do you have an idea if your application is directly compatible with
     
    269284    The '''client''' scripts are likely portable with minor changes
    270285    (just install a good perl interpreter and the required modules).
    271 
    272286
    273287
     
    277291    boinc server (but it can talk to any of its applications).  The
    278292    rboinc clients can talk to multiple servers using different URLs
    279     (-url option).
     293    ('''-url''' option).
     294
    280295
    281296I was thinking of having several Boinc projects to assign easily each
     
    289304
    290305
    291 The scientist may request the output at any time.  Is it also possible
    292 to retrieve automatically the output in a predefined folder when a job is
    293 performed?
    294 
    295     Scientists may request the outputs of successfully-completed WUs
    296     at any time (even if they are part of a still-ongoing chain of
    297     WUs). Automatic retrieval on the issuing scientist's machine via
    298     cron jobs is convenient.
    299 
    300 
    301 
    302306(Courtesy of BK)