Wee Hah! MR top 300 and first 100 work units completed. Making intermittant appearances on the MR top producer list, depending whether its a high completion day or not.
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.
It's a great week for Folding! (post your bragging here)
- Thread starter atszyman
- Start date
- Sort by reaction score
Err said:
Your 24 hour average is based on your last 7 24-hour periods of production. So you won't see your 24 hour average stabilize for about a week.
Yet another problem popped up 
Since I swithced to Tiger I have not been able to get a single WU to process. It either receives a faulty WU (which I realize can happen but it is rather frequent) or it says "- Couldn't get size info for dyn file: work/wudata_00.dyn" or:
"Warning: pressure scaling more than 1%, mu: inf inf inf
[08:52:25] Quit 101 - Fatal error: NaN detected: (ener[39])
[08:52:25]
[08:52:25] Simulation instability has been encountered. The run has entered a
[08:52:25] state from which no further progress can be made.
[08:52:25] This may be the correct result of the simulation, however if you
[08:52:25] often see other project units terminating early like this
[08:52:25] too, you may wish to check the stability of your computer (issues
[08:52:25] such as high temperature, overclocking, etc.).
[08:52:25] Going to send back what have done."
So, lovely as that is, I would love it to stop! I'm sorry if this is an obvious fix or in the rules of folding somewhere, I'll admit to having not looked solely because I haven't really ahd the time to browse much lately
Since I swithced to Tiger I have not been able to get a single WU to process. It either receives a faulty WU (which I realize can happen but it is rather frequent) or it says "- Couldn't get size info for dyn file: work/wudata_00.dyn" or:
"Warning: pressure scaling more than 1%, mu: inf inf inf
[08:52:25] Quit 101 - Fatal error: NaN detected: (ener[39])
[08:52:25]
[08:52:25] Simulation instability has been encountered. The run has entered a
[08:52:25] state from which no further progress can be made.
[08:52:25] This may be the correct result of the simulation, however if you
[08:52:25] often see other project units terminating early like this
[08:52:25] too, you may wish to check the stability of your computer (issues
[08:52:25] such as high temperature, overclocking, etc.).
[08:52:25] Going to send back what have done."
So, lovely as that is, I would love it to stop! I'm sorry if this is an obvious fix or in the rules of folding somewhere, I'll admit to having not looked solely because I haven't really ahd the time to browse much lately
Bollocks...CanadaRAM said:Heh! Helps that I can install on all my office computers so I can leave them folding all night and all weekend.
10,000 milestone!
Nermal, Ham-man, watch your mirrors - object approaching may be closer than it appears
The AMD has been producing more and more units. All of my past 4 weeks or so have been above 1K. Hopefully I will break the top 300 by the end of August...
Perhaps now is the time to see if I can get the IT guy at school to let me run the 150 or so computers in the school with Folding@home for the 16 hours of the day when they are not in use...
efoto said:Yet another problem popped up
Have you tried to delete/reinstall the F@H client and/or have it download a new unit?
Searched on google for your problem and the only thing that came up was something dated Aug. 2002 regarding problems with Unnamed units, and the same error popped up. Reinstall supposedly fixed that problem.
wow, been awhile for me.
I checked that site, kept looking for my name in grey but seems like there is still a computer with the client running back at my old job
Booya, still in top 10 after leaving 2 years ago! (I'm # 9)
Anyway, glad you guys are still crazy folding fools. Keep up the good work!
I checked that site, kept looking for my name in grey but seems like there is still a computer with the client running back at my old job
Booya, still in top 10 after leaving 2 years ago! (I'm # 9)
Anyway, glad you guys are still crazy folding fools. Keep up the good work!
dubbz said:
I was thinking about that, probably the best idea really although I just didn't figure it had to be done like that. I just repaired permissions and did some other maintenance, so perhaps it will have fixed itself magically
, otherwise I guess I will just have to try a reinstall.Thanks for looking into it.
Edit: How often do you guys get faulty work units? I seem to be getting a lot recently, however only on my Mac. My pc seems to be gruging away at the same thing running through frames at the moment....but it just seems like a lot of faulty units of late
bertinman said:wow, been awhile for me.
I checked that site, kept looking for my name in grey but seems like there is still a computer with the client running back at my old job
Booya, still in top 10 after leaving 2 years ago! (I'm # 9)
Anyway, glad you guys are still crazy folding fools. Keep up the good work!
It's time to get to the number 1 spot! Go for it, and welcome back!
Efoto, have you installed the security update? It gave me a couple of folding errors and had to install it 4 times. Therefore my daily average is now 66 per day, instead 266... Only thing that helps is to reinstall folding after deleting everything, and don't change anything in your system!
Why is it that sometimes the termnial shows "Finished a Frame (1)" and other times it is "Completed part 5000 of 4000000"?
Do different proteins process differently? or are these separate requests from Stanford requiring differnt processing? I just noticed it a little recently when fah finally started to process a protein, through 2 frames, then said it was faulty and sent it back This will make the third re-install....I hope it starts working soon.
Do different proteins process differently? or are these separate requests from Stanford requiring differnt processing? I just noticed it a little recently when fah finally started to process a protein, through 2 frames, then said it was faulty and sent it back
This will make the third re-install....I hope it starts working soon.
efoto said:Do different proteins process differently? or are these separate requests from Stanford requiring differnt processing? I just noticed it a little recently when fah finally started to process a protein, through 2 frames, then said it was faulty and sent it back
You're assumption is exactly correct. Different proteins are processed differently. Some have a large number of parts that update the display at intervals of #parts/100, and some (typically Tinkers) have 400 or so frames. For a breakdown of the different proteins and their point values go here. It appears that all of them are labeled as frames, some only have 100 and report more information on the number of intermediate steps, some just give frame counts.
atszyman said:
Excellent, thanks for that link. I have not seen that before, interesting read on a few of the proteins. Now if they would just continually process instead of crapping out all the time....that would be the day. It is getting really old to complete 2-3 frames and have it drop out as a faulty wu.
Our team is folding like crazy at the moment We have done 44,000 points in 3 hours Thats nearly what we do on an average day
We have done 44,000 points in 3 hours Thats nearly what we do on an average day 
DeSnousa said:Our team is folding like crazy at the moment
It looks like all the teams are having a banner day. Stanford mentioned on the 15th that they were having some network issues, so it could be a backlog of WU's that just got through....
Apparently some WU's were not processing credit for us properly. Here's a thread explaining it...
Folding Forum
redeye_be said:
Let's see how long it'll lasts.
LOL! If I think what you mean, it could last for a lifetime...
Pretty nice those three WU, can I have a couple of those?