texinga

Just a quick update, I tried one of the tricks people have used with their Fermi cards by stopping the WU, replacing the FAHCore_15 (2.25) with version (2.22), and restarting the WU on my Kepler.  Upon restart, it knew that Core version 2.25 was required, and I got a statement:

+ Core out of date.  Auto updating...

It then proceeded to download and install a fresh copy of Core 2.25, and started the 7623 WU.  Unfortunately, I did lose the WU progress because it restarted the 7623 WU from zero %.  But I did receive the same 7623 WU (Run,Clone,Gen), so I didn't lose it or return it to the pool for rework by someone else.  Still...a "happy Console camper" and will quit tinkerin' for awhile and just Fold!

Just click "finish" and when the wu completes, it won't download another wu.. THEN you can swap the core and start the client. You already had another wu in the queue ready to go, the program knew you needed the new core to do the wu, so it just re-downloaded it..

mflanaga

texinga
Just a quick update, I tried one of the tricks people have used with their Fermi cards by stopping the WU, replacing the FAHCore_15 (2.25) with version (2.22), and restarting the WU on my Kepler.  Upon restart, it knew that Core version 2.25 was required, and I got a statement:

+ Core out of date.  Auto updating...

It then proceeded to download and install a fresh copy of Core 2.25, and started the 7623 WU.  Unfortunately, I did lose the WU progress because it restarted the 7623 WU from zero %.  But I did receive the same 7623 WU (Run,Clone,Gen), so I didn't lose it or return it to the pool for rework by someone else.  Still...a "happy Console camper" and will quit tinkerin' for awhile and just Fold!

Just click "finish" and when the wu completes, it won't download another wu.. THEN you can swap the core and start the client. You already had another wu in the queue ready to go, the program knew you needed the new core to do the wu, so it just re-downloaded it..

Where's the "Finish" button on the "Console Client"? 

Glad it worked for you, Texinga,

But do NOT use FAHCore v2.22 for your Kepler GPUs, because that will not work... You need v2.24 or v2.25 for Kepler. FAHCore v2.22 is for Fermi GPUs.

You are lucky that you had an P7623 WU running that requires FAHCore v2.25, also for Fermi GPUs and the client auto-updated your FAHCore to v2.25 again. If you would have had an other WU (e.g. P8018), than your Kepler GPU would have stopped folding.

TheWolf

texinga

TheWolf
Ya I was going to tell you to not try that at least not with a 76xx WU.
Sorry I should have spoken sooner.
You should be fine replacing the core with any 80xx WU.
Always attempt the core change over before it gets to far into a WU.
or you can also backup the queue.dat , work folder, unitinfo.txt & FAHlog.txt before the try.
If core fails you can overwrite with the back to start back @ the % you were at.

Excellent...I'll do that if/when I get a 80xx WU.  Thanks! 

Not sure how the console will act, let it work a few WU's to see.
But may have to remove the -betateam to get some different WU's.
Just something else you may want to try if it keeps getting 76xx WU.

Yes, I was thinking about that too earlier.  I'm gonna let her run for a few WUs just to see if things continue to work.  I'm guessing that at minimum that I have to use some form of -beta argument with a Kepler.  That is what I've consistently read is required to Fold on those cards.  So maybe with the Console Client, I'll have to use the -betateam argument as a baseline to Fold my Kepler.  I'd like to get free of these 7623's...they are pretty poor PPD with that 2.25 Core.  But I'm not complainin'...still happy with the results that you guys helped me achieve today!
 
Edit: Don't know where my head went, but I already know that I have to use -betateam for Kepler with the Console client.  That client won't accept the -beta flag...it is rejected as an invalid argument.  Found that out when I first began tinkering with the Console and Kepler.

DutchForce
Glad it worked for you, Texinga,

But do NOT use FAHCore v2.22 for your Kepler GPUs, because that will not work... You need v2.24 or v2.25 for Kepler. FAHCore v2.22 is for Fermi GPUs.

You are lucky that you had an P7623 WU running that requires FAHCore v2.25, also for Fermi GPUs and the client auto-updated your FAHCore to v2.25 again. If you would have had an other WU (e.g. P8018), than your Kepler GPU would have stopped folding.

Ok, appreciate the clarification and I'll just stick with what I can get using Core 2.25.  I'd used that 2.22 Core switch on my GTX580 already and it works very well (what a breath of PPD fresh air).  So I thought (wrongly) that I could do it with the Kepler and was sent to the corner by the client. 
 
Thanks again, you guys are a "wealth of knowledge"!

Use V7 for the GPUs
Tracker for smp
Seems to work

Like I said I'll be small fry once others step in
 
my max will be around 375k on the cards running QRB WU's
add in 40-100k from SMP
 
 
 

I think we are close to the final numbers when talking about QRB,if your GPU is out working a CPU then why would it be OK to take less points when it's doing more work.
 
But then, as long as the work gets done why should we care about the points.

I've been getting 8057's about half time for the last 48 hours. Pretty cool.

My take on points: the reason we fold is of course primarily for the greater good. Part of that greater good is a sense of community within teams whose members support each other in a myriad of ways from social to technical. Team formation is based on competition. The points scheme is the basis for that competition. Part of true competition is fair play, and in order to maintain fair play, rules ( point scheme being part of the rules) need to evolve with the overall infrastructure of which the "game" is based around. The latest schema change to maintain fair play? GPU QRB.

widsss

This is just my 2 cents.

I think the reason the QRB seems so high is that GPUs have been short changed for years. You put 8057 through a CPU and see if you get a 1.30 tpf. There was a post on [h] a couple weeks ago where a knowledgeable person broke down the QRB calculation and he concluded that it seemed accurate compared to CPU.

+1 to this! My thoughts exactly!

If these QRB wu's are still around at the beginning of next month, I can't wait to see the size of the EVGA Bucks spike that's coming..
Imagine.. usually the spike is spread out over a week or two.. now it will blossom like in 2 days, but it should be HUGE!! The overall gain for the month will be about the same, but for those couple of days.. wow! We'll set a PPD team record for sure.. if those units are still here!!

Snagged my first 8057.  12.7k PPD on a stock clocked GT 540m.  Wow.

Sweet...I love it.  Now we get to show what a "GPU-heavy" team can do when we are unleashed and enabled!! 

Wow, that sucks. I really feel for the guy given his huge commitment.

Punchy

AtlasFolder appears to be running only 2 4P AMD rigs at the moment.  I read a rumor that he sold all his GPUs to buy the 4Ps.

I feel for him too.. Speaking of 4p commitment ( I was one) whatever happened to these wu's?:
 
new bigadv/bigbeta projects
by kasson » Fri Jul 27, 2012 12:07 am
We are releasing several new bigadv and bigbeta projects:

Project 6905: base points 18165, preferred deadline 4 days, final deadline 10 days, k-factor 38.05
Project 6906: base points 25233, preferred deadline 4.5 days, final deadline 12 days, k-factor 37.31
Project 8102: base points 22607, preferred deadline 2.4 days, final deadline 4 days, k-factor 49.43

These should complete our move to the points guidelines we adopted around the beginning of this calendar year. We do continue to periodically assess bigadv performance and update our points guidelines and benchmarking procedures. We may perform some minor tweaking, but we expect the next assessment to take place around the end of this calendar year.

Thanks for participating in the bigadv program and for folding!
 

I get an occasional 8102, but have heard of no one getting the 6905 or 6906.. just the boring lower PPD 8101's.
I'm a little off topic, but had some hopes that these wu's would be similar to the (now defunct) 6903 and 6904 with corresponding QRB results...