Page 1 of 4

New released client

Posted: Thu May 31, 2018 8:07 pm
by bruce
The (previously beta) version of the FAH client -- 7.5.1 is now a public release: https://foldingathome.org/start-folding/

If you encounter difficulties, please use this topic.

(Some comments can already be found in the 7.5.1 beta topic need not be repeated here)

Re: New released client

Posted: Thu May 31, 2018 9:14 pm
by RichardGiddens
Just downloaded 7.5 with no problems. As a Biochemistry graduate (admittedly from about 40 years ago) with a fairly basic computer based in the middle of rural England, may I just say how pleased I am as a "small guy" to contribute in some way to the science that this project supports. Good luck to all of you guys with the super number-crunchers and the work of the Pande team.

Re: New released client

Posted: Fri Jun 01, 2018 2:44 am
by Yavanius
Congrats! That was a while coming to fruition! :)

Re: New released client

Posted: Fri Jun 01, 2018 11:07 am
by yurexxx
Start folding page needs to be updated with new link https://download.foldingathome.org/rele ... .1_x86.exe

Re: New released client

Posted: Fri Jun 01, 2018 12:21 pm
by foldy
This is a caching issue. The webpage does not set its caching timeout right. So you see the old site but when you refresh the browser page then you see the latest with the new link.

New FAHClient

Posted: Fri Jun 01, 2018 2:47 pm
by M&M_Dutch
Hurrah! Finally!

Re: New released client

Posted: Fri Jun 01, 2018 11:28 pm
by Nert
Is there a description somewhere of what's different between this version and the previous one ?

Re: New released client

Posted: Fri Jun 01, 2018 11:48 pm
by JimboPalmer
There are change logs.

FAHClient:
7.5.1

OSX installer updates. @kbernhagen

FAHControl:
7.5.1

OSX installer updates. @kbernhagen
Fix for slot/queue highlighting. @informatoris
Install Gtk theme engines in correct place on Windows.

FAHViewer:
7.5.1

OSX installer updates. @kbernhagen
Fixed PyON message parsing.

FAHClient:
v7.5.0

Fixed client memory leak.
Some spelling fixes.

FAHControl:

Fixed inconsistent highlighting.
Fixed ``python setup.py install`` wo/ ``version.txt``.
Highlight Matching WU When Slot Is Selected. fah-issues/#1127

FAHClient:
v7.4.18:

Fixed user stats link in Web control.
Fixed create team link in Web control.
Fixes Google+ share link in Web control.
Automatically uninstall conflicting files in Windows installer.
More thorough termination of F@H apps in Windows installer.
Removed option to install for all users in Windows installer.
Fixed Windows CPUID problem which causes fail to assign to CPU slots.

FAHClient:
v7.4.17:

Updated assignment servers.
Use same AS for GPU slots.
Updated URLs to point to foldingathome.org.

FAHViewer:
v7.4.17:

Fixed terminate called. . .'cb::Socket::EndOfStream' on client exit.
Updated URLs to point to foldingathome.org.

FAHControl:
v7.4.17:

Changed Windows default theme to be same as Clearlooks-Vista.
Fixed major memory leak.
Updated URLs to point to foldingathome.org.

FAHClient:
v7.4.16:

Removed support for reading Gromacs trajectory files.
Skip over non-GPU OpenCL devices during detection.
Pass both CUDA and OpenCL device indices to GPU cores when available.
Fall back to guessing GPU indices when drivers cannot be loaded.
Added message to indicate why GPU drivers were not detected.
Don't inadvertently remove GPU index options from config.
Correctly handle PCI bus/dev IDs > 127.
Fixed AMD PCI bus/slot code.
Report GPU PCI function in info.
Fixed detection of multiple GPUs of the same type. #1161
max-packet-size=normal (the default) redefined to mean 25MiB. #1154
Report more CPUID feature flags, specifically to detect RDTSCP.

FAHViewer:
v7.4.16:

Read JSON files from command line.
Use basic mode by default.
Removed support for reading Gromacs format files .trn, .tpr, .xtc.
Removed ``--xyz <file>`` option. Not needed.

Re: New released client

Posted: Sat Jun 02, 2018 3:59 pm
by JimH
I downloaded the new Mac OS v7.5.1 and my problem of "no stats" disappeared. The stats loaded on the Web Control page. The first time in 5 days. That was yesterday. This morning when I checked the stats had once again disappeared. Web Control show them as "loading". After 5 minutes....still "loading!"

Re: New released client

Posted: Sat Jun 02, 2018 5:43 pm
by toTOW
Note that the 7.5.1 client won't install on older systems (Ubuntu 10.04 for instance).

Re: New released client

Posted: Sat Jun 02, 2018 7:57 pm
by Dr. Merkwürdigliebe
Looks OK to me, but the link to the current project still doesn't work in the GUI. Same goes for for "Work Server" and "Collection Server". Would it be possible to grey out the button "Viewer" if fahviewer ist not installed? I don't care much about visualization that is why I don't install fahviewer on my system. A simple check if /usr/bin/fahviewer exists would be enough.

Re: New released client

Posted: Sat Jun 02, 2018 9:50 pm
by bruce
You enhancement request to grey out buttons for software that you didn't install probably won't be accepted. FAH Development resources are limited (and expensive) and the first question that's going to be asked is "If we support this enhancement, how much additional throughput will FAH produce globally?" I suggest you don't click that button, since you know it's not going to work.

Some changes are being made to the locations of Work Servers / Collection Servers / Assignment Servers. I expect that problems with those links will be resolved shortly. If not, post enough information so that we can validate your problem. (Do check your firewall settings first.)

Re: New released client

Posted: Sun Jun 03, 2018 7:31 am
by foldy
The links to Project Description / Work Servers logs / Collection Servers logs in FAHControl are disabled in FAHClient 7.5.1 permanently. Maybe they come back in a later FahClient release

Re: New released client

Posted: Sun Jun 03, 2018 11:01 am
by road-runner
Installed and appears to be working fine win 7/64 bit

Re: New FAHClient

Posted: Fri Jun 08, 2018 6:40 am
by Duce H_K_
Yes, memory leak in the new Advanced Control is finally no more. No obstacle was the large uptime and big log size. Snapshot below is clickable
Image
Maybe I will go on 'stress-testing' with max verbosity and a ~month process session time