I'll work on that batch of P32^7's, but it will take me longer now as I have to use these machines for other things too.

All the easy ones are now gone. It takes me a couple days to do a single number.

This [URL=http://www.lirmm.fr/~ochem/opn/t2100.txt]file[/URL] (t2100) has some easier ones but you will want to do the last level of ECM before proceeding to NFS.

Edit: This post was really meant for others if they are interested in favoring these numbers.

[QUOTE=RichD;451467]All the easy ones are now gone. It takes me a couple days to do a single number.

This [URL=http://www.lirmm.fr/~ochem/opn/t2100.txt]file[/URL] (t2100) has some easier ones but you will want to do the last level of ECM before proceeding to NFS.

Edit: This post was really meant for others if they are interested in favoring these numbers.[/QUOTE]

I guess now's as good a time as any to say that I started on t2100.txt. I haven't gotten far and am currently factoring:
[CODE]11631194393088792859842873946687015232225553151591153476380898256002252323964088836953804424786287610024987111057589267012201[/CODE]

If somebody want to throw more firepower at this, I'm quite alright with stopping after this number. Otherwise, I'll let this chug on in the background. :smile:

[QUOTE=RichD;451467]All the easy ones are now gone. It takes me a couple days to do a single number.[/QUOTE]I don't really mind spending a few days to factor a number, but which numbers are more valuable to the project to have factored?

I assume the numbers in the tXXXX file with the lowest XXXX are preferred? If so then there are a couple of interesting candidates in the t500 and t600 file worth having a go at. For example, [URL="http://www.factordb.com/index.php?query=1727870509%5E23-1"]1727870509^23-1[/URL] which I estimate might take me 1 - 2 weeks to crack.

However I don't know if there are others working on these numbers elsewhere. For the time being I still have four more P32^7-1's to be working on.

I haven’t worked on t2100.txt in quite a while. Proceed as you wish.

I am currently working on four numbers in the t600.txt file, all GNFS.
13739597803^23-1
108541^43-1
1861441475983^17-1
850534…^3-1
Two are over half done, one is just starting and the last I have a poly generated. I’ve skipped some easier SNFS numbers - meaning, they’re available.

That’s my goal to clear out t480, t490 and eventually t500. I have some at yoyo@Home and others at NFS@Home. 1727870509^23-1 is available (not sure of the ECM level) and 26010319^29-1 (similar difficulty) just finished up ECM at yoyo. Both are available.
Edit: Both are two small for NFS@H.

The preferable ones come from the Most Wanter Road Blocks (mwrb2000.txt) file but those are pretty big. I did pick a few out for yoyo with the hopes to eventually get them to NFS@H, if they survive ECM.

Can someone please tell me why I can't download t2100.txt? Firefox simply says "Connecting...", and stays like that forever. I tried using JDownloader, but it keeps timing out and saying "Host Offline?" and waits 15 seconds before attempting to download it again.

Edit: Now it's working in FF with an extremely long delay, but JD still won't download it. What's wrong with my connection?

[QUOTE=RichD;451508]The preferable ones come from the Most Wanter Road Blocks (mwrb2000.txt) file but those are pretty big. I did pick a few out for yoyo with the hopes to eventually get them to NFS@H, if they survive ECM.[/QUOTE]I took a look through mwrb2000.txt and most of the numbers in there are well outside my range, however I did find 8178376117^23-1 and 12301^59-1. Without sieving I'd estimate those numbers to take 2 and 4 months to complete respectively.

I'd like to reserve these two numbers for now and see how it goes:
26010319^29-1 (mentioned in your last post)
8178376117^23-1

A lot of the numbers in mwrb2000.txt didn't have many (large) factors. Does that mean that there hasn't been much ECM done for them or just that they are very difficult nuts to crack? If it is from lack of ECM then I could run some on the second number.

Just got a very nice split:
[URL="http://factordb.com/index.php?query=%2824590837369596000747323534000451%5E7-1%29%2F24590837369596000747323534000450"](24590837369596000747323534000451^7-1)/24590837369596000747323534000450[/URL] = c44 * p73 * p73

Looking a little closer at the t600.txt file I see some interesting facts.

As of today there are 456 numbers in the file. The largest number is C282. I doubt any of the bigger numbers have had much ECM, so I don’t think a GNFS job is lurking in the last bunch. Reviewing the last few numbers it looks like the most difficult job is an SNFS-299. Everything might be within reach. (Well, not by you or me :smile:).

Since whatever is in t600 is also in t800 and since anything below a C183 from t800 has 10,000 @ 43e6, we can assume the same for t600. The first 100 records fall into that category. If there are any GNFS jobs above, say 160, they will need a little more ECM.

That sounds like a good idea to target the first quarter of the t600 file with personal boxes.

[QUOTE=lavalamp;451543]A lot of the numbers in mwrb2000.txt didn't have many (large) factors. Does that mean that there hasn't been much ECM done for them or just that they are very difficult nuts to crack? If it is from lack of ECM then I could run some on the second number.[/QUOTE]

If the numbers made it to this file I would think they have quite a bit of ECM. But do they have enough? Probably not.

Chris2be8 ran some of these numbers (above SNFS-200) until he ran out of resources or patience. He did find an occasional ECM hit. I would say do the last complete level or the equivalent before starting SNFS.

[QUOTE=lavalamp;451543] A lot of the numbers in mwrb2000.txt didn't have many (large) factors. Does that mean that there hasn't been much ECM done for them or just that they are very difficult nuts to crack? If it is from lack of ECM then I could run some on the second number.[/QUOTE]

As far as I know roadblocks are numbers with no known non-trivial factors. So if a factor was found it would be removed from the file. Eg 11^311-1 isn't in it now even though it's not fully factored in factordb.

Chris