Sell your 1060 and buy a 1650 / 1650 super

Bishop?
 

All of my mfaktc assignments are showing up in the GPU72 assignments report as assigned to a computer named "Bishop". I have no such machine.

[QUOTE=Chuck;533863]All of my mfaktc assignments are showing up in the GPU72 assignments report as assigned to a computer named "Bishop". I have no such machine.[/QUOTE]
I have one (a colab notebook) by that name. I tried to clear some manually assignments (that show up in my GPU72 assignments page) by dumping them into the woktodo file.

[QUOTE=Chuck;533863]All of my mfaktc assignments are showing up in the GPU72 assignments report as assigned to a computer named "Bishop". I have no such machine.[/QUOTE]

Ah, crap... Could you please PM me an example or two (exponent).

There have been no changes to any code, but this might be a "once a month" bug.

(Not meaning to gloat, but I just got home from watching fireworks with some friends; sitting on a beach in shorts and t-shirts, drinking fizzy wine and beers.)

Happy 2020 everyone!

[QUOTE=chalsall;533771]Yup, I'm afraid so.

Currently, Cat 4 is up in the 102M range. In a week or so, Cat 3 will enter 100M. We're still looking OK for Cats 0 through to 2.

But if anyone has any GPU compute available (perhaps Santa was kind???) we could *really* use some more TF'ing firepower.[/QUOTE]If you want help in TF, make it possible for non GPU72 to help. Leave some below 100M available to the rest of us to help TF without being part of GPU72. My gpu fleet is being forced to operate above 100M because it's not part of GPU72.

[QUOTE=Chuck;533863]All of my mfaktc assignments are showing up in the GPU72 assignments report as assigned to a computer named "Bishop".[/QUOTE][QUOTE=Uncwilly;533872]I have one (a colab notebook) by that name. I tried to clear some manually assignments (that show up in my GPU72 assignments page) by dumping them into the woktodo file.[/QUOTE]
[QUOTE=chalsall;533878]Ah, crap... Could you please PM me an example or two (exponent).

There have been no changes to any code, but this might be a "once a month" bug.[/QUOTE]
Seems fixed now for me.

[QUOTE=Uncwilly;533920]Seems fixed now for me.[/QUOTE]

Is there any chance you put a custom "Factor=" line into a Colab instance in the last day or so? Edit: Ah, I see that you said above that that's exactly what you did.

I /think/ what happened is you found a bug in my code; the ChkPoint code wasn't testing to see if the AID was blank, and so updated *everyone's* outstanding non-Colab assignments with your instance's CID.

Fixed.

[QUOTE=kriesel;533891]If you want help in TF, make it possible for non GPU72 to help. Leave some below 100M available to the rest of us to help TF without being part of GPU72. My gpu fleet is being forced to operate above 100M because it's not part of GPU72.[/QUOTE]

This is a bit tricky, in that Primenet will assign work sorted by P-1 desc, but not TF (grouped by 1M range).

I've just set things up such that GPU72 will now release at 76 bits in the Cat 2 and above ranges where P-1 has already been done. Several of our "big guns" who were working to 77 are now being giving work to 76.

I think it would be a good idea if George / Aaron set up Primenet such that Ben always got Cat 0 or 1.

I would welcome any other suggestions on how to deal with this situation.

[QUOTE=chalsall;533924]
I think it would be a good idea if George / Aaron set up Primenet such that Ben always got Cat 0 or 1.[/QUOTE]

All Ben's machines are Cat 1 eligible.

[QUOTE=Prime95;533929]All Ben's machines are Cat 1 eligible.[/QUOTE]

And yet I see *many* assignments in Cat 2; assigned as recently as 12.30. Is this a recent change?

[QUOTE=chalsall;533936]And yet I see *many* assignments in Cat 2; assigned as recently as 12.30. Is this a recent change?[/QUOTE]

No, been in place for months. I just looked at the "recent cleared" report and nearly all Ben's returned results are below 91M.

Not sure what assignments you are seeing and what their story is.