I just requested a bunch of LLTF work to take to 71 and 72 bits using the Lowest Exponent option, and got a number of DCTF assignments around 30M. Only I'm assigned to take them to 71 or 72 bits, not 70 bits. Was this intentional? Or should I stop and unreserve these and grab new assignments?

Considering the amount of work we've put into steering people away from DCTF, I'd say this was definitely a mistake.

[QUOTE=frmky;291682]I just requested a bunch of LLTF work to take to 71 and 72 bits using the Lowest Exponent option, and got a number of DCTF assignments around 30M. Only I'm assigned to take them to 71 or 72 bits, not 70 bits. Was this intentional? Or should I stop and unreserve these and grab new assignments?[/QUOTE]

Under my current assignments 30M exponents show as DCTF which is correct, but on my [URL="http://www.gpu72.com/reports/worker/b49e80e9382626afc7ebe2f81662dadb/"]progress report[/URL] 'work done' chart, my DCTF is flat for the last few days even though I turned in several per day. The system seems to be confused about that range and treats them as LLTF.

I would turn them back in and when you make your request, set the minimum exponent to 40M.

[QUOTE=Dubslow;291686]Considering the amount of work we've put into steering people away from DCTF, I'd say this was definitely a mistake.[/QUOTE]
Agree

Speaking of this...
[QUOTE=Bdot;291550]Probably one reason (for me the main one) for having a dedicated instance running only 69-70 is in a current deficiency of mfakto (a well-tested prerel-version that Kyle, flashjh and myself are running). The most efficient kernel of this version can only handle tests up to 70 bits, and the throughput difference compared to 71-tests is significant.[/QUOTE]

I've had much success with this pre-build. Any chance for a final version?

[QUOTE=frmky;291682]I just requested a bunch of LLTF work to take to 71 and 72 bits using the Lowest Exponent option, and got a number of DCTF assignments around 30M. Only I'm assigned to take them to 71 or 72 bits, not 70 bits. Was this intentional? Or should I stop and unreserve these and grab new assignments?[/QUOTE]

Whoops. Sorry -- that was an error. The new, lower load spider was used to grab a few hundred assignments in the 30M range, but set the worktype to be 100 rather than 101. Fixed.

But, yes please... Don't do that work -- unreserve them and get other work. The DC range definitly doesn't need to go to 72 bits!!! :smile:

[QUOTE=flashjh;291692]But on my [URL="http://www.gpu72.com/reports/worker/b49e80e9382626afc7ebe2f81662dadb/"]progress report[/URL] 'work done' chart, my DCTF is flat for the last few days even though I turned in several per day. The system seems to be confused about that range and treats them as LLTF.[/QUOTE]

No, it's not. If you look at your Work Done chart, you can see that the system is correctly detecting and graphing the (very small amount of) DCTFing you're returning. The line graph appears to be flat-lined simply because you haven't submitted enough work to be "worth a pixel" (:smile:).

[QUOTE=chalsall;291717]No, it's not. If you look at your Work Done chart, you can see that the system is correctly detecting and graphing the (very small amount of) DCTFing you're returning. The line graph appears to be flat-lined simply because you haven't submitted enough work to be "worth a pixel" (:smile:).[/QUOTE]

That's what that computer does too, a pixel's worth. Thanks.

Who took the two lowest 40M expos to 73? (Btw, no factor for any of my six.)

I just noticed that Spidey's new tricks also allowed it to get preferred DC expos. Are there any plans in place to clear those?

Mersenne.org seems to be down?! I can't submit anything.

Have you tried [URL]http://www.downforeveryoneorjustme.com/[/URL] ?

...Well, just pulling your leg. Of course [URL="http://www.mersenneforum.org/showthread.php?p=291596#post291596"]it is down[/URL].