compdewd wrote:Has it been suggested that HFM could link to other 3rd party stats sites rather than just EOC? Searching didn't bring up anything of the like. The reason I ask is because EOC does not provide my stats because I am part of team 0 and am out of the first 2000 that it keeps track of. Kakao Stats does keep track of me so it would be nice if HFM could include them as an option as well
Does Kakao have a publicly available xml feed?
GreyWhiskers wrote:Another suggestion. It seems like the HFM WU History Viewer revalues its database each time it comes up with the then-current ProjectSummary data. There was a recent event where an SMP Project had its deadline shortened because the QRB was overly generous. It seems that HFM WU History Viewer recomputed all the already completed projects with the new ProjSummary values.
Does the V7 Client interface pass on the actual points, as reported in the log, to the remote client interface software? If so, could that be permanently stored in the HFM Database vs. recomputing?
Great, great product - I feel I have a much better oversight into how my folding farm is doing.
Yes, you are correct. The currently loaded project info is used to calculate the points seen in the WU History Viewer. This is how the different variations in PPD and Credit are shown to the user. As many know, the bonus calculation needs to know the total length of time from WU assignment to submission. The first two options for viewing PPD and Credit are two variations on estimating this total time.
Bonus based on Download Time - Total length of time from Download to WU Completion
Bonus based on Frame Time - Average Frame Time for the WU (multiplied by) the Number of Frames
No Bonus - Base PPD and Credit numbers are displayed
This is why the final PPD and Credit are not directly stored in the Database, just the frame time. I need to do some work with the Database in the next, next version (a reliability update is coming soon) and I'll consider fully capturing the final PPD and Credit values.
It's been asked in the past that the actual time of Upload Completion be captured but this has proven problematic with v6 and since the information on previous WUs disappears in the v7 data once the unit is uploaded that is not an option for v7 either. That also falls into your question on whether the v7 interface transmits the final points estimate as seen in the log file. I believe the answer is no. Someone correct me if I am wrong. Could I try to get it from the log? Possibly, but to this point HFM doesn't pay any attention to the PPD and Credit values that come from v7. That logic was already built in HFM for v6 and that's the way I plan on keeping it.
Thanks for the kind words GW! I certainly appreciate it!
@Fahrenheit451 - Can you send me your entire log.txt file from the FAHClient and the entire HFM.log file (Help > View HFM.NET Data Files)?
To answer a few of your questions, the Completed Count has two views (Current Run and Total) - see the View menu. The Current Run view should yield a number for a v7 client, this is the total number since the client was last started. The Total view will always show 0 since there is currently no counting mechanism in the v7 client. The v6 client reports this total number in the log after every WU completes and I capture the number from there. I'm going to fix this for all client types by querying the WU History database in lieu of looking at the log file itself. I just haven't had time to make those adjustments yet.
As far as the 0% progress goes... if you see the correct log segment in the HFM log viewer and the frame progress lines are green it should be showing the progress correctly. There is a speed issue with transferring the log file from the v7 client to HFM and it looks like it's on my side of the fence. So, after starting HFM if a v7 client takes a while to before it shows the correct progress, that's probably what's going on. It may take a few minutes to get in sync. I've started looking at the speed issue more closely and it's the last thing I want to fix before the next HFM update.
If that's not the issue, let me just look at your logs and I'll see what they say... you can find me at gmail.com.
However, that "old" log contained the start of the WU and the frame completion information and thus HFM wasn't able to find the log lines associated with the WU that was in progress as reported by the v7 client. If HFM cannot find the log section in its internal log buffer you'll see a line like this printed in the HFM's log file: ! (FAH Box One Slot 01) Could not find log section for slot 1. Cannot update frame data for this slot. It's telling you there that the proper log section cannot be found... thus HFM defaults to pulling frame time information from the benchmarks (which is what happens when the status of a client is RunningNoFrameTimes == Yellow).