Ha-hey, that's nicer looking...I can actually use the computer for other things now :D

formula72

Quick question (hope it wasn't already asked), can I use other app's for monitoring ETA time completion..like FahMon??

 
Yes, just use the CPU/SMP/GPU0/GPU1/ect folders when you set it up. The only thing that doesn't work is HFM.NET's WU completed/failed totals.

Turbo_T

Tracker V2 Just started throwing a "unable to update status" message every 3 minutes. I cam back to the machine and it's been reporting for the last 2 hours.  EOC has the update from 3pm so I am not sure what is not updating.  The only change I made was to shut down Tracker completely and reboot the system before I had coppied the directory over to my C:/ drive.  I wanted to see if mounting it on a sata 3 ssd would improve performance.  I coppied the entire folder and built a new shortcut for the desktop so I would be sure to start the new folder app.  It was still running but shortly after discovering the problem it Bsod'd and I just restarted and have resumed folding from the other HDD I originally set it up in.  Any ideas on why it would report the error, and confirmation of SSD higher performance?  I am wondering if I need to completely reinstall it in the new drive rather than copy it all there as i did the first time.  THanks,

 
Folding on an SSD has no performance gain. Actually, because of the frequent writes it can shorten your SSD's lifespan. I recommend leaving it on the HDD.
 
The error message you are getting is the Tracker failing to save the status.xml file. This file just shows the current status of the clients along with the most recent log entries. The Tracker doesn't get stats from the EOC site so the timing makes no difference.

so if i have to fold gpu do i make the flag for dual hex cores to -23 or -11 ??

Hi, I have been trying to set this up on my sons AMD 1090T computer but the FahCore_a3.exe allways stop working after a short period of time. Here below is the detaied descriptin of the problem from Windows....any idea what could be the problem? (I just did a clean install of W7 earier today).
 
 
Problem signature:
  Problem Event Name:    APPCRASH
  Application Name:    FahCore_a3.exe
  Application Version:    0.0.0.0
  Application Timestamp:    4d4720af
  Fault Module Name:    ntdll.dll
  Fault Module Version:    6.1.7600.16695
  Fault Module Timestamp:    4cc7ab86
  Exception Code:    c0000005
  Exception Offset:    0002e3be
  OS Version:    6.1.7600.2.0.0.768.3
  Locale ID:    1039
  Additional Information 1:    0a9e
  Additional Information 2:    0a9e372d3b4ad19135b953a78882e789
  Additional Information 3:    0a9e
  Additional Information 4:    0a9e372d3b4ad19135b953a78882e789

Ok thanks, I will see if I can do something to get it to work. Would be a sin to leave this computer not folding while my son is away and a competition is on

I just found this program... it works great- to make a long story short, my GTX 570 HD SSC is actually folding properly now - I was having trouble getting it "interested" in actually folding, even with the GPU3 client.
 
My 570 HD SC is currently pulling around 16k PPD.... makes me wish I had a better PS so I could throw my previous GTX 275 CO-OP in to help out. :)  No PPD for the SMP client yet...

illutian

....

I have the tracker set to use only 25% of the GPU using Heat Control (Default and the 2 point values I have been assigned so far). However, using EVGA's Precision to monitor GPU usage it shows the GPU spiking from ~5% to 99% usage.

If I turn off Heat Usage the GPU has a steady 98% usage rate. So the question is: Why is it fluctuating.

...

 
When you set the folding client to use 25%, for example, what it actually does is load the GPU to 100%, but for only 25% of the time, which is why you see the fluctuations you do.
 
Furthermore, be aware that some work units weren't desiged to work with heat control, and will ignore the heat control settings and use 99-100% of the GPU all the time.  (I can't remember which work units those are).

Davabled
Furthermore, be aware that some work units weren't desiged to work with heat control, and will ignore the heat control settings and use 99-100% of the GPU all the time.  (I can't remember which work units those are).

 
The reason for this is the FahCore. Core 11 uses FAH_GPU_IDLE while core 15 ignores it completely. Any WUs that use core 11 will work with Heat Control, and any WUs using core 15 won't.

nick1551
Is there a way to have the tracker show TPF or est. completion time?

Something cool to add might be a cpu/gpu temp to the upload.  Being able to see temps would be cool to see remotely, especially with the f@hmonitor android app, or in the forum sigs. 

 
TPF and ETA are both already visible in the client status viewer. You can open it by clicking the client name. This is the viewer:

THANK YOU!!!!!!     THANK YOU !!!!!!!!
I never would be folding if it wasn't for this fine program making it so easy! Great work jedi and just reading thru the posts answered most of my ?'s, but I just hope I didnt break protocol  here when i used Evga's  team #. I just finished my first 2 units( hoping thats the right term) on my gpu's.   At least i hope they got sent back lol
Thanks again man it worked flawlessly on my 470's and they were still in sli but once i disable sli both card got the same ppd. worked in sli but gpu 1 on ab was cycling  up and down in gpu usage and had about 3000 less ppd . 

Since the V7 client has been released, I figure I should clarify my plans for the Tracker. First of all, the Tracker as-is will not support the V7 client because it is COMPLETELY different in terms of is interfaces with 3rd party software. That said, supporting the V7 client IS possible.
 
However, due to the massive changes that it requires, it would require a near-complete rewrite of the Tracker. My plan as of now is to continue to support the current version of the Tracker with bugfixes/minor changes as long as the V6 clients are supported by Stanford. This does mean that there will be very few if any new features added though.
 
