Posted on 01/08/2006 7:41:43 AM PST by texas booster
OK, new thread for the next week.
First, a big shout out to the SETI and BOINC members who have added CPUs to the effort. Remember, its Team 36120, NOT Team 0.
Next, congrats to all for bumping our team up to 384 processors and 192 user names. We have a number of new users in the team, with nearly a dozen folders now from GetLoaded.com all popping onto the hit list this week.
Special mention to Klutz Dohanger, who has quietly volunteered 80 systems to fold. That is 20% of all of the Free Republic Folders systems actively engaged in research. He is on a pace to pop 100,000 points personally before the end of January.
Malsua, uriah, Ken in Texas and Andrewksu are solidly in the top 10. Malsua is continuing to add (fast) systems and is now the number two folder on the team. Andrewksu will be the next member to hit 10,000 points. Great job!
Free Republic Folding@Home Stats Page
On the global front, Free Republic Folders is now listed at # 624. We are poised to overtake (today):
Flowers of Happiness (awww, ain’t that sweet)
SpongeZone
Team Redneck Beatdown
Go Navy!
French-Krew
and the Rochester Institute of Technology
As we continue to grow there are a number of milestones coming around the bend:
Top 600 by Monday
Top 500 within eight days
Top 400 within three weeks
We have 430,000 points so far. We will reach:
500,000 points by Thursday
750,000 points by Jan 24
1,000,000 points in early February
Thanks again to all that are helping us advance science and promote the peaceful use of computers.
Extreme Overclockers Stats for Free Republic
Also, if you were shipped a "beta" unit, under the advanced methods, those have to be "post-beta" inspected, to make sure that the code is correct, and works likes it's supposed to.
The point totals are higher, but there is a built-in delay, while the completed workunits are tested and compared.
After all, it's not the "amount" of work that is the most important to Stanford, but the "quality" of work. If the work units they ship out are rock solid, that's that much less manual intervention they have to do, and a lot less work in documentation.
Again, the log is the only way we can tell what might possibly have happened.
Here is the "successful" completion of WU 4 and the beginning of WU 5:
[16:31:24] Completed 471275 out of 500000 steps (94)
[16:33:48] Writing checkpoint files
[16:48:57] Writing checkpoint files
[17:00:39] Writing local files
[17:00:39] Completed 475000 out of 500000 steps (95)
[17:04:00] Writing checkpoint files
[17:19:10] Writing checkpoint files
[17:34:14] Writing checkpoint files
[17:37:38] Writing local files
[17:37:38] Completed 480000 out of 500000 steps (96)
[17:49:23] Writing checkpoint files
[18:04:33] Writing checkpoint files
[18:17:53] Writing local files
[18:17:53] Completed 485000 out of 500000 steps (97)
[18:19:39] Writing checkpoint files
[18:34:48] Writing checkpoint files
[18:49:54] Writing checkpoint files
[18:58:30] Writing local files
[18:58:30] Completed 490000 out of 500000 steps (98)
[19:04:57] Writing checkpoint files
[19:20:00] Writing checkpoint files
[19:35:13] Writing checkpoint files
[19:38:53] Writing local files
[19:38:53] Completed 495000 out of 500000 steps (99)
[19:50:20] Writing checkpoint files
[20:05:25] Writing checkpoint files
[20:14:18] Writing local files
[20:14:18] Completed 500000 out of 500000 steps (100)
[20:14:20] Writing checkpoint files
[20:15:20]
[20:15:20] Finished Work Unit:
[20:15:20] Leaving Run
[20:15:22] - Writing 536297 bytes of core data to disk...
[20:15:22] ... Done.
[20:15:22] - Shutting down core
[20:15:22]
[20:15:22] Folding@home Core Shutdown: FINISHED_UNIT
[20:15:24] CoreStatus = 64 (100)
[20:15:24] Sending work to server
[20:15:24] + Attempting to send results
[20:15:37] + Results successfully sent
[20:15:37] Thank you for your contribution to Folding@Home.
[20:15:37] + Number of Units Completed: 4
[20:15:42] - Preparing to get new work unit...
[20:15:42] + Attempting to get work packet
[20:15:42] - Connecting to assignment server
[20:15:42] - Successful: assigned to (171.65.103.158).
[20:15:42] + News From Folding@Home: Welcome to Folding@Home
[20:15:42] Loaded queue successfully.
[20:15:45] + Closed connections
[20:15:45]
[20:15:45] + Processing work unit
[20:15:45] Core required: FahCore_82.exe
[20:15:45] Core found.
[20:15:45] Working on Unit 05 [January 10 20:15:45]
[20:15:45] + Working ...
[20:15:45]
[20:15:45]
Rock on! :)
Shading, I think, has something to do with OpenGL and the GPU (Graphics processor unit).
I couldn't find which summary you were talking about, but I think it's part of how Gromacs does it's calculations.
They're running the console version now. I had installed the GUI version at first, since I wasn't too familiar with the console version yet.
I don't think there's a way to get the beta-core (QMD) stuff through the standard configuration - I think you have to add the command-line flag by hand, meaning that most folks here probably aren't set up for it. Probably for a reason - they're not kidding about the system requirements for these things. I have a QMD unit going now, and it's chewing up almost 330MB of memory all by itself.
That's definitely the way to go, especially for someone (like you) who has a farm to tend to. That way, it'll restart without any intervention on your part if the machine crashes and restarts for any reason. Less work for you, right? :)
It shows that it successfully upload. Can you scroll up to
where you're assigned the workunit.
The next step is to check the server you were assigned, to see
if it went down prior to posting the stats or....
Sent you FReepmail, so my log wouldn't hog the space. The log only goes back to Jan. 8.
The logs periodically recycle, there should be one called fahlog-Prev.txt in the same directory.
But it looks like you were assigned to a "non-advanced" ie, non-beta version, and the server logs show that it's been up all day.
Probably, like I said earlier, there is some checksum, or another anomaly in the data that you uploaded, and it has to be checked manually before posting.
Sometimes, over in the forum, you'll see where they post problems with specific servers, but with over a million cpu's folding, somehow, I don't think these guys have time to answer what happened to every uploaded Work Unit.
*shrug*
Woo Hoo...
Usually I don't toot my own horn, but I'm in the top 100
clubs...
#66 in points today
#90 in 24hr average
#97 in points for the week
Nice job!
I am VERY discouraged. I was touting this program to friends...but if my points aren't going to be counted, I am having second thoughts.
You know how good it feels to have your points counted....
Checking their forums, this is a pretty rare occurrance, and the participants get credited the points, just not right away, as expected.
Momentarily discouraging - yes, but probably the only fair way to do it.
After all, it's the quality of the data that really counts, and if they're zinged with some "questionable" work units, the integrity of the program goes down.
I'm sure you're just in the QA queue.
Don't get me wrong...I'm adult enough not to care about the points if it advances knowledge...the problem is, I've been advocating this program to some of my "mom" friends...telling them how much fun it would be for kids to see the points rack up.
Last message...I will wait and see if things resolve.
Thanks for taking a look at my data!
I would have guessed that it is there for improved readability, but as it is not of a uniform pattern, I have no idea.
Cool!
I'm 659/685 24/week. At least I'm in the top 1000.
Thanks, I'll have to try that on my console app.
Thanks for the link, Drango. I wasn't aware of that site. I bookmarked it and will check it out thoroughly as time permits.
Thanks again.
RT
BTTT!
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.