Page 1 of 14

FAHClient V7.1.38 released (4th Open-Beta)

PostPosted: Mon Oct 10, 2011 10:19 pm
by jcoffland
Beta Testers,

I've been focusing on addressing the issues which most affect v7 client users and which may help those still running v6 clients to make the decision to upgrade to v7. Your feedback has been very important, not only in finding and solving bugs but in prioritizing development time. One donor had these concerns with using v7.1.33:

Jesse_V wrote:I'd be happy to try out v7.1.33 and its upgrades if I was confident that my participation wouldn't hurt science. I am concerned with a number of bugs in v7, things such as FAHClient taking up way too much CPU time and slowing things down. I also am concerned about v7 not being able to talk to the servers right, especially when errors occur.


Although the issues Jesse_V mentioned only affected a small portion of the v7 users they were legitimate concerns. I made sure these issues were thoroughly addressed in this release. Concerns like this are exactly what we need to hear about.

If you are also concerned about v7 affecting the science of Folding@home I have this to say. v7 is more likely to increase your contribution but if you do have a problem, and you report it, you are potentially helping thousands of users donate computing time to Folding@home so it's more likely a net gain. However, beta testers often have to be satisfied with peer recognition and praise rather than points.

If you've been on the fence about v7 now is a great time to upgrade. Here are some of the other comments we've been getting:

jimerickson wrote:i am running windows 7 ultimate 64bit and windows 8 developer preview release. everything went smoothly. . .keep up the excellent work.

DarkFoss wrote:The upgrade from v7.1.24 to 7.1.33 went flawlessly. . .install took less than a minute and it resumed folding the wu's they finished without issue. . .

OEOTS wrote:Congrats on the new release guys. with V7 you've made it all so much easier.

soya_crack wrote:Wow, that is one of a big advance. That was what F@H just needed. It's awesome. Easy to understand and just kickin' ass, the slot thing is what I was missing from BOINC.

WhiteLion wrote:Awesome! :) The best client i ever use, perfect for newbies, easy setup. . .


