Yujah

The practical thing to do would probably be to reserve Steam keys for FPS games for top-N folders and hand out keys for story-driven adventures to us casual gamers folders...

Yesterday it seemed F@h got the stats back up; all was updating for me at least. This after points indeed not updating for at least a day before that (at the F@h state page; they did at EOC). Currently I've had at least two WUs again that haven't registered for hours, and this time including at EOC.

This thread's too busy to respond without quoting: personally I'd feel it nothing to worry about; just a case of whatever software you are using to monitor not ye being 2700X-aware.

Don't know why it's displayed but can assure you that it didn't. LOL.

Personally I'd feel it nothing to worry about; just a case of whatever software you are using to monitor not ye being 2700X-aware.

Don't know why it's displayed but can assure you that it didn't. LOL.

Note; on reading back that quote I noticed that while, yes, HD7730+ is GCN1, earlier discrete HD 7000 cards are TeraScale 3 and earlier APU-variants TeraScale 2 and should in the context of this thread, double precision math, therefore also work.
 
AMD's branding was rather confusing at that point, but this would be to say that we here get to summarize simply as "HD 5830+ and HD 6930+". Original post edited...

Yes. the discriminator is double-precision floating-point math support. The 7950 is GCN and all GCN chips should work. The HD 5000 and HD 6000 series, some HD 7000, are still TeraScale though and need an HD 5830+ (TeraScale 2) or HD 6930+ (TeraScale 3) to be usable by current F@h.
 
HD 7730+ is GCN1 and definitely works, before that HD7000 branded cards are TeraScale 3 (discrete cards) or TeraScale 2 (APUs) but that should also work it seems. I.e., 5830+, 6930+.
 
Specifically then, an HD 5750 will indeed not work. Note that this will/would not be evident in the client itself but that you'd getting 192.0.2.1 assigned as a work server each time. That's an unroutable, reserved IP address and F@h's way of saying "hell no!" at runtime...

This is exactly why we do it the way you say, even if we get corrupted data like yesterday, by the end of the event all is fine for the most part

Yah, know about that. Had already also followed up on that post myself; have basically gotten WUs back to back ever since shortly after posting it....

Basically, you're looking at atoms that are parts of some proteins, interacting with a forcefield.
 
Mostly, they are the proteins at the surface of the human malware, which are responsible for all the things it does (interacting with human cells, antibody recognition, etc.). Or, some drug targets, i.e. proteins or molecules that are supposed to interact with the virus surface proteins.

There currently is a problem with a collection server, it is addressed in this topic: Folding @ home forum (Some WUs send without points)
 
User "jcoffland" explained it:
Direct link

Yes, seems that should work; see FP64 spec at https://www.techpowerup.com/gpu-specs/radeon-r9-m275x.c2658
 
As to the specific issue I wouldn't currently know I'm afraid. We're basically all of us DDoS-ing F@h and  it's hard to separate issues that are due to a local problem from those that are due to former. It is any case not to be expected that all will be smooth....

LTT would like to make explicit it does not advise sprinkling maggots all over the inside of your computer though.

Yes, those don't support double precision in/through OpenCL; if you study the log you will undoubtedly see being assigned a work server 192.0.2.1 for the GPUs which is in fact an unroutable address, reserved for documentation and examples, and F@h's way of telling you that the GPU is unsupported. It's not evident in the frontend that it is because in theory the queue's available for single-precision work units, but well, those don't actually tend to exist anymore in practice.
 
Of that generation of AMD only a few top-models in the HD 58xx, HD 59xx and HD 68xx, HD 69xx series support OpenCL DP. I do believe that anything "new" does but I couldn't really tell you where the break-off point is specifically. The Nvidia types you mention would to me also seem too old but frankly I haven't payed much attention to Nvidia for many, many years now (am a Linux user) so perhaps simply trying is the best method: if you're assigned 192.0.2.1 as a work server, then you know they're not going to fly either.

Yes, I also noticed that "back-off system" where the client seems to wait exponentially longer between failed attempts; have indeed been pausing / unpausing due to that as well, but effect has still been minor it seems.
 
But... I did just now in fact land an 80K GPU WU; with 10 (or 14, what is it) days that would do as per-day result.

Adding maggots to your PC increases your FPS
 
 

LTT would like to make explicit it does not advise sprinkling maggots all over the inside of your computer though.

LTT would like to make explicit it does not advise sprinkling maggots all over the inside of your computer though.

Other than general instability of  your GPU it would seem this could be only the result of an driver bug. I don't pay much attention to Nvidia and certainly not on Windows, but there were indeed recent issues with Nvidia OpenCL on Linux at least. I.e., you may need to try updating your drivers and/or google specifically for your card, OpenCL and/or F@h.

Finish the sheet under the shower?

Possibly of note; the 500.000 points "minimum participation requirement" might be a bit of an issue now that F@H has quite a bit of trouble coming up with enough WUs to hand out --- and especially for LTT-forum members who signed up DUE to this event, as new donors don't get the so-called Quick Return Bonus (which can be 10x the base-credit for a WU) until they have 10 WUs total, which at the moment takes forever due to the WU shortage.

Entry 4907 in the list current at the time of posting, forum name "rene_" and folding name "rene" can be deleted.
 
Was/am new, but noticed that folding name "rene" was a bit too generic; saw e.g. combined stats from all donors folding under that name. The new forum and folding name which I'm now using is already in there as well, so nothing to change other than that; just rene_/rene that can go.