Posted on 08/02/2006 5:16:19 PM PDT by texas booster
Time for a new FreeRepublic folding@home thread.
Our FreeRepublic team of 358 members comprised primarily of Free Republic members in good standing have banded together to donate their excess CPU cycles to a worthy cause. Via distributed computing, millions of computers around the world, contribute directly to scientific research, in the quest for a greater understanding of diseases such as Alzheimer's, Cancer, and Mad Cow (BSE).
Currently, the team is in 75th place (with 1009 active CPUs - 55,700 completed Work Units and 9.75 million points).
This is an entirely voluntary program, and if you want to learn more, please see the links posted below (or read one of the previous 20 folding threads)
So I "Bring it" and Lucy yanks the football away again with a 3300 point day.
Bastard.
;)
LOL! You have indeed brought it. I've had to add a few more PCs just to keep up with your increasing daily average. Now that I've discovered the beauty of the service-based console version, look out!
Thanks for taking the time to answer my question. Before I saw RebelTex's post, I tried to reinstall the console download. During the install process, F@H came back to life with no loss of data.
I'm curious. How much faster, if any, is the console version than the graphical client?.......Colin
"I'm curious. How much faster, if any, is the console version than the graphical client?......."
I think it's slightly faster, not a great deal. From comments of other FReepers, the real benefit is if you use graphics intensive programs, they won't be slowed down by the GUI based FAH displaying folding proteins. I can't be sure, but I do know that I had a Gainward video card (Nvidia GeForce4 Ti4200, 4X, 128MB DDR, TV OUT+DVI+VIO AGP4x) burn out shortly after installing the FAH GUI version. Needless to say, I was PO'd and switched to the console version immediately. I seem to remember a couple of other FReepers having similar problems, but it might not be related to FAH - don't know.
RT
Well, YEEE-HAAHH!
I took down my 2.26G P4 over the weekend and vacuumed out it's innards. I found all kinds of lint and dust in the CPU heatsink, so I tore that all down and cleaned it thoroughly. I reinstalled the heatsink with some of Antec's "Formula5" thermal compund and did the same for the support chip heatsink, as well. Also, I also reversed one case fan in the lower front so it now functions as an intake rather than an exhaust, a move that has really increased airflow through the case.
WOW! What a difference.
In the wake of all that, I was able to bump my CPU Demand all the way back up to 100% and the machine just posted its highest to-date 24hr Average: 118.
A clean machine is a fast machine.
Just lost one on my laptop at 97%... At least this one sent something back for partial credit. This is turning out to be a bad week for me. Last week was my best. Hopefully next week will be better.
Those p1487s are still going along fine on my dual core @ 41% and 26%.
Is Stanford down??
[12:58:38] + Attempting to get work packet
[12:58:38] - Connecting to assignment server
[12:58:59] Couldn't send HTTP request to server (wininet)
[12:58:59] + Could not connect to Assignment Server
[12:59:20] Couldn't send HTTP request to server (wininet)
[12:59:20] + Could not connect to Assignment Server 2
[12:59:20] + Couldn't get work instructions.
[12:59:20] - Error: Attempt #5 to get work failed, and no other work to do.
Waiting before retry.
It sure looks like it. Extreme Overclockers does not have any points for anyone at teh 9:00 am update.
Looks like they are back, but I still have one slow machine that can't get deadlineless WU's.
They ran out of deadlineless WUs some time ago. I changed my laptop a few weeks ago. It was on their forums.
That makes sense. My drop in production had to be from more than taking down two fast systems.
I wonder what we should use for older, slower systems that seldom access the internet. I have a few systems that will time out on a WU before they complete the task.
Gotta find some time to research the forums.
Another FAHMonitor update...
I've added the ability for machines to downgrade to "inactive" status, if they haven't reported in in 7 days. They're still available on the monitor, but they'll be in a repressible (is that a word) section at the bottom of the machine list.
After 60 days of non-reporting, they'll be purged from the system automatically. This purge includes all history for the machine as well.
Users that have no machines will be purged as well.
Is 7 days and 60 days sufficient? Especially in your situation, Klutz, where you lose the ability to control the machines for the summer; does the threshold need to be raised higher?
I'm an anomaly, so write whatever works best for the users who really need it.
I lose machines all the time. They get ghosted, moved, sent to the boneyard. My PPD starts dropping, I just go find another lab to borg :)
Wow, almost 69K points yesterday - that's gotta be close to a record for us.
Friday night and I'm folding the laundry bump.
p1487s @ 70% and 54%
1161 pts each but it killing my average for the week...
Disclaimer: Opinions posted on Free Republic are those of the individual posters and do not necessarily represent the opinion of Free Republic or its management. All materials posted herein are protected by copyright law and the exemption for fair use of copyrighted works.