Trippple Checks

[Madpoo]

Originally Posted by ATH

I can take those needing extra verification, but it will not be quick as my computer is far more botanical than beefy.

I'm still waiting on the last one (22M range) with another 2 hours to go and 4 in the 6M-7M range with a few minutes left, but so far it looks like all of the others have passed okay.

Seems like those odd app versions only sometimes had a funky residue.

At least now there will be at least one "normal" residue in the bunch.

[Madpoo]

Originally Posted by Madpoo

The only really odd one out was on that exponent http://www.mersenne.org/M3365707 where the mismatched result actually came from app #67: "Windows,Prime95,v16,(aka WS1)"

It looks like George has marked my previously bad results as verified. There is still this odd one where the residue from "Reto Keiser" is different in just one nibble... an F instead of 2.

That one seems like it's a little too close but also different, and it's version is v16 of Prime95 so I'm kind of wondering if that's just some mistake that it was marked as good?

I'll be honest, I wrote a query to find the mismatches but I sat and stared at this for a while before my brain noticed that one little difference. Took me back to an old data entry temp job I had as a teen, comparing figures from two printouts. Ugh.

[Madpoo]

Originally Posted by Anonuser

I'll take the exponents between 40000000 and 55000000 in the updated list (TF only).

Noted, and new list attached.

Special mention to anyone doing double-checks in some of these ranges. VictordeHolland is doing some extra TF work and if you've already pasted in some worktodo entries for double-checking, you might look again in case he found any factors for those.

Especially for ATH: He found factors on 17358223 and 17042323 which are in the range you were going to triple-check, so make sure you don't bother with those.

I don't know how far he's going to TF at different ranges, but he's found 6 more factors so far by going an extra bit (68 to 69, or 69 to 70). That's cool.

On the downside, curtisc has checked in two more self-verified results in the 39M range. Oh well.

[Gordon]

Originally Posted by Madpoo

If you're serious about that, I can generate a list of exponents for you matching whatever criteria.

Like, if you set your cutoff points for "exponents below XXX I want to take to TF depth 68" and then "exponents up to YYY to depth 69" etc.

I can spit out a list of exponents that are not currently at whatever levels and send you the list. This *might* be something James at mersenne.ca could do, or GPU72 might have the reports you need to do the same basic thing.

For much smaller exponents, like below 1M, I have no idea if it would make any sense to factor them beyond where they are, like 501013 which has been factored to 61 bits. I mean, I haven't given any thought at all to what it would take to factor it higher or if it would be useful, etc.

61 bits appears to be the current "floor". All exponents that have had any factoring done at all have at least been TF'd to that depth.

Or I could generate the report here?

Ticking the options to "exclude currently assigned" and "ouptut tf worktodo..."

[lycorn]

Actually, if you tick "Output TF worktodo...", all relevant options will be automatically ticked.
That´s a very convenient tool to manually assign TF work.

[Madpoo]

Originally Posted by Gordon

Or I could generate the report here?

Ticking the options to "exclude currently assigned" and "ouptut tf worktodo..."

Doh! Yeah, that's much easier. LOL I forget sometimes what kinds of things are already on the site. :)

[Prime95]

Originally Posted by Gordon

Just out of interest I loaded that onto the 970, taking it one more bit (65-66) took exactly 7 minutes. I smell an interesting sub project of going right back to the lowest exponents and taking them all up to say 68 bits which for exponents in this range is just 42 minutes.

I have mixed feelings on this. I'd rather GPUs only TF'ed above 10M. Below 10M we are running ECM. ECM will (in all probability) find the factors a GPU would find. Plus, the GPU effort does not reduce the ECM effort required.

[Gordon]

Originally Posted by Prime95

I have mixed feelings on this. I'd rather GPUs only TF'ed above 10M. Below 10M we are running ECM. ECM will (in all probability) find the factors a GPU would find. Plus, the GPU effort does not reduce the ECM effort required.

Can you ECM it in 7 minutes? (66 bits test), it certainly does reduce the ECM required if it finds factors.

I have my cpu running ecm and it found a 69.5 bit factor on a 9.9m exponent that had tf stopped at 66 bits.

Sounds like there might be a lot of low hanging fruit just waiting to be picked, if I put the 2x660 and the 970 onto it.

That's about 400 exponents per day...

[Prime95]

Originally Posted by Gordon

Can you ECM it in 7 minutes? (66 bits test), it certainly does reduce the ECM required if it finds factors.

It will rarely reduce ECM as there are people trying to completely factor Mersenne numbers. So you'll save ECM work for the few factors you find that complete the factorization of the Mersenne number.

Sounds like there might be a lot of low hanging fruit just waiting to be picked,

Yes there is, and as always do whatever you find most fun with the knowledge that your work will not save very much effort in the long run.

[Anonuser]

Originally Posted by Anonuser

I'll take the exponents between 40000000 and 55000000 in the updated list (TF only).

My TF work is finished and submitted. I have cleared another 9 exponents:

M40381163 has a factor: 8987211259220713015249
M40859123 has a factor: 5665798530135723471577
M43127009 has a factor: 1218831075927922955879
M47084633 has a factor: 15762885842061282250801
M47813189 has a factor: 3014711912786173278017
M48914651 has a factor: 5869800563601119262529
M49120919 has a factor: 12890679828688757973847
M51602137 has a factor: 7188601069583227163689
M54865127 has a factor: 12712283309860820589703

Currently, I have not planned to do any more work between "40000000" and "55000000" (resp. between "30000000" and "35000000"). (It can be marked as completed.) From my point of view, anyone who wants to do more work in these ranges can feel free to do so.

[Madpoo]

Originally Posted by Anonuser

My TF work is finished and submitted. I have cleared another 9 exponents:

M40381163 has a factor: 8987211259220713015249
M40859123 has a factor: 5665798530135723471577
M43127009 has a factor: 1218831075927922955879
M47084633 has a factor: 15762885842061282250801
M47813189 has a factor: 3014711912786173278017
M48914651 has a factor: 5869800563601119262529
M49120919 has a factor: 12890679828688757973847
M51602137 has a factor: 7188601069583227163689
M54865127 has a factor: 12712283309860820589703

Currently, I have not planned to do any more work between "40000000" and "55000000" (resp. between "30000000" and "35000000"). (It can be marked as completed.) From my point of view, anyone who wants to do more work in these ranges can feel free to do so.

Awesome, good work finding all those. You must have a nice setup to go through those ranges so quick. I'm still jealous of those folks with GPUs that can do that kind of fun stuff.

Since I might be the one to do the triple-checks in those ranges, I especially appreciate how many factors were found in there. Very nice.

EDIT: Wow, I just looked at the 40-55M range and saw you moved it from 69-72 bits up to 74 bit depth for them. Above and beyond. :)