Folding Forum

What do you think is missing in version 6.20

I myself have been using SETI know known as BOINC for years.
Where i can see alot of stats etc.

1. Here is a few things i cant find in Folding 6.20, i might be blind or it dosen't exist.
2. Be able to see how many Work Unit i have downloaded.
3. Be able to download more if i gona go offline for some longer time .
4. Be able to see time left in the consol (whitout open display), because having the display open takes alot of resourses.
5. Be able to see more stats in the consol
6. Portable edition, to be able to have it running from a USB memory (ALL files/settings in ONE folder)

And also be able to choose from more kinds of projects then 1
Ok, not all projects is good to analyse with the support of a grafic card (High Performance Clients),
but there must be more then 1 project anyway..

2. This idea has been suggested before, but the answer was no. It would slow the project down, if u download 10 WUs in advance and take 5 days to complete each, you would definitely exceed both the preferred and final deadline

3,4. Use FAHMON to track console clients.


However this is a good start for suggestions.
What i really want is my "-local" flag back, for my service installation =|

I just tested FAHMON, its just CRAZY that the folding 6.20 dont have that kind of stuff originaly.
Thats was just one of the things that i was looking for. I really hope this gona be included in some version later.

Stanford has used a minimalist design philosophy in regards to it's clients. If it doesn't make the client go faster or do more science, then it doesn't get a high priority when updating the client. If a nice to have feature is easy to work in to the client while they are making other improvements, then it gets added eventually.

Remember, these are biologists, chemists, physicists, not software designers. Any time they spend on making bells and whistles is time they spend away from the science of the project, which is looking to eventually treat or cure several diseases. And since the Folding Community has shown a desire to provide some of those bells and whistles in 3rd party tools, Stanford has welcomed the donations of those talents as well.

To answer your questions more directly...

1. WUs completed are noted in the fahlog.txt file of each client. Total WUs completed are shown on the F@h project web site, under the Stats pages. There are excellent 3rd party stats sites as well, some linked on the toolbar at the top of this forum.

2. Being able to download (cache) more work is not something that is helpful to the F@h project. Work units in F@h are serial in nature, unlike so many other projects. If you were to download and hold a work unit for an extended time, that would prevent the work from continuing on that line of work units until you returned from vacation. F@h WUs build upon each other. Gen B work units are not created and sent out until Gen A work units are completed.

3. The updated Viewer application in the new v6.20 is still very much under development, and doesn't work as well as the v5 version. However, when it is done, it will have several improvements over the previous version. You're right, this one still needs a lot of work.

4. The Systray client, with the icon in the tooltray, has menu links to your personal and team stats. And as Trivolve mentioned, many 3rd party utilities fill this need. Check out the 3rd Party Tools section of this forum.

5. The Linux console client is portable. And except for one registry entry, the Windows Console client is portable as well. Many people setup diskless computers, folding only from a USB drive to save money. Or they carry a USB drive back and forth from home to school or work.

There are hundreds of projects, as shown on the Project Summary page linked on the toolbar above. However, Stanford determines the order of the work units sent out, to help the science of the project move along the quickest. And while you may get a string of work units all from one Project number, that changes all the time as one project is completed, and a new one starts. You'll see soon enough.

My addition to the wish list would be that client does not interfere with day to day work on the PC.

I do think it's great that the pause and quit functions are so readily available on the systray client, but I miss the transparency of the uniprocessor and SMP clients when it comes to staying out of the way when necessary.

A tennant of the past needs to be restored. "Above all, the DC client does not cripple the PC on which it is run"

-Sid

Insidious wrote:My addition to the wish list would be that client does not interfere with day to day work on the PC.

I do think it's great that the pause and quit functions are so readily available on the systray client, but I miss the transparency of the uniprocessor and SMP clients when it comes to staying out of the way when necessary.

A tennant of the past needs to be restored. "Above all, the DC client does not cripple the PC on which it is run"

-Sid

I believe you are talking about the GPU clients... this wishlist is in the uniprocessor foruM? The uniprocessors don't interfere noticeably with day-to-day work on the PC.

Trivolve wrote:

Insidious wrote:My addition to the wish list would be that client does not interfere with day to day work on the PC.

I do think it's great that the pause and quit functions are so readily available on the systray client, but I miss the transparency of the uniprocessor and SMP clients when it comes to staying out of the way when necessary.

A tennant of the past needs to be restored. "Above all, the DC client does not cripple the PC on which it is run"

-Sid

I believe you are talking about the GPU clients... this wishlist is in the uniprocessor foruM? The uniprocessors don't interfere noticeably with day-to-day work on the PC.

Client version 6.20 IS a GPU client. (See title of the thread) Beyond that this is the GENERAL FaH forum. Please pay attention

-Sid

v6.2 is both kinds, so when suggesting improvements, please be specific as to what suggestion with which type(s).

We'll assume you meant the known to be resource sucking "High Performance" GPU client, because the classic CPU client does stay out of the way.