Now to support the V7 client, I plan on doing a complete rewrite of the Tracker if there is enough interest from users. That said, below is a list of some ideas I have for the new version.
 
1. Client shutdowns between WUs no longer needed
Thanks to the ability to reconfig the V7 client on-the-fly, the current -oneunit on all clients is not needed to ensure that the clients can be reconfigured between WUs. With V7 it's possible to reconfigure the client while it's running without even restarting it!

2. Per-client name/team/passkey options
This option is again thanks to the simplicity of the V7 client. Since all options can be modified on-the-fly without restarting the client the Tracker can just directly apply settings per-client without any of the overhead of using -configonly clients to change client.cfg.

3. Built-in EOC stats feed
This would just be a simple display like with HFM.NET. It would show your 24 hour PPD average, points today, points last 24 hours, ect. This data would also be exported in status.xml for live signatures. There would also be an option to get your EOCID automatically from your name/team combination, similar to the "Get EOCID" option in the current Tracker config.

4. Hardware monitoring
This is mainly to allow for things like "shutdown GPU0 if temp > X," but I think many users would find it convienient to be able to monitor everything in one place. Hardware monitoring would of course have an enable/disable option if the user prefers to use some other software for this.
Additionally, if Stanford makes it possible to control the FahCore idle time without client restarts it could be used for "Smart Heat Control." Using this you can set a maximum desired temp, and the Tracker will throttle the client as needed to prevent it from exceeding this temp.

5. Leave clients running on Tracker exit
This option would allow you to close the Tracker to update it or simply conserve system resources, without exiting the FAH clients. This is again made possibly by the new interface provided by the V7 client. This isn't possible with the V6 clients because the Tracker needs to watch for client process exit events. This would of course be user-configurable, so users could retain the current behavior of the Tracker stopping all clients before exiting. This also leads me to the next feature:

6. Remote client control
Pretty self explanatory, this option would allow you to control FAH clients on other computers remotely using the Tracker's interface. This is again made possible by the new interface in the V7 clients. You could also use a Tracker on any computer to control any client, there would be no predefined "master" Tracker that other instances have to connect to.
 
Also, remote client control should be possible from a smartphone app. I am not a smartphone app developer, but I figured I would point out that this is a possibility with the V7 client.
 
7. Improved Gaming Pause
Currently Gaming Pause uses a list of executables defined in Games.txt to detect running games. The downside of this method is that obscure and new games will not be detected in some cases. The plan would be to add DirectX/OpenGL detection as an option, in addition to the current Games.txt method. The user would have the option to pick which method is used. Additionally, the new V7 interface allows clients to be paused without exiting the client. With the V6 clients the only option was to exit the client and restart it.

8. Better initial setup process
The new setup process would walk users through setting up a name/team/passkey, then list all the hardware in the system capable of running FAH. The user can simply select what they want to fold with, and the default settings that work with that configuration will be used. GPU detection would also be moved to OpenCL, in order to accurately detect both ATI and Nvidia cards.
 
9. Proper Installer
This redesigned Tracker would also be available as an installer, in addition to the current portable exe. I have seen countless users set up the Tracker by running it straight out of the .zip archive without extracting it. This results in the Tracker setting itself up in a temporary folder that gets purged on reboot. This leaves the user wondering where it went, and is overall just confusing for less tech-savvy users. The installer version would solve this problem. Of course the Trracker would also be available as a standalone exe for those who prefer the portable setup.
 
10. Open Source
If I do end up redesigning the Tracker to support V7 and include these features, I will release it as an open source project once the basic framework is complete. I have received several requests asking about the Tracker's source code. The main reasons I never made it open source were:
 
1. It was a way for me to learn programming, so I wanted to overcome challenges on my own.
2. A large portion of my code would be confusing to other developers not familiar with how the Tracker works as a whole
 
But, since the Tracker has become widely used since its initial release a year ago, I think the FAH community would benefit if other developers could contribute to the project.
 
 
Feel free to comment on this or suggest other things, since the redesign is still in the planning stages and it's easier to add new ideas at this point rather than once the design has been finalized.

Excellent features! One thing that is vital for me is some way of linking core shutdown to windows shutdown. I will be installing 2x EVGA GTX 260SSC in a family computer today, and the main thing that is bugging me is that none of my family would know/remember to Exit / Stop Client on teh tracker before shutting down. Now I know when you initiate a shutdown, USUALLY, the tracker stops fine, etc etc especially on Win7, however, i'd have loved a feature whereby, as soon as you press shutdown, FAH Tracker stops clients & exits itself. I keep trying to find apps that would allow me to do this but to no avail :(

Colorbar isn't hard to implement.
 
Average wu ppd is only possible if there is a centralized database which there isn't at the moment. If the tracker goes OS and a willing host would offer asp.net hosting that feature wouldn't be far off ( tied in with the hw detection so it can report clock speeds and whatever other interesting numbers ( utilization/temperature ? )).
 
Jedi:
 
3. Look in the repository, there already is an eoc class which does what you want I think?
 
4. HW monitoring is also already in the repository, lacking a proper ui though and I'm still working on the universal interface ( which ties in hw detection with ocl/cuda/cal ). 
 

I am VERY interested in this. Especially remote control and the possibility of a smartphone app. Currently i have to use teamviewer. This looks awesome!