Changes between Version 15 and Version 16 of RemoteJob
- Timestamp:
- Feb 3, 2011, 11:04:29 AM (14 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
RemoteJob
v15 v16 189 189 == Frequently asked questions == 190 190 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 194 In BOINC you can't have 2 WU with different input but 195 with the same name (say, "environment.dat"), 193 196 because it will already be in the folder "download" on your 194 197 project. So you would have to rename the file or set manually the file … … 196 199 overwritten ? 197 200 198 199 That should be handled correctly: file names in download are 201 No, it will be handled correctly: file names are made 200 202 unique (in fact, equal to the file's md5), even though the 201 203 submitter used the same name for different contents. (It's fairly … … 204 206 205 207 206 207 I understood that with RBoinc, user didn't have to worry about 208 I understood that with RBoinc, user doesn't have to worry about 208 209 uploading separately files used and that it was automatic. So is it 209 210 important to ensure all input files (for different WUs) will have a … … 216 217 217 218 219 Will there be a problem if a user send simultaneously 1000 jobs by a 220 script (as I saw you used temp folders which were deleted at the end 221 of 1 submission) ? 222 223 It's perfectly fine (quite common indeed). 224 225 === Retrieve === 226 218 227 How does the manual retrieve operation affect workunits once a job has 219 been performed 228 been performed? 220 229 221 230 Retrieve will free up space taken on the server by the results of 222 231 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'' 224 233 through the chaining mechanism). 225 234 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''. 228 238 229 239 … … 237 247 What is the relationship between RBoinc and the assimilator? 238 248 239 Let me clarify:249 This important point should be clarified: 240 250 241 251 1. a client ("volunteer") computes a WU … … 252 262 The "retrieve" operation is completely independent of the above 253 263 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 267 The scientist may request the output at any time. Is it also possible 268 to retrieve automatically the output in a predefined folder when a job is 269 performed? 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 === 265 280 266 281 Do you have an idea if your application is directly compatible with … … 269 284 The '''client''' scripts are likely portable with minor changes 270 285 (just install a good perl interpreter and the required modules). 271 272 286 273 287 … … 277 291 boinc server (but it can talk to any of its applications). The 278 292 rboinc clients can talk to multiple servers using different URLs 279 (-url option). 293 ('''-url''' option). 294 280 295 281 296 I was thinking of having several Boinc projects to assign easily each … … 289 304 290 305 291 The scientist may request the output at any time. Is it also possible292 to retrieve automatically the output in a predefined folder when a job is293 performed?294 295 Scientists may request the outputs of successfully-completed WUs296 at any time (even if they are part of a still-ongoing chain of297 WUs). Automatic retrieval on the issuing scientist's machine via298 cron jobs is convenient.299 300 301 302 306 (Courtesy of BK)