Project: 10200 (Run 0, Clone 5712, Gen 28)

Moderators: Site Moderators, FAHC Science Team

Post Reply
geluica
Posts: 9
Joined: Tue Sep 27, 2011 7:02 am

Project: 10200 (Run 0, Clone 5712, Gen 28)

Post by geluica »

Hello guys,

I have problem with Project: 10200 (Run 0, Clone 5712, Gen 28). I finish the project, but I didn't receive any credit, although there was plenty of time left for deadline. I use classic client for Windows. In log, there is only a sentence that said: "- Server reports problem with unit.", nothing else.

Here is the log:

Code: Select all

[06:51:44] Completed 241040 out of 250000 steps  (96%)
[07:13:36] Completed 242500 out of 250000 steps  (97%)
[07:49:55] Completed 245000 out of 250000 steps  (98%)
[08:27:54] Completed 247500 out of 250000 steps  (99%)
[09:04:41] Completed 250000 out of 250000 steps  (100%)
[09:04:44] DynamicWrapper: Finished Work Unit: sleep=10000
[09:04:54] 
[09:04:54] Finished Work Unit:
[09:04:54] - Reading up to 2822352 from "work/wudata_02.trr": Read 2822352
[09:04:54] trr file hash check passed.
[09:04:54] - Reading up to 434472 from "work/wudata_02.xtc": Read 434472
[09:04:54] xtc file hash check passed.
[09:04:54] edr file hash check passed.
[09:04:54] logfile size: 672982
[09:04:54] Leaving Run
[09:04:56] - Writing 3947834 bytes of core data to disk...
[09:04:58] Done: 3947322 -> 3151317 (compressed to 79.8 percent)
[09:04:59]   ... Done.
[09:05:01] - Shutting down core
[09:05:01] 
[09:05:01] Folding@home Core Shutdown: FINISHED_UNIT
[09:05:06] CoreStatus = 64 (100)
[09:05:06] Sending work to server
[09:05:06] Project: 10200 (Run 0, Clone 5712, Gen 28)


[09:05:06] + Attempting to send results [September 26 09:05:06 UTC]
[09:05:12] - Server reports problem with unit.
[09:05:12] - Preparing to get new work unit...
[09:05:12] + Attempting to get work packet
[09:05:12] - Connecting to assignment server
[09:05:13] - Successful: assigned to (171.64.65.99).
[09:05:13] + News From Folding@Home: Welcome to Folding@Home
[09:05:13] Loaded queue successfully.
[09:05:21] + Closed connections
[09:05:21] 
[09:05:21] + Processing work unit
[09:05:21] Core required: FahCore_a4.exe
[09:05:21] Core found.
[09:05:21] Working on queue slot 03 [September 26 09:05:21 UTC]
[09:05:21] + Working ...
[09:05:22] 
[09:05:22] *------------------------------*
[09:05:22] Folding@Home Gromacs GB Core
[09:05:22] Version 2.27 (Dec. 15, 2010)
[09:05:22] 
[09:05:22] Preparing to commence simulation
[09:05:22] - Looking at optimizations...
[09:05:22] - Created dyn
[09:05:22] - Files status OK
...
Mod Edit: Changed Quote Tags To Code Tags - PantherX
sortofageek
Site Admin
Posts: 3110
Joined: Fri Nov 30, 2007 8:06 pm
Location: Team Helix
Contact:

Re: Project 10200 Credit

Post by sortofageek »

Looking at your log, it appears you didn't receive a credit because there was a problem with the results returned.
[09:05:06] Sending work to server
[09:05:06] Project: 10200 (Run 0, Clone 5712, Gen 28)


[09:05:06] + Attempting to send results [September 26 09:05:06 UTC]
[09:05:12] - Server reports problem with unit.
If you haven't added the -verbosity 9 flag at client startup, please do so. That makes the log more chatty and may or may not give more info with this error.

Another folder did return that same WU successfully for full credit, so it wasn't a bad WU. Hopefully, this is just a fluke, maybe corrupted during the upload. If it keeps happening, there may be something wrong with your computer hardware.
geluica
Posts: 9
Joined: Tue Sep 27, 2011 7:02 am

Re: Project 10200 Credit

Post by geluica »

This means, there's no way to receive my credit?
This is not fare :( , I work for a month to this unit (on my work laptop, which is only 3-4h open/day). If it's something wrong why the client didn't say anything, to start other unit?
sortofageek
Site Admin
Posts: 3110
Joined: Fri Nov 30, 2007 8:06 pm
Location: Team Helix
Contact:

Re: Project 10200 Credit

Post by sortofageek »

I know it can be disappointing, particularly for those new to folding, when something goes wrong like that and you don't get a credit for your work. I remember feeling that way when I started folding end of December 2001. I have folded long enough now I realize this is just part of helping the scientists study protein folding. It happens to all folders occasionally, so it tends to even out over time.

We all lose WUs for various reasons, including problems on our end. It is good to report this, as you did, so we can keep an eye on it and discover whether it was a bad WU, so the project manager can perhaps discover that sooner and fix the issue. If, in monitoring the WU, we see it completed successfully by someone else, we can let you know so you can keep an eye on your system to determine whether it was just a fluke or whether you might need to fix something on your end.

There is really nothing we can do to get a credit for this WU, but you can add that -verbosity 9 flag, if you haven't already, to startup of the client. I don't know if that would have given you more of an answer in this case or not, but it definitely puts more info in the log than if you don't use the flag.

Given what you said about folding on the laptop which isn't on all the time, is it possible the WU wasn't returned to the server by the deadline? Check Project Summary to determine deadline for a 10200 WU and check your log to see how long it took your laptop to complete the WU and return it. That's just a stab in the dark. I really can't see much of your log.

Project Summary is here: http://fah-web.stanford.edu/psummary.html
It gives a preferred deadline of 4.59 days and a final deadline of 34.43 days for that type of WU.
sortofageek
Site Admin
Posts: 3110
Joined: Fri Nov 30, 2007 8:06 pm
Location: Team Helix
Contact:

Re: Project 10200 Credit

Post by sortofageek »

Having said all that, I just checked the database. Project: 10200 (Run 0, Clone 5712, Gen 28) has been completed successfully for full credit by another folder, so it was not a bad WU. That folder completed and returned the WU in 2.09 days.

Keep an eye on this. If you determine you are meeting the deadlines and it happens again, you probably need to do some troubleshooting.
Post Reply