[QUOTE=chalsall;291126]The problem was you Unreserved it on your G72 Assignments page, and Spidy then unreserved it from PrimeNet but wasn't able to recapture it in time.
[/QUOTE]

Sorry about that :/ - I thought once it was mine in PrimeNet only I could unreserve it.

Are Double Checks still on hold? I set the range to 0-28M, and could not get any. It says there are 46 available in the 26M range. I just now tried it with default settings, still says no availables matching criteria.

Unrelated: Can we have the CPUs and Num per CPU options for getting P-1 work? That would make the copy and pasting easier.

[QUOTE=Dubslow;291144]Are Double Checks still on hold? I set the range to 0-28M, and could not get any. It says there are 46 available in the 26M range. I just now tried it with default settings, still says no availables matching criteria.[/QUOTE]

No; nothing's on hold. And are you talking DCs, or DCTFs?

I just did a test DCTF allocation, setting the maximum to 28000000 and leaving the option "What Makes Sense" (Pledge to 70), and I was given a 26M assignment.

And so everyone knows, since we're so far ahead of the DC wavefront now, I'm keeping a few candidates below 29.69M for those who are willing to take them to 70. Adjust the maximum to be below 29.69, or choose the new "Lower Exponents to 70" option.

[QUOTE=Dubslow;291144]Unrelated: Can we have the CPUs and Num per CPU options for getting P-1 work? That would make the copy and pasting easier.[/QUOTE]

Sure. Added to the To Do list.

[QUOTE=chalsall;291164]
And so everyone knows, since we're so far ahead of the DC wavefront now, I'm keeping a few candidates below 29.69M for those who are willing to take them to 70. Adjust the maximum to be below 29.69, or choose the new "Lower Exponents to 70" option.
[/QUOTE]

One we reach 45M there will be no DC TF queue anymore I guess!

[QUOTE=chalsall;291164]No; nothing's on hold. And are you talking DCs, or DCTFs?
[/QUOTE]

The former, actual LL tests. I just tried again, and am still unable to acquire any, default settings. The available report says there are 50 at 26M, 39 at 69 bits and 11 at 70 bits.

[QUOTE=Dubslow;291175]The former, actual LL tests. I just tried again, and am still unable to acquire any, default settings.[/QUOTE]

Stupid programmer error.... My new quarantine conditional wasn't quite sane...

Fixed.

[QUOTE=KyleAskine;291169]One we reach 45M there will be no DC TF queue anymore I guess![/QUOTE]

That's years off, but it will simply mean the LL and DC "windows" will have shifted, and the DC work will be going to higher bit levels.

[QUOTE]But in addition to this, for anyone who's going to work on such assignments with either a GPU based system, or a CPU system which isn't going to talk to PrimeNet until the work is finished, could I ask that you still use Prime95/mprime to claim the assignment from PrimeNet when you get them?[/QUOTE]Does this apply to LLTF? Our boxes have no network access.

:sad:

[QUOTE=Xyzzy;291183]Does this apply to LLTF? Our boxes have no network access.[/QUOTE]

No -- only "real" LL and DC work.

All the candidates which are having LL-TF, DC-TF and P-1 work done are "owned" by Spidy, which checks in with PrimeNet at least once a month for each candidate to ensure they are not expired until all such work is completed.

I can now see the SQL query when I get DC work. It's just an aesthetic thing, but it does show the "Status=" part of the query as well, and somehow, I don't think you want that shown :wink::smile:
[QUOTE=chalsall;291164]
And so everyone knows, since we're so far ahead of the DC wavefront now, I'm keeping a few candidates below 29.69M for those who are willing to take them to 70. Adjust the maximum to be below 29.69, or choose the new "Lower Exponents to 70" option.[/QUOTE]
Note that the DC wavefront has now passed 29M, into the ~29.2M range, or at least, that's what PrimeNet gave me before I got some from here. I personally would not hold back those below the wave for extra factoring.

[QUOTE=Dubslow;291214]I can now see the SQL query when I get DC work. It's just an aesthetic thing, but it does show the "Status=" part of the query as well, and somehow, I don't think you want that shown :wink::smile:[/QUOTE]

Whoops... Not my best day... :cry: Although there's nothing "secret" about the Status field. It's 4 if owned by Spidy for LL/DC assignment.

[QUOTE=Dubslow;291214]Note that the DC wavefront has now passed 29M, into the ~29.2M range, or at least, that's what PrimeNet gave me before I got some from here. I personally would not hold back those below the wave for extra factoring.[/QUOTE]

Yeah, I know. I'm holding anything above 29.5M. (If you saw lower candidates available earlier today, it was because I was doing maintaince on another sub-system, and had turned off the returning script.)