Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Help the MacRumors SETI Team get on the Top 200 Lists!
- Thread starter simX
- Start date
- Sort by reaction score
Originally posted by Stelliform
That is what is interesting about SETI, if you can talk enough people to switch to your team, all of their WU's transfer. The drawback, like today when we lost a member who had a significant amount of points...
Damn, who did we lose?
Yes, there is a link to the stats for our team higher up in this thread. It would be nice if someone were to put that link in the SETI FAQ,
Yeah, wouldn't it? It'd also be nice if a someone were to unlock that thread so maybe it could be edited to include the link.
Originally posted by simX
Yeah, wouldn't it? It'd also be nice if a someone were to unlock that thread so maybe it could be edited to include the link.
Last I checked you could edit your own posts in locked threads. Let me know if you can't.
I locked it to prevent "off-topic" discussion.
I run the command-line version of SETI@home when my Mac is awake, but not when my Mac is asleep. I don't mind contributing CPU cycles, but I don't want it writing its status files to my hard disk every minute. I want my hard disk spun down and taking a well deserved rest overnight.
There was once an item at macosxhints about running SETI@home with a RAM disk. There was more to it than simply putting the SETI folder in the RAM disk. You had to have certain system folder items there too. But the item is no longer posted.
Does anyone have the facts about how to run CLI SETI@home without disk accesses?
There was once an item at macosxhints about running SETI@home with a RAM disk. There was more to it than simply putting the SETI folder in the RAM disk. You had to have certain system folder items there too. But the item is no longer posted.
Does anyone have the facts about how to run CLI SETI@home without disk accesses?
Originally posted by Rower_CPU
Last I checked you could edit your own posts in locked threads. Let me know if you can't.
I locked it to prevent "off-topic" discussion.
Nope, I can't edit it... it says it's locked and it just returns me to the thread.
Are you sure you have to have more stuff on the RAM disk other than the .sah files that SETI@home generates? I remember using a RAM disk, but I don't know if it's worth the effort or not... plus ramBunctious was pestering me to register.
I do have a gig of RAM, though, so it might not be a bad idea....
I am not sure that you have to move other files into the RAM disk, but I am sure that the tip I am referring to SAID THAT you have to.
Maybe I can test this myself. What's a way that I can find out the last time the hard disk was accessed, without accessing the disk to find out? I hope the Heisenberg uncertainty principle doesn't apply to Mac OS X!
Maybe I can test this myself. What's a way that I can find out the last time the hard disk was accessed, without accessing the disk to find out? I hope the Heisenberg uncertainty principle doesn't apply to Mac OS X!
Originally posted by Rower_CPU
Last I checked you could edit your own posts in locked threads. Let me know if you can't.
I locked it to prevent "off-topic" discussion.
nope, maybe mods can... but any Locked thread cannot be edited, as in posted in or edited a post you had previously wrote.
Arg! The gap between us and the top 200 clubs list is widening! While we've pushed over the 200000 work unit line, the 200th club is processing work units faster than us! We're looking at a 50167 unit gap right now, where before it was in the 40000s.
Anybody got any spare computers, or some spare people to convince to join the MacRumors SETI team?
Anybody got any spare computers, or some spare people to convince to join the MacRumors SETI team?
The gap has widened to 58000.
I am still running folding, but I have installed SETI on all of my old computers. They spit out a WU every few days, but it is better than nothing.
By the way, jBiga must have been using multiple logins, since he just added 102 WU's under the same name. Thanks!
....
A computer teacher who I help might not mind setting her classroom computers to run SETI, but I'm not sure whether or not it would be possible because we've set up the Macs to netboot. They all start with identical boot disk images on the server as their boot device and all student home folders are on the server too. I would need to set things up properly so that the SETI data files were in either a home folder on the server (and we hope the same student doesn't log in on two Macs at once) or on the local disk that is not otherwise used. Has anybody tried this or can anybody advise me on which of the two locations would be best for the SETI data files?
The SETI application itself would be resident in the Applications folder of the boot disk image and/or the local disk. Would it matter which one I use? Either would work if you launched it manually, but I'm not sure which would work when it is used as a screensaver.
The SETI application itself would be resident in the Applications folder of the boot disk image and/or the local disk. Would it matter which one I use? Either would work if you launched it manually, but I'm not sure which would work when it is used as a screensaver.
I'm really not sure what SETI is about. Since I have my first 2 units with folding that concept makes sense to me now. My thought on the subject of the 2 programs is that if we are to move into the red zone, all members on this forum should concentrate on folding only.
Doctor Q, from your comment about, do you have some real concerns about leaving a Power Mac Hard Disk running 24/4?
Doctor Q, from your comment about, do you have some real concerns about leaving a Power Mac Hard Disk running 24/4?
My comments about the hard disk are based on the assumption that the life of the disk will be longer if it gets to spin down in between the times that I really use the system, as opposed to having it running all the time if SETI writes to its status file every 60 seconds. I'm willing to donate idle CPU time, but not if the elapsed time MTBF (mean time between failure) of my disk will be vastly shorter. I think the same would be true for the teachers with idle computers at school.
wdlove -- They are 2 very different projects Folding and SETI are.
Some people feel that it is more worth the time to try and find Alien like (SETI) while others would like to cure dieases (folding)...
While yet others support both teams by allowing their Os 9 and under machines run SETI while the Os X and above machines run folding which support MacRumors even more.
(Hope I wasn't biased)
--MrMacMan
Some people feel that it is more worth the time to try and find Alien like (SETI) while others would like to cure dieases (folding)...
While yet others support both teams by allowing their Os 9 and under machines run SETI while the Os X and above machines run folding which support MacRumors even more.
(Hope I wasn't biased)
--MrMacMan
From my reading of the FAQs, I've concluded that you can't contribute to folding if your Mac isn't running it most of the time. With data sets that time out in a matter of days, a "weekend warrior" Mac that's on now and then but not for long continuous periods may not finish its work units before they time out.
Am I misunderstanding how it works?
Am I misunderstanding how it works?
Originally posted by MrMacman
wdlove -- They are 2 very different projects Folding and SETI are.
Some people feel that it is more worth the time to try and find Alien like (SETI) while others would like to cure diseases (folding)...
(Hope I wasn't biased)
--MrMacMan
Thank you for the explanation MrMacman. Since I'm a nurse, it means a lot to be assisting in research to fight diseases an find new cures. I also feel an accomplishment by helping the team.
http://www.stanford.edu/group/pandegroup/folding/faq.html#run.WUlimit
Folks-
Lets not turn this into another F@H vs SETI debate.
Sorry. But thanks for answering. I've been on the SETI team for over 500 units and my thoughts about devoting more machines and more CPU time for either project are based on my technical questions about disk accesses, timeouts, and netbooting.