Folding Forum

Hi Folding@home

I have had this problem for a bit now, the completed wu keeps resetting to 0 once closed and does not go to my completed wu in total after completeing a wu. so i let it complete several wu to see if that fixed it and id did not., i do not know how to fix this problem i have tryied re install and that did not fix the problem many thanks datahelp

If you stop and restart the client, creating a new log, the completed WU counter is reset to zero. The completed WU count is for the current log only.

It also won't count them if they don't complete. There are some failure types that aren't counted as failures.

If you happen to be using Langouste, I believe the method it uses to disconnect the WU from the client to send it separately prevents HFM from counting the WU as completed.

I think the "Number of Units Completed" count is from either the client or the servers, and HFM.net just reports what's in the log. The quote below is right out of HFM.net for my GTX560Ti card that's been folding for the last 8 months nonstop - through dozens of reboots, client starts and stops, CPU freezes, and other errors. Now, I haven't reloaded the v6 GPU client or updated the Nvidia driver since installation so that's a constant.

BTW, the snippet below was pulled a few minutes ago from a newer computer that is running HFM to monitor the remote machine that has the GTX560Ti. HFM is just reporting on what is sees in the FAH client logs on that remote machine.

BTW2, MtM's FAHWatch7 is shaping up into quite a useful tool, too. FAHControl alternative¶ While it doesn't give you the running log like HFM.net, it does give you a running graph of frame times, both for the currently folding WU, as well as for its historical archive of WUs. MtM is between versions now, so it isn't available for download, but watch for MtM's posts if you are looking for a good monitoring tool for v7.

[15:24:57] Posted data.
[15:24:57] Initial: 0000; - Uploaded at ~399 kB/s
[15:24:57] - Averaged speed for that direction ~507 kB/s
[15:24:57] + Results successfully sent
[15:24:57] Thank you for your contribution to Folding@Home.
[15:24:57] + Number of Units Completed: 1785

HFM parses the current log for the number of WUs completed successfully.

HFM is reporting 128 WUs completed on one of my GTX295 instances. That is the number of time it found FINISHED_UNIT in the current log. The log also reports Number of Units Completed: 10386, but this isn't used by HFM.

FWIW

All my numbers under completed are the same as "Number of Units Completed:" in the log which is the same number stored in client.cfg.

If the client is restarted the completed number stays at zero until the current WU is completed then the count goes back up to it's previous value +1 which could be in the hundreds or thousands. At that point there is only one "FINISHED_UNIT" in the current log.

Also, FWIW, none of mine match the "Number of Units Completed" shown in the log. They do match the number of occurrences of "FINISHED_UNIT" in the FAHlog.txt. I parsed the log with NoteTab to confirm the count. THis is in HFM 0.6.2 - Revision 336. There is a toggle under View that changes the Completed WU count from the Cout of FINISHED_Unit, to the Number of Units Completed. THat explains the discrepancy.

Yes, same version here. You can toggle the view of completed items using F10 or select it under View.

Edit was a little late. Default behavior is to parse the log for "FINISHED_UNIT",

bollix47 wrote:FWIW

All my numbers under completed are the same as "Number of Units Completed:" in the log which is the same number stored in client.cfg.

If the client is restarted the completed number stays at zero until the current WU is completed then the count goes back up to it's previous value +1 which could be in the hundreds or thousands. At that point there is only one "FINISHED_UNIT" in the current log.

Same here. I'm running an instance of HFM 0.6.2 Rev 336 Mon 07 Mar 2011 on a new computer monitoring two clients on an older remote computer and one client on the local computer - it is displaying in the header the same info from the client log.