There are still several issues that need to be addressed before we go to the front page with the v7 client. Specifically the tickets listed in Milestone Open Beta Phase 2 under ticket report 3. Log filtering (#157), better ETA calculation (#395) and better handling of cores that don't terminate cleanly (#563) are the top three items.

There is more work to do but we are getting ever closer to a front page release of the v7 client. Thanks for all your bug reports and feedback. Keep telling us what issues are most important to you and we will do our best to address them.

Joseph Coffland
Folding@home Developer
Cauldron Development LLC

Image

Documentation
Installation and user guides can be found here:
FAHControl -> The Graphical User Interface (GUI) what controls the Slots.
FAHViewer -> It shows the protein being folded, if applicable.
Pictorial Installation Guide (Windows) -> A detailed pictorial guide on the V7 installation.
Installation Guide (Windows) -> A brief guide on Windows installation.
Installation Guide (Linux) -> A guide for Linux installation.
Installation Guide (OSX) -> A guide for OSX installation that is in progress.
Client Remote Interface -> Documentation for 3rd party developers.
Main Page -> Main page of the V7.

Getting Help
Aside from the documentation the best place to get help is in this forum. If you do have a problem post a message. There are many knowledgeable people ready and willing to help. Keep in mind, we greatly appreciate thorough reports delivered by patient people who can keep a cool head even when things go wrong.

Bugs/Tickets
Open Tickets Ordered by Milestone and Priority
Active Tickets by Change Time
Note: Some tickets may be closed because they are fixed in an upcoming alpha release but are not yet fixed in the beta release.


Here are the change logs:

v7.1.38:
  • Fixed network connection dropping.

v7.1.37:
  • Added missing wraplabel.py file to FAHControl.
  • Changed socket error message verbosity.
  • Fail WU on UNSTABLE_MACHINE immediately & return for partial credit. #615

v7.1.36:
  • Fixed a potential socket connection bug. Maybe related to #734.
  • Added several NVidia cards to GPUs.txt. #737.
  • Improved Linux on battery detection. #738.
  • Print WU error state on WU status line.
  • Emit correct exception on FAH transaction failure. #615.
  • Fixed debian package install core permissions problem. #732.
  • Removed core byte order warning. #602.
  • Added GPL link to FAHControl about. #736.
  • Ask user, team, passkey and mode during .deb package install. #739.

v7.1.35:
  • Added 'Enchanter' theme. #731
  • Renamed 'Wimp' to 'Windows-Default'. #731
  • Unminimize FAHControl window on unhide. #567
  • Better core download failure message. #161
  • Cleaned up project descriptions using html2text.py.
  • Store project data in client DB.
  • Use system default font size. #733
  • Added project info to viewer. #575.
  • Added clickable buttons to viewer.
  • Fixed FAHViewer crash introduced in v7.1.34.
  • Fixed mouse wheel scrolling in FAHControl. #463.
  • Fixed color difference for text boxes. #698.
  • Changed FAHControl window name. #711.

v7.1.34:
  • Fixed CPU consumption in client connections. #702
  • Really fixed "Wrong architecture" bug on 32-bit Ubuntu. #599
  • Only warn on config errors. #722
  • Log error and continue of command server fails to initialize.
  • Fixed Slot configuration text. #717
  • Use -1 or 0 for CPUs default to be consistent with GPU options. #717
  • Disabled no longer supported AMD X1300 - 1900 GPUs.
  • Added "OpenGL Render" to info in FAHViewer. (For blacklisting)
  • Added 'override-blacklist' option to FAHViewer. (Nothing black listed yet)
  • 'OK' -> 'Save' in FAHViewer preferences window. #724
  • Fixed NVIDIA_DEV.1244.01 = "NVIDIA GeForce GTX 550 Ti" detection.
  • Added the 'Wimp' theme and win32 theme engines. #723
  • Made 'Wimp' theme the default in Windows. #713
  • Added heartbeat to viewer<->client connection to timeouts dead connections.
  • Stop trying FAILED, FAULTY and DUMP reports if WS connection was made. #728
  • Check WS server versions for unreasonable values. #728.

Here are the highlights and some of the technical details of the changes in this open-beta:

Improved network handling:
A number of networking related issues were solved. The run away CPU usage problem was caused by incorrectly handling dropped connections. Periodic connection loss on Windows machines was caused by not correctly handing a quirk in the Windows sockets API which was the cause of the greyed out FAHControl that some people were experiencing. Also, dropped connections are now being cleared out of the client much more quickly. This keeps dead connections from accumulating which caused problems in a few cases.

Improved communication with older WS:
Several problems with communication with older WS were fixed. This version does a better job of detecting older WS and aborts the error loops that the previous client got into when incorrectly trying to upload DUMP reports to the old servers. This was the cause of the repeated upload errors many people saw in their logs. Also, a bug was fixed in the handling of UNSTABLE_MACHINE core return code which was the start of many of these DUMP communication loops.

GPU detection:
More cards were added to the whitelist and some older, no longer supported, GPUs were removed.

Debian package improvements:
A permissions problem was fixed that was causing WU loss after reinstall. The installer also now asks for user, team and passkey if /etc/fahclient/config.xml does not already exist. RPMs and OSX packages still need this feature.

Added a native Windows theme (Wimp):
The Wimp (Windows Implementation) theme was added to FAHControl. This theme gives a true native look on all Windows platforms because the theme engine actually uses the Windows system to render the GUI components. This is now the default theme for Windows platforms. Still need something like this for OSX.

Re: FAHClient V7.1.38 released (4th Open-Beta)

PostPosted: Mon Oct 10, 2011 10:37 pm
by Jesse_V
Sweet! I'll be downloading!

http://en.wikipedia.org/wiki/Folding@home updated.

Thanks for your hard work!

Re: FAHClient V7.1.38 released (4th Open-Beta)

PostPosted: Mon Oct 10, 2011 11:12 pm
by 7im
Upgraded Win XP 32, Win 7 32, Win 7 64. No issues to report.

Will try the new .deb option soon.

Re: FAHClient V7.1.38 released (4th Open-Beta)

PostPosted: Mon Oct 10, 2011 11:16 pm
by bruce
First impressions after upgrading with the V7.1.38 .dmg: It seems to work as expected.

Re: FAHClient V7.1.38 released (4th Open-Beta)

PostPosted: Tue Oct 11, 2011 12:11 am
by Grandpa_01
7im wrote:Upgraded Win XP 32, Win 7 32, Win 7 64. No issues to report.

Will try the new .deb option soon.

Please let us know if you can do an over the top install with the .deb package. I would really prefer that some one besides me be the one to find out you can not this time. :lol:

Re: FAHClient V7.1.38 released (4th Open-Beta)

PostPosted: Tue Oct 11, 2011 12:52 am
by Jesse_V
That's a bit weird that the file is labeled "fahclient_7.1.38_Windows-XP-32bit-release.exe" Shouldn't be "fahclient_7.1.38_Windows-32bit-release.exe" without the specific Windows XP name? I'm assuming that it doesn't matter for those running Windows 7, but its a rather trivial thing that could be taken care of next time. Anyone who's downloading v7 at this point is very likely not going to be confused by that label, but I'm of the opinion that it should be taken care of for following versions. I realize I was quoted up there (wow! thanks!) so I just wanted to point out that I'm very pleased to see mine and other users' concerns taken care of like that, and for the first time I will be testing it out. Thanks very much Mr. Coffland, impressive work!

Re: FAHClient V7.1.38 released (4th Open-Beta)

PostPosted: Tue Oct 11, 2011 1:05 am
by PantherX
Jesse_V wrote:That's a bit weird that the file is labeled "fahclient_7.1.38_Windows-XP-32bit-release.exe" Shouldn't be "fahclient_7.1.38_Windows-32bit-release.exe" without the specific Windows XP name? I'm assuming that it doesn't matter for those running Windows 7, but its a rather trivial thing that could be taken care of next time. Anyone who's downloading v7 at this point is very likely not going to be confused by that label, but I'm of the opinion that it should be taken care of for following versions...
The name included in the .exe file is of the build machine and it was already identified a long time ago but was closed due since it would be taken care of in the final version (285)

Happy Beta Testing :D

Re: FAHClient V7.1.38 released (4th Open-Beta)

PostPosted: Tue Oct 11, 2011 1:13 am
by Zagen30
Installation in place of 7.1.33 went smoothly; my previous upgrade from .24 to .33 on Win7 64-bit did not, so I'm happy this one did.

Re: FAHClient V7.1.38 released (4th Open-Beta)

PostPosted: Tue Oct 11, 2011 1:26 am
by Jesse_V
jcoffland, I was just reading through the documentation, and here's a suggestion for you: as a feature request, please prompt the user as to whether or not their computer is a desktop or a laptop. In my opinion this should be asked in both levels of the installation. I feel that this is an important request as it appears from the documentation that "pausing on battery" is not checked by default. Perhaps it should be. In any case, I've read somewhere that college students are providing a lot of computing power. Most of the people I see here at USU have laptops, including myself, and it would be a shame if they ended up installing v7 only to have their battery drain within minutes because v7 didn't pause itself. The setting for this I gather is under the Advanced tab, and then under Configure. While everyone who installs v7 ought to read the documentation, I'm concerned that those that do not might have this issue. While I agree that those slot configuration settings are rightly under Advanced, either 1) the "pause on battery" is checked by default (I don't know the consequences of this being checked on a desktop, but perhaps nothing) or 2) pose a simple and easy-to-understand question in the configuration window, and not let installation continue until the user chose either the "Desktop" button or the "Laptop" button. If "Laptop" is selected, automatically check the "pause on battery" option. If "Desktop" do nothing and just continue the installation. If the user for some reason wanted v7 to run while on battery, this would likely be unusual and so they ought to look under the documentation and the Advanced setting as to how to uncheck that again. This wasn't that big of a deal in v6 as the setting was right there. Thanks.

Re: FAHClient V7.1.38 released (4th Open-Beta)

PostPosted: Tue Oct 11, 2011 1:53 am
by 7im
Please no additional prompting! The install needs to stay simple. Either autodetect it, or default to on (1). Desktops should never be affected, and laptops can turn it off if they so choose.

Re: FAHClient V7.1.38 released (4th Open-Beta)

PostPosted: Tue Oct 11, 2011 4:32 am
by jimerickson
updated windows 7 ultimate 64-bit, and debian 6. no problems to report. thanks jcoffland.

Re: FAHClient V7.1.38 released (4th Open-Beta)

PostPosted: Tue Oct 11, 2011 5:15 am
by gwildperson
Jesse_V wrote:If "Laptop" is selected, automatically check the "pause on battery" option. If "Desktop" do nothing and just continue the installation. If the user for some reason wanted v7 to run while on battery, this would likely be unusual and so they ought to look under the documentation and the Advanced setting as to how to uncheck that again. This wasn't that big of a deal in v6 as the setting was right there. Thanks.

7im wrote:Please no additional prompting! The install needs to stay simple. Either autodetect it, or default to on (1). Desktops should never be affected, and laptops can turn it off if they so choose.


Let me propose a compromise. Change the default to Pause on Battery=true. I'll bet that Desktops run fine with that setting and that they never happen to get the signal that they're running on battery.

Re: FAHClient V7.1.38 released (4th Open-Beta)

PostPosted: Tue Oct 11, 2011 6:41 am
by 7im
What compromise? I already said auto detect it, or default it to on, as in "default to Pause on Battery=true" but prompting is out of the question, IMO.

Re: FAHClient V7.1.38 released (4th Open-Beta)

PostPosted: Tue Oct 11, 2011 8:59 am
by Napoleon
Uninstall 7.1.33, keep data, install 7.1.38 went smoothly, except Local Client Autostart in Preferences got disabled for some reason. Enabled it again, and the new client picked up right where the previous one left off, no need to reconfigure anything else this time. Nice! 8-)

EDIT: Autostart with FAHControl disabled was my mistake, I chose the startup option incorrectly during install.

Re: FAHClient V7.1.38 released (4th Open-Beta)

PostPosted: Tue Oct 11, 2011 9:07 am
by Brama
It solves my problem of FAHControl window partially greyed out.
Good job!