SETI Started Project it Could Not Finish

Questions and Answers : Unix/Linux : SETI Started Project it Could Not Finish
Message board moderation

To post messages, you must log in.

AuthorMessage
Terry Toolin

Send message
Joined: 28 May 09
Posts: 4
Credit: 0
RAC: 0
United States
Message 914401 - Posted: 5 Jul 2009, 18:29:56 UTC

Hi, folks-

In May, I loaded BOINC into my machine after hearing a radio interview about SETI and BOINC. I signed up for SETI work, and what was downloaded and started was a project that required more hours to complete than there were calendar hours available between then and the due date (1340 project hours with a month to do it in). In other words, under the best conditions, it was impossible to finish that project on time.

I thought . . . okay . . . the software tested my computer and the program should've known what it was getting into (even I can do the math on my pocket calculator).

The allocated month went by, and the project was about 60% complete (about right, based on what I was figuring), and I see this message on BOINC that the project was not completed in time, I likely won't get credit for it, and it recommends that I abort the project. I saw an FAQ article that explained that the project was likely given to another computer to work, and yes, aborting the project is the best solution.

I'll be the first to admit that I have a slow computer (older P3 460MHz running Ubuntu 9.04). It is a machine I set up to try Linux (which I really like, as long as it is on my personal machine, and not my 'family' computer. I have more tolerance for the occasional set-up hassles). When I next wish to but another machine, I'll upgrade then. Enough about that . . .

. . . I see where BOINC has evaluated my machine, tested its speed and processing power, etc., and the software should know what it's getting into! Why did it send me a 1340 hour project that only had some 600 hours to work it (if I gave it 100% use of the machine 24/7, which I won't. I use it, too!).

I don't care about the credits. However, what BOINC and SETI did lacks a little common sense, in my view. I got a little annoyed, set SETI to have 20% resource availabilty, with the World Community and Rosetta both having 40% each. So far (3 hours) SETI has opted to not send new work (the other two jumped right in, both with short projects, now that the resource again became available).

Am I overreacting???? I'm happy to volunteer my machine. I don't really need the credits or stuff like that. It would be nice, however, to feel that the 24/7 availability of my resources (while I also use them sometimes) for a solid month (plus) would be met by something better than 'can't use it - throw it out!' SETI and BOINC knew what hardware they were loading their project into, the due date of that project, and the fact that the day is 24 hours long, at best!

Thanks.

terry
ID: 914401 · Report as offensive
Profile arkayn
Volunteer tester
Avatar

Send message
Joined: 14 May 99
Posts: 4438
Credit: 55,006,323
RAC: 0
United States
Message 914448 - Posted: 5 Jul 2009, 20:17:20 UTC

It sounds like you were sent a Astropulse unit, they do take a long time to do.

Your best bet is to go into SETI resource preferences and uncheck everything except SETI@home Enhanced and Use Central Processing Unit (CPU).

That will make certain that you only get multi-beam work which should complete within 12-20 processing hours or so on your computer.

ID: 914448 · Report as offensive
Terry Toolin

Send message
Joined: 28 May 09
Posts: 4
Credit: 0
RAC: 0
United States
Message 914522 - Posted: 5 Jul 2009, 23:38:35 UTC - in response to Message 914448.  

Thanks for the information.

I adjusted the preference. we'll see what happens.

Thanks.

terry
ID: 914522 · Report as offensive
Profile skildude
Avatar

Send message
Joined: 4 Oct 00
Posts: 9541
Credit: 50,759,529
RAC: 60
Yemen
Message 914725 - Posted: 6 Jul 2009, 14:41:06 UTC

Enthusiasm for a project is great but its always best to read what you can about the project. I've mentioned in other threads that this is like buying a new car and complaining that it doesnt run right before you find out you need to release the parking brake. This is no different. Had you read the Astropulse FAQ You'd have noticed that the recommended minimum CPU is a 1.6 Ghz. I'm glad you've backed off the AP's and are now running the seti_enhanced multibeam (MB) good luck!


In a rich man's house there is no place to spit but his face.
Diogenes Of Sinope
ID: 914725 · Report as offensive

Questions and Answers : Unix/Linux : SETI Started Project it Could Not Finish


 
©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.