1) Questions and Answers : Preferences : Scheduling vs. Report Deadline (Message 993553) Posted 2 May 2010 by K1VRA Post: Thanks for the reply. I didn't think it was a problem, just did not know how that scheduling worked.

2) Questions and Answers : Preferences : Scheduling vs. Report Deadline (Message 993308) Posted 1 May 2010 by K1VRA Post: I have noticed that, with every PC I have doing WUs,it looks like the WUs with the most immediate Report Deadline are NOT the ones being worked on. I believe my WUs are being finished before the deadline, I was just curious how BOINC decides which WUs to do first. Thanks.

3) Questions and Answers : Wish list : Change where BOINC stores unprocessed WUs? (Message 621052) Posted 17 Aug 2007 by K1VRA Post: BOINC was created to make sure cheating doesn't happen. So, they limited the ability to do server caching as you have recommended. Each machine that downloads a unit should be the same one that returns the unit. This way they can keep a better integrity on the data. Thanks for your response. So I take it that, even though the WUs were all downloaded by the same individual (not a 'team') user, albeit processed on different PCs, that would not be sufficient for tracking? (I do understand the need for tracking and maintaining the integrity of the research.) imho, is there really much difference between my PCs taking WUs off SETI's server or taking them from my own 'intermediate' server? The machine that actually processed the WU would be the one reporting it back. I just saw an opportunity to streamline the process while reducing the total number of WUs stored here (which makes them un-available for others to process - each of my machines caches several WUs ahead). Say, in order to keep my machines busy in the event of a SETI outage, or my own ISP's failure. Thanks, again.

4) Questions and Answers : Wish list : Change where BOINC stores unprocessed WUs? (Message 619538) Posted 15 Aug 2007 by K1VRA Post: I have several, networked PCs, each is using BOINC for s@h and each has it's own cache of WUs waiting to be processed. If every PC could 'look' in the same place (say, a shared network drive) for it's next WU, the local cache of WUs waiting to be processed would be much smaller. How about letting me choose where the WUs are stored?

 
©2024 University of California
 
SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.