[QUOTE=debrouxl;433970]If CADO generates better polynomials than msieve in the difficulty ranges we're interested in, like it does for large numbers nowadays, yeah, that would make sense. I suggested msieve because that's what we know best, and using it is easy :smile:[/quote]Having used both cado-nfs and msieve, I'd say the choice isn't clear cut. For a given amount of computation, cado-nfs usually generates better polynomials. For a given amount of time, msieve running on a gpu-equipped machine usually wins out. Brute force can indeed be competitive with smartness.

[QUOTE=debrouxl;433970] all projects maintain information about factors and who found them.[/QUOTE]Something I've been keen on for the GCW and HCN projects since day one. It irritates me intensely that three factorizations in the GCW tables are labelled "Anonymous lookup 2016-0x-yz" because the only source I can find is FactorDB. In these cases the date is that when I looked up the factorization, not the date when it was first discovered.

[QUOTE=xilman;434177]It irritates me intensely that three factorizations in the GCW tables are labelled "Anonymous lookup 2016-0x-yz" because the only source I can find is FactorDB. In these cases the date is that when I looked up the factorization, not the date when it was first discovered.[/QUOTE]

If you look up each of the factors and click the arrow next to "More information" you should be able to find when the factor was added to factordb.

I know factordb keeps other information, including the IP address it was submitted from, but I don't know any way to get that (short of asking Syd, if you can find him).

Chris

Here are the last of the "easy" xyyx composites needing no additional ECM. Polys are attached.

C187_133_54
C215_134_80
C189_134_82
C211_123_77
C179_125_73
C203_125_72
C203_148_46
C225_122_79
C209_131_59
C207_130_108
C216_150_44
C204_121_84

C199_121_91 (survived 8000 curves @B1=11e7)


The remaining SNFS numbers of the xyyx project are [url=http://www.mersenneforum.org/showthread.php?t=21243]being queued for proper ECM vetting[/url].

[QUOTE=debrouxl;434137]Andrey: which number / polynomial from that page, exactly ? :smile:
That would be food for 15e. And I'll probably queue it before the big GNFS 188.[/QUOTE][url=http://www.mersenneforum.org/showpost.php?p=434349]Here we are[/url]:[code]n: 344791381226851287279185036034642635800505109743063349757290593755437104984269862201468187980362970210149169351930
33172364267380987223293686993196656448672279611520337389721
skew: 1335808.0
c0: 387791869088524171451616910842298125552
c1: -1627706106635766854677420302311924
c2: 713730807612923775332352144
c3: 2041990797545923660967
c4: -104446892249868
c5: 36412740
Y0: -1232221203350897612542968561876865
Y1: 18890353014002536254449
# MurphyE (Bf=1.00e+07,Bg=5.00e+06,area=1.00e+16) = 2.25e-13
# lognorm 53.56[/code]

I see I'll have to look into providing test sieving as well as poly select... :smile:

I'll have a 2.26 and a pair of 2.20's in the poly select thread for this C173 shortly. A second -npr run is finishing up presently.

Grid-based GNFS polynomial selection is something that has interested me for years. Adding a GPU application to NFS@Home can potentially bring in hordes of new contributors, and I think that nobody has really pushed the limits of massively parallel polynomial selection at the largest input sizes. Also, if the administrative effort is tolerable we can run CADO-NFS for smaller poly selection jobs (say, 1 host = 1 number) and GPU Msieve for larger ones, possibly as a first stage for the latter with offline CADO polishing of the best results.

I would be willing to devote time to make some fraction of the above happen; what would we need?

[QUOTE=jasonp;434382]

I would be willing to devote time to make some fraction of the above happen; what would we need?[/QUOTE]

Contact Greg in first instance...
From my side I'll bring some GPU power to the project (it must pay very good credits like Collatz project, 3500 points per 60 seconds run)

An error has occurred
 

nfs@home is sieving, and Dmitri is linear-algebraing, 118^109+109^118, but this is already factored in factordb and in XYYXF's results2.txt file (creation date of factor 29/4/2016 0106 or so)

[QUOTE=fivemack;434537]nfs@home is sieving, and Dmitri is linear-algebraing, 118^109+109^118, but this is already factored in factordb and in XYYXF's results2.txt file (creation date of factor 29/4/2016 0106 or so)[/QUOTE]

It's already reported - [url]http://mersenneforum.org/showthread.php?p=432664#post432664[/url]

And C167 from aliquot 3366:2132 was factored too - [url]http://mersenneforum.org/showthread.php?p=433503#post433503[/url]

They can be removed from the list.

146^61+61^146 has been reported as well. [url]http://www.mersenneforum.org/showpost.php?p=432465&postcount=849[/url]. It can be moved to completed status.